Using the Monitor line command
The M (Monitor) line command is the quickest way to monitor a job or device that is excessively busy. You can invoke the M line command from MainView views of jobs or devices.
- On the COMMAND line, type JUDEV to display the JUDEV view.When JUDEV is displayed, look for a job that is using a lot of I/O resources.
In the Command field next to the job that you have selected, type M, as shown in the following figure..
DDMMMYYYY HH:MM:SS -------- MAINVIEW WINDOW INTERFACE (Vv.r.mm) ---------------
COMMAND ===> SCROLL ===> PAGE
CURR WIN ===> 1 ALT WIN ===>
>W1 =JUDEV=============SYSE=====*========DDMMMYYYY==HH:MM:SS====MVMVS====D===42
C Jobname JES Job T SrvClass %Use %Use %Use %Use %Use %Delay %Dly De
- -------- Number - -------- VolSer DASD Tape Dev AllRsn VolSer Dev Nu
M BMVSLKV TSU01243 T TSONRM 7.69 7.7 7.7 7.7 83A
XCFAS S SYSTEM 3.39 4.3 4.3 5.0 0.2 0.2 83A
MIMGR STC01143 S SYSSTC 1.95 1.9 1.9 3.3 871
CSTTXC TSU01296 T TSONRM 1.72 3.4 3.4 3.4 83A
CSTTXC TSU01296 T TSONRM 1.72 3.4 3.4 3.4 83A
SMF S SYSTEM 1.24 1.2 1.2 1.2 0.2 0.2 830
XCFAS S SYSTEM 0.89 4.3 4.3 5.0 0.2 831
AAOAOQF STC01225 S STCNRM 0.78 1.1 1.1 1.1 0.2 836
DC$BBIE STC01136 S STCNRM 0.57 1.0 1.0 1.4 0.7 0.7 83A
DC$ESTR STC01189 S STCNRM 0.55 0.7 0.7 0.8 0.8 0.8 83A
AAOAOQE STC01227 S STCNRM 0.44 0.9 0.9 1.0 83F
CATALOG S SYSTEM 0.41 0.6 0.6 0.8 830MVScope starts monitoring the job that you selected and displays the MSMONSET view. The MSMONSET view, as shown in the following figure, shows the selected job in the sampling state.
DDMMMYYYY HH:MM:SS -------- MAINVIEW WINDOW INTERFACE (Vv.r.mm) ---------------
COMMAND ===> SCROLL ===> PAGE
CURR WIN ===> 1 ALT WIN ===>
W1 =MSMONSET==========SYSE=====*========DDMMMYYYY==HH:MM:SS====MVMVS====D====1
MVScope Monitor Set
Symptoms Problem Analysis
. Hot Program Job BMVSLKV , Devn 0D06 . Tasks and SRBs
No samples 10:11:28 to 11:12:28 . Programs
. Hot Instruction 17 CPU, 39 I/O samples . I/Os
Addr: 00006B48 35.3% Sampling NOV 16, YYYY . Traces
Pgm: BBD9MAIV No sampling errors > Maps
CSECT: BBD9MAIV
Ofst: +0001B6 +----------------------+ Utilities
. Hot Task | Place cursor on | > Monitored Job
Addr: 007E39C8 94.1% | menu item and | > First Monitored Dev
Name: BBD0MACP | press ENTER | . Monitor Sets
. Hot DASD Track +----------------------+
CCHH: 00E5000C 35.9% . Return ...
Dsn: SYS96158.T13504- Press Enter to see the monitoring proceeding.
Default monitoring with the M line command
When you start MVScope by using the M line command, the type of sampling (CPU, IO, or CPUIO) is determined by the type of view in which you are located.
The MVScope primary command can only be called from views using the record types shown in the following table:
Type of record | Type of sampling |
|---|---|
ASIW | CPU |
DSRE | CPUIO |
DXRE | IO |
WUSR | CPUIO |
To determine the type of record with which your view is associated
- Go into hilevel.BBACTDEF(BBMSAV01), and find the name of the view from which you want to run the MVScope primary command.
Look in the record type column for the type of view. If the record type is listed in the previous table, the MVScope primary command will sample accordingly.
- If the view is listed as a JOIN view, scroll down until you see a list of the joined view types.
Locate the joined view, and look for the base records that make up that joined view.
- When you know the type of record for the view, refer to the previous table to determine the type of sampling that MVScope will perform for that view.
Related topic