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

 


No Entry Errors

No entry errors result from a lack of entries in the system tables or the data structure used to identify record types. The meaning of the no entry type error, TPENOENT, depends on the call that is returning it. The following table lists the calls that return this error and describes various causes of error.

No Entry Errors

Call

Cause

TPINITIALIZE

The calling process cannot join the application because there is no space left in the bulletin board to make an entry for it. Check with the system administrator.

TPCALL
TPACALL

The calling process references a service called SERVICE-NAME IN TPSVCDEF-REC that is not known to the system since there is no entry for it in the bulletin board. On an application level, ensure that you have referenced the service correctly; otherwise, check with the system administrator.

TPCONNECT

The system cannot connect to the specified name because the service named does not exist or it is not a conversational service.

TPGPRIO

The calling process seeks a request priority when no request has been made. This is an application-level error.

TPUNADVERTISE

The system cannot unadvertise SERVICE-NAME IN TPSVCDEF-REC because the name is not currently advertised by the calling process.

 

back to top previous page next page