Lizette, Apology If my thoughts are different. Does the wait state 064 really has to do anything with the wrong syntax ?
On Mon, Oct 21, 2013 at 6:52 PM, Lizette Koehler <[email protected]>wrote: > Just one comment, > > When I run into these types of issues, I usually add a comment to that > member with a warning on how to code things. > > You might want to consider adding comments at the end of this member > explaining how to comment out a line. It may save you or someone else in > the > future - how to avoid any confusion on comments and 064 Wait states. > > Lizette > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] On > > Behalf Of Lizette Koehler > > Sent: Monday, October 21, 2013 6:13 AM > > To: [email protected] > > Subject: Re: z/OS IPL Issue > > > > As you have seen, the syntax rules for LPALST and comments do not follow > other > > comment functions. This is probably due to where it is loaded and the > process has > > a very strict syntax for the process. > > > > So depending on where you put your /* you could have lost many datasets > that > > were to be loaded by LPALSTxx. > > > > > > > > From the Manual > > > > Syntax rules for LPALSTxx > > > > z/OS V1R12.0 MVS Initialization and Tuning Reference SA22-7592-21 > > > > The following rules apply to the creation of LPALSTxx: > > Comments: On a line, data entered after the last data set name and > the > optional > > comma continuation character is treated as a comment and ignored. > > > > A /* is not a recognized comment line in the LPALSTxx member. But you > could do > > > > NAME1, > > NAME2, > > NAME3 this ends the list, anything that follows is a comment. > > Comments follow here. > > > > > > > > My two cents worth - IBM could clarify the comment process in LPALSTxx a > bit > > better as well as provide a nice sample of how to place comments in > LPALSTxx. > > > > > > > > Lizette > > > > > > > -----Original Message----- > > > From: IBM Mainframe Discussion List [mailto:[email protected]] > > > On Behalf Of saurabh khandelwal > > > Sent: Monday, October 21, 2013 2:55 AM > > > To: [email protected] > > > Subject: Re: z/OS IPL Issue > > > > > > Hello, > > > In my LPALST member, while adding dataset for CICS 5.1 , > > > rather > > then > > > removing entry for older CICS 4.2, I simply commented CICS 4.2 dataset > > line like > > > below. > > > > > > /* SYS1.CICS41.SDFHLPA, > > > > > > > > > And added CICS 5.1 dataset SYS1.CICS51.SDFHLPA. I think, this is only > > reason > > > for this 064 wait code. But at last problem resolved. Thanks for all > > help. > > > > > > Regards > > > Saurabh > > > > > > > > > On Sun, Oct 20, 2013 at 6:30 PM, Peter Relson <[email protected]> > wrote: > > > > > > > >Problem has been resolved. The issue was with syntax issue in > > > > >LPALST parmlib member . > > > > > > > > Can you please explain exactly what the issue was? A syntax error in > > > > LPALST will not ordinarily result in a program check WAIT 064 unless > > > > it meant that your LPALST did not have a data set that the system > > > > requires during IPL. > > > > > > > > Peter Relson > > > > z/OS Core Technology Design > > > > > > -- > > > Thanks & Regards > > > Saurabh Khandelwal > > > > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
