A point of confusion has arisen regarding TIME and what it refers to with
respect to (1) JES2 JOBCLASS, (2) SMFPRMxx JWT, (3) TIME= specified on the
JOB or EXEC statements, and (4) the difference between S322 and S522
completion codes. Our shop "defaults" are JOBCLASS TIME=(30,0) and SMFPRMxx
JWT(0030).
Programmer submitted a job with TIME=120 on the JOB card. Third or fourth
jobstep caused job to ABEND S322 at 32 minutes after STEP initiation. RTFM
of the JCL Reference Manual says that TIME on the JOB card can only DECREASE
allowable time from "defaults"; and that to INCREASE allowable time TIME=
must go on the EXEC card. It also says (in the description of TIME= for the
JOB card):
"Every job step has a time limit. If you do not specify a TIME parameter on
the JOB statement, the time limit for each job step is:
The value you specify for the TIME parameter on its EXEC statement, or
The default time limit (that is, the JES default job step time limit), if
you do not specify a TIME parameter on its EXEC statement.
If you specify a value other than TIME=NOLIMIT or TIME=1440, SMF uses its
current job wait time limit."
That last sentence is where the confusion arose, because we had always
believed that the TIME specified in JES2 JOBCLASS and on the JOB or EXEC
statements referred to CPU time, and JWT in SMFPRM referred to wallclock
time. Apparently that is not true? And since we also know that the batch
job was waiting for access to VSAM datasets that a CICS region had
allocated, why wouldn't it have abended S522 instead of S322?
TIA,
-jc-
----------------------------------------------------------------------
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
