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
