I know that TIME=1440 and TIME=NOLIMIT can make their way into the JCTXJTL 
field via a combination of JCL settings, overrides, possible exits, defaults, 
and such - and that JCTXJTL is supposed to ultimately contain the effective 
job-step time limit - which is all well and good - and I do see that if I 
specify TIME=NOLIMIT, for example, I *do* end up with x'83D600' (1440*60*100) 
in that field - which is exactly what I would expect.

My question is - what does it mean when that field ends up with the value 
x'00000000', as is the case at our site if no TIME= is given?  I believe our 
default is "no limit" and that may be why it's ending up being zero, but I'd 
have expected to find x'83D600' instead. Is it actually true, perhaps, that 
finding *either* x'0083D600' *or* x'00000000' in that field means that there is 
no time limit in effect?

Thanks,

Rich Way
Micro Focus


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to