*********************************************************************
**                                                                 **
** TEXT FILE LIMITATIONS:                                          **
**                                                                 **
** The text extract for this document does not capture tables very **
** well, mainly because of the 75-column, monospaced character     **
** limitation. Be aware that large data tables probably will not   **
** wrap properly in this text file.                                **
**                                                                 **
** In addition, the text extract cannot capture figure images.     **
** You can see only placeholders (captions) for the figures.       **
**                                                                 **
** You may see references to italic or bold fonts that are visible **
** in the original document but not in this text extract.          **
**                                                                 **
*********************************************************************







Revision and Configuration Management Data Collector for OpenVMS
User Guide






 December 2001
 
 This document provides information for installing and using the
 Revision and Configuration Management Data Collector software
 for Compaq OpenVMS.
 
 
 
 
 
 Revision/Update Information:    This manual replaces the manual
                             for the Revision and Configuration
                             Data Collector for OpenVMS Version
                             3.4
                             
 Operating System and Version:   Compaq OpenVMS Version 6.2 to
                             7.3 and higher
                             
 Software Versions:         RCM Server Version 4.0
                             RCM Data Collector Version 4.0 for
                             OpenVMS
                             
 Compaq Computer Corporation
December 2001

 2001 Compaq Information Technologies Group, L.P.

Compaq, the Compaq logo, AlphaServer, OpenVMS, DECevent, and VAX
are trademarks of Compaq Information Technologies Group, L.P. in
the U.S. and/or other countries. Windows is a trademark of
Microsoft Corporation in the United States and/or other
countries. All other product names mentioned herein may be
trademarks of their respective companies.

Confidential computer software. Valid license from Compaq
required for possession, use or copying. Consistent with FAR
12.211 and 12.212, Commercial Computer Software, Computer
Software Documentation, and Technical Data for Commercial Items
are licensed to the U.S. Government under vendor's standard
commercial license.

Compaq shall not be liable for technical or editorial errors or
omissions contained herein. The information is provided "as is"
without warranty of any kind and is subject to change without
notice. The warranties for Compaq products are set forth in the
express limited warranty statements accompanying such products.
Nothing herein should be construed as constituting an additional
warranty.

This service tool software is the property of, and contains
confidential technology of, Compaq Computer Corporation or its
affiliates. Possession and use of this software is authorized
only pursuant to the Proprietary Service Tool Software License
contained in the software or documentation accompanying this
software.

Compaq service tool software, including associated documentation,
is the property of and contains confidential technology of Compaq
Computer Corporation or its affiliates. Service customer is
hereby licensed to use the software only for activities directly
relating to the delivery of, and only during the term of, the
applicable services delivered by Compaq or its authorized service
provider. Customer may not modify or reverse engineer, remove, or
transfer the software or make the software or any resultant
diagnosis or system management data available to other parties
without Compaq's or its authorized service provider's consent.
Upon termination of the services, customer will, at Compaq's or
its service provider's option, destroy or return the software and
associated documentation in its possession.




                                                                 
                                                                 
                                                                 
                                                                 
                                                                 
                                                                 
                                                                 
                                                                 
                                                                 
                                                Table of Contents
                                                                 

Preface                                                       i

Overview                                                    1-1
How Does RCM Work?                                        1-1
OpenVMS Systems Supported by RCM                          1-2

Installing the RCM Data Collector for OpenVMS               2-1
RCM Data Collection Prerequisites                         2-1
Skills Required to Use RCM                                2-2
Installing the RCM Data Collector                         2-2
Installing DECevent                                       2-3
Deinstalling the RCM Data Collector for OpenVMS           2-3

Performing an RCM Data Collection                           3-1
Scheduling and Executing the RCM Data Collection          3-1
Configuring and Scheduling the Data Collection         3-1
Executing the Data Collection Manually                 3-4
Monitoring the Data Collection                         3-5
Stopping a Data Collection                             3-5
Transferring RCM Data Indirectly                          3-5
Why Transfer Data Indirectly?                          3-6
Manually Transferring Data                             3-6
Sending Data to Compaq Services                        3-6
Using DSNlink with RCM                                    3-7

Viewing Configuration Tree Data                             4-1
What are the Configuration Tree and the Reader?           4-1
Collecting Configuration Tree Data                        4-1
Viewing Configuration Tree Data                           4-2
Software Prerequisite                                  4-2
Viewing Data on the System                             4-2
Viewing Data on a Different System                     4-2

RCM Technical Support                                       5-1
RCM Technical Support                                     5-1
Contact the RCM Team                                      5-1

Appendix A - Files included in the Data Collector Kit       A-1

Appendix B - Sample Scenarios                               B-1
OpenVMS Clusters                                          B-1
Cluster Scenario 1                                     B-1
Cluster Scenario 2                                     B-2
Cluster Scenario 3                                        B-3

                                                                 
                                                                 
                                                                 
                                                                 
                                                                 
                                                                 
                                                                 
                                                                 
                                                                 
                                                          Preface
                                                                 
                                                                 
                                                                 

Purpose of this Document
This document describes the procedures for installing and running
the Revision and Configuration Management Data Collector software
on a Compaq OpenVMST system.

Intended Audience
This guide is intended for Compaq Services personnel who will
install and use RCM to collect revision and configuration data
from customer systems.

Structure of this Guide
This guide is divided into the following sections:
    Overview
    Installing the RCM Data Collector for OpenVMS
    Performing an RCM Data Collection
    Viewing Configuration Tree Data
    RCM Technical Support

