This section describes error messages which can occur in the COBOL Wrapper. All COBOL Wrapper messages are in message class 2004.
The messages have the format:
2004nnnn
where | 2004 | is the message class, and |
nnnn | is the message number in the range 0000 - 9999 |
20040001 | 20040002 | 20040003 | 20040004 | 20040005 | 20040006 | 20040007 | 20040008 | 20040009 | 20040010 | 20040011 | 20040012 | 20040013 | 20040014 | 20040015 | 20040016 | 20040017 | 20040018 | 20040019 | 20040020 | 20040021 | 20040022 | 20040023 | 20040024 | 20040025 | 20040026 | 20040027 | 20040028 | 20040029 | 20040030 | 20040031 | 20040032 | 20040033 | 20040034 | 20040035 | 20040101 | 20040102 | 20040103 | 20040104 | 20040105 | 20040106 | 20040107 | 20040108 | 20040109 | 20040110 | 20040111 | 20040112 | 20040113 | 20040114 | 20040115 | 20040116 | 20040117 | 20040118 | 20040119 | 20040120 | 20040121 | 20040122 | 20040123 | 20040124 | 20040125 | 20040126
20040001 | Unbounded Arrays without maximum upper bounds not supported: <library>/<program>/< parameter>/<index> |
Explanation |
Unbounded arrays without maximum upper bounds are supported for RPC clients on operating system z/OS with the following interface types: Code generation for other Client Interface Types, other operating systems or RPC servers force this error message. The appendix of the message gives you the library, program, parameter name and index definition of the IDL parameter causing the error. |
Action |
Try to use a supported interface type and re-generate. |
20040002 | <idl-data-type> without maximum length not supported: <library>/<program>/< parameter> | ||||||||
Explanation |
The following IDL data types below are not supported if no maximum length is given:
The appendix of the message gives you the library, program and parameter name of the IDL parameter causing the error. |
||||||||
Action |
Adapt your IDL accordingly and re-generate. |
20040003 | Invalid CSECT name <CSECT-name> for target Compiler <compiler>: <library>/<program> |
Explanation |
The |
Action |
Adapt your IDL accordingly and re-generate. |
20040004 | IDL data type <idl-data-type> not supported: <library>/<program>/<parameter> | ||||
Explanation |
The following IDL data types are not supported:
|
||||
Action |
Adapt your IDL accordingly and re-generate your client and server interface objects. |
20040005 | Missing option TARGET - (BATCH_ZOS/BATCH_VSE/BATCH_BS2000/ BATCH_I5OS/CICS_ZOS/CICS_VSE/ IMS_MPP/IMS_BMP/ IDMS_ZOS) |
Explanation |
No option |
Action |
Specify the option |
20040006 | Wrong option <target-option> for TARGET - (BATCH_ZOS/BATCH_VSE/BATCH_BS2000/BATCH_I5OS/ CICS_ZOS/CICS_VSE/IMS_MPP/IMS_BMP/ IDMS_ZOS) |
Explanation |
A wrong option |
Action |
Specify a correct option |
20040007 | Wrong option <literal-option> for LITERAL - (QUOTE/APOST) |
Explanation |
A wrong option |
Action |
Specify a correct option |
20040008 | Wrong option <comm-option> for COMM - (LINKAGE/EXTERNAL/COPYBOOK) |
Explanation |
A wrong option |
Action |
Specify a correct option |
20040009 | Wrong option <rpc_highest-option> for RPC_HIGHEST - (1110/1120/1130/1140/2000/2020) |
Explanation |
A wrong option |
Action |
Specify a correct option |
20040010 | K/KV cannot be mapped to PIC G: <library>/<program>/<parameter> |
Explanation |
The IDL type K or KV (Kanji) was specified with an uneven length. This
runs into conflict with COBOL data type For example, the IDL 1 MyKanji (K10) corresponds to the COBOL 01 MyKanji PIC G(5) DISPLAY-1. |
Action |
Correct your Software AG IDL file to contain an even length for IDL types K/KV. |
20040011 | Wrong option <option> for INTERFACE - (DFHCOMMAREA/DFHLBUFFER/DFHCHANNEL/LINKAGE) |
Explanation |
A wrong value for the option |
Action |
Specify a valid value for the option |
20040012 | Wrong option combination <interface>/<target> for INTERFACE/TARGET |
Explanation |
Wrong values for the options |
Action |
Specify a valid combination for the options |
20040013 | Server stubs required only for IMS |
Explanation |
This is an internal error. |
Action |
Contact Software AG Support. |
20040014 | Maximum length for CICS container name is 16 characters: <library>/<program>/<parameter>/<container>[text] |
Explanation |
Container names are restricted to 16 characters by CICS. An optional text gives more information. |
Action |
Depending on the situation:
|
20040015 | IDL not valid for CICS with channel container calling convention: <library>/<program>/<parameter>[text] |
Explanation |
The IDL mapped to CICS programs with channel container calling convention may only contain IDL structures and IDL programs with references to this structures. An optional text gives more information. |
Action |
Correct your IDL and retry. |
20040016 | CICS container <container> already used for <direction> : <library>/<program>/<parameter> |
Explanation |
Container for CICS must be unique for input as well as for output. You cannot use them twice. In an IDL program an IDL structure, representing a container, is referenced twice for the same direction. |
Action |
Correct your IDL and retry. |
20040017 | IDL requires RPC protocol <protocol> - downgrade not possible |
Explanation |
Depending on the IDL types given in your IDL, a minimum RPC protocol version is required. You can upgrade it but never go beyond this lower limit. |
Action |
Specify the RPC protocol version <protocol> and re-generate. |
20040018 | Sent length <length> exceeds 24580 DFHCOMMAREA length: <library>/<program> |
Explanation |
The client interface object is generated with interface type
DFHCOMMAREA Calling Convention.
It is called with
The appendix of the message gives you the IDL library and IDL program causing the warning. |
Action |
Depending on the situation:
|
20040019 | Receive length of <length> exceeds 24580 DFHCOMMAREA length: <library>/<program> |
Explanation |
The client interface object is generated with interface type DFHCOMMAREA Calling Convention.
It is called with
The appendix of the message gives you the IDL library and IDL program causing the warning. |
Action |
Depending on the situation:
|
20040020 | Valid start level for data items in COPYBOOKS is from 1 thru 49 |
Explanation |
The COBOL programming language allows level numbers for data items in the range from 1 thru 49. |
Action |
Specify a valid starting level. |
20040021 | BS2000 does not support DBCS i.e. K/KV: <library>/<program>/<parameter> |
Explanation |
BS2000 does not support DBCS. |
Action |
Try to map the data to IDL B/BV (binary). |
20040022 | Wrong option <servercopybooks> for SERVERCOPYBOOKS - (TRUE/FALSE) |
Explanation |
The wrong value for the option was specified. |
Action |
Specify |
20040023 | Copybooklevel forced to 01 because of OCCURS DEPENDING ON: <library>/<program> |
Explanation |
If the IDL contains unbounded arrays, the
|
Action |
None. |
20040024 | Generation of server not supported for TARGET - (IMS_MPP/IDMS_ZOS) |
Explanation |
RPC server for this environment cannot be generated with the COBOL Wrapper. |
Action |
None. |
20040025 | COBOL program name contains more than <number-of-characters> : <library>/<program> |
Explanation |
COBOL for your environment supports a maximum length of <number-of-characters> characters for user-defined words depending on context (operating system etc.). The appendix of the message gives you the IDL library and IDL program causing the warning. |
Action |
Reduce the length of the IDL program name to meet COBOL restrictions. |
20040026 | IDL program alias contains more than 31 characters : <library>/<program> |
Explanation |
COBOL supports a maximum length of 31 characters for user defined words. The appendix of the message gives you the IDL library and IDL program causing the warning. |
Action |
Reduce the length of the IDL program alias to meet COBOL restrictions. |
20040027 | IDL program name contains more than 7 characters for option SERVERCOPYBOOKS : <library>/<program> |
Explanation |
A maximum of 7 characters is supported in this context for COBOL RPC server names. The appendix of the message gives you the IDL library and IDL program causing the warning. |
Action |
Reduce the length of the IDL program name to meet the restriction. |
20040028 | IDL program name contains more than 7 characters : <library>/<program> |
Explanation |
This is a special purpose message. |
Action |
Contact Software AG Support. |
20040029 | Wrong option combination <interface>/<comm> for INTERFACE/COMM |
Explanation |
Wrong values for the options |
Action |
Specify a valid combination for the options |
20040030 | Option value <option> too long. A maximum of 32 characters is allowed. |
Explanation |
The value specified for the option is too long. Options are |
Action |
Shorten the length for the option and retry generation. |
20040031 | Wrong option combination <target>/<comm> for TARGET/COMM |
Explanation |
Wrong values have been specified for the options |
Action |
Specify a valid combination for the options |
20040032 | IDL Library name (<library>) too long. A maximum of 127 characters is allowed |
Explanation |
The IDL library name is too long to generate a COBOL server. |
Action |
Shorten the length for the IDL library and retry generation. |
20040033 | IDL program name (<library>) too long. A maximum of 127 characters is allowed. IDL Library name is <library> |
Explanation |
The IDL program name is too long to generate a COBOL server. |
Action |
Shorten the length for the IDL program and retry generation. |
20040034 | IDL program has a client-side mapping (CVM). COBOL RPC clients not supported: <library>/<program> |
Explanation |
RPC clients generated with the COBOL Wrapper do not support server mapping files (.cvm). The appendix of the message gives you the IDL library and IDL program name causing the error. |
Action |
None. |
20040035 | N/NU/P/PU with more than <n> digits not supported for <target-option>: <library>/<program>/< parameter>/<index> |
Explanation |
For COBOL, the total number of digits for IDL datatypes N, NU, P and PU depends on the environment. See Mapping IDL Data Types to COBOL Data Types. The appendix of the message gives you the library, program, parameter name and index definition of the IDL parameter causing the error. |
Action |
Reduce the number of digits and re-generate. |
20040101 | Function not implemented |
Explanation |
Generic RPC function not implemented. |
Action |
Contact Software AG Support. |
20040102 | Invalid Argument(s) supplied |
Explanation |
Invalid Generic RPC function was given. |
Action |
Correct your program, specify a valid generic RPC function and retry. |
20040103 | Library missing |
Explanation |
No Library name was given. |
Action |
Provide a library in the RPC Communcation Area. |
20040104 | User ID missing |
Explanation |
No user ID was given. |
Action |
Provide a user ID in the RPC Communcation Area. |
20040105 | Not in reliable state CLIENT-COMMIT |
Explanation |
Generic RPC function issued only valid for reliable message(s) started
with |
Action |
Correct your program and retry. |
20040106 | Invalid reliable state |
Explanation |
This is an internal error. |
Action |
Contact Software AG Support. |
20040107 | Conversations mixed with reliable msgs |
Explanation |
You tried to open a conversation while you are within a reliable message sequence. |
Action |
Correct your program and retry. |
20040108 | No active UOWID found |
Explanation |
You tried to get the reliable state of a UOW, but there is no |
Action |
Correct your program and retry. |
20040109 | COMMAREA length not valid |
Explanation |
The length of the |
Action |
Correct your client CICS application. |
20040110 | Unknown CICS error <error> during call to COBSRVI |
Explanation |
During call of the generic RPC services module ( |
Action |
Refer to your IBM CICS documentation. |
20040111 | COBSRVI not found |
Explanation |
The generic RPC services module ( |
Action |
Check if the generic RPC service module is available in your environment. |
20040112 | Broker stub <stub-name> could not be loaded |
Explanation |
You dynamically call the broker stub with the COBOL Wrapper, but the broker stub called could not be found in the environment. |
Action |
Check the following possibilities:
|
20040113 | Invalid COBOL Wrapper API version |
Explanation |
The API version for the COBOL Wrapper is wrong. |
Action |
Specify a correct API version in the field |
20040114 | TRANSFER to <broker-stub> returns with <error-status> |
Explanation |
The |
Action |
See <error-status> and refer to the IDMS documentation. |
20040115 | Wrong data in parameter <idl-parameter-name> |
Explanation |
The data contained in the parameter < |
Action |
Check the value of the parameter, correct it and rerun the program. |
20040116 | Upper bound overflow in <occurs-depending-on-index> |
Explanation |
The actual value provided in an index for an |
Action |
Check the value of the parameter, correct it and rerun the program. |
20040117 | Negative value in <occurs-depending-on-index> |
Explanation |
The actual value provided in an index for an |
Action |
Check the value of the parameter, correct it and rerun the program. |
20040118 | Natural Security Token length error |
Explanation |
The |
Action |
Check if the RPC Communication Area is initialized properly. See Step 1: Declare and Initialize the RPC Communication Area under Writing Standard Call Interface Clients in the COBOL Wrapper documentation. |
20040119 | ODO content is not a rectangle or cuboid |
Explanation |
In COBOL, all vectors in a dimension must have the same length. A 2-dimensional array forms a rectangle, and a 3-dimensional array forms a cuboid. See Three-dimensional Array with Variable Upper Bounds under Software AG IDL Grammar in the IDL Editor documentation. |
Action |
Correct your program, IDL and RPC server and retry. |
20040120 | Memory shortage |
Explanation |
No storage was assigned with the COBOL |
Action |
Try to find the cause of the error. If you are executing in Batch, for example, the possible cause could be memory restrictions defined with the job card. |
20040121 | ACI Version 10 or higher required |
Explanation |
The highest possible ACI version possible is determined by the COBOL Wrapper automatically resulting in ACI version less than 10. Features you are using require at least ACI version 10. |
Action |
Check the version of the broker stub used. If you are using broker kernel, check its version. If you are using Direct RPC, check the version of the EntireX Adapter. |
20040122 | Broker Password length error (max <maximum>) |
Explanation |
The Broker password ( |
Action |
Correct your program and retry. |
20040123 | RPC Library length error (max <maximum>) |
Explanation |
The RPC library ( |
Action |
Correct your program and retry. |
20040124 | RPC User ID length error (max <maximum>) |
Explanation |
The RPC user ID ( |
Action |
Correct your program and retry. |
20040125 | RPC Password length error (max <maximum>) |
Explanation |
The RPC password ( |
Action |
Correct your program and retry. |
20040126 | RPC string buffer too small |
Explanation |
If you are using |
Action |
Correct your program and retry. |