Guardian Procedure Errors and Messages Manual

Recovery For more information, see the NonStop TM/MP Operations and Recovery Guide.
81 (%121) Operation is not valid for a transaction
which still has nowait I/Os outstanding
on a disk or process file.
(device type: 3 or none)
Cause The operation was invalid because the transaction had one or more outstanding nowait
I/O operations on a disk or process file. Error 81 is received by ENDTRANSACTION or REPLY.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery For more information, see the NonStop TM/MP Operations and Recovery Guide.
82 (%122) TMF not running on this system or
on the remote system.
(device type: 0, 3, or none)
Cause BEGINTRANSACTION failed for one of the following reasons:
• The Transaction Management Facility (TMF) subsystem was not running on this system.
• An I/O operation to an audited disk or a process file on a remote system was part of a TMF
transaction, but the TMF subsystem was not running on the remote system.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Ensure that the TMF subsystem is running on all systems involved in the transaction, then
retry the command.
83 (%123) Attempt to begin more concurrent
transactions than can be handled.
(device type: none)
Cause BEGINTRANSACTION failed because the process reached its maximum number of concurrent
transactions. The maximum is one transaction if the TFILE is not open; otherwise, the maximum
equals the TFILE depth.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery For more information, see the NonStop TM/MP Operations and Recovery Guide.
84 (%124) TMF has not been configured on
this system or on the remote system.
(device type: not applicable)
Cause BEGINTRANSACTION failed for one of the following reasons:
• The Transaction Management Facility (TMF) subsystem was not configured on this system.
• An I/O operation to an audited disk or a process file on a remote system was part of a TMF
transaction, but the TMF subsystem was not configured on the remote system.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Wait, then retry. Make sure the TMF subsystem is configured on all systems involved in
the transaction.
85 (%125) A device has not been started for TMF.
Cause A device has not been started for the Transaction Management Facility (TMF) subsystem.
Effect The procedure sets the error code and returns without performing the requested operation.
Error Code Descriptions 39