Document revision date: 30 March 2001

## DECamds User's Guide

Previous | Contents | Index

### A.5.1 Starting, Stopping, and Reloading DECamds

To start and stop the Data Provider driver, enter the following command. (Use this command if a node will be used to both provide and collect system data.)

    $ @SYS$STARTUP:AMDS$STARTUP.COM [parameter]

where the optional parameter is one of the following:

NODRIVER | Defines the default input and output logicals on the Data Analyzer node driver. Use this parameter on the Data Analyzer node where the Data Provider driver is not running. It is the default.
START | Starts the Data Provider driver.
STOP | Stops the Data Provider driver.
RELOAD | Loads a new Data Provider driver. Use this parameter when installing a new version of DECamds.

Note If you use the OpenVMS Snapshot Facility, stop the DECamds Data Analyzer and Data Provider node drivers before taking a system snapshot.

## A.6 Postinstallation Tasks on a Data Analyzer Node

Perform the following tasks after installing the DECamds Data Analyzer:

1. If you were previously running an earlier version of DECamds, check the differences between the .DAT or .COM files on your system and the associated .TEMPLATE files provided with the new kit. Change your existing files as necessary.

   Note The new .TEMPLATE files may contain important changes. However, to avoid altering your customizations, the upgrade procedure does not modify your existing customized versions of these files. Check the new .TEMPLATE versions of these files provided with the kit, and make the appropriate change to your files.

2. Modify default DECamds security files on each Data Analyzer node.
   The security files must be modified to implement fixes (fixes require write access). Refer to Section 1.3 for complete instructions about designing security files.
3. Define the system directory logical name AMDS$SYSTEM.
   To define the logical name AMDS$SYSTEM on systems running the Data Analyzer but not the Data Provider, enter the following command:

       $ @SYS$STARTUP:AMDS$STARTUP.COM NODRIVER

   This command requires SYSNAM privilege. The NODRIVER parameter specifies that the procedure is to define the input and output logical names in AMDS$LOGICALS.COM.
4. Modify user accounts as needed.
   To use DECamds, user accounts require certain privileges and quotas:
   - Using the Data Analyzer node for data collection (read access) requires TMPMBX, NETMBX, and OPER privileges.
   - Performing fixes (write access) requires the CMKRNL privilege in addition to TMPMBX, NETMBX, and OPER.
   - Using the AMDS$STARTUP.COM to start, stop, or reload the Data Provider requires at least TMPMBX, NETMBX, SYSNAM, LOG_IO, and CMKRNL privileges.
5. Start the application.
   For example, the following command starts DECamds with all input files read from AMDS$SYSTEM and all output files written to the current default directory. Only data from group A nodes and group B nodes is displayed.

       $ AVAIL /CONFIGURE=AMDS$SYSTEM /LOG_DIRECTORY=SYS$LOGIN-
       _$/GROUP=(GROUP_A, GROUP_B)

   See Chapter 2 for startup options.

## A.7 Starting to Use the Data Provider

Before starting to use the Data Provider, you need to move and remove several files to make the Data Provider RMDRIVER part of OpenVMS.

Move these Files

Move the following files:

File | Old Directory Location | New Directory Location
--- | --- | ---
AMDS$DRIVER_ACCESS.DAT | SYS$COMMON:[AMDS] | SYS$COMMON:[SYSMGR]
AMDS$LOGICALS.COM | SYS$COMMON:[AMDS] | SYS$COMMON:[SYSMGR]

These new directory locations should not affect previous copies of AMDS$DRIVER_ACCESS.DAT that are in the AMDS$SYSTEM directory because the AMDS$SYSTEM logical is now a search list for SYS$COMMON:[AMDS] and SYS$COMMON:[SYSMGR]. Previous copies of the files will still be valid; however, new copies of the files will be placed in the new locations.

Delete this File

Also, because the installation replaces the following file, remove it from your system:

       SYS$COMMON:[AMDS]AMDS$RMCP.EXE

Data Provider Commands

To start to use the Data Provider, perform either of the following tasks:

- Run the SYS$STARTUP:AMDS$STARTUP START command procedure at the OpenVMS DCL prompt ($).
- Add the @SYS$STARTUP:AMDS$STARTUP START command to the SYSTARTUP_VMS.COM command file in the SYS$MANAGER directory.

## A.8 Determining and Reporting Problems

