IGWASYS, IGWASMS, IGWABWO, IGWLSHR Return and Reason Codes

When IGWASYS, IGWASMS, IGWABWO, or IGWLSHR returns control to the calling program, it provides both a return code and a reason code. IGWASMS and IGWABWO can return additional data useful for problem determination in the prob_det array. IGWLSHR can return additional data regarding share_attr_selector and share_attr_array_length arguments. The following table identifies return code and reason code combinations, tells what each means, explains what and when additional problem determination data is returned, and recommends what action should be taken.

Table 1. IGWASYS, IGWASMS, IGWABWO, IGWLSHR Return and Reason Codes
Return Code Dec (Hex)	Reason Code Dec (Hex)	Description
0 (0)	0 (0)	The operation was successful.
4 (4)	4 (4)	The operation was successful, but the bwo_recov argument has no valid value for the data set specified in dsname. This is because it was created under DFP 3.1.0, and no bwo_recov has been added to the data set. Add bwo_recov to the data set as appropriate.
8 (8)	4 (4)	An invalid dsname_length or share_attr_selector was specified. Correct the argument and retry the request.
8 (8)	8 (8)	An invalid dsname of blanks or invalid share_attr_array_length was specified. Correct the argument and retry the request.
8 (8)	12 (C)	An invalid read_write was specified. A value of 0 or 1 must be supplied. Correct the read_write argument and retry the request.
8 (8)	16 (10)	The values supplied for bwo_flags are not valid. BWO1, BWO2, and BWO3 must have a value of either 0 or 1. Correct the bwo_flags argument and retry the request.
8 (8)	20 (14)	BWO is only supported for VSAM-type data sets. The name specified was not a VSAM cluster name. Specify the name of a VSAM cluster in the dsname argument and retry the request.
8 (8)	24 (18)	An invalid level_indicator was specified. Correct the level_indicator argument and retry the request.
8 (8)	28 (1C)	An invalid select argument was specified. A value between 1 and 3 must be specified. Correct the select argument and retry the request.
8 (8)	32 (20)	The data set specified in dsname is not an SMS-managed data set. Correct the dsname argument and retry the request.
12 (C)	8 (8)	There is insufficient virtual storage to process the request. Free some virtual storage and retry the request. If the condition persists, contact IBM® for programming assistance.
12 (C)	12 (C)	The data set specified in dsname could not be found. Verify that the data set exists and has been correctly specified in dsname.
12 (C)	16 (10)	The data set specified in dsname is currently in MIGRATE status.
16 (10)	4 (4)	An error occurred on a call to catalog management. The catalog return code is in the first element of prob_det and the catalog reason code is in the second element of prob_det. See message IDC3009I for an explanation of the catalog return code and reason code. A catalog management return code of 8 indicates that the specified data set was not found. If you get this return code, correct dsname and retry the request.
20 (14)	4 (4)	A system error occurred during IGWASYS/SMS/BWO or IGWLSHR processing. The elements of prob_det contain additional diagnostic data. Contact IBM for programming assistance and provide them with the IGWASYS/SMS/BWO return_code, reason_code, and prob_det values.
36 (24)	4 (4)	Linkage cannot be established to the IGWLSHR service module or to IGWASYS/SMS/BWO service modules, IGWAMCS1 and IGWAMCS2. Either the wrong level of the operating system is being used, or the callable system service library, SYS1.CSSLIB, is missing the required services. Contact your installation system programmer for assistance.