Australia - Updated: 24-SEP-2003
hp.com home products and services support and drivers solutions how to buy
» contact hp
hp.com home hp OpenVMS ECOs

IMPORTANT NOTICE

The online distribution of OpenVMS and related product patches is being migrated to the HP ITRC (Information Technology Resource Center) patch distribution site. The new ITRC patch server will allow OpenVMS customers to take advantage of many enhanced features for patch searching and distribution.

Beginning August 1, 2003, OpenVMS and related Layered Product, publicly available patches will be available from the HP ITRC web site at

http://itrc.hp.com/service/patch/mainPage.do

The same patches will still be available from the existing patch server in Colorado Springs (http://www.support.compaq.com/patches/) through the end of October 2003, to give customers sufficient time to update their bookmarks and make the transition to the HP ITRC web site.

ECO kits will also be available by raw FTP from (ftp://ftp.itrc.hp.com/).

PLEASE UPDATE YOUR BOOKMARKS AND REGISTER ON THE NEW SITE NOW

Note: if you're having trouble connecting to the ITRC site, please delete any cookies for "itrc.hp.com" from your browser and try again. Report any difficulties with or suggestions to MrVMS

» Sydney CSC home page

Navigation
» ECOinfo main index
» Search ECOs
» Search FTP site
» Browse FTP site

ECO Indexes
» Chronological Index
» Indexed by Version
» Indexed by Rating
» Alpha Indexed by Name
» VAX Indexed by Name
» On Hold List

Associated Links
» OpenVMS Home Page
» OpenVMS News
» DIA/WIS Web Service

Feedback
» mail to CSC
.
Sydney Customer Support Centre OpenVMS ECO information
    Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)

VAXLAT02_061 OpenVMS VAX V6.1 LTDRIVER/LATACP ECO Summary

To obtain this kit please call the Customer Support Centre or use the FTP site

Search for this ECO kit and dependencies
Search the Compaq FTP web site this kit (exact match)
Search the Compaq FTP web site this or related ECOs

    
    
    Copyright (c) Digital Equipment Corporation 1997.  All rights reserved.
    
    OP/SYS:     OpenVMS VAX
    
    COMPONENT:  LAT, LTDRIVER
    
    SOURCE:     Digital Equipment Corporation
    
    ECO INFORMATION:
    
         ECO Kit Name:  VAXLAT02_061
         ECO Kits Superseded by This ECO Kit:  VAXLAT01_061
         ECO Kit Approximate Size:  300 Blocks
                        Saveset A - 288 Blocks
    
         Kit Applies To:  OpenVMS VAX V6.1
         System/Cluster Reboot Necessary:  Yes
    
         Installation Rating:   2 - To be installed on all systems running
                                    the listed version(s) of OpenVMS and
                                    using the following feature:
    
                                       LAT
    
    
         NOTE:  In order to receive the full fixes listed in this kit,
                the following remedial kits also need to be installed:
    
                     None
    
    
    ECO KIT SUMMARY:
    
    An ECO kit exists for LAT on OpenVMS VAX V6.1.  This kit addresses the
    following problems:
    
    
    PROBLEMS ADDRESSED IN VAXLAT02_061 KIT
    
      o  VCRP packets are being overwritten.
    
      o  A CREATE LINE LINK$NAME/DEV=XXA0:  command in LATCP  can  crash
         the system.
    
      o  After executing the following commands:
    
           LATCP> CREATE SERVICE SERVICE1/APPL
           LATCP> CREATE SERVICE SERVICE2/APPL
           LATCP> CREATE SERVICE SERVICE3/APPL
           LATCP> DELETE SERVICE SERVICE2
           LATCP> SET SERVICE SERVICE3/STATIC_RATING=1
    
         the static ratings for services following SERVICE2 can  not  be
         changed.
    
    
    PROBLEMS ADDRESSED IN VAXLAT01_061:
    
      o  System crash due to memory being  allocated  twice  during  TSM
         TEST LAT command.
    
      o  System crash due to dedicated port queue corruption
    
      o  The LATACP process loops, blocking further LAT connections
    
      o  SET HOST/LAT connections hang when connected to OSF systems.
    
      o  System crash during link deletion and/or creation.
    
      o  CPUSPINWAIT BUGCHECKs
    
      o  Connecting to a dedicated port for application service  results
         in  a protocol violation and the "invalid credit" counter being
         incremented.
    
      o  Fix possible CPUSPINWAIT crashes in PORT_CANCEL.
    
      o  The LAT architecture describes the response timer field in  two
         places.   Once, it is described as a value during solicitation.
         Secondarily, it  also  describes  how  to  use  that  value  to
         generate  a  random  number  timeout  period  within acceptable
         limits.  In one place, "10ms units" are referred to and in  the
         other,  "seconds"  is  referred  to as the unit of time.  LTDEF
         thought the "10ms units"  was  the  correct  value  for  a  LAT
         message when "seconds" is needed.
    
    
      o  In a SET HOST /LAT session,  during  certain  circumstances  of
         lost  messages,  LTDRIVER is erroneously setting the RRF bit in
         the master message without checking to see if  the  circuit  is
         doing  delayed acknowledgments.  RRF should not be set unless a
         circuit has successfully negotiated delayed ACKS
    
      o  LATACP crashes with PGFIPLHI
    
      o  LTDRIVER crashes with INVEXCEPTN
    
      o  Some applications use break, through  the  system  service,  to
         write to their numerous terminals at the same time.  When LATCP
         is running, the management LTA device created by LATCP is  also
         broadcast  to.   This  slows  done the application to the point
         where the application exhausts its byte limit
    
      o  An MC LATCP CREATE PORT command with  an  invalid  device  name
         will crash the system.
    
    
    RELATED ARTICLES:
    
    Detailed articles describing the problems listed above may exist in
    the LAT-DECSERVER or OPENVMS databases.  To view these articles, open
    the appropriate product database and perform a query using either of
    the following search strings: 'VAXLAT' or 'VAXLAT02_061'.
    
    
    ECO KIT ORDERING INSTRUCTIONS:
    
    If after an evaluation you wish to obtain this kit, request it
    electronically using the appropriate Advanced Electronic Services
    (AES) Service Tool.  If you are not familiar with how to request
    kits electronically, open the DIA, WIS or DSNLINK database and
    review the article entitled:
    
         [AES] How To Electronically Request ECO Kits Using Service Tools
    
    
    INSTALLATION NOTES:
    
    In order for the corrections in this kit to take effect, the system must
    be rebooted.  If the system is a member of a VMScluster, the entire
    cluster should be rebooted.
      
      ==========================================================================
      |                     Table of Kit Image Information                     |
      +----------------------------+----------+-----------------+--------------+
      |                            | Overall  | Image File      | Image Link   |
      | Image Name                 | Checksum | Identification  | Date/Time    |
      +----------------------------+----------+-----------------+--------------+
      | LATACP.EXE                 |%X30F32132| V1.0-147F       | 18-NOV-1997  |
      |                                       |                 | 15:19:25.76  |
      +----------------------------+----------+-----------------+--------------+
      | LATCP.EXE                  |%X8FCDC8AD| X1.38           | 18-NOV-1997  |
      |                                       |                 | 15:19:31.12  |
      +----------------------------+----------+-----------------+--------------+
      | LTDRIVER.EXE               |%XD931E734| V6.0-406        | 18-NOV-1997  |
      |                                       |                 | 15:19:20.96  |
      +----------------------------+----------+-----------------+--------------+
    
privacy statement using this site means you accept its terms feedback to the webmaster
VMS rules VMS rocks OpenVMS rules OpenVMS rocks