This might be OTT, but I have used the following "JS" Clist edit macro
since the 1980's when submitting jobs to record when and from where (and
by whom) a job was submitted:
ISREDIT MACRO
CONTROL: +
CONTROL MAIN END(ENDO)
ISREDIT (DSN) = DATASET
ISREDIT (MEM) = MEMBER
IF &STR(&MEM) ¬= THEN SET DSN = &STR(&DSN(&MEM))
SET DATE = +
&SUBSTR(4:6,&SYSDATE)&SUBSTR(1:3,&SYSDATE)&SUBSTR(7:8,&SYSDATE)
SET TIME = &SYSTIME
ERROR GOTO EXIT
ISREDIT FIND P'//@' 1 FIRST
ERROR DO
ISREDIT FIND P'//=' 1 LAST
GOTO CONTINUE
ENDO
ISREDIT FIND P'//¬' 1 NEXT
CONTINUE: +
ISREDIT (ROW) = CURSOR
ERROR OFF
ISREDIT LINE_BEFORE &ROW = '//* '
ISREDIT LINE_BEFORE &ROW = +
'&STR(//* USER : &SYSUID, AT &TIME ON &DATE..)'
ISREDIT LINE_BEFORE &ROW = "//* DATASET: '&DSN' "
ISREDIT LINE_BEFORE &ROW = '//* '
ISREDIT SUBMIT
ISREDIT CURSOR = 1
ISREDIT DELETE &ROW &EVAL(&ROW+3)
ISREDIT LOCATE .ZLAST
ISREDIT LOCATE 0
EXIT: +
EXIT CODE(1)
I had no problem tracking jobs submitted by Control-M or ZEKE (or
whatever else), either.
Just my ha'penny worth.
CP
Brian Westerman wrote:
If the job came through the INTRDR from TSO the exit will see it, if it comes
via a scheduling product, then you already know where the JCL came from:) JOB
scheduling packages aren't all that smart about where they get the JCL from.
Plus I would imagine that every one of them has the capability of logging that
data either via a parm or via an exit. If the job were submitted from another
batch job, you're going to see that in the syslog already. If it comes via
FTP, then you can't possibly care where the JCL came from because it's not
anywhere you can get to and all that matters is that you know who sent it to
you and when, it would be their job to know where they sent it from. There
just aren't that many ways to get jobs into the system that don't have exits to
use to keep thing under observation.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
