;(e) ajn...@ufl.edu
>(p) (352) 273-1298
>
>-Original Message-
>From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
>Behalf Of Vernooij, Kees (ITOPT1) - KLM
>Sent: Tuesday, March 27, 2018 7:36 AM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: Ignoring TIME= s
[Default] On 27 Mar 2018 04:27:03 -0700, in bit.listserv.ibm-main
p...@gmx.ch (Peter Hunkeler) wrote:
>I've got the requirement to limit who is allowed to specify TIME= on either
>JOB or EXEC statement. This is for z/OS V2.2 (and up) and JES2.
>
What is behind the requirement? If the idea is to
On Mar 27, 2018, at 3:25 PM, Edward Gould wrote:
>
> The problem is with UJV was that it takes an IPL to change it (the JES exits
> only take a warm start).
Well, nowadays you can use SETPROG EXIT to change UJV without waiting for an
IPL.
--
Pew, Curtis G
curtis@austin.utexas.edu
ITS Sys
> On Mar 27, 2018, at 6:28 AM, Peter Hunkeler wrote:
>
> I've got the requirement to limit who is allowed to specify TIME= on either
> JOB or EXEC statement. This is for z/OS V2.2 (and up) and JES2.
>
>
> There is JES2 exit 4 to scan and modify the JCL statements. Is there an
> alternative?
>
27, 2018 9:33 AM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: Ignoring TIME= specification in JCL
Jes2 Exit 6 can also do this. You will need to process the internal text
(similar to DYNALLOC text units).
Depending on how you want to handle things other exist can also do this by
failing the job
ssion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Peter Hunkeler
Sent: Tuesday, March 27, 2018 9:02 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: AW: FW: Ignoring TIME= specification in JCL
>Responded too soon. Since you also want to look at the step level IEFUSI would
>also be needed.
>Responded too soon. Since you also want to look at the step level IEFUSI would
>also be needed.
I had a look at IEFUSI before posting, but did not see how to change the (CPU)
TIME= limit there. It's purpos is mainly to deal with memory limits. Did I
overlook something?
--
Peter Hunkeler
Responded too soon. Since you also want to look at the step level IEFUSI would
also be needed.
-Original Message-
From: Allan Staller
Sent: Tuesday, March 27, 2018 8:33 AM
To: 'IBM Mainframe Discussion List'
Subject: RE: Ignoring TIME= specification in JCL
Jes2 Exit 6 can al
[mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Peter Hunkeler
Sent: Tuesday, March 27, 2018 6:28 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Ignoring TIME= specification in JCL
I've got the requirement to limit who is allowed to specify TIME= on either JOB
or EXEC statement. This is for z/OS V2.2 (and up
2611
(e) ajn...@ufl.edu
(p) (352) 273-1298
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Vernooij, Kees (ITOPT1) - KLM
Sent: Tuesday, March 27, 2018 7:36 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignoring TIME= specification in JCL
I
>If you have ThruPut Manager, it can do it.
Don't have this.
>If you issue a SEARCHFOR against all the datasets concatenated on the EQQJBLIB
>DDNAME and remove TIME=.
It has to be at submit time. Firstly, the JCL is maintained by a change control
software, so a one time change is no option.
27, 2018 7:28 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Ignoring TIME= specification in JCL
I've got the requirement to limit who is allowed to specify TIME= on either JOB
or EXEC statement. This is for z/OS V2.2 (and up) and JES2.
There is JES2 exit 4 to scan and modify the JCL statement
Hunkeler
> Sent: 27 March, 2018 13:28
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Ignoring TIME= specification in JCL
>
> I've got the requirement to limit who is allowed to specify TIME= on
> either JOB or EXEC statement. This is for z/OS V2.2 (and up) and JES2.
>
>
>
I've got the requirement to limit who is allowed to specify TIME= on either JOB
or EXEC statement. This is for z/OS V2.2 (and up) and JES2.
There is JES2 exit 4 to scan and modify the JCL statements. Is there an
alternative?
Would TWS (aka IWS) be able to do this for jobs it submits?
--
Pet
14 matches
Mail list logo
