Exspans Systems Inc Logo home
 
Forum
Sign up Calendar Latest Topics
 
 
 


Reply
  Author   Comment   Page 2 of 6      Prev   1   2   3   4   5   Next   »
rakesh

Member
Registered:
Posts: 52
Reply with quote  #16 
Hi, I got the documents. They are self explanatory and easy to understand. Nicely written. And i see aumoman can do lot of things. I will start with simple functionalitues initially. Eagerly awaiting for the the loadlib :-). Thanks a lot.
0
automan

Avatar / Picture

Moderator
Registered:
Posts: 136
Reply with quote  #17 
rakesh, here is the load library for your school, generated for Stage 2 message monitoring only. When you have it installed and running get the licence serial number and send it to support@exspans.ca to do the serial update.

http://forums.exspans.ca/file?id=2318922

0
rakesh

Member
Registered:
Posts: 52
Reply with quote  #18 
Hi,

I downloaded the copy of the libs and started configuring. AUTOMAN task is up now. I see the message in the start log stating the product is only valid for 29 days :-(

12.20.26 STC07929 AUTOMAN License expires in 29 days

And i sent the serial number to support email id.

The documents you sent have only 9 examples of message interpret. Where can i find all the option i can use on "qualification logic and response" sections?
Is it possible to share documentation of "Generalized Automation Language Guide V3.2"

For some reason, i am unable to run my first test.

Here is what i have:

AUT0085I System XCF Local. Prefix > applies to this system only
AUT0076I SYSPLEX Command prefix is now >
AMAN055W SYSLOG record length set to 121
AMAN054W SYSLOG block size set to 6050
AMAN019I Dft PARM lib=AUTOMAN.SYSPARMS
AMAN019I Dft CMDS lib=AUTOMAN.SYSCMDS
AMAN019I Dft JOB lib=AUTOMAN.SYSJOBS
AMAN448W Compiler option not enabled. SYSLOAD ignored
AMAN105W CLASS not specified EMAIL support dropped
AMAN039I Cross systems communication is inactive
AMAN012I AUT0 Starting on ADCD
AMAN194W AutoMan is interlocked with JES
AMAN006I Starting Stage 2 Monitor
AMAN019I Initialization in progress for SYS1AUT0
IEA630I OPERATOR SYS1AUT0 NOW ACTIVE, SYSTEM=ADCD , LU=SYS1AUT0
AMAN020I Initialization of SYS1AUT0 is complete
AMAN031I No scheduling will be performed
AMAN008I Environment Initialization is complete
AUT0080I Online and ready

AUTOMAN.SYSPARMS(MESSAGES)
MSG=$HASP395 VAR=&JOB POS=10 LEN=8 CMD(P &JOB)

AUTOMAN.SYSPARMS(ENVIR)
MONITOR=ON

AUTOMAN.SYSPARMS(INPUT)
MSGID(*(MESSAGES))

what am i missing here?

Thank you
0
automan

Avatar / Picture

Moderator
Registered:
Posts: 136
Reply with quote  #19 
Hi,

I downloaded the copy of the libs and started configuring. AUTOMAN task is up now. I see the message in the start log stating the product is only valid for 29 days :-(

12.20.26 STC07929 AUTOMAN License expires in 29 days

And i sent the serial number to support email id.

-------------------
This is standard behaviour and the response you will be getting will fix this




The documents you sent have only 9 examples of message interpret. Where can i find all the option i can use on "qualification logic and response" sections?
Is it possible to share documentation of "Generalized Automation Language Guide V3.2"


--------------------------------------

Yes, it will be posted for you shortly. If you have specific questions ask them here and I will arrange for you to get the information you need.

----------------------------------
For some reason, i am unable to run my first test.

Here is what i have:

AUT0085I System XCF Local. Prefix > applies to this system only
AUT0076I SYSPLEX Command prefix is now >
AMAN055W SYSLOG record length set to 121
AMAN054W SYSLOG block size set to 6050
AMAN019I Dft PARM lib=AUTOMAN.SYSPARMS
AMAN019I Dft CMDS lib=AUTOMAN.SYSCMDS
AMAN019I Dft JOB lib=AUTOMAN.SYSJOBS
AMAN448W Compiler option not enabled. SYSLOAD ignored
AMAN105W CLASS not specified EMAIL support dropped
AMAN039I Cross systems communication is inactive
AMAN012I AUT0 Starting on ADCD
AMAN194W AutoMan is interlocked with JES
AMAN006I Starting Stage 2 Monitor
AMAN019I Initialization in progress for SYS1AUT0
IEA630I OPERATOR SYS1AUT0 NOW ACTIVE, SYSTEM=ADCD , LU=SYS1AUT0
AMAN020I Initialization of SYS1AUT0 is complete
AMAN031I No scheduling will be performed
AMAN008I Environment Initialization is complete
AUT0080I Online and ready

AUTOMAN.SYSPARMS(MESSAGES)
MSG=$HASP395 VAR=&JOB POS=10 LEN=8 CMD(P &JOB)

AUTOMAN.SYSPARMS(ENVIR)
MONITOR=ON

AUTOMAN.SYSPARMS(INPUT)
MSGID(*(MESSAGES))
------------------------

What is not working?
0
rakesh

Member
Registered:
Posts: 52
Reply with quote  #20 
My intent is to let AutoMan issue a "P JOBNAME" when we the job completes. Here is the message which i want Automan monitor and get the job name out of it and issue purge to it.

15142 21:07:08.61 JOB08406 00000281 $HASP395 SHRDV01R ENDED

So, i coded below condition:
MSG=$HASP395 VAR=&JOB POS=10 LEN=8 CMD(P &JOB)

But i don't see Automan issuing Purge against the job.

When i listed "D MSGID" i expected to see all the MSGIDs defined to Automan but i see just the file name.
15.53.30 STC08211 DSN=AUTOMAN.SYSPARMS MEM=MESSAGE

Is there a special command to see all the active MSGIDs. This will be useful once i add a new MSGID with "LOAD or UPDATE"

Thank you
0
automan

Avatar / Picture

Moderator
Registered:
Posts: 136
Reply with quote  #21 
Are you absolutely sure about the position of the jobname in that message. I believe system options may insert jobid information in front of the name.

Experiment to see what you are picking up

MSG=$HASP395
VAR=&JOB POS=10 LEN=8
WTO 'XXXX???? jobname=&JOB'
* CMD(P &JOB)

to see what is picked up in position 10


0
automan

Avatar / Picture

Moderator
Registered:
Posts: 136
Reply with quote  #22 
D MSGID displays the names of the files from which the message identifiers were loaded, and is updated when you issue a LOAD command. There is no console command to display all the loaded message identifiers. It would be impractical to do that because there can be potentially many thousands of message intercepts defined for a system.
0
rakesh

Member
Registered:
Posts: 52
Reply with quote  #23 
Hi,

Please ignore my previous post. Automan is working perfectly now. :-)
I will do somemore testing before i apply for production messages.

Only one outstanding question is:

When i listed "D MSGID" i expected to see all the MSGIDs defined to Automan but i see just the file name.
15.53.30 STC08211 DSN=AUTOMAN.SYSPARMS MEM=MESSAGE

Is there a special command to see all the active MSGIDs. This will be useful once i add a new MSGID with "LOAD or UPDATE"

Thank you
0
automan

Avatar / Picture

Moderator
Registered:
Posts: 136
Reply with quote  #24 
When i listed "D MSGID" i expected to see all the MSGIDs defined to Automan but i see just the file name.
15.53.30 STC08211 DSN=AUTOMAN.SYSPARMS MEM=MESSAGE

---------------------------------------

This command displays the dataset name from which the message intercepts were loaded.
There is no command to list each individual message as there could be thousands of them.
0
rakesh

Member
Registered:
Posts: 52
Reply with quote  #25 
Hi sir,

ok, i got it. just a suggestion, it might be useful if there could be command to list the MSGIDs. Might be we can direct the output to SYSLOG DD if we think its huge.

The commands that Automan issuing based on MSGIDs are not leaving any traces in neither SYSLOG or Automan "SYSLOG" dd.

We see the response for the CMDs in SYSLOG and JESMSGLG but not that command itself.

MSGID: MSG=$HASP395 CMD(D T) WTO 'DISPLAYING TIME COMPLETED'

00000281 $HASP395 SHRDV06 ENDED
00000090 IEE136I LOCAL: TIME=02.33.23 DATE=2015.143 UTC: TIME=08.33.23
DATE=2015.143
00000090 DISPLAYING TIME COMPLETED

Is there any DD name or LOG where AUTOMAN write the commands it's issuing?

Thank you
0
automan

Avatar / Picture

Moderator
Registered:
Posts: 136
Reply with quote  #26 
The message ids are echoed to SYSLOG when they are interpreted, so you can see a list there

See COMMAND HARDCOPY on page 31 of Startup and General Usage Manual for information about displaying internal commands to the log.
0
rakesh

Member
Registered:
Posts: 52
Reply with quote  #27 
It worked. Thanks a lot. I see the command along with it's response in logs

STC08467 D T
STC08467 IEE136I LOCAL: TIME=10.22.33 DATE=2015.143 UTC: TIME=16.22.33 DATE=2
STC08467 DISPLAYING TIME COMPLETED
0
rakesh

Member
Registered:
Posts: 52
Reply with quote  #28 
While i am reading the documents, i found this.

Aren't these statements conflicting:

Page 8 in "Message Automation.pdf"
The LEN option specifies the maximum number of characters that the variable can hold. If no LEN is given the default length of 31 is used.

Page 11 in "GAL guide"
If a string variable is defined without a length attribute the system default length of 32 is used as the maximum length attribute.

One book says length of 31 while other says 32.

Or am i got confused?

And: I was trying to auto reply for a WTOR.

*18 IEF238D IBMUSERA - REPLY DEVICE NAME OR 'CANCEL'.

MSG=IEF238D
VAR &JOBN LEN 8
LET &JOBN=$$MSGJNM
LET &R1=$$MSGRID
REPLY &R1 (CANCEL)
WTO '&R1 &JOBN'

Below is from log:

AMAN082E Invalid variable for reply ID
AMAN081E No reply made. ID var &R1 Too short
&R1 IBMUSERA
INVALID VOLUME MENTIONED ON JOB IBMUSERA AUTOMATION CANCELLED THE JOB
AMAN955E AMCMCSCN Abend RC=840C4000 Reason=00000011
AMAN995I in AMCMCSCN PSW=078C4000 9E6626D2
AMAN R0=00000000 0000000C 00000000 1E61D208
AR0=9E043D16 00000000 00000000 00000000
AMAN R4=0000438C 1E5DCDE8 000042D4 1E5DCDC8
AR4=00000000 01020038 01020038 00000000
AMAN R8=1E5DCDF0 1E5C21BC 1E65C01C 00000000
AR8=00000000 00000000 00000000 01020038
AMAN RC=9E662000 1E61D070 00000006 00000000
ARC=00000000 00000000 00000000 00000000
AMAN801I Monitor Recovering from Abend

-------------------
I even tried to allocate length=100 for &R1. I still got same error.

Could you help

Thank you
0
automan

Avatar / Picture

Moderator
Registered:
Posts: 136
Reply with quote  #29 
The default length is 32. Thanks for finding the error. You get the Golden Eyeball prize. I will get the manual fixed.

The length of the variable used is the actual length, not the defined length. The actual length is set by the assignment.

&R1 is not defined in that script so it does not know to use it as a replacement variable. The message id is not used if you are replying to a message in context of the message. It is only used if you are delaying replying until some other event has occurred.

MSG=IEF238D
VAR &JOBN LEN 8
LET &JOBN=$$MSGJNM
REPLY (CANCEL)
WTO 'Job &JOBN cancelled'

I will look at why that caused the error.
0
automan

Avatar / Picture

Moderator
Registered:
Posts: 136
Reply with quote  #30 
I have tested this construct

MSG=IEF238D
VAR &JOBN LEN 8
LET &JOBN=$$MSGJNM
LET &R1=$$MSGRID
REPLY &R1 (CANCEL)
WTO '&R1 &JOBN'

and and cannot reproduce your result. I would like to see the whole of your message intercept definition to find out why this has failed.
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:


Create your own forum with Website Toolbox!