Sense code 081C

Request not executable: The requested function cannot be executed, because of a permanent error condition in the receiver.

Bytes 2 and 3 following the sense code contain sense-code-specific information.

Note: For VTAM® sense codes, the meaning of the data in bytes 2 and 3 is dependent upon the context of the sense code.

0000

No specific code applies.

0002

The receiver has an error resulting from a software problem that prevents execution of the request.

0004

For request dump request units:

A requested NCP dump has been terminated because of a permanent I/O error on the dump file—the dump is partially complete and can be formatted and printed.

For activate link and deactivate link request units:

During activation of a channel link, the channel device name for the link to be activated did not consist of three valid hexadecimal digits.

0008

For request load (conditional) and request load (unconditional) request units:

VTAM is unable to successfully open the data set containing the NCP load module.

For request dump request units:

A requested NCP dump has been terminated because of a permanent communication controller I/O error—the dump is partially complete and can be formatted and printed.

For activate link and deactivate link request units:

During activation of a channel link, the channel device name for the link to be activated was found not to have been defined to the operating system.

0009

Device is not online due to system action or explicit system operator action. The device must be varied online. Contact the system operator.

000C

For request load (conditional) and request load (unconditional) request units:

One of the following situations has occurred:

A permanent I/O error has occurred on the diagnostic or load-module data set.
The diagnostic program has detected a probable communication controller hardware error.
A permanent I/O error has occurred on the communication controller. Check that the channel adapter is enabled and that the device is attached.

For Request dump request units:

A requested NCP dump has been terminated because of a permanent I/O error on the dump file—the dump data set cannot be formatted and printed.

For activate link and deactivate link request units:

The hardware device type associated with the channel device name of the channel link being activated is not supported by the PU receiving an ACTLINK.

0010

For request load (conditional) and request load (unconditional) request units:

A time-out has occurred while the diagnostic load program was running (hardstop in the communication controller).

For request dump request units:

A requested NCP dump has been terminated because of a permanent communication controller I/O error—the dump data set cannot be formatted and printed.

For activate link and deactivate link request units:

During activation of a channel link, the attached device specified by a channel device name could not be allocated because it was already allocated to another user.

VTAM hint:

This sense code can occur in response to a VARY ACT command for an NCP if U=device_numbers is specified on the command when the same device number has already been activated.
When this sense code is received in message IST380I for an ACTLINK request, message IST1386I might also be issued. See the return code and reason code in IST1386I to determine the cause of the failure.

0014

For request load (conditional) and request load (unconditional) request units:

The loaded NCP has encountered an error, preventing successful initialization.

For request dump request units:

Cannot successfully open the dump data set.

0018

For request load (conditional) and request load (unconditional) request units:

Load not performed—HALT is in progress.

001C

For request load (conditional) and request load (unconditional) request units:

The communication controller dump-load-restart router has received an input work element that contains an unrecognized command code. The NCP load module is not present in the load module data set (BLDL failure).

This error might also occur if there is an I/O error while loading the file.

0020

For request load (conditional) and request load (unconditional) request units:

A permanent I/O error has occurred. Possible reasons include, but are not limited to, the following ones:

The device type is not defined properly.
The communication controller is not in the proper state for loading.
The service processor is not in the proper state. For example, MOSS-E is powered off.
A hardware error occurred.
The channel adapter address in NCP GEN might not match the hardware address.

For request dump request units:

Unable to successfully load a necessary dump utility module, or insufficient storage is available.

For activate link and deactivate link request units:

VPBUF storage is insufficient.

0024

For request load (conditional) and request load (unconditional) request units:

VTAM is unable to successfully open the data set containing the diagnostic program (ddname INITTEST).

0028

For request load (conditional) and request load (unconditional) request units:

A load of an NCP was requested with an SSP release prior to V3R4 and a release of VTAM prior to V3R2 (this is prohibited), or IFWLEVEL was not loaded with SSP V3R4.

