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." All the other methods (LINK, etc.) of invoking BPXCOPY allow specifying alternative ddnames, but the TSO/E CALL command with the asis option does not belong in the list. Nor does it belong in the preceding paragraphs about alternative ddnames for SYSUT1 and SYSUT2. I suspect the list was mistakenly thought to be the same as the list earlier on the same page, where it says "You can invoke BPXCOPY in several ways:" followed by exactly the same list of methods. That part is not referring to alternative ddnames, so the TSO/E CALL command is correctly in the list. Bill 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? > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
