Message Class 2004 - COBOL Wrapper

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

Overview of Messages

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 | 20040101 | 20040102 | 20040103 | 20040104 | 20040105 | 20040106 | 20040107 | 20040108 | 20040109 | 20040110 | 20040111 | 20040112 | 20040113 | 20040114 | 20040115 | 20040116 | 20040117
20040001 Unbounded Arrays without maximum upper bounds not supported: <library>/<program>/< parameter>/<index>
Explanation

Unbounded arrays without maximum upper bounds are not supported. The appendix of the message gives you the library, program, parameter name and index definition of the IDL parameter causing the error.

Action

Adapt your IDL accordingly 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:

IDL Data Type Description
BV Binary variable length.
AV Alphanumeric variable length.
KV Kanji variable length.

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 program-name or program-alias in the IDL contains characters not allowed for CSECT names. The appendix of the message gives you the library and program of the IDL parameter causing the error.

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:

UV Unicode variable length
U Unicode
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/MICROFOCUS_WINDOWS/MICROFOCUS_UNIX)
Explanation

No option TARGET was specified during generation. TARGET is a required option.

Action

Specify the option TARGET.

20040006 Wrong option <target-option> for TARGET - (BATCH_ZOS/BATCH_VSE/BATCH_BS2000/BATCH_I5OS/ CICS_ZOS/CICS_VSE/IMS_MPP/IMS_BMP/MICROFOCUS_WINDOWS/MICROFOCUS_UNIX)
Explanation

A wrong option TARGET was specified during generation. Valid targets are BATCH_ZOS, BATCH_VSE, BATCH_BS2000, BATCH_I5OS, CICS_ZOS, CICS_VSE, IMS_MPP, IMS_BMP, MICROFOCUS_WINDOWS and MICROFOCUS_UNIX.

Action

Specify a correct option TARGET.

20040007 Wrong option <literal-option> for LITERAL - (QUOTE/APOST)
Explanation

A wrong option LITERAL was specified during generation. Valid values for literal are QUOTE and APOST.

Action

Specify a correct option LITERAL.

20040008 Wrong option <comm-option> for COMM - (LINKAGE/EXTERNAL/COPYBOOK)
Explanation

A wrong option COMM was specified during generation. Valid values for option COMM are LINKAGE, EXTERNAL and COPYBOOK.

Action

Specify a correct option COMM.

20040009 Wrong option <rpc_highest-option> for RPC_HIGHEST - (1110/1120/1130/1140/2000/2020)
Explanation

A wrong option RPC_HIGHEST was specified during generation. Valid values for option RPC_HIGHEST are 1110, 1120, 1130, 1140, 2000 and 2020.

Action

Specify a correct option RPC_HIGHEST.

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 GRAPHIC, which requires exactly half the length of IDL type K/KV.

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 INTERFACE is specified.

Action

Specify a valid value for the option INTERFACE. See the error message or documentation for valid values.

20040012 Wrong option combination <interface>/<target> for INTERFACE/TARGET
Explanation

Wrong values for the options INTERFACE and TARGET are specified.

Action

Specify a valid combination for the options INTERFACE and TARGET. Refer to Using the COBOL Wrapper in Command-line Mode for valid combinations.

20040013 Server stubs required only for IMS
Explanation

This is an internal error.
Action

Contact Software AG.
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:

  • Shorten the structure name representing the container in the IDL to fit to this restriction.

  • If variable number of containers are used with an IDL unbounded array (see array-definition) with maximum, restrict the number of containers.

See CICS Channel Container IDL Rules.

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.

See CICS Channel Container IDL Rules.

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 EXEC CICS LINK from the calling application. This message is a warning issued during generation and tells you that the DFHCOMMAREA of a generated client interface object requires more than 24 KB to send the data (IN and INOUT IDL parameters). Certain restrictions apply depending on how you plan to call the client interface:

  • Distributed program link (DPL)
    That is, the calling application program is in a CICS that is different from the client interface object. Refer to the IBM documentation of EXEC CICS LINK for 24 KB limitations. See also IBM's APAR PQ06624.

  • Program link within the same CICS
    The normal upper limit for the length of the CICS COMMAREA is approx. 32 KB.

The appendix of the message gives you the IDL library and IDL program causing the warning.

Action

