TRANSFER Programming Manual

Additional Considerations
Developing TRANSFER Applications
40970 Tandem Computers Incorporated 8–5
When the sender receives notification for every recipient that the package was
received, that it could not be delivered, or that it expired before it was received
When every recipient has taken some action and explicitly replied to the sender
When the sender has taken some specific action based on the reply
When replies to senders are part of a transaction, define exactly what the reply means
to the sender and how that reply is linked to the original package.
Figure 8-1 shows an example illustrating deliveries and replies that constitute
complete transactions.
Figure 8-1. Sample Transactions
Transaction 1
1. Accept and record sales order on \SALES.
2. Send order to Inventory Control on \WHSE.
3. Reserve merchandise by requesting pick ticket.
4. Reply to \SALES.
5. On \SALES, record ticket number with order.
Transaction 2
1. On \WHSE, request pick ticket.
2. Generate pick ticket on May 17.
Transaction 3
1. On \WHSE, check inventory.
2. Send purchase request to Purchasing.
3. On \CORP, issue purchase order to vendor.
4. On \CORP, reply to Inventory Control.
5. On \WHSE, file purchase request with purchase order number.
Transaction 4
1. On \WHSE, receive invoice with shipment.
2. Send invoice to Accounts Payable.
3. On \CORP, issue check to vendor.
Additional Considerations Consider the level of data protection and integrity that your application must provide.
This might involve the use of fault-tolerant features, TMF, or both.
Try to anticipate any operational and administrative requirements that your
application imposes upon others at your site.