CIP-NEVADA Error Messages

Error messages related to the CIP interrupt controller

Error Message    %NEVADA-0-BADADD: Add: Invalid nevada interrupt code [dec]

Explanation    An attempt was made to specify an interrupt handler for an invalid interrupt type on the NEVADA interrupt control chip. This is a fatal internal logic error.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %NEVADA-0-BADDISABLE: Disable: Invalid nevada interrupt code [dec]

Explanation    An attempt was made to disable an invalid interrupt type on the NEVADA interrupt control chip. This is a fatal internal logic error.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %NEVADA-0-BADENABLE: Enable: Invalid nevada interrupt code [dec]

Explanation    An attempt was made to enable an invalid interrupt type on the NEVADA interrupt control chip. This is a fatal internal logic error.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %NEVADA-0-BADENABLE2: Enable: No interrupt routine for code [dec]

Explanation    An attempt was made to enable an interrupt routine on the NEVADA interrupt control chip, but no interrupt routine was specified. This is a fatal internal logic error.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %NEVADA-0-BADINT: Interrupt received with no interrupt routine defined

Explanation    An interrupt was received for a code with an undefined interrupt handler. This is a fatal internal logic error.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %NEVADA-0-BADREMOVE: Remove: Invalid nevada interrupt code [dec]

Explanation    An attempt was made to remove an interrupt handler for an invalid interrupt type on the NEVADA interrupt control chip. This is a fatal internal logic error.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

CIP-OFFL Error Messages

CIP error messages related to the offload protocol.

Error Message    %OFFL-6-COMMAND: Unrecognized Offload command code [dec]. xfer_element = 0x[hex]

Explanation    The host sent an offload command with an invalid offload command code. The CIP ignored the request.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %OFFL-3-HEX4W: [hex]: [hex] [hex] [hex] [hex] [chars]

Explanation    This message contains a hex dump of data associated with the immediately preceding error message.

Recommended Action    Copy the error message and the whole hex dump, and contact your technical support representative.

Error Message    %OFFL-3-HEX16B: [hex]: [hex][hex][hex][hex] [hex][hex][hex][hex] [hex][hex][hex][hex] [hex][hex][hex][hex] [chars]

Explanation    This message contains a hex dump of data associated with the immediately preceding error message.

Recommended Action    Copy the error message and the whole hex dump, and contact your technical support representative.

Error Message    %OFFL-3-ILLALD: Illegal data alignment: 0x[hex] + [dec] bytes >= 0x[hex]. xfer_element = 0x[hex]

Explanation    An internal logic error occurred. A block of offload protocol parameters crossed a buffer boundary. The CIP ignored the request.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %OFFL-3-ILLALH: Illegal hdr alignment detected. Address 0x[hex] + [dec] bytes > 0x[hex]. xfer_element = 0x[hex]

Explanation    An internal logic error occurred. An offload message header crossed a buffer boundary. The CIP ignored the request.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %OFFL-3-ILLEN: Illegal byte count in offload data. [dec] specified, [dec] available. xfer_element = 0x[hex]

Explanation    An internal logic error occurred. The buffer length field in the offload message header does not equal the size of the data buffer. The CIP assumes the offload message header contains no data.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %OFFL-0-ILLFREE1: SCB chain does not end with a read hdr.

Explanation    An internal logic error occurred. An attempt was made to free a sequence of buffers. The attempt failed.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %OFFL-0-ILLFREE2: SCB ends with a read hdr with the MTC bit set.

Explanation    An internal logic error occurred. An attempt was made to free a sequence of buffers. The attempt failed.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %OFFL-0-ILLINTF: Illegal number of offload interfaces. [dec] specified, [dec] expected.

Explanation    The offload initialization code found an internal error.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %OFFL-3-ILLRST: Received restart with [dec] intf, [dec] is max. xfer_element = 0x[hex]

Explanation    The host sent an offload restart request with too many defined interfaces. The CIP ignored the request.

Recommended Action    Check your host configuration for this offload device. Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %OFFL-6-LONGREC: Attempt to transmit too large a record.

Explanation    The amount of data read by the channel exceeded the size of the read channel command word (CCW).

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %OFFL-3-MISRST: Received restart [chars] with unknown IP [dec].[dec].[dec].[dec]

Explanation    The host sent an offload restart request with an unknown IP address for the application programming interface (API) link.

