 |
» |
|
|
|
MESSAGE: No error,
info only. | |
MESSAGE: The driver
detected an exception in hardware operation. | CAUSE: The driver
detects an exception in hardware operation. At this state, the only
type of requests that would be processed are the diagnostic requests
or Module Deconfigurator Call. ACTION: Stop the normal operation
and execute the diagnostic software. |
MESSAGE: Adapter
card firmware reported an error. | CAUSE: The firmware
reports an error, at this state, the driver would stop the normal
operation and process diagnostic requests or Module Deconfigurator
Call. ACTION: Stop the normal operation
and execute error recovery software. |
MESSAGE: A power
failure occurred. | CAUSE: A power
failure occurred. The driver failed to process the powerfail recovery. ACTION: According to the
subsystem. |
MESSAGE: Error in
interface with Operating System. | CAUSE: Errors
in interfacing with the operating system (example, ports, memory,
procedures, I/O services etc.). ACTION: According to the
situation. |
MESSAGE: Error in
interface with Buffer Manager. | CAUSE: An error
was detected in interfacing with Buffer Manager (example, Nil buffer
pointer in read/write, nil buffer pool id, etc.). ACTION: According to the
situation. |
MESSAGE: General
error in operation of link driver software. | CAUSE: This is
a "catch all" error for the ultimate non-specific
driver error. ACTION: According to the
implementation. |
MESSAGE: Inadequate
resources available to satisfy a request. | CAUSE: There are
inadequate SAP control block, buffers, or link stations available
to satisfy the request. ACTION: According to the
situation, close some SAPs/stations or wait. |
MESSAGE: An adapter
card is not responding. | CAUSE: The driver
detects an exception in hardware operation. At this state, the only
type of requests that would be processed are the diagnostic requests
or Module Deconfigurator Call. ACTION: Stop the normal operation
and execute the diagnostic software. |
MESSAGE: Could not
establish requested connection, but can retry. | CAUSE: The Connect
Request could not establish a requested connection, however, it
is a recoverable situation. ACTION: Start a timer and
try again when timer popped. |
MESSAGE: Could not
establish requested connection, cannot retry. | CAUSE: The Connect
Request could not establish a requested connection and it is not
a recoverable situation. ACTION: Determine the cause
for the failure and try again when resolved. |
MESSAGE: Could not
establish requested connection, no remote response. | CAUSE: The Connect
Request could not establish a requested connection. ACTION: Check the configuration
and make sure the remote system is up and running. |
MESSAGE: Remote connections
are still active. | CAUSE: For the
Separate Request, there are connections still active on the LSAP,
the driver did not close the LSAP or disconnect the associated connections. ACTION: Disconnect all the
associated connections and try again. |
MESSAGE: Link has
lost its connection to the remote link. | CAUSE: After the
link has been established and both link stations are in open state,
a link station detected an inoperative condition in either the remote
link station or in the transmission medium (the recovery attempt
has failed). The driver informs the user that link is inoperative,
also, no link station resource has been deallocated. ACTION: Send a Disconnect
Request to the Driver and log the error. |
MESSAGE: Remote link
has disconnected. | CAUSE: For the
Disconnect Event, the remote link station issued a Disconnect command
to the link station, and the link station has replied that disconnect
command and notified the subsystem. ACTION: According to the
subsystem. |
MESSAGE: Link disconnected,
although remote has not acknowledged. | CAUSE: The driver
issued a disconnect command to the remote link station as a result
of receiving a Disconnect Request. No acknowledgment has bee received
from the remote link station and the in station has been closed. ACTION: According to the
subsystem. |
MESSAGE: An active
connection with the remote link already exists. | CAUSE: The Driver
is already configured. ACTION: According to the
subsystem. |
MESSAGE: Link sharing
conflicts with current usage. | CAUSE: A driver is being exclusively accessed by a subsystem
already, no resources have been allocated for the second subsystem. A subsystem wants to have exclusive access to a
"shared" driver which is currently in use, no
resources have been allocated. Driver does not support link sharing. Configurable parameters conflict.
ACTION: According to the
subsystem. |
MESSAGE: Configuration
file access error. | CAUSE: A module
Configurator/Deconfigurator detected an error in the configuration
file on accessing the configuration file. ACTION: According to the
subsystem. |
MESSAGE: Error in
interface with Link Support Services. | CAUSE: A module
Configurator/Deconfigurator failed in calling Link Support Services
(LSS) procedures. ACTION: According to the
subsystem. |
MESSAGE: Error in
interface with Trace Services. | CAUSE: A module
Configurator/Deconfigurator failed to start/stop the TRACE MANAGER,
however, the configuration/deconfiguration operation has the completed
(example, The Driver has deallocated the Driver's resources). ACTION: According to the
subsystem. |
MESSAGE: Resource
deallocation error. | CAUSE: For the
error shutdown handling, all SAPs and all associated link stations
are deallocated, and the driver is deconfigured. ACTION: None |
MESSAGE: One or more
still active resources were deallocated. | CAUSE: For the
error shutdown handling, all SAPs and all associated link stations
are deallocated, and the driver is deconfigured. ACTION: None |
MESSAGE: Link is
already active. | CAUSE: The Driver
is already configured. ACTION: According to the
subsystem. |
MESSAGE: A requested
feature is not supported by this link. | CAUSE: Feature
is not supported/implemented. This might be the result of subsystem
"probing" the capability of the driver (example,
Connection oriented subsystem over a datagram service). ACTION: None |
MESSAGE: A requested
option is not supported by this link. | CAUSE: The Driver
understands the option that user requested, however, it does not
support the option. ACTION: Check Driver ES and
make sure you talk to the right Driver. |
MESSAGE: Link was
expecting optional parameters but they were missing. | CAUSE: The Driver
was expecting some driver specific information, the driver may or
may not be configurated (for some drivers, this information may
be considered critical; and for some other drivers, this information
may be considered optional). ACTION: According to the
subsystem. |
MESSAGE: Link did
not understand the optional parameters supplied. | CAUSE: The Driver
did not understand the optional parameter in the request message. ACTION: Check Driver ES and
make sure you talk to the right Driver. |
MESSAGE: Link type
of the named link is not supported. | CAUSE: The Linkname
passed by the Module Configuration Call or Deconfigurator Call is
invalid. The particular driver is not configured. ACTION: Fix the configuration
file and try again. |
MESSAGE: Link type
of the named link is not supported. | CAUSE: The linktype
that stored in the NMCONFIG file which associated with the Linkname
in a Module Configurator call is unsupported. The particular driver
is not configured. ACTION: Fix the Configuration
file and try again. |
MESSAGE: An invalid
subsystem open ID was specified. | CAUSE: The Open
ID in the Rendezvous Request or Module Deconfigurator call is invalid.
The LSAP is not opened or closed. ACTION: Use a Valid open
ID. |
MESSAGE: An invalid
protocol bind ID was specified. | CAUSE: The requested
Protocol Bind ID does not exist. ACTION: Make the appropriate
changes and reissue the request. |
MESSAGE: An invalid
connection ID was specified. | CAUSE: The requested
Connection ID does not exist. ACTION: Make the appropriate
changes and reissue the request. |
MESSAGE: Link did
not understand the specified address family. | CAUSE: The Driver
detected an error in the address family in the request message. ACTION: Fix the configuration
file and then try again. |
MESSAGE: Link found
an error within the specified address family. | CAUSE: The Driver
detected an error in the address family in the request message. ACTION: Fix the configuration
file and they try again. |
MESSAGE: An invalid
or redundant protocol SAP address was specified. | CAUSE: For the
Rendezvous Request, the LSAP value is the NULL or Global SAP. For
the connect request, this error indicates that this SAP already
has a link to the specified RSAP and destination address combination,
or the remote SAP specified was the null SAP, global SAP, or a group
SAP. ACTION: Use an acceptable
SAP and Destination Address. |
MESSAGE: The specified
local Protocol SAP was already opened. | CAUSE: For the
Rendezvous Request, this error indicates that the LSAP has already
opened. ACTION: Use an acceptable
SAP value. |
MESSAGE: A request
was not accepted due to current state of the link. | CAUSE: The requested
message cannot be accepted because of the existing state of the
link station. (example, A write event message will not be accepted
if the link is in the disconnected, opening or closed state). ACTION: According to the
subsystem. |
MESSAGE: A formatter
error was detected. | CAUSE: A Module
Configurator/Deconfigurator failed to start/stop the TRACE MANAGER,
however, the configuration/deconfiguration operation has completed
(example, The Driver has deallocated the Driver's resources). ACTION: According to the
subsystem. |
|
