Paul Gilmartin wrote:
What is the rationale for that rule? Whose job was made easier by imposing it?
I would surmise that when the logic for scanning passed data set chains was established, someone either assumed that references would be unique, or the logic to handle it correctly proved to be too convoluted (e.g., resolving different DISP requests).
BTW, what's the rationale for the rule that UNIT=AFF is not allowed to refer to a DASD dataset having DISP=NEW?
No idea, but a single reference always resolves both the volume and the unit, so a UNIT override is not meaningful?
BTW, concatenation is not the culprit; any two references to the same temporary data set in one step require that one specify VOL. I frequently find myself in this bind when I want to run an EXEC from an instream data set:
I've used the technique to run IEBUPDTE/IEBUPDTX (in a PROC) to a temporary PDS, then use that PDS as part of an ASM SYSLIB concatenation, and the updated member as the SYSIN.
Gerhard Postpischil Bradford, VT new e-mail address: gerhardp (at) charter (dot) net ---------------------------------------------------------------------- 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
