Guardian Procedure Errors and Messages Manual

Or, the Expand process encountered one of the following situations:
• The Layer 4 protocol detected a protocol error.
• An I/O power on occurred but all lines used by the Expand process were attached to the
controller for which the IOPON occurred.
• A processor power on occurred.
• The Expand process received a request from a system for which it is not the current path.
• An Expand process received a request to forward a message, but all its lines are down.
Effect The procedure sets the error code and returns without performing the requested operation.
The application must not see this error.
Recovery The file system retries automatically. For additional information, see the Expand Network
Management Guide.
246 (%366) External cluster bypass error; operation
aborted. (device type: 63, subtype 3)
Cause A message from one cluster to another bypassed the Expand process, went directly to its
destination, and terminated due to a disconnect or resynchronization of the bus protocol between
clusters.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Retry the operation if possible. For additional information, see the Expand Network
Management Guide.
248 (%370) Network line handler error; operation
aborted. (device type: 63)
Cause If this error was returned to the application, the Expand process performed an ownership
switch. The request, sent to its remote destination, is aborted because the operating system does
not know the state of the request.
If the error was returned in Expand or X25AM operator message 45, or in SNAX operator message
23 or 24 (line not ready), the network process was unable to establish level-2 communications or
all level-2 retries were exhausted. Possible reasons for this error are:
• The other system was down
• There was an incorrect NEXTSYS parameter in the configuration
• A correctly configured Expand line was initially ready
• There was garbled data or no data in or out
Effect The procedure sets the error code and returns. The request to perform the operation is sent
but it might not have been performed.
Recovery If the error is returned to the application, determine whether the operation must be retried.
If so, retry the request.
If the error is returned in an operator message, recovery is as follows for the corresponding cause:
• Select an alternate path if one exists. The state of the other system can be determined by
issuing an SCF INFO PROCESS $NCP, NETMAP command.
• The Expand process is not usable until the correct NEXTSYS parameter is supplied. Either
correct the NEXTSYS parameter in the SYSGEN file and perform another SYSGEN or use the
Subsystem Control Facility (SCF) to alter the NEXTSYS parameter and then bring the line up
using SCF.
64 File-System Errors