http://www.redbooks.ibm.com/redbooks/pdfs/sg246982.pdf PDF page 63-64, printed page 47-48.
On Thu, Oct 2, 2014 at 5:12 PM, Storr, Lon A CTR USARMY HRC (US) <lon.a.storr....@mail.mil> 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 > > > > > > Classification: UNCLASSIFIED > Caveats: NONE > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
