MEASURE Subsystem

MEASURE is a monitoring tool that collects performance statistics about system resources. It gathers data from system components, network components , and applications. This information can be used to tune the system, detect bottlenecks, balance workload, and do capacity planning.

The MEASURE subsystem must be running before any measurement can be made. The subsystem must be started by a SUPER Group member. It is often started as part of the cold-load system start up procedure.

Multiple users can run MEASURE sessions at the same time, and each user can configure and take measurements independently. The performance monitor provides both a command interface and a programmatic interface.

The command interface provides commands that can be entered at a terminal or input from a file. The programmatic interface consists of a set of callable procedures that can be used in application programs to access MEASURE's functions. The procedures allow an application to configure a measurement, start it, stop it, and write the information to the specified output file for analysis.

RISK MEASURE is strictly a reporting tool and, therefore, poses no security risk. The subsystem itself has minimal impact on performance; it can be started and then allowed to run continuously. However, a MEASURE collection process can consume large amounts of system resources and should not be run on secure system without close supervision to minimize performance issues.

RISK MEASURE data files can be very large.

Once the data files have been reviewed they should be deleted.

RISK MEASURE data files can be very large.

Don't store the files on $SYSTEM to avoid affecting system performance.

The following list describes the components that make up the MEASURE Subsystem.

MEASCHMA

MEASCOM

MEASCTL

MEASFH

MEASDDLB

MEASDDLF

MEASDDLS

MEASDECS

MEASIMMU

MEASMON

MEASTCM

MEASZIP

OUTPUT DATA FILES

MEASCOM

MEASCOM is the command interpreter for the MEASURE subsystem. It allows the user who started it to carry on an interactive session with the MEASURE subsystem.

MEASCOM can be used by a SUPER Group member to start the MEASURE subsystem.

Once the subsystem is started, any user can use MEASCOM to configure, run, and examine measurements. Multiple MEASURE sessions can be run simultaneously and multiple measurements may be performed within a single session.

MEASCTL

MEASCTL is Measure's control program. There is one MEASCTL for each CPU on a system named $XMnn where the nn is the number of the CPU; i.e. $XM01. They are created by MEASMON when the MEASURE subsystem is started. MEASMON automatically starts the MEASCTL processes, and restarts them if they abend or stop.

MEASFH

MEASFH processes are the Measure's file handlers. The MEASFH processes are created whenever a measurement is run or a resulting measure data file is examined. There is one MEASFH process per user-designated data file. The process formats the file, adds the data to it, and retrieves the data as needed.

MEASCHMA, MEASDDLB, MEASDDLF, MEASDDLS, MEASDECS

These files contain the record definitions (DDLs) for all the optional structured files produced by the MEASURE commands and procedures that display Measurement results. These files allow users to produce custom reports and programs using measurement data.

MEASDECS

The MEASDECS file contains the structure declarations and literal value definitions used in the MEASURE callable procedures.

MEASIMMU

The MEASIMMU file contains the MEASURE error messages and the online help text accessible through the MEASCOM HELP command.

MEASMON

MEASMON is Measure's Monitor. It creates and coordinates all the MEASCTL processes in each CPU, sending measurement configuration requests and gathering information from them.

There is a single MEASMON process (running as a NonStop process pair) per system. The process is created when the MEASURE subsystem is started.

MEASMON monitors the operation of MEASURE for an entire system. There is one MEASMON process pair for each system, named $XMON or $XMM. The process pair is normally started as part of the standard system startup procedure. MEASMON starts the MEASCTL processes.

RISK Measurements cannot be performed if the MEASURE Subsystem is not running.

RISK If the $XMON process is stopped using the name form of the TACL STOP command, only the MEASMON processes are stopped, not the MEASCTL processes. So once MEASMON is stopped, the MEASCTL processes must be stopped individually or they will be left running.

AP-ADVICE-MEASDATA-01 Use MEASCOM to stop the MEASURE subsystem.

MEASTCM

The MEASTCM product is used to summarize measurement data for capacity- planning studies.

MEASZIP

The MEASZIP contains the optional MEASURE GUI application, which can be downloaded to a PC to install the windows client interface.

OUTPUT DATA FILES

MEASURE generates large data files that can reside anywhere on the system. These files are identified with file code 175.

AP-ADVICE-MEASDATA-02 MEASURE data files do not present a security risk, however, they can be very large files. Once reviewed they should be removed.

Securing MEASURE Components

BP-FILE-MEASURE-01 MEASCHMA should be secured "NUNU".

BP-OPSYS-OWNER-01 MEASCHMA should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-01 MEASCHMA must reside in $SYSTEM.SYSnn.

BP-FILE-MEASURE-02 MEASCOM should be secured "UUNU".

BP-OPSYS-OWNER-01 MEASCOM should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-01 MEASCOM must reside in $SYSTEM.SYSnn.

BP-PROCESS-MEASCTL-01 $XMnn processes should be running.

BP-FILE-MEASURE-03 MEASCTL should be secured "UUNU".

BP-OPSYS-LICENSE-01 MEASCTL must be LICENSED.

BP-OPSYS-OWNER-01 MEASCTL should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-01 MEASCTL must reside in $SYSTEM.SYSnn.

BP-FILE-MEASURE-04 MEASFH should be secured "UUNU".

BP-OPSYS-OWNER-01 MEASFH should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-01 MEASFH must reside in $SYSTEM.SYSnn.

BP-FILE-MEASURE-05 MEASDDLB should be secured "NUNU".

BP-OPSYS-OWNER-01 MEASDDLB should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-01 MEASDDLB must reside in $SYSTEM.SYSnn.

BP-FILE-MEASURE-06 MEASDDLF should be secured "NUNU".

BP-OPSYS-OWNER-01 MEASDDLF should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-01 MEASDDLF must reside in $SYSTEM.SYSnn.

BP-FILE-MEASURE-07 MEASDDLS should be secured "NUNU".

BP-OPSYS-OWNER-01 MEASDDLS should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-01 MEASDDLS must reside in $SYSTEM.SYSnn.

BP-FILE-MEASURE-08 MEASDECS should be secured "NUNU".

BP-OPSYS-OWNER-01 MEASDECS should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-01 MEASDECS must reside in $SYSTEM.SYSnn.

BP-FILE-MEASURE-09 MEASIMMU should be secured "NUNU".

BP-OPSYS-OWNER-01 MEASIMMU should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-01 MEASIMMU must reside in $SYSTEM.SYSnn.

BP-PROCESS-MEASMON-01 $XMM process should be running.

BP-FILE-MEASURE-10 MEASMON should be secured "UUNU".

BP-OPSYS-LICENSE-01 MEASMON must be LICENSED.

BP-OPSYS-OWNER-01 MEASMON should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-01 MEASMON must reside in $SYSTEM.SYSnn.

BP-FILE-MEASURE-11 MEASTCM should be secured "UUNU".

BP-OPSYS-OWNER-02 MEASTCM should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-02 MEASTCM must reside in $SYSTEM.SYSTEM.

BP-FILE-MEASURE-12 MEASZIP should be secured "NUNU".

BP-OPSYS-OWNER-01 MEASZIP should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-01 MEASZIP must reside in $SYSTEM.SYSnn.

If available, use Safeguard software or a third party object security product to grant access to the MEASURE subsystem programs only to users who require access in order to perform their jobs.

BP-SAFE-MEASURE-01 Add a Safeguard Protection Record to grant appropriate access to the MEASMON object file.

BP-SAFE-MEASURE-02 Add a Safeguard Protection Record to grant appropriate access to the MEASCOM object file.

	Discovery Questions	Look here:
PROCESS-MEASMON-01	Is the $XMM process running?	Status
PROCESS-MEASCTL-01	Are the $XMnn processes running?	Status
FILE-POLICY	Who is allowed to run MEASURE queries on the system?	Policy
OPSYS-OWNER-01	Who owns the MEASCHMA file?	Fileinfo
OPSYS-OWNER-01	Who owns the MEASCOM object file?	Fileinfo
OPSYS-OWNER-01	Who owns the MEASCTL object file?	Fileinfo
OPSYS-OWNER-01	Who owns the MEASFH object file?	Fileinfo
OPSYS-OWNER-01	Who owns the MEASDDLB object file?	Fileinfo
OPSYS-OWNER-01	Who owns the MEASDDLF object file?	Fileinfo
OPSYS-OWNER-01	Who owns the MEASDDLS object file?	Fileinfo
OPSYS-OWNER-01	Who owns the MEASDECS object file?	Fileinfo
OPSYS-OWNER-01	Who owns the MEASIMMU object file?	Fileinfo
OPSYS-OWNER-01	Who owns the MEASMON object file?	Fileinfo
OPSYS-OWNER-01	Who owns the MEASZIP object file?	Fileinfo
OPSYS-OWNER-02	Who owns the MEASTCM object file?	Fileinfo
OPSYS-LICENSE-01	Is the MEASCTL object file licensed?	Fileinfo
OPSYS-LICENSE-01	Is the MEASMON object file licensed?	Fileinfo
FILE-MEASURE-01	Is the MEASCHMA file secured correctly?	Fileinfo
FILE-MEASURE-02 SAFE-MEASURE-02	Is the MEASCOM object file correctly secured with the Guardian or Safeguard system?	Fileinfo Safecom
FILE-MEASURE-03	Is the MEASCTL object file secured correctly?	Fileinfo
FILE-MEASURE-04	Is the MEASFH object file secured correctly?	Fileinfo
FILE-MEASURE-05	Is the MEASDDLB file secured correctly?	Fileinfo
FILE-MEASURE-06	Is the MEASDDLF file secured correctly?	Fileinfo
FILE-MEASURE-07	Is the MEASDDLS file secured correctly?	Fileinfo
FILE-MEASURE-08	Is the MEASDECS file secured correctly?	Fileinfo
FILE-MEASURE-09	Is the MEASIMMU object file secured correctly?	Fileinfo
FILE-MEASURE-10 SAFE-MEASURE-01	Is the MEASMON object file correctly secured with the Guardian or Safeguard system?	Fileinfo Safecom
FILE-MEASURE-11	Is the MEASTCM object file secured correctly?	Fileinfo
FILE-MEASURE-12	Is the MEASZIP file secured correctly?	Fileinfo