For activate link and deactivate link request units:

During deactivation of a channel link, a device could not be deallocated by the operating system.

For request dump request units:

A requested NCP dump has been terminated because ENQUEUE of the dump data set failed—DASD was not opened and the dump data set cannot be formatted and printed.

002C

For request load (conditional) and request load (unconditional) request units:

The diagnostic program has detected a probable communication controller hardware error.

0030

For request load (conditional) and request load (unconditional) request units:

The NCP or diagnostic program load module has a block size greater than 1024 bytes (the DC option was not specified when the link edit was performed), or the channel adapter address of the controller is not correct in NCP GEN.

For activate link and deactivate link request units:

During activation of a channel link, the operating system path validation failed for the device specified by the channel device name.

0034

For activate link and deactivate link request units:

An SSCP sent ACTLINK or DACTLINK for a resource type to which ACTLINK or DACTLINK does not apply.

0038

For activate link and deactivate link request units:

During activation or deactivation of a channel link, the RDTE was not found, causing a permanent error in locating the resource definition was detected in the PU.

If this sense code is issued as the result of the activation of a 3172 XCA major node, verify that the ADAPNO parameter on the PORT definition statement matches the adapter number assigned by the IBM® 3172 communication controller.

If this sense code is issued as the result of the activation of an XCA major node used in conjunction with an Open Systems Adapter, verify that the ADAPNO parameter on the PORT matches the adapter number configured in the OSA, and that the MEDIUM parameter on the PORT matches the media type that the OSA is configured to support.

003C

For request load (conditional) and request load (unconditional) request units:

The communication controller unit control block does not contain a valid value for the channel-adapter-type field, or the channel adapter address of the controller is not correct in NCP GEN.

For activate link and deactivate link request units:

During activation of a channel link, the device specified by the channel device name was found not to have been made available by the operating system.

0040

For request load (conditional) and request load (unconditional) request units:

The NCP or diagnostic program load module is improperly constructed.

For activate link and deactivate link request units:

During activation of a channel link, the operating system could not complete OPEN processing, denying access to the channel link.

For request dump request units:

A requested NCP dump has been terminated because the dump file is empty.

0044

For request load (conditional) and request load (unconditional) request units:

The IFLOADRN communication controller load utility program is unable to allocate sufficient storage.

0048

For request load (conditional) and request load (unconditional) request units:

The function is already active; the NCP is already loaded.

004A

For request load (conditional) and request load (unconditional) request units:

The NCP is ready to receive the load module.

004C

For request load (conditional) and request load (unconditional) request units:

The size of the NCP load module exceeds the storage capacity of the communication controller.

0050

For request load (conditional) and request load (unconditional) request units:

A permanent I/O error has occurred on the NCP load-module library.

0054

For request load (conditional) and request load (unconditional) request units:

A permanent I/O error has occurred on the diagnostic program load-module library (ddname INITTEST).

0058

For request load (conditional) and request load (unconditional) request units:

A diagnostic program cannot be located in the diagnostic program load-module library (ddname INITTEST)—BLDL failure.

005C

For request load (conditional) and request load (unconditional) request units:

Request Load (conditional) is attempted while another host is already loading the communication controller (unit exception on SENSE channel program).

0060

For request load (conditional) and request load (unconditional) request units:

Start I/O condition Code 3 on SENSE channel program can occur for the following reasons:

Request load (conditional) is attempted while another host is already loading the communication controller.
Channel bypass switch is on.
If the request load is attempted through an ESCON channel, check the fiber link for loose connectors.

0064

For request load (conditional) and request load (unconditional) request units:

A load I/O operation (to a link-attached communication controller) has been purged (by VARY INACT or error recovery of the communication controller of another node in the path to the communication controller).

0068

For request load (conditional) and request load (unconditional) request units:

A load I/O operation (to a link-attached communication controller) has failed (a negative response has been generated by the adjacent communication controller).

