View previous topic :: View next topic
|
Author |
Message |
Gary McDowell
Active User
Joined: 15 Oct 2012 Posts: 139 Location: USA
|
|
|
|
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.
TEST.CYCLE.CARDLIB members
Column...123456789012345678901234567890…
(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?
Thanks. |
|
Back to top |
|
|
gcicchet
Senior Member
Joined: 28 Jul 2006 Posts: 1702 Location: Australia
|
|
|
|
Hi,
not sure if this is what you are after but you can try this
create a member SETDATES in a PDS containing the following :-
Code: |
// SET RUN1=L13324 TODAYS RUN DATE
// SET RUN2=L13324 CYCLE RUN DATE
|
include the following after the job card
Code: |
// JCLLIB ORDER=DSN PDS containing member SETDATES
// INCLUDE MEMBER=SETDATES
|
Gerry |
|
Back to top |
|
|
Gary McDowell
Active User
Joined: 15 Oct 2012 Posts: 139 Location: USA
|
|
|
|
Thanks for the reply gcicchet.
Since the SET represent a Symbolic for datasets, how do I extract only the RUN value (L13324) for the symbolic? |
|
Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
|
|
|
|
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 ? |
|
Back to top |
|
|
Gary McDowell
Active User
Joined: 15 Oct 2012 Posts: 139 Location: USA
|
|
|
|
expat wrote: |
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) |
|
Back to top |
|
|
Nic Clouston
Global Moderator
Joined: 10 May 2007 Posts: 2455 Location: Hampshire, UK
|
|
|
|
Perhaps do as Gerry suggested with a little ISPF dialogue to update the INCLUDE member. (It could also submit the job(s)) |
|
Back to top |
|
|
Gary McDowell
Active User
Joined: 15 Oct 2012 Posts: 139 Location: USA
|
|
|
|
Nic Clouston wrote: |
Perhaps do as Gerry suggested with a little ISPF dialogue to update the INCLUDE member. (It could also submit the job(s)) |
Sounds like a plan. Thanks. |
|
Back to top |
|
|
|