
              NOVELL TECHNICAL INFORMATION DOCUMENT

TITLE:              SAA 1.3B Maintenance PTF
DOCUMENT ID:        TID250050
DOCUMENT REVISION:  B
DATE:               05APR94
ALERT STATUS:       Yellow
INFORMATION TYPE:   Symptom Solution
README FOR:         PTF443.EXE

NOVELL PRODUCT and VERSION:
NetWare for SAA 1.3B

ABSTRACT:

This file contains the current maintenance PTF for NetWare for SAA 1.3B.  PTF
443 supersedes PTF435, and PTF438.  PTF443 is recommended for all SAA 1.3B
installations and all NetWare SAA 1.3 installations that have installed the
PTF410 series.


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.


ADDITIONAL CONFIGURATION

     Other:

     GENERAL

SYMPTOM

     The server hung in a multidrop environment.

SYMPTOM

     RTS toggles to low even when set to constant high.

SYMPTOM

     Spurious Interrupt error messages were displayed.

SYMPTOM

     In some environment, pressing Attention during a logoff could result in a
     Profile Unload.

SYMPTOM

     Problems gathering statistics through SSM were noted.

SYMPTOM

     Problems using OS/2 Connection Manager were noted.

SYMPTOM

     Failure to reestablish connect with host was noted.

SYMPTOM

     Failure to respond to a DISC from NCP was noted.

SYMPTOM

     The following message was displayed:

     MESSAGE

          DLCI Error: Unable to Attach to a Logical Board

SYMPTOM

      Failure of the link to come up was noted.


ADDITIONAL CONFIGURATION

     Other:

     SNALINKS

SYMPTOM

     Even though SNALINKS was configured for auto connect, the connection did
     not automatically come up after a link was downed.


ADDITIONAL CONFIGURATION

     Other:

     SAACOPY

SYMPTOM

     When the user was trying to back up or restore SAA service files, the
     following message was displayed:

     MESSAGE

          Unable to open file

SYMPTOM

     Downstream LUs were unable to establish host sessions.

SYMPTOM

     SAACOPY was unable to copy between a 1.3 and a 1.4 Communication Server.

SYMPTOM

     The following message was displayed:

     MESSAGE

          No more WCM connection

SYMPTOM

     The following message was displayed:

     MESSAGE

          Error on Attach

SYMPTOM

     PC hangs after using SAACOPY

SYMPTOM

     In a VLM environment, the prompt changes to %p.


ADDITIONAL CONFIGURATION

     Other:

     AS/400

SYMPTOM

     Users are unable to access Shared Folders.


ADDITIONAL CONFIGURATION

     Other:

     Using NetView

SYMPTOM

     Server crash when NetView issues a REQMS.

SOLUTION

     Apply the files from the PTF443.EXE file.

     Self-Extracting File Name:  PTF443.EXE     Revision:  B

     Files Included     Size     Date      Time

     \
       PTF443.TXT         (This File)
          DLM.NLM      99615   10-15-93    9:53a   *533
          WCM.DLL      33129   08-26-93    5:43p   *517
        NWSAA.001        502   03-16-94    2:34p
        NWSAA.NLM     364510   02-16-94   11:05a   *566, 545
        NWSAA.RMV       1860   06-28-93   11:54a   *545
        SDLCS.NLM      39652   12-27-93   10:40a   *557, 549
       R3SDLC.LAN      22385   02-28-94    2:02p   *570, 546
      PRODUCT.DEF        433   02-15-94    5:10p   *545
      SAACOPY.EXE     262089   11-02-93    4:44p   *541
      SAACOPY.TXT       5781   03-10-94    4:41p
      SPC_FRM.HLP      67975   10-11-93    5:15p   *541
      STRNRTR.EXE      41757   10-22-93    4:39p   *541
     AS400PCS.NLM      18642   10-22-93    4:41p   *535
     CSINSTAL.HLP       2336   03-09-93    6:44p   *545
     MASTERTD.TXT       1299   12-03-93    6:15p
     NOVELLRT.OVL       6678   10-22-93    4:39p   *535
     PINSTALL.NLM      87963   06-10-93   11:29a   *545

     *Novell internal control number

     Installation Instructions:

     1.   Install this PTF ONLY IF you have NetWare for SAA 1.3B or have
          installed the PTF410 series.

     2.   Copy the files in the PTF onto a high-density floppy diskette.

     3.   Put that disk into the A: drive of the NetWare for SAA server.

     4.   Do a CSDOWN so that COMMEXEC will not be running.

     5.   LOAD Install.

     6.   Select Product Options.

     7.   Press INSERT.

     8.   Select server to update.

     9.   Press enter.

     10.  Wait for the update to complete.

     11.  Reload COMMEXEC

     12.  Reload the profile.

     13.  Copy the new STRNRTR.EXE over any copies that may exist outside of
          SYS:\SYSTEM\NWSAA\AS400 directory.

     14.  Read the SAACOPY.TXT file for new instructions on the use of
          SAACOPY.

     Patch History:

     PTF 443 supersedes all prior PTFs for NetWare for SAA 1.3B including
     PTF435 and PTF438.  It also replaces the NetWire file SAACPY.EXE that
     introduced the problem of restored downstream LUs being unable to
     establish host sessions and PTF431 that was the first PTF for NetWare for
     SAA 1.3B.

     Solution Specifics:

     A.   GENERAL

          R3SDLC.LAN was modified to correct problem 1, 2, and 3.

          1.   In a multidrop environment, the SAA server could hang if
               another device kept RTS high.

          2.   When CSCON was configured to keep RTS high, it was not kept
               high.

          3.   Spurious interrupts/ missed polls.

          4.   In some environments, pressing Attention during a logoff could
               result in a Profile Unload.

          5.   The R3SDLC and SDLCS were modified so that DTR is not toggled
               when SAA receives a disconnect command in a leased line
               configuration.

          6.   The new SDLCS acknowledges DISCs from NCP.

          7.   SDLCS.NLM was modified so that a "DLCI Error" will no longer
               result when loading both a PU2.0 and a PU2.1 profile to the
               same board.

          8.   The SDLCS.NLM was modified so that the link will no longer fail
               to come up when a DISC immediately follows SNRM/UA.

     B.   SAACOPY

          1.   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 error message "Unable to Open File" when you try to
               back up or restore SAA service files

          2.   If you backed up Downstream PU configurations with files in
               SAACPY.EXE and have to restore them, please contact the Sysop
               on NetWire in NCONNECT Section 3.

          3.   Previous versions of SAACOPY could not copy between a 1.3
               Communications Server and a 1.4 Communications Server (or vice
               versa).

          4.   Connections were failing to clear.  Therefore, as new
               connections were made the maximum number would be reached.

          5.   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.

          6.   Under certain circumstances, the use of SAACOPY then CSCON,
               could result in the DOS prompt being changed to "%p".

     C.   WITH SNALINKS

          Even though SNALINKS was configured for auto connect, the connection
          did not come back up automatically after a link was downed.

     D.   SHARED FOLDERS

          Support for the "query conversation state" service verb has been
          added.  Therefore, attempts to access Shared Folders will no longer
          result in a drive error.

     E.   USING NetView

          When the new DLM.NLM is used, a server crash will no longer result
          from an REQMS resulting in a DLM_GET_STATISTICS or
          DLM_RESET_STATISTICS.




