Message Class 2003 - PL/I Wrapper

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, IMS_ZOS and CICS_ZOS.

Specify a correct option TARGET.

Unbounded arrays are not supported.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 your clients, server, stubs, etc.

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 your clients, server, stubs, etc.

The length of the IDL data types below must be even:

This is because the resulting PL/I data type graphic is measured in graphics (2 bytes each) and the IDL length for K, KV in bytes.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 your clients, server, stubs, etc.

The following IDL data types are not supported:

Adapt your IDL accordingly and re-generate your clients, server, stubs, etc.

For the following IDL data types the maximum length of the resulting PL/I data types is usually restricted by the PL/I programming language.

In this case a warning message is produced, generation of sources continues. However, it is likely that the compilation of the generated sources is not possible.The appendix of the message gives you the library, program and parameter name of the IDL parameter causing the warning message.

If the compilation process of the generated sources fails, adapt your IDL accordingly and re-generate your clients, server, stubs, etc.

The following IDL data types below are not supported if a 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 your clients, server, stubs, etc.

For the following IDL data types the maximum precision of the resulting PL/I data types is usually restricted by the PL/I programming language.

If the precision exceeds 15 a warning message is produced, generation of sources continues. However, depending on your compiler, compilation of the generated sources may not possible.The appendix of the message gives you the library, program and parameter name of the IDL parameter causing the warning message.

If the compilation process of the generated sources fails, adapt your IDL accordingly and re-generate your clients, server, stubs, etc.

The IDL data types below have to be aligned. This applies only for RPC servers in the environment IMS:

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

Adapt your IDL and re-generate your clients, server, stubs, etc.

The operating system could not satisfy a memory request.

Increase your memory resources and retry.

Calling the broker stub by the Generic RPC Services program (xxxSRVI) failed.

Check if the broker stub is correctly linked and/or installed in your environment.

The field COM_VERSION in the RPC communication area is not correctly assigned. This is checked in the Generic RPC Services program (xxxSRVI) and Specific RPC Functions module (xxxSRVS).

Correctly assign the COM_VERSION field. For information on how to declare and initialize the RPC communication area, see Using the RPC Communication Area under Writing Applications with the PL/I Wrapper.

The field COM_SIZE in the RPC communication area is not correctly assigned.

Correctly assign the COM_SIZE field. For information on how to declare and initialize the RPC communication area, see Using the RPC Communication Area under Writing Applications with the PL/I Wrapper.

With a packed-decimal unsigned IDL data type, negative values cannot be sent.

Either use positive values (including zero) or change the IDL data type to P packed decimal.

The Generic RPC Services program (xxxSRVI) was invoked with an invalid function assigned to COM_FUNCTION in the RPC communication area.

Correct your program. For a list of valid functions, refer to COM_FUNCTION.

An internal error occurred in a specific RPC functions module (xxxSRVS).

Contact Software AG support.

Calling the Generic RPC Services (xxxSRVI) by the RPC stub from the Specific RPC Functions module (xxxSRVS) failed.

Contact Software AG support.

CICS returned an error during an EXEC CICS LINK call. RESP1 and RESP2 are CICS return codes. The additional error text gives more information on the program called. Possible programs are: calling Generic RPC Services (xxxSRVI)

Contact Software AG support.

CICS did not find the program specified in an EXEC CICS LINK call. The additional error text gives more information on the program called, possible programs are: calling Generic RPC Services (xxxSRVI)

Contact Software AG support.

None.

None.

The required field COM_CLIENT_USERID in the RPC communication area is not given.

Specify a user ID. For information on the required settings in the RPC communication area, see Using the RPC Communication Area under Writing Applications with the PL/I Wrapper.

The password is required in the following situations:

• If EntireX Security is installed, a password is required in the field COM_CLIENT_PASSWORD. See Step 5: Optional Settings in the RPC Communication Area under Writing Applications with the PL/I Wrapper.

• If the flag COM_CLIENT_NATSECURITY is switched on, a password is required in the field COM_CLIENT_PASSWORD or COM_CLIENT_RPCPASSWORD.

Depending on the situation, specify a password or see Using Natural Security under Writing Applications with the PL/I Wrapper.

The reply from the RPC Server is invalid and does not follow the rules of the RPC protocol.

Contact Software AG support.

The field COM_SERVER_LIBRARY in the RPC communication area is not given. The field is required for RPC conversations.

For information on how to work with RPC conversations, see Conversational RPC under Writing Applications with the PL/I Wrapper.

The RPC communication area holds an ongoing RPC conversation which has not been ended. It is not possible to ship in parallel simple non-conversational RPC requests or open another RPC conversation using the same RPC communication area.

For information on how to work with RPC conversations, see Conversational RPC under Writing Applications with the PL/I Wrapper.

The RPC communication area holds an ongoing RPC conversation which has not been ended. It is not possible to ship in parallel simple non-conversational RPC requests or open another RPC conversation using the same RPC communication area.

For information on how to work with RPC conversations, see Conversational RPC under Writing Applications with the PL/I Wrapper.