Recommended Action    The CIP ignored the mismatch. Correct your host configuration for this offload device.

Error Message    %OFFL-6-MSGLEFT: Type [dec] xfer_element in work queue after shutdown.

Explanation    An internal logic error occurred. The offload application received a message after a shutdown. The message was ignored.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %OFFL-0-NOMBUF: Out of mbuf's for handling socket operations.

Explanation    An internal logic error occurred. Not enough memory buffers were allocated to handle the current offload socket operation.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %OFFL-3-NOMEM: Not enough memory to start offload tasks.

Explanation    Not enough free memory is available to start the TCP/IP offload tasks. The configuration request was ignored.

Recommended Action    Install more memory for the CIP, or configure fewer devices.

Error Message    %OFFL-0-NOPEND: Trying to free buffer when no send is pending. Operation: [dec]

Explanation    A request to free a send buffer was made even though no send is pending. This is an internal logic error.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %OFFL-6-NOTXBUF: Unable to allocate txbuf.

Explanation    No transmit buffers are available for sending a RESTART response.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %OFFL-3-PENDREQ: Pending request [hex] deleted due to new request [hex].

Explanation    An internal logic error occurred. The offload application had to save a socket request for later execution while another request of the same type was pending. The first request was dropped.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %OFFL-3-REJSOCK: Not enough memory to handle new socket. [dec] sockets open.

Explanation    Not enough free memory is available to open another socket. The socket request failed.

Recommended Action    Install more memory for the CIP, configure fewer devices, or limit the number of sessions through this offload device.

Error Message    %OFFL-3-REQFORM: Socket request [dec] uses invalid parameters. Offset [dec]: [hex].

Explanation    The host sent a socket request with an invalid parameter. The CIP sent an error message in response to this request.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %OFFL-3-REQLEN: Socket request [dec] has wrong length [dec].

Explanation    The host sent a socket request with an incorrect length. The CIP sent an error message in response to this request.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %OFFL-3-REQTYPE: Unknown [chars] socket request code [dec].

Explanation    The host sent a socket request with an unknown type.

Recommended Action    The CIP ignored the request. Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %OFFL-6-SOCREQ: Unrecognized socket request code [dec].

Explanation    The host sent a socket request with an invalid code.

Recommended Action    The CIP ignored the request. Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %OFFL-6-UNEXP: Unexpected Offload command code [dec].

Explanation    An internal logic error occurred. The request type in the offload message was valid but unexpected. The CIP ignored the request.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %OFFL-6-VIRTOFFL: Offload device may not be created on a virtual port adapter.

Explanation    An attempt was made to configure an offload device on the virtual port adapter. Offload devices are permitted on physical port adapters only.

Recommended Action    The configuration request was ignored. No action is required.

Error Message    %OFFL-6-WRCHAIN: Received too long message, xfer_element 0x[hex] chains to 0x[hex].

Explanation    The offload application received a message that consisted of more than one transfer element (xfer_element). This is not currently supported.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %OFFL-0-WRONGFREE: Trying to free mbuf out of sequence.

Explanation    An internal logic error occurred. An unexpected address was specified in a request to free a buffer

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %OFFL-3-WRONGLINK: Trying to send mbuf on CLAW control link.

Explanation    An internal logic error occurred. An attempt was detected to send a packet in a memory buffer on Common Link Access for Workstations (CLAW) link 0. The packet was ignored.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

CIP-SCB Error Message

CIP error message related to the storage control block.

Error Message    %SCB-6-BADSCB: Request to free SCB 0 ignored

Explanation    An attempt was made to free storage control block (SCB) 0. This is an internal logic error. The request was ignored.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

CIP-SCHED Error Messages

Error messages related to the scheduler, the facility responsible for determining which process to run at a given time on the CIP

Error Message    %SCHED-0-BADPRIORITY: Task priority of [dec] is not allowed.

Explanation    A request was made to create a process, but the priority for the process was not valid. The process was not created.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %SCHED-0-INVLOCK1: Invalied lock word of [dec] used in lock request.

Explanation    An attempt was made to request a lock, but the lock word contained invalid data. This is a fatal internal logic error.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %SCHED-0-INVLOCK2: Invalied lock word of [dec] used in unlock request.

