In
2055c4ebc2b05442853ca436c40652851d87a...@nwb-exchange.microfocus.com,
on 08/11/2011
at 02:38 PM, Robin Atwood robin.atw...@microfocus.com said:
So when the job deck is read and IEFUJV is called,
Those are two different points in time, and in two different address
spaces.
So when the job
Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
Behalf Of Chicklon, Thomas
Sent: 10 August 2011 16:57
To: IBM-MAIN@bama.ua.edu
Subject: Re: Enforcing job name conventions - which exit?
IEFUJV can do everything, and the TSO submit exit would not be
necessary
In 1228402832218791.wa.paulgboulderaim@bama.ua.edu, on
08/10/2011
at 10:45 AM, Paul Gilmartin paulgboul...@aim.com said:
What can be done in IKJEFF10 that couldn't equally well be done in
IEFUJV?
Issue a TPUT[1] to the user, or anything else that is dependent on a
TSO environment.
Can
Thanks to everybody for all the suggestions, it looks like IEFUJV or the
JESJOBS profile is the best way forward, I will see what the customer thinks.
Cheers
-Robin
--
Robin Atwood
Communications Technology
Micro Focus
The Lawn, 22-30 Old Bath Road
Newbury, Berkshire, RG14 1QN, UK
Direct: +44
On Tue, 9 Aug 2011 10:27:31 -0500, Williamson, James R wrote:
IKJEFF10
Customizing how users submit jobs and process the output
http://publib.boulder.ibm.com/infocenter/zos/v1r11/index.jsp?topic=/com.ibm.zos.r11.ikjb400/ikj4b4a0211.htm
-Original Message-
From: IBM Mainframe
Two what?
There is one TSO submit exit (IKJEFF10), and one job verification exit
(IEFUJV). These two exit points were created for different purposes and
functions.
On Wed, Aug 10, 2011 at 10:02 AM, Paul Gilmartin paulgboul...@aim.comwrote:
On Tue, 9 Aug 2011 10:27:31 -0500, Williamson, James
On Wed, 10 Aug 2011 10:25:37 -0400, Scott Rowe wrote:
Two what?
There is one TSO submit exit (IKJEFF10), and one job verification exit
(IEFUJV). These two exit points were created for different purposes and
functions.
What can be done in IKJEFF10 that couldn't equally well be done in
IEFUJV?
for a number of reasons before the job is failed by UJV.
Tom Chicklon
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
Behalf Of Paul Gilmartin
Sent: Wednesday, August 10, 2011 11:45 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Enforcing job name conventions
IKJEFF10 gets control as the JCL is being submitted (via the SUBMIT
command), and it has access to all the TSO control blocks, so it can supply
jobcard info, etc. IEFUJV does not get control until the job is actually
selected by the initiator, and has no access to the TSO environment.
On Wed,
...@aim.com
To:
IBM-MAIN@bama.ua.edu
Date:
08/10/2011 10:46 AM
Subject:
Re: Enforcing job name conventions - which exit?
Sent by:
IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu
On Wed, 10 Aug 2011 10:25:37 -0400, Scott Rowe wrote:
Two what?
There is one TSO submit exit (IKJEFF10), and one job
Life and Health Insurance Company.SM
-Original Message-
From: IBM Mainframe Discussion List
[mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Paul Gilmartin
Sent: Wednesday, August 10, 2011 10:45 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Enforcing job name conventions - which exit?
On Wed
From: Robin Atwood
Sent: 09 August 2011 15:08
To: 'IBM-MAIN@bama.ua.edu'
Subject: Enforcing job name conventions - which exit?
We have a requirement that any job submitted to JES2 must have its jobname
starting with the userid, like the standard TSO submit command behaviour. I
recall
On Tue, 9 Aug 2011 15:18:11 +0100, Robin Atwood wrote:
We have a requirement that any job submitted to JES2 must have its jobname
starting with the userid, ...
Why? There are more meaningful uses for the scant 8 characters allowed,
given that the userid is available elsewhere in the spool
Very likely, but the requirement is for a bank and..., well, who knows?
:)
-Robin
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
Behalf Of Paul Gilmartin
Sent: 09 August 2011 15:49
To: IBM-MAIN@bama.ua.edu
Subject: Re: Enforcing job name
Of
Robin Atwood
Sent: Tuesday, August 09, 2011 9:18 AM
To: IBM-MAIN@bama.ua.edu
Subject: Enforcing job name conventions - which exit?
From: Robin Atwood
Sent: 09 August 2011 15:08
To: 'IBM-MAIN@bama.ua.edu'
Subject: Enforcing job name conventions - which exit?
We have a requirement that any job
To: IBM-MAIN@bama.ua.edu
Subject: Re: Enforcing job name conventions - which exit?
IKJEFF10
Customizing how users submit jobs and process the output
http://publib.boulder.ibm.com/infocenter/zos/v1r11/index.jsp?topic=/com.
ibm.zos.r11.ikjb400/ikj4b4a0211.htm
-Original Message
I used IEFUJV. It also let me enforce other installation standards as well. We
had strict job naming standards and this was a great way to do so. The code was
trivial.
Ed
--
For IBM-MAIN subscribe / signoff / archive access
: Tuesday, August 09, 2011 10:41 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Enforcing job name conventions - which exit?
Thanks but the requirement is for jobs submitted via any internal
reader, which why I was wondering if there was a convenient JES2 exit.
-Robin
-Original Message-
From
-MAIN@bama.ua.edu
Subject: Re: Enforcing job name conventions - which exit?
IEFUJV is rather easy. SYS1.SAMPLIB(SMFEXITS) has an example. JES2 exit 2 can
do this. As could exits 6 or 20, but with more difficulty. Personally, I'd go
with IEFUJV.
Jes2:
http://publibz.boulder.ibm.com/cgi-bin
List
[mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Grinsell, Don
Sent: Tuesday, August 09, 2011 10:59 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Enforcing job name conventions - which exit?
You could also look at what controls you can implement in
your security software...rather than writing
besides just job name checking.
/jack
- Original Message -
From: Robin Atwood robin.atw...@microfocus.com
Newsgroups: bit.listserv.ibm-main
To: IBM-MAIN@bama.ua.edu
Sent: Tuesday, August 09, 2011 10:18 AM
Subject: Enforcing job name conventions - which exit?
From: Robin Atwood
Sent: 09
Why not to use RACF controls, JESJOBS class?
It provides quite useful control of jobnames, execution userids, etc.
BTW, caution: there are (in general) two kind of JESJOBS profiles:
SUBMIT.nodename.jobname.userid
CANCEL.nodename.userid.jobname
SUBMIT profiles work as expected and are very
On 8/9/2011 11:27 AM, Williamson, James R wrote:
IKJEFF10
Customizing how users submit jobs and process the output
As the OP pointed out, the request was for a general solution,
not just from a TSO SUBMIT. And you might be astonished at how
many installations write elaborate code for this
Why would you want to enforce such a ridiculious restriction?
:-(
From: Robin Atwood robin.atw...@microfocus.com
To: IBM-MAIN@bama.ua.edu
Sent: Tuesday, August 9, 2011 8:18 AM
Subject: Enforcing job name conventions - which exit?
From: Robin Atwood
Sent: 09 August 2011 15:08
To: 'IBM-MAIN
In
64819e7175d9f54398a14fdea6a731e3012d1...@emo-exmb-m-404.main.ads.uscg.mil,
on 08/09/2011
at 10:27 AM, Williamson, James R james.r.william...@uscg.mil
said:
IKJEFF10
That's TSO. The OP was asking about enforcing it for jobs not
submitted via the TSO SUBMIT command.
--
Shmuel
25 matches
Mail list logo
