NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: SAA014.EXE; NetWare 1.3B Maintenance README FOR: SAA014.EXE NOVELL PRODUCTS and VERSIONS: NetWare for SAA 1.3B ABSTRACT: SAA014.EXE & SAA008.EXE, together, are the current patch for SAA 1.3B and must be used together. The patch is recommended for all SAA 1.3B sites and all SAA 1.3 sites that have installed the PTF410 series. Do Not Apply to COMMEXEC & NWSAA versions below 1.3.42! Check Product Options Under "Load Install" First! NOTE: SAA008 HAS NOT changed. Please apply SAA014 & SAA008 before calling Tech Support. If you are using SAA013 without problems, do not download SAA014. ----------------------------------------------------------------- DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION. ----------------------------------------------------------------- SYMPTOM: General Symptoms 1. Not compatible with NetSoft and DCA emulators. 2. Unexpected disconnects. 3. Failure to attach with Password Encryption turned on. 4. Multiple line RUNCMD responses limited to 110 characters. 5. Problems gathering statistics through SSM. 6. Problems using the verb CNOS. 7. If a session was terminated while the DCA emulator was using mod 5, subsequent users would get 4B? on the OIA line when trying to get a new session. 8. Definite response with Pacing ON, caused sense code 200A. 9. Test frames being sent causing the link to reset. 10. 3174 X.25 RPQ failure to connect with NWSAA. 11. Several different state transition errors; event=1 state=5 & event=7 state=7. 12. Several LU6.2 problems, including send error in recv state problems. 13. Failure to respond to a Null XID when configured as a PU type 2.1 over a SDLC link. Symptoms Related to R3SDLC & SDLCS 1. Server hang in a multidrop environment, if another device kept RTS high. 2. RTS toggled to Low even if CSCON was configured to set it constantly High. 3. Spurious interrupt/missed poll messages. 4. Pressing Attention, during a Logoff could result in a Profile Unload. 5. Failure to re-establish connection with host. 6. Failure to respond to a DISC from NCP. 7. "DLCI ERROR:unable to attach to a logical board" when loading both a PU2.0 and a PU2.1 profile to the same board. 8. Failure of link to come up. Symptoms WITH SNALINKS 1. Even when SNALINKS was configured for Auto Connect, after a link was downed, the connection might not be brought up automatically. 2. Incompatibility with MPR 3.0. Symptoms with SAACOPY 1. "Unable to open file" 2. Downstream LUs unable to establish host sessions. 3. Unable to copy between a 1.3 and a 1.4 Communication Server. 4. "No more WCM connection" 5. "Error on Attach" 6. After a profile was copied onto a NetWare 4.01 server, an attempt to run CSCON from the same NetWare drive would cause the workstation to hang. 7. The use of SAACOPY, then CSCON, could result in the DOS prompt being changed to "%p". 8. SAACopy set the wrong model number. Symptoms with AS/400 1. Unable to access Shared Folders. 2. Invalid XID messages on the console. Symptoms Related to OS/2 1. Lack of OS/2 DOS Box support for CSCON. 2. Problems using OS/2 Connection Manager. Symptom Using Netview Server crash when NetView issues a REQMS. Symptom using Data Link Switch/Custom link Errors when session data spanned multiple data blocks. Symptoms When Using MPA Boards 1. System crash when using MPA driver and PS/2 model 9585. 2. MPA driver not compatible with servers over 16 meg of RAM. New Features 1. Compatibility added for the new "LINKSNA", due out in the near future. 2. Compatibility added for the new data link switch product. SOLUTION: Apply SAA014 and SAA008 Patch History --------------------- SAA014 supersedes SAA001, SAA003, SAA004, SAA007, and SAA013. SAA001 contained CSMPX.NLM dated 2/17/94, which randomized CSLIST. Such randomization is not desirable at many sites. SAA001 and SAA002 superseded PTF 443, PTF 435 and PTF 438. These files also replace the NetWire file SAACPY.EXE that introduced the problem of restored downstream LUs being unable to establish host sessions and PTF 431 that was the first PTF for SAA 1.3B. SAA008 superseded SAA002. Solution Specifics: (for some of the symptoms listed above) GENERAL 1. CMTCP.NLM modified to handle multiple QELs in a single packet. This was done for compatibility. 4. RUNCMD responses will now be limited to 220 characters. If in excess of 220 characters, will be truncated. Single line RUNCMD responses will be broken down into 220 character chunks. 6. When changing the number of sessions (CNOS) from X to Y, must be at 0 first before the change can be made. 9. DLM.NLM and LLC8022.NLM modified so that test frames will be turned around once the link is established. 12. Many fixes for LU6.2, including adding sense code for FMH-7 10086040,CNOS fixes, chaining and bracketing fixes,etc. 13. DLM.NLM modified. SOLUTIONS RELATED to R3SDLC & SDLCS 5. R3SDLC and SDLCS were modified so that DTR is not toggled when SAA receives a disconnect command in a leased line configuration. 8. SDLCS.NLM modified so that the link will no longer fail to come up when a DISC immediately follows a SNRM/UA. SAACOPY 4. Connections will now clear. They had not been, and as new connections were made the maximum number would be reached. 8. Model numbers will now transfer correctly. AS/400 1. Corrected by adding support for the "query conversation state" service verb. OS/2 2. WCM.DLL modified. USING NETVIEW DLM.NLM modified so that a server crash will no longer result from a REQMS resulting in a DLM_GET_STATISTICS or DLM_RESET_STATISTICS. DATA LINK SWITCH/CUSTOM DATA LINK Support provided for data spanning multiple data blocks, instead of being required to remain in one data block. This also effects Custom data link configurations as well. Self-Extracting File Name: saa014.exe Files Included Size Date Time ..\ SAA014.TXT (This file) AS400PCS.NLM 18642 10-22-93 4:41:38 pm CMTCP.NLM 39644 12-15-93 9:09:44 am CPIC_SAA.NLM 32756 1-10-94 2:01:16 pm CSCFG.EXE 113445 4-18-94 10:07:38 am CSCON.EXE 41183 4-18-94 10:05:36 am CSCONFRM.HLP 4425 7-23-92 4:26:16 pm CSINSTAL.HLP 2336 3-9-93 6:44:30 pm CSINSTAL.NLM 802 6-10-93 11:28:56 am CS_ERR.DAT 9451 2-26-90 6:52:08 pm CS_HELP.DAT 3722 9-1-89 12:00:00 pm CS_MSG.DAT 24812 12-14-89 4:52:28 pm DLM.NLM 107523 11-15-94 10:21:36 am LLC8022.NLM 34606 9-1-94 11:02:12 am MPASDLC.LAN 10809 8-4-94 11:37:06 am NOVELLRT.OVL 6678 10-22-93 4:39:36 pm NWSAA.001 855 11-17-94 8:46:56 am NWSAA.NLM 367462 11-4-94 3:49:56 pm NWSAA.RMV 1839 7-7-94 6:20:16 pm PBTRACE.NLM 2735 4-19-94 3:00:14 pm PB_NWSAA.NLM 28622 4-19-94 3:00:06 pm PINSTALL.NLM 87963 6-10-93 11:29:04 am PRODUCT.DEF 434 11-2-94 5:40:22 pm R3SDLC.LAN 22551 4-29-94 9:18:46 am ROUTE.NLM 5033 6-9-94 6:11:48 pm SAACOPY.EXE 262121 9-26-94 3:55:22 pm SDLCS.NLM 40905 4-19-94 3:01:46 pm SMA.NLM 28138 3-28-94 2:36:46 pm SPC_ERR.DAT 9451 2-26-90 6:52:08 pm SPC_FRM.FRM 1387 10-7-92 11:24:18 am SPC_FRM.HLP 67975 10-11-93 5:15:44 pm SPC_HELP.DAT 3722 9-1-89 12:00:00 pm SPC_MSG.DAT 24812 12-14-89 4:52:28 pm STRNRTR.EXE 41757 10-22-93 4:39:06 pm WCM.DLL 33309 3-8-94 10:48:30 am Installation Instructions: 1. Although there are diferences between SAA014 and SAA013, they report the same version to the installation program. Therefore, an attempt to install SAA014 over SAA013, will result in an error message. However, if you are using SAA013 without problems, there is no reason to put SAA014 on top of SAA013. 2. Make sure you have the latest NIC drivers for your system. They must be ODI 4.0 compliant!. 3. If you have not already done so, install the LANDR3.EXE patch and the STRTL3.EXE patch. 4. Install SAA014, ONLY IF you have NetWare for SAA 1.3B or have installed the PTF410 series. 5. If you have Novell's "MultiProtocol Router 3.0" installed on the server with NetWare for SAA, do the following: | a. Save your current LLC8022.NLM before installing SAA014. | b. After following the instructions below to install SAA014, copy the old LLC8022.NLM over the new one which SAA014 will automatically put in place. 6. Put SAA014.EXE into an empty directory, called SAA014, on a hard disk or network drive. Make sure the directory path is available to the server(s) you are updating. 7. Unzip SAA014.EXE. SAA014 8. Have you ever applied SAA008? If you have, you are currently at version 1.3.46. If you are currently at version 1.3.46 skip to step #9. Do NOT apply SAA008 a second time. Put SAA008.EXE into an empty directory, called SAA008, on a hard disk or network drive. Make sure the directory path is available to the server(s) you are updating. 9. Unzip SAA008.EXE. SAA008 10. Do a CSDOWN so that COMMEXEC will not be running. 11. LOAD Install. 12. Select Product Options. 13. Press . You should select the directory path created above ie, sys:\saa014 or c:\saa014 14. Select server to update. 15. Press . 16. Wait for the update to complete. 17. Press . You should see NWSAA 1.3.60 18. If you have never applied SAA008, press .select directory path for SAA008 ie, sys:\SAA008 or c:\SAA008. 19. Select the server to update. 20. Press 21. Wait for the update to complete. 22. Press . You should see COMMEXEC 1.3.46. ***!!! !!! IMPORTANT NOTE: Never manually copy COMMEXEC.NLM or NWSAA.NLM into the system. The install scripts must be used! If you copy in manually, the version information will be incorrect. If you have ever applied an ETF that required copying NWSAA.NLM into the system directory manually, please recopy the NWSAA.NLM that was on the system just prior to installing the ETF, and then be sure the version number under Product Options for NWSAA is lower than the one in this patch. If an ETF was applied with an install script, you do not have to recopy NWSAA.NLM (however, be sure the version you have is lower than the one in this patch). If the version number is equal than or greater than the one to be installed by this patch, the install will fail. !!!****** 22. Unload and Reload LLC8022.NLM, (this will load the new LLC8022.NLM) 23. Reload COMMEXEC. 24. Reload the profile. 25. Copy the new STRNRTR.EXE and NOVELLRT.OVL over any copies that exist outside of SYS:\SYSTEM\NWSAA\AS400. 26. Read SAACOPY.TXT for instructions on the use of SAACOPY. Please note that there was a patch to SAACOPY that created an incorrect directory. The INCORRECT PATH is SYS:\SYSTEM\SAACOPY. Please delete the contents and the directory. The CORRECT directory path is SYS:\SYSTEM\NWSAA\SAACOPY. SAA014 will install the files here. 27. The CONFIG.SYS for the workstation from which you run SAACOPY must contain FILES=20 (or greater). If it does not, you will receive the following error message when you try to back up or restore SAA service files: MESSAGE Unable to Open File 28. If you are using the MPA board: The new MPA driver uses interrupt 3 and is non-shareable, run reference setup to make sure no other device uses Interrupt 3! 29. If you are using the MPA board with OS/2: Load MPASDLC Name=board mode=ns 30. If you will be using 3174 X.25 RPQ, copy the new ROUTE.NLM to the SYSTEM directory and load it with the GBR option. (specifies that all General Broadcast frames are to be sent as All Routes Broadcast Frames.) Note: even if you will not be using 3174 X.25, copying the new ROUTE.NLM is advised. (the same ROUTE.NLM contained in SROUTE.EXE and included here as a convenience). ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. -----------------------------------------------------------------