Compaq SNA Peer Server Version 1.5A Release Notes August 29, 2000 This document contains information not included in the Compaq SNA Peer Server V1.5 documentation. It includes information about required and optional software, installation notes, oper- ating notes, problem corrections, and known problems with this software version and known restrictions in companion software. IMPORTANT Please read these notes before installing or using the software. Revision Information: This is a new document. Operating System Version: Tru64 UNIX V5.0, V5.0A, and V5.1 DECnet Version: DECnet-Plus for Tru64 UNIX V5.0A Software Version: Compaq SNA Peer Server V1.5A Compaq Computer Corporation Houston, Texas © 2000 Electronic Data Systems Corporation © 2000 Compaq Computer Corporation COMPAQ, DECnet, VAX, VMS, the Compaq logo, and the DIGITAL logo Registered in U.S. Patent and Trademark Office. Motif, OSF/1, and UNIX are registered trademarks of The Open Group. All other product names mentioned herein may be the trademarks or registered trademarks of their respective companies. Confidential computer software. Valid license from Compaq or authorized sublicensor required for possession, use, or copy- ing. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this publication is subject to change without notice and is provided "AS IS" WITHOUT WARRANTY OF ANY KIND. THE ENTIRE RISK ARISING OUT OF THE USE OF THIS INFORMATION REMAINS WITH THE RECIPIENT. IN NO EVENT SHALL COMPAQ BE LIABLE FOR ANY DIRECT, CONSEQUENTIAL, INCIDENTAL, SPECIAL, PUNITIVE, OR OTHER DAMAGES WHATSOEVER (INCLUDING WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, OR LOSS OF BUSINESS INFORMATION), EVEN IF COMPAQ HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING SHALL APPLY REGARDLESS OF THE NEGLIGENCE OR OTHER FAULT OF EITHER PARTY AND REGARDLESS OF WHETHER SUCH LIABILITY SOUNDS IN CONTRACT, NEGLIGENCE, TORT, OR ANY OTHER THEORY OF LEGAL LIABILITY, AND NOTWITHSTANDING ANY FAILURE OF ESSENTIAL PURPOSE OF ANY LIMITED REMEDY. The limited warranties for Compaq products are exclusively set forth in the documentation accompanying such products. Nothing herein should be construed as constituting a further or additional warranty. Contents 1 INTRODUCTION 1 1.1 Version 1.5A Overview 1 1.2 Appendices Removed in NCL Reference Manual 1 1.3 LLC2 Entity Changes 1 2 REQUIRED SOFTWARE 2 2.1 Compaq Tru64 UNIX 2 2.2 DECnet-Plus for Tru64 UNIX 2 2.3 Compaq WAN X.25 3 3 INSTALLATION NOTES 3 3.1 Removing Prior Versions 3 3.2 Installing or Upgrading Peer Server Required Software 4 3.3 NCL Initialization File Reuse 4 4 OPERATING NOTES 4 4.1 System Requirements for Supporting up to 10,000 Concurrent Sessions 4 4.2 Synchronous Data Link Control Support (SDLC) 5 4.2.1 Supported SDLC Devices 5 4.2.2 Naming of Synchronous Lines 6 4.2.3 SDLC Receive Frame Size Limitation 6 4.2.4 Modem Connect Line Speed Characteristic 6 4.2.5 SCC Device Name 7 4.2.6 CCITT V.24 Incompatibility with EIA RS-232C (DSYT1 and DNSES Only) 7 4.3 Logical Link Control Type 2 (LLC2) 8 4.3.1 Token Ring Support 8 4.3.2 Ethernet Support 8 4.3.3 FDDI Support 8 4.3.4 Operation in Bridged Token-Ring and FDDI Environments 8 4.3.5 Mapping Between IBM LLC2 and EMA LLC2 Parameters 8 4.4 WANDD Loader 9 4.5 Automatic Generation of NOTIFY(ONLINE) and NOTIFY(OFFLINE) 9 4.6 Specifying PU Name and Session Number on Client Connections 10 4.7 Session Termination Support for Non-IBM Mainframes 10 4.8 Startup Initialization Delay 10 4.9 OS/2 LAN Support Withheld 11 5 KNOWN IBM RESTRICTIONS 11 iii Contents 5.1 Configuring Multiple Lines as PU T2.1 on the Peer Server 11 5.2 IBM 3745 Scanner Problem Running Above 230Kbps 11 5.3 NCP Problems with SDLC Mixed Modulo Stations on a Multipoint Line 11 5.4 NCP Problems with Modulo 128 Token Ring Stations 12 5.5 INIT-SELF Rejected with Sense Code 10105006 12 5.6 VTAM ABEND S0C4 at ISTATCTR+1F0 12 6 KNOWN PROBLEMS AND PRODUCT RESTRICTIONS 12 6.1 Common Trace Facility (CTF) Restrictions 13 6.1.1 LU Tracepoints Not Supported 13 6.2 Network Management Restrictions 13 6.2.1 NCL Delete Transmission Group Generates "Wrong State" Exception 13 6.2.2 NCL Enable SDLC Link Station Generates "Invalid Parameter" Exception 14 6.2.3 LocalEntityName Instance Specification 14 6.3 SDLC Datalink Restrictions 15 6.3.1 Multipoint Full Duplex Configuration Requires TWA 15 6.3.2 Using the PBXDI ISA-bus Synchronous Communications Controller 15 6.4 QLLC Datalink Restrictions 15 6.4.1 Temporary TGs Lack Automated Call Startup 15 6.4.2 Filtername Mismatch Error is Ambiguous 16 6.4.3 QLLC Link and Station Must be Enabled Before TG 16 6.5 TN3270 Server Restrictions 16 6.5.1 TN3270 Server Default Port (2301) Used by Insight Manager 16 6.5.2 TN3270 Server Drops Connection when Client Does Not Respond Properly 17 6.6 LLC2 Datalink Performance Issues 17 6.6.1 FDDI Performance 17 7 FILES INSTALLED/MODIFIED 18 8 FIXES FOR THE PEER SERVER V1.5A RELEASE 20 8.1 NCL Wild Card Parsing of Peer Server Entities Now Supported 20 8.2 Corrected SNA LU Services Authorization Node Characteristic Reset Problem 20 8.3 Corrected Independent LU Capability With Passive Listens Problem 21 8.4 Pass Unbinds from Access Routines Now Left Unmodified 21 iv Contents 8.5 Stop Session Management Commands for LU Sessions Now Working 21 8.6 Corrected BIND before INIT-SELF-RSP Rejection 21 8.7 Corrected Transition Address During XID3 Negotiation for SDLC Dial Configuration 21 8.8 Corrected Routine q25_dlpi_bind_req() Reference to Deallocated Memory 21 8.9 Corrected Routine t21__spam_process_sess_route_inop() Reference to Deallocated Memory 22 8.10 Corrected T21MCD Daemon Crash Caused by Reference to Deallocated Memory 22 8.11 Corrected T21WAD Crash Caused by Reference to Deallocated Memory 22 8.12 Initialize Data Structure in t21cad_thread 22 8.13 Added Check to Catch Thread Wakeups on llc_dispatch Tasks 22 8.14 Added Correction to Prevent Internal Timer from Stopping Prematurely 22 8.15 Added correction to Prevent TN3270 Server from Rejecting a Valid BIND Image 23 8.16 Corrected Stop Session Commands for Independent LU Sessions 23 8.17 Made Outbound Session Startup SMP Safe 23 8.18 Changed t21llc Dispatcher Routines To Use Noninterruptable Thread Blocks 23 8.19 Removed T21_WARNING Message for Timeout Entry from Kernel Log 24 8.20 Changed t21llc's Close Routine to An Event Driven Process 24 8.21 Corrected SDLC Unacknowledge Frame Check Routine 24 8.22 Corrected Queue Macro Calls in Minor Device Allocation Routines 24 8.23 Corrected LMF Capacity Unit for Local Server Streams 24 8.24 Corrected LU Old Name String Descriptor 24 8.25 Corrected Queue Macro Pointer In Minor Device Allocation Routines 25 8.26 Corrected t21cad Thread Stack Overflow Caused By Simultaneous Loss of Client And Gateway Connections 25 8.27 Corrected Notify RSP RU for Segemented RU 25 8.28 Corrected GAP UNBIND Race Condition Problem 25 8.29 Corrected Premature Inbound Segmentation Fields Update Problem 25 v Contents 8.30 Corrected Loss of Inbound Segmented GAP Messages 26 8.31 Corrected GAP Message Length When DECnet Connection Lost 26 8.32 Corrected Handling of BINDS In Cross Domain Networks To Prevent Duplicate LFSID Assignment When An LU is Deactivated 26 8.33 Corrected Integer Overflow in T21CAD When Using TCP Transport 26 8.34 Corrected CTF trace points in SDLC datalink when Peer Server is restarted 26 8.35 Enable XID negotiation restart on XID vector '22' errors. 27 8.36 Set correct message pointer before calling dispatcher. 27 8.37 Ignore -RSP's from remote LU's on LU-LU in TN3270. 27 8.38 Correctly handle thread cleanup in TN3270. 27 8.39 Fix SNA_S_LOGNOUSE messages in TN3270. 27 8.40 Corrected Erroneous Output Associated with the TN3270 Server 27 8.41 Fix kernel memory corruption in QLLC module. 28 8.42 Initialize LU pointer for plumb cancel. 28 8.43 Do not dispatch X25 messages after shared memory is deallocated. 28 8.44 Change Peer Server LLC2 to handle multiple SABME frames. 28 8.45 Check shared memory reference in Peer Server QLLC trace calls. 28 8.46 Allow for Peer Server transmission group shutdown before killing daemon processes. 29 8.47 Change number of downcredits passed to X25L3. 29 8.48 Fix Peer Server CINIT internal response for terminated sessions. 29 8.49 Fix memory corruption in management access daemon (T21MAD). 29 8.50 Deallocate Peer Server capacity license unit on open stream failures. 29 8.51 Allow only privileged Users the ability to modify Peer Server SNA Entities. 30 8.52 Add "keep-alive" option to TN3270. 30 vi Contents TABLES 1 Peer Server Installed Files 18 2 Peer Server Configuration Files 19 3 Peer Server Files Used for Logging 19 4 Peer Server Modified Files 20 vii 1 Introduction These release notes are for Version 1.5A of the Compaq SNA Peer Server. Following product installation, this file can be found in /var/sna/t21_15A-0_release_notes. The abbreviated Peer Server product name is used throughout this document. 1.1 Version 1.5A Overview Compaq SNA Peer Server Version 1.5A is a manditory update re- lease for Compaq SNA Peer Server V1.5 to support Tru64 UNIX V5.0, V5.0A, and V5.1 operating systems. The release includes all fixes from Compaq SNA Peer Server V1.4 through ECO 05. The primary enhancement provided by V1.5 of the Peer Server is sup- port for Primary Dependent LU (R3270) sessions. Refer to the Compaq SNA Peer Server Management manual for more information on the primary dependent LU feature. Version 1.5A is a functional superset of Version 1.4. All ca- pabilities supported in Version 1.4 are supported in Version 1.5A. Please note that there is a new release of the Peer Server documentation in conjunction with this release of the Peer Server software. 1.2 Appendices Removed in NCL Reference Manual The Token Ring, CSMA-CD, and FDDI appendices in the Peer Server's NCL Reference manual have been removed. Some of the information in these appendices was out of date. To prevent this possibility in the future, these appendices have been re- moved. You should use the DECnet-Plus for Compaq Tru64 UNIX NCL Reference manual for information about these entities. 1.3 LLC2 Entity Changes The LLC2 material in the Peer Server's Management and NCL Reference manuals has been updated to reflect the latest LLC2 implementation. Because of the close association of this entity with the Peer Server, the description of this module was kept in the Peer Server's documentation. However, the DECnet-Plus for Compaq Tru64 UNIX NCL Reference may contain more up-to-date information. 1 The online help for the LLC2 entities has been removed from the SNA_Peer_Server help topic. You should use the LLC2 help available under the individual command descriptions. 2 Required Software You must have the required software installed before you can install the Peer Server software. This includes the correct version of the Compaq Tru64 UNIX operating system and certain required, DECnet-Plus for Tru64 UNIX V5.0A and Compaq WAN X.25 subsets V3.1B. For optional DECnet and/or X.25 functionality, DECnet-Plus for Tru64 UNIX and/or Compaq WAN X.25 software must also be installed and configured. The Compaq SNA Peer Server Installation and Configuration manual describe these requirements. See DECnet-Plus for Tru64 UNIX and/or Compaq WAN X.25 documentation if those functionalities are required. 2.1 Compaq Tru64 UNIX The Peer Server V1.5A software installs on Tru64 UNIX V5.0, V5.0A, and V5.1. 2.2 DECnet-Plus for Tru64 UNIX The Peer Server can use both TCP/IP and DECnet networks. If you plan to use DECnet, you must install DECnet-Plus for Tru64 UNIX V5.0A or later. If you wish to install or upgrade DECnet-Plus software on a system that is already running a version of the Peer Server, then you must delete the Peer Server subsets before installing DECnet-Plus for Tru64 UNIX. See Section 3.1 for instructions on removing the Peer Server software. Once you have installed and configured DECnet-Plus, you should install the Peer Server V1.5A software. Unless you are planning to use DECnet communications to access the Peer Server, there is no requirement that the DECnet-Plus for Tru64 UNIX layered product be installed on the Peer Server system. (However, certain DECnet-Plus subsets are required to be installed and configured on the Peer Server system. See the Compaq SNA Peer Server Installation and Configuration manual.) 2 2.3 Compaq WAN X.25 With the Peer Server, SNA traffic may be sent over X.25 Packet Switched Data Network (PSDN) backbones using the Qualified Logical Link Control (QLLC) protocol. This enables X.25 cus- tomers to communicate with their IBM machines using SNA pro- tocols over X.25 networks. To do so, you need Compaq WAN X.25 for Tru64 UNIX Systems V3.1B or later software product (avail- able separately) installed prior to installing the Peer Server. You must also have the IBM software resident and configured on the IBM machine (for example, X.25 Network Control Program Packet Switching Interface (NPSI) for IBM mainframe front end communications processors). The use of QLLC is supported with both types of X.25 PSDN ac- cess provided by the Compaq WAN X.25 Systems product, namely: by direct synchronous communications link (LAPB) or by LAN access to an X.25 Relay node (LLC2). Unless you are planning to use the QLLC protocol with the Peer Server, there is no requirement that the Compaq WAN X.25 lay- ered product be installed on the Peer Server system. However, certain X.25 subsets are required to be installed and config- ured on the Peer Server system. See the Compaq SNA Peer Server Installation and Configuration manual. If you wish to install or upgrade Compaq WAN X.25 software on a system that has a previous version of the Peer Server in- stalled, then you must delete the Peer Server subsets before installing X.25. See Section 3.1 for instructions on removing the Peer Server software. Once you have installed and config- ured Compaq WAN X.25, you should install the Peer Server V1.5A software. 3 Installation Notes 3.1 Removing Prior Versions If you have an earlier version of the Peer Server software installed on your node, you must delete it prior to installing this kit. To see whether a previous version is installed, issue the command setld -i | grep T21 The following subsets must be deleted to completely remove the Peer Server software prior to installing a new version of the Peer Server software. T21MGMTnnn T21SRVRnnn 3 Delete the named subsets listed as installed (substituting the correct subset numbers for "nnn") using the command # setld -d subset subset ... 3.2 Installing or Upgrading Peer Server Required Software If you install or upgrade DECnet-Plus for Tru64 UNIX and/or Compaq WAN X.25 required software, then you must delete and reinstall the Peer Server software. See Section 3.1 for in- structions on removing the Peer Server software. Once you have installed and configured DECnet-Plus and/or Compaq WAN X.25 software, you should reinstall the Peer Server software. The following is the list of software that requires reinstallation of the Peer Server if upgraded or installed after Peer Server is installed. CTAANALnnn (Compaq WAN X.25) CTABASEnnn (Compaq WAN X.25) WDABASEnnn (Compaq WAN X.25) WDADATALNKSnnn (Compaq WAN X.25) WDADRIVERSnnn (Compaq WAN X.25) ZZAUTILnnn (Compaq WAN X.25) DNAKBINnnn (DECnet-Plus) DNANETMANnnn (DECnet-Plus) DNABASEnnn (DECnet-Plus) 3.3 NCL Initialization File Reuse Previous Peer Server customers can retain the NCL initial- ization scripts configured for earlier versions of the Peer Server, provided they anticipate the same configuration for their Version 1.5A installation. (The default startup script is t21_init_sna_server.ncl in the /var/sna directory.) 4 Operating Notes 4.1 System Requirements for Supporting up to 10,000 Concurrent Sessions By default, DECnet-Plus for Tru64 UNIX is configured to allow up to 128 concurrent connections. The Tru64 UNIX operating system software limits the number of open files (sockets) that a process can have to 4096. Appendix F of the Compaq SNA Peer Server Installation and Configuration manual discusses how to raise these limits to allow the Peer Server to support up to 10,000 concurrent DECnet connections. 4 4.2 Synchronous Data Link Control Support (SDLC) As with earlier versions of the Peer Server, Version 1.5A sup- ports IBM's Synchronous Data Link Control (SDLC) WAN datalink protocol for the SNA connection to the adjacent PU T2.1 or PU T4 node. (The AS/400 is an example of a PU T2.1 node. A mainframe front-end communications processor, such as a 3745 running IBM's NCP software is an example of a PU T4 node.) 4.2.1 Supported SDLC Devices The synchronous port used by the Peer Server is provided by a combination of the Tru64 UNIX WAN Device Drivers software and the synchronous communications hardware itself. Four types of synchronous hardware are supported with Version 1.5A of the Peer Server: the built-in, integral SCC sync port, the optional DSYT1 high speed TURBOchannel adapter (DSYT1-BA), the optional DNSES EISA synchronous communications controller hardware, and the optional PBXDI ISA synchronous communications controller. The SCC port supports the V.24/RS-232 interface only, at speeds up to 19.2 kb/s. The optional DSYT1 (also known as the DIGITAL WANcontroller 720) and the DNSES adapters both contain two lines per device and support SDLC up to T1/E1 (2.048 Mb/s for a single line and up to 64 kb/s when both lines are used. The DSYT1 and DNSES support both the V.24/RS-232 and the V.35 physical interfaces. The PBXDI controller supports two lines; one model (PBXDI-AA) supports the V.24/RS-232 interface, an- other (PBXDI-AB) supports both RS-232 and V.35 interfaces. (A third model (PBXDI-AC) exists but should not be used for SDLC.) External clocking (modems, modem eliminators, or NCP "direct attach" lines) are required in all cases. The SCC port is present on all DIGITAL 3000 systems supported by the Peer Server. On the 3000-300 and 3000-300L, however, the SCC port may only be used with the Peer Server when it is otherwise not used as the console port (that is, a monitor must be used for the console). Multiple DSYT1, DNSES, or PBXDI devices may be used for a higher number of concurrent links (each device having two links). All require a free bus slot (TURBOchannel, EISA, and ISA bus, respectively), and slot availability varies by spe- cific system model. For example, the 3000 Model 800/S has up to 6 free TURBOchannel slots (thus 13 links - 6 DSYT1's and a single SCC - may be used in the extreme case). Similarly, the maximum number of DNSES units is limited by free EISA slots and specific hardware configuration. Consult the Compaq Systems and Options Catalog (Alpha product hardware information) for full configuration details. 5 4.2.2 Naming of Synchronous Lines The Modem Connect Line entities are assigned names based on the order that the devices are named during configuration. When you execute or re-execute wddsetup, make sure that the devices are named in the same order as previously, or else the existing configurations of Peer Server or other products may become invalid. Please specify which device(s) {dsy scc none} are to be used. [scc]: dsy scc 4.2.3 SDLC Receive Frame Size Limitation The Peer Server Configuration utility prompts you to enter the SDLC maximum receive frame size for the selected link. If you are using the built-in synchronous adapter (SCC) on the Alpha system instead of a DEC WANcontroler 720 (DSYT1), this value cannot exceed 1000 bytes due to hardware limitations. If you are using ta DEC WANcontroller 720 line, this value cannot exceed 4000 bytes. 4.2.4 Modem Connect Line Speed Characteristic The following pertains to half-duplex and multipoint config- urations, in which the local Peer Server DTE is toggling its Request to Send (RTS). Because of a limitation with the SCC, DSYT1, and DNSES hard- ware with regard to transmit interrupts, the respective device driver must compute the time to retain RTS assertion following the last data byte transmitted. The delay time is a function of the actual line speed, and the driver must therefore be aware of the speed of the link. To accommodate the RTS drop delay computation, the Modem Connect Line entity includes a characteristic attribute called "Speed." If the Peer Server is to be used in a half-duplex or multipoint configuration, the Speed characteristic must be set to the actual speed at which the line is being externally clocked. Speed is entered in bits per second, for example a 19.2 kb/s link would have Speed set to 19200. (When set to zero, the default RTS computation assumes an actual line speed of 1200 bits per second.) Failure to set the speed accurately results in unpredictable results with half-duplex and multidrop lines, from reduced line throughput to transmission failures. On a multipoint line, it is possible that a misconfigured Peer Server line could affect data transfer between other tributary stations and the primary station. 6 The wddsetup step of the V1.5A Peer Server (/usr/sbin/wddsetup), invoked as part of the product installation, includes prompt- ing for line speed when the line specified is half duplex or full duplex multipoint. If the Tru64 UNIX WAN Device Drivers are already present and configured on the Peer Server tar- get node and the wddsetup step is not re-run during the Peer Server installation, you must ensure that the Speed character- istic is properly set for the lines to work properly in half duplex and multipoint modes. Re-running /usr/sbin/wddsetup or manually editing the Modem Connect startup NCL file in /var/dna/scripts/wdd.mconnect.ncl and restarting renders the change permanent. 4.2.5 SCC Device Name The SCC built-in synchronous port is referred to by NCL manage- ment and the WAN Device Driver scripts (wddsetup) as the "sscc" device, and as communications port "sscc0". The latter forms must be used when entering network management or configuration commands. 4.2.6 CCITT V.24 Incompatibility with EIA RS-232C (DSYT1 and DNSES Only) An incompatibility exists between the CCITT V.24 and EIA RS- 232C physical interface standards with respect to pins 18, 21 and 23. The DSYT1 and DNSES are engineered for strict accor- dance with the newer V.24 standard, and are therefore incom- patible with the older RS-232C interface. In order to permit the DSYT1 and DNSES to be used with RS-232C compliant devices, a V.24 hardware adapter connector part number 12-27591-01 is supplied with the BS19D-02 V.24 cable set. The adapter is at- tached to the DCE end of the BC19D-02 V.24 cable. Refer to the information sheet supplied with the cable hardware for more information (info sheet EK-BS19D-IS-001). Failure to use the adapter where indicated results in an in- ability to activate the line and possibly even damage the modem or interface module. If you are unsure whether the adapter should be used or not, it should be fitted as a matter of course. Note that doing so may disable remote and local loop functions. This issue does not apply to the SCC sync port, which has tolerance for the difference in the standards. No adapter is required with the SCC. 7 4.3 Logical Link Control Type 2 (LLC2) 4.3.1 Token Ring Support The hardware adapter required for Token Ring is the DIGITAL TRNcontroller 700 (DETRA) TURBOchannel card or the EISA Token Ring Communications Controller (DW300/DT424). Both accommo- date 4 and 16 Mb/s ring speeds (selectable). A single hardware adapter may be used simultaneously with multiple protocols (for example DECnet-Plus, IP, and Compaq WAN X.25), using different SAPs. 4.3.2 Ethernet Support All Compaq-supplied Alpha Ethernet adapters supported under Tru64 UNIX are supported with this version of the Peer Server. Peer Server V1.5A support Ethernet using IEEE 802.3 frame for- mat, and not Ethernet V2. This may be an issue when configuring SNA over Ethernet to an IBM SNA node, which typically has a configuration option for Ethernet 802.3 or V2 (with protocol type 80d5). Ensure that your IBM Ethernet implementations (both destina- tion nodes and bridges, such as the IBM 8209) are configured to use the 802.3 format for Ethernet frame transmission for communication with the Peer Server. 4.3.3 FDDI Support All Compaq-supplied Alpha FDDI adapters supported under Tru64 UNIX V5.0 are supported with this version of the Peer Server. 4.3.4 Operation in Bridged Token-Ring and FDDI Environments When running the Peer Server in a bridged environment, it is possible that an intervening bridge or LAN segment supports a maximum frame size smaller than that configured in the two communicating systems. The Peer Server detects this and auto- matically reduces the maximum frame size used in this case. 4.3.5 Mapping Between IBM LLC2 and EMA LLC2 Parameters Appendix E of the Compaq SNA Peer Server Installation and Configuration manual contains a mapping between the IBM LLC2 parameters and the EMA LLC2 parameters (settable through NCL). 8 NOTE The default value for Holdback Timer is 500ms. To achieve a reasonable level of throughput, this parameter must be set to a value of 10ms. 4.4 WANDD Loader The wdd_loader program runs as a daemon process and is re- sponsible for handling microcode loading and dumping for those synchronous devices that require it. This daemon must not be killed; doing so may result in a system panic. 4.5 Automatic Generation of NOTIFY(ONLINE) and NOTIFY(OFFLINE) Starting with V1.2, the Peer Server sends ACTLU responses that indicate the LU is not available by default. The product then sends NOTIFY(ONLINE) when an access routine connects to the LU, and NOTIFY(OFFLINE) when the access routine disconnects. This is different from previous versions of the product and also different from the PU2.0 Gateway-ST and Gateway-CT products. This behavior can be modified such that the Peer Server behaves exactly as before if necessary, but doing so means that the product cannot be used for 3270 Terminal Emulator access to AS/400 systems. While the new behavior is typically closer to real IBM equip- ment, it does cause problems when connections to the LU are made and broken in quick succession. It also causes problems when the LU is in session when the Peer Server is deacti- vated, as the next time the LU is used the host application may attempt to re- BIND to the LU (which can override the real session activation request sent by the client). To turn off this feature, you should edit the file /var/subsys/t21scl.stanza and modify the line: use-notify = 1 to be: use-notify = 0 then enter the following command (as root): # sysconfigdb -u -f /var/subsys/t21scl.stanza t21scl This modifies the permanent database, which takes affect next time the system is booted. To modify the running system, use the following command: # sysconfig -r t21scl use-notify=0 9 The new setting takes effect the next time each LU is acti- vated. 4.6 Specifying PU Name and Session Number on Client Connections The Peer Server Logical Units (LUs) are named entities and have an attribute called "Old Name" that can be set so that existing client applications can continue to connect to spe- cific LUs using the PU name and Session Address syntax used with DECnet/SNA Gateway-ST and -CT. Specify the Old Name in the format [pu-name.][session-number]. If a client connection is received by the Peer Server specify- ing only a PU-name and no session number, the Peer Server will not use the PU-name when attempting to match the connection to an LU with an "old name" set. 4.7 Session Termination Support for Non-IBM Mainframes Certain IBM plug compatible (PCM) mainframe SNA implemen- tations, e.g. Fujitsu, are known to require dependent SLU initiated session termination with (Rq)TERM-SELF instead of (Rq)UNBIND. Peer Server LU Services supports this feature. In the case where an LU-LU session (Rq)UNBIND sent from Peer Server to the mainframe is rejected with 1003 -Rsp, a TERM-SELF is sent from Peer Server to solicit an UNBIND from the PLU. This feature addresses PCM compatibility without affecting standard IBM mainframe session behavior. 4.8 Startup Initialization Delay The time between starting the Peer Server (from system boot, running of the t21icu Configuration utility, or explicit ex- ecution of "t21_sna_server start" from /sbin/init.d and full initialization may be on the order of minutes, particularly if your specific t21_init_sna_server.ncl has a very large number of LUs and related entities specified. Confirmation of initialization completion can be seen by run- ning a Tru64 UNIX system utilization utility (for example iostat), to show CPU utilization dropoff following comple- tion) or by interactively running NCL on the Peer Server ma- chine, confirming final entity enabling. In addition, the file /var/tmp/t21_init_sna_server.log contains the output from the initialization. 10 4.9 OS/2 LAN Support Withheld As documented in Compaq SNA Peer Server Guide to IBM Resource Definition, formal support for connections to OS/2 Extended Services and Communications Manager are limited in this release to SDLC. 5 Known IBM Restrictions The following sections list problems identified with IBM soft- ware that you may encounter when installing/running the Peer Server in your environment. APAR and PTF numbers are provided that can be used to ensure that your VTAM/NCP installation has the fixes applied. 5.1 Configuring Multiple Lines as PU T2.1 on the Peer Server If you are configuring multiple lines on the Peer Server to connect to the IBM front-end (3725/3745) as a PU T2.1 link (XID=YES on the PU macro) you need to code CONNTYPE=LEN on the PU macro also. If CONNTYPE=LEN is not coded, the activation of the second line fails with a sense code of 081D. This problem is due to the Peer Server sending the same CP Name on each link (which is consistent with an SNA LEN node). 5.2 IBM 3745 Scanner Problem Running Above 230Kbps When connecting a DSYT1 or DNSES high speed SDLC line to an IBM 3745 communications controller running a line speed of 256 kbps, the IBM controller may report hardware underruns. The symptoms of the problem on the Peer Server are that the link fails and restarts, or that a large number of SDLC frames are retransmitted. This problem is not seen on links running at 230 kbps or below. Contact your Compaq Customer Support Center for an update or resolution to the problem if you plan to run SDLC links at speeds above 230Kbps. 5.3 NCP Problems with SDLC Mixed Modulo Stations on a Multipoint Line A problem exists in NCP V4, V5, and V6 whereby an SDLC mul- tipoint line configured with PU T2.1 stations of both normal (modulo 8) and extended (modulo 128) SDLC window sizes can er- roneously issue a modulo 128 SDLC poll from the NCP to a modulo 8 station. 11 This has been corrected with the following APARS from IBM: o NCP V4 IR24362 o NCP V5 IR24307 o NCP V6 IR24170 5.4 NCP Problems with Modulo 128 Token Ring Stations A problem exists in NCP, whereby NCP always indicates that it is able to receive 128 frames between acknowledgments from a modulo 128 token ring station, when in fact it can only receive much fewer. This results in many unnecessary retransmissions, and can seriously degrade performance. This has been corrected with the following APARs from IBM: o NCP V6 IR25667 5.5 INIT-SELF Rejected with Sense Code 10105006 Under heavy traffic conditions, VTAM can intermittently reject INIT-SELF requests with a sense code of 10105006, when in fact the response should be positive. This has been corrected with the following APARs from IBM: o VTAM V4R1 OW02909 o VTAM V4R2 OW04173 5.6 VTAM ABEND S0C4 at ISTATCTR+1F0 VTAM can intermittently ABEND while writing an internal trace record when the Peer Server has just established the data link connection over X.25 or token ring. This has been corrected with the following APARs from IBM: o VTAM V4 OW06433 6 Known Problems and Product Restrictions Known restrictions existing in the Version 1.5A software are detailed in this section. 12 6.1 Common Trace Facility (CTF) Restrictions 6.1.1 LU Tracepoints Not Supported Because of a CTF limitation in the maximum number of concur- rently declared tracepoints, Peer Server V1.5A does not sup- port tracing on the LU entity (LU tracepoints) as described in Compaq SNA Peer Server Management. Tracing can be done by Transmission Group to trace activity across all sessions on the TG, or on an individual session basis (Session tracepoints). Despite the lack of LU tracepoints, tracing of all sessions belonging to a specific LU can be accomplished as shown in the following CTF command example (LU name "t001"): ctf>start sna lu services lu t001 session * 6.2 Network Management Restrictions 6.2.1 NCL Delete Transmission Group Generates "Wrong State" Exception A Transmission Group that is dependent LU capable and has one or more enabled LU Services dependent LUs referencing it cannot be deleted until the LUs are themselves disabled. An attempt to delete a Transmission Group with active dependent LUs results in a "Wrong State" error exception. "Wrong State" is also pro- duced for failed attempts to delete a Transmission Group when it is not first disabled (entity state OFF and protocol state RESET), and both conditions must be considered when "Wrong State" is returned. An example of the failure follows: ncl> dele sna cp serv t g tg005 Node 0 SNA CP Services Transmission Group TG005 AT 1994-11-23-10:11:07.000-05:00I----- FAILED IN DIRECTIVE: Delete DUE TO: Error specific to this entity's class REASON: Wrong state Description: Wrong state 13 6.2.2 NCL Enable SDLC Link Station Generates "Invalid Parameter" Exception An ambiguous NCL exception of "Invalid Parameter" is produced when attempting to enable an SDLC link station where the sta- tion and/or the parent link have an invalid Send or Receive Frame Size set, respectively. This is most commonly a problem when configuring SDLC for the built-in SCC device, which has an upper limit size of 1021 bytes. Note the exception occurs when enabling the station and not the link. For example, a link configured with a Receive Frame Size of 1024 (too high) is successfully enabled. Its child station, with a Send Frame size of 1000 (legal) incurs an NCL "Invalid Parameter" exception when it is enabled. The solution in this example is to disable and correct the link Receive Frame Size, re-enable the link, and enable the station. An example of the failure follows: ncl> enable sdlc link sdlc-0 sta stn-40 Node 0 SDLC Link sdlc-0 Station stn-40 AT 1994-05-03-13:04:59.000-04:00I----- FAILED IN DIRECTIVE: Enable DUE TO: Error specific to this entity's class REASON: Failure Description: Failure Reason = Invalid Parameter 6.2.3 LocalEntityName Instance Specification With Peer Server V1.0 it was possible to specify a LocalEntityName instance using parenthesis, for example: set sna cp services trans group tg-1 - datalink = (sdlc link foo station bar) In fact, the V1.0 Initialization and Configuration Utility (t21icu) generated this syntax automatically. Due to some changes in NCL processing introduced with DECnet-Plus V1.5, it is no longer valid to specify LocalEntityNames using parenthesis, and doing so generates an NCL syntax error, e.g. "SYNTAX ERROR: No match was found for this string." The Peer Server t21icu has been modified to accommodate the new requirement; however, if you were a Peer Server V1.0 customer and will be running NCL scripts generated with the older t21icu utility (or generated manually), those scripts must be modified in order to work properly with 1.5A. 14 The t21_init_sna_server.log file, located in /var/tmp and cre- ated at the time of Peer Server startup, reveals this error. 6.3 SDLC Datalink Restrictions 6.3.1 Multipoint Full Duplex Configuration Requires TWA The use of two-way simultaneous (TWS) transfer mode (as spec- ified on the SDLC link station) in the full duplex multipoint case is not recommended. A known restriction with RTS/CTS han- dling in the Wide Area Device Drivers (wdd) can cause aborted frame retransmission and, ultimately, link failure. 6.3.2 Using the PBXDI ISA-bus Synchronous Communications Controller o Only those models which support RS-232C or V.35 interfaces (PBXDI-AA and PBXDI-AB) are supported for use with SDLC. o Half-Duplex is not supported. o Transmission of frames larger than 1022 bytes (including SDLC header) is not supported. The SDLC Link Send Frame Size should not exceed 1020 for modulo 7, and 1019 for modulo 127. o The Interface Type attribute for the Modem Connect Line entity does not accurately reflect whether an RS-232C or V.35 interface is currently in use. This inaccuracy lies in the management attribute only and does not actually affect the operation of the controller. 6.4 QLLC Datalink Restrictions 6.4.1 Temporary TGs Lack Automated Call Startup Dependent LU session traffic (for example, 3270 LU2 termi- nal sessions) does not automatically activate a temporary Transmission Group when initiated from the client (Secondary LU) side. This handling is based on the assumption that an SLU not yet activated from the IBM host (that is, no ACTLU yet received) cannot initiate an LU-LU session (using INIT-SELF). There are circumstances with QLLC and X.25 networks where call initiation based on an SLU request for session could benefit from such behavior. 15 6.4.2 Filtername Mismatch Error is Ambiguous As explained in Peer Server documentation, the use of filter names must be consistent between the Compaq WAN X.25 product and Peer Server QLLC entity configurations. If a QLLC link is set up with a filter name that doesn't exist in the X.25 configuration, an Enable of the TG fails with: FAILED IN DIRECTIVE: Enable DUE TO: The target implementation does not support this entity class Should this error occur, CTF may be used to determine if the problem is due to a filter mismatch as shown below (no event message is generated in this case). ctf>start qllc link *,live . . 08:06:31.94| Tx| 14| X_LISTEN_RE| 08:06:31.95|Rx | 16| X_ERROR_ACK (xerrno=-176) Specified . filter does not exist . 6.4.3 QLLC Link and Station Must be Enabled Before TG When configuring a Transmission Group (TG) for use with a QLLC link, the link and underlying link station must be enabled before enabling the corresponding (TG). The enable of the TG fails with an "Facility = DLPI, Reason = 1" exception error if this order is not followed. 6.5 TN3270 Server Restrictions 6.5.1 TN3270 Server Default Port (2301) Used by Insight Manager The default TCP port for the TN3270 Server is the port number following the last defined port number for the last TN3270 con- figuration (or TCP port 2301 if no port numbers are defined). If the default port of 2301 is used and the system is running Insight Manager, port 2301 will be in use by the Insight dae- mon. The error message is: Error binding socket to listening port, errno=48 Workaround: Select another port other than 2301 as the listening TCP port for the TN3270 Server. 16 6.5.2 TN3270 Server Drops Connection when Client Does Not Respond Properly When a client has successfully negotiated the RESPONSES func- tion and then does not respond appropriately when receiving a RU when in definite response mode, the TN3270 server drops the connection. While the client is required to respond to every RU when in definite response mode, the TN3270 server could be more tolerant with such a minor infraction by the client. However, the current version of the TN3270 server is intolerant of such infractions and drops the connection every time the client fails to properly respond. Workaround: If this is happening with your client, you can disable the RESPONSES function when configuring the TN3270 server. 6.6 LLC2 Datalink Performance Issues 6.6.1 FDDI Performance In order to allow high throughput of data via the FDDI datalink, it is necessary to change the llc2 sap link Holdback Timer characteristic attribute from the default value of 500ms to 10ms. To have this value set when the Peer Server is started, it is necessary to change the Peer Server startup NCL file /var/sna/t21_init_sna_server.ncl. The Peer Server uses this NCL startup configuration file everytime the Peer Server starts. Because of the overhead associated with data processing through the UNIX kernel, FDDI performance is a function of sys- tem capability, in particularly CPU speed. (This is also true when using TCP over a FDDI datalink.) Testing has indicated that with the Holdback Timer set to 10 ms, and a properly sized system, FDDI data rates in access of 80 megabit/seconds can be achieved when using Peer Server. (Note: The degradation in performance associated with the Holdback Timer is also manifested in CSMA-CD and Token Ring data links. Although it is more noticeable in FDDI, perfor- mance degradation can be significant in any of the datalinks and the default setting of the Holdback Timer attribute should be changed for all data links.) 17 7 Files Installed/Modified Table 1 lists all the files placed onto the system during the Peer Server installation, or created during configuration. Table_1:_Peer_Server_Installed_Files___________________________ ___Directory______________Filename_____________________________ /dev/streams/ t21_smgd t21cpnm t21ctrl t21mgmt t21llc q25_qllc q25_mgd q25_xpi t21sd_ctrl t21sd_mgmt t21cd_ctrl t21cd_mgmt t21trc t21sdlc t21cdlc t21sess0 t21wadd /sbin/init.d/ t21_sna_server /sbin/rc0.d/ K09t21_sna_server /sbin/rc3.d/ S90t21_sna_server /sys/opt/T21SRVR200/ config.file files /usr/sbin/ t21cad t21cadgas t21mad t21mcd t21smd t21smc q25mad q25mcd 18 Table_1_(Cont.):_Peer_Server_Installed_Files___________________ ___Directory______________Filename_____________________________ t21trcd t21setup tn3270_config tn3270_server tn3270_server_start /usr/share/dna/dict/ t21_server.hlp /var/sna/ q25mcd.conf t21icu t21mcd.conf t21smc.conf t21strsetup.conf t21_15A-0_release_notes /var/subsys/ t21llc.mod t21qllc.mod t21scl.mod t21scl.stanza t21sdlc.mod t21cdlc.mod __________________________t21spd.mod___________________________ Table 2 lists Peer Server configuration files. Table_2:_Peer_Server_Configuration_Files_______________________ ___Directory______________Filename_____________________________ /var/sna/ t21_init_sna_server.ncl t21_init_sna_server.ans ___/usr/sbin/_____________tn3270_conf.nnn______________________ Table 3 lists files the Peer Server uses for logging. Table_3:_Peer_Server_Files_Used_for_Logging____________________ ___Directory______________Filename_____________________________ var/tmp/ t21_init_sna_server.log var/adm/ syslog.dated/date/daemon.log 19 Table_3_(Cont.):_Peer_Server_Files_Used_for_Logging____________ ___Directory______________Filename_____________________________ ___var/adm/_______________syslog.dated/date/kern.log___________ Table 4 lists various operating system or layered product files that are replaced or modified by the Peer Server installation and configuration. Table_4:_Peer_Server_Modified_Files____________________________ ___Directory______________Filename_____________________________ /usr/bin/ ctf /usr/share/ctf/ ctfua_library.c libctflibs.a ___/usr/share/dna/________ncl_help.txt_________________________ 8 Fixes for the Peer Server V1.5A Release The following section describes restrictions and problems present in Peer Server V1.4 that have been fixed in Peer Server V1.5A. 8.1 NCL Wild Card Parsing of Peer Server Entities Now Supported Prior to V1.5, certain combinations of wild cards when access- ing Peer Server entities via NCL did not worked properly. 8.2 Corrected SNA LU Services Authorization Node Characteristic Reset Problem Prior to V1.5, there was a problems with resetting the SNA LU SERVICES AUTHORIZATION NODE characteristic attribute. It was not possible to reset the SNA LU Service Authorization Node characteristic attribute back to the default 0:. value and allow access when the Transport attribute was set to DECnet. And it was not possible to set the SNA LU SERVICES AUTHORIZATION NODE characteristic attribute to the default, by not supply- ing a value with the NCL set command. Due to this problem the "t21mad" daemon process was exiting. 20 8.3 Corrected Independent LU Capability With Passive Listens Problem Prior to V1.5, due to a problem in the Peer Server SNA LU Services module, client "passive" LU-LU session listens (Secondary LU, Independent LU session) failed if the LU was configured as Independent but with a Capability characteris- tic value of "secondary". The nature of the failure was "LU Unavailable". 8.4 Pass Unbinds from Access Routines Now Left Unmodified Previously, the Peer Server mapped all unbinds sent from an Access Routine to a normal unbind before forwarding it to the remote LU. 8.5 Stop Session Management Commands for LU Sessions Now Working Corrected session cleanup problems for dependent and indepen- dent LU's when stop session management commands were issued. Management commands "Stop SNA LU Services LU XXX Session XXX Severity= ???" would not terminate sessions if there was ongo- ing outbound segmentation in the RU. 8.6 Corrected BIND before INIT-SELF-RSP Rejection Corrected BIND reject error when the BIND arrives before the response to INIT-SELF. The BIND was rejected with sense code 0801. This change fixes the problem reported in IPMT case 45709. 8.7 Corrected Transition Address During XID3 Negotiation for SDLC Dial Configuration When SDLC was configured for a dial connection with a station role of "secondary" or "negotiable", XID3 negotiation was not successful. The address transitioned to the correct address and then incorrectly back to the broadcast address FF. This change fixes the problem reported in IPMT case 45828. 8.8 Corrected Routine q25_dlpi_bind_req() Reference to Deallocated Memory The routine q25_dlpi_bind_req() was accessing deallocated mem- ory. This could potentially cause a system crash. 21 8.9 Corrected Routine t21__spam_process_sess_route_inop() Reference to Deallocated Memory The routine t21__spam_process_sess_route_inop() was access- ing deallocated memory. This could potentially cause a system crash. 8.10 Corrected T21MCD Daemon Crash Caused by Reference to Deallocated Memory Set pid to -1 for initialization process after it has com- pleted. Fixes t21mcd crash if UNIX reuses the pid again for a daemon or client process. When the pid is reused MCD finds the pid on the init queue and then tries to free the initent-> data structures again. This change fixes the problem reported in IBM IC notes 473 and 467. 8.11 Corrected T21WAD Crash Caused by Reference to Deallocated Memory On SMP systems there was a window in T21WAD that allowed mblks to be updated on one thread while another thread deallocated the mblks data structure. This change fixes the problem re- ported in IPMT 52192. 8.12 Initialize Data Structure in t21cad_thread Initialize rcvdsc data structure in t21cad_thread. This can po- tentially cause t21cad to crash when trying to free the buffer. This fixes the problem reported in IBM_IC_SUPPORT note 488 and IPMT case 55494. 8.13 Added Check to Catch Thread Wakeups on llc_dispatch Tasks For llc_dispatcher routine. Added check to see if task entry was still on the dispatch queue after dispatcher is woken up. If the task is on the queue call panic(). The task thread was not blocked or a spurious wakeup on the thread occurred. 8.14 Added Correction to Prevent Internal Timer from Stopping Prematurely If multiple Transmission Groups are enabled at once and these transmission groups become completely synchronized in their sending of NULL XIDs, the internal timer the Peer Server main- tains would stop running. This would cause the Transmission Groups to stop sending NULL XIDs. If the Transmission Group 22 was disabled and then reenabled, exactly one NULL XID would be transmitted, instead of a sequence of multiple NULL XIDs. The only recourse was to reboot the system. This change fixes this problem by making sure that the timer isn't prematurely disabled. 8.15 Added correction to Prevent TN3270 Server from Rejecting a Valid BIND Image The TN3270 Server rejected the BIND image if either of the following flags were set: o Byte 6 bit 1 (FM header usage) to an LU1 printer o Byte 15 bit 0 (Query supported) on a printer session The code was modified to accept these flags. 8.16 Corrected Stop Session Commands for Independent LU Sessions On NCL stop session command for independent lu sessions, the UNBIND sent to remote if the session state is greater than or equal to SPAM_C_SCB_PEND_GAP_BIND_RSP and SPUD tgcb is valid. Previously, Peer Server crashed in session cleanup because of inconsistent data structures between SPAM and SPUD. The constraint allows the session to reach a state where it can be successfully cleaned up. 8.17 Made Outbound Session Startup SMP Safe Prior to V1.5, there was a problem activating independent ses- sions in rapid succession from an LU62 server. This was due to SMP. 8.18 Changed t21llc Dispatcher Routines To Use Noninterruptable Thread Blocks Previously, blocked t21llc dispatcher threads were prematurely interrupted before the dispatched routine completed. Modified t21llc dispatcher routines to use noninterruptable thread blocks. This change fixes the problem reported in IPMT 55087 and 54683. 23 8.19 Removed T21_WARNING Message for Timeout Entry from Kernel Log There is a window in Peer Server t21_timeout/t21_untimeout logic when a timer entry is not on the queue. This condition is valid. The warning message was being logged too often and was removed. 8.20 Changed t21llc's Close Routine to An Event Driven Process The t21llc module was not handling disconnects correctly from certain states. This caused Peer Server to crash when the con- nection or listener stream was closed prematurely. This fixes the problems reported in IPMT case 58249 and 58459. 8.21 Corrected SDLC Unacknowledge Frame Check Routine In some cases Peer Server SDLC was retransmitting frames that had already been acknowledged. This caused the link to dis- connect after the max number of requests for frames had been reached. This fixes the problem reported in IBM IC SUPPORT note 562. 8.22 Corrected Queue Macro Calls in Minor Device Allocation Routines The Peer Server minor device routines where incorrectly using queue macro's. In some cases this created invalid queue point- ers which resulted in an infinite search when looking for DACB blocks. This fixes the problem reported in IPMT 58402. 8.23 Corrected LMF Capacity Unit for Local Server Streams Peer Server was not releasing the LMF capacity unit for servers running locally on the same node as Peer Server. This fixes the problem reported in IPMT 59395. 8.24 Corrected LU Old Name String Descriptor String descriptor's used to find LU old name strings where not correctly initialized. This caused case sensitive compares to be done on old style LU names. This fixes the problem reported in IPMT 58571. 24 8.25 Corrected Queue Macro Pointer In Minor Device Allocation Routines A Peer Server minor device routines was incorrectly referencing a queue pointer. This caused the system to crash when secondary gap blocks were inserted between each other. 8.26 Corrected t21cad Thread Stack Overflow Caused By Simultaneous Loss of Client And Gateway Connections Connection status in Peer Server's t21cad event_callback rou- tine were being set to late which caused a thread stack over- flow when the gateway and client connection were lost simulta- neously. 8.27 Corrected Notify RSP RU for Segemented RU If use-notify is set to 1 so that the Peer Server has to turn around NOTIFY RUs from the client with dummy responses there was a bug whereby if the USS screen was segmented and segmen- tation to the client was in progress the NOTIFY rsp RU would never get sent. This caused programs such as the Terminal Emulator to hang. 8.28 Corrected GAP UNBIND Race Condition Problem Corrected handling of GAP UNBIND arrive from user when a GAP UNBIND RQ from Peer Server has already been sent. This causes a race condition where both sides are waiting for an UNBIND OK. Now when a GAP UNBIND RQ has been sent and an GAP UNBIND is received, the GAP UNBIND received is responded to with a UNBIND-OK and an UNBIND +RSP is sent down to SPUD. 8.29 Corrected Premature Inbound Segmentation Fields Update Problem Moved setting of port->inb_msgtype and port->inb_sscp values from SPAM's write put and service procedures to t21__spam_ process_gap_data. This prevents the values from being prema- turely updated in the stream write procedures which can cause GAP message errors during inbound message segmentation. 25 8.30 Corrected Loss of Inbound Segmented GAP Messages The inbound GAP messages were lost when the port state changed during the receipt of segemented GAP data. This problem was fixed, processing all the inbound segmented GAP data irrespec- tive of port state. 8.31 Corrected GAP Message Length When DECnet Connection Lost When a DECnet connection is lost, the last GCI buffer is re- transmitted with a invalid message length. The Peer Server treats parts of the segmented message as an "Uknown GAP Message" and logs a error to the kernel log. Peer Server was relinked to pick up this fix. (PAI030_ECO05) This fixes the problem reported in IPMT 62341. 8.32 Corrected Handling of BINDS In Cross Domain Networks To Prevent Duplicate LFSID Assignment When An LU is Deactivated Free LFSID_IN_USE binds when an LU is deactivated in cross domain networks. This prevents the LFSID from being reassigned when it should have been freed. This fixes the problem reported in IPMT case 65084. 8.33 Corrected Integer Overflow in T21CAD When Using TCP Transport When the TCP transport was used and a BIND with a primary RU size set to zero was received, the Peer Server would set the max RU size to 65336. This caused an integer overflow in the local GCI. This fixes the problem reported in IPMT 66435. 8.34 Corrected CTF trace points in SDLC datalink when Peer Server is restarted When the Peer Server was restarted using SDLC as a datalink, the CTF trace points for the SDLC link and station did not work. Registering of CTF trace points in the SDLC module have been changed to resolve this problem. This fixes the problem reported in IPMT 67253. 26 8.35 Enable XID negotiation restart on XID vector '22' errors. Previously, when a XID vector '22' error code was received, Peer Server would disconnect the link and manual intervention via an disable/enable for the transmission group was needed to restart XID negotiation. A change has been made to automati- cally restart XID negotiation when a XID vector '22' error is received. This fixes the problem reported in IPMT 68024. 8.36 Set correct message pointer before calling dispatcher. In the T21SPD, the env->mp pointer was not being cleared be- fore calling the dispatcher when processing "DISCONNECTS" on XID errors. This caused a crash when trying to free the env->mp pointer since the mp had already been freed prior to the dis- patched routine executing. This fixes the problem reported in IPMT 67432. 8.37 Ignore -RSP's from remote LU's on LU-LU in TN3270. Change server to ignore -RSP's from remote LU's on LU-LU ses- sions. This is to prevent the tn3270 server from trying to recover a failed connection and return back to the USS screen. This fixes the problem reported in IPMT 65411. 8.38 Correctly handle thread cleanup in TN3270. Change call pthread_mutex_destroy() to pthread_cond_destroy() for condition variables. This prevents tn3270 server from from coring because the wrong pthread routine was used to clean up condition variables. This fixes the problem reported in IPMT 66344. 8.39 Fix SNA_S_LOGNOUSE messages in TN3270. Fix problem where TN3270 logs SNA_S_LOGNOUSE messages to the console screen. This was caused by not correctly initializing the log parameters when logmask tracing was enabled. 8.40 Corrected Erroneous Output Associated with the TN3270 Server Prior V1.5, the TN3270 server generated occasional erroneous messages that appear on the user stdout/stderr. 27 Example: ***Routine: snalog_text status = 0x0203F6E2 ***Routine: snalog_text status = 0x0203F6E2 8.41 Fix kernel memory corruption in QLLC module. Incorrect freeing of memory and invalid data buffer sizes in the Peer Server QLLC module was causing kernel memory corrup- tion. Changes were made to correct the memory corruption. This fixes the problems reported in IPMT's 68966, 68866, and 68996. 8.42 Initialize LU pointer for plumb cancel. Initialize the LU pointer at the beginning of the routine to continue outbound session initiation. This prevents crashes when an outbound session is cancelled before the LU session is established. This fixes the crash reported in IPMT69842. 8.43 Do not dispatch X25 messages after shared memory is deallocated. Do not dispatch messages in the XPI driver after the X25 port has been closed. This prevents crashes when PRCI_ABORT's are issued to clear previous calls that have already been cleared. This fixes the crash reported in IPMT69906. 8.44 Change Peer Server LLC2 to handle multiple SABME frames. On some networks, mutilple SABME frames can be generated. Peer Server LLC2 state machines would get out of state when this condition occured. A change was made to handle multiple SABME frames in the Peer Server T21LLC2 layer. This fixes the hang reported in IPMT 71394. 8.45 Check shared memory reference in Peer Server QLLC trace calls. In certain cases the shared memory allocated between Peer Server and Compaq WAN X.25 was referenced when it has al- ready been deallocated in the Peer Server streams trace calls. The problem only occurs with Peer Server xkits with streams tracing. This fixes the crash reported in IPMT 72048. 28 8.46 Allow for Peer Server transmission group shutdown before killing daemon processes. When the script events below are executed, Peer Server QLLC crashes. STOP Peer Server STOP X25 START X25 START Peer Server Changes were made to allow for Transmission Groups to complete shutdown process before killing Peer Server daemon processes. This fixes the crash reported in IPMT 72178. 8.47 Change number of downcredits passed to X25L3. X25L3 hangs if downcredits get below a certain level. Peer Server QLLC was changed to provide additional downcredits to X25L3. This fixes the hang reported in IPMT 69205. 8.48 Fix Peer Server CINIT internal response for terminated sessions. Change routines to correctly handle internal CINIT responses for terminated sessions. Only send SESSEND for Primary Independent LU's. This fixes the kernel memory fault reported in IPMT 74583. 8.49 Fix memory corruption in management access daemon (T21MAD). Memory was prematurely being freed for object id structures in T21MAD which caused the data link sub-entity on Transmission Groups to be undefined. 8.50 Deallocate Peer Server capacity license unit on open stream failures. Peer Server capacity license units were not being deallocated when a outbound session failed to open a SPUD driver stream. This resulted in the depletion of Peer Server capacity license units when there where a number of open failures to the SPUD streams module. 29 8.51 Allow only privileged Users the ability to modify Peer Server SNA Entities. Allow only privileged Users the ability to modify Peer Server SNA Entities. Previously non-privileged Users had modify ac- cess. This fixes the problem reported in IPMT76048. 8.52 Add "keep-alive" option to TN3270. When TN3270 Clients lost connections to the TN3270 Server, the TN3270 port for the connection would remain in use indefi- nitely. The "keep-alive" option will probe for idle connections and disconnect the link after a period of no activity. 30