If you encounter a problem while using DECamds, report the problem to Compaq. Depending on the nature of the problem and the type of support you have, take one of these actions:

- If your software contract or warranty agreement entitles you to telephone support, contact a Compaq support representative.
- If the problem is related to the DECamds documentation, see the Preface of this manual for instructions.

## A.9 Running the Installation Verification Procedure Separately

Usually the Installation Verification Procedure (IVP) runs during installation. Should system problems occur after you install DECamds, check the integrity of installed files by executing the following command procedure:

    $ @SYS$TEST:AMDS$IVP.COM

The IVP leaves the Data Provider in the same state in which it was found. For example, if the Data Provider is running, the IVP stops and starts it.

## Appendix B
DECamds Files and Logical Names

The DECamds Data Analyzer installation procedure installs files and defines logical names to customize the environment.

The installation procedure defines all logical names in executive mode in the system table (with the /SYSTEM /EXECUTIVE qualifiers). However, you can define logical names in /JOB or /GROUP tables, preceding the system definitions.

Table B_1 and Table B-2 explain the files installed and logical names defined with the Data Analyzer.

Table B_3 and Table B-4 explain the files installed and logicals defined on each node running the Data Provider.

Logical names are added to the logical name table when the AMDS$LOGICALS.COM procedure is invoked by AMDS$STARTUP.COM.

Note Logical names can be a search list of other logicals. The logical names in Table B_2 and Table B-4 must be defined in the job, group, or system table. If you change the name, define the new logical in the job, group, or system table.

## B.1 Files and Logical Names for the Data Analyzer Node

Table B_1 and Table B-2 contain the names of all files created on a Data Analyzer node when DECamds is installed.

Table B-1 Files on the Data Analyzer Node
Directory-Logical:File-Name | Function
--- | ---
AMDS$HELP:AMDS$HELP.HLB | Help library
AMDS$CONFIG:AMDS$*.DAT | Customization files
AMDS$SYSTEM:AMDS073.RELEASE_NOTES | Product Release Notes
AMDS$CONFIG:AMDS$COMM.EXE | Communication image
AMDS$SYSTEM:AMDS$CONSOLE.EXE | Data Analyzer image
AMDS$CONFIG:AMDS$CONSOLE.UID | User interface description file
AMDS$CONFIG:AMDS$CONSOLE_ACCESS.DAT 1 | Data Analyzer security file
SYS$MANAGER:AMDS$LOGICALS.COM 1 | Logical name definition file
AMDS$SYSTEM:AMDS$VMS*-*.LIB | DECamds version-specific libraries
AMDS$TEST:AMDS$IVP.COM | Installation verification procedure
SYS$STARTUP:AMDS$STARTUP.COM | DECamds startup file

1Can be provided as a TEMPLATE file, depending on whether the file was found during installation.

Table B-2 Logical Names Defined for the Data Analyzer
Logical Name | Definition | Default
--- | --- | ---
AMDS$COMM_BUFFER_SIZE | This value is the size (in bytes) of the communications buffer between the AMDS$CONSOLE process and the AMDS$COMM process. | 300000 bytes
AMDS$COMM_READS | This value is the number of read aheads posted by the DECamds communications process (AMDS$COMM) to handle the delivery of remote response packets from the Data Provider to the Data Analyzer node. | 50 read aheads
AMDS$COMM_PKT_RETRY | Specifies the number of retries before quitting and issuing a "delivery path lost message." | 4
AMDS$COMM_PKT_TMOUT | Specifies the timeout period (in seconds) for packet retry for the Data Analyzer. | 10
AMDS$CONFIG | The device and directory location for the following DECamds input files: AMDS$APPLIC_CUSTOMIZE.DAT AMDS$COMM.EXE AMDS$CONSOLE.UID AMDS$CONSOLE_ACCESS.DAT AMDS$VMS*-*.LIB All customization files AMDS$*_DEFS.DAT | AMDS$SYSTEM
AMDS$DPI | This value specifies the DPI value of your display device. | 75 or 100
AMDS$LOG | The device and directory location for the following DECamds output files: AMDS$EVENT_LOG.LOG AMDS$LOCK_LOG.LOG | AMDS$SYSTEM

## B.2 Files and Logical Names for Data Provider Nodes

Table B_3 and Table B-4 contain the names of all files created on a node when a Data Provider is installed.

