Harold,

You say "usually IBM tends to rename the sys1 files, moves them to other
volsers, 
changes sizes of files which tend to force file to different volsers.
etc.".  I may not understand what you mean by this, but I have not
really encountered these issues.

Many of the data sets are on the sysres (or its extensions) and the
catalog entries can use indirect volsers or symbols.  If it's on the
sysres for 1.4, it will probably be on the sysres for 1.7.  So the 1.4
catalog entry with volser ****** will still work for 1.7; when you IPL a
1.4 sysres, those will point to that volume; when you IPL a 1.7 sysres,
they will point to the 1.7 sysres.  Other data sets tend to stay in
place also, whether it be a volume for 

HFS/zFS data sets or operational data sets such as SYS1.PARMLIB; so
catalog entries for 1.4 will still work for 1.7.

With each new release, you can use ServerPac to identify what data sets
are new and where they are located.  You can add those entries to your
master catalog without impacting the running of your 1.4 system, but
still be ready to run 1.7.

If IBM 'tends to rename the sys1 files' (which I don't really think they
do), add the new name to the catalog.  When you've completed conversion
to 1.7, then delete the old unneeded entries.

Don Imbriale

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Harold Zbiegien
Sent: Friday, December 29, 2006 3:34 PM
To: [email protected]
Subject: Re: Catalog Question

Uh, could you (or any one else) expound on this?,

usually IBM tends to rename the sys1 files, moves them to other volsers,

changes sizes of files which tend to force file to different volsers.
etc.

And in our case, (just getting ready to install 1.7 into production) we
went 
from mod3 to mod 9 volumes for our opsystem packs.

I don't see how you can easily get away with not building a new master 
catalog.

----- Original Message ----- 
From: "Imbriale, Donald (Exchange)" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To: <[email protected]>
Sent: Friday, December 29, 2006 10:50 AM
Subject: Re: Catalog Question


<snip>
Second, you can avoid this issue in the future by abandoning the process
of building a new master catalog for each new release of the operating
system.

<snip>




***********************************************************************
Bear Stearns is not responsible for any recommendation, solicitation, 
offer or agreement or any information about any transaction, customer 
account or account activity contained in this communication.
***********************************************************************

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

Reply via email to