Message Class 1003 - Conversion

The error indicated by number has occurred within an internal conversion routine.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

The length of the receive buffer given by the receiver is too small. Depending on the version of EntireX Broker, EntireX and Natural components in use:

• The situation is handled inside the EntireX Broker, that is, conversion is called a second time by the EntireX Broker with a buffer that is large enough.

• The EntireX Broker passes this error as error 00200377 to the client or server.

The error can be ignored. See error 00200377 for more information if the EntireX Broker passes 00200377 to the client or server.

An error has occurred in the interface between EntireX Broker kernel and the conversion routine.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An error has occurred in the interface between EntireX Broker kernel and the conversion routine.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An error has occurred in the interface between EntireX Broker kernel and the conversion routine.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An error has occurred in the interface between EntireX Broker kernel and the conversion routine.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An internal error has occurred inside the conversion routine.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

Error number has occurred during ECS initialization.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

Error number has occurred during ECS conversion.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

The length of the data (of numeric and binary data types such as Nm.n, Pm.n, NUm.n, PUm.n, L, B, F4, F8, I1, I2, I4, D, T ) contained in an IDL parameter has increased/decreased, but the data must keep its length when converted.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An internal error occurred in the conversion routine.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

The conversion routine is out of memory.

Try the following:

• Increase the memory resources available for EntireX Broker.

• If the error persists:

  Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An invalid RPC payload was sent. The conversion routine detected an inconsistent RPC protocol.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

The RPC protocol is not supported by the conversion routine.

Try the following:

• Check if an older version of the EntireX Broker and/or conversion routine is in effect.

• Determine the component (RPC client or RPC server) sending the RPC payload. To find out the IDL library and IDL program where the error occurred, configure trace level 2 for the service-specific or topic-specific broker attribute CONVERSION.

• If the error persists:

  Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

The conversion routine supports "RPC compression 2" and "no RPC compression". "RPC compression 1" is not supported.

Try the following:

• Determine the component (RPC client or RPC server) sending the RPC payload. To find out the IDL library and IDL program where the error occurred, configure trace level 2 for the service-specific or topic-specific broker attribute CONVERSION.

• Do not use "RPC compression 1" when RPC conversion SAGTRPC is involved. Use "RPC compression 2" in your RPC client. See the documentation of the RPC client component involved for how to configure RPC compression.

• If the error persists:

  Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

The RPC protocol sent by the client or server is invalid.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

The RPC protocol sent by the client or server is invalid.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

The RPC protocol sent by the client or server is invalid.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An internal error occurred.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An internal error occurred.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

Some of the characters to be converted have no equivalent in the target ICU converter.

Try the following:

• Determine the component (RPC client or RPC server) sending the RPC payload. To find out the IDL library and IDL program where the error occurred, configure trace level 2 for the service-specific or topic-specific broker attribute CONVERSION.

• Use an ICU converter where all needed characters are defined (see ICU Resources and Codepage Requirements for RPC Data Stream Conversions). Check if the ICU converter is the correct one. If not, reconfigure the RPC component. See Preparing EntireX Components for Internationalization.

• If possible for the scenario, you can replace the inconvertible characters with a codepage-dependent substitution character. See OPTION Values for Conversion.

• If the error persists:

  Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

Some of the characters to be converted are not defined in the source ICU converter of the sender. The payload and the ICU converter of the sender do not match.

Try the following:

• Determine the component (RPC client or RPC server) sending the RPC payload. To find out the IDL library and IDL program where the error occurred, configure trace level 2 for the service-specific or topic-specific broker attribute CONVERSION.

• Use an ICU converter where all needed characters are defined (see ICU Resources and Codepage Requirements for RPC Data Stream Conversions). Check if the ICU converter is the correct one. If not, reconfigure the RPC component. See Preparing EntireX Components for Internationalization.

• If possible for the scenario, you can replace the inconvertible characters with a codepage-dependent substitution character. See OPTION Values for Conversion.

• If the error persists:

  Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An internal table overflow occurred.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An internal error occurred.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An internal error occurred.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An internal error occurred.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

The valid range of errors returned by the SAGTRPC user exit is 1-9999. For more information see Writing SAGTRPC User Exits under z/OS | UNIX | Windows.