Document Conventions
This guide uses the following document conventions:
Convention    Description
Courier       File names, commands, and user input
              are shown in courier typeface.
Italics       Italics emphasize important
              information, and indicate menu
              buttons, menu items, field names,
              section titles, and document titles.

More Information
For more information on the RCM tool, see the following URL:
     http://www.support.compaq.com/svctools/rcm/
     

                                                                 
                                                                 
                                                                 
                                                                 
                                                                 
                                                                1
                                                         Overview
                                                                 
                                                                 
                                                                 
This chapter provides an overview of the Revision and
Configuration Management Data Collector software for Compaq
OpenVMS. It contains the following sections:
    How Does RCM Work?
    OpenVMS Systems Supported by RCM

How Does RCM Work?
Revision and Configuration Management (RCM) provides revision and
configuration reporting for Compaq AlphaServer and Compaq VAX
systems running OpenVMS Versions 6.2 to 7.3 and higher. RCM uses
the following components to perform the data collection on an
OpenVMS system:
    RCM$DIR:RCM_START.COM - A DCL command procedure
   used to configure and schedule the data collection on
   each selected node.
    AlphaServer models DS20, ES40, ES45, DS20E, DS10,
DS10L, GS80, GS160, and GS320, require RCM to be
installed from the WEBES kit. For details of WEBES, see
the following URL:
     http://www.support.compaq.com/svctools/webes
     
    Compaq DECeventT is required for AlphaServer
   systems with FRU Table 4.0 (1200, 4X00, 8X00, GS60,
   GS140). DECevent is a hardware fault-management
   diagnostic tool that reads hardware configuration
   information from the error log. No Product
   Authorization Kit (PAK) is required for the error log
   translation feature of DECevent.
   For details of DECevent, see the following URL:
     http://www.support.compaq.com/svctools/decevent
                           
The RCM collected data is automatically transported to Compaq
Services using e-mail, FTP, or DSNlink. The data is then loaded
onto the RCM Server, which is maintained in Compaq by the RCM
team.
The Data Collector collects configuration and revision
information such as Firmware Revision levels (if available),
Layered Products Revisions, License information, Hardware
Configuration details, and HSJ/HSD/HSZ/HSG device information. On
systems that support FRU4 hardware logging, DECevent is used to
decode the FRU table. For OpenVMS systems V6.2 - V7.1.2, the FRU
utility included in the kit is used to write the FRU data from
memory to a file that DECevent can translate. For OpenVMS V7.2
and higher systems, the Analyze/System command CLUE FRU is used
to generate a dummy error log record containing the FRU4 entry.
The RCM Data Collector gathers additional hardware configuration
information on AlphaServer models DS20, ES40, ES45, DS20E, DS10,
DS10L, GS80, GS160, and GS320, where RCM from the WEBES kit is
installed. This detailed hardware configuration information is
called the Configuration Tree. This detailed configuration tree
can be viewed on the OpenVMS system using the frudump utility.
For more information, refer to Chapter 4, Viewing the
Configuration Tree Data.
The collected data for each node is written to a file with the
filename, RCMO-<nodename>-<yyyymmdd-mmhhss>.TXT. A HTML version
is also generated for each selected node. This gives the user a
convenient method of browsing the collected data. A .LIF file is
also generated for each node. This is used by the RCM Server to
request a ProPatch report which may be viewed through the
Electronic Site Management Guide (eSMG).
The RCM Server incorporates a web-based user interface that
enables authorized personnel in Compaq Customers Services to view
detailed configuration and change reports. Customers with premium
service contracts are able to view these configuration and change
reports through the eSMG.
Further information on using the RCM Server is available to
Compaq Services personnel in the RCM Server User Guide.

OpenVMS Systems Supported by RCM
RCM supports the following systems, running OpenVMS Version 6.2
to 7.3 and higher:
    All VAX systems
    All AlphaServer systems
AlphaServer models DS20, ES40, ES45, DS20E, DS10, DS10L, GS80,
GS160, and GS320, require RCM to be installed from the WEBES kit.
For details of WEBES, see the following URL:
     http://www.support.compaq.com/svctools/webes/



                                                                 
                                                                 
                                                                 
                                                                 
                                                                 
                                                                2
                    Installing the RCM Data Collector for OpenVMS
                                                                 
                                                                 
                                                                 
This chapter describes how you install and deinstall the Revision
and Configuration Management Data Collector for a Compaq OpenVMS
system. It contains the following sections:
    RCM Data Collection Prerequisites
    Skills Required to Use RCM
    Installing the RCM Data Collector
    Installing DECevent
    Deinstalling the RCM Data Collector for OpenVMS

RCM Data Collection Prerequisites
The following table lists the requirements for installing and
running the RCM Data Collector on an OpenVMS system. Requirements
may vary according to system.
Area     Requirements
Disk     5000 blocks of free disk space for
Space    each node on which you run the
         data collection.
Privileg     OPER
es           DIAGNOSE
             SYSPRV
             CMKRNL
             SYSLCK
             PHY_IO
Minimum      RCM Data Collector for
Software    OpenVMS kit Version 4.0
Version     OR
             RCM from WEBES kit V4.0 (plus
            any associated Service PAKs) .
             DECevent Version 3.3
            installed on AlphaServers with
            FRU4 support
             DSNlink Version 2.2 or higher
            if DSNlink is to be used as a
            transport mechanism
