Message Class 2004 - COBOL Wrapper

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.

Adapt your IDL accordingly and re-generate.

The following IDL data types 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.

Adapt your IDL accordingly and re-generate.

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.

Adapt your IDL accordingly and re-generate.

The following IDL data types are not supported:

Adapt your IDL accordingly and re-generate your client and server interface objects.

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

Specify the option TARGET.

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.

Specify a correct option TARGET.

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

Specify a correct option LITERAL.

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

Specify a correct option COMM.

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

Specify a correct option RPC_HIGHEST.

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.

Correct your Software AG IDL file to contain an even length for IDL types K/KV.

A wrong value for the option INTERFACE is specified.

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

Wrong values for the options INTERFACE and TARGET are specified.

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

This is an internal error.

Contact Software AG.

Container names are restricted to 16 characters by CICS. An optional text gives more information.

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.

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.

Correct your IDL and retry.

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.

Correct your IDL and retry.

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.

Specify the RPC protocol version <protocol> and re-generate.

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.

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.

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.

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.

The COBOL programming language allows level numbers for data items in the range from 1 thru 49.

Specify a valid starting level.

BS2000/OSD does not support DBCS.

Remove IDL type K or KV from your IDL.

The wrong value for the option was specified.

Specify TRUE or FALSE.

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

None.

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

Do not specify target IMS_MPP for server.

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.

Reduce the length of the IDL program name to meet COBOL restrictions.

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.

Reduce the length of the IDL program alias to meet COBOL restrictions.

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.

Reduce the length of the IDL program name to meet the restriction.

This is a special purpose message.

Contact Software AG support.

Wrong values for the options INTERFACE and COMM are specified.

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

The value specified for the option is too long. Options are BROKER, CLASS, SERVER or SERVICE.

Shorten the length for the option and retry generation.

Wrong values have been specified for the options TARGET and COMM.

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

The IDL library name is too long to generate a COBOL server.

Shorten the length for the IDL library and retry generation.

The IDL program name is too long to generate a COBOL server.

Shorten the length for the IDL program and retry generation.

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.

None.

Generic RPC function not implemented.

Contact Software AG.

Invalid Generic RPC function was given.

Correct your program, specify a valid generic RPC function and retry.

No Library name was given.

Provide a library in the RPC Communcation Area.

No user ID was given.

Provide a user ID in the RPC Communcation Area.

Generic RPC function issued only valid for reliable message(s) started with CLIENT-COMMIT.

Correct your program and retry.

This is an internal error.

Contact Software AG.

You tried to open a conversation while you are within a reliable message sequence.

Correct your program and retry.

You tried to get the reliable state of an UOW, but there is no UOWID in the RPC communication area.

Correct your program and retry.

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 in the COBOL Wrapper documentation.

Correct your client CICS application.

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

Refer to your IBM CICS documentation.

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

Check if the generic RPC service module is available in your environment.

You dynamically call the broker stub with the COBOL Wrapper, but the broker stub called could not be found in the environment.

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.

The API version for the COBOL Wrapper is wrong.

Specify a correct API version in the field COMM-VERSION of the RPC communication area. See The RPC Communication Area (Reference) in the COBOL Wrapper documentation.

The TRANSFER CONTROL within IDMS to the broker stub failed.

See <error-status> and refer to the IDMS documentation.

The data contained in the parameter <idl-parameter-name> does not match the COBOL data type.

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

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

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

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

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