Visit our Home Pages on the Internet: NetWare for SAA http://www.software.ibm.com/network/commserver/support ====================================================================== DATE: 10/12/99 DESCRIPTION: Cumulative Service Pack for IntranetWare for SAA Ver. 3.0 README FILE FOR: IntranetWare for SAA Version: 3.0 PTF NUMBER: SAA30020 APAR NUMBER: JR13823___ This package contains APAR fixes to the product above. This package can be distributed to any one who has a license for this product. ====================================================================== =============== PREREQUISITES : =============== None =========================== Function Added via PTF10 : =========================== Self Test Support Added -- Configuration and Sessions Add HPR for Frame Relay Provide ODI 3.31 compliant SDLCTSM.NLM RTP data collection fixes Allow custom protocol stack name to be mixed case NW2000.LDI and FRTSM.TLI now Installed Improve performance for 3270 LUA over TCP/IP Transport Trap adding additional Host Print Licenses Improve APPC/PC Attach_PU return_control behavior for receive_immediate =========================== PROBLEMS FIXED in this PTF: =========================== Apar # Description ----------------------------------------------------------------------------- JR11489 TN3270 connections are denied JR12623 8 character pool names now give access (TN3270 support for Pool Names) JR12344 Netsoft Router 5.10N fails with a security error when trying to activate the link with no password or userid. JR12360 0812000D sense code with link BTU size set to 64K JR12462A Allocate problems with Dependent LU 6.2 JR12487 Abend in the STREAMS.NLM called by NWTN3270.NLM. JR12513 Unable to forward QEL/MU packet to client JR12518 LLC8022 for NW 3.x platforms only (NW 3.x compatible version of LLC8022) JR12525 NWSAA Attach fails resulting in FMH 07 with sense 084B6031. Dependent LU support added to APPC/PC attach manager JR12553 Security violation at installation time JR12607 Print Job hangs due to IWAPI SHUTD/SHUTC processing JR12699 Page fault exception in nwtnSendAckGetData JR12725 SDLC line drops due to failure to ack after 7th packet JR12736 Global trace detailed information incorrect for SLU capabilities in NOTIFY JR12740 Dependent LUs are incorrectly displayed in CSSTATUS JR12752 Server abending on Commexec module JR12810 Fix trap in CMTCP JR12862 IWSAA3.0.10 server hangs for hours JR12867 Display dedicated LU name in host LU list JR12868 Correct max_ifrm_rcvd for V3 links with incorrect defaults. JR12889 Uptime is incorrect in CSSTATUS for an LU with connection type of CSA_HLLAPI (such as Host Print) JR12898 Cannot start new sessions in AS400PCS JR12903 Ensure that the TN3270E client doubles FF in sequence number so that the server will not hang. JR12907 CommExec MXHNG process causes the server to freeze. JR12916 SAA 3.0 should issue 0813 instead of 081B if BID in bracket JR12931 PFPE abend in NWTN3270.NLM -- running process CommExec - LCPRM JR13151 Bracketing error JR13442 COMMEXEC - Unable to use server configurator when user is under country object. JR13471 Country code not allowed in CREATSAA. JR13498 Stream head queues associated with PCS file descriptors become disabled JR13620 NWTN5250 drops 2 bytes at the end of a packet JR13689 SMA not freeing LU's. CSSTATUS showing LU's are available. JR13690 QEL Clients causing 0x081B when upgrading from NWSAA 2.0 to IWSAA3.0 JR13764 AS400PCS client DEALLOCATE causing ABEND in THREADS.NLM JR13781 Invalid use of CDI by host application causing QEL client to hang. ========================== Comments: ========================== SAA30020 supercedes SAA30010. In addition, it contains all the above mentioned fixes. It needs to be installed on top of IWSAA 3.0, and may be installed on top of PTF10. SAA30020 contains a rewrite for the SMA NLM. The Service Mapping Agent (SMA) component has been redesigned to provide greatly improved performance and reliability. This is useful under heavy load conditions occurring as a result of hot standby rollover or initial server startup. SMA aids clients in locating and establishing connections with Communication Executive (COMMEXEC) platform services. ========================== Global Trace Changes: ========================== The syntax to start and stop the global trace from the command line has changed from IWSAA 3.0 PTF 10. Old syntax: iwtrace file=xxx record=xxx size=xxx New syntax: saatrace tracefile=xxx tracerecord=xxx tracesize=xxx To stop the trace: saatrace traceoff ========================== INSTALLATION INSTRUCTIONS: ========================== SAA30020.EXE is a self-extracting file containing the shipped executables. The ability to remove or "back off" an SAA PTF from the NetWare server is included with this PTF. To back off a PTF means that the system will be returned to its state prior to installing PTF. All files overwritten or removed by the PTF are restored from copies saved during PTF installation. Likewise, all files created by the PTF will be removed. The PTF removal process is documented below. Note that the process to remove the entire product is not changed by this feature. If the entire product is removed it removes all PTF's and their history from the system as well. Hence, BE CAREFUL to follow the PTF removal process if you only want to back off the last PTF installed. The PARTS LIST is as follows: The self-extracting .EXE file. SAA30020 in turn contains: SAA30020.TXT (which is this file) EXPAND.BAT 30020.EXE A list of the files that are included in this PTF can be found in the file named "FILES.LST" after running the EXPAND batch file. NOTE: It is a good practice to back up the configuration files prior to applying service to your server. *********************************************************************** IMPORTANT: Never manually copy COMMEXEC.NLM or NWSAA.NLM into the system. The install scripts MUST be used!!! *********************************************************************** ___________________________________________________ 1. SAA30020 will only install on top of Version 3.00.00 or Version 3.00.10 of NWSAA! It will not work on any BETA version of NWSAA 3.0! 2. If you have not already done so, make sure the latest operating system patches are applied to your system. 3. Make a directory called 30020, on a hard disk or network drive. 4. Put SAA30020.EXE into the 30020 directory you just made. 5. "Explode" SAA30020 by executing it (type SAA30020 and press ). This will place the following files in the SAA30020 directory: 30020.EXE EXPAND.BAT SAA30020.TXT 6. Run the batch file (type EXPAND and press ) ================================= Server Installation Procedures: ================================= 1. Stop NetWare for SAA. 2. From the server console type LOAD INSTALL and Press . 3. Select "Product Options" and Press . 4. Select "Install a product not listed" Press . 5. Press to enter the path on the server of the location of the installation files. For example: SYS:\30020 or C:\30020 6. Select the server to update. 7. Press . 8. Select the Language to Install. NOTE: If selecting more than one language, highlight each language using the key. 9. Press . 10. Wait for the update to complete. 11. Read the SERVER INSTALLATION -- WARNING section for X25*.NLM information and Frame Relay information before continuing. 12. Restart the server before loading NWSAA; this will activate the new system modules copied over during installation. =============================== SERVER INSTALLATION -- WARNING: =============================== There are several issues to beware of when installing this PTF: 1. If you have previously installed MPR, BorderManager or the ODI33x patch, compare the X25*.NLM files in the SYS:SYSTEM\NWSAA\BACKUP directory with those in the SYS:SYSTEM directory. If the ones in the BACKUP directory have more recent dates, copy them back to the SYS:SYSTEM directory. 2. If you have installed BorderManager or the ODI33x patch and want to use HPR on Frame Relay, you will need to install an update to the MPR modules which supports the HPR TID. (The file is nwsaahpr.exe -- High Performance Routing for SAA (TID number 2948899). 3. For NetWare 4.11, when installing Novell's service pack 6 or greater, pay careful attention to the readme file for the Service Pack to avoid connectivity problems. ============================================ NetWare for SAA Configuration Install Notes: ============================================ The NWSAA Server Configuration tool which was orginally installed with the base product using NWSAA Management Setup needs to be updated. Two new files, SAACFG.EXE and SAACFMRI.DLL, are included in this PTF. To apply this update on the client machine on which the NWSAA Server Configuration was originally installed, two options are available: (1) Uninstall the NWSAA Server Configuration from the Client using the UNINSTALL shipped with the base product. Map a drive to the server on which the PTF is installed. Follow the installation procedures to reinstall the NWSAA Server Configuration from the mapped server. (2) Use the SETUP.EXE program in the SAAMGMT directory of the PTF. Execute SETUP.EXE on the client machine on which the NWSAA Server Configuration was originally installed. The setup program will locate SAACFG.EXE and SAACFMRI.DLL, rename the files to SAACFG.0XE and SAACFMRI.0LL, and copy the new files in their place. ============================================ ***** PTF Removal Procedure and Notes ***** ============================================ Two types of PTFs are identified: (1) Cumulative - These PTFs include all prior PTFs, backwards to the initial release of the product. Their names end in a suffix of '0' (e.g. SAA30020). They require only the base product. This PTF contains a Cumulative PTF. (2) Delta - These PTFs include only those PTFs backwards to the last cumulative PTF. Their names end in a suffix which contains the number of the last cumulative PTF, plus the number of the delta PTF (e.g.,SAA30012). They require the prior cumulative PTF. A Delta PTF does NOT exist for NWSAA 3.0. An inventory of system information is maintained such that the user is able to perform any of the following operations: * Remove the most recently applied PTF (cumulative or delta). * Remove all delta PTFs back to the most recently applied cumulative PTF. * Remove all PTFs back to the base product. The most recent PTF (e.g. SAA30020) is removed using these procedures at the server console: 1. Type load install and press Enter key. 2. Select Product Options and press Enter key. 3. Select View/Configure/Remove installed products and press Enter key. 4. Select the product from the list of currently installed products and press Enter key. This causes a recent history of applied PTFs to be displayed, with the last (most recent) PTF highlighted at the top of the list. 5. Press the Delete key to remove the most recent PTF. (Pressing the Enter key instead of Delete will display a list of files modified by the PTF). 6. Choose YES at the prompt to confirm deletion. 7. Wait for the deletion to complete. 8. To remove the SAACFG.EXE which is shipped with the PTF, the SETUP.EXE from the base product must be run to replace the SAACFG.EXE shipped with the PTF. ==================== CONTACT FOR Support: ==================== If you have any questions, please call the IBM SUPPORT CENTER for your Country. For example in the USA call: 1-800-992-4777 ====================== COPYRIGHT INFORMATION: ====================== Copyright Novell Inc. and International Business Machines Corp. 1999. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, transmitted, or translated into any language without the express written consent of the publisher: Novell Inc. International Business Machines Corp. 2180 Fortune Drive P.O. Box 12195 San Jose, CA 95131 Research Triangle Park, NC 27709-2195 U.S.A. U.S.A. Note to U.S. Government Users - Documentation related to restricted rights - Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. =================== LIMIT OF LIABILITY: =================== License to the contained APAR fixes is conditioned upon the recipient holding a license to the prerequisite product. The license terms and conditions of the APAR fixes are the same as those for the prerequisite product. Please see the product license for specifics.