Examples of numeric and symbolic subscripts
The following table illustrates how numeric and symbolic subscripts are processed. The table is based on the following initialization statements for system initiators.
To avoid confusion, it is recommended that when both numeric and symbolic subscripts are allowed, symbolic names (specified using the NAME= parameter) either include at least one alphabetic character or match the numeric value exactly (for example, INIT(1) NAME=1). This example illustrates the confusion that can occur when this is not done.
Based on these initiator definitions, JES2 interprets the initiator
number and its name as follows:
Example Initiator Statements | |
---|---|
|
|
Command Example | JES2 Processing Interpretation |
|
Initiator number 1 |
|
Initiator with name "1" exists. |
|
Initiator with name "5" does not exist, use init number 5. |
|
Initiator with name "1" |
|
Initiator in numeric range of 3-4. |
|
Initiator in numeric range of 3-4. |
|
Initiator with names in EBCDIC range '3' to '4' |
|
4b is non-numeric, therefore, initiator in EBCDIC range '3'-'4b' |
|
All initiators between EBCDIC '1' to '2' in HEX that is 'F1404040' to 'F2404040' |
|
All initiators between EBCDIC '1' to '10' in HEX that is 'F1404040' to 'F1F04040' |
|
Numeric range (4 is numeric and * represents the maximum numeric value) |
|
Ascending EBCDIC range '4A' to '*', in HEX that is 'F4C14040' to 'FFFFFFFF' |
Note: There are exceptions
to the processing results above. When using JES2 Commands for JOB,
STC, TSU, JOBQ, a numeric subscript (JOB(nn)) is always treated as
numeric unless enclosed in quotation marks.
Also, job names consisting of all numerics are not valid but may
occur in error scenarios, such as when a job is incorrectly submitted
or received from NJE.
|