TRANSFER Programming Manual

Wild-Card Names and Patterns
Naming TRANSFER Objects
4–2 069138, Update 1 to 040970 Tandem Computers Incorporated
The TRANSFER delivery system upshifts characters in names according to the
following rules:
All lowercase alphabetic characters are treated the same as, and are upshifted to,
their equivalent uppercase characters. For example, lowercase a becomes
uppercase A.
All digits, special characters, and the German "sharp s" (ß) and lowercase
"u-umlaut" (ü) remain as entered.
Correspondents supply required names within 80-byte or 120-byte fields. These fields
can contain leading blanks, but no character in a name can occupy the last byte. The
last byte must contain a null (binary zero) character or a blank. A process can
terminate a name at any point in the field by entering a null character after the last
character in the name, in which case the TRANSFER delivery system pads the trailing
portion of the field with blanks.
The TRANSFER delivery system returns a name to a process in a response UOW. The
name is returned in an 80-byte or 120-byte field that is padded on the right with
blanks.
Examples of TRANSFER simple names are:
BROWN
BROWN_JOE
BROWN-JOE
MYPROC-2
123-5
Note You can use the underscore or hyphen character in simple names, but the two are not treated as
equivalent. The underscore might be preferable when names contain hyphens. You should consistently
use whichever character you select.
Wild-Card Names
and Patterns
In any context except the initial definition of a name or the deletion of members of a
distribution list or a recipient list, you can use an asterisk in a simple name to indicate
that any single character, any string of characters, or no characters can appear. The
simple name can be a correspondent name, distribution list name, folder name, or item
name, as long as the abbreviated name identifies only one correspondent, distribution
list, folder, or item. This capability is known as using wild-card characters in
TRANSFER names. The asterisk serves as the wild-card character in all cases,
regardless of the character map in effect.
For correspondent, distribution list, or folder names, the asterisk can appear anywhere
within the name. For example, *-Robert identifies a correspondent whose first name is
Robert. For item names, however, the asterisk can appear only as the last character.
For example, MYTRIP.ROUTE* is a legal entry, but MYTRIP.*ROUTE is not.
If you place an asterisk at the end of a name, the process needs to supply only enough
characters to uniquely identify the name. If Benson-Jill and Benson-Jonathan are both