Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

SET from CARDLIB member ?

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
Gary McDowell

Active User


Joined: 15 Oct 2012
Posts: 139
Location: USA

PostPosted: Thu Nov 21, 2013 7:04 am    Post subject: SET from CARDLIB member ?
Reply with quote

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
View user's profile Send private message

gcicchet

Senior Member


Joined: 28 Jul 2006
Posts: 1703
Location: Australia

PostPosted: Thu Nov 21, 2013 10:01 am    Post subject:
Reply with quote

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
View user's profile Send private message
Gary McDowell

Active User


Joined: 15 Oct 2012
Posts: 139
Location: USA

PostPosted: Thu Nov 21, 2013 6:10 pm    Post subject:
Reply with quote

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
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Thu Nov 21, 2013 6:23 pm    Post subject:
Reply with quote

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
View user's profile Send private message
Gary McDowell

Active User


Joined: 15 Oct 2012
Posts: 139
Location: USA

PostPosted: Thu Nov 21, 2013 7:36 pm    Post subject:
Reply with quote

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
View user's profile Send private message
Nic Clouston

Global Moderator


Joined: 10 May 2007
Posts: 1715
Location: UK

PostPosted: Thu Nov 21, 2013 7:42 pm    Post subject:
Reply with quote

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
View user's profile Send private message
Gary McDowell

Active User


Joined: 15 Oct 2012
Posts: 139
Location: USA

PostPosted: Thu Nov 21, 2013 11:24 pm    Post subject:
Reply with quote

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
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts What is the command to check MODE of ... rohanthengal CLIST & REXX 6 Fri Nov 18, 2016 1:48 pm
No new posts File Stauts 92 with member of PDS sandip_mainframe COBOL Programming 4 Fri Jun 10, 2016 12:06 pm
No new posts how to extract the member name ? jackzhang75 CLIST & REXX 1 Wed Feb 17, 2016 9:21 pm
No new posts Check if a member is present in libra... enrico-sorichetti All Other Mainframe Topics 1 Wed Feb 03, 2016 12:29 pm
No new posts Editing "member generations"... Ricardo Viegas TSO/ISPF 1 Tue Dec 29, 2015 7:27 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us