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

Peter Hunkeler

unread,

Feb 19, 2015, 7:40:39 AM2/19/15

to

Today, 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 jbs 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.

--
Peter Hunkeler

Lizette Koehler

unread,

Feb 19, 2015, 9:42:04 AM2/19/15

to

A quick internet search turned up
http://www-01.ibm.com/support/docview.wss?uid=isg1OA21984

OA21984: $HASP311 ISSUED REPEATEDLY FOR SAME JOB

Does this help?

Lizette

> -----Original Message-----
> From: JES2 discussion group [mailto:JES...@listserv.vt.edu] On Behalf Of
> Peter Hunkeler
> Sent: Thursday, February 19, 2015 5:40 AM
> To: JES...@LISTSERV.VT.EDU
> Subject: $HASP311 jobname re-queued at end of memory and held
>
> --SZ_634223056_549809500
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="ISO-8859-1"
> Content-Transfer-Encoding: quoted-printable

>
>
> Today, 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

> detail= s.

>
>
> 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 jbs 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.
>
>
>
> --
> Peter Hunkeler

Peter Hunkeler

unread,

Feb 19, 2015, 12:29:56 PM2/19/15

to

>A quick internet search turned up
>http://www-01.ibm.com/support/docview.wss?uid=isg1OA21984
>
>OA21984: $HASP311 ISSUED REPEATEDLY FOR SAME JOB
>
>Does this help?

I had seen this one, too. And no, it does not help to understand the mechanisms. Thanks anyway.

--

Peter Hunkeler