To define the accounts

As part of installing UIE/VM, you need to define the VM accounts as follows:

UIEDRIVE controls the VM Monitor data collection process. You run UIEMON EXEC on this account to send VM Monitor commands to the UIEMON account. This provides a mechanism to sample SEEKS records by alternately enabling and disabling the SEEKS domain. BMC Software recommends that you sample SEEKS records so that device usage information reported by UIE/VM can be as accurate as possible. UIEDRIVE should be given permission to XAUTOLOG and send commands to UIEMON and UIERUN. The following is a sample of a UIEDRIVE directory entry. A sample PROFILE EXEC called UIEDRIVE PROFILE is included on the UIE/VM distribution tape.  

UIEMON is the account that runs the VM Monitor. UIEMON must be logged on with access to the necessary tape drives or project disk, before UIEDRIVE attempts to start the VM Monitor data collection process. A sample PROFILE EXEC called UIEMON PROFILE is included on the UIE/VM distribution tape.
When defining UIEMON, you need to include several directory entries, as follows:
XAUTOLOG UIEDRIVE
OPTION APPLMON
IUCV *MONITOR MSGLIMIT 255
NAMESAVE MONDCSS
CONSOLE vdev 3270 T UIEDRIVE
vdev is the virtual device number for the virtual console (for example, 3E0). The following is a sample of a UIEMON directory entry:

UIERUN is the account from which you run UIE/VM. This account needs to link to and obtain read access to the UIEVM disk. When defining UIERUN, you need to include XAUTOLOG UIEDRIVE. The UIERUN memory requirements increase when:

• More intervals are processed per run
• More workloads are defined
• CMS users are included in the Visualizer file

The following is a sample of a UIERUN directory entry:

UIEVM is the disk on which the UIE/VM software is to be installed. After UIE/VM is installed on this disk, no additional action on this disk is required. For more information, seeInstalling UIE/VM section in the BMC AMI Capacity Management documentation. 
The following is a sample of a UIE/VM directory entry:

Deciding whether to collect VM Monitor data on tape or disk

Before deciding whether to collect VM Monitor on a disk or a tape, consider the advantages of each.

The advantages of collecting VM Monitor on disk:

• This method requires less user intervention making the process easier to automate
• VM Monitor data processing proceeds more quickly

The advantages of collecting VM Monitor data on tape:

• Disk space requirements are dramatically lower
• VM Monitor data can be archived

Collecting on disk

If you collect VM Monitor data on disk, you need to give UIEMON (or a project disk to which UIEMON has write access) a large amount of disk space as described in To define the accounts section. If you collect data for more than 22 hours per day on a daily basis, then the disk must be large enough to hold two days worth of data. In this case, UIE/VM can process one VM Monitor data file while another VM Monitor data file is being collected. If you collect data for fewer than 22 hours a day, then UIE/VM has a window of 2 hours or more to process the VM Monitor data before the collection for the next day begins.

Collecting on tape

If you collect VM Monitor data on tape, you need to decide if you want to devote one or two tape drives to the process.

• If you use a single tape drive, then that tape drive must be attached at address 181 after you log on to UIEMON. When the tape is filled, it is ejected from the tape drive and a blank must be inserted.
• If you use two tape drives, then those tape drives must be attached at addresses 181 and 182 after you log on to UIEMON. When a tape is filled, it is ejected, and VM Monitor data is written to the tape in the other tape drive. You need to be sure that a blank tape has been inserted into the tape drive that is not in use before the tape in the drive that is in use is filled.

If you collect VM Monitor on tape, we recommend that you devote two tape drives to UIEMON. Devoting two tape drives enables VM Monitor to switch to the other drive when the tape in the active drive is filled. If you just use one tape drive, a gap in the data will begin whenever a tape is filled, and that gap will persist until the tape has been rewound and ejected and a new tape has been inserted.

Setting up the UIEMON EXEC on the UIEDRIVE account

An EXEC called the UIEMON EXEC is distributed on the UIE/VM product tape. You should copy the UIEMON EXEC to the UIEDRIVE account. The top several lines of UIEMON EXEC have several parameters that need to be tailored. The parameters are as follows:

Parameter settings in the UIEMON EXEC

