On Sep 5, 2007, at 12:31 PM, Paul Gilmartin wrote:
On Wed, 5 Sep 2007 12:09:06 -0500, Ed Gould wrote:
Indeed. I'm so accustomed to "address ATTCHMVS" for
o Better PARM facilities
Could you please explain "better parm facilities" , please? The
address [TSO -- gil] command offers parm facilities.
What more could you need?
Two things:
The first has been discussed ad tedium here; surely the list will
prefer
that I not resurrect it today.
The second is the ability to pass multiple PARMs, for example
alternate
DDNAME lists to utilities.
Gil,
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, as all other ddnames can by changed by
specification in sysin . If you are talking about sysut3 or sysut4
(maybe) but they are work type datasets and are worthless after the
job so a temporary dataset is perfect for this.
Mind you this is from a self written program so I am not sure why you
would need to override the ddnames sysprint (or sysin) from TSO.
Please let me know why you would need to do so from TSO. I can't
think if a single reason for either sysin or sysprint, I am not
saying there isn't a good reason just that I can't think of one. TSO
environment allows you to re-allocate either one to a different file,
so its not like batch is user definable. There are other utilities
this might not be true for, I am just curious as to why you say
IEBCOPY it is so needed.
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
