Introducing NetMaster REXX › Keyword Instructions › PARSE

PARSE

NetMaster REXX supports the PARSE instruction fully with the following differences:

• PARSE EXTERNAL (a TSO/E REXX extension) is not supported. You can emulate PARSE EXTERNAL with PARSE PULL when the stack is empty.
• PARSE PULL reads from the stack (per TSO/E REXX). If the stack is empty, a message is sent to the execution environment (for example, the terminal) requesting input. The GO command can be used to supply input to the waiting procedure. (This implementation is similar to the implementation of PARSE PULL in Tivoli NetView.)
• PARSE NUMERIC is not supported. The three values used as input to the parsing template are the current settings of NUMERIC DIGITS, NUMERIC FUZZ, and NUMERIC FORM. The first two (DIGITS and FUZZ) can be obtained through built-in functions. The last is always SCIENTIFIC in NetMaster REXX.
• PARSE SOURCE provides, as input to the parsing template, a string in the following format:

  GREXX COMMAND MYREXX COMMANDS ? MYREXX NM NM NM
  

  TSO/E REXX provides a string of the format:

  TSO COMMAND MYREXX SYS00271 SYSPROG.SOURCE.REXX ? TSO ISPF ?
  

  The string provided by PARSE SOURCE consists of the following tokens:

  • The string GREXX (IBM provides TSO)
  • The string COMMAND, FUNCTION, SUBROUTINE, or SERVER indicating how the procedure was invoked (Currently, NetMaster REXX always uses SUBROUTINE for a called procedure. It does not distinguish function calls.)
  • The name of the procedure in uppercase
  • The library ddname (typically COMMANDS)
  • A question mark (in TSO/E REXX, possibly the data set name that the procedure was loaded from)
  • The procedure name again
  • Initial (default) command environment (typically NM)
  • Address space name (typically NM)
  • PARSETOK (typically NM)
• PARSE VERSION provides, as input to the parsing template, a string in the following format:

  REXX/CA 3.92 18 Oct 1995
  

  TSO/E REXX provides a string in the format:

  REXX370 3.48 01 May 1992