
              NOVELL TECHNICAL INFORMATION DOCUMENT

TITLE:              SAA016.EXE; NetWare 2.0 SAA Maintenance
DOCUMENT ID:        TID1004841
DOCUMENT REVISION:  A
DATE:               03AUG95
ALERT STATUS:       Yellow
INFORMATION TYPE:   Symptom Solution
README FOR:         SAA016.EXE

NOVELL PRODUCT and VERSION:
NetWare for SAA 2.0

ABSTRACT:

SAA016.EXE and SAA017.EXE are the current maintenance patch for SAA 2.0.  It
upgrades "NetWare for SAA 2.0.22" to "NetWare for SAA 2.0.23".  SAA016.EXE and
SAA017 are recommended for SAA 2 sites.  Please apply SAA016 and SAA017 before
calling Tech Support.

-----------------------------------------------------------------
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
Symptoms related to API's 
1. Register AH not updated during successful execution.
2. Convert using table G not functioning properly. 
3. Application Termination problems. 

Symptoms related to AS400.
1. If AS400PCS.NLM loaded with security ON and the Netware Client Address
started with 0, user did not connect. 
2. WSF failure if client was connecting to 3 or more systems. 
3. AS400PCS unloading, because Client Access V3R10 would deallocate. 

Symptoms Related to Data Links.
1. R2SDLC driver loading concurrently with the R3SDLC driver using the same
I/O port caused server abends. 
2. R3SDLC driver hang with receive overruns. 

Symptoms Related to NWSAA.
1. RUNCMD with long response, not working for a PU which is not the focal
point. 
2. LUx secondary return codes intermittently byte swapped. 
3. LUx, SLIOPEN verb with secondary initialization with an unformatted 
LOGON message returned primary return code session failure=0F00, and secondary
return code LUx_Sli_Logic_Error=7FD00000.
4. LUx, SLI_OPEN failed after USS MSG 10. 
5. Bind without mode name and or PLU name in the user data field.   
6. PREPARE_TO_RECEIVE REPORTED conversation failure when partner did
SEND_ERROR rather than PROG_ERROR_PURGING.
7. Receive Immediate could fail with large (64K) RU size. 

Symptoms related to Windows Configurator. 
1. Lower case for adapter not allowed. 
2. Link Type restricted to A - Z. 
3. Setup wiped out existing icons. 
4. Local station address accepted more than 2 digits hex.
5. Sorting for the print job name list box was case sensitive.
6. No PU profile remained selected in hot standby.
7. After the PU profile was copied, Focus moved to the PU profile.
  
New Feature
1. APPC and AS400 configuration in the windows configurator. 
2. Multi adapter PU2.1 profile for all peer connections. 

SOLUTION

Apply SAA016 and SAA017.

Self-Extracting File Name:  SAA016.EXE     Revision:  A

Files Included     Size     Date      Time

\
  SAA016.TXT         (This File)
\DISK1\
   NWSAA.001       2668   04-19-95    1:47p
   NWSAA.RMV       1706   04-19-95    1:46p
 PRODUCT.DEF       1045   04-24-95    4:30p
CSSYSMSG.NLM      43905   02-16-95    4:09p
PINSTALL.NLM     130785   02-16-95    4:09p
\DISK1\AS400\
 STRNRTR.EXE      49337   03-28-95   10:59a
 STRNTCP.EXE      69951   03-28-95    3:14p
\DISK1\DOS\
     CCM.OVL      51708   03-30-95    3:05p
    APPC.OVL       8982   03-30-95    3:06p
    SSET.OVL      35768   04-18-95    2:27p
