From:Roberto Halais roberto.hal...@gmail.com
Sorry for the mental check. The exit I wrote is an IEFUJI not a IEFUSI.
You can still have qa copy. :-)
Tom Russell
Internet: tom_russ...@ca.ibm.com
Stay calm. Be brave. Wait for the signs. ─ Jasper FriendlyBear
... and remember to leave
Using Mark's idea.
I have a question.
Once the job gets authorized by the exit to proceed what would happen if the
operator decides to change the job class. Will the exit reenter again or is
there another exit we have to code?
Thank you for you replies.
On Tue, Aug 24, 2010 at 5:29 PM, Mark
-Original Message-
From: IBM Mainframe Discussion List
[mailto:ibm-m...@bama.ua.edu] On Behalf Of Roberto Halais
Sent: Wednesday, August 25, 2010 7:29 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Job Submission exit
Using Mark's idea.
I have a question.
Once the job gets
No, the exit will not get called again after conversion of the JCL.But you
can protect the ability to change the class via operator commands or
products like SDSF with external security (RACF/ACF2/Top Secret).
For example, in the OPERCMDS class you would protect
JES2.MODIFY.BAT
See the
John and Mark:
Thank you for your comments.
On Wed, Aug 25, 2010 at 9:55 AM, Mark Zelden mzel...@flash.net wrote:
No, the exit will not get called again after conversion of the JCL.But
you
can protect the ability to change the class via operator commands or
products like SDSF with
In
c55ebb8de31be74bb4340979cfea615a05e43...@emo-exmb-m-404.main.ads.uscg.mil,
on 08/24/2010
at 03:31 PM, Williamson, James R james.r.william...@uscg.mil
said:
I believe the TSO submit exit is IKJEFF10,
it's not a JES exit.
And therefore won't catch TSO applications that write directly to the
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of
Ward, Mike S
Sent: Tuesday, August 24, 2010 3:22 PM
To: IBM-MAIN@bama.ua.edu
Subject: Job Submission exit
Hello all, I'm asking for a little help. I would like to keep TSO users
from
...@bama.ua.edu] On Behalf Of
Williamson, James R
Sent: Tuesday, August 24, 2010 13:32
To: IBM-MAIN@bama.ua.edu
Subject: Re: Job Submission exit
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of
Ward, Mike S
Sent: Tuesday, August 24, 2010 3:22 PM
Sorry Mike. The exit that James mentioned will work fine too, as long as you're
only concerned with jobs entering via the TSO SUBmit CP. There are other ways
to submit jobs into the system from TSO (e.g. executing a foreground IEBGENER
to INTRDR or FTPing to JES).
Cheers...
-Original
We use JES2 exit 6 to restrict job classes to selected RACF groups,
but is should be pretty easy to just check the origin for TSUn
instead.
The problem with using the TSO submit exit is that it is easy to
bypass by just using any old program to send card images to the
INTRDR.
/jack
On Tue, 24 Aug 2010 15:22:20 -0500, Ward, Mike S mw...@ssfcu.org wrote:
Hello all, I'm asking for a little help. I would like to keep TSO users
from submitting jobs using class P. I am looking through the Jes2 exits,
but I'm not sure which one to choose. If someone could point me in the
right
I've sent you, via private E-Mail, a copy of the IKJEFF10 exit we used
at Board of Trade Clearing Corp. It does job-class enforcement based on
userid. Enjoy. :-)
Rick
---
Ward, Mike S wrote:
Hello all, I'm asking for a little help. I would like to
: Re: Job Submission exit
Sorry Mike. The exit that James mentioned will work fine too, as long as
you're only concerned with jobs entering via the TSO SUBmit CP. There
are other ways to submit jobs into the system from TSO (e.g. executing a
foreground IEBGENER to INTRDR or FTPing to JES).
Cheers
13 matches
Mail list logo
