VOL=REF=*.Ddname can be used here.
It seems that once you refer to a data set on the Passed Data Set Queue,
then it has been marked as received, and hence cannot be referenced
again in the same job step.
However, using a previous ddname overcomes that, and also picks up the
correct volume if a tape fills, and another is being written to.
Clem
Dyck, Lionel B. (RavenTek) wrote:
The use we need to to xfer a tape with multiple files on it (label=1,2,3,....)
and thus need the vol=ref.
The working syntax after a suggestion from ibm is VOL=(,RETAIN,REF=dsn)
And since we are using GDG's it must be VOL=(,RETAIN,REF='dsn')
--------------------------------------------------------------------------
Lionel B. Dyck (Contractor) <sdg><
Mainframe Systems Programmer – RavenTek Solution Partners
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Steve Thompson
Sent: Tuesday, July 03, 2018 12:23 PM
To: [email protected]
Subject: Re: [EXTERNAL] Re: Connect:Direct and VOL=REF ?
Wow, this doc is not formatted the way it used to be.
When one does a copy, one can send the data or one can pull the
data. Let us assume that the system that starts the process is
the one in control (Process control *AND* PNODE), and that one is
going to copy *from* the PNODE to the SNODE (again, it can be
done the other way).
Now, where the data set is going *TO* one can use REF=dsn, and
this will force that data set being copied to the same VOLUME as
the DSN specified by the REF=.
Why would one want to do this?
One may want or need to do this because one knows the name of a
DSN on the client's system and by using that reference, one can
put another file over there where the client has asked for it to be.
HTHs
Steve Thompson
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
