The following conventions must be observed for names entered in KDCDEF control statements:
The base name of the KDCFILE (MAX ...,KDCFILE=) must comply with the rules for file names of the operating system, under which the application is to run (for further information, see MAX statement in section "MAX - define UTM application parameters").
The names of LTERM partners, clients and printers, transaction codes and TAC queues etc. can be up to eight characters in length, where the following characters are permitted:
A,B,C,...,Z
0,1,...,9
#, @, $
On Unix, Linux and Windows systems, names may also contain lowercase letters (a,b,c,...,z). The names are case sensitive.
Program names specified as entry/object names in the PROGRAM statement may be up to 32 characters long. This also applies for program names in TAC PROGRAM= and EXIT PROGRAM=.
The following characters are permitted in program names:
A,B,C,...,Z
0,1,...,9
#, @, $
If other special characters are used, the program name must be enclosed in quotes, see below.
Additional special characters in names:
Program names or passwords may also include other special characters such as "_" (underscore) and "-" (hyphen) if permitted by the particular system environment.
- Names of IP subnets must start with an asterisk ("*").
Load module names on BS2000 systems (LOAD-MODULE) may also include the "." (period) and "-" (hyphen) characters.
Names that include special characters (program names, passwords, etc.) must be enclosed in quotes.
Exceptions to name length rules:
Presentation and session selectors in the ACCESS-POINT and OSI-CON statements can be up to 16 characters in length.
Program names can be up to 32 characters long.
- Processor names can be up to 64 characters long.
On BS2000 systems, load module names in BLS generation and character set names can be up to 32 characters long; the names of common memory pools (MPOOLs) can be up to 50 characters long.