Table B-3 Files on Nodes Running the Data Provider
Directory-Logical:File-Name | Function
--- | ---
SYS$MANAGER:AMDS$DRIVER_ACCESS.DAT 1 | Data Provider security file
SYS$MANAGER:AMDS$LOGICALS.COM 1 | Logical name definition file
AMDS$SYSTEM:RMCP.EXE | Management interface to the Data Provider
SYS$HELP:AMDS072-1B.RELEASE_NOTES | Product Release Notes
SYS$HELP:AMDS$HELP.HLB | Help library
SYS$LOADABLE_IMAGES:RMDRIVER.EXE, SYS$LOADABLE_IMAGES:RMDRIVER.STB 2 | Data Provider (VAX systems)
SYS$LOADABLE_IMAGES:SYS$RMDRIVER.EXE, SYS$LOADABLE_IMAGES:SYS$RMDRIVER.STB 3 | Data Provider (Alpha systems)
SYS$STARTUP:AMDS$STARTUP.COM | DECamds startup file
SYS$TEST:AMDS$IVP.COM | Installation verification procedure

1Can be provided as a .TEMPLATE file, depending on whether the file was found during installation.
2VAX specific
3Alpha specific

Table B-4 Logical Names Defined on Nodes Running the Data Provider
Logical Name | Definition | Default
--- | --- | ---
AMDS$CONFIG | The device and directory location for the DECamds input file AMDS$DRIVER_ACCESS.DAT. | AMDS$SYSTEM
AMDS$DEVICE | This logical is translated as the first LAN device to which the Data Provider or Data Analyzer node attempts to connect. The attempts are made in this order: AMDS$DEVICE, FXA0, XEA0, XQA0, EFA0, ETA0, ESA0, EXA0, EZA0, FCA0, ECA0. | Undefined
| If your LAN line is not in this list, use AMDS$DEVICE. |
| If the Data Analyzer node and Data Provider run on the same node, *RMA0 is used. |
AMDS$GROUP_NAME | The group to which the node is assigned. Choose an alphanumeric string of up to 15 characters. The group name is defined on the node running the Data Provider and is used by the Data Analyzer node to display nodes in the System Overview window. | DECAMDS
AMDS$NUM_DL_READS | The number of data link reads to be posted by the Data Provider as read-ahead buffers. Generally between 4 and 8 should be sufficient to allow the Data Provider to process without having to wait for a data link buffer to be cleared. | 5 data link reads 1
AMDS$RM_DEFAULT_INTERVAL | The number of seconds between multicast hello messages from the Data Provider to the Data Analyzer node when the Data Provider is inactive or is only minimally active. The minimum value is 15. The maximum value is 300. | 30
AMDS$RM_OPCOM_READ | This logical defined as TRUE allows OPCOM messages for read failures from the Data Provider. Defined as FALSE, the message facility is disabled. | TRUE
AMDS$RM_OPCOM_WRITE | This logical defined as TRUE allows OPCOM messages for write (fix) successes and failures from the Data Provider. Defined as FALSE, the message facility is disabled. | TRUE
AMDS$RM_SECONDARY_INTERVAL | The number of seconds between multicast hello messages from the Data Provider to the Data Analyzer node when the Data Provider is active. The minimum value is 15. The maximum value is 1800. | 90

1Each read request requires 1500 bytes of BYTCNT quota used for the starting process.

## B.3 Log Files

The DECamds Data Analyzer records two log files:

- An events log file named AMDS$EVENT_LOG.LOG. This ASCII text file records all event messages displayed in the Event Log window.
- A lock contention log file named AMDS$LOCK_LOG.LOG. This ASCII text file records all lock contention information displayed in the Lock Contention window.

Both log files are created when the DECamds application is started. Either file can be edited while the application is running.

Event Log File and Lock Log File Enhancements

Prior to Version 7.2, the Event Log File and Lock Log File were created with a default creation size of 1 block and a default extension size of 1 block. This sometimes resulted in a very fragmented log file (and disk) when DECamds was allowed to run for a long period of time.

Two new logicals in the AMDS$LOGICALS.COM file allow users to define additional sizes in log files. The following table describes these logicals and their default values.

Logical | Description | Default Value
--- | --- | ---
AMDS$EVTLOG_ALLOC_SIZE | Sets the initial size of the log files. | 100 blocks
AMDS$EVTLOG_EXTNT_SIZE | Sets the extension size of a file when it needs to grow. | 0 blocks

