SNA_CT SNACSA_E08021 DECnet SNA Gateway-CT for OpenVMS ECO Summary

 
NOTE:  An OpenVMS saveset or PCSI installation file is stored
       on the Internet in a self-expanding compressed file.
       The name of the compressed file will be kit_name-dcx_vaxexe
       for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha.
 
       Once the file is copied to your system, it can be expanded
       by typing RUN compressed_file.  The resultant file will
       be the OpenVMS saveset or PCSI installation file which
       can be used to install the ECO.
 
Copyright (c) Digital Equipment Corporation 1994, 1997.  All rights reserved.

PRODUCT:    DECnet SNA Gateway-CT

OP/SYS:     OpenVMS VAX
            OpenVMS Alpha

SOURCE:     Digital Equipment Corporation

ECO INFORMATION:

     ECO Kit Name:  SNACSA_E08021
     ECO Kits Superseded by This Kit:  SNACSA_E07021
                                       SNACSA_E06021 (CSCPAT_5024)
     ECO Kit Approximate Size:  6336 Blocks
     Kit Applies To:  DECnet SNA Gateway for Channel Transport V2.1
                      OpenVMS VAX V5.5 or higher
                      OpenVMS Alpha V6.1 or higher 

                      NOTE:  This kit is an OpenVMS load host kit only. 

     System Reboot Necessary:  No


ECO KIT SUMMARY:

An ECO kit exists for DECnet SNA Gateway for Channel Transport V2.1 on
OpenVMS VAX V5.5 or higher and OpenVMS Alpha V6.1 or higher.  This kit
addresses the following problems: 

Problems addressed by the SNACSA_E08021 kit:

  o  Gateway Crash Due To LU Service Table Entries Not Deleted.
  o  A Gateway Crash Occurred When Process Buffers Were Not Deallocated.
  o  Additional Logging Information Added For Analysis Of Dumpfiles.

This ECO also incorporates all of the fixes in previous ECO releases. 
Below is a brief description of each of them: 

  o  Potential Crash Occurred In Handling ACTLU Responses.
  o  Crash May Occur When Running Snap For Excessively Long Times.
  o  Gateway Event Collector Fails To Reconnect To SINK NODE.
  o  SNATRACE Data Buffer Size Incorrect.
  o  SNANCP Commands Not Parsed When Included On A Single Line From DCL.
  o  Gateway Kit Would Not Install On ULTRIX V4.3 Or Higher.
  o  SNAP Display Problems Of Multiple PUs On ULTRIX RISC Systems.
  o  RJE 'unexpected Line Condition, Workstation Is Now Off' Problem.
  o  Extra Line May Be Seen In RJE Punch Output If LRECL=80.
  o  LUs May Hang Or Become Inaccessible To Users.
  o  Constraint Violation In SNAGM$EVL_STARTUP When Started On DECnet/OSI
     Systems.
  o  Lines Output In Some SNA Event Messages.
  o  Some SNANCP Messages Are Output Incorrectly.
  o  SNATRACE Commands Not Parsed On Alpha Systems When Entered From DCL.
  o  Starting with ECO-04, the DECnet SNA Gateway-CT is available for 
     OpenVMS Alpha as well as for the OpenVMS VAX operating system.
  o  Potential Crash When Gateway Low On Memory/pool.
  o  Crash May Occur In DECnet Session.
  o  Crash May Occur When Issuing Many Network Management Commands.
  o  If DECnet Logical Link Is Broken, Gateway LU May Remain In Unusable
     State.
  o  Certain ANSI Printer Controls Did Not Function Properly.
  o  Support Provided To Install Gateway On DECnet-Vax Extensions Or
     DECnet/OSI Systems.
  o  'IBM Host Violated The SNA Protocol' Error Message Seen When Using 
     RJE.
  o  RJE Server Would Place Carriage Returns As The Only Character In
     Record.
  o  Insufficient Resources Seen When Using RJE.
  o  Application Names With Trailing Spaces Caused Connection To Fail.
  o  Sessions Either Hang Or Cannot Restart After A VTAM Cancel Is Issued.
  o  IBM Sense Code 084C Issued By Gateway On A VTAM Restart.
  o  Error In SNACSA$CONFIGURE.COM When Processing SET ACCESS NAME 
     Commands.
  o  Crash On Processing A Bind.
  o  Crash During Heavy Load.
  o  SNACSA$CONFIGURE.COM Will Support A Directory Search List.
  o  The NOCCTL Parameter In A JES2 Workstation Definition Will Cause A
     Crash.
  o  The RJE Server Issued A Chaining Error When Multiple Copies Was
     Specified.
  o  The RJE Server Created Files With Wrong Max Record Length.
  o  The RJE Server Lost Bracket State If It Rejected Certain RUs.
  o  SNANCP> SET ACC Name LU List Without PU Name Now Provides An
     Error Message.
  o  DECnet Out-of-order Packet Caching Errors.
  o  Use Of Session Number 255 Caused Return Of The Negative Response
     Code 080A.
  o  Memory Depletion On Highly Utilized Systems.
  o  RJE Server Changes - Chaining Protocol.
  o  RJE Server Changes - Reader Stream Compression Of IRS.
  o  RJE Server Changes - Outbound BID (DFC) Request.
  o  RJE Server Changes - TRN Count Wrong During Compression.
  o  RJE Server Changes - Support For FM Profile 3.
  o  RJE Server Changes - FORMS Name Length.
  o  Reconnect Problem With MS-DOS And ULTRIX 3270 TEs.

More information regarding the nature of these problems can be found in the
ECO kit's release notes. 


INSTALLATION NOTES:

No system reboot is necessary after successful installation of the kit;
however, the gateway must be rebooted to load the new software image.

Colorado Site
Georgia Site

snacsa_e08021.README
snacsa_e08021.CHKSUM
snacsa_e08021.CVRLET_TXT
snacsa_e08021.a-dcx_axpexe
snacsa_e08021.a-dcx_vaxexe