ALIAS2

[Cartwright, Dave]

I am trying to set up some alias pointers to make it easier to switch
software releases, as documented in Managing Catalogs
(http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DGT2C110/2.2
7?DT=20011230194816)



In ISPF 3.4 two of my eight datasets are shown as ALIAS2 rather than
ALIAS.

What does this mean?

It is ZOS R1.4 and I am not using SYMBOLICRELATE.



Dave




*********************************************************************************
This email is intended solely for the use of the individual to whom
it is addressed and may contain confidential and/or privileged
material. Any views or opinions presented are solely those of the
author and do not necessarily represent those of AGCO.
If you are not the intended recipient, be advised that you have
received this email in error and that any use, dissemination,
forwarding, printing or copying of this email is strictly prohibited.

Neither AGCO nor the sender accepts any responsibility for viruses and it is your
responsibility to scan and virus check the e-mail and its attachment(s) (if any).
*********************************************************************************
AGCO Limited, a limited company, registered in England (registered no.509133) with its registered office at Abbey Park Stoneleigh, Kenilworth CV8 2TQ, England.


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

[Dave Cartwright]

Sorry, got it.
The referenced dataset is on HSM ML2

Dave

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

[Mark Zelden]

On Tue, 3 Apr 2007 13:01:36 +0100, Cartwright, Dave
<***@UK.AGCOCORP.COM> wrote:

>I am trying to set up some alias pointers to make it easier to switch
>software releases, as documented in Managing Catalogs
>(http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DGT2C110/2.2
>.7?DT=20011230194816)
>
>

Can I just say .. yuck. I dislike data set aliases. I have used them for
a quick fix or temporarily for a migration but that is it. They always seem
to get messed up by someone. The problem is that when you rename the
data set, the alias is removed so you have to manually establish it
again. But that is just my take. I think our DB2 group uses them.

That last time I used them for software *I* supported was to get
rid of VnRnMn from ISPF data set names around OS/390 R1. Changing
logon procs was no problem, but there was a lot of batch ISPF and
I didn't want anything to break when I migrated. After the migration I
got all the JCL changed and removed the aliases. Other than that I have
used it at some SYNCSORT shops to create a SYS1.SORTLIB alias to
the SYNCSORT linklib (I used to see a lot of sample JCL with
SYS1.SORTLIB references). I am in a SYNCSORT shop now I just
looked and found a SYS1.SORTLIB... but it is an empty PDS.

>
>In ISPF 3.4 two of my eight datasets are shown as ALIAS2 rather than
>ALIAS.
>
>What does this mean?
>
>It is ZOS R1.4 and I am not using SYMBOLICRELATE.
>

It means the real dsn is migrated to HSM ML2. If it said ALIAS1 it means
the real dsn is migrated to HSM ML1.

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group: G-ITO
mailto:***@zurichna.com
z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/
Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html

ML1.

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

[Shane]

On Tue, 2007-04-03 at 07:52 -0500, Mark Zelden wrote:

> Can I just say .. yuck. I dislike data set aliases.

What he said.

> I think our DB2 group uses them.

Must come with the territory. I finally weaned our guys off them when I
deleted all the old "SYS1.DB2.SDSNEXIT" (et al) alias' with my V7
cleanup.
They all pointed to V6 datasets, so I trashed them. Weekend batch
started falling over, but the DBAs got called, not me.
They decided to bite the bullet and (finally) get rid of the references
rather than call me.
Smart move.

Shane ...

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

[Steve Runtsch]

On Tue, 3 Apr 2007 13:01:36 +0100, Cartwright, Dave
<***@UK.AGCOCORP.COM> wrote:

>I am trying to set up some alias pointers to make it easier to switch
>software releases,

Good move. It can make your software support life much easier.

Steve

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

[Jousma, David]

I agree, taking version number out of dataset names for running datasets
is a good thing, as it reduces the need to "fix" JCL. With that said, I
HATE ALIAS's. We install to ver.rel datasets, then at implementation
time, do dataset copies with rename to remove ver.rel. That way NO ONE
has your maintenance libraries allocated either. I don't mind limited
use of alias's to get out of a pinch TEMPORARILY, but not as a long term
solution.

Dave


________________________________________________________
Dave Jousma
Principal Systems Programmer
***@53.com
616.653.8429


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@ibm-main.lst
Behalf Of Steve Runtsch
Sent: Tuesday, April 03, 2007 10:44 AM
To: IBM-***@BAMA.UA.EDU
Subject: Re: ALIAS2

On Tue, 3 Apr 2007 13:01:36 +0100, Cartwright, Dave
<***@UK.AGCOCORP.COM> wrote:

>I am trying to set up some alias pointers to make it easier to switch
>software releases,

Good move. It can make your software support life much easier.

Steve

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

This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated.

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

[Richard Peurifoy]

Jousma, David wrote:
> I agree, taking version number out of dataset names for running datasets
> is a good thing, as it reduces the need to "fix" JCL. With that said, I
> HATE ALIAS's. We install to ver.rel datasets, then at implementation
> time, do dataset copies with rename to remove ver.rel. That way NO ONE
> has your maintenance libraries allocated either. I don't mind limited
> use of alias's to get out of a pinch TEMPORARILY, but not as a long term
> solution.
>
> Dave

We have a product used by several different groups. They never all want
to upgrade at the same time. My solution was to leave release numbers
in the datasets, and modify the JCL to have symbols for the version
number in the DSN's. An INCLUDE member specifies the version for each
group. Whenever one group is ready to upgrade the version number in the
INCLUDE member is updated.

INCLUDE member VER

//GRP1PRD SET G1PRD=V413
//GRP1TST SET G1TST=V510
//GRP2PRD SET G2PRD=V413
//GRP2TST SET G2TST=V413


PROC used by group 1 for test

//G1TEST PROC
// INCLUDE MEMBER=VER
//STEP1 EXEC PGM=xxx
//STEPLIB DD DSN=hlq.&G1TST..LOAD,DISP=SHR

Once setup the only change needed is to the VER
member. Of course if the groups create their own JCL
they have to use the INCLUDE and symbols correctly
for this to work. This does create more PROC's, so
if JCL changes have to be made for other reasons there
are more places to do it. Other INCLUDE's might be used
for some of this.

--
Richard

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

[Steve Runtsch]

On Tue, 3 Apr 2007 11:23:29 -0400, Jousma, David <***@53.COM>
wrote:

>We install to ver.rel datasets, then at implementation
>time, do dataset copies with rename to remove ver.rel. That way NO ONE
>has your maintenance libraries allocated either.

Whether your users use your maintenance library or not is entirely your
choice, not your users' choice. You have control over the data set to which
the alias relates.

Steve

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

[Ted MacNEIL]

>That last time I used them for software *I* supported was to get rid of VnRnMn from ISPF data set names around OS/390 R1.

In a previous life, we had two IMS sub-systems that we wanted to merge into an IMS-PLEX.
The libraries were named differently for each one, so we created a common set of libraries and created aliases with the old name(s) so we wouldn't break (application and system) updates.

Last I heard, they never took the final step and got all jobs to point to the new names.

-
Too busy driving to stop for gas!

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