Depending on the situation:

  • If the client interface object exceeds 32 KB it is not possible to use the interface type CICS with DFHCOMMAREA. Use the interface type DFHCOMMAREA Calling Convention instead.

  • For distributed program links, see your IBM CICS documentation of EXEC CICS LINK for further information.

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 EXEC CICS LINK from the calling application. This message is a warning issued during generation and tells you that the DFHCOMMAREA of a generated client interface object requires more than 24 KB to receive the data (OUT and INOUT IDL parameters). Certain restrictions apply depending on how you plan to call the client interface:

  • Distributed program link (DPL)
    That is, the calling application program is in a CICS that is different from the client interface object. Refer to the IBM documentation of EXEC CICS LINK for 24 KB limitations. See also IBM's APAR PQ06624.

  • Program link within the same CICS
    The normal upper limit for the length of the CICS COMMAREA is approx. 32 KB.

The appendix of the message gives you the IDL library and IDL program causing the warning.

Action

Depending on the situation:

  • If the client interface object exceeds 32 KB it is not possible to use the interface type CICS with DFHCOMMAREA. Use the interface type DFHCOMMAREA Calling Convention instead.

  • For distributed program links, see your IBM CICS documentation of EXEC CICS LINK for further information.

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

Remove IDL type K or KV from your IDL.
20040022 Wrong option <servercopybooks> for SERVERCOPYBOOKS - (TRUE/FALSE)
Explanation

The wrong value for the option was specified.
Action

Specify TRUE or FALSE.

20040023 Copybooklevel forced to 01 because of OCCURS DEPENDING ON: <library>/<program>
Explanation

If the IDL contains unbounded arrays, the copybooklevel cannot be set to greater than 1.

Action

None.
20040024 Generation of server not supported for TARGET - (IMS_MPP)
Explanation

RPC server for IMS MPP cannot be generated with the COBOL Wrapper.

Action

Do not specify target IMS_MPP for server.

20040025 IDL program name 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 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 8 characters : <library>/<program>
Explanation

EntireX supports a maximum of 8 characters 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 INTERFACE and COMM are specified.

Action

Specify a valid combination for the options INTERFACE and COMM. See Using the COBOL Wrapper in Command-line Mode for valid combinations.

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 BROKER, CLASS, SERVER or SERVICE.

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 TARGET and COMM.

Action

Specify a valid combination for the options TARGET and COMM. See Using the COBOL Wrapper in Command-line Mode for valid combinations.

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 client-side mapping files (Natural | COBOL). The appendix of the message gives you the IDL library and IDL program name causing the error.

Action

None.
20040101 Function not implemented
Explanation

Generic RPC function not implemented.
Action

Contact Software AG.
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 CLIENT-COMMIT.

Action

Correct your program and retry.
20040106 Invalid reliable state
Explanation

This is an internal error.
Action

Contact Software AG.
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 UOWID in the RPC communication area.

Action

Correct your program and retry.
20040109 COMMAREA length not valid
Explanation

The length of the DFHCOMMAREA defined in the EXEC CICS LINK statement when calling a client interface object of interface type DFHCOMMAREA Calling Convention is too short. See Using the COBOL Wrapper for CICS with DFHCOMMAREA Calling Convention (z/OS and z/VSE) under Using the COBOL Wrapper for the Client Side.

Action

Correct your client CICS application.
20040110 Unknown CICS error <error> during call to COBSRVI
Explanation

During call of the generic RPC services module (COBSRVI) by your client interface object the CICS error <error> occurred.

Action

Refer to your IBM CICS documentation.
20040111 COBSRVI not found
Explanation

The generic RPC services module (COBSRVI) was not found by your client interface object.

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:

  • Check if the broker stubs are correctly installed in your target environment and are accessible from your application.

  • Possibly customize the subprogram DOBROKER in the Generic RPC Service module for a valid broker stub name of your target environment.

  • Possibly recompile the Generic RPC Service module and rebuild your application. Proceed as described under Using the COBOL Wrapper.

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 COMM-VERSION of the RPC communication area. See The RPC Communication Area (Reference).

20040114 TRANSFER to <broker-stub> returns with <error-status>
Explanation

The TRANSFER CONTROL within IDMS to the broker stub failed.

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 <idl-parameter-name> does not match the COBOL data type.

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 OCCURS DEPENDING ON is higher than the maximum upper bound defined for an IDL unbounded array, see array-definition under Software AG IDL Grammar in the IDL Editor documentation. For the parameter name, see the generated copybook (see IDL Interface Copybooks) and <occurs-depending-on-index>.

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 OCCURS DEPENDING ON is negative. For the parameter name, see the generated copybook (see IDL Interface Copybooks) and <occurs-depending-on-index>.

Action

Check the value of the parameter, correct it and rerun the program.