| » contact hp |
search: |  | more options |
| Supportall of hp US

|  | HP Services Software Patches |

» | software & drivers
» | ask Compaq
» | reference library
» | forums & communities
» | support tools
» | warranty information
» | contact support
» | parts
» | give us feedback
patches by topic
» | DOS
» | OpenVMS
» | Security
» | Tru64 Unix
» | Ultrix 32
» | Windows
» | Windows NT
associated links
» | what's new
» | contract access
» | browse patch tree
» | search patch tree
» | join mailing list
connection tools
» | nameserver lookup
» | traceroute
» | ping
HP Services Software Patches - vaxlat03_u2055
    Copyright (c) Digital Equipment Corporation 1995.  All rights reserved.

    OP/SYS:     OPENVMS VAX

    COMPONENT:  LAT

    SOURCE:     Digital Equipment Corporation

    ECO INFORMATION:

         ECO Kit Name:  VAXLAT03_U2055
         ECO Kits Superseded by This ECO Kit:  VAXLAT02_U2055 (CSCPAT_0511)
         ECO Kit Approximate Size:  300 Blocks
         Kit Applies To:  OpenVMS VAX V5.5, V5.5-1, V5.5-2,
                          V5.5-2H4, V5.5-2HF
         System/Cluster Reboot Necessary:  Yes

      NOTE:  The CSCPAT_0511 ECO applied to OpenVMS VAX V5.4 - V5.5-2H4.
             This kit applies to OpenVMS VAX V5.5 - V5.5-2HF.  If the
             fixes in this kit are required for a version that precedes
             V5.5, engineering highly recommends that you update to V5.5-2
    	 or higher.

    ECO KIT SUMMARY:

    An ECO kit exists for LAT on OpenVMS VAX V5.5 through V5.5-2HF.  This
    kit addresses the following problems:

          o  It is possible for a system to crash when using  the  TSM  TEST
             LAT command.  This problem is corrected in OpenVMS VAX V6.2

          o  System crash when the  LTDRIVER  or  LATACP  attempts  to  walk
             through the LAT UCBs on the dedicated port queue.

          o  LATACP process is caught  in  a  continuous  loop  and  ignores
             processing all LAT requests such as incoming connections, LATCP
             commands, new service  announcements  and  solicit  information
             messages.  This problem is corrected in OpenVMS VAX V6.2

    Problems Addressed in VAXLAT02_U2055 Kit

          o  OpenVMS VAX does not recognize any speed above 38400  kbps  and
             will  report  a  terminal  speed  of  0 if set to 57600 kbps on
             terminal server.

          o  If a system manager  creates  several  services  (sometimes  in
             excess  of  20  LAT  services)  on an OpenVMS VAX system, it is
             possible that the system may crash if the resulting LAT Service
             Announcement message is between 1488 and 1500 bytes in size.

          o  If the LAT node state is set  to  "shut",  OpenVMS  will  still
             allow  new incoming connections.  This is incorrect behavior as
             the LATCP documentation states that  the  "shut"  state  allows
             existing  connections  to  continue  and  operate  but  no  new
             connections are allowed.

          o  If a system manager  creates  several  services  (sometimes  in
             excess  of  20  LAT  services)  on an OpenVMS VAX system, it is
             possible that the system may crash if the resulting LAT Service
             Announcement message is between 1488 and 1500 bytes in size.

          o  If the LAT node state is set  to  "shut",  OpenVMS  will  still
             allow  new incoming connections.  This is incorrect behavior as
             the LATCP documentation states that  the  "shut"  state  allows
             existing  connections  to  continue  and  operate  but  no  new
             connections are allowed.

          o  If a user program issues a POSIX selective cancel operation for
             an OpenVMS VAX LAT device, this operation will return "function
             not supported".

    Problems Addressed in VAXLAT01_U2055 Kit

          o  BUGCHECK INVEXCEPTN in routine LT$TICK.  A LAT UCB has been
             marked  for deletion and LTDRIVER is verifying that the UCB
             does not exist on another CPU's IPL 8  fork  queue.   Since
             the  SMP  environment  does  not  provide a synchronization
             mechanism for this operation, it is possible that the other
             CPU  IPL 8 fork queue can change while LTDRIVER is checking
             the queue items.  If this occurs, the queue is no longer in
             the  same  state  as it was when LTDRIVER began walking it.
             This will result in either a system crash or system hung at
             IPL 8 holding the IOLOCK8 spinlock.

          o  BUGCHECK INVEXCEPTN  in  LTDRIVER  (routine  LT$XMT_REJSL).
             System  is  attempting  to  transmit a LAT reject slot to a
             remote terminal server  but  crashes  because  the  virtual
             circuit  for the connection has already been deleted.  This
             crash  is  mostly  seen  with  systems   that   have   many
             connections from an EMULEX terminal server.

          o  If a User does a SET HOST /LAT to an Infoserver or  another
             system, that requires a password for the LAT service, after
             the user provides the password, the message:

                 %LAT-I-DISCONNECTED, session disconnected from SERVICE
                 -LAT-I-END, control returned to node NODE_NAME

             appears.  If the user attempts  to  get  back  to  the  DCL
             prompt  through the use of Control Y, the process hangs and
             goes into the RWAST state.

          o  An OpenVMS VAX system can have the non-paged pool exhausted
             by LAT service announcement messages which could eventually
             lead to system crash or  hang.   The  system  manager  will
             probably  see  "pool  expansion  failure"  messages  on the
             console and SHOW MEMORY/FULL will show  that  the  nonpaged
             pool has grown from its original value and much of it is in
             use.

          o  System can crash with BUCHECK  INCONSTATE  in  LTDRIVER  in
             routine LT$XMT_RUN.

          o  When using a dedicated port with application LAT  services,
             the  LATCP  SHOW  SERVICE  command  can  incorrectly  list
             dedicated ports for the wrong application services.

    INSTALLATION NOTES:

    Install this kit with the VMSINSTAL utility  by  logging  into  the
    SYSTEM account, and typing the following at the DCL prompt:

         @SYS$UPDATE:VMSINSTAL VAXLAT03_U2055 [location of the saveset]

    The saveset location may be a tape drive, or a disk directory that
    contains the kit saveset.

    In order for the corrections in this kit to take effect, the system
    must be rebooted.  If  you  have  other  nodes in your VAXcluster,
    they should also be rebooted in order to make use of the new images.
Files on this server are as follows:
    »vaxlat03_u2055.README
    »vaxlat03_u2055.CHKSUM
    »vaxlat03_u2055.CVRLET_TXT
    »vaxlat03_u2055.a-dcx_vaxexe

privacy statement | using this site means you accept its terms |
© 1994-2002 Hewlett-Packard Company