Return Codes

The following table lists the possible return codes, their symbolic equates, and their meanings, for the APPC/MVS allocate queue services.

Table 1. Return Codes and Their Meanings
Return Code (Decimal)	Symbolic	Meaning
0	atbcts_ok	The service completed as requested.
4	atbcts_warning	The service completed but possibly not as expected. See the reason_code parameter for a description of the warning condition.
8	atbcts_parameter_error	A user-supplied parameter was found to be in error. For example, a parameter contains characters not in the required character set. See the reason_code parameter to determine which parameter is in error.
16	atbcts_request_unsuccessful	The service was unsuccessful. The cause is most likely a parameter error other than a syntax error, or an environmental error. For example, a syntactically valid LU name was specified, but the LU is not defined to APPC/MVS. An example of an environmental error is that the caller called the service while holding locks. See the reason_code parameter for the specific cause of the error, and to determine whether the error can be corrected and the service re-issued.
32	atbcts_service_failure	APPC/MVS service failure. Record the return and reason code, and give them to your systems programmer, who should contact the appropriate IBM support personnel.
64	atbcts_appc_not_available	APPC/MVS is not currently active. Call the service again after APPC is available.