TRANSFER Programming Manual

Network Considerations
Naming TRANSFER Objects
069138, Update 1 to 040970 Tandem Computers Incorporated 4–13
Once a name is resolved into the identification of an object, the TRANSFER delivery
system validates the fully qualified name as follows:
1. Checks the TRANSFER name directory to verify that the name is registered
2. Checks to make sure that the name designates the correct object type (such as
correspondent or distribution list), as follows:
a. The TRANSFER delivery system first determines whether the name is that of
an object belonging to the correspondent represented by the requesting
process.
b. If not, the TRANSFER delivery system checks to verify that there is a
correspondent with that name.
You might find it difficult to tell at a glance whether an object name is a correspondent
name, folder name, or distribution list name. The TRANSFER delivery system,
however, can readily identify the object type because names are always associated
with particular types in the TRANSFER name directory.
Validation Example Consider a request on behalf of a correspondent named SIMMS-JASON in which the
object name MANAGER appears. The object name MANAGER is resolved as follows:
1. Is there an object named MANAGER that belongs to correspondent SIMMS-
JASON? MANAGER could be the name of a folder or a distribution list.
2. If not, is there a correspondent named MANAGER at this node?
3. If not, the object named MANAGER does not exist and is an illegal reference.
Network Considerations The following special considerations apply when you use the TRANSFER delivery
system to deliver packages over a multinode network:
1. Be sure that TMF is configured at all nodes in the network where the TRANSFER
delivery system is running.
2. A misspelling of network node designators within recipient names might not
cause immediate rejection of a package. When your application specifies a node in
a recipient name and remote name resolution is deferred, the TRANSFER delivery
system assumes that the node exists, places the package in the network queue, and
waits for availability of the node. Although the TRANSFER delivery system
returns an appropriate warning in the case of a nonexistent node, the package is
not withdrawn from sending until it is explicitly cancelled or the delivery time
window expires.
4. If remote name resolution is not deferred, specifying an incorrect node name
immediately results in an error.
5. If you defer remote name resolution when submitting a package, the package can
be reproduced at the receiving node but with invalid recipients. When the
TRANSFER delivery system at that node detects such a recipient, it returns an
error to the sending depot.