I agree that IBM should provide a means to dynamically assign an alias to a ddname, but IMHO ATTACH is the wrong place to do it. DYNALLOC would seems to be the obvious place to do it.
In the meantime, it is a SMOP to write a subsystem to redirect the I/O. I don't recall the file, but on the CBT there is a subsystem to allow utilities that do not support Wylbur compressed data sets to access them transparently. DDNAME= is implemented in the C/I; there should be no need for Initiator involvement. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Paul Gilmartin <[email protected]> Sent: Wednesday, October 23, 2019 11:20 AM To: [email protected] Subject: Re: Is there a TSO equivalent to JCL DDNAME=? On Wed, 23 Oct 2019 13:54:13 +0300, ITschak Mugzach wrote: >Jcl allows "routing" on DD name to another using DDNAME= opeerand. is there >an equivalent in tso? I remember TSO PIPE, but this was not a standard TSO >command (CBTTAPE maybe). > Perhaps the elusive CMS/TSO Pipelines, formerly available from IBM. Use alternate DDNAME list if invoking a utility that supports it. Use BPXWDYN( 'info ...' ) to extract DSN, VOL, and UNIT, then allocate to a different DDNAME. I suspect DDNAME=, PASS, and referback are implemented in the initiator and unavailable within the jobstep. It's regrettable that alternate DDNAME requires each program to code for it rather than being a part of ATTACH and transparent to the ATTACHed program. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN to write a subsystem ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
