Re: $HASP311 jobname re-queued at end of memory and held

2015-03-24 Thread Shane Ginnane
On Tue, 24 Mar 2015 09:02:49 +0100, Peter Hunkeler wrote: So, the action taken at next warmstart will be determined by the setting of JOURNAL and RESTART on JOBCLASS. However, you could decide to release the job ($AJ) or cancel it ($PJ) immediately. ... And an additional hint: The job is

Re: $HASP311 jobname re-queued at end of memory and held

2015-03-24 Thread Tom Marchant
On Tue, 24 Mar 2015 09:02:49 +0100, Peter Hunkeler wrote: an End-of-Memory condition The way I used to understand it is that a Memory was once a common term for an an address space, and that the End of memory message simply meant that the address space (the initiator) terminated, taking the

Re: $HASP311 jobname re-queued at end of memory and held

2015-03-24 Thread Anthony Thompson
Note also the DIAGxx parameter VSM CHECKREGIONLOSS(above,below) which looks at an initiator address space at the end of each job and automatically restarts the initiator if a loss of virtual storage exceeding the specified values is detected. This parameter is intended to avoid or minimize job

Re: $HASP311 jobname re-queued at end of memory and held

2015-03-24 Thread Anthony Thompson
Oh... of course the proper syntax is VSM CHECKREGIONLOSS(below,above) not (above,below), if anyone cares. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Anthony Thompson Sent: Tuesday, 24 March 2015 6:29 PM To:

Re: $HASP311 jobname re-queued at end of memory and held

2015-03-24 Thread Peter Hunkeler
Cross-posted to IBM-MAing and JES2-L A while ago I was seeking for help regarding jobs being re-queued at an EOM situation. I did not get the desired insight here, so we asked IBM for details. We got below explanation, which IBM support found in internal documents, only, but not in any FM. I

Re: $HASP311 jobname re-queued at end of memory and held

2015-02-21 Thread Steve Horein
It seems I've seen this kind of behavior when the initiator the job was running on would ABEND. That may be something to look at. To address that symptom, I put some automation around $PI/$SI once a week. That was circa OS/390 2.10 time frame. ​

$HASP311 jobname re-queued at end of memory and held

2015-02-21 Thread Peter Hunkeler
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 $HJnnn while the job was

Re: $HASP311 jobname re-queued at end of memory and held

2015-02-21 Thread Lizette Koehler
So APAR OA21984 states you would need JOURNAL=YES on JOB. Without complete understanding of your JES2 INIT Deck, you initiators, I am not sure if we can answer that question. You might open an SR with IBM to get in-depth knowledge for your question. I am not sure that IBM provided full