Re: SUB=MSTR STC with DSNs in User Catalog
On Tue, 2008-05-27 at 19:55 -0700, Philip R Chauvet wrote: > Other data sets that you should catalog in the master catalog are > shown in Table 3. > > Table 3. Master Catalog Entries > Key operational data sets such > as: > ° SMF data sets FWIW I've been running with the SMF datasets in a usercat for quite a long time now. (Though to be sure Greg Dyck recommended against it ten years ago, pointing out that SMF can end up allocating your usercat forever.) -- David Andrews A. Duda and Sons, Inc. [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
Re: SUB=MSTR STC with DSNs in User Catalog
This is still a documented restriction. See section 2.4.1 in the 1.9 version of the manual DFSMS Managing Catalogs (SC26-7409-05) where it states: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DGT2C150/2.4.1?SHELF=DGT2BK71&DT=20060608131553 The master catalog for a system contains entries for all the user catalogs that are used on the system and the aliases pointing to them. Other data sets that you should catalog in the master catalog are shown in Table 3. Table 3. Master Catalog Entries Entry types Description/Example User catalogs Entries for all user catalogs used on the system. Aliases Entries for all aliases pointing to the user catalogs on the system. Pagespaces Entries for the pagespaces used on the system. System software target libraries The data sets used to run the system such as LINKLIB and ISPPENU. Key operational data sets Key operational data sets such as: ° PARMLIB data sets ° Parameter libraries for JES and TCP/IP ° SMS configuration data sets ° SMF data sets ° RACF databases ° Couple data sets Subsystem data sets Subsystem data sets, such as those for IMS(TM), DB2®, or CICS®, especially when they are replaced. Requirement: Data sets required during the IPL process must be cataloged in the master catalog. Recommendation: A master catalog should not contain entries for application or end user data sets. These should be contained in user catalogs that are pointed to by the appropriate aliases in the master catalog. For a further description of what may occur see apar OA18992. You may get away with this at times, but sooner or later it will catch up with you. Most likely, it will catch up with you when it's most inconvenient. Phil Chauvet Tucson Software Technical Support - Catalog and IDCAMS Level 2 support "William H. Blair" <[EMAIL PROTECTED]> Sent by: IBM Mainframe Discussion List 05/14/2008 06:53 PM Please respond to IBM Mainframe Discussion List To IBM-MAIN@BAMA.UA.EDU cc Subject SUB=MSTR STC with DSNs in User Catalog Distinguished IBMers that might be lurking, (especially of the CATALOG ADDRESS SPACE-knowledgeable variety) On Wed, 21 Mar 2001 15:55, Mark Thomen <[EMAIL PROTECTED]> wrote: > THIS RESTRICTION HAS NOT BEEN REMOVED! Until CAS is "full function", > which doesn't occur until after Master Scheduler Initialization is > complete, we cannot allocate user catalogs to access them - the > dynamic allocation services are not available until that time. On Wed, 22 Mar 2001 11:28, Mark Thomen <[EMAIL PROTECTED]> wrote: > The Catalog Address Space comes up at the start of MSI. User > catalogs cannot be allocated by CAS during that period of time, > but CAS is "initialized" - it supports all catalog functions > except accessing user catalogs. Without distinguishing between > limited-function CAS and full-function CAS you [might] assume > that as SOON as CAS comes up it can allocate the catalogs [but] > it can't. The casual user will see CAS initialization messages > issued prior to MSI complete and assume they can access user > catalogs [but] they can't. So the distinction is important. > ... > [this] is still documented in "Managing Catalogs". > > Mark Thomen, DFSMS Development - Catalog, IDCAMS, and VSAM I checked as far back as z/OS 1.5 (as far as I had, or cared to download, back releases of this SRL). I could not locate any text that even remotely resembled these statements. I do remember this being documented in "Managing Catalogs" for OS/390 2.?, because I found it when the above message was sent, but unfortunately I do not remember the exact text, so I was unable to search current versions of this publication for the old text or find the section it was once contained in. Is this still "documented?" If not, why was it removed? I hope it is because this issue has now been addressed and fixed, and the Catalog Address Space is now "full function" by the time any other address spaces (other than the ones that the Master Scheduler itself starts, of course) that start under the Master Subsystem actually do start to go through JCL conversion and interpretation, and then allocation (which is the first time that a user catalog might be referenced during IPL). Inquiring minds (still) want to know where Mark Thomen is when we really need him. -- WB -- 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.
Re: SUB=MSTR STC with DSNs in User Catalog
Mark Thomen is on medical leave. Damn sorry to hear that. Please let him know he has all our best wishes. -- 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
Re: SUB=MSTR STC with DSNs in User Catalog
> -Original Message- > From: IBM Mainframe Discussion List On Behalf Of Jim Mulder > > IBM Mainframe Discussion List wrote on > 05/14/2008 09:53:49 PM: > > > Inquiring minds (still) want to know where Mark Thomen is when we > > really need him. > > Mark Thomen is on medical leave. Nothing devastating, we hope. -jc- -- 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
Re: SUB=MSTR STC with DSNs in User Catalog
IBM Mainframe Discussion List wrote on 05/14/2008 09:53:49 PM: > Inquiring minds (still) want to know where Mark Thomen is when > we really need him. Mark Thomen is on medical leave. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY -- 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
Re: SUB=MSTR STC with DSNs in User Catalog
IBM Mainframe Discussion List wrote on 05/15/2008 01:23:44 AM: > Go to SDSF DA screen, look at all asids > and sort them by asid. There will be an asid in the upper 20 not > used (in my case it was x'10'). That was limited function CAS, the > one only capable of accessing the master cat. Full function CAS is > asid x'26' on that system. In z/OS 1.9, if you specify REUSASID(YES) in DIAGxx, the CATALOG address space will use a reusable asid, so that your asid x'10' could subsequently used by another reusable asid address space. So if you specify REUSASID=YES on the START command for LLA or VLF, it could use asid x'10'. Also, CATALOG used to obtain a new system LX for each restart. This was fixed in z/OS 1.9 so that CATALOG reuses its system LX. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY -- 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
Re: SUB=MSTR STC with DSNs in User Catalog
Without knowing *where* what Mark Thomen said is now documented, the restriction still applies. Go to SDSF DA screen, look at all asids and sort them by asid. There will be an asid in the upper 20 not used (in my case it was x'10'). That was limited function CAS, the one only capable of accessing the master cat. Full function CAS is asid x'26' on that system. The only hint I was able to find in the 'Managing Catalogs' manual was this: "Aliases of data sets may not be used prior to the start of Master Scheduler Initialization. This is approximately the time that the system switches to full screen console mode. Thus, cataloged data set names contained in system initialization members that are read and processed prior to this time may NOT be specified as aliases. The actual data set names must be provided." Regards, Barbara Nitz -- GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen! Jetzt dabei sein: http://www.shortview.de/[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
SUB=MSTR STC with DSNs in User Catalog
Distinguished IBMers that might be lurking, (especially of the CATALOG ADDRESS SPACE-knowledgeable variety) On Wed, 21 Mar 2001 15:55, Mark Thomen <[EMAIL PROTECTED]> wrote: > THIS RESTRICTION HAS NOT BEEN REMOVED! Until CAS is "full function", > which doesn't occur until after Master Scheduler Initialization is > complete, we cannot allocate user catalogs to access them - the > dynamic allocation services are not available until that time. On Wed, 22 Mar 2001 11:28, Mark Thomen <[EMAIL PROTECTED]> wrote: > The Catalog Address Space comes up at the start of MSI. User > catalogs cannot be allocated by CAS during that period of time, > but CAS is "initialized" - it supports all catalog functions > except accessing user catalogs. Without distinguishing between > limited-function CAS and full-function CAS you [might] assume > that as SOON as CAS comes up it can allocate the catalogs [but] > it can't. The casual user will see CAS initialization messages > issued prior to MSI complete and assume they can access user > catalogs [but] they can't. So the distinction is important. > ... > [this] is still documented in "Managing Catalogs". > > Mark Thomen, DFSMS Development - Catalog, IDCAMS, and VSAM I checked as far back as z/OS 1.5 (as far as I had, or cared to download, back releases of this SRL). I could not locate any text that even remotely resembled these statements. I do remember this being documented in "Managing Catalogs" for OS/390 2.?, because I found it when the above message was sent, but unfortunately I do not remember the exact text, so I was unable to search current versions of this publication for the old text or find the section it was once contained in. Is this still "documented?" If not, why was it removed? I hope it is because this issue has now been addressed and fixed, and the Catalog Address Space is now "full function" by the time any other address spaces (other than the ones that the Master Scheduler itself starts, of course) that start under the Master Subsystem actually do start to go through JCL conversion and interpretation, and then allocation (which is the first time that a user catalog might be referenced during IPL). Inquiring minds (still) want to know where Mark Thomen is when we really need him. -- WB -- 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
