Message Class 1001 - RPC Protocol

The RPC server does not have enough memory to receive the client request.

If your server is a Natural RPC Server, increase the MAXBUFF memory parameter.

The RPC server is unable to allocate enough memory to fulfill the request.

Increase the memory resources of your RPC server.

The RPC server returned an internal error. A more specific error <number> may follow.

1. See the trace on the server and/or client side and contact Software AG Support.

2. See under error <number> for an explanation and action to take.

This error message is returned in the following situations:

1. The RPC protocol version you requested is not supported by your RPC server.

2. The server command is not known.

3. There is an error in the RPC protocol header.

Depending on the situation above, for

1. If possible, upgrade your RPC server or use only those data types supported by your RPC server in the IDL file.

2. See the trace on the server and/or client side and contact Software AG Support.

The format buffer within the RPC protocol could not be parsed.

Contact Software AG Support.

The value buffer within the RPC protocol could not be parsed.

Contact Software AG Support.

The packet type shipped with the RPC protocol is not valid.

Contact Software AG Support.

One of the following occurred on the RPC server side:

1. A Natural RPC Server secured by Natural Security denied access because the Natural RPC Security ticket could not be evaluated correctly or is missing.

2. Initialization of a Natural RPC Server failed.

3. An EntireX RPC Server for z/OS CICS® secured by CICS security denied the user's request.

Depending on the situation described above, check your security configuration on the server side.

Natural RPC Server message.

Contact Software AG Support.

Natural RPC Server message.

Contact Software AG Support.

Natural RPC Server message.

Contact Software AG Support.

The RPC server did not find the target customer server program. This message can be appended optionally by IDL information and an RPC Server Message Appendix, where

<Software AG IDL File Information> is either

• Library=<Library> see library-definition under Software AG IDL Grammar in the IDL Editor documentation
  or

• Library=<Library>, Program=<Program> see program-definition under Software AG IDL Grammar in the IDL Editor documentation

<RPC Server Message Appendix> depends on the target RPC server, for example:

• CICS
  For the RPC Server for CICS:

  • RPC Server: CICS program <program> not found.

• COBOL
  For the RPC Server for Batch (z/OS | BS2000) if configured for COBOL⁽¹⁾, or RPC Server for IMS if configured for COBOL⁽²⁾:

  • RPC Server: COBOL program <program> not found.

• PL/I
  For the RPC Server for Batch (z/OS) if configured for PL/I⁽¹⁾ or RPC Server for IMS if configured for PL/I⁽²⁾:

  • RPC Server: PL/I program <program> not found.

• Java
  For the RPC Server for Java:

  • RPC Server: java.lang.ClassNotFoundException: <class>

  • RPC Server: Method <method> not found in class <class> (java.lang.NoSuchMethodException: <class>.<method>())

  • etc.

