Cause
An error occurred while attempting to convert character data from
one code page to another.
The most common reason for this error is that the conversion
table required to perform the conversion is not yet present on
the personal computer. Under normal circumstances, when a
conversion table is missing, the table is automatically retrieved
from the default server and saved on the
personal computer. When a default server is not configured or not
available for some reason, the necessary code page conversion
table cannot be retrieved.
Another possible reason this error might occur is that there is
no conversion table defined for this pair of code pages.
Conversion tables are usually not defined for incompatible pairs
of code pages. The code pages may be incompatible because the
characters represented by one code page cannot be represented by
the other code page.
Recovery
Configure a default server, verify its connection, and signon to
the server when prompted. See Work with the
default server for information about configuring a default
server. The Central Client server must be started in order to
retrieve conversion tables. See Check Host Socket
Server Status for information on how to check the status of
the various servers.
Cause
Conversion table is in a format that is not recognized.
Recovery
Do one of the following:
* Delete the not valid conversion table so that a new table will
be retrieved from the server.
* Obtain a copy of the conversion table from your server
administrator.
* Review the message log for other causes of this error.
* Contact your service representative.
Cause
An attempt was made to use a conversion table, but the table was
not found.
Recovery
Do one of the following:
* Obtain a copy of the conversion table from your server
administrator.
* Review the message log for other causes of this error.
* Contact your service representative.
Cause
A code page conversion table was being retrieved from the server
when an error occurred.
Recovery
Do one of the following:
* Review the message log for other causes of this error.
* Obtain a copy of the conversion table from your server
administrator.
* Contact your service representative.
Cause
Communications returned a primary return code and secondary error
code.
A primary return code of 0005 indicates a conversion map
retrieval error.
Secondary error codes:
* 0001 - Invalid request
* 0003 - Error calling user exit program
* 0004 - Request rejected by exit program
* 0036 - Retrieve conversion map error
Recovery
Do one of the following:
* Review the message log for other causes of this error.
* Contact your service representative.
Cause
Server returned a primary return code and secondary error code.
Recovery
Do one of the following:
* Review the message log for other causes of this error.
* Obtain a copy of the conversion table from your server
administrator.
* Contact your service representative.
Cause
While converting character data from one code page to another,
some untranslatable characters were encountered.
Recovery
Verify that the data being converted is correct and that it does
not contain any not valid characters.
Cause
A required conversion table was not found on the PC. An attempt
was made to retrieve the table from the default server, but no
default server is configured.
Recovery
A default server is required for retrieving conversion tables.
Configure iSeries Access
and retry the operation. See iSeries Access Default Server and Work with the
default server for information about configuring a default
server.
Cause
Message file not in a recognized format. It has been corrupted.
Recovery
Do one or more of the following:
* Update iSeries Access.
* Copy the message file from the server.
* Obtain a copy of the message file from your server
administrator.
* Contact your service representative.
Cause
Message file could not be found.
Recovery
Do one of the following:
* Update iSeries Access.
* Copy the message file from the server.
* Obtain a copy of the message file from your server
administrator.
Cause
The message file is missing a message. The message file could be
corrupted, or a newer version of the message file is needed.
Recovery
Do one or more of the following:
* Update iSeries Access.
* Obtain a copy of the message file from your server
administrator.
* Contact your service representative.