Yes, that's the standard way of doing it in Zeke - you define the schedule time and/or the conditions that must be satisfied and also the member name and library that is the source of the job. However, Zeke also allows for dynamically created schedule queue records (SQRs), whereby Zeke "captures" the JCL being submitted and manages it. Also, given the proper authorities, you can modify an SQR to read a different PDS member, run the job, then delete the SQR, leaving no clue behind.
Admittedly, the last two scenarios are rare, and perhaps not noteworthy for this discussion. Regards, Greg Shirey Ben E. Keith Company -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of retired mainframer Sent: Monday, June 06, 2016 5:06 PM To: [email protected] Subject: Re: Determine the PDS a job was submitted from? Did ZEKE actually submit the job or did it submit a "launcher" job that then submitted the one you are really interested in? I have never used ZEKE but surely it did not just up and decide to submit a job. Some form of input to ZEKE must have specified "when this condition occurs then ...." ZEKE should have some kind of report that allows you to see the active directives. The relevant directive must tell ZEKE where to find the job. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