• C
  For the RPC Server for Batch (BS2000) if configured for C⁽¹⁾, or RPC Server for C:

  • RPC Server: Library <library> not found.

  • RPC Server: Function (Entry Point) <function> not found.

  • RPC Server: Interface Object (Library <library> not found.

  • RPC Server: Interface Object (Entry Point) <function> not found.

  • etc.

Depends on the target RPC server:

• CICS
  For the RPC Server for CICS: see Locating and Calling the Target Server in the RPC Server for CICS documentation on how to make the RPC server customer code available.

• COBOL
  For the RPC Server for Batch (z/OS | BS2000) if configured for COBOL⁽¹⁾, or RPC Server for IMS if configured for COBOL⁽²⁾: see Locating and Calling the Target Server in the z/OS | BS2000  RPC Server documentation on how to make the RPC server customer code available.

• PL/I
  For the RPC Server for Batch (z/OS) if configured for PL/I⁽¹⁾, or RPC Server for IMS if configured for PL/I⁽²⁾: see Locating and Calling the Target Server in the Batch | IMS RPC Server documentation on how to make the RPC server customer code available.

• Java
  The action depends on the <RPC Server Message Appendix> returned. See Generating a Java Server Interface Object under Using the Java Wrapper and entirex.server.packagename in the RPC Server for Java documentation for information.

• C
  For the RPC Server for Batch (z/OS) if configured for C⁽¹⁾, or RPC Server for C: the action depends on the <RPC Server Message Appendix> returned. See Locating and Calling the Target Server in the respective RPC server documentation on how to make the RPC server customer code available.

• etc.

Notes:

1. See marshalling parameter for the RPC Server for Batch (z/OS | BS2000).
2. See marshalling parameter RPC Server for IMS.

The stub or the program/method called by the RPC server ended abnormally. This message can be appended by Natural error information:

[,(Natural Error Info: Program=<NAT Pgm>,Error=<NAT Error>,
                       Line=<NAT Line>,Status=<NAT Status>,Level=<NAT Level>)]
<NAT Pgm>       The Natural Program name which caused the error.
<NAT Error>     The Natural Error number.
<NAT Line>      The Line number within the erroneous program which caused the error.
<NAT Status>    See the Natural documentation.
<NAT Level>     See the Natural documentation.

Correct the program/method called by the RPC server.

The program/method called by the RPC server can return application errors within the range 1 - 9999. The user error is outside of this range.

Check your program/method called by the RPC server and correct the error.

The header within the RPC protocol is invalid.

See the trace on the server and/or client side and contact Software AG Support.

The RPC protocol contains an unknown server command.

Contact Software AG Support.

The parameter definitions within the stub called by the RPC server are different. This error code is typical if clients send data using an older RPC protocol. The code will be detected by the RPC server to adjust its call information.

When working with the Linux or Windows RPC server, no action is required if the error message appears just once per call. Multiple appearances indicate a general problem: re-generate your stubs with the template file server.tpl, compile and link them. If the error persists, contact Software AG Support.

The value range for a parameter is outside the defined range.
Example:
An I1 data type is mapped to a 2-byte integer type in a programming language environment where there is no 1-byte integer type. The range is defined in the interface specification, that is, the IDL file. See Software AG IDL File.
For I1 it is from -127 to 128. The mapping to a 2-byte integer permits a program to set values less than -127 or greater than 128 which is not allowed for I1.

Check the program and correct the error.

This error message is returned in the following situations:

1. The RPC server cannot handle variable-length data types such as AV, BV and KV without maximum lengths.

2. The RPC server cannot handle arrays with variable bounds without maximum upper bounds.

Depending on the situation above, for

1. Specify maximum values for the variable-length data types in the IDL file. See Software AG IDL File.

2. Specify maximum values for the upper bounds of the array in the IDL file.

Internal error in the string buffer of the RPC protocol.

Contact Software AG Support.

The RPC server cannot parse the RPC protocol.

Contact Software AG Support.

The RPC server did not find the library or class given in the RPC protocol.

Check your configuration, server programs and stubs and the library name sent by the client.

The header of the RPC protocol contains an invalid eyecatcher.

Contact Software AG Support.

An overflow occurs with an unbounded array whose maximum array bounds are determined in the IDL file. See Software AG IDL File.

Check the program and correct the error.

Internal error in string buffer.

Contact Software AG Support.

During marshalling/unmarshalling on the server side an error occurred when accessing the unbounded array.

One of the following may apply:

1. The unbounded array was destroyed by your server program. Check the program and correct the error.

2. An internal error occurred in the RPC server. Contact Software AG Support.

The data type and attributes of the unbounded array sent to the server do not match the data type or attributes of the unbounded array within the server stub.

Re-generate, compile and link your server stub using the same IDL file as on the client side.

The client application issues an open conversation RPC request having the conversation already opened.

Contact Software AG Support.

The client application issues a close conversation, close conversation commit or conversational RPC request without having any open conversation.

Contact Software AG Support.

The client application issues a non-conversational RPC request while having an open conversation.

Contact Software AG Support.

The RPC server does not reply in the correct encoding.

• <encoding> ASCII when the RPC server answers in ASCII but EBCDIC is expected

  EBCDIC when the RPC server answers in EBCDIC but ASCII is expected

• <error code> The error code replied by the Server.

Check that character conversion is correctly configured for the broker. See Internationalization with EntireX.

The receiver of an RPC message (client or server) is not able to understand (decode) the message.
Possible causes:

• character conversion issues

• communicating with an incompatible partner (RPC client to ACI)

• the message is damaged for whatever reason

• etc.

Except for character conversion issues, the broker is not the cause of this error.

• Check that character conversion is correctly configured for the broker and the associated components. See Internationalization with EntireX.

• Check that the server you are communicating with is an RPC server and not, for example, an ACI server.

If the error occurs sporadically, contact Software AG Support.

The RPC server does not support optional parameters. Optional parameters are supported by a Natural RPC Server. EntireX RPC servers do not support optional parameters.

Contact Software AG Support to check whether a newer version of the Natural RPC Server may support the feature.

The maximum level for groups is 99.

Correct your application.

You tried to use the Change Password feature of the RPC protocol with an RPC server that does not support this feature.

Do not try to change the password with this RPC server.

The IDL you are using contains features which require a Natural client interface object.

Generate a Natural client interface object out of the Software AG IDL File and use it with the RPC client. See Using the Natural Wrapper for the Client Side in the Natural Wrapper documentation.

This error indicates an application error code. Application error codes enable the RPC server to return customer-invented errors back to the RPC client in a standardized way without defining an error code field in the IDL.

Here the RPC Server for CICS received a CICS ABEND code forced by the application server program using the EXEC CICS ABEND ABCODE(myabend). The ABEND starts with a letter other than "A" and follows the rules for CICS user ABEND codes. The ABEND code (myabend) can be used in the RPC client to gain information about specific application error situations of the server.

For more information see Returning Application Errors.

The error code can be used in RPC clients to test for specific application error codes.

The string buffer item "REL" shipped with the RPC protocol is not valid with RPC request.

Contact Software AG Support.

The value area in the server mapping file could not be parsed. A server mapping file is a Designer file with extension .cvm. See Server Mapping Files for COBOL.

Contact Software AG Support.

The string buffer item "REL" is missing or invalid.

Contact Software AG Support.

The packet type shipped with the RPC protocol is not valid for the use of reliable RPC. The string buffer item "REL" is not valid for the packet type.

Contact Software AG Support.

Reliable RPC allows only IDL direction IN parameters.

Update your IDL, i.e. remove any OUT and INOUT parameters, possibly re-generate your interface object and/or update your application, then retry the RPC call.

The RPC client communicates with an RPC Server for CICS. The RPC server programmer used EXEC CICS ABEND CANCEL together with RPCUEX01 to abort the RPC server customer code. See Using EXEC CICS ABEND CANCEL under Scenarios and Programmer Information in the RPC Server for CICS documentation.

This is an informational message. How the program continues depends on the application.

The RPC server does not support server mapping files (Designer files with extension .cvm). A wrong RPC server was used to execute the RPC request. For <library> see library-definition and for <program> see program-definition under Software AG IDL Grammar in the IDL Editor documentation. The following RPC servers support server mapping files:

• COBOL RPC servers: RPC Server for z/OS (CICS, Batch, IMS) | BS2000 | CICS IPIC | CICS ECI | AS/400 | IMS Connect | CICS Socket Listener. See Server Mapping Files for COBOL for more information.

• Natural RPC server. See Server Mapping Files for Natural for more information.

Use an RPC server that supports client-side server mapping files.

The RPC server does not support the programming language (Natural, COBOL etc.) in the server mapping file (Designer file with extension .cvm). For <library> see library-definition and for <program> see program-definition under Software AG IDL Grammar in the IDL Editor documentation. One of the following situations occurred:

1. At design time with the Designer, a server mapping file containing COBOL mapping was created with COBOL plug-in IDL Extractor for COBOL or COBOL Wrapper (Generate RPC Server). See also Server Mapping Files for COBOL in the Designer documentation.
   At runtime, however, the RPC server used was not a COBOL RPC server.

2. At design time with the Designer, a server mapping file containing Natural mapping was created with Natural plug-in IDL Extractor for Natural or Natural Wrapper (Generate RPC Server). See also Server Mapping Files for Natural in the Designer documentation.
   At runtime, however, the RPC server used was not a Natural RPC server.

• For situation 1, use one of the following COBOL RPC servers: RPC Server for z/OS (CICS, Batch, IMS) | BS2000 | CICS IPIC | CICS ECI | AS/400 | IMS Connect | CICS Socket Listener.

• For situation 2, use a Natural RPC server.

The interface type in the server mapping (Batch, DFHCOMMAREA, IMS MPP (IMS Connect) etc.) is not supported by the EntireX Adapter or RPC server and/or the platform the RPC server is running on. For <library> see library-definition and for <program> see program-definition under Software AG IDL Grammar in the IDL Editor documentation.

At design time with the Designer, a server mapping file (Designer file with extension .cvm) for COBOL with a specific interface type was created with a COBOL plug-in: IDL Extractor for COBOL or COBOL Wrapper (Generate RPC Server).

To call your server program successfully, the target RPC runtime component used must support the interface type. The table below gives an overview of possible combinations of an interface type and RPC server.

Probably a user error. For example, a CICS interface type was used with an RPC Server for Batch.

The length of a numeric IDL type, one of N/NU/P/PU sent by the RPC client is too long for the target programming language and environment where the RPC server is running.

Update your IDL. Re-generate your interface object and/or update your application, then retry the RPC call.

The RPC client sent a client-side mapping file (Designer file with extension .cvm), but a server-side mapping file (.svm) also still exists in the server mapping container for <library> see library-definition and for <program> see program-definition under Software AG IDL Grammar in the IDL Editor documentation. See Server-side Mapping Files in the RPC server documentation for z/OS (CICS, Batch, IMS) | CICS ECI | IMS Connect | BS2000. Usage of server mapping files is mutually exclusive.

If you migrate server-side mapping files to client side mapping files, you may have forgotten Step 2: Remove the Server-side Mapping Files on Target RPC Server. See Migrating Server Mapping Files under Server Mapping Files for COBOL in the Designer documentation.

The server mapping for the IDL library and IDL program contained a server mapping version not supported by the RPC server. A server mapping file is a Designer file with extension .cvm. See Server Mapping Files for COBOL.

Contact Software AG Support for RPC server upgrade.

The EntireX RPC server detected an inconsistency between the deployed server-side mapping (see Server Mapping Files for COBOL in the Designer documentation) and the IDL file with which the RPC client was built. The direction-attribute (IN, OUT, INOUT) of a parameter (see attribute-list under Software AG IDL Grammar in the IDL Editor documentation) defined in the IDL file is different to the direction-attribute in the related server-side mapping.

Possible causes:

• You are calling an existing COBOL server and have reextracted the IDL and server-side mapping without redeploying the server-side mapping file. See Scenario Calling an Existing COBOL Server under z/OS (CICS, Batch, IMS) | BS2000, and Server Mapping Deployment Wizard in the Designer documentation.

• You are writing a new COBOL server and have rebuilt the RPC server with a modified IDL file using the COBOL Wrapper, which updates the server-side mapping file, but the updated server-side mapping file is not redeployed. See Scenario Writing a New COBOL Server under z/OS (CICS, Batch, IMS) | BS2000, and and Server Mapping Deployment Wizard in the Designer documentation.

• etc.

The message provides additional information such as <type-length> and <location>, where

• <type-length> matches the IDL data type; see IDL Data Types

• <location> contains the hierarchy of IDL nodes, separated by a colon

Example: IDL field (NU14.0), location=3.2.1.

The IDL below was used for the RPC call. The location is interpreted as follows:

• third field on level 1 is 'G-parameter-3-on-level-1'

• second parameter on level 2 is the array 'G-parameter-32-on-level-2'

• first field on level 3, which is 'G-parameter-322-on-level-3', produced the error

. . .
define data parameter
1 G-parameter-1-on-level-1       (A10) In
1 G-parameter-2-on-level-1             In
1 G-parameter-3-on-level-1             Out
   2 G-parameter-31-on-level-2
      3 G-parameter-311-on-level-3 (A5)
      3 G-parameter-312-on-level-3 (N8)
      3 G-parameter-313-on-level-3 (NU4)
   2 G-parameter-32-on-level-2    (/25)
      3 G-parameter-322-on-level-3 (NU14)
      3 G-parameter-321-on-level-3 (A5)
1 G-parameter-4-on-level-1      (A64)
. . .
end-define

Make sure the IDL file and the deployed server-side mapping file are consistent. Possibly redeploy the server-side mapping file. If the problem persists, reextract or rewrap and then redeploy.

The EntireX RPC server detected an inconsistency between the deployed server-side mapping (see Server Mapping Files for COBOL in the Designer documentation) and the IDL file with which the RPC client was built. The sequence of IDL data types (see IDL Data Types in the IDL Editor documentation) defined in the IDL file is different to the sequence in the related server-side mapping. See error message 10010150 for possible causes of this situation and additional information for <type-length> and <location>.

Make sure the IDL file and the deployed server-side mapping file are consistent. Possibly redeploy the server-side mapping file. If the problem persists, reextract or rewrap and then redeploy.

The EntireX RPC server detected an inconsistency between the deployed server-side mapping (see Server Mapping Files for COBOL in the Designer documentation) and the IDL file with which the RPC client was built. The length definition of a parameter (see simple-parameter-definition under Software AG IDL Grammar in the IDL Editor documentation) defined in the IDL file is different to the length definition in the related server-side mapping. See error message 10010150 for possible causes of this situation and additional information for <type-length> and <location>.

Make sure the IDL file and the deployed server-side mapping file are consistent. Possibly redeploy the server-side mapping file. If the problem persists, reextract or rewrap and then redeploy.

The EntireX RPC server detected an inconsistency between the deployed server-side mapping (see Server Mapping Files for COBOL in the Designer documentation) and the IDL file with which the RPC client was built. The attributes of a parameter (see attribute-list under Software AG IDL Grammar in the IDL Editor documentation) defined in the IDL file are different to the attributes in the related server-side mapping. See error message 10010150 for possible causes of this situation and additional information for <type-length> and <location>.

Make sure the IDL file and the deployed server-side mapping file are consistent. Possibly redeploy the server-side mapping file. If the problem persists, reextract or rewrap and then redeploy.

The EntireX RPC server detected an inconsistency between the deployed server-side mapping (see Server Mapping Files for COBOL in the Designer documentation) and the IDL file with which the RPC client was built. Either the number of dimensions (one-, two- three-dimensional) or the upper bounds (see array-definition) do not match. See error message 10010150 for possible causes of this situation and additional information for <type-length> and <location>.

Make sure the IDL file and the deployed server-side mapping file are consistent. Possibly redeploy the server-side mapping file. If the problem persists, reextract or rewrap and then redeploy.

An application parameter cannot be processed because its content does not match the expected format unsigned numeric (NU). See IDL Data Types.

The message provides additional information such as <direction>, <parameter-name>, <type-length> and <location>, where

• <direction> is either 'Request' if the error was detected before the RPC server was executed, or 'Reply' for the answer, that is, if the RPC server was already executed.

• <parameter-name> is available for target programming language C only

• <type-length> matches the IDL data type; see IDL Data Types

• <location> contains the hierarchy of IDL nodes, separated by a colon. If an IDL node is an array, its indexes are given in parentheses.

Example: Reply of IDL field (NU14.0), location=3.2(I=5).1.

The IDL below was used for the RPC call. The location is interpreted as follows:

• third field on level 1 is 'G-parameter-3-on-level-1'

• second parameter on level 2 is the array 'G-parameter-32-on-level-2' and (I=5) means the fifth occurrence

• first field on level 3, which is 'G-parameter-322-on-level-3', produced the error

. . .
define data parameter
1 G-parameter-1-on-level-1       (A10) In
1 G-parameter-2-on-level-1             In
1 G-parameter-3-on-level-1             Out
   2 G-parameter-31-on-level-2
      3 G-parameter-311-on-level-3 (A5)
      3 G-parameter-312-on-level-3 (N8)
      3 G-parameter-313-on-level-3 (NU4)
   2 G-parameter-32-on-level-2    (/25)
      3 G-parameter-322-on-level-3 (NU14)
      3 G-parameter-321-on-level-3 (A5)
1 G-parameter-4-on-level-1      (A64)
. . .
end-define

Make sure the IDL file and, if it exists, the server-side mapping file and your server application are consistent. See Server Mapping Files for COBOL in the Designer documentation. Check your application for parameter integrity.

An application parameter cannot be processed because its content does not match the expected format signed numeric (N). See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 10010200.

Make sure the IDL file and, if it exists, the server-side mapping file and your server application are consistent. See Server Mapping Files for COBOL in the Designer documentation. Check your application for parameter integrity.

An application parameter cannot be processed because its content does not match the expected format unsigned numeric (NU) or signed numeric (N). See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 10010200.

Make sure the IDL file and, if it exists, the server-side mapping file and your server application are consistent. See Server Mapping Files for COBOL in the Designer documentation. Check your application for parameter integrity.

An application parameter cannot be processed because its content does not match the expected format unsigned packed (PU). See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 10010200.

Make sure the IDL file and, if it exists, the server-side mapping file and your server application are consistent. See Server Mapping Files for COBOL in the Designer documentation. Check your application for parameter integrity.

An application parameter cannot be processed because its content does not match the expected format signed packed (P). See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 10010200.

Make sure the IDL file and, if it exists, the server-side mapping file and your server application are consistent. See Server Mapping Files for COBOL in the Designer documentation. Check your application for parameter integrity.

An application parameter cannot be processed because its content does not match the expected format unsigned packed (PU) or signed packed (P). See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 10010200.

Make sure the IDL file and, if it exists, the server-side mapping file and your server application are consistent. See Server Mapping Files for COBOL in the Designer documentation. Check your application for parameter integrity.

An application parameter of IDL type I1 cannot be processed because its content is less than the allowed minimum (-128) for I1. See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 10010200.

Make sure the IDL file and, if it exists, the server-side mapping file and your server application are consistent. See Server Mapping Files for COBOL in the Designer documentation. Check your application for parameter integrity.

An application parameter of IDL type I1 cannot be processed because its content is greater than the allowed maximum (+127) for I1. See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 10010200.

Make sure the IDL file and, if it exists, the server-side mapping file and your server application are consistent. See Server Mapping Files for COBOL in the Designer documentation. Check your application for parameter integrity.

An application parameter of IDL type I2 cannot be processed because its content is less than the allowed minimum (-32768) for I2. See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 10010200.

Make sure the IDL file and, if it exists, the server-side mapping file and your server application are consistent. See Server Mapping Files for COBOL in the Designer documentation. Check your application for parameter integrity.

An application parameter of IDL type I2 cannot be processed because its content is greater than the allowed maximum (+32767) for I2. See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 10010200.

Make sure the IDL file and, if it exists, the server-side mapping file and your server application are consistent. See Server Mapping Files for COBOL in the Designer documentation. Check your application for parameter integrity.

An application parameter of IDL type I4 cannot be processed because its content is less than the allowed minimum (-2147483648) for I4. See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 10010200.

Make sure the IDL file and, if it exists, the server-side mapping file and your server application are consistent. See Server Mapping Files for COBOL in the Designer documentation. Check your application for parameter integrity.

An application parameter of IDL type I2 cannot be processed because its content is greater than the allowed maximum (+2147483647) for I2. See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 10010200.

Make sure the IDL file and, if it exists, the server-side mapping file and your server application are consistent. See Server Mapping Files for COBOL in the Designer documentation. Check your application for parameter integrity.

An application parameter of IDL type F4 cannot be processed because its content is less than the allowed minimum (1.175494351e-38F) for F4. See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 10010200.

Make sure the IDL file and, if it exists, the server-side mapping file and your server application are consistent. See Server Mapping Files for COBOL in the Designer documentation. Check your application for parameter integrity.

An application parameter of IDL type F4 cannot be processed because its content is greater than the allowed maximum (3.402823466e+38F) for F4. See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 10010200.

Make sure the IDL file and, if it exists, the server-side mapping file and your server application are consistent. See Server Mapping Files for COBOL in the Designer documentation. Check your application for parameter integrity.

An application parameter of IDL type F4 cannot be processed because of conversation error HUGE_VAL (see C library strtod() for more information). The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 10010200.

Make sure the IDL file and, if it exists, the server-side mapping file and your server application are consistent. See Server Mapping Files for COBOL in the Designer documentation. Check your application for parameter integrity.

An application parameter of IDL type F8 cannot be processed because its content is less than the allowed minimum (2.2250738585072014e-308) for F8. See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 10010200.

Make sure the IDL file and, if it exists, the server-side mapping file and your server application are consistent. See Server Mapping Files for COBOL in the Designer documentation. Check your application for parameter integrity.

An application parameter of IDL type F8 cannot be processed because its content is greater than the allowed maximum (1.7976931348623158e+308) for F8. See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 10010200.

Make sure the IDL file and, if it exists, the server-side mapping file and your server application are consistent. See Server Mapping Files for COBOL in the Designer documentation. Check your application for parameter integrity.

An application parameter of IDL type F4 or F8 cannot be processed because of exponent over- or underflow. See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 10010200.

Make sure the IDL file and, if it exists, the server-side mapping file and your server application are consistent. See Server Mapping Files for COBOL in the Designer documentation. Check your application for parameter integrity.

An application parameter of IDL type AV, BV, KV or UV cannot be processed because incorrect data was applied, see Using Variable-length Data Types AV, BV, KV and UV.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 10010200.

Make sure the IDL file and, if it exists, the server-side mapping file and your server application are consistent. See Server Mapping Files for COBOL in the Designer documentation. Check your application for parameter integrity.

An index of an application parameter for an IDL unbounded-array (see array-definition under Software AG IDL Grammar in the IDL Editor documentation) cannot be processed because its value exceeds the maximum for upper bound The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 10010200.

Make sure the IDL file and, if it exists, the server-side mapping file and your server application are consistent. See Server Mapping Files for COBOL in the Designer documentation. Check your application for parameter integrity.