Still, why fight. The instructions to have SMS be the first subsystem up are clear and only a couple decades old. Your error shows that something was not as you and your IPL expected. This may not fix the problem, but it will eliminate one possibility and doing it correct may prevent other problems in the future.
> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Jake anderson > Sent: Tuesday, October 07, 2014 11:26 AM > To: [email protected] > Subject: Re: Linklist load during IPL message > > Dave > > Its a pds. > On 7 Oct 2014 23:53, "Gibney, Dave" <[email protected]> wrote: > > > The SMS documentation clears says that SUBSYS SUBNAME(SMS) > > INITRTN(IGDSSIIN) INITPARM('ID=00,PROMPT=DISPLAY') Should be the first > > entry in IEFSSNxx and you don't seem to have it at all. > > > > If SYSTEM.DB210.LINKLIST is a PDS/E, then that would be yet another > > reason to be sure to have SMS initialized first. > > > > > -----Original Message----- > > > From: IBM Mainframe Discussion List > > > [mailto:[email protected]] On Behalf Of Jake anderson > > > Sent: Tuesday, October 07, 2014 4:49 AM > > > To: [email protected] > > > Subject: Re: Linklist load during IPL message > > > > > > Hi Peter/All, > > > > > > I did : > > > > > > SETPROG LNKLST TEST NAME(CURRENT) MOD(DSN3INI) CSV502I > MODULE > > > DSN3INI WAS LOCATED 715 IN DATA SET SYSTEM.DB210.LINKLIST USING > > > LNKLST SET CURRENT > > > > > > > > > SUBSYS SUBNAME(JES2) /* JES2 IS THE PRIMARY SUBSYSTEM */ > > > PRIMARY(YES) START(NO) > > > SUBSYS SUBNAME(BLSR) /* BATCH LOCAL SHARED RESOURCES */ > > > INITRTN(CSRBISUB) > > > SUBSYS SUBNAME(XXXX) > > > INITRTN(DSN3INI) > > > INITPARM('DSN3EPX,!XXXX,S') > > > > > > > > > The DB2 maintenance went on before the IPL, but not sure if some of > > > the > > PTF > > > would have caused this problem. > > > > > > > > > > > > > > > On Tue, Oct 7, 2014 at 5:01 PM, Peter Relson <[email protected]> > wrote: > > > > > > > If you have not dynamically updated the LNKLST after IPL, then > > > > probably the easiest thing to do is > > > > > > > > SETPROG LNKLST TEST NAME(CURRENT) MOD(xxxx). > > > > > > > > Which will use the actual LNKLST DCB to "search" for xxxx. Given > > > > the behavior cited, it likely won't be found. And there likely is > > > > a message about the data set in question in the log. > > > > > > > > Substitute LNKLST00 (or whatever was the IPL-time definition via > > > > PROGxx) if you have dynamically updated the LNKLST. > > > > > > > > I'm sure we all recognize that the phrase "LINKLIST libraries are > > loaded" > > > > from the OP is not really legit. The libraries themselves are not > > > > "loaded". Modules are loaded from the libraries (upon > request/demand). > > > > > > > > Peter Relson > > > > z/OS Core Technology Design > > > > > > > > ------------------------------------------------------------------ > > > > ---- 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 > > > > ---------------------------------------------------------------------- > > 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
