LISTDSI is a REXX function, It is not a host command; ADDRESS has no effect on LISTDSI.
Use CALL LISTDSI DSNVAR ... or IF LISTDSIO\(DSNVAR) = 0 THEN ... , e.g, in any mixed case where you have stored the dataset name in DSNVAR or the variable of your choice. (All REXX functions can also be invoked as subroutines.) As with any argument in REXX, it can be a constant, variable or expression that evaluates to something that is valid for the specific function. ISPF is not required. TSO probably is. OREXXMan Q: What do you call the residence of the ungulate with the largest antlers? A: A moose pad. :-D Would you rather pass data in move mode (*nix piping) or locate mode (Pipes) or via disk (JCL)? Why do you think you rarely see *nix commands with more than a dozen filters, while Pipelines specifications are commonly over 100s of stages, and 1000s of stages are not uncommon. REXX is the new C. On Mon, Feb 20, 2023 at 2:28 PM Paul Gilmartin < [email protected]> wrote: > On Mon, 20 Feb 2023 14:53:49 -0500, Steve Thompson wrote: > > ... > > PARSE ARG UPPER COMMAND_LINE EXCESS > ??? > PARSE UPPER ARG COMMAND_LINE EXCESS > > But that limits your COMMAND_LINE to only one word; perhaps not what you > want. > > Example from <https://www.ibm.com/docs/en/zos/2.5.0?topic=tef-listdsi>: > argument_string = "REXXEXEC VOLUME(PACK1) NODIRECTORY NORECALL" > x = LISTDSI(argument_string) > > -- > gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
