TRANSFER Programming Manual

Node Designation
Naming TRANSFER Objects
4–10 069138, Update 1 to 040970 Tandem Computers Incorporated
Node Designation If a correspondent at a node references a TRANSFER name defined at that same node,
the correspondent need not enter the node designator. Specific ramifications of this
rule are as follows:
A new correspondent must be registered(defined) at the same node as the
correspondent who requests the registration. Therefore, a process can omit the
node designation from the new correspondent name in the CREATE-DEPOT
UOW. For example, LOUIS-JAMES @ TS can register BAKER-JON @ TS simply as
BAKER-JON.
A correspondent must initiate a session at the node where that correspondent
name is registered. Therefore, a process can omit the node designation from the
correspondent name in any request to establish a session.
During package delivery, TRANSFER processes at each recipient node resolve
names and expand distribution lists that were defined at that node. Therefore, a
user process adding a name to a distribution list can omit the node designation if
the name is defined at the same node as the distribution list. Note, however, that
the user process must include the node designation if the name is defined at a
different node.
Name-Length
Restriction
The TRANSFER delivery system converts the external format of object names into an
internal format to resolve the names and manage the objects that they represent. The
internal format includes the name of the node where the object is defined, the name of
the TRANSFER name directory that contains the definition, and all other simple
names needed to uniquely identify the object.
For example, you use the following format to identify a folder:
correspondent-name . folder-name trigger node
The folder is identified internally in the following format, where T.CORR indicates the
name directory:
%\node . $T.CORR . correspondent-name . folder-name
The internally expanded name must not exceed 79 characters. To avoid having a
simple name rejected because of a name-length conflict, your application and its users
should avoid defining excessively long names.
TRANSFER Name
Management
The TRANSFER delivery system stores names in a directory file. When the name is
used, the TRANSFER delivery system resolves (expands) the name if necessary, then
checks to make sure the name references an existing object.