Patch Name: PHNE_17405 Patch Description: s700_800 10.20 R6.10.20 SNAplus2 Link cumulative patch Creation Date: 99/02/04 Post Date: 99/06/25 Hardware Platforms - OS Releases: s700: 10.20 s800: 10.20 Products: SNAplus2-Link R6.10.20 Filesets: SNAplus2-Link.SNAP2-LINK Automatic Reboot?: Yes Status: General Superseded Critical: Yes PHNE_17405: HANG PANIC PHNE_16758: HANG Path Name: /hp-ux_patches/s700_800/10.X/PHNE_17405 Symptoms: PHNE_17405: (1) 5003441717 The snaperrlog process can be left lying around when the SNAplus2 daemon is not started. Attempting to restart the SNAplus2 software using 'snap start' will fail (because the snaperrlog process is still there from a previous run). (2) 4701413054 System panic - Data Page Fault at nsm_process_record_from_ss+130 (3) 4701399279 The PSI firmware header is not recognized by the snapwhat command. (4) 1653289686 If using a TN3270 (not E) client and hit the clear key while TN Server is presenting an SSCP screen, then the client will lock up. The host may respond with an error message. (5) 1653289603 If using a TN3270 (not E) client and hit the clear key while TN Server is presenting an SSCP screen, TN Server forwards the clear key to the host(sends an empty RU on SSCP-LU session). The host may respond with an error message. PHNE_16758: (1) 4701405316 Updated binaries required for patching the latest R6 release of SNAplus2. (2) 4701399527 Assert errors are produced when the host sends a USSMSG10 screen to a LU configured for LU6.2. The ASSERTS are in fact benign, and will cause no problems with the integrity of the system. The ASSERTs only occur when the USSMSG10 screen is segmented, and greater than around 500 bytes in size. (3) 1653279703 Assert errors logged when RJE workstation is started due to RTM request being received. This has no affect on opperation other than bad entries in the error log. (4) 1653276543 3270 session can hang, even if you stop and restart the snap3270 emulator. If you take a trace of the problem, you will see that a NOTIFY is not sent when the 3270 emulator is stopped or started. (5) 1653273979 Enhancement to allow multiple PUs to be used on a secondary leased link. This means that if an SDLC port is connected to a leased line, you can have multiple LS's active over the port at the same time. (6) 1653267179 An Application can fail to start a remote LU62 transaction, because an invalid user ID is specified on the Attach, when AP_SAME is specified on the ALLOCATE verb. PHNE_15937: (1) 5003398354 If you issue 'snapadmin define_local_lu' for an LU which is already defined, only the attach routing data and the description field are updated - all other parameters are ignored - however, the snapadmin command does not indicate this but gives a successful return message. (2) 4701396374 Node fails to start if TN Client configured with unrecognised hostname. (3) 4701395459 The following assert message is logged to the console, syslog file and sna log files. Assert ips->cont_size >= MU_CONT_SIZE from vtc.c (4) 4701392670 When in client /server configuration, various ASSERT messages recorded in the sna.err log file from the SLIM component, followed often by a crash of the SLIM. This causes general unpredictable behaviour of the system when the master server goes down and is restarted. (5) 1653261669 SDLC link shows DISABLED after restart of SNAPLUS2 daemon PHNE_14392: (1) 4701386227 Unable to start SDLC Eisa cards Defect Description: PHNE_17405: (1) 5003441717 If the kernel initialisation fails, it is possible that the snaperrlog process could hang - waiting for a signal from the kernel which never arrives. Resolution: A code change has been made to ensure that ,if the kernel initialisation fails, a failure notification is sent to the snaperrlog process so it can exit cleanly. (2) 4701413054 Small timing window when there is an empty list of LULU control blocks when processing SSCP_INIT_SIGNAL_NEG_RSP ISP. Resolution: Code changed to check whether LULU list is empty before trying to obtain first element of it. (3) 4701399279 The PSI f/w header string was not changed with the release of SNAplus2 as the f/w is common to both SNAplus & SNAplus2. Resolution: - a new what string for the NIO firmware - a new what string and a new compilation format for the EISA firmware The ']' character has been added at the beginning of each PSI firmware library header line so that the header can be recognized by the snapwhat command. (4) 1653289686 TN3270 cliemt was locking up when the clear key was entered because TN Server was passing the clear command to the Host instead of processing it locally (as is done in the Motif 3270 emulator for example). Resolution: Code changed to add check and special handling for the clear key at the beginning of the TN Server SSCP inbound MU processing. (5) 1653289603 TN3270 client was receiving SSCP datas when the clear key was entered because TN Server was passing the clear command to the Host instead of processing it locally (as is done in the Motif 3270 emulator for example). Resolution: Code changed to add check and special handling for the clear key at the beginning of the TN Server SSCP inbound MU processing. PHNE_16758: (1) 4701405316 Updated binaries provided for combined patching of latest R6 release ,as documented in SR text. (2) 4701399527 A Code change has been made to prevent Assert errors occurring when a large USSMSG10 is received for an LU6.2 session . The maximum amount of data permissible on the SSCP screen has been increased to 2048 bytes, to ensure segmented data on SSCP screen handled correctly. (3) 1653279703 Code change made to fix a problem with Assert errors being logged when an RJE workstation is started. Code changed to correct the ASSERT - it should only be produced if an application has opened the SSCP session and is listening for RTM requests (RJE does not do this so it should not be logged as an error). (4) 1653276543 Code change to prevent 3270 session hang, due to NOTIFY not sent. The fix applied is to ensure that any pending NOTIFY requests are flushed from the CH queue in the APPN node when a CLOSE_SSCP message is received (indicating that the emulator has been stopped). (5) 1653273979 Enhancement to allow multiple PUs to be used on a secondary leased link. This means that if an SDLC port is connected to a leased line, you can have multiple LS's active over the port at the same time. (6) 1653267179 The problem is basically that if you specify AP_SAME on the ALLOCATE verb but did not configure user validation, then we will send a user ID consisting of 10 NULLs. A code change has been made, and the following behavior applies when AP_SAME is used : case 1: a TP on Unix invokes a remote TP: the outgoing Allocate will contain a userID subfield, set to the Unix user ID the TP is running under; case 2 :a TP on Unix invokes several remote TPs:see case 1; case 3 : multiple conversations, where an INVOKED TP issues an ALLOCATE:in that case, the outgoing Allocate will include the same level of validation which was on the ATTACH that invoked that TP. PHNE_15937: (1) 5003398354 Code changed to ensure that if the user specifies any other parameters, they match those used on the initial define. Produce an error code otherwise. (2) 4701396374 Code changed to allow the node to start if it finds a TN Client configured with unrecognised hostname, but generates an error log which tells the user of the failure. (3) 4701395459 This was an incorrect ASSERT which has been removed. It is a benign problem, but produces annoying error logs and console messages. (4) 4701392670 The LAN logger component (which handles central logging) incorrectly registered itself with the service manager as a server. This means that a server could end up twice in the service table (for example, once as a backup, then again as a master server). This lead to extremely unpredictable and unreliable client/server operation. Code change made to prevent this incorrect registering. (5) 1653261669 Send a signal to the host when firmware is ready (backplane and frontplane are initialized) Remove debug trace from msgbuf (opt1:) PHNE_14392: (1) 4701386227 Fixed problems in SDLC driver and firmware. SR: 5003441717 5003398354 4701413054 4701405316 4701399527 4701399279 4701396374 4701395459 4701392670 4701386227 1653289686 1653289603 1653279703 1653276543 1653273979 1653267179 1653261669 Patch Files: /opt/sna/conf/lib/libpsi0.a /opt/sna/conf/lib/libpsi1.a /opt/sna/conf/lib/libsixd.a /opt/sna/conf/lib/libsixl.a /opt/sna/conf/lib/libsixs.a /opt/sna/sdlc.dlf /opt/sna/sdlc.pbs /opt/sna/bin/snaptnsrvr what(1) Output: /opt/sna/bin/snaptnsrvr: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ ]R6.10.20.101 SNAplus2 R6 TN Server ] (PHNE_17405 : 99/01/11 17:27:05) ] /opt/sna/conf/lib/libpsi0.a: ]R6.10.20.100 SNAplus2 R6 NIO PSI driver ] (10.20.R6 (DART 41): 98/07/17 13:16:55) ] /opt/sna/conf/lib/libpsi1.a: ]R6.10.20.100 SNAplus2 R6 EISA PSI driver ] (10.20.R6 (DART 41): 98/07/22 10:36:54) ] /opt/sna/conf/lib/libsixd.a: ]R6.10.20.100 SNAplus2 R6 NDLC to DLPI Mapping ] (10.20.R6: 98/08/17 14:16:43) ] /opt/sna/conf/lib/libsixl.a: ]R6.10.20.101 SNAplus2 R6 SDLC in the Kernel ] (PHNE_16758 : 98/10/13 15:08:41) ] /opt/sna/conf/lib/libsixs.a: ]R6.10.20.107 SNAplus2 R6 Router in the kernel ] (PHNE_17405 : 99/01/19 17:34:17) ] ]R6.10.20.105 SNAplus2 R6 APPN kernel library routin es ] (PHNE_17405 : 99/01/19 17:29:21) ] /opt/sna/sdlc.dlf: ]SNAplus2 EISA FW v2.5 ](99/01/07 15:26:09) /opt/sna/sdlc.pbs: ]SNAplus2 NIO FW v2.1 ](98/11/13 11:58:22) cksum(1) Output: 2390782579 204416 /opt/sna/bin/snaptnsrvr 2855579278 64504 /opt/sna/conf/lib/libpsi0.a 3528364603 46800 /opt/sna/conf/lib/libpsi1.a 2674665038 172144 /opt/sna/conf/lib/libsixd.a 54941538 360416 /opt/sna/conf/lib/libsixl.a 37998968 3023652 /opt/sna/conf/lib/libsixs.a 3269251168 105244 /opt/sna/sdlc.dlf 3918812582 172212 /opt/sna/sdlc.pbs Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHNE_14392 PHNE_15937 PHNE_16758 Equivalent Patches: None Patch Package Size: 4120 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_17405 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHNE_17405.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_17405.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. By default swinstall will archive the original software in /var/adm/sw/patch/PHNE_17405. 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_17405.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_17405.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: Stop SNA daemon before installing patch (snap stop). After installing the patch start the SNA daemon (snap start).