IMPORTANT NOTICE

Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)

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) Compaq Computer Corporation 2002.  All rights reserved.

Modification Date:  01-APR-2002
Modification Date:  Not Applicable
Modification Type:  NEW KIT

OP/SYS:     OpenVMS VAX

COMPONENT:  DRIVER

SOURCE:     Compaq Computer Corporation

ECO INFORMATION:

     ECO Kit Name:  VAXDRIV01_073
     ECO Kits Superseded by This ECO Kit:  None
     ECO Kit Approximate Size:  414 Blocks
     Kit Applies To:  OpenVMS VAX V7.3
     System/Cluster Reboot Necessary:  Yes
     Rolling Re-boot Supported:  Yes
     Installation Rating:  INSTALL_3
                           3 - To be installed on all systems running
                               the listed versions of OpenVMS which
                               are experiencing the problems described.

     Kit Dependencies:

       The following remedial kit(s) must be installed BEFORE
       installation of this kit:

         None

       In order to receive all the corrections listed in this
       kit, the following remedial kits should also be installed:

         None


ECO KIT SUMMARY:

An ECO kit exists for DRIVER  on OpenVMS VAX V7.3.
This kit addresses the following problems:

PROBLEMS ADDRESSED IN VAXDRIV01_073 KIT:

  o  SCACP erroneously returns a "managed  object  handle  invalid"
     error  status.   This  results  in an inability to issue SCACP
     commands on some systems.  Also,  on  some  systems  (random),
     SCACP returns an error status on every command.

          Images Affected:  [SYS$LDR]PEDRIVER.EXE
                            [SYSEXE]SCACP.EXE
                            [SYSEXE]PEDRIVER.STB


  o  The error status given to SCACP is not displayed.

          Images Affected:  [SYS$LDR]PEDRIVER.EXE
                            [SYSEXE]SCACP.EXE
                            [SYSEXE]PEDRIVER.STB


  o  SET, STOP, START, SHOW commands default to wildcard  *  if  no
     device,  channel,  or  VC name is specified.  Only SHOW should
     default in such a manner.  SET, STOP and START should  require
     explicit  specification  of  the  names  or  an  *  if all are
     requested.  four error messages have been added:

       o  NODEVGIVEN - No devices  specified  (default  to  wildcard
          only on SHOW)

       o  NOCHANGIVEN - No channels specified (default  to  wildcard
          only on SHOW)

       o  NOVCGIVEN - No VCs specified (default to wildcard only  on
          SHOW)

       o  OBJ_HANDLE_INV - Managed object handle invalid


          Images Affected:  [SYS$LDR]PEDRIVER.EXE
                            [SYSEXE]SCACP.EXE
                            [SYSEXE]PEDRIVER.STB


  o  The /OUTPUT qualifier does not process the supplied file  name
     correctly.   This results in an output file being created with
     the wrong name, generally the specified name with  some  extra
     characters.

          Images Affected:  [SYSEXE]SCACP.EXE

RELATED ARTICLES:

Detailed articles describing the problems listed above may exist in
the OPENVMS database.  To view these articles, open the appropriate
product database and perform a query using either of the following
search strings: 'VAXDRIV01_073', 'VAXDRIV'.


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:

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

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

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

This kit requires a system reboot.  Compaq strongly recommends that
a  reboot  is performed immediately after kit installation to avoid
system instability

If you have other nodes in your OpenVMS cluster, they must also  be
rebooted  in  order  to make use of the new image(s).  If it is not
possible or convenient to reboot the entire cluster at this time, a
rolling re-boot may be performed.

  
  ==========================================================================
  |                     Table of Kit Image Information                     |
  +----------------------------+----------+-----------------+--------------+
  |                            | Overall  | Image File      | Image Link   |
  | Image Name                 | Checksum | Identification  | Date/Time    |
  +----------------------------+----------+-----------------+--------------+
  | PEDRIVER.EXE               |%X1F954C2B| VMS-17          | 30-JUL-2001  |
  |                                       |                 | 23:25:04.99  |
  +----------------------------+----------+-----------------+--------------+
  | SCACP.EXE                  |%X6C0AA89A| X-13            | 30-JUL-2001  |
  |                                       |                 | 23:33:52.14  |
  +----------------------------+----------+-----------------+--------------+


All trademarks are the property of their respective owners.