We have lots of new test jobs that we change and run and done manually because of the SET RUN dates. Would there be a way to "SET" a value from data in a PDS Member? …and if so, how? I don't know if this can even be done the way I like to proceed. We can't do a global PDS change since not all "like" values should change, and not all SETs mean the same from job-to-job.
Current Partial Example of a job:
// SET RUN1=L13324 TODAYS RUN DATE
// SET RUN2=L13324 CYCLE RUN DATE (NOT ALWAYS CURRENT DATE)
// SET INPUT1=TEST.CYCLE.&RUN2..REPORT
//SORTOUT DD DSN=TEST.CYCLE.&RUN1..SORT.DETAIL
Proposed Idea; have "SET" CARDLIB members that jobs reference so that we can add jobs to ESP Scheduler to automatically run after the CARDLIB members are changed. In other words, change a handful of Cardlib members for 50+ jobs to reference.
(RUN1) - 13324 * TODAYS RUN DATE
(RUN2) - 13324 * CYCLE RUN DATE (NOT ALWAYS CURRENT DATE)
// SET RUN1=TEST.CYCLE.CARDLIB(RUN1) How would I extract only the 'L13324' from col 1-5?
// SET RUN2=TEST.CYCLE.CARDLIB(RUN2) How would I extract only the 'L13324' from col 1-5?
I use the method Gerry has suggested for one of the yearly jobs here, where the SET= is built from a batch job that goes off and interrogates the CA1 TMS.
The output is created into a PDS and then included in a subsequent batch job.
Where do you currently get the information from ?
If by information you mean how are the SETs determined?; The CYCLE RUN DATE, for example, points to when client datasets arrived in our shop for testing or re-testing. So for example if we wanted to re-test today (11/21/2013.325 Thursday) for client files sent Monday (11/18/2013.322) we would manually change the SETs in every 50+ jobs as follows:
// SET RUN1=L13325 TODAYS RUN DATE
// SET RUN2=L13322 CYCLE RUN DATE (NOT ALWAYS CURRENT DATE)