Crossposted. I had posted this on the JES2 list but got no insight so far. Hopefully someone here can shed some light on this.
I stumbled across a job that had ended and was in status HELD in the JES2 execution queue. First I thought someone must have issued a $HJnnnnnnn while the job was running. I then saw that the job has had some problems (878-10 abends) which finally lead the job and the initiator being terminated at end of memory (initiated by DB2 - step ends with S0F4 reason F30905). Now the intersting thing which I didn't know (and don't understand either), and for which I was not yet able to find where this is documented: JES2 writes message "$HASP3111 jobname RE-QUEUED AT END OF MEMORY AND HELD" Well, I've found the doc on message $HASP311 but it doesn't tell much details. Questions I have: - When are jobs eligible for this kind of JES2 automatic restart? - What are the factors being part of this decision? - Not sure all jobs are restartable per se. - What would have happended to the job at next JES2 warm start? - How to correctly handle jos in this state? - Can this be configured? Can someone shed some light on this and/or point me to the document where I can read how this works. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
