---------------------------<snip>----------------------------
FWIW, I looked back through our log and discovered that this is
happening to us *every* morning in our z/OS V1R7 JES2 environments!
$COJOBQ,Q=ABCDEHIKMNOSTUWXY0123456789,DAYS>60
$HASP263 WAITING FOR ACCESS TO JES2 CHECKPOINT VOLUME MVSJ21
$HASP263 WAITING FOR ACCESS TO JES2 CHECKPOINT VOLUME MVSJ21
*$HASP9203 LONG PCE DISPATCH 214
DURATION-000:00:13.94 PCE-COMM EXIT-NONE JOB ID-JOB03849
COMMAND-$COJOBQ,Q=ABCDEHIKMNOSTUWXY0123456789,DAYS>60
IEF196I IOS071I 2036,**,*MASTER*, START PENDING
IOS071I 2036,**,*MASTER*, START PENDING
*$HASP9207 JES2 CHECKPOINT LOCK HELD 247
DURATION-000:00:18.03
[it finally breaks free and cancels the intended output]
$HASP9301 JES2 MAIN TASK ALERTS CLEARED
$HASP9302 JES2 CHECKPOINT LOCK RELEASED
No similar issues exist for our JES3 environments.
------------------------<unsnip>------------------------------
Now THAT looks familiar. It appears to be a VERY LONG RESERVE of the
Checkpoint volume. Does the same happen if you shorten the Q= operand to
just one or two classes? How large is the OUPUT Q ?? Would be nice to
know which images the various messages were coming from. Different
images or all the same image?
----------------------------------------------------------------------
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
