Binder API common return and reason codes

A return code, indicating the completion status of the requested function, is returned in register 15 and in the fullword designated by the keyword RETCODE, if provided. Return codes are interpreted as follows:

0: Successful completion of the operation.
4: Successful completion, but an unusual condition existed. One or more warning level messages have been issued, and the reason code has been set to indicate the nature of the problem or situation.
8: Error condition detected. Invalid data might have been discarded. Corrective action has been taken by the binder, but results might require inspection.
12: Severe error encountered. Requested operation could not be completed, but the dialog is allowed to continue.
16: Terminating error. Dialog could not be continued. Either a program error occurred in the binder, or binder control blocks have been damaged. The integrity of binder data cannot be assured.

A reason code is returned in register 0 and in the fullword designated by the keyword RSNCODE, if provided.

The reason code identifies the nature of the problem. It is zero if the return code was zero, a valid reason code otherwise. Reason codes are in the format 83eegggg. ee is 00 except for logic errors and abends when it is EEor FF respectively. gggg contains an information code.

Reason codes are described with the individual function descriptions. A few reason codes are common to many functions and described in Table 1. All the binder API reason codes, and the API function that calls them are shown in Binder API reason codes in numeric sequence.

See z/OS MVS Program Management: User's Guide and Reference for a complete list of binder return codes.

Table 1. Common binder API reason codes
Return Code	Reason Code (hex)	Explanation
00	00000000	Normal completion.
08	83000813	Data incompatible with buffer version. Request rejected.
12	83000001	Invalid workmod token. Request rejected.
12	83000002	Invalid dialog token. Request rejected.
12	83000003	Binder invoked from within user exit. Request rejected.
12	83000004	Invalid function code specified. Request rejected.
12	83000005	Invalid parameter. Request rejected.
12	83000006	A function not allowed during PUTD input mode operation was requested. The request is rejected.
12	83000007	Passed symbol contains characters outside the range acceptable to the binder.
12	83000008	Wrong number of arguments specified. Request rejected.
12	83000009	Parameter list contains invalid address, or refers to storage that is not accessible by the binder. Request rejected.
12	83000010	Parameter list is not addressable by the binder. Request rejected.
12	83000101	Improper combination of parameters. Request rejected.
16	83000050	Storage limit established by workspace option exceeded. Dialog terminated.
16	83000051	Insufficient storage available. Dialog terminated. Increase REGION parameter on EXEC statement and rerun job.
16	83000060	Operating system not at correct DFSMS/MVS level. No dialog established, function not processed.
16	83000FFF	IEWBIND module could not be loaded. Issued only by IEWBIND macro.
16	83EE2900	Binder logic error. Dialog terminated. Normally accompanied by a 0F4 abend.
16	83FF`aaa`0	Binder abend occurred. Dialog terminated. `aaa` is the system abend completion code. If the binder is invoked through one of the batch entry points, no attempt is made to intercept x37 abends (indicating out-of-space conditions in SYSLMOD).