On Sep 5, 2007, at 5:59 PM, Paul Gilmartin wrote:
On Wed, 5 Sep 2007 15:30:37 -0500, Ed Gould wrote:
Its been awhile since I had to dynamically invoke IEBCOPY so if I am
out of phase please just say I am wrong.
The only ddname(s) that I can think of that you might need to change
is sysprint and sysin,
I fell into the habit of using "address ATTCHMVS" in EXECs not for
IEBCOPY but for IEBGENER, where some prior step allocated a SYSPRINT
that I wanted to use as SYSUT1 for a subsequent IEBGENER, or I
wanted to use the SYSUT2 from IEBGENER as input to a subsequent
program, all within the single EXEC. I felt it expedient to
override the DDNAMEs to IEBGENER rather than FREE and re-ALLOCATE
(which wouldn't have worked for temporary data sets anyway).
-- gil
Gil,
I guess I was misunderstanding what your issue is. There is an option
when (in assembler) you invoke most (all?) IBM utilities to specify
in a parm list the ddnames you want to use. I don't remember the
syntax exactly but essentially you pass the utility a list of ddnames
and a parm list. In that list in an exact sequence (order) is a
alternate ddname for each file the utility uses ie
sysprint,sysin,first ddname,second ddname etc. I misunderstood what
you were complaining about. I am guessing now you are complaining the
names of the ddnames and not being able to "override " it. In
assembler you would be able to but in JCL and TSO you cannot. while
(to me) its a small complaint, its one I have lived with since day
one of os/360 and don't see it as an issue or overly restrictive.
Ed
----------------------------------------------------------------------
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
