ASAP 2.8 Messages Manual

HP NonStop ASAP Messages Manual—429917-004
3-11
1812: ZASP-EVT-API-BEGINTRANS-ERROR
fname
is the name of the file that ASAPX was attempting to update.
begintrans
is the error returned from BEGINTRANSACTION.
Cause. ASAPX could not obtain a transaction ID from TMF in an attempted operation
against file fname. To determine the cause of this problem, see the description of
BEGINTRANSACTION procedure error numbers in the Guardian Procedure Errors
and Messages Manual.
Effect. ASAPX could not access the Domain table. This results in domain registration
and removal failures.
Recovery. Correct the TMF error and retry the operation.
Tokens in the Event Buffer.
ZASP-TKN-ASAP-ERRORNUM is 1812.
ZASP-TKN-ASAPX-COMPONENT is the name of the ASAPX component that
reported the event.
ZASP-TKN-ASAPX-FNAME contains the name of the file.
ZASP-TKN-ASAPX-ERROR contains the BEGINTRANSACTION error number.
ZEMS-TKN-TEXT contains an abbreviated version of the error text.
1814: ZASP-EVT-API-ILLEGAL-REQUEST
rbuf[0]
is the first word of the illegal buffer received.
Cause. An ASAPX process received an illegal request on $RECEIVE. Another
process inadvertently wrote to an ASAPX process.
Effect. None. ASAPX ignores the illegal request and continues processing.
Recovery. Make sure you have the correct version of all ASAPX object modules.
Tokens in the Event Buffer.
ZASP-TKN-ASAP-ERRORNUM is 1814.
Begintransaction error: fname, Er: begintrans
Illegal request on $receive: rbuf[0]