> After an IPL, I can access my program from this linklist data set.
> Now, the dataset is moved to a new volser. I do the following
sequence of
> commands:
>
> SETPROG LNKLST DEFINE,NAME=NEW1,COPYFROM=CURRENT
<<>>
> SETPROG LNKLST ACTIVATE,NAME=NEW2
>
> At this point, a SETPROG LNKLST,TEST,NAME=CURRENT,MODNAME=myprogram
> shows that the module is being found in the library 'dataset'.<<>>
> {The dataset 'dataset' is cataloged in a user catalog, not the master
> catalog.}
>
> Now, when I submit a batch job that does a EXEC PGM=myprogram, I
> receive a S106-F RC=40 which indicates an I/O error on a PDS.
No. SETPROG LNKLST is doing what it was advertised to do, but remember
that changes to the active linklist only take effect for address spaces
started after you issue SETPROG. Batch jobs run in initiators and they
live a very long time. So chances are your job is trying to fetch the
module using the original IPL-time linklist and barfing because that
extent is no longer valid.
CC
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