HSG      To collect HSG information the
Informat Command Console LUN (CCL) should
ion      be enabled by the following Array
         Controller command:
         SET THIS_CONTROLLER
         COMMAND_CONSOLE_LUN
Note: If you are running OpenVMS Alpha V7.1-2, it is important to
have the latest patches installed, in particular, the
VMS712_PTHREADS-V0300 patch. If this patch is not installed, the
data collection from HSZ/G devices may fail with an error similar
to the following:
%DCL-W-ACTIMAGE, error activating image CMA$TIS_SHR-CLI-E-
IMGNAME, image file
$1$DKC0:[SYS0.SYSCOMMON.][SYSLIB]CMA$TIS_SHR.EXE-SYSTEM-F-
SHRIDMISMAT, ident mismatch with shareable image
The latest version of the RCM Data Collector software is
available from the following URL:
http://www.support.compaq.com/svctools/rcm/
For a list of files included with the RCM Data Collector kit,
see:
Appendix A - Files included in the Data Collector Kit.

Skills Required to Use RCM
To collect RCM data and generate RCM reports, you should have
practical experience in the following areas:
    Performing system administration tasks
    Using a web browser application

Installing the RCM Data Collector
This section describes how to install the RCM Data Collector for
OpenVMS from the RCM-only kit.
The RCM collector should normally only be installed on one node
in a Cluster and data can be collected from all nodes that can
access the collection disk. For Clusters with multiple system
disks, it is recommended that RCM be installed on each system
disk.
Note: For AlphaServers with Configuration Tree (CT) 5.0 or 6.0,
you need to install RCM from the WEBES V4.0 kit to gather the
hardware information. This is because RCM on CT machines depend
on the services of the WEBES common components to read the
Configuration Tree hardware information. The following systems
are the CT systems supported by RCM: DS10, DS10L, GS80, DS20,
DS20E, ES40, ES45, GS160, and GS320. If you are installing RCM on
these models, please use the WEBES Install Guide available from
the following URL:
http://www.support.compaq.com/svctools/webes
The RCM Data Collector for OpenVMS kit Version 4.0 is in a self-
extracting executable format, and once extracted, it uses PCSI as
the installation method. To install the Data Collector, follow
these steps:
1.   Extract the self-extracting executable file using
   the following command:
   $ RUN <kitname>
   For example: RUN RCM_AXPVMS_V0400-475.EXE
   This creates the .PCSI kit file called
   DEC-AXPVMS-RCM-V0400-475.PCSI. The build number at the end
   of the kit name may change.
2.   Decide where you want to install RCM.
   Note: It must be installed on a disk that is accessible by
   all the nodes from which data will be collected.
3.   To install RCM, enter the following command:
   $ PRODUCT INSTALL RCM /DESTINATION = <disk><dir>
   /SOURCE=<disk><dir> /HELP
   Replace the destination <disk><dir> with the area you want
   to install the kit in, and replace the source <disk><dir>
   with the location of the extracted PCSI file. If the
   destination area is not specified, then RCM will be
   installed to the following area:
   SYS$SYSDEVICE:[VMS$COMMON]
   Note: The installation process will create a subdirectory
   [.RCM] in the destination area.

Installing DECevent
For the following AlphaServer (1200, 4X00, 8X00, GS60, GS140)
systems, you should ensure that DECevent is installed. For help
during this installation, refer to the DECevent documentation,
available from the following URL:
http://www.support.compaq.com/svctools/decevent/

Deinstalling the RCM Data Collector for OpenVMS
With standalone versions of RCM, the deinstallation procedure
doesn't automatically remove RCM Archive collections. If you
want to remove the archived collections during the
deinstallation, you must first manually define the logical
RCM$ARCHIVE_REMOVE as follows:
$ DEFINE RCM$ARCHIVE_REMOVE TRUE
Note: RCM kits installed from WEBES include a prompt in the
deinstallation procedure that asks whether you want to keep
the RCM Archive collections, so it is unnecessary to define
the RCM$ARCHIVE_REMOVE logical manually.
To deinstall the RCM Data Collector for OpenVMS, do the
following:
1.   Enter the following command:
   $ product remove rcm
2.   Follow the instructions displayed on the screen.
3.   For information on deinstalling DECevent, refer to
   the DECevent documentation, available from the
   following URL:
   http://www.support.compaq.com/svctools/decevent
   Note: During the deinstallation, the RCM configuration
   file is saved as SYS$SYSTEM:RCMCONFIG.CFG, so that it can
   be automatically restored if RCM is reinstalled.

                                                                 
                                                                 
                                                                 
                                                                 
                                                                 
                                                                3
                                Performing an RCM Data Collection
                                                                 
                                                                 
                                                                 
This chapter describes how you can schedule and execute an RCM
data collection for a Compaq OpenVMS system. It contains the
following sections:
    Scheduling and Executing the RCM Data Collection
    Transferring RCM Data Indirectly
    Using DSNlink with RCM

Scheduling and Executing the RCM Data Collection
This section describes how to configure the RCM data collection,
including configuring the data collection schedule, and how to
execute and monitor the data collection. It describes the
following topics:
    Configuring and Scheduling the Data Collection
    Executing the Data Collection Manually
    Monitoring the Data Collection
    Stopping a Data Collection
Note: Each time an RCM data collection runs on a system, the
results of any previous collections are archived in the
RCM$ARCHIVE directory. By default, the 10 previous collections
are stored in this directory. You can change the directory and
the number of collections that are stored by modifying the MAX
ARCHIVES option in the configuration file.

