I have found command SETOMVS SYNTAXCHECK=(xx) to be useful when making changes to BPXPRMxx members.
It checks syntax as well as the existence of HFS and zFS data sets specified in the catalog. Mount points are not verified. -- -- Don Imbriale On Wed, Jan 6, 2010 at 9:04 AM, McKown, John <john.mck...@healthmarkets.com>wrote: > > -----Original Message----- > > From: IBM Mainframe Discussion List > > [mailto:ibm-m...@bama.ua.edu] On Behalf Of Peter Relson > > Sent: Wednesday, January 06, 2010 6:55 AM > > To: IBM-MAIN@bama.ua.edu > > Subject: Re: useless message at IPL > > > <snip> > > > > What message was it waiting for you to reply to? > > > > It's almost certain that the messages were written via WTO, > > not WTL. They > > probably specified MCSFLG of HARDCPY. If these were ASAxxxI > > messages, it's > > possible that the invoker did not take advantage of some > > infrastructure > > support that would avoid using hardcopy-only during IPL for > > precisely the > > case you encountered. After IPL, hardcopy-only is used to > > avoid flooding > > the console, since the syslog can be examined. A change to > > take advantage > > of this could likely be made in a future release. > > > > Peter Relson > > z/OS Core Technology Design > > Unfortunately, I don't have the SYSLOG from that IPL. The message being > waited upon was one which said that I need to reply with an OMVS= which > contained BPXPRMnn members which did not have any syntax errors. I knew the > old PARMLIB BPXPRMnn suffix values and so reply with them. This allowed z/OS > to continue to IPL. I then looked at the SYSLOG to see what I did wrong and > fix it. I then IPL'ed again. If the BPXPRMnn syntax errors had been shown, I > could have fixed them on another system and simply replied with same member > suffixes and thus avoided a second IPL. OK, not a big deal. However, if I > had done an "update in place" of the PARMLIB member, I wouldn't have had a > way to continue the IPL. So I would have had to try to figure out the error > on another system with no help. I guess what it really means is that I > should never update an in-use member of PARMLIB, but copy it to a different > suffix, modify it, then point to the modified PARMLIB member. > > -- > John McKown > Systems Engineer IV > IT > > Administrative Services Group > > HealthMarkets(r) > > 9151 Boulevard 26 * N. Richland Hills * TX 76010 > (817) 255-3225 phone * (817)-961-6183 cell > john.mck...@healthmarkets.com * www.HealthMarkets.com > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