In this example, the Monitor is stopped at 17:00 (5:00 P.M.). The Monitor sample interval is 1 minute, with a sampling rate of 2 seconds. For every 5 second period, 1 second of SEEKS records is recorded. The VM Monitor data is written to disk file called MONITOR DATA. UIEMON must obtain write access to a disk at file mode J.

When collection of VM Monitor data is complete, the VM Monitor file is renamed to have a file type of PROCESS. VM Monitor data from the SCHEDULER, PROCESSOR, and APPLDATA domains is not collected.

In this example, the Monitor is stopped at 23:45 (11:45 P.M.). The Monitor sample interval is 2 minutes, with a sampling rate of 5 seconds. No SEEKS records are recorded. The VM Monitor data is written to tape. UIEMON has access to two tape drives at addresses 181 and 182.

Automating VM Monitor data collection and processing

After you have set up the accounts that are necessary to run VM Monitor and have defined the parameters that you plan to use to collect data, you can run the process on an automated basis. Perform the following steps:

1. Have your VM Systems Programmer set up UIEDRIVE so that it is logged on automatically a few minutes before you want to start VM Monitor data collection. Or begin just after midnight if you want start the VM Monitor at the very beginning of the day.

2. At the end of the PROFILE EXEC on UIEDRIVE, add the lines:

   ‘EXEC UIEMON’
   ‘CP LINK uievm 191 401’ /* (where uievm is the UIE/VM installed disk) */
   ‘ACCESS 401 J’
   ‘EXECIO 0 CP (str XAUTOLOG UIERUN IPL CMS SYNCH #EXEC UIERUN study #LOGOFF’ /*
   (where study is the name of a UIE/VM study) */
   ‘LOGOFF’

   Warning

   Important

   As an alternative to steps 1 and 2, you can use the UIEDRIVE PROFILE file distributed with UIE/VM as the PROFILE EXEC on the UIEDRIVE account. This EXEC will keep the UIE/VM daily process perpetually running. If you collect less than 16 hours of data per day, you will need to reduce the size of the execution window in UIEDRIVE PROFILE to be smaller then the number of hours collected. You should instruct your VM systems programmer to always log on UIEDRIVE whenever your VM system is restarted.

3. If you are processing more than 22 hours of data a day and if you are collecting VM Monitor data on disk, you need to rename the VM Monitor file before you start processing it using UIE/VM. Then the collection of the VM Monitor data for the next day can begin while UIE/VM is running. You should define your UIE/VM study to use that new name.
   By default, this is done in UIEMON EXEC. If you do not need to rename the VM Monitor file in UIEMON EXEC, you can comment out the following line:

   'EXECIO 0 CP (str SEND' mvm 'RENAME' mname mtype mm mname mtype2 mm

   These statements appear in the UIEMON EXEC. You can comment them out or uncomment them, as necessary. A sample PROFILE EXEC called UIEDRIVE PROFILE is included on the UIE/VM distribution tape.

4. If you are collecting VM Monitor data on tape, the appropriate tape drives need to be accessed by UIEMON after logging on. After collection of a day's VM Monitor data is complete, the tapes containing that data must be made available to UIERUN, the VM account that uses UIE/VM to process the VM Monitor data.

Running the VM Monitor manually

UIE/VM uses data from the VM Monitor domains in the following table:

If you want to run the VM Monitor manually rather than by using the UIEMON EXEC, enter the following commands:

Avoiding Monitor Suspension Records

A Monitor Suspension Record (Domain 1 Record 3) shows the count of Event Records lost due to DCSS overflow, or loss of the IUCV path to MONWRITE. You may need to enlarge the MONITOR DCSS. For capacity planning studies, you should avoid intervals that contain Monitor Suspension Records.

Moving Monitor Data from disk to tape or from tape to disk

The writer virtual machine can use MONWRITE to write MONITOR data from the MONITOR saved segment (DCSS) to disk or tape. UIE/VM processes the data from both mediums as long as it is in MONWRITE format. Monitor data written to disk file fileid can be transferred to tape with the following statements:

The sequence of steps outlined preserves the format of the data. However, do not use the VMFPLC2 or TAPE commands to transfer Monitor disk files to tape because they do not preserve the format of the data.