\DISK1\INSTALL\
CSSYSMSG.NLM      43905   02-16-95    4:09p
PINSTALL.NLM     130785   02-16-95    4:09p
\DISK1\INSTALL\NLS\4\
CSSYSMSG.HLP       3302   05-18-93    3:49p
CSSYSMSG.MSG      11605   01-20-95   10:13a
PINSTALL.HLP       2799   05-26-94    7:41p
PINSTALL.MSG      12786   12-05-94   12:58p
\DISK1\NLMS\
     CCM.NLM      41501   03-30-95   12:23p
    SSET.NLM      50068   04-18-95    1:30p
   NWSAA.NLM     244593   04-20-95    2:53p
   QLLCS.NLM      48227   03-27-95    4:56p
  R2SDLC.LAN      13908   02-17-95    3:02p
  R3SDLC.LAN      22622   03-08-95    2:58p
AS400PCS.NLM      31808   04-13-95   10:26a
NWSAACFG.NLM      61380   03-28-95    4:38p
\DISK1\NLS\4\
   QLLCS.MSG       2706   06-18-93    5:27p
CSSYSMSG.HLP       3302   05-18-93    3:49p
CSSYSMSG.MSG      11605   01-20-95   10:13a
NWSAACFG.MSG        402   03-28-95    3:46p
PINSTALL.HLP       2799   05-26-94    7:41p
PINSTALL.MSG      12786   12-05-94   12:58p
\DISK1\SYSTEM.3X\
 LLC8022.NLM      34876   03-23-95    1:30p
\DISK1\SYSTEM.4X\
 LLC8022.NLM      36145   03-23-95    1:28p
\DISK1\WINDOWS\
     CCS.DLL      37392   03-28-95    7:09p
    SSET.DLL      56557   04-19-95    6:06p
   TRANS.EXE       8768   03-28-95    7:17p
  ATTMGR.EXE      16416   03-29-95    9:23a
  CCSWIN.EXE       9408   03-28-95    7:10p
  WINLUX.DLL       4929   03-29-95    9:43a
 WINSSET.DLL       4848   03-30-95    3:56p


Installation Instructions:

1. SAA016 and SAA017 will install only on top of version 2.00.22 of NWSAA!! 
It will not work on any BETA version of NWSAA 2.0! 

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.0!!

3. Only attempt installation on NetWare 4.1 or NetWare 3.12.

4. CSLOAD/CSUNLOAD commands are no longer supported. 

5. If you have not already done so, install the LANDR4.EXE patch.

6. If you have not already done so, install the STRTL3.EXE patch. 

7. Make a directory called SAA016, on a hard disk or network drive.  Make sure
the directory path is available to the server(s) you are updating.

8. Put SAA016.EXE into the SAA016 directory you just made.

9. Unzip SAA016.EXE.
                  SAA016  <Enter>

10. LOAD Install.

11. Select Product Options.

12. Press <Insert>.  

13. Select the directory path created above ie, SYS:\SAA016\DISK1 or
C:\SAA016\DISK1

14. Select the server to update.

15. Press <Enter>.

16. Wait for the update to complete.

17. Press <Esc>.  You should see NWSAA 2.0.23

18. See readme for saa017 for instructions on installation of that patch. 

!! 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 than or greater than the
one to be installed by this patch, the install will fail. !!***

23. Restart the server before loading COMMEXEC, this will activate the new
system modules copied over during installation. 

24. Run SAAUP.NCF, this will autoload COMMEXEC and NWSAA.NLM. 

NOTE: 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. 

Patch History:

SAA016/017 are the first maintenance patch for SAA 2.0. 


Solution Specifics: (for some of the symptoms listed above)

Solutions Related to API'S 
1. Code modified so that register AH is updated with 0 upon successful
execution.
2. CCSCVRT.C code modified so that it will function with table G. 
3. Windows APIs modified. 

Solutions related to AS400 
1. AS400PCS.NLM modified so that it will not reject this user. 
2. AS400PCS.NLM modified. 
3. The second byte of the opcode has been masked to zero.
 
Solutions Related to NWSAA
1. NWSAA.NLM modified.
5. When no Mode Name is specified, a string of eight blanks will be assumed.

-----------------------------------------------------------------
Any trademarks referenced in this document are the property of their
respective owners.  Consult your product manuals for complete trademark
information.
-----------------------------------------------------------------

