On Thu, 27 Sep 2012 16:08:18 -0500, McKown, John wrote:
>
>And I don't see where it is really of any use. Perhaps the OP could help me on
>this point. I really am stumped about why anybody would care. Now, being able
>to log the entire "job stream" (JCL and data images) might be of some interest
>to somebody. But not to me.
>
Yup. Anyone who can ALLOCATE SYSOUT W(INTRDR) can manufacture
jobs out of thin air. But the OP may have requirements for audit tracking
to know where jobs come from (and to ensure they come from nowhere
else).
He needs a customized submitter to log submits or to insert a sentinel
comment after each JOB statement. And (harder) rules that ensure
that process is used. And that probably won't work because there are
likely applications extant that write directly to INTRDR. User exit to
log SUBMITs?
SDSF API will let a job read (its own?) JCL. But it needs the JOBID to
start with. And there's Rexx MVSVAR('SYMDEF','JOBNAME'), but no
MVSVAR('SYMDEF','JOBID') that I can find. And it's TSO only, but one
can always add an IKJEFT%% step early to do the dirty work.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
