Table Of Contents
Channel Port Adapter Microcode Release Note and Microcode Upgrade Requirements
Introduction
Cisco IOS Software and Cisco 7200 Family Hardware Documentation
How Does CPA Microcode Ship?
CPA Microcode Release xcpa27 Caveats
Caveats for Version 27.8/Version 27.9 Modifications
Caveats for Version 27.7/Version 27.8 Modifications
Caveats for Version 27.6/Version 27.7 Modifications
Caveats for Version 27.5/Version 27.6 Modifications
Caveats for Version 27.4/Version 27.5 Modifications
Caveats for Version 27.3/Version 27.4 Modifications
Caveats for Version 27.2/Version 27.3 Modifications
Caveats for Version 27.1/Version 27.2 Modifications
Caveats for Version 27.0/Version 27.1 Modifications
CPA Microcode Release xcpa26 Caveats
Caveats for Version 26.14/Version 26.15 Modifications
Caveats for Version 26.13/Version 26.14 Modifications
Caveats for Version 26.12/Version 26.13 Modifications
Caveats for Version 26.11/Version 26.12 Modifications
Caveats for Version 26.10/Version 26.11 Modifications
Caveats for Version 26.9/Version 26.10 Modifications
Caveats for Version 26.8/Version 26.9 Modifications
Caveats for Version 26.7/Version 26.8 Modifications
Caveats for Version 26.5/Version 26.7 Modifications
Caveats for Version 26.4/Version 26.5 Modifications
Caveats for Version 26.2/Version 26.4 Modifications
Caveats for Version 26.1/Version 26.2 Modifications
Caveats for Version 26.0/Version 26.1 Modifications
CPA Microcode/Cisco IOS Software Compatibility Matrix
CPA-Related Caveats for Cisco IOS Releases
CPA and Processor Module ROM Monitor Recommendations
CPA and Cisco 7200 DRAM Requirements
CPA Microcode Upgrade Overview
Upgrading from CCO
Cisco Connection Online
Documentation CD-ROM
Channel Port Adapter Microcode Release Note and Microcode Upgrade Requirements
July 24, 2000
This document contains the release notes for the Channel Port Adapter (CPA) microcode software. The CPA includes the Enterprise Systems Connection (ESCON) CPA and the Parallel CPA. The ESCON CPA (ECPA) and Parallel CPA (PCPA) are additions to the Cisco Mainframe Channel Connection (CMCC) family of adapters, which also includes the Channel Interface Processor (CIP) and CIP2. The CPA microcode runs on both the ECPA and the PCPA.
Note 
In this document, references to CPA correspond to both the ECPA and PCPA.
The CPA microcode is unbundled from the Cisco IOS software. Therefore, you can obtain the CPA microcode as a separately loadable software module and match a version of the CPA microcode to the Cisco IOS software. Refer to the section "CPA Microcode/Cisco IOS Software Compatibility Matrix" for more information.
Cisco IOS Release 11.3(3)T and later supports the ECPA. Cisco IOS Release 11.3(7)T and later and Release 12.0(1) and later support the PCPA. There is a default setting in the Cisco IOS software that corresponds to a particular microcode that is already loaded on the router Flash memory card or on the SanDisk memory device when a CPA is purchased as a system. Refer to the section "CPA Microcode/Cisco IOS Software Compatibility Matrix" for more information. However, when the CPA is ordered as a spare (shipped separately from a system), you might be required to download the microcode image from Cisco Connection Online (CCO).
Note We recommend that you load and use the version of CPA microcode that corresponds with your Cisco IOS software, in which case the following step is not necessary.
If you choose to use a version of the CPA microcode other than the one that corresponds with your Cisco IOS software, you must copy a CPA microcode image onto the router Flash memory card or SanDisk memory device and use the microcode router configuration command to specify this microcode image rather than the default microcode image.
For general information on CPA microcode, refer to the PA-1C-E ESCON Channel Port Adapter Installation and Configuration document or the PA-1C-P Parallel Channel Port Adapter Installation and Configuration document that shipped with the port adapter.
Introduction
This release note describes the CPA microcode caveats for the latest version of CPA microcode. It includes the CPA microcode releases described in the "CPA Microcode Release xcpa26 Caveats" section. Also included is an overview of the procedures required to upgrade to the latest versions of CPA microcode.
This CPA microcode release note discusses the following topics:
•Cisco IOS Software and Cisco 7200 Family Hardware Documentation
•How Does CPA Microcode Ship?
•CPA Microcode Release xcpa27 Caveats
•CPA Microcode Release xcpa26 Caveats
•CPA Microcode/Cisco IOS Software Compatibility Matrix
•CPA-Related Caveats for Cisco IOS Releases
•CPA and Processor Module ROM Monitor Recommendations
•CPA and Cisco 7200 DRAM Requirements
•CPA Microcode Upgrade Overview
•Cisco Connection Online
•Documentation CD-ROM
Cisco IOS Software and Cisco 7200 Family Hardware Documentation
For documentation of CPA features in the Cisco IOS Release 11.3, refer to .
Table 1 Cisco IOS Release 11.3 Publications
Cisco IOS 11.3 Release Publication
|
Tracking Number
|
Configuration Fundamentals Configuration Guide
|
DOC-CFCG11.3=
|
Configuration Fundamentals Command Reference
|
DOC-CFCR11.3=
|
Bridging and IBM Networking Configuration Guide
|
DOC-IBMNCG11.3=
|
Bridging and IBM Networking Command Reference
|
DOC-IBMNCR11.3=
|
Cisco IOS Software Command Summary
|
DOC-CIOSCS11.3=
|
System Error Messages
|
DOC-SYSEM11.3=
|
Release Notes for Cisco IOS Release 11.3
|
78-4998-xx
|
For documentation of CPA features in the Cisco IOS Release 11.3T, refer to .
Table 2 Cisco IOS Release 11.3T Publications
Cisco IOS Release 11.3T Publication
|
Tracking Number
|
Release Notes for Cisco IOS Release 11.3
|
78-4998-xx
|
Release Notes for Cisco 7000 Family for Cisco IOS Release 11.3T
|
78-5015-xx
|
Cisco IOS Release 11.3T New Features
|
Available on CCO only
|
For documentation of CPA features in the Cisco IOS Release 12.0, refer to .
Table 3 Cisco IOS Release 12.0 Publications
Cisco IOS Release 12.0 Publication
|
Tracking Number
|
Configuration Fundamentals Configuration Guide
|
DOC-785829=
|
Configuration Fundamentals Command Reference
|
DOC-785830=
|
Bridging and IBM Networking Configuration Guide
|
DOC-785850=
|
Bridging and IBM Networking Command Reference
|
DOC-785851=
|
Cisco IOS Software Command Summary
|
DOC-785859=
|
Cisco IOS Software System Error Messages
|
DOC-785860=
|
Debug Command Reference
|
DOC-785858=
|
Release Notes for Cisco IOS Release 12.0
|
78-6035-xx
|
For documentation of CPA features in the Cisco IOS Release 12.0T, refer to .
Table 4 Cisco IOS Release 12.0T Publications
Cisco IOS Release 12.0T Publication
|
Tracking Number
|
Release Notes for Cisco IOS Release 12.0
|
78-6035-xx
|
Release Notes for Cisco 7000 Family for Cisco IOS Release 12.0T
|
78-6055-xx
|
Cisco IOS Release 12.0T New Features
|
Available on CCO only
|
For documentation of CPA features in the Cisco IOS Release 12.1, refer to .
Table 5 Cisco IOS Release 12.1 Publication
Cisco IOS Release 12.1 Publication
|
Tracking Number
|
Cisco IOS Configuration Fundamentals Configuration Guide
|
DOC-7810222=
|
Cisco IOS Configuration Fundamentals Command Reference
|
DOC-7810223=
|
Cisco IOS Bridging and IBM Networking Configuration Guide
|
DOC-7810256=
|
Cisco IOS Bridging and IBM Networking Command Reference, Volume I
|
DOC-7810257=
|
Cisco IOS Bridging and IBM Networking Command Reference, Volume II
|
DOC-7810520=
|
Cisco IOS Command Summary
|
DOC-7810262=
|
Cisco IOS System Error Messages
|
DOC-7810263=
|
Cisco IOS Debug Command Reference
|
DOC-7810264=
|
Release Notes for Cisco IOS Release 12.1
|
78-10724-xx
|
For documentation of CPA features in the Cisco IOS Release 12.1T, refer to .
Table 6
Cisco IOS Release 12.1T Publication
|
Tracking Number
|
Release Notes for Cisco IOS Release 12.1
|
78-10724-xx
|
Release Notes for Cisco 7000 Family for Cisco IOS Release 12.1T
|
78-10811-xx
|
Cisco IOS Release 12.1T New Features
|
Available on CCO only
|
Cisco IOS Release 12.1T Publications
For hardware installation and configuration information on the CPA, refer to the PA-1C-E ESCON Channel Port Adapter Installation and Configuration document and the PA-1C-P Parallel Channel Port Adapter Installation and Configuration document that shipped with the port adapter.
To obtain general information about documentation, refer to the section "Cisco Connection Online" or call customer service at 800 553-6387 or 408 526-7208. Customer service hours are 5:00 a.m. to 6:00 p.m. Pacific time, Monday through Friday (excluding Cisco-observed holidays). You can also send e-mail to cs-rep@cisco.com, or you can refer to the Cisco Information Packet that shipped with your router.
How Does CPA Microcode Ship?
In Cisco IOS Release 11.3(3)T and later, the CPA microcode is available from the following sources:
•Electronic download from CCO using File Transfer Protocol (FTP) for all Cisco 7200-series routers
•Pre-installed on a Flash memory card or SanDisk memory device with Cisco IOS software
CPA Microcode Release xcpa27 Caveats
The following section describes the caveats to current CPA microcode versions and the modifications made in current CPA microcode versions for xcpa27 microcode. The caveats listed apply to only the most serious problems. See for the Cisco IOS software releases supported by xcpa27 microcode.
Caveats for Version 27.8/Version 27.9 Modifications
This section describes possible unexpected behavior by Version 27.8. All the caveats listed in this section are resolved in Version 27.9. See for the Cisco IOS software release that corresponds to the 27.9 microcode version.
•The TN3270 server disconnects the session. This occurs when a client connects to a dynamic LU that has received a DACTLU message. The TN3270 server requests an ACTLU response and starts a two-minute timer. A timer value of this length is invalid because the LU has been deactivated by the VTAM console operators. The TN3270 server does not receive the ACTLU response within the timer period and disconnects the session.
The workaround is to configure the TN3270 server to assign a different LU. [CSCdk30136]
•Users are unable to start new CMCC sessions. The results of a show extended channel x/2 tn command show that some PUs are in an ACT/Busy state. The results of a VTAM display of the PU show that the PU is in an active state.
The workaround is to reload the microcode. [CSCdm44279]
•When a parallel link that connects a Cisco TN3270 server to another server and carries the control point-to-control point sessions goes down, the Cisco TN3270 server cannot establish a control point-to-control point session with any server.
The workaround is to define alternate links to the same VTAM host only at the host end, or avoid multiple links to the same VTAM host. [CSCdp02702]
•The CMCC adapter fails with a fatal error message number 9.
CIP2-3-MSG: slot0 %SSI802-3-FATAL_ERROR: SSI_ASSERT failure in ../ssi/ssi_buff.c @ 1035
- msgP->m_next
Jan 31 15:40:12: %CIP2-0-MSG: slot0 %DEBUGGER-0-FATAL_ERROR: Fatal error (code=09)
There is no workaround. [CSCdp84989]
•VTAM issues a V NET,INACT,TYPE=GIVEBACK message. The control point-to-control point session moves to the other DLUS, but the DLUR pipe stops and restarts on the same host.
There is no workaround. [CSCdr28173]
•The last logical PU in an IP pool of listen points is placed into the WAIT state. This problem occurs when changing the TCP-port while PUs are in an ACTIVE state.
The workaround is to shutdown and restart the TN3270 server using the shutdown command. [CSCdr30174]
•TN3270 server LUs can not be used. This problem occurs when the TN3270 server does not clear the indication that LUs were nailed during processing and delete the nailing definition.
The workaround is to avoid manipulating nailing definitions without issuing the microcode reload command. [CSCdr32205]
•The TN3270 server inconsistently names the TN3270E clients. Sometimes the name is a fully-qualified APPN name such as NETA.BTEST001. At other times the name is the local LU name, such as BTEST001.
There is no workaround. [CSCdr38323]
•The TN3270 server uses an incorrect default value of 30 minutes for the max response time for the keepalive timer. This problem occurs if the keepalive command is configured without specifying any values for the nop or timing-mark or max-response-time parameters.
The workaround is to configure the nop or timing-mark parameters. [CSCdr59806]
Caveats for Version 27.7/Version 27.8 Modifications
This section describes possible unexpected behavior by Version 27.7. All the caveats listed in this section are resolved in Version 27.8. See for the Cisco IOS software release that corresponds to the 27.8 microcode version.
•The TN3270 server loses pool-based LU nailing information. This problem occurs when the no shutdown command is configured multiple times on the same PU.
The workaround for customers who are using pool-based LU nailing is to avoid configuring the no shut command multiple times on the same PU. [CSCdm24372]
•A user receives another user's session when both users are logged into the same applications owning region (AOR) in the Customer Information Control System and that AOR is manually cancelled.
The workaround is to not disconnect a client during the logon process; that is, after requesting an application from the SSCP screen, but before establishing the LU-LU session with that application. [CSCdm51110]
•The following message appears on the CMCC console:
bad error-code 12 given
This valid error code indicates a missing TERMSELF response. The code to log and format this specific error into a console message is missing.
There is no workaround. [CSCdm55961]
•The CMCC adapter fails with error message number 32. This problem occurs when the TN3270 server is configured and is using, or has used, the TN3270 monitor or a similar product.
The workaround is to not configure the TN3270 monitor or a similar product. [CSCdp16086]
•The CMCC adapter fails with fatal error message number 35. This problem occurs when the no client ip ipaddr [ipmask] pool poolname command is configured when using LU pooling. The command configuration causes memory corruption and the CMCC failure. The failure usually occurs because the TN3270 server attempts to access ODD addresses when EVEN addresses are expected.
There is no workaround. [CSCdp18803]
•The TN3270 server disconnects a TCP session after sending an "in use" message. This problem occurs when OpenConnect clients are configured to negotiate multiple LU names by using a device list used by the client.
The workaround is to configure the OpenConnect client to use a single device name. [CSCdp24684]
•The TN3270 server show pu command output is missing LU states. The missing states are displayed as P-RESET. This applies also to the LU state objects in the TN3270 server MIB.
There is no workaround. [CSCdp51038]
•The CMCC adapter fails with fatal error message number 32. This problem occurs when approximately 25 or more DLUR links are configured. The reply buffer is too small to contain all of the Cross Domain Init vectors and the positive locate reply.
The workaround is to configure fewer DLUR links. [CSCdp79125]
•The CMCC adapter may fail when the shutdown command is configured in TN3270 sub-mode.
There is no workaround. [CSCdp99538]
•The CMCC adapter configured for CSNA may not respond to a test poll. This problem occurs because there is a miscount of the available IBM VTAM External Communications Adapter (XCA) resources. Typically an XCA autogen parameter is configured to automatically generate lines and PUs. This is not required for PU5-to-PU4 or PU5-to-PU5 communications.
The workaround is to recycle the XCA major node. [CSCdr03103]
•The TN3270 Server running on TPF returns the following error message:
This problem occurs when the client establishes a connection to the server, issues a request, gets the response and then closes the connection by sending a RST (reset) segment.
The server issues a read to the connection, the read message is blocked and returns with the error message. The read message should return with a 0 message, meaning that the connection was closed. This problem happens after one minute.
There is no workaround. [CSCdr05011]
•The LU number in the show extended channel tn3270-server command output decreases every time a client fails to telnet. Once the LU number reaches zero, clients cannot telnet to the TN3270 server although LUs are available.
There is no workaround. [CSCdr09662]
•Unless the Definite Response option is set in the request/response unit (RU) from the host, nothing which can measure IP response time is sent to the client. This problem applies to response times obtained from the TN3270E-RT-MIB, or by using the TN3270 server show commands.
The workaround is to use only Definite Response flows. [CSCdr10939]
•The TN3270 server allows a client to access LUs which are nailed to another subnet.
There is no workaround. [CSCdr12567]
•The CMCC adapter fails with the following error message:
%ECPA-4-MSG: slotx %TN3270S-4-NO_LU_SESSIONS
: No LU sessions left in :GENERIC for PUs at IP addr xxx.xxx.xxx.xxx, port 23
The TN3270 server PU output displays skipped LUs. The TN3270 server does not select these LUs. All other LUs are set to ACT/SESS. Note that there is no LU display for lu4 and lu9.
lu name client-ip:tcp nail state model frames in out idle for
1 ABCD2001 xxx.xxx.xxx.x:1042 N ACT/SESS 3278S5E 38418 19615 0:6:6
2 ABCD2002 xxx.xxx.xxx.xxx:1043 N ACT/SESS 3278S2E 21473 14085 0:18:11
3 ABCD2003 xxx.xxx.xxx.xx:1665 N ACT/SESS 3278S5E 9992 6147 0:0:6
5 ABCD2005 xxx.xxx.xxx.x:1046 N ACT/SESS 3278S5E 12731 8074 10:33:7
6 ABCD2006 xxx.xxx.xxx.x:4033 N ACT/SESS 3278S2E 31367 18838 2:0:51
7 ABCD2007 xxx.xxx.xxx.x:1045 N ACT/SESS 3278S5E 8184 4413 2:55:4
8 ABCD2008 xxx.xxx.xxx.xx:1323 N ACT/SESS 3278S2E 16274 7580 4:28:19
10 ABCD200A xxx.xxx.xxx.xxx:1205 N ACT/SESS 3278S2E 7752 4175 1:3:39
The workaround is to add more PUs to the TN3270 server and VTAM configuration. [CSCdr13016]
•The TN3270E client cannot connect when it specifies PAC04 as the LU. This problem occurs when a direct PU is named PAC and an LU seed is named PAC##. Incorrect LU names such as PAC001, PAC002,... PAC255 (note decimal locaddrs) are generated. The PAC04 name is not found and the connection is refused.
The workaround is for the TN3270E client to specify PAC004 instead of PAC04. [CSCdr13524]
•The CMCC adapter fails with the following fatal error message number 35:
%CTA-0-INACTIVE: PA1 CTA 7C00-50 reset after being inactive for 180 seconds
The workaround is to shutdown the CSNA subchannel before shutting down VTAM. [CSCdr13804]
•The LU-available number in the show extended channel tn3270 command output is incremented on inactive PUs when adding nailing configuration commands.
The workaround is to ignore or activate the PU to correct the lu-available number. [CSCdr17334]
•The TN3270 server improperly releases nodes which had not been deleted from the resource AVL tree. This problem occurs when the TN3270 server is restarted by configuring the shutdown and no shutdown TN3270 commands.
A workaround is to avoid restarting the TN3270 server when there is a heavy processing load. [CSCdr18250]
•The CMCC adapter fails with fatal error message number 35. This problem occurs when the no listen-point TN3270 server command is configured.
There is no workaround. [CSCdr19257]
•The CMCC adapter fails with fatal error message number 7. This problem occurs when the client disconnects after the response time group is removed from the configuration. This occurs when the response time group and the subnet are configured.
The workaround is to remove the response time group configuration. [CSCdr20842]
•When using the TN3270 server monitor or a similar product such as SOLVE:Netmaster for TCP/IP, the length of the message fragment field is reported incorrectly. The field length is reported as "18". It should be reported as "20". The message fragment field is defined as follows:
struct {short PACKED(pktLength); short PACKED(len);
unsigned char PACKED(bytes[16]);}
This is a cosmetic failure and is present in all CIP and CPA microcode releases.
There is no workaround. [CSCdr24412]
•VTAM issues a V NET,INACT,TYPE=GIVEBACK message. The control point-to-control point session moves to the other DLUS, but the DLUR pipe stops and restarts on the same host.
There is no workaround. [CSCdr28173]
Caveats for Version 27.6/Version 27.7 Modifications
This section describes possible unexpected behavior by Version 27.6. All the caveats listed in this section are resolved in Version 27.7. See for the Cisco IOS software release that corresponds to the 27.7 microcode version.
•At show ext cn/2 pu/lu, some dddlu LU names appear blank if Host applications send NULL slu data in the bind.
There is no workaround. [CSCdj90734]
•Users are unable to start new CMCC sessions. The results of a show extended channel x/2 tn command show that some PUs are in an ACT/Busy state. The results of a VTAM display of the PU show that the PU is in an active state.
The workaround is to reload the microcode. [CSCdm44279]
•A Cisco Multipath Channel (CMPC) transmission group (TG) does not activate and the following duplicate group token message occurs:
Get CMPCP_DUPL_TOKEN:
This problem occurs when bringing up a TG from the host activating a transport resource list entry (TRLE) and when multiple TGs are configured with paths to multiple mainframes via a director.
The workaround is to activate the TRLE again. [CSCdp66330]
•The CMCC adapter fails with fatal error message number 32. This problem occurs when approximately 25 or more DLUR links are configured. The reply buffer is too small to contain all of the Cross Domain Init vectors and the positive locate reply.
The workaround is to configure fewer DLUR links. [CSCdp79125]
•The CMCC adapter running CIP Offload returns the following error message:
%CIP2-4-MSG: slot0 %OFFL-4-BADDESC: 0/9300/60 Socket descriptor 259 in request is bad: state DESC_Holddown compare 259
This is a cosmetic problem that should not impact performance.
There is no workaround. [CSCdp84965]
•The CMCC adapter running CIP Offload reloads with fatal error message number 35. This problem occurs when too many Offload and CLAW statements are configured on the same interface. The process table is shared by two interfaces and can not exceed 530 processes. Each Offload uses 4 processes. Each CLAW uses 2 processes. There are about 20 to 30 processes that are always running in addition to any Offload or CLAW configurations.
The workaround is to configure fewer Offload and CLAW statements. [CSCdp85560]
•The CMCC adapter fails with fatal error message number 32. This problem occurs when changing the IP address of a loopback interface.
There is no workaround. [CSCdp85890]
•There is a 10-second delay from the time that the host application sends a SHUTDOWN message until the TN3270 server responds with the SHUTC RU message. This delay applies to printer emulators and should not apply to screen devices.
There is no workaround. [CSCdp90214]
•A CMCC adapter error occurs when host-defined LU names for one PU conflict with implicit lu-seed derived names on another PU.
The workaround is to avoid name conflicts by specifying lu-seed names on every PU in the configuration that do not overlap with the host-defined names. [CSCdr06007]
•The TN3270 Server LU goes into P-RESET mode. This problem occurs when the server closes a client connection that is using a static LU due to an inactivity or keepalive timeout. The server sends an unbind message to the host and then waits 6 seconds before sending a Notify/Unavailable message. If the same client attempts to reconnect within that time window and the System Service Control Point (SSCP) logon screen is received after the reconnect, but still within that window, the TN3270 Server locks up. This problem occurs because the accepted SSCP screen stops the timer that would normally send in the Notify/Unavailable message. Also, the SSCP logon screen will be rejected with an 0x0831 sense code.
The workaround is to reject any connect requests for that LU until the Notify/Unavailable message transmission is complete. [CSCdp66402]
•The LU termination setting is incorrect in SNA-NAU-MIB. The snaLuAdminTerm and snaLuOperTerm objects are set to unbind even if termself is configured.
There is no workaround. [CSCdp88662]
Caveats for Version 27.5/Version 27.6 Modifications
This section describes possible unexpected behavior by Version 27.5. All the caveats listed in this section are resolved in Version 27.6. See for the Cisco IOS software release that corresponds to the 27.6 microcode version.
•BADTIMER messages appear when running TN3270 Server. In this case, the messages appear because a TN3270 session is being negotiated or recently has been negotiated. The messages do not impact normal TN3270 Server operations.
There is no workaround. [CSCdk21633]
•The CMCC Adapter fails with error message 37. The following error messages appear:
%CONFIG-3-WORKLEFT:Work pending on work queue when device terminated
%DEBUGGER-0-FATAL_ERROR:Fatal error (code=37)
There is no workaround. [CSCp54593]
•The tn-parameter code codevalue command incorporates a code value of 3. PUs configured on the TN3270 Server request activation by sending ReqACTPU (DLUR PUs) or TEST/XID (Direct PUs) messages to the host. When the TN3270 Server and its PUs are in backup or standby mode, the PUs should not request activation. The PUs must wait to be activated by the host.
To enable this passive activation, enter the tn-parameter code codevalue command with a code value of 3. This command tells the Server to put all PUs in a waiting state and not to send ReqACTPU or TEST/XID messages to the host. [CSCdm80770]
•In duplicate MAC environments, idle Systems Application Architecture (SAA) gateway sessions terminate. SAA gateways time out the route to the CMCC MAC address and send receive ready poll (RR(P)) single route explorer (SRE) messages to rediscover the route. The CMCC Adapter is not in session and responds to the RR(P) messages with a disconnect mode final (DM(F)) message. The SAA gateway then disconnects the session. The RR(P) SRE is contrary to the LLC2 specifications.
The workaround is to specify XTX=7 on the route.nlm. [CSCdp09295]
•The CMCC adapter fails with the following message:
%CIP2-3-MSG: slot0 %SSI802-3-FATAL_ERROR: SSI_ASSERT failure in ../cta802/ciptask.c @
322 - !mxcb->mx_next
%CIP2-0-MSG: slot0 %DEBUGGER-0-FATAL_ERROR: Fatal error (code=09)
The assertion is intended to detect messages with 15 or more memory buffers (mbufs). There is no workaround. [CSCdp13245]
•The CMCC Adapter fails when running CSNA. This problem occurs while processing the detection of idle subchannel conditions.
The workaround is to avoid creating idle subchannel conditions by not using the Z NET cancel command. Other possible workarounds include shutting down the router channel interface or removing the CSNA configuration statement before issuing the Z NET cancel command. [CSCdp31175]
•The CMCC Adapter deletes all the PUs associated with IP pool and fails with error message 35. This problem occurs when a listen-point PU and another non-listen-point PU are configured with the same IP address and TCP port pair and the no listen command is issued. PUs that are not configured under the listen-point are deleted.
The workaround is to not configure a listen-point PU and another PU with the same IP address and TCP port pair. [CSCdp45166]
•The CMCC Adapter fails with error message 35 when the TN3270 Server is shut down. This problem occurs when using CIP microcode version cip24-15 or later.
There is no workaround. [CSCdp58083]
•CMCC Adapter configuration errors occur when the CIP microcode is upgraded from version cip24-14 to cip24-15. The following error message occurs when attempting to delete an allocate LU pool statement:
dec 20 05:48:57 UTC: %CBUS-3-CIPCFGFAIL: Channel0/2: configuration command
TN3270S_LISTEN_POINT_PU_LU_POOL cmd 40 failed
There is no workaround. [CSCdp56576]
•When the TN3270 Server statistics are displayed, a negative LU IN USE message appears. This is a cosmetic problem. LUs are still available to the clients as needed.
There is no workaround. [CSCdp69064]
•The TN3270 Server LU Nailing feature fails in a subnetted IP address scheme. This problem occurs because the client addresses are not recognized.
The workaround is to configure the tn-parameter code codevalue command with a code value of 9. This workaround applies only if the client is capable of requesting a specific LU name. If the client does not specify an LU name, then an LU will be awarded based on the LU Nailing rules configured. [CSCdp58041]
Caveats for Version 27.4/Version 27.5 Modifications
This section describes possible unexpected behavior by Version 27.4. All the caveats listed in this section are resolved in Version 27.5. See for the Cisco IOS software release that corresponds to the 27.5 microcode version.
•BADTIMER messages appear when running TN3270 Server. In this case, the messages appear because a TN3270 session is being negotiated or recently has been negotiated. The messages do not impact normal TN3270 Server operations.
There is no workaround. [CSCdk21633]
•The TN3270 Server fails intermittently during the shutdown procedure. This failure occurs when the shutdown procedure is performed and TN3270 Server sessions are receiving client data. TheTN3270 Server shutdown procedure sequence shuts down the TCP/IP stack prematurely. The failure is intermittent depending upon the timing between receiving data from the client and the shutdown sequence.
This problem occurs in CMCC microcode releases cip22-35, cip24-10, cip25-10, cip26-5, xcpa 26-5, cip27-0, xcpa27-0, and later.
The workaround is to perform the shutdown procedure when there is no activity on the TN3270 sessions. [CSCdm35562]
•The TN3270 Server configured for a direct, non-APPN connection sets the parallel transmission group (TG) supported bit on xid3 to byte = 15(bit 0 of XID3).
This setting is incorrect for a LEN node direct connect configuration and causes connection failure problems when connecting to the SNA Switch. The SNA Switch expects the device to negotiate a TG number, but the TN3270 Server does not support this action. The TN3270 Server must either negotiate a TG number or not configure a TG-capable bit setting.
The workaround is to configure the snasw port command with the conntype len keyword specified on the SNA Switch port to which the TN3270 Server connects. The TN3270 Server will no longer set the parallel TGs supported bit during the XID exchange for direct PUs. [CSCdm71315]
•The user is unable to acquire specific LUs when using TN3270E clients. This error occurs intermittently on one of the several configured PUs. This error occurs when the customer is running direct-connect PUs (no DLUR) and does not have the INCLUD0E=YES parameter set on the switched major node. This error occurs in CIP microcode version cip210-140, but the affected PUs do not have LU pools defined.
There is no workaround. [CSCdm73361]
•Data is lost on printer emulators. This problem occurs when the user is running TN3270 Server in an environment with small (768) RU sizes and low pacing values. The printer receives the first RU of data, but intermittently fails to receive the second. The TN3270 Server received an EXPEDITED SHUTD command prior to receiving the last-in-chain RU. The shutdown process causes loss of data.
This fix adds a 10 second delay between receiving the shutdown command and responding to the shutdown command. This time window will allow any data that is in queue to transmit before the shutdown procedure.
There is no workaround. [CSCdm80945]
•CSNA devices fail with INOP messages during Interface Control Check (IFCC) status. This problem occurs when CLAW and CSNA are operating in high traffic conditions. It can occur in CMPC and CSNA, also.
The workaround is to upgrade the CMCC microcode or to restart the external communication adapter (XCA) nodes. [CSCdm88239]
•A BIND REQUEST or SSCP-LU message is expected but not received from the host within 30 seconds from the start of an SSCP-LU session for the CMCC Adapter TN3270 server session. If the condition continues for another 2 minutes, the LU is declared bad and the following error message appears:
%TN3270S-1-NO_BIND_REQ_RCVD: No BIND REQ received on LU [chars].[dec], 120*ONESEC
This error and several others are logged as priority 1 (alert) messages in error reports. The priority level of the following error messages is now priority level 3:
[CSCdm94788]
•Support is added for the TCP/IP information vector (CV64). The CV64 carries TN3270 Server clients IP address, TCP port number, and optionally the DNS name. The CV64 is sent inbound along with the NOTIFY(enable) and RSP(ACTLU) messages.
VTAM indicates whether it can receive the CV64 by setting a bit in the PU Capabilities vector (CV80) in the outbound ACTPU Request message. For DLUR PUs with all static LUs, the VTAM may not send the CV80 and the TN3270 Server will not send the CV64.
If the parameter INCLUD0E=YES is coded for this PU in the switched major node, the VTAM will send CV80 and enable the TN3270 Server to send the CV64. [CSCdp06211]
•The TN3270 Server client fails when configuring printer LUs. This problem occurs when the two LU definitions required to configure the printer are set. One LU is nailed with the client IP address and the other is nailed with the client IP address of the printer. The TN2370 Server allocates the video client to the printer LU and then neither client works. This problem occurs in CIP microcode versions cip24-10 through cip24-13 and later.
There is no workaround. [CSCdp06760]
•In duplicate MAC environments, idle Systems Application Architecture (SAA) gateway sessions terminate. SAA gateways time out the route to the CMCC MAC address and send receive ready poll (RR(P)) single route explorer (SRE) messages to rediscover the route. The CMCC Adapter is not in session and responds to the RR(P) messages with a disconnect mode final (DM(F)) message. The SAA gateway then disconnects the session. The RR(P) SRE is contrary to the LLC2 specifications.
The workaround is to specify XTX=7 on the route.nlm. [CSCdp09295]
•The TN3270 Server or TN3270E client fails when it connects to the server, but does not specify the name of an LU to be obtained. This problem occurs in CIP microcode version cip24-14 and later when a combination of DDDLU and nailed LUs are used.
The workaround is to code an lu-seed in the router on the PU, then connect to a TN3270E client configured with the correct LU name. [CSCdp09708]
•When an ICMP Host Unreachable packet is received by the TCP stack, it generates several soft errors before the error becomes permanent. The Offload select() returns readable to the soft errors. [CSCdp18373]
•The CMCC adapter with TN3270 Server configured fails with fatal error message 35. This problem occurs when attempting to clear the TN3270 configuration from the router. After entering the no tn3270-server command while in configuration mode on the virtual channel interface, the microcode reloads and all the interfaces flap. The CSNA devices are removed from the running configuration and must be reconfigured.
There is no workaround. [CSCdp24670]
•The printer emulators receive an -RSP sense 2005 message. The problem is caused by an emulator that sends data to the host after the BIND, but before the Start Data Traffic (SDT) processing is complete. This data is rejected from the host and the following -RSP sense 2005 message appears:
J+FKP4390E UNEXPECTED DATA RECEIVED.QUE.HELD.LU="LUname"
There is no workaround. [CSCdp30854]
•The CMCC Adapter fails when running CSNA. This problem occurs while processing the detection of idle subchannel conditions.
The workaround is to avoid creating idle subchannel conditions by not using the Z NET cancel command. Other possible workarounds include shutting down the router channel interface or removing the CSNA configuration statement before issuing the Z NET cancel command. [CSCdp31175]
•The CLAW control link does not establish. This problem most likely occurs on a TPF system or on an IBM TCP/IP system. The problem occurs because the timing of the Halt Subchannel message related to the Start Subchannel message is off.
The workaround is to stop and restart the CLAW driver causing the CLAW control link to synchronize again. [CSCdp32675]
•The CMCC Adapter fails with error message 35. This problem occurs when adding a second TN3270 Server PU under the DLUR and when the CMCC Adapter is offline.
There is no workaround. [CSCdp43223]
•A print server with 10 LUs fails to get 10 TNET connections with the TN3270 Server. The tenth LU client receives a FIN message from the TN3270 Server. The TN3270 Server rejects the TNET message indicating Listen Closed on the PU. Additional attempts to connect to the tenth LU fail until the LU is reactivated or another LU is disconnected. The problem only occurs when the last ACTLU static LU is obtained by a client. It is standard practice for the TN3270 Server to close the listen vector at this time; however, it should not close any connections that are being negotiated and have obtained LUs.
The workaround is to add an additional 3 LUs to the VTAM switched major node, leaving the print server to request only 10 TNET connections. [CSCdp43253]
•The CMCC Adapter calculates a set buffer address (SBA) that is above the screen size. This problem occurs when connecting a 327802 client using a 3270 datastream. This causes the connected session to hang on the MSG0 screen.
The workaround is to code the LUGROUP parameter with one of the following values: SSCPFM=USS3270 or SSCPFM=USS3270. [CSCdp46564]
•The CMCC Adapter configured for TCP/IP Offload fails with a error message 35. This problem occurs after a %MBUF-0-MFREEx2 message error. The problem occurs in rare circumstances when a socket request close() is issued on a TCP/IP server socket which has an outstanding accept() socket response on a BLOCKING socket. This problem also occurs in the same circumstances on a CMCC Adapter configured for TPF Offload.
There is no workaround. [CSCdp47885]
•The CMCC Adapter fails with error message 35. This problem occurs when the no client ip command is issued in listen point submode.
There is no workaround. [CSCdp55519]
•The TN3270 Server client does not connect when requesting a resource by name. This problem occurs because the ACTLU improperly truncates the LU name. This problem effects all DLUR configurations and direct-connect configurations when INCLUD0E is specified in the Switched Major Node definitions.
There is no workaround. [CSCdp34029]
Caveats for Version 27.3/Version 27.4 Modifications
This section describes possible unexpected behavior by Version 27.3. All the caveats listed in this section are resolved in Version 27.4. See for the Cisco IOS software release that corresponds to the 27.4 microcode version.
•OpenConnect has an informal extension to the Termtype in TN3270. When connecting through an OpenConnect TN3270 gateway, the client IP address is concatenated on the end with a percent (%) symbol.
The CMCC TN3270 Server does not use this client IP address for matching on LU nailing statements in the configuration. [CSCdj44584]
•MSG10 data from one LU might be seen on an LU already in session. This problem occurs when the TN3270 server remote MAC address resides on a different physical adapter or in a different physical machine, such as a front-end processor (FEP).
The workaround is to make sure that the RMAC TN3270 server PU resides on the same CMCC adapter as the TN3270 Server. [CSCdm01837]
•In a duplicate MAC environment, the CIP will continue to respond to a TEST command when the lines configured for the XCA are in use. This problem prevents other duplicate MAC adapters from responding to new requests.
The workaround is to configure the maximum LLC or threshold to equal the number of XCA lines configured. [CSCdm29597]
•The TN3270 Server fails intermittently during the shutdown procedure. This failure occurs when the shutdown procedure is performed and TN3270 Server sessions are receiving client data. TheTN3270 Server shutdown procedure sequence shuts down the TCP/IP stack prematurely. The failure is intermittent depending upon the timing between receiving data from the client and the shutdown sequence.
This problem occurs in CMCC microcode releases cip22-35, cip24-10, cip25-10, cip26-5, xcpa 26-5, cip27-0, xcpa27-0, and later.
The workaround is to perform the shutdown procedure when there is no activity on the TN3270 sessions. [CSCdm35562]
•The CMCC displays a RSP sense 089F0004 message when processing a REQACTPU message. The problem occurs when the VARY command is entered for DLUR PUs that have multiple PATH statements. The problem occurs because the DLUR sends a message to the DLUS containing an FQPCID value which DLUS created on an earlier acquisition of the PU. The host processes the FQPCID message as invalid.
The workaround is to remove the PATH statements. [CSCdm42103]
•Users are unable to start new CMCC sessions. The results of a show extended channel x/2 tn command show that some PUs are in an ACT/Busy state. The results of a VTAM display of the PU show that the PU is in an active state.
The workaround is to reload the microcode. [CSCdm44279]
•A user receives another user's session when both users are logged into the same applications owning region (AOR) in the Customer Information Control System and that AOR is manually cancelled.
The workaround is to not disconnect a client during the logon process; that is, after requesting an application from the SSCP screen, but before establishing the LU-LU session with that application. [CSCdm51110]
•The CMCC adapter fails with fatal error code 35 during the TN3270 Server shutdown. This problem occurs because the TN3270 Server PUs are not communicating with the host.
A workaround is available. Contact the Cisco TN3270 Server development engineers for the interim fix. [CSCdm61159]
•The TN3270 Server running DLUR/DLUS fails with fatal error message code 35. This problem occurs because the TN3270 Server tries to invoke a SendACTLURSP using a NULL object reference.
This fix adds a debug message to the log and marks the ACTLU as not processed.
There is no workaround. [CSCdm69186]
•The DLUR pipe between VTAM and the CMCC adapter hangs. This problem occurs when a large number of TN3270 Server TCP/IP requests (1000 per CMCC Adapter) arrive at the same time.
The workaround is to space out the TCP/IP requests. [CSCdm75120]
•When the CMCC adapter is configured with a large number of offload sessions, the following error message occurs:
%CIP2-3-MSG: slot0 %OFFL-3-NOMEM2: Not enough memory to process socket requests,
0 open, 0 in holddown
The workaround is to increase memory. [CSCdm76552]
•The TN3270 Server fails with the following error message:
%DEBUGGER-0-FATAL_ERROR: Fatal error (code=35)
This error occurs when the TN3270 Server is shut down while traffic is still transmitting. [CSCdm78261]
•The unbind/bind sequence in the response time logic during a transaction does not reset the sample. This error causes an invalid response time which might be extremely large, depending upon the timing of the transaction. This problem occurs when the unbind keep is configured when the next transaction completes.
There is no workaround. [CSCdm82521]
•A select() message does not respond or times out when the peer closes the connection. This problem is more likely to occur when using TPF.
The workaround is to delay the shutdown for 20 ms after the last send() message. [CSCdm85311]
•The TN3270 IND$FILE file transfer performs poorly if the RU size is smaller than the maximum transmission unit (MTU). This problem occurs because the Cisco TN3270 Server uses the Nagle algorithm by default.
The workaround is to set the RU size so that it is at least as big as the MTU on the file transfer path. [CSCdm86734]
•The TN3270 Server overwrites 1 byte of a Read Partition Query (RPQ) response. The overwrite occurs because of a logic that was entered to capture a non-standard SYSREQ key sequence for non-TN3270E emulators.
There is no workaround. [CSCdm88195]
•A TPF receive message fails to retrieve all the data. The problem occurs when the TPF client performs a shutdown-writing and then tries to receive the data.
The workaround is to not perform the shutdown-writing. [CSCdm92713]
•A CMCC file transfer hangs or the keyboard stops working. The problem occurs when the IND$FILE uses structured fields and buffers that are 2000 bytes or greater. The keyboard is restored using the TN3270 write command instead of the structured field.
The workaround is to use buffers that are 2000 bytes or less or non-structured fields (presentation space transfer. To enable the fix in CMCC releases cip27-4 and greater and xcpa27-4 and greater, you must configure the TN3270 tn-parameter code codevalue command with a code value of 7. [CSCdm93990]
•The VTAM to VTAM communication for APPN and FID2 hangs. The non-LLC2 HPR traffic does not hang. This problem occurs when both VTAMs are attached to the CIP running the CMPC feature.
There is no workaround. [CSCdp00921]
•The CMCC displays the following error message:
This error will not cause any serious problems.
There is no workaround. [CSCdp04360]
•A 4-to-5 second delay occurs between the CMCC connection to the server and the USSMSG10 screen display. This problem occurs only in CMCC trains cip24-x, cip27-x, and xcpa27-x.
There is no workaround. [CSCdp06877]
•The CMCC fails with error message 35. The problem occurs when the TN3270 Server is using the LU Nailing feature with the older PU definition for the nailed LUs instead of the LU Pooling definition in CMCC branches cip24-x, cip27-x, and xcpa27-x. The following example shows the old PU without the LU Pooling definition:
pu CISCO 04921002 157.2.196.101 token-adapter 31 24 rmac 4000.7206.0001
client ip 157.2.0.0 255.255.255.0 lu 4 20
The problem occurs when the client ip or no tn3270 server command is entered. The problem also can occur when the interface is shut down.
There is no workaround. [CSCdp07729]
•A TCP/IP Offload select() for readability message indicates that there are no readable sockets in the descriptor list when in fact there are readable sockets available. This problem occurs when the TCP/IP connection fails while a select() for readability message is outstanding on the socket.
There is no workaround. [CSCdp08103]
Caveats for Version 27.2/Version 27.3 Modifications
This section describes possible unexpected behavior by Version 27.1. All the caveats listed in this section are resolved in Version 27.2. See for the Cisco IOS software release that corresponds to the 27.2 microcode version.
•The CPA running the TN3270 Server fails with error code 35. This problem occurs when PUs are added to the configuration after the no tn3270 command was entered.
The workaround is to not enter the no tn3270 command.
• The TN3270 Server session disconnects after 150 seconds when the LOGON APPLID is not entered. In this case, there is no unformatted system services table (USSTAB).
There is no workaround. [CSCdk83774]
•Adding and removing PUs configured in TN3270 DLUR causes the CMCC Adapter to reload with fatal error message 32. This failure occurs when a shutdown command is issued during high traffic periods on the server. The following messages appear immediately before the error:
%CIP2-1-MSG: slot1 %TN3270S-1-RP_PU_CONFLICT:RP & CIP hold conflicting PU name(xxxxxxxx) or index(92)
Where "xxxxxxxx" is the PU name.
%CBUS-3-CIPCFGFAIL: Channel1/2: configuration command TN3270S_DLUR_PU_NEW cmd 18 failed
%CIP2-0-MSG: slot1 %DEBUGGER-0-FATAL_ERROR: Fatal error (code=32)
The workaround is to perform the shutdown when the server load is light. [CSCdk83807]
•The CMCC Adapter running TN3270 fails with fatal error number 35 when a shut command is issued to the TN3270 Server. This problem occurs when the shut command is issued and the TN3270 Server is operating at high capacity.
The workaround is to issue the shut command only after the client traffic terminates. [CSCdk87658]
•If a CIP2 PCA (Bus and Tag) has an Altera FLEX chip (the large chip on the PCA daughter card) with a date code of 9601 or greater, the CIP will fail with parity errors shortly after the card is first installed. The date code on the PCA can be found only by looking for a code on the edge of the chip or the top heat sink area.
The workaround is to upgrade to the recommended CIP microcode version which corresponds to your Cisco IOS software. [CSCdm28629]
•The TN3270 Server fails intermittently during the shutdown procedure. This failure occurs when the shutdown procedure is performed and TN3270 Server sessions are receiving client data. TheTN3270 Server shutdown procedure sequence shuts down the TCP/IP stack prematurely. The failure is intermittent depending upon the timing between receiving data from the client and the shutdown sequence.
This problem occurs in CMCC microcode releases cip22-35, cip24-10, cip25-10, cip26-5, xcpa 26-5, cip27-0, xcpa27-0, and later.
The workaround is to perform the shutdown procedure when there is no activity on the TN3270 sessions. [CSCdm35562]
•The CIP running TN3270 Server receives DSI562I error messages on the NetView console. The messages indicate that in the activate physical unit (ACTPU) control vector 80, unsolicited network management vector transport (NMVT) request units are not allowed. The CIP TN3270 Server still sends product-set identification (PSID) NMVT messages for VTAM PUs with only LUs.
There is no workaround.
To enable the fix in the cip24-13 microcode, the maximum-lu command must be added to the TN3270 Server configuration file. [CSCdm36152]
•The CMCC VTAM session hangs at the VTAM message10 menu. This problem occurs when the user is at the VTAM message10 menu and hits multiple blank Enter keys and when the inbound request unit on the SSCP-LU session is 256 bytes or greater.
There is no workaround. [CSCdm37663]
•The CIP fails and causes a CBUS restart. Activating the VTAM external communication adapter (XCA) causes the CIP to fail with fatal error number 35. Repeated restarts and reactivation of the XCA produces the same results. This problem occurs when running Cisco IOS Release 11.2(18)BC and CIP microcode version cip24-11.
The workaround is to use Cisco IOS Release 11.2(16)BC and CIP microcode version cip24-10. [CSCdm53220]
•When the Attention (ATTN) key is pressed, the TN3270 client sends PA1 and ATTN messages. This problem occurs for IBM Personal Communication clients only.
To enable this fix and filter out the PA1 messages, you must configure the TN3270 tn-parameter code codevalue command with a code value of 2.
There is no workaround. [CSCdm54076]
•Every other CMCC TN3270 Server client connection fails. This problem occurs when clients are trying to connect at a slow rate and the TN3270 Server is operating with a light traffic load.
There is no workaround. [CSCdm55234]
•The following message appears on the CMCC console:
bad error-code 12 given
This valid error code indicates a missing TERMSELF response. The code to log and format this specific error into a console message is missing.
There is no workaround. [CSCdm55961]
•The downstream mini-EN/DLUR is unable to connect because it incorrectly calculates the lengths on the REGISTER general data stream (GDS). Shutting down and restarting exacerbates the problem.
The workaround is to reload the CMCC adapter after changing the DLUR configuration. [CSCdm56389]
•Attachmate clients loop when attempting to connect to the server. This problem occurs when the client is running Attachmate software version 6.2, the auto-reconnect feature is enabled, and invalid client names are configured.
The workaround is to upgrade to Attachmate software release 6.3. [CSCdm58334]
•The TN3270 Server response time to the clients is slow (2 to 90 seconds). This problem occurs only if the clients are on a Token Ring or FDDI network and the server is on an Ethernet network. The problem occurs when there is a moderate to heavy load on the network.
The problem occurs because the client network maximum segment size (MSS) is set to 4000 and the server network MSS is set to 1500. The CMCC TCP stack attempts to increase the maximum transmission unit (MTU) from 1500 to 4000 every 10 minutes for each TCP connection. The Cisco IOS software sends only one or two ICMP messages per second, therefore some TCP packets are dropped and must be retransmitted. The retransmission intervals increase exponentially and these intervals appear to the user as a delay in response time.
To enable this fix in microcode version cip22-39 and later, you must configure the TN3270 server keepalive seconds command with a value of 14444. To enable this fix in microcode version cip27-3, xcpa27-3 and later, you must configure the TN3270 server tn-parameter code codevalue value minutes command with a code value of 5. Value is the number of minutes between path MTU discovery retries. The default is 10 minutes. A value of 0 implies an infinite timer value.
There is no workaround for other microcode versions. [CSCdm61803]
•The CMCC TCP/IP Offload server socket application hangs. This problem occurs because an accept() socket request blocks after the select() indicated that the server socket was READABLE. The accept() socket request should have returned a so_error condition or the socket ID of a new client socket. In TPF Offload environments, where a single select() may monitor multiple sockets, this problem can cause the application to hang on multiple server sockets if an accept() is issued from the same thread that processes the select() response.
The workaround is to close and re-open the server socket by restarting the server application on the host. [CSCdm63283]
•The CMCC TN3270 server fails with fatal error code 35. This error occurs if the fix in CSCdm58334 has been applied.
There is no workaround. [CSCdm69837]
•The TN3270 server sends an LIC message to the DLUS on a +RSP. This message causes the DLUS to send an unbind message with sense data 400B0000 and to shut down the DLUR/DLUS pipe. The DLUR/DLUS pipe will re-establish and the user LU-LU sessions will not be affected.
This problem occurs when the TN3270 server DLUR component improperly saves RU chain bits from the original request to create a response message. This generates the +RSP sense data 400B0000.
The workaround is to increase the RU sizes on the DLUR/DLUS sessions. To increase the RU sizes on the DLUR/DLUS sessions, the user must do the following:
•Create a new member called ISTINCLM in the customizable datasets ahead of SYS1.VTAMLIB in the concatenation sequence for DD name VTAMLIB.
•Copy the ISTINCLM member from SYS1.SAMPLIB.
•Change the RU sizes in member CPSVRMGR from 0x9797 to 0xC8C8 and assemble and link.
•Issue the VTAM command FNET,TABLE,TYPE=MODETAB,OPTION=LOAD,NEWTAB=ISTINCLM
•Restart the TN3270 server DLUR end node. [CSCdm70432]
•When the CMCC adapter is configured with a large number of offload sessions, the following error message occurs:
%CIP2-3-MSG: slot0 %OFFL-3-NOMEM2: Not enough memory to process socket requests,
0 open, 0 in holddown
The workaround is to increase memory. [CSCdm76552]
•To enable the fix for CSCdk83774, the user must set the seconds value of the TN3270 keepalive seconds command to a multiple of 21. This prevents clients from disconnecting when the idle timer expires because there was not an SSCP screen.
To enable the CSCdk83774 fix in microcode versions cip27-3, xcpa27-3 and later, you must configure the TN3270 tn-parameter code codevalue command with a code value of 6. [CSCdm76554]
Caveats for Version 27.1/Version 27.2 Modifications
This section describes possible unexpected behavior by Version 27.1. All the caveats listed in this section are resolved in Version 27.2. See for the Cisco IOS software release that corresponds to the 27.2 microcode version.
•An Offload application uses up resources and prevents traffic from going through the port adapter on the CMCC. This occurs in very unusual circumstances only, for example, when closing several thousand established TCP connections in a very short period of time.
The workaround is to reload the CMCC microcode. [CSCdj08904]
•A VTAM connect out completion time greater than 20 seconds causes unexpected connection failures and XCA major node failures. This failure occurs because VTAM overloads the PORT TIMER and, if the PORT TIMER is set too low, the LSA commands start to time out.
VTAM version 4.3 introduced restrictions for the PORT TIMER value. The TIMER value cannot be less than the CMCC's T1 * N2. VTAM uses a hard-coded N2 value of 2. Before this fix, the CMCC reported a T1 value of 10. The VTAM documentation indicates that the T1 value is measured in tenths of a second. Therefore, a T1 value of 10 should equal 1 second. However, VTAM interprets the T1 value in seconds so a T1 value of 10 equals 10 seconds, not 1 second. VTAM then multiplies the value by 2 to get a minimum TIMER value of 20 seconds.
The CMCC's reported T1 value is not the CMCC LLC T1 value. Because VTAM overloads the use of the PORT TIMER, do not adjust the CMCC's real LLC T1 value to alter the PORT TIMER. These adjustments can cause severe LLC2 problems.
VTAM overloads the use of PORT TIMER. TIMER is used to set TEST request interval on connect outs. After each TEST request is sent, VTAM sets a timer equal to the PORT TIMER number of seconds and waits for a TEST response. If the TEST response is not received by VTAM before the timer expires, the next TEST request is sent. In CMCC scenarios, the first TEST request is a TEST local, the second is a spanning-route explorer.
For the CMCC, most VTAM initiated LLC connections will not complete before the PORT TIMER seconds expire because the local TEST does not leave the CMCC's internal LAN. LLC connection setup requires a minimum of 20 seconds. VTAM will timeout on LSA commands if a response is not received within the set PORT TIMER value. For example, when VTAM sends a CONNECT request the CONNECT CONFIRM must be received before the PORT TIMER expires. The SABME and UA must be exchanged within the value set in PORT TIMER. If the SABME must be retried, the PORT ITMER might expire before the CONNECT CONFIRM is returned to VTAM.
The workaround is to set the PORT TIMER value to 20 seconds or more unless the user is confident that the LSA commands will not timeout. [CSCdj45782]
•The TN3270 Server crashes with fatal error code 35. See caveat CSCdk02535. [CSCdk11968]
•During a brief TCP connection, the CMCC TCP/IP Offload feature fails to return a response to a Read/Recv type socket request causing the connection's host application to hang while waiting for a response.
A window exists for brief TCP connections when a connection is made with TCP/IP on the CMCC and then broken (FIN received) before Offload has received and processed an Accept socket request from the host. In this situation, Offload misses the notification from TCP/IP that the connection had been terminated.
There is no workaround. [CSCdk12291]
•The TN3270 Server session fails with the following error message:
The workaround is to reactivate the external communication adapter (XCA) major node. [CSCdk36329]
•The user is unable to track, using Hot Standby Router Protocol (HSRP) or SNMP Traps, the channel interface on a Cisco 7200 series router with a Channel Port Adapter (CPA). The channel interface is always up/up even if the physical interface cable is not attached to the CPA.
There is no workaround.
A new channel interface configuration command which is valid only for the CPA, state-tracks-signal, fixes this problem. This command directs the CPA's channel interface state to follow the physical signal value when the interface is in the no shut state. [CSCdk44052]
•If a user disconnects without properly logging off the mainframe, a new user can connect to those existing sessions. This problem occurs when accessing Customer Information Control System (CICS) applications through the TN3270 Server. [CSCdk48736]
•Sometimes TN3270 client disconnections are counted twice. This miscount results in an incorrect TN3270 active session count. The dynamic LU count for that PU becomes one less than the actual number. This is not a problem until the actual count reaches zero and the dynamic LU count cycles to 255. When this miscount occurs, if you enter the show extended ch4/2 tn command, (which shows how many LUs are in use) the result is inflated by 255.
The workaround is to shut down and restart the PU or to cycle the PU in VTAM. [CSCdk57112]
•Inconsistent keepalives occur when multiple TN3270 sessions are configured to the same server. When the sessions are idle for an hour or more, keepalives are not sent even though the keepalive value is set to 300 (5 minutes).
The workaround is to restart the session. [CSCdk57453]
•Dynamic LUs remain in a P-NFT/UA state when the TN3270 Server is configured. The LUs cannot be used again when in this state.
The workaround is to deactivate the LU or the owning PU in VTAM. [CSCdk60263]
•The TN3270 session between the client and TN3270 server is disconnected when the client issues the logoff command at the VTAM MSG10 screen. [CSCdk80609]
•The TN3270 Server session disconnects after 150 seconds when the LOGON APPLID is not entered. In this case, there is no unformatted system services table (USSTAB).
There is no workaround. [CSCdk83774]
•When the TN3270 server is configured, entering the SYSREQ key followed by the logoff command does not return the user to the queued session. Instead, the VTAM MSG1 warning is displayed.
Other SYSREQ key errors that occur when the TN3270 server is configured include:
•Pressing the SYSREQ key twice does not return the user to the LU-LU session. An LUSTAT is sent inbound on the second SYSREQ key entry.
•Entering the logoff command incorrectly locks the session. SSCP-LU does not recognize the change direction in a sense data frame. This problem might occur in other remote cases.
•LU-LU data shows up on an SSCP-LU session.
•When responding to DACTLU in LU-LU or bound states, an inbound unbind should be sent. This inbound unbind was not working, but it was not evident because the client is normally disconnected which causes a SESSEND.
The workaround is to not use the SYSREQ key. [CSCdk83960]
•The TN3270 Server does not process the 0x016C6102 message from the client as a system request (SYSREQ). Therefore, the TN3270 Server does not send a logoff message to the system services control point (SSCP). This message should produce the sequence described in RFC 1647 (TN3270E), except that 0x016C6102 is used to indicate SYSREQ instead of Abort Output (FFF5).
There is no workaround. [CSCdk89383]
•CMCC devices with Bus and Tag connections do not activate properly when connected to an Amdahl 857 running the UTS operating system.
There is no workaround. [CSCdk91964]
•For extended periods of time, the write device for a CLAW connection experiences the same number of command retries and connects. Data throughput decreases significantly during these periods, but the connection is not lost. The connections and the command retries are displayed with the show extended channel slot/port command. This situation occurs when the channel operates at 95 percent or greater capacity for many hours.
A workaround is to distribute the traffic to multiple boxes to avoid a channel capacity of 95 percent or greater. [CSCdk92004]
•The CMCC TCP/IP Offload feature fails during select() processing when 28 or more sockets are defined in a single select request. If a select() request contains 28 or more socket descriptors in the descriptor list, the select() response is truncated after the offload message header. If the mainframe offload application does not validate the offload message header buffer_length field and detect the ZERO length response data, it may process random data in the memory which follows the offload message header as the start of response data and incorrectly interprets the select() response results.
This problem does not occur when using select() under VM or MVS because select() is issued for one socket at a time. This problem occurs when using TPF if the select() request contains 28 or more socket descriptors.
There is no workaround for this problem. This DDTS is a continuation of CSCdk86184. [CSCdm02126]
•If IP fragments that are 21 to 23 bytes long are sent to the CLAW of an OFFLOAD connection to a mainframe the packet is dropped and the following error message is sent:
CLAW-6-TOOSMALL: xx byte IP datagram is to small, device x/yyyy/zz
The workaround is to modify the network so that IP fragments do not occur. [CSCdm11522]
•The CMCC unexpectedly reloads with the following error messages:
