A +-------------------------------------------------------------------+ | README file for SM2 V15.0B | | Edition: April 2006 | | openSM2 V6.0A Manual, U3585-J-Z125-9-76 | | Edition December 2004 | +-------------------------------------------------------------------+ This README file describes all changes to the user interfaces of the SM2 Software Monitor, including its components SM2U1 and SM2R1, which have been implemented for SM2 V15.0B for BS2000/OSD 6.0B. Contents -------- 1 The SM2 monitoring program............................Page 1 1.1 Dynamic IO reconfiguration ..........................Page 1 1.2 Parallel Access Volumes (PAV) .......................Page 1 2 SM2 monitoring programs ..............................Page 2 2.1 CHANNEL-IO ..........................................Page 2 2.2 ISAM ................................................Page 2 2.3 PERIODIC-TASK .......................................Page 2 2.4 SAMPLING-DEVICE .....................................Page 2 2.5 SERVICETIME .........................................Page 3 2.6 STORAGE-SYSTEM ......................................Page 3 2.7 SYSTEM ..............................................Page 3 2.8 TASK ................................................Page 4 2.9 VM2000 ..............................................Page 4 3 SM2 operation ........................................Page 5 3.1 Statements for SM2 administrators ...................Page 5 3.1.1 ADD-/REMOVE-COSMOS-EVENT ............................Page 5 3.1.2 ADD-ISAM-FILE .......................................Page 5 3.1.3 REMOVE-ISAM-FILE ....................................Page 6 3.2 Statements for nonprivileged users ..................Page 7 3.2.1 Report ..............................................Page 7 3.2.2 SELECT-DEVICE-DISK-PARAMETERS .......................Page 7 3.2.3 SELECT-PERIODIC-TASK-PARAMETERS......................Page 7 4 SM2 screen output ....................................Page 8 4.1 ACTIVITY Report .....................................Page 8 4.2 DEVICE DISK Report ..................................Page 9 4.3 DEVICE TD Report ....................................Page 10 4.4 ISAM FILE Report ....................................Page 11 4.5 MEMORY Report .......................................Page 12 4.6 PERIODIC TASK Report ................................Page 13 4.7 SHARED PUBSET Report ................................Page 14 4.8 VM Report ...........................................Page 15 4.9 VM GROUP Report .....................................Page 16 5 SM2 program interfaces ...............................Page 17 5.1 The SM2GDAT macro ...................................Page 17 5.1.1 Structure of the output area ........................Page 17 5.2 Structures of the SM2GDAT macro .....................Page 18 5.2.1 Structure of the ISAM-FILE data buffer ..............Page 18 5.2.2 Structure of the VM-GROUP data buffer ...............Page 19 5.2.3 Structure of the TIME-IO data buffer ................Page 20 6 SM2U1 ................................................Page 21 6.1 SELECT-MEASUREMENT-GROUPS ...........................Page 21 7 SM2R1 ................................................Page 22 7.1 PRINT-REPORTS .......................................Page 22 A 8 Variables reports / Statistics .......................Page 23 8.1 Notes to variables reports and statistics ...........Page 23 8.2 Table of report groups ..............................Page 24 8.3 Table of report names ...............................Page 24 8.4 Table of variables reports ..........................Page 25 9 Messages .............................................Page 27 10 Glossary .............................................Page 29 A Page 1 1 The SM2 monitoring program 1.1 Dynamic IO reconfiguration (addition to page 34, Volume 1) The following table describes the behavior of the monitoring programs when adding a device/channel in the context of a dynamic IO reconfiguration: Monitoring | behavior when adding a device/channel program | --------------+------------------------------------------------------- DISK | Monitoring program is not restartet, even if the | device belongs to the monitoring program definition --------------+------------------------------------------------------- DISK-FILE | No action --------------+------------------------------------------------------- SAMPLING- | Monitoring program is terminated internally and then DEVICE | restarted --------------+------------------------------------------------------- SERVICETIME | Monitoring program is not restartet, even if the | device belongs to the monitoring program definition --------------+------------------------------------------------------- SYSTEM | Device is involved in the measurement, if it belongs | to the monitoring program definition --------------+------------------------------------------------------- TASK | Monitoring program is not restartet, even if the | device belongs to the monitoring program definition --------------+------------------------------------------------------- CHANNEL-IO | Monitoring program is terminated internally and then | restartet, if monitoring program definition is *ALL --------------+------------------------------------------------------- SAMPLING- | Monitoring program is terminated internally and then CHANNEL | restartet --------------+------------------------------------------------------- If a device /channel is removed, no monitoring program is terminated internally and then restarted. The device/channel is anymore visible in the SM2 datas, but the measurement values are always zero. 1.2 Parallel Access Volumes (PAV) SM2 supports maximally 7 alias devices of a base device. A Page 2 2 SM2 monitoring programs 2.1 CHANNEL-IO (addition to page 42, Volume 1) The monitoring program CHANNEL-IO provides RSC IOs (only on systems with SPARC architecture) of TD / openCRYPT-BOX devices and disks. 2.2 ISAM (addition to page 46, Volume 1) The monitoring program ISAM also provides the measurement of ISAM pools in the Data Space. For this purpose the pathname of the NKISAM file is the sign for identification of the ISAM pool. In addition to the previous monitoring program definition of ISAM pools by the pool name, it is now possible to select ISAM pools with the pathname of the NKISAM file. Die Daten werden in einem neuen ISAM FILE-Report ausgegeben, der die gleichen Daten wie der ISAM-Report enthaelt. The datas are output in a new ISAM FILE report, which has the same datas as the ISAM report. In SM2R1 there is a new report group ISAM-FILE. The nonprovileged monitoring program ISAM does not support this ISAM pools. 2.3 PERIODIC-TASK (addition to page 47, Volume 1) The support of RSC IOs (only on systems with SPARC architecture) of TD / openCRYPT-BOX devices is not possible, because there is no connection between RSC IOs and tasks. Instead of this the number of physical accesses to coded files are output. 2.4 SAMPLING-DEVICE (addition to page 54, Volume 1) RSC IOs for disks (only on systems with SPARC architecture) are gathered and gone into the IOs for read and write. Additionally the average number of parallel handled RSC IOs is a new value. RSC IOs for TD / openCRYPT-BOX devices (only on systems with SPARC architecture) are gathered and gone into the IOs for read and write (since BCAM V18.0 and/or CRYPT V1.2). If the monitoring program is used for parallel access volumes (PAV) in Symmetrix systems, the following applies: - Only base devices are output in the DEVICE DISK report A Page 3 - The monitored data refers to the base device and the assigned alias devices (summation, averaging). If an alias device changes from one base device to another, then the datas of the alias device are not included in the datas of any base device in the actual measurement interval. The data of the alias devices are also output at the SM2GDAT data interface. 2.5 SERVICETIME (addition to page 55, Volume 1) There is an incompatible modification: A check is carried out to establish that the disk devices have the status 'attached'. 2.6 STORAGE-SYSTEM (addition to page 57, Volume 1) The monitoring program STORAGE-SYSTEM gathers additionally the meta volume information for Symmetrix systems. The information is only output at the SM2GDAT data interface and written into SM2 output file. The SM2 online reports and the SM2R1 reports do not provide the meta volume information of Symmetrix systems. This is only supported from Inspector and Analyzer. 2.7 SYSTEM (addition to page 58, Volume 1) The support of RSC IOs (only on systems with SPARC architecture) of TD / openCRYPT-BOX devices is not possible, because there is no connection between RSC IOs and tasks. If the monitoring program is used for parallel access volumes (PAV) in Symmetrix systems, the following applies: - Base and alias devices can be selected. - The monitored data refers to the base device and the assigned alias devices (summation, averaging). If a base device gets a new alias device, then the alias device is involved in the measurement. A Page 4 2.8 TASK (addition to page 58, Volume 1) The support of RSC IOs (only on systems with SPARC architecture) of TD / openCRYPT-BOX devices is not possible, because there is no connection between RSC IOs and tasks. Instead of this the number of physical accesses to coded files are output. If the monitoring program is used for parallel access volumes (PAV) in Symmetrix systems, the following applies: - Base and alias devices can be selected. - The monitored data refers to the base device and the assigned alias devices (summation, averaging). If a basic device is selected, the data also applies to the assigned alias devices. If a base device gets a new alias device, then the alias device is involved in the measurement. 2.9 VM (addition to page 61, Volume 1) The monitoring program VM gathers additionally datas of VM groups (since VM2000 V8.0A). A Page 5 3 SM2 operation 3.1 Statements for SM2 administrators 3.1.1 ADD-/REMOVE-COSMOS-EVENT (addition to page 81, Volume 1) The operand EVENT-NAME of the statements ADD-COSMOS-EVENT and REMOVE-COSMOS-EVENT respectively is extended with the events RSCS and RSCT. +------------------------------------------------------------------+ | ADD/REMOVE-COSMOS-EVENT | +------------------------------------------------------------------+ | | | EVENT-NAME = ... / *RSCS / *RSCT | | | +------------------------------------------------------------------+ 3.1.2 ADD-ISAM-FILE This statement is used to define an ISAM pool in the Data Space through the pathname of a NKISAM file, which is to be added to the ISAM monitoring program definition. This monitoring program allows you to define up to 16 ISAM pools through the pathname of NKISAM files for monitoring. If this number is exceeded, the statement is rejected and a message is issued. Independently it is allowed to define up to 16 ISAM pools through the poolname for monitoring. +------------------------------------------------------------------+ | ADD-ISAM-FILE | +------------------------------------------------------------------+ | | | FILE-NAME = | | | +------------------------------------------------------------------+ Operands FILE-NAME = Specifies the name of the ISAM pool in the Data Space (= name of the NKISAM file) to be added to the monitoring program definition. The file name must be specified as a fully qualified name. A Page 6 3.1.3 REMOVE-ISAM-FILE This statement is used to remove ISAM pool(s) in the Data Space, which are defined through the pathname of a NKISAM file, from the ISAM monitoring program definition. +------------------------------------------------------------------+ | REMOVE-ISAM-FILE | +------------------------------------------------------------------+ | | | FILE-NAME = *ALL / | | ---- | | | +------------------------------------------------------------------+ Operands FILE-NAME = FILE-NAME = *ALL All ISAM pools in the Data Space, which are defined through the name of a NKISAM file, are to be removed from the monitoring program definition. FILE-NAME = Specifies the name of the ISAM pool in the Data Space (= name of the NKISAM file) to be removed from the monitoring program definition. The file name must be specified fully qualified. A Page 7 3.2 Statements for nonprivileged users 3.2.1 Report (addition to page 184, Volume 1) The statement is extended by the following parameters: Report ID | Guarant. | Report name | abbrev. | -------------------+-------------+------------- ISAM_FILE | | ISAM FILE VM_GROUP | VMG | VM GROUP 3.2.2 SELECT-DEVICE-DISK-PARAMETERS (addition to page 191, Volume 1) The statement is extended by a new sort criterion. +----------------------+---------------------------------------------+ | Operation | Operands | +----------------------+---------------------------------------------+ | SELECT-DEVICE-DISK- | SORT = ... / *RSC | | PARAMETERS | | +----------------------+---------------------------------------------+ 3.2.3 SELECT-PERIODIC-TASK-PARAMETERS (addition to page 192, Volume 1) The statement is extended by a new sort criterion. +--------------------+-----------------------------------------------+ | Operation | Operands | +--------------------+-----------------------------------------------+ | SELECT-PERIODIC- | ... | | TASK-PARAMETERS | / \ | | | | SERVICE-UNITS | | | | | ------------- | | | | | CPU | | | | | IO | | | | | UPG | | | | | PAGING-READ | | | | | ENCRYPTED-FILE-IO | | | | [,SORT = < >] | | | | / \ | | | | | | SERVICE-UNITS | | | | | | | ------------- | | | | | | | CPU | | | | | | (< IO >,...) | | | | | | UPG | | | | | | | PAGING-READ | | | | | | | ENCRYPTED-FILE-IO | | | | | | \ / | | | | \ / | | | | +--------------------+-----------------------------------------------+ A Page 8 4 SM2 screen output 4.1 ACTIVITY Report (addition to page 227, Volume 1) In the ACTIVITY report there are the following changes: - additionally the number of read/write IOs of openCRYPT-BOX devices are output - the meaning of the TD value changes - the OTHER value escapes From space reasons the following figure shows a reduced ACTVITY report. +--------------------------------------------------------------------+ |D016ZE04 SM2 ACTIVITY (VM) CYCLE: 60 S SAMPLES: 50 05-09-07 11:11:11| | | | CPU UTILIZATION % ( 4 LM'S) PCS DATA MEMORY | |+-----+-----+-----+-----+-----++------+-----++------+------+-------+| || TU | TPR | SIH |IDLE |/390 ||SRACT |RDACT|| NPP |WS-ACT|WS-WACT|| |+-----+-----+-----+-----+-----++------+-----++------+------+-------+| ||10.8 |46.3 | 7.8 |34.9 | 0.0 || 90366| 1.0||441343| 14403| 0|| |+-----+-----+-----+-----+-----++------+-----++------+------+-------+| | | | TASKS (CURRENT TASK TYPE) TASKS IN SCHEDULER QUEUES | |+------+------+------+------+-------+ +-------+------+------+------+| ||BATCH |DIALOG| TP | SYS |#-TASKS| | #-ACT |CPU-Q |IO-Q |PAG-Q || |+------+------+------+------+-------+ +-------+------+------+------+| || 88.7| 177.3| 37.0| 203.0| 506.1| | 123.6 | 3.0 | 0.8 | 0.0 || |+------+------+------+------+-------+ +-------+------+------+------+| | | | IO'S PER SEC POSIX DATA | |+------+------+------+------+------+------+------+ +-------+-------+| ||TOTAL | DISK | PAGE | TD |CRYPT | TAPE |PRINT | |SCALL/S|FORK/S || |+------+------+------+------+------+------+------+ +-------+-------+| ||861.2 |688.5 | 0.0 |172.6 |100.0 | 0.0 | 0.0 | | 55.9 | 0.1 || |+------+------+------+------+------+------+------+ +-------+-------+| | | +--------------------------------------------------------------------+ Monitoring information TD Number of IO operations to communication devices per second (family name TD) (since CRYPT V1.2A without the IOs of openCRYPT-BOX devices) CRYPT Number of I/O operations to openCRYPT-BOX devices per second (since CRYPT V1.2A) A Page 9 4.2 DEVICE DISK Report (addition to page 260, Volume 1) In the DEVICE DISK report there are the following changes: - a new indicator for base devices (PAV) - the average number of parallel processed RSC IOs (only on systems with SPARC architecture) - the average number of assigned alias devices (PAV) escapes For parallel access volumes (PAV) in Symmetrix systems, the following applies: - only base devices are output - The monitored data refers to the base device and the assigned alias devices (summation, averaging). If an alias device changes from one base device to another, then the datas of the alias device are not included in the datas of any base device in the actual measurement interval. From space reasons the following figure shows a reduced DEVICE DISK report without SERVICETIME. +--------------------------------------------------------------------+ |D016ZE04 SM2 DEVICE DISK (I) CYCLE: 60 S SAMPLES: 150 ... | | | | MN |VOLUME|V | UTIL | Q |RSC| READ | WRITE | .. | | | | P|IO%|PG%|LGTH| |(IO/S)| (KB/S) |(IO/S)| (KB/S) | | |----+------+--+---+---+----+---+------+--------+------+--------+----| |D300|VVVV.0|D | 46| | 0.5|1.3| 164.3| 329.2| 135.1| 270.2| | |D2BB|2RZV.7|I | | | 0.0|0.0| 9.0| 245.0| 0.0| 0.0| | |D302|XXXX.2|DB| | | 0.0|0.0| 7.3| 29.2| 0.2| 1.2| | |D2FA|VVVV.4|D | 1| | 0.0|2.1| 6.7| 174.0| 0.0| 0.0| | |D13B|2RZV.0|D | | | 0.0|1.0| 4.6| 25.9| 0.3| 0.5| | | | +--------------------------------------------------------------------+ Monitoring information P PAV information Base devices are marked with a 'B'. RSC Average number of parallel processed RSC IOs (only on systems with SPARC architecture) A Page 10 4.3 DEVICE TD Report (addition to page 267, Volume 1) In the DEVICE TD report there are the following changes: - a new indicator for openCRYPT-BOX devices (since CRYPT V1.2A) - additionally the transferred datas are output in KB/S +--------------------------------------------------------------------+ |D016ZE04 SM2 DEVICE TD CYCLE: 60 S 05-09-07 11:11:11| | | | | MN | DEVICE TYPE | READ | WRITE | DATA | | | | | | (IO/S) | (IO/S) | (KB/S) |(BYTES/IO)| | | +------+--------------+---------+---------+----------+----------+ | | | 603A | ZAS-LAN (C) | 1234.2 | 0.0 | 12345.7 | 32563.5 | | | | 603B | ZAS-LAN (C) | 0.0 | 1234.4 | 302.8 | 50.5 | | | | PX | ZAS-LAN | 0.2 | 0.0 | 8.7 | 60.6 | | | | QE | ZAS-BCAM | 0.0 | 0.0 | 2.0 | 70.7 | | | | +--------------------------------------------------------------------+ Monitoring information DEVICE TYPE Short name for the device type openCRYPT-BOX devices are marked with a '(C)' (since CRYPT V1.2A) DATA Transferred data in - number of KB per second - bytes per I/O operation A Page 11 4.4 ISAM FILE Report The ISAM FILE report provides performance data on ISAM pools in the Data Space, which are identified through the pathname of a NKISAM file. Report output The REPORT ISAM_FILE statement is used to request the output of the ISAM FILE report. The ISAM FILE report can only be output if the SM2 administrator has - defined ISAM pools in the Data Space over the name of a NKISAM file using the ADD-ISAM-FILE statement - started ISAM pool monitoring using the START-MEASUREMENT-PROGRAM TYPE=*ISAM statement The privileged user receives values for all measured ISAM pools in the Data Space. The nonprivileged user receives values only on the measured ISAM pools belonging to their user ID. From space reasons the following figure shows a reduced ISAM FILE report. +--------------------------------------------------------------------+ |D016ZE04 SM2 ISAM FILE CYCLE: 10 S 05-09-07 11:11:11| | | | FILENAME | FIX SLOT| INDEX | SIZE | | | OP |HIT%|WAI%|WAI%| OP |HIT%| | |-------------------------+-------+----+----+----+-------+----+------| |:2OS6:$TEST.1234567891234| 150.5 |99.9| 0.0| 0.0| 100.4 | 100| 54000| |-------------------------+-------+----+----+----+-------+----+------| | | +--------------------------------------------------------------------+ Monitoring information FILENAME Name of the ISAM pool in the Data Space (= name of NKISAM file) The further values correspond to those of the ISAM report. The name of the NKISAM file is possibly shortened spent; there is output a '>' as last character. A Page 12 4.5 MEMORY Report (addition to page 281, Volume 1) In the MEMORY report there are the following changes: - additionally datas about Big Pages are output From space reasons the following figure shows a reduced MEMORY report. +--------------------------------------------------------------------+ |D016ZE04 SM2 MEMORY CYCLE: 60 S SAMPLES: 75 05-06-14 16:41:02| | | | MAIN MEMORY FRAMES BIG PAGES | |+---------+---------+---------+---------+------- +-------+-------+| || TOTAL |PAGEABLE |R-ONLY-Q | RD-WR-Q | EMPTY- | TOTAL | USED || |+---------+---------+---------+---------+------- +-------+-------+| || 528385 | 504147 | 63 | 8618 | 25519 | 10000 | 0 || |+---------+---------+---------+---------+------- +-------+-------+| |... | | | +--------------------------------------------------------------------+ Monitoring information BIG PAGES TOTAL Total number of Big Pages (only on systems with SPARC architecture) USED Number of used Big Pages (only on systems with SPARC architecture) A Page 13 4.6 PERIODIC TASK Report (addition to page 292, Volume 1) In the PERIODIC TASK report there are the following changes: - additionally the number of physical accesses to coded files are output From space reasons the following figure shows a reduced PERIODIC TASK report. +--------------------------------------------------------------------+ |D016ZE04 SM2 PERIODIC TASK (S-U) CYCLE: 60 S 05-09-07 11:11:11 | | | | TU + TPR= 17.8 % SIH= 12.0 % IDLE= 70.3 % IO(1/S)= 414.0 | | | | TSN | ... |T|SERV-RATE| CPU% | IO(1/S)| UPG |PAG RD| CRYPT | |-----+----------+-+---------+------+--------+--------+------+-------| |8E74 | |D| 166.1 | 59.2 | 1.7 | 478 | 0.0 | 80.0| |8D7R | |D| 64.9 | 0.1 | 1.0 | 258 | 0.0 | 20.0| | | +--------------------------------------------------------------------+ Monitoring information CRYPT Number of physical accesses to coded files per second A Page 14 4.7 SHARED PUBSET Report (addition to page 308, Volume 1) In the SHARED PUBSET report there are the following changes: - additionally the average number of parallel processed RSC IOs is output (only on systems with SPARC architecture) - the average number of assigned alias devices (PAV) escapes From space reasons the following figure shows a reduced SHARED PUBSET report. +--------------------------------------------------------------------+ |D016ZE04 SM2 SHARED PUBSET CYCLE: 150 S SAMPLES: 7 05-06-28 .| | | | MN !VOLUME! Q !RSC! READ ! WRITE ! .. | | ! !LGTH ! !(IO/S) ! (KB/S) !(IO/S) ! (KB/S) ! | | ----+------+-----+---+-------+---------+-------+---------+------ | | D258|CVS1.4! 1.5! ! 604.5! 12091.5! 3022.6! 120915.1! | | D0FA|CVS2.0! 0.6! ! 302.2! 6045.8! 1511.3! 60457.6! | | D2C3|2RZV.5! 0.0!3.0! 151.1! 3022.9! 755.6! 30228.8! | | D262|CVS6.4! 3.0! ! 151.1! 3022.9! 755.6! 30228.8! | | D129|GVS5.1! 0.0! ! 151.1! 3022.9! 755.6! 30228.8! | | | +--------------------------------------------------------------------+ Monitoring information RSC Average number of parallel processed RSC IOs (only on systems with SPARC architecture) A Page 15 4.8 VM Report (addition to page 333, Volume 1) In the VM report there are the following changes: - the name of the VM group of the VM is output - a new indicator shows, if the idle time of the VM is contained into MEAS From space reasons the following figure shows a reduced VM report. +--------------------------------------------------------------------+ |D016ZE04 SM2 VM CYCLE: 150 S 05-09-07 09:33:01| | | |HYPERVISOR: IDLE: 9.8% ACTIVE: 9.8% # REAL CPUS: 16| |-----+----------+----------+----------+-+--------+------------+-----| | IND ! NAME ! VM-GROUP ! CPU-POOL !I! MEMORY ! CPU ! # | | ! ! ! ! ! (MB) ! ! CPUS| |-----+----------+----------+----------+-+--------+------------+-----| | 1 ! VM1 ! ! *STDPOOL !Y! 512 ! ! 2 | | 2 ! VM2 ! GROUP001 ! CPUPOOL1 !Y! 512 ! ! 2 | | 2 ! VM3 ! GROUP002 ! CPUPOOL2 !Y! 512 ! ! 2 | | | +--------------------------------------------------------------------+ Monitoring information IND Index of the VM VM-GROUP Name of the VM group the VM belongs to (since VM2000 V8.0A) I If a VM runs in the scheduling mode Dedicated CPUs (DC) and uses VM-ACTIVE-IDLE=*AT-DEDICATED-CPUs (see SHOW-VM-RESOURCES INF=*CPU), then the monitoring value MEAS contains also the hypervisor idle share of the CPUs available to the VM. This is indicated with a 'Y'. The VM active share then is only visible in the guest systems CPU report. (since VM2000 V8.0A) A Page 16 4.9 VM GROUP Report This report provides monitored data for VM groups. It can only be output if at least VM2000 V8.0A is in use. Report output The REPORT VM_GROUP statement is used to request the output of the VM GROUP report. The report can only be output if the SM2 administrator has activated the monitoring process using the statement START-MEASUREMENT-PROGRAM TYPE=*VM. The values for all VM groups are only output if SM2 is running on the monitor machine VM1. If this is not the case, only the values for the VM group which is assigned to the VM on which SM2 is running are output. Overflow screens may also be requested for this report. +--------------------------------------------------------------------+ |D016ZE04 SM2 VM GROUP CYCLE: 60 S 05-09-07 11:11:11| | | | +----------+----------+-------------------+ | | ! VM-GROUP ! CPU-POOL ! CPU (%) ! | | ! ! ! MAX PLAN MEAS ! | | +----------+----------+-----+-----+-------+ | | ! GROUP001 ! CPUPOOL1 ! 100 ! 20 ! 72.1 ! | | ! GROUP002 ! CPUPOOL2 ! 100 ! 20 ! 72.1 ! | | | +--------------------------------------------------------------------+ Monitoring information VM-GROUP Name of the VM group CPU POOL Name of the CPU pool the VM group belongs to CPU (%) MAX Maximum percentage of the VM group on the CPU performance PLAN Planned percentage of the VM group on the CPU performance MEAS Percentage of TOTAL TIME that can be accounted for by the CPU time of the VM TOTAL TIME is the whole available CPU time during the monitoring period. The following applies: TOTAL TIME = CYCLE * # REAL CPUS with CYCLE Duration of the monitoring interval # REAL CPUS Number of real CPUs (also extra CPUs) that have the status 'attached' A Page 17 5 SM2 program interfaces 5.1 The SM2GDAT macro (Extension to the macro on page 185, Volume 2) The list of symbolic constants for specifying the SM2 data buffer (on page 185f) is to be extended to include the new symbolic constants: SM2GDAT_BUFFER_ISAM_FILE requests the ISAM-FILE data buffer SM2GDAT_BUFFER_VM_GROUP requests the VM-GROUP data buffer 5.1.1 Structure of the output area (Extension to the macro on page 190, Volume 2) The table on the data buffer and structures (on pages 190-192) has been extended to include the following entries: Data |Typ| Symbolic constants | Structures buffer | | for selecting the | | | data buffer | -----------+---+----------------------+----------------------------- ISAM-FILE | 3 | SM2GDAT_BUFFER_ | SM2GDAT_isam_file_single_mdl | | ISAM_FILE | SM2GDAT_isam_file_multiple_mdl -----------+---+----------------------+------------------------------- VM-GROUP | 3 | SM2GDAT_BUFFER_ | SM2GDAT_vm_group_single_mdl | | VM_GROUP | SM2GDAT_vm_group_multiple_mdl A Page 18 5.2 Structures of the SM2GDAT macro (Extension to the macro on page 210, Volume 2) 5.2.1 Structure of the ISAM-FILE data buffer The ISAM-FILE data buffer supplies data on access to ISAM pools in the Data Space, which are identified through the the pathname of a NKISAM file. The data area of the ISAM-FILE data buffer comprises an area of fixed length and a number of repeat groups. Data buffer type: 3 Fixed-length data area The fixed-length data area contains only the number of repeat groups to follow. Descriptive structure: SM2GDAT_isam_file_single_mdl Displacement from the beginning of the buffer header: 'fixed_part_dsp' from the buffer header Repeat groups A repeat group is written for each ISAM pool monitored. The repeat group provides on the accesses and the pages used for buffering. Descriptive structure: SM2GDAT_isam_file_multiple_mdl Displacement of the first repeat group from the beginning of the buffer header: 'first_group_dsp' from the buffer header Length of a repeat group: 'length_group' from the buffer header Number of repeat groups: 'used_groups' from SM2GDAT_isam_file_single_mdl Note Corresponding screen report in the online component: ISAM_FILE Monitoring program: ISAM A Page 19 5.2.2 Structure of the VM-GROUP data buffer The VM-GROUP data buffer supplies data on the utilization of VM groups. The data area of the VM-GROUP data buffer comprises an area of fixed length and a number of repeat groups. Data buffer type: 3 Fixed-length data area The data area of fixed length supplies the number of real CPUs that have the 'attached' status. The number of supplied repeat groups to follow is contained in 'used_groups'. Descriptive structure: SM2GDAT_vm_group_single_mdl Displacement from the beginning of the buffer header: 'fixed_part_dsp' from the buffer header Repeat groups A repeat group exists for each VM group. The repeat group provides information on the CPU time utilized, the planned relative share and the maximum share of CPU time. Values for all VM groups are output only on the VM1 monitor machine. Otherwise, only the values of your own VM group are output. Descriptive structure: SM2GDAT_vm_group_multiple_mdl Displacement of the first repeat group from the beginning of the buffer header: 'first_group_dsp' from the buffer header Length of a repeat group: 'length_group' from the buffer header Number of repeat groups: 'used_groups' from SM2GDAT_vm_group_single_mdl Note Corresponding screen report in the online component: VM GROUP Monitoring program: VM A Page 20 5.2.3 Structure of the TIME-IO data buffer (Extension to the macro on page 245, Volume 2) Repeat groups On systems with SPARC architecture and starting from BCAM V18.0 and/or CRYPT V1.2 the following applies: Only in the first repeat group the element "other_io" contains the operations on devices of the family type TD (including openCRYPT-BOX devices) A Page 21 6 SM2U1 6.1 SELECT-MEASUREMENT-GROUPS (Addition to page 20, Volume 2) The statement has been extended to include the new SM2R1 report group ISAM-FILE. +------------------------------------------------------------------+ | SELECT-MESUREMENT-GROUPS | +------------------------------------------------------------------+ | | | SELECTION =... / *ISAM-FILE | | | +------------------------------------------------------------------+ Operand description SELECTION = *ISAM-FILE All data records required by the SM2R1 are transferred if REPORT-LIST = *ISAM-FILE is specified in the PRINT-REPORTS statement. SELECTION = *ALL (EXCEPT = ...) has also been extended by ISAM-FILE. A Page 22 7 SM2R1 7.1 PRINT-REPORTS (Addition to page 76, Volume 2) The statement has been extended to include the new report group ISAM-FILE and some other new reports. +------------------------------------------------------------------+ | PRINT-REPORTS | +------------------------------------------------------------------+ | ... | | ,REPORT-LIST = ... / *DISK(...) / *ISAM-FILE(...) / | | *MEMORY(...) / *VM2000(...) | | | | *DISK(...) | | : | | ,REPORT-NUMBER = ... / list-poss(18): | | | | | | ,REPORT-NUMBER = *ALL / *STD / | | ---- | | list-poss(4): | | | | ,CONDITIONED-REPORTS = *YES / *NO | | --- | | | | *MEMORY(...) | | : | | ,REPORT-NUMBER = ... / list-poss(5): | | = V7.0A The restriction applies only to devices, which are operated with indirect IO mode. - VM2000 Version < V7.0A The restriction applies to all devices, which are shared by different VMs on one system. SM2 cannot determine this status; the warning is therefore output for all devices. The restriction applies also to devices, which are not attached. Only the device queue and the remaining service time are monitored. A Page 29 10 Glossary (additions to the glossary page 473ff, Volume 1) Big Pages Big Pages with a size of 4 MB are supported since BS2000/OSD-BC V6.0 on systems with Sparc architecture (since SX150). Et al. they are used for JIT compilations for a better performance. RSC-IOs By RSC IOs (disk I/O request with "Remote System Call" on systems with Sparc architecture) one understands the execution of a disk I/O request for an emulated disk with a high-peformance interface between BS2000 and X2000. With this interface it is possible to execute up to 3 I/Os parallel for one disk.