The default value for AMDS$EVTLOG_EXTNT_SIZE causes DECamds to use the system defaults for extent size.

## B.4 Event Log File

The event log file keeps a record of the events detected by DECamds. You can review it without a DECwindows terminal. Every 30 minutes, DECamds writes a message to the file, noting the date and time.

Example B-1 is an example of AMDS$LOG:AMDS$EVENT_LOG.LOG.

Example B-1 Sample Event Log File

    Time      Sev   Event
    Opening DECamds Event Log on date/time: 11:16:07.00
    11:16:07.98 0  CFGDON, PROD12 configuration done
    11:16:08.44 0  CFGDON, PROD09 configuration done
    11:16:09.65 0  CFGDON, AXPND1 configuration done
    11:16:11.47 0  CFGDON, PROD01 configuration done
    11:16:11.89 0  CFGDON, VAXND1 configuration done
    11:16:12.14 0  CFGDON, PROD15 configuration done
    11:16:14.02 0  CFGDON, PROD14 configuration done
    11:16:14.57 60 HIDIOR, PROD12 direct I/O rate is high
    11:16:14.57 70 HITTLP, PROD12 total page fault rate is high
    11:16:14.57 80 LOMEMY, PROD12 free memory is low
    11:16:14.58 70 HITTLP, PROD09 total page fault rate is high
    11:16:14.58 80 LOMEMY, PROD09 free memory is low
    11:16:15.32 70 HITTLP, AXPND1 total page fault rate is high
    11:16:25.33 60 HIBIOR, PROD09 buffered I/O rate is high
    11:16:35.46 60 HIBIOR, AXPND1 buffered I/O rate is high
    11:16:40.62 95 LOSWSP, AXPND1 DISK$ALPHAVMS015:[SYS0.SYSEXE]SWAPFILE.SYS swap file space is low
    11:16:49.84 70 HITTLP, PROD09 total page fault rate is high
    11:16:55.14 60 HIBIOR, PROD12 buffered I/O rate is high
    11:17:14.58 0  CFGDON, PROD05 configuration done
    11:17:14.94 70 HITTLP, PROD09 total page fault rate is high
    11:17:16.93 0  CFGDON, PROD04 configuration done
    11:17:18.10 0  CFGDON, PROD17 configuration done
    11:17:18.15 0  CFGDON, PROD10 configuration done
    11:17:19.50 60 HIBIOR, PROD10 buffered I/O rate is high
    11:17:19.50 60 HIDIOR, PROD10 direct I/O rate is high
    11:17:19.50 70 HITTLP, PROD10 total page fault rate is high
    11:17:19.50 80 LOMEMY, PROD10 free memory is low
    11:17:20.33 60 HIBIOR, PROD05 buffered I/O rate is high
    11:17:21.49 0  CFGDON, PROD20 configuration done
    11:17:21.52 0  CFGDON, PROD13 configuration done
    11:17:24.96 0  CFGDON, PROD06 configuration done
    11:17:35.35 0  CFGDON, PROD07 configuration done
    11:17:39.84 60 HINTER, PROD07 interrupt mode time is high
    11:17:40.21 70 HITTLP, PROD09 total page fault rate is high
    11:18:04.69 60 HIBIOR, PROD10 buffered I/O rate is high
    11:18:05.36 60 HIDIOR, PROD07 direct I/O rate is high
    11:18:10.49 60 HIBIOR, PROD09 buffered I/O rate is high
    11:18:10.49 60 HIDIOR, PROD09 direct I/O rate is high
    11:18:14.70 60 HIBIOR, PROD12 buffered I/O rate is high
    11:18:15.68 60 HIBIOR, AXPND1 buffered I/O rate is high
    11:18:26.05 60 HIBIOR, PROD05 buffered I/O rate is high
    11:18:40.57 75 HIHRDP, PROD10 hard page fault rate is high
    11:18:45.80 60 HIDIOR, PROD09 direct I/O rate is high
    11:18:55.91 60 HINTER, PROD07 interrupt mode time is high
    11:19:09.67 60 HIBIOR, PROD09 buffered I/O rate is high
    11:19:09.67 60 HIDIOR, PROD09 direct I/O rate is high
    11:19:09.67 75 HIHRDP, PROD09 hard page fault rate is high
    11:19:15.48 60 HIBIOR, PROD05 buffered I/O rate is high

Previous | Next | Contents | Index

| privacy and legal statement |
5929PRO_009.HTML