Lizette, I think that is an oversimplification. For a lot of datasets a catalog 
search is not needed to access them as long as the system can find them. Some 
examples: 

LPALSTxx: 
PRTCP.PERM.SEZALPA(&SYSR1),

PROGxx: 
APF    ADD          DSN(PRTCP.PERM.SEZALOAD)             VOLUME(&SYSR1)
LNKLST ADD NAME(PR) DSN(PRTCP.PERM.SEZALOAD)             VOLUME(&SYSR1)

COUPLExx: 
DATA TYPE(CFRM)                                            
     PCOUPLE(PSIXC.OPER.&SYSPLEX..CFRM.CDS01,SC&SYSPLEX.10)
     ACOUPLE(PSIXC.OPER.&SYSPLEX..CFRM.CDS02,SC&SYSPLEX.11)

IODF: volume identified through load parm.  

Thanks,
Bart

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Lizette Koehler
Sent: Thursday, October 02, 2014 8:08 PM
To: [email protected]
Subject: Re: z/OS datasets that must be in the MCAT (UNCLASSIFIED)

IIRC, So during an IPL until SMS is UP, any datasets needed have to be in the 
mcat.  Once SMS is up, UCATs are available and then the datasets can have 
different access paths.

Does this help?

Lizette


>On Thu, Oct 2, 2014 at 5:12 PM, Storr, Lon A CTR USARMY HRC (US)
><[email protected]> wrote:
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>> Hello List,
>>
>> It appears that some of the old restrictions regarding MCAT-cataloging of 
>> installation-allocated datasets that are accessed during system 
>> initialization (usually for OUTPUT) have been relaxed.
>>
>> I have verified that page datasets must still be defined in the MCAT but, 
>> other than that, I haven't yet found any absolute restrictions. Even couple 
>> datasets, it seems, may be in a UCAT if a volser is specified in COUPLExx.
>>
>> So far, I've checked SMF (MAN) datasets, BRODCAST, "couple", UADS, USS file 
>> systems (including root) and DFSMS ACDS/COMMDS. I find no text explicitly 
>> forbidding UCAT cataloging.
>>
>> I'm fairly certain that the CATALOG address space must be active before 
>> UCATs are accessible but I'm rather fuzzy about exactly where in the system 
>> initialization timeline this occurs (i.e. relative to the components that 
>> want to access these datasets).
>>
>> What other installation-allocated datasets that z/OS accesses during system 
>> initialization must be MCAT-cataloged?
>>
>> Thanks,
>> Alan

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to