Explanation    An attempt was made to unlock a lock, but the data in the lock word was not valid. This is a fatal internal logic error.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %SCHED-0-NMLDATA: tcb_addr = 0x[hex] current_tcb = 0x[hex] lock_value = [dec]

Explanation    This message contains data that relates to the "SCHED-0-NOTMYLOCK" message.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %SCHED-0-NOLOCK: Attempt was made to unlock resource that wasn't locked.

Explanation    An attempt was made to unlock a lock that was not held. This is a fatal internal logic error.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %SCHED-0-NOPROCID: No process id available for task creation.

Explanation    An attempt was made to create more tasks than the CIP is designed to allow. The task was not created.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %SCHED-0-NOSTACK: Could not allocate [dec] bytes for stack from SRAM.

Explanation    An attempt was made to create a process, but not enough storage was available to contain the stack for the process. The process was not created.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %SCHED-0-NOTCB: Could not allocate [dec] bytes for tcb from SRAM.

Explanation    An attempt was made to create a process, but not enough storage was available to contain the control block for the process. The process was not created.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %SCHED-0-NOTMYLOCK: Attempt was made to unlock another task's resource.

Explanation    An attempt was made to unlock a lock that was set by another task. This is a fatal internal logic error.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %SCHED-0-NOTPROCES: Attempt was made to lock while not at process level.

Explanation    An attempt was made to lock while not at process level. This is a fatal internal logic error.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

CIP-SLC Error Messages

CIP error messages related to the serial link controller

Error Message    %SLC-3-PCANMIRESET: Reset of Port [dec] NMI failed

Explanation    After a nonmaskable interrupt from a Parallel Channel Adapter (PCA) interface was serviced, an attempt to reset the interrupt failed.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %SLC-3-SCANEP1: Scan of EP ring 1 failed

Explanation    An attempt to scan the first set of internal latches on the Enterprise System Connection (ESCON) processor failed.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %SLC-3-SCANEP2: Scan of EP ring 2 failed

Explanation    An attempt to scan the second set of internal latches on the Enterprise System Connection (ESCON) processor failed.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %SLC-3-SCANSLC: Scan of SLC ring failed

Explanation    An attempt to scan the internal latches of the serial link controller failed.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %SLC-3-STOPBIDITO: Stop BIDI clock timed out

Explanation    An attempt was made to stop the clock on the interface between the Enterprise Systems Connection (ESCON) processor and the serial link controller. The serial link controller did not indicate that the clock was stopped.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %SLC-3-STOPEPTO: Stop EP clock timed out

Explanation    An attempt was made to stop the clock on the Enterprise System Connection (ESCON) processor. The serial link controller did not indicate that the clock was stopped. The CIP attempted to stop the bidirectional bus (BIDI) clock.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

CIP-SSI802 Error Messages

CIP SSI802 error messages related to the common service System Service Interface (SSI) facility

Error Message    %SSI802-6-DUMP: [chars]

Explanation    The dump utility displayed this message to indicate the hexadecimal location of the storage dump.

Recommended Action    This is an informational message. No action is required.

Error Message    %SSI802-3-FATAL_ERROR: SSI_ASSERT failure in [chars] @ [int] - [chars]

Explanation    The CIP Systems Network Architecture (CSNA) encountered unrecoverable error conditions that prevented it from continuing its normal operations.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %SSI802-3-RTN_ADR: Return Address: 0x[hex]

Explanation    This is a debug feature to show the return address when an ASSERT is used in an inline function. It contains extended data related to the subsequent failure message and information dump.

Recommended Action    Report the contents of this message, along with the information provided by the subsequent error message, to your technical support representative.

CIP-SUBSYS Error Messages

Software subsystem error messages

Error Message    %SUBSYS-2-BADCLASS: Bad subsystem clas ([dec]) - ignoring subsystem

Explanation    A software consistency check failed.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %SUBSYS-2-BADSEQUENCE: Subsystem ([chars]) has cross-class sequence for ([chars])

Explanation    A software consistency check failed.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %SUBSYS-2-BADVERSION: Bad subsystem version number ([dec]) - ignoring subsystem

Explanation    A software consistency check failed.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %SUBSYS-2-MAXRECUR: Too many levels of recursion

Explanation    A software consistency check failed.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %SUBSYS-2-MISMATCH: Kernel and subsystem version differ ([dec].[dec]) - ignoring subsystem

