Interstage Shunsaku Data Manager Application Development Guide - Microsoft(R) Windows(R) 2000/ Microsoft(R) Windows Server(TM) 2003 - - UNIX -

M.4 Error Codes Output

This section explains the error codes that are output when Java API functions for data searches and updates are used.

• Error codes can be obtained by using the getErrCode() method of the ShunException class.
• The getMessage() method of the ShunException class can be used to obtain error messages in the format shown in the following table (errCode = error code).

[Table M-1 Error Codes]

Error code	Meaning	User response
-1	An error occurred when an attempt was made to connect to the host.	Check the host name and port number of the target director server and rerun the command.
-10	The service is not ready to receive a request.	Wait a few moments and then rerun the command.
-11	The maximum number of simultaneous search requests has been exceeded.	Wait a few moments and then rerun the command.
-12	A timeout occurred while the system was waiting for a response from the director.	Wait a few moments and then rerun the command.
-20	A parameter error occurred.	Check all parameters and then rerun the command.
-21	A search expression syntax error occurred.	Check the search expression and then rerun the command.
-22	A return expression syntax error occurred.	Check the return expression and then rerun the command.
-23	A search expression size error occurred.	Check the length of the input parameter search expression and then rerun the command.
-24	A return expression size error occurred.	Check the length of the input parameter return expression and then rerun the command.
-30	The response data storage area was insufficient.	Increase the response data storage area and then rerun the command.
-100	An API internal error occurred.	Change the search condition so that the number of reply records is not zero, then call the data acquisition method.
-101	An API internal error occurred.	Call a data acquisition method that conforms to the search method.
-102	An API internal error occurred.	Change the search condition so that the number of reply records is not zero, then call the record identifier acquisition method.
-103	An API internal error occurred.	Call a record identifier acquisition method that conforms to the search method.
-104	An API internal error occurred.	Call the search method and then call the hit count acquisition method.
-105	An API internal error occurred.	Create an instance normally (by executing the create method), then call the search method.
-106	An API internal error occurred.	Call a reply record count acquisition method that conforms to the search method.
-107	An API internal error occurred.	Change the return expression to a value other than NULL, then call the data acquisition method.
-201	The pathname of the Shunsaku command directory has not been specified.	Specify the pathname of the Shunsaku command directory in the system properties, and rerun the command.
-202	The director identifier has not been specified.	Set the director identifier, and rerun the command.
-203	The pathname of the XML document to be added has not been specified.	Set the pathname of the XML document to be added, and rerun the command.
-204	Addition of XML data with the shundimport command failed.	Confirm that the content of the XML document to be added with the shundimport command is correct, and then rerun the command. Check the state of the director server, and then rerun the command.
-206	The work file has not been specified.	Specify the pathname of the work file, and rerun the command.
-207	Deletion of XML data with the shundimport command failed.	Specify the full pathname for the recordIDfileName argument (the path to work files). Check the state of the director server and then rerun the command.
-208	The shundimport command failed to start.	Confirm that the pathname of the shundimport command specified in the system properties is correct, and then rerun the command. Execute the command with privileged user authority.
-209	The shundimport command was suspended.	Follow the procedure described in Handling when Server Fails during Command Execution in the Troubleshooting, and then rerun the command.
-210	The work file could not be opened.	Confirm that the pathname of the work file is correct, and then rerun the command.
-211	The work file could not be written to.	Check the status of the disk, and then rerun the command.

Java exceptions also have to be caught by an application. The following table shows the exception that may occur.

Exception	Applicable method	Meaning	Action
OutOfMemoryError	executeSearch2 executeSearch3 executeDelete	Memory error	Rerun the command after reducing the number of reply requests. Rerun the command after reducing the number of return items.