On Sat, 16 Jul 2022 06:39:31 -0500, Bill Godfrey wrote: >In the part about BPXCOPY, the UNIX System Services Command Reference manual >is incorrect. > >Restoring the part that you showed with ellipses, the statement is: "If >BPXCOPY is invoked from LINK, XCTL, ATTACH, a TSO/E CALL command with the asis >option, or by a CALL after a LOAD, you can specify an alternative ddname." > I elided the part I trusted in order to emphasize what I doubted. I've used the alternate DDDNAME list with ADDRESS SYSCALL ATTCHMVS to override SYSUT1.
I'm least familiar with CLIST, but ASIS seems particularly irrelevant. It may pertain to UNIX pathnames. I'll submit an RCF. A few hours earlier, I had submitted an RCF questioning whether it's possible to override SYSTSPRT, even with LINK, etc. I'll watch for a response, >On Fri, 15 Jul 2022 16:56:02 -0500, Paul Gilmartin wrote: > >>In the z/OS UNIXI Ref. for BPXCOPY I read: >>• The message output ddname is associated with an MVS data set. >> The default ddname is SYSTSPRT, ... If BPXCOPY is invoked >> from ..., a TSO/E CALL command with the asis option, ..., you can >> specify an alternative ddname. >> >>In the TSO/E Commands Ref. for CALL, I read: >>CALL command ... >>parameter_string ... >>Some utilities accept multiple entry parameter lists; for example, to pass a >>list of alternate ddnames, TSO/E commands require a special multiple entry >>parameter list known as a command processor parameter list (CPPL). Neither of >>these options are supported by the CALL command, ... >> >>Is there a contradiction here? -- Thanks, gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
