Message Class 1003 - Conversion

This message class is returned if an error has occurred within Conversion. The messages have the format:

1003nnnn

where 1003 is the message class, and
nnnn is the message number in the range 0000 - 9999.

Overview of Messages

10030001 | 10030002 | 10030003 | 10030004 | 10030005 | 10030006 | 10030007 | 10030008 | 10030009 | 10030010 | 10030011 | 10030012 | 10030013 | 10030014 | 10030015 | 10030016 | 10030017 | 10030018 | 10030019 | 10030020 | 10030021 | 10030022 | 10030023 | 10030024 | 10030025 | 10030026 | 10030027 | 10030028 | 10030029 | 10030030 | 10030031 | 10030032 | 10030033 | 10030034 | 10030035 | 10030036 | 10030037 | 10030038 | 10030039 | 10030040 | 10030041 | 10030042 | 10030043 | 10030044 | 10030045 | 10030046 | 10030047 | 10030048 | 10030049 | 10030050 | 10030051 | 10030052 | 10030053 | 10030054 | 10030055 | 10030056 | 10030057 | 10030058 | 10030059 | 10030060 | 10030061 | 10030062 | 10030063 | 10030064 | 10030065 | 10030066 | 10030067 | 10030068 | 10030069 | 10030070 | 10030071 | 10030072 | 10030073 | 10030074 | 10030075 | 10030076 | 10030077 | 10030078 | 10030079 | 10030080
10030001 Error number returned by RPCTRANS
Explanation

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

Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030002 Buffer too small. Requires length bytes
Explanation

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.
Action

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

10030003 No Input Buffer Length
Explanation

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

Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030004 No Input Buffer
Explanation

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

Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030005 No Output Buffer Length
Explanation

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

Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030006 No Output Buffer
Explanation

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

Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030007 Internal Error
Explanation

An internal error has occurred inside the conversion routine.
Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030008 Error number returned by ECS initialize
Explanation

Error number has occurred during ECS initialization.

Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030009 Error number returned by ECS conversion
Explanation

Error number has occurred during ECS conversion.

Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030010 Error converting binary/numeric fields
Explanation

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.

Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030011 No free entries in preallocated list
Explanation

An internal error occurred in the conversion routine.
Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030012 Out of Memory
Explanation

The conversion routine is out of memory.
Action

Try the following:

  • Increase the memory resources available for EntireX Broker.

  • If the error persists:

    Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030013 RPC Protocol Version error
Explanation

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

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030014 RPC Protocol Version not supported
Explanation

The RPC protocol is not supported by the conversion routine.
Action

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 attribute CONVERSION.

  • If the error persists:

    Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030015 RPC Protocol Compression 1 not supported
Explanation

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

Action

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 attribute CONVERSION.

  • Do not use "RPC compression 1" when RPC conversion SAGTRPC is involved. Use "RPC compression 2" in your RPC client.

  • If the error persists:

    Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030016 RPC protocol error parsing format buffer
Explanation

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

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030017 Digit/Character not found
Explanation

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

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030018 Unexpected end During Scan
Explanation

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

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030019 Codepage attribute has bad format
Explanation

An internal error occurred.
Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030020 Codepage attribute contains no data
Explanation

An internal error occurred.
Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030021 Some chars inconvertible to target CP
Explanation

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

Action

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 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 Introduction to 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 attribute CONVERSION and provide a trace to Software AG Support.

10030022 Chars to convert undefined in source CP
Explanation

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.

Action

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 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 Introduction to 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 attribute CONVERSION and provide a trace to Software AG Support.

10030023 Internal attribute table overflow
Explanation

An internal table overflow occurred.
Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030024 Error error returned by ECS free handle
Explanation

An internal error occurred.
Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030025 Error error returned by ECS get handle
Explanation

An internal error occurred.
Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030026 Error error returned by ECS get attributes
Explanation

An internal error occurred.
Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030027 Error error from user exit out of range
Explanation

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 | Linux | Windows.

Action

Check your SAGTRPC user exit and correct the error.
10030028 String Buffer missing
Explanation

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

Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030029 Format Buffer missing
Explanation

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

Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030030 Attribute end tag missing
Explanation

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

Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030031 Attribute error
Explanation

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

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030032 Value Buffer parse error
Explanation

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.
Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030033 Error update addresses/length in header
Explanation

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

Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030034 Output Buffer overflow
Explanation

This is an internal message.
Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030035 Format Buffer length change occurred
Explanation

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

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030036 String Buffer parse error
Explanation

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

Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030037 Delimiter missing
Explanation

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

Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030038 Variable Length Data parse error
Explanation

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.

Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030039 Group end without corresponding start
Explanation

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

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030040 Group end missing
Explanation

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

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030041 No Group start tag
Explanation

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

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030042 Error number returned by ECS create binding
Explanation

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

Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030043 DBCS Space missing for modal codepage
Explanation

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

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030044 K or KV Field must have even length
Explanation

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 EBCDIC Stateful Codepages.

