> -----Original Message-----
> From: IBM Mainframe Discussion List 
> [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Staller, Allan
> Sent: Tuesday, February 22, 2011 8:22 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: cascading catalog dataset aliases.
> 
> I suggest the JCL include statement. Much easier to use and less to
> change (After the initial pain).
> Change the JCLLIB statement to point to the appropriate 
> STEPLIBS member.
> Modify the STEPLIBS member as required.
> 
> e.g.
> 
> // JCLLIB ORDER=(PROCLIB1, PROCLIB2) 
> 
> //STEP1 EXEC PGM=SOMETHING
>  INCLUDE MEMBER=STEPLIBS
> // rest of jcl
> 
> MEMBER STEPLIBS in PROCLIB1
> //STEPLIB DD DSN= SYS3.SOMEPROD.V1R1M0.LINKLIB
> //               DD ....
> 
> MEMBER STEPLIBS in PROCLIB2
> //STEPLIB DD DSN= SYS3.SOMEPROD.V2R1M0.LINKLIB
> //               DD ....
> 
> 
> HTH.

I considered that. But the PROCLIB is resolved at JCL read time, not at 
execution time. So if I submit the JCL on Prod (where CA-7 runs), it uses the 
Prod version of the PROC. Even if the job is SYSAFF'd to run on Development. 
This method would work if Prod and Development ran the identical versions at 
all times. And would save JCL changes for a simple case. But the simple use of 
an ALIAS would do the same. The desire is to use the correct DSN dependant on 
the running system at the time of execution. Without any JCL change needed. If 
fact, to have it run with the system-dependant DSN even if the job's SYSAFF is 
changed dynamically. In program terms: "Late Binding" or "Dynamic Binding" 
where the DSN name is not resolved until the last possible instant.

--
John McKown 
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)

9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone * 
john.mck...@healthmarkets.com * www.HealthMarkets.com

Confidentiality Notice: This e-mail message may contain confidential or 
proprietary information. If you are not the intended recipient, please contact 
the sender by reply e-mail and destroy all copies of the original message. 
HealthMarkets(r) is the brand name for products underwritten and issued by the 
insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance 
Company(r), Mid-West National Life Insurance Company of TennesseeSM and The 
MEGA Life and Health Insurance Company.SM

 

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to