Visit the our Home Pages on the Internet: NetWare for SAA http://www.networking.ibm.com/nsa/nsamain.html +-------------------------------------------------------------------+ | | | | DATE: 05/23/97 | | | | | | DESCRIPTION: Cumulative Service Pack for NetWare for SAA Ver. 2.2 | | | | | | README FILE FOR: NetWare for SAA Version: 2.2 | | | | PTF NUMBER: SAA22010 | | APAR NUMBER: N/A___ | | | | 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 PROBLEMS FIXED in this PTF: APAR # Description ----------------------------------------------------------------------------------------------- n/a Cannot connect then disconnect LUA emulator session via PCOMM {cmvc1598} n/a Trap in LUX.DLL when running GRIND.EXE on LUA session {cmvc1603} n/a "Run the Same" option in PCOMM doesn't work with pooled connection {cmvc1619} n/a LU62MGR.EXE grows in memory usage with APPC5250 PCOMM {cmvc1621} n/a Installing NWSAA client does not get installed in the COMMON area (below the line of the start menu) when it is installed on a WIN NT 4.0 system {cmvc1614} n/a Uninstall of NWSAA client on WIN NT 4.0 machine does not work {cmvc1615} n/a Drop down query selections for Local LU and Partner LU do not work for 5250 sessions {cmvc1659} n/a PCSCM.EXE Appl Error using LUA via WinRUI {cmvc1639} n/a Session hangs if NWSAAAPI.INI file is missing {cmvc1669} n/a PCSCM.EXE Application Error fix {cmvc1652} n/a Out of Virtual Memory Message when running PCOMM and NWSAA 2.2 {cmvc1664} n/a Exception violation in CCS.DLL when running batch files {cmvc1685} n/a GPF if Host PU Profiles option (TN3270) changed when no PU profiles created. {cmvc1628} n/a Reinstall of 2.2 over 2.2 causes rename of existing datafiles {cmvc1640} n/a Assign users context invalid when server bindery context not at top tree {cmvc1727} n/a Problems loading AS400PCS {cmvc1288} n/a CA/400 data transfer doesn't work {cmvc0347} n/a STRNTCP causes Module did not release 64 resources {cmvc1399} Module: AS400PCS (2.20.0 - Wed Sep Resource: Small memory allocations Description Alloc Memory (Bytes) n/a AS400PCS Abends with Page Fault {cmvc1644} n/a CFGNRTR will not accept a file name different than startpcs.bat {cmvc1666} n/a Deleting 2 or more PU Profiles, one of which is in two Hot Standy definitions abends server {cmvc1626} n/a Security=OFF is ignored {cmvc1699} n/a PINSTALL fails to load on 3.12 server {cmvc1865} n/a No TP_ENDED on termination of CPIC TPs {cmvc1774} n/a Downstream LU Map button actions are not correct {cmvc1149} n/a Help buttons fixed thoughout the product {cmvc1909} n/a PINSTALL.NLM fails to select the appropriate language {cmvc2068} n/a Local Lu group not redisplayed when new default added after AS400 system definition. {cmvc2034} n/a Fix for WRQ - Reflections software to process public lus correctly {cmvc2043} JR09444 AS400 device still showing up in CSSTATUS when device was deleted INSTALLATION INSTRUCTIONS: 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 will be documented below. Note that the process to remove the entire product is not changed by this new 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 new PTF removal process if you only want to back off the the last PTF installed. The PARTS LIST is as follows: A list of the files that are installed by this PTF can be found in the file named "FILES.LST". NOTE: It is a good practice to run SAACOPY to backup your current SAA configuration prior to applying service to your server. Please note that the CONFIG.SYS for the workstation from which you run SAACOPY must contain FILES=20 (or greater) and BUFFERS=20 (or greater). Also, you must have a minimum of 550K free base memory to run this SAACOPY. ! IMPORTANT: 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 to or greater than the one to be installed by this patch, the install will fail! ___________________________________________________ 1. SAA22010 will only install on top of version 2.20.00 of NWSAA!! It will not work on any BETA version of NWSAA 2.2! 2. You must have the latest NIC drivers for your system. They must be ODI 4.0 compliant AND certified for use with SAA 2.2!! 3. Only attempt installation on NetWare 4.10, 4.11. 4. CSLOAD/CSUNLOAD commands are no longer supported, use SAAUP, SAADOWN, and CSDOWN instead. 5. If you have not already done so, make sure the latest operating system patches are applied to your system. 10. Read the Solution Notes (in this document) regarding new configuration features. Server installation procedures are as follows: ___________________________________________________ 1. Stop NetWare for SAA. 2. From the server console type LOAD INSTALL and Press . 3. Select Product Options and Press . 4. Select Products Not Listed and Press . 5. Press to enter path on server to location of the installation files. for example if the CD is mounted locally: SAA22010:\COMMEXEC 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 Press . You should see COMMEXEC 2.20.10 12. Select Product Options and Press . 13. Select Products Not Listed and Press . 14. Press to enter path on server to location of the installation files. for example if the CD is mounted locally: SA22010:\NWSAA 15. Select the server to update. 16. Press . 17. Select the Language to Install. NOTE: If selecting more than one language, highlight each language using the key. 18. Press . 19. Wait for the update to complete. 20. Press . You should see NWSAA 2.20.10 21. Restart the server before loading NWSAA, this will activate the new system modules copied over during installation. Client installation procedures are as follows: ___________________________________________________ 1. If the NWSAA Client API's are currently installed, run the un-install program before proceeding with the installation process. 2. Map a drive on the Client to the location of the installation files. 3. To install the NWSAA Client API's run SETUP from appropriate directory: d:\NWSAA\WINDOWS\WIN16\ENGLISH or d:\NWSAA\WINDOWS\WIN95\ENGLISH or d:\NWSAA\WINDOWS\WINNT\ENGLISH or d:\NWSAA\OS2\ENGLISH ***** PTF Removal Procedure and Notes ***** Two types of PTFs are identified: 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., SAA22010). They require only the base product. Delta - These PTFs include only those PTFs backwards to the last cumulative PTF. Their names end in a suffix wich contains the number of the last cumulative PTF, plus the number of the delta PTF (e.g.,SAA22011). They require the prior cumulative PTF. 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. SAA22010) 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. 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. 1997. 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.