EasyManua.ls Logo

HP Guardian Errors - Page 38

HP Guardian Errors
283 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Cause This error can occur for two reasons:
A process called READUPDATE to read a message from $RECEIVE, but the number of
outstanding messages read but not replied to equals the receive depth.
A process called ACTIVATERECEIVETRANSID or REPLY either with an invalid message tag or
when no outstanding message exists.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Corrective action is application dependent.
75 (%113) Requesting process has no current
process transaction identifier.
(device type: 3)
Cause The requesting process tried to access an audited file but had no current transaction identifier,
or a process called ACTIVATERECEIVETRANSID, ENDTRANSACTION, or ABORTTRANSACTION
but the message specified by the message-tag has no associated transaction identifier.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery See the NonStop TM/MP Operations and Recovery Guide
76 (%114) Transaction is in the process
of ending. (device type: 3 or none)
Cause The transaction was ending so it could not be aborted or resumed.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery See the NonStop TM/MP Operations and Recovery Guide.
78 (%116) Transaction identifier is invalid or
obsolete. (device type: 3 or none)
Cause The transaction identifier was invalid or obsolete, or it is no longer available because the
Transaction Management Facility (TMF) subsystem removed it from the system.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery See the NonStop TM/MP Operations and Recovery Guide
79 (%117) A transaction attempted to update or delete
a record which it has not previously
locked. (device type: 3)
Cause The transaction failed to lock a record before attempting to change or delete it.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery See the NonStop TM/MP Operations and Recovery Guide
80 (%120) Invalid operation on audited file
or non-audited disk volume.
(device type: 3)
Cause An invalid operation was attempted on an audited file or a nonaudited disk volume.
Effect The procedure sets the error code and returns without performing the requested operation.
38 File-System Errors

Table of Contents

Related product manuals