Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Syntax requirements for command and subcommand names z/OS TSO/E Programming Services SA32-0973-00 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
If you write your own Command Processor, and you
intend to use the Command Scan Service Routine to check
for a valid subcommand name, the name you choose must meet the following
syntax requirements:
Include one or more numerals in the name to differentiate it from the IBM-supplied command names, which do not include numerals. The Command Scan Service Routine accepts double-byte character set (DBCS) strings in addition to EBCDIC character strings. The shift-out character (X'0E') indicates a change from EBCDIC to DBCS; the shift-in character (X'0F') indicates the reverse. Each double-byte character requires a double-byte representation so that valid DBCS strings contain an even number of bytes. With the exception of blank, which is X'4040', each byte has a value from X'41' to X'FE'. Double-byte characters can appear in comments and certain types of strings of user data. For a discussion of the types of strings that can contain double-byte characters, see Verifying command and subcommand operands with parse. The following table shows the various character types recognized by the Command Scan Service Routine. Unless otherwise indicated, alphanumeric characters are (1) alphabetic (A-Z), (2) numeric (0-9), and (3) the special characters $, #, @.
|
Copyright IBM Corporation 1990, 2014
|