On 2017-05-24 11:46 PM, [hidden email] [H390-MVS] wrote:
> Running with 1440 will NOT prevent a S522, only S222/S322. ECB wait
> time has nothing to do with the time parameter on the job.
I think I must disagree...
TIME=1440 in the JCL causes the flag in the ASCB to be set which tells
the system to not apply time limits. These time limits are the CPU time
(normally S322 abend if you exceed this) and WAIT time (normally S522
abend if you exceed the JWT value specified in the active SMFPRMxx
S222 abend occurs when the operator issues a CANCEL and TIME=1440 will
NOT protect the job from this.
Note that TIME=1440 originally flagged "free" CPU time and so the used
CPU time was not recorded in the SMF records for the job, or shown in
the spooled IEF37nI messages. Usermod ZP60019 "fixed" this.