This is likely another weird idea of mine. We have a two system basic sysplex.
One system is designated as Production. The other as Development. We also have
a "sandbox" z/OS which is not in the sysplex for sysprogs only. Our method to
install a new product or release of an existing product is:
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 MEM
Another option is to use another alias - SYS3.SOMEPROD.DEVL.LINKLIB for use
in development, separate from SYS3.SOMEPROD.PROD.LINKLIB in production. Most
of the time, these both will point to the same base file name, but in this
case, .DEVL will have the new version, and .PROD will have the current
> -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
Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
Behalf Of McKown, John
Sent: Tuesday, February 22, 2011 8:11 AM
To: IBM-MAIN@bama.ua.edu
Subject: cascading catalog dataset aliases.
This is likely another weird idea of mine. We have a two system basic
sysplex
ance Company of TennesseeSM and The
MEGA Life and Health Insurance Company.SM
> -Original Message-
> From: IBM Mainframe Discussion List
> [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Donald Johnson
> Sent: Tuesday, February 22, 2011 8:40 AM
> To: IBM-MAIN@bama.ua.edu
> Subje
If management requires the dsnames to include the version number, then
doesn't the JCL have to be changed anyway to avoid confusion? For example,
if you're running V1R1 and want to upgrade to V1R2, if you use aliases then
the JCL would say V1R1 but would resolve to V1R2. And you know who gets the
PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: cascading catalog dataset aliases.
If management requires the dsnames to include the version number, then
doesn't the JCL have to be changed anyway to avoid confusion? For example,
if you're running V1R1 and want to upgrade to V1R2, if you use aliase
>If management requires the dsnames to include the version number
I have two concerns with this:
1. Shouldn't management tell you what to do, not how to do it?
2. What is the benefit of having versions in the Production dsn?
-
Ted MacNEIL
eamacn...@yahoo.ca
--
> -Original Message-
> From: IBM Mainframe Discussion List
> [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Ted MacNEIL
> Sent: Tuesday, February 22, 2011 1:38 PM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: cascading catalog dataset aliases.
>
> >If management requ
On Tue, 22 Feb 2011 08:10:55 -0600, McKown, John wrote:
>Suppose the DSN is SYS3.SOMEPROD.V1R1M0.LINKLIB. Make an
>alias called SYS3.SOMEPROD.PROD.LINKLIB which "points" to the
>SYS3.SOMEPROD.V1R1M0.LINKLIB
>
>Now, the SYMBOLICRELATE alias occurred to me. That's where
>an ALIAS, such as SYS
The obvious advantage to #2 is that it gives you the benefit of allowing you to
change hundreds or thousands of JCL members for every install.
--
Eric Bielefeld
Systems Programmer
Ted MacNEIL wrote:
> >If management requires the dsnames to include the version number
>
> I have two conce
[mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Eric Bielefeld
Sent: Tuesday, February 22, 2011 3:25 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: cascading catalog dataset aliases.
The obvious advantage to #2 is that it gives you the benefit of allowing you to
change hundreds or thousands of JCL members for
In <45e5f2f45d7878458ee5ca6796973355b85...@usdaexch01.kbm1.loc>, on
02/22/2011
at 08:21 AM, "Staller, Allan" said:
>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. M
14 matches
Mail list logo