Configuring and Scheduling the Data Collection
To configure and schedule the data collection, execute the
RCM$DIR:RCM_START.COM procedure, optionally supplying the name of
a configuration file by entering the following command in the
directory where you want the collected RCM data to be stored:
$ @RCM$DIR:RCM_START <ConfigurationFileName>.CFG
The configuration file may be generated in two ways:
1.   Before you invoke RCM_START, you can edit the
  configuration file, <filename.CFG>, using
  RCM$DEFAULTS.CFG as a template, or
2.   Invoke RCM_START and you are prompted for the
following configuration information:

Prompt            Description
COMPANY NAME      The name of the company owning
                  the system.
CONTACT NAME      The name of your contact in the
                  company owning the system.
CONTACT           The telephone number of your
TELEPHONE         contact in the company owning
                  the system.
CONTACT EMAIL     The e-mail address of your
                  contact in the company owning
                  the system.
TECHNICAL         The name of the technical
ACCOUNT MANAGER   account manager.
ACCOUNT MANAGER   The mail address of the
EMAIL             technical account manager (must
                  end with 'compaq.com').
CUSTOMER ACCESS   The RCM access identifier for
ID                this system. This will be
                  supplied by your Compaq Services
                  representative.
TRANSPORT OPTION  The method for returning the
                  collected data to Compaq
                  Services. You can specify one of
                  the following:
                  F - automatically FTP the data.
                  This is the default.
                  E - automatically e-mail the
                  data.
                  D - automatically send the data
                  using DSNlink. For further
                  information on DSNlink, see
                  Using DSNlink with RCM section.
                  M - do not automatically
                  transport the data. If you wish
                  to manually transfer collected
                  data to Compaq Services, please
                  see the Transferring RCM Data
                  Indirectly section.
COLLECTION        The frequency at which you want
FREQUENCY         to schedule data collections.
                  Enter one of the following:
                  N - run a single collection. (a
                  collection will started
                  immediately)
                  D - run the collection daily.
                  W - run the collection weekly.
                  M - run the collection monthly.
                  This is the default.
                  Q - run the collection
                  quarterly.
                  Where an option other than N is
                  specified, RCM collections will
                  run at the specified intervals.
                  For each collection, a detached
                  scheduling process called RCM
                  will be started. This process
                  will hibernate until the next
                  scheduled collection time. In
                  order to survive system reboots,
                  an entry is made to the SYSMAN
                  STARTUP database that will
                  restart the RCM scheduling
                  process on system startup. The
                  entry can be seen by using the
                  following command:
                  MCR SYSMAN STARTUP SHOW FILE
NEXT COLLECTION   Time to run the next data
TIME              collection in the format dd-mm-
                  yyyy hh:mm. To run a collection
                  immediately, enter N.
MAX ARCHIVES      The number of collections to
                  keep in the RCM Archive area.
                  Default value is 10.
ARCHIVE           Default is :
DIRECTORY         RCM$ROOT:[RCM_ARCHIVE]
COLLECTION        Specify directory to use for RCM
DIRECTORY         Collections. Default is
                  RCM$ROOT:[DATA]
LOCAL SITE        Answer Y to have collected data
                  copied to a local system.
                  Default is N.
                  If answer is Y, you will be
                  prompted for Local Transport
                  option:
Local Transport   If FTP (default) is specified,
Option            the following additional prompts
(EMAIL/FTP/DECne  are displayed:
t):               Local FTP Hostname       :
                  Local FTP Login Username :
                            Password       :
                  Local FTP Directory      :
                  Local FTP Procedure      :
                  
                  If DECnet is specified, the
                  following additional prompts are
                  displayed:
                  Local DECnet Hostname       :
                  Local DECnet Username       :
                               Password       :
                  Local DECnet Directory      :
                  
                  Note: The local FTP or DECnet
                  password is used only for the
                  local transport of the collected
                  data within the client
                  environment and is stored in
                  encrypted form in the
                  configuration file. It is
                  removed from the configuration
                  file before the collected data
                  is sent to Compaq.
                  
                  If Email is specified as the
                  Local Transport Option, the
                  following prompt is displayed:
                  Local EMAIL Address :
RUN ON REBOOT     Answer Y to configure RCM to run
                  automatically when the system
                  reboots. Default is N.
NODES             If you are running the
                  collection in a cluster
                  environment, the software
                  detects each node on the system.
                  You select if you want the data
                  collection to run on each node.
                  The node you run the
                  RCM$DIR:RCM_START command on is
                  automatically selected. Only
                  nodes which have the collection
                  disk mounted can be selected.
<node> SYSTEM     The serial number of each node
SERIAL NUMBER     on which you are running the
                  data collection. If the Data
                  Collector software does not
                  detect this number, then you
                  will be prompted to enter it.
If you selected to run a single, once-off data collection, the
data collection will start immediately as a background process.
If you set up a schedule for collection, the data collection will
begin at the next scheduled interval that you selected.
When the data collection is complete, the data is sent to Compaq
Services, using the transport method you specified.
The configuration details are saved in a configuration file using
the file name you provided. If you want to change any details,
you can run RCM_START.COM again, providing the same filename, or
you can edit the configuration file. If you edit the
configuration file, you will see the following additional
configuration options:
Configuration     Description
option
FTP AREA          The default is
                  rcm.support.compaq.com/to_rcm/
