BEA Logo BEA Tuxedo Release 8.0

  BEA Home  |  Events  |  Solutions  |  Partners  |  Products  |  Services  |  Download  |  Developer Center  |  WebSUPPORT

 

   Tuxedo Documentation   |   Programming BEA Tuxedo ATMI Applications Using COBOL   |   Local Topics   |   Previous Topic   |   Next Topic   |   Contents

 


System Errors

The BEA Tuxedo system uses TP-STATUS IN TPSTATUS-REC to supply information to a process when a routine fails. All ATMI calls set TP-STATUS to a value that describes the nature of the error. When a call does not return to its caller, as in the case of TPRETURN or TPFORWAR, which are used to terminate a service routine, the only way the system can communicate success or failure is through TP-STATUS in the requester.

APPL-RETURN-CODE is used to communicate user-defined conditions only. The system sets the value of APPL-RETURN-CODE to the value of APPL-CODE IN TPSVCRET-REC during TPRETURN. The system sets APPL-RETURN-CODE, regardless of the value of APPL-RETURN-CODE IN TPSTATUS-REC during TPRETURN, unless an error is encountered by TPRETURN or a transaction timeout occurs.

The codes returned in TP-STATUS represent categories of errors, which are listed in the following table.

TP-STATUS Error Categories

Error Category

TP-STATUS Values

Abort

TPEABORT2

BEA Tuxedo system1

TPESYSTEM

Communication handle

TPELIMIT and TPEBADDESC

Conversational

TPEVENT

Duplicate operation

TPEMATCH

General communication

TPESVCFAIL, TPESVCERR, TPEBLOCK, and TPGOTSIG

Heuristic decision

TPEHAZARD2 and TPEHEURISTIC2

Invalid argument1

TPEINVAL

MIB

TPEMIB

No entry

TPENOENT

Operating system1

TPEOS

Permission

TPEPERM

Protocol1

TPEPROTO

Queueing

TPEDIAGNOSTIC

Release compatibility

TPERELEASE

Resource manager

TPERMERR

Timeout

TPETIME

Transaction

TPETRAN2

Typed record mismatch

TPEITYPE and TPEOTYPE

1

Applicable to all ATMI calls for which failure is reported by the value returned in TP-STATUS.

2

Refer to Fatal Transaction Errors for more information on this error category.

As footnote 1 shows, four categories of errors are reported by TP-STATUS and are applicable to all ATMI calls. The remaining categories are used only for specific ATMI calls.The following sections describe some error categories in detail.

 

back to top previous page next page