I have to agree with Don. If something needs to be in the linklist or
LPA list, I try to find another way. For instance, in the LINKLIST, I'll
refer to the dataset with a vol-ser reference. I don't recall ever
having something that needed to be in the LPALIST, so I'm unsure how to
handle that situation. I try to avoid anything that might require MCAT
updates, such as re-installing a OEM product. ANY update to a catalog,
no matter how trivial it seems, poses a risk of damage and the MCAT is
the "Sacred Cow" of your system. Damage might mean a disastrous outage.
Rick
-----------------------------------------------------------------------------
Imbriale, Donald (Exchange) wrote:
First, I don't usually put OEM stuff in the master catalog unless it
absolutely positively has to be there. OEM stuff is better of in a
usercat. Doing so makes it easier to get to those products from other
systems with other mastercats.
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.
To handle your situation now you could just DEFINE entries in the 1.7
mastercat for the data sets that you need. This would work only for
non-VSAM entries. For VSAM data sets, you can do a DEFINE RECATALOG,
but only if the high-level qualifier is SYS1.
To help build new entries for the 1.7 mastercat, you could check out
Alistair Gray's REXX-based RCNVTCAT (or is it RCATCNVT?) on the CBT
'tape'.
Don Imbriale
----------------------------------------------------------------------
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
