Rules: Observe the following rules for LU name
specification:
- The first character must be in the range A through Z, @, #, or $. In addition, remaining characters can also be numeric (any single digit 0 through 9). Unprintable characters are not allowed. If a name that is not valid is found, an error message is issued and the statement is ignored.
- LUs can be defined as a range. Use the following syntax to specify
a range of LUs:
>>-LowerRange..UpperRange--+-------------+---------------------><
'-..rangerule-'
- No spaces are allowed within a range definition.
- UpperRange must be greater than the LowerRange.
- The lengths of LowerRange or UpperRange, and rangerule must be the same and each must be less than or equal to eight characters.
- All LUs in the range must be valid and defined to VTAM® for a successful session.
- The number of LU names in one range is limited to 4 294 967 295. The total number of LU names in the group is also limited to 4 294 967 295. Storage is not used until the LU name is assigned to the connection.
- The rangerule represents the variant
used for wildcarding. For example:
where:TCP000A0..TCP9F$ZZ..FFFNX?AB- F
- The position is fixed and does not change.
- A
- Alphabetic range.
- N
- Numeric range.
- B
- Alphanumeric range.
- X
- Hexadecimal range.
- ?
- Alphanumeric including national characters @, #, and $.
If an incorrect range definition is parsed, it is ignored and a debug warning message is issued.
Result: The range specification AB100..CB299..AFNNN defines AB100-AB999 (900), BB000-BB999 (1000) and CB000-CB299 (300) (2200 names). If a specification of AB100-AB299, BB100-BB299 and CB100-CB299 (600 names) is desired, then two range specifications are required: AB100..CB199..AFFNN AB200..CB299..AFFNN.
See z/OS Communications Server: IP Configuration Guide for LU range usage examples.
- If the range rule is omitted, Telnet assumes
the following style, where the LowerRange and UpperRange values must
be all numeric or all alphabetic:
LuBase+LowerRange..LuBase+UpperRange