Guardian Procedure Errors and Messages Manual

Recovery Ensure that devices are enabled for the TMF subsystem. For example, use the command
ENABLE VOLUMES through TMFCOM.
86 (%126) BEGINTRANSACTION is disabled either by
the operator or because one or more TMF
limits have been reached.
(device type: not applicable)
Cause BEGINTRANSACTION failed due to explicit action by an operator or because one or more
audit trails have reached maxfiles, the maximum number of audit files permitted.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Contact the operator. If operator intervention caused the failure, have the operator correct
the problem.
If one or more audit trails have reached maxfiles, dump audit trails until the maximum is no longer
exceeded.
87 (%127) Waiting on a READ request and
did not get it.
(device type: 10 and 60)
Cause A subdevice that was waiting on a read request received an I/O request that was not a
read request.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Corrective action is application dependent.
88 (%130) A CONTROL READ is pending so a second
READ is not valid. (device type: 10 and 60)
Cause A two-step read (CONTROL 22) was queued at the subdevice, so a second two-step read
was invalid.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Corrective action is application dependent.
89 (%131) A remote device cannot accept text
because it has no buffer available.
(device type: 10)
Cause The remote device cannot accept text because it does not have an available buffer.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Retry the write from the application process.
90 (%132) The transaction was aborted by the system
because its parent process died, a server
using the transaction failed, or a message
to a server using the transaction was
cancelled. (device type: 3 or none)
Cause The transaction aborted because either its BEGINTRANSACTION process failed, a server
using the transaction failed, or a message to a server using the transaction was canceled.
Effect The procedure sets the error code and returns without performing the requested operation.
40 File-System Errors