Explanation    A software consistency check failed.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %SUBSYS-2-NOTFOUND: Subsystem ([chars]) needs subsystem ([chars]) to start

Explanation    A software consistency check failed.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

CIP-SYS Error Messages

CIP operating system error messages

Error Message    %SYS-3-BADBLOCK: Bad block pointer [hex]

Explanation    At the indicated location, a block of memory is corrupt.

Recommended Action    If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.

Error Message    %SYS-3-BADFREEMAGIC: Corrupt free block at [hex] (magic [hex])

Explanation    A block of memory is corrupt at the indicated location.

Recommended Action    If this message recurs, copy it exactly as it appears and report it to your technical support representative.

Error Message    %SYS-3-BADFREEPTRS: Bad [chars] pointer [hex] at [hex] ([chars] = [hex])

Explanation    A pointer in the block header at the indicated location is corrupt.

Recommended Action    If this message recurs, copy it exactly as it appears and report it to your technical support representative.

Error Message    %SYS-3-BADMAGIC: Corrupt block at [hex] (magic [hex])

Explanation    The free memory pool is corrupted.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %SYS-2-BADSHARE: Bad refcount in [chars], ptr=[hex], count=[hex]

Explanation    An internal software error occurred.

Recommended Action    If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.

Error Message    %SYS-6-BLKINFO: [chars]blk [hex], words [int], alloc [hex], [chars], dealloc [hex], rfcnt [hex]

Explanation    An internal software error occurred.

Recommended Action    If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.

Error Message    %SYS-2-FREEBAD: Attempted to free memory at [hex], not part of buffer pool

Explanation    An internal software error occurred.

Recommended Action    If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.

Error Message    %SYS-2-FREEFREE: Attempted to free unassigned memory at [hex], alloc [hex], dealloc [hex]

Explanation    An internal software error occurred.

Recommended Action    If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.

Error Message    %SYS-3-INUSEFREE: Block [hex] on free list [dec] in use

Explanation    An internal software error has occurred.

Recommended Action    If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.

Error Message    %SYS-3-INVMEMINT: Invalid memory action ([chars]) at interrupt level

Explanation    A memory allocation or deallocation was attempted from an interrupt handler.

Recommended Action    If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.

Error Message    %SYS-2-LOWMEM: Low memory debug exception (limit=[int] free=[int])

Explanation    The CIP is running short on memory.

Recommended Action    You might need to free some memory by quitting a program. If this message recurs, copy it exactly as it appears and report it to your technical support representative.

Error Message    %SYS-2-MEMTOOSMALL: CIP software requires a minimum of 8MB of DRAM

Explanation    The CIP software has become so large that 2 MB of dynamic RAM (DRAM) is insufficient. The CIP software will not run.

Recommended Action    Contact your technical support representative. Free 8-MB upgrades are available.

Error Message    %SYS-6-MTRACE: [chars]: addr, pc\n ADDRPC ADDRPC ADDRPC ADDRPC \n ADDRPC ADDRPC ADDRPC ADDRPC

Explanation    The free memory pool is corrupted.

Recommended Action    If this message occurs again, copy it exactly as it appears and report it to your technical support representative.

Error Message    %SYS-2-NOMEMFRG: Memory fragmentation check debug exception (fragment size [int])

Explanation    The system detected an error-checking memory fragmentation.

Recommended Action    If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.

Error Message    %SYS-2-NOMEMORY: No memory available for [chars] [dec]

Explanation    An operation could not be accomplished because of a low memory condition.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message    %SYS-3-NZREFCNT: Block [hex] on free list [dec] with ref count [dec]

Explanation    A block of memory in the free pool is in use. The number of processes using the memory block is indicated.

Recommended Action    If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.

Error Message    %SYS-3-OVERRUN: Block overrun at [hex] (redzone [hex])

Explanation    An internal software error occurred.

Recommended Action    If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.

Error Message    %SYS-5-RELOAD: Reload requested

Explanation    A reload or restart was requested.

Recommended Action    Informational message. No action is required.

Error Message    %SYS-5-RESTART: System restarted --\n[chars]

Explanation    A reload or restart was requested.

Recommended Action    Informational message. No action is required.

Error Message    %SYS-3-WRONGFREELIST: Block [hex], size [dec], on wrong free list ([dec], [dec])