FTP PROCEDURE     This is a feature that allows a
                  client to use a custom FTP
                  Command procedure in order to
                  send the collected data to
                  Compaq. If you want to use a
                  custom DCL procedure to
                  transfer the data, specify the
                  location of the procedure using
                  this option. RCM will pass the
                  RCM Zip file as parameter P1.
EMAIL ADDRESS     The default is
                  rcm.data@compaq.com
LOCAL FTP         This is a feature that allows a
PROCEDURE         client to use a custom FTP
                  Command procedure in order to
                  copy the collected data to a
                  local system.
SUPPRESS IP       This is set to N by default. If
ADDRESSES         this is set to Y then client IP
                  addresses are not collected.
FCT BINARY IMAGE  The default is N. If it is set
                  to Y, then the Configuration
                  Tree 5.0 or 6.0 data is written
                  to a binary file called
                  <node>.CT5. This would normally
                  be set to Y, in consultation
                  with your Technical Account
                  manager, as Compaq Services use
                  it for debugging purposes.
DATA FOR          This option allows only LIF
ANALYSIS          data to be sent from the
                  customer site. Permitted values
                  are: Full, Lif or None. The
                  default is F, which means all
                  RCM data is sent to Compaq.
                  Setting this option to L means
                  only the LIF files are sent and
                  the only reports available will
                  be the ProPatch reports.
Note: The FTP PROCEDURE and the LOCAL FTP PROCEDURE items in the
preceding table are used to specify custom DCL procedures. These
procedures enable you to use FTP to transport collected data when
the RCM supported methods do not work. RCM currently supports
both Compaq's TCP/IP products and Process Software's Multinet
TCP/IP products.

Executing the Data Collection Manually
If you set up a schedule for data collection when you entered
configuration information, the data collection automatically
executes at the scheduled times. You can also execute a once-off
data collection that will start immediately.
To execute a once-off data collection, enter the following
command in the directory where you want the collected RCM data to
be stored:
$ @RCM$DIR:RCM_START -now
This executes the data collection using the most recent
configuration file. If you have not already configured the RCM
Data Collector, you will be prompted for the required
information, as described above. The data collection will begin
immediately.
To collect data only on the node that you are currently logged
into, enter the following command:
$ @RCM$DIR:RCM_START -now -thisnode
When the data collection is complete, the transfer method you
selected during the configuration process is executed. A local
version of the collected data is created in the installation
directory. You can view this data in two formats:
RCMO-<nodename>-<timestamp>.html or
RCMO-<nodename>-<timestamp>.txt
Please note that this HTML file is provided for convenience but
is not the official RCM report, which must be obtained from the
RCM server or from the eSMG.

Monitoring the Data Collection
To monitor the data collection while it is executing, enter the
following command:
$ @RCM$DIR:RCM_STATUS
For each node on which the data collection is running, the
progress of the data collection is displayed. RCM_STATUS will
loop every 30 seconds until the data collection is completed on
all nodes. These data files can be transported to Compaq Services
automatically, or you may transfer them manually, depending on
the configuration options you selected.
    If you selected to automatically transport the
   data to Compaq Services, the status of the transport
   action is displayed.
    If you selected to manually transport the data to
   Compaq Services, instructions on how to do this are
   displayed.
If you want to check the status of a collection that has
finished, and the result of the data transport, you can check the
RCM$DATA:RCMO-<node name>-<time stamp>-MASTER.LOG file.
If the data collection is paused for an unusually long period of
time, or some of the collection log files are growing extremely
large, or the disk is filling with log information, you may stop
the data collection by entering the following command:
$ @RCM$DIR:RCM_STOP
This command displays each RCM process running on each node in
the cluster, and prompts you if you want to kill each process in
turn.

Stopping a Data Collection
You can stop all RCM processes by executing the following
command:
RCM$DIR:RCM_STOP
This will show any RCM_COLLECT processes that are currently
active and ask you if you wish to stop them. This should only be
necessary if problems occur and the collection process seems to
be taking too long.
If the RCM scheduling process is active, you will be asked if you
wish to stop it. Stopping this process will remove the entry in
the SYSMAN STARTUP database and the RCM scheduling process will
not restart on a system reboot.
To start RCM collections again, RCM_START must be run.

Transferring RCM Data Indirectly
This section describes how to indirectly transfer data collected
by RCM back to Compaq Services for analysis. It describes the
following topics:
    Why Transfer Data Indirectly
    Manually Transferring Data
    Sending Data to Compaq Services

Why Transfer Data Indirectly?
Some systems running RCM do not have a direct connection to the
Internet. For example, the target system (or systems) may be one
of the following:
    A standalone system with no Internet connection
    A system on a network, where no other system on
   the network has a direct Internet connection
    A system on a network, where another system on the
   network has a direct Internet connection
In these situations, you can manually transfer the collected data
to a system that has a direct Internet connection. After the data
is transferred, you need to send the data to Compaq Services for
analysis.
The method for manually transferring the data and the methods for
sending the data to Compaq Services are described in the
following sections.

Manually Transferring Data
When the data collection is completed, the collected data is
saved into the following files:
RCMO-<nodename>-<timestamp>.ZIP (zipped file)
RCMO-<nodename>-<timestamp>.UUE (uuencoded file, if e-mail is
used)
You can copy these files to a machine with a direct Internet
connection.
Note: Do not change the name of the files, or their extensions.

Sending Data to Compaq Services
When you have moved the files containing the collected RCM data
to a machine with an Internet connection, you can send the data
to Compaq Services using one of the following options:
    Microsoft Exchange
    DSNlink
    FTP
    VMSMAIL
