Guardian Procedure Errors and Messages Manual

Recovery Corrective action usually involves increasing the read count. For more information, see
the manual for the specific device. If this problem persists and a data communications process is
involved, obtain a trace and submit it to your service provider.
178 (%262) No address list specified.
(device type: 7.2, 7.3, 7.8, 7.9, 11.40, or
61)
Cause An address list was required for this operation, but none was specified.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Corrective action is device dependent and application dependent.
179 (%263) Application buffer is incorrect
(device type: 10 or 61), control request
pending, or autopoll active
(device type: 11.40).
Cause For an AM3270, TR3271, or X25AM data-communication line, an error was encountered
in the application buffer, typically a bad WCC on packet type.
For an EnvoyACP/XF line, the operation was not performed because a control request was pending
or the auto poll feature was active.
For a SNAX line, there was a cryptography failure.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Corrective action is device dependent and application dependent.
180 (%264) Unknown device status received.
(device type: 5.3, 6.6 through 6.10, or 10)
Cause An invalid device status was received and was not translated into a usable error number.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Use the Subsystem Control Facility (SCF) to determine what status was received.
181 (%265) Subdevice expected status information but
received data instead. (device type: 10)
Cause Data was sent to the subdevice, but the subdevice expected status information.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Corrective action is application dependent.
182 (%266) SNALU access method outbound RU error;
see SNALU error code in status area of
SNAX header. (device type: 14.2)
Cause SNAX was unable to transmit an outbound response unit (RU), and the detailed SNAX
application logical unit (SNALU) error code is contained in the status area (2 bytes) of the SNAX
header.
Effect The procedure sets the error code and returns without performing the requested operation.
56 File-System Errors