> It's possible for data-driven conditions, some of which might happen, > say, but once a year, to cause the selective loading and/or execution > of otherwise un-referenced programs. You cannot make a definitive > determination of this from an analysis of JCL, expanded or otherwise.
It's also at least theoretically possible for one jobstep to create a load module that is executed in a subsequent step - so a "verification" of the latter step without executing the former will fail - but the job would not fail in actual execution. Didn't some early report writer type products work this way? Build COBOL source code for a compile, link, and go? Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Graeme Gibson Sent: Monday, June 12, 2006 3:38 AM To: [email protected] Subject: Re: Decide whether programs invoked by a JCL exist Hmmm.. Is this a test? Game playing? >...But,it seems that's not the method my manager expects. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
