Document revision date: 30 March 2001

Example B-2 is an example of a Lock Contention Log File.

Example B-2 Sample Lock Contention Log File

*********************************************** Time: 9-JUL-2000 14:23:46.68 Master Node: AXPND1 Resource Name: QMAN$JBC_ALIVE_01 Parent Resource Name: QMAN$MSR_$10$DKA300.....ñ..... RSB Address: 805B1400, GGMODE: EX, CGMODE: EX Hex Representation 514D414E 244A4243 (Bytes 0 - 7) 5F414C49 56455F30 (Bytes 8 - 15) 31000000 00000000 (Bytes 16 - 23) 00000000 000000C0 (Bytes 24 - 31) Status: VALID *********************************************** Time: 9-JUL-2000 14:28:42.44 Resource Name: QMAN$JBC_ALIVE_01 Parent Resource Name: QMAN$MSR_$10$DKA300.....ñ..... Blocking Lock Data Node: AXPND1, PID: 2020008C, Name: JOB_CONTROL LKID: 0200015E, GR Mode: EX Flags: NOQUEUE Local Copy Blocked Lock on WAITING queue Node: AXPND1, PID: 2020008D, Name: QUEUE_MANAGER LKID: 2000013B, RQ Mode: CR Flags: NODLCKW Local Copy ***********************************************

B.6 OPCOM Log

The following examples show some of the OPCOM messages that appear in the operator log file from the Data Provider:

%%%%%%%%%%% OPCOM 2-JAN-2000 08:16:21.92 %%%%%%%%%%% Message from user RMDRIVER RMA0: - No privilege to access from node 2.2

This message means that the node does not have the privilege to perform a read operation.

%%%%%%%%%%% OPCOM 2-JAN-2000 10:10:45.08 %%%%%%%%%%% Message from user RMDRIVER RMA0: - No privilege to write from node 2.2

This message means that the Data Provider does not have the privilege to perform a write operation.

%%%%%%%%%%% OPCOM 2-JAN-2000 12:35:05.28 %%%%%%%%%%% Message from user RMDRIVER RMA0: - Process 2390003c modified from node 2.2

This message means that the Data Provider has successfully performed a write operation on the node.

Following is an alphabetical listing of terms used in this manual and their definitions.

automatic data collection: Data collection that begins automatically when the Data Analyzer runs and recognizes a Data Provider. By default, this feature is enabled.

The default data windows for which automatic collection is enabled are:

Node Summary
Page/Swap File Summary
Lock Contention Summary
Cluster Transition Summary

Automatic Event Investigation: Enhances the speed with which you can pursue a specified event. When this option is enabled, DECamds automatically collects follow-up data on the event. When this option is disabled, you must initiate follow-up data collection when an event occurs.

To enable automatic event investigation, choose Enable Automatic Event Investigation from the Control menu of the System Overview or Event Log window. To disable it, choose the Disable Automatic Event Investigation menu item.

This feature does not apply to any lock contention events. To enable automatic lock contention detection, use the DECamds Application Customizations dialog box, as explained in Section 5.1.

collection interval: The frequency at which the Data Analyzer will send requests to a Data Provider to collect data.

See also Data Analyzer, Data Provider.

Data Analyzer: The portion of DECamds that collects and displays system data from Data Provider nodes. You can also perform fixes with the Data Analyzer.

See also Data Provider, fix.

Data Provider: The portion of DECamds that is installed to provide system data when requested by authorized Data Analyzers. A Data Provider node uses the OpenVMS LAN drivers to receive and send data across the network.

See also Data Analyzer.

data window: A Data Analyzer window that displays additional data. A number of different data windows are available as follows (see also Chapter 3):

CPU Modes Summary
CPU Summary
Disk Status Summary
Volume Summary
Single Disk Summary
Lock Contention Summary
Memory Summary
Node Summary
Page/Swap File Summary
Process I/O Summary
Single Lock Summary
Single Process Summary
Cluster Transition/Overview Summary
System Communication Architecture Summary
NISCA Summary

event: A description of a potential resource availability problem, based on rules defined by the Data Analyzer and customized thresholds. Events trigger display changes in data windows such as color and item highlighting.

See also Data Analyzer, data window.

Event Log window: One of two primary Data Analyzer windows that displays events as they occur. For each event, you can display more detailed information to investigate the underlying problem by double-clicking on the event. You can also perform fixes for some events from this window.

See also System Overview window.

fix: A corrective action made to a Data Provider node but initiated from the Data Analyzer node.

group: A set of remote Data Provider nodes with similar attributes; for example, all the members of an OpenVMS Cluster can be in the same group. The group that a node belongs to is determined by the translation of the AMDS$GROUP_NAME logical on each Data Analyzer.

occurrence value: The number of consecutive data samples that must exceed the event threshold before an event is signaled.

page: A unit used by the operating system to section memory. On VAX systems, a page is 512 bytes. On Alpha systems, a page can be 8 kilobytes (8192 bytes), 16 KB, 32 KB, or 64 KB.

pagelet: A unit used by the OpenVMS Alpha operating system to break down the page into smaller addressable units. One pagelet is the same as a VAX page: 512 bytes.

security triplet: A three-part access code located in the AMDS$DRIVER_ACCESS.DAT and AMDS$CONSOLE_ACCESS.DAT files that enables communications to be established between the Data Analyzer and Data Provider.

System Overview window: One of two primary Data Analyzer windows that graphically displays groups and the nodes that belong to each group. The System Overview window provides summary data about CPU, Memory, Process I/O usage, Number of Processes in CPU Queues, Operating System Version, and Hardware Model for the nodes being monitored.

	privacy and legal statement
5929PRO_010.HTML