0070

For request load (conditional) and request load (unconditional) request units:

A load from the disk was initiated, and the save was ignored.

0074

For request load (conditional) and request load (unconditional) request units:

Error caused by specifying DIAG with the 3725 or the 3720.

0078

For request load (conditional) and request load (unconditional) request units:

Either the CCU is not at the correct level, or the CTLR disk option is not available.

007C

For request load (conditional) and request load (unconditional) request units:

Load module not available on disk.

0080

For request load (conditional) and request load (unconditional) request units:

MOSS error–load module not loaded from the disk.

0084

For request load (conditional) and request load (unconditional) request units:

MOSS error–load module and switch not saved.

0088

For request load (conditional) and request load (unconditional) request units:

The disk function is not supported. Either the CCU is not the correct level, or the CTLR disk option is not available.

008C

For request load (conditional) and request load (unconditional) request units:

The NCP load module has an entry point address of zero.

0090

For request load (conditional) and request load (unconditional) request units:

Warning–loading continued: cannot perform LOADFROM, SAVEMOD, or DUMPLOAD.

00AB

For request load (conditional) and request load (unconditional) request units:

Load not performed—the load subtask has abended.

For request dump request units:

Dump not performed—the dump subtask has abended.

00B0

For request load (conditional) and request load (unconditional) request units:

Probable MOSS error—the load module or switch might not be saved.

00B4

For request load (conditional) and request load (unconditional) request units:

MOSS error–switch not saved.

00B8

For request load (conditional) and request load (unconditional) request units:

Load already in progress.

00BC

For request load (conditional) and request load (unconditional) request units:

Duplicate load module on the disk.

00C0

For request load (conditional) and request load (unconditional) request units:

No room on the disk.

00C4

For request load (conditional) and request load (unconditional) request units:

A disk resource is temporarily unavailable.

00C8

For request load (conditional) and request load (unconditional) request units:

RU length error.

00CC

For request load (conditional) and request load (unconditional) request units:

The request was cancelled by the operator.

00D0

For request load (conditional) and request load (unconditional) request units:

A fast load was not performed, a sequential load has been started.

00D4

For request load (conditional) and request load (unconditional) request units:

The logical unit block (LUB) for the controller is not valid.

00D8

For request load (conditional) and request load (unconditional) request units:

The scheduled IPL cannot be cancelled because it was never scheduled.

00DC

For request load (conditional) and request load (unconditional) request units:

The function is not supported.

00E0

For request load (conditional) and request load (unconditional) request units:

RU sequence error.

00E4

For request load (conditional) and request load (unconditional) request units:

Another load module has been scheduled to IPL within five minutes on the MOSS disk.

00E8

A request was made to BINDER to perform the GETBUF function. The request failed with the return code specified in the message.

00EC

A request was made to BINDER to perform the STARTD function. The request failed with the return code and reason code specified in the message.

00F0

A request was made to BINDER to perform the CREATEW function. The request failed with the return code and reason code specified in the message.

00F2

For request load (conditional) and request load (unconditional) request units:

IPL time is earlier than the system time.

00F4

A request was made to BINDER to perform the INCLUDE function. The request failed with the return code and reason code specified in the message.

00F6

For request load (conditional) and request load (unconditional) request units:

Notify time is earlier than the system time.

00F8

A request was made to BINDER to perform the GETDATA function. The request failed with the GETDATA function. The request failed with the message.

00FC

A request was made to BINDER to perform the FREEBUF function. The request failed with the return code specified in the message.

0A01

An error was detected by the DLC manager of the receiving node during the execution of a management services request. The link connection status has not changed from the state previous to the execution. Volatile storage error.

0A02

0A03

0A04

0B01

An error was detected by the DLC manager of the receiving node during the execution of a management services request. The link connection status was modified from the state existing previous to the execution. Volatile storage error.

0B02

0B03

0B04