Explanation    A freed buffer has been placed on the wrong list of free buffers.

Recommended Action    If this message recurs, copy it exactly as it appears and report it to your technical support representative.

CIP-SYSMGT Error Messages

CIP error messages related to network management processing for system management remote procedure calls

Error Message    %SYSMGT_RPC-3-ERROR: Error detected ([chars])

Explanation    An error was detected in the systems management remote procedure call processing.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %SYSMGT_RPC-3-IPC_ERROR: [chars] [chars] failed ([chars])

Explanation    The system management remote procedure call operation failed. Requests for information from the CIP card will not be processed.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %SYSMGT_RPC-6-STATE_CHANGE: System Management [chars]

Explanation    The CIP system management subsystem has changed state.

Recommended Action    This is an informational message. No action is required.

CIP-TCPIP Error Message

TCP/IP CIP error message

Error Message    %TCPIP-0-PANIC: panic[[chars]@[dec]] in [chars]: [chars]

Explanation    An unexpected internal error occurred in the TCP/IP stack.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

CIP-TN3270 Error Messages

These error messages relate to the TN3270 server feature of the CIP card.

Error Message    %TN3270S-4-BAD_MAX_LUS_CFG: Could not change maximum LUs to [dec]

Explanation    The TN3270 server could not change the maximum number of logical units (LUs) to the requested value. The previous number is still in use.

Recommended Action    Review the previous error messages to discover what caused the failure. Take action based on those messages.

Error Message    %TN3270S-1-LISTENFAIL: Listening on [hex] [dec] Failed

Explanation    An attempt was made to bring up a physical unit (PU), but listening on a corresponding TCP/IP port could not be initialized.

Recommended Action    Verify that sufficient memory is available on the CIP card. If inadequate memory does not appear to be the problem, copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %TN3270S-1-NO_BIND_REQ_RCVD: No BIND REQ received on LU [chars].[dec]

Explanation    The TN3270 session did not receive a BIND REQUEST or system services control point (SSCP)-logical unit (LU) data from the host within 30 seconds of the start of the SSCP-LU session. The host should have sent one or the other. If this condition persists for another 2 minutes, the LU is declared bad. Bad dynamic LUs are not reused until all good dynamic LUs associated with the Internet Protocol (IP) listening point are in use.

Recommended Action    Examine the SSCP host VTAM console for the status of the specified PU and LU. Review the VTAM console log output for relevant events, such as the deactivation of the PU or LU. If the cause of the problem is still unknown after you review the VTAM console, copy the error message exactly as it appears, and report it to your technical support representative. A temporary workaround is to recycle the affected LU at the VTAM console to return the LU to normal circulation.

Error Message    %TN3270S-1-NO_DYN_ACTLU_REQ_RCVD: No ACTLU REQ received on LU [chars].[dec]

Explanation    The host has not sent an ACTLU (Activate LU) request within 1 minute of sending a Reply PSID (product-set identification) response. If this condition persists for another 2 minutes, the current TN3270 session will be disconnected from the logical unit (LU) and the LU will be declared bad. Bad dynamic LUs are not reused until all good dynamic LUs associated with the Internet Protocol (IP) listening point are in use.

Recommended Action    Examine the system services control point (SSCP) host Virtual Telecommunications Access Method (VTAM) console for the status of the specified PU and LU. Review the VTAM console log output for relevant events, such as a deactivation of the PU or LU. If, after the VTAM console review, the cause is still unknown, copy the error message exactly as it appears, and report it to your technical support representative. As a temporary workaround, recycle the affected LU at the VTAM console to return the LU to normal circulation.

Error Message    %TN3270S-1-NO_EVENT_BUFS: No IPC sysmgt event buffers for at least one minute

Explanation    A TN3270 server has events that result in Simple Network Management Protocol (SNMP) traps and/or Systems Network Architecture (SNA) alerts, but has not been able to allocate interprocess communication (IPC) buffer resources to report the events to the router system code. The TN3270 server will persist in attempting to report these events, but lack of buffers might continue to be a problem until the CIP microcode is reloaded.

Recommended Action    Copy the error message exactly as it appears, and copy the output from the following commands:

• show ipc status

• show ipc queue

• show ipc ports

• show ipc nodes

• show controllers cbus

• show version

Report this information to your technical support representative. As a workaround, reload the CIP microcode.

