Charles Mills wrote: > Apparently that's not how CALL works, at least not based on my > experimentation. Could I have fat-fingered it?
Sine the earliest days of TSO, CALL has used the dataset as a TASKLIB when it attaches the user program, and this effect is propagated down to lower task levels. What has always been missing from TSO is a similar program to invoke a TSO Command Processor with a TASKLIB. TSO TEST, although syntactically similar to CALL, has traditionally not used TASKLIB on its ATTACH, so there have been various versions of "CALLCP" commands over the years. Having a different argument format for TSO commands is one of those longstanding IBM design errors - not as bad as making blanks silently significant in JCL, but still... Tony H. ---------------------------------------------------------------------- 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
