The declarations of the structures of the SM2GDAT macro are in SM2GDAT.H, and the definitions of the symbolic constants for evaluating the return codes are in SM2RC.H.
In addition to the “SM2GDAT_get_data_mdl” structure (and its substructures) used in the macro call, there are a number of structures for describing the data buffers of the output area.
All the structures of the SM2GDAT macro are described below. The data buffers are described in alphabetical order.
The “SM2GDAT_get_data_mdl” structure
The “SM2GDAT_get_data_mdl” structure is passed to the SM2GDAT macro as a parameter in the macro call.
The macro sets parameters internally in “hdr”, and it also stores its return codes there. The evaluation of the return codes is described in section "Evaluating the return codes".
The macro supplies the “selected1”, “selected2”, “length_buffer”, “buffer_ptr” and “host_name” elements internally with the values passed by the caller in the “buffer_flags”, “length_buffer”, “buffer_ptr” or “host_name” parameters.
After an error-free call and in the case of the return code SM2GDAT_buffer_too_short, the “buffer_length” element contains the actually used or required length of the output area.
Structure of the global header
The global header is located at the beginning of the output area and is described by the “SM2GDAT_global_header_mdl” structure.
For each data buffer, it contains a pointer to the beginning of the data buffer. Only the pointers for those data buffers requested by the caller are supplied. All other pointers are filled with null.
Structure of the BUFFER HEADER
Each data buffer begins with the BUFFER HEADER, which is described by the“SM2GDAT_buffer_header_mdl” structure. The BUFFER HEADER contains administration information that enables the actual monitoring data (in the data area) of the respective data buffer to be accessed. The administration information is evaluated differently, depending on the type of data buffer (see the description of the relevant data buffer).
The “valid” bit indicates whether valid data exists for the data buffer. It must always be queried first. A “valid” bit that is not set means both that the remaining administration elements in the BUFFER HEADER and the monitoring data in the data area may be invalid.
The possible causes of an unset “valid” bit are:
The monitoring program is not activated.
SM2 cannot create any monitoring data because different monitoring objects occurred in two successive monitoring cycles.
SM2 cannot create any monitoring data because SM2 did not receive any basic data from the system.
SM2 has an error.
The “size” element specifies the length of the data buffer (including that of the BUFFER HEADER).
Structure of the ACF data buffer
The ACF data buffer supplies data for activation control of the PRIOR task administration facility. The data provides information for the internal decision concerning activation.
The data area of the ACF data buffer comprises an area of fixed length.
Data buffer type: 1
Fixed-length data area
The fixed-length data area contains monitoring data of the PRIOR task scheduler (number of task activations, deactivations, preemptions, etc.). In addition, 3 counters for each of the resources CPU, MEMORY and PAGING provide information on how often the utilization of these resources was low, medium or high.
Descriptive structure: | struct SM2GDAT_ACF_single_mdl |
Displacement from the beginning of the BUFFER HEADER: | “fixed_part_dsp” from the BUFFER HEADER |
Monitoring program: –
Structure of the BASIC data buffer
The BASIC data buffer contains basic information on SM2 monitoring.
The data area of the BASIC data buffer comprises an area of fixed length.
Data buffer type: 1
Fixed-length data area
The fixed-length data area supplies basic data for the most recently completed monitoring cycle (elapsed time, data, time, number of samples, etc.). The number of logical machines set, the number of data records not written to the output file (and thus lost), a VM2000 indicator and the host name are also made available.
Descriptive structure: | struct SM2GDAT_basic_single_mdl |
Displacement from the beginning of the BUFFER HEADER: | “fixed_part_dsp” from the BUFFER HEADER |
Monitoring program: –
Structure of the BCAM-CONNECTION data buffer
The BCAM-CONNECTION data buffer supplies data for defined connection sets and on the size of the resident memory for data transfer.
The data area of the BCAM-CONNECTION 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 the number of subsequent repeat groups and the data on the size of the resident memory for data transfer.
Descriptive structure: | SM2GDAT_bcam_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 every monitored connection set. The repeat group contains
the name of the connection set,
the definition of the connection set (the structures SM2GDAT_bcam_description_mdl, SM2GDAT_bcam_nea_mdl, SM2GDAT_bcam_port_number_mdl),
the number of active connections, and
the monitored data (the structure SM2GDAT_bcam_measurement_mdl) for the connection set.
The “description_data_dsp” element contains the displacement from the beginning of the repeat group to the definition of the connection set. Among other things, the definition of the connection set contains a list of application names or port numbers which can be accessed via length, number and displacement using the familiar logic. The access elements are “length_description”, “number_description” and “first_description_dsp”. The displacement is measured from the start of the definition of the connection set.
The connection set data comprises only those connections that were active both at observation time and during the immediately preceding monitoring cycle.
Descriptive structure: | SM2GDAT_bcam_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: | “number_groups” from the BUFFER HEADER |
Monitoring program: BCAM-CONNECTION
Structure of the CATEGORY data buffer
The CATEGORY data buffer contains data for task administration and the working set and data of the PCS system. It supplies monitoring data for each category.
The data area of the CATEGORY data buffer consists of 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 monitoring data not assigned to any specific category.
The mean number of tasks is made available for the SYS, DIALOG, BATCH and TP task types. The sum of the values provides the mean number of all tasks in the system.
The “pcs_active” indicator reveals whether data of the PCS subsystem exist. In the case of PCS reconfiguration (“pcs_reconfigurations” not equal to 0), no PCS data can be supplied.
Most of the values of the CATEGORY data buffer are obtained by sampling. You should bear in mind that the accuracy of the data varies with the number of samples taken.
Descriptive structure: | SM2GDAT_category_single_mdl |
Displacement from the beginning of the BUFFER HEADER: | “fixed_part_dsp” from the BUFFER HEADER |
Repeat groups
The first repeat group contains the sum values of all categories. SUM is output as “name”. “type” and “number” are undefined. Each subsequent repeat group contains the monitoring data for a single category.
Each repeat group provides information on the number of tasks in the different queues and on the working set of different task groups.
The data of the PCS subsystem is only valid when the “pcs_data” indicator is set in the SM2GDAT_category_single_mdl structure.
Descriptive structures: | SM2GDAT_category_multiple_mdl |
Displacement of the first repeat group from the beginning of the BUFFER HEADER: | “first_group_dsp” from the BUFFER HEADER |
Length of the repeat group: | “length_group” from the BUFFER HEADER |
Number of repeat groups: | “used_groups” from SM2GDAT_category_single_mdl |
Monitoring program: –
Structure of the CHANNEL-IO data buffer
The CHANNEL-IO data buffer contains data on I/O channel data transmission.
Fixed-length data area.
The number of repeat groups that are subsequently used is located in “number_used_groups”.
Descriptive structure: | SM2GDAT_hsms_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 monitored channel. The repeat group provides information about the number of I/Os or the volume of the transferred data in the case of PAM block or byte transfer. The I/Os without data transfer are also output.
Descriptive structure: | SM2GDAT_chio_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: | “number_groups” from the BUFFER HEADER |
Monitoring program: CHANNEL-IO
Structure of the CMS data buffer
The CMS data buffer supplies data on the performance of the catalog management system.
The data area of the CMS 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 the number of CMS reconfigurations. In the case of a reconfiguration, no data can be supplied to the repeat groups.
Descriptive structure: | SM2GDAT_cms_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 imported public volume set. In addition, a repeat group is written for the entire set of all private disks. Data is supplied for queues, accesses and response times.
The data for the queues is obtained by sampling. The number of samples is contained in “samples”. You should bear in mind that the accuracy of the data varies with the number of samples taken.
Descriptive structure: | SM2GDAT_cms_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: | “number_groups” from the BUFFER HEADER |
Monitoring program: CMS
Structure of the DAB data buffer
The DAB data buffer supplies data on the activity of the disk access buffer function.
The data area of the DAB data buffer comprises an area of fixed length and two types of repeat group, which are arranged in two chains.
Data buffer type: 4
Fixed-length data area
For each of the two chains of repeat groups, the fixed-length data area contains the length of a repeat group, the number of repeat groups and the displacement from the first repeat group. The displacements are measured from the beginning of the “SM2GDAT_dab_single_mdl” structure.
The “reconfigurations” element provides information on the possible changes to the configuration of the DAB buffers. In this case, the repeat groups contain only information on the new configuration of the DAB buffers but no monitoring data on the accesses.
Descriptive structure: | SM2GDAT_dab_single_mdl |
Displacement from the beginning of the BUFFER HEADER: | “fixed_part_dsp” from the BUFFER HEADER |
The BUFFER AREA repeat group
A repeat group exists for each DAB cache area. This contains the name and size of the DAB cache area as well as various attributes. The repeat groups come one after the other in the data buffer.
Descriptive structure: | SM2GDAT_dab_buffer_area_mdl |
Displacement of the first repeat group from the beginning of the structure SM2GDAT_dab_single_mdl: | “first_buffer_area_group_dsp” from SM2GDAT_dab_single_mdl |
Length of a repeat group: | “length_buffer_area_group” from SM2GDAT_dab_single_mdl |
Number of repeat groups: | “number_buffer_area_groups” from SM2GDAT_dab_single_mdl |
The PARTIAL AREA repeat group
The name of the repeat group is PARTIAL AREA for reasons of compatibility, although DAB no longer supports subareas. All elements with a possible double meaning (subarea/file) only have the meaning for file.
A repeat group exists for each file of each DAB buffer. The repeat groups come one after the other in the data buffer.
The assignment of the PARTIAL AREA repeat groups to the DAB cache areas is as follows:
If the “buffer_index” element of the PARTIAL AREA repeat group has the value n, it belongs to the DAB buffer of the nth repeat group in the chain of BUFFER AREA repeat groups.
A PARTIAL AREA repeat group contains administration information and monitoring data on the accesses (“SM2GDAT_cache_transfers_mdl” structure). The “state” element reveals whether the file was used in the monitoring cycle.
Descriptive structures: | SM2GDAT_dab_partial_area_mdl |
Displacement of the first repeat group from the beginning of the structure SM2GDAT_dab_single_mdl: | “first_partial_area_group_dsp” from SM2GDAT_dab_single_mdl |
Length of a repeat group: | “length_partial_area_group” from SM2GDAT_dab_single_mdl |
Number of repeat groups: | “number_partial_area_groups” from SM2GDAT_dab_single_mdl |
Monitoring program: DAB
Structure of the DISK-FILE data buffer
For the selected disk devices, the DISK-FILE data buffer contains an overview of the files which have triggered physical I/Os.
Fixed-length data area.
The number of repeat groups that are subsequently used is located in “number_used_groups”.
Descriptive structure: | SM2GDAT_disk_file_single_mdl |
Displacement from the beginning of the BUFFER HEADER: | “fixed_part_dsp” from the BUFFER HEADER |
Repeat groups
A maximum of 300 repeat groups are created for each monitored disk device. Each repeat group contains the mnemonic of the disk device, the VSN and the file name together with the number of physical I/Os for reading and writing. If multiple disk devices are monitored then the repeat groups are always collated for each individual device on output, i.e. if there are two devices, then all the repeat groups for the first device are output first followed by all the repeat groups for the second device.
For each device, a repeat group with the filename “*OVERRUNS” is always output first. These group gathers together the I/Os for those files for which there was no free entry in the SM2 table.
Descriptive structure: | SM2GDAT_disk_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: | “number_groups” from SM2GDAT_disk_file_single |
Monitoring program: DISK-FILE
Structure of the DLM data buffer
The DLM data buffer provides general information on Distributed Lock Managers events.
The data area of the DLM data buffer comprises an area of fixed length.
Data buffer type: 1
Fixed-length data area
The fixed-length data area contains the number of different lock requests from TU, TPR and NSM in the system.
Descriptive structure: | SM2GDAT_dlm_single_mdl |
Displacement from the beginning of the BUFFER HEADER: | “fixed_part_dsp” from the BUFFER HEADER |
Monitoring program: DLM
Structure of the FILE data buffer
The FILE data buffer contains data on file accesses.
The data area of the 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_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 file monitored. The repeat group provides information on the number of read, write, wait and check accesses as well as the average duration of I/Os.
Descriptive structure: | SM2GDAT_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_file_single_mdl |
Monitoring program: FILE
Structure of the HSMS data buffer
The HSMS data buffer provides information about the migration of files to the background level and their retrieval into the processing level. The data area of the HSMS data buffer comprises an area of fixed length.
Data buffer type: 1
Fixed length data area
Descriptive structure: | SM2GDAT_hsms_single_mdl |
Displacement from the beginning of the BUFFER HEADER: | “fixed_part_dsp” from the BUFFER HEADER |
Monitoring program: HSMS
Structure of the ISAM data buffer
The ISAM data buffer supplies data on access to ISAM pools.
The data area of the ISAM 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_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 information on the accesses and the pages used for buffering.
Descriptive structure: | SM2GDAT_isam_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_single_mdl |
Monitoring program: ISAM
Structure of the ISAM-FILE data buffer
The ISAM-FILE data buffer supplies data on access to NK-ISAM files in a global ISAM pool in the Data Space.
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 file 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 |
Monitoring program: ISAM
Structure of the MEMORY data buffer
The MEMORY data buffer supplies data on the utilization of main memory and the virtual address space.
The data area of the MEMORY data buffer comprises an area of fixed length.
Data buffer type: 1
Fixed-length data area
The fixed-length data area provides information on the size and utilization of main memory and on paging.
Descriptive structure: | struct SM2GDAT_memory_single_mdl |
Displacement from the beginning of the BUFFER HEADER: | “fixed_part_dsp” from the BUFFER HEADER |
Monitoring program: –
Structure of the MSCF data buffer
The MSCF data buffer provides general information on the MSCF subsystem.
The data area of the MSCF data buffer comprises an area of fixed length.
Data buffer type: 1
Fixed-length data area
The fixed-length data area contains the number of server tasks and limit values at which the MSCF subsystem sets the FLOW state (see the “HIPLEX MSCF” manual [8]). The number of executed and rejected send jobs is also shown.
For send jobs of type REQUEST WITH REPLY, the average total times of the job and the wait times for the first reply from the receiving host are displayed. The average time the system spent in the FLOW state is also shown, whereby only the transitions from FLOW to NO FLOW are taken into account.
The latter data is event-driven and is described by the structure SM2GDAT_mscf_time_count_mdl, where “average_time” already contains an average time. “count” specifies how often the event has occurred.
Descriptive structures: | SM2GDAT_mscf_single_mdl |
Displacement from the beginning of the BUFFER HEADER: | “fixed_part_dsp” from the BUFFER HEADER |
Monitoring program: MSCF
Structure of the NSM data buffer
The NSM data buffer contains information about the token and locks in the host network.
The data area of the NSM data buffer comprises an area of fixed length.
Data buffer type: 1
Fixed-length data area
The fixed-length data area contains the number of hosts in the host network and information about the token and locks.
Descriptive structures: | SM2GDAT_nsm_single_mdl |
Displacement from the beginning of the BUFFER HEADER: | “fixed_part_dsp” from the BUFFER HEADER |
Monitoring program: NSM
Structure of the OPENFT data buffer
The OPENFT data buffer contains information about openFT instances.
The data area of the OPENFT data buffer comprises only of repeat groups.
Data buffer type: 2
Repeat groups
A repeat group exists for each monitored openFT instance.
Descriptive structure: | SM2GDAT_openft_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: | „number_groups“ from the BUFFER HEADER |
Corresponding screen report in the online component: OPENFT
Monitoring program: OPENFT
Structure of the PERIODIC-TASK data buffer
The PERIODIC-TASK data buffer supplies utilization data for all tasks.
The data area of the PERIODIC-TASK 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 the number of supplied repeat groups to follow (used_groups). In addition, the number of existing repeat groups is also supplied here (number_groups). This value is, however, not required for analyzing the data buffer and is used only for internal purposes.
Descriptive structure: | SM2GDAT_pertask_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 task. The repeat group provides information on service units, CPU time, I/Os, UPG (used page count) and PAGE READs. In addition, it is indicated whether the data of this task is written to the output file. In this case, the “task_in_file” bit is set.
The caller without the SWMONADM privilege receives only the data of tasks of his or her own ID.
Descriptive structure: | SM2GDAT_pertask_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_pertask_single_mdl |
Monitoring program: PERIODIC-TASK
Structure of the POSIX data buffer
The POSIX data buffer supplies data on the use of various functions of the POSIX subsystem.
The data area of the POSIX data buffer comprises an area of fixed length.
Data buffer type: 1
Fixed-length data area
The monitored data is supplied in dual form: as a absolute count for the interval and as a count per second for the interval. At high load peaks, the absolute counts can overflow and thus supply incorrect values. It is advisable to work with the time-related data.
The supplied data corresponds to that of the sar command in UNIX.
Descriptive structure: | struct SM2GDAT_posix_single_mdl |
Displacement from the beginning of the BUFFER HEADER: | “fixed_part_dsp” from the BUFFER HEADER |
Monitoring program: POSIX
Structure of the PUBSET data buffer
The PUBSET data buffer supplies data on the utilization of imported pubsets. Data for SF pubsets and volume sets is supplied.
The data area of the PUBSET 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 the following repeat groups
Descriptive structure: | SM2GDAT_pubset_single_mdl |
Displacement from the beginning of the BUFFER HEADER: | “fixed_part_dsp” from BUFFER HEADER |
Repeat groups
For each SF pubset and volume set a repeat group exists with
information on the pubset
CATID, name of the SM pubset in the case of volume sets, saturation levelmonitored data
capacity and utilized storage area of the pubset
Descriptive structure: | SM2GDAT_pubset_multiple_mdl |
Displacement of the first repeat group from the beginning of the BUFFER HEADER: | “first_group_dsp” from BUFFER HEADER |
Length of a repeat group: | “length_group” from BUFFER HEADER |
Number of repeat groups: | “used_groups” from SM2GDAT_pubset_single_mdl |
Monitoring program: PUBSET
Structure of the RESPONSETIME data buffer
The RESPONSETIME data buffer supplies data on response, think, transaction and message wait times. The monitored data is supplied bucket-specific and/or category-specific for defined connection sets.
The data area of the RESPONSETIME data buffer comprises an area of fixed length and three types of repeat group, which are arranged in three chains.
Data buffer type: 4
Fixed-length data area
The fixed-length data area contains for each of the three chains of repeat groups the length of a repeat group, the number of repeat groups and the displacement from the first repeat group.
The number of buckets and the data for each bucket are output for the different response time definitions.
The “connection” element (“SM2GDAT_rtime_connection_mdl” structure type) contains the defined connection groups of which the connection sets are composed.
The “connection_set” element (“SM2GDAT_rtime_connectionset_mdl” structure type) contains the definition of the connection sets, particularly how the connection sets are composed of the connection groups. A connection set consists of one or more (up to five) connection groups. The connection set can be defined either positively (i.e. all the groups specified in this connection set are monitored) or negatively (i.e. all groups are monitored except those specified in the connection set).
Each bit of the “connection_set.define_set.connection.selection” element corresponds to a connection group of the “connection” element: a set bit means that the connection group belongs to the connection set. The “connection_set.indication.indicate.positive” bit specifies whether the connection set is defined positively or negatively.
Descriptive structures: | SM2GDAT_rtime_single_mdl |
Displacement from the beginning of the BUFFER HEADER: | “fixed_part_dsp” from the BUFFER HEADER |
The CATEGORY LIST repeat group
CATEGORY LIST repeat groups are only written when the response time data is collected category-specifically. A repeat group exists for each category monitored. Each repeat group contains the name of the category monitored. The repeat groups come one after the other in the data buffer. No repeat group is written for the SUM category.
Descriptive structure: | SM2GDAT_rtime_category_list_mdl |
Displacement of the first repeat group from the beginning of the structure SM2GDAT_rtime_single_mdl: | “first_category_name_group_dsp” from SM2GDAT_rtime_single_mdl |
Length of a repeat group: | “length_category_name_group” from SM2GDAT_rtime_single_mdl |
Number of repeat groups: | “number_category_name_groups” from SM2GDAT_rtime_single_mdl |
The BUCKET repeat group
BUCKET repeat groups are only written when the response time data is collected bucket-specifically. A repeat group exists for each connection set. The repeat groups come one after the other in the data buffer and are assigned to the connection sets as follows: the nth repeat group contains the data for the connection set that is in the nth position in the “connection_set” element of the “SM2GDAT_rtime_single_mdl” structure.
A repeat group provides information on how many interactions have occurred in the individual areas (buckets). The number and limits of the buckets are described in the “SM2GDAT_rtime_single_mdl” structure.
In addition, the time sums up to the largest bucket and the overflow values are output.
Descriptive structure: | SM2GDAT_rtime_bucket_mdl |
Displacement of the first repeat group from the beginning of the structure SM2GDAT_rtime_single_mdl: | “first_bucket_group_dsp” from SM2GDAT_rtime_single_mdl |
Length of a repeat group: | “length_bucket_group” from SM2GDAT_rtime_single_mdl |
Number of repeat groups: | “number_bucket_groups” from SM2GDAT_rtime_single_mdl |
The CATEGORY repeat group
CATEGORY repeat groups are written only when the response time data is collected category-specifically. A chain of CATEGORY repeat groups is written for each category (including the “SUM” category). The chains come one after the other in the data buffer. Each chain supplies the category-specific data for all connection sets of a particular category. The chain of the SUM category comes at the end.
The chains with CATEGORY repeat groups are assigned to the categories as follows: the nth chain contains the date of the category in the nth position in the chain of the CATEGORY LIST repeat groups.
In a chain with CATEGORY repeat groups, the individual repeat groups are assigned to the connection sets as follows: the nth repeat group contains the data for the connection set in the nth position in the “connection_set” of the “SM2GDAT_rtime_single_mdl” structure.
A CATEGORY repeat group provides information on time sums and the number of interactions with and without overflow values.
Descriptive structure: | SM2GDAT_rtime_category_mdl |
Displacement of the first repeat group from the beginning of the structure SM2GDAT_rtime_single_mdl: | “first_category_group_dsp” from SM2GDAT_rtime_single_mdl |
Length of a repeat group: | “length_category_group” from SM2GDAT_rtime_single_mdl |
Number of repeat groups: | “number_category_groups” from SM2GDAT_rtime_single_mdl |
Monitoring program: RESPONSETIME
Structure of the SCHANNEL data buffer
The SCHANNEL data buffer contains data of input/output channels . It supplies monitoring data for each channel.
The data area of the SCHANNEL data buffer consists only of repeat groups.
Data buffer type: 2
Repeat groups
A repeat group is written for each channel.
The repeat group provides information on whether the IOPT function is active. If required, the channel utilization is recorded by tasks of the various priority classes. For information on IOPT, see the IORM utility in the “Utility Routines” manual [1]. The elements "channel_busy_cpu_busy" and "channel_busy_cpu_idle" are not supplied.
Descriptive structure: | SM2GDAT_schannel_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: | “number_groups” from the BUFFER HEADER |
Monitoring program: –
Structure of the SDEVICE data buffer
The SDEVICE data buffer supplies data about input/output operations on peripheral devices. Also the monitored data for communication devices are delivered. There are only ever read or write accesses for communication devices.
The data area of the SDEVICE data buffer consists only of repeat groups.
Data buffer type: 2
Repeat groups
A repeat group is written for each device. The repeat group provides information on how often the device was active on account of DMS or paging input/output operations and on the mean queue length.
This monitoring data is obtained by sampling. The number of samples is contained in “samples” in the “SM2GDAT_basic_single_mdl” structure (BASIC data buffer). You should note that the accuracy of the data varies with the number of samples.
In addition, the number of I/Os and the volume of data transferred are output.
In addition, the repeat group provides information on whether the IOPT funciton is active (see the IORM utility in the “Utility Routines” manual [1]). If required, the channel utilization is recorded by tasks of the various priority classes.
Descriptive structure: | SM2GDAT_sdevice_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: | “number_groups” from the BUFFER HEADER |
When parallel access volumes (PAVs) on /390 servers are used, the data of the base and alias devices is output. The data of base devices relates to the base device and the assigned alias devices (summation or averaging of the monitored data). An exception are the elements "busy_dms" and "busy_paging", which only contain data for the base device without taking alias devices into account.
On x86 servers the elements “busy_dms” and “busy_paging” are calculated:
„busy_dms“ = „avg_number_running_ios“ / „max_number_parallel_ios“
Corresponding screen report in the online component: DEVICE DISK, DEVICE TAPE, DEVICE TD
Monitoring program: SAMPLING-DEVICE
Structure of the SESAM-SQL data buffer
The SESAM-SQL data buffer supplies data on SESAM/SQL data base systems.
The data area of the SESAM-SQL 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 the number of the following repeat groups
Descriptive structure: | SM2GDAT_sesam_sql_single_mdl |
Displacement from the beginning of the BUFFER HEADER: | “fixed_part_dsp” from BUFFER HEADER |
Repeat groups
A repeat group is written for each monitored database system.
All monitored data with the unit “Number” applies for the monitoring cycle specified in “elapsed_time”. Because of the asynchronous data collection (see section "PrivilegedSM2 monitoring programs"), the “elapsed_time” can differ from the variable of the same name in the BASIC data buffer.
Descriptive structure: | SM2GDAT_sesam_sql_multiple_mdl |
Displacement of the first repeat group from the beginning of the BUFFER HEADER: | “first_group_dsp” from BUFFER HEADER |
Length of a repeat group: | “length_group” from BUFFER HEADER |
Number of repeat groups: | “used_groups” from SM2GDAT_sesam_sql_single_mdl |
Monitoring program: SESAM-SQL
Structure of the SVC data buffer
The SVC data buffer provides information on the number of SVC calls.
The data area of the SVC data buffer comprises only repeat groups.
Data buffer type: 2
Repeat groups
A repeat group exists for each SVC.
The number of SVC calls is collected separately for TU and TPR calls.
Descriptive structure: | SM2GDAT_svc_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: | “number_groups” from the BUFFER HEADER |
Monitoring program: SVC
Structure of the SYSTEM data buffer
For each category, the SYSTEM data buffer supplies information on queues and DMS and paging input/output operations.
The data area of the SYSTEM 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 the number of devices monitored and their names. In the case of the *ALL, *DISK and *TAPE monitoring program definitions, the real number of devices cannot be specified: the “number_used_devices” element contains a one, and the first four characters of the relevant name appear for the first device name.
The number of PAGE WRITEs and the associated mean service times are also output. This data cannot be assigned to a category, which is why it is found here. It applies only to the devices included in monitoring.
The number of supplied repeat groups to follow is contained in “used_groups”.
Descriptive structure: | SM2GDAT_system_single_mdl |
Displacement from the | “fixed_part_dsp” from the BUFFER HEADER |
Repeat groups
The first repeat group contains the sum values of all categories. SUM is output as “category_name”. The “category_number” is undefined. Each subsequent repeat group contains the monitoring data for a single category.
Each repeat group provides information on the CPU and system time. In multiprocessor servers, the sum of the times across all categories can be greater than the “elapsed_time” in the SM2GDAT_basic_single_mdl structure.
The number of DMS/paging I/Os and the associated service times refer only to the devices specified in the SM2GDAT_system_single_mdl structure in the “device_name” element. In the case of paging I/O, only the assignable I/Os are supplied (see above). In the case of the SUM category, the sum is formed on the basis of all I/Os and times.
For the queues, the number of tasks in the queue at the end of the monitoring cycle or the number of tasks that left the queue during the monitoring cycle is output.
Descriptive structures: | SM2GDAT_system_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_system_single_mdl |
Monitoring program: SYSTEM
Structure of the TCP-IP data buffer
The TCP-IP data buffer provides monitored data on each TCP/IP connection of the local host.
The data area of the TCP-IP 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 the number of repeat groups to follow.
Descriptive structure: | SM2GDAT_tcp_ip_single_mdl |
Displacement from the beginning of | “fixed_part_dsp” from the BUFFER HEADER |
Repeat groups
A repeat group is written for each connection. IPv4 as well as IPv6 connections are reported. Depending on the version (ip-version variable), the variables of the local or remote IP address are only partially (IPv4) or fully (IPv6) filled. The repeat group provides the number of data packets sent and received, the cache area occupied by messages to be sent and received, and the size of the last window sent or received.
Descriptive structure: | SM2GDAT_tcp_ip_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_tcp_ip_single_mdl |
Monitoring program: TCP-IP
Structure of the TIME-IO data buffer
The TIME-IO data buffer provides an overview of important system activities. It supplies monitoring data for each logical machine.
The data area of the TIME-IO 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 monitoring data that is not specific to any particular logical machine. The number of CPU reconfigurations and active logical machines is output here.
Descriptive structure: | SM2GDAT_time_io_single_mdl |
Displacement from the beginning of the BUFFER HEADER: | “fixed_part_dsp” from the BUFFER HEADER |
Repeat groups
The first repeat group contains for all logical machines mean values for the TU, TPR, SIH and IDLE times and cumulative values for the other monitoring data. Each subsequent repeat group contains the monitoring data for a single logical machine. Consequently, when there is only one logical machine, there is only one repeat group.A repeat group contains the CPU time in the various function statuses, the number of SVC calls and the number of input/output operations. The number of the logical machine is provided in printable form (beginning with '00'). The first repeat group always contains AV for the number of the logical machine.
On x86 servers the following applies: Only in the first repeat group the element “other_io” contains the operations on devices of the family type TD.
Descriptive structure: | SM2GDAT_time_io_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: | “number_groups” from the BUFFER HEADER |
Monitoring program: –
Structure of the TLM data buffer
The TLM data buffer supplies data on the utilization of locks administered by the Task Lock Manager.
The data area of the TLM data buffer comprises an area of fixed length and a number of repeat groups.
Data buffer type: 3
Fixed-length data area
The number of supplied repeat groups to follow is contained in “used_groups”.
Descriptive structure: | SM2GDAT_tlm_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 lock. The repeat group provides information on the mean number of tasks in the queue and on how often the lock was identified as occupied.
The data is collected by sampling. The number of samples is contained in the SM2GDAT_tlm_single_mdl structure in the “samples” element. You should bear in mind that the accuracy of the data varies with the number of samples taken.
Descriptive structure: | SM2GDAT_tlm_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_tlm_single_mdl |
Monitoring program: TLM
Structure of the UDS-SQL data buffer
The UDS-SQL data buffer supplies data on UDS/SQL data base systems.
The data area of the SESAM-SQL 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 the number of the following repeat groups
Descriptive structure: | SM2GDAT_uds_sql_single_mdl |
Displacement from the beginning of the BUFFER HEADER: | “fixed_part_dsp” from BUFFER HEADER |
Repeat groups
A repeat group is written for each monitored database system.
All monitored data with the unit “Number” applies for the monitoring cycle specified in “elapsed_time”. Because of the asynchronous data collection (see section "PrivilegedSM2 monitoring programs"), the “elapsed_time” can differ from the variable of the same name in the BASIC data buffer.
Descriptive structure: | SM2GDAT_uds_sql_multiple_mdl |
Displacement of the first repeat group from the beginning of the BUFFER HEADER: | “first_group_dsp” from BUFFER HEADER |
Length of a repeat group: | “length_group” from BUFFER HEADER |
Number of repeat groups: | “used_groups” from SM2GDAT_uds_sql_single_mdl |
Monitoring program: UDS-SQL
Structure of the USERFILE data buffer
The USERFILE data buffer contains data on access to user-specifically registered files.
The data area of the USERFILE 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_userfile_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 monitored file. The repeat group provides information on the number of read, write, wait and check accesses as well as the average duration of I/Os.
The number of repeat groups that are actually filled (“used_groups”) may be smaller than the number of groups that exist (“number_groups”). Equally, the filled repeat groups can be distributed arbitrarily among the existing groups.
Descriptive structure: | SM2GDAT_userfile_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_userfile_single_mdl |
Monitoring program: FILE (USER MEASUREMENTS)
Structure of the USERISAM data buffer
The USERISAM data buffer supplies data on access to user-specifically registered ISAM pools.
The data area of the USERISAM 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_userisam_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 monitored ISAM pool. The repeat group provides information on the accesses and the pages used for buffering.
The number of repeat groups that are actually filled (“used_groups”) may be smaller than the number of groups that exist (“number_groups”). Equally, the filled repeat groups can be distributed arbitrarily among the existing repeat groups.
Descriptive structure: | SM2GDAT_userisam_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_userisam_single_mdl |
Monitoring program: ISAM (USER MEASUREMENTS)
Structure of the UTM data buffer
The UTM data buffer supplies application-specific data for UTM applications.The data area of the UTM data buffer comprises only repeat groups.
Data buffer type: 2
Repeat groups
A repeat group exists for each UTM application. A repeat group is subdivided into constant, periodic and event-driven data. Each of these types of data has its own structures. In the case of the event-driven data (SM2GDAT_utm_event_mdl structure), each monitoring value is calculated on the basis of a counter (“count”) and a sum element (“sum”). The counter specifies how often the event has occurred. The sum element contains the sum of the data made available for the events. The quotient of “sum” and “count” is the mean monitoring value.
Descriptive structures: | SM2GDAT_utm_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: | “number_groups” from the BUFFER HEADER |
With the extension extv3 the repeat group is extended by, among other things, TAC class values. The data of the TAC classes is contained in the repeat groups of the UTM application as TAC class repeat groups (structure SM2GDAT_utm_ext_tacclass_mdl). 16 TAC class repeat groups always exist which are addressed analogously to the UTM application repeat groups:
Descriptive structure: | SM2GDAT_utm_ext_tacclass_mdl |
Displacement of the first repeat group from the beginning of the MULTIPLE BUFFER (structure SM2GDAT_utm_multiple_mdl): | „ev3_first_tacclass_group_dsp“ from SM2GDAT_utm_ext_tacclass_mdl |
Length of a repeat group: | „ev3_length_tacclass_group“ from SM2GDAT_utm_ext_tacclass_mdl |
Number of repeat groups: | „ev3_number_tacclass_groups“ from SM2GDAT_utm_ext_tacclass_mdl |
Monitoring program: UTM
Structure of the VM data buffer
The VM data buffer provides data for the individual virtual machines (VMs) of a VM2000 system.
The data area of the VM data buffer comprises an area of fixed length and a number of repeat groups.
Data buffer type: 3
Fixed-length data area
In addition to the number of repeat groups subsequently supplied with values, the fixed-length data area contains the number of real, available CPUs.
The values for the hypervisor are only available on /390 servers.
The values for the utilization of all domains, for the BS2000 guest systems and for the CPU percentages available to BS2000 guest systems are only available on x86 servers.
Displays which show the validity of the data exist for this data.
Descriptive structure: | SM2GDAT_vm_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. The repeat group provides information on the CPU time utilized and the planned relative share of CPU time. The available main memory and the number of the active, virtual CPUs are also output.
Values for all VMs are output only on the monitor VM. Otherwise, only the values of your own VM are output.
Descriptive structure: | SM2GDAT_vm_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_single_mdl |
Monitoring program: VM
Structure of the VM-CPU-POOL data buffer
The VM-CPU-POOL data buffer supplies data on the utilization of the CPU pool.
The data area of the VM-CPU-POOL 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 the following repeat groups.
Descriptive structure: | SM2GDAT_vm_cpupool_single_mdl |
Displacement from the beginning of the BUFFER HEADER: | “fixed_part_dsp” from BUFFER HEADER |
Repeat groups
For each CPU pool a repeat group exists with
information on the CPU pool
name, number of available real CPUs (also extra CPUs)monitored data
The values for the hypervisor are only available on /390 servers.The values for the utilization of all domains, for the BS2000 guest systems and for the CPU shares available to BS2000 guest systems are only available on x86 servers.Displays which show the validity of the data exist for this data.
Values for all CPU pools are output only on the monitor VM. Otherwise, only the values for the CPU pool of your VM are output.
Descriptive structure: | SM2GDAT_vm_cpupool_multiple_mdl |
Displacement of the first repeat group from the beginning of the BUFFER HEADER: | “first_group_dsp” from BUFFER HEADER |
Length of a repeat group: | “length_group” from BUFFER HEADER |
Number of repeat groups: | “used_groups” from SM2GDAT_vm_cpupool_single_mdl |
Monitoring program: VM
Structure of the VM-GROUP data buffer
The VM-GROUP data buffer supplies data on the utilization of VM groups (/390 servers only).
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 fixed-length data area supplies the number of available real CPUs.
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 monitor VM. 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 |
Monitoring program: VM