Action

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 attribute CONVERSION and provide a trace to Software AG Support.

10030045 DBCS Space less or more than 2 bytes
Explanation

The length of DBCS space is not as expected.
Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030046 Single Space more than 1 byte
Explanation

The length of space is not as expected.
Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030047 Space missing for codepage
Explanation

There is no space defined.
Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030048 SAGTRPC Load error number
Explanation

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.

Action

Where applicable check the following possibilities:

  • Under Linux 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 | Linux | Windows.

  • Under Linux, 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 attribute CONVERSION and provide a trace to Software AG Support.

10030049 User exit missing
Explanation

Internal error.
Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030050 Invalid Conversion Method
Explanation

Internal error.
Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030051 Invalid Trap Function
Explanation

Internal error.
Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030052 Invalid Direction
Explanation

Internal error.
Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030053 ICU Error error occurred
Explanation

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).

Action

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.

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

  • For all other errors:

    Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030054 SAGTRPC Get EP error number
Explanation

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.

Action

Contact Software AG Support.
10030055 Option conflicts with Method
Explanation

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

Action

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

10030056 Padding occurred for K field and modal CP
Explanation

Internal error.
Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030057 Invalid Unicode Byte Sequence
Explanation

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

Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030058 SAGTRPC ICU Wrapper Load error number
Explanation

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

Action

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 Linux, check that libsagtrpcicu.so is accessible by the broker. If it is not accessible, reinstall EntireX.

  • Under Windows, check that sagtrpcicu.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 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 in the z/OS installation documentation.

10030059 SAGTRPC ICU Wrapper Get EP error number
Explanation

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

Action

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 Linux, check that libsagtrpcicu.so is accessible by the broker. If it is not accessible, reinstall EntireX.

  • Under Windows, check that sagtrpcicu.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 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 in the z/OS installation documentation.

10030060 Unconvertible Chars in B,I,D,.. Field
Explanation

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.

Action

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 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 Introduction to Internationalization.

  • If the error persists:

    Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030061 Unconvertible Chars in Metadata
Explanation

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.

Action

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 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 Introduction to Internationalization.

  • If the error persists:

    Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030062 Invalid Source Chars in B,I,D,.. Field
Explanation

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.

Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030063 Invalid Source Chars in Metadata
Explanation

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.

Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030064 Substitution character length error
Explanation

Internal error.
Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030065 Error error returned by ICU free handle
Explanation

Closing an ICU handle returned an error.
Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030066 Bad access to memory
Explanation

An internal error occurred.
Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030067 No support for ECS
Explanation

ECS Conversion is no longer supported.
Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030068 Length changed during uppercase conversion
Explanation

For the Hebrew codepage CP803, lowercase metadata is converted to uppercase. An error occurred during this. For more information see Hebrew Codepage 803.

Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030069 Missing Unicode character char in target ICU Converter converter
Explanation

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.

Action

Try the following:
10030070 No character at codepoint codepoint in source ICU Converter converter
Explanation

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.

Action

Try the following:

  • Check the codepage configured with the client is the expected one.

  • Check that the data sent is correct and matches the ICU converter (codepage) sent along with the request.

  • 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 attribute CONVERSION and provide a trace to Software AG Support.

10030071 Missing Unicode character char in broker ICU Converter converter
Explanation

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.

Action

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 attribute CONVERSION and provide a trace to Software AG Support.

10030072 No character at codepoint codepoint in broker ICU Converter converter defined
Explanation

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.

Action

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 attribute CONVERSION and provide a trace to Software AG Support.

10030073 Missing Unicode character char in ICU Converter converter
Explanation

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.

Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030074 No character at codepoint codepoint in ICU Converter converter defined
Explanation

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.

Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030075 No character at codepoint codepoint in ICU Converter converter defined for integer or binary data
Explanation

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.

Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030076 No character at codepoint codepoint in ICU Converter converter defined for metadata
Explanation

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.

Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030077 No character at codepoint codepoint in ICU Converter converter defined for string buffer item
Explanation

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.

Action

Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030078 Missing Unicode character char in target ICU Converter converter for integer or binary data
Explanation

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.

Action

  • 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 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 Introduction to Internationalization.

  • If the error persists:

    Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030079 Missing Unicode character char in target ICU Converter converter for metadata
Explanation

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.

Action

  • 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 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 Introduction to Internationalization.

  • If the error persists:

    Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.

10030080 Missing Unicode character char in target ICU Converter converter for string buffer
Explanation

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.

Action

  • 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 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 Introduction to Internationalization.

  • If the error persists:

    Configure trace level 3 for the service-specific attribute CONVERSION and provide a trace to Software AG Support.