Error Message    %TN3270S-1-NO_LU_MEMORY: No memory on the CIP was available for completing a requested TN3270 LU session

Explanation    Not enough memory is available to the TN3270 server to complete one or more requests by TN3270/E clients for logical unit (LU) sessions. The sessions have been disconnected.

Recommended Action    Review the memory requirements needed to run the TN3270 server application, considering the current client load. Install additional memory, if necessary.

Error Message    %TN3270S-4-NO_LU_SESSIONS: No LU sessions left for PUs at IP addr [chars], port [dec]

Explanation    The TN3270 server cannot complete one or more connection requests from a TN3270/E client because no more logical units (LUs) are available in the generic pool associated with the specified Internet Protocol (IP) listening point address.

Recommended Action    Review the LU requirements for this application's endpoints. Configure additional physical units (PUs) to listen to the specified IP address and port number.

Error Message    %TN3270S-1-NO_NTFY_AV_RSP_RCVD: No NOTIFY(available) RSP received on LU [chars].[dec]

Explanation    The TN3270 server did not receive a response to a power-on (AVAILABLE) NOTIFY request within 30 seconds of sending it to the host. If this condition persists for another 2 minutes, the current TN3270 session connected to the logical unit (LU) will be disconnected and the LU declared bad. Bad dynamic LUs are not reused until all good dynamic LUs associated with the Internet Protocol (IP) listening point are in use.

Recommended Action    Examine the SSCP host VTAM console for the status of the specified physical unit (PU) and LU. Review VTAM console log output for relevant events, such deactivation of the PU or LU. If, after VTAM console review, the cause is still unknown, copy the error message exactly as it appears, and report it to your technical support representative. A temporary workaround is to recycle the affected LU at the VTAM console to return the LU to normal circulation.

Error Message    %TN3270S-1-NO_NTFY_UA_RSP_RCVD: No NOTIFY(UA) RSP received on LU [chars].[dec]

Explanation    The host failed to reply within 30 seconds of when the TN3270 server sent a power-off (UNAVAILABLE) NOTIFY request. If this condition persists for another
2 minutes, the current TN3270 session will be disconnected from the logical unit (LU) and the LU will be declared bad. Bad dynamic LUs are not reused until all good dynamic LUs associated with the Internet Protocol (IP) listening point are in use.

Recommended Action    Examine the system services control point (SSCP) host Virtual Telecommunications Access Method (VTAM) console for the status of the specified physical unit (PU) and LU. Review the VTAM console log output for relevant events, such as a deactivation of the PU or LU. If, after the VTAM console review, the cause is still unknown, copy the error message exactly as it appears, and report it to your technical support representative. As a temporary workaround, recycle the affected LU at the VTAM console to return the LU to normal circulation.

Error Message    %TN3270S-1-NO_PSID_RSP_RCVD: No NMVT Reply PSID received on LU [chars].[dec]

Explanation    The host failed to send a response within 1 minute of when the TN3270 server sent a Reply PSID. This fault can occur only on dynamic logical units (LUs) that have been misconfigured or deactivated at the host. If this condition persists for another
2 minutes, the current TN3270 session will be disconnected from the LU and the LU will be declared bad. Bad dynamic LUs are placed in a special area where they are not allowed to be reused until all the other generic pool LUs of the listening Internet Protocol (IP) have been exhausted.

Recommended Action    Check the status of the LU using Virtual Telecommunications Access Method (VTAM), and vary the active LU if appropriate. This action must happen within 2 minutes of the time this message appears; otherwise, the LU is placed in the bad LU area and will not be reused unless all good LUs are in use. Examine the host VTAM log for errors or problems. In particular, look for messages indicating a badly configured LUGROUP resource definition or file. Fix the configuration, and recycle the affected major nodes.

Error Message    %TN3270S-1-NO_SDT_REQ_RCVD: No SDT REQ received on LU [chars].[dec]

Explanation    The TN3270 server received a TN3270 no SDT (Start Data Traffic) request from the primary logical unit (PLU) host for the specified logical unit (LU). If this condition persists for another 2 minutes, the LU is declared bad. Bad dynamic LUs are not reused until all good dynamic LUs associated with the Internet Protocol (IP) listening point are in use.

