This is one of those recurring questions. After the page ds is created
is must be accessed internally by another utility to format it and that
access uses standard catalog search order, which basically means you
can't use "CATALOG" to redirect creation to a non default catalog.
The way to do this is come up with a new HLQ with an alias to direct it
to the new master catalog, and use that HLQ for the new pageds so that
it ends up in the correct master catalog by default. If there were
reasons why you had to be able to refer to this dataset by a different
name, you could then define that name as a PATH to the newly-defined
cluster, pointing that define to the new master catalog. It might also
be possible to alter the names of all components of the ds after
creation by using ALTER with CATALOG redirection, but I would expect
this to fail or cause problems if the dataset were SMS controlled.
If you are going to a new system version, there is probably no real need
for preserving the old pageds HLQ usage, since you can easily change the
pageds names in the IEASYSxx member at the same time you migrate.
We "ping-pong" between two volser conventions and master catalog
conventions when doing system migrations and use "T1M" HLQ for such
master catalog datasets on system 1 vs "T2M" on system two, defining the
appropriate ALIAS on the live system to point to the master catalog of
the system being built. In the case of non-VSAM datasets, you can use
"DEFINE ALIAS" with full dataset name and catalog redirection to play
similar games with non-VSAM datasets, so that those datasets on the new
system can also be uniquely referenced with a system-specific HLQ via
standard catalog search. (Just be aware that RACF access is based on the
real dataset name, not the alias or path that may be used for catalog
search)
[EMAIL PROTECTED] wrote:
In the process of upgrading from Z/os 1.4 to 1.7 I'm taking the
opportunity to upgrade the systems master catalog from 3380 to 3390
device. I have the new master catalog connected as a user catalog on
this system and am in the process of defining all my vsam and non vsam
file, when I attempt to define the new page datasets, the cluster gets
created fine but idcams comes back and
issues these errors
/* DEFINE LOCAL PAGE DATA SET PLPA AND COMMON ON SAME VOLUME */
DEFINE PAGESPACE (NAME(PAGE.VCP3PGA.PLPA) -
FILE(DD1) -
CYLINDERS(1) -
VOLUME(CP3PGA)) -
CATALOG(CATALOG.MASTER.VCP3CT1)
IDC0508I DATA ALLOCATION STATUS FOR VOLUME CP3PGA IS 0
IKJ56228I DATA SET PAGE.VCP3PGA.PLPA NOT IN CATALOG OR CATALOG CAN NOT
IKJ56228I BE ACCESSED
IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12
I'm thinking its due to the fact the page datasets are not in a master
catalog at the time, but how can I stage these page datasets ahead of
time. any help would be appreicated.
thanks
Carmen Vitullo
Acxiom
--
Joel C. Ewing, Fort Smith, AR [EMAIL PROTECTED]
----------------------------------------------------------------------
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
