Well, I have a solution. The $HASP308 message is indeed being issued by the JES2 task. So, what I do is trap the $HASP308 message using CA-OPS/MVS. I then parse out the name of the job from the message. I then use the OPS function OPSTATUS with that job name. This gives me the JES2 jobid and the RACF owner id as well for the job. I can then test the RACF id to see if it is a programmer. If it is a programmer, I can use the JOBID from OPSTATUS to issue a $DMJ message on the job telling the programmer that it ran too long. I then issue a $CJ command to cancel the job.
I don't like this, but it conforms to the specifications given to me my the people who pay my salary. -- John ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