Check your SAGTRPC user exit and correct the error.

An invalid RPC payload was sent. A string buffer is required for the RPC protocol but could not be detected.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An invalid RPC payload was sent. A format buffer is required for the RPC protocol but could not be detected.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An invalid RPC payload was sent. An attribute start tag was detected but the corresponding end tag is missing.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An invalid RPC payload was sent. An invalid attribute was detected.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An invalid RPC payload was sent. This error occurs in the following situations:

1. An unexpected end of the value buffer occurred.

2. The indices of an unbounded array cannot be parsed correctly.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An error occurred when updating new offsets and length in the RPC protocol header after decrease/increase of buffers.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

This is an internal message.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

During conversion the format buffer has increased or decreased, but the format buffer must keep its length when converted.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An invalid RPC payload was sent. An unexpected end of the string buffer occurred.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An invalid RPC payload was sent. The delimiter between keyword and value in the string buffer is missing.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An invalid RPC payload was sent. This error occurs in the following situations:

1. An unexpected end of the value buffer occurred.

2. An error occurred when parsing the value buffer for the actual length of AV, BV and KV data types.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An invalid RPC payload was sent. A group end was detected without a group start tag.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An invalid RPC payload was sent. A group was detected without a corresponding group end.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An invalid payload was sent. A group was detected with an invalid group start indicator.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

The error indicated by number has occurred during ECS binding of codepages.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

For an EBCDIC stateful codepage (encoded with escape technique, that is, SI/SO bytes) there is no DBCS space defined.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

If IDL K fields are used with EBCDIC stateful codepages (encoded with escape technique, that is, SI/SO bytes) the fields must have even length. For more information see Conversion with Multibyte, Double-byte and other Complex Codepages.

Try the following:

• For fixed-length IDL K fields, define the field in your IDL with even length. For variable-length KV fields, make sure to send your data with even length. For more information see IDL Data Types.

• If the error persists:

  Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

The length of DBCS space is not as expected.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

The length of space is not as expected.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

There is no space defined.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

The error indicated by number has occurred during load of the conversion routine by your SAGTRPC user exit. For number refer to your operating system documentation.

Where applicable check the following possibilities:

• Under UNIX and Windows, check that the link step of SAGTRPC user exit is correct and all required libraries are linked to your SAGTRPC user exit.

  See Writing SAGTRPC User Exits under z/OS | UNIX | Windows.

• Under UNIX, check that libsagtrpc.so is accessible by the broker. If it is not accessible, reinstall EntireX.

• Under Windows, check that libsagtrpc.dll is accessible by the broker. If it is not accessible, reinstall EntireX.

• Under all other operating systems and if the error persists:

  Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

Internal error.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

Internal error.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

Internal error.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

Internal error.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

The error indicated by error has occurred during execution of an ICU function. Possible errors are:

U_FILE_ACCESS_ERROR - This error indicates a missing ICU converter or a missing mapping from ICU alias name to the real ICU converter name. The ICU converter can be accessed with any name (alias name or real name).

Depending on the error situation:

• U_FILE_ACCESS_ERROR - Examine the broker's trace for the name used to locate the ICU converter. For information on available ICU converters and their alias names, see ICU Converter Explorer. There are the following possibilities:

  • If the client or server component uses a valid codepage for its environment but sends a name which is not a valid ICU alias, you can define an ICU alias to ICU Converter name mapping in the EntireX Broker attribute file. See Codepage-specific Attributes under Broker Attributes.

  • Reconfigure the client or server component to use a codepage valid in its own environment and available as an ICU converter. See Preparing EntireX Components for Internationalization.

• For all other errors:

  Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

The error indicated by number has occurred during load of the conversion routine by your SAGTRPC user exit. For number refer to your operating system documentation.

Contact Software AG support.

The option defined with the service-specific or topic-specific broker attribute CONVERSION cannot be used together with the defined conversion.

Define an option supported by the defined conversion. See OPTION Values for Conversion.

Internal error.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An invalid RPC payload was sent. The sender's data was not correctly converted to the intermediate Unicode encoding of the RPC protocol.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

The error indicated by number has occurred during load of a module required by the conversion. For number refer to your operating system documentation.

Where applicable, check the following possibilities:

• Under z/OS, check that EXXICU is accessible by the broker. If it is not accessible, reinstall EntireX.

• Under UNIX, check that libsagtrpcicu.so is accessible by the broker. If it is not accessible, reinstall EntireX.

• Under Windows, check that libsagtrpcicu.dll is accessible by the broker. If it is not accessible, reinstall EntireX.

If the error persists:

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

If your EntireX Broker is running under z/OS, also provide the module report. Refer to DDNAME ETBMREP under Step 2: Edit the Broker Startup Procedure under Installing EntireX Broker under z/OS.

The error indicated by number has occurred during load of a module required by the conversion. For number refer to your operating system.

Where applicable, check the following possibilities:

• Under z/OS, check that EXXICU is accessible by the broker. If it is not accessible, reinstall EntireX.

• Under UNIX, check that libsagtrpcicu.so is accessible by the broker. If it is not accessible, reinstall EntireX.

• Under Windows, check that libsagtrpcicu.dll is accessible by the broker. If it is not accessible, reinstall EntireX.

If the error persists:

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

If your EntireX Broker is running under z/OS, also provide the module report. Refer to DDNAME ETBMREP under Step 2: Edit the Broker Startup Procedure under Installing EntireX Broker under z/OS.

Unconvertible characters were detected in RPC binary, integer or date fields. The ICU converter used by the receiver does not support characters required by the RPC protocol. The ICU converter of the receiver cannot be used with RPC calls.

Try the following:

• Determine the component (RPC client or RPC server) sending the RPC payload. To find out the IDL library and IDL program where the error occurred, configure trace level 2 for the service-specific or topic-specific broker attribute CONVERSION.

• Use an ICU converter where all needed characters are defined (see ICU Resources and Codepage Requirements for RPC Data Stream Conversions). Check if the ICU converter is the correct one. If not, reconfigure the RPC component. See Preparing EntireX Components for Internationalization.

• If the error persists:

  Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

Unconvertible characters were detected in RPC metadata. The ICU converter used by the receiver does not support characters required by the RPC protocol. The ICU converter of the receiver cannot be used with RPC calls.

Try the following:

• Determine the component (RPC client or RPC server) sending the RPC payload. To find out the IDL library and IDL program where the error occurred, configure trace level 2 for the service-specific or topic-specific broker attribute CONVERSION.

• Use an ICU converter where all needed characters are defined (see ICU Resources and Codepage Requirements for RPC Data Stream Conversions). Check if the ICU converter is the correct one. If not, reconfigure the RPC component. See Preparing EntireX Components for Internationalization.

• If the error persists:

  Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An invalid RPC payload was sent. Invalid characters where detected in IDL binary, integer or date fields of the sender. The payload and the ICU converter of the sender do not match or the payload that was sent is not a valid RPC protocol.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An invalid RPC payload was sent. Invalid characters were detected in RPC metadata of the sender. The payload and the ICU converter of the sender do not match, or the payload that was sent is not a valid RPC protocol.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

Internal error.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

Closing an ICU handle returned an error.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An internal error occurred.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

ECS Conversion is no longer supported.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

For the Hebrew codepage CP803, lowercase metadata is converted to uppercase. An error occurred during this. For more information see Conversion with Multibyte, Double-byte and other Complex Codepages.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

The payload of the sender could not be converted to the encoding of the receiver. The given Unicode character is not contained in the ICU converter of the receiver.

Try the following:

• For RPC-based Components:

  • Determine the component (RPC client or RPC server) sending the RPC payload. To find out the IDL library and IDL program where the error occurred, configure trace level 2 for the service-specific or topic-specific broker attribute CONVERSION.

  • Use an ICU converter where all needed characters are defined (see ICU Resources and Codepage Requirements for RPC Data Stream Conversions). Check if the ICU converter is the correct one. If not, reconfigure the RPC component. See Preparing EntireX Components for Internationalization.

• If possible for the scenario, you can replace the inconvertible characters with a codepage-dependent substitution character. See OPTION Values for Conversion.

• If the error persists:

  Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An invalid payload was sent. The payload and the ICU converter of the sender do not match. There is no character defined in the ICU converter at the given codepoint.

Try the following:

