Regarding
SETPROG LNKLST,UNALLOCATE
P LLA
SET PROG=09
S LLA,SUB=MSTR
SETPROG LNKLST,ALLOCATE
This approach is not right. It is either unnecessary or wrong. LNKLST
UNALLOCATE is provided so that you can manipulate an uncataloged data set
of the same name as a data set in the LNKLST. It is not provided so that
you can attempt to fool the system into working with catalog updates that
will not be reflected in current allocations (such as in the LNKLST).
>LNKLST ACTIVATE NAME(SAMPLLA)
>LNKLST UPDATE JOB(*)
>APF ADD DSNAME(SYS1.MYLINKLB) VOLUME(&SYSR3)
The APF state of LNKLST data sets should be established before the LNKLST
set is activated. Not critical, but better.
And you should never use LNKLST UPDATE unless you are willing to re-IPL at
the next instant, as it is unpredictably dangerous. Of course sometimes
that is better than not trying it at all.
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
