Previous     Contents     Index     DocHome     Next     
iPlanet Application Server Enterprise Connector of CICS Developer's Guide



Appendix A   Error Messages and Codes


The developer writes servlets that use connectors to connect with the EIS. Error messages are generated to assist the developer in debugging these processes. This appendix contains a list of identified errors and the error handling code that is used to catch the error.

The following topics are described:



Description of Errors

Table A-1 lists the error handling codes, msgid, and the corresponding messages.

Table A-1    Error Messages 

Error Message Code msgid

Error Message

1  

Communication Failure. Error: {error text} (rc : {return code}), Applind : {indication}.  

2  

Failed to connect to Relay or SRVXLINK: RC:{return code}, RelayRC:{relay return code}, StubRC:{stub return code}, StubReason:{stub error code}.  

3  

{Input\Output} data is too long, maximal length {length}, actual length {length}.  

4  

Illegal user type value {type code} for property name {name}.  

5  

Internal error. Failed to get {object type} {object name}.  

6  

Internal error. Object {object name} is NULL.  

7  

Type not supported, in Data Object {object name}, field {field name}, type {field type}.  

8  

Not used.  

9  

Not used.  

10  

Not used.  

11  

Not used.  

12  

Not used.  

13  

Not used.  

14  

Not used.  

15  

Not used.  

16  

Failed to {get\set} user defined type.  

17  

Failed to initialize marshalling parameters, error code: {return code}.  

18  

Array {name} has {number} element,{text} {valid value} elements.  

19  

Illegal value={value} of field {field name}.  

20  

Field {field name) has illegal Value {value} ,contain more digits than {max digits}.  

21  

Field {field name} has illegal Value {value} ,contain illegal character {char}.  

22  

Field {field name} has invalid length,Max Len {length}, is smaller than {property name} {value}.  



Error Handling Code



The error handling code is an example of how to handle an exception raised by the connector.

When there is an error in the process the CICS connector throws a BspException object. The exception object contains a data object. The data object contains the numeric code, msgid, as listed in Table A-1.

An example of error handling code is shown in Code Example A-1.

Code Example A-1    Error Handling Code Sample

try
{

   ... some code in the servlet

}

catch (BspException e)

{

IBSPDataObjectStructure info = null;

errorMessage += " Error : " + e.getMessage() ;

info=e.getInfo();

if (info != null && info.attrExists("msgid") )

{

errorMessage += " Error code : " + info.getAttrInt("msgid") ;

}

}



Previous     Contents     Index     DocHome     Next     
Copyright © 2000 Sun Microsystems, Inc. Some preexisting portions Copyright © 2000 Netscape Communications Corp. All rights reserved.

Last Updated November 13, 2000