• For RPC-based Components:

  • Determine the component (RPC client or RPC server) sending the RPC payload. To find out the IDL library and IDL program where the error occurred, configure trace level 2 for the service-specific or topic-specific broker attribute CONVERSION.

  • Use an ICU converter where all needed characters are defined (see ICU Resources and Codepage Requirements for RPC Data Stream Conversions). Check if the ICU converter is the correct one. If not, reconfigure the RPC component. See Preparing EntireX Components for Internationalization.

• Check that the data sent is correct.

• If possible for the scenario, you can replace the inconvertible characters with a codepage-dependent substitution character. See OPTION Values for Conversion.

• If the error persists:

  Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

The EntireX Broker's ICU converter is required to parse the RPC payload of the sender. The given Unicode character is missing in the defined EntireX Broker's ICU converter.

Try the following:

• Check if the ICU converter of the EntireX Broker is the correct one. If not, reconfigure the EntireX Broker.

• If the error persists:

  Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

The EntireX Broker's ICU converter is required to parse the RPC payload of the sender. There is no character defined at the given codepoint in the ICU converter.

Try the following:

• Check if the ICU converter of the EntireX Broker is the correct one. If not, reconfigure the EntireX Broker.

• If the error persists:

  Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

In some situations it is necessary to use an additional ICU converter for conversion (for example the old Hebrew codepage CP803). The error occurred using this additional converter. The given Unicode character is not contained in the given ICU converter.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

In some situations it is necessary to use an additional ICU converter for conversion (for example the old Hebrew codepage CP803). The error occurred using this additional converter. No character is defined in the given ICU converter at the given codepoint.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An invalid RPC payload was sent. Invalid characters where detected in integer or binary data of the sender. The payload and the ICU converter of the sender do not match, that is, there is no character defined in the given ICU converter at the given codepoint, or the payload that was sent is not a valid RPC protocol.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An invalid RPC payload was sent. Invalid characters where detected in metadata of the sender. The payload and the ICU converter of the sender do not match, that is, there is no character defined in the given ICU converter at the given codepoint, or the payload that was sent is not a valid RPC protocol.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

An invalid RPC payload was sent. Invalid characters where detected in string buffer items of the sender. The payload and the ICU converter of the sender do not match, that is, there is no character defined in the given ICU converter at the given codepoint, or the payload send is not a valid RPC protocol.

Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

Integer or binary data of the RPC payload of the sender could not be converted into the encoding of the receiver. The given Unicode character is not contained in the given ICU converter.

• Determine the component (RPC client or RPC server) sending the RPC payload. To find out the IDL library and IDL program where the error occurred, configure trace level 2 for the service-specific or topic-specific broker attribute CONVERSION.

• Use an ICU converter where all needed characters are defined (see ICU Resources and Codepage Requirements for RPC Data Stream Conversions). Check if the ICU converter is the correct one. If not, reconfigure the RPC component. See Preparing EntireX Components for Internationalization.

• If the error persists:

  Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

Metadata of the RPC payload of the sender could not be converted into the encoding of the receiver. The given Unicode character is not contained in the given ICU converter.

• Determine the component (RPC client or RPC server) sending the RPC payload. To find out the IDL library and IDL program where the error occurred, configure trace level 2 for the service-specific or topic-specific broker attribute CONVERSION.

• Use an ICU converter where all needed characters are defined (see ICU Resources and Codepage Requirements for RPC Data Stream Conversions). Check if the ICU converter is the correct one. If not, reconfigure the RPC component. See Preparing EntireX Components for Internationalization.

• If the error persists:

  Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.

The RPC string buffer of the RPC payload of the sender could not be converted into the encoding of the receiver. The given Unicode character is not contained in the given ICU converter.

• Determine the component (RPC client or RPC server) sending the RPC payload. To find out the IDL library and IDL program where the error occurred, configure trace level 2 for the service-specific or topic-specific broker attribute CONVERSION.

• Use an ICU converter where all needed characters are defined (see ICU Resources and Codepage Requirements for RPC Data Stream Conversions). Check if the ICU converter is the correct one. If not, reconfigure the RPC component. See Preparing EntireX Components for Internationalization.

• If the error persists:

  Configure trace level 3 for the service-specific or topic-specific broker attribute CONVERSION and provide a trace to Software AG support.