Hi Group,
I have reviewed the LOG, Here is my summary on what I took :
The DB2 Linklist is on USERCAT and SMS managed Volume.
The SYSLOG says that SMS got active after the below message IEFJ004I
IEFJ004I SUBSYSTEM XXX NOT INITIALIZED - DSN3INI NOT FOUND
IGD020I SMS IS NOW ACTIVE
The Linklist has the below entry :
LNKLST ADD NAME(LNKLST00) DSNAME(SYSTEM.DB210.LINKLIST)
VOLUME(LNKL01).
Dynamically no LNKLST00 was added.
Not sure why DSN3INI did not get recognized.
On Mon, Oct 6, 2014 at 11:48 PM, Lucas Rosalen <[email protected]>
wrote:
> No IEA716I messages during the IPL?
>
> 2014-10-06 15:15 GMT-03:00 Staller, Allan <[email protected]>:
>
> > I do not believe that the CAS is available at the initial LNKLST build
> > time. Thus, datasets in LNKLST *MUST* be in LNKLST at IPL time.
> > They can be added later, which describes the symptoms in your OP.
> >
> > I believe if you peruse the system log, you will find a message "SDSNLINK
> > NOT FOUND"
> >
> > HTH,
> >
> > <snip>
> >
> > Its on single extent. The sdsnlink is catalogued to a usercat.
> >
> > </snip>
> >
> > ----------------------------------------------------------------------
> > 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
