I believe we've discussed the 'NIP message' problem before. While a very useful message may well be displayed on the IPL-time console, in many (most?) cases it disappears instantly when the machine enters wait state. It's gone so fast that any detail is pretty much indecipherable. While SAD with IPCS is truly much more usable than it used to be, it's still a far cry from getting an operator to read you a message in an oh-dark-thirty phone call.
. . JO.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com From: Peter Relson <rel...@us.ibm.com> To: IBM-MAIN@LISTSERV.UA.EDU, Date: 10/22/2013 06:22 AM Subject: Re: z/OS IPL Issue Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> WIth a syntax error such as the one shown by the OP, there would have been an IPL-time message such as: IEA712I LPALST LIBRARY DATA SETS IGNORED /* -UNABLE TO LOCATE As to why it blew up, it was likely because one of the data sets later in the LPALSTxx definition was also therefore not included (this line was treated as the end of input because it had no trailing comma after the initial token which was the "/*") and some later processing needed a module in one of the not-included data sets. FWIW, I would think that not very many things would treat /* SYS1.CICS41.SDFHLPA, as a valid comment since it does not have the traiilng */. Of course LPALSTxx wouldn't treat it as a valid comment even with the trailing */. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
