⇐=== NEW
robin...@sce.com
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Keith Costley
Sent: Tuesday, March 10, 2020 2:39 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: JES2 - stopping users from sending output to specific
outputclass
CAUTION EXTERNAL EMAIL
Thanks everyone for your help and feedback! I am going to try going down the
path of the JES2 Exit 6 for now to see if that will handle the majority of our
issues.
Keith Costley
Mastercard International
Mainframe Platform Services
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JES2 - stopping users from sending output to specific outputclass
Jantje pointed out what seems the sensible solution, use the ACF2 JESSPOOL
resource class:
https://secure-web.cisco.com/1SQs1JP1i-71OzMTZOyJFk-Fu5Hli_ATR82
Keith,
I use JES2 EXIT 6 for this.
One item is to change sysout psuedo dataset names by replacing "?" for "DDNAME"
- enables "proper" RACF control of SYSOUT classes.
Regards
Bruce
On Tue, 3 Mar 2020 11:13:16 -0600, John McKown
wrote:
>On Mon, Mar 2, 2020 at 4:13 PM Keith Costley
>wrote:
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: JES2 - stopping users from sending output to specific outputclass
We are having an issue with users using a restricted output class based on
standards. We are looking for a way to prevent this from happening by canceling
the job if the JCL contains SYSOUT=X
On Tue, 3 Mar 2020 18:43:40 +, Jesse 1 Robinson wrote:
>We have controlled use of sysout classes for decades using JES2 exits and SAF.
>What we have is way too complicated to share, but I can attest that it's
>possible depending on how much work you want to do. If you have a working Exit
: IBM Mainframe Discussion List On Behalf Of
John McKown
Sent: Tuesday, March 3, 2020 9:13 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: JES2 - stopping users from sending output to specific
outputclass
CAUTION EXTERNAL EMAIL
On Mon, Mar 2, 2020 at 4:13 PM Keith Costley
wrote:
>
On Mon, Mar 2, 2020 at 4:13 PM Keith Costley
wrote:
> We are having an issue with users using a restricted output class based on
> standards. We are looking for a way to prevent this from happening by
> canceling the job if the JCL contains SYSOUT=X. We are an ACF2 shop but I
> am unaware if
-MAIN@LISTSERV.UA.EDU
Subject: Re: JES2 - stopping users from sending output to specific outputclass
On Tue, 3 Mar 2020 08:48:43 -0500, Brian France wrote:
>We too are an ACF2 shop and I don't know of a way to do this using ACF2
>tho I have not really researched that since we've used IEFU
Sorry can't help ya. I have no ide'er... Maybe check broadcom's ( soon
to be bmc ) website's knowledge center.
On 3/3/2020 9:40 AM, Paul Gilmartin wrote:
On Tue, 3 Mar 2020 08:48:43 -0500, Brian France wrote:
We too are an ACF2 shop and I don't know of a way to do this using ACF2
tho I have
On Tue, 3 Mar 2020 08:48:43 -0500, Brian France wrote:
>We too are an ACF2 shop and I don't know of a way to do this using ACF2
>tho I have not really researched that since we've used IEFUV exit to
>perform jcl validation while the job is being interpreted in my time
>here and before.
>
What can
We too are an ACF2 shop and I don't know of a way to do this using ACF2
tho I have not really researched that since we've used IEFUV exit to
perform jcl validation while the job is being interpreted in my time
here and before.
On 3/2/2020 5:03 PM, Keith Costley wrote:
We are having an issue
On Mon, 2 Mar 2020 16:03:28 -0600, Keith Costley
wrote:
>We are having an issue with users using a restricted output class based on
>standards. We are looking for a way to prevent this from happening by
>canceling the job if the JCL contains SYSOUT=X. We are an ACF2 shop but I am
>unaware
We are having an issue with users using a restricted output class based on
standards. We are looking for a way to prevent this from happening by canceling
the job if the JCL contains SYSOUT=X. We are an ACF2 shop but I am unaware if
ACF2 security can limit this through a security definition.
14 matches
Mail list logo
