Patch Name: PHNE_6037 Patch Description: s700_800 10.0X SNAPlusLink (SNAP-LINK) R4 cumulative patch Creation Date: 95/09/07 Post Date: 95/10/24 Hardware Platforms - OS Releases: s700: 10.00 10.01 s800: 10.00 10.01 Products: SNAplusLink R4 Filesets: SNAP-LINK.SNAP-LINK Automatic Reboot?: Yes Status: General Release Critical: No (superseded patches were critical) PHNE_5444: PANIC Path Name: /hp-ux_patches/s700_800/10.X/PHNE_6037 Symptoms: PHNE_6037: (1)4701292557 When you use "Ctrl-C" to interrupt a COV program in the middle of a COV, you get to an unrecoverable state. The The current COV is terminated, but no new COV can do anything because the current COV has resources still. (2) 1653140210 Using the APPC verb Receive_Allocate, the returned parameter Mode_Name is in ASCII and should be in EBCDIC as stated on page 5-7 in the APPC Programmer's Guide. (3) 1653132977 We are trying to implement a TN client /server solution. However, after leaving an application (e.g., CICS , the TN client is disconnected from the TN Server instead of returning to the Application Selection Menu. This is an enhancement request to change the behaviour of the SNAplus TN server so that it does not disconnect the TN client when closing a session with an host application. PHNE_5521: (1) 1653127431 TN3270 client is unexpectedly disconnected from an SNAplus TN Server connection. PHNE_5444: (1) 5000712018 Customer has a large T500, with Unix 10.0 and SNAPlus Release 4. They are using LU6.2 with 249 LUs configured When the SNAplus links (connections) are started the system panics. Defect Description: PHNE_6037: (1)4701292557 When you use "Ctrl-C" to interrupt a COV program in the middle of a COV, you get to an unrecoverable sto force TN Server to treat an UNBIND 3201 as if it is an UNBIND 3202. (2) 1653140210 Using the APPC verb Receive_Allocate, the returned parameter Mode_Name is in ASCII and should be in EBCDIC as stated on page 5-7 in the APPC Programmer's Guide. (3) 1653132977 What is desired is to have the ability to configure TN Server to hold open the telnet session to the TN3270 the LU that was previously in use. In terms of HP's TN Server, this means the action taken when an UNBIND 3201 is received would have to change. Currently, when an UNBIND 3201 is received, TN Core gets a CLOSE SSCP from PU2.1, then sends a CLOSE TNI to TN Stub, which then closes the telnet socket connection. It appears that what the customer is asking for is to be able to force TN Server to treat an UNBIND 3201 as if it is an UNBIND 3202. PHNE_5521: (1) 1653127431 The customer application uses a menu-driven interface to connect users to the appropriate service. In SNA terms, there are actually two LU-LU sessions that are required to make the connection. The first LU-LU session brings up the menu, and when the user picks one of the menu options, a new LU-LU session is started that is the chosen application. The unique thing about this situation is that TN Server must hold open the socket connection to TN3270 so that the second LU-LU session can get started. TN Server supports this function in that it holds open a socket connection if the first session is disconnected by the IBM host with a '3202 UNBIND'. This is a termination of a session that says 'Another session is about to start, so hold on.' TN Server was holding the socket connection open, but an internal variable that determines the state of the send/receive bracket was not set correctly. So when the IBM started sending data, TN Server complained about a protocol violation (-RSP to a BID with sense code 0813) and shut down the session. This caused the TN3270 application to terminate unexpectedly. PHNE_5444: (1) 5000712018 The system panic is in one of the PU2.1 routines. The panic is on an 800 MP machine running SDLC in full duplex mode. The system panics when the customer tries to activate 220 links (connections) from snapmanage. SR: 5000712018 4701292557 1653140210 1653132977 Patch Files: /usr/conf/lib/libsix1.a /usr/conf/lib/libsixet.a /usr/conf/lib/libsixn.a /usr/conf/lib/libsixtk.a /opt/sna/sdlc.dlf what(1) Output: /usr/conf/lib/libsixet.a: A.10.00.001 SNAplus R4 802.3 (PHNE_6037: 95/09/07 10:01:27) /usr/conf/lib/libsixtk.a: A.10.00.003 SNAplus R4 Token Ring (PHNE_6037: 95/09/05 15:00:02) /usr/conf/lib/libsixn.a: A.10.00.002 SNAplus R4 TN Server Core (PHNE_5521: 95/08/25 16:58:37) /usr/conf/lib/libsix1.a: A.10.00.003 SNAplus R4 PU 2.1 (PHNE_6037: 95/09/05 14:58:01) /opt/sna/sdlc.dlf: A.10.00.001 SNAplus EISA FW cksum(1) Output: 402599858 183084 /usr/conf/lib/libsixet.a 3436115023 182060 /usr/conf/lib/libsixtk.a 3319445916 72600 /usr/conf/lib/libsixn.a 2802115400 900272 /usr/conf/lib/libsix1.a 3928612951 70516 /opt/sna/sdlc.dlf Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHNE_5444 PHNE_5521 Equivalent Patches: None Patch Package Size: 1440 Kbytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHNE_6037 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHNE_6037.depot 5b. For a homogeneous NFS Diskless cluster run swcluster on the server to install the patch on the server and the clients: swcluster -i -b This will invoke swcluster in the interactive mode and force all clients to be shut down. WARNING: All cluster clients must be shut down prior to the patch installation. Installing the patch while the clients are booted is unsupported and can lead to serious problems. The swcluster command will invoke an swinstall session in which you must specify: alternate root path - default is /export/shared_root/OS_700 source depot path - /tmp/PHNE_6037.depot To complete the installation, select the patch by choosing "Actions -> Match What Target Has" and then "Actions -> Install" from the Menubar. 5c. For a heterogeneous NFS Diskless cluster: - run swinstall on the server as in step 5a to install the patch on the cluster server. - run swcluster on the server as in step 5b to install the patch on the cluster clients. The cluster clients must be shut down as described in step 5b. By default swinstall will archive the original software in /var/adm/sw/patch/PHNE_6037. If you do not wish to retain a copy of the original software, you can create an empty file named /var/adm/sw/patch/PATCH_NOSAVE. Warning: If this file exists when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. It is recommended that you move the PHNE_6037.text file to /var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHNE_6037.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: Stop SNA daemon before installing patch (snapstop daemon). After installing the patch start the SNA daemon (snapstart daemon).