RSC/MP 7.2 Programming Manual

Application Development
HP NonStop Remote Server Call (RSC/MP) Programming Manual—522360-004
6-17
Using a Backup TDP
2. Attempt to reconnect to the TDP. Reconnection attempts should occur at
reasonable intervals for a reasonable period of time; for example, the application
should make a connection attempt every 5 seconds for 60 seconds, or longer. If
the connection cannot be established, notify the user that the application has failed
and that operator intervention is required.
3. After the connection has been re-established, begin a new session.
4. If the connection failure occurred on an RscEndTransaction request, analyze the
database to determine if the transaction was really committed. If it was not, the
transaction was in progress at the time of the failure and was aborted.
5. If a transaction was in progress at the time of the failure, resubmit the entire
transaction.
6. Inform the user that the connection-failure recovery was completed.
See Section 7, Message Handling, for more information about handling TDP failures
and recovering from data communications failures.
Using a Backup TDP
The TDP process checkpoints configuration information; therefore, the backup TDP
process has the same configuration as the primary process. The backup process does
not save transactions or I/Os, it only saves the configuration. After a TDP failure,
applications must re-establish the connection to the workstation and perform any
outstanding transactions in the TDP again. During the recovery process the TDP is
inaccessible to applications and the RSCCOM interface.
The TDP performs these tasks during the recovery process:
•
Reopens the log file (if one was open at the time of the failure)
•
Re-establishes the operational state of all objects that were configured at the time
of primary process failure
•
If system resources that support these objects are not immediately available, the
object stops or enters automatic restart mode if the AUTORESTART attribute is
configured
•
Logs the completion of recovery
•
Allows RSCCOM access
•
Starts another backup process in the primary CPU when and if it is available
•
Deletes any Pathway terminals in the associated Pathway’s TCP that were
supporting IDS sessions at the time of the primary process failure.