Document revision date: 19 July 1999

On VAX systems, the MONITOR VBS command displays information about the processing of virtual balance slots (VBS).

Format

MONITOR VBS

Description

The MONITOR VBS command includes the following data items:

Data Item	Description
RBS Fault Rate	Rate at which processes fault from virtual balance slots into real balance slots (RBS)
CPU Utilization	Amount of CPU time used by the operating system to support the virtual balance slot feature (at a rate of 10-millisecond clock ticks per second)

To see which processes have the highest RBS fault rates, issue the MONITOR PROCESSES/TOPRBS command.

Example

MONITOR> MONITOR VBS
 
 



  

    

      

      
 
  
 
  
                           OpenVMS Monitor Utility 
                         VIRTUAL BALANCE SLOT STATISTICS 
                                 on node SAMPLE 
                              29-APR-1998 12:43:28 
 
                                       CUR        AVE        MIN        MAX 
     RBS Fault Rate                   4.62       3.80       0.33       7.61 
     CPU Utilization                  0.99       0.24       0.00       0.99 
 




      

This example shows the tabular style format for the VBS display.

The MONITOR VECTOR command displays the number of 10-millisecond clock ticks per second in which one or more vector consumers have been scheduled on each currently configured vector processor in the system.

Format

MONITOR VECTOR

Command Qualifiers

/qualifier[,...]

One or more qualifiers as described in the Command Qualifier Descriptions section.

Classname Qualifiers

/ALL

Specifies that a table of all available statistics (current, average, minimum, and maximum) is to be included in the display and summary output. For summary output, this qualifier is the default for all classes; otherwise, it is the default for all classes except CLUSTER, MODES, PROCESSES, STATES, SYSTEM, and VECTOR.

/AVERAGE

Selects average statistics to be displayed in a bar graph for display and summary output.

/CURRENT

Selects current statistics to be displayed in a bar graph for display and summary output. The /CURRENT qualifier is the default for the CLUSTER, MODES, STATES, SYSTEM, and VECTOR classes.

/MAXIMUM

Selects maximum statistics to be displayed in a bar graph for display and summary output.

/MINIMUM

Selects minimum statistics to be displayed in a bar graph for display and summary output.

Description

The MONITOR VECTOR command displays the number of 10-millisecond clock ticks per second in which one or more vector consumers have been scheduled on each currently configured vector processor in the system. Because the operating system schedules vector consumers only on those processors identified as "vector present," the VECTOR class output never displays vector CPU time for those processors that are "vector absent."

Note that, because vector consumers can use either the vector CPU, the scalar CPU, or both components of a vector-present processor, the vector CPU time in the VECTOR class display is not a strict measure of the actual usage of the processor's vector CPU component. Rather, it indicates the time during which a scheduled vector consumer has reserved both vector CPU and scalar CPU components of the vector-present processor for its own exclusive use.

The VECTOR class consists of the data item Vector Scheduled Rate, which is represented by a display of statistics that show the rates of 10-millisecond clock ticks per second during which vector consumers have been scheduled on each vector-present CPU.

Example

MONITOR>  MONITOR VECTOR
 
 



  

    

      

      
 
  
 
  
                           OpenVMS Monitor Utility 
                          VECTOR PROCESSOR STATISTICS 
              +-----+             on node SAMPLE 
              | CUR |          12-JUN-1998  22:52:42 
              +-----+ 
 Vector Consumers Scheduled          0         25        50        75      100 
                                     + - - - - + - - - - + - - - - + - - - - -+ 
 Vector Present CPU ID  0          13|***** 
 Vector Absent  CPU ID  1            | 
 Vector Absent  CPU ID  2            | 
 Vector Present CPU ID  4          58|********************** 
                                     |         |         |         |          | 
                                     |         |         |         |          | 
                                     |         |         |         |          | 
                                     |         |         |         |          | 
                                     |         |         |         |          | 
                                     |         |         |         |          | 
                                     + - - - - + - - - - + - - - - + - - - - -+ 
 




      

This example shows the VECTOR class display for a multiprocessing system containing two vector-present processors, CPU 0 and CPU 4. Displayed statistics represent rates of 10-millisecond clock ticks per second. For an average of 13 ticks per second over the last collection interval, vector consumers have been scheduled on CPU 0. For an average of 58 ticks per second over the last collection interval, vector consumers have been scheduled on CPU 4.

The SET DEFAULT command sets command qualifier, classname parameter, and classname qualifier defaults for the MONITOR command. Each SET DEFAULT command sets only the command qualifiers you specify, but replaces the entire set of classname parameters and classname qualifiers. All qualifiers and class names are identical to those for the MONITOR command.

Format

SET DEFAULT [/qualifier[,...]] classname[,...] [/qualifier[,...]]

Parameters

classname[,...]

Specifies one or more class names.

Command Qualifiers

/qualifier[,...]

One or more command qualifiers as described in the Command Qualifier Descriptions section.

Classname Qualifiers

/qualifier[,...]

One or more classname qualifiers.

Description

Command and classname qualifiers are identical to those for the MONITOR classname commands.

Example

MONITOR> SET DEFAULT /INTERVAL=10 PAGE/AVERAGE+IO/MAXIMUM /NODE=(LARRY,MOE,CURLEY)
      

The command in this example selects PAGE and IO as the default classes for the MONITOR command and specifies an interval of 10 seconds for the statistics display. The command specifies that AVERAGE statistics be displayed for the PAGE class, and that MAXIMUM statistics be displayed for the IO class. Finally, the command requests that data be collected on nodes LARRY, MOE, and CURLEY. After establishing these defaults, you can enter the MONITOR command without any qualifiers or parameters to display the requested information.

The SHOW DEFAULT command displays the defaults established by the SET DEFAULT command.

Format

SHOW DEFAULT

Parameters

None.

Qualifiers

None.

Description

The SHOW DEFAULT command verifies the defaults you have set with the SET DEFAULT command.

Example

MONITOR> SHOW DEFAULT
 
 



  

    

      

      
 
  
 
  
/BEGINNING = current time               /INTERVAL     = 10 
/ENDING    = indefinite                 /VIEWING_TIME = 10 
 
/FLUSH_INTERVAL = 300 
 
/NOINPUT 
 
/NORECORD 
 
/DISPLAY   = SYS$OUTPUT:.; 
 
/NOSUMMARY 
 
/NOFILENAME 
 
/NOCOMMENT 
 
Classes: 
 PAGE/AVERAGE              IO/MAXIMUM 
 
Nodes: 
 LARRY                     MOE                       CURLEY 




      

The command in this example displays the defaults specified by the previous SET DEFAULT command.

16.1 MOUNT Description

Normally, MOUNT allocates the device to the user who enters the command. However, mounting volumes with the /SHARE, /GROUP, or /SYSTEM qualifier deallocates the device, because the purpose of these qualifiers is to make the volume shareable.

Any subprocess in the process tree can mount or dismount a volume for the job. When a subprocess mounts a volume (for the job) as private, the master process of the job becomes the owner of this device. This provision is necessary because the subprocess may be deleted and the volume should remain privately mounted for this job. However, when a subprocess explicitly allocates a device and then mounts a private volume on this device, the subprocess retains device ownership. In this situation, only subprocesses with SHARE privilege have access to the device.

Upon successful completion of the operation, MOUNT notifies you with a message sent to SYS$OUTPUT. If the operation fails for any reason, MOUNT notifies you with an error message.

Certain file utilities such as MOUNT allocate virtual memory to hold copies of the index file and storage bitmaps. Beginning with larger bitmaps in OpenVMS Version 7.2, the virtual memory requirements of these utilities increase correspondingly. To use MOUNT on volumes with large bitmaps, you might need to increase your page file quota. On OpenVMS VAX systems, you might also need to increase the system parameter VIRTUALPAGECNT. The virtual memory size is shown as VAX pages (or Alpha 512-byte pagelets) per block of bitmap. Note that the size of the index file bitmap in blocks is the maximum number of files divided by 4096. The virtual memory requirements for MOUNT is equal to the sum of the sizes of all index file bitmaps and storage bitmaps on the volume set. This requirement applies to MOUNT only if you rebuild a volume.

16.2 MOUNT Usage Summary

The Mount utility (MOUNT) makes a disk or magnetic tape volume available for processing.

Format

MOUNT device-name[:][,...] [volume-label[,...]] [logical-name[:]]

Parameters

device-name[:][,...]

Specifies the physical device name or logical name of the device on which the volume is to be mounted. On a system where volumes are not connected to HSCs (hierarchical storage controllers), use the following format:

• ddcu:

The dd describes the device type of the physical devices used. For example, an RA60 disk drive is device type DJ, and an RA80 or RA81 disk drive is device type DU. The c identifies the controller, and the u identifies the unit number of the device.

On a system with HSCs, use one of the following formats:

• node$ddcu:
• allocation-class$ddcu:

If your devices are dual ported to HSCs, use the allocation-class format. For example, $125$DUA23 represents an RA80 or RA81 disk with unit number 23. The disk's allocation class is $125$. The c part of the format is always A for HSC disks. TROLL$DJA12 represents an RA60 disk with unit number 12. The device is connected to an HSC named TROLL. Refer to OpenVMS Cluster Systems for more information about naming conventions.

Device names can be generic so that if no controller or unit number is specified, the system attempts to mount the first available device that satisfies those specified components of the device names. If no volume is physically mounted on the specified device, MOUNT displays a message requesting that you place the volume in the device; after you place the volume in the named drive, MOUNT then completes the operation.

If you specify more than one device name for a disk or magnetic tape volume set, separate the device names with either commas or plus signs. For a magnetic tape volume set, you can specify more volume labels than device names or more device names than volumes.

volume-label[,...]

Specifies the label on the volume. The number of characters allowed in a label depends on the type of device, as follows:

Device Type	Number of Characters in Label
Magnetic tape	0-6
Files--11 disk	1-12
ISO 9660 disk	1-32

OpenVMS requires disk volume labels to be unique in the first 12 characters within a given domain. For example, disks mounted by different members of the same group using the /GROUP qualifier must be unique. However, disks mounted in different domains, such as one mounted using the /GROUP qualifier and one mounted privately, can use the same volume label.

If you mount an ISO 9660 volume using the /SYSTEM or /CLUSTER qualifier, and the volume label is not unique within the first 12 characters, you must supply an alternate volume label using the qualifier /OVERRIDE=IDENTIFICATION. If you choose this option, then Mount verification is disabled for the device.

In addition, if a volume is part of a volume set and the first 12 characters of the volume-set name are the same as the first 12 characters of the volume label, a lock manager deadlock will occur. To avoid this problem, you must override either the volume label (by using the /OVERRIDE qualifier) or the volume-set name (by using the /BIND qualifier).

If you specify more than one volume label, separate the labels with either commas or plus signs. The volumes must be in the same volume set and the labels must be specified in ascending order according to relative volume number.

When you mount a magnetic tape volume set, the number of volume labels need not equal the number of device names specified. When a magnetic tape reaches the end-of-tape (EOT) mark, the system requests the operator to mount the next volume on one of the devices. The user is not informed of this request; only the operator is informed.

When you mount a disk volume set, each volume label specified in the list must correspond to a device name in the same position in the device name list.

The volume-label parameter is not required when you mount a volume with the /FOREIGN or /NOLABEL qualifier or when you specify /OVERRIDE=IDENTIFICATION. To specify a logical name when you enter either of these qualifiers, type any alphanumeric characters in the volume-label parameter position.

logical-name[:]

Defines a 1- to 255-alphanumeric character string logical name to be associated with the volume.

If you do not specify a logical name, the MOUNT command assigns the default logical name DISK$volume-label to individual disk drives; it assigns the default logical name DISK$volume-set-name to the device on which the root volume of a disk volume set is mounted. Note that if you specify a logical name in the mount request that is different from DISK$volume-label or DISK$volume-set-name, then two logical names are associated with the device.

If you do not specify a logical name for a magnetic tape drive, the MOUNT command assigns only one logical name, TAPE$volume-label, to the first magnetic tape device in the list. No default logical volume-set name is assigned in this case.

The MOUNT command places the name in the process logical name table, unless you specify /GROUP or /SYSTEM. In the latter cases, it places the logical names in the group or system logical name table.

If you specify the /CLUSTER qualifier, the logical name is established on each node in the cluster.

Note Avoid assigning a logical name that matches the file name of an executable image in SYS$SYSTEM. Such an assignment prohibits you from invoking that image.

Do not use the logical name assigned to a volume as a distributed file system (DFS) access point. If you attempt to add a DFS access point using the same name as the logical name, DFS fails as in the following example:

$ SHOW LOG DISK$* (LNM$SYSTEM_TABLE) "DISK$TIVOLI_SYS" = "TIVOLI$DUA0:" $ MCR DFS$CONTROL DFS> ADD ACCESS DISK$TIVOLI_SYS TIVOLI$DUA0:[000000] %DNS-W-NONSNAME, Unknown namespace name specified

If the logical name of a volume is in a process-private table, then the name is not deleted when the volume is dismounted.

MOUNT returns you to the DCL level after it either successfully completes the operation or fails, generating an error message. If you press Ctrl/Y or Ctrl/C, MOUNT aborts the operation and returns you to the DCL prompt.

You can direct output from MOUNT operations with the /COMMENT and /MESSAGE qualifiers. When the mount operation requires operator assistance, use /COMMENT to specify additional information to be included with the operator request. The /COMMENT text string is sent to the operator log file and to SYS$OUTPUT. The string must contain no more than 78 characters.

Use the /MESSAGE qualifier (this is the default) to send mount request messages to your current SYS$OUTPUT device. If you specify /NOMESSAGE during an operator-assisted mount, messages are not sent to SYS$OUTPUT; the operator sees them, however, if an operator terminal is enabled to receive messages.

Many MOUNT qualifiers require special privileges. Some qualifiers require different privileges according to which qualifier keyword you specify. See the individual qualifiers for details. The following table lists MOUNT qualifiers that require special privileges.

Qualifier	Keywords	Required Privilege
/ACCESSED		OPER
/CACHE=	[NO]EXTENT[=n]	OPER
	[NO]FILE_ID[=n]	OPER
	[NO]QUOTA[=n]	OPER
/FOREIGN		VOLPRO 1
/GROUP		GRPNAM
/MULTI_VOLUME		VOLPRO
/OVERRIDE=	ACCESSIBILITY	VOLPRO 1
	EXPIRATION	VOLPRO 1
	LOCK	VOLPRO 1
	SHADOW	VOLPRO 1
/OWNER_UIC=	uic	VOLPRO 1
/PROCESSOR=	UNIQUE	OPER
	SAME:device	OPER
	file-spec	OPER and CMKRNL
/PROTECTION=	code	VOLPRO 1
/QUOTA		VOLPRO 1
/SYSTEM		SYSNAM
/WINDOWS=	n	OPER

	privacy and legal statement
6048PRO_046.HTML