Each of these methods is described as follows:
Microsoft Exchange
To mail the data using Microsoft Exchange; using FTP, send the
zipped (.ZIP) file in binary mode to the PC and e-mail the (.ZIP)
file, as an attachment, to the following address:
     rcm.data@compaq.com
DSNlink
To send the data using DSNlink, enter the following command:
$ DSN COPY/TOOL=RCM RCMO-<nodename>-<timestamp>.ZIP
Note: To check the requirements for using DSNlink, see the Using
DSNlink with RCM section.
FTP
To FTP the data, send the zipped (.ZIP) file in binary mode,
using anonymous FTP, to the following location:
     rcm.support.compaq.com/to_rcm/
VMSMail
To mail the data using VMSMAIL, mail the uuencoded (.UUE) file to
the following address:
     rcm.data@compaq.com

Using DSNlink with RCM
You can use DSNlink to send RCM data to Compaq Services, if you
are transferring data automatically, or if you are transferring
data manually. However, in order to use DSNlink to transfer RCM
data, you must meet the following requirements:
    You must have DSNlink Version 2.x or higher
   installed on the system from which you want to transfer
   the data. If you are transferring data automatically,
   DSNlink must be installed on the machine where you
   installed the Data Collector.

                                                                 
                                                                 
                                                                 
                                                                 
                                                                 
                                                                4
                                  Viewing Configuration Tree Data
                                                                 
                                                                 
                                                                 
This chapter describes the Configuration Tree, how to collect it,
and how to view it using a browser. It contains the following
sections:
    What are the Configuration Tree and the Reader?
    Collecting Configuration Tree Data
    Viewing Configuration Tree Data

What are the Configuration Tree and the Reader?
The Configuration Tree describes the hardware in an AlphaServer
system for models DS20, ES40, ES45, DS20E, DS10, DS10L, GS80,
GS160, and GS320. It is created and maintained by the SRM console
code and always represents the current configuration of the
system.
The Configuration Tree is read from memory and converted to human-
readable format by the Configuration Tree Reader. The RCM Data
Collector installs the Configuration Tree Reader the first time
the RCM Data Collector is executed.
The syntax of the command is as follows:
@rcm$root:[ct5.bin]frudump [-i imagefile][-v]
  The following options are available:
      -i imagefile this enables the CT Reader to read
     from an image file, rather than from memory. The full
     path and filename must be specified as imagefile. This
     option is typically only used in complex
     troubleshooting situations.
      -v returns the current version of the tool.

Collecting Configuration Tree Data
To collect the Configuration Tree data, do the following:
1.   Execute the command:
  @RCM$ROOT:[CT5.BIN]FRUDUMP
2.   The data is captured from memory and written to
  two files in the directory RCM$ROOT:[CT5.OUTPUT] These
  files are called <NODENAME>_<DATE>_<TIME>_HARDWARE.HTML
  and <NODENAME>_<DATE>_<TIME>_TREE.HTML where:
     <NODENAME> is the node name of the system on which the FCT
     Reader was run
     <DATE> is the date the FCT Reader was run (using the format
     yyyymmdd)
     <TIME> is the time the FCT Reader was run (using the format
     hhmmss).
     The above filename convention is used to:
     a) Allow a common directory to be used in a clustered
     environment
     b) Allow a means of examining differences between two
     collections for a node.

Viewing Configuration Tree Data
This section describes how you use a browser to view
Configuration Tree data.

Software Prerequisite
You must have one of the following browsers installed on the
machine where you intend to view the data:
    Internet Explorer Version 4.0 or higher
    Netscape Navigator Version 4.0 or higher

Viewing Data on the System
To view Configuration Tree data on the system where FRUDUMP was
executed, do the following:
1.   Copy the node/date/time specific files to
  HARDWARE.HTML and TREE_MAIN.HTML. For example, if you
  are interested in node X, date Y, and time Z then do
  the following:
  a) Copy the file X_Y_Z_HARDWARE.HTML to HARDWARE.HTML
  b) Copy the file X_Y_Z_TREE.HTML to TREE_MAIN.HTML
2.   Open a browser.
3.   Open the file TREE_MAIN.HTML in the directory
  RCM$ROOT:[CT5.OUTPUT]
4.   The data is displayed in the browser.
The next time you run the FRUDUMP command, you need to copy the
new NODENAME_X_Y_Z_TREE.HTML and NODENAME_X_Y_Z_HARDWARE.HTML
files as indicated above.

Viewing Data on a Different System
You can view the Configuration Tree data on a different system
from the machine where FRUDUMP was executed. For example, you may
want to view it on a Windows-based system. The first time you
view the data, do the following:
1.   Create a temp directory for which the browser has
  read access on the different machine.
2.   Copy all the files from the directory
  RCM$ROOT:[CT5.OUTPUT] to this temp directory.
3.   Copy the node/date/time specific files to
  HARDWARE.HTML and TREE_MAIN.HTML. For example, if you
  are interested in node X, on date Y, and time Z, then
  do the following:
  Copy the file X_Y_Z_HARDWARE.HTML to HARDWARE.HTML
  Copy the file X_Y_Z_TREE.HTML to TREE_MAIN.HTML
4.   Open a browser.
5.   Open the file TREE_MAIN.HTML from the temp
  directory.
