Re: Ignoring TIME= specification in JCL

[Clark Morris]

[Default] On 27 Mar 2018 06:15:55 -0700, in bit.listserv.ibm-main
ajn...@ufl.edu (Nims,Alva John  , Al) wrote:

>From the "z/OS JES2 Installation Exits - Version 2 Release 2" manual:
>
>"Exit 6 only gets control when the converter is called in the JES2 address 
>space. If conversion is being run with the interpreter in the JES2CI address 
>space, use exit 60 to perform the equivalent exit 6 function."

Can most of the code be the same in both exit 6 and exit 60?  Is there
another exit needed as well.

Clark Morris
>
>Also from the same manual, "For more information about C/I text, see z/OS MVS 
>Installation Exits."
>[Note: C/I text is "Converter/Interpreter text"]
>
>Al Nims
>Systems Admin/Programmer III
>UF Information Technology
>East Campus 
>P.O. Box 112050
>Gainesville, FL. 32611
>(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 think this exit only captures the submitted JCL. Expanded procs and included 
>JCL will be added by the convertor and will be available in Exit 6.
>
>Grtn,
>Kees.
>
>
>> -Original Message-
>> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
>> On Behalf Of Peter 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.
>> 
>> 
>> 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?
>> 
>> 
>> --
>> Peter Hunkeler
>> 
>> 
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions, send 
>> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
>For information, services and offers, please visit our web site: 
>https://urldefense.proofpoint.com/v2/url?u=http-3A__www.klm.com=DwIFAg=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM=0Ef64GJS77DVfhr5GGKZeQ=aCHhcPgc98u7xyZ_8LQW2DBuOREfY6avwRErDvodTWA=bQPkb2gqjxtsJKpXZN0WhZdWbb6s7Xmmf34mC_d5qcg=.
> This e-mail and any attachment may contain confidential and privileged 
>material intended for the addressee only. If you are not the addressee, you 
>are notified that no part of the e-mail or any attachment may be disclosed, 
>copied or distributed, and that any other action related to this e-mail or 
>attachment is strictly prohibited, and may be unlawful. If you have received 
>this e-mail by error, please notify the sender immediately by return e-mail, 
>and delete this message. 
>
>Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
>employees shall not be liable for the incorrect or incomplete transmission of 
>this e-mail or any attachments, nor responsible for any delay in receipt. 
>Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
>Airlines) is registered in Amstelveen, The Netherlands, with registered number 
>33014286
>
>
>--
>For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
>lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
>--
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Ignoring TIME= specification in JCL

[Clark Morris]

