Everyone, To clarify, The tool suite in question also understands the jobs run outside the scheduler (by analyzing the SMF), and the STC are checked as well. It is essentially an all encompassing solution.
Mitch -----Original Message----- From: Elardus Engelbrecht <[email protected]> To: IBM-MAIN <[email protected]> Sent: Fri, Feb 13, 2015 4:29 am Subject: Re: XREF Members of JCL libs and their datasets Shmuel Metz (Seymour J.) wrote: >How does it determined the DD statements for cataloged procedures without >information about the relevant JES JCL, JES parms and JES commands. There is >no way to get those data automatically. Indeed. You can ask JES something, but reply may or may not be the same as in Parmlib member used at initialization. >Now, once the program knows what JES to look at, it can determine the proclib >configuaration assuming that no subsequent JES commands will change that, but >that's a big assumption. Ah, yes, JES commands. I forgot about them. You can add/delete proclibs at will. Or you can read in a JCL, edit it in memory programmatically, insert a JCLLIB ORDER and/or INCLUDE MEMBER and submit the JCL as modified without changing the actual stored JCL. No scanner, except in JES or SMF exits, will block this. [1] >Il va sans dir. JOBLIB is totally irrelevant to determining the JCL. Hehehehe. No one argues with Shmuel. Good reply, Shmuel! Keep it up! Groete / Greetings Elardus Engelbrecht [1] - This trick has been used to insert your own program sitting in a private STEPLIB via a 'secret private proclib' to do something bad for your health. ---------------------------------------------------------------------- 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