The next time you run the FRUDUMP command, the new
NODENAME_X_Y_Z_TREE.HTML and NODENAME_X_Y_Z_HARDWARE.HTML files
need to be copied to the temp directory. Then repeat steps 3, 4
and 5 to view the new information.

                                                                 
                                                                 
                                                                 
                                                                 
                                                                 
                                                                5
                                            RCM Technical Support
                                                                 
                                                                 
                                                                 
This chapter provides information on accessing RCM technical
support resources. It contains the following sections:
    RCM Technical Support
    Contact the RCM Team

RCM Technical Support
If you have a problem using any aspect of RCM including the Data
Collectors, data transport or the user interface, please contact
us, at the following address:
     rcm.support@compaq.com
To help us resolve any problems quickly, please send us the
following information:
1.   Your name, RCM user name (registration name), and
   contact details.
2.   The access ID (entered during data collector
   installation), hostname, and serial number of the
   system on which you collected data.
3.   The platform, system serial number, operating
   system version, and data collection utility versions
   and build numbers.
4.   The platform, operating system name and version,
   and browser name and version on the system from which
   you accessed the RCM Server.
5.   Details of the problem, including any log files,
   error files, or messages generated by the system.

Contact the RCM Team
The RCM team welcomes any queries or comments that you may have
about RCM. If you have questions or comments, or you would like
to participate in future field tests or early release programs,
contact the Product Manager, Tom Kilgarriff.
     mailto:rcm.feedback@compaq.com

                                                                 
                                                                 
                                                                 
                                                                 
                                                                 
                                                                A
            Appendix A - Files included in the Data Collector Kit
                                                                 
                                                                 
                                                                 
The RCM OpenVMS Data Collector kit contains the following files:
File              Details
RCM_START.COM     DCL procedure to start
                  the RCM Collection.
RCM_COLLECT.COM   DCL procedure that is
                  run on each selected
                  node.
RCM_STATUS.COM    DCL procedure to check
                  status of collection.
RCM_STOP.COM      DCL procedure to abort
                  an RCM Collection.
RCM_HTML.COM      DCL procedure to
                  generate the local HTML
                  files.
RCM_PROPATCH.COM  DCL procedure to
                  generate LIF files for
                  ProPatch
ZIP-ALPHA.EXE     Info-ZIP ZIP utility for
                  OpenVMS Alpha.
ZIP-VAX.EXE       Info-ZIP ZIP utility for
                  OpenVMS VAX.
RCM$DEFAULTS.CFG  Template Configuration
                  file.
RCMVMS_V4_UG.TXT  A text version of this
                  User Guide.
HSDSA-SCRIPT-     Utility to collect
ALPHA.EXE         HSJ/HSD information on
                  OpenVMS Alpha.
HSDSA-SCRIPT-     Utility to collect
VAX.EXE           HSJ/HSD information on
                  OpenVMS VAX.
RCMHS.EXE         Utility to read HSZ/G
                  data
RCM$LICS_ALPHA.L  Modified version of
IST               DASC$LICS.LIST file from
                  DASC V5.4.
RCM$LICS_VAX.LIS  Modified version of
T                 DASC$LICS.LIST file from
                  DASC V5.4.
RCM$SOFT_ALPHA.L  Modified version of
IST   V5.4.       DASC$SOFT.LIST file from
                  DASC
RCM$SOFT_VAX.LIS  Modified version of
T                 DASC$SOFT.LIST file from
                  DASC V5.4.
UUENCODE_ALPHA.O  UUencode utility object
BJ                file for Alpha
UUENCODE_VAX.OBJ  UUencode utility object
                  file for VAX
FRU.OBJ           Extracts FRU Table 4
                  from memory for DECevent
                  to read.
RCM_SETUP.COM     Procedure used by PCSI
                  when installing RCM.
RCM_DEINSTALL.CO  Procedure used by PCSI
M                 when removing RCM.
RCM.RELEASE_NOTE  Release Notes. Renamed
S                 at installation to
                  SYS$HELP:RCM040.RELEASE_
                  NOTES
CT5150_OVMS.EXE   Alpha OpenVMS Self-
                  extracting executable
                  with CT5 reader.


                                                                 
                                                                 
                                                                 
                                                                 
                                                                 
                                                                B
                                    Appendix B - Sample Scenarios
                                                                 
                                                                 
                                                                 
This appendix describes some typical scenarios that are
encountered using the RCM Data Collector for OpenVMS. It includes
step-by-step instructions for each scenario to ensure that RCM
(and in some cases WEBES) continues to perform as expected.

OpenVMS Clusters
The three scenarios in this appendix, describe how to change a
member of an OpenVMS cluster. An existing member (an 8400) is to
be replaced by a GS160. The node name of the GS160 will be the
same as that of the 8400, that is, nodex. In the following
scenarios, the step-by-step instructions should be followed
carefully, so that RCM (and WEBES) remain in a consistent,
stable, and working state.

Cluster Scenario 1
If you already have WEBES Version 4.0 and Service Pack 2
installed on the cluster, then you should do the following:
Stage 1: Remove the 8400
1.   Remove the 8400 (nodex) from the list of WEBES
   cluster nodes by running the following command:
   @svctools_home:[bin]cluster remove nodex
   where nodex is the node to be removed from the cluster.
2.   Remove the 8400 (nodex) from the list of RCM
   cluster nodes by running the following command (from
   one of the other cluster members):
   @RCM$DIR:RCM_START <ConfigurationFileName>.CFG
   where <ConfigurationFileName>.cfg is the name of the
   configuration file that you used when you set up RCM
   initially.
   Note: The default configuration file name is rcm$defaults.cfg
   After you run the command, ensure that the 8400 (nodex) has
   been removed from the list of cluster members. If it has not
   been removed, you must manually edit the configuration file,
   and remove all nodex entries.
