My first thought for validity verification is Exit 6, which we use a lot. 
However, that runs in JES2 Main Task. I don't think you can issue WTOR there: 
all of JES2 would wait for the reply. In looking through the JES2 exit table

https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieae400/jes2.htm

I don't see anything promising other than 52 and 54 (statement scan), which run 
in JES2 User environment. The scan exits run only at submit time, so you would 
have no control over a job that is later moved to a different LPAR or job 
class. 

The WTOR is highly problematic for many system tasks. 

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-302-7535 Office
[email protected]


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Elardus Engelbrecht
Sent: Tuesday, July 12, 2016 3:24 AM
To: [email protected]
Subject: (External):Re: issue WTOR if surrogat ID submits a job

Itschak Mugzach wrote:

>May be a job with a user= in the jobcard that is not the submiter id. I 
>believe jes exits 5x can do that.

Yes, a JES2 exit (nr 5 I think) which scans the JCL statements and when 
discovering a USER=??? statement, can issue a WTOR. That is *if* you may issue 
a WTOR in the environment where that exit is running.


Munif Sadek wrote:

>"We are JES2, z/OS 2.1 and would like batch to issues a WTOR (Confirm Y/N?)  
>if a job is submitted by surrogate Batch Id in a specific JOB class of a 
>specific LPAR."

Use automation to catch that job and issue a WTOR. (Control-O has this clause 
'ON-JOB-ARRIVAL'.)


>"Can RACF help?"

With SURROGAT Class yes. But still no WTOR, just a NOTIFY which may be picked 
up many minutes/hours/days later.

Groete / Greetings
Elardus Engelbrecht


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to