Many thanks for this suggestion.
I have found a copy of IEFU84/MXGU84 in our MXG.SOURCLIB. This should
solve the audit trail issue.
Thanks again.
Tony
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Barry Merrill
Sent: Tuesday, August 07, 2018 3:50 PM
To: [email protected]
Subject: Re: Jes2 Initiator number
In 2004, MXG Change 19.269 provided an IEFU84 exit that captures
and moves the Initiator Number and Initiator Number into the
SMF 30 Subtype 1, and MXG type 30 processing picks them up.
I have no recent confirmation that exit code runs but I also
have no recent confirmations that it's in use anywhere.
Barry
Herbert W. “Barry” Merrill, PhD
President-Programmer
Merrill Consultants
MXG Software
10717 Cromwell Drive
Dallas, TX 75229
www.mxg.com
[email protected]
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Tony Cieri
Sent: Tuesday, August 7, 2018 2:34 PM
To: [email protected]
Subject: Jes2 Initiator number
Is the JES2 initiator number that runs a job recorded in any SMF records??
The only "audit" trail that I can find is the $HASP373 message when a job is
started.
I would appreciate any pointers that anyone can provide.
Thanks
Tony
----------------------------------------------------------------------
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
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
