Table Of Contents
System Error Messages
Accounting Messages
TACACS+ authentication, authorization, and accounting security accounting error messages
Error Message%AAAA-3-BADSTR : Bad accounting data: [chars]
Explanation During AAA accounting operations, the internal database of accounting information for a user was found to be corrupt. In all cases, this indicates an internal software error, and that accounting information for a particular user session has been lost.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%AAAA-3-DROPACCT : accounting record dropped: [chars]-[chars] [chars] [chars]
Explanation An attempt to send an accounting record to a server failed.
Recommended Action Check that the server (TACACS+ or RADIUS) is operational. Next, check the NAS is configured properly. Finally, check that the NAS can communicate with the server.
Error Message%AAAA-3-LOSTTIMER : Lost periodic accounting timer for user [chars]. Restarting timer...
Explanation Somehow, the periodic timer associated with this ustruct has been lost.
Recommended Action Re-allocate and restart a timer.
Error Message%AAAA-3-MKTIMERFAIL : Failed to create periodic accounting timer for user [chars]. This user may not generate periodic accounting records.
Explanation Failed to malloc a timer struct for periodic accounting.
Recommended Action Free up some memory and have the user re-authenticate.
Error Message%AAAA-3-NULUSR : accounting for null user
Explanation This message indicates an internal software error. During shutdown of a line or interface, the system tried to send accounting information via AAA, but could not find the user to which the accounting information belonged. The most likely reason for this error is trying to do accounting twice for the same event. This error message can occur without any loss of accounting information.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%AAAA-3-PERIODICFORKFAIL : Failed to start periodic accounting process. Periodic accounting records may not be sent.
Explanation Failed to create the periodic accounting process.
Recommended Action Free up some memory.
Error Message%AAAA-3-RELOGIN : sanity check in re-login [chars] to [chars]
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
AIP Error Messages
ATM Interface Processor error messages
Error Message%AIP-3-AIPFAILSETUPVC : [chars] Failed to setup vc [dec] (Cause: [chars])
Explanation The AIP driver failed to set up a virtual circuit.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AIP-3-AIPFAILSETUPVCAVG : Interface [chars], Failed to setup vc [dec] (Cause: [chars]) Expected range [[dec] .. [dec]]Kbps for AIP Average Rate Metering. Average Rate=Peak Rate= [dec] Kbps turns Average Rate Metering OFF
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
ALIGN Error Messages
The ALIGN facility controls a feature in reduced instruction-set computer (RISC)-processor-based Cisco products that identifies software in need of memory use optimization.
Error Message%ALIGN-3-CORRECT : Alignment correction made at 0x[hex] reading/writing 0x[hex]
Explanation A software component within the router needs memory optimization.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%ALIGN-3-FULL : Alignment log is full - no new entries will be recorded
Explanation The router identified more software components in need of memory optimization than it can record.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%ALIGN-3-READEXCEPTION : Warning : read access failed, still continuing
Explanation A Cisco LS1010 read access failure did not cause a crash. This is a result of either a bad resister value in ASP version 3.3 or less, or a problem in the hardware.
Recommended Action If the ASP version is 3.3 or higher, report it to your technical support representative.
Error Message%ALIGN-3-SPURIOUS : Spurious memory access made at 0x[hex] reading 0x[hex]
Explanation An error was identified (and temporarily corrected) within a software component in the router.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
AMDP2_FE Error Messages
Presidio Ethernet and Laguna Fast Ethernet error messages
Error Message%AMDP2_FE-4-BABBLE : AMDP2/FE([dec]/[dec]), Babble error
Explanation The transmitter has been on the channel longer than the time taken to transmit the largest frame.
Recommended Action The system should recover. No action is required.
Error Message%AMDP2_FE-5-COLL : AMDP2/FE([dec]/[dec]), Excessive collisions, TDR=[dec], TRC=[dec]
Explanation Ethernet/Fast Ethernet is seeing multiple collisions. This may occur under heavy loads.
Recommended Action The system should recover. No action is required.
Error Message%AMDP2_FE-1-DISCOVER : Only found [dec] interfaces on bay [dec], shutting down bay
Explanation The software could not identify the interface card.
Recommended Action Power down, reseat the interface card, and reboot. If the message recurs, call your technical support representative for assistance.
Error Message%AMDP2_FE-1-INITFAIL : AMDP2/FE([dec]/[dec]), Init failed, CSR[dec]=0x[hex]
Explanation The software failed to initialize/restart an Ethernet/Fast Ethernet interface.
Recommended Action Clear the interface. If the message recurs, call your technical support representative for assistance.
Error Message%AMDP2_FE-5-LATECOLL : AMDP2/FE([dec]/[dec]), Late collision
Explanation Late collisions occurred on the Ethernet/Fast Ethernet interface.
Recommended Action If the interface is Fast Ethernet, verify that both peers are in the same duplex mode. For regular Ethernet, the system should recover. No action is required.
Error Message%AMDP2_FE-5-LOSTCARR : AMDP2/FE([dec]/[dec]), Lost carrier. Transceiver problem?
Explanation The cable and/or transceiver is not connected.
Recommended Action Connect the cable and/or transceiver.
Error Message%AMDP2_FE-1-MEMERR : AMDP2/FE([dec]/[dec]), Memory error, CSR[dec]=0x[hex]
Explanation The interface could not access system resources for a long time. This problem may occur under very heavy loads.
Recommended Action The system should recover. No action is required. If the message recurs, call your technical support representative for assistance.
Error Message%AMDP2_FE-2-NOISL : Interface [chars] does not support ISL
Explanation The interface cannot be configured as an ISL trunk.
Recommended Action Check the configuration.
Error Message%AMDP2_FE-1-NOMII : AMDFE([dec]/[dec]),MII Interface transceiver not connected
Explanation The MII transceiver was disconnected while the MII port was selected.
Recommended Action Connect the transceiver and enter the shutdown and no shutdown commands for the interface in the configuration menu.
Error Message%AMDP2_FE-3-NOTAMDP2 : Device reported [hex]
Explanation The software could not recognize the interface chips.
Recommended Action Power down, reseat the interface card, and reboot. If the message recurs, call your technical support representative for assistance.
Error Message%AMDP2_FE-3-OVERFLO : AMDP2/FE([dec]/[dec]), Receive overflow
Explanation While receiving a frame, the controller chip's local buffer transmitted insufficient data because data could not be transferred to DRAM fast enough to keep pace with its input rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
Error Message%AMDP2_FE-3-OWNERR : AMDP2/FE([dec]/[dec]), Buffer ownership error, pak=0x[hex]
Explanation The software detected an error in descriptor ownership.
Recommended Action Try a later version of the software. If the message recurs, call your technical support representative for assistance.
Error Message%AMDP2_FE-3-SPURIDON : AMDP2/FE([dec]/[dec]), Spurious IDON interrupt, CSR[dec]=0x[hex]
Explanation An illegal condition indicating initialization done has occurred.
Recommended Action Clear the interface. If this message recurs, call your technical support representative for assistance.
Error Message%AMDP2_FE-3-UNDERFLO : AMDP2/FE([dec]/[dec]), Transmit underflow
Explanation While transmitting a frame, the controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
APPN Error Messages
Advanced Peer-to-Peer Networking error messages
Error Message%APPN-3-APPN_ASSERT : APPN_ASSERT
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-Assert : Assertion failed in [chars] at line [dec]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BadIPSreceived : RTP received unrecognized IPS
Explanation A system component received an internal interprocess signal that it does not recognize or cannot process.
Recommended Action There is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BADJ02 : BADJ02: Pool [hex] is neither Limited nor Permanent
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BadMemory : Mfreeing bad storage: addr = [hex], header = [hex], size = [dec]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BadQCase : RTP is getting messages for the queues can't be processed
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BDLAY01 : BDLAY01: Delay ipm while previous delay ipm still pending; pool_p=[hex]
Explanation A request to send an IPM (SNA pacing message) after an appropriate delay has detected a serious problem.
Recommended Action 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. There is an internal code problem with the system. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BDST01 : BDST01: bfr_cnt for pool [hex] is [dec] after all buffers freed
Explanation A system software problem occurred.
Recommended Action 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. Either a logic problem exists, or the buffer pool control block has been overwritten with bad data. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BFRE01 : BFRE01:Buffer [hex] is invalid
Explanation A request to free a data buffer detected a serious problem.
Recommended Action The data buffer's header has been corrupted, or more likely, a data buffer that has already been freed is being freed again. There is an internal code problem with the system. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BFRE02 : BFRE02:Buffer [hex] points to an invalid pool [hex]
Explanation A request to free a data buffer detected a serious problem.
Recommended Action The data buffer's header contains invalid information, or the target buffer pool is invalid. Either a logic problem exists, or more likely, the buffer header or the buffer pool control block have been overwritten with bad data. There is an internal code problem with the system. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BFRE03 : BFRE03:Buffer [hex] points to pool [hex] with in_use_p of NULL
Explanation A request to free a data buffer detected a serious problem.
Recommended Action 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, or more likely, the buffer header or the buffer pool control block have been overwritten with bad data. There is an internal code problem with the system. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BFRE04 : BFRE04:Buffer [hex] is of an unknown type
Explanation A request to free a data buffer detected a serious problem.
Recommended Action The data buffer's header contains invalid information. The buffer type (the type of buffer pool from which the buffer was allocated) is invalid. Either a logic problem exists, or more likely, the buffer header or the buffer pool control block have been overwritten with bad data. There is an internal code problem with the system. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BFRE50 : BFRE50:Pool [hex] header was freed but wait list was not empty
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BGET01 : BGET01:Pool [hex] is invalid
Explanation A request to allocate a data buffer detected a serious problem.
Recommended Action The specified buffer pool contains invalid information, or the buffer pool is invalid. Either a logic problem exists, the buffer pool control block have been overwritten with bad data, or the specified buffer pool has been freed. There is an internal code problem with the system. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BGET02 : BGET02:Pool [hex] type is unknown
Explanation A request to allocate a data buffer detected a serious problem.
Recommended Action 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, or more likely, the buffer pool control block have been overwritten with bad data. There is an internal code problem with the system. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BGET03 : BGET03:Demand buffer size must be 0
Explanation A request to allocate a data buffer detected a serious problem.
Recommended Action 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. There is an internal code problem with the system. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BGET99 : BGET99:Pool [hex] has no free buffers
Explanation A request to allocate a data buffer detected a serious problem.
Recommended Action 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. There is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BGETAS01 : BGETAS01:Pool [hex] is invalid
Explanation A request to allocate a data buffer detected a serious problem.
Recommended Action The specified buffer pool contains invalid information, or the buffer pool is invalid. Either a logic problem exists, the buffer pool control block have been overwritten with bad data, or the specified buffer pool has been freed. There is an internal code problem with the system. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BGETAS02 : BGETAS02:Pool [hex] type is unknown
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BGETAS03 : BGETAS03:Demand buffer size must be 0
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BGETAS04 : BGETAS04:Invalid pool type
Explanation A request to allocate a data buffer detected a serious problem.
Recommended Action 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 to asynchronously allocate a buffer. Either a logic problem exists, or more likely, the buffer pool control block has been overwritten with bad data. There is an internal code problem with the system. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BGETAS99 : BGETAS99:Pool [hex] has no free buffers
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BQXFR01 : BQXFR01:Source data will not fit in target- source bfr=[hex], length is [dec], target length is [dec], byte_count is [dec]
Explanation A system software problem occurred.
Recommended Action 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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BQXFR02 : BQXFR02:Byte_count of [dec] exceeds source bfr ([hex]) length of [dec]
Explanation A system software problem occurred.
Recommended Action 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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BQXFR03 : BQXFR03: Byte_count of [dec] exceeds buf_size of [dec] - source bfr is [hex]
Explanation A system software problem occurred.
Recommended Action 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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BQXFR04 : BQXFR04: Pool type is unknown- target_pool_p is [hex]
Explanation A system software problem occurred.
Recommended Action 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, or more likely, the buffer pool control block has been overwritten with bad data. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BQXFR05 : BQXFR05: Source buffer [hex] type unknown
Explanation A system software problem occurred.
Recommended Action 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 from which the buffer was allocated) in the source data buffer is invalid. Either a logic problem exists, or more likely, the buffer header has been overwritten with bad data. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BQXFR06 : BQXFR06: Target pool [hex] is invalid
Explanation A system software problem occurred.
Recommended Action 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. A logic problem exists, the buffer pool control block has been overwritten with bad data, or the buffer pool has been freed. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BQXFR07 : BQXFR07: Target pool [hex] has no buffers available
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BRDLRECYC01 : BRDLRECYC01:Rate_Delay B_delay recycled
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BRST01 : BRST01:Pool [hex] is not valid
Explanation A request to reset the number of buffers in a buffer pool to its initial, current, or assigned value has detected a serious problem.
Recommended Action The specified buffer pool is invalid. Either a logic problem exists, or the buffer pool control block has been overwritten with bad data. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BRST02 : BRST02:new_size for pool [hex] is not valid
Explanation A request to reset the number of buffers in a buffer pool to its initial, current, or assigned value has detected a serious problem.
Recommended Action One of the parameters specified on the request is invalid. There is an internal code problem with the system. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BRST03 : BRST03:Pool [hex] is not Fixed or Varying
Explanation A request to reset the number of buffers in a buffer pool to its current value has detected a serious problem.
Recommended Action 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. There is an internal code problem with the system. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BRST04 : BRST04:Pool [hex] is not a Varying pool
Explanation A request to reset the number of buffers in a buffer pool to its current value has detected a serious problem.
Recommended Action 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. There is an internal code problem with the system. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BRSV01 : BRSV01: buf_size is [dec], Buffer size must be zero
Explanation A system software problem occurred.
Recommended Action A request to create a buffer pool has detected a serious problem. The parameters specified in the request are inconsistent. The specified buffer size is invalid for the requested type of buffer pool. For fixed and varying buffer pools, you must specify a nonzero buffer size. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BRSV02 : BRSV02:pool_size is [dec], Pool size must be 0
Explanation A system software problem occurred.
Recommended Action A request to create a buffer pool has detected a serious problem. The parameters specified in the request are inconsistent. The specified size of the buffer pool (the 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, you must specify a nonzero buffer pool size. For limited and rate-limited buffer pools, a value of -1 is also allowed. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BRSV03 : BRSV03:pool_size is [dec], Pool size must be 0
Explanation A system software problem occurred.
Recommended Action A request to create a buffer pool has detected a serious problem. The parameters specified in the request are inconsistent. The specified size of the buffer pool (the 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, you must specify a nonzero buffer pool size. For limited and rate-limited buffer pools, a value of -1 is also allowed. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BRSV04 : BRSV04: pool_size is [hex]
Explanation A system software problem occurred.
Recommended Action A request to create a buffer pool has detected a serious problem. The parameters specified in the request are inconsistent. The specified size of the buffer pool (the 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, you must specify a nonzero buffer pool size. For limited and rate-limited buffer pools, a value of -1 is also allowed. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BRSV05 : BRSV05: Cannot reserve a pool of Demand buffers..
Explanation A system software problem occurred.
Recommended Action 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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BRSV06 : BRSV06: Pool type is unknown..
Explanation A system software problem occurred.
Recommended Action The specified type of buffer pool was invalid. The specified type is not an allowed buffer pool type. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BRSV07 : BRSV07: Unknown Mstatus value..
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BRSV08 : BRSV08: Rate_Limited pool size must = -1 and buffer size = 0..
Explanation A system software problem occurred.
Recommended Action A request to create a buffer pool has detected a serious problem. The parameters specified in 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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BSEG01 : BSEG01: Source buffer [hex] or Pool [hex] is not valid
Explanation 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.
Recommended Action Probable causes of this error are a logic problem, the buffer header has been overwritten with bad data, the buffer pool control block has been overwritten with bad data, the data buffer has been freed, or the buffer pool has been freed. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BSEG02 : BSEG02: Bad input parameter to segment buffer [hex] in Pool [hex]
Explanation 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 in the request are invalid.
Recommended Action There is an internal code problem with the system. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BSEG03 : BSEG03: Bqxfr failed while segmenting buffer [hex] in Pool [hex]
Explanation 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:
•
F7100000-00000036
•
•
•
•
•
There is an internal code problem with the system.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BSEG04 : BSEG04: Request to move [dec] bytes; actual moved [dec] bytes
Explanation 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.
Recommended Action The actual number of bytes copied did not match the requested number of bytes to be copied. There is an internal code problem with the system. 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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BSEG05 : BSEG05: Request to join [hex] to [hex] failed with return of [dec]
Explanation 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.
Recommended Action There is an internal code problem with the system. 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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BUNR01 : BUNR01: Pool [hex] is not valid
Explanation A system software problem occurred.
Recommended Action A request to decrease the number of buffers in a buffer pool has detected a serious problem. The specified buffer pool is invalid. Either there is a logic problem, or the buffer pool control block has been overwritten with bad data. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BUNR02 : BUNR02: chg_amt for pool [hex] is negative
Explanation A system software problem occurred.
Recommended Action 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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BUNR03 : BUNR03: Pool [hex] is not a Fixed or Varying pool
Explanation A system software problem occurred.
Recommended Action 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 (the number of buffers in the pool) decreased. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BXFER01 : BXFER01: Source data will not fit in target-
Explanation 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.
Recommended Action The amount of data to be transferred exceeds the size of the target data buffer. There is an internal code problem with the system. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BXFER02 : BXFER02: Source buffer type unknown- buffer=[hex]
Explanation 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.
Recommended Action The buffer type indicator in the source data buffer (which specifies type of buffer pool from which the buffer was allocated) is invalid. Either there is a logic problem, or more likely, the buffer header has been overwritten with bad data. There is an internal code problem with the system. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BXFER03 : BXFER03: Source buffer is invalid - buffer=[hex]
Explanation 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.
Recommended Action Either the data buffer has been overwritten with bad data, or a data buffer that has already been freed is being used. There is an internal code problem with the system. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BXFER04 : BXFER04: Target buffer is invalid - buffer=[hex]
Explanation 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.
Recommended Action Either the data buffer has been overwritten with bad data, or a data buffer that has already been freed is being used. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-BXFER05 : BXFER05: Cannot Bxfr into a Rate_limited pool, target buffer=[hex]
Explanation 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.
Recommended Action The specified buffer pool cannot be used for the requested type of transfer (data cannot be transferred into a rate-limited buffer pool). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-DlurRetryFail : DLUS Operator activation required for DLUS-DLUR pipe
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-7-Error : [chars]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-Generic : [chars]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logamATTACH_REJECTED : Incoming Attach Rejected, subtype = 0x[hex]
Explanation The attach manager (AM) rejected a request to start a conversation (SNA ATTACH). The AM rejected an incoming ATTACH from a partner node. Following are some of the reasons that the ATTACH is rejected, along with the associated subtype:
•
•
•
•
•
•
•
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-logamRCV_ALLOC_NEVER_ISSUED : Program never issued RECEIVE ALLOCATE
Explanation A program was started by the attach manager (AM) but ended before issuing a RECEIVE_ALLOCATE for the ATTACH that initiated the program.
Recommended Action The AM 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. Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-logamUNEXPECTED_DOS_ERROR_RC : Unexpected system error, start_timer_rc = 0x[hex]
Explanation An operating system function failed while processing an incoming ATTACH or a RECEIVE_ALLOCATE from a transaction program.
Recommended Action The attach manager (AM) could not process an incoming request to create a conversation because a system function failed. The conversation failure occurred while processing an incoming ATTACH message or a RECEIVE_ALLOCATE from a local transaction program. The failure could have occurred for one of the following reasons. The function PEstart_timer failed while queueing the RECEIVE_ALLOCATE verb (to wait for an incoming ATTACH). The program file referenced in an incoming ATTACH could not be found. The program filename was determined from the transaction program in the ATTACH (default TP processing). The function PEstart_timer failed while queueing the incoming ATTACH (to wait for a transaction program to issue the appropriate RECEIVE_ALLOCATE verb). The program file referenced in an incoming ATTACH could not be found. The program filename was obtained from a DEFINE_TP verb for the transaction program in the ATTACH. There is an internal code problem. Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-logamUNEXPECTED_EGPE_ERROR_RC : AM unable to create process
Explanation A hardware or software error occurred.
Recommended Action There is an internal code problem. Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-logamUNKNOWN_IPS_RCVD : Unknown IPS received
Explanation The attach manager (AM) received an internal interprocess signal that it does not recognize or cannot process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-logamUNKNOWN_VERB_RCVD : Unknown verb received from API, ips name = [hex]
Explanation The attach manager (AM) received an application programming interface verb from an API interface that it does not recognize or cannot process.
Recommended Action There is an internal code problem. Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-logapiGPE_ERROR : Error Encountered, = [hex]
Explanation A system function failed while trying to process an API verb received from an application program.
Recommended Action Probable causes of the error are a serious memory shortage, a system error that occurred while processing the API verb, or a programming error in the local node. One of the functions that can fail is Pattach. Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-logapiOS_ERROR : OS Error Encountered, rc = [hex]
Explanation An operating system function failed while trying to process an API verb received from an application program.
Recommended Action Probable causes of this error are a serious memory shortage, a system error that occurred while processing the API verb, or a programming error in the local node. Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-logcsCS_ACT_AS_DLCX_FAIL_RSP : CS - CS - activate_as for local path control failed.
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_ACT_AS_RSP : CS - CS - activate_as for local path control failed, sense_code = [hex]
Explanation Configuration services (CS) failed to initialize. The address space for local path control could not be created.
Recommended Action 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 occur only if there is a serious memory shortage. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_ACT_AS_RSP_NEG : CS - Rcvd activate_as_rsp(neg): sense_code = [hex], ls_name = [chars], real_adj_cp_name = [chars]
Explanation Configuration services (CS) failed to successfully activate a route. The address space for the transmission group could not be created.
Recommended Action Activation of the indicated route failed. The request to create the transmission group's address space failed. The cause of the failure is indicated by the sense code. The most probable cause of this problem is that memory could not be allocated for the new address space. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_ACT_AS_RSP_UNKWN_LPID : CS - ACT_AS_RSP UNKNOWN LPID: lpid = [hex]
Explanation The link station identified in the received response does not exist.
Recommended Action Configuration services (CS) received an ACTIVATE_AS_RSP interprocess signal (IPS) specifying a link-station control block that is invalid or no longer exists. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_ACT_ROUTE : CS - ACTIVATE ROUTE FAILED, sense_code = [hex], tg_number = [hex], native_name = [chars]
Explanation An attempt to activate a route to the indicated node failed. The route is a connection network transmission group (TG), link TG, or local TG.
Recommended Action The sense code specifies the error encountered. Probable causes of this error are that a communications error occurred trying to establish a connection, a hardware error occurred, or internal resources (such as memory) are not available. If the condition is one that generates an alert (such as a hardware error), the detecting component that generated an alert will indicate the specific cause of the problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_ALERT_MSU : CS - ALERT_MSU received either:
Explanation A connection was unexpectedly terminated by the local DLC support because an alert situation was detected.
Recommended Action An established connection or a connection in the process of being established was unexpectedly terminated. Probable causes of this error are a communications error terminating the connection, or a hardware error terminating the connection. The local DLC support generates an alert indicating the specific cause of the problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_AS_DEACTVD_UNKN_LPID : CS - AS_DEACTIVATED UNKNOWN LPID: lpid = [hex]
Explanation The link station identified in the received interprocess signal (IPS) does not exist.
Recommended Action Configuration services (CS) received an AS_DEACTIVATED IPS from ASM specifying a link-station control block that is invalid or no longer exists. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_CREATE_TG_RSP : CS - create_tg for local path control failed, return_code = [hex]
Explanation Configuration services (CS) failed to initialize. The transmission group (TG) for local path control could not be created.
Recommended Action Initialization of the CS component failed. The request to create the local path control TG failed with the indicated return code. The probable cause of this error is a serious memory shortage. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_DISC_IND : CS - DISC.IND for: port_name = [chars], link_status = [hex]
Explanation A connection was unexpectedly terminated by the remote node or because a communications error occurred.
Recommended Action Probable causes of this error are the remote node terminating the connection, a communications error terminating the connection, or a hardware error terminating the connection. If the condition is one that generates an alert (such as a hardware error), the detecting DLC will generate an alert indicating the specific cause of the problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_FLUSH_IPS : CS - Flushing ips queue, ips_name = [hex]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_FSM_CN_TG : CS - FSM_CN_TG Abending - INVALID ACTION!, pratner_cp_name = [chars]
Explanation The connection network transmission group (TG) finite state machine (FSM) encountered an unrecoverable error and configuration services (CS) abended.
Recommended Action Probable causes of this error are invalid input or input out of sequence. Configuration services abends, effectively terminating the node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_FSM_DLC_INV_INPUT : CS - FSM_DLC INVALID INPUT:, dlc_name = [chars], current state = [hex], input value = [hex]
Explanation The DLC finite state machine (FSM) received an unexpected or unrecognized input value.
Recommended Action Probable causes of this error are invalid input or input out of sequence. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_FSM_LS_INVALID_ACTION : CS - FSM_LS INVALID ACTION: ls_name = [chars]
Explanation The link station finite state machine (FSM) encountered an unrecoverable error.
Recommended Action Probable causes of this error are invalid input or input out of sequence. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_FSM_LS_INV_INPUT : CS - FSM_LS INVALID INPUT: ls_name = [chars], current_state = [hex]
Explanation The finite state machine (FSM) governing link activation XID3 exchanges encountered an unrecoverable error.
Recommended Action Probable causes of this error are invalid input or input out of sequence. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_FSM_LS_INV_STATE : CS - FSM_LS INVALID STATE: ls_name = [chars], current_state = [hex], input_value = [hex]
Explanation The link station finite state machine (FSM) encountered an unrecoverable error.
Recommended Action Probable causes of this error are invalid input or input out of sequence. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_FSM_PORT_INV_ACTION : CS - FSM_PORT INVALID ACTION: port_name = [chars], action = [hex]
Explanation The port finite state machine (FSM) encountered an unrecoverable error.
Recommended Action Probable causes of this error are invalid input or input out of sequence. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_FSM_PORT_INV_INPUT : CS - FSM_PORT INVALID INPUT: port_name = [chars], current_state = [hex], ips_name(input) = [hex]
Explanation The port finite state machine (FSM) received an unexpected or unrecognized input value.
Recommended Action Probable causes of this error are invalid input or input out of sequence. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_FSM_PORT_INV_STATE : CS - FSM_PORT INVALID STATE: port_name = [chars], current_state = [hex], input_value = [hex]
Explanation The port finite state machine (FSM) encountered an unrecoverable error.
Recommended Action Probable causes of this error are invalid input or input out of sequence. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_FSM_TG_INVALID_ACTN : CS - FSM_TG_NEGOTIATION INVALID ACTION: ls_name = [chars], action = [hex]
Explanation The transmission group (TG) number negotiation FSM encountered an unrecoverable error.
Recommended Action Probable causes of this error are invalid input or input out of sequence. The remote node can also cause this problem by sending an XID out of sequence or with invalid parameters. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_FSM_TG_INVALID_STATE : CS - FSM_TG_NEGOTIATION INVALID STATE: ls_name = [chars], current_state = [hex], input_value = [hex]
Explanation The transmission group (TG) number negotiation FSM for secondary link stations encountered an unexpected condition.
Recommended Action Probable causes of this error are invalid input or input out of sequence. The remote node can also cause this problem by sending an XID out of sequence or with invalid parameters. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_FSM_XID3_INVAL_INPUT : CS - FSM_XID3 INVALID INPUT: ls_name = [chars], current_state = [hex], input_value = [hex]
Explanation The finite state machine (FSM) governing link activation XID3 exchanges encountered an unrecoverable error.
Recommended Action Probable causes of this error are invalid input or input out of sequence. The remote node can also cause this problem by sending an XID with invalid settings. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_FSM_XID3_NONACT_PRI : CS - FSM_XID3_NONACT_PRI INVALID ACTION: ls_name = [chars], action = [hex]
Explanation The finite state machine (FSM) governing nonactivation XID3 exchanges for primary link stations encountered an unrecoverable error.
Recommended Action Probable causes of this error are invalid input or input out of sequence. 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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_NONACT_SEC_INV_ACTION : CS - FSM_XID3_NONACT_SEC INVALID ACTION: LS=[chars]; ACTION=[hex];
Explanation The finite state machine (FSM) governing nonactivation XID3 exchanges for secondary link stations encountered an unrecoverable error.
Recommended Action Probable causes of this error are invalid input or input out of sequence. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_NONACT_SEC_INV_STATE : CS - FSM_XID3_NONACT_SEC INVALID STATE: ls_name = [chars], current state = [hex], input = [hex]
Explanation The finite state machine (FSM) governing nonactivation XID3 exchanges for secondary link stations encountered an unrecoverable error.
Recommended Action Probable causes of this error are invalid input or input out of sequence. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_NULL_LS_CB : CS - Null LS CB: Dlc:%1; Port:%2
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_NULL_PORT_CB : CS - Null Port CB: Dlc:%1
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_PDOPEN_TO_DLCX_FAILED : CS - PDopen to DLCX failed
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_PEGET_PID_PC_FAILED : CS - PEget_pid for PC failed
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_PEGET_SS_EID_FAILED : CS - PEget_ss_eid for port failed, ss_name = [chars]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_START_LS : CS - Sending START_LS(-RSP) to Console: ls_name = [chars], sense_code = [hex]
Explanation The link station finite state machine (FSM) encountered a normal race condition.
Recommended Action An inbound activation request was received for a link station at the same time that the node was attempting to activate the link station with an outbound request. The local 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. 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, communication is established via the inbound connection attempt. The only undesired side effect is that the link station is changed to one used for inbound requests, not outbound requests. If the connection is established, ensure that the established connection's characteristics are valid and usable (such as CP-CP session support and BTU sizes). 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.
Error Message%APPN-3-logcsCS_START_LS_SENT_TO_NOF : CS - START_LS sent to NOF:
Explanation Configuration services (CS) completed processing a NOF request to activate a link station or completed processing a NOF request while starting up all activate-at-startup link stations.
Recommended Action This log entry indicates the results of that attempt. If the response is positive (the sense code is zero), the link station 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. Probable causes of this error are that a communications error occurred trying to establish a connection, a hardware error occurred, or internal resources (such as memory) are not available. If the condition is one that generates an alert (such as a hardware error), the detecting component generates an alert that indicates the specific cause of the problem. If the attempt failed, the indicating link station is not activated. The operator request that triggered the request from NOF fails. If this failure occurs while a node is starting up, one or more of the activate-at-startup links did not activate. Determine why the link could not be activated and remedy the situation. When fixed, reissue the request to start the link station. If the error occurred during node startup, reactivate all links that were not activated.
Error Message%APPN-3-logcsCS_XID_ON_INACTV_PORT : CS - XID received on inactive port: port_name = [chars]
Explanation Configuration services (CS) received an XID from a DLC for an undefined or inactive port.
Recommended Action 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 occur only during a race condition where the DLC is forwarding the XID just as CS is deactivating the port. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_XXXCSP51_LOGMSG_00 : CS - Invalid LSA_IPS lsah.u_cep_id (ls_cb_p)
Explanation Configuration services (CS) encountered an unrecoverable error.
Recommended Action CS received an invalid data-link control (DLC) command from a DLC component. The link station identifier contained in the command is invalid (it does not reference a valid link station). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_XXXCSP51_LOGMSG_01 : CS - Invalid LSA_IPS lsah.primitive_code (port_cb_p)
Explanation Configuration services (CS) encountered an unrecoverable error.
Recommended Action CS received an invalid data-link control (DLC) command from a DLC component. The port identifier contained in the command is invalid (it does not reference a valid port). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_XXXXIP11_LOGMSG_00 : CS - Unable to locate link station control block
Explanation The configuration services component detected an external error and attempted to generate an alert to be sent to the Systems Network Architecture/Management Services (SNA/MS) alert focal point.
Recommended Action The alert could not be sent because the data-link control (DLC) control block associated with the alert cannot be determined. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_XXXXIP11_LOGMSG_01 : CS - Sending Alert to MS, sense_code = [hex], proc_name = [chars], port_name = [chars], ls_name = [chars]
Explanation The configuration services (CS) component detected an external error and generated an alert to be sent to the Systems Network Architecture/Management Services (SNA/MS) alert focal point.
Recommended Action 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 tries to forward the alert to the alert focal point, and also logs 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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_XXXXIP11_LOGMSG_02 : CS - Associated outbound XID data in alert (length < 29):
Explanation This log record is used to log any associated outbound XID data associated with the alert.
Recommended Action 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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_XXXXIP11_LOGMSG_03 : CS - Associated outbound XID data in alert (length = 29):
Explanation This log record is used to log any associated outbound XID data associated with the alert.
Recommended Action In particular, this log record is used when outbound XID data is available. See the description of log record 2F101000-0000001D for more information. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_XXXXIP11_LOGMSG_04 : CS - Associated inbound XID data in alert (length < 29):
Explanation This log record is used to log any associated outbound XID data associated with the alert.
Recommended Action In particular, this log record is used when outbound XID data is available. See the description of log record 2F101000-0000001D for more information. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logcsCS_XXXXIP11_LOGMSG_05 : CS - Associated inbound XID data in alert (length = 29):
Explanation This log record is used to log any associated outbound XID data associated with the alert.
Recommended Action In particular, this log record is used when inbound XID data is available. See the description of log record 2F101000-0000001D for more information. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSa00_LOGMSG_01 : DS - APmain: Unknown APPL message received = %#0.4x
Explanation Directory services (DS) internal search routine received an internal interprocess signal that it does not recognize or cannot process.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSa01_LOGMSG_01 : DS - LSprocess_locate_msg: Unknown search procedure
Explanation Directory services (DS) received an invalid LOCATE_MESSAGE interprocess signal.
Recommended Action The appropriate search finite state machine (FSM) could not be determined from the data in the signal. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSa01_LOGMSG_02 : DS - LSprocess_locate_msg: Invalid searchFSM type
Explanation Directory services (DS) received an invalid LOCATE_MESSAGE interprocess signal.
Recommended Action The appropriate search finite state machine (FSM) could not be determined from the data in the signal. The DS routine used to determine the search FSM returned an invalid value. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSc02_LOGMSG_01 : DS - Invalid wildcard indicator in resource descriptor
Explanation Directory services (DS) received an invalid UPDATE_DIRECTORY (of type DELETE) interprocess signal.
Recommended Action The resource type could not be determined from the resource descriptor in the signal. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSc02_LOGMSG_02 : DS - CPupdate directory: Invalid resource hierarchy found in UPDATE_DIRECTORY message
Explanation Directory services (DS) received an invalid UPDATE_DIRECTORY (of type UPDATE or ADD) interprocess signal.
Recommended Action The resource hierarchy contained in the signal's resource descriptor is invalid. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDScf0_LOGMSG_01 : DS - CP_STATUS FSM: Unanticipated CP_STATUS message received, node name = [chars], new state = [dec], old state = [dec], session status = [dec]
Explanation The control point (CP) status FSM encountered an unexpected CP_STATUS interprocess signal (IPS).
Recommended Action Probable causes of this error are invalid input or input out of sequence. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDScf0_LOGMSG_02 : DS - CP_STATUS FSM: Invalid action encountered
Explanation The control point (CP) status FSM encountered an unrecoverable error.
Recommended Action Probable causes of this error are invalid input or input out of sequence. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSd03_LOGMSG_01 : DS - DBcheck_rsc_hierarchy_error: rsc_hierarchy structure does not contain an NN or EN
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action A resource hierarchy control block in the directory is invalid. It does not contain a network node name or end node name. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSd03_LOGMSG_02 : DS - DBcheck_rsc_hierarchy_error: rsc_hierarchy structure does not contain an LU
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action A resource hierarchy control block in the directory is invalid. It does not contain an LU name. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSd10_LOGMSG_01 : DS - DBcreate_adj_node: Duplicate adjacent node record created
Explanation Directory services (DS) detected two adjacent nodes with the same control point name.
Recommended Action DS 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. Probable causes of this error are a network definition error where two nodes are defined with the same control point name, a remote node sending an invalid message, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSd15_LOGMSG_01 : DS - Invalid adjacent node record encountered
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action An adjacent node record in the directory is invalid. It does not contain a valid eyecatcher. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSd20_LOGMSG_01 : DS - DBcopy_sdi_to_sdo: sdi not allocated
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action There is an internal code problem in the DS component. The routine that is used to copy search data descriptor control blocks determined the source control block is either not a search data descriptor or is no longer in use. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSd20_LOGMSG_02 : DS - DBcopy_sdi_to_sdo: sdo not allocated
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action There is an internal code problem in the DS component. The routine that is used to copy search data descriptor control blocks determined the source control block is either not a search data descriptor or is no longer in use. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSd20_LOGMSG_03 : DS - DB_insert_search_data: duplicate DB entry
Explanation Directory services (DS) encountered an unexpected condition. An internal logic problem exists within DS.
Recommended Action Duplicate search requests for the same resource have been requested (duplicate search data descriptors). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSd20_LOGMSG_04 : DS - DBdump_search_data: invalid search_status enum
Explanation Directory services (DS) encountered an unexpected condition. An internal control block is invalid.
Recommended Action The search status indicator in the descriptor is invalid. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSd30_LOGMSG_01 : DS - DBcreate_locate_record: Creating duplicate locate record
Explanation Directory services (DS) encountered an unexpected condition. There is an internal logic problem with DS.
Recommended Action Duplicate locate requests have been created (duplicate locate records). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSd30_LOGMSG_02 : DS - DBinit_search: Invalid SEARCH_EVENT.TYPE
Explanation Directory services (DS) encountered an unexpected condition. An internal control block is invalid.
Recommended Action The type of search in the request is invalid. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSd40_LOGMSG_01 : DS - DBcreate_locate_cb: Creating duplicate locate cb
Explanation Directory services (DS) encountered an unexpected condition. There is an internal logic problem with DS.
Recommended Action Duplicate locate records have been created (duplicate descriptors for the same locate request). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSd42_LOGMSG_01 : DS - Invalid search_state
Explanation Directory services (DS) encountered an unexpected condition. An internal control block is invalid.
Recommended Action The search status in the locate record is invalid. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSd42_LOGMSG_02 : DS - Invalid node_role enum encountered
Explanation Directory services (DS) encountered an unexpected condition. An internal control block is invalid.
Recommended Action The search finite state machine (FSM) ID, which indicates the local node's role in the search, is invalid. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSd50_LOGMSG_01 : DS - Invalid wildcard indicator in resource descriptor, value = [dec]
Explanation Directory services (DS) encountered an unexpected condition. An internal control block is invalid.
Recommended Action A resource descriptor is invalid. The wildcard indicator in the descriptor is invalid. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSd50_LOGMSG_02 : DS - LU name duplicates the name of a non-cached directory entry
Explanation Directory services (DS) detected two resources with the same name.
Recommended Action DS 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. Probable causes of this error are a network definition error with two resources defined with the same name, the remote node sending an invalid message, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSd50_LOGMSG_03 : DS - Partial wildcard LU name conflicts with another partial wildcard directory entry
Explanation Directory services (DS) received a request to add duplicate partial wildcard entries in the directory.
Recommended Action DS received a request to add a partial wildcard resource description to the directory, but the wildcard LU name is already defined in the directory. Probable causes of this error are a network definition error with the same partial wildcard entry defined twice, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSd50_LOGMSG_04 : DS - Duplicate full wildcard directory entries
Explanation Directory services (DS) received a request to add duplicate partial wildcard entries in the directory.
Recommended Action Configuration services (CS) 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. Probable causes of the error are a network definition error with the multiple full wildcard entries defined, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSd51_LOGMSG_01 : DS - Adjacent node has an unexpected node type of NN
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action An internal control block is invalid or there is a logic error in the DS component. A search of the directory returned an incorrect or invalid directory entry. The search was a domain search, which should search only 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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSd51_LOGMSG_02 : DS - Invalid adjacent node type in adjacent node record, value = [dec]
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action An internal control block is invalid. An adjacent node record in the directory is invalid. It does not contain a valid node type value. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSd54_LOGMSG_01 : DS - Could not open DSrd.log file, unable to dump DS database
Explanation The request to open the specified dump file failed.
Recommended Action Directory services (DS) could not dump the resource directory. The dump file could not be opened. Probable causes of the error are that a system function failure has occurred (preventing the file from being opened by directory services), or the file is already opened by another program within the system. The file can be read by other programs, but should not be opened for write access. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSd54_LOGMSG_02 : DS - Invalid resource location in a directory entry
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action A resource directory entry is invalid. The resource location in the entry is invalid. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSd54_LOGMSG_03 : DS - Invalid entry type in a directory entry, type = [dec]
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action A resource directory entry is invalid. The entry type (permanent, registered, or cached) in the entry is invalid. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSd54_LOGMSG_04 : DS - Invalid wildcard indicator in a directory entry, type = [dec]
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action A resource directory entry is invalid. The wildcard type (explicit, partial, or full) in the entry is invalid. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSf01_LOGMSG_01 : DS - DBsd_gds_12C4_search_status invalid, value = [dec]
Explanation Directory services (DS) received or detected an invalid LOCATE message (GDS x'12C4').
Recommended Action DS encountered an invalid LOCATE GDS variable. The search-status indicators in the message are invalid. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSf03_LOGMSG_01 : DS - FMT: Inbound search: Unrecognized control vector in CV2B = %#0.2x
Explanation Directory services (DS) does not recognize a control vector contained in a received x'2B' control vector.
Recommended Action DS encountered an invalid x'2B' control vector. It contains one or more control vectors not recognized by directory services. Probable causes of this error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSf04_LOGMSG_01 : DS - FMTmap_cv0E: invalid cv0E
Explanation Directory services (DS) encountered an unexpected situation.
Recommended Action There is an internal code problem in the DS component. The routine used to map and 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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSf04_LOGMSG_02 : DS - FMTmap_cv0E: invalid NET_NAME_TYPE
Explanation Directory services (DS) encountered an unexpected situation.
Recommended Action There is an internal code problem in the DS component. The routine used to map and unmap the control vector x'0E' determined that the unmapped x'0E' control vector structure is invalid. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSf04_LOGMSG_03 : DS - FMTunmap_cv0E: invalid NET_NAME_TYPE
Explanation Directory services (DS) cannot parse a received x'0E' control vector.
Recommended Action DS encountered an invalid x'0E' control vector. The network name (resource) type is not recognized by DS. Probable causes of this error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSf05_LOGMSG_01 : DS - FMTmap_find_cv80: Invalid MIN_RSP_ENTRY
Explanation Directory services (DS) encountered an unexpected situation.
Recommended Action There is an internal code problem in the DS component. The routine used to map and 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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSf06_LOGMSG_01 : DS - FMTunmap_rsc_entry: Invalid resource type
Explanation Directory services (DS) could not parse received an x'3C', x'3D', x'81', or x'82' control vector.
Recommended Action The resource type is not recognized by DS. Probable causes of this error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSf06_LOGMSG_02 : DS - FMTunmap_rsc_entry: Invalid cvkey
Explanation Directory services (DS) could not parse a received resource entry control vector.
Recommended Action DS 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'. Probable causes of this error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSi00_LOGMSG_01 : DS - INFOmain: Unknown IPS received, IPS = %#0.4x
Explanation Directory services (DS) received an internal interprocess signal that it does not recognize or cannot process.
Recommended Action There is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSl00_LOGMSG_01 : DS - LSmain: invalid search_event received, %#0.4x
Explanation Directory services (DS) received an invalid request from another node (search).
Recommended Action DS received an invalid search request that contains an invalid search event type. Probable causes of this error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSl01_LOGMSG_01 : DS - Inbound search received, but adjacent node does not exist, adj cp name = [chars]
Explanation Directory services (DS) received an invalid request from another node (search).
Recommended Action DS received an invalid search request. The adjacent node name in the search request does not match any adjacent node records in the directory. Probable causes of this error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSl01_LOGMSG_02 : DS - Received inbound search from node which is being disabled; ignoring search
Explanation Directory services (DS) received a search request from a node with which it is currently deactivating its CP-CP sessions.
Recommended Action The search request is ignored. The node could not send back the reply, because the CP-CP sessions are no longer active to the node. The search request is ignored, and DS continues to process other signals. 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.
Error Message%APPN-3-logdsDS_NEWDSl01_LOGMSG_03 : DS - Adjacent node state is invalid. We have a bug
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action An adjacent node record in the directory is invalid. The node state (status) in the adjacent node record is invalid. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSl01_LOGMSG_04 : DS - Inbound search contained invalid or unrecognized control vectors, sense_code = [hex]
Explanation Directory services (DS) received an invalid network search request from another node.
Recommended Action DS received an invalid network search request. DS could not parse the control vectors contained in the request. The sense code specifies the type of error encountered by DS. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSl01_LOGMSG_05 : DS - Inbound search contained incorrect or unexpected control vectors, sense_code = [hex]
Explanation Directory services (DS) received an invalid network search request from another node.
Recommended Action DS 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. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSl01_LOGMSG_06 : DS - LSprocess_rcvd_search: SearchFSM_Error
Explanation Directory services (DS) received an invalid network search request from another node.
Recommended Action The appropriate search finite state machine (FSM) could not be determined from the data in the request. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSl01_LOGMSG_07 : DS - LSprocess_rcvd_search: Invalid SearchFSM type
Explanation Directory services (DS) received an invalid network search request from another node.
Recommended Action The appropriate search finite state machine (FSM) could not be determined from the data in the request. The DS routine used to determine the search FSM returned an invalid value. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSl02_LOGMSG_01 : DS - FMT:Inbound search: Unexpected control vector in CV2B, mapped_cv[[dec]] = [hex]
Explanation Directory services (DS) does not recognize a control vector contained in a received x'2B' control vector.
Recommended Action DS encountered an invalid network search request. The x'2B' control vector in the request contains one or more control vectors not recognized or processed by directory services. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSl04_LOGMSG_01 : DS - LSprocess_cp_outage: Unknown search procedure
Explanation Directory services (DS) received an invalid CP outage notification from another node.
Recommended Action DS received an invalid notification from another node that a control point has been deactivated (the CP-CP sessions to the node have been deactivated). The appropriate search finite state machine (FSM) could not be determined from the data in the notification. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSl04_LOGMSG_02 : DS - LSprocess_cp_outage: Invalid searchFSM type
Explanation Directory services (DS) received an invalid CP outage notification from another node, which caused an unexpected condition.
Recommended Action DS received an invalid notification from another node that a control point has been deactivated (the CP-CP sessions to the node have been deactivated). The appropriate search finite state machine (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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSl10_LOGMSG_01 : DS - DBsd_gds12C4_search_status invalid, value = [dec]
Explanation Directory services (DS) tried to process a search request containing an invalid locate GDS x'12C4'.
Recommended Action DS encountered a search request containing an invalid LOCATE GDS variable. The search status indicators in the variable are invalid. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error on the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSl10_LOGMSG_02 : DS - Search event type invalid, type = [dec]
Explanation Directory services (DS) received an invalid request from another node (search).
Recommended Action The search event type in the request is invalid. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSl20_LOGMSG_01 : DS - LSeval_input_InpRole: Invalid LR.SEARCH.ROLE
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action A locate record is invalid. The local node search role indicator in the locate record is invalid. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf1_LOGMSG_01 : DS - FSM(dir_INN): Invalid search status in GDS variable x'12C4', value = [dec]
Explanation Directory services (DS) tried to process a search request containing an invalid locate GDS x'12C4'.
Recommended Action The DS finite state machine (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. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf1_LOGMSG_02 : DS - FSM(dir_INN): Invalid input. CP name in CP outage not found, cp name = [chars]
Explanation Directory services (DS) received an invalid control point (CP) outage notification.
Recommended Action The DS finite state machine (FSM) dir_INN received an invalid or unexpected CP outage notification. DS 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. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf1_LOGMSG_03 : DS - FSM(dir_INN): Invalid input. Search event type is invalid, type = [dec]
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The directory services finite state machine (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. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf1_LOGMSG_04 : DS - FSM(dir_INN): invalid input value = %#0.8x
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (FSM) dir_INN received an unexpected or unrecognized input value. This FSM controls the processing of directed searches for resources by an intermediate network node. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Another log record may be created in conjunction with this log record (2F102000-00000038 or 2F102000-0000003A) that contains more detailed information on the invalid input condition. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf1_LOGMSG_05 : DS - FSM(dir_INN): state error, lcb: %#0.8x pcid: %#0.8x%0.8x row: [dec] col: [dec] inp: %#0.8x
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (FSM) dir_INN encountered a state error. This FSM controls the processing of directed searches for resources by an intermediate network node. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-0000003B) may be created in conjunction with this log record when an invalid input value is received. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf1_LOGMSG_06 : DS - FSM(dir_INN): invalid action value, lcb: %#0.8x se_p: %#0.8x inp: %#0.8x action: [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) dir_INN sent an unknown or invalid action value. This FSM controls the processing of directed searches for resources by an intermediate network node. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-0000003B) may be created in conjunction with this log record when an invalid input value is received. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf2_LOGMSG_01 : DS - FSM(brd_INN): Invalid search status in GDS variable x'12C4', status = [dec]
Explanation Directory services (DS) tried to process a search request containing an invalid locate GDS x'12C4'.
Recommended Action The DS finite state machine (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. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf2_LOGMSG_02 : DS - FSM(brd_INN): Invalid input. CP name in CP outage not found. cp name = [chars]
Explanation Directory services (DS) received an invalid control point (CP) outage notification. The associated locate record could not be determined.
Recommended Action The DS finite state machine (FSM) brd_INN received an invalid or unexpected CP outage notification. DS 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. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf2_LOGMSG_03 : DS - FSM(brd_INN): Invalid input. Search event type is invalid, type = [dec]
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (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. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf2_LOGMSG_04 : DS - FSM(brd_INN): invalid input value = %#0.8x
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (FSM) brd_INN received an unexpected or unrecognized input value. This FSM controls the processing of broadcast searches for resources by an intermediate network node. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Another log record may be created in conjunction with this log record (2F102000-0000003E or 2F102000-00000040) that contains more detailed information on the invalid input condition. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf2_LOGMSG_05 : DS - FSM(brd_INN): state error, lcb: %#0.8x pcid: %#0.8x%0.8x row: [dec] col: [dec]
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (FSM) brd_INN encountered a state error. This FSM controls the processing of broadcast searches for resources by an intermediate network node. Probable causes of the error are an invalid input value was received because of a programming error in the local node, or the remote node sent an invalid message. Another log record (2F102000-00000041) may be created in conjunction with this log record when an invalid input value is received. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf2_LOGMSG_06 : DS - FSM(brd_INN): Invalid resource returned from a domain search, rsc_location = [dec]
Explanation Directory services (DS) encounter an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (FSM) brd_INN retrieved an incorrect or 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 (of which the resource is in the domain) is a network node. This FSM controls the processing of broadcast searches for resources by an intermediate network node. There is a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf2_LOGMSG_07 : DS - FSM(brd_INN): invalid action value, lcb: %#0.8x se_p: %#0.8x inp: %#0.8x action: [dec]
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (FSM) brd_INN send an unknown or invalid action value. This FSM controls the processing of broadcast searches for resources by an intermediate network node. Probable causes of the error are an invalid input value was received because of a programming error in the local node, or the remote node sent an invalid message. Another log record (2F102000-00000041) may be created in conjunction with this log record when an invalid input value is received. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf3_LOGMSG_01 : DS - FSM(parent): Invalid search status in GDS variable x'12C4', value = [dec]
Explanation Directory services (DS) tried to process a search request containing an invalid locate GDS x'12C4'.
Recommended Action The DS finite state machine (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. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf3_LOGMSG_02 : DS - FSM(parent): Invalid input. Search event type is invalid = [dec]
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (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. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf3_LOGMSG_03 : DS - FSM(parent): invalid input value = %#0.8x
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf3_LOGMSG_04 : DS - FSM(parent): state error, lr: %#0.8x row: [dec] col: [dec] inp: %#0.8x
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf3_LOGMSG_05 : DS - FSM(parent): invalid action, lr: %#0.8x se_p: %#0.8x inp: %#0.8x action: [dec]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf4_LOGMSG_01 : DS - FSM(child): Invalid search status in GDS variable x'12C4', value = [dec]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf4_LOGMSG_02 : DS - FSM(child): Invalid input. Locate message is a request
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (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. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf4_LOGMSG_03 : DS - FSM(child): Invalid input. Search event type is invalid, se type = [dec]
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (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. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf4_LOGMSG_04 : DS - FSM(child): invalid input value = %#0.8x
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (FSM) child received an unexpected or unrecognized input value. This FSM controls the processing of searches for resources relative to the child node in the request. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Another log record may be created in conjunction with this log record (2F102000-0000004A, 2F102000-0000004B, or 2F102000-0000004C) that contains more detailed information about the invalid input condition. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf4_LOGMSG_05 : DS - FSM(child): state error, lr: %#0.8x row: [dec] col: [dec] inp: %#0.8x
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (FSM) child encountered a state error. This FSM controls the processing of searches for resources relative to the child node in the request. Probable causes of the error are an invalid input value was received because of a programming error in the local node, or the remote node sent an invalid message. Another log record (2F102000-0000004D) may be created in conjunction with this log record when an invalid input value is received. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf4_LOGMSG_06 : DS - FSM(child): invalid action value, lr: %#0.8x se_p: %#0.8x inp: %#0.8x action: [dec]
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (FSM) child sent an unknown or invalid action value. This FSM controls the processing of searches for resources relative to the child node in the request. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-0000004D) may be created in conjunction with this log record when an invalid input value is received. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf5_LOGMSG_01 : DS - FSM(dir_NNSdlu): Received locate reply is incompatible with inputted search type
Explanation Directory services (DS) received an invalid locate reply.
Recommended Action The DS finite state machine (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. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf5_LOGMSG_02 : DS - FSM(dir_NNSdlu): Invalid search status in GDS variable x'12C4', value = [dec]
Explanation Directory services (DS) tried to process a search request containing an invalid locate GDS x'12C4'.
Recommended Action The DS finite state machine (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. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf5_LOGMSG_03 : DS - FSM(dir_NNSdlu): Received CP outage is incompatible with inputted search type
Explanation Directory services (DS) received an invalid control point (CP) outage notification.
Recommended Action The DS finite state machine (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. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf5_LOGMSG_04 : DS - FSM(dir_NNSdlu): Invalid input. Locate message is a request
Explanation Directory services (DS) encountered an unexpected software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) dir_NNSdlu 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 directed searches for resources by the network node server of the destination LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf5_LOGMSG_05 : DS - FSM(dir_NNSdlu): Invalid input. Search event type is invalid, se type = [dec]
Explanation Directory services (DS) encountered an unexpected software problem while searching for a resource.
Recommended Action The DS finite state machine (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. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf5_LOGMSG_06 : DS - FSM(dir_NNSdlu): invalid input value = %#0.8x
Explanation Directory services (DS) encountered an unexpected software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) dir_NNSdlu received an unexpected or unrecognized input value. This FSM controls the processing of directed searches for resources by the network node server of the destination LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Another log record may be created in conjunction with this log record (2F102000-00000051, 2F102000-00000053, or 2F102000-00000054) that contains more detailed information on the invalid input condition. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf5_LOGMSG_07 : DS - FSM(dir_NNSdlu): state error, lcb: %#0.8x pcid: %#0.8x%0.8x row: [dec] col: [dec] inp: %#0.8x
Explanation Directory services (DS) encountered an unexpected software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) dir_NNSdlu encountered a state error. This FSM controls the processing of directed searches for resources by the network node server of the destination LU. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-00000055) may be created in conjunction with this log record when an invalid input value is received. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf5_LOGMSG_08 : DS - FSM(dir_NNSdlu): Invalid resource location in a directory entry, value = [dec]
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action The DS finite state machine (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. There is a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf5_LOGMSG_09 : DS - FSM(dir_NNSdlu): invalid action, lcb: %#0.8x se_p: %#0.8x inp: %#0.8x action: [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) dir_NNSdlu sent an unknown or invalid action value. This FSM controls the processing of directed searches for resources by the network node server of the destination LU. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-00000055) may be created in conjunction with this log record when an invalid input value is received. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf6_LOGMSG_01 : DS - FSM(ENdlu): Invalid search status in GDS variable x'12C4', value = [dec]
Explanation Directory services (DS) tried to process a search request containing an invalid locate GDS x'12C4'.
Recommended Action The DS finite state machine (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. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf6_LOGMSG_02 : DS - FSM(ENdlu): Invalid chain status in GDS variable x'12C4', value = [dec]
Explanation Directory services (DS) tried to process a search request containing an invalid locate GDS x'12C4'.
Recommended Action The DS finite state machine (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. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf6_LOGMSG_03 : DS - FSM(ENdlu): Invalid input. Search event type is invalid, se type = [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (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. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf6_LOGMSG_04 : DS - FSM(ENdlu): invalid input value = %#0.8x
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) ENdlu received an unrecognized or unexpected input value. This FSM controls the processing of searches for resources by the end node owning the destination LU. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf6_LOGMSG_05 : DS - FSM(ENdlu): state error, lcb: %#0.8x pcid: %#0.8x row: [dec] col: [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) ENdlu encountered a state error. This FSM controls the processing of searches for resources by the end node owning the destination LU. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-0000005C) may be created in conjunction with this log record when an invalid input value is received. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf6_LOGMSG_06 : DS - FSM(ENdlu): invalid action value, lcb: %#0.8x se_p: %#0.8x inp: %#0.8x action: [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) ENdlu sent an unknown or invalid action value. This FSM controls the processing of searches for resources by the end node owning the destination LU. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-0000005C) may be created in conjunction with this log record when an invalid input value is received. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf7_LOGMSG_01 : DS - FSM(NNolu): Invalid search status in GDS variable x'12C4', value = [dec]
Explanation Directory services (DS) tried to process a search request containing an invalid locate GDS x'12C4'.
Recommended Action The DS finite state machine (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. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf7_LOGMSG_02 : DS - FSM(NNolu): Invalid input. Locate message is not a request
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action 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. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf7_LOGMSG_03 : DS - FSM(NNolu): Invalid input. Search event type is invalid, se type = [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action 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. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf7_LOGMSG_04 : DS - FSM(NNolu): invalid input value, input = [hex]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The directory services FSM NNolu received an unexpected or unrecognized input value. This FSM controls the processing of searches for resources by the network node owning the origin LU. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Another log record may be created in conjunction with this log record (2F102000-0000005F, 2F102000-00000060, or 2F102000-00000061) that contains more detailed information about the invalid input condition. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf7_LOGMSG_05 : DS - FSM(NNolu): state error, lcb: %#0.8x pcid: %#0.8x%0.8x row: [dec] col: [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) ENdlu encountered a state error. This FSM controls the processing of searches for resources by the end node owning the destination LU. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-00000062) may be created in conjunction with this log record when an invalid input value is received. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf7_LOGMSG_06 : DS - FSM(NNolu): Invalid resource location in a directory entry, value = [dec]
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action 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. There is a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf7_LOGMSG_07 : DS - FSM(NNolu): State error. Expected non-explicit (wildcard) locate reply not found
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action The DS finite state machine (FSM) NNolu encountered a state error. The current state indicates that a nonexplicit (wildcard) locate reply was received for the resource and saved by DS. 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. There is a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf7_LOGMSG_08 : DS - FSM(NNolu): Duplicate LU found on search
Explanation Directory services (DS) detected two resources with the same name.
Recommended Action The DS finite state machine (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. Probable causes of the error are a network definition error (two resources defined with the same name), the remote node sending an invalid message, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf7_LOGMSG_09 : DS - FSM(NNolu): invalid action value, input = [hex], action = [hex]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The directory services FSM NNolu sent an unknown or invalid action value. This FSM controls the processing of searches for resources by the network node owning the origin LU. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-00000062) may be created in conjunction with this log record when an invalid input value is received. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf8_LOGMSG_01 : DS - FSM(CPolu_child): Invalid search status in GDS variable x'12C4', value = [dec]
Explanation Directory services (DS) tried to process a search request containing an invalid locate GDS x'12C4'.
Recommended Action The DS finite state machine (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. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf8_LOGMSG_02 : DS - FSM(CPolu_child): Invalid input. Search event type is invalid, se type = [dec]
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action The DS finite state machine (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. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf8_LOGMSG_03 : DS - FSM(CPolu_child): invalid input value = [dec]
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action The DS finite state machine (FSM) CPolu_child received an unexpected or unrecognized input value. This FSM controls the processing of searches for resources relative to the child node in the request by the node owning the origin LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Another log record may be created in conjunction with this log record (2F102000-00000068 or 2F102000-00000069). The additional log record contains more detailed information on the invalid input condition. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf8_LOGMSG_04 : DS - FSM(CPolu_child): state error, lr: %#0.8x row: [dec] col: [dec] inp: %#0.8x
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action The DS finite state machine (FSM) CPolu_child encountered a state error. This FSM controls the processing of searches for resources relative to the child node in the request by the node owning the origin LU. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-0000006A) may be created in conjunction with this log record when an invalid input value is received. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf8_LOGMSG_05 : DS - FSM(CPolu_child): invalid action, lr: %#0.8x se_p: %#0.8x inp: %#0.8x action: [dec]
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action The DS finite state machine (FSM) CPolu_child sent an unknown or invalid action value. This FSM controls the processing of searches for resources relative to the child node in the request by the node owning the origin LU. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-0000006A) may be created in conjunction with this log record when an invalid input value is received. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf9_LOGMSG_01 : DS - FSM(CPolu_parent): Negative LOCATE_MESSAGE(RQ) invalid
Explanation Directory services (DS) received a locate request containing sense data.
Recommended Action The DS finite state machine (FSM) CPolu_parent received a locate request containing a nonzero 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. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf9_LOGMSG_02 : DS - FSM(CPolu_parent): Invalid input. Search event type is invalid, type = [dec]
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action The DS finite state machine (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. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf9_LOGMSG_03 : DS - FSM(CPolu_parent): invalid input value = [hex]
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action The DS finite state machine (FSM) CPolu_parent received an unexpected or unrecognized input value. This FSM controls the processing of searches for resources relative to the parent node in the request by the node owning the origin LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Another log record may be created in conjunction with this log record (2F102000-0000006E). The additional log record contains more detailed information on the invalid input condition. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf9_LOGMSG_04 : DS - FSM(CPolu_parent): state error, lr: %#0.8x row: [dec] col: [dec] inp: %#0.8x
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action The DS finite state machine (FSM) CPolu_parent encountered a state error. This FSM controls the processing of searches for resources relative to the parent node in the request by the node owning the origin LU. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-0000006F) may be created in conjunction with this log record when an invalid input value is received. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlf9_LOGMSG_05 : DS - FSM(CPolu_parent): invalid action, lr: %#0.8x se_p: %#0.8x inp: %#0.8x action: [dec]
Explanation The DS finite state machine (FSM) CPolu_parent sent an unknown or invalid action value. This FSM controls the processing of searches for resources relative to the parent node in the request by the node owning the origin LU. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-0000006F) may be created in conjunction with this log record when an invalid input value is received. Copy the error message exactly as it appears, and report it to your technical support representative.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlfa_LOGMSG_01 : DS - FSM(NNSolu): Invalid search status in GDS variable x'12C4', value = [dec]
Explanation Directory services (DS) tried to process a search request containing an invalid locate GDS x'12C4'.
Recommended Action The DS finite state machine (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. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. This error is also logged by the directory services resource registration routines. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlfa_LOGMSG_02 : DS - FSM(NNSolu): Invalid input. Locate message status is invalid, status = [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (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. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlfa_LOGMSG_03 : DS - FSM(NNSolu): Invalid input. Search event type is invalid, type = [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (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. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. This error is also logged by the directory services resource registration routines. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlfa_LOGMSG_04 : DS - FSM(NNSolu): invalid input value = %#0.8x
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) NNSolu received an unexpected or unrecognized input value. This FSM controls the processing of searches for resources by the network node server of the origin LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Another log record may be created in conjunction with this log record (2F102000-00000072 or 2F102000-00000074) that contains more detailed information on the invalid input condition. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlfa_LOGMSG_05 : DS - FSM(NNSolu): state error, lcb: %#0.8x pcid: %#0.8x%0.8x row: [dec] col: [dec] inp: %#0.8x
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) NNSolu encountered a state error. This FSM controls the processing of searches for resources by the network node server of the origin LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Another log record (2F102000-00000075) may be created in conjunction with this log record when an invalid input value is received. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlfa_LOGMSG_06 : DS - FSM(NNSolu): Invalid resource location in a directory entry, value = [dec]
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action The DS finite state machine (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. There is a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlfa_LOGMSG_07 : DS - FSM(NNSolu): State error. Expected non-explicit (wildcard) locate reply not found
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action The DS finite state machine (FSM) NNSolu encountered a state error. The current state indicates that a nonexplicit (wildcard) locate reply was received for the resource and saved by DS. 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. There is a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlfa_LOGMSG_08 : DS - FSM(NNSolu): Duplicate LU found on search
Explanation Directory services (DS) detected two resources with the same name.
Recommended Action The DS finite state machine (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. Probable causes of the error are a network definition error (two resources are defined with the same name), the remote node sending an invalid message, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlfa_LOGMSG_09 : DS - FSM(NNSolu): invalid action, lcb: %#0.8x se_p: %#0.8x inp: %#0.8x action: [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) NNSolu sent an unknown or invalid action value. This FSM controls the processing of searches for resources by the network node server of the origin LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Another log record (2F102000-00000075) may be created in conjunction with this log record when an invalid input value is received. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlfb_LOGMSG_01 : DS - FSM(ENolu): Invalid search status in GDS variable x'12C4', value = [dec]
Explanation Directory services (DS) tried to process a search request containing an invalid locate GDS x'12C4'.
Recommended Action The DS finite state machine (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. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlfb_LOGMSG_02 : DS - FSM(ENolu): Invalid input. Locate message is not a request
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) 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. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlfb_LOGMSG_03 : DS - FSM(ENolu): Invalid input. Search event type is invalid, type = [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (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. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlfb_LOGMSG_04 : DS - FSM(ENolu): invalid input value = %#0.8x
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) ENolu received an unexpected or unrecognized input value. This FSM controls the processing of searches for resources by the end node owning the origin LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Another log record may be created in conjunction with this log record (2F102000-0000007B, 2F102000-0000007C, or 2F102000-0000007D) that contains more detailed information on the invalid input condition. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlfb_LOGMSG_05 : DS - FSM(ENolu): state error, lcb: %#0.8x pcid: %#0.8x row: [dec] col: [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) ENolu encountered a state error. This FSM controls the processing of searches for resources by the end node owning the origin LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Another log record (2F102000-0000007E) may be created in conjunction with this log record when an invalid input value is received. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlfb_LOGMSG_06 : DS - FSM(ENolu): Invalid resource location in a directory entry, value = [dec]
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action The DS finite state machine (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. There is a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlfb_LOGMSG_07 : DS - FSM(ENolu): Duplicate LU found on search
Explanation Directory services (DS) detected two resources with the same name.
Recommended Action The DS finite state machine (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. Probable causes of the error are a network definition error (two resources defined with the same name), the remote node sending an invalid message, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlfb_LOGMSG_08 : DS - FSM(ENolu): invalid action, lcb: %#0.8x se_p: %#0.8x inp: %#0.8x action: [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) ENolu sent an unknown or invalid action value. This FSM controls the processing of searches for resources by the end node owning the origin LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Another log record (2F102000-0000007E) may be created in conjunction with this log record when an invalid input value is received. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSlse_LOGMSG_01 : DS - Search event type is invalid, type = [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action DS detected an invalid search event. The search event type is invalid. Probable causes of the error are a programming error in the local node, or the remote node sending an invalid message. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSr00_LOGMSG_01 : DS - RRmain: Unknown IPS received, IPS = %#0.4x
Explanation Directory services (DS) received an internal interprocess signal (IPS) that it does not recognize or cannot process.
Recommended Action The DS internal data reporting routine received an IPS that it does not recognize or process. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSr10_LOGMSG_01 : DS - Resource Registration Request length error, lu name = [chars]
Explanation Directory services (DS) received an invalid resource registration request from another node.
Recommended Action 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. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSr10_LOGMSG_02 : DS - Resource Registration Request received from an invalid session (not CP-CP) adj cp name = [chars], cgid = = [dec], conw_cgid = [dec], conl_gid = [dec]
Explanation Directory services (DS) received an unexpected resource registration request from another node.
Recommended Action DS received a resource registration request from an invalid session. The session from which the received request was received is not one of the CP-CP sessions with the adjacent node. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSr10_LOGMSG_03 : DS - Resource Registration Request is not a REGISTER or a DELETE
Explanation Directory services (DS) received an invalid resource registration request from another node.
Recommended Action DS received an invalid resource registration request. The received request is not a resource registration or registration deletion request. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSr10_LOGMSG_04 : DS - LU name in Resource Registration duplicates non-cached directory entry
Explanation Directory services (DS) detected two resources with the same name.
Recommended Action DS 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. Probable causes of the error are a network definition error (two resources are defined with the same name), the remote node sending an invalid message, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSr10_LOGMSG_05 : DS - Resource Type field in cv3c in Resource Registration Request is not ENCP
Explanation Directory services (DS) received an invalid resource registration request from another node.
Recommended Action The type of resource contained in the control vector X'3C' is not an end node (X'00F4' - end node control point name). Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSr10_LOGMSG_06 : DS - Resource Type field in cv3d in Resource Registration Request is not ENCP or LU
Explanation Directory services (DS) received an invalid resource registration request from another node.
Recommended Action 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). Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSr20_LOGMSG_01 : DS - Resource Registration Reply received, but adjacent node cb does not exist or is not authorized, lu name = [chars], sense code = [hex]
Explanation Directory services (DS) received an unexpected resource registration reply from another node.
Recommended Action The adjacent node name in the registration reply does not match any adjacent node records in the directory. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSr20_LOGMSG_02 : DS - Resource Registration Reply has an invalid length
Explanation Directory services (DS) received an invalid resource registration reply from another node.
Recommended Action 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. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSr20_LOGMSG_03 : DS - Resource Registration Reply received from an invalid session (not CP-CP), adjacent cp name = [chars], cgid = [dec], conn winner gid = [dec], conn lose gid = [dec]
Explanation Directory services (DS) received an unexpected resource registration reply from another node.
Recommended Action DS received a resource registration reply from an invalid session. The session the received reply was received from is not one of the CP-CP sessions with the adjacent node. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSr20_LOGMSG_04 : DS - Resource Registration Reply is not a REGISTER or DELETE
Explanation Directory services (DS) received an invalid resource registration reply from another node.
Recommended Action DS received an invalid resource registration reply. The received reply is not a resource registration (GDS X'12C3') or registration deletion (GDS X'12C9') reply. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSr20_LOGMSG_05 : DS - First CV in Resource Registration Reply is not cv80
Explanation Directory services (DS) received an invalid resource registration reply from another node.
Recommended Action The first control vector in the received reply is not X'80' (register), or the length of the X'80' control vector is invalid. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSr20_LOGMSG_06 : DS - CV80 is not a REGISTER_REPLY
Explanation Directory services (DS) received an invalid resource registration reply from another node.
Recommended Action The request/reply indicator in the X'80' control vector (register) is invalid. It does not indicate that the received message is a reply. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSr20_LOGMSG_07 : DS - CV80 is not a DELETE_REPLY
Explanation Directory services (DS) received an invalid resource registration reply from another node.
Recommended Action DS 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. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSr20_LOGMSG_08 : DS - CV in Resource Registration Reply is too short
Explanation Directory services (DS) received an invalid resource registration reply from another node.
Recommended Action The length of one or more of the control vectors in the received reply is invalid, or the length of the containing GDS variable is invalid. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSr20_LOGMSG_09 : DS - Resource Registration Reply error: TP failure
Explanation The directory services (DS) resource registration receive transaction program failed.
Recommended Action The transaction program used by DS to receive resource registration replies encountered an error while trying to receive a registration reply. Probable causes of the error are a serious memory shortage, the remote node sending an invalid message, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSr20_LOGMSG_10 : DS - Resource Registration failed for a resource, lu name = [chars], sense code = [hex]
Explanation Registration of a resource with its network node server failed.
Recommended Action 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. Probable causes of the error are a network definition error (the resource being registered is already defined in the network), the remote node encountering an unrecoverable error while processing the request, or the local node sending an invalid registration request. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSr20_LOGMSG_11 : DS - Resource Registration Delete Reply received, not supported
Explanation Directory services (DS) received an invalid resource registration reply from another node.
Recommended Action The reply is to a resource deletion request. The local DS does not send resource deletion requests, so it should never receive a resource deletion reply. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSr20_LOGMSG_12 : DS - Unable to find directory entry for correlator in resource registration negative reply
Explanation Registration of a resource with its network node server failed.
Recommended Action The local node's network node server or central directory server rejected a resource registration request from the local node. DS cannot correlate the resource identified in the reply to any resource defined in the local directory. Probable causes of the error are corrupted data in the directory, a programming error in the local node, or the remote node sending an invalid message. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSs02_LOGMSG_01 : DS - start send_search transaction program failed
Explanation An operating system function failed while trying to start the directory services send_search transaction program.
Recommended Action Directory services could not start the transaction program used to send search requests (locates and CP outage notifications) to adjacent nodes. Probable causes are an operating system error occurring while attempting to start the transaction program (TP) process, one or more missing required files (preventing the creation of the TP process), a serious memory shortage problem, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsDS_NEWDSs02_LOGMSG_02 : DS - start en_rsc_registration transaction program failed
Explanation An operating system function failed while trying to start the directory services en_rsc_registration transaction program.
Recommended Action 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. Probable causes are an operating system error occurring while attempting to start the transaction program (TP) process, one or more missing required files (preventing the creation of the TP process), a serious memory shortage problem, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsInvalid_LR : DS - Invalid locate record detected
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action There is an internal code problem in the DS component. A invalid locate record was encountered. One or more of the fields in the record are invalid. Probable causes of the error are corrupted data in the directory or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsLR_CP_NAME : DS - DBset_lr_cp_name invoked
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action There is an internal code problem in the DS component. An invalid internal function was invoked. The internal routine DBset_lr_cp_name() is no longer valid and should not be invoked by directory services. There is a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsLR_FQPCID : DS - DBset_lr_fqpcid invoked
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action There is an internal code problem in the DS component. An invalid internal function was invoked. The internal routine DBset_lr_fqpcid() is no longer valid and should not be invoked by directory services. There is a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsLR_PCID_modifier : DS - DBset_lr_PCID_modifier invoked
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action There is an internal code problem in the DS component. The internal routine DBset_lr_PCID_modifier() is no longer valid and should not be invoked by directory services. There is a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsLR_SEARCH_NUM : DS - DBset_lr_search_num invoked
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action There is an internal code problem in the DS component. The internal routine DBset_lr_search_num() is no longer valid and should not be invoked by directory services. There is a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsLR_SEARCH_ROLE : DS - DBset_lr_search_role invoked
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action There is an internal code problem in the DS component. An invalid internal function was invoked. The internal routine DBset_lr_search_role() is no longer valid and should not be invoked by directory services. There is a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logdsNULLPOINTER : DS - NULL POINTER
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action There is an internal code problem in the DS 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 DS control block. Probable causes of this error are corrupted data in the directory or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-loghpcFRR : HPC Process entered FRR
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-loghpcHASM_DEQD_UNKWN_MU : HPC Process dequeued an unknown MU
Explanation The high-performance routing address space manager (HPR ASM) received an SNA message (MU) that it does not recognize or cannot process.
Recommended Action HPR ASM processes only session messages (such as BIND and UNBIND). There is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-loghpcHASM_DEQD_UNKWN_Q : HPC Process dequeued from an unknown Q
Explanation A high-performance routing address space manager (HPR ASM) received an interprocess signal (IPS) via an unrecognized process queue.
Recommended Action There is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-loghpcHPC_ALERT : HPC Process sending an Alert to MS
Explanation High-performance routing (HPR) path control generated an alert.
Recommended Action The HPR path control, address space manager, or session connector detected an alert condition and sent the formatted SNA alert to MS for transmission to its alert focal point. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-loghpcHPC_BAD_FSM_RR_COMBO : HPC Bad FSM receive router combination
Explanation An instance of high-performance routing path control (HPR PC) received an SNA message that it does not recognize or cannot process.
Recommended Action The HPR path control receive router FSM sent an unknown or invalid action code. Probable causes of this error are an invalid message was received or a message was received out of sequence. There is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-loghpcHPC_DEQD_UNKWN_IPS : HPC dequeued an unknown IPS
Explanation The high-performance routing address space manager (HPR ASM) or an instance of HPR path control received an internal interprocess signal that it does not recognize or cannot process.
Recommended Action There is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-loghpcHPC_DEQD_UNKWN_MU : HPC dequeue unknown MU
Explanation The high-performance routing path control (HPR PC) received an SNA message (MU) that it does not recognize or cannot process.
Recommended Action There is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-loghpcHPC_DEQD_UNKWN_RQ : HPC Process dequeued an unknown RU request code
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-loghpcHPC_DEQD_UNKWN_RQ_1STSG : HPC dequeued an unknown RU request code in the first segment
Explanation The high-performance routing path control (HPR PC) received an SNA message (MU) that it does not recognize or cannot process.
Recommended Action The received message is the first segment in a multisegmented message. There is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-loghpcHPC_DEQD_UNKWN_RQ_LSTSG : HPC dequeued an unknown RU request code in the last segment
Explanation The high-performance routing path control (HRP PC) received an SNA message (MU) that it does not recognize or cannot process.
Recommended Action The received message is the last segment in a multisegmented message. The request code was obtained from the first segment. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-loghpcHPC_DEQD_UNKWN_RQ_MIDSG : HPC dequeued an unknown RU request code in the middle segment
Explanation The high-performance routing path control (HPR PC) received an SNA message (MU) that it does not recognize or cannot process.
Recommended Action The received message is a middle segment in a multisegmented message. The request code was obtained from the first segment. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-loghpcHPC_DEQD_UNKWN_RQ_ONYSG : HPC dequeued an unknown RU request code in the only segment
Explanation The high-performance routing path control (HPR PC) received an SNA message (MU) that it does not recognize or cannot process.
Recommended Action The received message is a single-segment message. There is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-loghpcHPC_DQD_UNK_RTP_IPS : HPC dequeued unknown RTP IPS
Explanation An instance of high-performance routing path control (HPR PC) received an invalid IPS message from a DLC or rapid transport protocol (RTP).
Recommended Action The received IPS was a DLC message not recognized or supported by HPR path control. There is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-loghpcHPC_MU_ERR_CHK_FAILED : HPC MU error checker failed
Explanation An instance of high-performance routing path control (HPR PC) received an SNA message (MU) that contains SNA headers whose TH or RH settings are invalid.
Recommended Action 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). Probable causes of this error are the remote node sending an invalid message, a programming error in the local node, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-loghpcHPC_SC_CANT_GET_SC_CB : HPC SC can't get SC CB
Explanation A high-performance routing session connector (HPR SC) received an internal interprocess signal, but cannot find the control blocks associated with the session connector.
Recommended Action The HPR path control/session connector main process received an interprocess signal that it cannot route. The logical process identified in the signal is a session connector using HPR, but the process-specific control blocks cannot be located. There is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-loghpcHPC_SC_DQD_UNK_IPS : HPC SC dequeued unknown IPS
Explanation The high-performance routing path control (HPR PC) received an internal interprocess signal that it does not recognize or cannot process.
Recommended Action There is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-loghsINVALID_MASK_GEN : Invalid Jump Table Mask Generated, hs lpid = [hex], mask = [hex]
Explanation A half-session (HS) cannot parse the SNA request header in an SNA message.
Recommended Action A half-session for an LU could not compute an internal hash value from the SNA request header contained in an SNA message. The SNA message can either be an outbound message being sent by the local node or an inbound message received from a remote node. Probable causes of this error are a programming error in the local node or the remote node sending an invalid message. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-loghsPROTOCOL_ERROR_IN_DFC : Session level protocol error detected, hs lpid = [hex], sense code = [hex]
Explanation An SNA protocol error was detected while half-session (HS) (data flow control) was processing a message.
Recommended Action 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. Probable causes of this error are the remote node sending an invalid message, the local transaction program or SNA component sending an invalid message, a programming error in the local node, a software problem in the node that sent the message, or incompatible APPC/APPN support in the remote node (with the local APPC/APPN support). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-loghsUNKNOWN_IPS_RCVD : Unknown IPS Received, hs lpid = [hex], ips name = [hex]
Explanation A half-session (HS) for an LU received an internal interprocess signal it does not recognize or cannot process.
Recommended Action There is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsASSIGN_PCID_FAILED : MS: Assign PCID failed, rc = [hex]
Explanation Management services (MS) encountered an unrecoverable error.
Recommended Action Management services encountered an error trying to obtain the local node's procedure correlator identifier (PCID) value from session services. Probable causes of this error are a system function failure (preventing the transmission of the internal message), a serious memory shortage, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsCSWMSAPI_LOGMSG_01 : MSAPI: PQENQ FP information to APPL PID failed, application pid = [hex]
Explanation Management services (MS) encountered a problem trying to send a message to a management services application.
Recommended Action 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. Probable causes of this error are an operating system error occurring while attempting to send the message, a serious memory shortage, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsCSWMSAPL_LOGMSG_01 : MSAPL: Same APPL name with different PIDS encountered, appl name = [chars], pid = [hex], application entry pid = [hex]
Explanation Management services (MS) received duplicate application registration requests.
Recommended Action The application name in the registration request has already been registered before with a different process ID. Probable causes of this error are the MS application starting multiple times, two different applications using the same application name, or the application ending, restarting, and trying to reregister with a new PID. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsCSWMSAPL_LOGMSG_02 : MSAPL: APPL name not found, appl name = [chars].
Explanation Management services (MS) encountered a problem while updating the MS application list.
Recommended Action MS could not find the MS application name in the application list while trying to delete the application from the list or to increase the counters associated with the application. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsCSWMSAPS_BAD_DEST_APPL : MSAPS: Invalid destination APPL name, dest_fq_cp_name = [chars], origin_appl = [chars], dest_appl = [chars], seq_no = [hex], pid = [hex]
Explanation Management services (MS) encountered a problem trying to send a message.
Recommended Action 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. Probable causes of this error are the originator of the MDS message specifying an incorrect destination or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsCSWMSAPS_BAD_DEST_CP : MSAPS: Invalid fully qualified destination CP name, dest_fq_cp_name = [chars], origin_appl = [chars], dest_appl = [chars], seq_no = [hex]
Explanation Management services (MS) encountered a problem trying to send a message.
Recommended Action The request did not specify a valid network-qualified destination control point name. Probable causes of this error are the originator of the MDS message specifying an incorrect destination or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsCSWMSAPS_BAD_ORIG_APPL : MSAPS: Invalid original APPL name, dest_fq_cp_name = [chars], origin_appl = [chars], dest_appl = [chars], seq_no = [hex]
Explanation Management services (MS) encountered a problem trying to send a message.
Recommended Action 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. Probable causes of this error are the originator of the MDS message specifying an incorrect destination or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsCSWMSAPS_TP_APPL_FAILED : MSAPS: Sending error message TP failed, origin_appl = [chars], pid = [hex], seq_no = [hex]
Explanation Management services (MS) encountered a problem trying to send a message.
Recommended Action 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. Probable causes of this error are the originator of the MDS message specifying an incorrect destination, an operating system error occurring while attempting to send the error message, a serious memory shortage, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsCSWMSCAP_LOGMSG_01 : MSCAP: cannot process received MS capability
Explanation Management services (MS) does not recognize a subvector contained in a received MS capabilities message (x'80F0' major vector).
Recommended Action The received MS capabilities message contains one or more control vectors not recognized by management services. Probable causes of this error are the message containing subvectors used only by MS focal points, the remote node sending an invalid message, or a programming error in the local node. Unless a network configuration error exists, there is probably a software problem in the node that sent the message or the APPC/APPN support in the remote node is incompatible with the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsCSWMSCAP_LOGMSG_02 : MSCAP: Trying to build unknown MS CAP
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action MS detected an error while processing a request to build and send an MS capabilities message. The request specified an invalid MS capabilities message type. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsCSWMSCAT_LOGMSG_01 : MSCAT: CACHED_MSG not found from UOW
Explanation Management services (MS) encountered a problem trying to correlate a received MS error message (SNA condition report, or SNACR) with an outstanding MS request.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-logmsCSWMSCAT_LOGMSG_02 : MSCAT: MS_TRANSPORT not marked by UOW
Explanation 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.
Recommended Action The error message indicated that the focal point was lost. MS is trying to locate the originating message so it can 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. There is programming error in the local node. The unit-of-work is logged in a related log record (2F103000-00000035). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsCSWMSRAP_LOGMSG_01 : MSRAP: Error trying to register as FP, pid = [hex]
Explanation Management services (MS) MS_CAPS received an application request to be registered as a focal point.
Recommended Action An MS application has requested to register itself as a focal point application. This function is not supported, so the request is ignored. Probable causes of this error are a user trying to start a focal point application on this node, or a non-FP application falsely identifying itself as a focal point application. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsCSWMSRAP_LOGMSG_02 : MSRAP: Error trying to register with duplicate PID, pid = [hex]
Explanation Management services (MS) received duplicate application registration requests.
Recommended Action The application name in the registration request has already been registered with a different process Probable causes of this error are the MS application starting multiple times, two different applications using the same application name, or the application ending, starting and trying to reregister with a new PID. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsCSWMSRAP_LOGMSG_03 : MSRAP: Send registration response to APPL failed, application name = [chars]
Explanation Management services (MS) could not send the results of a registration request back to the MS application.
Recommended Action Probable causes of this error are a system function failure (preventing the transmission of the internal message), or a serious memory shortage. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsCSWMSRAP_LOGMSG_04 : MSRAP: APPL name not found for de-registration, application name = [chars]
Explanation Management services (MS) encountered a problem while processing a deregistration request from an application.
Recommended Action MS could not find the MS application name in the list of active MS applications. Probable causes of this error are the application not registering itself, the application specifying an incorrect name on the deregistration request, or a software problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsCSWMSRAP_LOGMSG_05 : MSRAP: APPL name not found for deletion, application name = [chars]
Explanation Management services (MS) encountered a problem while updating the MS application list.
Recommended Action MS could not find the MS application name in the application list while attempting to remove the application from the list. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsCSWMSRBM_LOGMSG_01 : MSRBM: GDS_CP_MSU not found by set_held_alert_flag_on
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action 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 did not contain a valid CP-MSU. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsCSWMSRBM_LOGMSG_02 : MSRBM: GDS_CP_MSU not found by set_buffered_flag_on
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action 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 did not contain a valid CP-MSU. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsCSWMSUTL_LOGMSG_01 : MSUTL: Time not found from UOW
Explanation Management services received an invalid MS message.
Recommended Action MS could not locate the time stamp subvector (x'02') in the received unit-of-work correlator. Probable causes of this error are the message containing an invalid unit-of-work correlator, the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsCSWMSUTL_LOGMSG_02 : MSUTL: Cannot find CP_MSU from GDS DATA
Explanation Management services (MS) detected an error while trying to parse a received MS error message.
Recommended Action MS detected a serious error in an 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. Probable causes of this error are the originator of the MDS message not formatting the message correctly or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsCSWMSUTL_LOGMSG_03 : MSUTL: Cannot parse CP_MSU from GDS DATA
Explanation Management services (MS) detected an error while trying to parse a received MS error message.
Recommended Action MS detected a serious error in an 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. Probable causes of this error are the originator of the MDS message not formatting the message correctly or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsCSWMSUTL_LOGMSG_04 : MSUTL: Cannot find SNA_REPORT_CODE SV from SNACR GDS DATA
Explanation Management services (MS) detected an error while trying to parse a received MS error message.
Recommended Action MS detected a serious error in an 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 subvector (x'7D'). The sense code identifying the error that generated the message cannot be located. Probable causes of this error are the originator of the MDS message not formatting the message correctly or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsDISPLAY_CONSOLE_BUFFER : MS: Displaying console buffer
Explanation Management services (MS) detected an error while trying to parse a received error message.
Recommended Action This log record is created along with other log records to identify the type of error that was detected by MS. Refer to the related log entries and messages for more information and other recommended actions.
Error Message%APPN-6-LogMsg : [chars]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsMDS_MU_ERROR : MS: MDS_MU received with error, sense_data = [hex]
Explanation Management services (MS) encountered an error processing a received MS message.
Recommended Action This log record is created along with other log records to identify the type of error that was detected by MS. Refer to the related log entries and messages for more information and other recommended actions.
Error Message%APPN-3-logmsPQENQ_FAILED : MS: PQenq failed, pid = [hex]
Explanation Management services (MS) encountered a problem while trying to send a message to a management services application program.
Recommended Action The request to send the MS message (PQenq) failed. Probable causes of this error are an operating system error occurring while attempting to send the message, a serious memory shortage, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsPQENQ_FAILED_ABEND : MS: PQenq FAILED, MS ABENDING
Explanation Management services (MS) could not send a request to another node component.
Recommended Action MS sends requests to directory services to search for destination nodes (that is LOCATE messages) and the control point's resource manager to start one of the MS service transaction programs. Probable causes of this error are a system function failure occurring (preventing the transmission of the internal message), a serious memory shortage, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsSVKEY_NOT_FOUND : MSSVL: Subvector key not found, key = [hex]
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action 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 subvector. For inbound messages, probable causes of this error are the remote node sending an invalid message, a programming error in the local node, a software problem (probably in the node that sent the message), or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. For outbound messages, the probable cause is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsSVLIST_EMPTY : MSSVL: SV LIST empty
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action 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 subvector. For inbound messages, the probable causes of this error are the remote node sending an invalid message, a programming error on the local node, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. For outbound messages, the probable cause is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsUNKNOWN_ALERT : Processing an unknown ALERT, storage in signal queue is lost, id = [hex], sender_name = [chars], failing_module = [chars], detecting_module = [chars]
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action MS detected an error while processing a request to build and send an alert. The request specified an unrecognized alert ID. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsUNKNOWN_CAP : Processing an unknown CAP
Explanation Management services (MS) does not recognize a subvector contained in a received MS capabilities message (x'80F0' major vector).
Recommended Action The received MS capabilities message contains one or more control vectors not recognized by management services. Probable causes of this error are the message containing subvectors used only by MS focal points, the remote node sending an invalid message, or a programming error in the local node. Unless a network configuration error exists, there is probably a software problem in the node that sent the message or the APPC/APPN support in the remote node is incompatible with the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsUNKNOWN_GDS : Processing an unknown GDS, gds key = [hex]
Explanation Management services (MS) does not recognize a message received from another node.
Recommended Action The local node does not recognize the GDS variable contained in a message. The only MS capabilities messages processed by the local node are CP-MSU (control point management services units), MS capabilities messages, and SNACRs (SNA condition reports). Probable causes of this error are the remote node sending an invalid message, a programming error in the local node, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsUNKNOWN_ID_FOR_ALERT : MS: Unknown ID for alert, id = [hex]
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action MS detected an error while processing a request to build and send an alert. The request specified an unrecognized alert ID. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXID_NO_DATA : MS: xid_psid_sv_p passed by CS has no data
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action MS detected an error while processing a request to build and send an alert from configuration services. The alert request received from configuration services (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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXID_NULL : MSP79: xid_psid_sv_p passed by CS = NULL
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action MS detected an error while processing a request to build and send an alert from configuration services. The alert request received from configuration services (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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXXXMSP03_LOGMSG_01 : MSP03: Unknown local node type encountered, node_type = [hex]
Explanation Management services (MS) encountered an error while processing an interprocess signal.
Recommended Action MS received a CP_STATUS signal from session services (SS) for a network node, but the local node type indicator is invalid. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXXXMSP03_LOGMSG_02 : MSP03: CP status for EN-EN session
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action MS 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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXXXMSP03_LOGMSG_03 : MSP03: Misdefined as network node
Explanation Management services (MS) encountered an error while processing an interprocess signal.
Recommended Action MS 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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXXXMSP03_LOGMSG_04 : MSP03: Misdefined as virtual node
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action MS received an unexpected CP_STATUS signal from session services (SS). The CP_STATUS update is for a virtual node (connection network). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXXXMSP03_LOGMSG_05 : MSP03: CP status received from unknown node type, node_type = [hex]
Explanation Management services (MS) encountered an error while processing an interprocess signal.
Recommended Action MS 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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXXXMSP04_LOGMSG_01 : MSP04: EN received data from another node
Explanation Management services (MS) received an unexpected MS message.
Recommended Action MS received an MS message in which the local node is not the final destination. This should not occur because 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. Probable causes of this error are the remote node believing the local node is a network node, the remote node sending an invalid message, a programming error in the local node, a network configuration error, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXXXMSP04_LOGMSG_02 : MSP04: Tried to use specified LU name for ISR, partner_lu_name = [chars]
Explanation Management services (MS) received an unexpected MS message.
Recommended Action MS 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, because 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. Probable causes of this error are the remote node believing the local node is its serving network node, the remote node sending the message over an invalid session, a programming error in the local node, a network configuration error, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXXXMSP04_LOGMSG_03 : MSP04: Tried to send to this node, partner_lu_name = [chars], destination_name = [chars]
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action MS 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, because 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. Probable causes of this error are the remote node believing the local node is its serving network node, the remote node sending the message over an invalid session, a programming error in the local node, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXXXMSP04_LOGMSG_04 : MSP04: Destination application not recognized, rc = [hex]
Explanation Management services (MS) received an MS message for an unrecognized MS application.
Recommended Action MS received an MS message it could not route locally. The destination MS application name is not recognized by management services. That is, it is not EP_ALERT, MS_CAPS, or any of the other registered MS applications. Probable causes of this error are the originator of the MDS message specifying the wrong MS application name, the destination application not registering with MS or deregistering before the message was received, the remote node sending an invalid message, a programming error in the local node, a software problem probably in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXXXMSP09_LOGMSG_01 : MSP09: NN information routed to EN, node_type = [hex]
Explanation Management services (MS) received an unexpected MS message.
Recommended Action MS 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 is a network node, it recomputes the route and resends the message, assuming that the network information it used to send the original message is out of date. However, because 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. Probable causes of this error are the local node sending the original message over an invalid session, the remote node sending the message over an invalid session, a programming error in the local node, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXXXMSP12_LOGMSG_01 : MSP12: Should not have received MS Caps 62, dest_appl = [chars]
Explanation Management services (MS) received an unexpected MS message.
Recommended Action MS received an invalid MS capabilities message from an MS migration node. The MS capabilities message was a focal point authorization reply (x'62'). Probable causes of this error are the remote node sending an invalid message, a programming error in the local node, a software problem probably in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXXXMSP12_LOGMSG_02 : MSP12: ATL not found for 0x64. This should not happen
Explanation Management services (MS) received an unexpected MS message.
Recommended Action MS 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. Probable causes of this error are the remote node sending an invalid message, a programming error in the local node, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXXXMSP12_LOGMSG_03 : MSP12: Unknown MS Caps SV received, sv_key = [hex]
Explanation Management services (MS) received an invalid MS message.
Recommended Action MS received an unexpected 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. Probable causes of this error are the remote node sending an invalid message, a programming error in the local node, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXXXMSP12_LOGMSG_04 : MSP12: Missing MS Caps SV. This should not happen, key = %lx
Explanation Management services (MS) received an invalid MS message from an MS migration node.
Recommended Action MS 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. Probable causes of this error are the remote node sending an invalid message, a programming error in the local node, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXXXMSP12_LOGMSG_05 : MSP12: Non CP_MSU received. This should not happen, cp_msu = %lx
Explanation Management services (MS) received an invalid MS message from an MS migration node.
Recommended Action MS received an invalid MS message from an MS migration node. The message was not a CP-MSU (GDS variable x'1212'). Probable causes of this error are the remote node sending an invalid message, a programming error in the local node, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXXXMSP16_LOGMSG_02 : MSP16: Bad response code from start_tp, response_code = [hex]
Explanation Management services (MS) encountered a problem trying to start a management services service transaction program.
Recommended Action The control point resource manager replied to the request to start the transaction program (TP) with an error code. The service transaction program is not started. Probable causes of this error are an operating system error occurring while attempting to start the TP process, one or more missing required files (preventing the creation of the TP process), a serious memory shortage, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXXXMSP16_LOGMSG_03 : MSP16: Pcreate failed, returned pid = [hex]
Explanation Management services (MS) encountered a problem trying to start a management services service transaction program.
Recommended Action The request to start the service transaction program (Pcreate) failed. Probable causes of this error are an operating system error occurring while attempting to start the transaction program (TP) process, one or more missing required files (preventing the creation of the TP process), a serious memory shortage, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXXXMSP17_LOGMSG_01 : MSP17: PQENQ failed to SS. MS abending
Explanation Management services (MS) could not send an internal request (IPS) to session services.
Recommended Action The function PQenq failed. Probable causes of this error are a system function failure occurring (preventing the transmission of the internal message), a serious memory shortage, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXXXMSP18_LOGMSG_01 : MSP18: No MDS_CTL, verification bit not set
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action 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 subvector (x'90') within the MDS routing variable. The MS message is invalid. For inbound messages, probable causes of this error are the remote node sending an invalid message, a programming error in the local node, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. For outbound messages, the probable cause is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXXXMSP19_LOGMSG_01 : MSP19: Message to migration node, but dest APPL is not ALERT NETOP nor MS CAPS
Explanation Management services (MS) MDS router received an incorrectly routed message.
Recommended Action MS 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. Probable causes of this error are the originator of the MDS message specifying the wrong MS application name, the remote node sending an invalid message, or a programming error in the local node. Unless an application in the local node specified an invalid destination application, there is probably a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXXXMSP19_LOGMSG_02 : MSP19: PQenq to tp failed, ms_transport tossed
Explanation Management services (MS) encountered a problem trying to send a message to a management services service transaction program.
Recommended Action The request to send the MS message (PQenq) failed. Probable causes of this error are an operating system error occurring while attempting to send the message, a serious memory shortage, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXXXMSP23_LOGMSG_01 : MSP23: Destination nau name not located, destination nau name = [chars]
Explanation Management services (MS) detected an error while trying to send an MS message.
Recommended Action The local node cannot find the destination (LU or control point) specified in the MS message. The search of the APPN network for the destination failed. Probable causes of this error are the originator of the MDS message specifying the wrong destination LU, the remote node owning the destination LU not currently being available, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXXXMSP29_LOGMSG_01 : MSP29: Message to unknown APPL name
Explanation Management services (MS) detected an error while trying to send an MS message to a local MS application.
Recommended Action 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. Probable causes of this error are the destination application not being started, the destination application not registering itself, the originator of the MDS message specifying the wrong destination LU, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXXXMSP29_LOGMSG_02 : MDP29: No sense code in the error message to APPL, message discarded
Explanation Management services (MS) detected an error while trying to send an MS message to a local MS application.
Recommended Action MS detected a serious error in an 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. Probable causes of this error are the originator of the MDS message not formatting the message correctly or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logmsXXXMSP70_LOGMSG_01 : MSP70: Received invalid major vector, vector = [int]
Explanation Management services (MS) encountered a problem trying to send an alert.
Recommended Action The size of the alert (the alert major vector) in the message is too small or too large. There is a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-lognofASM_ID_NOT_FOUND : NOF unable to find ASM process ID in recovered subsystem ssid, ssid = [chars]
Explanation Node operator facility (NOF) could not find the address space manager (ASM) process in a recovered subsystem.
Recommended Action NOF is in the process of restarting a recovered subsystem (coprocessor). NOF could not locate the ASM process in the recovered subsystem, so it cannot load the subsystem with the list of NAUs (control point and LUs) defined locally to the APPN node. Probable causes of this error are the ASM in the recovered subsystem not starting or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-lognofBAD_SUBSYSTEM_STATE : NOF received SS_AVAILABLE - subsytem is in an incompatible state, ssid_number = [hex], status_1 = [hex], state = [hex]
Explanation Node operator facility (NOF) received a notification IPS (SS_AVAILABLE) that contains unexpected data.
Recommended Action The notification was sent to inform NOF that an environment manager process (probably in an attached coprocessor) that ended has been restarted. The status indicators in the notification indicate that the subsystem is not loaded, or that the subsystem is loaded and the node is operational and available. There is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-lognofCANT_CREATE_PROCESS : NOF could not create a node process in a subsystem, process_name = [chars], ss_id = [chars]
Explanation A surrogate NOF process in an attached coprocessor could not create a local process in the attached subsystem (coprocessor).
Recommended Action The function Pcreate failed. Probable causes of this error are a system function failure occurring (preventing the creation of the node process), a serious memory shortage, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-lognofCANT_MAKE_PROC_ON_SSID : NOF could not create environment in a subsystem, ss_id name = [chars]
Explanation The node operator facility (NOF) process in the control point could not create the environment manager process in an attached subsystem (coprocessor).
Recommended Action Probable causes of this error are a system function failure (preventing the creation of environment manager), one or more missing required files (preventing the creation of environment manager), a serious memory shortage, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-lognofCANT_SEND_RQST_CREATE : Could not send REQUEST_CREATE message
Explanation The main node operator facility (NOF) process in the APPN node control point cannot send a process create message to the surrogate NOF in an attached coprocessor.
Recommended Action The command to send the creation request (REQUEST_CREATE IPS message) to the surrogate NOF process (PIM) in the coprocessor failed. The function PQenq failed. Probable causes of this error are a system function failure occurring (preventing the activation of the surrogate NOF process in the attached coprocessor), an error sending the IPS message to the surrogate NOF process, a serious memory shortage, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-lognofCOULD_NOT_CREATE_PROC : NOF could not create a node process, process name = [chars]
Explanation The main node operator facility (NOF) process in the APPN control point could not create a local process in the control point processor.
Recommended Action The function Pcreate failed. Probable causes of this error are a system function failure (preventing the creation of the node process), a serious memory shortage, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-lognofDATA_DUMP : NOF - Additional data for previous event
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-lognofDLC_NAME_ACTV_VCB : Required dlc_name not found in ACTIVATE_DLC VCB
Explanation Node operator facility (NOF) rejected an ACTIVATE_DLC verb because the DLC name in the verb (dlc_name) was not specified.
Recommended Action The ACTIVATE_DLC verb is rejected, so the specified data-link control is not started. Reissue 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 reload the configuration.
Error Message%APPN-3-lognofDLC_NAME_DEACTV_VCB : Required dlc_name not found in DEACTIVATE_DLC VCB
Explanation Node operator facility (NOF) rejected a DEACTIVATE_DLC verb because the DLC name in the verb (dlc_name) was not specified.
Recommended Action The DEACTIVATE_DLC verb is rejected, so the specified data-link control is not stopped. Reissue 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 reload the configuration.
Error Message%APPN-3-lognofDLC_NAME_WAS_NOT_FOUND : DEFINE_DLC dlc name is not specified
Explanation A DEFINE_DLC verb was rejected because the DLC name in the verb (dlc_name) was not specified.
Recommended Action The DEFINE_DLC verb is rejected, so the specified data-link control is not created or started. Reissue 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 reload the configuration.
Error Message%APPN-3-lognofENV_RSP_INV_CORREL : NOF received PE_CREATE_ENVIRONMENT_RSP with invalid correlator
Explanation Node operator facility (NOF) received a response interprocess signal (IPS) (PE_CREATE_ENVIRONMENT_RSP) that it could not correlate.
Recommended Action The response is from a request to create an environment, probably in an attached coprocessor. NOF could not correlate the response to any of its outstanding creation requests. There is an internal code problem in the local NOF or environment manager. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-lognofEXCEPTION_RSP_RCVD : NOF received exception response, sense_code = [hex], ips_name = [hex]
Explanation A node component encountered an error while processing a node operator facility (NOF) request.
Recommended Action The other component sent an EXCEPTION_RSP IPS message indicating the failure. The EXCEPTION_RSP message contains a sense code that identifies the cause of the failure. Probable causes of this error are an unrecoverable system error, detection of a configuration error by the node, not all required software components being installed or available for use by the node, a serious memory shortage, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-lognofFQ_ADJ_CPNAME_NOT_FOUND : DEFINE_LINK adjacent CP name is invalid or not specified when required, adj_cp_name = [chars]
Explanation Node operator facility (NOF) rejected a DEFINE_LINK verb because the value of the adjacent CP name in the verb (fq_adj_cpname) is invalid or is missing.
Recommended Action The error occurred because of a specified adjacent CP name that was not a network-qualified, SNA type-a character name or because the node specified is a LEN node and the adjacent CP name was not specified. The DEFINE_LINK verb is rejected, so the link to the adjacent node is not defined. Reissue 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 reload the configuration.
Error Message%APPN-3-lognofIBM_COS_NOT_DELETED : IBM defined COS names (CPSVCMG or SNASVCMG) cannot be deleted
Explanation Node operator facility (NOF) rejected a DELETE_COS verb because the specified class-of-service name was CPSVCMG or SNASVCMG.
Recommended Action A DELETE_COS verb was rejected because it attempted to delete a class-of-service definition (CPSVCMG or SNASVCMG) that is required by the APPN node. The DELETE_COS verb is rejected, so the class-of-service definition is still defined. The specified class-of-service cannot be deleted. No action is required unless you meant to delete a different class-of-service definition and specified the name incorrectly. If so, reissue the verb with the correct name.
Error Message%APPN-3-lognofINVALID_EID : NOF received PE_LOST_ENVIRONMENT with invalid EID, eid = [hex]
Explanation Node operator facility (NOF) received a notification interprocess signal (IPS) (PE_LOST_ENVIRONMENT) that it could not correlate.
Recommended Action The notification was sent by environment manager to inform operator facility (OF) that an environment manager process (probably in an attached coprocessor) ended. NOF could not correlate the notification to any of the subsystems (coprocessors) that it is using. There is an internal code problem in the local NOF. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-lognofNO_MS_CNTL_MSG_TO_SCM : NOF could not send MS cntl message to SCM, send_pid = [hex]
Explanation Node operator facility (NOF) could not send an interprocess signal (IPS) to the session connector manager to request accounting data.
Recommended Action 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 function PQenq failed. Probable causes of this error are a system function failure (preventing the transmission of the IPS to the session connector manager), a serious memory shortage problem, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-lognofPAP01_ERROR_RECOV : WARNING PAP01 error recovery was called, event == not Rcld([hex]), qualifier = [hex]
Explanation A node process encountered an unrecoverable error and abended.
Recommended Action The node continues to execute. Node operator facility (NOF) detected that one or more local processes abended with an unrecoverable error. Probable causes of this error are an internal code problem in the local system, an unrecoverable system error, or a serious memory shortage. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-lognofPDQENQ_ERROR : NOF - Error in PDqenq, rc = [hex], cfg_did = [hex]
Explanation The main node operator facility (NOF) process in the node control point cannot forward an IPS message to the configuration control component in the system.
Recommended Action The function PDQenq failed. Probable causes of this problem are a system function failure (preventing the sending of the IPS), a serious memory shortage, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-lognofPECREATE_ENV_FAILED : NOF - PEcreate_environment_failed, define_rc = [hex]
Explanation Node operator facility (NOF) could not create the processing environment required by the local system in the attached subsystem (coprocessor).
Recommended Action None of the ports or links supplied by the attached subsystem can be used by the node. The function PEdefine_subsystem failed. Probable causes of this error are a system function failure (preventing the creation of environment manager), not all required software components being installed or available for use by the node, a serious memory shortage, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-lognofPEDEFINE_SUBSYS_FAILED : NOF - PEdefine_subsystem failed, define_rc = [hex]
Explanation Node operator facility (NOF) could not create the processing environment required by the local system in the attached subsystem (coprocessor).
Recommended Action None of the ports or links supplied by the attached subsystem can be used by the node. The function PEdefine_subsystem failed. Probable causes of this error are a system function failure (preventing the creation of environment manager), not all required software components being installed or available for use by the node, a serious memory shortage, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-lognofRECVD_ABEND_NOTIF : NOF received abend notification from a process, abending_process = [chars], abending_process_id = [hex], lpid = [hex]
Explanation A node process notified node operator facility (NOF) sent a ABEND_NOTIFICATION to NOF, thereby notifying NOF that it is abending.
Recommended Action NOF detected that one or more local processes abended. The local 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. Probable causes of this error are an internal code problem, an unrecoverable system error, or a serious memory shortage. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-lognofRECVD_VAL_STRING_EXPCTD : NOF received an unexpected response IPS, ips_name = [hex], message_name = [chars]
Explanation Node operator facility (NOF) received an unexpected internal interprocess signal (IPS).
Recommended Action NOF was expecting a response from another node component, but received a different signal. There is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-lognofRQD_COS_NAME_NOT_FOUND : DEFINE_COS class-of-service name is invalid or not specified, cos_name = [chars]
Explanation Node operator facility (NOF) rejected a DEFINE_COS verb (cos_name) because the class-of-service name is invalid or was not specified.
Recommended Action This error occurred because you specified a COS name, but the specified value is not an SNA type-a character name, or because you did not specify a COS name. The DEFINE_COS verb is rejected, so the class-of-service definition is not created. Reissue 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 reload the configuration.
Error Message%APPN-3-lognofUNABLE_TO_MONITOR_EGPE : NOF unable to monitor environment manager, RC is %1
Explanation Node operator facility (NOF) could not add a notification to inform it when an environment manager process ends.
Recommended Action NOF is notified whenever the environment manager in the control point or a subsystem (coprocessor) ends. If environment manager ends, that subsystem is no longer available for use by the APPN node. The environment manager function PEstart_EGPE_down_monitor failed. Probable causes of this error are an internal code problem, an error occurring while trying to set up the monitor path between NOF and the environment manager environments, or a serious memory shortage. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-lognofUNEXPCTD_DOS_ERROR_RC : Unexpected system error while stopping the node
Explanation While the node operator facility (NOF) was stopping an APPN node, an operating system function failed.
Recommended Action NOF encountered a system error while NOF was processing an immediate stop request (STOP_APPN type=HARD). Probable causes of the error are the failure of the function PEstart_timer or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-lognofUNEXPCTD_SGNL : NOF received an unexpected signal from CS
Explanation Node operator facility (NOF) received an internal interprocess signal (IPS) from configuration services (CS) that it does not recognize or cannot process.
Recommended Action There is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-lognofUNEXPCTD_SGNL_SM_AM_RM : NOF received an unexpected signal from SM, AM or RM, ips_name = [hex]
Explanation Node operator facility (NOF) received an internal interprocess signal (IPS) from an APPC component (session manager, attach manager, or resource manager) that it does not recognize or cannot process.
Recommended Action There is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-lognofUNKNOWN_IPS_RECEIVED : NOF received unknown IPS from API, ips_name = [hex]
Explanation Node operator facility (NOF) received an internal interprocess signal containing an API verb that it does not recognize or cannot process.
Recommended Action There is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-lognofUNKNOWN_SSID : NOF received SS_AVAILABLE with unknown ss_id, ss_id = [hex]
Explanation Node operator facility (NOF) received a notification IPS (SS_AVAILABLE) that it cannot correlate.
Recommended Action NOF could not correlate the notification to any of the subsystems (coprocessors) that it is using. There is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-lognofUNKNOWN_VERB_RECEIVED : NOF received unknown verb from API, pri.rc = [hex], sec.rc = [hex]
Explanation Node operator facility (NOF) received an internal interprocess signal containing an API verb that it does not recognize or cannot process.
Recommended Action There is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-lognofUNRECOV_ERR_EVENT_RCLD : WARNING Unrecoverable Error: event == Rcld, qualifier = [dec], rc= [hex]
Explanation A node process encountered an unrecoverable error and abended.
Recommended Action Node operator facility (NOF) detected that one or more local processes abended with an unrecoverable error. Probable causes of this error are an internal code problem, an unrecoverable system error, or a serious memory shortage. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_ACTIVATE_AS_FAILED : ASM - Address Space cannot be activated, sense code = [hex]
Explanation The address space manager encountered an error while trying to create a new address space.
Recommended Action The address space manager could not create an address space for a new path control instance because 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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_AS_NOT_FOUND : ASM - Address Space was not found in the AS Table
Explanation The address space manager could not determine the address space responsible for handling the messages processed by a particular path control instance.
Recommended Action The address space for the path control instance does not exist. Probable causes of this error are a programming error within the local node or the remote node sending an invalid message. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_BIUI_RCV_CHECK : ASM - neither BIUI nor EBIUI was set when MU segmentation is not allowed
Explanation The address space manager received an invalid message.
Recommended Action The address space manager received a segmented message, but the received message should not be segmented. That is, the received message is not allowed to be segmented, but the segmentation indicators in the transmission header (TH) indicate the message is not a one-segment message. For example, UNBIND messages and messages received from a session services control point (SSCP) should not be segmented. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_CV_LENGTH_ERR : ASM - CV length error, remaining length = [hex]
Explanation The address space manager received a message containing invalid control vector information.
Recommended Action The lengths of a set of control vectors or subvectors do not correspond to the expected length indicated by the containing SNA vector. The address space manager received a message containing invalid control vectors. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_DEQD_UNKWN_IPS : ASM dequeued an unknown IPS, ips name = [hex]
Explanation The address space manager (ASM) received an internal signal (IPS) that it does not recognize or cannot process.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_DEQD_UNKWN_MU : ASM dequeued an unknown MU, header type = [hex]
Explanation The address space manager (ASM) received an SNA message (MU) that it does not recognize or cannot process.
Recommended Action ASM processes only session messages (such as BIND, UNBIND, or ACTPU/ACTLU). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_IPM_4_NONADAPT_PAC : ASM - IPM received while Adaptive Pacing is not supported by the node, sense code = [hex]
Explanation The address space manager received an unexpected BIND pacing message.
Recommended Action The address space manager received an SNA isolated pacing message (IPM) from a transmission group (TG) that is not allowed to perform adaptive pacing (that is, 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 from which the IPM was received. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_LFSID_IN_USE_REJ1 : ASM - the LFSID is in use, reject the BIND, sense code = [hex]
Explanation 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.
Recommended Action Probable causes of this error are the remote node sent an invalid message or lost the existing session, the APPC/APPN support in the remote node is not compatible with the local APPC/APPN support, or a network race condition may have occurred in which the remote node detected the loss of an existing session before the local node and sent a request using the same LFSID. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_LFSID_IN_USE_REJ2 : ASM - a NAU is being deleted and ASM is waiting for a LFSID_IN_USE_RSP, sense code = [hex]
Explanation The address space manager is rejecting any outstanding session creation requests because the LU or control point (CP) is being stopped.
Recommended Action 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 is not an error condition. The event is logged so that problem-determination personnel can determine why a session was rejected. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_LFSID_IN_USE_REJ3 : ASM - the LFSID is not in use, but has not been freed in ASM, sense_code = [hex]
Explanation The address space manager encountered an error while trying to accept a new session.
Recommended Action 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. One probable cause of this error is that a race condition occurred where the local node detected the loss of an existing session and is in the process of cleaning up the session when it receives a request from a remote node for a session with the same LFSID. Other probable causes are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_LRG_LFSID_RCV_CHECK : ASM - LFSID is out of bounds, large table is used, sidh = [hex], sense code = [hex]
Explanation The address space manager received a message containing an invalid or unrecognized LFSID.
Recommended Action Possible problems include the following. The SIDH value was 00, which is reserved for messages exchanged with a session services control point (SSCP), but the received message was not an SSCP message. The SIDH value was not 00, but the received message was an SSCP message. The SIDH value was 01, which should be reserved for BIND pacing, but the received message is not a BIND pacing message. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_MSG_DEQ_UNKN_Q : ASM - ASM message dequeued from unknown Queue, returned queue no. = [hex]
Explanation An address space manager received an interprocess signal (IPS) via an unrecognized process queue in the address space manager (ASM).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_NO_BUFF_4_IPM_ACK : ASM - Cannot get a buffer to build and send an IPM ack
Explanation The address space manager encountered an error while trying to respond to a BIND pacing message.
Recommended Action The address space manager could not send an acknowledgment to a BIND pacing message because it could not obtain the buffer needed to build the acknowledgment. Probable causes of this error are the local node not having enough memory available to accept any new BIND requests for the related address space (TG), a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_PREM_END : ASM ending prematurely
Explanation The address space manager (ASM) process unexpectedly exited its internal signal processing loop.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_RCV_BIND_BAD_SIDH : ASM - The BIND received contains an invalid sidh value
Explanation The address space manager received an invalid BIND message.
Recommended Action The address space manager could not process a received session initiation request (BIND). The LFSID contained in the BIND was invalid (bad SIDH value). Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_RCV_BIND_RU_ERROR : ASM - BIND RU error(s), reject the BIND, sense code = [hex]
Explanation The address space manager received an invalid BIND message.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-logpcASM_RCV_IPM_0_SEND_NWS : ASM - Received a solicited IPM but the next window size is zero, sense code = [hex]
Explanation The address space manager received an invalid pacing message.
Recommended Action The address space manager could not process a received pacing message (IPM) because 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. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_RCV_IPM_PACING_ERR1 : ASM - Received a reset ack and this node does not support adaptive bind pacing, sense code = [hex]
Explanation The address space manager received an unexpected BIND pacing message.
Recommended Action 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. More specifically, 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 acknowledgment is for a message that was never sent. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_RCV_IPM_PACING_ERR2 : ASM - Received an UNKNOWN ipm, sense code = [hex]
Explanation The address space manager received an invalid pacing message.
Recommended Action The address space manager could not process a received pacing message (IPM) because the message type in the received message is invalid. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_RCV_IPM_RH_RU_ERR : ASM - IPM RH or RU error, sense code = [hex]
Explanation The address space manager received an invalid pacing message.
Recommended Action The address space manager could not process a received pacing message (IPM) because it contained invalid SNA control information. Some or all of the following information is invalid: the request/response indicator in the RH is set (the message is a response), the pacing indicator in the RH is not set, the response type indicators in the RH (DR1, DR2) are set, the format indicator in the IPM RU is invalid, or the size of the received message is incorrect. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_RCV_IPM_TH_ERR : ASM - IPM TH bits are not set correctly, sense code = [hex]
Explanation The address space manager received an invalid pacing message.
Recommended Action The address space manager could not process a received pacing message (IPM) because it contained invalid SNA control information. The received IPM violated SNA segmentation rules. The received message is multisegmented, but IPM messages are not allowed to be segmented. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_RCV_IPM_UNEXPECTED : ASM - Received a solicited IPM which was never requested, sense code = [hex]
Explanation The address space manager received an unexpected BIND pacing message.
Recommended Action 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 want 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 nonzero). Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_RCV_IPM_WRONG_STATE : ASM - IPM received while ASM is in the middle of reassembling, sense code = [hex]
Explanation The address space manager received an unexpected BIND pacing message.
Recommended Action The address space manager received an SNA isolated pacing message (IPM) while in the process of receiving a multisegmented message from the node that sent the IPM. IPM messages can be sent only until all the segments of the previously transmitted message are sent. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_RECVD_BAD_SIDH : ASM received bad SIDH in SMALL mode, sense code = [hex]
Explanation The address space manager (ASM) received a message containing an invalid LFSID.
Recommended Action The address space manager received a message containing an SIDH (high session index) that is invalid or unrecognized. If the SIDH value was 01, which is reserved for BIND pacing, the received message was not a BIND pacing message. If the SIDH value was 00, which is reserved for session services control point (SSCP) data, the received message was not an SSCP message. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_SEGMENTATION_ERROR1 : ASM - MU segment reassembly error, sense code = [hex]
Explanation The address space manager received an invalid message.
Recommended Action The address space manager could not process a received message, because it contained invalid SNA control information. This error could occur in the following situations. The received message violated SNA segmentation rules. The local node was in the process of assembling a multisegmented message, and the begin segment indicator was set in the TH (it was attempting to begin a new message before completing the previous message). The local node was expecting a new message, but the begin segment indicator was not set in the TH (it was attempting to continue a message that was already completely assembled). The received message was part of a multisegmented message, but the LFSID or the sequence number in the message did not match the values in the other segments of the message. The received message is multisegmented, but the node that sent the message had indicated that it would not send multisegmented messages. The received message violated SNA pacing protocols. The size of the received message exceeded the maximum size agreed upon by the local node and the node that sent the message. Probable causes of this error are a programming error in the local node or in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_SEGMENTATION_ERROR2 : ASM - MU segment reassembly failed, free up MU, sense code = [hex]
Explanation The address space manager received an invalid message.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-logpcASM_SEND_ACTV_AS_FAILED : ASM - Activate Address Space request failed, sense code = [hex]
Explanation The address space manager encountered an error while trying to create a new address space.
Recommended Action The address space manager could not create an address space for a new path control instance because the related path control instance could not be determined, or the attempt to access the path control block failed. Possible causes are a system function failure (preventing the access of the path control block by the address space manager), the path control instance detecting a severe error and deactivating, a serious memory shortage problem, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_SML_LFSID_RCV_CHECK : ASM - LFSID is out of bounds, small table is used
Explanation The address space manager received a message containing an invalid or unrecognized LFSID.
Recommended Action Possible problems include the following. The SIDH value was 00, which is reserved for messages exchanged with a session services control point (SSCP), but the received message was not an SSCP message. The SIDH value was not 00, but the received message was an SSCP message. The SIDH value was 01, which should be reserved for BIND pacing, but the received message is not a BIND pacing message. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_SYSDEF_LINK_MISMATCH : ASM - Host link definition mismatch
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_UNKN_CV_KEY : ASM - unknown cvkl_key
Explanation The address space manager received a message containing unrecognized or unsupported control vector.
Recommended Action Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcASM_UNKN_CV_KEY_0E : ASM - unknown CV: cvkl_key= 0x0E
Explanation The address space manager received a message containing a control vector X'0E' with invalid or unrecognized subvectors.
Recommended Action Probable causes of this error are the remote node sending an invalid message, a software error in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcAS_NOT_THERE : PC - Address space does not exist
Explanation Path control (PC) encountered an invalid internal control block.
Recommended Action 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. There is a programming error in the local node or in the node that sent the message, or the APPC/APPN support in the remote node is not compatible with the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcDATA_IN_QUEUES_WRONG : PC - data_in_queues wrong
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcLOCAL_HS_SMALLTBL : LOCAL_HS_LPID is NULL - Small Table
Explanation Path control (PC) could not determine the PC logical process responsible for handling a message received via a session connector for an intermediate session.
Recommended Action The PC logical process for the TG (link) that is supposed to handle the session connector's messages does not exist. The logical process was obtained using the small table of LFSIDs in PC. Probable causes of this error are a programming error in the local node or the remote node sending an invalid message. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcLPID_LOCK_FAILED : PC - LPID lock failed
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcNULL_LPID : PC - NULL LPID
Explanation 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).
Recommended Action There is a problem in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPCPONG_RSP_RECVD : PC - Pong RSP received, bad LPID
Explanation The path control process received a DLC PONG response from a DLC, but the path control instance identified in the response does not exist.
Recommended Action The logical process ID of the path control instance is invalid. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_AGING_COUNT_GR_6 : PC - trpr_q_aging_count is greater than 6, aging_count = [hex]
Explanation Path control (PC) encountered a situation in which the internal counter used to manage the transmission priority queues and the associated aging algorithm has an invalid value.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_ALERT_SIGNAL : PC is sending ALERTSIGNAL to MS
Explanation Path control (PC) generated an alert.
Recommended Action Path control, address space manager, or session connector detected an alertable condition and sent the formatted SNA alert to MS for transmission to its alert focal point. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_DEQD_CLOSE_STN : PC dequeued CLOSE_STN that is not a CNF
Explanation Path control (PC) received an invalid IPS message from a DLC.
Recommended Action The received IPS was a DLC CLOSE_STN message, but did not contain a confirmation. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_DEQD_DATA_NOT_IND : PC dequeued DATA that is not an IND
Explanation Path control (PC) received an invalid IPS message from a DLC.
Recommended Action The received IPS was a DLC DATA message but did not contain an indication. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_DEQD_DL_DATA : PC dequeued dequeued DL_DATA.(rsp/cnf), releasing msg
Explanation Path control (PC) received a recognized but unexpected IPS message from a DLC.
Recommended Action The received IPS was a DLC DATA response or confirmation, which path control recognizes but does not process. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_DEQD_DL_DATA_IND : PC dequeuing a DL_DATA.IND after DESTROY_TG received
Explanation Path control (PC) received a DATA indication after a link station (TG) was closed.
Recommended Action Path control received an out-of-sequence IPS message from a DLC. The received IPS was a DLC DATA indication message, but path control received a DESTROY_TG signal for the TG related to the link station, indicating that the link station is closed. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_DEQD_INV_MSG : PC dequeued invalid message, releasing msg
Explanation Path control (PC) received an invalid IPS message from a DLC.
Recommended Action The received IPS was a DLC message that path control does not recognize or cannot support. This event is usually logged with another event that specifies the received DLC message (2F105000-00000010 through 2F105000-00000013). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_DEQD_OPEN_STN : PC dequeued OPEN_STN that is not a CNF
Explanation Path control (PC) received an invalid IPS message from a DLC.
Recommended Action The received IPS was a DLC OPEN_STN message, but it did not contain a confirmation. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_DEQD_PRIOR_OPEN_STN : PC dequeued DL_DATA.ind prior to OPEN_STN.cnf, releasing msg
Explanation Path control (PC) received a DATA indication before the link station was open.
Recommended Action The received interprocess signal (IPS) was a DLC DATA indication message, but path control has not received the OPEN_STN confirmation from the DLC indicating that the link station is open. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_DEQD_UNKWN_IPS_NAME : PC dequeued unknown IPS NAME, ips name = [hex]
Explanation An instance of path control received an internal interprocess signal (IPS) that it does not recognize or cannot process.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_DEQD_UNKWN_LSA_IPS : PC dequeued unknown LSA IPS, lsa primitive = [hex]
Explanation Path control (PC) received an unknown interprocess signal (IPS) from a DLC.
Recommended Action Path control does not recognize the DLC command contained in the received signal. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_DEQD_UNKWN_LS_IPS : PC dequeued unknown LSA IPS, ls ips code = [hex]
Explanation Path control (PC) received an invalid IPS message from a DLC.
Recommended Action The received IPS was an DLC message that path control does not recognize or support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_DEQD_UNKWN_MU : PC dequeued unknown MU.
Explanation A path control instance received an SNA message (MU) that it does not recognize or cannot process.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_FLUSH_IPS : PC - Flushing ips queue, ips name = [hex]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_FRR_DEQD_FIRST_SEG : FRR dequeued unknown rq_code - first segment, rq_code = [hex]
Explanation Path control's (PC's) receive FSM received an SNA message that it does not recognize or cannot process.
Recommended Action Path control's receive router FSM received an unexpected or unrecognized input message (MU) that is the first segment in a multisegmented message. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_FRR_DEQD_LAST_SEG : FRR dequeued unknown rq_code - last segment,rq_code = [hex]
Explanation Path control's (PC's) receive FSM received an SNA message that it does not recognize or cannot process.
Recommended Action Path control's receive router FSM received an unexpected or unrecognized input message (MU) that is the last segment in a multisegmented message. The request code was obtained from the first segment. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_FRR_DEQD_MIDDLE_SEG : FRR dequeued unknown rq_code - middle segment, rq_code = [hex]
Explanation Path control's (PC's) receive FSM received an SNA message that it does not recognize or cannot process.
Recommended Action Path control's receive router FSM received an unexpected or unrecognized input message (MU) that is a middle segment in a multisegmented message. The request code was obtained from the first segment. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_FRR_DEQD_SINGL_SEG : FRR dequeued unknown rq_code - single segment
Explanation Path control's (PC's) receive FSM received an SNA message that it does not recognize or cannot process.
Recommended Action Path control's receive router FSM received an unexpected or unrecognized single-segment input message (MU). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_HS_LPID_LARGE_TABLE : LOCAL_HS_LPID is NULL - Large Table
Explanation Path control (PC) could not determine the PC logical process responsible for handling a message received via a session connector for an intermediate session.
Recommended Action The PC logical process for the TG/link that is supposed to handle the session connector's messages does not exist. The logical process was obtained using the large table of LFSIDs in PC. Probable causes of this error are a programming error within the local node or the remote node sending an invalid message. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_INVALID_COMB : PC - Invalid combination in FSM RECEIVE ROUTER, old_fsm = [hex], input value = [hex], action code = [hex]
Explanation The path control's (PC's) receive FSM received an SNA message that it does not recognize or cannot process.
Recommended Action The path control's receive router FSM sent an unknown or invalid action code. Probable causes of this error are an invalid message was received or a message was received out of sequence. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_LOG_DEBUG_DATA : PC - Invalid MU received, bad TH/RH/RU, sense code = [hex]
Explanation A session connector, path control instance, or address space manager received an invalid SNA message from a partner node.
Recommended Action The system received an SNA message that failed the basic SNA integrity checks. The following are some sample message problems and the sense code used to reject the message:
•
•
•
•
Detected errors are either the RH indicates it is a response to a session control request, but the message is not large enough to hold the 4-byte sense data and the 1-byte session control request code; or the RH indicates it is a session control request, but the message is not large enough to hold the 1-byte session control request code. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_MU_ERROR_CHECKER : PC mu_error_checker failed, freeing LSA msg
Explanation Path control (PC) received an SNA message that contains invalid SNA headers.
Recommended Action Path control received an invalid SNA message from another node. The received message did not pass the basic SNA message verification checks for the TH and RH settings. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_NO_DESTRY_TG_RSP : PC - No destroy_tg_rsp to send to CS
Explanation Path control (PC) encountered an unexpected condition while trying to send a DESTROY_TG response.
Recommended Action Path control expected to use the saved DESTROY_TG request to construct the response, but the request no longer exists. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_PD_OPEN_RSP_RCVD1 : PC - PD_open_rsp rcvd with bad response code
Explanation The path control instance could not open a process dialog with the APPN control point configuration services component or the DLC associated with the instance's link (TG).
Recommended Action Probable causes of this error are a system function failure (preventing the establishment of the communications path), an error occurring while transferring initialization data, a serious memory shortage problem, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_PD_OPEN_RSP_RCVD2 : PC - PD_open_rsp rcvd but did's do not match or fsm not reset, fsm state = [hex], did = [hex], dlcdx did = [hex]
Explanation The path control instance could not open a process dialog with the APPN control point configuration services component or the DLC associated with the instance's link (TG).
Recommended Action 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. Probable causes of this error are an internal code problem, a system function failure occurring (preventing the establishment of the communications path), an error occurring while transferring initialization data, or a serious memory shortage problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_SC_INV_IPS_RECVD : PC/SC - Invalid ips received, ips_name = [hex]
Explanation A session connector (SC) received an internal interprocess signal (IPS) that it does not recognize or cannot process.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_SC_NO_PROC_CB : PC/SC - can't get process_cb for message
Explanation The path control/session connector (PC/SC) received an internal interprocess signal, but cannot find the control blocks associated with the session connector.
Recommended Action The logical process identified in the signal is a session connector, but the process-specific control blocks cannot be located. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_SNO_COND : PC encountered SNO cond, releasing msg, resetting state, old fsm state = [hex], input value = [hex]
Explanation Path control (PC) received an invalid interprocess signal (IPS) or an out-of-sequence message from a DLC.
Recommended Action This event is usually logged with another event that specifies the DLC message that was received (2F105000-00000010 through 2F105000-00000017). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_SNO_ENCNTRD : PC - SNO condition encountered, but no create_tg_rsp to send
Explanation Path control (PC) encountered an unexpected condition while trying to send a CREATE_TG response.
Recommended Action Path control expected to use the saved CREATE_TG request to construct the response, but the request no longer exists. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_UNKWN_MSG_DLCPCQ : PC dequeued unknown msg on DLC_TO_PC_Q, ips_name = [hex]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPC_UNKWN_XMIT_PRIORITY : PC - unknown transmission priority, q_name = [hex]
Explanation Path control specified an invalid transmission priority queue.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcPD_CLOSE_REQ : PC - Received PD_CLOSE_REQ
Explanation An instance of path control lost its dialog with configuration services or one of its underlying DLCs.
Recommended Action 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 and to access configuration services in the main processor. Probable causes of this error are a system function failure (causing the termination of the communications path), a serious memory shortage problem, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcSC_ABORT_TO_SCM : SC_ABORT sent to SCM. SC CB will be freed, proc name = [chars], sense code = [hex]
Explanation A session connector (SC) received an invalid SNA message, an out-of-sequence SNA message, or detected another severe error condition that terminated the session connector.
Recommended Action Probable causes of this error are receipt of an invalid SNA message, receipt of an out-of-sequence SNA message (such as a message with message segments in the wrong order), or other unrecoverable error conditions (such as internal errors). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcSC_INV_RH_SIZE : SC detected invalid RH size after PC validated, rh_size = [dec]
Explanation A session connector (SC) received an invalid SNA message from a partner node.
Recommended Action 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). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpcSC_INV_SNO_COND : SC - Invalid or sno condition in SC CLEAR FSM, input value = [hex], current state = [hex]
Explanation A session connector (SC) received an invalid or out-of-sequence interprocess signal.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpsFMH7_LOG : FMH-7 Error Condition, sense code = [hex]
Explanation Presentation services in the local node either received an FMH-7 (error data) or sent an FMH-7 to a conversation partner.
Recommended Action The sense code indicates the error condition that triggered the FMH-7. The local node might send an FMH-7 for one of the following reasons. The local node may be ending a conversation by issuing a DEALLOCATE TYPE=ABEND or SEND_DATA TYPE=DEALLOCATE_ABEND. If this occurs, the local support or transaction program detected an unrecoverable error and decided to end the conversation. The local transaction program may have detected an error and is notifying its conversation partner by issuing a SEND_ERROR. If this occurs, the node sends an FMH-7 to the conversation partner to indicate the error information and purges all unprocessed data. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpsPROTOCOL_ERROR : Conversation protocol error for a mapped conversation
Explanation Presentation services detected an SNA protocol error while receiving data over a mapped conversation with a conversation partner.
Recommended Action The received message did not pass one or more of the SNA receive checks. The sense code identifies the actual SNA protocol error. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpsRCVD_ERROR_GDS_VARIABLE : Error data GDS received over mapped conversation
Explanation An SNA protocol error was detected while receiving data over a mapped conversation.
Recommended Action A conversation detected an SNA protocol error while processing a message received from a conversation partner. An unexpected error data GDS variable was received (a preceding FMH-7 was not received). Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpsSEND_UNBINDFE_LOG : Conversation protocol error at basic conversation level, sense code = [hex], lu name = [chars]
Explanation Presentation services detected an SNA protocol error while processing a message received from a conversation partner.
Recommended Action The received message did not pass one or more of the SNA receive checks. The sense code identifies the actual SNA protocol error. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpsUNKNOWN_IPS_RCVD : Unknown IPS Received, current pid = [hex], ips name = [hex]
Explanation Presentation services for an LU received an internal interprocess signal it does not recognize or cannot process.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpsnavCRITICAL_LOG : Critical Error, header = [chars], [chars]
Explanation The configuration verification utility detected a severe error condition while processing the configuration file.
Recommended Action The log record describes the error, the resulting system action and any recommended user responses, and contains the message number of the logged message. In most cases, the error is related to a system error (such as an underlying system function failed or a memory problem). Refer to the description of the message for a detailed explanation. In severe cases, the utility ends immediately. The configuration is not successfully loaded into the local node. Depending on the error, the configuration might have been partially loaded when the error was detected. The resulting configuration is not usable. Stop the local node and fix the error. Fix the error using the recommended responses and restart the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpsnavERROR_LOG : Error, header = [chars], [chars]
Explanation The configuration verification utility detected an error condition while processing the configuration file.
Recommended Action The log record describes the error, the resulting system action and any recommended user responses, and contains the message number of the logged message. In most cases, the error is related to a configuration problem. The utility continues to check the configuration file for any syntax or configuration errors, and the configuration is not successfully loaded into the local node. Depending on the error, the configuration might have been partially loaded when the error was detected. 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 restart the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logpsnavWARNING_LOG : Warning, header = [chars], [chars]
Explanation The configuration verification utility detected a recoverable error condition while processing the configuration file.
Recommended Action The log record describes the error, the resulting system action and any recommended user responses, and contains the message number of the logged message. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrmBIS_REPLY_NOT_EXPECTED : Unexpected BIS reply received, sense_code = 0x[hex], originator = [chars]
Explanation The resource manager detected that a received message violates the SNA bracket protocol rules for a session.
Recommended Action The sense code identifies the actual protocol error (20100000). The resource manager received an unexpected BIS response from a session partner. That is, a BIS response was received but a BIS request was not pending. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrmBIS_RQ_NOT_EXPECTED : Received unexpected BIS request, sense_code = 0x[hex], originator = [chars]
Explanation The resource manager detected that a received message violates the SNA bracket protocol rules for a session.
Recommended Action The sense code identifies the actual protocol error (20100000). The resource manager received an unexpected BIS request from a session partner. That is, a BIS request was received after another BIS request was received. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrmBRACKET_ERROR : Bracket error, sense_code = 0x[hex], originator = [chars]
Explanation The resource manager detected that a received message violates the SNA bracket protocol rules for a session.
Recommended Action The sense code identifies the actual protocol error (20030000). The remote node sent an ATTACH on a session that already has an active conversation, or sent a BID over a session of which it is the first speaker. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrm_CANNOT_CREATE_PS : RM - Failed to create a new PS instance
Explanation The resource manager for an LU could not create the presentation services instance required for a new APPC transaction program instance.
Recommended Action Probable causes of this error are a system function failure (preventing the creation of the presentation services instance), the presentation services instance detecting a severe error and deactivating, a serious memory shortage problem, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrmCONV_SECURITY_ERROR : Conversation-level security error, sense_code = 0x[hex], originator = [chars]
Explanation The resource manager detected an error in the conversation security parameters contained in a received ATTACH.
Recommended Action The sense code identifies the actual SNA protocol error (10086040 or 080F6051). Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrm_ERR_INVALID_SUBFIELD : RM - Received invalid security subfields, user id without passwords
Explanation The resource manager rejected a remote request to start a new conversation (an SNA ATTACH message) because it contained inconsistent access security information.
Recommended Action The security information specified a user ID, but did not specify the related password. Probable causes of this error are the remote node sending an ATTACH request containing invalid security information, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrm_ERR_MULTIPLE_PASSWORDS : RM - Security subfield contains multiple passwords
Explanation The resource manager rejected a remote request to start a new conversation (an SNA ATTACH message) because it contained multiple access security passwords.
Recommended Action Probable causes of this error are the remote node sending an ATTACH request containing invalid security information, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrm_ERR_MULTIPLE_PROFILES : RM - Security subfield contains multiple profiles
Explanation The resource manager rejected a remote request to start a new conversation (an SNA ATTACH message) because it contained multiple access security profiles.
Recommended Action Probable causes of this error are the remote node sending an ATTACH request containing invalid security information, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrm_ERR_MULTIPLE_USERIDS : RM - Security subfield contains multiple userids
Explanation The resource manager rejected a remote request to start a new conversation (an SNA ATTACH message) because it contained multiple access security user IDs.
Recommended Action Probable causes of this error are the remote node sending an ATTACH request containing invalid security information, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrmINSUFFICIENT_RESOURCES : Insufficient Resources for Attach, sense_code = 0x[hex], originator = [chars]
Explanation A system error occurred while processing a received ATTACH, or enough resources (such as memory or buffers) could not be allocated to process the ATTACH.
Recommended Action 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. The ATTACH is rejected with the sense code 20030000. The node may continue to work correctly. If it appears to be behaving satisfactorily (that is, if a subsequent retry of the operation was successful), no immediate action is required. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrm_INVALID_FSM_BIS_STATE : RM - BIS rq received in unknown fsm_bis_state
Explanation The resource manager encountered a software problem while processing an SNA BIS request.
Recommended Action 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 following are probable causes of this error.
•
•
•
Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrm_INVALID_RETURN_CNTL_VAL : RM - Invalid return_control value from ALLOCATE verb, return control value = [hex]
Explanation The resource manager encountered an unexpected situation while processing a request for a new conversation (an ALLOCATE API verb or internal ALLOCATE request).
Recommended Action The resource manager does not recognize the return control indicator in the ALLOCATE request. The return control indicator specifies the desired action when no session is available for the new conversation. 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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrm_INVALID_SECU_INFO_TYPE : RM - Received ATTACH contains invalid security info type = [hex]
Explanation The resource manager for the LU rejected a remote request to start a new conversation (an SNA ATTACH message) because it does not recognize one or more of the security subfields in the request.
Recommended Action Probable causes of this error are the remote node sending an ATTACH request containing invalid security information, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrmNO_BEGIN_BRACKET : BID received immediately after receipt of BIS,sense_code = 0x[hex], originator = [chars]
Explanation The resource manager detected that a received message violates the SNA bracket protocol rules for a session.
Recommended Action The sense code identifies the actual protocol error (20080000). The resource manager received a BID request after receiving a BIS from a session partner. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrm_RCV_FROM_UNKNOWN_Q : RM - Receive IPS from an UNKNOWN Q, receiving queue = [hex], ips name = [hex]
Explanation The resource manager for an LU received an internal interprocess signal that it does not recognize or cannot process.
Recommended Action An internal code problem exists. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrmRTR_NOT_EXPECTED : Unexpected RTR message received, sense_code = 0x[hex], originator = [chars]
Explanation The resource manager detected that a received message violates the SNA bracket protocol rules for a session.
Recommended Action The sense code identifies the actual protocol error (20030000). The resource manager received an unexpected RTR request from a session partner. That is, an RTR was sent over a session on which the previous BID was not rejected. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrm_SCB_IS_IN_USE_STATE : RM - SCB is still in IN_USE state!
Explanation A session deactivated by the resource manager was still in use. That is, the session was still being used by a conversation, while processing a notification that a session is being ended (a session outage notification).
Recommended Action 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 to help determine why the conversation and its session were deactivated. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrmSESS_SECURITY_ERROR : Session-level security error
Explanation The resource manager detected an error in the conversation security parameters contained in a received ATTACH.
Recommended Action The sense code identifies the actual SNA protocol error (10086040 or 080F6051). Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrm_UNKNOWN_DEACT_REASON : RM - Invalid reason value for sess_deact, reason = [hex]
Explanation The resource manager encountered an unexpected situation in which the session was being ended (a session outage notification) while processing a notification.
Recommended Action The resource manager does not recognize the reason code contained in the internal session deactivated signal. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrm_UNKNOWN_IPS_FROM_GPE : RM - Received unknown IPS, ips name = [hex]
Explanation The resource manager for an LU received an internal interprocess signal that it does not recognize or cannot process.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrm_UNKNOWN_IPS_FROM_HS : RM - Received unknown IPS from HS, ips name = [hex]
Explanation The resource manager for an LU received an internal interprocess signal from a half-session that it does not recognize or cannot process.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrm_UNKNOWN_IPS_FROM_NOF : RM - Received unknown IPS from NOF, ips name = [hex]
Explanation The resource manager for an LU received an internal interprocess signal from NOF that it does not recognize or cannot process.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrm_UNKNOWN_IPS_FROM_SM : RM - Received unknown IPS from SM, ips name = [hex]
Explanation The resource manager for an LU received an internal interprocess signal from the session manager that it does not recognize or cannot process.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrtpBadMulticast : RTP Multicast unreliable
Explanation The rapid transport protocol (RTP) component detected an error while attempting to send a message.
Recommended Action The connection for the message is in an invalid state. The current status of the connection indicates that transmission of the message is unreliable. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrtpConnTypeError : RTP Connection Type not Supported
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrtpUnknownTimer : RTP Unknown Timer Event
Explanation The rapid transport protocol (RTP) component received a timer-expired notification that it does not recognize or cannot process.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrtprcvFRR : RTP Process entered FRR, rtp rcv name = [chars], abend code = [hex]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logrtpsndFRR : RTP Process entered FRR, rtp snd name = [chars], abend code = [hex]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_CSWIMBNC_LOGMSG_01 : SCM - Could not lock sec_sc_lpid
Explanation The session connector manager (SCM) could not lock the process or data responsible for servicing the secondary side of a session connector.
Recommended Action The function LP_cb_lock failed. Probable causes of this error are an internal code problem, a system function failure (preventing the process from being locked), an error trying to set up the logical process data for the secondary session connector, or a serious memory shortage problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_CSWIMBNR_LOGMSG_01 : SCM - bad sense code on bind_negotiation_complete_rsp, sense code = [hex]
Explanation The session connector manager (SCM) could not create an intermediate session because it detected an unexpected BIND response sense code while setting up the session connectors.
Recommended Action The BIND negotiation failed with a sense code, but, in most cases, this is handled by other sections of code. Probable causes of this error are an internal code problem, an error that occurred while trying to set up the communications paths between the session connectors, or a serious memory shortage. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_CSWIMBNR_LOGMSG_03 : SCM - unable to correlate bind_negotiation_complete_rsp
Explanation The session connector manager (SCM) could not lock the process or data responsible for servicing the primary side of a session connector.
Recommended Action The function LP_cb_lock failed. Probable causes of this error are an internal code problem, unexpected termination of the primary session connector logical process, a system function failure (preventing the process from being locked), an error trying to locate the logical process data for the primary session connector, or a serious memory shortage. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_CSWIMI04_LOGMSG_01 : SCM/ACS - PQenq of ms_data_request failed
Explanation The session connector manager (SCM) could not send the internal IPS containing the SCM accounting data to the accounting services component.
Recommended Action Probable causes are an internal code problem, a system function failure (preventing the transmission of the internal message), or a serious memory shortage. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_CSWIMI04_LOGMSG_02 : SCM/ACS - PEstart_ready_monitor failed, rc = [hex]
Explanation The session connector manager (SCM) could not verify that APPN accounting services are active and available.
Recommended Action The function PEstart_ready_monitor failed. Probable causes are a system function failure (preventing the activation of APPN accounting services), an error while trying to set up the monitor path between APPN accounting services and the session connector manager, a serious memory shortage, or an internal code problem exists. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_CSWIMI04_LOGMSG_03 : SCM/ACS - Ignoring unexpected response (IPS), ips name = [hex]
Explanation The session connection manager (SCM) received an unexpected internal interprocess signal (IPS) while waiting for the response message to a PEstart_reqdy_monitor request.
Recommended Action 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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_CSWIMPBS_LOGMSG_01 : SCM - Bad RC from Bmonitor, rc = [hex]
Explanation The session connector manager (SCM) could not resume monitoring the status of the SNA buffer manager buffer pool status.
Recommended Action The SCM monitors the status and is notified when the storage status is constrained. The buffer manager function Bstatus_monitor failed. Probable causes of this error are an internal code problem, an error that occurred while trying to set up the monitor path between the SNA buffer manager and the session connector manager, or a serious memory shortage. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_CSWIMPBS_LOGMSG_02 : SCM - Bad RC from PEstart timer, rc = [hex]
Explanation The request to start a timer used when monitoring the status of the SNA buffer manager storage status failed.
Recommended Action The session connector manager (SCM) 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 SCM 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 function PEstart_timer failed. Probable causes of this error are an internal code problem, a system error that occurred while starting the requested timer, or a serious memory shortage. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_CSWIMPMR_LOGMSG_01 : SCM - Bad RC from PEstart_down_monitor
Explanation The request to set up a notification when an instance of session connector manager (SCM) deactivates failed.
Recommended Action The SCM could not add a notification to inform it when another instance of SCM deactivates. The function PEstart_down_monitor failed. Probable causes are an internal code problem, an error that occurred while trying to set up the monitor path between the session connector managers, or a serious memory shortage. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_FLUSH_IPS : SCM - Flushing ips queue, ips name = [hex]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_LIM_FAILURE : SCM - LIM failure, scm pid = [hex], eid = [hex]
Explanation A session connector manager (SCM) in an attached coprocessor ended.
Recommended Action The SCM assumes that the attached coprocessor is no longer usable, and all links and their related sessions are lost. Probable causes of this error are a system function failure (resulting in the loss of the attached coprocessor), an error transferring data between processors, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_RTP_SIGNIN_FAILED : SCM - RTP signin failed, rc = [hex]
Explanation The request to register the session connector manager (SCM) with RTP failed.
Recommended Action The SCM could not sign into RTP. Probable causes of this error are a system function failure (preventing the activation of the RTP resources needed by the SCM), an error trying to set up the path between RTP and the SCM, an error trying to set up the RTP communications paths needed by the SCM, a serious memory shortage, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_XXXIMACS_LOGMSG_01 : SCM - couldn't find sess info, sending mu to actxx
Explanation The session connector manager (SCM) could not determine the destination session for a received ACTPU/ACTLU request.
Recommended Action 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. Probable causes are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_XXXIMACS_LOGMSG_02 : ERROR-SCM - couldn't find lu hierar, sending mu to actxx
Explanation The session connector manager (SCM) could not determine the destination session for a received ACTPU/ACTLU request.
Recommended Action 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 an SSCP session). Probable causes are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_XXXIMFFA_LOGMSG_01 : SCM FSM encountered should not occur state, input = [hex]
Explanation The session connector manager (SCM) received an invalid or out-of-sequence interprocess signal (IPS) or SNA message.
Recommended Action Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_XXXIMFFA_LOGMSG_02 : SCM FSM encountered invalid input signal, ips name = [hex].
Explanation The session connector manager (SCM) received an invalid interprocess signal (IPS) or SNA message.
Recommended Action The received IPS or SNA message is not recognized by the SCM FSM. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_XXXIMPCA_LOGMSG_01 : SCM - FSM != PEND_BIND_RSP and BIND response received
Explanation The session connector manager (SCM) received an invalid BIND response.
Recommended Action Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_XXXIMPCA_LOGMSG_02 : SCM - No match on BIND_RSP CV60s
Explanation The session connector manager (SCM) detected a session correlation error in a received BIND response.
Recommended Action The SCM used the LFSID in the received response to locate the correct intermediate session, but the session's fully qualified procedure correlator identifier (PCID) does not match the fully qualified PCID in the received BIND response. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_XXXIMPDU_LOGMSG_01 : SCM - Could not correlate dlur_unbind lfsid, table_p = [hex], pc_lpid = [hex], lfsid_key_value = [hex]
Explanation The session connector manager (SCM) could not determine the destination intermediate session related to a received DLUR_UNBIND request from dependent LU requestor.
Recommended Action 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. Probable causes of this error are a programming error on the local node, the remote node sending an invalid message, a software problem in the local node (the DLUR component should not have forwarded the extraneous UNBIND), a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote nodes (the DLUS and downstream nodes) and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_XXXIMPPH_LOGMSG_01 : SCM - Could not lock pri_sc_lpid
Explanation The session connector manager (SCM) could not lock the logical process or data responsible for servicing the primary side of a session connector.
Recommended Action The LP_cb_lock failed. Probable causes of this error are an internal code problem, a system function failure (preventing the process from being locked), an error while trying to set up the logical process data for the primary session connector, or a serious memory shortage. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_XXXIMPPH_LOGMSG_02 : SCM - Could not Tfind/correlate FID2 unbind_rq lfsid, session table p = [hex], lpid = [hex], lfsid key value = [hex]
Explanation The session connector manager (SCM) could not determine the destination intermediate session for a received BIND response.
Recommended Action 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. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_XXXIMPPS_LOGMSG_01 : SCM - Could not Tfind/correlate FID2 unbind_rq lfsid, lfsid value = [hex]
Explanation The session connector manager (SCM) could not determine the destination intermediate session related to a received UNBIND request.
Recommended Action 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. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_XXXIMPPS_LOGMSG_02 : SCM - No match on unbind_rq CV60s
Explanation The session connector manager (SCM) detected a session correlation error in a received UNBIND request.
Recommended Action The SCM used the LFSID in the received UNBIND to locate the correct intermediate session, but the session's fully qualified procedure correlator identifier (PCID) does not match the fully qualified PCID in the received UNBIND request. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_XXXIMPPS_LOGMSG_03 : SCM - bad unbind_rq, sense code = [hex]
Explanation The session connector manager (SCM) detected a format or protocol error in a received UNBIND request.
Recommended Action The received request contained incorrect values. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_XXXIMPPS_LOGMSG_04 : SCM - Could not Tfind/correlate FID5 unbind_rq fqpcid
Explanation The session connector manager (SCM) could not determine the destination intermediate session for a received UNBIND request.
Recommended Action The received UNBIND is a FID5 request, and the fully qualified procedure correlator identifier (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. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_XXXIMPPS_LOGMSG_05 : SCM - FID5 unbind_rq received without fqpcid
Explanation The session connector manager (SCM) could not determine the destination intermediate session for a received UNBIND request.
Recommended Action The received UNBIND is a FID5 request, and the system 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'). Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_XXXIMPPS_LOGMSG_06 : SCM - PID and LPID in UNBIND did not match session_info_cb
Explanation The session connector manager (SCM) detected a session correlation error in a received UNBIND request.
Recommended Action The SCM 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. Probable causes of this error are a programming error in the local node, the remote node sending an invalid message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_XXXIMPPT_LOGMSG_01 : SCM - Could not correlate UNBIND_RSP, pc id = %lx, lfsid = %lx
Explanation The session connector manager (SCM) could not determine the destination intermediate session related to a received UNBIND response.
Recommended Action 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. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_XXXIMS00_LOGMSG_01 : SCM - Bad RC from PEstart_ready_monitor, rc = [hex]
Explanation The request to verify that session or configuration services are available failed.
Recommended Action The session connector manager (SCM) could not verify that APPN session services or configuration services are active and available. The function PEstart_ready_monitor failed. Probable causes of this error are a system function failure (preventing the activation of APPN session and configuration services), an error trying to set up the monitor path (between APPN session or configuration services and the session connector manager), a serious memory shortage problem, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_XXXIMS00_LOGMSG_04 : SCM - Bad RC from Bmonitor, rc = [hex]
Explanation The session connector manager (SCM) could not start monitoring the status of the SNA buffer manager buffer pool status.
Recommended Action The SCM monitors the status and is notified when the storage status is constrained. The buffer manager function Bstatus_monitor failed. Probable causes of this error are an internal code problem, an error trying to set up the monitor path (between the SNA buffer manager and the session connector manager), or a serious memory shortage problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logscm_XXXIMS00_LOGMSG_05 : SCM - Dequeued unknown IPS, ips name = [hex]
Explanation The session connection manager (SCM) received an internal interprocess signal (IPS) that it does not recognize or cannot process.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logsmBIND_ALR_VER_DIFF : ALREADY_VERIFIED in BIND different than existing sessions, sense_code =0x[hex], lu name = [chars]
Explanation The session manager (SM) rejected a BIND from a partner LU because it contained invalid security data.
Recommended Action 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. Probable causes of this error are the remote node sending an invalid BIND request or sending a BIND on an incorrect session, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. This log record is created in conjunction with the log record 2F11C000-00000016, which contains additional information (such as the local LU name and the sense code used to reject the BIND request). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logsmBIND_ATT_SEC_DIFF : ATTACH_SECURITY in BIND different than existing sessions, sense_code =0x[hex], lu name = [chars]
Explanation The session manager (SM) rejected a BIND received from a partner LU because it contained invalid security data.
Recommended Action 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. Probable causes of this error are the remote node sending an invalid BIND request or sending a BIND on an incorrect session, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. This log record is created in conjunction with the log record 2F11C000-00000016, which contains additional information (such as the local LU name and the sense code used to reject the BIND request). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logsmBIND_INVALID_SEC_IN : Invalid security information in the BIND, sense_code =0x[hex], lu name = [chars]
Explanation The session manager (SM) 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.
Recommended Action This error may occur when 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 the local system, which expects the random data length to be 8 bytes. This log record is created in conjunction with the log record 2F11C000-00000016, which contains additional information (such as the local LU name and the sense code used to reject the BIND request). Probable causes of this error are the local node containing an incorrect definition for the partner LU, the remote node containing an incorrect definition for a local LU, the remote node sending an invalid BIND request, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logsmBIND_RQ_RCV_ERROR : Received BIND request with syntax, state, or semantic error, sense code = 0x[hex]
Explanation The session manager (SM) rejected an incoming BIND from a partner LU because it contained invalid data, or the BIND was not expected.
Recommended Action 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. Probable causes of this error are the remote node sending an invalid BIND request or sending a BIND on an incorrect session, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logsmBIND_RSP_ALR_VER_ER : BIND RSP ALREADY_VERIFIED error, sense_code =0x[hex], lu name = [chars]
Explanation The session manager (SM) ended a session because the received BIND response contains security information inconsistent with the session.
Recommended Action 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 security is supported, but the session and the BIND request used to initiate the session indicated that security is not supported. This log record is created in conjunction with the log record 2F11C000-00000016, which contains additional information (such as the local LU name and the sense code used to reject the BIND request). Probable causes of this error are the remote node sending an invalid BIND request or sending a BIND on an incorrect session, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logsmBIND_RSP_ATT_SEC_ER : BIND RSP ATTACH_SECURITY error, sense_code =0x[hex], lu name = [chars]
Explanation The session manager (SM) ended a session because the received BIND response contained invalid security data.
Recommended Action 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. This log record is created in conjunction with the log record 2F11C000-00000016, which contains additional information (such as the local LU name and the sense code used to reject the BIND request). Probable causes of this error are the remote node sending an invalid BIND request or sending a BIND on an incorrect session, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logsmBIND_RSP_ENC_SUB_ER : BIND RSP enciphered data subfield error, sense_code =0x[hex], lu name = [chars]
Explanation The session manager (SM) ended a session because the received BIND response contains encryption information inconsistent with the session.
Recommended Action 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. This log record is created in conjunction with the log record 2F11C000-00000016, which contains additional information (such as the local LU name and the sense code used to reject the BIND request). Probable causes of this error are the remote node sending an invalid BIND request or sending a BIND on an incorrect session, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logsmBIND_RSP_ENC_SUB_IN : BIND RSP enciphered data subfield incorrect, sense_code =0x[hex], lu name = [chars]
Explanation The session manager (SM) ended a session because the received BIND response did not pass the session-level security checks.
Recommended Action The encrypted data in the BIND response did not match the expected encrypted data. This log record is created in conjunction with the log record 2F11C000-00000016, which contains additional information (such as the local LU name and the sense code used to reject the BIND request). Probable causes of this error are security information on the remote node being configured incorrectly, the remote node not being authorized to establish a session with the local LU, the remote node sending an invalid BIND request or sending a BIND on an incorrect session, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logsmBIND_RSP_RAND_SUB : BIND RSP random data subfield error, sense_code =0x[hex], lu name = [chars]
Explanation The session manager (SM) ended a session because the received BIND response contains encryption information inconsistent with the session.
Recommended Action 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. This log record is created in conjunction with the log record 2F11C000-00000016, which contains additional information (such as the local LU name and the sense code used to reject the BIND request). Probable causes of this error are the remote node sending an invalid BIND request or sending a BIND on an incorrect session, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logsmBIND_RSP_SEC_MISMTC : BIND RSP ATTACH_SECURITY/ALREADY_VERIFIED mismatch, sense_code =0x[hex], lu name = [chars]
Explanation The session manager (SM) ended a session because the received response contained inconsistent security information.
Recommended Action The BIND response indicated that conversation level security is not supported, but the already verified indicator was set. That is, security was already verified by the partner LU. This log record is created in conjunction with the log record 2F11C000-00000016, which contains additional information (such as the local LU name and the sense code used to reject the BIND request). Probable causes of this error are the remote node sending an invalid BIND request or sending a BIND on an incorrect session, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logsmBIND_SEC_MISMATCH : BIND ATTACH_SECURITY/ALREADY_VERIFIED mismatch, sense_code =0x[hex], lu name = [chars]
Explanation The session manager (SM) rejected a BIND from a partner LU because it contained invalid security data.
Recommended Action 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. Probable causes of this error are the remote node sending an invalid BIND request or sending a BIND on an incorrect session, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. This log record is created in conjunction with the log record 2F11C000-00000016, which contains additional information (such as the local LU name and the sense code used to reject the BIND request). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logsmENC_DATA_LEN_INCOR : Random data subfield length incorrect, sense code = 0x[hex], lu name = [chars]
Explanation The session manager (SM) rejected an incoming BIND because it contained encryption data that is not the length supported by the local system.
Recommended Action The length of the enciphered data sub-field was not 9, which is the only value supported by &prod. This log record is created in conjunction with the log record 2F11C000-00000016, which contains additional information (such as the local LU name and the sense code used to reject the BIND request). Probable causes of this error are the remote node containing an incorrect definition for a local LU, the remote node sending an invalid BIND request, or a programming error in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logsmENC_DATA_NOT_ALLOW : Enciphered data in BIND - not allowed, sense_code =0x[hex], lu name = [chars]
Explanation The session manager (SM) rejected a BIND received from a partner LU because it contained encrypted data, although the system does not support session-level encryption.
Recommended Action The system APPC support does not support session-level encryption. Probable causes are the remote node containing an incorrect definition for a local LU (indicating that the LU supports session-level encryption), the remote node sending an invalid BIND request, or a programming error in the local node. This log record is created in conjunction with the log record 2F11C000-00000016, which contains additional information (such as the local LU name and the sense code used to reject the BIND request). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logsmINTRA_LU_SESS_ERROR : Intra-LU session cannot find LULU CB, sense_code =0x[hex], lu name = [chars]
Explanation The session manager (SM) could not correlate a BIND request with its associated LU-LU control block.
Recommended Action 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). This log record is created in conjunction with the log record 2F11C000-00000016, which contains additional information (such as the local LU name and the sense code used to reject the BIND request). Probable causes of this error are the remote node sending an invalid BIND request specifying an invalid partner LU or an internal code problem in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logsmINVALID_NS_RECORD : Received an invalid record for network services
Explanation An invalid record for network services was received.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logsmNS_HEADER_NOT_RECOGNIZED : NS header not recognized by SSCP-LU or SSCP-PU session
Explanation The NS header was not recognized by the SSCP-LU or SSCP-PU session.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logsmRAND_DATA_LEN_INCOR : Random data subfield length incorrect, sense code = 0x[hex], lu name = [chars]
Explanation The session manager (SM) rejected a BIND request because the session-level security in the BIND is not supported by the local system.
Recommended Action This error may occur when the local session-level security does not match the value specified by the associated partner LU definition. The length of the random data subfield was not 10, which is the only value supported (8-byte password). This log record is created in conjunction with the log record 2F11C000-00000016, which contains additional information (such as the local LU name and the sense code used to reject the BIND request). Probable causes of this error are the remote node containing an incorrect definition for a local LU, the remote node sending an invalid BIND request, or a programming error exists in the local node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logsmRAND_DATA_PREV_USED : Random data previously used - not allowed, sense code = 0x[hex], lu name = [chars]
Explanation The session manager (SM) rejected a BIND received from a partner LU, because the BIND contained random data that matches random data already pending for a session between the two LUs.
Recommended Action This log record is created in conjunction with the log record 2F11C000-00000016, which contains additional information (such as the local LU name and the sense code used to reject the BIND request). Probable causes of this error are the remote node sending an invalid BIND request or sending a BIND on an incorrect session, a programming error in the local node, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logsmRCVD_NON_NORMAL_UNBIND : Local LU received non-normal UNBIND, sub type = 0x[hex]
Explanation The session manager (SM) received an UNBIND request from a partner LU indicating that this is not a normal session terminal request. For example, the type could be session protocol error x'FE'.
Recommended Action The sense code identifies the reason that the partner LU deactivated the session. Probable causes of this error are the partner LU detecting a protocol error (possibly caused by a message sent by the local LU) or other unrecoverable error, or the session support in the partner LU being incompatible with the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logsmSESS_SECURITY_ERROR : Session-level security error, sense_code = 0x[hex], originator = [chars]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logsmUNBIND_RQ_SYNTAX_ERROR : Received UNBIND response with a syntax error, sense code = 0x[hex]
Explanation The session manager (SM) detected a syntax error in an UNBIND request received from a partner LU.
Recommended Action The UNBIND contained invalid information that violates SNA protocols. The sense code identifies the actual error. Probable causes are the remote node sending an invalid UNBIND request, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logsmUNKNOWN_IPS_RCVD : Unknown IPS received, ips_name = [hex]
Explanation The session manager (SM) received an internal interprocess signal (IPS) that it does not recognize or cannot process.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logsmUNKNOWN_MU_HDR_TYPE_RCVD : Unknown MU Header Type Received, header type = [hex]
Explanation The session manager (SM) for an LU received an SNA message (MU) that it does not recognize or cannot process.
Recommended Action SM processes only session messages, such as BIND and UNBIND. Probable causes of this error are a programming error in the local node, the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logss_CP_CP_OVER_RETRY_CNT : SS - Exceeded CP-CP session retry count
Explanation Session services (SS) encountered an error while trying to activate CP-CP sessions with an adjacent node.
Recommended Action The maximum number of retries for CP-CP session activation has been exceeded. The local node will not try to reactivate CP-CP sessions with the adjacent node. Probable causes of this error are incorrect network configuration, a communications error with the remote node, the remote node sending an invalid message, or the required system resources could not be obtained. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logss_CSWSSSTR_LOGMSG_01 : SS - received unexpected start_tp_reply for tp: %1
Explanation An incorrect target_tp_name was sent in the start_tp_reply.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
%APPN-3-logss_FLUSH_IPS : SS - Flushing ips queue, ips_name = [chars]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logss_PARSE_CV46_ERROR : SS - Error found when parsing CV46, sense_code = [hex]
Explanation Session services (SS) received an invalid SNA message.
Recommended Action Session services (SS) encountered an invalid RSCV (control vector x'46') while attempting to activate a route for a session. The required subvector x'4680' was not found in the received RSCV. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logss_PCREATE_CP_CAPS_FAILED : SS - Unable to PCreate CP-Caps tp - RC =
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logss_RANDOMIZE_PCID_VALUE : SS - PCID has been modified as the result of PCID collision, old_pcid = [hex], hash1_cp_name = [hex]
Explanation The local node detected a collision while generating PCIDs (SNA session identifiers).
Recommended Action 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.
Error Message%APPN-3-logss_RCV_UNKNOWN_IPS_SS_P_Q : SS - Deq UNKNOWN IPS msg from SS Priority Q, ips_name = [hex]
Explanation SS main dequeued an unknown IPS message.
Recommended Action Copy the error message exactly as it appears, copy the IPS message header, and report it to your technical support representative.
Error Message%APPN-3-logss_RCV_UNKNOWN_IPS_SS_Q : SS - Deq UNKNOWN IPS msg from SS Q
Explanation SS main dequeued an unknown IPS message.
Recommended Action Copy the error message exactly as it appears, copy the IPS message header, and report it to your technical support representative.
Error Message%APPN-3-logss_REJECT_CP_CP_SESSION : SS - Reject CP-CP session from an adjacent node, sense_code = [hex]
Explanation Session services (SS) encountered an error while trying to activate CP-CP sessions with an adjacent node.
Recommended Action The sense code provides more detailed information about why the sessions could not be activated. Probable causes of this error are incorrect network configuration, a communications error with the remote node, the remote node sending an invalid message, or the required system resources could not be obtained. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logss_RSCV_TOO_LONG : SS - RSCV exceeds maximum length
Explanation Session services (SS) could not process a session initialization request.
Recommended Action 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 incorrect network configuration. For example, if a session route must 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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logss_SEND_NEG_INIT_SIG_RSP : SS - Send Negative INIT_SIGNAL Response to SM
Explanation Session services (SS) rejected a session initialization request.
Recommended Action The sense code contained in the negative response provides more detailed information on why the request was rejected. Probable causes are incorrect network configuration, a communications error with the remote node, the remote node sending an invalid message, or the required system resources could not be obtained. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logss_START_TP_FAILED : SS - START TP Failed, sending ALERT_SIGNAL message to MS, sense_code = [hex]
Explanation The transaction program (TP) start failed for either the REQUEST_CP_CAP_TP or the DEACT_SESSION_TP.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-logss_UNEXPECTED_LOC_MSG_RQ : SS - Received a LOCATE_MESSAGE from DS in the wrong state
Explanation Session services (SS) received an unexpected locate request from another node via directory services.
Recommended Action The request does not specify the local node as the network node server of the LU that sent the request (the origin LU). Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logss_XXXSSP04_LOGMSG_01 : SS - Sending ADJACENT_CP_ERROR to CS: adj_node_p=%1; cp_name=%2
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logss_XXXSSP16_LOGMSG_01 : SS - ssp16: Rcvd DEACT_CP_CP_SESSION
Explanation A DEACTIVATE_CP_CP_SESSION message was received from either DS or TRS.
Recommended Action A CP-CP session with the adjacent node was deactivated. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logss_XXXSSP1C_LOGMSG_01 : SS - ssp1c: Design Flow: cdinit_without_cvs_p is NULL
Explanation A CDINIT is not present in the LOCATE MESSAGE GDS_VARIABLE list received from DS for this distributed search request.
Recommended Action The locate search terminates, and sessions cannot be established with the resource being located. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logss_XXXSSP31_LOGMSG_01 : SS - Sending ALERT_SIGNAL to MS
Explanation RSCV was not present in the ISR_INIT signal when a bind was sent from an NN.
Recommended Action An RSCV is not present in the ISR_INIT and the adjacent node is unknown. This is an informational message only. No action is required.
Error Message%APPN-3-logssa_DEQ_UNKN_IPS_NAME : -- SSA -- (gen) Deq UNKNOWN ips_name, ips_name: [hex]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logssa_Z12_SUBAGENT_TIMEOUT : APPN SNMP Subagent Timeout. ms_data_type= %ld; total # timeouts=%ld
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logssa_Z12_UNRECOGNIZED_IPS : retr_ms_data() unrecognized ips
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logssa_Z38_MSDATA_DIALOG_F : send_via_dialog(): can't forward the message to component via dialog
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logssa_Z38_PID_PQNUM_INVALID : SSA's pid id, or PQnum is invalid, pid = [hex] return code = [hex]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD01_LOGMSG_01 : TP(receive_network_search): APPN not registered with name server
Explanation The directory services transaction program (TP) was started but could not attach to the APPN communications system.
Recommended Action Probable causes of this error are an operator starting the transaction program without starting the APPN communications system (the local node), the APPN communications system abending, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD01_LOGMSG_02 : TP(receive_network_search): APPC not started
Explanation The directory services transaction program (TP) was started but could not attach to the APPC communications system.
Recommended Action Probable causes of this error are an operator starting the TP without starting the APPC/APPN communications system (the local node), the APPC/APPN communications system abending, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD01_LOGMSG_03 : TP(receive_network_search): Receive_Allocate Failed, primary rc = [hex], secondary rc = [hex].
Explanation The transaction program (TP) could not receive (accept) a network search (LOCATE) request from an adjacent node.
Recommended Action The APPC RECEIVE_ALLOCATE verb failed for the TP in an adjacent node (over the CP-CP sessions). The primary and secondary return codes detail the error. Possible causes of this error are an internal code problem, or a communications error (preventing the establishment of a conversation with the adjacent node). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD01_LOGMSG_04 : TP(receive_network_search): Unexpected return code from RECEIVE_AND_WAIT, primary rc = [hex], secondary rc = [hex]
Explanation The directory services transaction program (TP) could not receive a network search request from an adjacent node.
Recommended Action The APPC RECEIVE_AND_WAIT verb for the message failed. The primary and secondary return codes detail the error. Probable causes of this error are a communications error while receiving the message, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD01_LOGMSG_05 : TP(receive_network_search): Unexpected data_rcvd from GDS RECEIVE_AND_WAIT, data received type = [hex]
Explanation The directory services transaction program (TP) that receives network search request from other nodes received invalid or unexpected data.
Recommended Action The what received data indicator from the APPC RECEIVE_AND_WAIT verb is not an expected value. Probable causes of this error are the remote node sending a too large message and the transaction program aborting the reception of any more data, the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD02_LOGMSG_01 : TP(send_network_search): lu6.2 verb: ALLOCATE failed, primary rc = [hex], secondary rc = [hex]
Explanation The transaction program (TP) could not allocate a conversation with an adjacent node.
Recommended Action The directory services transaction program could not send a locate search request to an adjacent node. The APPC ALLOCATE verb failed for the TP in an adjacent node over the CP-CP sessions. The primary and secondary return codes detail the error. One possible cause of this problem is that a communications error occurred (preventing the establishment of a conversation with the adjacent node). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD02_LOGMSG_02 : TP(send_network_search): lu6.2 verb: SEND_DATA failed, primary rc = [hex], secondary rc = [hex]
Explanation The transaction program (TP) could not send a search request to an adjacent node.
Recommended Action The directory services TP could not send a locate search request to an adjacent node. The APPC SEND_DATA for the locate command failed. The primary and secondary return codes detail the error. One possible cause of this problem is that a communications error occurred while sending the search request. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD02_LOGMSG_03 : TP(send_network_search): APPN not registered with name server
Explanation The directory services transaction program (TP) was started but could not attach to the APPN communications system.
Recommended Action Probable causes of this error are an operator starting the transaction program without starting the APPN communications system (the local node), the APPN communications system abending, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD02_LOGMSG_04 : TP(send_network_search): APPC not started
Explanation The directory services transaction program (TP) was started but could not attach to the APPC communications system.
Recommended Action Probable causes of this error are an operator starting the TP without starting the APPC/APPN communications system (the local node), the APPC/APPN communications system abending, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD02_LOGMSG_05 : TP(send_network_search): Start_TP Failure, primary rc = [hex], secondary rc = [hex]
Explanation The transaction program (TP) could not register itself as an APPC transaction program.
Recommended Action The directory services TP cannot attach to the APPC/APPN communications system. The APPC TP_STARTED verb failed. The primary and secondary return codes detail the error. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD03_LOGMSG_01 : TP(receive_resource_reg): DS could not parse GDS
Explanation The network node transaction program (TP) received invalid data.
Recommended Action The TP that processes resource registration requests from other nodes received invalid data. It could not parse the received resource registration request. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD03_LOGMSG_02 : TP(receive_resource_reg): SEND_ERROR failed, primary rc = [hex]
Explanation The network node transaction program (TP) detected an error in a received resource registration request, but could not send the "negative" reply.
Recommended Action Directory services detected an error in a received resource registration request, but the TP could not send an error reply to the adjacent node. The APPC SEND_ERROR verb failed for the resource registration reply. The primary return code details the error. Probable causes of this error are a communications error while sending the registration reply, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD03_LOGMSG_03 : TP(receive_resource_reg): Invalid Resource Registration Reply type, Reply Type = [hex]
Explanation The network node transaction program (TP) received an invalid message from directory services.
Recommended Action The network node TP received an IPS message from directory services that it does not recognize or cannot process. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD03_LOGMSG_04 : TP(receive_resource_reg): APPN not registered with name server
Explanation The directory services transaction program (TP) was started but could not attach to the APPN communications system.
Recommended Action Probable causes of this error are an operator starting the TP without starting the APPN communications system (the local node), the APPN communications system abending, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD03_LOGMSG_05 : TP(receive_resource_reg): APPC not started, primary rc = [hex], secondary rc = [hex]
Explanation The directory services transaction program (TP) was started but could not attach to the APPC communications system.
Recommended Action Probable causes of this error are an operator starting the TP without starting the APPN communications system (the local node), the APPN communications system abending, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD03_LOGMSG_06 : TP(receive_resource_reg): Receive_Allocate Failed
Explanation The transaction program (TP) could not receive (accept) a registration request from an adjacent node.
Recommended Action The APPC RECEIVE_ALLOCATE verb failed for the TP in an adjacent node (over the CP-CP sessions). The primary and secondary return codes detail the error. Probable causes of this error are an internal code problem, or a communications error (preventing the establishment of a conversation with the adjacent node). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD03_LOGMSG_07 : TP(receive_resource_reg): Unexpected RC from receive_and_wait, primary rc = [hex], secondary rc = [hex]
Explanation The directory services transaction program (TP) could not receive a resource registration message from an adjacent node.
Recommended Action The APPC RECEIVE_AND_WAIT verb for the message failed. The primary and secondary returns codes detail the error. Probable causes of this error are a communications error while receiving the message, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD03_LOGMSG_08 : TP(receive_resource_reg): Unexpected data_rcvd from GDS receive_and_wait: [hex]
Explanation The directory services transaction program (TP) that receives resource registration requests from other nodes received invalid or unexpected data.
Recommended Action The what received data indicator from the APPC RECEIVE_AND_WAIT verb is not an expected value. Probable causes of this error are the remote node sending a message that was too large and the transaction program aborting the reception of any more data, the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD03_LOGMSG_09 : TP(receive_resource_reg): Unexpected stat_rcvd from GDS receive_and_wait: [hex]
Explanation The directory services transaction program (TP) that receives resource registration requests from other nodes received invalid or unexpected data.
Recommended Action The what received status indicator from the APPC RECEIVE_AND_WAIT verb is not an expected value. Probable causes of this error are the remote node sending a too large message and the transaction program aborting the reception of any more data, the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD03_LOGMSG_10 : TP(receive_resource_reg): Unexpected return code from CONFIRMED verb, primary rc = [hex], secondary rc = [hex]
Explanation The transaction program (TP) could not confirm the successful processing of a resource registration request.
Recommended Action The directory services TP could not confirm the successful processing of a resource registration request received from an adjacent node. The APPC CONFIRMED verb failed. The primary and secondary return codes detail the error. Probable causes of this error are a communications error while sending the confirmation, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD04_LOGMSG_01 : TP(req_resource_reg): APPN not registered with name server
Explanation The directory services transaction program (TP) was started but could not attach to the APPN communications system.
Recommended Action Probable causes of this error are an operator starting the TP without starting the APPN communications system (the local node), the APPN communications system abending, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD04_LOGMSG_02 : TP(req_resource_reg): APPC not started
Explanation The directory services transaction program (TP) was started but could not attach to the APPC communications system.
Recommended Action Probable causes of this error are an operator starting the TP without starting the APPN communications system (the local node), the APPN communications system abending, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD04_LOGMSG_03 : TP(req_resource_reg): Start_TP Failure, primary rc = [hex], secondary rc = [hex]
Explanation The transaction program (TP) could not register itself as an APPC transaction program.
Recommended Action The directory services TP cannot attach to the APPC/APPN communications system. The APPC TP_STARTED verb failed. The primary and secondary return codes detail the error. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD04_LOGMSG_04 : TP(req_resource_reg): ALLOCATE failure, primary rc = [hex], secondary rc = [hex], sense code = [hex]
Explanation The transaction program (TP) could not send a resource registration request to an adjacent node.
Recommended Action The APPC ALLOCATE verb failed for the TP in an adjacent node. The primary and secondary return codes detail the error. Possible causes of this error are a communications error (preventing the establishment of a conversation with the adjacent node), or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD04_LOGMSG_05 : TP(req_resource_reg): SEND_DATA failure, primary rc = [hex], secondary rc = [hex]
Explanation The directory services transaction program (TP) could not send a resource registration request to an adjacent node.
Recommended Action The APPC SEND_DATA verb for the registration request failed. The primary and secondary return codes detail the error. Probable causes of this error are a communications error while sending the registration request, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD04_LOGMSG_06 : TP(req_resource_reg): DEALLOCATE failure, primary rc = [hex], secondary rc = [hex]
Explanation An error occurred while the directory services transaction program (TP) was sending a resource registration request to an adjacent node.
Recommended Action The APPC DEALLOCATE verb for the registration request failed. The primary and secondary return codes detail the error. Probable causes of this error are a communications error while sending the registration request, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD04_LOGMSG_07 : TP(req_resource_reg): Unexpected rc on rcv_and_wait
Explanation The directory services transaction program (TP) could not receive a reply to a resource registration request from an adjacent node.
Recommended Action The APPC RECEIVE_AND_WAIT verb for the reply failed. The primary and secondary return codes detail the error. Probable causes of this error are a communications error occurred while receiving the reply, the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPD04_LOGMSG_08 : TP(req_resource_reg): Unexpected data_rcvd: [hex]
Explanation The directory services transaction program (TP) that sends resource registration requests to other nodes received invalid or unexpected data while waiting for the resource registration reply from an adjacent node.
Recommended Action The what received data indicator from the APPC RECEIVE_AND_WAIT verb is not an expected value. Probable causes of this error are the remote node sending a message that was too large and the TP aborting the reception of any more data, the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPM90_LOGMSG_01 : TP(mds_send): SEND_DATA failed, primary rc = [hex], secondary rc = [hex]
Explanation The management services transaction program (TP) could not send a multiple domain support (MDS) message to an adjacent node.
Recommended Action The APPC SEND_DATA verb for the MDS message failed. The primary and secondary return codes detail the error. Probable causes of this error are a communications error while sending the MDS message, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPM90_LOGMSG_02 : TP(mds_send): APPN not registered with name server
Explanation The management services transaction program (TP) was started but could not attach to the APPN communications system.
Recommended Action Probable causes of this error are an operator starting the TP without starting the APPN communications system (the local node), the APPN communications system abending, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPM90_LOGMSG_03 : TP(mds_send): APPC not started
Explanation The management services transaction program (TP) was started but could not attach to the APPC communications system.
Recommended Action Probable causes of this error are an operator starting the TP without starting the APPN communications system (the local node), the APPN communications system abending, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPM90_LOGMSG_04 : TP(mds_send): Start_TP Failure, primary rc = [hex], secondary rc = [hex]
Explanation The transaction program (TP) could not register itself as an APPC transaction program.
Recommended Action The management services TP cannot attach to the APPC/APPN communications system. The APPC TP_STARTED verb failed. The primary and secondary return codes detail the error. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPM90_LOGMSG_05 : TP(mds_send): allocation failure, primary rc = [hex], secondary rc = [hex]
Explanation The transaction program (TP) could not start a management services transaction with an adjacent node.
Recommended Action The APPC ALLOCATE verb failed for the TP in an adjacent node. The primary and secondary return codes detail the error. Probable causes of this error are a communications error (preventing the establishment of a conversation with the adjacent node), or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPM91_LOGMSG_01 : TP(mds_send): invalid mode in ms_transport, mode name = [chars]
Explanation The management services transaction program (TP) specified an invalid mode name to use for a management services transaction.
Recommended Action The only modes allowed for MS transactions are CPSVCMG and SNASVCMG. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPM92_LOGMSG_01 : TP(mds_send): send_ms_response failed, primary rc = [hex], sense data = [hex]
Explanation The transaction program (TP) could not send a multiple domain support (MDS) message to an adjacent node.
Recommended Action Either a software problem was detected or an error occurred while transferring the data. The primary return code details the error. This log record is created in conjunction with the following log records (which contain additional information about the nature of the failure): 2F115000-00000006, 2F115000-0000002B, and 2F115000-0000002C. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPM93_LOGMSG_01 : TP(mds_receive): size of received message 32767 bytes, size = [hex]
Explanation The management services transaction program (TP) that receives multiple domain support (MDS) messages from other nodes received invalid data.
Recommended Action The size of the received MDS message exceeded the maximum size allowed by SNA protocol rules. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPM93_LOGMSG_02 : TP(mds_receive): Unexpected or unrecognized stat_rcvd type = [hex]
Explanation The management services transaction program (TP) that receives multiple domain support (MDS) messages from other nodes received invalid or unexpected data.
Recommended Action The what received status indicator from the APPC RECEIVE_AND_WAIT verb is not an expected value. Probable causes of this error are the remote node sending a message that was too large and the transaction program aborting the reception of any more data (log event 2F115000-00000007 is also logged), the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPM93_LOGMSG_03 : TP(mds_receive): RECEIVE_AND_WAIT failed, primary rc = [hex], secondary rc = [hex]
Explanation The management services transaction program (TP) could not receive a multiple domain support (MDS) message from an adjacent node.
Recommended Action 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. Probable causes of this error are a communications error occurred while receiving the MDS message or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPM93_LOGMSG_04 : TP(mds_receive): APPN not registered with name server
Explanation The management services transaction program (TP) was started but could not attach to the APPN communications system.
Recommended Action Probable causes of this error are an operator starting the TP without starting the APPN communications system (the local node), the APPN communications system abending, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPM93_LOGMSG_05 : TP(mds_receive): APPC not started
Explanation The management services transaction program (TP) was started but could not attach to the APPC communications system.
Recommended Action Probable causes of this error are an operator starting the TP without starting the APPC/APPN communications system (the local node), the APPC/APPN communications system abending, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPM93_LOGMSG_06 : TP(mds_receive): Receive_Allocate Failed, primary rc = [hex], secondary rc = [hex]
Explanation The transaction program (TP) could not receive (accept) a management services message, such as an alert or MS capabilities, from an adjacent node.
Recommended Action The APPC RECEIVE_ALLOCATE verb failed for the TP in an adjacent node. The primary and secondary return codes detail the error. Probable causes of this error are an internal code problem or a communications error (preventing the establishment of a conversation with the adjacent node). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPM93_LOGMSG_07 : TP(mds_receive): Invalid mode name in Receive_Allocate, mode name = [chars]
Explanation The management services transaction program (TP) could not receive a management services message, such as an alert or MS capabilities, from an adjacent node.
Recommended Action The mode name of the session from which the message was received is invalid. Management services messages can only be transferred using the CPSVCMG or SNASVCMG modes. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPM94_LOGMSG_01 : TP(msu_handler): size of received message 32767 bytes, size = [hex]
Explanation The management services transaction program (TP) that receives CP-MSU messages from migration nodes received invalid data.
Recommended Action The size of the received CP-MSU message exceeded the maximum size allowed by SNA protocol rules. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPM94_LOGMSG_02 : TP(msu_handler): Unexpected or unrecognized stat_rcvd type = [hex]
Explanation The management services transaction program (TP) 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. Probable causes of this error are the following:
•
•
•
•
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPM94_LOGMSG_03 : TP(msu_handler): RECEIVE_AND_WAIT failed, primary rc = [hex], secondary rc = [hex]
Explanation The management services transaction program (TP) could not receive a CP-MSU message from an adjacent migration node.
Recommended Action The APPC RECEIVE_AND_WAIT verb for the CP-MSU message failed. The primary and secondary return codes detail the error. Probable causes of this error are a communications error while receiving the CP-MSU message, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPM94_LOGMSG_04 : TP(msu_handler): APPN not registered with name server
Explanation The management services transaction program (TP) was started but could not attach to the APPN communications system.
Recommended Action Probable causes of this error are an operator starting the TP without starting the APPN communications system (the local node), the APPN communications system abending, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPM94_LOGMSG_05 : TP(msu_handler): APPC not started
Explanation The management services transaction program (TP) was started but could not attach to the APPC communications system.
Recommended Action Probable causes of this error are an operator starting the TP without starting the APPC/APPN communications system (the local node), the APPC/APPN communications system abending, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPM94_LOGMSG_06 : TP(msu_handler): Receive_Allocate Failed, primary rc = [hex], secondary rc = [hex]
Explanation The management services transaction program (TP) could not receive (accept) a management services message, such as an alert encapsulated in a CP-MSU, from an adjacent management services migration node.
Recommended Action The APPC RECEIVE_ALLOCATE verb failed for the migration management services send TP in an adjacent node. The primary and secondary return codes detail the error. Probable causes of this error are an internal code problem or a communications error (preventing the establishment of a conversation with the adjacent node). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPM94_LOGMSG_07 : TP(msu_handler): Invalid mode name in Receive_Allocate, mode name = [chars]
Explanation The management services transaction program (TP) could not receive a management services message (such as an alert encapsulated in a CP-MSU) from an adjacent management services migration node.
Recommended Action The mode name of the session from which the message was received is invalid. Management services messages can only be transferred using the CPSVCMG or SNASVCMG modes. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPS17_LOGMSG_01 : TP(deact_session): APPN not registered with name server
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPS17_LOGMSG_02 : TP(deact_session): APPC not started
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPS21_LOGMSG_01 : TP(cp_cap_son): Protocol error: RECEIVE_AND_WAIT failed, primary rc = [hex], secondaryt rc = [hex], stat rcvd = [hex]
Explanation The session services transaction program (TP) that receives CP capabilities on the contention loser session from adjacent nodes received invalid or unexpected data, or an error occurred while receiving the data.
Recommended Action 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 primary and secondary return codes detail the error and the what received indicator. Probable causes of this error are a communications error while receiving the CP capabilities message, the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPS21_LOGMSG_02 : TP(cp_cap_son): APPN not registered with name server
Explanation The session services transaction program (TP) was started but could not attach to the APPN communications system.
Recommended Action Probable causes of this error are an operator starting the TP without starting the APPN communications system (the local node), the APPN communications system abending, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPS21_LOGMSG_03 : TP(cp_cap_son): APPC not started
Explanation The session services transaction program (TP) was started but could not attach to the APPC communications system.
Recommended Action Probable causes of this error are an operator starting the TP without starting the APPC/APPN communications system (the local node), the APPC/APPN communications system abending, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPS21_LOGMSG_04 : TP(cp_cap_son): Receive_Allocate Failed, primary rc = [hex], secondary rc = [hex]
Explanation The transaction program (TP) could not receive (accept) a CP capabilities message from an adjacent node.
Recommended Action The APPC RECEIVE_ALLOCATE verb failed for the TP in an adjacent node (over the CP-CP sessions). The primary and secondary return codes detail the error. Probable causes of this error are an internal code problem or a communications error (preventing the establishment of a conversation with the adjacent node). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPS21_LOGMSG_05 : TP(cp_cap_son): Invalid RC from initial receive_and_wait, primary rc = [hex], secondary rc = [hex]
Explanation The session services transaction program (TP) that receives CP capabilities on the contention loser session could not receive CP capabilities information from an adjacent node.
Recommended Action The APPC RECEIVE_AND_WAIT verb for the CP capabilities message failed. The primary and secondary return codes detail the error. Probable causes of this error are a communications error while receiving the CP capabilities message, the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPS21_LOGMSG_06 : TP(cp_cap_son): Unexpected what_rcvd from GDS receive_and_wait = [hex]
Explanation The session services transaction program (TP) that receives CP capabilities messages from other nodes received invalid or unexpected data.
Recommended Action The returned what received data indicator in the APPC RECEIVE_AND_WAIT verb is not an expected value. Probable causes are the remote node sending a message that is too large and the transaction program aborting the reception of any more data, the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPS21_LOGMSG_07 : TP(cp_cap_son): Invalid GDS length = [hex]
Explanation The session services transaction program (TP) that receives CP capabilities messages from other nodes received invalid or unexpected data.
Recommended Action The size of the received data is not large enough to hold a CP capabilities message (GDS variable x'12C1'). Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPS21_LOGMSG_08 : TP(cp_cap_son): Invalid GDS variable received = [hex]
Explanation The session services transaction program (TP) that receives CP capabilities messages from other nodes received invalid or unexpected data.
Recommended Action The received message is not a CP capabilities message (GDS variable x'12C1'). Probable causes are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPS21_LOGMSG_09 : TP(cp_cap_son): Bad sense code received from ss on rsp, sense code = [hex]
Explanation The session services transaction program (TP) that receives CP capabilities messages from other nodes received invalid or unexpected data, or session services encountered an error processing the data.
Recommended Action Session services rejected the received message with the indicated sense code. Probable causes of this error are a system function failure while processing the message, a serious memory shortage problem, the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPS27_LOGMSG_01 : TP(request_cp_cap): Protocol error: RECEIVE_AND_WAIT failed, primary rc = [hex], secondary rc = [hex]
Explanation The session services transaction program (TP) could not receive the CP capabilities message from an adjacent node.
Recommended Action 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. Probable causes of this error are a communications error while receiving the CP capabilities message, the remote node sending an invalid message, a communications error, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPS27_LOGMSG_02 : TP(request_cp_cap): Protocol error: RECEIVE_AND_WAIT failed, data rcvd = [hex], stat rcvd = [hex]
Explanation The session services transaction program (TP) could not receive a CP capabilities message from an adjacent node.
Recommended Action 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. Probable causes of the error are a communications error while receiving the CP capabilities message, the remote node sending an invalid message, a communications error, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPS27_LOGMSG_03 : TP(request_cp_cap): APPN not registered with name server
Explanation The session services transaction program (TP) was started but could not attach to the APPN communications system.
Recommended Action Probable causes of this error are an operator starting the TP without starting the APPN communications system (the local node), the APPN communications system abending, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPS27_LOGMSG_04 : TP(request_cp_cap): APPC not started
Explanation The session services transaction program (TP) was started but could not attach to the APPC communications system.
Recommended Action Probable causes of this error are an operator starting the TP without starting the APPC/APPN communications system (the local node), the APPC/APPN communications system abending, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPS27_LOGMSG_05 : TP(request_cp_cap): Start_TP Failure, primary rc = [hex], secondary rc = [hex]
Explanation The transaction program (TP) could not register itself as an APPC transaction program.
Recommended Action The session services TP cannot attach to the APPC/APPN communications system. The APPC TP_STARTED verb failed. The primary and secondary return codes detail the error. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPS27_LOGMSG_06 : TP(request_cp_cap): Unexpected RC from Allocate, primary rc = [hex], secondary rc = [hex]
Explanation The session services transaction program (TP) could not send a CP capabilities message to an adjacent node.
Recommended Action The APPC ALLOCATE verb failed for the TP in an adjacent node. The primary and secondary return codes detail the error. Probable causes of this error are a communications error (preventing the establishment of a conversation with the adjacent node), or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPS27_LOGMSG_07 : TP(request_cp_cap): Unexpected RC from SEND_DATA, primary rc = [hex], secondary rc = [hex]
Explanation The session services transaction program (TP) could not send a CP capabilities message to an adjacent node.
Recommended Action The APPC SEND_DATA verb failed for the TP in an adjacent node. The primary and secondary return codes detail the error. Probable causes of this error are a communications error (preventing the establishment of a conversation with the adjacent node), or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPS27_LOGMSG_08 : TP(request_cp_cap): Unexpected RC from GET_ATTRIBUTES, primary rc = [hex], secondar rc = [hex]
Explanation The session services transaction program (TP) could not obtain the characteristics of the established CP-CP session (such as the adjacent node name and conversation group ID) while exchanging CP capabilities with an adjacent node.
Recommended Action The APPC GET_ATTRIBUTES verb failed. The primary and secondary return codes detail the error. Probable causes of this error are a system function failure while processing the message, a serious memory shortage problem, or a programming error within the node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPS27_LOGMSG_09 : TP(request_cp_cap): Invalid GDS length or incomplete data, data_rcvd = [hex]
Explanation The session services transaction program (TP) that exchanges CP capabilities messages with other nodes received invalid or unexpected data.
Recommended Action 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'). Probable causes of this error are the remote node sending a message that was too large and the TP aborting the reception of any more data, the remote node sending an invalid message, a programming error in the node, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPS27_LOGMSG_10 : TP(request_cp_cap): Invalid GDS variable received
Explanation The session services transaction program (TP) that exchanges CP capabilities messages with other nodes received invalid or unexpected data.
Recommended Action The received message is not a CP capabilities message (GDS variable x'12C1'). Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPTP0_LOGMSG_01 : TP(process_output_tdu): ALLOCATE failed, primary rc = [hex], secondary rc = [hex]
Explanation The transaction program (TP) could not allocate a conversation with an adjacent node.
Recommended Action The TRS transaction program could not send one or more topology updates (TDUs) to an adjacent node. The APPC ALLOCATE verb failed for the TP in an adjacent node (over the CP-CP sessions). The primary and secondary return codes detail the error. Possible causes of this error are a communications error preventing the establishment of a conversation with the adjacent node, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPTP0_LOGMSG_02 : TP(process_output_tdu): APPN not registered with name server
Explanation The topology and route selection services transaction program (TP) was started but could not attach to the APPN communications system.
Recommended Action Probable causes of this error are an operator starting the TP without starting the APPN communications system (the local node), the APPN communications system abending, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPTP0_LOGMSG_03 : TP(process_output_tdu): APPC not started
Explanation The topology and route selection services transaction program (TP) was started but could not attach to the APPC communications system.
Recommended Action Probable causes of this error are an operator starting the TP without starting the APPC/APPN communications system (the local node), the APPC/APPN communications system abending, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPTP0_LOGMSG_04 : TP(process_output_tdu): Start_TP Failure, primary rc = [hex], secondary rc = [hex]
Explanation The topology and route selection services transaction program (TP) could not register itself as an APPC transaction program.
Recommended Action The APPC TP_STARTED verb failed. The primary and secondary return codes detail the error. There is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPTP0_LOGMSG_05 : TP(process_output_tdu): Unexpected RC from SEND_DATA, primary rc = [hex], secondary rc = [hex]
Explanation The topology and route selection services transaction program (TP) could not send a topology update to an adjacent node.
Recommended Action The APPC SEND_DATA verb for the update failed. The primary and secondary return codes detail the error. Probable causes of this error are a communications error while sending the topology update, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPTP0_LOGMSG_06 : TP(process_output_tdu): Unexpected RC from DEALLOCATE, primary rc = [hex], secondary rc = [hex]
Explanation The topology and route selection services transaction program (TP) could not send a topology update to an adjacent node.
Recommended Action The APPC DEALLOCATE verb for the update failed. The primary and secondary return codes detail the error. Probable causes of this error are a communications error while sending the topology update, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPTXA_LOGMSG_01 : TP(receive_tdu): APPN not registered with name server
Explanation The topology and route selection services transaction program (TP) was started but could not attach to the APPN communications system.
Recommended Action Probable causes of this error are an operator starting the TP without starting the APPN communications system (the local node), the APPN communications system abending, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPTXA_LOGMSG_02 : TP(receive_tdu): APPC not started
Explanation The topology and route selection services transaction program (TP) was started but could not attach to the APPC communications system.
Recommended Action Probable causes of this error are an operator starting the TP without starting the APPN communications system (the local node), the APPN communications system abending, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPTXA_LOGMSG_03 : TP(receive_tdu): Receive_Allocate Failed, primary rc = [hex], secondary rc = [hex]
Explanation The topology and route selection services transaction program (TP) could not receive (accept) a topology update from an adjacent node.
Recommended Action The APPC RECEIVE_ALLOCATE verb failed for the TP in an adjacent node (over the CP-CP sessions). The primary and secondary return codes detail the error. Probable causes of this error are an internal code problem, or a communications error (preventing the establishment of a conversation with the adjacent node). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPTXA_LOGMSG_04 : TP(receive_tdu): Unexpected RC from receive_and_wait, primary rc = [hex], secondary rc = [hex]
Explanation The topology and route selection services transaction program (TP) could not receive a topology update message from an adjacent node.
Recommended Action The APPC RECEIVE_AND_WAIT verb for the message failed. The primary and secondary return codes detail the error. Probable causes of this error are a communications error while receiving the message, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtps_XXXTPTXA_LOGMSG_05 : TP(receive_tdu): Unexpected data_received = [hex]
Explanation The topology and route selection services transaction program (TP) received invalid or unexpected data.
Recommended Action The what received data indicator from the APPC RECEIVE_AND_WAIT verb is not an expected value. Probable causes of this error are the remote node sending a message that was too large and the TP aborting the reception of any more data, the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logTraceAccess : logTraceAccess, trcrc = 0x[hex]
Explanation The attempt to access the trace resources used by IOS failed.
Recommended Action The TraceAccess function failed with the indicated return code. Probable causes of this error are required system resources not being available to the issuing process (for example, trace files), a serious memory shortage, one or more missing required files, or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logTraceControl : logTraceControl, rc = 0x[hex]
Explanation An attempt to modify the trace information being trace failed.
Recommended Action The trace administration request failed. The attempt to start or stop the tracing of one or more trace categories failed. The TraceEnable or TraceDisable function failed with the indicated return code, because bad parameters were passed to the function. There is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logTraceDefineDestination : logTraceDefineDestination, rc = 0x[hex]
Explanation Could not create its internal trace information.
Recommended Action Initialization failed. The attempt to create the trace information failed. The function TraceDefineDestination failed with the indicated return code, because bad parameters were passed to the function or memory could not be allocated. Probable causes of this error are a serious memory shortage or an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logTraceInitialize : logTraceInitialize, trcrc = 0x[hex]
Explanation OS could not create its internal trace information.
Recommended Action Initialization failed. The attempt to create the trace information failed. The TraceInitialize function failed with the indicated return code, because bad parameters were passed to the function, a memory allocation attempt failed, or the specified NLS string tables could not be loaded. Probable causes of this error are a serious memory shortage, required system resources not being available to the issuing process (for example, trace files), one or more missing required files, or an internal code problem Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logTraceSetDestination : logTraceSetDestination, trcrc = 0x[hex]
Explanation The attempt to create the trace information failed.
Recommended Action The function TraceSetDestination failed with the indicated return code, because bad parameters were passed to the function. There is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logTraceSizeOf : logTraceSizeof, rc = 0x[hex]
Explanation The attempt to create the trace information failed.
Recommended Action The TraceSizeOf function failed with the indicated return code because bad parameters were passed to the function. There is an internal code problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtrsCOS_DATABASE : COS Database
Explanation Topology and route selection services (TRS) encountered a processing error.
Recommended Action Other log records are created in conjunction with this log record to provide additional information about the error. Use this log record to display the contents of the TRS class-of-service database (COS) to aid in determining the nature of the problem. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtrsCREATE_RQST_RTE_RSP : CREATE_RQ_SINGLE_HOP_ROUTE_RSP: invalid return code, return_code = [hex]
Explanation Topology and route selection services (TRS) encountered a condition within the component that should not occur.
Recommended Action The routine that builds responses to request route requests was invoked with an invalid parameter. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtrsDEACTIVATE_CPCP_L : TRS sending DEACTIVATE_CP_CP_SESSION to SS for ConLoser CP-CP session, sense_code = [hex]
Explanation Topology and route selection services (TRS) deactivated the contention loser CP-CP session with an adjacent node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-logtrsDEACTIVATE_CPCP_L_W : TRS sending DEACTIVATE_CP_CP_SESSION to SS for both CP-CP sessions, conloser_cgid = [hex], conwinner_cgid = [hex], sense_code = [hex]
Explanation Topology and route selection services (TRS) deactivated the CP-CP sessions with an adjacent node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-logtrsDEACTIVATE_CPCP_W : TRS sending DEACTIVATE_CP_CP_SESSION to SS for ConWinner CP-CP session, conwinner_gid = [hex], sense_code = [hex]
Explanation Topology and route selection services (TRS) deactivated the contention winner CP-CP session with an adjacent node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-logtrsDEST_TG_VECTOR : Destination TG Vector
Explanation Topology and route selection services (TRS) encountered a processing error while processing a request to compute a route through the APPN network.
Recommended Action Other log records are created in conjunction with this log record to provide additional information about the error. Use this log record, along with log records 2F10A000-0000001A and 2F10A000-0000001B, to determine which internal route request failed. Specifically, use this log record to display the destination transmission group (TG) vectors in the route request. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtrsINCONSISTENT_NODE_INFO : Inconsistent node information in TDU, network_qualified_name = [chars]
Explanation Topology and route selection services (TRS) received a topology update containing inconsistent topology information.
Recommended Action 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. This error probably occurred because some of the nodes (including the local node) have out-of-date information about the resource, the remote node sent an invalid message, there is a programming error in the node, there is a software problem in the node that sent the message, or the APPC/APPN support in the remote node is not compatible with the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtrsINCONSISTENT_TG : Inconsistent TG information in TDU, tg_number = [hex], partner_name = [chars]
Explanation Topology and route selection services (TRS) received a topology update containing inconsistent topology information.
Recommended Action A transmission group (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. This error probably occurred because some of the nodes (including the local node) have out-of-date information about the resource, the remote node sent an invalid message, a programming error may exist in the node that sent the message, or the APPC/APPN support in the remote node is incompatible with the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtrsINIT_TDM_IN_NULL : INITIALIZE_TDM: node_vector_p in NULL
Explanation A system function failed while trying to initialize the topology database manager component of topology and route selection services.
Recommended Action This error probably occurred because a serious memory shortage problem exists, an operating system error occurred while attempting to start the topology database manager, or a programming error exists within the node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtrsINVALID_TDU_RECVD : Invalid TDU received, adjacent_node_name = [chars], sense_code = [hex], detector_name = [chars]
Explanation Topology and route selection services (TRS) received an invalid topology update from a partner node.
Recommended Action The specific error is indicated by the logged sense code:
•
•
•
•
•
•
•
This error probably occurred because the remote node sent an invalid message, a programming error occurred on the node, a software problem exists in the node that sent the message, or the APPC/APPN support in the remote node is incompatible with the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtrsLAST_FRSN_SENT_CURR : Current FRSN in received TDU greater than last FRSN value, last_frsn_sent = [dec], current_frsn = [dec]
Explanation Topology and route selection services (TRS) received an invalid topology update from a partner node.
Recommended Action The flow reduction sequence numbers (FRSN) in the received TDU are invalid. The last sent number is greater than the current number. This error probably occurred because the remote node sent an invalid message, a software problem probably exists in the node that sent the message, or the APPC/APPN support in the remote node is incompatible with the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtrsLAST_FRSN_SENT_RECVD : Last FRSN sent value in received TDU is less than the last FRSN received, last_frsn_sent = [dec], last_frsn_rcvd = [dec]
Explanation Topology and route selection services (TRS) received an invalid topology update from a partner node.
Recommended Action The received TDU is out of sequence. The last flow reduction sequence numbers (FRSN) value sent in the TDU is less than the last FRSN value sent in a previously received TDU. This problem probably occurred because the remote node sent an invalid message, a software problem exists in the node that sent the message, or the APPC/APPN support in the remote node is incompatible with the local APPC/APPN support. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtrsNODE_WEIGHT_COMPUTATION : NODE_WEIGHT_COMPUTATION: invalid weight_definition_string, string = [chars]
Explanation Topology and route selection services (TRS) encountered an error while computing a route.
Recommended Action A class-of-service (COS) entry in the topology database contained an invalid weight definition string for a node row. The problem probably occurred because the network configuration is incorrect. This error should have been detected when the COS was defined. The COS definition in the topology database has been corrupted. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtrsORIG_TG_VECTOR : Origin TG Vector
Explanation Topology and route selection services (TRS) encountered a processing error while processing a request to compute a route through the APPN network.
Recommended Action Other log records are created in conjunction with this log record to provide additional information about the error. Use this log record, along with log records 2F10A000-0000001A and 2F10A000-0000001C, to determine which internal route request failed. Specifically, use this log record to display the origin transmission group (TG) vectors contained in the route request. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtrsPROCESS_COS_UPDATE : PROCESS_COS_UPDATE: Invalid request type, request_type = [hex]
Explanation Topology and route selection services (TRS) received an invalid internal interprocess signal.
Recommended Action TRS detected an error while processing a request to add or update a class-of-service (COS) definition. The COS_UPDATE internal signal contained an invalid request code. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtrsPROCESS_LOCAL_CHANGES : PROCESS_LOCAL_RESOURCE_CHANGES: invalid ips_name, ips_name = [hex]
Explanation Topology and route selection services (TRS) received an internal interprocess signal (IPS) it does not recognize or process.
Recommended Action TRS internal data reporting routine received an IPS that it does not recognize or process while processing a transmission group (TG) update. This condition should not occur, because the unrecognized signal should not have been routed to TRS. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtrsPROCESS_LOCAL_TG_UPDATE : PROCESS_LOCAL_TG_UPDATE:tg_update direction is not OUT, partner_node_type = [dec]
Explanation Topology and route selection services (TRS) received an invalid internal interprocess signal.
Recommended Action 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 transmission group (TG). TRS processes TG updates for outbound TGs only; it expects the remote node owning the TG to send TDUs whenever the status of an inbound TG changes. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtrsPROCESS_UPDATE_COS : PROCESS_UPDATE_COS: Invalid request type, request_type = [hex]
Explanation Topology and route selection services (TRS) received an invalid internal interprocess signal.
Recommended Action TRS detected an error while processing a request to add or update a class-of-service (COS) definition. The COS_UPDATE internal signal contained an invalid request code. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtrsREQ_ROUTE : Request Route
Explanation Topology and route selection services (TRS) encountered a processing error while processing a request to compute a route through the APPN network.
Recommended Action Other log records are created in conjunction with this log record to provide additional information about the error. Use this log record, along with log records 2F10A000-0000001B and 2F10A000-0000001C, to determine which internal route request failed. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtrsREQUEST_RTE_RSP_SENSE : REQUEST_ROUTE_RSP failed, sense_code = [hex]
Explanation Topology and route selection services (TRS) encountered an error while processing a request to compute a route. The following are some possible causes of this error:
•
•
•
•
•
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtrsRQST_SNGL_HOP_RTE_RSP : Rq_single_hop_route failed, sense_code = [hex]
Explanation Topology and route selection services (TRS) encountered an error while processing a request to compute a single hop route (one intermediate node). This error can be caused by the following problems:
•
•
•
•
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtrsSENSECODE_PID_MODENAME : Invalid REQUEST_COS_TPF_VECTOR, sense_code = [hex], mode_name = [chars]
Explanation Topology and route selection services (TRS) encountered an error while processing a request to determine the class-of-service (COS) definition associated with a mode.
Recommended Action The request specified an invalid mode name (the requested mode name is unknown). Verify the mode and resend the request. This problem probably occurred because the network configuration is incorrect, or the COS definition in the topology database has been corrupted. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtrsTG_WEIGHT_COMPUTATION : TG_WEIGHT_COMPUTATION: invalid weight definition string, string = [chars]
Explanation Topology and route selection services (TRS) encountered an error while computing a route.
Recommended Action A class-of-service (COS) entry in the topology database contained an invalid weight definition string for a transmission group (TG) row. This problem probably occurred because the network configuration is incorrect. Check your network configuration and COS definition. The COS definition in the topology database has been corrupted. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtrsTRS_COUNTERS : TRS Counters, current_frsn_for_node = 0x[hex] , nbr_of_backward_tdus_sent = 0x[hex] , nbr_of_tdus_sent = 0x[hex] , nbr_of_tdus_received = 0x[hex] , nbr_of_route_calc_success = 0x[hex] , nbr_of_route_calc_failed = 0x[hex] , node_rsn_lt_current_rsn = 0x[hex] , node_rsn_eq_current_rsn = 0x[hex] , node_rsn_gt_current_rsn = 0x[hex] , node_rsn_found_inconsistent = 0x[hex] , node_rsn_odd_lt_current_rsn = 0x[hex] , node_rsn_odd_eq_current_rsn = 0x[hex] , node_rsn_odd_gt_current_rsn = 0x[hex] , node_topology_state_change = 0x[hex] , node_timer_pop_tdu_sent = 0x[hex] , node_garbage_collect_tdb_entry = 0x[hex] , tg_rsn_lt_current_rsn = 0x[hex] , tg_rsn_eq_current_rsn = 0x[hex] , tg_rsn_gt_current_rsn = 0x[hex] , tg_rsn_found_inconsistent = 0x[hex] , tg_rsn_odd_lt_current_rsn = 0x[hex] , tg_rsn_odd_eq_current_rsn = 0x[hex] , tg_rsn_odd_gt_current_rsn = 0x[hex] , tg_topology_state_change = 0x[hex] , tg_timer_pop_tdu_sent = 0x[hex] , tg_garbage_collect_tdb_entry = 0x[hex] , node_deleted_due_to_inconsist = 0x[hex]
Explanation Topology and route selection services (TRS) encountered a processing error.
Recommended Action Other log records are created in conjunction with this log record to provide additional information about the error. Use this log record to display statistics about the messages and actions TRS has processed. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtrsTRYING_TO_RECOVER : TRS Trying to recover from error
Explanation Topology and route selection services (TRS) encountered a processing error, but is trying to recover and continue processing.
Recommended Action Another log record that provides additional information about the error is created in conjunction with this log record (2F10A000-0000000A or 2F10A000-0000000B). Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtrsUNABLE_TO_CREATE_ERROR : TRS UNABLE_TO_CREATE error code, error_code = [hex]
Explanation Topology and route selection services (TRS) encountered an error while trying to initialize the component or an data structure.
Recommended Action This error probably occurred because of an operating system error, a serious memory shortage problem, or a programming error in the node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtrsUNABLE_TO_SEND_ERROR : TRS_UNABLE_TO_SEND error code
Explanation Topology and route selection services (TRS) encountered an error while trying to send an internal message (IPS) to another node component.
Recommended Action This error probably occurred because of an operating system error, a serious memory shortage, or a programming error in the node. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-logtrsUNKNOWN_MSG : Received an unknown msg, ips_name = [hex]
Explanation Topology and route selection services (TRS) received an internal interprocess signal it does not recognize or cannot process.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-7-MSALERT : Alert [chars] issued with sense code [hex] by [chars]
Explanation An alertable condition occurred in the local node.
Recommended Action Refer to "Detailed Alert" section of the IBM Systems Network Architecture Management Services Reference (order number SC30-3346) for a description of ALERTID. Also refer to the "Sense Data" section of IBM Systems Network Architecture Formats (order number GA27-3136) for a description of SENSE_CODE. Report this message to your technical support representative.
Error Message%APPN-3-nlsBADMEMSTATUS : Unrecognized memory status
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-nlspsnaBADCASE : Software Error: Unexpected switch statement value
Explanation The trace component encountered an unexpected condition while processing a request.
Recommended Action An internal value is invalid. Specifically, the value in a switch statement is invalid. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-nlspsnaBADIPS : Software Error: Unexpected IPS received
Explanation The trace component received an internal interprocess signal (IPS) it does not recognize, or the received IPS contains invalid data.
Recommended Action The unrecognized signal should not have been routed to the trace component for processing. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-nlspsnaBADPARM : Software Error: Invalid input parameter
Explanation The trace component encountered an unexpected condition while processing a request.
Recommended Action An internal function was invoked with an invalid or unexpected parameter. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-nlspsnaCONFLICTPARM : Software Error: Conflicting input parameters
Explanation The trace component encountered an unexpected condition while processing a request.
Recommended Action An internal function was invoked with conflicting or invalid parameters. An internal code problem exists. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-nlspsnaMALLOCFAILURE : Could not obtain local memory
Explanation Trace process could not obtain enough memory to perform a function.
Recommended Action Probable causes of this error are a serious memory shortage or a programming error in the trace utility. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-nlspsnaNOSHAREDMEMORY : Could not obtain shared memory
Explanation Trace process could not obtain enough memory to perform a function.
Recommended Action Probable causes of this error are a serious memory shortage or a programming error in the trace utility. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-nlspsnaSHAREMEMACCESSFAILED : Could not access shared memory
Explanation Trace process could not access the shared memory needed perform a function.
Recommended Action Probable causes of this error are a serious memory shortage or a programming error in the trace utility. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-nlspsnaSYSTEMRECOVERABLE : System function failed, will retry
Explanation A system component encountered a system error while processing a request.
Recommended Action The encountered error is recoverable, and the system component will retry the function that failed. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-nlspsnaSYSTEMSEVERE : System function failed, no retry
Explanation A system component encountered a system error while processing a request.
Recommended Action Either the encountered error is not recoverable, or the retry limit for the function has been reached. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-nlspsnaSYSTEMWARNING : System function failed, processing continues
Explanation A system component encountered a system error while processing a request.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-RMCG01 : RMCG01: Pool_p=[hex], is invalid or not proper type for this function
Explanation A request to adjust the scheduled delay period for sending an IPM (SNA pacing message) has detected a serious problem.
Recommended Action 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 has 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. There is an internal code problem with the system. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-6-SendMsg : [chars]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-5-SendReq : [chars]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-StartLinkFail : Link-station [chars] failed to activate. Sense code =[hex]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-3-StubFunction : APPN attempted to execute stubbed function [chars]().
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.