Stage 2: Bring in the GS160
1.   Once the GS160 is in the cluster, run the
   following command from one of the other cluster members
   to register the GS160 (nodex) with WEBES:
   @svctools_home:[bin]cluster install nodex
   where nodex is the name of the new cluster member (the
   GS160).
2.   Once you have registered nodex with WEBES,
   register the new cluster member (nodex) with RCM, by
   running the following command on one of the other
   cluster members:
   @RCM$DIR:RCM_START <ConfigurationFileName>.CFG
   where <ConfigurationFileName>.cfg is the name of the
   configuration file that you used when you set up RCM
   initially.
   Note: The default configuration file name is rcm$defaults.cfg
   After you run the command ensure that the GS160 (nodex) is
   included in the list of cluster members. If it is not
   included, you must manually edit the configuration file,
   by adding the nodename and the serial number of the
   missing cluster member.
3.   Run the RCM Data collector on any of the cluster
   members. A cluster-wide data collection will start.
   After the data has been transported to Compaq, check
   out the configuration reports to ensure that all the
   cluster members have been reported correctly.

Cluster Scenario 2
If you only have the standalone version of RCM installed on the
production cluster, do the following:
Stage 1: Remove RCM
1.   From any of the cluster members, remove RCM by
   doing the following:
       a.   Look at the value for the logical rcm$root by
          running the following command:
          sh log rcm$root
       b.   Remove the RCM product by running the following
          command:
          $ product remove rcm
       c.   Navigate to the parent directory of the RCM
          product, for example, if the rcm$root logical value is
          DISK$AXPVMSRL72:[SYS0.SYSCOMMON.RCM.], then run the
          following command:
          set def DISK$AXPVMSRL72:[SYS0.SYSCOMMON]
       d.   Make sure the RCM directory has been removed
          (delete it if necessary).
Stage 2: Remove the 8400
Remove the 8400 (nodex) from the cluster as described in stage 1
of the section Cluster Scenario 1.
Stage 3: Bring in the GS160
1.   Once the GS160 is part of the cluster, install the
   latest version of WEBES using any of the cluster
   members.
2.   Install the latest WEBES Service Pack
   Note: It is convenient to use the same cluster member as
   before for this step.
3.   Configure RCM (if it was not configured as part of
   the WEBES or WEBES Service Pack installations), by
   running the following command:
   @RCM$DIR:RCM_START <ConfigurationFileName>.CFG
   where <ConfigurationFileName>.cfg is the name of a
   configuration file.
   Note: The default configuration filename is
   rcm$defaults.cfg.
   If you configure RCM using the above command, ensure that
   all the cluster members are included in the list of nodes.
   If they are not included, you must manually edit the
   configuration file, adding both the nodename and the
   serial number of the missing cluster members.
   If RCM was configured as part of the WEBES or WEBES
   Service Pack installation, check the configuration file,
   and ensure that all the cluster members and their serial
   numbers are included.
4.   Run the RCM Data collector on any of the cluster
   members. A cluster-wide data collection will start.
   After the data has been transported to Compaq, check
   the configuration reports to ensure that all the
   cluster members have been reported correctly.

Cluster Scenario 3
If you have WEBES or RCM installed in a directory that is not
seen across all the cluster members (including the new GS160),
then please do the following:
1.   Remove WEBES (if it is installed), by running the
   following command:
   product remove webes
2.   Remove RCM (if it is installed), by doing the
   following:
       a.   Look at the value for the logical rcm$root by
          running the following command:
          sh log rcm$root
       b.   Remove the RCM product by running the following
          command:
          $ product remove rcm
       c.   Navigate to the parent directory of the RCM
          product, for example, if the rcm$root logical is
          DISK$AXPVMSRL72:[SYS0.SYSCOMMON.RCM.], then run the
          following command:
          set def DISK$AXPVMSRL72:[SYS0.SYSCOMMON]
       d.   Ensure that the RCM directory has been removed
          (delete it if necessary).
3.   Install the latest version of WEBES, specifying a
   destination directory which can be seen by all cluster
   members by running the following command:
   product install webes/destination=device:[directory]
   where device:[directory] can be seen by all cluster
   members.
   Note: The product will install in sys$common by default.
4.   Ensure that you select RCM as one of the
   components during the WEBES installation.
5.   Install the latest WEBES Service Pack.
   Note: It is convenient to use the same cluster member as
   before for this step.
6.   Configure RCM (if it was not configured as part of
   the WEBES or WEBES Service Pack installation), by
   running the following command:
   @RCM$DIR:RCM_START <ConfigurationFileName>.CFG
   where <ConfigurationFileName>.cfg is the name of a
   configuration file.
   Note: The default configuration filename is
   rcm$defaults.cfg.
   If you configure RCM using the above command, ensure that
   all the cluster members are included in the list of nodes.
   If they are not included, you must manually edit the
   configuration file, adding both the nodename and the
   serial number of the missing cluster members.
   If RCM was configured as part of the WEBES or WEBES
   Service Pack installation, check the configuration file,
   and ensure that all the cluster members and their serial
   numbers are included.
7.   Run the RCM Data collector on any of the cluster
   members. A cluster-wide data collection will start.
   After the data has been transported to Compaq, check
   the configuration reports to ensure that all the
   cluster members have been reported correctly.


