Hello: I am encountering a problem with the following scenario:
I have a dataset defined in the PARMLIB member LNKLSTxx like this:
dataset(volser)
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 DELETE,NAME=NEW1,DATASET=dataset
SETPROG LNKLST ACTIVATE,NAME=NEW1
SETPROG LNKLST DEFINE,NAME=NEW2,COPYFROM=CURRENT
SETPROG LNKLST ADD,NAME=NEW2,DSNAME=dataset,VOLUME=newvolser
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'. (It would be
useful if
this would also return what volume it found it on.)
{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.
Is this a possible problem with the SETPROG LNKLST functionality, or
is my methodology for moving this dataset to a new volume flawed?
After an IPL, (of course) everything is ok. The data set is found
in the LINKLST on the new volume.
Thank you.
Paul Schuster
----------------------------------------------------------------------
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