[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 prohibit excessive
use of time that based on a value set in security system of choice,
JES2 exit 6 can be used to for time to be no greater than the system
defined value for a given group of submitters.  In my version of exit
6, time was one of the values I used to determine job class.

Clark Morris
>
>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?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Ignoring TIME= specification in JCL

[Pew, Curtis G]

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 Systems/Core/Administrative Services

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Ignoring TIME= specification in JCL

[Edward Gould]

> 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?
> 
> 
> Would TWS (aka IWS) be able to do this for jobs it submits?
> 
> 
> --
> Peter Hunkeler
> 

Peter,
I looked at this 20+ years ago and found 3 ways.
IIRC (this is 20 years ago) the SMF exit UJV(?) and 2 exits in JES 4 & 6 (I 
could be wrong)
The only fool proof I think is UJV. The problem is with UJV was that it takes 
an IPL to change it (the JES exits only take a warm start). My memory is 
probably off on this, but IIRC I did it in a JES2 exit but I had a back end so 
I could override it with a password that changed daily. I never had to use the 
backend though.
Ed
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Ignoring TIME= specification in JCL

[Seymour J Metz]

FWIW, I have found scanning and modifying the internal text to be easier than 
parsing and modifying the JCL.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List <IBM-MAIN@listserv.ua.edu> on behalf of 
Allan Staller <allan.stal...@hcl.com>
Sent: Tuesday, March 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.
IKJEFF10
IEFUJI

HTH,

-Original Message-
From: IBM Mainframe Discussion List [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) 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?


--
Peter Hunkeler


--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
::DISCLAIMER::
--
The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.
--

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: FW: Ignoring TIME= specification in JCL

[Allan Staller]

Most/all of the region related information is provided in the parameter list, 
however, IEFUSI has *ALL* of the INTTXT available .

You will need to provide you own addressability/ctlblock chasing  to get to the 
INTTXT, since it is not in the provided parameter list.
Recommended reading SA38-0679-03 " MVS Using the Subsystem Interface z/OS V2R2" 
 or similar for your level of z/OS.
CBTTAPE might also have some good examples.

Examine the appropriate INTTXT and set an appropriate return code for what you 
want to do.

IEFUSI is a sledge hammer. About all you can do is smash the job.
It may have been running for quite a while before you see the TIME= in the exec 
card and all of the processing will be lost.

IEFUVJ, JES2 exit 4 or 6 are most likely better places for this, however IEFUSI 
can also do what you want.

HTH,


-Original Message-
From: IBM Mainframe Discussion 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.


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




--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
::DISCLAIMER::
--
The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.
--

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

AW: FW: Ignoring TIME= specification in JCL

[Peter Hunkeler]

>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




--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

FW: Ignoring TIME= specification in JCL

[Allan Staller]

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' <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.
IKJEFF10
IEFUJI

HTH,

-Original Message-
From: IBM Mainframe Discussion List [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) 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?


--
Peter Hunkeler


--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
::DISCLAIMER::
--
The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.
--

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Ignoring TIME= specification in JCL

[Allan Staller]

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.
IKJEFF10
IEFUJI

HTH,

-Original Message-
From: IBM Mainframe Discussion List [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) 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?


--
Peter Hunkeler


--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
::DISCLAIMER::
--
The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.
--

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Ignoring TIME= specification in JCL

[Nims,Alva John (Al)]

>From the "z/OS JES2 Installation Exits - Version 2 Release 2" manual:

"Exit 6 only gets control when the converter is called in the JES2 address 
space. If conversion is being run with the interpreter in the JES2CI address 
space, use exit 60 to perform the equivalent exit 6 function."

Also from the same manual, "For more information about C/I text, see z/OS MVS 
Installation Exits."
[Note: C/I text is "Converter/Interpreter text"]

Al Nims
Systems Admin/Programmer III
UF Information Technology
East Campus 
P.O. Box 112050
Gainesville, FL. 32611
(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 think this exit only captures the submitted JCL. Expanded procs and included 
JCL will be added by the convertor and will be available in Exit 6.

Grtn,
Kees.


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Peter 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.
> 
> 
> 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?
> 
> 
> --
> Peter Hunkeler
> 
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

For information, services and offers, please visit our web site: 
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.klm.com=DwIFAg=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM=0Ef64GJS77DVfhr5GGKZeQ=aCHhcPgc98u7xyZ_8LQW2DBuOREfY6avwRErDvodTWA=bQPkb2gqjxtsJKpXZN0WhZdWbb6s7Xmmf34mC_d5qcg=.
 This e-mail and any attachment may contain confidential and privileged 
material intended for the addressee only. If you are not the addressee, you are 
notified that no part of the e-mail or any attachment may be disclosed, copied 
or distributed, and that any other action related to this e-mail or attachment 
is strictly prohibited, and may be unlawful. If you have received this e-mail 
by error, please notify the sender immediately by return e-mail, and delete 
this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286


--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

AW: Re: Ignoring TIME= specification in JCL

[Peter Hunkeler]

>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. Secondly, the very same JCL is 
distributed to test and prod environments and TIME= is to be ignored in test 
only.


--
Peter Hunkeler




--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Ignoring TIME= specification in JCL

[Richards, Robert B.]

If you have ThruPut Manager, it can do it.

If you issue a SEARCHFOR against all the datasets concatenated on the EQQJBLIB 
DDNAME and remove TIME=.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Peter Hunkeler
Sent: Tuesday, March 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 statements. Is there an 
alternative?


Would TWS (aka IWS) be able to do this for jobs it submits?


--
Peter Hunkeler


--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Ignoring TIME= specification in JCL

[Vernooij, Kees (ITOPT1) - KLM]

I think this exit only captures the submitted JCL. Expanded procs and included 
JCL will be added by the convertor and will be available in Exit 6.

Grtn,
Kees.


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Peter 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.
> 
> 
> 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?
> 
> 
> --
> Peter Hunkeler
> 
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Ignoring TIME= specification in JCL

[Peter Hunkeler]

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?


--
Peter Hunkeler


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN