A security triplet determines which nodes can access system data from an OpenVMS Data Collector node. The AMDS$DRIVER_ACCESS.DAT file on OpenVMS Data Collector nodes lists security triplets.

On OpenVMS Data Collector nodes, the AMDS$AM_SYSTEM logical translates to the location of the default security file, AMDS$DRIVER_ACCESS.DAT. This file is installed on all OpenVMS Data Collector nodes.

The exclamation point (!) is a comment delimiter; any characters to the right of the comment delimiter are ignored.

Example

*\FINGROUP\R   ! Let anyone with FINGROUP password monitor
               ! system, process, or device data
               !
2.1\DEVGROUP\W ! Let only DECnet node 2.1 with
               ! DEVGROUP password perform fixes (writes)

      Network address\password\access

Use a backslash character (\) to separate the three fields.

*\1decamds\r   ! Anyone with password "1decamds" can monitor
*\1decamds\w   ! Anyone with password "1decamds" can monitor or write
2.1\1decamds\r ! Only node 2.1 with password "1decamds" can monitor
2.1\1decamds\w ! Only node 2.1 with password "1decamds" can monitor and
               ! write
08-00-2b-03-23-cd\1decamds\w ! Allows a particular hardware address to
                             ! write
08-00-2b-03-23-cd\1decamds\r ! Allows a particular hardware address to
                             ! read node

*\1DECAMDS\R
*\KOINECLS\R
*\KOINEFIX\W
*\AVAILMAN\C

In this example, Data Analyzer nodes with the passwords 1DECAMDS and KOINECLS are able to access monitored data from the Data Collector, but only the Data Analyzer node with the KOINEFIX password is able to write or change information, including performing fixes, on the Data Collector node. The Data Analyzer node with the AVAILMAN password is able to perform switched LAN fixes and other control functions.

*\1DECAMDS\R
08-00-2B-03-23-CD\2NODEFIX\C

The data that the Data Analyzer collects is grouped into data collections. These collections are composed of related data—for example, CPU data, memory data, and so on. Usually, the data items on the tabs (like the ones displayed in Figure 1.7) consist of one data collection.

An event is a problem or potential problem associated with resource availability. Events are associated with various data collections. For example, the CPU Process data collection shown in Figure 1.8 is associated with the PRCCUR, PRCMWT, and PRCPWT events. (Appendix C describes events, and Appendix D describes the events that each type of data collection can signal.) For these events to be signalled, you must enable the CPU Process data collection, as described in Section 1.4.1.2.

Users can also customize criteria for events, which is described in Section 1.4.2.

You can use the Data Analyzer to collect data either as a background activity or as a foreground activity.

Thresholds and occurrences are criteria that the Data Analyzer uses for posting events.

A threshold is a value against which data in a data collection is compared. An occurrence is a value that represents the number of consecutive data collections that meet or exceed the threshold.

Both thresholds and occurrences are customizable values that you can adjust according to the needs of your system. For details about how to change the values for thresholds and occurrences, see Chapter 7.

Relationship Between Thresholds and Occurrences

For a particular event, when the data collected meet or exceed the threshold, the data collection enters a threshold-exceeded state. When the number of consecutive data collections to enter this state meets or exceeds the value in the Occurrence box (see Figure 1.9), the Data Analyzer displays (posts) the event in the Event pane.

A closer look at Figure 1.9 shows the relationship between thresholds and occurrences. For the DSKERR, high disk device error count event, a threshold of 15 errors has been set. A value of 2 in the Occurrence box indicates that the number of errors during 2 consecutive data collections must meet or exceed the threshold of 15 for the DSKERR event to be posted.

Another example of the relationship between thresholds and occurrences is for the HINTER, High interrupt mode time event. If the threshold setting is 30%, and the occurrence setting is 3, then the event is signaled if three consecutive data collections have the interrupt mode time greater or equal to 30%. Using the occurrence setting of 3 helps to show more long-term trends in the interrupt time, and not occasional spikes where only 1 or 2 data collections have exceeded the threshold.

Creating the key store from the server system is the simplest method. You create the key store and export the public key using the Data Analyzer on the server system, copy the public key to the analyzer system, and import the public key with the Data Analyzer on the analyzer system. For a description of this method, see Section 2.4.3.

Using this method assumes that you can use the Data Analyzer's GUI interface on the server system. You can start the Data Analyzer on the server system and display the GUI on the following:

If this is not possible, use the alternate method to create and maintain key stores described in Section 2.4.2.2.

With this method, you create the key store and export the public key using the Data Analyzer on the analyzer system, and copy the key store to the server system. This method is described in Section 2.4.4.

To run the Data Analyzer on other systems, see Section 2.4.3.2

To run the Data Analyzer on other systems, and to connect to the Data Server on this system, you must export the public key for the Data Server as a trusted certificate. To do this, click the key pair name in the Key Store Management dialog box. This action enables the Export... button. Click Export... to export the public key in a trusted certificate. The Availability Manager displays the Export Certificate dialog box as shown in Figure 2.5.

Store the trusted certificate in the folder and file name of your choice. Any file name with a CER extension works, although naming the file the same as the server alias can make it easier to identify. Click Export to complete this process.

To save the key store on the server system, click OK in the Key Store Management dialog box. Then see Section 2.4.5 to import the trusted certificate into the Data Analyzer trust store.

Start the Data Analyzer on the analyzer system. When the Data Analyzer starts, it displays the Network Connection dialog box as shown in Figure 2.6.

From the Key Stores menu, click New Trust or Key Store.... The Availability Manager displays the Key Store Management dialog box, shown in Figure 2.7.

In the Key Store Management dialog box, click New Key... to display the Generate New Key Pair dialog box as shown in Figure 2.8. To create a new key pair, fill in the fields in this dialog box. For a description of these fields, see Section 2.4.3.1.

When you finish entering information in the Generate New Key Pair dialog box, click Add (it might take a few seconds to create the key). If you checked the Default Trust Store checkbox, the default Trust Store for this key pair is created for the Data Analyzer running on the this analyzer system.

The Key Store Management dialog box (Figure 2.9) now displays the new key pair, reflecting the information you entered.

This step finishes the setup needed for this analyzer system. If this is the only Data Analyzer that needs to connect to this Data Server, go to Section 2.4.4.4.

For other Data Analyzers that need to connect to the Data Server, export the public key as described in this section.

In the Key Store Management dialog box, select the Data Server key pair by clicking the key entry. This enables the Export... button in the dialog box. Click Export... to extract the Data Server's public key and store it in a file as a trusted certificate.

The Export Certificate dialog box is displayed as shown in Figure 2.10.

Store the trusted certificate in the folder and file name of your choice. Any file name with the CER extension works, although accepting the default can make the file easier to identify. Click on the Export button to complete this process.

Now that you have created the key pair for the Data Server, you must save the pair in a key store. In the Key Store Management dialog box, select the Key Store menu, and then select Save. This displays the Save Key Store dialog box as shown in Figure 2.11.

Save the key store in the folder and file name of your choice. Any file name with a JKS extension works, although naming the file the same as the server alias can make the file easier to identify. Enter this file name in the File Name field, and click Save to save the key store. In the Key Store Management dialog box, click Cancel to dismiss the dialog box.

The key store is now ready for the server system. Copy the file to the server system. If you use FTP to transfer the file, be sure to use the binary transfer mode.

Once the file is copied, move it to the location and file name that the Data Server looks for when it starts. On OpenVMS, the location is in the AMDS$AM_MANAGER: directory. On Windows, the location is the installation directory. Make sure that the file is named AM$KeyStore.jks for Windows systems. On OpenVMS, if the AMDS$AM_MANAGER: directory is on an ODS-2 disk volume, make sure that the file is named AM$KEYSTORE.JKS.

Once you have created the key store and copied it to the server system, it is recommended that you delete the key and trust store on the analyzer system. This sets up the analyzer system to create a key store for another Data Server, or to create the trust store by importing the trusted certificates from each Data Server into the Data Analyzer.

This concludes the Data Server setup on the server system. If you want to create a key store for another Data Server, go to Section 2.4.4. Otherwise, go to Section 2.4.5, which describes how to import the Data Server's public key into the trust store of other Data Analyzers.

The next section describes how to obtain the public key from an existing Data Server. This step allows the Data Analyzer to connect to the Data Server.

This section describes how to obtain a Data Server's public key from the analyzer system.

2.4.4.6.2. Export the Key Store Public Key to a Trusted Certificate

This step extracts the Data Server public key from the key store by exporting it to a trusted certificate.

Start the Data Analyzer on the analyzer system. When the Availability Manager starts, it displays the Network Connection dialog box as shown in Figure 2.12.

From the Key Stores menu, select Open Trust or Key Store... to open the Open Key or Trust Store dialog box as shown in Figure 2.13.

In this dialog box, locate the key store file by selecting the name of the key store file, and clicking Open. The opened key store is displayed in the Key Store Management dialog box as shown in Figure 2.14.

Select the key pair entry in the dialog box. This enables the Export... button. Click Export... to export the public key of the key pair into a trusted certificate. The Availability Manager displays the Export Certificate dialog box as shown in Figure 2.15.

Store the trusted certificate in the folder and file name of your choice. Any file with the CER extension works, although accepting the default can make the file easier to identify. Click Export to complete this process. You now have the trusted certificate.

Important

Remember the location of this certificate. This certificate is used in Section 2.4.5.

First enter the Data Server's public key into the trust store of the Data Analyzer. This transfer involves exporting the key into a trusted certificate from the key store, and importing the key into the Data Analyzer's trust store.

The following sections describe how to export the public key into a trusted certificate. If you need to export the public key, determine which of the following applies to you.

Make sure you have the Data Server's public key in a trusted certificate for the next step.

Copy the trusted certificate from the server system to the analyzer system. Note that the trusted certificate contains binary data, so you must use binary mode if FTP is the file transport. The certificate is now ready for importing to the Data Analyzer’s trust store.

Start the Data Analyzer on the analyzer system. From the Analyzer menu, select Trust Store to open the default trust store for this system. The Availability Manager displays the Trust Store Management dialog box as shown in Figure 2.16.

Click Import... to import the trusted certificate. The Availability Manager displays the Import Certificate dialog box as shown in Figure 2.17.

Select the name of the trusted certificate, and click Import. The Availability Manager displays the Assign Alias for Certificate dialog box as shown in Figure 2.18.

This dialog box displays the trusted certificate. Enter the alias name for the certificate in the Assign Alias field. Although you can put any text in this field, it is best to choose the same alias name that the Data Server uses. Then click OK to continue. The Availability Manager displays the Trust Store Management dialog box with the imported key as shown in Figure 2.19.

In the Trust Store Management dialog box, click OK to save the trusted certificate in the Data Analyzer trust store.

This sets up the Data Analyzer to connect to a Data Server. The Data Analyzer supports connections to multiple Data Servers. To connect to multiple Data Servers, export the public key for each Data Server and import it into the Data Analyzer.

This completes the Data Analyzer key configuration. You are now ready to run the Data Analyzer and connect to the Data Server.

Note the following:

The Availability Manager allows you to open multiple key and trust stores using the menus on the Network Connection dialog box. The Key Store and Trust Store Management dialog boxes allow you to drag and drop items interchangeably between dialog boxes (and to the file system or desktop on Windows). This operation can make import and export easier if you open the key and trust stores locally or if you use network shares to open them.

The certificate that you create is a ‘‘self-signed’’ one. This means that the person who creates the certificate also signs off on its legitimacy. This type of certificate is also called a root certificate.

Groups are set up during the Data Collector kit installation and configuration on Data Collector nodes and are user-definable. Be sure to define groups by cluster membership. If a node is not a member of a cluster, then you can define a group by function, type of hardware, or geographical location.

Groups—and the nodes in each group with which the Data Analyzer is able to establish a connection—are displayed in the Group/Node pane of the System Overview window (see Figure 2.25).

To display only groups in the Group/Node pane, click the handle in front of a group name to a horizontal position, and the nodes in that group are removed, as shown for both groups in Figure 2.26. (Clicking the handle into a vertical position displays nodes again.)

On each group name row, following the name of the group, the number in parentheses is the number of nodes in that group with which the Data Analyzer has established a connection.

On a group name row under the OS Version heading are color-coded numbers indicating the number of nodes in that group that are one of five color-coded states. These states are explained in Table 2.2.

Additional summary information about the entire group is on the group line. CPU, MEM, BIO, and DIO numbers are averages. The rest of the number are totals for all of the nodes in the group.

Notice the small triangle in the BIO heading in Figure 2.26. The direction of the triangle indicates that the nodes are sorted in descending order of BIO rates. Click on the triangle to reserve the sort order, or click on another column header to select a new item on which to sort data.

In the Group/Node pane, only nodes within a group are sorted. The groups remain in alphabetical order. You can sort groups in the Group Overview window by changing the sort order of one of the data column headings (see Figure 2.26).

Even when nodes are not displayed on the System Overview window or the Group/Node pane, you can display important node information by placing the cursor over a group name or icon. By holding the cursor over the DECAMDS group name, for example, the tooltip similar to the one shown in Figure 2.27 is displayed, containing summary node information.

The first window to help you view large sites is the Group Overview window. To view all the group name row data easily, click on the View menu at the top of the page and select Group Overview. The Group Overview window that is displayed (Figure 2.28) is similar to the Group Overview pane in Figure 2.26.

This display is designed to provide an overview of all the groups being monitored. If you want more information about a group, place the cursor over the group name or icon. A tooltip is displayed with additional information about nodes in the group similar to the one displayed in Figure 2.27.

You can also double-click a group name to display a Single-Group window, as explained in Section 2.8.2.3.

The second window to help you view large sites is the Single-Group window. This display shows the nodes in one group (see Figure 2.29).

To obtain this display, you can also right-click the group name in the Group/Node pane and select the Display option. A separate window appears with only the nodes in the group you have selected (see Figure 2.29). This window is useful in simultaneously displaying groups that are not adjacent in the list in the Group/Node pane.

Within each group of nodes displayed, the Data Analyzer displays all the nodes with which it can communicate. If some nodes in the group are not displayed, it is because the Data Analyzer has not received a multicast “Hello” message from the Data Collector on that node.

More information about node data is in Chapter 3.

Somewhat different information is displayed for a group of Windows nodes. For more information, see Section 3.1.2.

To display more information about an individual node, double-click a node name or in the Single-Group window in the Group/Node pane. You can also right-click a node name and select the Display... option. The Data Analyzer displays the Node Summary page shown in Figure 2.30. (The data on this page is explained in more detail in Chapter 3.)

At the top of the Node Summary page are tabs that correspond to types of node data displayed in the Group/Node pane. If you double-click a field under a column heading in the Group/Node pane, the Data Analyzer displays a page that provides more information about that field. For example, if you click a value under CPU, the Data Analyzer displays a page similar to the one shown in Figure 3.6.

By default, the only data collected for a node is the data displayed in the Node pane (Figure 2.29) and in the Group/Node pane of the System Overview window (see Figure 2.25). This data is called a node summary data collection. The events in the Event pane of the System Overview window (see Figure 2.25) are produced when node summary data is processed. See Appendix D for a list of events associated with node summary data.

If you want to signal additional events that are listed in Appendix D, you must collect the data associated with those events. To collect this data by default, you must enable background data collection for the data. Background and foreground data collections are explained in more detail in Section 1.4.1.2.

For OpenVMS nodes, if you want background data collection (and the associated event detection), you must turn on data collection for each type of data you want to collect. On Windows nodes, background data collection is always enabled and cannot be turned off.

The Data Analyzer then displays the Data Collection Customization page (Figure 2.31).

To turn on a type of data collection, select the checkbox for that type of data collection in the Collect column. For example, to collect CPU process data, check the checkbox for CPU process in the Collect column.

When you click a data collection name, the Explanation section at the bottom of the page tells where the data for a particular data collection is displayed. Table 7.3 summarizes this information.

You cannot turn off the collection of single disk and single process data. These types of data are collected by default when you open a Single Disk Summary page or a Process Information page, respectively.

On the Data Collection Customization page, you can change the intervals at which data is collected. Collection intervals are explained in Chapter 7.

Depending on the field, you can sort data alphabetically or numerically. An alphabetical sort is performed using ASCII character values; for example, dollar signs ($) precede letters in the sort order.

Figure 3.5 provides an example of a Windows CPU Modes page. The sample page contains values for the three CPU modes—user, privileged, and null.

The top pane of the Windows CPU Modes page is a summary of Windows CPU usage, listed by type of mode.

On the graph, values that exceed thresholds are displayed in red. To the right of the graph are current and extreme amounts for each mode.

Figure 3.6 shows sample OpenVMS CPU Mode Summary and CPU Process States, which are the left and right top panes of the CPU Modes page.

CPU Mode Summary

In the CPU Mode Summary section of the pane, percentages are averaged across all the CPUs and are displayed as a single value on symmetric multiprocessing (SMP) nodes.

To the left of the graph is a list of CPU modes. The bars in the graph represent the percentage of CPU cycles used for each mode. To the right of the graph are current and extreme percentages of time spent in each mode.

CPU Process States

The right side of Figure 3.6 shows a sample CPU Process States display. Note that the value for MWAIT, in the left column, is the sum of all values for the states in the two right columns.

This display shows the number of processes in each process state. This number is tallied from the data in CPU Process view of the CPU page (Figure 3.6). For systems with many processes, the data in the CPU Process view is collected in segments over a short period of time because the amount of data a network packet can contain is limited. Because of this, the number of processes in the Process States pane might differ slightly from what is reported by the MONITOR STATES command.

Appendix B contains explanations of the CPU process states.

The lower pane of the CPU Modes page contains CPU mode details, as shown in Figure 3.7.

The status bar in the OpenVMS CPU Mode Details pane (see Figure 3.7) shows the potential number of physical CPUs on the node, the number that are listed, and the number that are filtered out. The status bar is updated with each data collection. The data collection rate is determined by the customization of CPU mode data collection intervals. See Section 7.5 for instructions on how to change data collection intervals.

To display the OpenVMS CPU Process Summary pane at the bottom of the CPU page, select CPU Process Summary from the View menu (Figure 3.6). Figure 3.8 shows a sample OpenVMS CPU Process Summary pane.

Displaying Single Process Information

When you double-click a PID on the lower part of an OpenVMS CPU Process Summary (Figure 3.8), Memory Summary (Figure 3.10), or I/O Summary (Figure 3.12) page, the Data Analyzer displays the first of several OpenVMS Single Process pages.

On these pages, you can click tabs to display specific data about one process. Alternatively, you can display all of the information on the pages on a single vertical or horizontal grid page.

This data includes a combination of data elements from the CPU Process, Memory, and I/O pages, as well as data for specific quota utilization, current image, and queue wait time. These pages are described in more detail in Section 3.3.

The status bar in the OpenVMS CPU Process Summary pane (Figure 3.8) shows the total number of processes on the node, the number that are listed, and the number that are filtered out. The status bar is updated with each data collection. The data collection rate is determined by the customization of CPU process data collection intervals. See Section 7.5 for instructions on how to change data collection intervals.

The Data Analyzer displays the Windows Memory page (Figure 3.9).

When you double-click a value under the MEM heading in an OpenVMS Node pane, or if you click the Memory tab, the Data Analyzer displays the OpenVMS Memory Summary page (Figure 3.10).

You can click Memory Summary view to select the Memory Summary page, shown in Figure 3.10.

The graph in the top pane of Figure 3.10 shows memory distribution (Free, Used, and Modified) as absolute values, in megabytes of memory. Current and extreme values are also listed for each type of memory distribution. (Free memory uses the lowest seen value as its extreme.) Bad Pages show the number of pages that the operating system has marked as bad.

The thresholds that you see in the graph are the ones set for the LOMEMY event. (The LOMEMY thresholds are also in the display of values for the MEM field in the OpenVMS Group/Node pane shown in Figure 2.25.)

When you double-click a PID on the lower part of the Memory Summary page (Figure 3.10), the Data Analyzer displays an OpenVMS Single Process (Figure 3.23), where you can click tabs to display pages containing specific data about one process. This data includes a combination of data from the CPU Process, Memory, and I/O pages, as well as data for specific quota utilization, current image, and queue wait time. These pages are described in Section 3.3.

The status bar in the Memory Summary page (Figure 3.10) shows the total number of processes on the node, the number that are listed, and the number that are filtered out. The status bar is updated with each data collection. The data collection rate is determined by the customization of memory data collection intervals. See Section 7.5 for instructions on how to change data collection intervals.

The Data Analyzer displays the OpenVMS Memory Details page (Figure 3.11).

To the right of the box is a list of system memory data that is displayed in the bar graphs at the bottom of the page. You can toggle these data items on or off (that is, to display them as bar graphs). You can also click a small box to choose between Linear and Logarithmic bar graph displays.

Below the list of single RAD items is a box where you can toggle between Percentage and Raw Data to display Current and Extreme values to the right of the bar graphs.

The OpenVMS I/O Summary page displays the rate, per second, at which I/O transfers take place, including paging write I/O (WIO), direct I/O (DIO), and buffered I/O (BIO). In the top pane, the summary is for all CPUs; in the lower pane, the summary is for one process.

When you double-click a data item under the DIO or BIO heading on the Node pane, or if you click the I/O tab, by default, the Data Analyzer displays the OpenVMS I/O Summary (Figure 3.12).

Current and peak values are listed for each type of I/O. Values that exceed thresholds set by the events indicated in the table are displayed in red on the screen. Appendix C describes OpenVMS and Windows events.

When you double-click a PID on the lower part of the I/O Summary page, the Data Analyzer displays an OpenVMS Single Process, where you can click tabs to display specific data about one process. See Section 3.3 for more details.

The status bar in the OpenVMS I/O Summary page (Figure 3.12) shows the total number of processes on the node, the number that are listed, and the number that are filtered out. The status bar is updated with each data collection. The data collection rate is determined by the customization of I/O data collection intervals. See Section 7.5 for instructions on how to change data collection intervals.

Click I/O Page/Swap Files on the I/O page View menu to select this option. The Data Analyzer displays an OpenVMS I/O Page/Swap Files page. The top pane displays the same information as that in the OpenVMS I/O Summary page in Figure 3.12. The lower pane contains the I/O Page/Swap Files pane shown in Figure 3.13.

The status bar in the OpenVMS I/O Page/Swap Files pane (Figure 3.13) shows the total number of processes on the node, the number that are listed, and the number that are filtered out. The status bar is updated with each data collection. The data collection rate is determined by the customization of page/swap data collection intervals. See Section 7.5 for instructions on how to change data collection intervals.

To display the default disk page, the OpenVMS Disk Status Summary page (Figure 3.14), click the Disk tab on the OpenVMS Node Summary page (Figure 3.4). The Disk Status Summary page displays disk device data, including path, volume name, status, and mount, transaction, error, and resource wait counts.

The status bar in the OpenVMS Disk Status Summary (Figure 3.14) shows the total number of disks on the node, the number that are listed, and the number that are filtered out. The status bar is updated with each data collection. The data collection rate is determined by the customization of disk status data collection intervals. See Section 7.5 for instructions on how to change data collection intervals.

To collect single disk data and display the data on the Single Disk Summary, double-click a device name on the Disk Status Summary. Figure 3.15 is an example of a Single Disk Summary page. The display interval of the data collected is 5 seconds.

Note that you can sort the order in which data is displayed in the Single Disk Summary page by clicking a column header. To reverse the sort order of a column of data, click the column header again.

By using the View option on the Disk Status Summary page (Figure 3.14), you can select the Volume Summary option to display the OpenVMS Disk Volume Summary (Figure 3.16). This page displays disk volume data, including path, volume name, disk block utilization, queue length, and operation rate.

 AFFS55 Volume size of device $8$DKA200 (OPAL-X9U6) has changed
   ^                              ^          ^
  Node                          Device     Volume
  name                           name       name

The status bar in the OpenVMS Disk Volume Summary (Figure 3.16) shows the total number of volumes on the node, the number that are listed, and the number that are filtered out. The status bar is updated with each data collection. The data collection rate is determined by the customization of disk volume data collection intervals. See Section 7.5 for instructions on how to change data collection intervals.

Windows Logical Disk Summary

A logical disk is the user-definable set of partitions under a drive letter. The Windows Logical Disk Summary displays logical disk device data, including path, label, percentage used, free space, and queue statistics.

The Data Analyzer displays the Windows Logical Disk Summary page (Figure 3.17).

Windows Physical Disk Summary

A physical disk is hardware used on your computer system. The Windows Physical Disk Summary displays disk volume data, including path, label, queue statistics, transfers, and bytes per second.

The Data Analyzer displays the Windows Physical Disk Summary page (Figure 3.18).

Figure 3.19 shows a sample Lock Contention page containing resource names in decoded format, which is the default.

You can display a tooltip similar to the one shown in Figure 3.19 by holding the cursor on a resource line.

Figure 3.19 displays the resource names in decoded format. (The Data Analyzer decodes common resource names.)

Figure 3.20 shows the Lock Contention page with resource name data displayed in raw format. It also shows the tooltip that is displayed when you hold the cursor over a line of data.

In Figure 3.20, notice that a period is substituted for each unprintable character in the Resource Name and Parent Resource Name fields.

When you click the handle that precedes any line of resource data, the Data Analyzer displays the lock block data that is shown in Figure 3.21 and Figure 3.22.

To interpret the information displayed on the OpenVMS Lock Contention page, you need to understand OpenVMS lock management services. For more information, see the VSI OpenVMS System Services Reference Manual.

Example 3.1 contains an excerpt of a lock block log file. See Appendix A for the lock block log file name format and location.

**************************************************
Time:  11-Feb-2020 14:54:13.656

16)Reason for logging:    Number of locks has changed

2) Master Lock Node:      ALTOS

1) Resource Name:         I.....
17)    GGMODE/CGMODE:     EX/EX
6)     Status:            VALID
7)     RSB Address:       FFFFFFFE.889F1580
18)    Resource Name Dump (includes initial count byte):
          0000:   000200 00004906  .I.....

8)     Value Block Dump:
          0000: 00000000 00000000  ........
          0008: 00000000 00000000  ........

19) Rdb Remote monitor resource
          #:                 2

3) Parent Resource Name:  Ý...D....VDEROOT     . 7....
7)     RSB Address:       FFFFFFFE.8847DB80
20)    Resource Name Dump (includes initial count byte):
          0000: 00004400 0000DD1C  .....D..
          0008: 4F4F5245 44560200  ..VDEROO
          0010: A0002020 20202054  T     ..
          0018:       00 00000237  7....

8)     Value Block Dump:
          0000: 00000000 00000000  ........
          0008: 00000000 00000000  ........

21)    Rdb global database name resource
          Disk volume name:  VDEROOT
          FID for file:      (14240,2,0)

22) Lock data is being collected

5)     Granted lock count:       1
5)     Conversion lock count:    0
5)     Waiting lock count:       4
5)     Stalled lock count:       0

  10)     9)              11)           12)      13) Master copy info:  15)
 Lock    Node  Process  Process         Lock    Gr/Cv Remote Remote   Flags
 State         PID      Name            ID       Mode Node   Lock ID
                                                       23)    24)
 Granted ALTOS 28E00441 RDMS_MONITOR70  04014B37 EX (Local copy)    NQUE SYNC SYS
 Waiting ALTOS 2880023F RDMS_MONITOR70  4C0065B5 PR TSAVO  32005001 SYNC SYS  NDLW
 Waiting ALTOS 00000000 (EPID=28A0023D) 4C0144C4 PR ETOSHA 74005E36 SYNC SYS  NDLW
 Waiting ALTOS 28C00448 RDMS_MONITOR70  1D0144A3 PR CHOBE  77005906 SYNC SYS  NDLW
 Waiting ALTOS 28E026C3 VDE$KEPT126A3   01014B2D PR (Local copy)         SYS  NDLW

**************************************************

The LAN Device Overview Data page (Figure 4.9) displays LAN device summary data.

The LAN Device Transmit Data page (Figure 4.10) displays LAN device transmit data.

The LAN Device Receive Data page (Figure 4.11) displays LAN device receive data.

The LAN Device Events Data page (Figure 4.12) displays LAN device events data.

The LAN Device Errors Data page (Figure 4.13) displays LAN device errors data.

The LAN Channel Overview Data page (Figure 4.14) displays general channel data, including the state, status, and total errors of the channel.

The LAN Channel Counters Data page (Figure 4.15) displays path counters data, including ECS transitions as well as messages and bytes sent.

The LAN Channel Errors Data page (Figure 4.16) displays LAN channel errors data.

The LAN Channel Remote System Data page (Figure 4.17) displays LAN path remote system data.

The LAN Channel ECS Criteria Data page (Figure 4.18) displays equivalent channel set criteria data.