Document revision date: 19 July 1999

Recovering from Errors

Errors can occur during the installation if any of the following conditions exist:

• The operating system version is incorrect.
• A prerequisite software version is incorrect.
• Privileges necessary for successful IVP are insufficient.
• Quotas necessary for successful IVP are insufficient.
• System parameter values for successful IVP are insufficient.
• The OpenVMS Help library is currently in use.
• The node on which the DECamds Data Analyzer is to be displayed does not allow connections from your process and node.

For descriptions of the error messages generated by these conditions, see the OpenVMS documentation on system messages, recovery procedures, and OpenVMS software installation. If you are notified that any of these conditions exist, you should take the appropriate action as described in the message. For information on installation requirements, see Section A.3.

If the IVP fails, check the AMDS$SYSTEM:AMDS$CONS_LOG.LOG for any errors that might have occurred while the IVP was executing the console verification portion.

A.6 Postinstallation Tasks on Data Provider Nodes

Perform the following tasks after installing DECamds on Data Provider nodes:

1. If you have not read the release notes, please read them.
2. Modify user accounts.
   Users who maintain the security or group name files or load new versions of the driver need privileges associated with the driver startup procedure.
3. Add AMDS$STARTUP.COM to the node's startup and shutdown procedures to provide for automatic startup and shutdown of the Data Provider driver when a node is booted or shut down.
   Add the following command line to SYS$MANAGER:SYSTARTUP_VMS.COM:

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

   
   Also, edit SYSHUTDWN.COM to add the following line:

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

4. Modify default security files.
   To implement fixes, which require write access, the security files must be modified. The Data Provider security file contains a list of three-part codes representing Data Analyzer nodes that have read or write access to that node. Refer to Section 1.3 for complete instructions about designing security files.
5. Assign a node to a group.
   See Section 1.3.2.1.
6. Start DECamds (the Data Provider).
   Even though the IVP starts and stops the driver, you must start the Data Provider drivers by entering the following command on each node:

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

   Note Starting, stopping, or reloading DECamds (the AMDS$STARTUP.COM procedure) requires at least TMPMBX, NETMBX, SYSNAM, LOG_IO, and CMKRNL privileges. Use the OpenVMS Authorize utility (AUTHORIZE) to determine whether users have the required privileges and then make adjustments as needed.

A.6.1 Starting, Stopping, and Reloading DECamds

$ @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.

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.

If you encounter a problem while using DECamds, report the problem to Digital. 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 Digital support representative.
• If the problem has to do with the DECamds documentation, submit a Reader's Comments form. See the Preface for instructions.

Review the Software Product Description (SPD) and Warranty Addendum for an explanation of the warranty. If you encounter a problem during the warranty period, report the problem as indicated above or follow alternate instructions provided by Digital for reporting SPD nonconformance problems.

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.

The DECamds 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.

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 DECamds Data Analyzer

Directory-Logical:File-Name	Function
AMDS$HELP:AMDS$HELP.HLB	Help library
AMDS$SYSTEM:AMDS$*.DAT	Customization files
AMDS$SYSTEM:AMDS071.RELEASE_NOTES	Product Release Notes
AMDS$SYSTEM:AMDS$COMM.EXE	Communication image
AMDS$SYSTEM:AMDS$CONSOLE.EXE	Data Analyzer image
AMDS$SYSTEM:AMDS$CONSOLE.UID	User interface description file
AMDS$SYSTEM:AMDS$CONSOLE_ACCESS.DAT 1	Data Analyzer security file
AMDS$SYSTEM: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

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 the Data Provider Nodes

Table B-3 Files on Nodes Running the Data Provider

Directory-Logical:File-Name	Function
AMDS$SYSTEM:AMDS$DRIVER_ACCESS.DAT 1	Data Provider security file
AMDS$SYSTEM:AMDS$LOGICALS.COM 1	Logical name definition file
AMDS$SYSTEM:RMCP.EXE	Management interface to the Data Provider
SYS$HELP:AMDS071.RELEASE_NOTES	Product Release Notes
SYS$HELP:AMDS$HELP.HLB	Help library
SYS$LOADABLE_IMAGES:RMDRIVER.EXE, SYS$LOADABLE_IMAGES:RMDRIVER.STB 2	On VAX systems, Data Provider
SYS$LOADABLE_IMAGES:SYS$RMDRIVER.EXE, SYS$LOADABLE_IMAGES:SYS$RMDRIVER.STB 3	On Alpha systems, OpenVMS Alpha driver
SYS$STARTUP:AMDS$STARTUP.COM	DECamds startup file
SYS$TEST:AMDS$IVP.COM	Installation verification procedure

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

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.

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.98 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

	privacy and legal statement
5929PRO_009.HTML