TRANSFER Programming Manual

Messages Processed within Standard Sessions
National Language and Character Set Support
7–6 40970 Tandem Computers Incorporated
Note When an IPC that contains a START-SESSION-B40 request has a B20 or previous version in the
VERSION-CODE field of the IPC header, the TRANSFER delivery system always assigns the US ASCII
map as the map for that session. In fact, any request with a B20 or previous VERSION-CODE forces the
TRANSFER delivery system to use the US ASCII map for that request (even if the request occurs within
a session that has some other character map associated with it). In other words, such a version code
makes any version of the TRANSFER delivery system act like a B20 version.
If you use the START-SESSION UOW (rather than the START-SESSION-B40 UOW) to
initiate a standard session, you cannot specify an alternate character map for the
session. Instead, the following restriction, which parallels that for specifying an
alternate language, applies:
If the START-SESSION request occurs in an IPC with a Release B20 or earlier
VERSION-CODE, then the TRANSFER delivery system uses US ASCII.
If the START-SESSION request occurs in an IPC with a Release B40 or later
VERSION-CODE, then the TRANSFER delivery system uses the default map
defined for your node in the SYSTEM-LANG-CMAP-ID configuration entity.
For UOWs issued during a session and within IPCs with a B40 or later VERSION-
CODE:
The TRANSFER delivery system expects names of TRANSFER objects to be
submitted in the native codes defined by the character map for the current session.
This rule includes the names of correspondents, folders, distribution lists, and
instances of named items in folders. Before storing or comparing the names, the
TRANSFER delivery system upshifts them all (with the exception of recipient
suffixes), so that lowercase names are treated the same as their uppercase
equivalents.
The TRANSFER delivery system returns all names in the uppercase native code
defined by the character map associated with the current session.
The TRANSFER delivery system expects all digits to be supplied with the native
codes defined by the character map for the current session, and emits all digits in
these native codes. (The most common examples of this rule are digits that
represent days, months, and years in all dates.)
The TRANSFER delivery system expects that all alphanumeric TRANSFER
keywords are represented by the ASCII encodings for the English alphabetic
characters and Arabic digits. Within your application,you must map appropriate
native codes to these fixed keywords, which include:
Contents of BOOLEAN fields: Y, N
Relative time units: D, H, M (DAY, HOUR, and MINUTE)
Folder-ordering specifiers in the CREATE-FOLDER-B10 and
ALTER-FOLDER-DESCR UOWs: T, C, E, A (TIME-SAVED, CREATOR-
NAME, EARLIEST-DELIV-DATE, and APPLIC-DEFINED)