On Tue, 25 Oct 2016 11:47:34 +0200, R.S. wrote: W dniu 2016-10-25 o 04:55, Jesse 1 Robinson pisze: > OK, consider this case. All defaults, no TIME= coded anywhere. JES2 parms > have TIME=3. Five steps. How long will the job run? > >Assumed first step consumed 30s the limit for the rest of the job is >(2,30). Assumed second step consumed 10s, the limit for the remaining >steps is (2,20), etc.
Nope. From the JES2 Init and Tuning reference: <quote> TIME=(mmmmmm,ss)|(30,0) Specifies the default for the maximum processor time that each job step may run. The "mmmmmm" indicates minutes (0-357912); the "ss" indicates seconds (0-59). The value specified is subject to the limits described for the TIME parameter in z/OS MVS JCL Reference. This default TIME= specification is used when no TIME parameter is specified on the JCL EXEC statement. (See z/OS MVS JCL Reference for further details on specifying the TIME parameter on the EXEC statement. See notes for $T job C=class in z/OS JES2 Commands for further details concerning the results of changing the job class.) Modification: $T JOBCLASS operator command or cold start Note: This parameter only defaults the TIME for the EXEC statement; not for the JOB statement. </quote> -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
