This document describes error conditions logged by portable APPN and TN3270 code (pSNA). It summarizes each error condition, describes the detailed data logged, and provides recommended recovery actions.
Events in this document are indexed by message IDs, which are in a major-minor number format. The major part of the message ID represents the component that logged the event, and the minor part identifies a specific message. The table of contents below shows the major part of the message ID and provides a link to sections with all the events under that major ID.
To use this document, you use appropriate APPN log monitoring command. The event log display shows the major-minor message ID for events that have occurred. Once you identify message(s) of interest, you look up their meaning and detailed information in this reference manual.
Change history:
15100000 - pRAS Memory Management Log Events
16100000 - pRAS System Error Log Events (OS)
16101000 - pRAS EGPE Error Log Events (EGPE)
16102000 - pRAS RAS Error Log Events (pRAS)
17100000 - pRAS Software Error Log Events
1F100000 - pRAS General Error Log Events
25100000 - pSNA Storage Management Log Events
26100000 - pSNA General System Error Log Events
27100000 - pSNA General Software Error Log Events
2F101000 - Configuration Services (CS) Log Events
2F102000 - Directory Services (DS) Log Events
2F103000 - Managment Services (MS) Log Events
2F104000 - Node Operator Facility (NOF) Log Events
2F105000 - PC/ASM/SC Log Events
2F107000 - Session Connector Manager (SCM) Log Events
2F109000 - Session Services (SS) Log Events
2F10A000 - Topology & Route Selection (TRS) Log Events
2F10B000 - Accounting Services (ACS) Log Events
2F10C000 - Problem Determination Services (PDS) Log Events
2F10D000 - HPR Path Control (HPC) Log Events
2F10E000 - Rapid Transport Protocol (RTP) Log Events
2F10F000 - PU Network Services (PNS) Log Events
2F114000 - SNMP subagent (SSA) Log Events
2F113000 - Application Interface (API) Log Events
2F115000 - Architected Transaction Program (TPS) Log Events
2F116000 - Attach Manager (AM) Log Events
2F118000 - Half-Session (HS) Log Events
2F119000 - Configuration Verification (PSNAV) Log Events
2F11A000 - Presentation Services (PS) Log Events
2F11B000 - Resource Manager (RM) Log Events
2F11C000 - Session Manager (SM) Log Events
2F11D000 - Dependent LU Requester (DLUR) Log Events
2F11F000 - Data Encryption (CPA) Log Events
2F120000 - pSNA LUA_RUI log event descriptions
2F121000 - pSNA LUA_API log event descriptions
2F122000 - pSNA LUA_API log event descriptions
2F123000 - Discovery Log Events
2F125000 - Logical Data Link Control (LDLC) Log Events
2F126000 - TN3270E Server Log Events
F6100000 - EGPE Log Events (system errors)
F7100000 - EGPE Log Events (software errors)
FF100000 - EGPE Log Events (general errors)
Storage management log events used by pRAS.
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: pRAS could not obtain enough memory (storage) to perform a function. The probable causes are:
Function Degradation: The resulting system action depends on the RAS request being processed when the error occurred. In almost all cases, the request being processed fails and in some cases, is rejected. This may result in the loss of RAS information, such as log or trace records. If this occurs, corresponding log records are created:
When the local node is initializing, the pSNA component that issued the RAS function that failed usually terminates.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
The problem was probably caused by a shortage of available memory in the local node. Increase the amount of memory available to the node and re-start the node.
If the problem was not caused by a memory shortage, the problem was probably caused by a problem in the communications support in the local node. Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pRAS.
Additional Data: Has the following format:
Description: pRAS could not obtain enough memory (storage) to perform a function. The probable causes are:
Function Degradation: The resulting system action depends on the RAS request being processed when the error occurred. In almost all cases, the request being processed fails and in some cases, is rejected. This may result in the loss of RAS information, such as log or trace records. If this occurs, corresponding log records are created:
When the local node is initializing, the pSNA component that issued the RAS function that failed usually terminates.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
The problem was probably caused by a shortage of available memory in the local node. Increase the amount of memory available to the node and re-start the node.
If the problem was not caused by a memory shortage, the problem was probably caused by a problem in the communications support in the local node. Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA.
Additional Data: Has the following format:
Description: pRAS could not access the shared memory (storage) needed perform a function. The probable causes are:
Function Degradation: The resulting system action depends on the RAS request being processed when the error occurred. In almost all cases, the request being processed fails and in some cases, is rejected. This may result in the loss of RAS information, such as log or trace records. If this occurs, corresponding log records are created:
When the local node is initializing, the pSNA component that issued the RAS function that failed usually terminates.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
If the problem was not caused by a system failure or resource shortage, the problem was probably caused by a problem in the communications support in the local node. Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA.
Operating system error log events used by pRAS.
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: A system function failed. A pSNA component encountered a system error while processing a request.
Function Degradation: The failing system function could be recovered from or ignored. The pSNA component continues to process the request. Unexpected behaviour may follow this problem, since not all expected functions may have been performed.
In some severe cases, if the recovery is not possible, the detecting pSNA component terminates or abends.
Customer Action: The local node attempts to recover from the problem and continues processing. In some cases, the recovery is successful and no action is required.
If the node did not recover successfully, or the subsequent behaviour of the local node is erratic, try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
For the 3746 this Logevent is systematically created when a new configuration is activated on a previouly active machine. The failing function is a Pattach of PRAS to node in the control point.
This is related to a timing window, between the deactivation of the APPN tower and the new reactivation, while all DLLs are not completely released in the NNP processor, so that the PRAS exe is restarted before the node.exe
The situation is automatically recovered when node complete its restart. So no action required by the Customer.
Additional Data: Has the following format:
Description: A system function failed. A pSNA component encountered a system error while processing a request. The encountered error is recoverable. The pSNA component will retry the function that failed.
Function Degradation: The failing system function is recoverable. The pSNA component retries the function that failed and if successful, continues to process the request. Unexpected behaviour may follow this problem, especially if the error recovery procedures fail. In most cases, if the system function can not be executed, the log record 16100000-00000003 is created.
In some severe cases, if the recovery is not possible, the detecting pSNA component terminates or abends.
Customer Action: The local node attempts to recover from the problem and continues processing. In some cases, the recovery is successful and no action is required.
If the node did not recover successfully, or the subsequent behaviour of the local node is erratic, try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A system function failed. A pSNA component encountered a system error while processing a request. Either the encountered error is not recoverable, or the retry limit for the function has been reached.
Function Degradation: The resulting system action depends on the RAS request being processed when the error occurred. In almost all cases, the request being processed fails and in some cases, is rejected. This may result in the loss of RAS information, such as log or trace records. If this occurs, corresponding log records are created:
When the local node is initializing, the pSNA component that issued the RAS function that failed usually terminates.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages). If the error was recoverable but the retry limit for the failing function was reached, one or more log records 16100000-00000002 may have been created.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Description: Not used except in old AIX pRAS system layer.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
EGPE error log events used by pRAS.
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Description: None.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Description: None.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Description: None.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Description: Not used except in old AIX pRAS system layer.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
pRAS error log events used by pRAS. Log errors encountered by pRAS external functions used within pRAS.
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Description: None.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: A RAS function failed while processing a RAS request. The RAS component encountered an error while processing a request. The encountered error is recoverable. The RAS component will retry the function that failed.
Function Degradation: The failing RAS function is recoverable. The RAS component retries the function that failed and if successful, continues to process the request. Unexpected behaviour may follow this problem, especially if the error recovery procedures fail. In most cases, if the RAS function can not be executed, the log record 16102000-00000003 is created.
In some severe cases, if the recovery is not possible, the detecting component terminates or abends.
Customer Action: The local node attempts to recover from the problem and continues processing. In some cases, the recovery is successful and no action is required.
If the node did not recover successfully, or the subsequent behaviour of the local node is erratic, try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A RAS function failed while processing a RAS request. The RAS component encountered an error while processing a request. Either the encountered error is not recoverable, or the retry limit for the function has been reached.
Function Degradation: The resulting system action depends on the RAS request being processed when the error occurred. In almost all cases, the request being processed fails and in some cases, is rejected. This may result in the loss of RAS information, such as log or trace records. If this occurs, corresponding log records are created:
When the local node is initializing, the pSNA component that issued the RAS function that failed usually terminates.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages). If the error was recoverable but the retry limit for the failing function was reached, one or more log records 16102000-00000002 may have been created.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Description: Not used except in old AIX pRAS system layer.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Software error log events used by pRAS.
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: The RAS component encountered a should-not-occur condition while processing a request. An internal function was invoked with conflicting or invalid parameters. An internal code problem exists within pSNA.
Function Degradation: The resulting system action depends on the RAS request being processed when the error occurred. In almost all cases, the request being processed fails and in some cases, is rejected. This may result in the loss of RAS information, such as log or trace records. If this occurs, corresponding log records are created:
When the local node is initializing, the pSNA component that issued the RAS function that failed usually terminates.
Even if the component does not terminate immediately, the severity of the error will probably cause the component to abend.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The RAS component encountered a should-not-occur condition while processing a request. An internal function was invoked with an invalid or unexpected parameter. An internal code problem exists within pSNA.
Function Degradation: The resulting system action depends on the RAS request being processed when the error occurred. In almost all cases, the request being processed fails and in some cases, is rejected. This may result in the loss of RAS information, such as log or trace records. If this occurs, corresponding log records are created:
When the local node is initializing, the pSNA component that issued the RAS function that failed usually terminates.
Even if the component does not terminate immediately, the severity of the error will probably cause the component to abend.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The RAS component encountered a should-not-occur condition while processing a request. An internal value is invalid (the value in a switch statement is invalid). An internal code problem exists within pSNA.
Function Degradation: The resulting system action depends on the RAS request being processed when the error occurred. In almost all cases, the request being processed fails and in some cases, is rejected. This may result in the loss of RAS information, such as log or trace records. If this occurs, corresponding log records are created:
When the local node is initializing, the pSNA component that issued the RAS function that failed usually terminates. Even if the component does not terminate immediately, the severity of the error will probably cause the component to abend.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The RAS component received an internal inter-process signal it does not recognize, or the received IPS contains invalid data. This condition should not occur, since the unrecognized signal should not have been routed to the RAS component for processing. An internal code problem exists within pSNA.
Function Degradation: The resulting system action depends on the RAS request being processed when the error occurred. In almost all cases, the unrecognized IPS is ignored, and the component continues to process other signals. Unexpected results will probably follow this problem, since one or more node components are probably in error and out of sequence. This may result in the loss of RAS information, such as log or trace records. If this occurs, corresponding log records are created:
In some cases, the pSNA component that detected the failure terminates.
Customer Action: Call service with the code point, error description, and abend code value if available. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
If possible, try and re-create the problem with traces enabled for the component that detected the error and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The RAS component encountered a should-not-occur condition while processing a request. An internal data structure is invalid. An internal code problem exists within pSNA.
Function Degradation: The pSNA component that issued the RAS request terminates.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The RAS component encountered a should-not-occur condition while processing a request. An internal data structure is invalid. An internal code problem exists within pSNA.
Function Degradation: The pSNA component that issued the RAS request terminates.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The RAS component encountered a should-not-occur condition while processing a request. An internal data structure is invalid. An internal code problem exists within pSNA.
Function Degradation: The pSNA component that issued the RAS request terminates.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: A pSNA component encountered a should-not-occur condition. An internal code problem exists within pSNA.
Function Degradation: The resulting system action depends on the pSNA component that detected the error and the request being processed when the error occurred. In almost all cases, the request being processed fails and in some cases, is rejected. In many cases, the pSNA component that detected the failure terminates. Even if the component does not terminate immediately, the severity of the error will probably cause the component to abend.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA.
General pRAS error log events used by pRAS.
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: The RAS component encountered an error while formatting a log record. The log record identified in this log record cannot be stored in the log database and is lost.
Possible causes are:
Function Degradation: The request being processed is rejected, resulting in the loss of the data currently being logged. Additional log entries or messages are usually created to identify the specific problem that caused the request to fail.
In some cases, the pSNA component that detected the failure terminates. When the local node is initializing, the pSNA component that issued the RAS function that failed usually terminates.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The RAS component encountered an error while storing a log record in the log database. The log record identified in this log record cannot be stored in the log database and is lost.
Possible causes are:
Function Degradation: The request being processed is rejected, resulting in the loss of the data currently being logged. Additional log entries or messages are usually created to identify the specific problem that caused the request to fail.
In some cases, the pSNA component that detected the failure terminates. When the local node is initializing, the pSNA component that issued the RAS function that failed usually terminates.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The RAS component encountered an error while formatting or retrieving a message. The message identified in this log record cannot be issued and is lost.
Possible causes are:
Function Degradation: The request being processed is rejected, resulting in the loss of the message being issued. Additional log entries or messages are usually created to identify the specific problem that caused the request to fail.
In some cases, the pSNA component that detected the failure terminates. When the local node is initializing, the pSNA component that issued the RAS function that failed usually terminates.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The RAS component encountered an error while issuing a message. The message identified in this log record cannot be issued and is lost.
Possible causes are:
Function Degradation: The request being processed is rejected, resulting in the loss of the message being issued. Additional log entries or messages are usually created to identify the specific problem that caused the request to fail.
In some cases, the pSNA component that detected the failure terminates. When the local node is initializing, the pSNA component that issued the RAS function that failed usually terminates.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The RAS component encountered an error while retrieving NLS-enabled text data. The NLS string identified in this log record cannot be retrieved.
Most of the time, NLS data is retrieved while formatting a log or trace record. If this error occurs while formatting one of those records, the log or trace record is not created and the data is lost.
Possible causes are:
Function Degradation: The request being processed is rejected, resulting in the loss of the data being retrieved. Additional log entries or messages are usually created to identify the specific problem that caused the request to fail. This error may result in the loss of RAS information, such as log or trace records. If this occurs, corresponding log records are created:
In some cases, the pSNA component that detected the failure terminates. When the local node is initializing, the pSNA component that issued the RAS function that failed usually terminates.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The RAS component encountered an error while formatting a trace record. The trace record identified in this log record cannot be stored in the trace files and is lost.
Possible causes are:
Function Degradation: The request being processed is rejected, resulting in the loss of the data currently being traced. Additional log entries or messages are usually created to identify the specific problem that caused the request to fail.
In some cases, the pSNA component that detected the failure terminates. When the local node is initializing, the pSNA component that issued the RAS function that failed usually terminates.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The RAS component encountered an error while storing a trace record in the trace files. The trace record identified in this log record cannot be stored in the trace file and is lost.
Possible causes are:
Function Degradation: The request being processed is rejected, resulting in the loss of the data currently being traced. Additional log entries or messages are usually created to identify the specific problem that caused the request to fail.
In some cases, the pSNA component that detected the failure terminates. When the local node is initializing, the pSNA component that issued the RAS function that failed usually terminates.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The RAS component encountered an error while attempting to format and store trace data. The trace record could not be stored because the specified destination for the data is temporarily unavailable.
The destination has been locked and no data can currently be stored in its buffers. This is usually a temporary condition that the RAS component can recovers from. This error is logged when the destination is locked for an unacceptable amount of time (usually greater than 30 seconds).
Possible causes are:
Function Degradation: The request being processed is rejected, resulting in the loss of the data currently being traced. Additional log entries or messages are usually created to identify the specific problem that caused the request to fail. The log record 1F100000-00000006 contains the major and minor codes of the event that could not be traced.
In some cases, the pSNA component that detected the failure terminates. Even if the component does not terminate immediately, the severity of the error will probably cause the component to terminate later. When the local node is initializing, the pSNA component that issued the RAS function that failed usually terminates.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The RAS component encountered an error while automatically flushing buffered trace data to the trace files. Some or all of the trace records currently in the internal trace data cache cannot be stored in the trace file and are lost.
Possible causes are:
Function Degradation: All data that can be successfully stored is copied from the trace cache to the trace data files. The remaining data in the internal trace data cache is purged, resulting in the loss of that portion of the trace data. The RAS component continues to gather trace data after purging the data cache. Additional log entries or messages are usually created to identify the specific problem that prevented the successful storing of the cached trace data. to fail.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The RAS component encountered an error while retrieving NLS-enabled text data. The NLS string identified in this log record cannot be retrieved.
Most of the time, NLS data is retrieved while formatting a log or trace record. If this error occurs while formatting one of those records, the log or trace record is not created and the data is lost.
Possible causes are:
Function Degradation: The request being processed is rejected, resulting in the loss of the data being retrieved. Additional log entries or messages are usually created to identify the specific problem that caused the request to fail (this error is usually logged in conjunction with 1F100000-00000005). This error may result in the loss of RAS information, such as log or trace records. If this occurs, corresponding log records are created:
In some cases, the pSNA component that detected the failure terminates. When the local node is initializing, the pSNA component that issued the RAS function that failed usually terminates.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The RAS component encountered an error while flushing buffered trace data to the trace files. Some or all of the trace records currently in the internal trace data cache cannot be stored in the trace file and are lost.
Possible causes are:
This problem can occur when the RAS component is automatically flushing the trace data cache (in which case log record 1F100000-00000009 is also created) or when the RAS component is requested to flush the trace data in the internal trace data cache.
Function Degradation: All data that can be successfully stored is copied from the trace cache to the trace data files. The remaining data in the internal trace data cache is purged, resulting in the loss of that portion of the trace data. The RAS component continues to gather trace data after purging the data cache. Additional log entries or messages are usually created to identify the specific problem that prevented the successful storing of the cached trace data. to fail.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The RAS component encountered an error while attempting to format and store trace data. The trace record could not be stored because the system trace data cache or system trace files are not defined or available.
Possible causes are:
Function Degradation: The request being processed is rejected, resulting in the loss of the data currently being traced. Additional log entries or messages are usually created to identify the specific problem that caused the request to fail. The log record 1F100000-00000006 contains the major and minor codes of the event that could not be traced.
In some cases, the pSNA component that detected the failure terminates. Even if the component does not terminate immediately, the severity of the error will probably cause the component to terminate later. When the local node is initializing, the pSNA component that issued the RAS function that failed usually terminates.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
If the problem was not caused by a system failure or resource shortage, the problem was probably caused by a problem in the communications support in the local node. Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA.
Storage management log events used by all components of pSNA.
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: A pSNA component could not obtain enough memory (storage) to perform a function. The probable causes are:
Function Degradation: The resulting system action depends on the pSNA component that detected the error and the request being processed when the error occurred. In almost all cases, the request being processed fails and in some cases, is rejected. In many cases, the pSNA component that detected the failure terminates. Even if the component does not terminate immediately, the severity of the error will probably cause the component to abend.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
The problem was probably caused by a shortage of available memory in the local node. Increase the amount of memory available to the node and re-start the node.
If the problem was not caused by a memory shortage, the problem was probably caused by a problem in the communications support in the local node. Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA.
Additional Data: Has the following format:
Description: A pSNA component could not obtain enough memory (storage) to perform a function. The probable causes are:
Function Degradation: The resulting system action depends on the pSNA component that detected the error and the request being processed when the error occurred. In almost all cases, the request being processed fails and in some cases, is rejected. In many cases, the pSNA component that detected the failure terminates. Even if the component does not terminate immediately, the severity of the error will probably cause the component to abend.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
The problem was probably caused by a shortage of available memory in the local node. Increase the amount of memory available to the node and re-start the node.
If the problem was not caused by a memory shortage, the problem was probably caused by a problem in the communications support in the local node. Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA.
Additional Data: Has the following format:
Description: A pSNA component could not access the shared memory (storage) needed perform a function. The probable causes are:
Function Degradation: The resulting system action depends on the pSNA component that detected the error and the request being processed when the error occurred. In almost all cases, the request being processed fails and in some cases, is rejected. In many cases, the pSNA component that detected the failure terminates. Even if the component does not terminate immediately, the severity of the error will probably cause the component to abend.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
If the problem was not caused by a system failure or resource shortage, the problem was probably caused by a problem in the communications support in the local node. Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA.
System error log events used by all components of pSNA.
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: A system function failed. A pSNA component encountered a system error while processing a request.
Function Degradation: The failing system function could be recovered from or ignored. The pSNA component continues to process the request. Unexpected behaviour may follow this problem, since not all expected functions may have been performed.
In some severe cases, if the recovery is not possible, the detecting pSNA component terminates or abends.
Customer Action: The local node attempts to recover from the problem and continues processing. In some cases, the recovery is successful and no action is required.
If the node did not recover successfully, or the subsequent behaviour of the local node is erratic, try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A system function failed. A pSNA component encountered a system error while processing a request. The encountered error is recoverable. The pSNA component will retry the function that failed.
Function Degradation: The failing system function is recoverable. The pSNA component retries the function that failed and if successful, continues to process the request. Unexpected behaviour may follow this problem, especially if the error recovery procedures fail. In most cases, if the system function can not be executed, the log record 26100000-00000003 is created.
In some severe cases, if the recovery is not possible, the detecting pSNA component terminates or abends.
Customer Action: The local node attempts to recover from the problem and continues processing. In some cases, the recovery is successful and no action is required.
If the node did not recover successfully, or the subsequent behaviour of the local node is erratic, try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A system function failed. A pSNA component encountered a system error while processing a request. Either the encountered error is not recoverable, or the retry limit for the function has been reached.
Function Degradation: The resulting system action depends on the pSNA component that detected the error and the request being processed when the error occurred. In almost all cases, the request being processed fails and in some cases, is rejected. In many cases, the pSNA component that detected the failure terminates. Even if the component does not terminate immediately, the severity of the error may cause the component to abend.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages). If the error was recoverable but the retry limit for the failing function was reached, one or more log records 26100000-00000002 may have been created.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Description: None.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Software error log events used by all components of pSNA.
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: A pSNA component encountered a should-not-occur condition while processing a request. An internal function was invoked with conflicting or invalid parameters. An internal code problem exists within pSNA.
Function Degradation: The resulting system action depends on the pSNA component that detected the error and the request being processed when the error occurred. In almost all cases, the request being processed fails and in some cases, is rejected. In many cases, the pSNA component that detected the failure terminates. Even if the component does not terminate immediately, the severity of the error will probably cause the component to abend.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA.
Additional Data: Has the following format:
Description: A pSNA component encountered a should-not-occur condition while processing a request. An internal function was invoked with an invalid or unexpected parameter. An internal code problem exists within pSNA.
Function Degradation: The resulting system action depends on the pSNA component that detected the error and the request being processed when the error occurred. In almost all cases, the request being processed fails and in some cases, is rejected. In many cases, the pSNA component that detected the failure terminates. Even if the component does not terminate immediately, the severity of the error will probably cause the component to abend.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA.
Additional Data: Has the following format:
Description: A pSNA component encountered a should-not-occur condition while processing a request. An internal value is invalid (the value in a switch statement is invalid). An internal code problem exists within pSNA.
Function Degradation: The resulting system action depends on the pSNA component that detected the error and the request being processed when the error occurred. In almost all cases, the request being processed fails and in some cases, is rejected. In many cases, the pSNA component that detected the failure terminates. Even if the component does not terminate immediately, the severity of the error will probably cause the component to abend.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA.
Additional Data: Has the following format:
Description: A pSNA component received an internal inter-process signal it does not recognize (or process). This condition should not occur, since the unrecognized signal should not have been routed to the component for processing. An internal code problem exists within pSNA.
Function Degradation: The resulting system action depends on the pSNA component that detected the error and the request being processed when the error occurred. In almost all cases, the unrecognized IPS is ignored, and the component continues to process other signals. Unexpected results will probably follow this problem, since one or more node components are probably in error and out of sequence.
In some cases, the pSNA component that detected the failure terminates.
Customer Action: Call service with the code point, error description, and abend code value if available. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
If possible, try and re-create the problem with traces enabled for the component that detected the error and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: A pSNA component encountered a should-not-occur condition. An internal code problem exists within pSNA.
Function Degradation: The resulting system action depends on the pSNA component that detected the error and the request being processed when the error occurred. In almost all cases, the request being processed fails and in some cases, is rejected. In many cases, the pSNA component that detected the failure terminates. Even if the component does not terminate immediately, the severity of the error will probably cause the component to abend.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA.
Log events for the configuration services component of APPN (CS).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: The DLC FSM encountered an unrecognized/unexpected input.
The DLC FSM received an unexpected or unrecognized input value. The probable causes are:
Function Degradation: The input value is ignored, and processing continues. Unexpected results will probably follow this problem, since CS and a DLC are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine if the received input value was invalid or was unexpected. If invalid, implement a code fix eliminating the invalid input value (possibly replacing it with a valid value). If unexpected, implement a code fix to the DLC FSM to handle the input value while in the indicated state.
Additional Data: Has the following format:
Description: The link station FSM encountered an unrecoverable error (should-not-occur condition).
The link station FSM encountered a should-not-occur situation. The probable causes are:
Function Degradation: The input value is ignored, and processing continues. Unexpected results will probably follow this problem, since CS and a link station are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Implement code fix.
Additional Data: Has the following format:
Description: The link station FSM encountered a normal race condition. An inbound activation request was received for a link station at the same time the node was attempting to activate the link station with an outbound request.
The pSNA node was in the process of attempting to establish a connection with a remote node (link station outbound activation request) when an inbound activation request was received from the same remote node for the same link station. This is a normal race condition that can be avoided, but is recoverable.
Function Degradation: The outbound connection request is rejected with a X'C3E2F4F8' sense code, but the node continues by processing the inbound connection attempt. If successfully processed, communications is established via the inbound connection attempt. The only undesired side-affect is that the link-station is changed to a link-station used for inbound requests, not outbound requests.
Customer Action: If the connection is established, ensure that the established connection's characteristics are valid and usable (e.g. CP-CP session support, BTU sizes, etc.). If not satisfactory, terminate the connection and retry initiating it from the local node. To prevent these collisions, change the network definitions in the nodes so that only one node will attempt to establish the connection.
System Developer Action: None.
Additional Data: Has the following format:
Description: A connection was unexpectedly terminated by the remote node or because a communications error occurred.
An established connection or a connection in the process of being established was unexpectedly terminated. The most probable causes are:
If the condition is an alert-able condition, such as a hardware error, the detecting DLC will generate an alert indicating the specific cause of the problem.
Function Degradation: The connection, along with any related sessions, are terminated. Communications with the remote node via this link station are no longer available. Depending on why the connection was terminated, the node may try and re-establish the connection later.
Customer Action: Determine why the connection was unexpectedly terminated and remedy the situation. If not automatically recovered by the node, try and re-initiate the connection.
System Developer Action: None.
Additional Data: Has the following format:
Description: A connection was unexpectedly terminated by the local DLC support because an alert-able situation was detected
An established connection or a connection in the process of being established was unexpectedly terminated. The most probable causes are:
Function Degradation: The connection, along with any related sessions, are terminated. Communications with the remote node via this link station or no longer available. Depending on why the connection was terminated, the node may try and re-establish the connection later.
Customer Action: Determine why the connection was unexpectedly terminated and remedy the situation. The information contained in the alert generated by the DLC support will indicate the specific cause of the problem, along with any recommended actions. If not automatically recovered by the node, try and re-initiate the connection.
System Developer Action: None.
Additional Data: Has the following format:
Description: The port FSM encountered an unrecoverable error (should-not-occur condition).
The port FSM encountered a should-not-occur situation. The probable causes are:
Function Degradation: The input value is ignored, and processing continues. Unexpected results will probably follow this problem, since CS and a port are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Implement code fix.
Additional Data: Has the following format:
Description: The port received an unrecognized/unexpected input.
The port FSM received an unexpected or unrecognized input value. The probable causes are:
Function Degradation: The input value is ignored, and processing continues. Unexpected results will probably follow this problem, since CS and a port are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine if the received input value was invalid or was unexpected. If invalid, implement a code fix eliminating the invalid input value (possibly replacing it with a valid value). If unexpected, implement a code fix to the port FSM to handle the input value while in the indicated state.
Additional Data: Has the following format:
Description: The port FSM encountered an unrecoverable error (should-not-occur condition).
The port FSM outputted an unknown or invalid action code. The probable causes are:
Function Degradation: The input value is ignored, and processing continues. Unexpected results will probably follow this problem, since CS and a port are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Implement code fix.
Additional Data: Has the following format:
Description: The link station identified in the received response does not exist.
CS received an ACTIVATE_AS_RSP IPS specifying a link station control block that is invalid or no longer exists. This condition should not occur. An internal code problem exists within pSNA.
Function Degradation: The ACTIVATE_AS_RSP IPS is ignored, and processing continues. Unexpected results will probably follow this problem, since CS is probably in error and out of sequence.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS and ASM traces enabled and supply that trace information with the problem.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: An attempt to activate a route to the indicated node failed.
An attempt to activate a route to the indicated node failed (the route being a connection network TG, link TG, or local TG). The sense code specifies the error encountered. The most probable causes are:
Function Degradation: The indicating route is not activated. The session triggering the route being activated fails.
Customer Action: Determine why the route could not be activated and remedy the situation. When fixed, re-start the failed session(s).
System Developer Action: None.
Additional Data: Has the following format:
Description: The link station identified in the received IPS does not exist.
CS received an AS_DEACTIVATED IPS from ASM specifying a link station control block that is invalid or no longer exists. This condition should not occur. An internal code problem exists within pSNA.
Function Degradation: The AS_DEACTIVATED IPS is ignored, and processing continues. Unexpected results will probably follow this problem, since CS is probably in error and out of sequence. Most probable symptoms are resources not being cleaned up or available for re-use.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS and ASM traces enabled and supply that trace information with the problem.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: CS received an XID from a DLC for an undefined or inactive port.
CS received an incoming XID from a DLC for a port that is not defined to CS or is inactive (according to CS). This condition should never occur, with the one exception that a race condition exists where the DLC is forwarding the XID just as CS is deactivating the port. This condition should not occur. An internal code problem exists within pSNA.
Function Degradation: The received XID is ignored. The remote node will eventually time-out and re-try the XID or stop trying to activate a link to the local node.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS, DLC, and data traces enabled and supply that trace information with the problem.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: CS failed to initialize. The TG for local path control could not be created.
Initialization of the CS component failed. The request to create the local path control TG failed with the indicated return code. This condition should never occur, unless a serious memory shortage problem exists. This condition should not occur. An internal code problem exists within pSNA, UNLESS a memory shortage was detected.
Function Degradation: The pSNA node aborts its initialization and stops. No APPC/APPN communication services are available.
Customer Action: Verify that a memory shortage did not cause the problem. If not related to a memory shortage, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS and path control traces enabled and supply that trace information with the problem.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: CS failed to initialize. The address space for local path control could not be created.
Initialization of the CS component failed. The request to create the local path control address space failed. The cause of the failure is indicated by the sense code. This condition should never occur, unless a serious memory shortage problem exists. This condition should not occur. An internal code problem exists within pSNA, UNLESS a memory shortage was detected.
Function Degradation: The pSNA node aborts its initialization and stops. No APPC/APPN communication services are available.
Customer Action: Verify that a memory shortage did not cause the problem. If not related to a memory shortage, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS and ASM traces enabled and supply that trace information with the problem.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: CS completed the attempt to activate a link station on behalf of a request received from NOF (an operator).
CS completed processing a NOF request to activate a link station (or during start-up, all activate-at-startup link stations). This log entry indicates the results of that attempt. If the response is positive (sense code equal zero), the link station(s) was successfully started and is now available for use. If the sense code is not zero, the activation attempt failed and the sense code specifies the error encountered. The most probable causes are:
Function Degradation: If the attempt failed, the indicating link station is not activated. The operator request that triggered the request from NOF fails. During node start-up, a failure indicates that one or more of the activate-at-startup links did not activate.
Customer Action: Determine why the link could not be activated and remedy the situation. When fixed, re-issue the request to start the link station. If the error occurred during node start-up, re-activate all links that were not activated.
System Developer Action: None.
Additional Data: Has the following format:
Description: The FSM governing non-activation XID3 exchanges for primary link stations encountered an unrecoverable error (should-not-occur condition).
The FSM governing non-activation XID3 exchanges for primary link stations outputted an unknown or invalid action code. The probable causes are:
Function Degradation: Configuration services abends, effectively terminating the node.
Customer Action: Call service with the code point, error description, and abend code value if possible. Supply any pSNA dump information. If possible, try and re-create the problem with CS and data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Implement code fix to handle the unexpected sequence or input. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The FSM governing non-activation XID3 exchanges for secondary link stations encountered an unrecoverable error (should-not-occur condition).
The FSM governing non-activation XID3 exchanges for secondary link stations encountered a should-not-occur condition. The probable causes are:
This condition should not occur, since the FSM should be robust enough to handle any valid input in any valid sequence. An internal code problem exists within pSNA. The remote node can also cause this problem by sending an XID out of sequence or with invalid parameters. The FSM should be robust enough to handle any condition, except blatant protocol violations.
Function Degradation: Configuration services abends, effectively terminating the node.
Customer Action: Call service with the code point, error description, and abend code value if possible. Supply any pSNA dump information. If possible, try and re-create the problem with CS and data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Implement code fix to handle the unexpected sequence or input. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The FSM governing non-activation XID3 exchanges for secondary link stations encountered an unrecoverable error (should-not-occur condition).
The FSM governing non-activation XID3 exchanges for secondary link stations outputted an unknown or invalid action code. The probable causes are:
Function Degradation: Configuration services abends, effectively terminating the node.
Customer Action: Call service with the code point, error description, and abend code value if possible. Supply any pSNA dump information. If possible, try and re-create the problem with CS and data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Implement code fix to handle the unexpected sequence or input. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The FSM governing link activation XID3 exchanges encountered an unrecoverable error (should-not-occur condition).
The link activation XID3 FSM received an unexpected or unrecognized input value. The probable causes are:
Function Degradation: Configuration services abends, effectively terminating the node.
Customer Action: Call service with the code point, error description, and abend code value if possible. Supply any pSNA dump information. If possible, try and re-create the problem with CS and data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: The TG number negotiation FSM encountered an unrecoverable error (should-not-occur condition).
The TG number negotiation FSM encountered a for secondary link stations encountered a should-not-occur condition. The probable causes are:
Function Degradation: Configuration services abends, effectively terminating the node.
Customer Action: Call service with the code point, error description, and abend code value if possible. Supply any pSNA dump information. If possible, try and re-create the problem with CS and data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Implement code fix to handle the unexpected sequence or input. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The TG number negotiation FSM encountered an unrecoverable error (should-not-occur condition).
The TG number negotiation FSM outputted an unknown or invalid action code. The probable causes are:
Function Degradation: Configuration services abends, effectively terminating the node.
Customer Action: Call service with the code point, error description, and abend code value if possible. Supply any pSNA dump information. If possible, try and re-create the problem with CS and data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Implement code fix to handle the unexpected sequence or input. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The link station FSM encountered an unrecoverable error (should-not-occur condition).
The link station FSM outputted an unknown or invalid action code. The probable causes are:
Function Degradation: The input value is ignored, and processing continues. Unexpected results will probably follow this problem, since CS and a link station are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Implement code fix to handle the unexpected sequence or input.
Additional Data: Has the following format:
Description: The FSM governing link activation XID3 exchanges encountered an unrecoverable error (should-not-occur condition).
The link station FSM received an unexpected or unrecognized input value (IPS). The probable causes are:
Function Degradation: None.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: The CS component encountered an alert-able condition.
The configuration services component detected an external error and generated an alert to be sent to the SNA/MS alert focal point. The sense code indicates the type of error encountered. The SNA/MS reference lists the alerts that are generated by the CS component of APPN. MS will try and forward the alert to the alert focal point, and will also log the contents of the alert in the local system log. Any XID data associated with the alert is logged separately in log records 2F101000-0000001E, 2F101000-0000001F, 2F101000-00000020, or 2F101000-00000021.
Function Degradation: None.
Customer Action: Use the sense code and logged alert data to determine the cause of the problem and remedy the situation. If the customer cannot determine the cause of the problem, call service with the code point, error description, and logged data. If possible, try and re-create the problem with CS and data traces enabled and supply that trace information with the problem.
System Developer Action: Use the sense code and logged alert data to determine the cause of the problem and remedy the situation.
Additional Data: Has the following format:
Description: This log record is used to log any associated outbound XID data associated with the alert indicated by the accompanying log record 2F101000-0000001D.
This log record is used to log any outbound XID (or related) data associated with the log record 2F101000-0000001D. The length of the XID is < 29. In particular, this log record is used to log any additional information when an outbound XID is not available. See the description of log record 2F101000-0000001D for more information.
Function Degradation: None.
Customer Action: Combine this information with the information contained in 2F101000-0000001D (and any other associated log records) to determine the cause of the problem. See the description of log record 2F101000-0000001D for more information. If the customer cannot determine the cause of the problem, call service with the code point, error description, and logged data. If possible, try and re-create the problem with CS and data traces enabled and supply that trace information with the problem.
System Developer Action: Combine this information with the information contained in 2F101000-0000001D (and any other associated log records) to determine the cause of the problem. See the description of log record 2F101000-0000001D for more information.
Additional Data: Has the following format:
Description: This log record is used to log any associated outbound XID data associated with the alert indicated by the accompanying log record 2F101000-0000001D.
This log record is used to log the outbound XID data associated with the log record 2F101000-0000001D. The length of the XID is >= 29. In particular, this log record is used when outbound XID data is available. See the description of log record 2F101000-0000001D for more information.
Function Degradation: None.
Customer Action: Combine this information with the information contained in 2F101000-0000001D (and any other associated log records) to determine the cause of the problem. See the description of log record 2F101000-0000001D for more information. If the customer cannot determine the cause of the problem, call service with the code point, error description, and logged data. If possible, try and re-create the problem with CS and data traces enabled and supply that trace information with the problem.
System Developer Action: Combine this information with the information contained in 2F101000-0000001D (and any other associated log records) to determine the cause of the problem. See the description of log record 2F101000-0000001D for more information.
Additional Data: Has the following format:
Description: This log record is used to log any associated inbound XID data associated with the alert indicated by the accompanying log record 2F101000-0000001D.
This log record is used to log any inbound XID (or related) data associated with the log record 2F101000-0000001D. The length of the XID is < 29. In particular, this log record is used to log any additional information when an inbound XID is not available. See the description of log record 2F101000-0000001D for more information.
Function Degradation: None.
Customer Action: Combine this information with the information contained in 2F101000-0000001D (and any other associated log records) to determine the cause of the problem. See the description of log record 2F101000-0000001D for more information. If the customer cannot determine the cause of the problem, call service with the code point, error description, and logged data. If possible, try and re-create the problem with CS and data traces enabled and supply that trace information with the problem.
System Developer Action: Combine this information with the information contained in 2F101000-0000001D (and any other associated log records) to determine the cause of the problem. See the description of log record 2F101000-0000001D for more information.
Additional Data: Has the following format:
Description: This log record is used to log any associated inbound XID data associated with the alert indicated by the accompanying log record 2F101000-0000001D.
This log record is used to log the inbound XID data associated with the log record 2F101000-0000001D. The length of the XID is >= 29. In particular, this log record is used when inbound XID data is available. See the description of log record 2F101000-0000001D for more information.
Function Degradation: None.
Customer Action: Combine this information with the information contained in 2F101000-0000001D (and any other associated log records) to determine the cause of the problem. See the description of log record 2F101000-0000001D for more information. If the customer cannot determine the cause of the problem, call service with the code point, error description, and logged data. If possible, try and re-create the problem with CS and data traces enabled and supply that trace information with the problem.
System Developer Action: Combine this information with the information contained in 2F101000-0000001D (and any other associated log records) to determine the cause of the problem. See the description of log record 2F101000-0000001D for more information.
Additional Data: Has the following format:
Description: CS failed to successfully activate a route. The address space for the TG could not be created.
Activation of the indicated route failed. The request to create the TG's address space failed. The cause of the failure is indicated by the sense code. The most probable cause of this problem is memory could not be allocated for the new address space.
Function Degradation: The indicated route fails to activate. Any sessions planning on using this route cannot be started. CS will try and activate the route again when another request is received for the related TG.
Customer Action: Determine if a memory shortage caused the problem. Investigate the amount of memory being used by the pSNA node and determine if the node is experiencing memory shortages. If the customer does not suspect a memory shortage problem, dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS and ASM traces enabled and supply that trace information with the problem.
System Developer Action: If a memory shortage is not the cause of the problem, investigate and implement a code fix.
Additional Data: Has the following format:
Description: The connection network TG FSM encountered an unrecoverable error (should-not-occur condition) and CS abended.
The connection network TG FSM outputted an unknown or invalid action code. The probable causes are:
An internal code problem exists within pSNA. Configuration services abends, effectively terminating the node.
Function Degradation: Configuration services abends, effectively terminating the node.
Customer Action: Call service with the code point, error description, and abend code value if possible. Supply any pSNA dump information. If possible, try and re-create the problem with CS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Implement code fix.
Additional Data: Has the following format:
Description: The CS component encountered an alert-able condition.
The configuration services component detected an external error and attempted to generated an alert to be sent to the SNA/MS alert focal point. The alert could not be sent because the data link control (DLC) control block associated with the alert cannot be determined. An internal code problem exists within pSNA.
Function Degradation: Processing continues.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS and data traces enabled and supply that trace information with the problem.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: Configuration services (CS) encountered an unrecoverable error (should-not-occur condition).
CS received an invalid DLC command from a data link control (DLC) component. The link station identifier contained in the command is invalid (it does not reference a valid link station). An internal code problem exists within pSNA.
Function Degradation: None.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS traces enabled and supply that trace information with the problem.
System Developer Action: Implement a code fix within the DLC component so that it does not send invalid link station identifiers. If the received link station identifier should have been valid, fix CS so it does not lose link stations.
Additional Data: Has the following format:
Description: Configuration services (CS) encountered an unrecoverable error (should-not-occur condition).
CS received an invalid DLC command from a data link control (DLC) component. The port identifier contained in the command is invalid (it does not reference a valid port). An internal code problem exists within pSNA.
Function Degradation: None.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS traces enabled and supply that trace information with the problem.
System Developer Action: Implement a code fix within the DLC component so that it does not send invalid port identifiers. If the received port identifier should have been valid, fix CS so it does not lose ports.
Additional Data: Has the following format:
Description: The APPN configuration services component (CS) received an unexpected internal inter-process signal.
The IPS was received before CS was ready to process the received message. This condition should not occur, since the unrecognized signal should not have been routed to CS for processing. An internal code problem exists within pSNA. CS received the unexpected IPS while waiting for the following:
Function Degradation: The unexpected IPS is ignored, and CS continues to process other signals. Unexpected results will probably follow this problem, since CS or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: APPN configuration services (CS) encountered an error while attempting to start a port on an attached co-processor (subsystem). CS could not retrieve the internal ID used to communicate with the attached subsystem. The possible causes of this problem are:
Function Degradation: Configuration services rejects the request to start the indicated port.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: APPN configuration services (CS) encountered an error while attempting to start a port on an attached co-processor (subsystem). CS could not establish a connection (dialog) with the DLC component in the attached subsystem. The possible causes of this problem are:
Function Degradation: Configuration services rejects the request to start the indicated port.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: APPN configuration services (CS) encountered an error while attempting to start a port on an attached co-processor (subsystem). CS could not retrieve the internal ID used to identify the path control component associated with the attached subsystem. The possible causes of this problem are:
Function Degradation: Configuration services rejects the request to start the indicated port.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The CCE (Discovery) Client FSM encountered an unrecognized/unexpected input.
The CCE Client FSM received an unexpected or unrecognized input value. The probable causes are:
Function Degradation: The input value is ignored, and processing continues. Unexpected results will probably follow this problem, since CS and CCE (Discovery) are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine if the received input value was invalid or was unexpected. If invalid, implement a code fix eliminating the invalid input value (possibly replacing it with a valid value). If unexpected, implement a code fix to the CCE Client FSM to handle the input value while in the indicated state.
Additional Data: Has the following format:
Description: The CCE (Discovery) Client FSM encountered an unrecoverable error (should-not-occur condition).
The CCE Client FSM encountered a should-not-occur situation. The probable causes are:
Function Degradation: The input value is ignored, and processing continues. Unexpected results will probably follow this problem, since CS and CCE (Discovery) are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Implement code fix.
Additional Data: Has the following format:
Description: A request sent to the CCE (Discovery) component failed.
CS encountered a problem either in registering network servers with the CCE (Discovery) component or in attempting to dynamically discover a network server with which to establish a CP-CP session. The details of the error are indicated by the primary and secondary return codes found in the response. This condition should not occur. An internal code problem exists within pSNA.
Function Degradation: If CS is processing a Set_Discovery_Server verb when the problem is encountered, the verb is returned to the issuing transaction program with the return code fields set appropriately. If CS is attempting to dynamically discover a network node server, no CP-CP session is established.
Customer Action: Use the information in the response (especially the primary and secondary return codes) to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local node.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A destination address table entry for an ATMSVC link was not found.
CS could not find the entry for the destination address for a defined ATM SVC link. Either the last defined link to this address was already deleted or there is some memory corruption. This condition should not occur. An internal code problem exists within pSNA.
Function Degradation: If CS is activating a link when the problem is encountered, the link continues to activate, but the CS internal table which tracks destination addresses for ATM SVC's has been corrupted. If CS is deleting a link, the link continues to delete. The table may or may not be corrupted.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The duplicate address FSM encountered an unrecoverable error (should-not-occur condition) due to a configuration error.
The duplicate address FSM encountered a should-not-occur situation. The probable causes are:
Function Degradation: The input value is ignored, and processing continues. Unexpected results will probably follow this problem, since CS and a destination address of an ATM SVC link station are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what action code and input value caused the FSM to abend.
Additional Data: Has the following format:
Description: The duplicate address FSM encountered a configuration error
The duplicate address FSM encountered a configuration error while processing an ATM SVC link. The probable causes are:
Function Degradation: The input value is ignored, and processing continues. Unexpected results will probably follow this problem, since CS and an ATM SVC link station's configuration are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what action code and input value caused the FSM to abend.
Additional Data: Has the following format:
Description: The duplicate address FSM encountered an unrecoverable error (should-not-occur condition).
The duplicate address FSM outputted an unknown or invalid action code. The probable causes are:
Function Degradation: The input value is ignored, and processing continues. Unexpected results will probably follow this problem, since CS and a port are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Implement code fix.
Additional Data: Has the following format:
Description: The DEFINE_LS request was rejected. The reason is specified by the sense code returned.
The probable cause is invalid parameter when defining the link.
Function Degradation: The define_ls is ignored, and processing continues. Unexpected results may follow this problem, since CS will not have prior knowledge of the link the user was trying to define.
Customer Action: Correct the definition error.
System Developer Action: Debug and determine the define link parameter in error from the sense code returned.
Additional Data: Has the following format:
Description: The local link station FSM encountered an unrecoverable error (should-not-occur condition).
The local link station FSM encountered a should-not-occur situation. The probable causes are:
Function Degradation: The input value is ignored, and processing continues. Unexpected results will probably follow this problem, since CS and a local link station are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Implement code fix.
Additional Data: Has the following format:
Description: The FSM governing link activation XID3 exchanges encountered an unrecoverable error (should-not-occur condition).
The local link station FSM received an unexpected or unrecognized input value (IPS). The probable causes are:
Function Degradation: None.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: The local link station FSM encountered an unrecoverable error (should-not-occur condition).
The local link station FSM encountered a should-not-occur situation. The probable causes are:
Function Degradation: None.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: CS failed to successfully activate a route. The address space for the TG could not be created.
Activation of the indicated route failed. The request to create the TG's address space failed. The cause of the failure is indicated by the sense code. The most probable cause of this problem is memory could not be allocated for the new address space.
Function Degradation: The indicated route fails to activate. Any sessions planning on using this route cannot be started. CS will try and activate the route again when another request is received for the related TG.
Customer Action: Determine if a memory shortage caused the problem. Investigate the amount of memory being used by the pSNA node and determine if the node is experiencing memory shortages. If the customer does not suspect a memory shortage problem, dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS and ASM traces enabled and supply that trace information with the problem.
System Developer Action: If a memory shortage is not the cause of the problem, investigate and implement a code fix.
Additional Data: Has the following format:
Description: The local link station identified in the received response does not exist.
CS received an ACTIVATE_AS_RSP IPS specifying a local link station control block that is invalid or no longer exists. This condition should not occur. An internal code problem exists within pSNA.
Function Degradation: The ACTIVATE_AS_RSP IPS is ignored, and processing continues. Unexpected results will probably follow this problem, since CS is probably in error and out of sequence.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CS and ASM traces enabled and supply that trace information with the problem.
System Developer Action: Isolate and implement code fix.
Log events for the directory services component of APPN (DS).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: Directory services (DS) received an internal inter-process signal it does not recognize (or process).
The directory services internal search routine received an IPS that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to the directory service search routines. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services (DS) received an invalid inter-process signal (LOCATE_MESSAGE).
Directory services received an invalid LOCATE_MESSAGE IPS. The appropriate search FSM could not be determined from the data in the signal. An internal code problem exists within pSNA.
Function Degradation: The invalid IPS is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services (DS) received an invalid inter-process signal, which caused a should-not-occur condition.
Directory services received an invalid LOCATE_MESSAGE IPS. The appropriate search FSM could not be determined from the data in the signal. The directory services routine used to determine the search FSM returned an invalid value. An internal code problem exists within pSNA (DS).
Function Degradation: The invalid IPS is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services (DS) received an invalid inter-process signal (UPDATE_DIRECTORY).
Directory services received an invalid UPDATE_DIRECTORY (type=DELETE) IPS. The resource type could not be determined from the resource descriptor in the signal. An internal code problem exists within pSNA.
Function Degradation: The invalid IPS is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS or another node component (NOF) are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services (DS) received an invalid inter-process signal (UPDATE_DIRECTORY).
Directory services received an invalid UPDATE_DIRECTORY (type=UPDATE or ADD) IPS. The resource hierarchy contained in the signal's resource descriptor is invalid. An internal code problem exists within pSNA.
Function Degradation: The invalid IPS is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS or another node component (NOF) are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: The CP status FSM encountered an unexpected CP_STATUS IPS.
The CP status FSM received an unexpected input value. The probable causes are:
Function Degradation: The input value is ignored, and processing continues. Unexpected results will probably follow this problem, since DS and a node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: The CP status FSM encountered an unrecoverable error (should-not-occur condition).
The CP status FSM outputted an unknown or invalid action code. The probable causes are:
Function Degradation: The input value is ignored, and processing continues. Unexpected results will probably follow this problem, since DS and another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Implement code fix.
Description: Directory services encountered a should-not-occur condition within the component. An internal control block is invalid.
A resource hierarchy control block in the directory is invalid. It does not contain a network node name or end node name. An internal code problem exists within pSNA (DS).
Function Degradation: The input value is ignored, and processing continues. Unexpected results will probably follow this problem, since the data in the directory is corrupted.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services encountered a should-not-occur condition within the component. An internal control block is invalid.
A resource hierarchy control block in the directory is invalid. It does not contain a LU name. An internal code problem exists within pSNA (DS).
Function Degradation: The input value is ignored, and processing continues. Unexpected results will probably follow this problem, since the data in the directory is corrupted.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services detected two adjacent nodes with the same control point name.
Directory services received a CP_STATUS message to add an adjacent node to the directory. The adjacent node identified in the signal is already defined in the directory. The probable causes are:
Function Degradation: Directory services continues to process the CP_STATUS message, adding the new adjacent node to the directory (creating two adjacent node definitions with the same control point name). Unexpected results will probably follow this problem, since the directory now contains two resources with the same name. Messages may be routed to the wrong node.
Customer Action: Try and determine if the problem was caused by a network definition error or a software error.
Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services encountered a should-not-occur condition within the component. An internal control block is invalid.
An adjacent node record in the directory is invalid. It does not contain a valid "eyecatcher". An internal code problem exists within pSNA (DS).
Function Degradation: Directory services continues to process requests. Unexpected results will probably follow this problem, since the data in the directory is corrupted.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services encountered a should-not-occur condition within the component. An internal control block is invalid.
An internal code problem exists within the directory services component. The routine used to copy search data descriptor control blocks determined that the source control block is either not a search data descriptor or is no longer in use.
Function Degradation: Directory services continues to process requests. Unexpected results will probably follow this problem, since DS is probably in error and its internal data structures are probably corrupted.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services encountered a should-not-occur condition within the component. An internal control block is invalid.
An internal code problem exists within the directory services component. The routine used to copy search data descriptor control blocks determined that the target control block is either not a search data descriptor or is no longer in use.
Function Degradation: Directory services continues to process requests. Unexpected results will probably follow this problem, since DS is probably in error and its internal data structures are probably corrupted.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services encountered a should-not-occur condition within the component. An internal logic problem exists within DS.
An internal code problem exists within the directory services component. Duplicate search requests for the same resource have been requested (duplicate search data descriptors). Directory services should not allow this condition to occur.
Function Degradation: Directory services continues to process requests. Unexpected results will probably follow this problem, since DS is probably in error and its internal data structures are probably corrupted.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services encountered a should-not-occur condition within the component. An internal control block is invalid.
A search data descriptor is invalid. The search status indicator in the descriptor is invalid. An internal code problem exists within pSNA (DS).
Function Degradation: Directory services continues to process requests. Unexpected results will probably follow this problem, since DS is probably in error and its internal data structures are probably corrupted.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services encountered a should-not-occur condition within the component. An internal logic problem exists within DS.
An internal code problem exists within the directory services component. Duplicate locate requests have been created (duplicate locate records). Directory services should not allow this condition to occur.
Function Degradation: Directory services continues to process requests. Unexpected results will probably follow this problem, since DS is probably in error and its internal data structures are probably corrupted.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services encountered a should-not-occur condition within the component. An internal control block is invalid.
A search event request is invalid. The type of search in the request is invalid. An internal code problem exists within pSNA (DS).
Function Degradation: Directory services continues to process requests. Unexpected results will probably follow this problem, since DS is probably in error and its internal data structures are probably corrupted.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services encountered a should-not-occur condition within the component. An internal logic problem exists within DS.
An internal code problem exists within the directory services component. Duplicate locate records have been created (duplicate descriptors for the same locate request). Directory services should not allow this condition to occur.
Function Degradation: Directory services continues to process requests. Unexpected results will probably follow this problem, since DS is probably in error and its internal data structures are probably corrupted.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services encountered a should-not-occur condition within the component. An internal control block is invalid.
A locate record is invalid. The search status in the locate record is invalid. An internal code problem exists within pSNA (DS).
Function Degradation: Directory services continues to process requests. Unexpected results will probably follow this problem, since DS is probably in error and its internal data structures are probably corrupted.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services encountered a should-not-occur condition within the component. An internal control block is invalid.
A locate record is invalid. The search FSM ID (which indicates the local node's role in the search) is invalid. An internal code problem exists within pSNA (DS).
Function Degradation: Directory services continues to process requests. Unexpected results will probably follow this problem, since DS is probably in error and its internal data structures are probably corrupted.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Directory services encountered a should-not-occur condition within the component. An internal control block is invalid.
A resource descriptor is invalid. The wildcard indicator in the descriptor is invalid. An internal code problem exists within pSNA (DS).
Function Degradation: Directory services ignores the request to create a directory entry based on the invalid resource descriptor, but continues to process requests. Unexpected results will probably follow this problem, since DS is probably in error and its internal data structures are probably corrupted.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Directory services detected two resources with the same name.
Directory services received a request to add an LU to the directory, but an LU or control point is already defined in the directory with the same name. The existing entry is a home or registered entry, meaning it was explicitly placed in the directory by local or remote configuration information. The probable causes are:
Function Degradation: Directory services ignores the request to create the duplicate directory entry and continues to process requests. Unexpected results will probably follow this problem, since the network appears to contain two resources with the same name. Messages may be routed to the wrong node.
Customer Action: Try and determine if the problem was caused by a network definition error or a software error.
Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services received a request to add duplicate partial wildcard entries in the directory.
Directory services received a request to add a partial wildcard resource description to the directory, but the wildcarded LU name is already defined in the directory. The probable causes are:
Function Degradation: Directory services ignores the request to create the duplicate directory entry and continues to process requests. Unexpected results will probably follow this problem. The same set of resources is defined by more than one partial wildcard. Messages may be routed to the wrong node.
Customer Action: Try and determine if the problem was caused by a network definition error or a software error.
Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services received a request to add multiple full wildcard entries in the directory.
Directory services received a request to add a full wildcard resource description to the directory, but the directory already contains a full wildcard directory entry. Only one full wildcard entry is allowed in the directory. The probable causes are:
Function Degradation: Directory services ignores the request to create the duplicate directory entry and continues to process requests. Unexpected results will probably follow this problem. Multiple full wildcards are defined. Messages may be routed to the wrong node.
Customer Action: Try and determine if the problem was caused by a network definition error or a software error.
Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services encountered a should-not-occur condition within the component. An internal control block is invalid or a logic error exists within the DS component.
A search of the directory returned an incorrect/invalid directory entry. The search was a domain search, which should only search for resources "owned" by end nodes or migration end nodes within the domain of the network node. The returned directory entry is invalid, because its associated adjacent node record indicates that the adjacent node (which the resource is in the domain of) is a network node. An internal code problem exists within pSNA (DS).
Function Degradation: The invalid directory entry is ignored, and the search returns no found resources. Unexpected results will probably follow this problem, since the definition of the resource within the directory is invalid or directory services has a logic problem that prevents it from finding the requested resource.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Directory services encountered a should-not-occur condition within the component. An internal control block is invalid.
An adjacent node record in the directory is invalid. It does not contain a valid node type value. An internal code problem exists within pSNA (DS).
Function Degradation: Directory services continues to process requests. Unexpected results will probably follow this problem, since the data in the directory is corrupted.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: The request to open the specified dump file failed.
Directory services could not dump the resource directory. The dump file could not be opened. The possible causes of this problem are:
Function Degradation: Directory services cannot process the request to dump the resource directory. It continues to process other requests.
Customer Action: Try and determine if the problem was caused by a system and/or machine failure by investigating any related error information (such as additional log entries). If a problem is discovered in these systems, use the appropriate procedures to resolve the problem.
If it appears that all other systems are functioning correctly, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: Directory services encountered a should-not-occur condition within the component. An internal control block is invalid.
A resource directory entry is invalid. The resource location in the entry is invalid. An internal code problem exists within pSNA (DS).
Function Degradation: Directory services continues dumping the resource directory, including the invalid entry. Unexpected results will probably follow this problem, since the data in the directory is corrupted.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Directory services encountered a should-not-occur condition within the component. An internal control block is invalid.
A resource directory entry is invalid. The entry type (permanent, registered, or cached) in the entry is invalid. An internal code problem exists within pSNA (DS).
Function Degradation: Directory services continues dumping the resource directory, including the invalid entry. Unexpected results will probably follow this problem, since the data in the directory is corrupted.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Directory services encountered a should-not-occur condition within the component. An internal control block is invalid.
A resource directory entry is invalid. The wildcard type (explicit, partial, or full) in the entry is invalid. An internal code problem exists within pSNA (DS).
Function Degradation: Directory services continues dumping the resource directory, including the invalid entry. Unexpected results will probably follow this problem, since the data in the directory is corrupted.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Directory services received/detected an invalid LOCATE message (GDS x'12C4').
Directory services encountered an invalid LOCATE GDS variable. The search status indicators in the message are invalid. The probable causes are:
Function Degradation: Directory services continues to process the LOCATE request. Unexpected results will probably follow this problem, since DS cannot correctly parse the received LOCATE message. In addition, the communications support in the sending node and the local node are either in error or incompatible; or the data in the directory is corrupted.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services does not recognize a control vector contained in a received x'2B' control vector.
Directory services encountered an invalid x'2B' control vector. It contains one or more control vectors not recognized by directory services. The probable causes are:
Function Degradation: Directory services continues to process the LOCATE request. Unexpected results will probably follow this problem, since DS cannot correctly parse the control vectors in the message. In addition, the communications support in the sending node and the local node are either in error or incompatible; or the data in the directory is corrupted.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services encountered a should-not-occur condition within the component. An internal control block is invalid.
An internal code problem exists within the directory services component. The routine used to map/unmap the control vector x'0E' determined that the unmapped x'0E' control vector structure is either not a x'0E' control vector structure or is no longer in use.
Function Degradation: Directory services ignores the control vector structure, but continues to process requests. Unexpected results will probably follow this problem, since DS is probably in error and its internal data structures are probably corrupted.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services encountered a should-not-occur condition within the component. An internal control block is invalid.
An internal code problem exists within the directory services component. The routine used to map/unmap the control vector x'0E' determined that the unmapped x'0E' control vector structure is invalid. It contains an invalid network name (resource) type indicator.
Function Degradation: Directory services ignores the control vector structure, but continues to process requests. Unexpected results will probably follow this problem, since DS is probably in error and its internal data structures are probably corrupted.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services cannot parse a received x'0E' control vector.
Directory services encountered an invalid x'0E' control vector. The network name (resource) type is not recognized by directory services. The probable causes are:
Function Degradation: Directory services continues to process the LOCATE request. Unexpected results will probably follow this problem, since DS cannot correctly parse the control vectors in the message. In addition, the communications support in the sending node and the local node are either in error or incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services encountered a should-not-occur condition within the component. An internal control block is invalid.
An internal code problem exists within the directory services component. The routine used to map/unmap the control vector x'80' determined that the unmapped x'0E' control vector structure is invalid. It contains an invalid minimum response entry type indicator.
Function Degradation: Directory services ignores the control vector structure, but continues to process requests. Unexpected results will probably follow this problem, since DS is probably in error and its internal data structures are probably corrupted.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services cannot parse a received x'3C', x'3D', x'81', or x'82' control vector.
Directory services encountered an invalid x'3C', x'3D', x'81', or x'82' control vector. The resource type is not recognized by directory services. The probable causes are:
Function Degradation: Directory services continues to process the received message. Unexpected results will probably follow this problem, since DS cannot correctly parse the control vectors in the message. In addition, the communications support in the sending node and the local node are either in error or incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services cannot parse a received resource entry control vector.
Directory services encountered an invalid resource entry control vector. The resource entry control vectors understood by directory services are x'3C', x'3D', x'81', and x'82'. The probable causes are:
Function Degradation: Directory services continues to process the received message. Unexpected results will probably follow this problem, since DS cannot correctly parse the control vectors in the message. In addition, the communications support in the sending node and the local node are either in error or incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services (DS) received an internal inter-process signal it does not recognize (or process).
The directory services internal data reporting routine received an IPS that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to the directory service dump routines. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Directory services (DS) received an invalid request from another node (search).
Directory services received an invalid search request. The search event type in the request is invalid. The probable causes are:
Function Degradation: The invalid request is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS or another node component are probably in error and out of sequence. In addition, the communications support in the sending node and the local node are either in error or incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services (DS) received an invalid request from another node (search).
Directory services received an invalid search request. The adjacent node name in the search request does not match any adjacent node records in the directory. The probable causes are:
Function Degradation: The invalid request is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS or another node component are probably in error and out of sequence. In addition, the communications support in the sending node and the local node are either in error or incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services (DS) received a search request from a node that it is currently deactivating its CP-CP sessions with. The request is ignored.
Directory services received a search request from an adjacent node that it is currently deactivating its CP-CP sessions with. The search request is ignored. The node could not send the reply back, since the CP-CP sessions are no longer active to the node.
Function Degradation: The search request is ignored, and DS continues to process other signals.
Customer Action: It is possible that the node will continue to work correctly if this problem occurs. If it appears to be behaving satisfactorily, no immediate action is required.
System Developer Action: None.
Description: Directory services encountered a should-not-occur condition within the component. An internal control block is invalid.
An adjacent node record in the directory is invalid. The node state (status) in the adjacent node record is invalid. An internal code problem exists within pSNA (DS).
Function Degradation: Directory services continues to process requests. Unexpected results will probably follow this problem, since the data in the directory is corrupted.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Directory services (DS) received an invalid network search request from another node.
Directory services received an invalid network search request. Directory services could not parse the control vectors contained in the request. The sense code specifies the type of error encountered by directory services. The probable causes are:
Function Degradation: Directory services generates an alert (ID is CPDN001). The search request is ignored, and the CP-CP sessions with the node that sent the request are deactivated.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services (DS) received an invalid network search request from another node.
Directory services received an invalid network search request. The network search either does not contain one or more required control vectors or contains one or more control vectors that are not valid for the requested type of search. The probable causes are:
Function Degradation: Directory services generates an alert (ID is CPDN001). The search request is ignored, and the CP-CP sessions with the node that sent the request are deactivated.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services (DS) received an invalid network search request from another node.
Directory services received an invalid network search request. The appropriate search FSM could not be determined from the data in the request. The probable causes are:
Function Degradation: The invalid request is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS or another node component are probably in error and out of sequence. In addition, the communications support in the sending node and the local node are either in error or incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services (DS) received an invalid network search request from another node, which caused a should-not-occur condition.
Directory services received an invalid network search request. The appropriate search FSM could not be determined from the data in the request. The directory services routine used to determine the search FSM returned an invalid value. An internal code problem exists within pSNA (DS).
Function Degradation: The invalid request is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS or another node component are probably in error and out of sequence. In addition, the communications support in the sending node and the local node are either in error or incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Directory services does not recognize a control vector contained in a received x'2B' control vector.
Directory services encountered an invalid network search request. The x'2B' control vector contained in the request contains one or more control vectors not recognized or processed by directory services. The probable causes are:
Function Degradation: Directory services rejects the network search request with the sense code x'10100000'. Unexpected results will probably follow this problem, since DS cannot correctly parse the control vectors in the message. In addition, the communications support in the sending node and the local node are either in error or incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services (DS) received an invalid CP outage notification from another node.
Directory services received an invalid notification from another node that a control point was been deactivated (i.e. the CP-CP sessions to the node have deactivated). The appropriate search FSM could not be determined from the data in the notification. The probable causes are:
Function Degradation: The invalid notification is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS or another node component are probably in error and out of sequence. In addition, the communications support in the sending node and the local node are either in error or incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services (DS) received an invalid CP outage notification from another node, which caused a should-not-occur condition.
Directory services received an invalid notification from another node that a control point was been deactivated (i.e. the CP-CP sessions to the node have deactivated). The appropriate search FSM could not be determined from the data in the notification. The directory services routine used to determine the search FSM returned an invalid value. An internal code problem exists within pSNA (DS).
Function Degradation: The invalid notification is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS or another node component are probably in error and out of sequence. In addition, the communications support in the sending node and the local node are either in error or incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Directory services tried to process a search request containing an invalid locate GDS x'12C4'.
Directory services encountered a search request containing an invalid LOCATE GDS variable. The search status indicators in the variable are invalid. The probable causes are:
Function Degradation: The invalid request is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS cannot correctly parse the received search request. In addition, the communications support in the sending node and the local node are either in error or incompatible; or the data in the directory is corrupted.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services (DS) received an invalid request from another node (search).
Directory services received an invalid search request. The search event type in the request is invalid. The probable causes are:
Function Degradation: The invalid request is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS or another node component are probably in error and out of sequence. In addition, the communications support in the sending node and the local node are either in error or incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services encountered a should-not-occur condition within the component. An internal control block is invalid.
A locate record is invalid. The local node search role indicator in the locate record is invalid. An internal code problem exists within pSNA (DS).
Function Degradation: Directory services continues to process requests. Unexpected results will probably follow this problem, since DS is probably in error and its internal data structures are probably corrupted.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Directory services tried to process a search request containing an invalid locate GDS x'12C4'.
The directory services FSM dir_INN received a search request containing an invalid LOCATE GDS variable. The search status indicators in the variable are invalid. This FSM controls the processing of directed searches for resources by an intermediate network node. The probable causes are:
Function Degradation: DS continues to process the request, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received search request. In addition, either the communications support in the sending node and the local node are in error or incompatible; or the data in the directory is corrupted.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Directory services (DS) received an invalid control point (CP) outage notification.
The directory services FSM dir_INN received an invalid or unexpected CP outage notification. Directory services does not have any locate records (pending locate requests) for the control point name contained in the notification. This FSM controls the processing of directed searches for resources by an intermediate network node. The probable causes are:
Function Degradation: DS continues to process the notification, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correlate the received notification to an outstanding request. Either the communications support in the sending node and the local node are in error or incompatible; or the data in the directory is corrupted.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM dir_INN received an invalid input search event. The search event type is invalid. This FSM controls the processing of directed searches for resources by an intermediate network node. The probable causes are:
Function Degradation: DS continues to process the event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received search event. In addition, the communications support in the sending node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM dir_INN received an unexpected or unrecognized input value. This condition should not occur, since the FSM should be robust enough to handle any valid input, and only valid inputs should be passed to the FSM. This FSM controls the processing of directed searches for resources by an intermediate network node. The probable causes are:
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM dir_INN encountered a state error (should-not-occur situation). The FSM should be robust enough to handle any valid input in any valid sequence. This FSM controls the processing of directed searches for resources by an intermediate network node. The probable causes are:
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM dir_INN outputted an unknown or invalid action value. The FSM should be robust enough to handle any valid input in any valid sequence, as well as any produced action values. This FSM controls the processing of directed searches for resources by an intermediate network node. The probable causes are:
Function Degradation: DS completes processing the current input event and then prepares to process the next request. The results may be unpredictable since the requested actions were not performed. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Directory services tried to process a search request containing an invalid locate GDS x'12C4'.
The directory services FSM brd_INN received a search request containing an invalid LOCATE GDS variable. The search status indicators in the variable are invalid. This FSM controls the processing of broadcast searches for resources by an intermediate network node. The probable causes are:
Function Degradation: DS continues to process the request, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received search request. In addition, either the communications support in the sending node and the local node are in error or incompatible; or the data in the directory is corrupted.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services (DS) received an invalid control point (CP) outage notification. The associated locate record could not be determined.
The directory services FSM brd_INN received an invalid or unexpected CP outage notification. Directory services does not have any locate records (pending locate requests) for the control point name contained in the notification. This FSM controls the processing of broadcast searches for resources by an intermediate network node. The probable causes are:
Function Degradation: DS continues to process the notification, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correlate the received notification to an outstanding request. Either the communications support in the sending node and the local node are in error or incompatible; or the data in the directory is corrupted.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM brd_INN received an invalid input search event. The search event type is invalid. This FSM controls the processing of broadcast searches for resources by an intermediate network node. The probable causes are:
Function Degradation: DS continues to process the event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received search event. In addition, the communications support in the sending node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM brd_INN received an unexpected or unrecognized input value. This condition should not occur, since the FSM should be robust enough to handle any valid input, and only valid inputs should be passed to the FSM. This FSM controls the processing of broadcast searches for resources by an intermediate network node. The probable causes are:
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM brd_INN encountered a state error (should-not-occur situation). The FSM should be robust enough to handle any valid input in any valid sequence. This FSM controls the processing of broadcast searches for resources by an intermediate network node. The probable causes are:
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Directory services encountered a should-not-occur condition within the component. An internal control block is invalid or a logic error exists within the DS component.
The directory services FSM brd_INN retrieved an incorrect/invalid directory entry from the directory. The directory entry was retrieved using a domain search, which should only search for resources "owned" by end nodes or migration end nodes within the domain of the network node. The returned directory entry is invalid, because its associated adjacent node record indicates that the adjacent node (which the resource is in the domain of) is a network node. This FSM controls the processing of broadcast searches for resources by an intermediate network node. A programming error/deficiency exists within the pSNA node (DS).
Function Degradation: The invalid directory entry is ignored, and the search returns no found resources. Unexpected results will probably follow this problem, since the definition of the resource within the directory is invalid or directory services has a logic problem that prevents it from finding the requested resource.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM brd_INN outputted an unknown or invalid action value. The FSM should be robust enough to handle any valid input in any valid sequence, as well as any produced action values. This FSM controls the processing of broadcast searches for resources by an intermediate network node. The probable causes are:
Function Degradation: DS completes processing the current input event and then prepares to process the next request. The results may be unpredictable since the requested actions were not performed. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Directory services tried to process a search request containing an invalid locate GDS x'12C4'.
The directory services FSM parent received a search request containing an invalid LOCATE GDS variable. The search status indicators in the variable are invalid. This FSM controls the processing of searches for resources relative to the parent node in the request. The probable causes are:
Function Degradation: DS continues to process the request, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received search request. In addition, either the communications support in the sending node and the local node are in error or incompatible; or the data in the directory is corrupted.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM parent received an invalid input search event. The search event type is invalid. This FSM controls the processing of searches for resources relative to the parent node in the request. The probable causes are:
Function Degradation: DS continues to process the event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received search event. In addition, the communications support in the sending node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM parent received an unexpected or unrecognized input value. This condition should not occur, since the FSM should be robust enough to handle any valid input, and only valid inputs should be passed to the FSM. This FSM controls the processing of searches for resources relative to the parent node in the request. The probable causes are:
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM parent encountered a state error (should-not-occur situation). The FSM should be robust enough to handle any valid input in any valid sequence. This FSM controls the processing of searches for resources relative to the parent node in the request. The probable causes are:
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM parent outputted an unknown or invalid action value. The FSM should be robust enough to handle any valid input in any valid sequence, as well as any produced action values. This FSM controls the processing of searches for resources relative to the parent node in the request. The probable causes are:
Function Degradation: DS completes processing the current input event and then prepares to process the next request. The results may be unpredictable since the requested actions were not performed. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Directory services tried to process a search request containing an invalid locate GDS x'12C4'.
The directory services FSM child received a search request containing an invalid LOCATE GDS variable. The search status indicators in the variable are invalid. This FSM controls the processing of searches for resources relative to the child node in the request. The probable causes are:
Function Degradation: DS continues to process the request, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received search request. In addition, either the communications support in the sending node and the local node are in error or incompatible; or the data in the directory is corrupted.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM child received an invalid input locate message. The locate message is a locate request, and only locate replies should be processed by this FSM. This FSM controls the processing of searches for resources relative to the child node in the request. The probable causes are:
Function Degradation: DS continues to process the request, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received locate message. In addition, either the communications support in the sending node and the local node are in error or incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM child received an invalid input search event. The search event type is invalid. This FSM controls the processing of searches for resources relative to the child node in the request. The probable causes are:
Function Degradation: DS continues to process the event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received search event. In addition, the communications support in the sending node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM child received an unexpected or unrecognized input value. This condition should not occur, since the FSM should be robust enough to handle any valid input, and only valid inputs should be passed to the FSM. This FSM controls the processing of searches for resources relative to the child node in the request. The probable causes are:
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM child encountered a state error (should-not-occur situation). The FSM should be robust enough to handle any valid input in any valid sequence. This FSM controls the processing of searches for resources relative to the child node in the request. The probable causes are:
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM child outputted an unknown or invalid action value. The FSM should be robust enough to handle any valid input in any valid sequence, as well as any produced action values. This FSM controls the processing of searches for resources relative to the child node in the request. The probable causes are:
Function Degradation: DS completes processing the current input event and then prepares to process the next request. The results may be unpredictable since the requested actions were not performed. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Description: Directory services (DS) received an invalid locate reply.
The directory services FSM dir_NNSdlu received an invalid locate reply. The node received a locate reply from a child node, but the child node is not in the domain of the network node server. This FSM controls the processing of directed searches for resources by the network node server of the destination LU. The probable causes are:
Function Degradation: DS continues to process the reply, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS is probably in error. In addition, either the communications support in the sending node and the local node are in error or incompatible; or the data in the directory is corrupted.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services tried to process a search request containing an invalid locate GDS x'12C4'.
The directory services FSM dir_NNSdlu received a search request containing an invalid LOCATE GDS variable. The search status indicators in the variable are invalid. This FSM controls the processing of directed searches for resources by the network node server of the destination LU. The probable causes are:
Function Degradation: DS continues to process the request, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received search request. In addition, either the communications support in the sending node and the local node are in error or incompatible; or the data in the directory is corrupted.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Description: Directory services (DS) received an invalid control point (CP) outage notification.
The directory services FSM dir_NNSdlu received an invalid CP outage notification. The node received the notification from a child node, but the child node is not in the domain of the network node server. This FSM controls the processing of directed searches for resources by the network node server of the destination LU. The probable causes are:
Function Degradation: DS continues to process the notification, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS is probably in error. In addition, either the communications support in the sending node and the local node are in error or incompatible; or the data in the directory is corrupted.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM NNSdlu received an invalid input locate message. The locate status value is invalid. This FSM controls the processing of searches for resources by the network node server of the origin LU. The probable causes are:
Function Degradation: DS continues to process the request, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received locate message. In addition, either the communications support in the sending node and the local node are in error or incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM dir_NNSdlu received an invalid input search event. The search event type is invalid. This FSM controls the processing of directed searches for resources by the network node server of the destination LU. The probable causes are:
Function Degradation: DS continues to process the event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received search event. In addition, the communications support in the sending node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM dir_NNSdlu received an unexpected or unrecognized input value. This condition should not occur, since the FSM should be robust enough to handle any valid input, and only valid inputs should be passed to the FSM. This FSM controls the processing of directed searches for resources by the network node server of the destination LU. The probable causes are:
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM dir_NNSdlu encountered a state error (should-not-occur situation). The FSM should be robust enough to handle any valid input in any valid sequence. This FSM controls the processing of directed searches for resources by the network node server of the destination LU. The probable causes are:
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Directory services encountered a should-not-occur condition within the component. An internal control block is invalid.
The directory services FSM dir_NNSdlu detected an error in the directory database. A resource directory entry is invalid. The resource location indicator in the entry is invalid. This FSM controls the processing of directed searches for resources by the network node server of the destination LU. A programming error/deficiency exists within the pSNA node (DS).
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since the directory services component contains a software error and the data in the directory is corrupted.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM dir_NNSdlu outputted an unknown or invalid action value. The FSM should be robust enough to handle any valid input in any valid sequence, as well as any produced action values. This FSM controls the processing of directed searches for resources by the network node server of the destination LU. The probable causes are:
Function Degradation: DS completes processing the current input event and then prepares to process the next request. The results may be unpredictable since the requested actions were not performed. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Directory services tried to process a search request containing an invalid locate GDS x'12C4'.
The directory services FSM ENdlu received a search request containing an invalid LOCATE GDS variable. The search status indicators in the variable are invalid. This FSM controls the processing of searches for resources by the end node owning the destination LU. The probable causes are:
Function Degradation: DS continues to process the request, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received search request. In addition, either the communications support in the sending node and the local node are in error or incompatible; or the data in the directory is corrupted.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Directory services tried to process a search request containing an invalid locate GDS x'12C4'.
The directory services FSM ENdlu received a search request containing an invalid LOCATE GDS variable. The chain status indicators in the variable are invalid. This FSM controls the processing of searches for resources by the end node owning the destination LU. The probable causes are:
Function Degradation: DS continues to process the request, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received search request. In addition, either the communications support in the sending node and the local node are in error or incompatible; or the data in the directory is corrupted.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM ENdlu received an invalid input search event. The search event type is invalid. This FSM controls the processing of searches for resources by the end node owning the destination LU. The probable causes are:
Function Degradation: DS continues to process the event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received search event. In addition, the communications support in the sending node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM ENdlu received an unexpected or unrecognized input value. This condition should not occur, since the FSM should be robust enough to handle any valid input, and only valid inputs should be passed to the FSM. This FSM controls the processing of searches for resources by the end node owning the destination LU. The probable causes are:
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM ENdlu encountered a state error (should-not-occur situation). The FSM should be robust enough to handle any valid input in any valid sequence. This FSM controls the processing of searches for resources by the end node owning the destination LU. The probable causes are:
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM ENdlu outputted an unknown or invalid action value. The FSM should be robust enough to handle any valid input in any valid sequence, as well as any produced action values. This FSM controls the processing of searches for resources by the end node owning the destination LU. The probable causes are:
Function Degradation: DS completes processing the current input event and then prepares to process the next request. The results may be unpredictable since the requested actions were not performed. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Directory services tried to process a search request containing an invalid locate GDS x'12C4'.
The directory services FSM NNolu received a search request containing an invalid LOCATE GDS variable. The search status indicators in the variable are invalid. This FSM controls the processing of searches for resources by the network node owning the origin LU. The probable causes are:
Function Degradation: DS continues to process the request, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received search request. In addition, either the communications support in the sending node and the local node are in error or incompatible; or the data in the directory is corrupted.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM NNolu received an invalid input locate message. The locate message is not a locate request, and only locate requests should be processed by this FSM. This FSM controls the processing of searches for resources by the network node owning the origin LU. The probable causes are:
Function Degradation: DS continues to process the request, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received locate message. In addition, either the communications support in the sending node and the local node are in error or incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM NNolu received an invalid input search event. The search event type is invalid. This FSM controls the processing of searches for resources by the network node owning the origin LU. The probable causes are:
Function Degradation: DS continues to process the event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received search event. In addition, the communications support in the sending node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM NNolu received an unexpected or unrecognized input value. This condition should not occur, since the FSM should be robust enough to handle any valid input, and only valid inputs should be passed to the FSM. This FSM controls the processing of searches for resources by the network node owning the origin LU. The probable causes are:
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM NNolu encountered a state error (should-not-occur situation). The FSM should be robust enough to handle any valid input in any valid sequence. This FSM controls the processing of searches for resources by the network node owning the origin LU. The probable causes are:
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Directory services encountered a should-not-occur condition within the component. An internal control block is invalid.
The directory services FSM NNolu detected an error in the directory database. A resource directory entry is invalid. The resource location indicator in the entry is invalid. This FSM controls the processing of searches for resources by the network node owning the origin LU. A programming error/deficiency exists within the pSNA node (DS).
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since the directory services component contains a software error and the data in the directory is corrupted.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM NNolu encountered a state error (should-not-occur situation). The current state indicates that a non-explicit (wildcard) locate reply was received for the resource and saved by directory services. The saved reply cannot be located using the current search correlator. This FSM controls the processing of searches for resources by the network node owning the origin LU. A programming error/deficiency exists within the pSNA node (DS).
Function Degradation: DS stops processing the current event and prepares to process the next request. Unexpected results will probably follow this problem since DS is probably in error. In addition, DS may not respond to an outstanding search (locate) request because it cannot correlate the received response to the request.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Description: Directory services detected two resources with the same name.
The directory services FSM NNolu received more than one positive locate reply for the same LU name. This FSM controls the processing of searches for resources by the network node owning the origin LU. The probable causes are:
Function Degradation: Directory services generates an alert (ID is CPDN001). DS ignores the received locate reply, although it does continue to process any other replies received for the search request. Unexpected results will probably follow this problem, since the network appears to contain two resources with the same name. Messages may be routed to the wrong node.
Customer Action: Try and determine if the problem was caused by a network definition error or a software error.
Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM NNolu outputted an unknown or invalid action value. The FSM should be robust enough to handle any valid input in any valid sequence, as well as any produced action values. This FSM controls the processing of searches for resources by the network node owning the origin LU. The probable causes are:
Function Degradation: DS completes processing the current input event and then prepares to process the next request. The results may be unpredictable since the requested actions were not performed. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Directory services tried to process a search request containing an invalid locate GDS x'12C4'.
The directory services FSM CPolu_child received a search request containing an invalid LOCATE GDS variable. The search status indicators in the variable are invalid. This FSM controls the processing of searches for resources relative to the child node in the request by the node owning the origin LU. The probable causes are:
Function Degradation: DS continues to process the request, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received search request. In addition, either the communications support in the sending node and the local node are in error or incompatible; or the data in the directory is corrupted.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM CPolu_child received an invalid input search event. The search event type is invalid. This FSM controls the processing of searches for resources relative to the child node in the request by the node owning the origin LU. The probable causes are:
Function Degradation: DS continues to process the event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received search event. In addition, the communications support in the sending node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM CPolu_child received an unexpected or unrecognized input value. This condition should not occur, since the FSM should be robust enough to handle any valid input, and only valid inputs should be passed to the FSM. This FSM controls the processing of searches for resources relative to the child node in the request by the node owning the origin LU. The probable causes are:
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM CPolu_child encountered a state error (should-not-occur situation). The FSM should be robust enough to handle any valid input in any valid sequence. This FSM controls the processing of searches for resources relative to the child node in the request by the node owning the origin LU. The probable causes are:
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM CPolu_child outputted an unknown or invalid action value. The FSM should be robust enough to handle any valid input in any valid sequence, as well as any produced action values. This FSM controls the processing of searches for resources relative to the child node in the request by the node owning the origin LU. The probable causes are:
Function Degradation: DS completes processing the current input event and then prepares to process the next request. The results may be unpredictable since the requested actions were not performed. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Description: Directory services received a locate request containing sense data.
The directory services FSM CPolu_parent received a locate request containing a non-zero sense code. This FSM controls the processing of searches for resources relative to the parent node in the request by the node owning the origin LU. The probable causes are:
Function Degradation: DS continues to process the request, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in the sending node and the local node are probably in error or incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM CPolu_parent received an invalid input search event. The search event type is invalid. This FSM controls the processing of searches for resources relative to the parent node in the request by the node owning the origin LU. The probable causes are:
Function Degradation: DS continues to process the event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received search event. In addition, the communications support in the sending node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM CPolu_parent received an unexpected or unrecognized input value. This condition should not occur, since the FSM should be robust enough to handle any valid input, and only valid inputs should be passed to the FSM. This FSM controls the processing of searches for resources relative to the parent node in the request by the node owning the origin LU. The probable causes are:
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM CPolu_parent encountered a state error (should-not-occur situation). The FSM should be robust enough to handle any valid input in any valid sequence. This FSM controls the processing of searches for resources relative to the parent node in the request by the node owning the origin LU. The probable causes are:
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM CPolu_parent outputted an unknown or invalid action value. The FSM should be robust enough to handle any valid input in any valid sequence, as well as any produced action values. This FSM controls the processing of searches for resources relative to the parent node in the request by the node owning the origin LU. The probable causes are:
Function Degradation: DS completes processing the current input event and then prepares to process the next request. The results may be unpredictable since the requested actions were not performed. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Directory services tried to process a search request containing an invalid locate GDS x'12C4'.
The directory services FSM NNSolu received a search request containing an invalid LOCATE GDS variable. The search status indicators in the variable are invalid. This FSM controls the processing of searches for resources by the network node server of the origin LU. The probable causes are:
Function Degradation: DS continues to process the request, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received search request. In addition, either the communications support in the sending node and the local node are in error or incompatible; or the data in the directory is corrupted.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM NNSolu received an invalid input locate message. The locate status value is invalid. This FSM controls the processing of searches for resources by the network node server of the origin LU. The probable causes are:
Function Degradation: DS continues to process the message, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received locate message. In addition, the communications support in the sending node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM NNSolu received an invalid input search event. The search event type is invalid. This FSM controls the processing of searches for resources by the network node server of the origin LU. The probable causes are:
Function Degradation: DS continues to process the event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received search event. In addition, the communications support in the sending node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM NNSolu received an unexpected or unrecognized input value. This condition should not occur, since the FSM should be robust enough to handle any valid input, and only valid inputs should be passed to the FSM. This FSM controls the processing of searches for resources by the network node server of the origin LU. The probable causes are:
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM NNSolu encountered a state error (should-not-occur situation). The FSM should be robust enough to handle any valid input in any valid sequence. This FSM controls the processing of searches for resources by the network node server of the origin LU. The probable causes are:
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Directory services encountered a should-not-occur condition within the component. An internal control block is invalid.
The directory services FSM NNSolu detected an error in the directory database. A resource directory entry is invalid. The resource location indicator in the entry is invalid. This FSM controls the processing of searches for resources by the network node server of the origin LU. A programming error/deficiency exists within the pSNA node (DS).
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since the directory services component contains a software error and the data in the directory is corrupted.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM NNSolu encountered a state error (should-not-occur situation). The current state indicates that a non-explicit (wildcard) locate reply was received for the resource and saved by directory services. The saved reply cannot be located using the current search correlator. This FSM controls the processing of searches for resources by the network node server of the origin LU. A programming error/deficiency exists within the pSNA node (DS).
Function Degradation: DS stops processing the current event and prepares to process the next request. Unexpected results will probably follow this problem since DS is probably in error. In addition, DS may not respond to an outstanding search (locate) request because it cannot correlate the received response to the request.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Description: Directory services detected two resources with the same name.
The directory services FSM NNSolu received more than one positive locate reply for the same LU name. This FSM controls the processing of searches for resources by the network node server of the origin LU. The probable causes are:
Function Degradation: Directory services generates an alert (ID is CPDN001). DS ignores the received locate reply, although it does continue to process any other replies received for the search request. Unexpected results will probably follow this problem, since the network appears to contain two resources with the same name. Messages may be routed to the wrong node.
Customer Action: Try and determine if the problem was caused by a network definition error or a software error.
Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM NNSolu outputted an unknown or invalid action value. The FSM should be robust enough to handle any valid input in any valid sequence, as well as any produced action values. This FSM controls the processing of searches for resources by the network node server of the origin LU. The probable causes are:
Function Degradation: DS completes processing the current input event and then prepares to process the next request. The results may be unpredictable since the requested actions were not performed. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Directory services tried to process a search request containing an invalid locate GDS x'12C4'.
The directory services FSM ENolu received a search request containing an invalid LOCATE GDS variable. The search status indicators in the variable are invalid. This FSM controls the processing of searches for resources by the end node owning the origin LU. The probable causes are:
Function Degradation: DS continues to process the request, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received search request. In addition, either the communications support in the sending node and the local node are in error or incompatible; or the data in the directory is corrupted.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services ENolu child received an invalid input locate message. The locate message is not a locate request, and only locate requests should be processed by this FSM. This FSM controls the processing of searches for resources by the end node owning the origin LU. The probable causes are:
Function Degradation: DS continues to process the request, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received locate message. In addition, either the communications support in the sending node and the local node are in error or incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM ENolu received an invalid input search event. The search event type is invalid. This FSM controls the processing of searches for resources by the end node owning the origin LU. The probable causes are:
Function Degradation: DS continues to process the event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received search event. In addition, the communications support in the sending node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM ENolu received an unexpected or unrecognized input value. This condition should not occur, since the FSM should be robust enough to handle any valid input, and only valid inputs should be passed to the FSM. This FSM controls the processing of searches for resources by the end node owning the origin LU. The probable causes are:
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM ENolu encountered a state error (should-not-occur situation). The FSM should be robust enough to handle any valid input in any valid sequence. This FSM controls the processing of searches for resources by the end node owning the origin LU. The probable causes are:
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Directory services encountered a should-not-occur condition within the component. An internal control block is invalid.
The directory services FSM ENolu detected an error in the directory database. A resource directory entry is invalid. The resource location indicator in the entry is invalid. This FSM controls the processing of searches for resources by the end node owning the origin LU. A programming error/deficiency exists within the pSNA node (DS).
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since the directory services component contains a software error and the data in the directory is corrupted.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services detected two resources with the same name.
The directory services FSM ENolu received more than one positive locate reply for the same LU name. This FSM controls the processing of searches for resources by the end node owning the origin LU. The probable causes are:
Function Degradation: Directory services generates an alert (ID is CPDN001). DS ignores the received locate reply, although it does continue to process any other replies received for the search request. Unexpected results will probably follow this problem, since the network appears to contain two resources with the same name. Messages may be routed to the wrong node.
Customer Action: Try and determine if the problem was caused by a network definition error or a software error.
Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM ENolu outputted an unknown or invalid action value. The FSM should be robust enough to handle any valid input in any valid sequence, as well as any produced action values. This FSM controls the processing of searches for resources by the end node owning the origin LU. The probable causes are:
Function Degradation: DS completes processing the current input event and then prepares to process the next request. The results may be unpredictable since the requested actions were not performed. Unexpected results will probably follow this problem, since DS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Directory services encountered a software problem (should-not-occur condition).
Directory services detected an invalid search event. The search event type is invalid. The probable causes are:
Function Degradation: Directory services continues to process requests, but will usually abend after this problem is logged.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services (DS) received an internal inter-process signal it does not recognize (or process).
The directory services internal data reporting routine received an IPS that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to the directory service resource registration routines. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services (DS) received an invalid resource registration request from another node.
Directory services received an invalid resource registration request. The received request is either not large enough to contain the required control vectors (X'80' and X'3D') or exceeds the maximum allowed length for a GDS variable. The probable causes are:
Function Degradation: The resource registration request is rejected with sense code 10100000 and the CP-CP sessions with the node that sent the request are deactivated.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services (DS) received an unexpected resource registration request from another node
Directory services received a resource registration request from an invalid session. The session the received request was received from is not one of the CP-CP sessions with the adjacent node. The probable causes are:
Function Degradation: The resource registration request is rejected with sense code 10100000 and the CP-CP sessions with the node that sent the request are deactivated.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services (DS) received an invalid resource registration request from another node.
Directory services received an invalid resource registration request. The received request is not a resource registration or registration deletion request. The probable causes are:
Function Degradation: The resource registration request is rejected with sense code 10100000 and the CP-CP sessions with the node that sent the request are deactivated.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services detected two resources with the same name.
Directory services received a resource registration request for an LU that is already defined in the directory. The resource hierarchy (the owning node or network server) of the resource in the directory does not match the resource hierarchy in the received request. The probable causes are:
Function Degradation: The resource registration request is rejected with sense code 1014023C (conflicting directory entry). Unexpected results may follow this problem, since the network appears to contain two resources with the same name. Messages may be routed to the wrong node.
Customer Action: Try and determine if the problem was caused by a network definition error or a software error.
Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services (DS) received an invalid resource registration request from another node.
Directory services received an invalid resource registration request. The type of resource contained in the control vector X'3C' is not an end node (X'00F4' - end node control point name). The probable causes are:
Function Degradation: The resource registration request is rejected with sense code 0897000D (invalid resource type).
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services (DS) received an invalid resource registration request from another node.
Directory services received an invalid resource registration request. The type of resource contained in the control vector X'3D' is not an end node (X'00F4' - end node control point name) or LU (X'00F3' - LU). The probable causes are:
Function Degradation: The resource registration request is rejected with sense code 0897000D (invalid resource type).
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services (DS) received an unexpected resource registration reply from another node
Directory services received an invalid resource request. The adjacent node name in the registration reply does not match any adjacent node records in the directory. The probable causes are:
Function Degradation: The received reply is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since one of the following is probably true:
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services (DS) received an invalid resource registration reply from another node.
Directory services received an invalid resource registration reply. The received reply is either not large enough to contain the required control vectors (X'80' and X'3D') or exceeds the maximum allowed length for a GDS variable. The probable causes are:
Function Degradation: The received reply is ignored, and the CP-CP sessions with the node that sent the reply are deactivated (using sense code 10100000, unrecoverable error).
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Directory services (DS) received an unexpected resource registration reply from another node
Directory services received a resource registration reply fom an invalid session. The session the received reply was received from is not one of the CP-CP sessions with the adjacent node. The probable causes are:
Function Degradation: The received reply is ignored, and the CP-CP sessions with the node that sent the reply are deactivated (using sense code 10100000, unrecoverable error).
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services (DS) received an invalid resource registration reply from another node.
Directory services received an invalid resource registration reply. The received reply is not a resource registration (GDS X'12C3') or registration deletion (GDS X'12C9') reply. The probable causes are:
Function Degradation: The received reply is ignored, and the CP-CP sessions with the node that sent the reply are deactivated (using sense code 10100000, unrecoverable error).
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services (DS) received an invalid resource registration reply from another node.
Directory services received an invalid resource registration reply. The first control vector in the received reply is not X'80' (register) or the length of the X'80' control vector is invalid. The probable causes are:
Function Degradation: The received reply is ignored, and the CP-CP sessions with the node that sent the reply are deactivated (using sense code 10140080, invalid control vector).
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services (DS) received an invalid resource registration reply from another node.
Directory services received an invalid resource registration reply. The request/reply indicator in the X'80' control vector (register) is invalid. It does not indicate that the received message is a reply. The probable causes are:
Function Degradation: The received reply is ignored, and the CP-CP sessions with the node that sent the reply are deactivated (using sense code 10140080, invalid control vector).
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services (DS) received an invalid resource registration reply from another node.
Directory services received an invalid resource registration reply (type=delete). The request/reply indicator in the X'80' control vector (register) is invalid. It does not indicate that the received message is a reply. The probable causes are:
Function Degradation: The received reply is ignored, and the CP-CP sessions with the node that sent the reply are deactivated (using sense code 10140080, invalid control vector).
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services (DS) received an invalid resource registration reply from another node.
Directory services received an invalid resource registration reply. The length of one or more of the control vectors in the received reply are invalid, or the length of the containing GDS variable is invalid. The probable causes are:
Function Degradation: The received reply is ignored, and the CP-CP sessions with the node that sent the reply are deactivated using sense code X'089500xx' (invalid control vector length or control vector error).
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: The directory services resource registration receive transaction program failed.
The transaction program used by directory services to receive resource registration replies encountered an error while trying to receive a registration reply. The probable causes are:
Function Degradation: The received reply is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS and its resource registration receive TP are probably in error and out of sequence. This problem may also cause communications problems, since the received reply is ignored.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages). If the problem was detected by the transaction program while an APPC verb was outstanding, the TP may have logged the APPC primary and secondary return codes from the failed APPC function. Use the descriptions of these return codes to help determine the cause of the problem.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Registration of a resource with its network node server failed.
The local node's network node server or central directory server rejected a resource registration request from the local node. The sense code indicates why the node rejected the request. The probable causes are:
Function Degradation: The identified resource is not registered with the NNS or CDS. Other nodes in the APPN network may not be able to establish sessions with the resource (LU). The local node may retry registering its resources, depending on the error.
Customer Action: Try and determine if the problem was caused by a network definition error, a communications problem, a system failure in one of the nodes, or a software error. More detailed information may be available by investigating any related error log entries or messages in the local or remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services (DS) received an invalid resource registration reply from another node.
Directory services received an invalid resource registration reply. The reply is to a resource deletion request. pSNA directory services does not send resource deletion requests, so it should never receive a resource deletion reply. The probable causes are:
Function Degradation: The received reply is ignored.
Customer Action: It is possible that the node will continue to work correctly if this problem occurs. If it appears to be behaving satisfactorily, no immediate action is required. To fix the problem, try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Registration of a resource with its network node server failed.
The local node's network node server or central directory server rejected a resource registration request from the local node. Directory services cannot correlate the resource identified in the reply to any resource defined in the local directory. The probable causes are:
Function Degradation: Directory services continues to process the received reply. The resource is not registered with the NNS or CDS. Other nodes in the APPN network may not be able to establish sessions with the resource (LU). The local node will not retry registering the resource, since it could not be located in the directory.
Customer Action: Try and determine if the problem was caused by a network definition error, a communications problem, or a software error. More detailed information may be available by investigating any related error log entries or messages in the local or remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: A system (EGPE or OS) function failed while trying to start the directory services send_search transaction program.
Directory services could not start the transaction program used to send search requests (locates and CP outage notifications) to adjacent nodes. The probable causes are:
Function Degradation: Directory services continues processing, trying to start any other service TPs and processing any received requests. Unexpected results will probably follow this problem (severe errors), since directory services will not be able to send any search requests.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages). If the problem was detected by the transaction program while an APPC verb was outstanding, the TP may have logged the APPC primary and secondary return codes from the failed APPC function. Use the descriptions of these return codes to help determine the cause of the problem.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: A system (EGPE or OS) function failed while trying to start the directory services en_rsc_registration transaction program.
Directory services could not start the transaction program used to send resource registration requests to the node's network node server and central directory server. The probable causes are:
Function Degradation: Directory services continues processing, trying to start any other service TPs and processing any received requests. Unexpected results will probably follow this problem (severe errors), since directory services will not be able to register any of its locally defined resources.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages). If the problem was detected by the transaction program while an APPC verb was outstanding, the TP may have logged the APPC primary and secondary return codes from the failed APPC function. Use the descriptions of these return codes to help determine the cause of the problem.
Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services encountered a should-not-occur condition within the component. An unexpected NULL pointer was encountered.
An internal code problem exists within the directory services component. The pointer to a required control block or data structure is NULL. The NULL pointer could be a value returned from a directory services function or a pointer contained in an internal directory services control block. The probable causes are:
Function Degradation: Directory services continues to process requests, but will usually abend after this problem is logged.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services encountered a should-not-occur condition within the component.
An internal code problem exists within the directory services component. A invalid locate record was encountered. One or more of the fields in the record are invalid. The probable causes are:
Function Degradation: Directory services continues to process requests, but may abend after this problem is logged. Unexpected results will probably follow this problem, since DS is probably in error.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services encountered a should-not-occur condition within the component.
An internal code problem exists within the directory services component. A invalid internal function was invoked. The internal routine DBset_lr_search_num() is no longer valid and should not be invoked by directory services. A programming error/deficiency exists within the pSNA node (DS).
Function Degradation: Directory services continues to process requests, but may abend after this problem is logged. Unexpected results will probably follow this problem, since DS is probably in error.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services encountered a should-not-occur condition within the component.
An internal code problem exists within the directory services component. A invalid internal function was invoked. The internal routine DBset_lr_search_role() is no longer valid and should not be invoked by directory services. A programming error/deficiency exists within the pSNA node (DS).
Function Degradation: Directory services continues to process requests, but may abend after this problem is logged. Unexpected results will probably follow this problem, since DS is probably in error.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services encountered a should-not-occur condition within the component.
An internal code problem exists within the directory services component. A invalid internal function was invoked. The internal routine DBset_lr_fqpcid() is no longer valid and should not be invoked by directory services. A programming error/deficiency exists within the pSNA node (DS).
Function Degradation: Directory services continues to process requests, but may abend after this problem is logged. Unexpected results will probably follow this problem, since DS is probably in error.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services encountered a should-not-occur condition within the component.
An internal code problem exists within the directory services component. A invalid internal function was invoked. The internal routine DBset_lr_cp_name() is no longer valid and should not be invoked by directory services. A programming error/deficiency exists within the pSNA node (DS).
Function Degradation: Directory services continues to process requests, but may abend after this problem is logged. Unexpected results will probably follow this problem, since DS is probably in error.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services encountered a should-not-occur condition within the component.
An internal code problem exists within the directory services component. A invalid internal function was invoked. The internal routine DBset_lr_PCID_modifier() is no longer valid and should not be invoked by directory services. A programming error/deficiency exists within the pSNA node (DS).
Function Degradation: Directory services continues to process requests, but may abend after this problem is logged. Unexpected results will probably follow this problem, since DS is probably in error.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services has a cross net directory entry for which it can not get the cos name.
The directory services FSM NNSolu has a cached directory entry of type non-native and it could not get the corresponding cdinit from Session service to obtain the cos name. This FSM controls the processing of searches for resources by the network node server of the origin LU. The probable causes are:
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since the directory services component contains a software error and the data in the directory is corrupted.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services has a cross net directory entry for which it can not get the cos name.
The directory services FSM NNSdlu has a cached directory entry of type non-native and it could not get the corresponding cdinit from Session service to obtain the cos name. This FSM controls the processing of directed searches for resources by the network node server of the destination LU. The probable causes are:
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since the directory services component contains a software error and the data in the directory is corrupted.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services encountered a software problem (should-not-occur condition) while searching for a resource.
The directory services FSM brd_INN received an invalid input locate message. The locate status value is invalid. This FSM controls the processing of broadcast searches for resources by an intermediate network node. The probable causes are:
Function Degradation: DS continues to process the request, although the results may be unpredictable. Unexpected results will probably follow this problem, since DS cannot correctly parse the received locate message. In addition, either the communications support in the sending node and the local node are in error or incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Directory services has a cross net directory entry for which it can not get the cos name.
The directory services FSM brd_INN has a cached directory entry of type non-native and it could not get the corresponding cdinit from Session service to obtain the cos name. This FSM controls the processing of broadcast searches for resources by an intermediate network node. The probable causes are:
Function Degradation: DS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since the directory services component contains a software error and the data in the directory is corrupted.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services (DS) received an invalid inter-process signal, which caused a should-not-occur condition.
Directory services received an invalid BN_REQUSET_ROUTE_RSP IPS. The appropriate search FSM could not be determined from the data in the signal. The directory services routine used to determine the search FSM returned an invalid value. An internal code problem exists within pSNA (DS).
Function Degradation: The invalid IPS is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services (DS) received an invalid inter-process signal, which caused a should-not-occur condition.
Directory services received an invalid BN_REQUSET_ROUTE_RSP IPS. Directory service is not expecting this IPS from TRS. The appropriate search FSM could not be determined from the data in the signal. An internal code problem exists within pSNA (DS).
Function Degradation: The invalid IPS is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services (DS) received an invalid inter-process signal, which caused a should-not-occur condition.
Directory services received an invalid CLEANUP IPS. The appropriate search FSM could not be determined from the data in the signal. The directory services routine used to determine the search FSM returned an invalid value. An internal code problem exists within pSNA (DS).
Function Degradation: The invalid IPS is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services (DS) received an invalid inter-process signal, which caused a should-not-occur condition.
Directory services received an invalid CLEANUP IPS. Directory service is not expecting this IPS from SS The appropriate search FSM could not be determined from the data in the signal. An internal code problem exists within pSNA (DS).
Function Degradation: The invalid IPS is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services (DS) received an invalid inter-process signal, which caused a should-not-occur condition.
Directory services received an invalid CHAIN_FLOW IPS. The appropriate search FSM could not be determined from the data in the signal. The directory services routine used to determine the search FSM returned an invalid value. An internal code problem exists within pSNA (DS).
Function Degradation: The invalid IPS is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services (DS) received an invalid inter-process signal, which caused a should-not-occur condition.
Directory services received an invalid CHAIN_FLOW IPS. Directory service is not expecting this IPS from SS The appropriate search FSM could not be determined from the data in the signal. An internal code problem exists within pSNA (DS).
Function Degradation: The invalid IPS is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services (DS) received an invalid inter-process signal, which caused a should-not-occur condition.
Directory services received an invalid REQUEST_CDINIT_REPLY IPS. The appropriate search FSM could not be determined from the data in the signal. The directory services routine used to determine the search FSM returned an invalid value. An internal code problem exists within pSNA (DS).
Function Degradation: The invalid IPS is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services (DS) received an invalid inter-process signal, which caused a should-not-occur condition.
Directory services received an invalid REQUEST_CDINIT_REPLY IPS. Directory service is not expecting this IPS from SS The appropriate search FSM could not be determined from the data in the signal. An internal code problem exists within pSNA (DS).
Function Degradation: The invalid IPS is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services (DS) received an invalid inter-process signal, which caused a should-not-occur condition.
Directory services received an invalid LOCATE_MESSAGE IPS. Directory service is not expecting this IPS from SS. Received a new search initiation with EBN acting as CP(OLU) and this node is not an EBN. An internal code problem exists within pSNA (DS).
Function Degradation: The invalid IPS is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Directory services received an LRY (Locate Reply) that could not be related to an existing search procedure.
Function Degradation: Directory services discards the unrecognized LRY and continues to process requests.
Customer Action: Check if the adjacent device(s) behave well.
System Developer Action:
Description: Directory services (DS) received an invalid inter-process signal, which caused a should-not-occur condition.
Directory services received an invalid PE_TIMER_RSP IPS. The appropriate search FSM could not be determined from the data in the signal. The directory services routine used to determine the search FSM returned an invalid value. An internal code problem exists within pSNA (DS).
Function Degradation: The invalid IPS is ignored, and DS continues to process other signals. Unexpected results will probably follow this problem, since DS or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Log events for the management services component of APPN (MS).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: Management Services(MS) received duplicate application registration requests. The application name in the registration request has already been registered before with a different EGPE process ID. The probable causes are:
Function Degradation: The registration request is rejected. The application that tried to register with the same application name will not be able to send or receive MDS messages. MS continues to process other requests and messages.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the application. In most cases, the error is caused by multiple copies of the same application being started, or multiple applications using the same MS application name.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix.
Additional Data: Has the following format:
Description: Management Services encountered a problem while updating the MS application list.
Management Services could not find the MS application name in the application list when trying to perform one of the following:
Function Degradation: The invalid request is ignored, and MS continues to process other requests and messages. Unexpected results will probably follow this problem, since MS is probably in error.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with MS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Management services does not recognize a sub-vector contained in a received MS capabilities message (x'80F0' major vector). It contains one or more control vectors not recognized by management services. The probable causes are:
Function Degradation: Management services rejects the received MS message by sending a SNACR (SNA condition report) to the node that send the unknown message. Unexpected results will probably follow this problem, since MS cannot correctly parse the control vectors in the message. In addition, the communications support in the sending node and the local node are either in error or incompatible.
Customer Action: If the sub-vector is a MS sub-vector that is only processed by MS focal points, a network configuration error exists. Change the network configuration so the local node is no longer used as a focal point by any nodes in the network.
If the problem was not caused by a network configuration error, the problem was probably caused by a software problem in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Management Services encountered a should-not-occur condition within the component.
MS detected an error while processing a request to build and send a MS capabilities message. The request specified an invalid MS capabilities message type. An internal code problem exists within pSNA.
Function Degradation: The MS process continues to process the request, but will probably abend soon after this error occurs. The local node can not send the MS capabilities message.
Customer Action: Call service with the code point, error description, and abend code value if available. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Management services does not recognize a sub-vector contained in a received MS capabilities message (x'80F0' major vector). It contains one or more control vectors not recognized by management services. The probable causes are:
Function Degradation: Management services rejects the received MS message by sending a SNACR (SNA condition report) to the node that send the unknown message. Unexpected results will probably follow this problem, since MS cannot correctly parse the control vectors in the message. In addition, the communications support in the sending node and the local node are either in error or incompatible.
Customer Action: If the sub-vector is a MS sub-vector that is only processed by MS focal points, a network configuration error exists. Change the network configuration so the local node is no longer used as a focal point by any nodes in the network.
If the problem was not caused by a network configuration error, the problem was probably caused by a software problem in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Management services does not recognize the a message received from another node. The GDS variable contained in the message is not recognized by the local node. The only MS capabilities messages) processed by the local node are:
The probable causes are:
Function Degradation: Management services rejects the received MS message by sending a SNACR (SNA condition report) to the node that send the unknown message. In addition, the communications support in the sending node and the local node are either in error or incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Management Services encountered a should-not-occur condition within the component.
MS detected an error while processing a request to build and send an alert. The request specified an unrecognized alert ID. An internal code problem exists within pSNA.
Function Degradation: The unrecognized request is ignored, and MS continues to process other signals. Unexpected results may follow this problem, since MS or another node component are probably in error and out of sequence. The alert is not sent.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with MS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Management Services(MS) MS_CAPS received an application request to be registered as a focal point.
An MS application has requested to register itself as a focal point application. This function is not support by pSNA so the request is ignored. The probable causes are:
Function Degradation: The registration request is rejected. The application that tried to register as a focal point will not be able to send or receive MDS messages. MS continues to process other requests and messages.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the application.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix.
Additional Data: Has the following format:
Description: Management Services (MS) received duplicate application registration requests. The application name in the registration request has already been registered before with a different EGPE process ID. The probable causes are:
Function Degradation: The registration request is rejected. The application that tried to register with the same application name will not be able to send or receive MDS messages. MS continues to process other requests and messages.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the application. In most cases, the error is caused by multiple copies of the same application being started, or multiple applications using the same MS application name.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix.
Additional Data: Has the following format:
Description: Management services could not send the results of a registration request back to the MS application. The probable causes of this problem are:
Function Degradation: Processing continues, but the registration reply is lost. Unexpected results will probably follow this problem, since the application will not receive the results of its registration request. The application will probably hang.
Customer Action: It is possible that the node will continue to work correctly if this problem occurs. The application will not be able to send or receive MS messages. To resolve the problem:
Try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: Management Services encountered a problem while processing a de-registration request from an application.
Management Services could not find the MS application name in the list of active MS applications. The probable causes are:
Function Degradation: The de-registration request is rejected. MS continues to process other requests and messages.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the application.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix.
Additional Data: Has the following format:
Description: Management Services encountered a problem while updating the MS application list.
Management Services could not find the MS application name in the application list while attempting to remove (delete) the application from the list. This condition should not occur, since MS should always verify the existence of the application before processing the request. An internal code problem exists within pSNA.
Function Degradation: The invalid request is ignored, and MS continues to process other requests and messages. Unexpected results will probably follow this problem, since MS is probably in error.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with MS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Management Services encountered a should-not-occur condition within the component.
Management Services (MS) could not find the CP-MSU GDS variable when trying to send out a queued alert message to the focal point.
Management Services has established a new focal-point/entry-point relationship and was trying to resend the queued messages, but the message does not contain a valid CP-MSU. An internal code problem exists within pSNA.
Function Degradation: MS continues to process the queued alert. The error occurred while trying to set the held alert indicator in the alert. Unexpected results may follow this problem, since MS is probably in error. In addition, the alert, if sent, will not be formatted correctly.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with MS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Management Services encountered a should-not-occur condition within the component.
Management Services (MS) could not find the CP-MSU GDS variable when trying to send out a queued alert message to the focal point.
Management Services has established a new focal-point/entry-point relationship and was trying to resend the queued messages, but the message does not contain a valid CP-MSU. An internal code problem exists within pSNA.
Function Degradation: MS continues to process the queued alert. The error occurred while trying to set the buffered indicator in the alert. Unexpected results may follow this problem, since MS is probably in error. In addition, the alert, if sent, will not be formatted correctly.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with MS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Management Services encountered a should-not-occur condition within the component.
MS detected an error while parsing an MDS message. This error could occur while processing a message received from another node or while building a message to send to another node. The message does not contain an expected or required sub-vector.
For inbound messages, the probable causes are:
For outbound messages, the probable cause is an internal code problem exists within pSNA.
Function Degradation: For inbound messages, management services rejects the received message by sending a SNACR (SNA condition report) to the node that send the unknown message. Unexpected results will probably follow this problem, since MS cannot correctly parse the control vectors in the message. In addition, the communications support in the sending node and the local node are either in error or incompatible.
For outbound messages, MS continues to process the request, but will probably abend soon after this error occurs. The local node will not send the MS message, or if it does, the message will not be correctly formatted.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data and API traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Management services (MS) encountered an error while processing an inter-process signal.
Management Services received a CP_STATUS signal from session services (SS) for a network node, but the local node type indicator is invalid. This condition should not occur, since the local node type should have been verified (EN or NN) when the node was started. An internal code problem exists within pSNA.
Function Degradation: The invalid IPS is ignored, and MS continues to process other signals. Unexpected results will probably follow this problem, since MS or SS are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with MS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Management Services (MS) encountered a should-not-occur condition.
Management Services received an unexpected CP_STATUS signal from session services (SS). The local node is an end node, and the CP_STATUS update is for an adjacent end node. This condition should not occur, since session services should only send CP_STATUS messages for the serving network node when the local node is an end node. An internal code problem exists within pSNA.
Function Degradation: The invalid IPS is ignored, and MS continues to process other signals. Unexpected results will probably follow this problem, since MS or SS are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with MS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Management services (MS) encountered an error while processing an inter-process signal.
Management Services received a CP_STATUS signal from session services (SS) for an end node, but the local node type indicator is invalid. This condition should not occur, since the local node type should have been verified (EN or NN) when the node was started. An internal code problem exists within pSNA.
Function Degradation: The invalid IPS is ignored, and MS continues to process other signals. Unexpected results will probably follow this problem, since MS or SS are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with MS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Management Services (MS) encountered a should-not-occur condition.
Management Services received an unexpected CP_STATUS signal from session services (SS). The CP_STATUS update is for a virtual node (connection network). This condition should not occur, since session services should not send CP_STATUS messages for virtual nodes. An internal code problem exists within pSNA.
Function Degradation: The invalid IPS is ignored, and MS continues to process other signals. Unexpected results will probably follow this problem, since MS or SS are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with MS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Management services (MS) received an invalid internal inter-process signal.
Management Services received a CP_STATUS signal from session services (SS), but the local node type indicator is invalid. This condition should not occur, since the signal should indicate the correct local node type (EN or NN). An internal code problem exists within pSNA.
Function Degradation: The invalid IPS is ignored, and MS continues to process other signals. Unexpected results will probably follow this problem, since MS or SS are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with MS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Management services received an unexpected MS message.
Management Services received an MS message in which the local node is not the final destination. This should not occur, since the local node is an end node. The message must have been routed incorrectly. The only time end nodes should receive MS messages is when they are the final destination. The probable causes are:
Function Degradation: Management services rejects the received MS message by sending a SNACR (SNA condition report). An MS alert (CPMS002) is also generated. Unexpected results will probably follow this problem, since MS rejected a MS message received from the network. In addition, the communications support in the sending node and the local node are either in error or incompatible.
Customer Action: Determine if the problem was caused because the node that forwarded the message believed the local node is a network node. Change the network configuration so the local node is recognized (either defined or learned) as an end node by all its adjacent nodes.
If the problem was not caused by a network configuration error, the problem was probably caused by a software problem in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Management services received an unexpected MS message.
Management Services received an MS message from an adjacent node via the CP-CP sessions set up with that node. The adjacent node is not an end node served by the local node, which is a network node. This should not occur, since the only time network nodes should receive MS messages via CP-CP sessions is from their served end nodes. The message must have been routed incorrectly. The probable causes are:
Function Degradation: Management services rejects the received MS message by sending a SNACR (SNA condition report). An MS alert (CPMS002) is also generated. Unexpected results will probably follow this problem, since MS rejected a MS message received from the network. In addition, the communications support in the sending node and the local node are either in error or incompatible.
Customer Action: Determine if the problem was caused because the node that forwarded the message believed the local node is its serving network node. Change the network configuration so the local node is recognized (either defined or learned) as a network node, but is not the serving network node for the adjacent node.
If the problem was not caused by a network configuration error, the problem was probably caused by a software problem in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Management services received an unexpected MS message.
Management Services received an MS message from an adjacent node via a SNASVCMG session set up with that node. The destination of the message is not the local node or one of the end nodes served by the local node. This should not occur, since the only time MS messages should be received via CP-CP sessions is if the local node is the destination, or the local node is a network node and the destination is one of the end nodes served by the local node. The message must have been routed incorrectly. The probable causes are:
Function Degradation: Management services rejects the received MS message by sending a SNACR (SNA condition report). An MS alert (CPMS002) is also generated. Unexpected results will probably follow this problem, since MS rejected a MS message received from the network. In addition, the communications support in the sending node and the local node are either in error or incompatible.
| Note: |
Sometimes a remote node will send an MS message based on old network information. Once the remote node receives the SNACR, it will verify the destination, and possibly re-send the message. This situation does not signify an error. For example, if the destination end node at one time was served by the local network node but has changed network node servers, the remote node may not be aware the end node has switched servers. Once the local node rejects the message, the remote node searches the network, determines the correct network node server, and resends the message to the correct network node. |
Customer Action: Determine if the problem was caused because the node that forwarded the message believed the local node is a network node. Change the network configuration so the local node is recognized (either defined or learned) as an end node by all its adjacent nodes.
If the problem was not caused by a network configuration error, the problem was probably caused by a software problem in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Management Services (MS) received an MS message for an unrecognized MS application.
Management Services received an MS message it could not route locally. The destination MS application name is not recognized by management services. It is not EP_ALERT, MS_CAPS, or any of the other registered MS applications. The probable causes are:
Unless an application in the local or remote node is in error, a software problem probably exists in the node that sent the message, or the APPC/APPN support in the remote node is not compatible (which should never happen) with the pSNA APPC/APPN support.
Function Degradation: Management services rejects the received MS message by sending a SNACR (SNA condition report). An MS alert (CPMS002) is also generated. Unexpected results will probably follow this problem, since MS rejected a MS message received from the network. In addition, the communications support in the sending node and the local node are possibly in error or incompatible.
Customer Action: Determine if the problem was caused by an application error. Verify that the originating application specified the correct destination. Fix the application to send correct messages if the originating application is in error. Make sure the target application remains active so that it does not miss any messages sent to it.
If the problem was not caused by an application error, the problem was probably caused by a software problem in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Management services received an unexpected MS error message.
Management Services received an MS error message rejecting a message sent by the local node. The remote network node that received the MS message does not serve the intended destination end node, and it is not the intended destination either. Normally, if the local node were a network node, it would re-compute the route and re-send the message, assuming that the network information it used to send the original message is out of date. But since the local node is an end node, the message is ignored and an alert is generated. The original message or the error message must have been routed incorrectly. The probable causes are:
Function Degradation: Management services ignores the received MS error message and continues processing other messages. The original MS message is lost. An MS alert (CPMS002) is also generated. Unexpected results will probably follow this problem, since the original MS message could not be sent. In addition, the communications support in the sending node and the local node are either in error or incompatible.
Customer Action: Determine if the problem was caused because the local node contains invalid network configuration information. Change the network configuration so the destination node is correctly defined (or learned) by the local node.
If the problem was not caused by a network configuration error, the problem was probably caused by a software problem in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Management services received an unexpected MS message.
Management Services received an invalid MS capabilities message from a MS migration node. The MS capabilities message was a focal point authorization reply (x'62'). This should not occur, since migration nodes should not send this message. The probable causes are:
Function Degradation: Management services ignores the received MS message. An MS alert (CPMS002) is also generated. Unexpected results will probably follow this problem, since MS ignored a message received from the migration node. In addition, the communications support in the sending node and the local node are either in error or incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Management services received an unexpected MS message.
Management Services received an unexpected MS capabilities message from a MS migration node. The MS capabilities message was an entry point authorization reply (x'64'), but the reply could not be correlated with an outstanding entry point authorization request (x'63) for that node. The reply could not be correlated with any outstanding request. The probable causes are:
Function Degradation: Management services ignores the received MS message. An MS alert (CPMS002) is also generated. Unexpected results will probably follow this problem, since MS ignored a message received from the migration node. In addition, the communications support in the sending node and the local node are either in error or incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Management services received an invalid MS message.
Management Services received an invalid MS capabilities message from a MS migration node. The type of message was not recognized by the local node. The local node only processes focal point authorization requests (x'61') or entry point authorization replies (x'64) from MS migration nodes. The probable causes are:
Function Degradation: Management services ignores the received MS message. An MS alert (CPMS002) is also generated. Unexpected results will probably follow this problem, since MS ignored a message received from the migration node. In addition, the communications support in the sending node and the local node are either in error or incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Management Services received an invalid MS message from a MS migration node. The message was not an alert (major vector x'0000') MS capabilities (major vector x'80F0') message. The probable causes are:
Function Degradation: Management services ignores the received MS message. An MS alert (CPMS002) is also generated. Unexpected results will probably follow this problem, since MS ignored a message received from the migration node. In addition, the communications support in the sending node and the local node are either in error or incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Management Services received an invalid MS message from a MS migration node. The message was not a CP-MSU (GDS variable x'1212'). The probable causes are:
Function Degradation: Management services ignores the received MS message. An MS alert (CPMS002) is also generated. Unexpected results will probably follow this problem, since MS ignored a message received from the migration node. In addition, the communications support in the sending node and the local node are either in error or incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Management services could not send a request to another node component. MS sends requests to directory services to search for destination nodes (i.e. LOCATE messages) and the control point's resource manager to start one of the MS service transaction programs. The probable causes of this problem are:
Function Degradation: The management services process terminates. The local node can no longer send or receive MS messages, such as alerts, and will also probably terminate.
Customer Action: To resolve the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: Management Services (MS) encountered a problem trying to start a management services service transaction program. The control point resource manager replied to the request to start the TP with an error code. The service transaction program is not started. The probable causes are:
Function Degradation: Management services continues processing, trying to start any other service TPs and processing any received requests. Unexpected results will probably follow this problem, since MS could not send a MS message.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: Management Services (MS) encountered a problem trying to start a management services service transaction program. The request to start the service transaction program (Pcreate) failed. The probable causes are:
Function Degradation: Management services continues processing, trying to start any other service TPs and processing any received requests. Unexpected results will probably follow this problem, since MS could not send a MS message.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Description: Management services could not send an internal request (IPS) to session services. The EGPE function PQenq failed. The probable causes of this problem are:
Function Degradation: The management services process terminates. The local node can no longer send or receive MS messages, such as alerts, and will also probably terminate.
Customer Action: To resolve the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Description: Management Services encountered a should-not-occur condition within the component.
Management Services (MS) could not set the verification flag in the MDS routing information portion of a MS message. The MS message being processed is missing either the MDS routing GDS variable (x'1311') or the MDS control sub-vector (x'90') within the MDS routing variable. The MS message is invalid.
For inbound messages, the probable causes are:
For outbound messages, the probable cause is an internal code problem exists within pSNA.
Function Degradation: For both inbound and outbound messages, management services continues to process the message. The error occurred while trying to set the verification indicator in the routing information of the message. For inbound messages, unexpected results will probably follow this problem, since MS cannot correctly parse the control vectors in the message. In addition, the communications support in the sending node and the local node are either in error or incompatible.
For outbound messages, unexpected results may follow this problem, since MS is probably in error. In addition, the message, if sent, will not be formatted correctly and may be routed through the network incorrectly.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data and API traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Management Services (MS) MDS router received an incorrectly routed message.
Management Services tried to send an MDS message to a MS migration node, but the destination MS application name is not the alert focal point (ALERT_NETOP) or the MS capabilities application (MS_CAPS). Those two MS applications are the only two applications supported in an MS migration node. The probable causes are:
Unless an application in the local node specified an invalid destination application, a software problem probably exists in the node that sent the message, or the APPC/APPN support in the remote node is not compatible (which should never happen) with the pSNA APPC/APPN support.
Function Degradation: Management services rejects the received MS message by sending a SNACR (SNA condition report) to the application that attempted to send the message. An MS alert (CPMS002) is also generated. Unexpected results will probably follow this problem, since MS did not send a message. In addition, the communications support in the sending node and the local node are possibly in error or incompatible.
Customer Action: Determine if the problem was caused by an application error. Verify that the originating application specified the correct destination. Fix the application to send correct messages if the originating application is in error.
If the problem was not caused by an application error, the problem was probably caused by a software problem in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Management Services (MS) encountered a problem trying to send a message to a management services service transaction program. The request to send the MS message (PQenq) failed. The probable causes are:
Function Degradation: Management services continues processing, trying to send any other MS messages and processing any received requests. Unexpected results will probably follow this problem, since MS could not send a MS message.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: Management Services (MS) detected an error while trying to send a MS message.
The destination (LU or control point) specified in the MS message cannot be found by the local node. The search of the APPN network for the destination failed. The probable causes are:
Function Degradation: Management services rejects the received MS message by sending a SNACR (SNA condition report) to the application that attempted to send the message. An MS alert (CPMS002) is also generated. Unexpected results will probably follow this problem, since MS did not send a message.
Customer Action: Determine the cause of the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix.
Additional Data: Has the following format:
Description: Management Services (MS) detected an error while trying to send a MS message to a local MS application.
The destination application name specified in the MS message is not registered with the local node. The destination LU is owned by the local node, but the specified MS application is not active. The probable causes are:
Function Degradation: Management services rejects the received MS message by sending a SNACR (SNA condition report) to the application that attempted to send the message. An MS alert (CPMS002) may also be generated. Unexpected results will probably follow this problem, since MS did not send a message.
Customer Action: Determine the cause of the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix.
Description: Management Services (MS) detected an error while trying to send a MS error message to a local MS application.
Management services detected a serious error in a MS error message being sent to a local MS application. The message is an SNA condition report (SNACR), but the message does not specify a sense code. All SNACRs must contain a sense code identifying the error being reported. The probable causes are:
Function Degradation: Management services discards the MS message. Unexpected results will probably follow this problem, since MS did not send a message.
Customer Action: Determine the cause of the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix.
Additional Data: Has the following format:
Description: Management Services (MS) encountered a problem trying to send a message to a management services application program. The request to send the MS message (PQenq) failed. The probable causes are:
Function Degradation: Management services discards the current message. Management services continues processing, trying to send any other MS messages and processing any received requests. Unexpected results will probably follow this problem, since MS could not send a MS message.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: Management Services (MS) encountered a problem trying to send an alert. The size of the alert (the alert major vector) in the message is too small or too large. A programming error/deficiency exists within the pSNA node.
Function Degradation: Management services discards the current message. Management services continues processing, trying to send any other MS messages and processing any received requests. Unexpected results will probably follow this problem, since MS could not send the alert.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
The invalid alert is logged in a related log record (2F103000-00000035).
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: Management Services (MS) encountered a problem trying to send a message. The request did not specify a valid network-qualified destination control point name. The probable causes are:
Function Degradation: Management services discards the send request. Unexpected results will probably follow this problem, since MS did not send a message.
Customer Action: Determine the cause of the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix.
Additional Data: Has the following format:
Description: Management Services (MS) encountered a problem trying to send a message. The request did not specify a valid destination MS application name. The application name was either not specified or the specified name was longer than eight characters. The probable causes are:
Function Degradation: Management services discards the send request. Unexpected results will probably follow this problem, since MS did not send a message.
Customer Action: Determine the cause of the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix.
Additional Data: Has the following format:
Description: Management Services (MS) encountered a problem trying to send a message. The request did not specify a valid origin MS application name. The application name was either not specified or the specified name was longer than eight characters. The probable causes are:
Function Degradation: Management services discards the send request. Unexpected results will probably follow this problem, since MS did not send a message.
Customer Action: Determine the cause of the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix.
Additional Data: Has the following format:
Description: Management Services (MS) encountered a problem trying to send a message. The request did not specify a valid destination MS application name. The application name was either not specified or the specified name was longer than eight characters.
In addition, Management Services (MS) encountered a problem trying to send an error message back to the origin MS application. The request to send the MS message (PQenq) failed. The probable causes are:
Function Degradation: Management services discards the current message. Management services continues processing, trying to send any other MS messages and processing any received requests. Unexpected results will probably follow this problem, since MS could not send a MS message and could not inform the origin application of the error.
Customer Action: Determine why the original message could not be sent:
Then, try and determine why the error message could not be sent by investigating any related error information (such as additional log entries or messages).
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Description: Management Services (MS) encountered a problem trying to correlate a received MS error message (SNA condition report or SNACR) with an outstanding MS request.
The error message indicated that the focal point was lost. MS is trying to locate the originating message so it will be forwarded to a backup focal point. The unit-of-work correlator in the received error message does not match that of any outstanding MS request. The probable causes are:
Note: This log event can also be created during normal node initialization. During local node initialization, MS may try to send an entry point authorization request (x'63') to re-acquire its focal points before the connections to the focal point are active. The send request fails, and there are no cached messages, so this error is logged. If this log event is logged during node initialization, no specific action is required. MS will retry acquiring its focal point later.
Function Degradation: Management services ignores the received MS error message. Unexpected results will probably follow this problem, since MS cannot correctly correlate the reply and re-send the original request. In addition, the communications support in the sending node and the local node may be in error or incompatible.
Customer Action:
If the problem was not caused because the request was already discarded by MS, the problem was probably caused by a software problem in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Management Services encountered a should-not-occur condition within the component.
MS detected an error while processing a request to build and send an alert. The request specified an unrecognized alert ID. An internal code problem exists within pSNA.
Function Degradation: The unrecognized request is ignored, and MS continues to process other signals. Unexpected results may follow this problem, since MS or another node component are probably in error and out of sequence. The error was found while updating some internal counters within MS. The alert could still be successfully sent, although unlikely. Look for the related log event 2F103000-00000007.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with MS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Management services received an invalid MS message. Management services could not locate the time stamp sub-vector (x'02') in the received unit-of-work correlator. The probable causes are:
Function Degradation: Management services continues to process the received MS message. Unexpected results may follow this problem, since MS cannot correctly parse the control vectors in the message. In addition, the communications support in the sending node and the local node are either in error or incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Look for the related log event 2F103000-00000035.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Management Services (MS) detected an error while trying to parse a received MS error message.
Management services detected a serious error in a MS error message being sent to a local MS application. The message is an SNA condition report (SNACR), but the message does not contain a valid CP-MSU GDS variable (x'1212'). The sense code identifying the error that generated the message cannot be located. The probable causes are:
Function Degradation: Management services discards the MS message. Unexpected results will probably follow this problem, since MS did not send a message.
Customer Action: Determine the cause of the problem. Look for the related log events 2F103000-00000028 and 2F103000-00000035.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix.
Description: Management Services (MS) detected an error while trying to parse a received MS error message.
Management services detected a serious error in a MS error message being sent to a local MS application. The message is an SNA condition report (SNACR), but MS could not parse the CP-MSU GDS variable (x'1212'). The sense code identifying the error that generated the message cannot be located. The probable causes are:
Function Degradation: Management services discards the MS message. Unexpected results will probably follow this problem, since MS did not send a message. Look for the related log events 2F103000-00000028 2F103000-00000035.
Customer Action: Determine the cause of the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix.
Description: Management Services (MS) detected an error while trying to parse a received MS error message.
Management services detected a serious error in a MS error message being sent to a local MS application. The message is an SNA condition report (SNACR), but the CP-MSU GDS variable in the received message does not contain a SNA report code sub-vector (x'7D'). The sense code identifying the error that generated the message cannot be located. The probable causes are:
Function Degradation: Management services discards the MS message. Unexpected results will probably follow this problem, since MS did not send a message.
Customer Action: Determine the cause of the problem. Look for the related log events 2F103000-00000028 and 2F103000-00000035.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix.
Additional Data: Has the following format:
Description: Management Services (MS) encountered an error parsing a received message. This event is created to log the portion of the message in error. This log record is created along with other log records which identify the type of error that was detected by management services. Refer to these related log entries and messages for more information and other recommended actions.
Function Degradation: See related log records.
Customer Action: See related log records.
System Developer Action: See related log records.
Additional Data: Has the following format:
Description: Management services encountered a unrecoverable error. Management services encountered an error trying to obtain the local node's PCID value from session services. The probable causes of this problem are:
Function Degradation: The management services process terminates. The local node can no longer send or receive MS messages, such as alerts, and will also probably terminate.
Customer Action: To resolve the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: Management Services (MS) encountered an error processing a received MS message. This event is created to log the portion of the message in error. This log record is created along with other log records which identify the type of error that was detected by management services. Refer to these related log entries and messages for more information and other recommended actions.
Function Degradation: Management services rejects the received MS message by sending a SNACR (SNA condition report). An MS alert (CPMS002) may also be sent, depending on the error. Refer to related log entries and messages for more information and other system actions.
Customer Action: See related log records.
System Developer Action: See related log records.
Description: Management Services (MS) encountered a should-not-occur condition.
MS detected an error while processing a request to build and send an alert from configuration services. The alert request received from CS does not contain any product set ID information. MS expects CS to insert the product set ID from the XID being processed when the error occurred in the generated alert. An internal code problem exists within pSNA.
Function Degradation: The unrecognized request is ignored, and MS continues to process other signals. Unexpected results may follow this problem, since MS or CS are probably in error and out of sequence. The alert is still sent, but will not contain valid data (the product set ID information will be missing).
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with MS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Management Services (MS) encountered a should-not-occur condition.
MS detected an error while processing a request to build and send an alert from configuration services. The alert request received from CS does not contain any product set ID information. MS expects CS to insert the product set ID from the XID being processed when the error occurred in the generated alert. An internal code problem exists within pSNA.
Function Degradation: The unrecognized request is ignored, and MS continues to process other signals. Unexpected results may follow this problem, since MS or CS are probably in error and out of sequence. The alert is still sent, but will not contain valid data (the product set ID information will be missing).
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with MS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Management Services encountered a should-not-occur condition within the component.
MS detected an error while parsing an MDS message. This error could occur while processing a message received from another node or while building a message to send to another node. The message does not contain an expected or required sub-vector.
For inbound messages, the probable causes are:
For outbound messages, the probable cause is an internal code problem exists within pSNA.
Function Degradation: For inbound messages, management services rejects the received message by sending a SNACR (SNA condition report) to the node that send the unknown message. Unexpected results will probably follow this problem, since MS cannot correctly parse the control vectors in the message. In addition, the communications support in the sending node and the local node are either in error or incompatible.
For outbound messages, MS continues to process the request, but will probably abend soon after this error occurs. The local node will not send the MS message, or if it does, the message will not be correctly formatted.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data and API traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Management Services (MS) encountered a problem trying to correlate a received MS error message (SNA condition report or SNACR) with an outstanding MS capabilities request.
The error message indicated that the focal point was lost. MS is trying to locate the originating message so it will be forwarded to a backup focal point. The unit-of-work correlator in the received error message does not match that of any outstanding MS request. This problem should not occur, since MS verifies the existence of an outstanding request before trying to correlate the received error message.
A programming error/deficiency exists within the pSNA node. The unit-of-work is logged in a related log record (2F103000-00000035).
Function Degradation: Management services continues to process the received MS error message. Unexpected results will probably follow this problem, since MS cannot correctly correlate the reply.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Management Services (MS) encountered a problem trying to send a message to a management services application.
Management Services (MS) had new information regarding the focal point of a specific MS category. MS tried to inform all applications in this category of the change. The request to send the MS message (PQenq) failed. The probable causes are:
Function Degradation: Management services continues processing, trying to send any other MS messages and processing any received requests. Unexpected results will probably follow this problem, since MS could not inform the applications of the focal point change. Subsequent requests sent by the application will probably not be sent to the correct destination.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: AN APPN component detected an error condition and requested an alert be sent to the management services alert focal point. The sense code contained in the alert indicates the detected error condition. The SNA/MS reference lists the alerts that are generated by the APPN components. MS will try and forward the alert to the alert focal point.
Function Degradation: None.
Customer Action: Use the sense code and logged alert data to determine the cause of the problem and remedy the situation. If you cannot determine the cause of the problem, call service with the code point, error description, and logged data. If possible, try and re-create the problem with component and traces enabled and supply that trace information with the problem.
System Developer Action: Use the sense code and logged alert data to determine the cause of the problem and remedy the situation.
Additional Data: Has the following format:
Description: AN APPN component detected an error condition and requested an alert be sent to the management services alert focal point. MS Sent the ms_transport to the MDS router. The MDS router will route it to the correct destination. The sense code contained in the alert indicates the detected error condition. The SNA/MS reference lists the alerts that are generated by the APPN components. MS will try and forward the alert to the alert focal point.
Function Degradation: None.
Customer Action: Use the sense code and logged alert data to determine the cause of the problem and remedy the situation. If you cannot determine the cause of the problem, call service with the code point, error description, and logged data. If possible, try and re-create the problem with component and traces enabled and supply that trace information with the problem.
System Developer Action: Use the sense code and logged alert data to determine the cause of the problem and remedy the situation.
Additional Data: Has the following format:
Description: AN APPN component detected an error condition and requested an alert be sent to the management services alert focal point. The MDS router will route it to the correct destination. The sense code contained in the alert indicates the detected error condition. The SNA/MS reference lists the alerts that are generated by the APPN components. MS will try and forward the alert to the alert focal point.
Function Degradation: None.
Customer Action: Use the sense code and logged alert data to determine the cause of the problem and remedy the situation. If you cannot determine the cause of the problem, call service with the code point, error description, and logged data. If possible, try and re-create the problem with component and traces enabled and supply that trace information with the problem.
System Developer Action: Use the sense code and logged alert data to determine the cause of the problem and remedy the situation.
Description: Management Services (MS) encountered a problem trying to send a message to the RFC TRAP 3 subagent. The RFC TRAP 3 subagent application does not exist.
Function Degradation: Management services continues processing, trying to send any other MS messages and processing any received requests. Unexpected results will probably follow this problem, since MS could not send the alert to the RFC TRAP 3 subagent.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Description: Management Services (MS) has temporarily halted enqueueing alert messages to its MDS_SEND_TP, the transaction program responsible for sending these alerts to the focal point. This action was prompted by a build-up of alert messages on the transaction program's input queue.
Function Degradation: Management services will discard all alerts while the transaction program's input queue remains congested. The management focal point will probably contain inaccurate information about this node, since MS is stopping the sending of alerts to the focal point.
Customer Action: Try and determine what caused the congestion by investigating any related error information (such as additional log entries or messages).
System Developer Action: Debug and determine what caused the congestion to occur. Note that two threshold values are used to monitor congestion on the transaction program's input queue. These values may need to be adjusted if this condition is frequently encountered. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: Management Services (MS) has resumed enqueueing alert messages to its MDS_SEND_TP, the transaction program responsible for sending these alerts to the focal point. Enqueueing of these messages had been halted previously due to congestion on the transaction program's input queue. The congestion has now been reduced.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Log events for the node operator facility component of APPN (NOF).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Description: NOF rejected a DEFINE_LINK verb because the supplied adjacent CP name is invalid or is missing.
A DEFINE_LINK verb was rejected because the value of the adjacent CP name in the verb (fq_adj_cpname) is invalid:
Function Degradation: The DEFINE_LINK verb is rejected, so the link to the adjacent node is not defined.
Customer Action: Re-issue the verb with correct values. If the error occurred while loading the initial network configuration or while processing the network definition file, correct the error in the file and re-load the configuration.
System Developer Action: None.
Description: NOF rejected a DEFINE_COS verb because the class-of-service name is invalid or was not specified.
A DEFINE_COS verb was rejected because the value of the class-of-service name in the verb (cos_name) is invalid:
Function Degradation: The DEFINE_COS verb is rejected, so the class-of-service definition is not created.
Customer Action: Re-issue the verb with correct values. If the error occurred while loading the initial network configuration or while processing the network definition file, correct the error in the file and re-load the configuration.
System Developer Action: None.
Description: NOF rejected a DELETE_COS verb because the specified class-of-service name was CPSVCMG or SNASVCMG.
A DELETE_COS verb was rejected because it attempted to delete a class-of-service definition required by the APPN node (CPSVCMG or SNASVCMG).
Function Degradation: The DELETE_COS verb is rejected, so the class-of-service definition is still defined.
Customer Action: The specified class-of-service cannot be deleted. No action is required unless a different class-of-service definition was meant to be deleted and the name was incorrectly specified. If so, re-issue the verb with the correct name.
System Developer Action: None.
Description: The main NOF process (in the node control point) cannot send a process create message to the surrogate NOF in a co-processor.
The main NOF process (in the APPN control point) could not request the creation of a pSNA process in an attached co-processor. The command to send the creation request (REQUEST_CREATE IPS message) to the surrogate NOF process (PIM) in the co-processor failed. The EGPE function PQenq failed. The possible causes of this problem are:
Function Degradation: The control point NOF process continues processing, trying to create any other required node processes in the co-processor, as well as any other co-processors. Unexpected results will probably follow this problem (severe errors), since a process that provides necessary node services in a co-processor could not be created.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Description: NOF rejected a DEFINE_DLC verb because the DLC was not specified.
A DEFINE_DLC verb was rejected because the DLC name in the verb (dlc_name) was not specified.
Function Degradation: The DEFINE_DLC verb is rejected, so the desired data link control is not created or started.
Customer Action: Re-issue the verb with correct values. If the error occurred while loading the initial network configuration or while processing the network definition file, correct the error in the file and re-load the configuration.
System Developer Action: None.
Additional Data: Has the following format:
Description: A failure occurred trying to create a node process in an attached sub-system (co-processor).
A surrogate NOF process (in an attached co-processor) could not create (start) a pSNA process in the attached sub-system (co-processor). The EGPE function Pcreate failed. The possible causes of this problem are:
Function Degradation: The control point NOF process continues processing, trying to create any other required node processes in the co-processor, as well as any other co-processors. Unexpected results will probably follow this problem (severe errors), since a process that provides necessary node services in a co-processor could not be created.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: NOF could not send an IPS to the session connector manager to request accounting data.
NOF could not send an IPS to the session connector manager. The failed IPS was a request to retrieve accounting data from the session connector manager (including intermediate sessions, their RSCVs, performance statistics, and threshold values). The EGPE function PQenq failed. The possible causes of this problem are:
Function Degradation: NOF continues processing other requests. The requested accounting data is not retrieved.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: NOF received an unexpected IPS from EGPE. This condition should not occur, since the unexpected signal should not have been routed to NOF for processing. An internal code problem exists within pSNA (NOF or EGPE).
NOF received a response IPS (PE_CREATE_ENVIRONMENT_RSP) from EGPE that it cannot correlate. The response is from a request to create an "environment" (EGPE), probably in an attached co-processor. NOF could not correlate the response to any of its outstanding creation requests.
Function Degradation: The unexpected IPS is ignored, and NOF continues to process other signals. Unexpected results will probably follow this problem, since NOF and EGPE are probably in error and out of sequence.
This log record is created in conjunction with the log record 2F104000-0000001F, which contains additional information.
Customer Action: Call service with the code point and error description. Refer to related log entries and messages for more information and other recommended actions. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: A node process encountered an unrecoverable error and abended.
NOF detected that one or more pSNA processes abended with an unrecoverable error. The possible causes of this problem are:
Function Degradation: The node operator facility (NOF) process terminates. The pSNA node stops. No APPC/APPN communication services are available.
Customer Action: Call service with the code point, error description, and abend code value if possible. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: NOF rejected a ACTIVATE_DLC verb because the DLC was not specified.
A ACTIVATE_DLC verb was rejected because the DLC name in the verb (dlc_name) was not specified.
Function Degradation: The ACTIVATE_DLC verb is rejected, so the desired data link control is not started.
Customer Action: Re-issue the verb with correct values. If the error occurred while loading the initial network configuration or while processing the network definition file, correct the error in the file and re-load the configuration.
System Developer Action: None.
Description: NOF rejected a DEACTIVATE_DLC verb because the DLC was not specified.
A DEACTIVATE_DLC verb was rejected because the DLC name in the verb (dlc_name) was not specified.
Function Degradation: The DEACTIVATE_DLC verb is rejected, so the desired data link control is not stopped.
Customer Action: Re-issue the verb with correct values. If the error occurred while loading the initial network configuration or while processing the network definition file, correct the error in the file and re-load the configuration.
System Developer Action: None.
Additional Data: Has the following format:
Description: NOF could not create a pSNA environment (EGPE) in an attached co-processor.
The NOF process in the control point could not create the pSNA environment (EGPE) in an attached sub-system (co-processor). The possible causes of this problem are:
Function Degradation: The control point NOF process continues processing, trying to initialize any other co-processors. Unexpected results will probably follow this problem (severe errors), since the referenced sub-system (co-processor) is unavailable for use.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A node process notified NOF that it is abending by sending ABEND_NOTIFICATION to NOF.
NOF detected that one or more pSNA processes abended. The pSNA process sent an ABEND_NOTIFICATION to NOF before ending. The detected error is probably not a critical error (such as a processor exception) but it is unrecoverable. The possible causes of this problem are:
Function Degradation: The node operator facility (NOF) process terminates. The pSNA node stops. No APPC/APPN communication services are available.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: NOF received an internal inter-process signal from configuration services (CS) it does not recognize (or process).
NOF received an IPS from configuration services (CS) that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to NOF for processing. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and NOF continues to process other signals. Unexpected results will probably follow this problem, since NOF and CS are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: NOF received an internal inter-process signal an APPC component it does not recognize (or process).
NOF received an IPS from an APPC component (session manager, attach manager, or resource manager) that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to NOF for processing. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and NOF continues to process other signals. Unexpected results will probably follow this problem, since NOF and the APPC component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: A system (EGPE or OS) function failed while stopping the APPN node.
NOF encountered a system error while stopping the APPN node. NOF is processing an immediate stop request (STOP_APPN type=HARD). The list of failures includes:
Function Degradation: Normally, NOF waits 40 seconds for all the node components to end before terminating the node. Since the timer could not be started, NOF ends immediately, bringing the rest of the node down. APPC/APPN communication services are no longer available.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A node process encountered an unrecoverable error and abended. The node continues to execute.
NOF detected that one or more pSNA processes abended with an unrecoverable error. The error indication indicates that the abend is not unrecoverable. The possible causes of this problem are:
Function Degradation: NOF and the other node processes continue processing requests. Unexpected results may follow this problem, since the node process that abended is probably responsible for provided some required node services to the other pSNA components. The node process that abended may be able to recover, in which case the node may continue to execute correctly.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: NOF received an unexpected response (internal inter-process signal).
NOF received an unexpected response (IPS signal). NOF was expecting a response from another node component, but received a different signal. This condition should not occur, since NOF and the other node component should agree on the sequence of IPS signals sent between one another. An internal code problem exists within pSNA.
Function Degradation: The unexpected IPS is ignored, and NOF continues to process other signals. Unexpected results will probably follow this problem, since NOF and the other node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: A failure occurred trying to create a node process in the control point.
The main NOF process (in the APPN control point) could not create (start) a pSNA process in the control point processor. The EGPE function Pcreate failed. The possible causes of this problem are:
Function Degradation: The node operator facility (NOF) process abends. The pSNA node aborts its initialization and stops. No APPC/APPN communication services are available.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The request to set up a notification when an EGPE environment ends failed.
NOF could not add a notification to inform it when an EGPE environment ends. NOF is notified whenever the EGPE in the control point or a sub-system (co-processor) ends. If EGPE ends, that sub-system is no longer available for use by the APPN node. The EGPE function PEstart_EGPE_down_monitor failed. The possible causes of this problem are:
Function Degradation: NOF continues processing. NOF will not be able to detect the loss of an EGPE environment (EGPE sub-system). This should not be a problem unless an EGPE sub-system encounters a severe problem, in which case NOF and the other node components will experience errors when trying to access the lost sub-system. In addition, NOF will not be able to recover lost sub-systems.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: NOF received an unexpected IPS from EGPE.
NOF received a notification IPS (PE_LOST_ENVIRONMENT) from EGPE that it cannot correlate. The notification was sent by EGPE to inform NOF that an EGPE environment, probably in an attached co-processor, ended. NOF could not correlate the notification to any of the sub-systems (co-processors) it is using. This condition should not occur, since the unexpected signal should not have been routed to NOF for processing. An internal code problem exists within pSNA (NOF or EGPE).
Function Degradation: The unexpected IPS is ignored, and NOF continues to process other signals. Unexpected results will probably follow this problem, since NOF and EGPE are probably in error and out of sequence. NOF and the other node components will experience errors when trying to access the lost sub-system, and NOF will not be able to recover the lost sub-system.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: NOF received an unexpected IPS from EGPE.
NOF received a notification IPS (SS_AVAILABLE) from EGPE that it cannot correlate. The notification was sent by EGPE to inform NOF that an EGPE environment, probably in an attached co-processor, that ended has been restarted. NOF could not correlate the notification to any of the sub-systems (co-processors) it is using. This condition should not occur, since the unexpected signal should not have been routed to NOF for processing. An internal code problem exists within pSNA (NOF or EGPE).
Function Degradation: The unexpected IPS is ignored, and NOF continues to process other signals. Unexpected results will probably follow this problem, since NOF and EGPE are probably in error and out of sequence. APPN will be unaware that a lost sub-system has recovered, and will not use the sub-system (co-processor).
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: NOF received an IPS from EGPE containing invalid data.
NOF received a notification IPS (SS_AVAILABLE) from EGPE that contains invalid (unexpected) data. The notification was sent by EGPE to inform NOF that an EGPE environment, probably in an attached co-processor, that ended has been restarted. The status indicators in the notification indicate:
Function Degradation: The invalid IPS is ignored, and NOF continues to process other signals. Unexpected results will probably follow this problem, since NOF and EGPE are probably in error and out of sequence. APPN will not use the sub-system (co-processor).
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: NOF could not find the address space manager (ASM) process in a recovered sub-system.
NOF is in the process of re-starting a recovered sub-system (co-processor). NOF could not locate the ASM process in the recovered sub-system, so it cannot load the sub-system with the list of NAUs (control point and LUs) defined locally to the APPN node. This condition should not occur. NOF should have just re-started ASM in the recovered sub-system. The possible causes of this problem are:
Function Degradation: NOF stops re-starting the recovered sub-system and continues to process other signals. APPN will not use the recovered sub-system (co-processor).
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: NOF received an internal inter-process signal containing an API verb it does not recognize (or process).
NOF received an API verb that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to NOF for processing. An internal code problem exists within pSNA.
Function Degradation: The unrecognized API verb is ignored, and NOF continues to process other signals. Unexpected results will probably follow this problem, since NOF and the API verb interface layer are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: NOF received an internal inter-process signal from the API verb interface layer it does not recognize (or process).
NOF received an IPS from the API verb interface layer that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to NOF for processing. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and NOF continues to process other signals. Unexpected results will probably follow this problem, since NOF and the API verb interface layer are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The main NOF process (in the node control point) cannot forward an IPS message to the configuration control component in the system.
The command to send the IPS to the configuration control component failed. The EGPE function PDQenq failed. The possible causes of this problem are:
Function Degradation: The control point NOF process continues processing. Unexpected results will probably follow this problem since the configuration control component is now out-of-sync with the node.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A node component encountered an error while processing a NOF request.
Another component in the node encountered an error while processing a request received from NOF. It sent an EXCEPTION_RSP IPS message indicating the failure. The EXCEPTION_RSP message contains a sense code that identifies the cause of the failure. The possible causes of this problem are:
Function Degradation: NOF and the other node processes continue processing requests. Unexpected results may follow this problem, since the failed function will probably affect the processing of other requests in the node.
Customer Action: Try and determine the cause of the problem. Refer to related log entries and messages for more information and other recommended actions.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A failure occurred trying to create and start EGPE an attached sub-system (co-processor).
NOF could not create (start) the processing environment (EGPE) required by pSNA in the attached sub-system (co-processor). None of the ports or links supplied by the attached sub-system can be used by the node. The EGPE function PEdefine_subsystem failed.
The possible causes of this problem are:
Function Degradation: The control point NOF process continues processing. The attached co-processor is unavailable for use by the node. Any ports or links provided by the co-processor are also unavailable.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A failure occurred trying to create and start EGPE an attached sub-system (co-processor).
NOF could not create (start) the processing environment (EGPE) required by pSNA in the attached sub-system (co-processor). None of the ports or links supplied by the attached sub-system can be used by the node. The EGPE function PEcreate_environment failed.
The possible causes of this problem are:
Function Degradation: The control point NOF process continues processing. The attached co-processor is unavailable for use by the node. Any ports or links provided by the co-processor are also unavailable.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: This log record is created in conjunction with the log record 2F104000-00000008. This log record is used to log additional information associated with the problem identified by the other log record. Refer to the description of 2F104000-00000008 for more information.
Function Degradation: Refer to the description of the associated log record.
Customer Action: Refer to the description of the associated log record.
System Developer Action: Refer to the description of the associated log record.
Additional Data: Has the following format:
Description: A failure occurred trying to create and start one or more ports in an attached sub-system (co-processor).
NOF could not create (start) one or more ports because the data link control used by the ports is not compatible with the hardware in the referenced sub-system. None of the ports or links supplied by the attached sub-system can be used by the node. The possible causes of this problem are:
Function Degradation: The control point NOF process continues processing. The attached co-processor is unavailable for use by the node. Any ports or links provided by the co-processor are also unavailable.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: NOF encountered a problem trying to start the SIGNOFF service transaction program. The request to start the service transaction program (Pcreate) failed. The probable causes are:
Function Degradation: NOF continues processing. Unexpected results will probably follow this problem, since a SIGNOFF flow could not be sent to a partner LU.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: NOF received an internal sense code from configuration services (CS) or Session Services (SS) that it does not recognize.
NOF received a sense code from configuration services (CS) or Session Services (SS) that it does not recognize. This condition should have occured because of an internal code bug within pSNA.
Function Degradation: NOF sets a primary RC 'STATE_CHECK' and a secondary RC of 'INVALID_PA_VERB_VARIANT' in the verb control block. Unexpected results may probably follow this problem, since NOF is probably in error and out of sync with CS or SS.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug to see which sense code sent by CS or SS was not recognized by NOF and which module in NOF received this. Add to this module appropriate code for handling this sense code.
Additional Data: Has the following format:
Description: A STOP_APPN verb timer expired before all of the components responded with STOP_APPN_CLEANUP responses.
Function Degradation: The STOP_APPN verb completes the termination process.
Customer Action: None.
System Developer Action: Normally this event does not indicate a problem. If a particular component continually does not complete its STOP_APPN_CLEANUP processing, or if a component has difficultly restarting after STOP_APPN; the programmer may investigate why STOP_APPN_CLEANUP processing is taking too long to complete normally.
Log events for the path control (PC), address space manager (ASM), and session connector (SC) components of APPN.
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Description: A software problem exists within pSNA.
PC could not determine the PC logical process responsible for handling a message received via a session connector (intermediate session). The PC logical process handling the TG/link that is supposed to handle the session connector's messages does not exist. The probable causes are:
Function Degradation: The error was detected while updating the SNMP counters for the message's session connector. Processing of the message continues, but the session connector statistics are not updated with the information contained in the message. Unexpected results may follow this problem, since the tables in path control used to route messages internally are probably in error and out of sequence.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The address space manager (ASM) received an SNA message it does not recognize (or process).
An address space manager received a SNA message (MU) that it does not recognize or process. ASM only processes session messages, such as BIND, UNBIND, and ACTPU/ACTLU. This condition should not occur, since the unrecognized message should not have been routed to ASM for processing. An internal code problem exists within pSNA.
Function Degradation: The detecting address space manager process abends. The same process is used to process all messages sent and received for the related TG/link, so no further communications is available over that link (or any of the sessions that use the link). The adjacent node may not be notified of the abnormal termination until messages it sends are rejected.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The address space manager received a message containing unrecognized information (control vectors).
Address space manager received a message containing a control vector X'0E' with invalid/unrecognized sub-vectors. pSNA does not recognize or support one or more of the sub-vectors contained in the received control vector. The probable causes are:
Function Degradation: Processing of the message continues, but the unrecognized sub-vector is ignored. Unexpected results may follow this problem, since part of the message is ignored, and also because the communications support in the nodes are either in error or are incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The address space manager received a message containing unrecognized information (control vectors).
Address space manager received a message containing an unrecognized/unsupported control vector. pSNA does not recognize or support one or more of the control vectors contained in the received message. The probable causes are:
Function Degradation: Processing of the message continues, but the unrecognized control vector is ignored. Unexpected results may follow this problem, since part of the message is ignored, and also because the communications support in the nodes are either in error or are incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The address space manager received a message containing invalid control vector information. The lengths of a set of control vectors (or sub-vectors) does not correspond to the expected length indicated by the containing SNA vector.
Address space manager received a message containing invalid control vectors. The length of a set of control vectors (or their contained sub-vectors) does not match the expected length obtained from the containing SNA structure (higher level control vector). The probable causes are:
Function Degradation: The received message is rejected with an 086F0000 sense code.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Path control encountered a should-not-occur condition. An internal control block is invalid. A programming error/deficiency exists within the pSNA node. This condition should not occur. A software problem exists in the node that sent the message, or the APPC/APPN support in the remote node is not compatible (which should never happen) with the pSNA APPC/APPN support.
The address space manager related to the path control instance cannot be determined. The address of the related address space manager control block in the path control instance is invalid.
Function Degradation: The detecting path control process abends. The same process is used to process all messages sent and received for the related TG/link, so no further communications is available over that link (or any of the sessions that use the link). The adjacent node may not be notified of the abnormal termination until messages it sends are rejected.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The address space manager (ASM) received an internal inter-process signal it does not recognize (or process).
An address space manager received an IPS that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to ASM for processing. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and ASM continues to process other signals. Unexpected results will probably follow this problem, since ASM or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: A software problem exists within pSNA (ASM).
An address space manager received an IPS via an unrecognized process queue. This condition should never occur, since ASM defines all possible queues it can receive IPS data from. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and ASM continues to process other signals. Unexpected results will probably follow this problem, since ASM or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: A software problem exists within pSNA (ASM).
An address space manager process unexpectedly exited its internal signal processing loop. This condition should never occur. An internal code problem exists within pSNA.
Function Degradation: The issuing address space manager process abends. The same process is used to process all messages sent and received for the related TG/link, so no further communications is available over that link (or any of the sessions that use the link). The adjacent node may not be notified of the abnormal termination until messages it sends are rejected.
Customer Action: Call service with the code point, error description, and abend code value if possible. In addition, a process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
If possible, try and re-create the problem with ASM traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Path control (PC) receive FSM received an SNA message it does not recognize (or process). A software problem exists within pSNA (PC).
The path control receive router FSM received an unexpected or unrecognized input message (MU). The received message is a single-segment message. This condition should not occur, since the FSM should be robust enough to handle any valid message, and only valid messages should be passed to the FSM. An internal code problem exists within pSNA.
Function Degradation: The received message is ignored, and processing continues. Unexpected results will probably follow this problem, since PC is probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Path control (PC) receive FSM received an SNA message it does not recognize (or process). A software problem exists within pSNA (PC).
The path control receive router FSM received an unexpected or unrecognized input message (MU). The received message is the first segment in a multi-segmented message. This condition should not occur, since the FSM should be robust enough to handle any valid message, and only valid messages should be passed to the FSM. An internal code problem exists within pSNA.
Function Degradation: The received message is ignored, and processing continues. Unexpected results will probably follow this problem, since PC is probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Path control (PC) receive FSM received an SNA message it does not recognize (or process). A software problem exists within pSNA (PC).
The path control receive router FSM received an unexpected or unrecognized input message (MU). The received message is a middle segment in a multi-segmented message. The request code was obtained from the first segment. This condition should not occur, since the FSM should be robust enough to handle any valid message, and only valid messages should be passed to the FSM. An internal code problem exists within pSNA.
Function Degradation: The received message is ignored, and processing continues. Unexpected results will probably follow this problem, since PC is probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Path control (PC) receive FSM received an SNA message it does not recognize (or process). A software problem exists within pSNA (PC).
The path control receive router FSM received an unexpected or unrecognized input message (MU). The received message is the last segment in a multi-segmented message. The request code was obtained from the first segment. This condition should not occur, since the FSM should be robust enough to handle any valid message, and only valid messages should be passed to the FSM. An internal code problem exists within pSNA.
Function Degradation: The received message is ignored, and processing continues. Unexpected results will probably follow this problem, since PC is probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Path control (PC) receive FSM received an SNA message it does not recognize (or process). A software problem exists within pSNA (PC).
The path control (PC) receive router FSM outputted an unknown or invalid action code. The probable causes are:
Function Degradation: The input value is ignored, and processing continues. Unexpected results will probably follow this problem, since PC is probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Implement code fix.
Additional Data: Has the following format:
Description: Path control (PC) received an invalid IPS message from a DLC. A software problem exists within pSNA (PC).
Path control (PC) received an invalid IPS message from DLC. The received IPS was a DLC OPEN_STN message, but it was not a confirmation. This condition should not occur, since the DLC should only send OPEN_STN confirmations (and no other types) to path control. An internal code problem exists within pSNA.
Function Degradation: The input IPS is ignored, and processing continues. Unexpected results will probably follow this problem, since PC and a DLC are probably in error and out of sequence. Depending on the sequence of events, path control may explicitly deactivate the TG (link).
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Path control (PC) received an invalid IPS message from a DLC. A software problem exists within pSNA (PC).
Path control (PC) received an invalid IPS message from DLC. The received IPS was a DLC DATA message, but it was not an indication. This condition should not occur, since the DLC should only send DATA indications (and no other types) to path control. An internal code problem exists within pSNA.
Function Degradation: The input IPS is ignored, and processing continues. Unexpected results will probably follow this problem, since PC and a DLC are probably in error and out of sequence. Depending on the sequence of events, path control may explicitly deactivate the TG (link).
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Path control (PC) received an invalid IPS message from a DLC. A software problem exists within pSNA (PC).
Path control (PC) received an invalid IPS message from DLC. The received IPS was a DLC CLOSE_STN message, but it was not a confirmation. This condition should not occur, since the DLC should only send CLOSE_STN confirmations (and no other types) to path control. An internal code problem exists within pSNA.
Function Degradation: The input IPS is ignored, and processing continues. Unexpected results will probably follow this problem, since PC and a DLC are probably in error and out of sequence. Depending on the sequence of events, path control may explicitly deactivate the TG (link).
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Path control (PC) received an invalid IPS message from a DLC. A software problem exists within pSNA (PC).
Path control (PC) received an invalid IPS message from DLC. The received IPS was an DLC message not recognized or supported by path control. This condition should not occur, since the DLC should only send valid DLC messages that path control understands. An internal code problem exists within pSNA.
Function Degradation: The input IPS is ignored, and processing continues. Unexpected results will probably follow this problem, since PC and a DLC are probably in error and out of sequence. Depending on the sequence of events, path control may explicitly deactivate the TG (link).
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Path control (PC) received an unexpected IPS message from a DLC. A software problem exists within pSNA (PC).
Path control (PC) received an recognized but unexpected DLC message from a DLC. The received IPS was a DLC DATA response or confirmation, which path control recognizes but does not process (ignores). This condition should not occur, since the DLC should not send DATA responses and confirmations. An internal code problem exists within pSNA.
Function Degradation: The input IPS is ignored, and processing continues. Unexpected results may follow this problem, since PC and a DLC are probably in error and out of sequence. It is also possible in this case that no adverse side affects, other than performance degradation, are observed.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Path control (PC) received a DATA indication before the link station is open. A software problem exists within pSNA (PC).
Path control (PC) received an out-of-sequence IPS message from a DLC. The received IPS was an DLC DATA indication message, but path control does not believe the link station is opened (it has not received the OPEN_STN confirmation from the DLC). This condition should not occur, since the DLC should not send DATA indications until the link station is open (i.e. the OPEN_STN confirmation should precede any DATA indications). An internal code problem exists within pSNA.
Function Degradation: The input IPS is ignored, and processing continues. Unexpected results will probably follow this problem, since PC and a DLC are probably in error and out of sequence. This problem may indicate the loss of data received from an adjacent node (the data contained in the DATA indication).
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Path control (PC) received a DATA indication after a link station (TG) was closed. A software problem exists within pSNA (PC).
Path control (PC) received an out-of-sequence IPS message from a DLC. The received IPS was an DLC DATA indication message, but path control believes the link station is closed (it received a DESTROY_TG signal for the TG related to the link station). This condition should not occur, since the DLC should not send DATA indications after the link station is closed (i.e. no DATA indications should follow the DESTROY_TG signal for a link station). An internal code problem exists within pSNA.
Function Degradation: The input IPS is ignored, and processing continues. Unexpected results will probably follow this problem, since PC and a DLC are probably in error and out of sequence. This problem may indicate the loss of data received from an adjacent node (the data contained in the DATA indication).
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Path control (PC) received an invalid IPS message from a DLC. A software problem exists within pSNA (PC).
Path control (PC) received an invalid IPS message from DLC. The received IPS was an DLC message not recognized or supported by path control. This event is usually logged with another event that specifies the DLC message that was received (2F105000-00000010 through 2F105000-00000013). This condition should not occur, since the DLC should only send valid DLC messages that path control understands. An internal code problem exists within pSNA.
Function Degradation: The input IPS is ignored, and processing continues. Unexpected results will probably follow this problem, since PC and a DLC are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Path control (PC) received an invalid IPS or out-of-sequence message from a DLC. A software problem exists within pSNA (PC).
Path control (PC) received an invalid IPS message or a valid IPS message in an incorrect sequence. This event is usually logged with another event that specifies the DLC message that was received (2F105000-00000010 through 2F105000-00000017). This condition should not occur, since the DLC should only send CLOSE_STN confirmations (and no other types) to path control. An internal code problem exists within pSNA.
Function Degradation: The input IPS is ignored, and processing continues. Path control deactivates the TG (link).
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Refer to related log entries and messages for more information and other recommended actions. Isolate and implement a code fix.
Description: Path control generated an alert.
Path control/address space manager/session connector detected an alertable condition and sent the formatted SNA alert to MS for transmission to its alert focal point.
Function Degradation: The actual functional consequences depend on the detected condition (the generated alert).
Customer Action: Refer to the information contained in the alert, as well as related log entries and messages for more information and recommended actions.
System Developer Action: None.
Additional Data: Has the following format:
Description: An instance of path control could not open an EGPE dialog with configuration services and/or the corresponding DLC.
The path control instance could not open an EGPE process dialog with the APPN control point configuration services component and/or the DLC associated with the instance's link (TG). The possible causes of this problem are:
Function Degradation: The TG (link) activation attempt fails.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A software problem exists within pSNA (PC).
Path control (PC) specified an invalid transmission priority queue. An internal code problem exists within pSNA.
Function Degradation: Processing continues. Unexpected results may follow this problem, since PC is probably in error.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: A software problem exists within pSNA (PC).
Path control (PC) encountered a should-not-occur situation. The internal counter used to manage the transmission priority queues and the associated aging algorithm has an invalid value. An internal code problem exists within pSNA.
Function Degradation: Processing continues. Unexpected results may follow this problem, since PC is probably in error.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: A instance of path control (PC) received an internal inter-process signal it does not recognize (or process).
An instance of path control received an IPS that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to PC for processing. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and PC continues to process other signals. Unexpected results will probably follow this problem, since PC or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The path control process received a DLC PONG response from a DLC, but the path control instance identified in the response does not exist.
The path control main process received a PONG response from a DLC, but the path control instance identified in the response does not exist. The EGPE logical process ID of the path control instance is invalid. An internal code problem exists within pSNA.
Function Degradation: The PONG response is ignored, and processing continues. Unexpected results will probably follow this problem, since PC and a DLC are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Path control (PC) received an unknown inter-process signal from a DLC. Path control does not recognize (or process) the received signal.
Path control received an invalid DLC IPS from a DLC. PC does not recognize the DLC command contained in the received signal. This condition should not occur, since the unrecognized DLC command should not have been routed to PC for processing. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and PC continues to process other signals. Unexpected results will probably follow this problem, since the DLC is probably in error and out of sequence with PC.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Path control (PC) received an unknown inter-process signal from a DLC. Path control does not recognize (or process) the received signal.
Path control received an invalid IPS from a DLC. PC does not recognize (or process) the received inter-process signal. This condition should not occur, since the unrecognized signal should not have been routed to PC for processing. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and PC continues to process other signals. Unexpected results will probably follow this problem, since the DLC is probably in error and out of sequence with PC.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Path control encountered a should-not-occur condition. An internal control block is invalid. A programming error/deficiency exists within the pSNA node. This condition should not occur. An internal code problem exists within pSNA.
One or more of the outbound priority queues for a transmission group (TG) contains invalid data.
Function Degradation: The detecting path control process abends. The same process is used to process all messages sent and received for the related TG/link, so no further communications is available over that link (or any of the sessions that use the link). The adjacent node may not be notified of the abnormal termination until messages it sends are rejected.
Customer Action: Call service with the code point and error description. Supply any pSNA dump information. A process abend file containing a snapshot of the pSNA storage areas should have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: A session connector (SC) received an internal inter-process signal it does not recognize (or process).
A session connector received an IPS that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to a SC for processing. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and the session connector continues to process other signals. Unexpected results will probably follow this problem, since PC/SC or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: A session connector received an internal inter-process signal, but cannot find the control blocks associated with the session connector.
The path control/session connector main process received an inter-process signal that it cannot route. The EGPE logical process identified in the signal is a session connector, but the process-specific control blocks cannot be located. An internal code problem exists within pSNA.
Function Degradation: The IPS is ignored, and processing continues. Unexpected results will probably follow this problem, since PC/SC is probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Path control (PC) encountered a should-not-occur condition within the software. A software problem exists within pSNA (PC).
Path control (PC) encountered a should-not-occur condition while trying to send a CREATE_TG response. PC expected to use the saved CREATE_TG request to construct the response, but the request no longer exists. This condition should not occur. An internal code problem exists within pSNA.
Function Degradation: The request to send the CREATE_TG response is ignored and processing continues. Unexpected results (hang conditions) will probably follow this problem, since other node components are probably waiting for the response that could not be sent. In addition, PC is probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Path control (PC) encountered a should-not-occur condition within the software. A software problem exists within pSNA (PC).
Path control (PC) encountered a should-not-occur condition while trying to send a DESTROY_TG response. PC expected to use the saved DESTROY_TG request to construct the response, but the request no longer exists. This condition should not occur. An internal code problem exists within pSNA.
Function Degradation: The request to send the DESTROY_TG response is ignored and processing continues. Unexpected results (hang conditions) will probably follow this problem, since other node components are probably waiting for the response that could not be sent. In addition, PC is probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: A session connector (SC) received an invalid or out-of-sequence inter-process signal. A software problem exists within pSNA (SC).
A session connector (SC) received an invalid IPS message or a valid IPS message in an incorrect sequence. This condition should not occur, since the session connector FSM should be able to handle all valid signals, in any valid sequence. An internal code problem exists within pSNA.
Function Degradation: The input IPS is ignored, and processing continues. Unexpected results will probably follow this problem, since SC or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: A session connector received an invalid SNA message from a partner node.
A session connector received an invalid SNA message. The transmission header (TH) indicates that the message is the first or only segment of the message, but the message is not large enough to hold an SNA request/response header (RH). This condition should not occur. A software problem exists in the node that sent the message.
Function Degradation: The received message is ignored, and processing continues. Unexpected results will probably follow this problem, since the data contained in the ignored message is lost.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: A session connector received an invalid SNA message, an out-of-sequence SNA message, or detected another severe error condition that caused to terminate the session connector.
A session connector encountered a severe error that caused it to terminate immediately. Examples of errors that would cause this problem are:
Function Degradation: The detecting session connector is aborted (ended). The related session is terminated.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: A path control instance (PC) received an SNA message it does not recognize (or process).
A path control instance received a SNA message (MU) that it does not recognize or process. This condition should not occur, since the unrecognized message should not have been routed to PC for processing. An internal code problem exists within pSNA.
Function Degradation: The received message is ignored, and processing continues. Unexpected results will probably follow this problem, since the data contained in the ignored message is lost.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: An instance of path control could not open an EGPE dialog with configuration services and/or the corresponding DLC.
The path control instance could not open an EGPE process dialog with the APPN control point configuration services component and/or the DLC associated with the instance's link (TG). Either the response was received after the path control instance ended or the dialog ID contained in the response does not match the expected dialog ID. The possible causes of this problem are:
Function Degradation: The TG (link) activation attempt fails.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Description: Path control (PC) received an SNA message that contains invalid SNA headers (TH or RH settings are invalid).
Path control (PC) received an invalid SNA message from another node. The received message did not pass the basic SNA message verification checks (validating TH and RH settings). The probable causes are:
Function Degradation: The input IPS is ignored, and processing continues. Unexpected results will probably follow this problem, since the data contained in the message is lost. In addition, the communications support in the nodes are either in error or are incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: A session connector, path control instance, or address space manager received an invalid SNA message from a partner node.
pSNA received an invalid SNA message. The message failed the basic SNA integrity checks. Some sample message problems and the sense code used to reject the message are:
Function Degradation: The received message is rejected with the indicated sense code. An alert is generated and sent to the alert focal point.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: A software problem exists within pSNA.
PC could not determine the PC logical process responsible for handling a message received via a session connector (intermediate session). The PC logical process handling the TG/link that is supposed to handle the session connector's messages does not exist. The probable causes are:
Function Degradation: The error was detected while updating the SNMP counters for the message's session connector. Processing of the message continues, but the session connector statistics are not updated with the information contained in the message. Unexpected results may follow this problem, since the tables in path control used to route messages internally are probably in error and out of sequence.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Not used yet.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Description: A software problem exists within pSNA.
The address space manager could not determine the address space responsible for handling the messages processed by a particular path control instance. The address space for the path control instance does not exist. The probable causes are:
Function Degradation: The results of this error depend on the message being processed. In some cases, the received message is rejected with the sense code 0806002D. In most occurrences the error is ignored and processing of the message continues. Unexpected results may follow this problem, since in most cases the local node continues to process the message even though the address space could not be determined. In addition, either the internal tables in path control used to route messages internally are probably in error and out of sequence, or the communications support in the nodes are either in error or are incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The address space manager encountered an error while trying to create a new address space.
The address space manager could not create an address space for a new path control instance. The related path control instance could not be determined, or the attempt to access the path control control block failed. The possible causes of this problem are:
Function Degradation: The request to activate the address space fails. The related path control instance, as well as its associated links, TGs, and sessions, are de-activated. Communications with the remote node via the associated link are no longer available. Depending on why the connection was terminated, the remote node may try and re-establish the connection later.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The address space manager encountered an error while trying to create a new address space.
The address space manager could not create an address space for a new path control instance. The required buffers could not be allocated. The local node does not have enough memory available to accept the new address space (and its possible sessions).
Function Degradation: The request to activate the address space fails. The related path control instance, as well as its associated links, TGs, and sessions, are de-activated.
Communications with the remote node via the associated link are no longer available. Depending on why the connection was terminated, the remote node may try and re-establish the connection later.
Customer Action: Increase the amount of memory available to the pSNA node. Either stop any unneeded sessions and links, or stop and re-start the local node with more memory.
System Developer Action: None.
Additional Data: Has the following format:
Description: The address space manager received a message containing an invalid LFSID.
Address space manager received a message containing an invalid/unrecognized LFSID. Possible problems include:
The probable causes are:
Function Degradation: The received message is rejected with an 800F0000 sense code. The address space that received the message is deactivated. As a result, the sessions associated with the detecting address space are de-activated.
In addition, the local node generates and sends an alert to its focal point.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. The remote node is probably in error since the received message is invalid.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The address space manager received an invalid message.
Address space manager received a segmented message, but the received message should not be segmented. In other words, the received message is not allowed to be segmented, but the segmentation indicators in the transmission header (TH) indicate the message is not a only segment message. For example, UNBIND messages as well as messages received from an SSCP should not be segmented.
The probable causes are:
Function Degradation: The received message is rejected with an 80070000 sense code. The address space that received the message, as well as its related path control instance, are de-activated. As a result, the links, TGs, and sessions associated with the detecting path control are de-activated. Communications with the remote node via the associated link are no longer available.
In addition, the local node generates and sends an alert to its focal point.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. The remote node is probably in error since the received message is invalid.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The address space manager received an invalid message.
The address space manager could not process a received message. The message contained invalid SNA control information. Some of these errors include:
The probable causes are:
Function Degradation: The received message is rejected with the indicated sense code.
If the received message violated SNA segmentation protocols or is too large, the address space that received the message, as well as its related path control instance, are de-activated As a result, the links, TGs, and sessions associated with the detecting path control are de-activated. Communications with the remote node via the associated link are no longer available.
In addition, the local node generates and sends an alert to its focal point.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. The remote node is probably in error since the received message is invalid. The local node may have created additional log entries that further describe the problem. Refer to these related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The address space manager received an invalid message.
The address space manager could not process a received message. The message contained invalid SNA control information. Some of these errors include:
The probable causes are:
Function Degradation: The received message is rejected with the indicated sense code.
If the received message violated SNA segmentation protocols or is too large, the address space that received the message, as well as its related path control instance, are de-activated As a result, the links, TGs, and sessions associated with the detecting path control are de-activated. Communications with the remote node via the associated link are no longer available.
In addition, the local node generates and sends an alert to its focal point.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. The remote node is probably in error since the received message is invalid. The local node may have created additional log entries that further describe the problem. Refer to these related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The address space manager received an invalid pacing message.
The address space manager could not process a received pacing message (IPM). The message contained invalid SNA control information. The received IPM violated SNA segmentation rules. The received message is multi-segmented, but IPM messages are not allowed to be segmented.
The probable causes are:
Function Degradation: The received message is rejected with the indicated sense code.
The address space that received the message, as well as its related path control instance, are de-activated As a result, the links, TGs, and sessions associated with the detecting path control are de-activated. Communications with the remote node via the associated link are no longer available.
In addition, the local node generates and sends an alert to its focal point.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. The remote node is probably in error since the received message is invalid.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The address space manager received an invalid pacing message.
The address space manager could not process a received pacing message (IPM). The message contained invalid SNA control information.
The probable causes are:
Function Degradation: The received message is rejected with the indicated sense code.
The address space that received the message, as well as its related path control instance, are de-activated As a result, the links, TGs, and sessions associated with the detecting path control are de-activated. Communications with the remote node via the associated link are no longer available.
In addition, the local node generates and sends an alert to its focal point.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. The remote node is probably in error since the received message is invalid.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The address space manager received an unexpected BIND pacing message.
The address space manager received an SNA isolated pacing message (IPM) from a TG that is not allowed to perform adaptive pacing (i.e. use IPMs) for BIND messages. The local node and the node that sent the IPM negotiated that adaptive BIND pacing would not be used on the TG the IPM was received from.
The probable causes are:
Function Degradation: The received message is rejected with the indicated sense code.
The address space that received the message, as well as its related path control instance, are de-activated As a result, the links, TGs, and sessions associated with the detecting path control are de-activated. Communications with the remote node via the associated link are no longer available.
In addition, the local node generates and sends an alert to its focal point.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. The remote node is probably in error since the received message is invalid.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The address space manager received an unexpected BIND pacing message.
The address space manager received an SNA isolated pacing message (IPM) while in the process of receiving a multi-segmented message from the node that sent the IPM. IPM messages are only allowed to be sent until all the segments of the previously transmitted message are sent.
The probable causes are:
Function Degradation: The received message is rejected with the indicated sense code.
The address space that received the message, as well as its related path control instance, are de-activated As a result, the links, TGs, and sessions associated with the detecting path control are de-activated. Communications with the remote node via the associated link are no longer available.
In addition, the local node generates and sends an alert to its focal point.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. The remote node is probably in error since the received message is invalid.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The address space manager encountered an error while trying to respond to a BIND pacing message.
The address space manager could not send an acknowledgement to a BIND pacing message because it could not obtain the buffer needed to build the acknowledgement. The probable causes are:
Function Degradation: The received message is rejected with the indicated sense code.
The address space that received the message, as well as its related path control instance, are de-activated As a result, the links, TGs, and sessions associated with the detecting path control are de-activated. Communications with the remote node via the associated link are no longer available.
In addition, the local node generates and sends an alert to its focal point.
Customer Action: Try and determine if the problem was caused by a memory shortage, an error in the local node (pSNA), or an error in the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The address space manager received an unexpected BIND pacing message.
The address space manager received an SNA isolated pacing message (IPM) that indicates it was solicited by the local node, but the local node did not solicit the IPM. APPN nodes solicit IPMs when they wish to send more messages but have already sent all the messages allowed by the last pacing message received from the remote node. The local node received a solicited IPM message from the remote node but it still is allowed to send more messages (the new window size is non-zero in SNA terms).
The probable causes are:
Function Degradation: The received message is rejected with the indicated sense code.
The address space that received the message, as well as its related path control instance, are de-activated As a result, the links, TGs, and sessions associated with the detecting path control are de-activated. Communications with the remote node via the associated link are no longer available.
In addition, the local node generates and sends an alert to its focal point.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. The remote node is probably in error since the received message is invalid.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The address space manager received an invalid pacing message.
The address space manager could not process a received pacing message (IPM). The contents of the received message are invalid. The received message is a solicited IPM message, but the allowed next window size, as specified in the received message, is zero. APPN nodes should not send solicited IPM messages with a next window size of zero since the receiving node is already waiting for a pacing message before it will send any additional data.
The probable causes are:
Function Degradation: The received message is rejected with the indicated sense code.
The address space that received the message, as well as its related path control instance, are de-activated As a result, the links, TGs, and sessions associated with the detecting path control are de-activated. Communications with the remote node via the associated link are no longer available.
In addition, the local node generates and sends an alert to its focal point.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. The remote node is probably in error since the received message is invalid.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The address space manager received an unexpected BIND pacing message.
The address space manager received an SNA isolated pacing acknowledgment message (IPM) that acknowledges a request from the local node to reset the pacing window size (the number of messages allowed to be sent). The local node did not send a request to reset the pacing window size.
In more detailed SNA terms, the local node received a reset acknowledgment IPM from the remote node. The local node either does not support adaptive pacing or has not sent an unsolicited pacing message yet, so the acknowledgement is for a message that was never sent.
The probable causes are:
Function Degradation: The received message is rejected with the indicated sense code.
The address space that received the message, as well as its related path control instance, are de-activated As a result, the links, TGs, and sessions associated with the detecting path control are de-activated. Communications with the remote node via the associated link are no longer available.
In addition, the local node generates and sends an alert to its focal point.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. The remote node is probably in error since the received message is invalid.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The address space manager received an invalid pacing message.
The address space manager could not process a received pacing message (IPM). The message type in the received message are invalid.
The probable causes are:
Function Degradation: The received message is rejected with the indicated sense code.
The address space that received the message, as well as its related path control instance, are de-activated As a result, the links, TGs, and sessions associated with the detecting path control are de-activated. Communications with the remote node via the associated link are no longer available.
In addition, the local node generates and sends an alert to its focal point.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. The remote node is probably in error since the received message is invalid.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The address space manager encountered an error while trying to accept a new session.
The address space manager rejected a request to create a new session with a remote node because the LFSID in the BIND request is already assigned to another session.
The probable causes are:
Function Degradation: The local node rejects the BIND request with the indicated sense code.
Customer Action: Try and determine the cause of the problem:
Verify that the problem was not caused by a communications error in the network that caused a temporary network race condition. Try and re-start the session if you suspect a network race condition may have caused the problem. Otherwise the problem is the result of an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The address space manager is rejecting any outstanding session creation requests because the LU or control point (CP) is being stopped.
The address space manager was processing a session initiation request (BIND) from another node when the related LU or CP was deactivated (by operator request). This condition is not an error condition. The event is logged so that problem determination personnel can determine why a session was rejected.
Function Degradation: The local node rejects all BIND requests outstanding for the LU or CP being stopped, as well as terminating all existing sessions that use the LU or CP.
Customer Action: Try and determine why the LU or CP was stopped. If the outage was unexpected, re-start the LU or CP and try and re-start all lost and outstanding sessions.
System Developer Action: None.
Additional Data: Has the following format:
Description: The address space manager encountered an error while trying to accept a new session.
The address space manager rejected a request to create a new session with a remote node because the LFSID in the BIND request is already assigned to another session according to the address space manager.
The probable causes are:
Function Degradation: The local node rejects the BIND request with the indicated sense code.
Customer Action: Try and determine the cause of the problem:
Verify that the problem was not caused by a communications error in the network that caused a temporary race condition. Try and re-start the session if you suspect a network race condition may have caused the problem. Otherwise the problem is the result of an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The address space manager received an invalid BIND message.
The address space manager could not process a received session initiation request (BIND). The BIND contained invalid SNA control information. Some of these errors include:
The probable causes are:
Function Degradation: The received message is rejected with the indicated sense code.
The address space that received the message, as well as its related path control instance, are de-activated As a result, the links, TGs, and sessions associated with the detecting path control are de-activated. Communications with the remote node via the associated link are no longer available.
In addition, the local node generates and sends an alert to its focal point.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. The remote node is probably in error since the received message is invalid.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: Not used yet.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Description: A software problem exists within pSNA.
The local node could not determine the path control or session connector logical process responsible for handling a message received from another component within the node (probably a half-session, another path control instance, or another session connector instance). A programming error exists within the pSNA node
Function Degradation: The received message is ignored and processing continues. Unexpected results will probably follow this problem, since one or more of the internal components within the node are are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: An instance of path control lost its dialog with configuration services or one of its underlying DLCs.
One of the dialogs used by path control, address space manager, and the session connectors in the main control point or an I/O processor has been terminated. The components in the control point used these dialogs to communicate with their underlying DLC components to send and receive messages. The components in the I/O processors also use dialogs to access their DLC components, as well as access configuration services in the main processor. he possible causes of this problem are:
Function Degradation: The detecting patch control process abends. The same process is used to process all messages sent and received for the related TG/link, so no further communications is available over that link (or any of the sessions that use the link). The adjacent node may not be notified of the abnormal termination until messages it sends are rejected.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The address space manager received an invalid SNA message (DACTLU).
The address space manager could not process a received request to deactivate an LU-SSCP session (DACTLU). The LFSID (DAF) contained in the DACTLU was invalid (the indicated LU-SSCP session is not active).
The probable causes are:
Function Degradation: The received message is rejected with the indicated sense code. Unexpected results may follow this problem, since the local node and remote node appear to be incompatible with one another.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. The remote node is probably in error since the received message is invalid.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The address space manager received an invalid SNA message (ACTLU).
The address space manager could not process a received request to activate an LU-SSCP session (ACTLU). The profiles specified in the ACTLU are invalid.
The probable causes are:
Function Degradation: The received message is rejected with the indicated sense code. Unexpected results may follow this problem, since the local node and remote node appear to be incompatible with one another.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. The remote node is probably in error since the received message is invalid.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The APPN path control component (PC) received an unexpected internal inter-process signal.
The IPS was received before PC was ready to process the received message. This condition should not occur, since the unrecognized signal should not have been routed to PC for processing. An internal code problem exists within pSNA. PC received the unexpected IPS while waiting for a response to its monitor request (PEstart_ready_monitor) for a half session (HS).
Function Degradation: The unexpected IPS is ignored, and PC continues to process other signals. Unexpected results will probably follow this problem, since PC or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: APPN ASM has a null Process_ID associated with the LFSID.
The APPN Address Space Manager component (ASM) has determined that it is using an LFSID, but does not know if it is in use by SM. So while trying to send an LFSID_IN_USE IPS, it has found out that it has a invalid session type and a NULL Process_ID associated with that LFSID. This condition should not occur. An internal code problem exists within pSNA. ASM cannot PQenq the LFSID_IN_USE IPS to any process.
Function Degradation: The LFSID_IN_USE IPS is not sent to any other process and ASM will continue to process other signals. Unexpected results will probably follow this problem, since PC or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: APPN ASM has received an invalid LFSID.
The APPN Address Space Manager component (ASM) has received a free_lfsid call and determined that either sidh or sidl is invalid. There is no entry corresponding to either sidh or sidl index in the respective tables. This condition should not occur. An internal code problem exists within pSNA. ASM cannot handle this request.
Function Degradation: The FREE_LFSID is ignored and ASM will continue to process other signals. Unexpected results will probably follow this problem, since PC or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: APPN ASM Could Not Allocate AS
The APPN Address Space Manager component (ASM) The Address Space Manager does not have resources to allot the address space for the incoming session request. Asm can not validate this request.
Function Degradation: The incoming session request would have been rejected.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. If it is dependent session Please change the definitions in dlus and provid a quick workaround. Isolate and implement a code fix.
Log events for the session connector manager component of APPN (SCM).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: The request to verify that session services and/or configuration services is available failed.
The session connector manager could not verify that APPN session services and/or configuration services is active and available. The EGPE function PEstart_ready_monitor failed. The possible causes of this problem are:
Function Degradation: The session connector manager process abends. The pSNA node aborts its initialization and stops. No APPC/APPN communication services are available.
Customer Action: Try and determine the cause of the problem:
If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The request to start monitoring the status of the SNA buffer manager storage status failed.
The session connector manager could not start monitoring the status of the SNA buffer manager buffer pool status. The session connection manager monitors the status and is notified when the storage status is constrained or worse. The buffer manager function Bstatus_monitor failed. The possible causes of this problem are:
Function Degradation: The session connector manager process abends. The pSNA node aborts its initialization and stops. No APPC/APPN communication services are available.
Customer Action: Try and determine the cause of the problem:
If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The session connection manager (SCM) received an internal inter-process signal it does not recognize (or process).
The session connector manager received an IPS that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to SCM for processing. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and SCM continues to process other signals. Unexpected results will probably follow this problem, since SCM or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The session connector manager could not lock the secondary session connector's data (process).
The session connector manager could not lock the logical process (or data) responsible for servicing the secondary side of a session connector. The EGPE function LP_cb_lock failed. The possible causes of this problem are:
Function Degradation: The session connector manager process abends. The pSNA node will probably also terminate, disabling APPC/APPN communication services. If the pSNA node remains active, the node cannot set up any new intermediate sessions.
Customer Action: Try and determine the cause of the problem:
If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The session connector manager could not create an intermediate session. An unexpected BIND response sense code was detected while setting up the session connectors.
The session connector manager encountered an error while trying to create an intermediate session. The encountered error was not expected (the BIND negotiation failed with a sense code, but in most cases this is handled by other sections of code). The possible causes of this problem are:
Function Degradation: The intermediate session is rejected. The session connector manager sends UNBIND type=cleanups to the session end-points.
Customer Action: Try and determine the cause of the problem:
If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The session connector manager could not determine the intermediate session related to a received UNBIND request.
The session connector manager could not determine the destination intermediate session for a received UNBIND request. The received UNBIND is a FID5 request, and the fully-qualified PCID contained in the request is used to determine the targeted intermediate session. The PCID contained in the received UNBIND does not match the PCID of any intermediate session. The probable causes are:
Function Degradation: The received UNBIND request is ignored (a positive response is sent to the UNBIND request). Unexpected results may follow this problem, since the UNBIND is ignored. In addition, the communications support in the sending node and the local node are either in error or are incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session connector manager could not lock the primary session connector's data (process).
The session connector manager could not lock the logical process (or data) responsible for servicing the primary side of a session connector. The EGPE function LP_cb_lock failed. The possible causes of this problem are:
Function Degradation: The session connector manager ignores the session setup response (it assumes that the session connector was unexpectedly terminated). It continues to process other signals and messages. Unexpected results may follow this problem, since SCM is probably in error and out of sequence.
Customer Action: Try and determine the cause of the problem:
If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The session connector manager could not determine the intermediate session related to a received UNBIND request.
The session connector manager could not determine the destination intermediate session for a received UNBIND request. The received UNBIND is a FID5 request, and pSNA uses fully-qualified PCIDs to correlate UNBIND requests with their targeted intermediate session. The received UNBIND request does not contain a fully-qualified PCID (control vector X'60'). The probable causes are:
Function Degradation: The received UNBIND request is ignored (a positive response is sent to the UNBIND request). Unexpected results may follow this problem, since the UNBIND is ignored. In addition, the communications support in the sending node and the local node are either in error or are incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: The session connector manager could not send SNMP accounting data to the accounting services component.
The session connector manager could not send the internal IPS containing the SCM accounting information to accounting services. The possible causes of this problem are:
Function Degradation: Processing continues, but the accounting message is lost. Unexpected results, such as invalid accounting data, will probably follow this problem, since the accounting services component is out of sequence with the SCM.
Customer Action: It is possible that the node will continue to work correctly if this problem occurs. If it appears to be behaving satisfactorily, no immediate action is required. To resolve the problem:
Try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The request to verify that accounting services is available failed.
The session connector manager could not verify that APPN accounting services is active and available. The EGPE function PEstart_ready_monitor failed. The possible causes of this problem are:
Function Degradation: The session connector manager continues processing, but does not forward any accounting data to ACS.
Customer Action: It is possible that the node will continue to work correctly if this problem occurs. If it appears to be behaving satisfactorily, no immediate action is required. To resolve the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The session connection manager (SCM) received an unexpected internal inter-process signal.
The session connector manager received an unexpected IPS while waiting for the response message to a PEstart_ready_monitor request. This condition may occur under normal conditions, but not repeatedly. The SCM is expecting a response (PE_MONITOR_RSP), and will ignore all messages until it is received.
Function Degradation: The unexpected IPS is re-queued for later processing. The session connection manager continues processing, waiting for the PE_MONITOR_RSP message before processing any other requests.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: The request to set up a notification when an instance of session connector manager deactivates failed.
The session connector manager could not add a notification to inform it when another instance of session connector manager deactivates. The EGPE function PEstart_down_monitor failed. The possible causes of this problem are:
Function Degradation: The session connector manager process abends. The pSNA node will probably also terminate, disabling APPC/APPN communication services. If the pSNA node remains active, the node cannot set up any new intermediate sessions.
Customer Action: Try and determine the cause of the problem:
If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Description: The session connector manager could not correlate a received ACTPU/ACTLU response to its associated session.
The session connector manager could not determine the destination session for a received ACTPU/ACTLU request. The LFSID in the received request and the associated path control instance's process ID are used to determine the targeted session. The LFSID contained in the received request does not match the LFSID of any session associated with the path control instance. The probable causes are:
Function Degradation: The received request is rejected. Unexpected results may follow this problem, since the request is ignored. In addition, the communications support in the sending node and the local node are either in error or are incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: The session connector manager could not correlate a received ACTPU/ACTLU response to its associated session.
The session connector manager could not determine the destination session for a received ACTPU/ACTLU request. The LFSID in the received request and the associated path control instance's process ID are used to determine the targeted session. The LFSID contained in the received request matches the LFSID of a session, but there is no associated LU hierarchy control block for that session (the session is not a SSCP session). The probable causes are:
Function Degradation: The received request is rejected. Unexpected results may follow this problem, since the request is ignored. In addition, the communications support in the sending node and the local node are either in error or are incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The request to resume monitoring the status of the SNA buffer manager storage status failed.
The session connector manager could not resume monitoring the status of the SNA buffer manager buffer pool status. The session connection manager monitors the status and is notified when the storage status is constrained or worse. The buffer manager function Bstatus_monitor failed. The possible causes of this problem are:
Function Degradation: The session connector manager process abends. The pSNA node will probably also terminate, disabling APPC/APPN communication services. If the pSNA node remains active, the node cannot set up any new intermediate sessions.
Customer Action: Try and determine the cause of the problem:
If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The request to start a timer used when monitoring the status of the SNA buffer manager storage status failed.
The session connector manager could not resume monitoring the status of the SNA buffer manager buffer pool status because it could not start the timer used to delay the checking of the status. The session connection manager monitors the status and is notified when the storage status is constrained or worse. When it is constrained, SCM continues to periodically check the status of the buffer pool. The EGPE function PEstart_timer failed. The possible causes of this problem are:
Function Degradation: The session connector manager process abends. The pSNA node will probably also terminate, disabling APPC/APPN communication services. If the pSNA node remains active, the node cannot set up any new intermediate sessions.
Customer Action: Try and determine the cause of the problem:
If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The session connector manager (SCM) received an invalid or out-of-sequence IPS or SNA message.
The session connector manager (SCM) received an invalid IPS or SNA message, or received a valid but unexpected IPS or SNA message. The probable causes are:
Function Degradation: The session connector manager process abends. The pSNA node will probably also terminate, disabling APPC/APPN communication services. If the pSNA node remains active, the node cannot set up any new intermediate sessions.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: The session connector manager (SCM) received an invalid IPS signal.
The session connector manager (SCM) received an invalid IPS or SNA message. The received IPS or SNA message is not recognized by the SCM FSM. This condition should not occur. A software problem exists in pSNA. The SCM FSM should be able to recognize all input signals routed to it by the other node components.
Function Degradation: The session connector manager process abends. The pSNA node will probably also terminate, disabling APPC/APPN communication services. If the pSNA node remains active, the node cannot set up any new intermediate sessions.
Customer Action: Call service with the code point, error description, and abend code value if possible. In addition:
System Developer Action: Debug and determine if the received input value was invalid or was unexpected.
Description: The session connector manager received an invalid BIND response.
The session connector manager received a BIND response for a session that was not expecting to receive a BIND response. The probable causes are:
Function Degradation: The received BIND response is ignored. Unexpected results may follow this problem, since the BIND response is ignored. In addition, the communications support in the sending node and the local node are either in error or are incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine if the received input value was invalid or was unexpected.
Description: The session connector manager detected a session correlation error in a received BIND response.
The session connector manager detected a session correlation problem in a received BIND response. The session connector manager used the LFSID in the received response to locate the correct intermediate session, but the session's fully-qualified PCID does not match the fully-qualified PCID in the received BIND response. The probable causes are:
Function Degradation: The received BIND response is ignored. Unexpected results may follow this problem, since the BIND response is ignored. In addition, the communications support in the sending node and the local node are either in error or are incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session connector manager could not lock the primary session connector's data (process).
The session connector manager could not lock the logical process (or data) responsible for servicing the primary side of a session connector. The EGPE function LP_cb_lock failed. The possible causes of this problem are:
Function Degradation: The session connector manager process abends. The pSNA node will probably also terminate, disabling APPC/APPN communication services. If the pSNA node remains active, the node cannot set up any new intermediate sessions.
Customer Action: Try and determine the cause of the problem:
If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The session connector manager could not determine the intermediate session related to a received BIND response.
The session connector manager could not determine the destination intermediate session for a received BIND response. The received BIND is a FID2 response, and the LFSID contained in the response is used to determine the targeted intermediate session. The LFSID contained in the received response does not match the LFSID of any intermediate session. The probable causes are:
Function Degradation: The received BIND response is ignored. Unexpected results may follow this problem, since the BIND response is ignored. In addition, the communications support in the sending node and the local node are either in error or are incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session connector manager could not determine the intermediate session related to a received UNBIND request, or has received an unexpected LFSID Freed during BIND negotiation.
The session connector manager could not determine the destination intermediate session for a received UNBIND request. The received UNBIND is a FID2 request, and the LFSID contained in the request is used to determine the targeted intermediate session. The LFSID contained in the received UNBIND does not match the LFSID of any intermediate session.
Or path control (PC) has unexpectantly sent session connection manager (SCM) a signal that the LFSID has been freed while BIND negotation is still underway.
The probable causes are:
This condition should not occur. A software problem exists in the node that sent the message, or the APPC/APPN support in the remote node is not compatible (which should never happen) with the pSNA APPC/APPN support.
Function Degradation: The received UNBIND request is ignored (a positive response is sent to the UNBIND request). Unexpected results may follow this problem, since the UNBIND is ignored. In the case of an unexpected LFSID Freed, the session is brought down. In addition, the communications support in the sending node and the local node are either in error or are incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session connector manager detected a session correlation error in a received UNBIND request.
The session connector manager detected a session correlation problem in a received UNBIND request. The session connector manager used the LFSID in the received UNBIND to locate the correct intermediate session, but the session's fully-qualified PCID does not match the fully-qualified PCID in the received UNBIND request. The probable causes are:
Function Degradation: The received UNBIND request is ignored (a positive response is sent to the UNBIND request). Unexpected results may follow this problem, since the UNBIND is ignored. In addition, the communications support in the sending node and the local node are either in error or are incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session connector manager detected a format or protocol error in a received UNBIND request.
The session connector manager detected a format or protocol error in a received UNBIND request. The received request contained incorrect values. The probable causes are:
Function Degradation: The received UNBIND request is ignored. Unexpected results may follow this problem, since the UNBIND is ignored. In addition, the communications support in the sending node and the local node are either in error or are incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session connector manager could not determine the intermediate session related to a received UNBIND response.
The session connector manager could not determine the destination intermediate session for a received UNBIND response. The received UNBIND is a FID2 response, and the LFSID contained in the response is used to determine the targeted intermediate session. The LFSID contained in the received response does not match the LFSID of any intermediate session. The probable causes are:
Function Degradation: The received UNBIND response is ignored. Unexpected results may follow this problem, since the UNBIND response is ignored. In addition, the communications support in the sending node and the local node are either in error or are incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session connector manager could not determine the intermediate session related to a received DLUR_UNBIND request from dependent LU requestor.
The session connector manager could not determine the destination intermediate session for a received DLUR_UNBIND request. A DLUR_UNBIND is an UNBIND request created by DLUR to end one of the DLUR sessions, which use session connectors to transfer the data. The received DLUR_UNBIND is a FID2 request, and the LFSID contained in the request is used to determine the targeted intermediate session. The LFSID contained in the received request does not match the LFSID of any intermediate session. The probable causes are:
Function Degradation: The received DLUR_UNBIND request is ignored. Unexpected results will probably follow this problem, since SCM and DLUR are probably in error and out of sequence. In addition, the communications support in the remote nodes and the local node are either in error or are incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session connector manager detected a session correlation error in a received UNBIND request.
The session connector manager detected a session correlation problem in a received UNBIND request. The session connector manager used the LFSID in the received UNBIND to locate the correct intermediate session, but the session's path control instance does not match the path control instance identified in the received UNBIND request. The instance identified in the UNBIND request is the path control instance that received the UNBIND request. The probable causes are:
Function Degradation: The received UNBIND request is ignored (a positive response is sent to the UNBIND request). Unexpected results may follow this problem, since the UNBIND is ignored. In addition, the communications support in the sending node and the local node are either in error or are incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: A session connector manager in an attached co-processor ended. The session connector manager assumes that the attached co-processor is no longer usable, and all links (as well as their related sessions) are lost. Possible causes of this problem are:
Function Degradation: All intermediate sessions that were routed through the affected co-processor are terminated (UNBINDs are sent to the session end-points). The local node attempts to recover the lost co-processor and restart any ports on the attached co-processor. If successfully recovered, the associated links and sessions are re-activated on request.
Customer Action: If the co-processor is successfully recovered and all associated ports are restarted, the only required action is to restart any lost sessions. If the co-processor is not successfully recovered or the error occurs often, try and determine the cause of the problem:
Try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The request to register the session connector manager with RTP failed. The session connector manager could not sign-in to RTP.
The possible causes of this problem are:
Function Degradation: The session connector manager process abends. The pSNA node aborts its initialization and stops. No APPC/APPN communication services are available.
Customer Action: Try and determine the cause of the problem:
If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The APPN session connection manager (SCM) received an unexpected internal inter-process signal.
The IPS was received before SCM was ready to process the received message. This condition should not occur, since the unrecognized signal should not have been routed to SCM for processing. An internal code problem exists within pSNA. The SCM received the unexpected IPS while waiting for a response to its monitor request (PEstart_ready_monitor) for session services (SS).
Function Degradation: The unexpected IPS is ignored, and SCM continues to process other signals. Unexpected results will probably follow this problem, since SCM or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The APPN session connection manager (SCM) received a DLUR_INIT_RSP for which it could not find a corresponding session_info_p. AVLfind_key() returns session_info_p=NULL
The DLUR_INIT_RSP was received after SCM had cleaned up all session information because of an UNBIND. In this case SCM should not process the IPS as if it were a normal response The SCM received the IPS after it cleaned up the session information for an earlier UNBIND.
Function Degradation: The stray IPS is ignored, and SCM continues to process other signals.
Customer Action: Call service with the code point and error description. In addition:
Additional Data: Has the following format:
Description: Session Information Pointer is deleted during session activation Before getting response from the CS.
The SCM received the IPS after it cleaned up the session information while waiting for forward route from SS.
Function Degradation: Current session activation is terminated.
Customer Action: Call service with the code point and error description. In addition:
Additional Data: Has the following format:
Description: Non-normal UNBIND received.
The session is being deactivated.
Function Degradation: The session will be terminated.
Customer Action: An UNBIND that is not type 01-UNBIND_TYPE_NORMAL or 02-BIND_FORTHCOMING has been received. The reason for deactivation is determined by the UNBIND type and UNBIND sense if present. In addition:
Additional Data: Has the following format:
Description: Bind -rsp received.
The session activation attempt is being failed with a negative Bind response.
Function Degradation: The session will be terminated.
Customer Action: The reason why the session activation attempt failed is determined from the sense code. In addition:
Additional Data: Has the following format:
Description: This node is creating an UNBIND.
The session is being terminated.
Function Degradation: The session will be terminated.
Customer Action: The UNBIND is being created as a result of a problem being detected by this node or is being generated as the result of a received BIND negative response. The sense code will contain the reason why this session is being terminated. In addition:
Additional Data: Has the following format:
Description: The secondary Size in the incoming Bind is greater than the definition in NOF for this node. Since this is a non-neg BIND, It would be rejected.
The adjacent Node sends the secondary size window greater than that defined in the NOF. The bind would be rejected. This is a violation of the protocol error.
Function Degradation: Incoming BIND is rejected..
Customer Action: Maintain the SCR logged.Provide the adjacent CP names. if in the future any problem occurs at the node. In addition:
Additional Data: Has the following format:
Description: The primary ru size defined for lu 6.2 and extended bind is greater than 128. The Bind is Rejected.
The Max RU size sent on the normal flow by the primary half session for a lu6.2 and extended bind is greater than 128. The BIND is rejected.
Function Degradation: Incoming BIND is rejected..
Customer Action: Maintain the SCR logged.Provide the adjacent CP names. if in the future any problem occurs at the node. In addition:
Additional Data: Has the following format:
Description: The secondary ru size defined for lu 6.2 and extended bind is greater than 128. The Bind is Rejected.
The Max RU size sent on the normal flow by the secondary half session for a lu6.2 and extended bind is greater than 128. The BIND is rejected.
Function Degradation: Incoming BIND is rejected..
Customer Action: Maintain the SCR logged.Provide the adjacent CP names. if in the future any problem occurs at the node. In addition:
Additional Data: Has the following format:
Description: SLU sends the maximum RU size which is not supported in the primary stage of the session path.
When the node receives the BIND rsp It checks again to see the maximum RU size is modified anywhere or by SLU and whether it is less than the primary RU size that could be forwarded through the primary session stage.
Function Degradation: Session is rejected.
Customer Action: Maintain the SCR logged.Provide the adjacent CP names. Please have the node definition re-checked. If the problem still persists Place a call to Service. In addition:
Additional Data: Has the following format:
Description: SLU sends the maximum RU size which is not supported in the primary stage of the session path.
When the node receives the BIND rsp It checks again to see the maximum RU size is modified anywhere or by SLU and whether it is less than the primary RU size that could be forwarded through the primary session stage.
Function Degradation: Session is rejected.
Customer Action: Maintain the SCR logged.Provide the adjacent CP names. Please have the node definition re-checked. If the problem still persists Place a call to Service. In addition:
Additional Data: Has the following format:
Description: SLU sends the maximum RU size which is not supported in the primary stage of the session path.
When the node receives the BIND rsp It checks again to see the maximum RU size is modified anywhere or by SLU and whether it is less than the primary RU size that could be forwarded through the primary session stage.
Function Degradation: Session is rejected.
Customer Action: Maintain the SCR logged.Provide the adjacent CP names. Please have the node definition re-checked. If the problem still persists Place a call to Service. In addition:
Additional Data: Has the following format:
Description: SLU sends the maximum RU size which is not supported in the primary stage of the session path.
When the node receives the BIND rsp It checks again to see the maximum RU size is modified anywhere or by SLU and whether it is less than the primary RU size that could be forwarded through the primary session stage.
Function Degradation: Session is rejected.
Customer Action: Maintain the SCR logged.Provide the adjacent CP names. Please have the node definition re-checked. If the problem still persists Place a call to Service. In addition:
Additional Data: Has the following format:
Description: SLU sends the maximum RU size which is not supported in the primary stage of the session path.
When the node receives the BIND rsp It checks again to see the maximum RU size is modified anywhere or by SLU and whether it is less than the primary RU size that could be forwarded through the primary session stage.
Function Degradation: Session is rejected.
Customer Action: Maintain the SCR logged.Provide the adjacent CP names. Please have the node definition re-checked. If the problem still persists Place a call to Service. In addition:
Additional Data: Has the following format:
Description: While processing an ISR_CINIT signal, SCM determined that the secondary path control's RTP connection isr_session_count has already been incremented for this session. This session count should be incremented only once during session establishment, so this is a "should not occur" condition.
Function Degradation: Session establishment continues without incrementing the the secondary path control's RTP connection isr_session_count.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused this warning to occur. Isolate and implement a code fix if needed.
Log events for the session services component of APPN (SS).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Description: Not used yet.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: A DEACTIVATE_CP_CP_SESSION message has been received from either DS or TRS.
Function Degradation: CP-CP deactivation with adjacent node.
Customer Action: None.
System Developer Action: None.
Description: A CDINIT is not present in the LOCATE MESSAGE GDS_VARIABLE list received from DS for this distributed search request.
Function Degradation: Tolerable, but close to Intolerable. The Locate search will terminate, and sessions cannot be established with the resource being located.
Customer Action: Get code point and call services with a software defect in the appropriate node.
System Developer Action: Debug directory services code in the adjacent node if the node logging the error did not find a CDINIT in a LOCATE request or reply received from the adjacent node. Debug directory services code in the node logging the error to determine why this node does not recognize a CDINIT that has been sent in a LOCATE request or reply from an adjacent node. adjacent node.
Description: RSCV not present in the ISR_INIT signal when bind was sent from an NN. An RSCV is not present in the ISR_INIT and the adjacent node is unknown.
Function Degradation: None -- this code will never be executed because of the implementation of feature 7757 which allows a NN to send a bind without an RSCV present.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: Session services (SS) received an unexpected locate request.
Session services (SS) received an unexpected locate request from another node (via directory services). The request does not specify the local node as the network node server of the LU that sent the request (the origin LU). The probable causes are:
A software problem probably exists in the node that sent the message, or the APPC/APPN support in the remote node is not compatible (which should never happen) with the pSNA APPC/APPN support.
Function Degradation: The received request is ignored, and processing continues. Unexpected results will probably follow this problem, since the locate request is ignored. The node that sent the request will not receive a reply from the local node. In addition, the communications support in the nodes are either in error or are incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: SS main dequeued an unknown IPS message.
Function Degradation: Tolerable
Customer Action: Call service with the unknown IPS message header data.
System Developer Action: Debug and determine what was sent, from where, and why. Implement a code fix.
Additional Data: Has the following format:
Description: SS main dequeued an unknown IPS message.
Function Degradation: Tolerable
Customer Action: Call service with the unknown IPS message header data.
System Developer Action: Debug and determine what was sent, from where, and why. Implement a code fix.
Additional Data: Has the following format:
Description: Session services (SS) rejected a session initialization request. The sense code contained in the negative response provides more detailed information on why the request was rejected. The probable causes are:
Function Degradation: The session initiation request is rejected with the supplied sense code.
Customer Action: Use the descriptions of the logged sense code, as well as information contained in any related log entries, to determine the cause of the problem. More detailed information may be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a network configuration error, a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Session services (SS) received an invalid SNA message.
Session services (SS) encountered an invalid RSCV (control vector x'46') while attempting to activate a route for a session. The required sub-vector x'4680' was not found in the received RSCV. The probable causes are:
A software problem probably exists in the node that sent the message, or the APPC/APPN support in the remote node is not compatible (which should never happen) with the pSNA APPC/APPN support.
Function Degradation: The session initiation request that triggered the attempt to activate the route is rejected.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The local node detected a collision while generating PCIDs (SNA session identifiers).
Function Degradation: The local node recovers by generating a new seed value for calculating the random portion of the PCID. A new PCID is generated and processing continues.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: Session services (SS) could not process a session initialization request. The local CP name could not be inserted into the RSCV related to the request. The maximum length of an RSCV is 255 bytes, and the combination of the existing information in the RSCV plus the local CP name exceeds that length. The most probable cause is the network configuration is in error. For example, if a session route needs to be routed through too many network nodes, the combination of the names of all the network nodes in the route may cause the maximum length of the RSCV to be exceeded.
Function Degradation: The session initiation request is rejected with the sense code x'80140004'.
Customer Action: Investigate the logged RSCV to see why the maximum length was exceeded.
The problem was caused by incorrect network definitions (e.g. too many network nodes in the route). If a network definition error exists, fix the network configuration and re-establish connections between all affected nodes. The network may have to be segmented using border nodes, or additional links may have to be added between network nodes so that session routes do not use as many intermediate network nodes.
If the problem was not caused by a network configuration error, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Session services (SS) encountered an error while trying to activate CP-CP sessions with an adjacent node. The sense code provides more detailed information on why the sessions could not be activated. The probable causes are:
Function Degradation: The request to activate CP-CP sessions with an adjacent node is rejected with the indicated sense code.
Customer Action: Use the descriptions of the logged sense code, as well as information contained in any related log entries, to determine the cause of the problem. More detailed information may be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a network configuration error, a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Session services (SS) encountered an error while trying to activate CP-CP sessions with an adjacent node. The maximum number of retries for CP-CP session activation has been exceeded. The local node will not try and re-activate CP-CP sessions with the adjacent node. The probable causes are:
Function Degradation: The request to activate CP-CP sessions with an adjacent node is rejected. The local node will not try and activate CP-CP sessions with the adjacent node again.
Customer Action: Use the information contained in any related log entries (such as 2F109000-0000000E), to determine the cause of the problem. More detailed information may be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a network configuration error, a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The APPN session services component (SS) received an unexpected internal inter-process signal.
The IPS was received before SS was ready to process the received message. This condition should not occur, since the unrecognized signal should not have been routed to SS for processing. An internal code problem exists within pSNA. SS received the unexpected IPS while waiting for a response to its registration request with the HPR network connection layer.
Function Degradation: The unexpected IPS is ignored, and SS continues to process other signals. Unexpected results will probably follow this problem, since SS or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: APPN session services (SS) encountered a problem trying to start the request_cp_capabilities service transaction program. The request to start the service transaction program (Pcreate) failed. The probable causes are:
Function Degradation: The local node cannot establish CP-CP sessions with the adjacent node. The local node will not be able to exchange any APPN network control informatoin with the adjacent node, possibly creating network problems, such as unknown or unavailable resources. If SS cannot establish CP-CP sessions with any adjacent node, the SS process terminates, probably bringing down the rest of the node.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Description: An attempt to establish a DLUR-DLUS pipe with a domain EN served by Branch Network Node is made. This is illegal. A Branch Network Node cannot have domain ENs acting as DLURs.
Function Degradation: None
Customer Action: DLURs cannot exist in a domain served by a Branch Network Node. Correct the network configuration.
System Developer Action: None.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while doing NNS(OLU) processing for a PLU-initiated session.
The session services FSM PNO received an unexpected or unrecognized input value. This condition should not occur, since the FSM should be robust enough to handle any valid input, and only valid inputs should be passed to the FSM. This FSM controls the processing for the Network Node Server of the Primary LU in the PLU-initiated scenario. The probable causes are:
Function Degradation: SS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since SS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while doing NNS(OLU) processing for a PLU-initiated session.
The session services FSM PNO encountered a state and/or action error (should-not-occur situation). The FSM should be robust enough to handle any valid input in any valid sequence. This FSM controls the processing for the Network Node Server of the Primary LU in the PLU-initiated scenario. The probable causes are:
Function Degradation: SS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since SS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Session services (SS) received an invalid network search request from another node.
Session services received an invalid network search request. The remote node sending the CDINIT does not support TGV registration (APPN option set 1118) and it did not include its TGVs in its search request. This is an error condition. The sense code specifies the error encountered by session services. The probable causes are:
Function Degradation: Session Services rejects the search request, cleans up its control blocks and informs DS of the error condition. No chain is kept for this search.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Session services (SS) received either an invalid message from DS or a stray message from TRS of this node.
Session services received either an invalid message from DS or a stray message from TRS. DS or TRS sent a message to SS with a search correlator for which SS has not maintained a chain, or has discarded the chain. The probable causes are:
Function Degradation: Session Services does no further processing for this message. This is a should not occur situation if DS is the source of this signal, OR if TRS sent this signal and SS did not receive a CLEANUP message from DS between the time it sent a request IPS (REQUEST_COS_TPF, REQUEST_ROUTE, REQUEST_TG_VECTORS or COS_MAP_REQUEST) to TRS and the time SS received this response IPS.
Customer Action: If no unexpected results occur, this log message can be safely ignored. Otherwise try and determine if this is a should-not-occur situation as described above.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while doing NNS(DLU) processing for a PLU-initiated session.
The session services FSM PND received an unexpected or unrecognized input value. This condition should not occur, since the FSM should be robust enough to handle any valid input, and only valid inputs should be passed to the FSM. This FSM controls the processing for the Network Node Server of the Primary LU in the PLU-initiated scenario. The probable causes are:
Function Degradation: SS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since SS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while doing NNS(DLU) processing for a PLU-initiated session.
The session services FSM PND encountered a state and/or action error (should-not-occur situation). The FSM should be robust enough to handle any valid input in any valid sequence. This FSM controls the processing for the Network Node Server of the Primary LU in the PLU-initiated scenario. The probable causes are:
Function Degradation: SS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since SS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Session services (SS) received an invalid network search request from another node.
Session services received an invalid network search request. The remote node sending the CDINIT does not support TGV registration (APPN option set 1118) and it did not include its TGVs in its search reply. This is an error condition. The sense code specifies the error encountered by session services. The probable causes are:
Function Degradation: Session Services rejects the search request, cleans up its control blocks and informs DS of the error condition. No chain is kept for this search.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while doing entry Border Node preprocessing for a PLU-initiated session.
The session services FSM PYR received an unexpected or unrecognized input value. This condition should not occur, since the FSM should be robust enough to handle any valid input, and only valid inputs should be passed to the FSM. This FSM controls the preprocessing for the entry border Node in the PLU-initiated scenario. The probable causes are:
Function Degradation: SS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since SS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while doing entry border node preprocessing for a PLU-initiated session.
The session services FSM PYR encountered a state and/or action error (should-not-occur situation). The FSM should be robust enough to handle any valid input in any valid sequence. This FSM controls the entry border node preprocessing in the PLU-initiated scenario. The probable causes are:
Function Degradation: SS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since SS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while doing exit Border Node post-processing for a PLU-initiated session.
The session services FSM PXT received an unexpected or unrecognized input value. This condition should not occur, since the FSM should be robust enough to handle any valid input, and only valid inputs should be passed to the FSM. This FSM controls the post-processing for the exit Border Node in the PLU-initiated scenario. The probable causes are:
Function Degradation: SS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since SS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while doing exit Border Node post-processing for a PLU-initiated session.
The session services FSM PXT encountered a state and/or action error (should-not-occur situation). The FSM should be robust enough to handle any valid input in any valid sequence. This FSM controls the exit Border Node post-processing in the PLU-initiated scenario. The probable causes are:
Function Degradation: SS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since SS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while doing exit Border Node preprocessing for a PLU-initiated session.
The session services FSM PXR received an unexpected or unrecognized input value. This condition should not occur, since the FSM should be robust enough to handle any valid input, and only valid inputs should be passed to the FSM. This FSM controls the preprocessing for the exit border Node in the PLU-initiated scenario. The probable causes are:
Function Degradation: SS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since SS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while exit border node preprocessing for a PLU-initiated session.
The session services FSM PXR encountered a state and/or action error (should-not-occur situation). The FSM should be robust enough to handle any valid input in any valid sequence. This FSM controls the exit border node preprocessing in the PLU-initiated scenario. The probable causes are:
Function Degradation: SS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since SS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while doing entry Border Node post-processing for a PLU-initiated session.
The session services FSM PYT received an unexpected or unrecognized input value. This condition should not occur, since the FSM should be robust enough to handle any valid input, and only valid inputs should be passed to the FSM. This FSM controls the post-processing for the entry Border Node in the PLU-initiated scenario. The probable causes are:
Function Degradation: SS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since SS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while doing entry Border Node post-processing for a PLU-initiated session.
The session services FSM PXT encountered a state and/or action error (should-not-occur situation). The FSM should be robust enough to handle any valid input in any valid sequence. This FSM controls the entry Border Node post-processing in the PLU-initiated scenario. The probable causes are:
Function Degradation: SS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since SS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Session services (SS) received an invalid REQUEST_CDINIT IPS from DS of this node.
Session services received an invalid message from DS. REQUEST_CDINIT signal is used by DS to request SS to provide a new CDINIT GDS variable applicable to a particular non-native network. This signal is sent by DS when this node is acting as an Exit border node, before DS begins to search a particular non-native network. DS, must include the CDINIT GDS variable applicable to the native network, and in this case, it has failed to do so. The probable causes are:
Function Degradation: Session Services does no further processing for this invalid message. This is a should not occur situation.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA)
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while doing NNS(OLU) processing for a SLU-initiated session.
The session services FSM SNO received an unexpected or unrecognized input value. This condition should not occur, since the FSM should be robust enough to handle any valid input, and only valid inputs should be passed to the FSM. This FSM controls the processing for the Network Node Server of the Secondary LU in the SLU-initiated scenario. The probable causes are:
Function Degradation: SS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since SS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while doing NNS(OLU) processing for a SLU-initiated session.
The session services FSM SNO encountered a state and/or action error (should-not-occur situation). The FSM should be robust enough to handle any valid input in any valid sequence. This FSM controls the processing for the Network Node Server of the Secondary LU in the SLU-initiated scenario. The probable causes are:
Function Degradation: SS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since SS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while doing NNS(DLU) processing for a SLU-initiated session.
The session services FSM SND received an unexpected or unrecognized input value. This condition should not occur, since the FSM should be robust enough to handle any valid input, and only valid inputs should be passed to the FSM. This FSM controls the processing for the Network Node Server of the Primary LU in the SLU-initiated scenario. The probable causes are:
Function Degradation: SS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since SS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while doing NNS(DLU) processing for a SLU-initiated session.
The session services FSM SND encountered a state and/or action error (should-not-occur situation). The FSM should be robust enough to handle any valid input in any valid sequence. This FSM controls the processing for the Network Node Server of the Primary LU in the SLU-initiated scenario. The probable causes are:
Function Degradation: SS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since SS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Session services (SS) received an invalid network SLU-init search request from another node.
Session services received an invalid network search request. The NNS(SLU) is supposed to send the SLU tail vectors in the CDINIT to the NNS(PLU) as a part of its processing support for SLU-init searches. The NNS(PLU) uses these tail vectors to compute the the sesion route. The NNS(SLU) is in error as it did not include the SLU TG vectors. The sense code specifies the error encountered by session services. The probable causes are:
Function Degradation: Session Services rejects the search request, cleans up its control blocks and informs DS of the error condition. No chain is kept for this search.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while doing Entry Border Node preprocessing for a SLU-initiated session.
The session services FSM SYR received an unexpected or unrecognized input value. This condition should not occur, since the FSM should be robust enough to handle any valid input, and only valid inputs should be passed to the FSM. This FSM controls the Entry Border Node preprocessing for a SLU initiated session request. The probable causes are:
Function Degradation: SS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since SS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while doing Entry Border Node preprocessing for a SLU-initiated session.
The session services FSM SYR encountered a state and/or action error (should-not-occur situation). The FSM should be robust enough to handle any valid input in any valid sequence. This FSM controls the entry border node preprocessing for a SLU initiated session request. The probable causes are:
Function Degradation: SS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since SS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while doing Entry Border Node postprocessing for a SLU-initiated session.
The session services FSM SYT received an unexpected or unrecognized input value. This condition should not occur, since the FSM should be robust enough to handle any valid input, and only valid inputs should be passed to the FSM. This FSM controls the Entry Border Node postprocessing for a SLU initiated session request. The probable causes are:
Function Degradation: SS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since SS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while doing Entry Border Node postprocessing for a SLU-initiated session.
The session services FSM SYT encountered a state and/or action error (should-not-occur situation). The FSM should be robust enough to handle any valid input in any valid sequence. This FSM controls the entry border node postprocessing for a SLU initiated session request. The probable causes are:
Function Degradation: SS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since SS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while doing Exit Border Node preprocessing for a SLU-initiated session.
The session services FSM SXR received an unexpected or unrecognized input value. This condition should not occur, since the FSM should be robust enough to handle any valid input, and only valid inputs should be passed to the FSM. This FSM controls the Exit Border Node preprocessing for a SLU initiated session request. The probable causes are:
Function Degradation: SS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since SS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while doing Exit Border Node preprocessing for a SLU-initiated session.
The session services FSM SXR encountered a state and/or action error (should-not-occur situation). The FSM should be robust enough to handle any valid input in any valid sequence. This FSM controls the exit border node preprocessing for a SLU initiated session request. The probable causes are:
Function Degradation: SS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since SS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while doing Exit Border Node postprocessing for a SLU-initiated session.
The session services FSM SXT received an unexpected or unrecognized input value. This condition should not occur, since the FSM should be robust enough to handle any valid input, and only valid inputs should be passed to the FSM. This FSM controls the Exit Border Node postprocessing for a SLU initiated session request. The probable causes are:
Function Degradation: SS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since SS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while doing Exit Border Node postprocessing for a SLU-initiated session.
The session services FSM SXT encountered a state and/or action error (should-not-occur situation). The FSM should be robust enough to handle any valid input in any valid sequence. This FSM controls the exit border node postprocessing for a SLU initiated session request. The probable causes are:
Function Degradation: SS continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since SS is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while doing Border Node Bind processing. SCM, after analyzing the RSCV received on the BIND_RQ determined that this node is acting as the Exit EBN for this session request, and it indicated so in the ISR_INIT IPS that it sent to SS. But the locate chain maintained for this session request does not have any information pertaining to the non-native node in the direction of the SLU. This indicates an inconsistency in the locate search and the subsequent BIND flows.
The session services encountered a should-not-occur situation while doing BIND processing. The probable causes are:
Function Degradation: SS rejects the request by sending a ISR_INIT negative response to SCM, which will then reject the BIND.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Session services encountered a badly formed RSCV while doing Border Node Bind processing. The RSCV does not have as many hops as indicated by it's max_hop_counts field.
The session services encountered a badly formed control vector (RSCV). while doing BIND processing. The probable causes are:
Function Degradation: SS rejects the request by sending a ISR_INIT negative response to SCM, which will then reject the BIND.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received RSCV was invalid.
Additional Data: Has the following format:
Description: Session services (SS) could not process a search initialization request. The Extended Border Node could not append a CV'2B80' to the computed RSCV. The maximum length of an RSCV is 255 bytes, and the combination of the existing information in the RSCV plus the CV'2B80' control vector exceeds that length. The most probable cause is the network configuration is in error. For example, if a session route needs to be routed through too many network nodes, the combination of the names of all the network nodes in the route may cause the maximum length of the RSCV to be exceeded.
Function Degradation: The search request is rejected with the sense code x'80140004'.
Customer Action: Investigate the logged RSCV to see why the maximum length was exceeded.
The problem was caused by incorrect network definitions (e.g. too many network nodes in the route). If a network definition error exists, fix the network configuration and re-establish connections between all affected nodes. The network may have to be segmented using border nodes, or additional links may have to be added between network nodes so that session routes do not use as many intermediate network nodes.
If the problem was not caused by a network configuration error, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Session services (SS) could not process a session initialization request. The Extended Border Node could not append a CV'2B80' to the computed RSCV. The maximum length of an RSCV is 255 bytes, and the combination of the existing information in the RSCV plus the CV'2B80' control vector exceeds that length. The most probable cause is the network configuration is in error. For example, if a session route needs to be routed through too many network nodes, the combination of the names of all the network nodes in the route may cause the maximum length of the RSCV to be exceeded.
Function Degradation: The search request is rejected with the sense code x'80140004'.
Customer Action: Investigate the logged RSCV to see why the maximum length was exceeded.
The problem was caused by incorrect network definitions (e.g. too many network nodes in the route). If a network definition error exists, fix the network configuration and re-establish connections between all affected nodes. The network may have to be segmented using border nodes, or additional links may have to be added between network nodes so that session routes do not use as many intermediate network nodes.
If the problem was not caused by a network configuration error, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Session services (SS) could not satisfy a SLU-init correlation non-verify search.
Session services could not satisfy a non-verify request. The PLU of a SLU-initiated session sent this node, which is the NNS of the PLU, a one-hop non-verify correlation search. This search request comes in as a PLU init search with the "Verify not required" and the "Verify not permitted" indicators set. This search also has the same FQPCID as the parent SLU-init search, but a different PCID modifier. Session services could not satisfy this non-verify request with the information it has. This session request will be failed with the sense code X'08900021'. The probable causes are:
Function Degradation: Session Services rejects the search request, cleans up its control blocks and informs DS of the error condition. No chain is kept for this search.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Session services (SS) received an invalid locate message from DS.
Session services received an invalid locate message from DS in the reply phase. DS sent a locate message to SS with a search correlator for which SS has not maintained a chain, or has discarded the chain. The probable causes are:
Function Degradation: Session Services does no further processing for this message. This is a should not occur situation. DS being the source of this signal, is probably in error.
Customer Action: Try and determine the cause of the failure if this is a should-not-occur situation as described above.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix.
Additional Data: Has the following format:
Description: Session services encountered a software problem (should-not-occur condition) while doing Border Node Bind processing. SCM, after analyzing the RSCV received on the BIND_RQ determined that this node is acting as the Entry EBN for this session request, and it indicated so in the ISR_INIT IPS that it sent to SS. But the locate chain maintained for this session request does not have any information pertaining to the non-native node in the direction of the PLU. This indicates an inconsistency in the locate search and the subsequent BIND flows.
The session services encountered a should-not-occur situation while doing BIND processing. The probable causes are:
Function Degradation: SS rejects the request by sending a ISR_INIT negative response to SCM, which will then reject the BIND.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Session services encountered a COS/TPF mismatch while doing Border Node Bind processing. The PLU sent an unexpected COS/TPF on the BIND request. During locate search, the COS/TPF that was received from the PLU was different. This indicates an inconsistency in the locate search and the subsequent BIND flows.
The session services encountered a COS/TPF mismatch between locate and BIND flows. The probable causes are:
Function Degradation: SS sends an ALERT signal to MS. It also continues to process the received BIND request.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Session Services encountered a problem during locate processing. SS in a HPRBN expected to receive some information that was not present.
The session services encountered an error during locate processing. The probable causes are:
Function Degradation: An end-to-end HPR pipe will not be established for the session. In some cases, the session will not become active.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, determine if the received input value was invalid or was unexpected.
Additional Data: Has the following format:
Description: Session services (SS) has received a deactivate CP-CP session from an adjacent node. The local node will not try to re-activate CP-CP sessions with the adjacent node.
The problem was caused by a RTP (Rapid Transport Protocol) pipe undergoing a path switch and failing.
Function Degradation: CP-CP session deactivation with adjacent node. No retry is performed.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages). Check the remote node for errors.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: A CDINIT GDS variable with an invalid Control Vector length has been received from the sender of this search request.
Function Degradation: Tolerable, but close to Intolerable. The Locate search will terminate, and sessions cannot be established with the resource being located.
Customer Action: Get code point and call services with a software defect in the appropriate node.
System Developer Action: Debug Session Services code in the search origin or destination to find out why this control vector may have been included. Debug Session Services code in the node logging the error to determine why this node found an error in the Control vector length. node.
Additional Data: Has the following format:
Description: This node sent a route_setup to the adjacent node. No reply was received by this node. The route_setup processing will be timed out, and a negative route_setup response will be generated.
Function Degradation: Close to Intolerable. This problem may indicate a software error in any of the nodes in the route_setup path. Route_setup processing for the current session will terminate; and the session might fail to come up.
Customer Action:
System Developer Action: Use the route_setup information in the LogEvent to see if there is any problem in its construction. Also, the complete path of route_setup is displayed in the LogEvent at the origin. Contact service of all products on the path of the route_setup.
Log events for the topology and route selection services component of APPN (TRS).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: Topology and route selection services (TRS) received an internal inter-process signal it does not recognize (or process).
The TRS internal data routing routine received an IPS that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to TRS. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and TRS continues to process other signals. Unexpected results will probably follow this problem, since TRS or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Topology and route selection services (TRS) encountered a should-not-occur condition within the component. The routine that builds responses to request route requests was invoked with an invalid parameter. An internal code problem exists within pSNA.
Function Degradation: The TRS process terminates. The local node can no longer compute session routes through the APPN network and will also probably terminate. Attempts to create any new sessions will fail.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Topology and route selection services (TRS) encountered an error while processing a request to compute a single hop route (one intermediate node). Possible errors are:
Function Degradation: The route request is rejected with the indicated sense code. TRS continues to process other requests. Unexpected results will probably follow this problem, since TRS or session services (SS) is probably in error and out of sequence.
Another log record may be created in conjunction with this log record (2F10A000-00000019). The additional log record provides additional information about what requests TRS has processed.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Topology and route selection services (TRS) encountered an error while computing a route. A COS entry in the topology database contained an invalid weight definition string for a node row. The probable causes are:
Function Degradation: The TRS process terminates. The local node can no longer compute session routes through the APPN network and will also probably terminate. Attempts to create any new sessions will fail.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Topology and route selection services (TRS) received an invalid internal inter-process signal.
TRS detected an error while processing a request to add or update a class-of-service definition. The COS_UPDATE internal signal contained an invalid request code. An internal code problem exists within pSNA.
Function Degradation: The TRS process terminates. The local node can no longer compute session routes through the APPN network and will also probably terminate. Attempts to create any new sessions will fail.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Topology and route selection services (TRS) encountered an error while computing a route. A COS entry in the topology database contained an invalid weight definition string for a TG row. The probable causes are:
Function Degradation: The TRS process terminates. The local node can no longer compute session routes through the APPN network and will also probably terminate. Attempts to create any new sessions will fail.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Topology and route selection services (TRS) encountered an error while processing a request to compute a route. Some possible causes are:
Function Degradation: The route request is rejected with the indicated sense code. TRS continues to process other requests. Unexpected results will probably follow this problem, since TRS or session services (SS) is probably in error and out of sequence.
Other log records may be created in conjunction with this log record
Customer Action: Use the sense code to determine why the route could not be computed. If the maximum size of the RSCV was exceeded, the network configuration is probably invalid. If a network definition error exists, fix the network configuration and re-establish connections between all affected nodes. The network may have to be segmented using border nodes, or additional links may have to be added between network nodes so that session routes do not use as many intermediate network nodes.
If the problem was not caused by a network configuration error, the problem was probably caused by a software problem within the local node. Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with TRS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Topology and route selection services received an invalid topology update from a partner node. The specific error is indicated by the logged sense code:
Function Degradation: An alert is generated with the indicated sense code and sent to the alert focal point. The CP-CP sessions with the node that sent the topology update are deactivated.
Other log records may be created in conjunction with this log record when invalid FRSN values are detected:
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: A system (EGPE or OS) function failed while trying to initialize the topology database manager component of topology and route selection services. The probable causes are:
Function Degradation: The TRS process terminates. The local node can not compute session routes through the APPN network and will also probably terminate. Attempts to create any sessions will fail.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
If the problem was not caused by a system failure or resource shortage, the problem was probably caused by a problem in the communications support in the local node. Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: Topology and route selection services encountered an error while trying to initialize the component or an data structure. The probable causes are:
Function Degradation: Depending on the severity of the error, the TRS process either terminates or attempts to recover from the error. The log record 2F10A000-0000000C will be created if TRS attempts to recover from the error. If it does try and recover, unexpected results will probably follow this problem, since TRS is probably in error and possibly out of sequence with the other node components.
If the TRS process terminates, the local node will not be able to compute any new session routes through the APPN network and will also probably terminate. Attempts to create any new sessions will fail.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
If the problem was not caused by a system failure or resource shortage, the problem was probably caused by a problem in the communications support in the local node. Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: Topology and route selection services encountered an error while trying to send an internal message (IPS) to another node component. The probable causes are:
Function Degradation: Depending on the severity of the error, the TRS process either terminates or attempts to recover from the error. The log record 2F10A000-0000000C will be created if TRS attempts to recover from the error. If it does try and recover, unexpected results will probably follow this problem, since TRS is probably in error and possibly out of sequence with the other node components.
If the TRS process terminates, the local node will not be able to compute any new session routes through the APPN network and will also probably terminate. Attempts to create any new sessions will fail.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
If the problem was not caused by a system failure or resource shortage, the problem was probably caused by a problem in the communications support in the local node. Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Description: Topology and route selection services encountered a processing error, but is trying to recover and continue processing. Another log record will be created in conjunction with this log record (2F10A000-0000000A or 2F10A000-0000000B). The additional log record provides additional information about the error.
Function Degradation: See the description of the related log records. TRS will attempt to recover from the error. If it cannot, unexpected results will probably follow this problem, since TRS is probably in error and possibly out of sequence with the other node components.
Customer Action: Refer to related log entries and messages for more information and other recommended actions. If TRS does successfully recover, no immediate action is required.
System Developer Action: See the description of the related log records.
Additional Data: Has the following format:
Description: Topology and route selection services received a topology update containing inconsistent topology information. A TG update in the received TDU is inconsistent with the current information stored by the topology database manager. The sequence number in the TG update matches the sequence number stored for the TG in the database, so the update should match the current information stored in the database. The information in the database does not match that in the received TDU.
The probable causes are:
Function Degradation: The received update is assumed to be valid. TRS continues to process the TG update, as well as any other updates in the received TDU. The TG update in the received TDU is marked inconsistent (the sequence number is made odd), and the TDU is forwarded through the network, as well as sent back to the node that sent the update. The assumption is the node owning the resource will forward another update with an updated sequence number, which will contain valid information about the TG. Unexpected results may follow this problem, since the information about the TG in topology database in the local node may be incorrect. The information should be corrected as soon as the node owning the resource sends another update.
Customer Action: In most cases, the nodes in the network will correct the error and no action is required. In some cases, the network may not be able to recover.
If you suspect that the network did not successfully recover, try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Topology and route selection services received a topology update containing inconsistent topology information. A node update in the received TDU is inconsistent with the current information stored by the topology database manager. The sequence number in the node update matches the sequence number stored for the node in the database, so the update should match the current information stored in the database. The information in the database does not match that in the received TDU.
The probable causes are:
Function Degradation: The received update is assumed to be valid. TRS continues to process the node update, as well as any other updates in the received TDU. The node update in the received TDU is marked inconsistent (the sequence number is made odd), and the TDU is forwarded through the network, as well as sent back to the node that sent the update. The assumption is the node owning the resource will forward another update with an updated sequence number, which will contain valid information about the node. Unexpected results may follow this problem, since the information about the node in topology database in the local node may be incorrect. The information should be corrected as soon as the node owning the resource sends another update.
Customer Action: In most cases, the nodes in the network will correct the error and no action is required. In some cases, the network may not be able to recover.
If you suspect that the network did not successfully recover, try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Topology and route selection services (TRS) received an internal inter-process signal it does not recognize (or process).
TRS internal data reporting routine received an IPS that it does not recognize or process while processing a TG update. This condition should not occur, since the unrecognized signal should not have been routed to TRS. An internal code problem exists within pSNA.
Function Degradation: The TRS process terminates. The local node can no longer compute session routes through the APPN network and will also probably terminate. Attempts to create any new sessions will fail.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Topology and route selection services (TRS) received an invalid internal inter-process signal.
TRS detected an error while processing a request to update the status of a local TG. The TG_UPDATE internal signal contained an invalid partner node type value or was for an inbound TG. TRS only processes TG updates for outbound TGs (it expects the remote node owning the TG to send TDUs whenever the status of an inbound TG changes). An internal code problem exists within pSNA.
Function Degradation: The TRS process terminates. The local node can no longer compute session routes through the APPN network and will also probably terminate. Attempts to create any new sessions will fail.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Topology and route selection services an invalid topology update from a partner node. The FRSN (flow reduction sequence numbers) in the received TDU are invalid. The last sent number is greater than the current number. The probable causes are:
Function Degradation: An alert is generated with the sense code 08A00004 or 08A00005 and sent to the alert focal point. The CP-CP sessions with the node that sent the topology update are deactivated.
Another log record (2F10A000-00000008) may be created in conjunction with this log record. The additional log record provides additional information about the detected error and the generated alert.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Topology and route selection services an invalid topology update from a partner node. The received TDU is out of sequence. The last FRSN sent value in the TDU is less than the last FRSN sent value in a previously received TDU. The probable causes are:
Function Degradation: An alert is generated with the sense code 08A00004 or 08A00005 and sent to the alert focal point. The CP-CP sessions with the node that sent the topology update are deactivated.
Another log record (2F10A000-00000008) may be created in conjunction with this log record. The additional log record provides additional information about the detected error and the generated alert.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Topology and route selection services (TRS) received an invalid internal inter-process signal.
TRS detected an error while processing a request to add or update a class-of-service definition. The COS_UPDATE internal signal contained an invalid request code. An internal code problem exists within pSNA.
Function Degradation: The TRS process terminates. The local node can no longer compute session routes through the APPN network and will also probably terminate. Attempts to create any new sessions will fail.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Topology and route selection services (TRS) encountered an error while processing a request to determine the class-of-service definition associated with a mode. The request specified an invalid mode name (the requested mode name is unknown). The mode should have been verified before the request was sent. The probable causes are:
Function Degradation: The request is rejected with the indicated sense code. The related session creation request fails. TRS continues to process other requests. Unexpected results may follow this problem, since TRS or session services (SS) is probably in error and out of sequence.
Other log records may be created in conjunction with this log record
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Topology and route selection services deactivated the CP-CP sessions with an adjacent node. TRS either received an invalid message (such as a TDU) from the adjacent node or determined that the adjacent node is inoperative. The specific error is indicated by the logged sense code. Some possible sense codes are:
The probable causes are:
Function Degradation: In some cases, an alert is generated with the indicated sense code and sent to the alert focal point (log record 2F10A000-00000008 is generated if an alert is sent). The CP-CP sessions with the adjacent node are deactivated.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Topology and route selection services deactivated the con-loser CP-CP session with an adjacent node. TRS either received an invalid message (such as a TDU) from the adjacent node or determined that the adjacent node is inoperative. The specific error is indicated by the logged sense code. Some possible sense codes are:
The probable causes are:
Function Degradation: In some cases, an alert is generated with the indicated sense code and sent to the alert focal point (log record 2F10A000-00000008 is generated if an alert is sent). The con-loser CP-CP session with the adjacent node is deactivated.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Topology and route selection services deactivated the con-winner CP-CP session with an adjacent node. TRS either received an invalid message (such as a TDU) from the adjacent node or determined that the adjacent node is inoperative. The specific error is indicated by the logged sense code. Some possible sense codes are:
The probable causes are:
Function Degradation: In some cases, an alert is generated with the indicated sense code and sent to the alert focal point (log record 2F10A000-00000008 is generated if an alert is sent). The con-winner CP-CP session with the adjacent node is deactivated.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Topology and route selection services encountered a processing error. Other log records are created in conjunction with this log record. These additional log records provides additional information about the error.
This log record is used to dump the contents of the TRS class-of-service database to aid in problem determination.
Function Degradation: See the description of the related log records.
Customer Action: Refer to related log entries and messages for other information and other recommended actions.
System Developer Action: See the description of the related log records.
Additional Data: Has the following format:
Description: Topology and route selection services encountered a processing error. Other log records are created in conjunction with this log record. These additional log records provides additional information about the error.
This log record is used to dump statistics concerning what messages and actions TRS has processed to aid in problem determination.
Function Degradation: See the description of the related log records.
Customer Action: Refer to related log entries and messages for other information and other recommended actions.
System Developer Action: See the description of the related log records.
Additional Data: Has the following format:
Description: Topology and route selection services encountered a processing error while processing a request to compute a route through the APPN network. Other log records are created in conjunction with this log record. These additional log records provides additional information about the error.
This log record, along with the log records 2F10A000-0000001B and 2F10A000-0000001C, are used to log the internal route request that failed.
Function Degradation: See the description of the related log records.
Customer Action: Refer to related log entries and messages for other information and other recommended actions.
System Developer Action: See the description of the related log records.
Additional Data: Has the following format:
Description: Topology and route selection services encountered a processing error while processing a request to compute a route through the APPN network. Other log records are created in conjunction with this log record. These additional log records provides additional information about the error.
This log record, along with the log records 2F10A000-0000001A and 2F10A000-0000001C, are used to log the internal route request that failed. Specifically, this log record is used to dump the origin TG vectors contained in the route request.
Function Degradation: See the description of the related log records.
Customer Action: Refer to related log entries and messages for other information and other recommended actions.
System Developer Action: See the description of the related log records.
Additional Data: Has the following format:
Description: Topology and route selection services encountered a processing error while processing a request to compute a route through the APPN network. Other log records are created in conjunction with this log record. These additional log records provides additional information about the error.
This log record, along with the log records 2F10A000-0000001A and 2F10A000-0000001B, are used to log the internal route request that failed. Specifically, this log record is used to dump the destination TG vectors contained in the route request.
Function Degradation: See the description of the related log records.
Customer Action: Refer to related log entries and messages for other information and other recommended actions.
System Developer Action: See the description of the related log records.
Additional Data: Has the following format:
Description: Topology and route selection services was unable to perform the requested mapping from a non-native COS value to a COS which is defined in the native subnetwork. Possible errors are:
Function Degradation: The EBN will fail the session initiation with sense code "No Intersubnetwork Route For Specified COS" (X'80150004'). This will result in either the BIND or the locate search being railed.
Customer Action: If a network definition error exists, fix the network configuration
If the problem was not caused by a network configuration error, the problem was probably caused by a software problem within the local node. Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with TRS traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Topology and route selection services (TRS) encountered a processing error while reading from or writing to the topology safestore file.
Function Degradation: This is not a critical failure. If TRS encounters such an error during a read operation, it behaves as if the topology safestore file never existed. If it encounters such an error during a write operation, the corrupted topology safestore file will not contain critical authentication records and, therefore, will not be used in subsequent attempts to read safestore information.
Customer Action: The operator may observe a slight performance degradation during node initialization while the node "learns" the network topology from its adjacent nodes via Topology Database Update (TDU) exchanges.
If this problem is persistent, call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Topology and route selection services (TRS) could not open the topology database.
Function Degradation: TRS assumes there is no pre-existing topology data to load and continues to initialize. This is a normal condition when the node is first started on a system, or when the node did not previously safe-store the topology database.
Customer Action: The operator may observe a slight performance degradation during node initialization while the node "learns" the network topology from its adjacent nodes via Topology Database Update (TDU) exchanges. If TRS does successfully recover, no immediate action is required.
If this problem is persistent, call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: Topology and route selection services received an invalid topology update from a partner node. See related log record 2F10A000-00000008 for information. The specific error is indicated by the logged sense code:
Function Degradation: An alert is generated with the indicated sense code and sent to the alert focal point. The CP-CP sessions with the node that sent the topology update are deactivated. See related log record 2F10A000-00000008 for information.
System Developer Action: See related log record 2F10A000-00000008 for information.
Additional Data: Has the following format:
Description: A potential TDU War was detected. This node has received more than 350 topology updates about the reported resource. This implies that the status of the resource is changing at a rate above normal. If the status of the resource is not expected to change frequently then a TDU War may be in progress.
Function Degradation: This resource will not be broadcast in topology updates for the next 15 minutes. After that time re-broadcasting will continue and the War may continue until the problem is resolved. An MS alert is generated and sent to the focal point. The resource(node or tg) in question may have invalid characteristics which can make it unusable.
Customer Action: Check for multiple nodes that may be configured with the same CP name of that specified as the origin CP name. Take any duplicates down and reconfigure with a different CP name. If a duplicate is not found then there is a software error and documentation at the Origin CP name should be gathered. To stop the War, take down the CP which is defined as the Origin CP name. This CP should be reconfigured with a different CP name before re-activating.
System Developer Action: Debug and determine what caused the TDU war.
Log events for the accounting services component of APPC (ACS).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Additional Data:
Description: ????
??????
Function Degradation:
Customer Action:
System Developer Action:
Log events for the problem determination services component of APPC (PDS).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: The problem determinsation services component of APPN (PDS) received an internal inter-process signal it does not recognize (or process). An internal code problem exists within pSNA.
The PDS internal data routing routine received an IPS that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to PDS.
Function Degradation: The unrecognized IPS is ignored, and PDS continues to process other signals. Unexpected results will probably follow this problem, since PDS or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Log events for the high performance routing components of APPN (HPR). Included are the HPR path control, HPR address space manager, and HPR session connector components.
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Description: The high performance routing address space manager (HPR ASM) received an SNA message it does not recognize (or process).
An HPR address space manager received a SNA message (MU) that it does not recognize or process. HPR ASM only processes session messages, such as BIND and UNBIND. This condition should not occur, since the unrecognized message should not have been routed to HPR ASM for processing. An internal code problem exists within pSNA.
Function Degradation: The detecting HPR address space manager process abends. The same process is used to process all messages sent and received for the related HPR TG/link, so no further communications is available over that link (or any of the sessions that use the link). The adjacent node may not be notified of the abnormal termination until messages it sends are rejected.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: A software problem exists within pSNA.
A high performance routing address space manager (HPR ASM) received an IPS via an unrecognized process queue. This condition should never occur, since HPR ASM defines all possible queues it can receive IPS data from. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and HPR ASM continues to process other signals. Unexpected results will probably follow this problem, since HPR ASM or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Not used yet.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Description: High performance routing (HPR) path control generated an alert.
HPR path control/address space manager/session connector detected an alert-able condition and sent the formatted SNA alert to MS for transmission to its alert focal point.
Function Degradation: The actual functional consequences depend on the detected condition (the generated alert).
Customer Action: Refer to the information contained in the alert, as well as related log entries and messages for more information and recommended actions.
System Developer Action: None.
Description: Either the high performance routing address space manager (HPR ASM) or an instance of HPR path control received an internal inter-process signal it does not recognize (or process).
An HPR address space manager or path control instance received an IPS that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to HPR ASM or HPR path control for processing. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and HPR ASM or path control continues to process other signals. Unexpected results will probably follow this problem, since HPR ASM, HPR path control, or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: High performance routing path control (HPR PC) received an SNA message it does not recognize (or process). A software problem exists within pSNA.
The HPR path control receive router FSM received an unexpected or unrecognized input message (MU). The received message is a single-segment message. This condition should not occur, since the FSM should be robust enough to handle any valid message, and only valid messages should be passed to the FSM. An internal code problem exists within pSNA.
Function Degradation: The received message is ignored, and processing continues. Unexpected results will probably follow this problem, since HPR PC is probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine if the received input value was invalid or was unexpected.
Description: High performance routing path control (HPR PC) received an SNA message it does not recognize (or process). A software problem exists within pSNA.
The HPR path control receive router FSM received an unexpected or unrecognized input message (MU). The received message is the first segment in a multi-segmented message. This condition should not occur, since the FSM should be robust enough to handle any valid message, and only valid messages should be passed to the FSM. An internal code problem exists within pSNA.
Function Degradation: The received message is ignored, and processing continues. Unexpected results will probably follow this problem, since HPR PC is probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine if the received input value was invalid or was unexpected.
Description: High performance routing path control (HPR PC) received an SNA message it does not recognize (or process). A software problem exists within pSNA.
The HPR path control receive router FSM received an unexpected or unrecognized input message (MU). The received message is a middle segment in a multi-segmented message. The request code was obtained from the first segment. This condition should not occur, since the FSM should be robust enough to handle any valid message, and only valid messages should be passed to the FSM. An internal code problem exists within pSNA.
Function Degradation: The received message is ignored, and processing continues. Unexpected results will probably follow this problem, since HPR PC is probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine if the received input value was invalid or was unexpected.
Description: High performance routing path control (HPR PC) received an SNA message it does not recognize (or process). A software problem exists within pSNA.
The HPR path control receive router FSM received an unexpected or unrecognized input message (MU). The received message is the last segment in a multi-segmented message. The request code was obtained from the first segment. This condition should not occur, since the FSM should be robust enough to handle any valid message, and only valid messages should be passed to the FSM. An internal code problem exists within pSNA.
Function Degradation: The received message is ignored, and processing continues. Unexpected results will probably follow this problem, since HPR PC is probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine if the received input value was invalid or was unexpected.
Description: An instance of high performance routing path control (HPR PC) received an SNA message it does not recognize (or process). A software problem exists within pSNA.
The HPR path control receive router FSM outputted an unknown or invalid action code. The probable causes are:
Function Degradation: The input value is ignored, and processing continues. Unexpected results will probably follow this problem, since HPR PC is probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Implement code fix.
Description: A high performance routing path control instance (HPR PC) received an SNA message it does not recognize (or process).
A HPR path control instance received a SNA message (MU) that it does not recognize or process. This condition should not occur, since the unrecognized message should not have been routed to HPR PC for processing. An internal code problem exists within pSNA.
Function Degradation: The received message is ignored, and processing continues. Unexpected results will probably follow this problem, since the data contained in the ignored message is lost.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: An instance of high performance routing path control (HPR PC) received an SNA message that contains invalid SNA headers (TH or RH settings are invalid).
HPR path control received an invalid SNA message from another node. The received message did not pass the basic SNA message verification checks (validating TH and RH settings). The probable causes are:
Function Degradation: The input SNA message is ignored, and processing continues. Unexpected results will probably follow this problem, since the data contained in the message is lost. In addition, the communications support in the nodes are either in error or are incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: An instance of high performance routing path control (HPR PC) received an invalid IPS message from a DLC or RTP (rapid transport protocol). A software problem exists within pSNA.
The received IPS was a DLC message not recognized or supported by HPR path control. This condition should not occur, since HPR path control should only send receive messages from RTP, and RTP should send valid messages that HPR path control understands. An internal code problem exists within pSNA.
Function Degradation: The input IPS is ignored, and processing continues. Unexpected results will probably follow this problem, since HPR PC and RTP or a DLC are probably in error and out of sequence. Depending on the sequence of events, HPR path control may explicitly deactivate the HPR TG (link).
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: A high performance routing session connector (HPR SC) received an internal inter-process signal it does not recognize (or process).
A session connector using HPR received an IPS that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to a HPR session connector instance for processing. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and the HPR session connector continues to process other signals. Unexpected results will probably follow this problem, since the HPR session connector or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: A high performance routing session connector (HPR SC) received an internal inter-process signal, but cannot find the control blocks associated with the session connector.
The HPR path control/session connector main process received an inter-process signal that it cannot route. The EGPE logical process identified in the signal is a session connector using HPR, but the process-specific control blocks cannot be located. An internal code problem exists within pSNA.
Function Degradation: The IPS is ignored, and processing continues. Unexpected results will probably follow this problem, since the HPR session connector/path control instance is probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: None.
Function Degradation: None
Customer Action: None
System Developer Action: None
Log events for the rapid transport protocol component of APPN (RTP).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Description: None.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Description: The rapid transport protocol component (RTP) received a timer expired notification it does not recognize (or process). This condition should not occur, since the unrecognized timer event should not have been routed to RTP for processing. An internal code problem exists within pSNA.
Function Degradation: The unrecognized timer event is ignored, and RTP continues to process other signals. Unexpected results will probably follow this problem, since RTP or another node component are probably in error and out of sequence. Some RTP operations may hang because the timer event is ignored.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with RTP traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The error recovery routine for one of the processes that make up the rapid transport protocol component (RTP) was invoked. The associated process detected a severe error and abended. An internal code problem exists within pSNA or EGPE.
Function Degradation: The indicated RTP process terminates. The local node can no longer compute or use session routes using the rapid transport protocol over HPR (high performance routing) connections.
Customer Action: Call service with the code point, error description, and abend code value if possible. A process abend file containing a snapshot of the pSNA storage areas may have been created when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The rapid transport protocol component (RTP) detected an error while attempting to send a message.
The connection for the message is in an invalid state. The current status of the connection indicates that transmission of the message is unreliable.
Function Degradation: The current message is lost. RTP continues processing, trying to send any other messages and processing any received messages. Unexpected results will probably follow this problem, since RTP could not send a message.
Customer Action: Determine the cause of the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix.
Additional Data: Has the following format:
Description: The rapid transport protocol component (RTP) detected an error while processing a received message.
The connection for the message is in an invalid state. The current status of the connection indicates that transmission of the message is unreliable.
Function Degradation: The current message is lost and the rtp connection of this message is terminated. RTP continues processing, trying to send any other messages and processing any received messages. Unexpected results will probably follow this problem, since RTP could not send a message.
Customer Action: Determine the cause of the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix.
Log events for the PU Network Services of APPC (PNS).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: The PU Network Services (PNS) received an internal inter-process signal via an unrecognized process queue.
The PU Network Services for the node received an IPS via an unrecognized process queue. This condition should not occur since PU Network Services defines all process queues it can receive inter-process signals from. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and PNS continues to process other signals. Unexpected results will probably follow this problem, since PNS or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The PU Network Services (PNS) received an internal inter-process signal it does not recognize (or process) from the Configuration Services (CS) component.
The PU Network Services for the node received an IPS from from Configuration Services that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to PNS for processing. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and PNS continues to process other signals. Unexpected results will probably follow this problem, since PNS or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The PU Network Services (PNS) received an internal inter-process signal it does not recognize (or process) from the Address Space Manager (ASM) component.
The PU Network Services for the node received an IPS from from Address Space Manager that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to PNS for processing. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and PNS continues to process other signals. Unexpected results will probably follow this problem, since ASM, PNS or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: PU Network Services rejected an incoming ACTPU because it detected a syntax error in the ACTPU request.
The PU Network Services rejected an ACTPU received from the remote node. The ACTPU contained invalid information. The sense code identifies the actual error. The probable causes are:
Function Degradation: PU Network Services rejects the ACTPU by sending a negative response to the ACTPU.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: PU Network Services rejected an incoming DACTPU because it detected a syntax error in the DACTPU request.
The PU Network Services rejected an DACTPU received from the remote node. The DACTPU contained invalid information. The sense code identifies the actual error. The probable causes are:
Function Degradation: PU Network Services rejects the DACTPU by sending a negative response to the DACTPU.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The PU Network Services (PNS) received an SNA message from Address Space Manager with a request code that it does not recognize (or process).
The PU Network Services (PNS) for the node received a SNA message (MU) from Address Space Manager with a request code that it does not recognize or process. PU Network Services only processes session control request units for the SSCP-PU session, such as ACTPU and DACTPU. This condition should not occur, since Address Space Manager should not have routed the unrecognized message to PNS for processing. The probable causes are:
Function Degradation: The unrecognized MU is ignored, and PNS continues to process other signals. Unexpected results will probably follow this problem, since Address Space Manager, PNS or another node component are probably in error and out of sequence. In addition, communications may be affected since the received message is ignored.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The PU Network Services rejected an incoming ACTPU because the operator has issued a STOP_APPN verb to terminate the local node.
The PU Network Services rejected a ACTPU received from a remote node because a STOP_APPN verb is in progress and the local node is terminating. The sense code reflects this condition. The probable causes are:
Function Degradation: The PU Network Services rejects the ACTPU by sending a negative response to the ACTPU.
Customer Action: Re-start the local node (pSNA).
System Developer Action: None
Additional Data: Has the following format:
Description: The PU Network Services rejected an incoming ACTPU because it was not expected.
The PU Network Services rejected a ACTPU received from a remote node because an SSCP-PU session already exists with the remote node. The sense code reflects this error. The probable causes are:
Function Degradation: The PU Network Services rejects the ACTPU by sending a negative response to the ACTPU.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The PU Network Services rejected an incoming DACTPU because it was not expected.
The PU Network Services rejected a DACTPU received from a remote node because it had not received an ACTPU to start the SSCP-PU session prior to receiving the DACTPU. The sense code reflects this error. The probable causes are:
Function Degradation: The PU Network Services rejects the DACTPU by sending a negative response to the DACTPU.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The PU Network Services (PNS) received an internal inter-process signal it does not recognize (or process) from the Node Operator Facility (NOF) component.
The PU Network Services for the node received an IPS from the Node Operator Facility (NOF) component that it does not recognize or process. This condition should not occur, since the Node Operator Facility (NOF) should not have routed the unrecognized signal to PNS for processing. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and PNS continues to process other signals. Unexpected results will probably follow this problem, since NOF, PNS or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Log events for the common programming interface of APPC (CPIC).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: A user application specified an invalid parameter on a CPI-C call. The data identifies the parameter and verb that failed.
Function Degradation: The issued CPI-C verb fails with the indicated return code.
Customer Action: Use the information in the log record to determine the invalid parameter. Debug and fix the user application.
System Developer Action: None.
Additional Data: Has the following format:
Description: CPI-C encountered a should-not-occur condition while processing a verb issued by a user application. CPI-C encountered an unexpected return value from APPC or an internal logic problem within its software. An internal code problem exists within pSNA. The data identifies the verb that failed.
Function Degradation: The issued CPI-C verb fails.
Customer Action: Use the information in the log record to determine the verb that failed. Often another log record is created which identifies the encountered problem in more detail. Use the information in these additional log records to help determine the cause of the problem:
If possible, try and re-create the problem with data CPI-C, and APPC API traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: CPI-C encountered an error while processing a CPI-C verb issued by an application. An APPC verb issued by CPI-C failed. The details of the error are indicated by the primary and secondary return codes returned by the APPC verb. The possible causes of this problem are:
Function Degradation: The issued CPI-C verb fails.
Customer Action: Use the descriptions of the logged APPC primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the user application, the communications support in the local node, or the communications support in the remote node.
If possible, try and re-create the problem with data CPI-C, and APPC API traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: CPI-C encountered an error while trying to determine the APPC TP name use by an application. CPI-C either could not read the environment variable used to specify the TP name (APPCTPN) or the value of the variable is not a valid TP name.
Function Degradation: The issued CPI-C verb fails.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Description: CPI-C encountered an error while trying to start or end an APPC TP instance. APPC TP instances are used to correlate conversations. CPI-C allows multiple TP instances for a CPI-C application, but if more than one TP instance is used, then the CPI-C application must use product-specific extensions to indicate which instance is being used. This failure occurs in the following situations:
Function Degradation: The issued CPI-C verb fails with the indicated return code.
Customer Action: Debug and fix the user application. The application must limit itself to a single active TP instance, or must explicitly specify which TP instance to use when starting conversations and ending TP instances.
System Developer Action: None.
Description: An application tried to use CPI-C conversations while the underlying APPC support is not active.
Function Degradation: The issued CPI-C verb fails with the indicated return code.
Customer Action: Start the APPC communications subsystem.
System Developer Action: None.
Additional Data: Has the following format:
Description: A user application specified an invalid combination of parameters on a CPI-C verb. The parameters specified on a verb or either incompatible with one another, or inappropriate for the current state of the CPI-C conversation. The data identifies the parameter and verb that failed.
Function Degradation: The issued CPI-C verb fails with the indicated return code.
Customer Action: Use the information in the log record to determine the invalid parameter. Debug and fix the user application.
System Developer Action: None.
Additional Data: Has the following format:
Description: CPI-C could not obtain the memory needed to process a verb issued by a user application.
Function Degradation: The issued CPI-C verb fails.
Customer Action: Investigate whether the problem was caused by a shortage of available memory. Increase the amount of memory available to the application if a memory shortage is suspected.
If it appears that the application has enough memory available to process the request, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with data CPI-C, and APPC API traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA.
Additional Data: Has the following format:
Description: A system function failed while processing a CPI-C verb issued by an application. Possible errors include:
Function Degradation: The issued CPI-C verb fails.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Log events for the SNMP sub-agent for pSNA (SSA).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: The APPN SNMP sub-agent (SSA) received an internal inter-process signal containing data it does not recognize (or process). An internal code problem exists within pSNA.
The SSA internal data routing routine received a management services request it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to SSA.
Function Degradation: The invalid IPS is ignored, and SSA continues to process other signals. Unexpected results will probably follow this problem, since SSA or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: A failure occurred trying to create the problem determination services component. The APPN SNMP sub-agent (SSA)could not start the component. The possible causes of this problem are:
Function Degradation: SSA continues normal processing, trying to create any other required components and processing any received requests. Unexpected results may follow this problem since the problem determination services component is unavailable.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The APPN SNMP sub-agent encountered a should-not-occur condition within the component. An internal control block is invalid. An internal code problem exists within pSNA (SSA).
The SNMP sub-agent object is not defined in the internal SNMP object tree.
Function Degradation: The SNMP sub-agent terminates. Unexpected results will probably follow this problem, since SSA is not available for use. All SNMP management requests are rejected.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data:
Description: The APPN SNMP sub-agent encountered a should-not-occur condition within the component. An internal control block is invalid. An internal code problem exists within pSNA (SSA).
One of the APPN SNMP sub-agent sub-trees is not defined in the internal SNMP object tree.
Function Degradation: The SNMP sub-agent terminates. Unexpected results will probably follow this problem, since SSA is not available for use. All SNMP management requests are rejected.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The APPN SNMP sub-agent encountered a should-not-occur condition within the component. An internal control block is invalid. An internal code problem exists within pSNA (SSA).
One of the APPN SNMP variables (classes) is not defined in the internal SNMP object tree.
Function Degradation: The SNMP sub-agent terminates. Unexpected results will probably follow this problem, since SSA is not available for use. All SNMP management requests are rejected.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: A failure occurred trying to create one of the processes that make up the SNMP sub-agent (SSA). The process used to communication with SNMP managers could not be started. The possible causes of this problem are:
Function Degradation: The SNMP sub-agent terminates. Unexpected results will probably follow this problem, since SSA is not available for use. All SNMP management requests are rejected.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A failure occurred trying to create the APPN SNMP sub-agent process used to control tracing of the sockets calls used by the sub-agent. The possible causes of this problem are:
Function Degradation: SSA continues normal processing, trying to create any other required components and processing any received requests. The sockets calls issued by SSA can not be traced. The SNMP sub-agent will retry creating the trace process.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The APPN SNMP sub-agent (SSA) encountered an error trying to obtain management data from one of the other APPN node components. SSA did not receive a response to its request within 10 seconds. The possible causes of this problem are:
Function Degradation: The SNMP sub-agent fails to retrieve the requested management data. The response sent back to the SNMP manager application that requested the data will not contain all of the data requested by the manager.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The APPN SNMP sub-agent (SSA) received an internal inter-process signal it does not recognize (or process). An internal code problem exists within pSNA. This condition should not occur, since the unrecognized signal should not have been routed to SSA.
SSA received an unrecognized reply to a management data request.
Function Degradation: The unrecognized IPS is ignored, and SSA continues to wait for a reply from the APPN node containing the requested management data. Unexpected results will probably follow this problem, since SSA or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: An APPN component could not send management data to the APPN SNMP sub-agent (SSA), The possible causes of this problem are:
Function Degradation: The SNMP sub-agent fails to retrieve the requested management data. The SNMP sub-agent will time out waiting for the requested management data. The response sent back to the SNMP manager application that requested the data will not contain all of the data requested by the manager.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Description: The APPN SNMP sub-agent could not send a request for management data to an APPN component executing in an attached sub-system (co-processor). The possible causes of this problem are:
Function Degradation: The SNMP sub-agent fails to retrieve the requested management data. The response sent back to the SNMP manager application that requested the data will not contain all of the data requested by the manager.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A request to verify that the HPR rapid transport protocol component (RTP) or APPN session connector manager (SCM) failed.
The APPN SNMP sub-agent could not verify that the required APPN component (RTP or SCM) is active and available. The possible causes of this problem are:
This log entry may also be created if the sub-agent failed to verify the existence of other node components, such as path control or address space manager. The EGPE function PEstart_ready_monitor failed.
Function Degradation: The SNMP sub-agent fails to retrieve the requested (RTP or SCM) management data. The response sent back to the SNMP manager application that requested the data will not contain all of the data requested by the manager.
Customer Action: Try and determine the cause of the problem:
If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Description: The APPN SNMP sub-agent could not send a control request to one or more APPN components. The possible causes of this problem are:
Function Degradation: The SNMP sub-agent (SSA) fails to perform the requested control operation. SSA continues to process requests. Unexpected results will probably follow this problem, since the sub-agent could not perform the needed control operation. SSA and the targetted node component are probably out of sequence.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The APPN SNMP sub-agent (SSA) received an unexpected internal inter-process signal.
The IPS was received before SSA was ready to process the received message. This condition should not occur, since the unrecognized signal should not have been routed to SSA for processing. An internal code problem exists within pSNA. The SSA received the unexpected IPS while waiting for a response to its monitor request (PEstart_ready_monitor) for a node component.
Function Degradation: The unexpected IPS is ignored, and SSA continues to process other signals. Unexpected results will probably follow this problem, since SSA or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: The APPN SNMP sub-agent (SSA) process used to receive SNMP management requests from the network is being shut down by the main SSA process. SSA encountered an unrecoverable error condition and is in the process of shutting down. The main SSA process will create additional log entries identifying the unrecoverable error condition.
Function Degradation: The SNMP sub-agent terminates. Unexpected results will probably follow this problem, since SSA is not available for use. All SNMP management requests are rejected.
Customer Action: See the description of any related error log entries.
System Developer Action: See the description of any related error log entries.
Description: The APPN SNMP sub-agent could not send an HPR route test request to APPN session services. The possible causes of this problem are:
Function Degradation: The SNMP sub-agent (SSA) fails to perform the requested route test operation. SSA continues to process requests.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Description: The APPN SNMP sub-agent could not initiate a requested HPR path switch operation. The sub-agent could not forward the request to the HPR rapid transport protocol component (RTP). The possible causes of this problem are:
Function Degradation: The SNMP sub-agent (SSA) fails to perform the requested path switch operation. SSA continues to process requests. Unexpected network problems may follow this problem, since the requested path switch could not be performed.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: An APPN node component received an internal inter-process signal it does not recognize (or process) from the APPN SNMP sub-agent (SSA). An internal code problem exists within pSNA. This condition should not occur, since the unrecognized signal should not have been sent by SSA.
SSA sent an invalid IPS message to another APPN component.
Function Degradation: The unrecognized IPS is ignored. The component and SSA continue to process other messages. The SSA component may time-out, waiting for a reply to the discarded message. Unexpected results will probably follow this problem, since SSA or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The APPN SNMP sub-agent could not obtain the current statistical information from the HPR network control layer (NCL). The NCL encountered an error while retrieving the data. The possible causes of this problem are:
Function Degradation: The SNMP sub-agent fails to retrieve the requested management data. The response sent back to the SNMP manager application that requested the data will not contain all of the data requested by the manager.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The APPN SNMP sub-agent could not obtain the current statistical information from the HPR network control layer (NCL). The NCL encountered an error while retrieving the next block of data after successfully retrieving other SNMP data. The possible causes of this problem are:
Function Degradation: The SNMP sub-agent fails to retrieve all the requested management data. The response sent back to the SNMP manager application that requested the data will not contain all of the data requested by the manager.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A request to verify that the APPN session connector manager (SCM) failed.
The APPN SNMP sub-agent could not verify that the required APPN component (SCM) is active and available. The possible causes of this problem are:
Function Degradation: The SNMP sub-agent fails to retrieve the requested internediate session (ISR) management data. The response sent back to the SNMP manager application that requested the data will not contain all of the data requested by the manager.
Customer Action: Try and determine the cause of the problem:
If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Log events for the application program interface component of pSNA (API).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: A system (EGPE) function failed while trying to process an API verb received from an application program. The probable causes are:
Some of the EGPE functions that can fail are:
Function Degradation: In almost all cases, the error occurs while processing an API verb from an application. The verb being process is returned to the application with an UNEXPECTED_GPE_ERROR (x'1003') primary return code and the secondary return code set to the return code from the failing EGPE function.
In isolated cases, the error occurs while attempting to release the resources allocated for a transaction program when the APPC TP ends. In this case, processing continues within the local node, but some of the resources allocated for the TP may not be released.
Finally, this log record is also created when the local node is attempting to notify an application that an API verb has completed. In this case, processing continues, but the API verb is not posted complete and the application will probably hang.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as the logged return code).
If the problem was not caused by a system failure or resource shortage, the problem was probably caused by a problem in the communications support in the local node. Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A system (OS/2) function failed while trying to process an API verb received from an application program. The probable causes are:
Some of the OS/2 functions that can fail are:
Function Degradation: In almost all cases, the error occurs while processing an API verb from an application. The verb being process is returned to the application with an UNEXPECTED_DOS_ERROR (x'F011') primary return code and the secondary return code set to the return code from the failing operating system function. If the error occurs while processing appc_register_memory(), the function completes with REGISTER_UNEXPECTED_DOS_ERROR (2).
In isolated cases, the error occurs while attempting to release the resources allocated for a transaction program when the APPC TP ends. In this case, processing continues within the local node, but some of the resources allocated for the TP may not be released.
Finally, this log record is also created when the local node is attempting to notify an application that an API verb has completed. In this case, processing continues, but the API verb is not posted complete and the application will probably hang.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as the logged return code).
If the problem was not caused by a system failure or resource shortage, the problem was probably caused by a problem in the communications support in the local node. Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Log events for the APPN service transaction programs (TP).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: The send_network_search TP could not allocate a conversation with an adjacent node.
The send_network_search directory services transaction program could not send a locate search request to an adjacent node. The APPC ALLOCATE verb failed for the receive_network_search TP in an adjacent node (over the CP-CP sessions). The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The current search request is ignored, and the TP continues to service other search requests received from directory services. Unexpected results will probably follow this problem, since DS is expecting a reply to the failed search request.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The send_network_search TP could not send a search request to an adjacent node.
The send_network_search directory services transaction program could not send a locate search request to an adjacent node. The APPC SEND_DATA for the locate command failed. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The conversation created to send the search request is de-allocated (type=ABEND_PROGRAM). The current search request is purged, and the TP continues to service other search requests received from directory services. Unexpected results will probably follow this problem, since DS is expecting a reply to the failed search request.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: The network node receive_resource_reg transaction program received invalid data.
The transaction program that processes resource registration requests from other nodes received invalid data. It could not parse the received resource registration request. The probable causes are:
Function Degradation: The conversation from which the invalid data was received is de-allocated (type=ABEND_PROGRAM). The received registration request is ignored and the transaction program terminates. The local node continues to process registration requests from other nodes. Unexpected results will probably follow this problem, since the node that sent the request is probably not expecting its registration attempt to fail.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The network node receive_resource_reg transaction program detected an error in a received resource registration request, but could not send the "negative" reply.
Directory services detected an error in a received resource registration request, but the receive_resource_reg transaction program could not send an error reply to the adjacent node. The APPC SEND_ERROR verb failed for the resource registration reply. The details of the error are indicated by the primary return code. The possible causes of this problem are:
Function Degradation: The conversation from which the invalid data was received is de-allocated (type=ABEND_PROGRAM). The received registration request is ignored and the transaction program terminates. The local node continues to process registration requests from other nodes. Unexpected results will probably follow this problem, since the node that sent the request is probably not expecting its registration attempt to fail.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The network node receive_resource_reg transaction program received an invalid message from directory services.
The network node receive_resource_reg transaction program received an IPS message from directory services that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to the TP by directory services for processing. An internal code problem exists within pSNA.
Function Degradation: The conversation from which the current registration request was received is de-allocated. The received IPS is ignored. The transaction program continues to process registration requests from other nodes. Unexpected results will probably follow this problem, since DS and its resource registration TP are probably in error and out of sequence.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The mds_send TP could not send an MDS message to an adjacent node.
The mds_send management services transaction program could not send a MDS message to an adjacent node. The APPC SEND_DATA verb for the MDS message failed. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The conversation created to send the MDS message is de-allocated (type=ABEND_PROGRAM). The current MDS message is purged and MS is notified of the failure. The TP continues to service other MDS send requests received from management services. Unexpected results may follow this problem, since the management services message could not be sent.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The management services mds_receive transaction program received invalid data.
The transaction program that receives MDS messages from other nodes received invalid data. The size of the received MDS message exceeded the maximum size allowed by SNA protocol rules. The probable causes are:
Function Degradation: The conversation from which the invalid data was received is de-allocated (type=ABEND_PROGRAM). The received MDS message is ignored and the transaction program terminates. The local node continues to process MDS messages from other nodes. Unexpected results will probably follow this problem, since the node that sent the request is probably not expecting its transmission to fail.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The management services mds_receive transaction program received invalid or unexpected data.
The transaction program that receives MDS messages from other nodes received invalid or unexpected data. The what received status indicator from the APPC RECEIVE_AND_WAIT verb is not an expected value. The probable causes are:
Function Degradation: The conversation from which the invalid data was received is de-allocated (type=ABEND_PROGRAM). The received MDS message is ignored and the transaction program terminates. The local node continues to process MDS messages from other nodes. Unexpected results will probably follow this problem, since the node that sent the request is out of sync with the local node.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The management services mds_receive transaction program could not receive an MDS message.
The mds_receive management services transaction program could not receive a MDS message from an adjacent node. The APPC RECEIVE_AND_WAIT verb for the MDS message failed. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The conversation created to receive the MDS message is de-allocated (type=ABEND_PROGRAM). The received MDS message is ignored and the transaction program terminates. The local node continues to process MDS messages from other nodes. Unexpected results will follow this problem, since the node that sent the request is out of sync with the local node.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The management services msu_handler transaction program received invalid data.
The transaction program that receives CP-MSU messages from migration nodes received invalid data. The size of the received CP-MSU message exceeded the maximum size allowed by SNA protocol rules. The probable causes are:
Function Degradation: The conversation from which the invalid data was received is de-allocated (type=ABEND_PROGRAM). The received CP-MSU message is ignored and the transaction program terminates. The local node continues to process CP-MSU messages from other nodes. Unexpected results will probably follow this problem, since the node that sent the request is probably not expecting its transmission to fail.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The management services msu_handler transaction program received invalid or unexpected data.
The transaction program that receives CP-MSU messages from migration nodes received invalid or unexpected data. The what received status indicator from the APPC RECEIVE_AND_WAIT verb is not an expected value. The probable causes are:
Function Degradation: The conversation from which the invalid data was received is de-allocated (type=ABEND_PROGRAM). The received CP-MSU message is ignored and the transaction program terminates. The local node continues to process CP-MSU messages from other nodes. Unexpected results will probably follow this problem, since the node that sent the request is out of sync with the local node.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The management services msu_handler transaction program could not receive an CP-MSU message.
The msu_handler management services transaction program could not receive a CP-MSU message from an adjacent migration node. The APPC RECEIVE_AND_WAIT verb for the CP-MSU message failed. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The conversation created to receive the CP-MSU message is de-allocated (type=ABEND_PROGRAM). The received CP-MSU message is ignored and the transaction program terminates. The local node to process CP-MSU messages from other nodes. Unexpected results will probably follow this problem, since the node that sent the request is out of sync with the local node.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session services cp_cap_son transaction program received invalid or unexpected data.
The transaction program that receives CP capabilities on the con-loser session from adjacent nodes received invalid or unexpected data, or an error occurred while receiving the data. Either the what received status indicator from the APPC RECEIVE_AND_WAIT verb is not an expected value or the APPC RECEIVE_AND_WAIT verb for the CP capabilities message failed. The details of the error are indicated by the primary and secondary return codes and the what received indicator. The probable causes are:
Function Degradation: The conversation is de-allocated (type=ABEND_PROGRAM). The current CP capabilities message is purged, SS is notified of the failure, and the transaction program terminates. The local node continues to service other CP capabilities messages received from other nodes.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session services request_cp_cap transaction program could not receive the CP capabilities message from an adjacent node.
The request_cp_cap session services transaction program could not receive a CP capabilities message from an adjacent node. The APPC RECEIVE_AND_WAIT verb for the CP capabilities message failed. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The conversation created to receive the CP capabilities message is de-allocated (type=ABEND_PROGRAM). The received CP capabilities message is ignored, SS is notified of the failure, and the transaction program terminates. The local node continues to process CP capabilities messages from other adjacent nodes. Unexpected results will probably follow this problem, since CP capabilities could not be exchanged with an adjacent node (the CP-CP sessions with the adjacent node are probably deactivated).
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session services request_cp_cap transaction program received invalid or unexpected data.
The request_cp_cap session services transaction program could not receive a CP capabilities message from an adjacent node. The APPC RECEIVE_AND_WAIT verb for the CP capabilities message did not receive the expected data. The details of the error are indicated by the what received indicators from the RECEIVE_AND_WAIT APPC verb. The possible causes of this problem are:
Function Degradation: The conversation created to receive the CP capabilities message is de-allocated (type=ABEND_PROGRAM). The received CP capabilities message is ignored, SS is notified of the failure, and the transaction program terminates. The local node continues to process CP capabilities messages from other adjacent nodes. Unexpected results will probably follow this problem, since CP capabilities could not be exchanged with an adjacent node (the CP-CP sessions with the adjacent node are probably deactivated).
Customer Action: Use the descriptions of the logged return codes and indicators to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The process_output_tdu TP could not allocate a conversation with an adjacent node.
The process_output_tdu TRS transaction program could not send one or more topology updates (TDUs) to an adjacent node. The APPC ALLOCATE verb failed for the receive_tdu TP in an adjacent node (over the CP-CP sessions). The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The TP continues to transmit the TDUs to all other adjacent nodes. It also continues to service other broadcast requests received from TRS. Unexpected results will probably follow this problem, since some topology updates could not be sent to some adjacent network nodes. Some network node topology databases may be out of sync with the topology database in the adjacent node.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: The send_network_search directory services transaction program was started but could not attach to the APPN communications system. This should not occur since the transaction program cannot run without the APPN communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point, error description, and abend code value if possible. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: The send_network_search directory services transaction program was started but could not attach to the APPC communications system. This should not occur since the transaction program cannot run without the APPC communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The send_network_search transaction program could not register itself as an APPC transaction program.
The send_network_search directory services transaction program can not attach to the APPC/APPN communications system. The APPC TP_STARTED verb failed.
The details of the error are indicated by the primary and secondary return codes. An internal code problem exists within pSNA.
Function Degradation: The transaction program process terminates. APPC/APPN communication services will not function correctly because directory services will not be able to send search requests (LOCATEs) to other nodes in the APPN network.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: The receive_resource_reg directory services transaction program was started but could not attach to the APPN communications system. This should not occur since the transaction program cannot run without the APPN communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: The receive_resource_reg directory services transaction program was started but could not attach to the APPC communications system. This should not occur since the transaction program cannot run without the APPC communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The receive_resource_reg transaction program could not receive (accept) a conversation from an adjacent node.
The receive_resource_reg directory services transaction program could not receive a registration request from an adjacent node. The APPC RECEIVE_ALLOCATE verb failed for the receive_resource_reg TP in the local node (over the CP-CP sessions). The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The received message is ignored and the transaction program process terminates. The local node will continue to process resource registration requests from other nodes. Unexpected results will probably follow this problem, since the node that sent the request is out of sync with the local node.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The directory services receive_resource_reg transaction program could not receive a resource registration message.
The receive_resource_reg directory services transaction program could not receive a resource registration message from an adjacent node. The APPC RECEIVE_AND_WAIT verb for the message failed. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The conversation created to receive the message is de-allocated (type=ABEND_PROGRAM). The received message is ignored and the transaction program process terminates. The local node will continue to process resource registration requests from other nodes. Unexpected results will probably follow this problem, since the node that sent the request is out of sync with the local node.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The directory services receive_resource_reg transaction program received invalid or unexpected data.
The transaction program that receives resource registration requests from other nodes received invalid or unexpected data. The what received data indicator from the APPC RECEIVE_AND_WAIT verb is not an expected value. The probable causes are:
Function Degradation: The conversation from which the invalid data was received is de-allocated (type=ABEND_PROGRAM). The received resource registration request is ignored and the transaction program process terminates. The local node continues to process registration requests from other nodes. Unexpected results will probably follow this problem, since the node that sent the request is out of sync with the local node.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The directory services receive_resource_reg transaction program received invalid or unexpected data.
The transaction program that receives resource registration requests from other nodes received invalid or unexpected data. The what received status indicator from the APPC RECEIVE_AND_WAIT verb is not an expected value. The probable causes are:
Function Degradation: The conversation from which the invalid data was received is de-allocated (type=ABEND_PROGRAM). The received resource registration request is ignored and the transaction program process terminates. The local node continues to process registration requests from other nodes. Unexpected results will probably follow this problem, since the node that sent the request is out of sync with the local node.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The receive_resource_reg TP could not confirm the successful processing of a resource registration request.
The receive_resource_reg directory services transaction program could not confirm the successful processing of a resource registration request received from an adjacent node. The APPC CONFIRMED verb failed. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The conversation that received the registration request is de-allocated (type=ABEND_PROGRAM). The TP continues to receive resource registration requests from other nodes in the network. Unexpected results will probably follow this problem, since the remote node is expecting a reply to the registration request.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: The receive_network_search directory services transaction program was started but could not attach to the APPN communications system. This should not occur since the transaction program cannot run without the APPN communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: The receive_network_search directory services transaction program was started but could not attach to the APPC communications system. This should not occur since the transaction program cannot run without the APPC communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The receive_network_search transaction program could not receive (accept) a conversation from an adjacent node.
The receive_network_search directory services transaction program could not receive a network search (LOCATE) request from an adjacent node. The APPC RECEIVE_ALLOCATE verb failed for the receive_network_search TP in the local node (over the CP-CP sessions). The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The received message is ignored and the transaction program process terminates. The local node will continue to process network search requests from other nodes. Unexpected results will probably follow this problem, since the node that sent the request is out of sync with the local node.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The directory services receive_network_search transaction program could not receive a network search request.
The receive_network_search directory services transaction program could not receive a network search request from an adjacent node. The APPC RECEIVE_AND_WAIT verb for the message failed. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The conversation created to receive the message is de-allocated (type=ABEND_PROGRAM). The received message is ignored and the transaction program process terminates. The local node will continue to process network search requests from other nodes. Unexpected results will probably follow this problem, since the node that sent the request is out of sync with the local node.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The directory services receive_network_search transaction program received invalid or unexpected data.
The transaction program that receives network search requests from other nodes received invalid or unexpected data. The what received data indicator from the APPC RECEIVE_AND_WAIT verb is not an expected value. The probable causes are:
Function Degradation: The conversation from which the invalid data was received is de-allocated (type=ABEND_PROGRAM). The received network search request is ignored and the transaction program terminates. The local node continues to process requests from other nodes. Unexpected results will probably follow this problem, since the node that sent the request is out of sync with the local node.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: The req_resource_reg directory services transaction program was started but could not attach to the APPN communications system. This should not occur since the transaction program cannot run without the APPN communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: The req_resource_reg directory services transaction program was started but could not attach to the APPC communications system. This should not occur since the transaction program cannot run without the APPC communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The req_resource_reg transaction program could not register itself as an APPC transaction program.
The req_resource_reg directory services transaction program can not attach to the APPC/APPN communications system. The APPC TP_STARTED verb failed.
The details of the error are indicated by the primary and secondary return codes. An internal code problem exists within pSNA.
Function Degradation: The transaction program process terminates. APPC/APPN communication services will not function correctly because directory services will not be able to register its resources with other nodes in the APPN network.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The req_resource_reg TP could not allocate a conversation with an adjacent node.
The req_resource_reg directory services transaction program could not send a resource registration request to an adjacent node. The APPC ALLOCATE verb failed for the receive_resource_reg TP in an adjacent node. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The current registration request is ignored, and the TP continues to service other registration requests received from directory services. Unexpected results will probably follow this problem, since DS is expecting a reply to the failed request.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The req_resource_reg TP could not send a resource registration request to an adjacent node.
The req_resource_reg directory services transaction program could not send a resource registration request to an adjacent node. The APPC SEND_DATA verb for the registration request failed. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The conversation created to send the registration request is de-allocated (type=ABEND_PROGRAM). The current registration request is purged, and the TP continues to service other registration requests received from directory services. Unexpected results will probably follow this problem, since the resource is not registered with the adjacent node.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: An error occurred while the req_resource_reg TP was sending a resource registration request to an adjacent node.
The req_resource_reg directory services transaction program could not send a resource registration request to an adjacent node. The APPC DEALLOCATE verb for the registration request failed. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The TP continues to service other registration requests received from directory services. Unexpected results will probably follow this problem, since it is possible the resource is not registered with the adjacent node.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The directory services req_resource_reg transaction program could not receive a reply to a resource registration request from an adjacent node. CP capabilities message from an adjacent node.
The req_resource_reg directory services transaction program could not receive a resource registration reply from an adjacent node. The APPC RECEIVE_AND_WAIT verb for the reply failed. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The conversation created to send the resource registration request is de-allocated (type=NORMAL). The transaction program continues to send resource registration requests to other nodes. Unexpected results will probably follow this problem, since the node that received the request is out of sync with the local node. It is possible the resource is not registered with the adjacent node.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The directory services req_resource_reg transaction program received invalid or unexpected data.
The transaction program that sends resource registration requests to other nodes received invalid or unexpected data while waiting for the resource registration reply from an adjacent node. The what received data indicator from the APPC RECEIVE_AND_WAIT verb is not an expected value. The probable causes are:
Function Degradation: The conversation created to send the resource registration request is de-allocated (type=NORMAL). The transaction program continues to send resource registration requests to other nodes. Unexpected results will probably follow this problem, since the node that received the request is out of sync with the local node. It is possible the resource is not registered with the adjacent node.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: The mds_send management services transaction program was started but could not attach to the APPN communications system. This should not occur since the transaction program cannot run without the APPN communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: The mds_send management services transaction program was started but could not attach to the APPC communications system. This should not occur since the transaction program cannot run without the APPC communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The mds_send transaction program could not register itself as an APPC transaction program.
The mds_send management services transaction program can not attach to the APPC/APPN communications system. The APPC TP_STARTED verb failed.
The details of the error are indicated by the primary and secondary return codes. An internal code problem exists within pSNA.
Function Degradation: The transaction program process terminates. APPC/APPN communication services will not function correctly because management services will not be able to send any management data (such as alerts) to the management services focal points in the network.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The mds_send TP could not allocate a conversation with an adjacent node.
The mds_send management services transaction program could not start a management services transaction with an adjacent node. The APPC ALLOCATE verb failed for the mds_receive TP in an adjacent node. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The current management services message is ignored, and the TP continues to service other transactions received from management services. Unexpected results will probably follow this problem, since MS is expecting a reply to the failed transaction request.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The management services mds_send transaction program encountered a should-not-occur condition.
Management services specified an invalid mode name to use for a management services transaction. The only modes allowed for MS transactions are CPSVCMG and SNASVCMG. A programming error/deficiency exists within the pSNA node.
Function Degradation: The current management services message is ignored, and the TP continues to service other transactions received from management services. Unexpected results will probably follow this problem, since MS and the transaction program are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The mds_send transaction could not send an MDS message to an adjacent node.
The mds_send management services transaction program could not send a MDS message to an adjacent node. Either a software problem was detected or an error occurred while transferring the data. The details of the error are indicated by the primary return code.
This log record is created in conjunction with the following log records, which contain additional information about the nature of the failure.
Function Degradation: The conversation used to send the MDS message, if allocated, is de-allocated (type=ABEND_PROGRAM). The current MDS message is purged and MS is notified of the failure. The TP continues to service other MDS send requests received from management services. Unexpected results may follow this problem, since the management services message could not be sent.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: The mds_receive management services transaction program was started but could not attach to the APPN communications system. This should not occur since the transaction program cannot run without the APPN communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: The mds_receive management services transaction program was started but could not attach to the APPC communications system. This should not occur since the transaction program cannot run without the APPC communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The mds_receive transaction program could not receive (accept) a conversation from an adjacent node.
The mds_receive management services transaction program could not receive a management services message (such as an alert or a MS capabilities) from an adjacent node. The APPC RECEIVE_ALLOCATE verb failed for the mds_receive TP in the local node. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The received message is ignored and the transaction program process terminates. The local node will continue to process management service messages from other nodes. Unexpected results will probably follow this problem, since the node that sent the request is out of sync with the local node.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The mds_receive transaction program could not accept a conversation from an adjacent node.
The mds_receive management services transaction program could not receive a management services message (such as an alert or a MS capabilities) from an adjacent node. The mode name of the session the message was received from is invalid. Management services messages can only be transferred using the CPSVCMG or SNASVCMG modes. The possible causes of this problem are:
Function Degradation: The received message is ignored and the transaction program process terminates. The local node will continue to process management service messages from other nodes. Unexpected results will probably follow this problem, since the node that sent the request is out of sync with the local node and is probably in error.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: The msu_handler management services transaction program was started but could not attach to the APPN communications system. This should not occur since the transaction program cannot run without the APPN communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: The msu_handler management services transaction program was started but could not attach to the APPC communications system. This should not occur since the transaction program cannot run without the APPC communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The msu_handler transaction program could not receive (accept) a conversation from an adjacent node.
The msu_handler management services transaction program could not receive a management services message (such as an alert encapsulated in a CP-MSU) from an adjacent management services migration node. The APPC RECEIVE_ALLOCATE verb failed for the msu_handler transaction program in the local node. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The received message is ignored and the transaction program process terminates. The local node will continue to process management service messages from other MS migration nodes. Unexpected results will probably follow this problem, since the node that sent the request is out of sync with the local node.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The msu_handler transaction program could not accept a conversation from an adjacent node.
The msu_handler management services transaction program could not receive a management services message (such as an alert encapsulated in a CP-MSU) from an adjacent management services migration node. The mode name of the session the message was received from is invalid. Management services messages can only be transferred using the CPSVCMG or SNASVCMG modes. The possible causes of this problem are:
Function Degradation: The received message is ignored and the transaction program process terminates. The local node will continue to process management service messages from other nodes. Unexpected results will probably follow this problem, since the node that sent the request is out of sync with the local node and is probably in error.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: None.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Description: None.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Description: The cp_cap_son session services transaction program was started but could not attach to the APPN communications system. This should not occur since the transaction program cannot run without the APPN communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: The cp_cap_son session services transaction program was started but could not attach to the APPC communications system. This should not occur since the transaction program cannot run without the APPC communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The cp_cap_son transaction program could not receive (accept) a conversation from an adjacent node.
The cp_cap_son session services transaction program could not receive a CP capabilities message from an adjacent node. The APPC RECEIVE_ALLOCATE verb failed for the cp_cap_son TP in the local node (over the CP-CP sessions). The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The received message is ignored. The local node will continue to try and set-up CP-CP sessions with other APPN nodes in the network. Unexpected results will probably follow this problem, since the node that sent the request is out of sync with the local node. The local node will not set up CP-CP sessions with the adjacent node.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session services cp_cap_son transaction program could not received CP capabilities data from an adjacent node.
The transaction program that receives CP capabilities on the con-loser session from adjacent nodes encountered an error while attempting to receive CP capabilities information from an adjacent node. The APPC RECEIVE_AND_WAIT verb for the CP capabilities message failed. The details of the error are indicated by the primary and secondary return codes and the what received indicator. The probable causes are:
Function Degradation: The conversation is de-allocated (type=ABEND_PROGRAM). The current CP capabilities message is purged and SS is notified of the failure. The local node continues to service CP capabilities messages received from other nodes. The local node will not set up CP-CP sessions with the adjacent node.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session services cp_cap_son transaction program received invalid or unexpected data.
The transaction program that receives CP capabilities messages from other nodes received invalid or unexpected data. The returned what received data indicator in the APPC RECEIVE_AND_WAIT verb is not an expected value. The probable causes are:
Function Degradation: The conversation from which the invalid data was received is de-allocated (type=ABEND_PROGRAM). The received CP capabilities message is ignored. The transaction program continues to process messages from other nodes. Unexpected results will probably follow this problem, since the node that sent the message is out of sync with the local node. The local node will not set up CP-CP sessions with the adjacent node.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session services cp_cap_son transaction program received invalid or unexpected data.
The transaction program that receives CP capabilities messages from other nodes received invalid or unexpected data. The size of the received data is not large enough to hold a CP capabilities message (GDS variable x'12C1'). The probable causes are:
Function Degradation: The conversation from which the invalid data was received is de-allocated (type=ABEND_PROGRAM). The received CP capabilities message is ignored. The transaction program continues to process messages from other nodes. Unexpected results will probably follow this problem, since the node that sent the message is out of sync with the local node. The local node will not set up CP-CP sessions with the adjacent node.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session services cp_cap_son transaction program received invalid or unexpected data.
The transaction program that receives CP capabilities messages from other nodes received invalid or unexpected data. The received message is not a CP capabilities message (GDS variable x'12C1'). The probable causes are:
Function Degradation: The conversation from which the invalid data was received is de-allocated (type=ABEND_PROGRAM). The received message is ignored. The transaction program continues to process CP capabilities messages from other nodes. Unexpected results will probably follow this problem, since the node that sent the message is out of sync with the local node. The local node will not set up CP-CP sessions with the adjacent node.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session services cp_cap_son transaction program rejected a CP capabilities message received from an adjacent node.
The transaction program that receives CP capabilities messages from other nodes received invalid or unexpected data or session services encountered an error processing the data. Session services rejected the received message with the indicated sense code. Probable causes are:
Function Degradation: The resulting action depends on the detected error. If the problem is a serious protocol problem, such as the mode name of the session the message was received from is invalid (08210002) or session services does not recognize the adjacent node (08060002), the session with the adjacent node is terminated. Otherwise, the conversation from which the invalid data was received is de-allocated (type=ABEND_PROGRAM). The transaction program continues to process CP capabilities messages from other nodes. Unexpected results will probably follow this problem, since the node that sent the message is out of sync with the local node. The local node will probably not be able to establish CP-CP sessions with the adjacent node.
Customer Action: Use the description of the logged sense code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a system failure or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with SS and data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: The request_cp_cap session services transaction program was started but could not attach to the APPN communications system. This should not occur since the transaction program cannot run without the APPN communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: The request_cp_cap session services transaction program was started but could not attach to the APPC communications system. This should not occur since the transaction program cannot run without the APPC communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The request_cp_cap transaction program could not register itself as an APPC transaction program.
The request_cp_cap session services transaction program can not attach to the APPC/APPN communications system. The APPC TP_STARTED verb failed.
The details of the error are indicated by the primary and secondary return codes. An internal code problem exists within pSNA.
Function Degradation: The transaction program process terminates. The local node will not be able to establish CP-CP sessions with its adjacent nodes.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The request_cp_cap TP could not allocate a conversation with an adjacent node.
The request_cp_cap session services transaction program could not send a CP capabilities message to an adjacent node. The APPC ALLOCATE verb failed for the cp_cap_son TP in an adjacent node. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The current CP capabilities message is ignored and the transaction program process terminates. The local node will not be able to establish CP-CP sessions with its adjacent nodes. The local node will continue to try and establish CP-CP sessions with other adjacent nodes.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The request_cp_cap TP could not send a CP capabilities message to an adjacent node.
The request_cp_cap session services transaction program could not send a CP capabilities message to an adjacent node. The APPC SEND_DATA verb for the message failed. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The conversation created to send the CP capabilities message is de-allocated (type=ABEND_PROGRAM). The current CP capabilities message is purged and the transaction program terminates. The local node continues to try and establish CP-CP sessions with other adjacent nodes. CP-CP sessions are not established with the adjacent node.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The request_cp_cap TP encountered an error while exchanging CP capabilities with an adjacent node.
The request_cp_cap session services transaction program could not obtain the characteristics of the established CP-CP session (such as the adjacent node name and conversation group ID). The APPC GET_ATTRIBUTES verb failed. The details of the error are indicated by the primary and secondary return codes. Probable causes are:
Function Degradation: The conversation created to send the CP capabilities message is de-allocated (type=ABEND_PROGRAM). The current CP capabilities message is purged and the transaction program terminates. The local node continues to try and establish CP-CP sessions with other adjacent nodes. CP-CP sessions are not established with the adjacent node.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages.
If possible, try and re-create the problem with SS and data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The session services request_cp_cap transaction program received invalid or unexpected data.
The transaction program that exchanges CP capabilities messages with other nodes received invalid or unexpected data. Either the what received data indicator from the APPC RECEIVE_AND_WAIT verb is not an expected value or the size of the received data is not large enough to hold a CP capabilities message (GDS variable x'12C1'). The probable causes are:
Function Degradation: The conversation from which the invalid data was received is de-allocated (type=ABEND_PROGRAM). The received CP capabilities message is ignored. The transaction program terminates. The local node continues to try and establish CP-CP sessions with other adjacent nodes. CP-CP sessions are not established with the adjacent node. Unexpected errors will probably follow this problem, since the node that sent the message is out of sync with the local node.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session services request_cp_cap transaction program received invalid or unexpected data.
The transaction program that exchanges CP capabilities messages with other nodes received invalid or unexpected data. The received message is not a CP capabilities message (GDS variable x'12C1'). The probable causes are:
Function Degradation: The conversation from which the invalid data was received is de-allocated (type=ABEND_PROGRAM). The received CP capabilities message is ignored. The transaction program terminates. The local node continues to try and establish CP-CP sessions with other adjacent nodes. CP-CP sessions are not established with the adjacent node. Unexpected errors will probably follow this problem, since the node that sent the message is out of sync with the local node.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: The process_output_tdu topology and route selection services transaction program was started but could not attach to the APPN communications system. This should not occur since the transaction program cannot run without the APPN communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: The process_output_tdu topology and route selection services transaction program was started but could not attach to the APPC communications system. This should not occur since the transaction program cannot run without the APPC communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The process_output_tdu transaction program could not register itself as an APPC transaction program.
The process_output_tdu topology and route selection services transaction program can not attach to the APPC/APPN communications system. The APPC TP_STARTED verb failed.
The details of the error are indicated by the primary and secondary return codes. An internal code problem exists within pSNA.
Function Degradation: The transaction program process terminates. APPC/APPN communication services will not function correctly because TRS will not be able to send any APPN network topology updates to the other network nodes in the APPN network.
Customer Action: call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The process_output_tdu TP could not send a topology update to an adjacent node.
The process_output_tdu topology and route selection services transaction program could not send a topology update to an adjacent node. The APPC SEND_DATA verb for the update failed. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The conversation created to send the topology update is de-allocated (type=ABEND_PROGRAM). The current topology update is purged, and the TP continues to service other updates received from TRS. Unexpected results will probably follow this problem, since the targeted node did not receive the topology update. The adjacent node's topology database may be incorrect.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: An error occurred while the process_output_tdu TP was sending a topology update to an adjacent node.
The process_output_tdu topology and route selection services transaction program could not send a topology update to an adjacent node. The APPC DEALLOCATE verb for the update failed. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The TP continues to send other topology updates, as well as sending the current update to all other adjacent network nodes. Unexpected results will probably follow this problem, since it is possible an adjacent node did not receive the topology update.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: The receive_tdu topology and route selection services transaction program was started but could not attach to the APPN communications system. This should not occur since the transaction program cannot run without the APPN communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: The receive_tdu topology and route selection services transaction program was started but could not attach to the APPC communications system. This should not occur since the transaction program cannot run without the APPC communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The receive_tdu transaction program could not receive (accept) a conversation from an adjacent node.
The receive_tdu topology and route selection services transaction program could not receive a topology update message from an adjacent node. The APPC RECEIVE_ALLOCATE verb failed for the receive_tdu TP in the local node (over the CP-CP sessions). The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The received message is ignored and the transaction program process terminates. The local node will continue to receive topology updates from other APPN network nodes in the network. Unexpected results will probably follow this problem, since the node that sent the request is out of sync with the local node.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The topology and route selection services receive_tdu transaction program could not receive a topology update message.
The receive_tdu topology and route selection services transaction program could not receive a topology update message from an adjacent node. The APPC RECEIVE_AND_WAIT verb for the message failed. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The conversation created to receive the message is de-allocated (type=ABEND_PROGRAM). The received message is ignored and the transaction program process terminates. The local node will continue to process topology updates from other nodes. Unexpected results will probably follow this problem, since the node that sent the request is out of sync with the local node, and the local node's topology database may be incorrect.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The topology and route selection services receive_tdu transaction program received invalid or unexpected data.
The transaction program that receives topology updates from other nodes received invalid or unexpected data. The what received data indicator from the APPC RECEIVE_AND_WAIT verb is not an expected value. The probable causes are:
Function Degradation: The conversation from which the invalid data was received is de-allocated (type=ABEND_PROGRAM). The received topology update is ignored. The transaction program continues to process requests from other nodes. Unexpected results will probably follow this problem, since the node that sent the update is out of sync with the local node, and the local node's topology database may be incorrect.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: The receive_signoff APPC persistent verification transaction program was started but could not attach to the APPN communications system. This should not occur since the transaction program cannot run without the APPN communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: The receive_signoff APPC persistent verification transaction program was started but could not attach to the APPC communications system. This should not occur since the transaction program cannot run without the APPC communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The receive_tdu transaction program could not receive (accept) a conversation from an adjacent node.
The receive_signoff APPC persistent verification transaction program could not receive a SIGNOFF message from an adjacent node. The APPC RECEIVE_ALLOCATE verb failed for the receive_signoff TP in the local node (over the SNASVCMG session). The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The received message is ignored and the transaction program process terminates. The local node will continue to receive SIGNOFF requests from other APPC nodes in the network. Unexpected results will probably follow this problem, since the node that sent the request is out of sync with the local node.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
The receive_signoff APPC persistent verification transaction program could not receive a SIGNOFF message from an adjacent node. The APPC RECEIVE_AND_WAIT verb for the message failed. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The conversation created to receive the message is de-allocated (type=ABEND_PROGRAM). The received message is ignored and the transaction program process terminates. The local node will continue to process SIGNOFF requests from other nodes. Unexpected results will probably follow this problem, since the security information within the remote node that sent the request is out of sync with the security information in the local node.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The APPC persistent verification receive_signoff transaction program received invalid or unexpected data.
The transaction program that receives SIGNOFF requests from other nodes received invalid or unexpected data. The what received data indicator from the APPC RECEIVE_AND_WAIT verb is not an expected value. The probable causes are:
Function Degradation: The conversation from which the invalid data was received is de-allocated (type=ABEND_PROGRAM). The received message is ignored and the transaction program process terminates. The local node will continue to process SIGNOFF requests from other nodes. Unexpected results will probably follow this problem, since the security information within the remote node that sent the request is out of sync with the security information in the local node.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The APPC persistent verification receive_signoff transaction program received invalid data.
The transaction program that processes SIGNOFF requests from other nodes received invalid data. It could not parse the received request. The probable causes are:
Function Degradation: The conversation from which the invalid data was received is de-allocated (type=ABEND_PROGRAM). The received request is ignored and the transaction program terminates. The local node continues to process SIGNOFF requests from other nodes. Unexpected results will probably follow this problem, since the security information within the remote node that sent the request is out of sync with the security information in the local node.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The receive_signoff APPC persistent verification transaction program could not confirm the successful processing of a SIGNOFF request received from an adjacent node. The APPC CONFIRMED verb failed. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The conversation that received the SIGNOFF request is de-allocated (type=ABEND_PROGRAM). The TP continues to receive SIGNOFF requests from other nodes in the network. Unexpected results will probably follow this problem, since the remote node is expecting a reply to the SIGNOFF request.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: The send_signoff APPC persistent verification transaction program was started but could not attach to the APPN communications system. This should not occur since the transaction program cannot run without the APPN communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. The local node will not be able to use the APPC persistent verification security options for its conversations.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: The send_signoff APPC persistent verification transaction program was started but could not attach to the APPC communications system. This should not occur since the transaction program cannot run without the APPC communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. The local node will not be able to use the APPC persistent verification security options for its conversations.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically when the node is started, and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The send_signoff transaction program could not register itself as an APPC transaction program.
The transaction program could not attach to the APPC/APPN communications system. The APPC TP_STARTED verb failed.
The details of the error are indicated by the primary and secondary return codes. An internal code problem exists within pSNA.
Function Degradation: The transaction program process terminates. The local node will not be able to use the APPC persistent verification security options for its conversations.
Customer Action: call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The send_signoff APPC persistent verification transaction program could not send a SIGNOFF request to another node in the network. The APPC ALLOCATE verb failed for the receive_signoff TP in another node in the network (using a SNASVCMG session). The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The TP continues to send SIGNOFF requests to other nodes in the network. Unexpected results will probably follow this problem, since the security information within the remote node that sent the request is out of sync with the security information in the local node.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The send_signoff APPC persistent verification transaction program could not send a SIGNOFF request to another node in the network. The APPC SEND_DATA verb for the request failed. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The conversation created to send the SIGNOFF request is de-allocated (type=ABEND_PROGRAM). The current request is purged, and the TP continues to send SIGNOFF requests to other nodes in the network. Unexpected results will probably follow this problem, since the security information within the remote node that sent the request is out of sync with the security information in the local node.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: A session is being deactivated by the local node. This typically occurs when the deact_conversation_group transaction program determined that an adjacent node is not servicing APPN requests sent over the CP-CP sessions. The local node was unable to send a message or receive a confirmation within 120 seconds. The possible causes of this problem are:
Function Degradation: The CP-CP sessions with the adjacent node are terminated. The local node is no longer able to exchange APPN control information with the adjacent node. The local node continues to exchange messages with all other nodes in the network.
Customer Action: More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: The node_address_server management services transaction program was started but could not attach to the APPN communications system. This should not occur since the transaction program cannot run without the APPN communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically and should not be explicitly started.
If the program was not started by an operator, call service with the code point, error description, and abend code value if possible. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: The node_address_server management services transaction program was started but could not attach to the APPC communications system. This should not occur since the transaction program cannot run without the APPC communications system. Possible causes are:
Function Degradation: The transaction program process terminates. If the node is running it will probably abend. No APPC/APPN communication services are available, or if available, will not function correctly.
Customer Action: Verify that an operator did not mistakenly start the transaction program. The transaction program is started automatically and should not be explicitly started.
If the program was not started by an operator, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The node_address_server transaction program could not receive (accept) a conversation from an adjacent node.
The node_address_server management services transaction program could not receive a node address request from an adjacent node. The APPC RECEIVE_ALLOCATE verb failed for the node_address_server TP in the local node. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The received message is ignored and the transaction program process terminates. The local node will continue to process node address requests from other nodes.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The management services node_address_server transaction program could not receive a node address request.
The node_address_server management services transaction program could not receive a node address request from an adjacent node. The APPC RECEIVE_AND_WAIT verb for the node address request failed. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The conversation created to receive the node address request is de-allocated (type=ABEND_PROGRAM). The received request is ignored and the transaction program terminates. The local node continues to process node address requests from other nodes.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The management services node_address_server transaction program issued a call to a TCP/IP function with unexpected results.
The node_address_server management services transaction program can not satisfy the node address request. The possible causes of this problem are:
Function Degradation: The received request is ignored and the transaction program terminates. The local node continues to process node address requests from other nodes.
Customer Action:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The management services node_address_server transaction program could not send a node address response to another node in the network. The APPC ALLOCATE verb failed for the node_address_requester TP in another node in the network. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The received request is ignored and the transaction program terminates. The local node continues to process node address requests from other nodes.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The node_address_server TP could not send a node address response to an adjacent node. The APPC SEND_DATA verb for the response failed. The details of the error are indicated by the primary and secondary return codes. The possible causes of this problem are:
Function Degradation: The conversation created to send the node address response is de-allocated (type=ABEND_PROGRAM). The received request is ignored and the transaction program terminates. The local node continues to process node address requests from other nodes.
Customer Action: Use the descriptions of the logged primary and secondary return code to determine the cause of the problem. More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Log events for the attach manager component of APPC (AM).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: A system (EGPE or OS) function failed while processing an incoming ATTACH or a RECEIVE_ALLOCATE from a transaction program.
The attach manager could not process an incoming request to create a conversation because a system function failed. The conversation failure occurred processing an incoming ATTACH message or a RECEIVE_ALLOCATE from a local transaction program. The list of failures includes:
Function Degradation: If the error occurred processing a RECEIVE_ALLOCATE, the verb completes with an error. If the error occurred processing an incoming ATTACH, the ATTACH is rejected with the sense code 084C0000 or 084B6031.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A program was started by the attach manager but ended before issuing a RECEIVE_ALLOCATE for the ATTACH that initiated the program.
The attach manager started a program because of it received an ATTACH for a transaction program that references the program. The started program ended before issuing a RECEIVE_ALLOCATE for the incoming attach.
Function Degradation: The attach manager may try to reload the program (depending on the type of transaction program). If no reload is attempted, or if the reload failed, the ATTACH, and all other ATTACHs that refer to the program, are rejected.
Customer Action: It is possible that the node will continue to work correctly if this problem occurs. If it appears to be behaving satisfactorily, no immediate action is required. To use the indicated transaction program, determine why the started program ended before processing the received ATTACH. Fix the problem and re-try starting the conversation.
System Developer Action: None.
Additional Data: Has the following format:
Description: The attach manager rejected a request to start a conversation (SNA ATTACH).
The attach manager rejected an incoming ATTACH from a partner node. Some of the reasons that the ATTACH is rejected, along with their associated sub-type, are:
Function Degradation: The ATTACH is rejected. with the sense code 084C0000 or 084B6031.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The attach manager (AM) received an API verb it does not recognize (or process).
The attach manager received an API verb from the API interface that it does not recognize or process. This condition should not occur, since the unrecognized verb should not have been routed to AM for processing. An internal code problem exists within pSNA.
Function Degradation: The unrecognized verb is ignored, and AM continues to process other API verbs. Unexpected results will probably follow this problem, since AM or the API interface layer are probably in error and out of sequence. In addition, the transaction program that issued the verb will probably hang because the verb is ignored.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The attach manager (AM) received an internal inter-process signal it does not recognize (or process).
The attach manager received an IPS that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to AM for processing. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and AM continues to process other signals. Unexpected results will probably follow this problem, since AM or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The attach manager could not process an incoming request to create a conversation (ATTACH). A system function (Pcreate) failed while trying to start the specified transaction program. The probable causes are:
Function Degradation: The received conversation (ATTACH) is rejected with the sense code 084C0000 or 084B6031.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The Attach Manager (AM) encountered a problem trying to start the SIGNOFF service transaction program. The request to start the service transaction program (Pcreate) failed. The probable causes are:
Function Degradation: AM continues processing. Unexpected results will probably follow this problem, since a SIGNOFF flow could not be sent to a partner LU.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as additional log entries or messages).
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Log events for the half-session component of APPC (HS).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: An SNA protocol error was detected while half-session (data flow control) was processing a message.
Half-session detected an SNA protocol error while processing a message. The message did not pass one or more of the SNA protocol checks (send or receive checks). The sense code identifies the actual SNA protocol error. The probable causes are:
Function Degradation: The local node ends the session associated with the conversation by sending an UNBIND.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: A half-session (HS) received an internal inter-process signal it does not recognize (or process).
A half-session for an LU received an IPS that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to HS for processing. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and HS continues to process other signals. Unexpected results will probably follow this problem, since HS or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: A half-session cannot parse the SNA request header in an SNA message
A half-session for an LU could not compute an internal hash value from the SNA request header contained in an SNA message. This should not occur, since HS should be able to compute hash values from all valid request headers (RH) that it processes. The SNA message can either be an outbound message being sent by the local node or an inbound message received from a remote node. The probable causes are:
Function Degradation: Half-session continues to process the message. Unexpected results will probably follow this problem, since HS cannot correctly parse the request header in the message. In addition, if the message was received from a remote node, the communications support in the sending node and the local node are either in error or incompatible.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with HS and data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: A half-session encountered an internal error. The half-session could not reset (turn off) compression for the session when a conversation was deallocated by the remote node.
This should not occur. A programming error/deficiency exists within the pSNA
Function Degradation: Half-session continues to process messages. Unexpected results will probably follow this problem, since HS could not reset the compression algorithms being used for a session. Subsequent conversations using the session will probably fail.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: A half-session encountered an internal error. The half-session could not reset (turn off) compression for the session when a conversation was deallocated by the local node.
This should not occur. A programming error/deficiency exists within the pSNA
Function Degradation: The local node ends the session associated with the conversation by sending an UNBIND type='FE' (session protocol error), with the sense code 20130000.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: A half-session encountered a should-not-occur condition. A programming error/deficiency exists within the pSNA The half-session indicated that compression was being performed for the data being exchanged on a session, but the compression component did not contain any compression data for the session.
Function Degradation: Half-session continues to process messages, without performing any compression. Unexpected results will probably follow this problem, since the local node contains conflicting compression information for the session. Data may not be correctly compressed or decompressed.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: A half-session cannot process a received SNA message. The compression protocols and algorithms used by the session encountered a should-not-occur condition. The probable causes are:
Function Degradation: The local node ends the session associated with the conversation by sending an UNBIND type='FE' (session protocol error), with the sense code 20130000.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with HS and data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: A half-session cannot process a received SNA message. The compression protocols and algorithms used by the session encountered a should-not-occur condition. A compression request was received when the local node was expecting a request to reset the decompression algorithm. The probable causes are:
Function Degradation: The local node ends the session associated with the conversation by sending an UNBIND type='FE' (session protocol error), with the sense code 20130001.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with HS and data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: A half-session cannot process a received SNA message. The compression protocols and algorithms used by the session encountered a should-not-occur condition. A compression request was received containing an invalid compression control sequence. The probable causes are:
Function Degradation: The local node ends the session associated with the conversation by sending an UNBIND type='FE' (session protocol error), with the sense code 20130002.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with HS and data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: A half-session cannot process a received SNA message. The compression protocols and algorithms used by the session encountered a should-not-occur condition. The length of a decompressed message does not the expected length specified in the compression information contained in the message. The probable causes are:
Function Degradation: The local node ends the session associated with the conversation by sending an UNBIND type='FE' (session protocol error), with the sense code 20130003.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with HS and data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: A half-session cannot process a received SNA message. The compression protocols and algorithms used by the session encountered a should-not-occur condition. The compression algorithm specified in the received message does not match the algorithm agreed upon when the session was established. The probable causes are:
Function Degradation: The local node ends the session associated with the conversation by sending an UNBIND type='FE' (session protocol error), with the sense code 20130004.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with HS and data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: A half-session cannot process a received SNA message. The compression protocols and algorithms used by the session encountered a should-not-occur condition. The length of a decompressed message exceeds the maximum RU size allowed for the session. The probable causes are:
Function Degradation: The local node ends the session associated with the conversation by sending an UNBIND type='FE' (session protocol error), with the sense code 20130005.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with HS and data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: A half-session encountered a should-not-occur condition. A programming error/deficiency exists within the pSNA
The half-session received a return code from the compression component it does not recognize.
Function Degradation: The local node ends the session associated with the conversation by sending an UNBIND type='FE' (session protocol error), with the sense code 20130000.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: An SNA protocol error was detected while half-session (transmission control) was processing a message. Half-session detected an SNA protocol error while processing a message. The sequence number in the received message did not match the expected next sequence number. The probable causes are:
Function Degradation: The local node ends the session associated with the conversation by sending an UNBIND type='FE' (session protocol error), with the sense code 20010000.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: A half-session cannot process a received SNA message. A half-session received a message indicating that the message should be compressed or decompressed, but the associated session is not using compression. The probable causes are:
Function Degradation: The local node ends the session associated with the conversation by sending an UNBIND type='FE' (session protocol error), with the sense code 40220000.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with HS and data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: When the IPS from SM is received there is no corresponding half session available. The half session valus is NULL.
Half session is not avilable for the ips from SM.
Function Degradation: Last Ptraces and the SM IPS is logged for the future Diagnostics.
Customer Action: Call service with the code point and error description. In addition:
Additional Data: Has the following format:
Description: When the IPS from SM is received there is valid half session in existence. However the field Ptrace is corrupted.
Half session Ptrace table field is corrupted.
Function Degradation: Last Ptraces and the SM IPS and the half session is logged for the future Diagnostics.
Customer Action: Call service with the code point and error description. In addition:
Log events for the configuration verification and load utility of pSNA (PSNAV).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: The PSNA configuration verification utility detected a recoverable error condition while processing the configuration file. The log record contains a message describing the error, as well as the resulting system action and any recommended user responses.
Note: The descriptive text of the log record also contains the message number of the logged message.
Function Degradation: The utility continues to process the configuration file.
See the description of the logged message for a more detailed description of the procedures used to recover from the detected error.
Customer Action: The resulting configuration may be usable, but may contain differences from the original configuration file, depending on the detected error. See the description of the logged message for a description of the error and the resulting recovery actions. In many cases, the resulting configuration can be used and no action is required. The description of the message will provide any recommended user responses.
System Developer Action: See the description of the logged message.
Additional Data: Has the following format:
Description: The PSNA configuration verification utility detected an error condition while processing the configuration file. The log record contains a message describing the error, as well as the resulting system action and any recommended user responses. In most cases, the error is related to a configuration problem, but refer to the description of the message for a detailed description of the problem.
Note: The descriptive text of the log record also contains the message number of the logged message.
Function Degradation: The utility continues to check the configuration file for any syntax or configuration errors. The configuration is not successfully loaded into the local node (depending on the error, the configuration may have been partially loaded when the error was detected).
See the description of the logged message for a more detailed description of the actions taken by the local node when the error was detected.
Customer Action: The resulting configuration is not usable. Stop the local node and fix the error. See the description of the logged message for a description of the error and the recommended user responses. Fix the error using the recommended responses and re-start the local node.
System Developer Action: See the description of the logged message.
Additional Data: Has the following format:
Description: The PSNA configuration verification utility detected a severe error condition while processing the configuration file. The log record contains a message describing the error, as well as the resulting system action and any recommended user responses. In most cases, the error is related to a system error, such as an underlying system function failed or a memory problem, but refer to the description of the message for a detailed description of the problem.
Note: The descriptive text of the log record also contains the message number of the logged message.
Function Degradation: The utility end immediately (in most severe error cases). The configuration is not successfully loaded into the local node (depending on the error, the configuration may have been partially loaded when the error was detected).
See the description of the logged message for a more detailed description of the actions taken by the local node when the error was detected.
Customer Action: The resulting configuration is not usable. Stop the local node and fix the error. See the description of the logged message for a description of the error and the recommended user responses. Fix the error using the recommended responses and re-start the local node.
System Developer Action: See the description of the logged message.
Additional Data: Has the following format:
Description: The PSNA configuration verification utility detected an error condition while processing the configuration file. The log record contains a message describing the error, as well as the resulting system action and any recommended user responses. In most cases, an error while trying to define or start the resources contained in the configuration file. Refer to the description of the message for a detailed description of the problem.
Note: The descriptive text of the log record also contains the message number of the logged message.
Function Degradation: The utility continues to try and define and start the other resources in the configuration. Not all resources in the configuration are defined or started.
See the description of the logged message for a more detailed description of the actions taken by the local node when the error was detected.
This log record is created in conjunction with the log record 2F119000-00000005, which contains additional information.
Customer Action: The resulting configuration may be partially usable, but some of the resources contained in the configuration are not available. Depending on the error, you may be able to fix the resources in error without stopping the local node. In most cases you will probably have to stop the node, fix the problem, and re-start the node to recover. See the description of the logged message for a description of the error and the recommended user responses. Fix the error using the recommended responses and re-start the local node.
System Developer Action: See the description of the logged message.
Additional Data: Has the following format:
Description: This log record is created in conjunction with the log record 2F119000-00000004. This log record is used to log additional information associated with the problem identified by the other log record. Refer to the description of 2F104000-00000004 for more information.
Function Degradation: Refer to the description of the associated log record.
Customer Action: Refer to the description of the associated log record.
System Developer Action: Refer to the description of the associated log record.
Log events for the presentation services component of APPC (PS).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: An SNA protocol error was detected while receiving data over a basic conversation.
Presentation services detected an SNA protocol error while processing a message received from a conversation partner. The received message did not pass one or more of the SNA receive checks. The sense code identifies the actual SNA protocol error. The probable causes are:
This condition should not occur. A software problem exists in the node that sent the message, or the APPC/APPN support in the remote node is not compatible (which should never happen) with the pSNA APPC/APPN support.
Function Degradation: The local node ends the session associated with the conversation by sending an UNBIND, type='FE' (session protocol error).
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The local node either received an FMH-7 (error data) or sent an FMH-7 to a conversation partner.
Presentation services either received an FMH-7 (error data) from a conversation partner or sent an FMH-7 to a conversation partner. The sense code indicates the error condition that triggered the FMH-7. Some reasons why the local node would send an FMH-7:
Function Degradation: Depends on why the FMH-7 was generated. In most cases, the error condition that was detected will cause the detecting node (either node) to end the conversation. If the conversation is not ended, the sending transaction program initiates error recovery procedures by purging all unprocessed data. The conversation partners try and recover, possibly resending data, correcting the error condition that caused the problem.
Customer Action: It is possible that the node will continue to work correctly if this problem occurs. If it appears to be behaving satisfactorily (a subsequent retry of the operation was successful or the transaction programs successfully recovered), no immediate action is required. To resolve the problem, try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: An SNA protocol error was detected while receiving data over a mapped conversation.
Presentation services detected an SNA protocol error while processing a message received from a conversation partner. The received message did not pass one or more of the SNA receive checks. identifies the actual SNA protocol error. The probable causes are:
Function Degradation: The local node ends the conversation associated with the conversation by issuing DEALLOCATE TYPE=ABEND_SVC.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: An SNA protocol error was detected while receiving data over a mapped conversation.
A conversation detected an SNA protocol error while while processing a message received from a conversation partner. An unexpected error data GDS variable was received (a preceding FMH-7 was not received). The probable causes are:
Function Degradation: The local node ends the conversation associated with the conversation by issuing DEALLOCATE TYPE=ABEND_SVC.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: Presentation services (PS) received an internal inter-process signal it does not recognize (or process) in the current state.
Presentation services for an LU received an IPS that it does not recognize or process in the current state. This could indicate either:
Function Degradation: The unrecognized IPS is ignored, and PS continues to process other signals.
Customer Action: None.
System Developer Action: If symptoms indicate a should not occur situation, debug and determine what caused the failure to occur. Isolate and implement a code fix.
Log events for the resource manager component of APPC (RM).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: The resource manager detected an error in the conversation security parameters contained in a received ATTACH.
The resource manager detected an SNA protocol error while processing the security information contained in a received ATTACH. The sense code identifies the actual SNA protocol error (10086040 or 080F6051). The probable causes are:
This condition should not occur. A software problem exists in the node that sent the message, or the APPC/APPN support in the remote node is not compatible (which should never happen) with the pSNA APPC/APPN support.
Function Degradation: The resource manager ends the session associated with the conversation by sending an UNBIND type='FE' (session protocol error), with the indicated sense code.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: A received message violated SNA bracket rules.
The resource manager detected that a received message violates the bracket protocol rules for a session. The sense code identifies the actual protocol error (20030000). The remote node sent an ATTACH on an session that already has an active conversation, or sent a BID over a session that it is the first speaker of. The probable causes are:
This condition should not occur. A software problem exists in the node that sent the message, or the APPC/APPN support in the remote node is not compatible (which should never happen) with the pSNA APPC/APPN support.
Function Degradation: The resource manager ends the session by sending an UNBIND type='FE' (session protocol error), with the indicated sense code.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: A received message violated SNA bracket rules.
The resource manager detected that a received message violates the bracket protocol rules for a session. The sense code identifies the actual protocol error (20080000). The resource manager received a BID request after receiving a BIS from a session partner. The probable causes are:
This condition should not occur. A software problem exists in the node that sent the message, or the APPC/APPN support in the remote node is not compatible (which should never happen) with the pSNA APPC/APPN support.
Function Degradation: The resource manager ends the session by sending an UNBIND type='FE' (session protocol error), with the indicated sense code.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: A received message violated SNA bracket rules.
The resource manager detected that a received message violates the bracket protocol rules for a session. The sense code identifies the actual protocol error (20030000). The resource manager received an unexpected RTR request from a session partner (i.e. an RTR was sent over a session where the previous BID was not rejected). The probable causes are:
This condition should not occur. A software problem exists in the node that sent the message, or the APPC/APPN support in the remote node is not compatible (which should never happen) with the pSNA APPC/APPN support.
Function Degradation: The resource manager ends the session by sending an UNBIND type='FE' (session protocol error), with the indicated sense code.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: A received message violated SNA bracket rules.
The resource manager detected that a received message violates the bracket protocol rules for a session. The sense code identifies the actual protocol error (20100000). The resource manager received an unexpected BIS response from a session partner (i.e. a BIS response was received but a BIS request was not pending). The probable causes are:
Function Degradation: The resource manager ends the session by sending an UNBIND type='FE' (session protocol error), with the indicated sense code.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: A received message violated SNA bracket rules.
The resource manager detected that a received message violates the bracket protocol rules for a session. The sense code identifies the actual protocol error (20100000). The resource manager received an unexpected BIS request from a session partner (i.e. a BIS request was received after another BIS request was received). The probable causes are:
This condition should not occur. A software problem exists in the node that sent the message, or the APPC/APPN support in the remote node is not compatible (which should never happen) with the pSNA APPC/APPN support.
Function Degradation: The resource manager ends the session by sending an UNBIND type='FE' (session protocol error), with the indicated sense code.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: A system error occurred while processing a received ATTACH or enough resources (memory, buffers) could not be allocated to process the ATTACH.
The attach manager could not process an incoming request to create a conversation because a system function failed or enough resources could not be allocated. The conversation failure occurred processing an incoming ATTACH message.
Function Degradation: The ATTACH is rejected with the sense code 20030000.
Customer Action: It is possible that the node will continue to work correctly if this problem occurs. If it appears to be behaving satisfactorily (a subsequent retry of the operation was successful), no immediate action is required. To resolve the problem, try and determine the cause of the problem and then re-try starting the conversation:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The resource manager detected an error in the session security parameters contained in a received FMH-12.
The resource manager detected an SNA protocol error while processing the security information contained in a received FMH-12. The sense code identifies the actual SNA protocol error (080F6051). The probable causes are:
This condition should not occur. A software problem exists in the node that sent the message, or the APPC/APPN support in the remote node is not compatible (which should never happen) with the pSNA APPC/APPN support.
Function Degradation: The resource manager ends the session by sending an UNBIND type='FE' (session protocol error), with the indicated sense code.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The resource manager (RM) received an internal inter-process signal it does not recognize (or process).
The resource manager for an LU received an IPS from a process queue that it does not recognize or process. This condition should not occur. An internal code problem exists within pSNA.
Function Degradation: The received IPS is ignored, and RM continues to process other signals. Unexpected results will probably follow this problem, since RM or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The resource manager (RM) received an internal inter-process signal it does not recognize (or process).
The resource manager for an LU received an IPS from NOF that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to RM for processing. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and RM continues to process other signals. Unexpected results will probably follow this problem, since RM or NOF are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The resource manager (RM) received an internal inter-process signal it does not recognize (or process).
The resource manager for an LU received an IPS from a half-session that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to RM for processing. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and RM continues to process other signals. Unexpected results will probably follow this problem, since RM or HS are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The resource manager (RM) received an internal inter-process signal it does not recognize (or process).
The resource manager for an LU received an IPS from the session manager that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to RM for processing. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and RM continues to process other signals. Unexpected results will probably follow this problem, since RM or SM are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The resource manager (RM) received an internal inter-process signal it does not recognize (or process).
The resource manager for an LU received an IPS from the environment manager (EGPE) that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to RM for processing. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and RM continues to process other signals. Unexpected results will probably follow this problem, since RM or EGPE are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: The resource manager encountered an error while trying to create a presentation services instance (a APPC transaction program instance).
The resource manager for an LU could not create the presentation services instance required for a new APPC transaction program instance. The possible causes of this problem are:
Function Degradation: The request to start a new APPC transaction program failed. If the transaction program was started because the local node received a request for a new conversation from a remote node (an SNA ATTACH message), the received ATTACH is rejected. If the transaction program was initiated by the local node (a program issued an API request for a new APPC transaction program), the API request completes with an error.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The resource manager encountered a software problem (should-not-occur condition) while processing an SNA BIS request.
The resource manager does not recognize the current state of the FSM_BIS FSM. The FSM should be robust enough to handle any valid input in any valid sequence, as well as any produced action values. This FSM controls the processing of BIS requests and responses for a session. The probable causes are:
Function Degradation: The received BIS request is ignored, and RM continues to process other signals and SNA messages. Unexpected results will probably follow this problem, since RM or another node component are probably in error and out of sequence.
Communications will probably be affected since the received message is ignored (the related session will probably hang or unexpectedly terminate) In addition, the communications support in an adjacent node and the local node may be incompatible, causing other communications errors.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to output an invalid state. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with RM and data traces enabled and supply that trace information with the problem.
Additional Data: Has the following format:
Description: The resource manager rejected a remote request to start a new conversation (an SNA ATTACH message) because the received message contained invalid security data.
The resource manager for an LU rejected an ATTACH request because it does not recognize one or more of the security sub-fields contained in the request. The probable causes are:
Function Degradation: The resource manager rejects the received ATTACH request.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. The remote node is probably in error since the received message is invalid.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The resource manager rejected a remote request to start a new conversation (an SNA ATTACH message) because the received message contained invalid security data.
The resource manager for an LU rejected an ATTACH request because it contained multiple access security profiles. The probable causes are:
Function Degradation: The resource manager rejects the received ATTACH request.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. The remote node is probably in error since the received message is invalid.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The resource manager rejected a remote request to start a new conversation (an SNA ATTACH message) because the received message contained invalid security data.
The resource manager for an LU rejected an ATTACH request because it contained multiple access security passwords. The probable causes are:
Function Degradation: The resource manager rejects the received ATTACH request.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. The remote node is probably in error since the received message is invalid.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The resource manager rejected a remote request to start a new conversation (an SNA ATTACH message) because the received message contained invalid security data.
The resource manager for an LU rejected an ATTACH request because it contained multiple access security user IDs. The probable causes are:
Function Degradation: The resource manager rejects the received ATTACH request.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. The remote node is probably in error since the received message is invalid.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The resource manager rejected a remote request to start a new conversation (an SNA ATTACH message) because the received message contained invalid security data.
The resource manager for an LU rejected an ATTACH request because it contained inconsistent access security information. The security information specified a user ID, but did not specify the related password. The probable causes are:
Function Degradation: The resource manager rejects the received ATTACH request.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. The remote node is probably in error since the received message is invalid.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: A session deactivated by the resource manager was still in use (i.e. the session was still being used by a conversation). while processing a notification that a session is being ended (a session outage notification).
The resource manager determined that a conversation was still active on a session being deactivated. The resource manager detected the conversation while processing a notification that a session is being ended (a session outage notification). The session is probably being deactivated because of a communications error, an operator request, or an abnormal session termination request from the remote node (UNBIND).
This condition is not an error condition. The event is logged so that problem determination personnel can determine why the conversation and its session were deactivated.
Function Degradation: The local node de-allocates the active conversation and continues processing the session deactivation request. It may, depending on why the session is being stopped, also terminate the active session by sending an UNBIND request to the remote node.
This particular event is not logged because of an error condition within the local node. This does not mean that the session deactivation itself is not the result of an error condition. If the session was unexpectedly terminated, another log record is created to reflect the error condition. This event is logged to help problem determination personnel determine why a conversation was ended.
Customer Action: Try and determine why the session was stopped by investigating any related log entries or messages. If the outage was unexpected, re-start the session and try and re-start the lost conversation. The local node will automatically re-start the session if an APPC transaction program in the local node attempts to recover the conversation and the session outage is recoverable.
System Developer Action: None.
Additional Data: Has the following format:
Description: The resource manager encountered a should-not-occur situation while processing a notification that a session is being ended (a session outage notification).
The resource manager was deactivating a session when it encountered a should-not-occur condition. The resource manager does not recognize the reason code contained in the internal session deactivated signal. An internal code problem exists within pSNA.
Function Degradation: The resource manager continues to process the session deactivation notification. Unexpected results may follow this problem, since RM or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The resource manager encountered a should-not-occur situation while processing a request for a new conversation (an ALLOCATE API verb or internal ALLOCATE request).
The resource manager was starting a new conversation when it encountered a should-not-occur condition. The resource manager does not recognize the return control indicator in the ALLOCATE request. The return control indicator specifies the desired action when there isn't a session available for the new conversation. This condition should not occur since the other components should always set correct values and the API interface should verify this value before forwarding the API verb to presentation services. An internal code problem exists within pSNA.
Function Degradation: The resource manager continues to process the ALLOCATE request. Unexpected results may follow this problem, since RM or another node component are probably in error and out of sequence. Communication problems may also occur (such as hung conversations) because RM cannot determine the appropriate action to take when a session is not immediately available for the new conversation.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The resource manager detected an error in the sync-point parameters contained in a received ATTACH. The resource manager detected an SNA protocol error while processing the sync-point information contained in a received ATTACH (request for a new conversation).
The probable causes are:
Function Degradation: The resource manager ends the session associated with the conversation by sending an UNBIND type='FE' (session protocol error), with the sense code 10086041.
Customer Action: Try and determine if the problem was caused by a network definition error or a software error.
Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The resource manager rejected a remote request to start a new conversation (an SNA ATTACH message) because the received message contained invalid security data.
The resource manager for an LU rejected an ATTACH request because it specified a password but did not specify a userid. The probable causes are:
Function Degradation: The resource manager rejects the received ATTACH request with sense code 080F6051.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. The remote node is probably in error since the received message is invalid.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The resource manager detected an error in the conversation security parameters contained in a received ATTACH. The resource manager detected an SNA protocol error while processing the security information contained in a received ATTACH. The received ATTACH indicated that the security information is already verified (or the sending TP is already signed on); but the ATTACH did not contain a userid or also specified a password.
The probable causes are:
This condition should not occur. A software problem exists in the node that sent the message, or the APPC/APPN support in the remote node is not compatible (which should never happen) with the pSNA APPC/APPN support.
Function Degradation: The resource manager ends the session associated with the conversation by sending an UNBIND type='FE' (session protocol error), with the sense code 080F6051.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The resource manager detected an error in the conversation security parameters contained in a received ATTACH. The resource manager detected an SNA protocol error while processing the security information contained in a received ATTACH. The received ATTACH indicated it was a sign-on request, but it did not contain a userid.
The probable causes are:
This condition should not occur. A software problem exists in the node that sent the message, or the APPC/APPN support in the remote node is not compatible (which should never happen) with the pSNA APPC/APPN support.
Function Degradation: The resource manager ends the session associated with the conversation by sending an UNBIND type='FE' (session protocol error), with the sense code 080F6051.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The resource manager detected an error in the conversation security parameters contained in a received ATTACH. The resource manager detected an SNA protocol error while processing the security information contained in a received ATTACH. The received ATTACH indicated it was a sign-on request and the security information was not already verified, but it did not contain a password.
The probable causes are:
This condition should not occur. A software problem exists in the node that sent the message, or the APPC/APPN support in the remote node is not compatible (which should never happen) with the pSNA APPC/APPN support.
Function Degradation: The resource manager ends the session associated with the conversation by sending an UNBIND type='FE' (session protocol error), with the sense code 080F6051.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: A session is being deactivated by the local node. This typically occurs when the deact_conversation_group transaction program determined that an adjacent node is not servicing APPN requests sent over the CP-CP sessions. The local node was unable to send a message or receive a confirmation within 120 seconds. The possible causes of this problem are:
Function Degradation: The CP-CP sessions with the adjacent node are terminated. The local node is no longer able to exchange APPN control information with the adjacent node. The local node continues to exchange messages with all other nodes in the network.
Customer Action: More detailed information may also be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Log events for the session manager component of APPC (SM).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: The session manager rejected an incoming BIND because it contained invalid data, or the BIND was not expected.
The session manager rejected a BIND received from a partner LU. The BIND contained invalid information or was not expected (for example, a BIND was received for an existing session). The sense code identifies the actual error. The probable causes are:
Function Degradation: The session manager rejects the BIND by sending a negative response to the BIND or an UNBIND (depending on the state of the session when the BIND request was received).
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session manager detected a syntax error in a received UNBIND request.
The session manager detected a syntax error in an UNBIND request received from a partner LU. The UNBIND contained invalid information (violates SNA protocols). The sense code identifies the actual error. The probable causes are:
Function Degradation: The session manager continues to process the received UNBIND by terminating the targeted session.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session manager received an UNBIND request from a partner LU that indicates the partner LU detected a problem with the session.
The session manager received an UNBIND from a partner LU with the type indicating that this is not a normal session termination request (for example, the type could be session protocol error x'FE'). The sense code identifies the reason the partner LU deactivated the session. The probable causes are:
Function Degradation: The session manager continues to process the received UNBIND by terminating the targeted session.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: None. (dependent LU)
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Description: Not used yet (dependent LU)
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: The session manager rejected an incoming BIND because it contained encrypted data, although the pSNA support does not support session-level encryption.
The session manager rejected a BIND received from a partner LU. The BIND contained encrypted data which is not supported by pSNA. The pSNA APPC support does not support session-level encryption. The probable causes are:
Function Degradation: The session manager rejects the BIND by sending a negative response to the BIND or an UNBIND (depending on the state of the session when the BIND request was received).
Customer Action: Try and determine if the problem was caused by a network definition error or a software error. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session manager rejected an incoming BIND because it contained invalid security data.
The session manager rejected a BIND received from a partner LU. The BIND contained conversation security information that is inconsistent with the security information for other sessions between the same local LU, partner LU, and mode. The probable causes are:
Function Degradation: The session manager rejects the BIND by sending a negative response to the BIND or an UNBIND (depending on the state of the session when the BIND request was received).
Customer Action: Try and determine if the problem was caused by a network definition error or a software error. Refer to related log entries and messages for more information and other recommended actions.
Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session manager rejected an incoming BIND because it contained invalid security data.
The session manager rejected a BIND received from a partner LU. The BIND contained security information (the already verified indicator) that is inconsistent with the security information for other sessions between the same local LU, partner LU, and mode. The probable causes are:
Function Degradation: The session manager rejects the BIND by sending a negative response to the BIND or an UNBIND (depending on the state of the session when the BIND request was received).
Customer Action: Try and determine if the problem was caused by a network definition error or a software error. Refer to related log entries and messages for more information and other recommended actions.
Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session manager rejected an incoming BIND because it contained invalid security data.
The session manager rejected a BIND received from a partner LU. The BIND contained inconsistent security information. The BIND indicated that conversation level security is not supported, but the already verified indicator was set (security was already verified by the partner LU). The probable causes are:
Function Degradation: The session manager rejects the BIND by sending a negative response to the BIND or an UNBIND (depending on the state of the session when the BIND request was received).
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session manager ended a session because the received BIND response contained invalid security data.
The session manager ended a session because the received BIND response contains security information inconsistent with the session. The conversation level security indicators in the BIND response do not match the security information for the session (which were contained in the BIND request). For example, the BIND response indicates that security is supported, but the session (and the BIND request used to initiate the session) indicated that security is not supported. The probable causes are:
Function Degradation: The session manager ends the session by sending UNBIND.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session manager ended a session because the received BIND response contained invalid security data.
The session manager ended a session because the received BIND response contains security information inconsistent with the session. The already verified indicators in the BIND response do not match the security information for the session (which were contained in the BIND request). For example, the BIND response indicates that already verified security is supported, but the session (and the BIND request used to initiate the session) indicated that already verified is not supported. The probable causes are:
Function Degradation: The session manager ends the session by sending UNBIND.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session manager ended a session because the received BIND response contained invalid security data.
The session manager ended a session because the received response contained inconsistent security information. The BIND response indicated that conversation level security is not supported, but the already verified indicator was set (security was already verified by the partner LU). The probable causes are:
Function Degradation: The session manager ends the session by sending UNBIND.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session manager ended a session because the received BIND response contained invalid encryption data.
The session manager ended a session because the received BIND response contains encryption information inconsistent with the session. The random data fields in the BIND response are inconsistent with the encryption support specified for the session (which were contained in the BIND request). For example, the BIND response contains random data, but the session (and the BIND request used to initiate the session) indicated that encryption is not supported. The probable causes are:
Function Degradation: The session manager ends the session by sending UNBIND.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session manager ended a session because the received BIND response contained invalid encryption data.
The session manager ended a session because the received BIND response contains encryption information inconsistent with the session. The enciphered data fields in the BIND response are inconsistent with the encryption support specified for the session (which were contained in the BIND request). For example, the BIND response contains enciphered data, but the session (and the BIND request used to initiate the session) indicated that encryption is not supported. The probable causes are:
Function Degradation: The session manager ends the session by sending UNBIND.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session manager ended a session because the received BIND response contained invalid encryption data.
The session manager ended a session because the received BIND response did not pass the session-level security checks. The enciphered data in the BIND response did not match the expected enciphered data. The probable causes are:
Function Degradation: The session manager ends the session by sending UNBIND.
Customer Action: Try and determine if the problem was caused by a network definition error or a software error. Refer to related log entries and messages for more information and other recommended actions.
Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session manager could not correlate a BIND request with its appropriate session control block. This is an error because the BIND is being used to set up an intra-LU session (a session where the local and partner LUs are the same LU). The probable causes are:
Function Degradation: The session manager rejects the BIND by sending a negative response to the BIND or an UNBIND (depending on the state of the session when the BIND request was received).
Customer Action: Try and determine if the problem was caused by a network definition error or a software error. Refer to related log entries and messages for more information and other recommended actions.
Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session manager ended a session because the received BIND response contained invalid security data.
The session manager rejected a BIND request because the level of session-level security in the BIND does not match the value specified by the associated partner LU definition. For example, the partner LU definition indicates that session level security is not supported with the partner LU but the received request contains session level security information. This error is also flagged if the security information in the BIND request is not valid for pSNA (pSNA expects the random data length to be 8 bytes). The probable causes are:
Function Degradation: The session manager rejects the BIND by sending a negative response to the BIND or an UNBIND (depending on the state of the session when the BIND request was received).
Customer Action: Try and determine if the problem was caused by a network definition error or a software error. Refer to related log entries and messages for more information and other recommended actions.
Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session manager rejected an incoming BIND because it contained invalid random data.
The session manager rejected a BIND received from a partner LU. The BIND contained random data that matches random data already pending for a session between the two LUs. The probable causes are:
Function Degradation: The session manager rejects the BIND by sending a negative response to the BIND or an UNBIND (depending on the state of the session when the BIND request was received).
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session manager rejected an incoming BIND because it contained invalid random data.
The session manager rejected a BIND request because the session-level security in the BIND is not supported by pSNA (e.g. will not match the value specified by the associated partner LU definition). The length of the random data sub-field was not 10, which is the only value supported by pSNA (8 byte password). The probable causes are:
Function Degradation: The session manager rejects the BIND by sending a negative response to the BIND or an UNBIND (depending on the state of the session when the BIND request was received).
Customer Action: Try and determine if the problem was caused by a network definition error or a software error. Refer to related log entries and messages for more information and other recommended actions.
Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session manager rejected an incoming BIND because it contained invalid encryption data.
The session manager rejected a BIND request because the enciphered data in the BIND is not the length supported by pSNA. The length of the enciphered data sub-field was not 9, which is the only value supported by pSNA. The probable causes are:
Function Degradation: The session manager rejects the BIND by sending a negative response to the BIND or an UNBIND (depending on the state of the session when the BIND request was received).
Customer Action: Try and determine if the problem was caused by a network definition error or a software error. Refer to related log entries and messages for more information and other recommended actions.
Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session manager rejected an incoming BIND or ended a session because it detected a problem with the security or encryption data contained in the BIND or other received message.
The session manager ended a session because it detected a problem with the security information contained in the received message. In most case, the received message was a BIND request or response containing invalid security information or encryption data (which pSNA does not support). The sense code in the log record is the sense code used to end the session (by rejecting the received BIND request or by sending an UNBIND). The probable causes are:
Function Degradation: The session manager ends the session by sending a negative response to the BIND or an UNBIND (depending on the state of the session when the BIND request was received).
Customer Action: Try and determine if the problem was caused by a network definition error or a software error. Refer to related log entries and messages for more information and other recommended actions.
Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session manager (SM) received an internal inter-process signal it does not recognize (or process).
The session manager for an LU received an IPS that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to SM for processing. An internal code problem exists within pSNA.
Function Degradation: The unrecognized IPS is ignored, and SM continues to process other signals. Unexpected results will probably follow this problem, since SM or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The session manager (SM) received an SNA message it does not recognize (or process).
The session manager (SM) for an LU received a SNA message (MU) that it does not recognize or process. SM only processes session messages, such as BIND and UNBIND. This condition should not occur, since the unrecognized message should not have been routed to SM for processing. The probable causes are:
Function Degradation: The unrecognized MU is ignored, and SM continues to process other signals. Unexpected results will probably follow this problem, since SM or another node component are probably in error and out of sequence. In addition, communications may be affected since the received message is ignored.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The local node could not release some of the resources used by the compression component. The resources are no longer needed by the session.
Function Degradation: The node continues normal processing.
Customer Action: The node will probably continue to work correctly if this problem occurs, as long as resources are still available for subsequent sessions that request compression. If it appears to be behaving satisfactorily, no immediate action is required. To resolve the problem,
Customer Action: Try and determine the cause of the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The session manager ended a session because it detected a problem with the compression information contained in the received message (BIND response). The received message contained invalid or unsupported compression settings. The sense code in the log record is the sense code used to end the session (by rejecting the received BIND request or by sending an UNBIND). The probable causes are:
Function Degradation: The session manager ends the session by sending a negative response to the BIND or an UNBIND (depending on the state of the session when the message was received).
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session manager ended a session because it detected a problem with the compression information contained in the received message (BIND response). The compression options in the received response exceed those originally requested in the BIND request. The sense code in the log record is the sense code used to end the session. The probable causes are:
Function Degradation: The session manager ends the session by sending a an UNBIND with the indicated sense code.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The compression component could not allocate the resources needed to support the compression algorithms requested by a session.
Function Degradation: The session is established, with no compression used. Performance may be affected, since the data exchanged using the session is not compressed.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The session manager received a BIND requesting unsupported compression levels. The local node resets the compression levels to the indicated values. The pSNA APPC support does not support the requested compression levels. The probable causes are:
Function Degradation: The session manager accepts the session, but the compression levels are set to the indicated values. These values are communicated to the partner node in the BIND response. Performance may be affected, since the data exchanged is using a different compression algorithm.
Customer Action: Try and determine if the problem was caused by a network definition error or a software error.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session manager attempted to start a session requesting compression levels currently not supported by the compression component. The local node resets the compression levels to the indicated values. The probable causes are:
Function Degradation: The session is established, but the compression levels are set to the indicated values. These values are communicated to the partner node in the BIND request. Performance may be affected, since the data exchanged is using a different compression algorithm.
Customer Action: Try and determine if the problem was caused by a network definition error or a software error.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix.
Description: The compression component could not allocate the memory needed to support the compression algorithms requested by a session.
Function Degradation: The session is established, with no compression used. Performance may be affected, since the data exchanged using the session is not compressed.
Customer Action: Increase the amount of memory available to the pSNA node if a memory shortage is suspected.
If it appears that pSNA has memory available to process the request, and all required system resources are available, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA.
Description: The session manager encountered a should-not-occur condition. The internal compression indicators are invalid. A programming error/deficiency exists within the pSNA node.
Function Degradation: The session is established, with no compression used. Performance may be affected, since the data exchanged using the session is not compressed.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
If possible, try and re-create the problem with SM traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The session manager rejected an incoming BIND because it contained invalid security data. The persistent verification indicators in the BIND does not match the persistent verification information for other sessions between the same local LU, partner LU, and mode. The probable causes are:
Function Degradation: The session manager rejects the BIND by sending a negative response to the BIND or an UNBIND (depending on the state of the session when the BIND request was received).
Customer Action: Try and determine if the problem was caused by a network definition error or a software error. Refer to related log entries and messages for more information and other recommended actions.
Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session manager ended a session because it detected a problem with the persistent verification contained in the received message (BIND response). The BIND response indicates persistent verification is to be used for the session. The original BIND request did not indicate persistent verification was allowed for the session. The probable causes are:
Function Degradation: The session manager ends the session by sending a an UNBIND with the indicated sense code.
Customer Action: Try and determine if the problem was caused by a network definition error or a software error. Refer to related log entries and messages for more information and other recommended actions.
Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session manager ended a session because the received BIND response contained invalid security data.
The BIND indicated that conversation level security is not supported, but the already verified or persitent verification indicator was set (security was already verified by the partner LU). The probable causes are:
Function Degradation: The session manager ends the session by sending a an UNBIND with the indicated sense code.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session manager rejected an incoming BIND because it contained invalid security data.
The BIND indicated that conversation level security is not supported, but the persistent verification indicator was set. The probable causes are:
Function Degradation: The session manager rejects the BIND by sending a negative response to the BIND or an UNBIND (depending on the state of the session when the BIND request was received).
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node. Refer to related log entries and messages for more information and other recommended actions.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session manager ended a session because the received BIND response contained invalid security data.
The BIND indicated that only basic session level security is supported, but the original request requested enhanced security support. The probable causes are:
Function Degradation: The session manager rejects the BIND by sending a negative response to the BIND or an UNBIND (depending on the state of the session when the BIND request was received).
Customer Action: Try and determine if the problem was caused by a network definition error or a software error. Refer to related log entries and messages for more information and other recommended actions.
Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The session manager rejected an incoming BIND because it contained invalid security data. The password substitution indicators in the BIND does not match the password substitution information for other sessions between the same local LU, partner LU, and mode. The probable causes are:
Function Degradation: The session manager rejects the BIND by sending a negative response to the BIND or an UNBIND (depending on the state of the session when the BIND request was received).
Customer Action: Try and determine if the problem was caused by a network definition error or a software error. Refer to related log entries and messages for more information and other recommended actions.
Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Log events for the dependent LU requestor component of APPN (DLUR).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Description: Unacceptable DLUR capabilities structure (CV51) node type when being initialized from the GDB CB.
When initializing the DLUR capabilities structure (CV51) in DLUR main, the node type taken from the GDB CB indicates that the node type is neither a NN nor an EN.
Function Degradation: DLUR process exit
Customer Action: Call service with the code point and error description.
System Developer Action: Debug and determine what the node type is set to and if the setting is correct. Implement code fix.
Description: DLUR main fails to Pcreate the Send_Encap_Msg_TP.
A new EGPE process cannot be created at this time probably due to memory constraints within the node or a bad install of the process being Pcreated.
Function Degradation: DLUR process exit
Customer Action: Call service with the code point, error description, and abend code value if possible.
System Developer Action: Debug and determine what abend code was returned from the Pcreate call. A memory constraint problem can be solved by either adding memory to the hardware or by decreasing memory usage by stopping processes that are not needed. A bad install implies that the processes build was messed up (perhaps a missing file or something)Implement code fix based on the abend code value.
A memory constraint problem can be solved by either adding memory to the hardware or by decreasing memory usage by stopping processes that are not needed. A bad install implies that the processes build was messed up (perhaps a missing file or something) and should be rebuilt and reinstalled.
Additional Data: Has the following format:
Description: An MU determined to be SSCP-PU or SSCP-LU other data has been received with the SIDH set to a value other than 0x00.
DLUR main invokes a route_other_data subroutine when the incoming MU is not recognized to be a specific MU that DLUR must handle. The SIDH value should be 0x00 for both SSCP-PU other data or SSCP_LU other data. If the SIDH value is not 0x00, a route_other_data_error is logged.
Function Degradation: Tolerable - DLUR main will discard the MU.
Customer Action: Call service with the code point, error description, and MU SIDH value if possible.
System Developer Action: Debug and determine what the SIDH value is in the MU. Implement code fix.
Additional Data: Has the following format:
Description: The PU manager detected an error in the CV46 that was received along with an MU(ACTPU) signal from the DLUS SSCP.
Either the CV46 is missing from the ACTPU signal or information contained within the CV46 is missing or inaccurate.
Function Degradation: Tolerable - PU manager routine will discard the MU and generate and send a -RSP(ACTPU) signal to the SSCP. The sense code will be Sc_DLUR_MISSING_CV46 (0x08060000).
Customer Action: Call service with the code point, error description, and any or all of the CV46 data available.
System Developer Action: Debug DLUR and determine if the CV46 is present and the accuracy of the information within the CV46. Implement a code or configuration fix.
Description: The LU manager routine processing an MU signal was passed a NULL dlur_pu_cb_p from dlur main.
Within DLUR main, the subroutine pu_find_pu returned a null pointer to a dlur_pu_cb, meaning a PU CB could not be correlated with an lpid. This is most likely caused by timing window with PU and LU activation/deactivation flows: the PU has been deactivated (eg following a link down) while messages for an LU of this PU were queued. Or there may be a corrupted lpid value within the MU header or within a PU CB entry.
Function Degradation: Tolerable - LU manager routine will discard the MU and return.
Customer Action: Call service with the code point, error description, and any PU CB and information available.
System Developer Action: Debug DLUR and determine the state of both the DSPU and LU, look at PU CB's and MU header for lpid values. Implement a code fix.
Additional Data: Has the following format:
Description: The DLUR component rejected an ACTLU. The associated sense code is used to indicate the reason for rejection:
Function Degradation: Tolerable - LU manager will generate a -RSP(ACTLU) with a DEFAULT_SENSE_CODE (0x80200000) sense code or Sc_INSUFFICENT_STORAGE (0x8012000D) sense code and send RSP to SSCP.
Customer Action: Call service with the code point, error description, and any MU information available.
System Developer Action: Debug DLUR and determine the MU content received by the DLUR receive TP routine. For sense 0x80200000, if that looks consistent with what LU manager was processing, then open up an APAR on VTAM DLUS. For sense 0x8012000D, check storage use in node and customer configuration.
Additional Data: Has the following format:
Description: Input MU cannot be correlated with LU CB.
The LU manager routine processing an input MU signal cannot correlate an LU CB with the LFSID value within the MU header.
This message will sometimes be seen if a signal arrives for a dependent LU just after the LU is deactivated.
Function Degradation: Tolerable - For the following routines, LU manager will free the input MU and return to DLUR main:
xxxdlldq.c - Sc_DLUR_SSCP_SESSION_RESET (0x80050000)
-RSP(DACTLU) sent to SSCP
xxxdlliq.c - Sc_DLUR_SSCP_SESSION_RESET (0x80050000)
-RSP(INITSELF) sent to SLU
Customer Action: Call service with the code point, error description, and any LU CB and information available.
System Developer Action: Debug DLUR and determine the state of both the DSPU and LU, look at LU CB's and MU header for lfsid values. Implement a code fix.
Additional Data: Has the following format:
Description: MU(DACTLU) RSP cannot be correlated with LU CB or LU CB indicates the DLUS-DLUR pipe not active.
Either:
The LU manager routine processing an MU(DACTLU) RSP signal cannot correlate an LU CB with the LFSID value within the MU header.
Or:
The PIPE_CB_P within the PU CB is NULL, meaning there is no pipe on which to send the RSP(DACTLU)/RSP(ACTLU) signal to the SSCP.
Function Degradation: Tolerable - LU manager will free the MU and return.
Customer Action: Call service with the code point, error description, and any LU, PU, and PIPE CB information available.
System Developer Action: Debug DLUR and look at LU CB's and MU header for lfsid values. If the pipe_cb_p is null, check out possible link failure situations between the SSCP and DLUR node. Implement a code fix.
Additional Data: Has the following format:
Description: An MU(INITSELF) has been received while the SSCP-PU state is pending a DACTPU response (going inactive). LU-LU sessions cannot be supported while the SSCP-PU state is not active, therefore the MU(INITSELF) will not be forwarded to the SSCP.
Function Degradation: Tolerable - LU manager will discard the MU(INITSELF) and return.
Customer Action: Retry LU-LU session activation following SSCP-PU and SSCP-LU re-activation.
System Developer Action: Retry LU-LU session activation following SSCP-PU and SSCP-LU re-activation.
Additional Data: Has the following format:
Description: An MU(INITSELF) has been received while either the SSCP-LU or the down stream PU state is other than ACTIVE. LU-LU sessions cannot be supported while either the SSCP-LU or the PU state is not active, therefore the MU(INITSELF) will not be forwarded to the SSCP.
Function Degradation: Tolerable - LU manager will create a -RSP MU(INITSELF) for the SLU and return.
Customer Action: Retry LU-LU session activation following SSCP-PU and SSCP-LU re-activation.
System Developer Action: Retry LU-LU session activation following SSCP-PU and SSCP-LU re-activation.
Description: MU (LU OTHER DATA) cannot be correlated with LU CB, or LU CB state is other than active, or PU CB is other than active.
Either:
The LU manager routine processing an MU(LU OTHER DATA) signal cannot correlate an LU CB with the LFSID value within the MU header.
Or:
The state of either the LU-SSCP session is not active or the state of the DSPU is not active.
In both cases: A negative response for LU other data (SLU->SSCP) will be generated and sent if the data is first in segment and no dactpu has been sent.
Function Degradation: Tolerable - LU manager will generate and send a negative response. to the SLU->SSCP LU Other Data.
Customer Action: Call service with the code point, error description, and any LU and PU CB information available.
System Developer Action: Debug DLUR and determine the state of both the DSPU and LU, look at LU CB's and MU header for lfsid values and first in segment bits. Implement code fix.
Description: MU(LU OTHER DATA) cannot be correlated with LU CB, or LU CB state is other than active, or PU CB is other than active.
Either:
The LU manager routine processing an MU(LU OTHER DATA) signal cannot correlate an LU CB with the LFSID value within the MU header.
Or:
The state of either the LU-SSCP session is not active or the state of the DSPU is not active.
Function Degradation: Tolerable - LU manager will free the MU and return.
Customer Action: Call service with the code point, error description, and any LU CB and information available.
System Developer Action: Could possibly be a stray signal. Debug DLUR and determine the state of both the DSPU and LU, look at LU CB's and MU header for lfsid values. Implement a code fix.
Description: DLUR_SESSST cannot be correlated with LU CB, or the SSCP-LU state is other than active, or there is no active pipe between the DLUS and DLUR.
Either:
There is no active pipe servicing the dependent LU or the SSCP-LU session is not active. I.E. a link outage has occurred between the DLUS and DLUR nodes.
Or
The LU manager routine processing a SESSST signal from SS/SCM cannot correlate an LU CB with the LFSID value within the MU header. Either a corrupted lfsid value within the MU header or within an LU CB, or a timing type problem with LU activation/deactivation flows.
Function Degradation: Tolerable - A SESSST should will not be sent, but rather a CV2A will be added to the subsequent RSP(ACTLU).
Customer Action: Call service with the code point, error description, and any LU CB and information available if the LU CB is NULL.
System Developer Action:
Additional Data: Has the following format:
Description: Receipt of the pipe_allocate_Fail from the DLUR send_tp when it is unable to establish session with the DLUS receive_tp.
A DLUR send TP was unable to allocate a session with a partner DLUS receive TP. There are quite a few different reasons as to why the session failure occurred, so in this case the sense code is needed for further analysis of the problem.
Function Degradation: Intolerable - DLUR may retry pipe establishment with a secondary DLUS if the primary DLUS TP allocate has failed but the secondary DLUS TP allocate has not yet been tried.
Customer Action: Call service with the code point and sense code.
System Developer Action: Check the allocate failure sense code to further understand the problem. Implement the appropriate software or environment fix to the node in error.
Additional Data: Has the following format:
Description: The PIPE manager routine received an input signal while in a state such that the input signal should not have been sent and cannot be processed. The following input signals and PIPE states cause the should not occur log record:
Function Degradation: Tolerable - PIPE manager routine will discard the MU and return.
Customer Action: Call service with the code point, error description, PIPE state and input signal if possible.
System Developer Action: Debug and determine the PIPE state and what the input signal is and why. Implement code fix.
Additional Data: Has the following format:
Description: A PIPE manager routine hits the "should not occur" DEFAULT condition within a SWITCH statement.
The PIPE manager routine contains a switch statement with the DEFAULT condition being a should not occur situation. The switch statement expression is the PIPE state. The logdlur_PIPE_MGR_BAD_STATE error occurs when the DEFAULT condition is hit within one of the PIPE manager modules.
Function Degradation: Tolerable - PIPE manager routine will discard the MU and return.
Customer Action: Call service with the code point, error description, and switch variable value if possible.
System Developer Action: Debug and determine what the switch variable value is and why. Implement code fix.
Additional Data: Has the following format:
Description: A PIPE INOP signal arrived and could not be correlated to a pipe control block.
A PIPE INOP signal arrived that could not be correlated to a pipe control block based on the cgid value within the PIPE INOP signal. The cgid must match one of the cgid's in the pipe CB's. The dls_name is not being passed on the DLUR PIPE_INOP flows, so the only lookup for the PU manager routines is the cgid value.
The correlation error could have occurred as a result of timing situations. DLUR deactivating the pipe because of a CV X'51' capabilities mismatch problem is one example. A second situation to consider is one where the con-loser has been established, and the DLUR con-winner cannot be established due to an allocate fail problem. The con-loser will be deactivated by DLUR.
Function Degradation: Tolerable - The PIPE INOP signal will be discarded and DLUR processing will continue.
Customer Action: Call service with the code point, error description, and any configuration information about the resource in error.
System Developer Action: Debug and determine what pipe activation and deactivation flows have taken place within DLUR for both the con-winner and con-loser sessions. Implement code fix if a true timing problem is discovered.
Additional Data: Has the following format:
Description: A DLUR node has sent a CPSVRMGR initiation flow to a DLUR node (should be sent between DLUR and DLUS nodes).
A DLUR node is trying to establish a CPSVRMGR pipe with another DLUR node. The CPSVRMGR pipe should be established between a DLUR node and a serving DLUS node.
Function Degradation: Intolerable - A Management Services Alert will be generated. The DLUR Pipe will be deactivated with a sense code of Sc_DLUR_CAPS_MISMATCH_DLUR (0x088E0009) and the input MU (ACTPU or RECACTPU_RSP) will be discarded.
Customer Action: Call service with the code point, error description, and any configuration information about the resource in error.
System Developer Action:
Additional Data: Has the following format:
Description: A software release level mismatch has been detected by the DLUR node.
A DLUS node has sent a CPSVRMGR initiation flow to a DLUR node developed at a different software release level. In case the DLUS node's software release level is down-level to the DLUR node's release level.
Function Degradation: Intolerable - The DLUR Pipe will be deactivated with a sense code of Sc_DLUR_CAPS_MISMATCH_DLUR (0x088E0009) and the input MU (ACTPU or RECACTPU_RSP) will be discarded.
Customer Action: None.
System Developer Action: Obtain a compatible DLUS node software release level.
Additional Data: Has the following format:
Description: A PIPE INOP signal arrived from the DLUR node.
A PIPE INOP is simply an UNBIND for the DLUS-DLUR pipe. A sense code is included with the PIPE INOP, the most common sense code indicating that there are no more SSCP-PU sessions on the pipe, so DLUS is deactivating the CP-CP sessions making up the pipe. It is also normal for the sense code to be 00000000, indicating no sense data was included in the received UNBIND. Check the sense code for other reasons the pipe is being deactivated.
Function Degradation: Tolerable - The PIPE INOP signal will be processed and regular DLUR processing will continue. If there were any active PUs or LUs at the time of the INOP, DLUR will attempt to reestablish a pipe to a Primary or Secondary DLUS.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: An unrecognized control vector was encapsulated within a received GDS 1500 variable.
During parsing of the received MU buffer, a control vector that is not understood or recognized by the DLUR node was unmapped. The control vector will be discarded and the received MU buffer parsing will continue.
Function Degradation: Tolerable - Control vectors that are not recognized are ignored (i.e. not passed onto DLUR within the MU).
Customer Action: None.
System Developer Action: For information purposes, it might be wise to have a look at the CV and see if the header format is correct and includes the correct length.
Additional Data: Has the following format:
Description: A GDS 1500 variable was received without a required CV60 control vector.
A GDS 1500 variable was received by the DLUR Receive_Encap_Msg_TP but did not include the required CV60 control vector. The CV60 contains the FQPCID which is needed by DLUR to correlate the input signal to a PU control block and eventually forward the signal to the destination PU.
Function Degradation: Untolerable - The MU will not be forwarded to DLUR main. The condition will be alerted.
Customer Action: Call service with the code point, any GDS 1500 variable information available, and any DLUS node information that can be obtained.
System Developer Action: Debug DLUS code initiating the GDS 1500 flow to the DLUR node.
Additional Data: Has the following format:
Description: A link activation failure between the DSPU and the node where the PU manager resides has occurred.
The PU manager routine signaled CS to activate a link to a DSPU, and CS notified PU MGR that the link activation has failed.
Function Degradation: Tolerable - PU manager routine will discard the MU and generate and send a -RSP(ACTPU) signal to the SSCP. The sense code will be Sc_LINK_FAILURE (0x80020000).
Customer Action: Call service with the code point, error description, and any link activation failure sense code available.
System Developer Action: Debug CS and determine why the link activation has failed. Implement node definition or code fix.
Additional Data: Has the following format:
Description: The PU manager routine received an input signal while in a state such that the input signal should not have been sent and cannot be processed. The two situations where this event happens are
Function Degradation: Tolerable - PU manager routine will discard the MU and return.
Customer Action: Call service with the code point, error description, PU state and input signal if possible.
System Developer Action: Debug and determine the PU state and what the input signal is and why. Implement code fix.
Additional Data: Has the following format:
Description: A PU manager routine hits the "should not occur" DEFAULT condition within a SWITCH statement.
The PU (LU) manager routine contains a switch statement with the DEFAULT condition being a should not occur situation. The switch statement expression is the PU state. The logdlur_PU_MGR_BAD_STATE error occurs when the DEFAULT condition is hit within one of the PU (LU) manager modules.
Function Degradation: Tolerable - PU (LU) manager routine will discard the MU and return.
Customer Action: Call service with the code point, error description, and switch variable value if possible.
System Developer Action: Debug and determine what the switch variable value is and why. Implement code fix.
Additional Data: Has the following format:
Description: A PU manager routine received a null dlur_pu_cb_p after calling the subroutine pu_find_pu.
A PU manager routine calls pu_find_pu to search for a PU CB with an LPID entry matching the LPID value passed into the pu_find_pu routine. The LPID value passed into the pu_find_pu routine is one that was extracted from the MU header. PU_FIND_PU should return a valid PU CB pointer based on a comparison done between a lpid value passed to pu_find_pu and the lpid field stored within each PU CB entry, but in this case a null PU CB pointer is returned.
Function Degradation: Tolerable - PU manager routine will discard the MU and return.
Customer Action: Call service with the code point, error description, PU CB dump and MU LPID value if possible.
System Developer Action: Debug and determine why there is no PU CB for the given LPID within the MU header. Implement code fix.
Additional Data: Has the following format:
Description: DLUR detected an error while processing an ACTLU response. The control vectors in the response are invalid. The sum of the length fields in the control vectors exceeds the length of the received message. The error was detected while trying to process a control vector not recognized by DLUR. The probable causes are:
A software problem probably exists in the node that sent the message, or the APPC/APPN support in the remote node is not compatible (which should never happen) with the pSNA APPC/APPN support.
Function Degradation: Processing of the ACTLU response continues, but the control vector in error is not added to the response. Communications with other nodes may be affected because the control vector is not echoed in the response sent by the local node.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: DLUR main routine does an Mget to obtain storage for the DLUR process data control block, however there was no storage available.
Function Degradation: DLUR process exit
Customer Action: Call service with the Mget failure point.
System Developer Action: Debug and determine why there are memory constraints in the node. Implement code fix.
Additional Data: Has one of the following formats:
or
Description: DLUR rejected a session initialization request. The sense code provides more detailed information on why the request was rejected. An internal sense code 'FEEEEEEE' is shown if DLUR detects that the BIND arrived just after the associated LU had been deactivated. The probable causes are:
Function Degradation: The session initiation request is rejected with the indicated sense code.
Customer Action: Use the descriptions of the logged sense code, as well as information contained in any related log entries, to determine the cause of the problem. More detailed information may be available by investigating any related error log entries or messages in the local or remote node.
If the problem was not caused by a network configuration error, a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: DLUR cannot send a request to reserve an LFSID to the address space manager (ASM). DLUR could not successfully process a session initiation request. The LFSID assigned to the session could not be reserved because the command to send the request (ASSIGN_LFSID IPS message) to the address space manager failed. The EGPE function PQenq failed. The possible causes of this problem are:
Function Degradation: The session initiation request is rejected.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: Dynamic PU activation requested by DLUR (as a REQACTPU signal) is rejected by DLUS. The sense code provides more information on why the request was rejected.
Function Degradation: The DLUR initiated dynamic PU activation request is rejected with the indicated sense code.
Customer Action: Use the descriptions of the logged sense code, as well as information contained in any related log entries, to determine the cause of the problem. More detailed information may be available by investigating any related error log entries or messages in the local or remote node.
The problem could be due to the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The DLUR LU avlid tree should be in synch with the lu_cb_list maintained in each of the PUCBs. This error indicates that they have gone out of synch. This is a should not occur condition.
Function Degradation: This error indicates possible courruption of the AVL tree maintained off of the DLUR process data.
Customer Action: Try and determine the cause of the problem:
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
If the remote node is in error, contact the vendor providing the communications software for the remote node.
Description: The pu_free_pu routine was passed a NULL dlur_pu_cb_p.
pu_free_pu is called with a NULL PU_CB.
Function Degradation: Tolerable - pu_free_pu will return.
Customer Action: Call service with the code point, error description, and any PU CB and information available.
System Developer Action: Debug and determine why pu_free_pu is called with NULL PU_CB
Description: Number of PUs exceeded 64K while allocating PU_CB.
Unique pu_correlaor could not be alloted.
Function Degradation: Tolerable - Pexit.
Customer Action: Call service with the code point, error description, and any PU CB and information available.
System Developer Action: Debug and determine why the number of PUs exceeded 64K
Log events for the data encryption component of APPC (CPA).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: The LU compression component (CPA) encountered a should-not-occur condition. A received compression request contains invalid data. The LU role in the received request is invalid. An internal code problem exists within pSNA.
Function Degradation: The input value is ignored, and processing continues. Unexpected results will probably follow this problem, since the received request could not be processed (compression is not performed).
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The LU compression component (CPA) encountered a should-not-occur condition. A received compression request contains invalid data. The compression requirement (need) in the received request is invalid. An internal code problem exists within pSNA.
Function Degradation: The input value is ignored, and processing continues. Unexpected results will probably follow this problem, since the received request could not be processed (compression is not performed).
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The LU compression component (CPA) encountered a should-not-occur condition. An internal control block contains invalid data. The specified maximum compression value for the node (stored within the gdb) is invalid. An internal code problem exists within pSNA.
Function Degradation: Any received compression requests are ignored.
Customer Action: Call service with the code point and error description. In addition, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Log events for the RU level interface for the LUA component of APPC (LUA).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) encountered a should-not-occur condition while attempting to process an internal inter-process signal. An internal code problem exists within pSNA.
An LUA-RUI internal data processing module received a SNA message it does not recognize or process. This condition should not occur, since the unrecognized message should not have been routed to the module which encountered the error
Function Degradation: The unrecognized message is ignored, and LUA-RUI continues to process other signals. Unexpected results will probably follow this problem, since LUA or another node component are probably in error and out of sequence. In addition, the unrecognized message was an SNA message, so this error will probably cause problems with the associated session, such as hangs or protocol errors.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) received an internal inter-process signal it does not recognize (or process). An internal code problem exists within pSNA.
The LUA-RUI internal data routing routine received an IPS that it does not recognize or process. This condition should not occur, since the unrecognized signal should not have been routed to LUA.
Function Degradation: The unrecognized IPS is ignored, and LUA-RUI continues to process other signals. Unexpected results will probably follow this problem, since LUA or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) received an inter-process signal it does not recognize (or process). An internal code problem exists within pSNA.
The LUA-RUI internal data routing routine received an IPS from a process queue that it does not recognize or process. This condition should not occur.
Function Degradation: The received IPS is ignored, and LUA-RUI continues to process other signals. Unexpected results will probably follow this problem, since LUA-RUI or another node component are probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) received an unexpected ACTLU request from the SSCP. The received ACTLU request is a "cold" request, but the LUA-RUI interface believes the specified SSCP-LU session is already active or is being activated. The probable causes are:
Function Degradation: The received ACTLU is rejected. Unexpected network results will probably follow this problem, since the local node is out-of-sync with the SSCP.
Customer Action: The problem was probably caused by a communications problem with the remote node (such as a lost connection or session). Correct the communications error, and re-activate the connections with the remote node. If the problem persists, try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) encountered a should-not-occur condition while attempting to send an SNA message to a session partner. An internal code problem exists within pSNA.
Data Flow Control rejected an SNA message generated by LUA-RUI. This condition should not occur, since the rejected message should be valid. Possible rejected messages include:
Function Degradation: The unrecognized message is ignored, and LUA-RUI continues to process other messages. Unexpected results will probably follow this problem, since LUA or another node component are probably in error and out of sequence. In addition, the unrecognized message was an SNA message, so this error will probably cause problems with the associated session, such as hangs or protocol errors.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Not used.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) encountered a should-not-occur condition while attempting to send an SNA message to a session partner. An internal code problem exists within pSNA.
Transmission Control rejected an SNA message generated by LUA-RUI. This condition should not occur, since the rejected message should be valid.
Function Degradation: The unrecognized message is ignored, and LUA-RUI continues to process other messages. Depending on the severity of the error, the LUA-RUI interface may deactivated the related LU-LU session, as well as the SSCP-LU session.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) encountered a should-not-occur condition while attempting to send an SNA message to a session partner. An internal code problem exists within pSNA.
Transmission Control rejected an SNA message generated by LUA-RUI. This condition should not occur, since the rejected message should be valid. LUA-RUI does not recognize the return code used by transmission control to reject the message.
Function Degradation: The unrecognized message is ignored, and LUA-RUI continues to process other messages. Depending on the severity of the error, the LUA-RUI interface may deactivated the related LU-LU session, as well as the SSCP-LU session.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) encountered a should-not-occur condition while attempting to send an SNA message to a session partner. An internal control block is invalid.
The correlation table for an LU does not contain the expected entries.
Function Degradation: The uncorrelated request/response is ignored, LUA-RUI continues to process other messages. Unexpected results will probably follow this problem, since the data in the LU's correlation table is corrupted. This error will probably cause problems with the associated session, such as hangs or protocol errors.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) encountered a should-not-occur condition. One of the data flow control FSMs encountered a state error (should-not-occur situation). The current state of the FSM is invalid. The FSM should be robust enough to handle any valid input in any valid sequence. The probable causes are:
Function Degradation: LUA-RUI continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since LUA-RUI is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) received an invalid message from a session partner. The specific error is indicated by the logged sense code. The probable causes are:
Function Degradation: The received message is rejected with the indicated sense code (if it is a request). Depending on the severity of the error, the related session may also be terminated.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) encountered a should-not-occur condition. One of the data flow control FSMs encountered a state error (should-not-occur situation). The computed next state of the FSM is invalid. The FSM should be robust enough to handle any valid input in any valid sequence. The probable causes are:
Function Degradation: LUA-RUI continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since LUA-RUI is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) encountered a should-not-occur condition while attempting to process a received pacing response (IPR). An internal code problem exists within pSNA.
Function Degradation: The received pacing response messages is discarded. The outstanding BID request (send) fails. LUA-RUI continues to process other messages. This error will probably cause problems with the associated session, such as hangs or protocol errors.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) encountered a should-not-occur condition while attempting to process a received pacing response (IPR). An internal code problem exists within pSNA.
Function Degradation: The received pacing response messages is discarded. The outstanding receive request fails. LUA-RUI continues to process other messages. This error will probably cause problems with the associated session, such as hangs or protocol errors.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) encountered a should-not-occur condition while attempting to process an exception response (an internal SNA message used to reject an SNA message). An internal code problem exists within pSNA.
Function Degradation: The exception response is discarded. The outstanding BID request (send) fails. LUA-RUI continues to process other messages. This error will probably cause problems with the associated session, such as hangs or protocol errors.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) encountered a should-not-occur condition while attempting to process an exception response (an internal SNA message used to reject an SNA message). An internal code problem exists within pSNA.
Function Degradation: The exception response is discarded. The outstanding receive request fails. LUA-RUI continues to process other messages. This error will probably cause problems with the associated session, such as hangs or protocol errors.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) encountered a should-not-occur condition while attempting to send a pacing response (IPR). An internal code problem exists within pSNA.
Function Degradation: The pacing response message is not sent. Any outstanding send requests fail. LUA-RUI continues to process other messages. This error will probably cause problems with the associated session, such as hangs or protocol errors.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) encountered a should-not-occur condition while attempting to send a BIND response. An internal code problem exists within pSNA.
Function Degradation: The BIND response message is not sent. Any outstanding send requests fail. LUA-RUI continues to process other messages. This error will probably cause problems with the node that sent the original BIND request,such as hangs or protocol errors, since the local node could not respond to the received request.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) encountered a should-not-occur condition while attempting to send an UNBIND request to end a session. An internal code problem exists within pSNA.
Function Degradation: The UNBIND request message is not sent. Any outstanding send requests fail. LUA-RUI continues to process other messages. This error will probably cause problems with the associated session, such as hangs or protocol errors. The local node terminates the session, but cannot inform the partner of the session outage.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Not used.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) encountered a should-not-occur condition while attempting to send data. Possible failures include:
Function Degradation: The data is not sent and is discarded. Internal data structures, such as correlation tables and send queues, may be corrupted. Any outstanding send requests fail. LUA-RUI continues to process other messages. This error will probably cause problems with the associated session, such as hangs or protocol errors.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) encountered a should-not-occur condition. One of the transmission control FSMs encountered a state error (should-not-occur situation). The current state of the FSM is invalid. The FSM should be robust enough to handle any valid input in any valid sequence. The probable causes are:
Function Degradation: LUA-RUI continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since LUA-RUI is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) encountered a should-not-occur condition. One of the transmission control FSMs encountered a state error (should-not-occur situation). The computed next state of the FSM is invalid. The FSM should be robust enough to handle any valid input in any valid sequence. The probable causes are:
Function Degradation: LUA-RUI continues to process the input event, although the results may be unpredictable. Unexpected results will probably follow this problem, since LUA-RUI is probably in error. In addition, the communications support in an adjacent node and the local node may be incompatible.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what action code and input value caused the FSM to abend. Refer to related log entries and messages for more information. Implement code fix.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) encountered a should-not-occur condition while attempting to send a response to a session partner. The response that failed were to any pending messages on the LU-LU or LU-SSCP session when the session is being deactivated. An internal control block is invalid.
The correlation table for an LU does not contain the expected entries.
Function Degradation: The uncorrelated request/response is ignored, LUA-RUI continues to process other messages. Unexpected results will probably follow this problem, since the data in the LU's correlation table is corrupted. This error will probably cause problems with the associated session, such as hangs or protocol errors.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Description: Not used.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Description: Not used.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) encountered an internal error. The commpression status of a session could not be reset. The session was being reset because of the receipt of a CLEAR SNA message from the partner LU. node.
This should not occur. A programming error/deficiency exists within the pSNA
Function Degradation: The local node ends the session associated by sending an UNBIND type='FE' (session protocol error), with the sense code 20130000.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) encountered a should-not-occur condition. A programming error/deficiency exists within the pSNA The local session indicated that compression was being performed for the data being exchanged on a session, but the compression component did not contain any compression data for the session.
Function Degradation: LUA-RUI continues to process messages for the session, without performing any compression. Unexpected results will probably follow this problem, since the local node contains conflicting compression information for the session. Data may not be correctly compressed or decompressed.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) cannot process a received SNA message. It received a message indicating that the message should be compressed or decompressed, but the associated session is not using compression, or encountered an error while decompressing the received data. The probable causes are:
Function Degradation: The local node ends the session associated with the conversation by sending an UNBIND type='FE' (session protocol error), with the sense code 40220000.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with LUA and data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) encountered a should-not-occur condition. A programming error/deficiency exists within the pSNA The local session indicated that compression was being performed for the data being exchanged on a session, but the compression component did not contain any compression data for the session or encountered an error while de-compressing the received data.
Function Degradation: LUA-RUI terminates the associated session.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The dependent LUA RU interface (LUA-RUI) encountered an error while trying to free resources related to compressing and decompressing data for a session.
Function Degradation: LUA-RUI continues to process other messages. Unexpected results may follow this problem, since LUA could not release the allocated resources.
Customer Action: The node may continue to operate successfully. If the problem persists, or it adversely affects the operation of the node, call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: None.
Description: The dependent LUA RU interface (LUA-RUI) could not obtain the memory needed to compress or decompress data for a session.
Function Degradation: LUA RUI continues to process messages for the session, without performing any compression or decompression. Unexpected results will probably follow this problem, since the local node contains conflicting compression information for the session. Data may not be correctly compressed or decompressed.
Customer Action: Investigate whether the problem was caused by a shortage of available memory. Increase the amount of memory available to the local node if a memory shortage is suspected.
If it appears that the local node has enough memory available to process the request, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with LUA and data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA.
Additional Data: None.
Description: The dependent LUA RU interface (LUA-RUI) could not obtain the resources needed to compress or decompress data for a session.
Function Degradation: LUA RUI continues to process messages for the session, without performing any compression or decompression. Unexpected results will probably follow this problem, since the local node contains conflicting compression information for the session. Data may not be correctly compressed or decompressed.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: One of the send chaining correlation tables is full.
Function Degradation: The rui_write verb fails, and returns X'08780002' - send_correlation_table full.
Customer Action: The TH can be used to determine if the MU is for the LU-LU normal flow. If it is the LU-LU normal flow send correlation table that is full, it may be increased using the lua_ct_norm_send_size paramater on the rui_init verb. Otherwise, Call service with the code point and error description text.
System Developer Action: The TH can be used to determine if the MU was a normal or expedited flow. This will tell you which correlation table to check for the full condition. Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Log events for the dependent LU interface of APPC (LUA).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: A system (EGPE) function failed while trying to process an API verb received from an LUA application program. The probable causes are:
Some of the EGPE functions that can fail are:
Function Degradation: In almost all cases, the error occurs while processing an API verb from an application. The verb being process is returned to the application with an LUA_UNEXPECTED_DOS_ERROR (X'11F0') primary return code and the secondary return code set to the return code from the failing EGPE function.
In isolated cases, the error occurs while attempting to release the resources allocated for an application program when the application ends. In this case, processing continues within the local node, but some of the resources allocated for the application may not be released.
Finally, this log record is also created when the local node is attempting to notify an application that an API verb has completed. In this case, processing continues, but the API verb is not posted complete and the application will probably hang.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as the logged return code).
If the problem was not caused by a system failure or resource shortage, the problem was probably caused by a problem in the communications support in the local node. Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A system (OS/2) function failed while trying to process an API verb received from an LUA application program. The probable causes are:
Some of the OS/2 functions that can fail are:
Function Degradation: In almost all cases, the error occurs while processing an API verb from an application. The verb being process is returned to the application with an LUA_UNEXPECTED_DOS_ERROR (X'11F0') primary return code and the secondary return code set to the return code from the failing operating system function. If the error occurs while processing appc_register_memory(), the function completes with REGISTER_UNEXPECTED_DOS_ERROR (2).
In isolated cases, the error occurs while attempting to release the resources allocated for a transaction program when the APPC TP ends. In this case, processing continues within the local node, but some of the resources allocated for the TP may not be released.
Finally, this log record is also created when the local node is attempting to notify an application that an API verb has completed. In this case, processing continues, but the API verb is not posted complete and the application will probably hang.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as the logged return code).
If the problem was not caused by a system failure or resource shortage, the problem was probably caused by a problem in the communications support in the local node. Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Log events for the service layer interface for the LUA component of APPC (SLI).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: The LUA service layer interface component (SLI) encountered a system error. A system function failed while trying to process an API verb received from an LUA application program or while processing a received LUA message. The probable causes are:
The format of the log information data area:
Function Degradation: In almost all cases, the error occurs while processing an API verb from an application. The verb being process is returned to the application with an LUA_UNEXPECTED_DOS_ERROR (X'11F0') primary return code and the secondary return code set to the return code from the failing operating system function. If the failure occurred while processing a received LUA message, the received message is usually rejected and the associated application is notified.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as the logged return code).
If the problem was not caused by a system failure or resource shortage, the problem was probably caused by a problem in the communications support in the local node. Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The LUA service layer interface component (SLI) encountered a system error. A system function failed while trying to process an API verb received from an LUA application program or while processing a received LUA message. The probable causes are:
The format of the log information data area:
Function Degradation: In almost all cases, the error occurs while processing an API verb from an application. The verb being processed failed, with the primary and secondary return codes in the verb providing additional information on the encountered error. If the failure occurred while processing a received LUA message, the received message is usually rejected and the associated application is notified.
Customer Action: Try and determine what caused the problem by investigating any related error information (such as the logged return codes and message information).
If the problem was not caused by a communications error, system failure, or resource shortage, the problem was probably caused by a problem in the communications support in the local or remote node. Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
If possible, try and re-create the problem with data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Log events for the CCE/Discovery component of pSNA.
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: The CCE/Discovery component received an unrecognized IPS.
The probable cause is:
Function Degradation: The received IPS is ignored and processing continues. Unexpected results may follow this problem, since the sending component and the CCE/Discovery component are out of synchronization.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CCE/Discovery traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine if the received IPS was invalid or was unexpected. If invalid, implement a code fix eliminating the invalid IPS type (possibly replacing it with a valid value). If unexpected, implement a code fix to the CCE/Discovery module to handle the received IPS.
Additional Data: Has the following format:
Description: The CCE/Discovery component received a CCE_DISCOVERY IPS that contained an unrecognized cce_command_type.
The probable cause is:
Function Degradation: The received CCE_DISCOVERY IPS is ignored and processing continues. Unexpected results may follow this problem, since the sending component and the CCE/Discovery component are out of synchronization.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CCE/Discovery traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine if the received CCE_DISCOVERY IPS was invalid or was unexpected. If invalid, implement a code fix eliminating the invalid cce_command_type (possibly replacing it with a valid value). If unexpected, implement a code fix to the CCE/Discovery module to handle the received CCE_DISCOVERY cce_command_type.
Additional Data: Has the following format:
Description: The CCE/Discovery component received an CCE_DLC_MSG IPS that contained an unrecognized cce_msg_type.
The probable cause is:
Function Degradation: The received CCE_DLC_MSG IPS is ignored and processing continues. Unexpected results may follow this problem, since the sending component and the CCE/Discovery component are out of synchronization.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CCE/Discovery traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine if the received CCE_DLC_MSG IPS was invalid or was unexpected. If invalid, implement a code fix eliminating the invalid cce_msg_type (possibly replacing it with a valid value). If unexpected, implement a code fix to the CCE/Discovery module to handle the received CCE_DLC_MSG cce_msg_type.
Additional Data: Has the following format:
Description: The CCE/Discovery component encountered an error while attempting to start a port on an attached co-processor (subsystem). CCE/Discovery could not establish a connection (dialog) with the DLC component in the attached subsystem. The possible causes of this problem are:
Function Degradation: DLCX rejects the request to start the indicated port.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The CCE/Discovery component encountered an error while attempting to start a port on an attached co-processor (subsystem). The DLC component returned a negative response to the PDOPEN request. The possible causes of this problem are:
Function Degradation: DLCX rejects the request to start the indicated port.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The CCE/Discovery component encountered an error while attempting to activate a service access point (SAP). The DLC component returned a negative response to the Activate_SAP request. The possible causes of this problem are:
Function Degradation: DLCX rejects the request to start the indicated port.
Customer Action: Try and determine the cause of the problem:
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The CCE/Discovery component received an Unnumbered Information (UI) frame that was in error. The possible causes of this problem are:
Function Degradation: The UI frame is ignored and CCE/Discovery continues to process other frames. Unexpected results will probably follow this problem, since CCE/Discovery or another node component are probably in error and out of sequence. In addition, communications may be affected since the received frame is ignored.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The CCE/Discovery component received an Unnumbered Information (UI) frame that contained a sub-vector that CCE/Discovery does not recognize. The possible causes of this problem are:
Function Degradation: The unknown sub-vector is ignored and CCE/Discovery continues to process the rest of the frame. Communications may be affected since the received sub-vector is ignored.
Customer Action: Try and determine if the problem was caused by an error in the local node (pSNA) or the remote node.
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The CCE/Discovery component received an unrecognized DLC command from a data link control (DLC) component. An internal code problem exists within pSNA.
Function Degradation: None.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. If possible, try and re-create the problem with CCE/Discovery traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine if the received IPS was invalid or was unexpected. If invalid, implement a code fix eliminating the invalid IPS type (possibly replacing it with a valid value). If unexpected, implement a code fix to the CCE/Discovery module to handle the received IPS.
Log events for the Logical Data Link Control (LDLC) component of APPN.
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: A software problem exists within pSNA.
LDLC attempted to start the T1 timer, but the timer was already running.
This condition is caused by a logical software error. This condition should not occur, since LDLC should not be attempting to send a command to the remote node when a response from the remote node is outstanding.
Function Degradation:
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix.
Additional Data: Has the following format:
Description: LDLC received an LSA message it does not recognize (or process).
LDLC received an LSA message that it does not recognize or process. This condition should not occur, since the unrecognized message should not have been routed to LDLC for processing. An internal code problem exists within pSNA.
Function Degradation:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: LDLC received an IPS message it does not recognize (or process).
LDLC received an IPS message that it does not recognize or process. LDLC only processes IPS messages of type LSA_IPS or PE_TIMER_RSP. This condition should not occur, since the unrecognized message should not have been routed to LDLC for processing. An internal code problem exists within pSNA.
Function Degradation:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The frame which arrived from the DLC layer has an invalid LDLC header.
LDLC received a message from the network with an invalid LDLC header.
Function Degradation: The message will not be processed and will be discarded. Recovery maybe possible with the expiration of the T1 timer and resending of the outstanding messages.
Customer Action: Try and determine if the problem was caused by an error in remote node or the local node (pSNA).
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: The frame which arrived from the DLC layer has an invalid LLC header.
LDLC received a message from the network with an invalid LLC header.
Function Degradation: The message will not be processed and will be discarded. Recovery maybe possible with the expiration of the T1 timer and resending of the outstanding messages.
Customer Action: Try and determine if the problem was caused by an error in remote node or the local node (pSNA).
System Developer Action: Debug and determine what caused the failure to occur. If the error was caused by the pSNA support in the local node, isolate and implement a code fix. If the remote node is in error, contact the vendor providing the communications software for the remote node.
Additional Data: Has the following format:
Description: LDLC attempted to find a port in its port list for a received LSA and could not find it.
LDLC dequeued an LSA for which it cannot find the associated port control block in its port list.
Function Degradation:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: LDLC received invalid input to FSMXID. The received message is ignored.
The state of FSMXID will not accept this message type as input.
Function Degradation: The message will be discarded.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: LDLC could not allocate a link control block.
CS is attempting to start a link to a remote partner but LDLC cannot allocate a link control block.
Function Degradation: This condition should not occur and is the result of an internal programming error. The link will not be activated.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: LDLC received invalid input to FSMLDLC.
Either a message was received from the local node (pSNA) or remote that was not expected.
Function Degradation: The unrecognized IPS is ignored, and LDLC continues to process other signals.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: A software problem exists within pSNA.
LDLC could not allocate the link table to store link control blocks for this port. This condition should not occur. An internal code problem exists within pSNA.
Function Degradation:
Customer Action: Call service with the code point, error description, and abend code value if possible.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: LDLC does not recognize the DLC type for the message it received. A software problem exists within pSNA.
Function Degradation: The received message is ignored, and processing continues. Unexpected results will probably follow this problem, since LDLC is probably in error and out of sequence.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine the cause of the invalid dlc type.
Additional Data: Has the following format:
Description: LDLC received an LSA message with an invalid u_cep_id or p_cep_id. A software problem exists within pSNA.
Function Degradation: The received message is ignored, and processing continues.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Debug and determine if the received input value was invalid or was unexpected.
Log events for the TN3270E Server.
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: The TN3270E Server initialization could not be started using the currently defined system resources.
Function Degradation: The TN3270E Server is stopped.
Customer Action: Free up resources by reducing the number of active application programs that are running.
System Developer Action: None.
Additional Data: Has the following format:
Description: TN3270E Server requires TCP/IP sockets to initialize.
Function Degradation: The TN3270E Server is stopped.
Customer Action: Check your TCP/IP Protocol configuration. Restart pSNA. If the problem persists, save your message log. Note the time stamp on this message, and investigate messages with time stamps close to this one.
System Developer Action: None.
Additional Data: Has the following format:
Description: Another application is using the port configured for the TN3270E Server. The TN3270E Server uses port 23 as its default. Because this port is also used by the Telnet application, if the TELNETD process is running on the TN3270E Server, you must use another port for the TN3270E Server.
Function Degradation: The TN3270E Server is stopped.
Customer Action: Reconfigure TN3270E Server to use a port that is not already in use. When you choose another port, try to avoid port numbers used by other applications because if two applications inadvertently use the same port number, it can cause unpredictable results. You should notify users of the changed port number so that they can configure their client sessions accordingly.
System Developer Action: None.
Additional Data: Has the following format:
Description: The connection attempt from the specified IP address was rejected because there are no more LUAs available in the implicit workstation pool.
Function Degradation: The connection attempt is rejected.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: The connection attempt from the specified IP address was rejected because there are no more LUAs available in the implicit printer pool.
Function Degradation: The connection attempt is rejected.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: Multiple client connections have been terminated because of keepalive processing or TCP/IP errors.
Function Degradation: The specified number of connections are terminated.
Customer Action: Look in the message log to see whether the previous message was TNS0013I or TNS0015E. For TNS0013I, this message is informational and no further action is necessary. For TNS0015E, verify that TCP/IP is working correctly.
System Developer Action: None.
Additional Data: Has the following format:
Description: The indicated LUA verb received an unexpected return code. The primary and secondary return codes are displayed.
Function Degradation: This condition could cause a TN3270E Server function to fail.
Customer Action: If the problem persists, save your message log. Note the time stamp on this message, and investigate messages with time stamps close to this one.
System Developer Action: None.
Additional Data: Has the following format:
Description: The maximum number of TN3270E Server connections has been reached, so an additional connection cannot be started.
Function Degradation: The client is unable to connect to the TN3270E Server.
Customer Action: Stop any TN3270E connections that are not in use so that the client can attempt the connection again. You may want to use the keepalive or automatic logoff options to terminate connections that are no longer in use.
System Developer Action: None.
Additional Data: Has the following format:
Description: An internal error has occurred which caused the TN3270E Server to terminate.
Function Degradation: The TN3270E Server is stopped.
Customer Action: Restart pSNA. If the problem persists, save your message log. Note the time stamp on this message, and investigate messages with time stamps close to this one.
System Developer Action: None.
Additional Data: Has the following format:
Description: Multiple client connections have been terminated because the LU was not activated by the host within the one minute time limit.
Function Degradation: The specified number of connections are terminated.
Customer Action: Contact your local network operations Help Desk to activate the LU.
System Developer Action: None.
Additional Data: Has the following format:
Description: Keepalive processing was activated to examine client availability. This processing detected that the client with the specified IP address is not responding.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: The TN3270E Server encountered a TCP/IP error for the connection between the specified IP address and LU name.
Function Degradation: The TN3270E Server terminated the connection.
Customer Action: Check your TCP/IP Protocol configuration. If the problem persists, save your message log. Note the time stamp on this message, and investigate messages with time stamps close to this one.
System Developer Action: None.
Additional Data: Has the following format:
Description: The specified LU was not activated by the host within the one minute time limit.
Function Degradation: The TN3270E Server is stopped.
Customer Action: Contact your local network operations Help Desk to activate the specified LU.
System Developer Action: None.
Additional Data: Has the following format:
Description: An internal error has occurred and this condition could cause a TN3270E Server function to fail.
Function Degradation: A TN3270E Server function may fail.
Customer Action: If the problem persists, save your message log. Note the time stamp on this message and investigate messages with time stamps close to this one.
System Developer Action: None.
Additional Data: Has the following format:
Description: No LUs are avaialable for the client to connect
Function Degradation: The client cannot be connected to the host
Customer Action: Contact your local network operations Help Desk to add an LU to the specified POOL
System Developer Action: None.
Additional Data: Has the following format:
Description: No LUs are avaialable for the client to connect
Function Degradation: The client cannot be connected to the host
Customer Action: Contact your local network operations Help Desk to add an LU to the specified POOL
System Developer Action: None.
Additional Data: Has the following format:
Description: Default pool has to be configured for the client to connect
Function Degradation: The client cannot be connected to the host
Customer Action: Contact your local network operations Help Desk to configure a default pool
System Developer Action: None.
Additional Data: Has the following format:
Description: Client address mapping to be done
Function Degradation: The client cannot be connected to the host
Customer Action: Contact your local network operations Help Desk to configure a Address mapping
System Developer Action: None.
Additional Data: Has the following format:
Description: The TN3270 connection has queued to much data when APPN memory is constrained.
Function Degradation: APPN memory is past the constrained threshold
Customer Action: APPN may not have enough memory configured for the number of connections. Please recalulate the recommended APPN storage for this configuration.
System Developer Action: None.
Additional Data: Has the following format:
Description: No APPN memory left to allow new TN3270 connections
Function Degradation: The client cannot be connected to the host
Customer Action: Contact your local network operations Help Desk to configure more memory to APPN
System Developer Action: None.
Additional Data: Has the following format:
Description: No APPN beffers left for tn3270 traffic through APPN.
Function Degradation: The client connection was closed.
Customer Action: Contact your local network operations Help Desk to configure more memory to APPN
System Developer Action: None.
System error log events for the extended generalized programming environment (EGPE).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: A software problem exists within EGPE.
Initialization of EGPE failed. The attempt to create the pRAS trace information failed. The pRAS TraceSizeOf function failed with the indicated return code. The only reason this function should fail is bad parameters are passed to the function. An internal code problem exists within pSNA (EGPE).
Function Degradation: The pSNA node aborts its initialization and stops. No APPC/APPN communication services are available.
Customer Action: Call service with the code point and error description.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: EGPE could not create its internal trace information.
Initialization of EGPE failed. The attempt to create the pRAS trace information failed. The pRAS TraceInitialize function failed with the indicated return code. The only reasons this function should fail are bad parameters, a memory allocation attempt failed, or the specified NLS string tables could not be loaded. The possible causes of this problem are:
Function Degradation: The pSNA node aborts its initialization and stops. No APPC/APPN communication services are available.
Customer Action: Verify that the trace resources required by the pSNA node are available for use by all processes within the node. Next, verify that a memory shortage did not cause the problem. Finally, verify that all required communications program files have been installed and are available. If the problem is not resolved by any of these procedures, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: EGPE could not create its internal trace information.
Initialization of EGPE failed. The attempt to create the pRAS trace information failed. The pRAS function TraceDefineDestination failed with the indicated return code. The only reason this function should fail is bad parameters are passed to the function or memory could not be allocated. The possible causes of this problem are:
Function Degradation: The pSNA node aborts its initialization and stops. No APPC/APPN communication services are available.
Customer Action: Verify that a memory shortage did not cause the problem. If not related to a memory shortage problem, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE.
Initialization of EGPE failed. The attempt to create the pRAS trace information failed. The pRAS function TraceSetDestination failed with the indicated return code. The only reason this function should fail is bad parameters are passed to the function. An internal code problem exists within pSNA (EGPE).
Function Degradation: The pSNA node aborts its initialization and stops. No APPC/APPN communication services are available.
Customer Action: Call service with the code point and error description.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: Initialization of an EGPE process failed. The attempt to access the pRAS trace resources used by EGPE failed. The pRAS TraceAccess function failed with the indicated return code. The possible causes of this problem are:
Function Degradation: The EGPE process aborts its initialization and stops. The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: Verify that the trace resources required by the pSNA node are available for use by all processes within the node. Next, verify that a memory shortage did not cause the problem. Finally, verify that all required communications program files have been installed and are available. If the problem is not resolved by any of these procedures, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: The attempt to modify the trace information being trace failed.
The EGPE trace administration request failed. The attempt to start or stop the tracing of one or more EGPE trace categories failed. The pRAS TraceEnable or TraceDisable function failed with the indicated return code. The only reason this function should fail is bad parameters were passed to the function. An internal code problem exists within pSNA (EGPE).
Function Degradation: The trace administration request failed. The amount and type of trace information being gathered is unchanged. No other functions are disrupted.
Customer Action: Call service with the code point and error description.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: The attempt to receive an inter-layer (inter_processor) message failed. (AIX only)
EGPE could not receive an inter-layer transport message. These messages are typically used to exchange messages between co-processors within a system. The possible causes of this problem are:
Function Degradation: The message is lost. Processing continues, but the behavior of the node is unpredictable, since the lost message is probably a request from a component for services or information from another component within the communications sub-system. It could even result in communication errors, since the lost message may have contained actual communications data.
Customer Action: Try and determine if the problem was caused by a system and/or machine failure by investigating any related error information (such as additional log entries). If a problem is discovered in these systems, use the appropriate procedures to resolve the problem. If it appears that all other systems are functioning correctly, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The attempt to receive an inter-layer (inter-processor) message failed. (AIX only)
EGPE could not receive an inter-layer transport message. These messages are typically used to exchange messages between co-processors within a system. The possible causes of this problem are:
Function Degradation: The message is lost. Processing continues, but the behavior of the node is unpredictable, since the lost message is probably a request from a component for services or information from another component within the communications sub-system. It could even result in communication errors, since the lost message may have contained actual communications data.
Customer Action: Try and determine if the problem was caused by a system and/or machine failure by investigating any related error information (such as additional log entries). If a problem is discovered in these systems, use the appropriate procedures to resolve the problem. If it appears that all other systems are functioning correctly, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: EGPE could not establish a dialog with another EGPE in a different co-processor or with a non-EGPE process providing system services needed by EGPE or pSNA. Dialogs are typically used to exchange messages between co-processors or system processes within a system. The request to build the internal name used to identify the communications pipe between the two processes is incorrect. An internal code problem exists within pSNA (EGPE).
Function Degradation: The EGPE process is abnormally terminated (abended), The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: Call service with the code point and error description.
EGPE should create a process abend file containing a snapshot of the pSNA (EGPE) storage areas when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE (AIX only)
An invalid parameter was passed to the internal EGPE function MLTobtain_memory. The size of the requested memory packed is equal to or less than zero. An internal code problem exists within pSNA (EGPE).
Function Degradation: The function attempts to allocate the memory, using the erroneous size parameter. Processing continues.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: The gettimeofday() function failed. (AIX ONLY)
EGPE could not obtain the current time from the system. This time is used to compute the intervals needed to wait in timer requests. The possible causes of this problem are:
Function Degradation: The timer time can not be computed. If the return code is -1, then the EGPE process abends. The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
If the return code is not -1, processing continues but the related timer request is now invalid. The subsequent behavior of the node is unpredictable, since the timer request may hang or pop too early.
Customer Action: Try and determine if the problem was caused by a system failure by investigating the return code and any related error information (such as additional log entries). If a problem is discovered in these systems, use the appropriate procedures to resolve the problem. If it appears that all other systems are functioning correctly, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The nsleep() function failed. (AIX ONLY)
EGPE attempted to pause a process for a specified period of time, but the system request failed. These requests are typically used when waiting a specific period of time before continuing or retrying a function. The possible causes of this problem are:
Function Degradation: The process could not be paused. EGPE continues to spin in the wait loop until the expected amount of time has expired. This may cause a hard program loop if the nsleep() function continues to fail, possibly affecting the performance of the other components in the node. Ignoring the consequences of placing the process in a hard program loop, all other processing continues normally.
Customer Action: Try and determine if the problem was caused by a system failure by investigating the return code and any related error information (such as additional log entries). If a problem is discovered in these systems, use the appropriate procedures to resolve the problem. If it appears that all other systems are functioning correctly, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The DosSleep() function failed. (OS/2 ONLY)
EGPE attempted to pause a process for a specified period of time, but the system request failed. These requests are typically used when waiting a specific period of time before continuing or retrying a function. The possible causes of this problem are:
Function Degradation: The process could not be paused. EGPE continues to spin in the wait loop until the expected amount of time has expired. This may cause a hard program loop if the DosSleep() function continues to fail, possibly affecting the performance of the other components in the node. Ignoring the consequences of placing the process in a hard program loop, all other processing continues normally.
Customer Action: Try and determine if the problem was caused by a system failure by investigating the return code and any related error information (such as additional log entries). If a problem is discovered in these systems, use the appropriate procedures to resolve the problem. If it appears that all other systems are functioning correctly, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The DosGetDateTime() function failed. (OS/2 ONLY)
EGPE could not obtain the current time from the system. This time is used to compute the intervals needed to wait in timer requests. The possible causes of this problem are:
Function Degradation: The timer time can not be computed. The EGPE process abends. The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: Try and determine if the problem was caused by a system failure by investigating the return code and any related error information (such as additional log entries). If a problem is discovered in these systems, use the appropriate procedures to resolve the problem. If it appears that all other systems are functioning correctly, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The DosSetPrty() function failed.(OS/2 ONLY)
The attempt to set the tasking priority of the OS/2 process associated with an EGPE process failed. These requests are used to control the relative dispatching priority of tasks within OS/2. The possible causes of this problem are:
Function Degradation: The priority of the underlying OS/2 process could not be set. Processing continues, but the dispatch priority of the task is indeterminate. The subsequent behavior of the node is unpredictable although the node will probably function correctly, depending on how dependent the node is on the relative dispatching order of its tasks.
Customer Action: It is possible that the node will continue to work correctly if this problem occurs. If it appears to be behaving satisfactorily, no immediate action is required.
Try and determine if the problem was caused by a system failure by investigating the return code and any related error information (such as additional log entries). If a problem is discovered in these systems, use the appropriate procedures to resolve the problem. If it appears that all other systems are functioning correctly, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The DosSearchPath() function failed when looking for the C/C++ 2.0 debugger program. THIS PROBLEM SHOULD NOT OCCUR IN CUSTOMER ENVIRONMENTS. (OS/2 ONLY).
Initialization of an EGPE process failed. The attempt to load the process failed because the C/C++ debugger (IPMD.EXE) could not be found in the directories listed in the current PATH statement. The OS/2 DosSearchPath function failed with the indicated return code. The possible causes of this problem are:
Function Degradation: The EGPE process aborts its initialization and stops. The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: None.
System Developer Action: Verify that the debugger is installed correctly, and that the current PATH statement includes the directory containing the debugger program. If the problem is not resolved by any of these procedures, call service with the code point and error description.
Additional Data: Has the following format:
Description: The DosSearchPath() function failed when looking for the indicated program. OS/2 ONLY)
Initialization of an EGPE process failed. The attempt to load the process failed because the program load file could not be found in the directories listed in the current PATH statement. The OS/2 DosSearchPath function failed with the indicated return code. The possible causes of this problem are:
Function Degradation: The EGPE process aborts its initialization and stops. The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: Verify that the debugger is installed correctly, and that the current PATH statement includes the directory containing the debugger program. If the problem is not resolved by any of these procedures, call service with the code point and error description.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: The DosStartSession() function failed when loading the C/C++ 2.0 debugger program. THIS PROBLEM SHOULD NOT OCCUR IN CUSTOMER ENVIRONMENTS. (OS/2 ONLY)
Initialization of an EGPE process failed. The attempt to load the process failed because the C/C++ debugger (IPMD.EXE) could not be loaded. The OS/2 DosStartSession function failed with the indicated return code. The possible causes of this problem are:
Function Degradation: The EGPE process aborts its initialization and stops. The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: None.
System Developer Action: Verify that the debugger and program are installed correctly, and the LIBPATH statement includes the directories containing all DLLs needed by the debugger and the program. If the problem is not resolved by any of these procedures, call service with the code point and error description.
Additional Data: Has the following format:
Description: The DosSearchPath() function failed when looking for the C/C++ 2.0 profiler program. THIS PROBLEM SHOULD NOT OCCUR IN CUSTOMER ENVIRONMENTS. (OS/2 ONLY)
Initialization of an EGPE process failed. The attempt to load the process failed because the C/C++ profiler (IXTRA.EXE) could not be found in the directories listed in the current PATH statement. The OS/2 DosSearchPath function failed with the indicated return code. The possible causes of this problem are:
Function Degradation: The EGPE process aborts its initialization and stops. The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: None.
System Developer Action: Verify that the profiler is installed correctly, and that the current PATH statement includes the directory containing the profiler program. If the problem is not resolved by any of these procedures, call service with the code point and error description.
Additional Data: Has the following format:
Description: The DosStartSession() function failed when loading the C/C++ 2.0 profiler program. THIS PROBLEM SHOULD NOT OCCUR IN CUSTOMER ENVIRONMENTS.(OS/2 ONLY)
Initialization of an EGPE process failed. The attempt to load the process failed because the C/C++ profiler (IXTRA.EXE) could not be loaded. The OS/2 DosStartSession function failed with the indicated return code. The possible causes of this problem are:
Function Degradation: The EGPE process aborts its initialization and stops. The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: None.
System Developer Action: Verify that the profiler and program are installed correctly, and the LIBPATH statement includes the directories containing all DLLs needed by the profiler and the program. If the problem is not resolved by any of these procedures, call service with the code point and error description.
Additional Data: Has the following format:
Description: The DosExecPgm() function failed when loading the indicated program.(OS/2 ONLY)
Initialization of an EGPE process failed. The attempt to load the process failed. The OS/2 DosExecPgm function failed with the indicated return code. The possible causes of this problem are:
Function Degradation: The EGPE process aborts its initialization and stops. The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: Verify that the program is installed correctly, and the LIBPATH statement includes the directories containing all DLLs needed by the program. If the problem is not resolved by any of these procedures, call service with the code point and error description.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: The DosKillProcess() function failed when attempting to force-ably terminate a process. (OS/2 ONLY)
The attempt to force-ably stop an OS/2 process associated with an EGPE process failed. The possible causes of this problem are:
Function Degradation: The OS/2 process could not be stopped. Processing continues, but the identified process continues to execute, using any related system resources and possibly affecting the behavior of the rest of the node.
If the error occurred while shutting down the node, it is probable that the node will not successfully terminate.
Customer Action: It is possible that the node will continue to work correctly if this problem occurs. If it appears to be behaving satisfactorily, no immediate action is required. For example, one reason that the function may fail is that the process is already ended.
If the problem occurs while shutting down the node, the node probably will not successfully terminate. If that is the case, use any other system tools available to end the "NODE" process and all underlying processes, as well as the "XXXRAS00" process.
Try and determine if the problem was caused by a system failure by investigating the return code and any related error information (such as additional log entries). If a problem is discovered in these systems, use the appropriate procedures to resolve the problem. If it appears that all other systems are functioning correctly, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The DosQueryAppType() function failed when attempting to load the indicated program. (OS/2 ONLY)
Initialization of an EGPE process failed. The attempt to determine the OS/2 program type (e.g. WINDOWABLE, PM) of the process failed. The OS/2 DosQueryAppType function failed with the indicated return code. The possible causes of this problem are:
Function Degradation: The EGPE process aborts its initialization and stops. The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: Verify that the program is installed correctly. If the problem is not resolved by any of these procedures, call service with the code point and error description.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: Initialization of an EGPE process failed. The attempt to access the pRAS log resources used by EGPE failed. The pRAS LogSetDefault function failed with the indicated return code. The possible causes of this problem are:
Function Degradation: The EGPE process aborts its initialization and stops. The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: Verify that the log resources required by the pSNA node are available for use by all processes within the node. Next, verify that a memory shortage did not cause the problem. If the problem is not resolved by any of these procedures, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: Initialization of an EGPE process failed. The attempt to access the pRAS trace resources used by EGPE failed. The pRAS TraceAccess function failed with the indicated return code. The possible causes of this problem are:
Function Degradation: The EGPE process aborts its initialization and stops. The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: Verify that the trace resources required by the pSNA node are available for use by all processes within the node. Next, verify that a memory shortage did not cause the problem. Finally, verify that all required communications program files have been installed and are available. If the problem is not resolved by any of these procedures, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: The lockwait() function failed to get a lock after waiting %3 seconds. For some reason, another process is holding the lock and won't release it.
Function Degradation: The process that couldn't get a lock will Pexit.
Software error log events for the extended generalized programming environment (EGPE).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: A software problem exists within EGPE. (AIX ONLY)
EGPE does not recognize a inter-layer transport message received from another EGPE or sub-system services (SSS). These messages are typically used to exchange messages between co-processors within a system. An internal code problem exists within pSNA (EGPE).
Function Degradation: The message is ignored. Processing continues, but the behaviour of the node is unpredictable, since the ignored message is probably a request from a component for services or information from another component within the communications sub-system.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE. (AIX ONLY)
EGPE received an unexpected inter-layer transport acknowledgement message another EGPE or sub-system services (SSS). The local EGPE is out-of-sync with the other EGPE or SSS. An internal code problem exists within pSNA (EGPE).
Function Degradation: The message is ignored. Processing continues, but the behaviour of the node is unpredictable, since the systems are now out-of-sync and confused about the state of one another.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The attempt to open a dialog with another process (EGPE sub-system) failed. Dialogs are used by EGPE to communicate between processes in different processors, as well as communicate between EGPE processes and non-EGPE processes.
Initialization of EGPE failed. EGPE could not open a dialog with a sub-system (EGPE service) failed. EGPE can not establish a communications path with the needed sub-system. These sub-systems are used for system-specific functions, such as configuration and adapter/DLC services. The possible causes of this problem are:
Function Degradation: The pSNA node aborts its initialization and stops. No APPC/APPN communication services are available.
Customer Action: Try and determine if the problem was caused by a system and/or machine failure by investigating any related error information (such as additional log entries). If a problem is discovered in these systems, use the appropriate procedures to resolve the problem. If it appears that all other systems are functioning correctly, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: EGPE could not establish a dialog with another EGPE in a different co-processor. Dialogs are typically used to exchange messages between co-processors within a system. The possible causes of this problem are:
Function Degradation: Communications with the indicated EGPE cannot be established. Processing continues, but the behaviour of the node is unpredictable, since communications with the partner EGPE is impossible. The detecting EGPE system cannot exchange any information with the partner EGPE system, so components and services provided by each EGPE are not available to the other. It could even result in communication errors, since the partner EGPEs may provide outboard routing services.
Customer Action: Verify that a memory shortage did not cause the problem. If not, verify that the required communications program files have been installed and are available. If not related to a memory shortage or an installation problem, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: EGPE could not establish a dialog with another EGPE in a different co-processor. Dialogs are typically used to exchange messages between co-processors within a system. The possible causes of this problem are:
Function Degradation: Communications with the indicated EGPE cannot be established. Processing continues, but the behaviour of the node is unpredictable, since communications with the partner EGPE is impossible. The detecting EGPE system cannot exchange any information with the partner EGPE system, so components and services provided by each EGPE are not available to the other. It could even result in communication errors, since the partner EGPEs may provide outboard routing services.
Customer Action: Try and determine if the problem was caused by a system and/or machine failure by investigating any related error information (such as additional log entries). If a problem is discovered in these systems, use the appropriate procedures to resolve the problem. If it appears that all other systems are functioning correctly, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: EGPE could not establish a dialog with another EGPE in a different co-processor. Dialogs are typically used to exchange messages between co-processors within a system. The possible causes of this problem are:
Function Degradation: Communications with the indicated EGPE cannot be established. Processing continues, but the behaviour of the node is unpredictable, since communications with the partner EGPE is impossible. The detecting EGPE system cannot exchange any information with the partner EGPE system, so components and services provided by each EGPE are not available to the other. It could even result in communication errors, since the partner EGPEs may provide outboard routing services.
Customer Action: Verify that a memory shortage did not cause the problem. If not, verify that the required communications program files have been installed and are available. If not related to a memory shortage or an installation problem, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: EGPE could not send a message completing the creation of a dialog to the partner EGPE system. The dialog creation attempt failed. Dialogs are used by EGPE to communicate with EGPEs in different co-processors. The possible causes of this problem are:
Function Degradation: Communications with the indicated EGPE cannot be established. Processing continues, but the behaviour of the node is unpredictable, since communications with the partner EGPE is impossible. The detecting EGPE system cannot exchange any information with the partner EGPE system, so components and services provided by each EGPE are not available to the other. It could even result in communication errors, since the partner EGPEs may provide outboard routing services.
Customer Action: Try and determine if the problem was caused by a system and/or machine failure by investigating any related error information (such as additional log entries). If a problem is discovered in these systems, use the appropriate procedures to resolve the problem. If it appears that all other systems are functioning correctly, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: EGPE could not establish a dialog with a partner EGPE in a co-processor because the partner EGPE system rejected the setup request. The dialog creation attempt failed. Dialogs are used by EGPE to communicate with EGPEs in different co-processors. The possible causes of this problem are:
Function Degradation: Communications with the indicated EGPE cannot be established. Processing continues, but the behaviour of the node is unpredictable, since communications with the partner EGPE is impossible. The detecting EGPE system cannot exchange any information with the partner EGPE system, so components and services provided by each EGPE are not available to the other. It could even result in communication errors, since the partner EGPEs may provide outboard routing services.
Customer Action: Try and determine if the problem was caused by a system and/or machine failure by investigating any related error information (such as additional log entries). If a problem is discovered in these systems, use the appropriate procedures to resolve the problem. If it appears that all other systems are functioning correctly, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A software problem exists within EGPE. (AIX ONLY)
EGPE does not recognize a inter-layer transport message received from another EGPE or sub-system services (SSS). These messages are typically used to exchange messages between co-processors within a system. An internal code problem exists within pSNA (EGPE).
Function Degradation: The message is ignored. Processing continues, but the behaviour of the node is unpredictable, since the ignored message is probably a request from a component for services or information from another component within the communications sub-system.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE. (AIX only)
An invalid parameter was passed to the internal EGPE function MLTfree_memory. The provided storage address is invalid (NULL). An internal code problem exists within pSNA (EGPE).
Function Degradation: The request to free the invalid storage area is ignored. Processing continues.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to free an area of memory has detected a serious problem. The cell size specified in the storage area's memory header does not match the cell size in the memory pool's free storage control area. Either a logic problem exists within EGPE, or more likely the memory header or the memory pool control block have been overwritten with bad data. An internal code problem exists within pSNA or EGPE.
Function Degradation: The EGPE process is abnormally terminated (abended), The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: Call service with the code point and error description.
EGPE should create a process abend file containing a snapshot of the pSNA (EGPE) storage areas when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to free an area of memory has detected a serious problem. The storage area's memory header has been corrupted, or more likely a storage area that has already been freed is being freed again. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to free the storage area is ignored. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing the corruption of storage areas or the node is attempting to free memory that has already been freed. In addition the node may experience storage shortages since the corrupted storage area is lost.
Customer Action: Call service with the code point and error description.
EGPE should create a process dump file containing a snapshot of the pSNA (EGPE) storage areas when the problem was detected. Supply this dump file to service. If the dump file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to free an area of memory has detected a serious problem. The storage area's memory header has been corrupted or the storage area has been overwritten. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to free the storage area is ignored. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing the corruption of storage areas. In addition, the node may experience storage shortages since the corrupted storage area is lost.
Customer Action: Call service with the code point and error description.
EGPE should create a process dump file containing a snapshot of the pSNA (EGPE) storage areas when the problem was detected. Supply this dump file to service. If the dump file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
An EGPE memory free request (Mfree) failed because the supplied storage address in invalid (the storage area is not on the correct memory address alignment). An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to free the storage area is ignored. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing invalid storage areas to be used (freed). In addition, the node may experience storage shortages since the corrupted storage area is lost.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
An EGPE memory free request (Mfree) failed because the supplied storage address in invalid (the memory header contains invalid information, such as the allocating EGPE process ID). An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to free the storage area is ignored. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing invalid storage areas to be used (freed). In addition, the node may experience storage shortages since the corrupted storage area is lost.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
An EGPE memory free request (Mfree) failed because the supplied storage address in invalid (the size in the memory header is invalid). An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to free the storage area is ignored. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing invalid storage areas to be used (freed). In addition, the node may experience storage shortages since the corrupted storage area is lost.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to free an area of memory has detected a serious problem. The storage area's memory header contains invalid information or the target memory pool is invalid. Either a logic problem exists within EGPE, or more likely the memory header or the memory pool control block have been overwritten with bad data. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to free the storage area is ignored. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing the corruption of storage areas. In addition, the node may experience storage shortages since the corrupted storage area is lost.
Customer Action: Call service with the code point and error description.
EGPE should create a process dump file containing a snapshot of the pSNA (EGPE) storage areas when the problem was detected. Supply this dump file to service. If the dump file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: EGPE could not increase the amount of memory it uses for control blocks or data areas. The possible causes of this problem are:
Function Degradation: Processing continues, but the behaviour of the node is unpredictable, since the needed additional storage could not be obtained. The node could start ending processes that are waiting for additional memory, causing still other problems since those processes may provide services required by the node to function correctly. The throughput of the node may also decrease significantly, since storage may not be available to receive data.
Customer Action: Try and determine if the problem was caused by a shortage of available memory. Increase the amount of memory available to the pSNA node if a memory shortage is suspected. If it appears that there is storage available for use by EGPE, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to allocate internal EGPE control areas (queue elements) failed. The storage area used to control the usage of the queue elements has been overwritten. An internal code problem exists within pSNA or EGPE.
Function Degradation: The EGPE process is abnormally terminated (abended), The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: Call service with the code point and error description.
EGPE should create a process abend file containing a snapshot of the pSNA (EGPE) storage areas when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to allocate an area of memory has detected a serious problem. The internal data structures used to manage the memory pool's free areas are corrupted. Either a logic problem exists within EGPE, or more likely the internal memory management data structures have been overwritten with bad data. An internal code problem exists within pSNA or EGPE.
Function Degradation: The EGPE process is abnormally terminated (abended), The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: Call service with the code point and error description.
EGPE should create a process abend file containing a snapshot of the pSNA (EGPE) storage areas when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A request to allocate an area of memory failed. EGPE could not allocate the requested amount of storage. The most probable cause of this problem is A serious memory shortage problem exists.
Function Degradation: The EGPE process is abnormally terminated (abended), The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: Try and determine if the problem was caused by a shortage of available memory. Increase the amount of memory available to the pSNA node if a memory shortage is suspected. If it appears that there is storage available for use by the node, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA.
Additional Data: Has the following format:
Description: A request to allocate an area of memory failed. EGPE could not allocate the requested amount of storage. The most probable cause of this problem is A serious memory shortage problem exists.
Function Degradation: The EGPE process is abnormally terminated (abended), The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: Try and determine if the problem was caused by a shortage of available memory. Increase the amount of memory available to the pSNA node if a memory shortage is suspected. If it appears that there is storage available for use by the node, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
The name registry server's function recovery routine was invoked with a unrecognized/ unsupported recovery event. An internal code problem exists within pSNA or EGPE.
Function Degradation: The function recovery event is ignored. Processing continues.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: An EGPE process abended. (AIX only).
An EGPE process abended, either because of an unrecoverable error, or more likely a software problem that causes a system trap. An internal code problem exists within pSNA or EGPE.
Function Degradation: The EGPE process is abnormally terminated (abended), The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: Call service with the code point and error description.
EGPE should create a process abend file containing a snapshot of the pSNA (EGPE) storage areas when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A child process of an EGPE process abended. The child process could also be an EGPE process. (AIX only).
A process abended, either because of an unrecoverable error, or more likely a software problem that causes a system trap. This log entry is created by the EGPE process that created the process that abended. An internal code problem exists within pSNA or EGPE.
Function Degradation: The child process is abnormally terminated (abended), The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: Call service with the code point and error description.
EGPE should create a process abend file containing a snapshot of the pSNA (EGPE) storage areas when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A bus (system memory or I/O) error was detected. (AIX ONLY)
A system bus error (e.g. memory, I/O, or inter-processor data transfer) was detected.
Function Degradation: Processing continues, but the behaviour of the node is unpredictable, since a bus error usually indicates the loss or corruption of data. It could even result in communication errors, since the bus error may have occurred while transferring actual communications data.
Customer Action: Try and determine if the problem was caused by a system and/or machine failure by investigating any related error information (such as additional log entries). If a problem is discovered in these systems, use the appropriate procedures to resolve the problem. If it appears that all other systems are functioning correctly, call service with the code point and error description.
System Developer Action: Debug and determine what caused the failure to occur. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA. (OS/2 ONLY).
A request to create a new process failed because invalid parameters were passed on the creation attempt. The request specified a function address (not a program name). This type of request is not supported by OS/2. An internal code problem exists within pSNA or EGPE.
Function Degradation: The process creation attempt fails. The consequences of the process creation attempt failing depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA (OS/2 ONLY).
A request to force-ably stop a process failed because invalid parameters were passed on the termination attempt. The request specified a function address (not a process ID). This type of request is not supported by OS/2. An internal code problem exists within pSNA or EGPE.
Function Degradation: The OS/2 process could not be stopped. Processing continues, but the identified process continues to execute, using any related system resources and possibly affecting the behaviour of the rest of the node.
If the error occurred while shutting down the node, it is probable that the node will not successfully terminate.
Customer Action: It is possible that the node will continue to work correctly if this problem occurs. If it appears to be behaving satisfactorily, no immediate action is required.
If the problem occurs while shutting down the node, the node probably will not successfully terminate. If that is the case, use any other system tools available to end the "NODE" process and all underlying processes, as well as the "XXXRAS00" process.
Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: The DosSetExceptionHandler() function failed when attempting to start a new EGPE process (OS/2 thread). (OS/2 ONLY)
Initialization of an EGPE process failed. The attempt to hook an exception handler failed. The OS/2 DosSetExceptionHandler function failed with the indicated return code. The possible causes of this problem are:
Function Degradation: The EGPE process aborts its initialization and stops. The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: Try and determine if the problem was caused by a system failure by investigating the return code and any related error information (such as additional log entries). If a problem is discovered in these systems, use the appropriate procedures to resolve the problem. If it appears that all other systems are functioning correctly, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The DosUnsetExceptionHandler() function failed while ending an EGPE process (OS/2 thread). (OS/2 ONLY)
Processing continues, and the EGPE process completes terminating. The attempt to unhook an exception handler failed. The OS/2 DosUnsetExceptionHandler function failed with the indicated return code. The possible causes of this problem are:
Function Degradation: The EGPE process ends, and normal processing continues. The pSNA node should be able to recover from this problem, although the system resources associated with the exception handler are not freed.
Customer Action: In most cases, the problem will not adversely affect the operation of the pSNA node. It should still be investigated, since this error should not occur in a system that is operating correctly. Try and determine if the problem was caused by a system failure by investigating the return code and any related error information (such as additional log entries). If a problem is discovered in these systems, use the appropriate procedures to resolve the problem. If it appears that all other systems are functioning correctly, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA (OS/2 ONLY).
A request (Pexit) to stop an EGPE process failed because the process was in an invalid state. The process was in a critical section when the termination attempt was issued. An internal code problem exists within pSNA or EGPE.
Function Degradation: Processing of the termination request continues. The subsequent behaviour of the node may be affected, especially if the resources locked in the critical section are not freed when the terminating process ends.
Customer Action: It is possible that the node will continue to work correctly if this problem occurs. If it appears to be behaving satisfactorily, no immediate action is required.
Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: An EGPE process terminated, but with a non-zero termination code.
An EGPE process terminated because it detected an unrecoverable error. The cause of the error is indicated by the Pexit completion code. Lists of these codes can be found in the following header files:
Function Degradation: The EGPE process is terminated. The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: Call service with the code point and error description.
EGPE should create a process abend file containing a snapshot of the pSNA (EGPE) storage areas when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA
A request to validate a logical process ID specified in a received inter-process signal (IPS) failed. The indicated logical process does not exist (the supplied logical process ID is invalid). This condition should not occur. An internal code problem exists within pSNA.
Function Degradation: The EGPE process is abnormally terminated (abended), The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: Call service with the code point and error description.
EGPE should create a process abend file containing a snapshot of the pSNA (EGPE) storage areas when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs. In addition, try and re-create the problem with inter-process signal traces enabled and supply that trace information with the problem.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: An EGPE process received an internal inter-process signal (IPS) which contained an invalid logical process ID. The indicated logical process does not exist (the supplied logical process ID is invalid). This condition should not occur. An internal code problem exists within pSNA.
Function Degradation: The received IPS is ignored, and the EGPE process continues to receive other signals. Unexpected results will probably follow this problem. Either the receiving process or the sending process is in error; or the two processes are out of sequence with one another.
Customer Action: Call service with the code point and error description. In addition:
System Developer Action: Isolate and implement a code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to insert a queue element into a queue failed because the current queue position (the cursor) has not been set to a valid position within the queue. An internal code problem exists within pSNA or EGPE.
Function Degradation: The queue element is not placed on the queue and is probably lost. The subsequent behaviour of the node is unpredictable, since the lost queue element will probably affect future node functions.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to insert a queue element into a queue failed because the current queue position (the cursor) has not been set to a valid position within the queue. An internal code problem exists within pSNA or EGPE.
Function Degradation: The queue element is not placed on the queue and is probably lost. The subsequent behaviour of the node is unpredictable, since the lost queue element will probably affect future node functions.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to remove a queue element from a queue failed because the current queue position (the cursor) has not been set to a valid position within the queue. An internal code problem exists within pSNA or EGPE.
Function Degradation: The queue element is not removed from the queue. The subsequent behaviour of the node is unpredictable, since the invoking function expected to receive a valid queue element for processing. In fact, in many cases the requesting process will probably abend because it is not expecting the dequeue attempt to fail.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to transfer data into a buffer pool failed because the target pool type (e.g. LIMITED, PERMANENT) is invalid. The probable cause is that the supplied buffer pool pointer is invalid. An internal code problem exists within pSNA or EGPE.
Function Degradation: The buffer transfer is aborted. Processing continues, but the behaviour of the node is unpredictable. In fact, in many cases the requesting process will probably abend because it is not expecting the transfer attempt to fail. It will probably result in communication errors, since buffer transfers are usually used for communications data.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to transfer data into a buffer pool failed because the target pool is invalid. The target pool was a limited buffer pool, but the transfer request specified that the request should not wait if buffers are not available. This combination is invalid when transferring buffers. The probable cause is that the supplied buffer pool pointer is invalid. An internal code problem exists within pSNA or EGPE.
Function Degradation: The buffer transfer is aborted. Processing continues, but the behaviour of the node is unpredictable. In fact, in many cases the requesting process will probably abend because it is not expecting the transfer attempt to fail. It will probably result in communication errors, since buffer transfers are usually used for communications data.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to transfer data into a buffer pool failed because the target pool is marked invalid. The probable cause is that the supplied buffer pool pointer is invalid. An internal code problem exists within pSNA or EGPE.
Function Degradation: The buffer transfer is aborted. Processing continues, but the behaviour of the node is unpredictable. In fact, in many cases the requesting process will probably abend because it is not expecting the transfer attempt to fail. It will probably result in communication errors, since buffer transfers are usually used for communications data.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to transfer data into a buffer pool failed because the size of the buffers in the target pool are not large enough to hold the data being transferred. The probable cause is the invoking routine chose the wrong buffer pool or should have segmented the data before transferring the data. An internal code problem exists within pSNA or EGPE.
Function Degradation: The buffer transfer is aborted. Processing continues, but the behaviour of the node is unpredictable. In fact, in many cases the requesting process will probably abend because it is not expecting the transfer attempt to fail. It will probably result in communication errors, since buffer transfers are usually used for communications data.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to transfer data into a demand buffer failed because the size of the buffer is not large enough to hold the data being transferred. A demand buffer is a buffer that is not part of a buffer pool. The invoking function supplied a buffer that was not large enough to hold the amount of data being transferred. An internal code problem exists within problem exists within pSNA or EGPE.
Function Degradation: The buffer transfer is aborted. Processing continues, but the behaviour of the node is unpredictable. In fact, in many cases the requesting process will probably abend because it is not expecting the transfer attempt to fail. It will probably result in communication errors, since buffer transfers are usually used for communications data.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: Not enough memory is available for pSNA to process a message.
A request to transfer data into a buffer pool failed because the pool does not have enough buffers to hold the data being transferred (the status of the buffer pool is critical) and the invoking routine specified that it does not want to wait for buffers to become available. The pSNA node does not have enough memory available to process the current data request.
Function Degradation: The buffer transfer is aborted. Processing continues, but the behaviour of the node is unpredictable. In fact, in many cases the requesting process will probably abend because it is not expecting the transfer attempt to fail. It will probably result in communication errors, since buffer transfers are usually used for communications data.
Customer Action: Try and allocate more memory for usage by the pSNA node. Either try and make more memory available for usage, or stop and start the pSNA node with more memory. If no more memory can be made available, or it appears that pSNA should have enough memory available to process the request, call service with he code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix if a code fix is needed. In most cases, a code change is not required since the problem is related to a memory shortage, but the invoking routine may be changed to specify that it can wait for buffers to become available.
Additional Data: Has the following format:
Description: Not enough memory is available for pSNA to process a message. In some cases, this problem may be caused by a software defect within EGPE or pSNA.
A request to transfer data into a buffer pool failed because the pool does not have enough buffers to hold the data being transferred. This problem can occur because:
Function Degradation: The buffer transfer is aborted. Processing continues, but the behaviour of the node is unpredictable. In fact, in many cases the requesting process will probably abend because it is not expecting the transfer attempt to fail. It will probably result in communication errors, since buffer transfers are usually used for communications data.
Customer Action: Try and allocate more memory for usage by the pSNA node. Either try and make more memory available for usage, or stop and start the pSNA node with more memory. If no more memory can be made available, or it appears that pSNA should have enough memory available to process the request, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix if a code fix is needed.
Additional Data: Has the following format:
Description: Not enough memory is available for pSNA to process a message. In some cases, this problem may be caused by a software defect within EGPE or pSNA.
A request to transfer data into a buffer pool failed because the pool does not have enough buffers to hold the data being transferred. This problem is similar to F7100000-00000025, but in this case the transfer request involves multiple source buffers. This problem can occur because:
Function Degradation: The buffer transfer is aborted. Processing continues, but the behaviour of the node is unpredictable. In fact, in many cases the requesting process will probably abend because it is not expecting the transfer attempt to fail. It will probably result in communication errors, since buffer transfers are usually used for communications data.
Customer Action: Try and allocate more memory for usage by the pSNA node. Either try and make more memory available for usage, or stop and start the pSNA node with more memory. If no more memory can be made available, or it appears that pSNA should have enough memory available to process the request, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix if a code fix is needed.
Additional Data: Has the following format:
Description: EGPE detected an error processing an internal inter-process signal (IPS). An attempt to transfer the buffers contained in the signal failed. Possible causes are:
Function Degradation: Processing continues. Unexpected results will probably follow this problem, since the requested buffer transfer failed. In some cases, communications may be disrupted (e.g. data transfers are stopped) because the requested number of buffers are not available.
Customer Action: Verify that a memory shortage did not cause the problem.
If not related to a memory shortage, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service. In addition, try and re-create the problem with inter-process signal, buffer manager, and data traces enabled and supply that trace information with the problem.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: None.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to free a data buffer has detected a serious problem. The data buffer's header has been corrupted, or more likely a data buffer that has already been freed is being freed again. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to free the data buffer is ignored. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing the corruption of storage areas or the node is attempting to free memory that has already been freed. In addition the node may experience storage shortages since the corrupted data buffer is lost.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to free a data buffer has detected a serious problem. The data buffer's header contains invalid information or the target buffer pool is invalid. Either a logic problem exists within EGPE, or more likely the buffer header or the buffer pool control block have been overwritten with bad data. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to free the data buffer is ignored. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing the corruption of storage areas. In addition, the node may experience storage shortages since the corrupted data buffer is lost.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to free a data buffer has detected a serious problem. The buffer pool identified in the buffer header indicates that no buffers are currently allocated. Either the data buffer's header contains invalid information, the target buffer pool is invalid or has been corrupted, or the data buffer has already been freed. Either a logic problem exists within EGPE, or more likely the buffer header or the buffer pool control block have been overwritten with bad data. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to free the data buffer is ignored. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing the corruption of storage areas. In addition, the node may experience storage shortages since the corrupted data buffer is lost.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to free a data buffer has detected a serious problem. The data buffer's header contains invalid information. The buffer type (the type of buffer pool the buffer was allocated from) is invalid. Either a logic problem exists within EGPE, or more likely the buffer header or the buffer pool control block have been overwritten with bad data. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to free the data buffer is ignored. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing the corruption of storage areas. In addition, the node may experience storage shortages since the corrupted data buffer is lost.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to allocate a data buffer has detected a serious problem. The specified buffer pool contains invalid information or the buffer pool is invalid. Either a logic problem exists within EGPE, the buffer pool control block have been overwritten with bad data, or the specified buffer pool has been freed. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to allocate the data buffer fails. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing the corruption of storage areas. In addition, communications with other nodes may be disrupted because the requested data buffer could not be allocated.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to allocate a data buffer has detected a serious problem. The specified buffer pool control block contains invalid information. The type of buffer pool indicated in the control block is invalid. Either a logic problem exists within EGPE, or more likely the buffer pool control block have been overwritten with bad data. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to allocate the data buffer fails. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing the corruption of storage areas. In addition, communications with other nodes may be disrupted because the requested data buffer could not be allocated.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to allocate a data buffer has detected a serious problem. The parameters specified on the request are inconsistent. A demand buffer was requested, but the specified buffer size is invalid. Demand buffers are allocated on request (not from a buffer pool) and the size of the requested buffer must be specified on the request. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to allocate the data buffer fails. Processing continues, but the behaviour of the node will probably be erratic. Communications with other nodes may be disrupted because the requested data buffer could not be allocated.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE.
A request to allocate a data buffer has detected a serious problem. An internal routine was invoked with an invalid parameter. The invoked routine is used to take one of the available buffers in the buffer pool and mark it as allocated, but the specified buffer pool does not have any available buffers. An internal code problem exists within EGPE.
Function Degradation: The request to allocate the data buffer fails. Processing continues, but the behaviour of the node will probably be erratic. Communications with other nodes may be disrupted because the requested data buffer could not be allocated.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to allocate a data buffer has detected a serious problem. The specified buffer pool contains invalid information or the buffer pool is invalid. Either a logic problem exists within EGPE, the buffer pool control block have been overwritten with bad data, or the specified buffer pool has been freed. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to allocate the data buffer fails. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing the corruption of storage areas. In addition, communications with other nodes may be disrupted because the requested data buffer could not be allocated.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: Not used yet.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: Not used yet.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to allocate a data buffer has detected a serious problem. The specified buffer pool control block contains invalid information or cannot be used. The type of buffer pool indicated in the control block is invalid or specifies a type of buffer pool that cannot be used by the requested function (asynchronously allocate a buffer). Either a logic problem exists within EGPE, or more likely the buffer pool control block have been overwritten with bad data. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to allocate the data buffer fails. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing the corruption of storage areas. In addition, communications with other nodes may be disrupted because the requested data buffer could not be allocated.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: Not used yet.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: A software problem exists within pSNA or EGPE.
A request to transfer data from one data buffer to a data buffer in a different buffer pool failed because one or more parameters specified on the request are invalid. The amount of data to be transferred exceeds the size of the target data buffer. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to transfer the data fails. Processing continues, but the behaviour of the node will probably be erratic. Communications with other nodes may be disrupted because the data could not be placed in the correct buffer pool.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within pSNA or EGPE.
A request to transfer data from one data buffer to a data buffer in a different buffer pool failed because one or more parameters specified on the request are invalid. The specified amount of data to be transferred exceeds the size of the source data buffer. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to transfer the data fails. Processing continues, but the behaviour of the node will probably be erratic. Communications with other nodes may be disrupted because the data could not be placed in the correct buffer pool.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within pSNA or EGPE.
A request to transfer data from one data buffer to a demand data buffer failed because one or more parameters specified on the request are invalid. The target data buffer is a demand buffer. Demand buffers are allocated on request (not from a buffer pool) and the size of the requested buffer is specified on the request. The amount of data to be transferred exceeds the requested size of the target data buffer. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to transfer the data fails. Processing continues, but the behaviour of the node will probably be erratic. Communications with other nodes may be disrupted because the data could not be placed in the correct buffer pool.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within pSNA or EGPE.
A request to transfer data from one data buffer to a data buffer in a different buffer pool failed because the specified target buffer pool control block is invalid. The type of buffer pool indicated in the control block is invalid. Either a logic problem exists within EGPE, or more likely the buffer pool control block have been overwritten with bad data. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to transfer the data fails. Processing continues, but the behaviour of the node will probably be erratic. Communications with other nodes may be disrupted because the data could not be placed in the correct buffer pool.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within pSNA or EGPE.
A request to transfer data from one data buffer to a data buffer in a different buffer pool was successful, but the source data buffer could not be freed. The buffer type indicator (which specifies type of buffer pool the buffer was allocated from) in the source data buffer is invalid. Either a logic problem exists within EGPE, or more likely the buffer header has been overwritten with bad data. An internal code problem exists within pSNA or EGPE.
Function Degradation: The data is transferred successfully, but the request to free the source data buffer is ignored. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing the corruption of storage areas. In addition, the node may experience storage shortages since the corrupted data buffer is lost.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within pSNA or EGPE.
A request to transfer data from one data buffer to a data buffer in a different buffer pool failed because the specified target buffer pool control block is invalid. Either a logic problem exists within EGPE, the buffer pool control block have been overwritten with bad data, or the buffer pool has been freed. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to transfer the data fails. Processing continues, but the behaviour of the node will probably be erratic. Communications with other nodes may be disrupted because the data could not be placed in the correct buffer pool.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: EGPE detected an error while attempting to transfer data from one data buffer to a data buffer in a different buffer pool. The target buffer pool does not have enough buffers available to process the request. This condition should not occur. An internal code problem exists within pSNA or a serious memory shortage exists.
Function Degradation: The request to transfer the data fails. Processing continues, but the behaviour of the node will probably be erratic. Communications with other nodes may be disrupted because the data could not be placed in the correct buffer pool.
Customer Action: Verify that a memory shortage did not cause the problem.
If not related to a memory shortage, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement a code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to create a buffer pool has detected a serious problem. The parameters specified on the request are inconsistent. The specified buffer size is invalid for the requested type of buffer pool. For fixed and varying buffer pools, a non-zero buffer size must be specified. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to allocate the buffer pool fails. Processing continues, but the behaviour of the node will probably be erratic. Communications with other nodes will probably be disrupted because the requested buffer pool could not be created.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to create a buffer pool has detected a serious problem. The parameters specified on the request are inconsistent. The specified size of the buffer pool (e.g. number of buffers in the pool) is invalid for the requested type of buffer pool. For all types of buffer pools except varying buffer pools, a non-zero buffer pool size must be specified. For limited and rate limited buffer pools, a value of -1 is also allowed. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to allocate the buffer pool fails. Processing continues, but the behaviour of the node will probably be erratic. Communications with other nodes will probably be disrupted because the requested buffer pool could not be created.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to create a buffer pool has detected a serious problem. The parameters specified on the request are inconsistent. The specified size of the buffer pool (e.g. number of buffers in the pool) is invalid for the requested type of buffer pool. For all types of buffer pools except varying buffer pools, a non-zero buffer pool size must be specified. For limited and rate limited buffer pools, a value of -1 is also allowed. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to allocate the buffer pool fails. Processing continues, but the behaviour of the node will probably be erratic. Communications with other nodes will probably be disrupted because the requested buffer pool could not be created.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to create a buffer pool has detected a serious problem. The parameters specified on the request are inconsistent. The specified size of the buffer pool (e.g. number of buffers in the pool) is invalid for the requested type of buffer pool. For all types of buffer pools except varying buffer pools, a non-zero buffer pool size must be specified. For limited and rate limited buffer pools, a value of -1 is also allowed. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to allocate the buffer pool fails. Processing continues, but the behaviour of the node will probably be erratic. Communications with other nodes will probably be disrupted because the requested buffer pool could not be created.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to create a buffer pool has detected a serious problem. The specified type of buffer pool is not allowed. The request attempted to create a buffer pool containing demand buffers. Demand buffers are allocated on request and are not part of a buffer pool. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to allocate the buffer pool fails. Processing continues, but the behaviour of the node will probably be erratic. Communications with other nodes will probably be disrupted because the requested buffer pool could not be created.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A request to create a buffer pool has detected a serious problem. The specified type of buffer pool was invalid. The specified type is not an allowed buffer pool type. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to allocate the buffer pool fails. Processing continues, but the behaviour of the node will probably be erratic. Communications with other nodes will probably be disrupted because the requested buffer pool could not be created.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: Not used yet.
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to create a buffer pool has detected a serious problem. The parameters specified on the request are inconsistent. The request is trying to create a rate limited buffer pool. The only allowed value for the size of the buffer pool is -1, and the only allowed value for the size of the buffers in the pool is zero. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to allocate the buffer pool fails. Processing continues, but the behaviour of the node will probably be erratic. Communications with other nodes will probably be disrupted because the requested buffer pool could not be created.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to decrease the number of buffers in a buffer pool has detected a serious problem. The specified buffer pool is invalid. Either a logic problem exists within EGPE, or the buffer pool control block have been overwritten with bad data. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to decrease the size of the buffer pool is ignored. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing the corruption of storage areas. In addition, the node may experience storage shortages since the corrupted buffer pool (along with all of its associated data buffers) is lost.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to decrease the number of buffers in a buffer pool has detected a serious problem. The parameter used to indicate how many buffers should be removed from the buffer pool is invalid. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to decrease the size of the buffer pool is ignored. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing the corruption of storage areas. In addition, the node may experience storage shortages since the requested number of buffers are not freed.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to decrease the number of buffers in a buffer pool has detected a serious problem. The operation is not allowed on the specified buffer pool. Only fixed and varying buffer pools can have their sizes (number of buffers in the pool) decreased. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to decrease the size of the buffer pool is ignored. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing the corruption of storage areas. In addition, the node may experience storage shortages since the requested number of buffers are not freed.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to free (destroy) a buffer pool has detected a serious problem. The number of buffers in the pool (as indicated by the buffer pool control block) does not match the actual number of buffers in the pool. This condition should not occur. Either a logic problem exists within EGPE, or the buffer pool control block have been overwritten with bad data. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to free the buffer pool is ignored. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing the corruption of storage areas. In addition, the node may experience storage shortages since the some data buffers may not be freed.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within pSNA or EGPE.
A request to transfer data from one data buffer to a data buffer in a different buffer pool failed because one or more parameters specified on the request are invalid. The amount of data to be transferred exceeds the size of the target data buffer. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to transfer the data fails. Processing continues, but the behaviour of the node will probably be erratic. Communications with other nodes may be disrupted because the data could not be placed in the correct buffer pool.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within pSNA or EGPE.
A request to transfer data from one data buffer to a data buffer in a different buffer pool was successful, but the source data buffer could not be freed. The buffer type indicator (which specifies type of buffer pool the buffer was allocated from) in the source data buffer is invalid. Either a logic problem exists within EGPE, or more likely the buffer header has been overwritten with bad data. An internal code problem exists within pSNA or EGPE.
Function Degradation: The data is transferred successfully, but the request to free the source data buffer is ignored. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing the corruption of storage areas. In addition, the node may experience storage shortages since the corrupted data buffer is lost.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within pSNA or EGPE.
A request to transfer data from one data buffer to a data buffer in a different buffer pool failed because the specified source buffer is invalid. Either the data buffer has been overwritten with bad data or a data buffer that has already been freed is being used. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to transfer the data fails. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing the corruption of storage areas or the node is attempting to free memory that has already been freed. Communications with other nodes may be disrupted because the data could not be placed in the correct buffer pool.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within pSNA or EGPE.
A request to transfer data from one data buffer to a data buffer in a different buffer pool failed because the specified target buffer is invalid. Either the data buffer has been overwritten with bad data or a data buffer that has already been freed is being used. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to transfer the data fails. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing the corruption of storage areas or the node is attempting to free memory that has already been freed. Communications with other nodes may be disrupted because the data could not be placed in the correct buffer pool.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within pSNA or EGPE.
A request to transfer data from one data buffer to a data buffer in a different buffer pool failed because the specified target buffer pool control block is invalid. The specified buffer pool cannot be used for the requested type of transfer (data cannot be transferred into a rate limited buffer pool). An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to transfer the data fails. Processing continues, but the behaviour of the node will probably be erratic. Communications with other nodes may be disrupted because the data could not be placed in the correct buffer pool.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within pSNA or EGPE.
A request to segment the data contained in a data buffer (either split the data into segments or combine the data into existing data segments) failed because either the specified data buffer or buffer pool control block is invalid. Possible causes are:
Function Degradation: The request to segment the data fails. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing the corruption of storage areas or the usage of freed data areas. Communications with other nodes will probably be disrupted because the data could not be successfully segmented into the required size.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within pSNA or EGPE.
A request to segment the data contained in a data buffer (either split the data into segments or combine the data into existing data segments) failed because one or more of the parameters specified on the request are invalid. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to segment the data fails. Processing continues, but the behaviour of the node will probably be erratic. Communications with other nodes will probably be disrupted because the data could not be successfully segmented into the required size.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within pSNA or EGPE.
A request to segment the data contained in a data buffer (either split the data into segments or combine the data into existing data segments) failed because the segmented data could not be transferred into the specified target buffer pool. One or more of the following log entries should also be created when this error occurs:
Function Degradation: The request to segment the data fails. Processing continues, but the behaviour of the node will probably be erratic. Communications with other nodes will probably be disrupted because the data could not be successfully segmented into the required size.
Customer Action: Refer to related log entries and messages for more information and other recommended actions.
Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within pSNA or EGPE.
A request to segment the data contained in a data buffer (either split the data into segments or combine the data into existing data segments) encountered an error while copying the data from the source data buffer into a target buffer. The actual number of bytes copied did not match the requested number of bytes to be copied. An internal code problem exists within pSNA or EGPE.
It is possible that this condition may not cause any external processing problems. The node may be able to recover from the condition and continue normal processing.
Function Degradation: The request to segment the data continues. The behaviour of the node may be unpredictable, and communications with other nodes may be disrupted because the data could not be successfully segmented into the required size. It is possible that the data was moved correctly, and the node will continue nor processing with no notice-able degradation in performance.
Customer Action: It is possible that the node will continue to work correctly when this problem occurs. If it appears to be behaving satisfactorily, no immediate action is required.
If the processing of the node is affected or the problem occurs frequently, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within pSNA or EGPE.
A request to segment the data contained in a data buffer (either split the data into segments or combine the data into existing data segments) encountered an error while moving the data from the source data buffer into a target buffer. An internal code problem exists within pSNA or EGPE.
It is possible that this condition may not cause any external processing problems. The node may be able to recover from the condition and continue normal processing.
Function Degradation: The request to segment the data continues. The behaviour of the node may be unpredictable, and communications with other nodes may be disrupted because the data could not be successfully segmented into the required size. It is possible that the data was moved correctly, and the node will continue nor processing with no notice-able degradation in performance.
Customer Action: It is possible that the node will continue to work correctly when this problem occurs. If it appears to be behaving satisfactorily, no immediate action is required.
If the processing of the node is affected or the problem occurs frequently, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within pSNA or EGPE.
A request to free (destroy) a buffer pool has detected a serious problem. A request was made to free a buffer pool while there were one or more EGPE processes or pSNA components still using the buffer pool. This condition should not occur. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to free the buffer pool is ignored. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing one or more components within the node to become out-of-sync with one another. In addition, the node may experience storage shortages since the some data buffers may not be freed.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to reset the number of buffers in a buffer pool to its initial, current, or assigned value has detected a serious problem. The specified buffer pool is invalid. Either a logic problem exists within EGPE, or the buffer pool control block have been overwritten with bad data. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to reset the size of the buffer pool is ignored. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing the corruption of storage areas. Communications with other nodes may be disrupted because the number of buffers in a buffer pool could not be set to the desired value.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to reset the number of buffers in a buffer pool to its initial, current, or assigned value has detected a serious problem. One of the parameters specified on the request is invalid. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to reset the size of the buffer pool is ignored. Processing continues, but the behaviour of the node will probably be erratic. Communications with other nodes may be disrupted because the number of buffers in a buffer pool could not be set to the desired value.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to reset the number of buffers in a buffer pool to its current value has detected a serious problem. The operation is not allowed for the specified buffer pool. Only fixed or varying buffer pools can have the number of buffers contained by the pool reset to the current size of the pool. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to reset the size of the buffer pool is ignored. Processing continues, but the behaviour of the node will probably be erratic. Communications with other nodes may be disrupted because the number of buffers in a buffer pool could not be set to the desired value.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to reset the number of buffers in a buffer pool to its assigned value has detected a serious problem. The operation is not allowed for the specified buffer pool. Only varying buffer pools can have the number of buffers contained by the pool reset to the assigned size of the pool. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to reset the size of the buffer pool is ignored. Processing continues, but the behaviour of the node will probably be erratic. Communications with other nodes may be disrupted because the number of buffers in a buffer pool could not be set to the desired value.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE (the buffer manager).
A request to send an IPM (SNA pacing message) after an appropriate delay has detected a serious problem. The request is used to schedule the sending of an IPM when the overall status of the buffers in the node reaches a certain value. The request is invalid because the specified buffer pool has already been scheduled. This condition should not occur. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to schedule the sending of the IPM for the specified buffer pool is ignored. Processing continues, but the behaviour of the node will probably be erratic. Communications with other nodes may be disrupted because the required pacing messages may not be sent to the partner node.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to adjust the scheduled delay period for sending an IPM (SNA pacing message) has detected a serious problem. The request is used to react to an indication from a remote node that the remote node is congested by adjusting the amount of time to wait before sending an IPM. The specified buffer pool is invalid. The buffer pool control block have been overwritten with bad data, the buffer pool has been freed, or the operation is not allowed for the specified buffer pool. This operation is only allowed for fixed or varying buffer pools. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to adjust the delay period for the specified buffer pool is ignored. Processing continues, but the behaviour of the node will probably be erratic. Communications with other nodes may be disrupted because the required pacing messages may not be sent to the partner node at the appropriate time.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to change the number of buffers in a buffer pool has detected a serious problem. The specified buffer pool is invalid. Either a logic problem exists within EGPE, or the buffer pool control block have been overwritten with bad data. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to change the size of the buffer pool is ignored. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing the corruption of storage areas. Communications with other nodes may be disrupted because the number of buffers in a buffer pool could not be set to the desired value.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to change the number of buffers in a buffer pool has detected a serious problem. The operation is not allowed for the specified buffer pool. Only limited, rate limited, or permanent buffer pools can have the number of buffers contained by the pool adjusted. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to change the size of the buffer pool is ignored. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing the corruption of storage areas. Communications with other nodes may be disrupted because the number of buffers in a buffer pool could not be set to the desired value.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE or pSNA.
A request to change the number of buffers in a buffer pool has detected a serious problem. The operation is not allowed for the specified buffer pool. The buffer pool was created with no defined limit for the number of buffers allowed in the pool, and the limit cannot be adjusted. An internal code problem exists within pSNA or EGPE.
Function Degradation: The request to change the size of the buffer pool is ignored. Processing continues, but the behaviour of the node will probably be erratic. The node has a serious code problem causing the corruption of storage areas. Communications with other nodes may be disrupted because the number of buffers in a buffer pool could not be set to the desired value.
Customer Action: Call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within pSNA or EGPE.
A scheduled buffer transfer into a rate limited pool failed. The data buffer could not be transferred into the rate limited pool. This should not occur, since the transfer was scheduled to occur when the transfer should have been allowed. An internal code problem exists within pSNA or EGPE.
It is probable that this condition will not cause any external processing problems. The node will recover from the condition be re-scheduling the buffer transfer and continue normal processing.
Function Degradation: The node should continue normal processing. The buffer transfer is re-scheduled. Communications with other nodes may be slightly disrupted because the data was not transferred (and processed) when expected. The only notice-able affect should be a delay in the processing of some messages.
Customer Action: The node should continue to work correctly when this problem occurs. If it appears to be behaving satisfactorily, no immediate action is required.
If the processing of the node is affected or the problem occurs frequently, call service with the code point and error description. Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: A software problem exists within pSNA or EGPE. A should-not-occur condition has been encountered. An internal code problem exists within pSNA or EGPE.
Function Degradation: Processing continues in non-debug mode. Unexpected results will probably follow this problem, since the current request will probably fail and there are software errors being encountered within pSNA.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
General error log events for the extended generalized programming environment (EGPE).
Description: Dummy event used internally for managing the event category (enabling and disabling the events in the category).
Function Degradation: None.
Customer Action: None.
System Developer Action: None.
Additional Data: Has the following format:
Description: EGPE could not establish a dialog with another EGPE in a different co-processor or with a non-EGPE process providing system services needed by EGPE or pSNA. Dialogs are typically used to exchange messages between co-processors or system processes within a system. In this case, the dialog specified in the request is not available (or does not exist). An internal code problem exists within pSNA (EGPE).
Function Degradation: Communications with the indicated EGPE or service tower cannot be established. Processing continues, but the behaviour of the node is unpredictable, since communications with the partner EGPE or system process is impossible. The detecting EGPE system cannot exchange any information with the partner EGPE or request services from the targeted system process. Components and services provided by the target EGPE or system process are not available. It could even result in communication errors, since the partner EGPEs may provide outboard routing services.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: EGPE could not establish a dialog with another EGPE in a different co-processor or with a non-EGPE process providing system services needed by EGPE or pSNA. Dialogs are typically used to exchange messages between co-processors or system processes within a system. In this case, the dialog specified in the request is not available (or does not exist). An internal code problem exists within pSNA (EGPE).
Function Degradation: The EGPE process is abnormally terminated (abended), The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: Call service with the code point and error description.
EGPE should create a process abend file containing a snapshot of the pSNA (EGPE) storage areas when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: The attempt to send an internal dialog "pacing" message (pacing response) failed.
EGPE could not send an internal dialog pacing message to another EGPE (in another co-processor) or to a non-EGPE system process. Pacing messages are used internally within dialogs to control the amount of data exchanged within the dialog. The message that failed was a pacing response message, which are used to indicate that the other process can now send more data. The possible causes of this problem are:
Function Degradation: The message is lost. Processing continues, but the behaviour of the node is unpredictable, since the other process is probably waiting to send more data to the detecting process. It could even result in communication errors, since the data being held may be actual communications data.
The related dialog is ended, so communications between the two EGPE systems or between EGPE and the system process are no longer possible using this dialog. All services provided by the partner EGPE or system process are no longer available to the detecting EGPE system.
Customer Action: Try and determine if the problem was caused by a system and/or machine failure by investigating any related error information (such as additional log entries). If a problem is discovered in these systems, use the appropriate procedures to resolve the problem. If it appears that all other systems are functioning correctly, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A software problem exists within EGPE.
EGPE received a heartbeat request from a dialog that does not support heartbeats. Heartbeats are used within dialogs to verify that both sides of a dialog are still available when no data is being exchanged. In this case, a heartbeat message was received, but the receiving dialog is not supposed to be sending or receiving heartbeat messages. An internal code problem exists within pSNA (EGPE).
Function Degradation: The message is ignored. Processing continues, but the behaviour of the node is unpredictable, since the partner EGPE or system process is probably expecting a heartbeat and will not send any new messages until a heartbeat response is received.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE.
EGPE received an unexpected internal dialog pacing message from a dialog that does not support heartbeats. Pacing messages are used internally within dialogs to control the amount of data exchanged within the dialog. An internal code problem exists within pSNA (EGPE).
Function Degradation: The message is ignored. Processing continues, but the behaviour of the node may be unpredictable, since the partner EGPE or system process is out-of-sync with the local EGPE.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: A software problem exists within EGPE.
EGPE detected an error while receiving a segmented message from another EGPE or system process. The message was sent in two or more segments, and the receiving EGPE either did not receive one of the segments, or the segments were received out of order. The possible causes of this problem are:
Function Degradation: Processing of the message continues, but the behaviour of the node is unpredictable, since the received message is garbled. The message is probably a request from a component for services or information from another component within the communications sub-system. It could even result in communication errors, since the lost message may have contained actual communications data.
Customer Action: Try and determine if the problem was caused by a system and/or machine failure by investigating any related error information (such as additional log entries). If a problem is discovered in these systems, use the appropriate procedures to resolve the problem. If it appears that all other systems are functioning correctly, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A software problem exists within EGPE.
EGPE detected an error while receiving a segmented message from another EGPE or system process. The message was sent in two or more segments, and the receiving EGPE either did not receive one of the segments, or the segments were received out of order. The possible causes of this problem are:
Function Degradation: The received message is not converted. Processing continues, but the behaviour of the node is unpredictable, since the received message may not be in the correct format to be processed by the local EGPE.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The attempt to send an internal dialog "pacing" message (pacing response) failed.
EGPE could not send a message to another EGPE (in another co-processor) or to a non-EGPE system process. The possible causes of this problem are:
Function Degradation: The message is lost. Processing continues, but the behaviour of the node is unpredictable. The lost message is probably a request or reply from a component for services or information from another component within the communications sub-system. It could even result in communication errors, since the lost message may have contained actual communications data.
Customer Action: Try and determine if the problem was caused by a system and/or machine failure by investigating any related error information (such as additional log entries). If a problem is discovered in these systems, use the appropriate procedures to resolve the problem. If it appears that all other systems are functioning correctly, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: The attempt to establish a timer used to control the sending of heartbeat requests within a dialog failed. Dialogs are used by EGPE to communicate between processes in different processors, as well as communicate between EGPE processes and non-EGPE processes.
EGPE could not set a timer used to control the interval between the transmission of heartbeat requests in a dialog. Heartbeats are used within dialogs to verify that both sides of a dialog are still available when no data is being exchanged.
Function Degradation: The main EGPE dialog control process is abnormally terminated (abended). Dialog control functions (such as starting and stopping dialogs, pacing, and heartbeats) are lost. The loss of these services is a severe problem that eventually cause the entire node to terminate or severely degrade the capabilities of the node. The possible causes of this problem are:
Customer Action: Try and determine if the problem was caused by a system and/or machine failure by investigating any related error information (such as additional log entries). If a problem is discovered in these systems, use the appropriate procedures to resolve the problem. If it appears that all other systems are functioning correctly, call service with the code point and error description.
EGPE should create a process abend file containing a snapshot of the pSNA (EGPE) storage areas when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A software problem exists within EGPE.
EGPE does not recognize a inter-layer transport message received from another EGPE or non-EGPE system process. These messages are typically used to exchange messages between co-processors within a system. An internal code problem exists within pSNA (EGPE).
Function Degradation: The message is ignored. Processing continues, but the behaviour of the node is unpredictable, since the ignored message is probably a request from a component for services or information from another component within the communications sub-system.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: EGPE could not determine the current status of the internal buffer pool it uses to exchanges messages with different co-processors or non-EGPE processes. Dialogs are typically used to exchange messages between co-processors or system processes within a system, and the EGPE prevents one process from over-running another process by pacing the messages sent via dialogs. The request to determine the current status of the paced buffer pools returned an invalid value. An internal code problem exists within pSNA (EGPE).
Function Degradation: The EGPE process is abnormally terminated (abended), The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: Call service with the code point and error description.
EGPE should create a process abend file containing a snapshot of the pSNA (EGPE) storage areas when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Description: The attempt to send an internal dialog "pacing" message (pacing response) failed.
EGPE could not send an internal dialog pacing message to another EGPE (in another co-processor) or to a non-EGPE system process. Pacing messages are used internally within dialogs to control the amount of data exchanged within the dialog. The message that could not be sent is a pacing response message, which is used to indicate that the other process can now send more data.
The message could not be sent because the dialog partner currently is unable to receive any messages (its pacing window is slammed). The most probably cause of this problem is a serious memory shortage problem exists. In most cases, the node will eventually recover from this situation as messages are processed and storage is freed.
Function Degradation: The pacing response cannot be sent, but the node continues to process the received message. Performance of the node might be temporarily degraded. The node should eventually recover from this situation.
Customer Action: Unless the problem occurs repeatedly, or the node cannot satisfactorily recover, no action is required. To prevent the problem from re-occurring, increase the amount of memory available to the pSNA node if a memory shortage is suspected. If it appears that there is storage available for use by the node, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A dialog partner has informed the receiving process it is temporarily unable to receive any more messages (it slammed its pacing window). The receiving process will hold all messages destined for the congested process until the process indicates it is able to receive more data. The most probably cause of this problem is a serious memory shortage problem exists. In most cases, the node will eventually recover from this situation as messages are processed and storage is freed.
Function Degradation: Processing continues, but the performance of the node may be temporarily degraded, since the receiving process is probably waiting to send more data to the congested process. It could even result in communication performance problems, since the data being held may be actual communications data. The node should eventually recover from this situation.
Customer Action: Unless the problem occurs repeatedly, or the node cannot satisfactorily recover, no action is required. To prevent the problem from re-occurring, increase the amount of memory available to the pSNA node if a memory shortage is suspected. If it appears that there is storage available for use by the node, call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Debug and determine what caused the failure to occur. Implement a code fix if a software problem is discovered within pSNA. If a problem is discovered in the underlying operating system or processor, notify the appropriate service personnel.
Additional Data: Has the following format:
Description: A software problem exists within EGPE. (AIX ONLY)
EGPE does not recognize a inter-layer transport message received from another EGPE or adapter services (ADS). These messages are typically used to request the creation of EGPE in a co-processor. An internal code problem exists within pSNA (EGPE).
Function Degradation: The message is ignored. Processing continues, but the behaviour of the node is unpredictable, since the ignored message is probably a request from a component for services or information from another component within the communications sub-system.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service. Be sure to dump all related co-processors that are executing pSNA components.
System Developer Action: Debug and determine what caused the failure to occur. Isolate and implement a code fix.
Additional Data: Has the following format:
Description: The attempt to send an internal message (IPS) failed. The target process is not a valid or active EGPE process. An internal code problem exists within pSNA.
Function Degradation: The message is lost. Processing continues, but the behaviour of the node is unpredictable. The lost message is probably a request or reply from a component for services or information from another component within the communications sub-system. It could even result in communication errors, since the lost message may have contained actual communications data.
Customer Action: Call service with the code point and error description.
Try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
*For 3746 this Logevent may be created when a new configuration is activated on a previously active machine. This is related to a timing window between the deactivation of APPN CP in the NNP and the APPN tower in the different processors of the 3746. where the queued messages are unable to be sent/received to target processes that are on the way to be deactivate.
Ignore this Logevent if in the phase of node reactivation.
Additional Data: Has the following format:
Description: An EGPE process terminated, but with a non-zero termination code.
An EGPE process terminated because it detected an unrecoverable error. The cause of the error is indicated by the Pexit completion code. Lists of these codes can be found in the following header files:
Function Degradation: The EGPE process is terminated. The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: Call service with the code point and error description.
EGPE should create a process abend file containing a snapshot of the pSNA (EGPE) storage areas when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Current State %4 for %5 sec, inuse= %6 bytes;
event_peak_use= %7, min use= %8, node_peak_use= %9;
node_OK_cnt= %10, event_OK_cnt= %11, last_OK_for %12, avg_OK %13 sec;
node_Cons_cnt= %14, event_Cons_cnt= %15, last_Cons %16, avg_Cons %17 sec;
node_Crit_cnt= %18, event_Crit_cnt= %19, last_Crit %20, avg_Crit %21 sec.
Description: A software problem exists within EGPE or pSNA.
A request to allocate internal EGPE control areas (queue elements) failed. The storage area used to control the usage of the queue elements has been overwritten. An internal code problem exists within pSNA or EGPE.
Function Degradation: The EGPE process is abnormally terminated (abended), The consequences of the process terminating depend on the process that failed. Most EGPE and pSNA process failures are severe problems that eventually cause the entire node to terminate or severely degrade the capabilities of the node.
Customer Action: Call service with the code point and error description.
EGPE should create a process abend file containing a snapshot of the pSNA (EGPE) storage areas when the problem was detected. Supply this process abend file to service. If the process abend file cannot be found, try and dump the pSNA storage when the problem occurs and supply the dump information to service.
System Developer Action: Isolate and implement code fix.
Additional Data: Has the following format:
Current State %4 for %5 sec, inuse= %6 bytes;
event_peak_use= %7, min use= %8, node_peak_use= %9;
node_OK_cnt= %10, event_OK_cnt= %11, last_OK_for %12, avg_OK %13 sec;
node_Cons_cnt= %14, event_Cons_cnt= %15, last_Cons %16, avg_Cons %17 sec;
node_Crit_cnt= %18, event_Crit_cnt= %19, last_Crit %20, avg_Crit %21 sec.
Description: Memory congestion may indicate that an operational problem exists for APPN.
AMOUNT OF TRAFFIC GREATER THAN APPN NETWORK WAS DESIGNED TO SUPPORT
NEW NODE ADDED TO NETWORK WITHOUT RECONFIGURING ALERT SENDER'S APPN MEMORY
INSUFFICIENT APPN MAIN MEMORY CONFIGURED -- main memory Events
INSUFFICIENT APPN BUFFER MEMORY CONFIGURED -- buffer memory Events
FAILURE IN APPN NETWORK
Function Degradation: APPN is running with less than sufficient memory for normal operation. The consequences may be terminating sessions or rejection of new sessions.
Customer Action: The user should consider configuring APPN to run with more memory of the type having congestion.
The problem could be caused by failures elseware in the network forcing excessive/prolonged queuing within this node or excess traffic through this node beyond the present capacity of the network to sustain this level of throughput. The user should take the total system situation into account in addition to the data provided via these logEvents, to determine the best course of action for avoiding this problem in the future.
System Developer Action: Isolate problem and implement configuration changes, etc.