Recommended Action    Examine the SSCP host VTAM console for the status of the specified PU and LU. Review the VTAM console log output for relevant events, such as the deactivation of the PU or LU. If the cause of the problem is still unknown after you review the VTAM console, copy the error message exactly as it appears, and report it to your technical support representative. A temporary workaround is to recycle the affected LU at the VTAM console to return the LU to normal circulation.

Error Message    %TN3270S-1-NO_SDT_TMARK_RCVD: No SDT TIMING-MARK received on LU [chars].[dec]

Explanation    No SDT (Start Data Traffic) TIMING-MARK response was received by the TN3270 server from the TN3270 client software for the specified TN3270 session. If this condition persists for another 2 minutes, the logical unit (LU) is declared bad. Bad dynamic LUs are not reused until all good dynamic LUs associated with the Internet Protocol (IP) listening point are in use.

Recommended Action    Some TN3270 clients may not fully handle the TN3270 Requests for Comments (RFCs). Enable the client-side trace to discover where the client is failing. Replace the failing client software with software from the list of TN3270 software types known to work with the TN3270 server. If you have any questions about which software to use, or if the problem persists, copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %TN3270S-1-NO_UNBIND_RSP_RCVD: No UNBIND RSP received on LU [chars].[dec]

Explanation    The host failed to reply within 30 seconds of when the TN3270 server sent an UNBIND request. If this condition persists for another 2 minutes, the current TN3270 session will be disconnected from the logical unit (LU) and the LU declared bad. Bad dynamic LUs are not reused until all good dynamic LUs associated with the Internet Protocol (IP) listening point are in use.

Recommended Action    Examine the system services control point (SSCP) host Virtual Telecommunications Access Method (VTAM) console for the status of the specified PU and LU. Review the VTAM console log output for relevant events, such as a deactivation of the PU or LU. If, after the VTAM console review, the cause is still unknown, copy the error message exactly as it appears, and report it to your technical support representative. As a temporary workaround, recycle the affected LU at the VTAM console to return the LU to normal circulation.

Error Message    %TN3270S-1-NO_UNBIND_TMARK_RCVD: No UNBIND-time TIMING-MARK received from client for LU [chars].[dec]

Explanation    No UNBIND TIMING-MARK response was received by the TN3270 server from the TN3270 client software for the specified TN3270 session. If the condition persists for another 2 minutes, the logical unit (LU) is declared bad. Bad dynamic LUs are not reused until all good dynamic LUs associated with the Internet Protocol (IP) listening point are in use.

Recommended Action    Some TN3270 clients may not fully handle the TN3270 Requests For Comments (RFCs). Enable the client-side trace to determine where the client is failing. Replace the failing client software with software from the list of TN3270 software types that are known to work with the TN3270 server. If you are uncertain about which software to use, or if the problem persists, copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %TN3270S-1-RP_PU_CONFLICT: RP & CIP hold conflicting PU name([chars]) or index(%ld)

Explanation    The Route Processor (RP) requested an update or delete action on a physical unit (PU) resource reported as stale or incorrect by the CIP TN3270 server.

Recommended Action    Reload the CIP microcode. If the problem occurs again, copy the error message exactly as it appears. Run and record the output from the following commands on each CIP in the router before reloading the CIP microcode:

• show extended chan slot/2 tn3270

• show controllers cbus

• show running-config

Report this information to your technical support representative.

Error Message    %TN3270S-1-START_FAIL: Failed to start Tn3270-server

Explanation    The TN3270 server failed to start correctly and is not now running. The immediately preceding error messages indicate the cause of the failure.

Recommended Action    Review the previous error messages to discover what caused the start failure. Take action based on those messages.

Error Message    %TN3270S-6-START_OK: Starting Tn3270-server

Explanation    This is an informational message. The TN3270 server subsystem is now operating.

Recommended Action    No action is required.

Error Message    %TN3270S-6-STOPPING: Stopping Tn3270-server

Explanation    The TN3270 server subsystem is shut down. This is an informational message.

Recommended Action    No action is required.

Error Message    %TN3270S-0-TELNETINITFAIL: Initialization of TN3270 server Failed

Explanation    Initialization of the TN3270 server Telnet component failed, probably because of inadequate memory on the CIP card

Recommended Action    Check the CIP card memory. If inadequate memory does not appear to be the problem, copy this error message exactly as it appears, and report it to your technical support representative.