RSC/MP 7.2 Programming Manual

Application Development
HP NonStop Remote Server Call (RSC/MP) Programming Manual—522360-004
6-8
Generating Transactions Automatically (Implicitly)
Generating Transactions Automatically (Implicitly)
Automatic transactions can have these advantages:
•
Reduction of the message traffic between the TDP and the workstation
•
Reduction of CPU use
•
Improvement of response time
Instead of issuing RscBeginTransaction and RscEndTransaction function calls, you set
the workstation options TMF_OPTION, SUCCESS_HI, and SUCCESS_LO to the
desired values and then issue RscWriteRead calls to alter the database. RSC/MP uses
internal functions to start and end the transaction, which is also referred to as
“piggybacking” TMF transactions on RscWriteRead calls.
There are two types of automatic transactions: single-step and multi-step. Single-step
transactions contain a single RscWriteRead call. Multi-step transactions contain more
than one RscWrite and/or RscWriteRead call.
TMF Workstation Options
For automatic transactions, an RSC/MP application calls the RscSetOption function to
set the values of these TMF options (the defaults for all three are zero):
•
SUCCESS_HI specifies the highest server reply code (see Server Reply Codes in
TMF on page 6-10) that signifies successful completion of a transaction.
•
SUCCESS_LO specifies the lowest server reply code (see Server Reply Codes in
TMF on page 6-10) that signifies successful completion of a transaction.
•
TMF_OPTION indicates which TMF functions you want performed in conjunction
with one or more successful RscWriteRead function calls.
The TMF options defined in the RSC.H file are listed in Table 6-1.