Elardus, The initial question was about the TIME= Parameter on the JOB card. I am trying to understand why you mentioned the REGION= parameter? And, if a site has a standard that TIME is not allowed on a JOB card, then the solution is to remove it and/or flag it and then remove it with a JCL management tool such as J-Man. This can be done for any JCL statement parameter, keyword, sub-parameter, value, positional character, entire statements, automatically. And, it can be done any time a JCL object is moved into production.
Mitch -----Original Message----- From: Elardus Engelbrecht <[email protected]> To: IBM-MAIN <[email protected]> Sent: Mon, Dec 8, 2014 5:30 am Subject: Re: Ancient IEFUSI Mitch wrote: >This is all fine a good, but why check when a job is submitted? Why not check efore and eliminate the problem (and potential delay in batch)? Simply - USI is used to check memory and enforce limits at every job step(s) espite stated REGION=<value>. "IEFUSI exit routines receive control before the initiator checks to determine hether the job step will actually execute." You cannot enforce storage limits before job execution - Only WHILE the thing is unning. Groete / Greetings lardus Engelbrecht ---------------------------------------------------------------------- or IBM-MAIN subscribe / signoff / archive access instructions, end 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
