Jake,

Is SDSNLINK with 1 ext only? Also, is in cataloged in MCAT?

*Lucas Rosalen*

2014-10-06 13:12 GMT-03:00 Jake anderson <[email protected]>:

> I did Mark Zeldens utility TSO IPLINFO ALL and i see the required DB2
> linklist is loaded. The LNKLST00 has not changed after IPL.
>
> " Is it possible SDSNLINK was added to the LINKLIST after the IEFSSN00 was
> processed?"
>
>  Not sure.
>
> On Mon, Oct 6, 2014 at 9:38 PM, Ron Graham <
> [email protected]> wrote:
>
> > Data sets can be added to the LINKLIST after the initial IPL.  I do this
> > using a PROGxx member in PARMLIB and then issuing the T PROG=xx command:
> >
> > LNKLST DEFINE NAME(LNKLST11) COPYFROM(LNKLST00)
> > LNKLST ADD NAME(LNKLST11)
> >        DSN(data.set.to.add)
> > LNKLST ACTIVATE NAME(LNKLST11)
> >
> >  Is it possible SDSNLINK was added to the LINKLIST after the IEFSSN00 was
> > processed?
> >
> > -----Original Message-----
> > From: IBM Mainframe Discussion List [mailto:[email protected]] On
> > Behalf Of Jake anderson
> > Sent: Monday, October 06, 2014 10:56 AM
> > To: [email protected]
> > Subject: Re: Linklist load during IPL message
> >
> > I did D PROG,LNKLST and ISRDDN and i see the SDSNLINK (after IPL) which
> > has DSN3INI module in it. I am not sure why i received the below message
> > during IPL
> >
> > IEE252I MEMBER IEFSSN00 FOUND IN SYS1.PARMLIB CSR002I BATCH LSR SUBSYSTEM
> > BLSR INITIALIZATION COMPLETE.
> > IEFJ004I SUBSYSTEM xxx NOT INITIALIZED - DSN3INI NOT FOUND
> >
> > Strange thing was I was able to remove and add the IEFSSN Subsystem entry
> > and the issue was fixed.
> >
> > On Mon, Oct 6, 2014 at 9:18 PM, John McKown <
> [email protected]>
> > wrote:
> >
> > > As mentioned using DDLIST and doing a LINKLIST is helpful. An
> > > alternative is the z/OS operator command: d prog,lnklst
> > >
> > > On Mon, Oct 6, 2014 at 10:20 AM, Jake anderson
> > > <[email protected]>
> > > wrote:
> > >
> > > > Hi Group,
> > > >
> > > > We had a situation where a DB2 program DSN3INI was not found due to
> > > > which the DB2 start up command showed invalid command.
> > > >
> > > > I checked up the SYSLOG and I do not see any evidence where LINKLIST
> > > > libraries are loaded. Then Removed the DB2 subsystem dynamically
> > > > from the IEFSSNxx and readded to the IEFSSNxx.
> > > >
> > > > It worked after the above band aid. Is there a way to verify if the
> > > > LINKLIST library gets loaded during IPL time.
> > > >
> > > > Strange thing to see that DB2  SDSNLINK shows under D PROG,LNKLST
> > > > and it was weird thing was that DSN3INI showed as not found during
> IPL
> > time.
> > > >
> > > > Could someone throw light on the above.
> > > >
> > > >
> > > > Jake
> > > >
> > > > --------------------------------------------------------------------
> > > > -- For IBM-MAIN subscribe / signoff / archive access instructions,
> > > > send email to [email protected] with the message: INFO
> > > > IBM-MAIN
> > > >
> > >
> > >
> > >
> > > --
> > > There is nothing more pleasant than traveling and meeting new people!
> > > Genghis Khan
> > >
> > > Maranatha! <><
> > > John McKown
> > >
> > > ----------------------------------------------------------------------
> > > 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

Reply via email to