Classification: UNCLASSIFIED Caveats: NONE John:
I would agree that CPP does a reasonable job regarding the configuration options which are supported. I don't believe that there is anything marked MCAT=Y that shouldn't be; CPP must accommodate all enterprises and users of all skill levels. Hence, the CPP designers have justifiably opted to lean towards the "safe" side. Having said that, it appears that most of the MCAT=Y datasets don't have to be if, as you already specified, one knows what they are doing and is willing to do some extra work. I often tweak the jobs created by CPP. For example: adding ROUND to the allocation of PDS libraries containing LMODs. Elardus: 1) I will, of course, inform you of the results. 2) I don't expect issues regarding symbolics. NIP supports them fairly early in PARMLIBs and CAS supports them in UCAT entries. 3) My intent is for all "target" datasets associated with a z/OS element or feature to be MCAT-catalogued (whether or not the HLQ is SYS1). Cheers, Alan -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of John Eells Sent: Monday, October 06, 2014 1:41 PM To: [email protected] Subject: Re: z/OS datasets that must be in the MCAT (UNCLASSIFIED) [email protected] (Storr, Lon A CTR USARMY HRC , US) wrote: <snip> > I intend to build a test z/OS image to test my beliefs. If > system-initialization functions as per my current beliefs, I don't see any > reason why this site can't move forward. They would need to understand that > certain tasks performed by CPP might be incomplete or erroneous but this is > easily documented. <snip> "Incomplete" is of course literally true, but let me put it another way. ServerPac supports a subset of what's the system supports. As with a number of other flags, when you override the MCAT flag you should expect to have to do some additional work. In my view, the ServerPac team makes pretty good decisions about what to support for this particular flag. (A lot of the variations are unusual, as this very thread illustrates, and we have other things we can do that will yield broader benefits.) Of course, if we've failed to support a common variation you and others should open a requirement to let the team know. Sometimes we don't have a perfect view of "what's really going on out there" and need to know that "everybody who's rational does that." On the other hand, if you find a data set for which no additional setup is required marked MCAT=Y when it shouldn't be, I'd suggest opening a PMR to get that fixed. We shouldn't all try to live with "erroneous." -- John Eells z/OS Technical Marketing IBM Poughkeepsie [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN Classification: UNCLASSIFIED Caveats: NONE ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
