At 03:46 +0530 on 06/05/2013, baby eklavya wrote about Re: JES2
conversion delay:
Hello Doug ,
We had this problem 2 or 3 times in past few months . But each time , 4
jobs were affected (coincidence or not ) .Jobtrac by design issues the $AJ
command after 500 Milliseconds once it puts the HOLD . In that case , the
JCL conversion should have crossed more than 500 Milliseconds . If i
understand your previous comment right , the JCLLIB dataset for all these 4
jobs should have got migrated and HSM took longer than 500 Milliseconds for
the recall and make them available . Is that correct ? please correct me if
i understood wrong .
There is the solution to the HSM problem of just flagging the JCLLIB
dataset(s) as non-migrate so they do not need to be migrated back.
You can also force a backup periodically (which does not remove it
from DASD but only creates a migrated copy and for use if you need to
migrate back to DASD - if I remember if a dataset is selected for
migration and it has not been altered since the last backup the
physical migration is bypassed).
Another solution (which might not be viable) is to set the submitted
job to a non-executable class (with no TYPERUN=HOLD on the JOB Card
so it converts) and after 1 minute issue a $HJ and alter it to the
correct execution class.
Also you can up the wait interval from 500 milliseconds to something
longer such as 2 or 3 seconds.
Regards,
Baby(Sachin)
On Wed, Jun 5, 2013 at 1:56 AM, Baby Eklavya <[email protected]> wrote:
We dont have any other datasets on the checkpoint volume . I would also
plan to increase the no of converter tasks .
Regards,
Baby(Sachin)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
