Preface 1.1 Brief description of the SM2 monitoring system The SM2 monitoring system provides the user with statistics on the performance of the DP system and on resource utilization. It consists of the following components: ● the SM2 monitoring program ● the SM2U1 utility routine ● the SM2R1 analysis routine The SM2 monitoring program collects statistical data and outputs it either to a terminal and/ or to a file. The first option is ideally suited for real-time (online) monitoring.
Summary of contents Preface 1.2 Target group This manual is intended for system users who need information on the current system workload. It will be of particular interest to computer center and systems support staff who wish to assess the performance of their configuration and isolate bottleneck areas by means of long-term monitoring. 1.3 Summary of contents This is Volume 1 of a set of two manuals and describes the SM2 monitoring program.
Preface Summary of contents Chapter 7, Variables reports, contains a table detailing variables and report groups. Chapter 8, Messages, lists all the program messages, together with an explanation and the action to be taken in each case. Chapter 9, Installation, describes how to install SM2. Chapter 10, Appendix, contains descriptions of the SDF syntax and overviews of the SM2 statements.
Changes made since the last version Preface 1.4 Changes made since the last version of the manual SM2 Version 13.0A (June 1999) incorporates the following major changes as compared to the previous version (V12.0A, December 1996): SM2 ● ● 4 New monitoring programs – BCAM-CONNECTION This monitoring program is used to record monitored data for defined connections. – DISK-FILE This monitoring program is used to record inputs and outputs for selected disks.
Preface Changes made since the last version ● New reports – BCAM CONNECTION Outputs information on data that has been received/sent and on bucket-specific times. – DISK FILE Outputs files showing the inputs and outputs per second for the monitored disk devices. – SYMMETRIX CONTROLLER Outputs monitored data on the use of SYMMETRIX controllers. – SYMMETRIX DEVICE Outputs monitored data on the use of the individual devices of a SYMMETRIX controller.
Changes made since the last version ● 6 Preface – SET/MODIFY-COSMOS-PARAMETER The new MEASUREMENT-TIME operand can be used to specify the duration of the monitoring process. In the TSN operand, up to 16 TSNs can be specified. In the TSN, USER-ID, JOB-NAME and CATEGORY operands, the last character may be an asterisk (*). – SET-SERVICETIME-PARAMETER The DEVICES operand has been extended to accept 256 device names. – SET-TASK-PARAMETER The DEVICES operand has been extended to accept 64 device names.
Preface Notational conventions SM2U1 ● Extended statement: SELECT-MEASUREMENT-GROUPS The statement has been extended to include – the new monitoring programs BCAM-CONNECTION, DISK-FILE and HSMS – the new report groups SYMMETRIX-CONTROLLER and SYMMETRIX-DEVICE. SM2R1 ● New statement: PRINT-HSMS-STATISTICS Data from the HSMS monitoring program is displayed in the form of tables.
README file Preface 1.6 README file Information on any functional changes and additions to the current version of the product described in this manual can be found in the product-specific README file. You will find the README file on your BS2000 system under the file name SYSRME.SM2.130.E. Ask your systems support staff for the user ID under which the README file is located.
2 The SM2 monitoring program 2.1 Overview SM2 is a shareable program that runs under BS2000. It provides the user with information on the status and performance of the system, making it possible to improve the performance of both the system and its applications. The mode and scope of monitored data acquisition in SM2 can be controlled using commands and statements. SM2 generates a number of system tasks which are responsible for collecting data and writing it to the SM2 output files.
Overview SM2 monitoring program SM2 administrator SM2 user SM2 user Monitored task ...
SM2 monitoring program Operating modes/users 2.2 SM2 operating modes SM2 offers three operating modes: 1. Real-time monitoring (information output to a data display terminal) 2. Background monitoring (information output to a file for subsequent analysis) 3. User-specific task monitoring The operating modes can be used simultaneously. When mode 1 is used, SM2 periodically outputs monitored data in the form of reports on the data terminal. The color version of the 9752 Data Display Terminal is supported.
Operating modes/users SM2 monitoring program 2.3 Users Privileged users Privileged SM2 users are users who have been assigned the system privilege SW-MONITOR-ADMINISTRATION. These fall into the following categories: "primary" administrators, "secondary" administrators and other privileged users. Entry of an administration statement gives the first privileged SM2 user the status of SM2 primary administrator.
SM2 monitoring program Authorization table 2.4 Table of authorizations The following table indicates which users are permitted to carry out which functions and under what circumstances. Sys. priv. SWMONADM Function (group) Pr. adm Sec. adm Other Priv.
Activating the monitoring task SM2 monitoring program Key Pr. adm: Primary administrator Sec. adm: Secondary administrator Other: Other privileged user Priv.
SM2 monitoring program Acquisition of monitored data 2.6 Acquisition of monitored data SM2 records a wide range of monitored data and outputs it to either a screen and/or a file. The data is collected at regular intervals, called monitoring cycles. Some of the monitoring tasks are carried out by default, while others are carried out by special monitoring programs which can be activated as and when required.
Acquisition of monitored data SM2 monitoring program Analysis routine SM2R1 SM2R1-PC Output buffer SM2 in BS2000 SM2 data buffer Monitoring programs Tables Counter SM2 file I/O buffer BS2000 monitored object, event Figure 2: Collecting monitored data 16 U3585-J-Z125-8-76
SM2 monitoring program Monitoring cycle 2.7 Monitoring cycle As mentioned above, SM2 collects data at regular intervals known as monitoring cycles (except for the monitoring programs DISK and TASK). At the end of each monitoring cycle, the processed data is written to the data buffer and to the SM2 output file, if one is available. The length of the monitoring cycle is preset at 150 seconds when the subsystem is started.
Outputting and saving monitored data SM2 monitoring program Monitoring cycle Sampling cycle val1 val2 val3 val4 ..... valn To obtain data, SM2 counts and system counts are evaluated. Mean values are computed, percentage frequencies are determined, and total values are calculated in order to arrive at monitored data. 1 n value = --- ∑ val j n 1 Figure 3: Relationship between the sampling cycle and the monitoring cycle 2.
SM2 monitoring program Outputting and saving monitored data Methods used for compressed output of monitored data 1. Mean values SM2 adds up the sampled values at the end of each sampling cycle and computes a mean value for each monitoring cycle (e.g. the number of tasks) as follows: Average = Sum of sampled values LR2LR2LR2LR2LR2LR2LR2LR2LR2LR2LR2LR2LR2LR2LR2LR2LR2LR2LR2LR2LR2LR2LR2LR2LR2LR2 Number of samples 2.
SM2 monitored variables SM2 monitoring program 2.9 SM2 monitored variables The table below shows the main monitored variables of SM2. A table showing the links between the monitored variables and monitoring programs, ONLINE reports, and SM2R1 report groups can be found in chapter “Variables reports” on page 361.
SM2 monitoring program Monitored variable SM2 monitored variables Description Files (continued) File access statistics Number of PAM-WAIT, PAM-CHECK-READ, PAM-WRITE operations and input/output operations per second for one file. Distribution of input/output operations to files for selected disks. File access times Average access time in milliseconds for each input/output. IOs Number of input/output operations Number of input/output operations per second.
SM2 monitored variables Monitored variable SM2 monitoring program Description Memory Main memory utilization Number of 4-KB pages in main memory. Utilization of paging area Number of pageable 4-KB pages on the devices. Utilization of virtual address space Number of class 1 through class 4 pages in the virtual address space. Page fault rate Number of page fault interrupts per second.
SM2 monitoring program Monitored variable SM2 monitored variables Description VM2000 Hypervisor activities Percentage active and idle times of the system. Guest system activities Planned and measured CPU utilization as a percentage.
Analyzing monitored data SM2 monitoring program 2.10 Analyzing monitored data There are several tools on various different platforms which can be used to process and display monitored data. SM2-ONLINE (BS2000/OSD) SM2-ONLINE is a component of the SM2 monitoring program. At the end of each monitoring cycle, it outputs monitored data in the form of reports. For further information, please refer to chapter “SM2 screen output” on page 201ff.
SM2 monitoring program Performance expectations of the user 2.11 Performance expectations of the user When assessing the performance of a DP system, the user is generally interested in: ● the time it takes for the system to respond to requests, ● how many requests the system can handle within a given period of time, and ● what resources are used. The performance level of the hardware (e.g. the number of instructions processed per second) and of the operating system (e.g.
Performance expectations of the user SM2 monitoring program The sum of single-step and multi-step transactions required for handling one application is called an operation. The characteristic criteria for describing performance expectations are: ● Transaction rate Sum of all successfully completed transactions per unit of time ● Response time Time required for processing by the DP system ● Number of simultaneously active users.
SM2 monitoring program System monitoring 2.
System monitoring SM2 monitoring program Bottleneck analysis Before monitoring is started, you must clarify any performance problems, i.e. performance expectations that are not satisfied. The following problems may exist: ● System-oriented performance problems These arise if the system throughput rate is unsatisfactory, and are indicated by a low transaction rate and/or throughput rate. The most likely cause is the overloading of one or more resources.
SM2 monitoring program Efficient DP system usage Because of the volume of data generated, it does not make sense to copy all data record types into the master SM2 output file. SM2U1 can be used to suppress certain data records when updating the master SM2 output file. To investigate delays when handling special load requirements, you will need further information in addition to the system utilization data described above.
SM2 in computer networks SM2 monitoring program 2.14 SM2 in computer networks SM2 provides functions for the central online monitoring and control of monitored-data acquisition in a computer network. The monitored data is independently recorded on each host in the network by a local SM2 monitoring program, and is exchanged between the hosts via a LAN. In this way, the online reports of all hosts can be output on any computer in the network.
SM2 monitoring program SM2 in computer networks Users in a computer network SM2 distinguishes between privileged users (“primary” and “secondary” administrators and other privileged users) and nonprivileged users. This also applies in a computer network. It does not distinguish between the rights of local and remote users. Users can have different rights on different hosts, depending on their privileges and the rights they have already been assigned.
SM2 in computer networks SM2 monitoring program Restrictions for the computer network 1. The BS2000 /START-TASK-MEASUREMENT command can only be used on the local host. 2. Scroll commands – Scrolling backward with “-” or “-R” is not supported across host boundaries; i.e. you cannot scroll back from the first report of one host to the last report of the previous host. – You can only change to the first report of the previous host using the scroll command “-N” (node) (see page 152).
3 SM2 monitoring programs 3.1 Overview SM2 offers a range of optional monitoring programs that record additional data. A distinction is drawn between privileged monitoring programs, which only an SM2 administrator can start and stop, and monitoring programs for user-specific monitored objects, for which the permission of the SM2 primary administrator is required (see the MODIFY-USERADMISSION statement, page 98).
Overview SM2 monitoring programs Monitoring programs Parameter/ monitored object definition BCAM-CONNECTION CHANNEL-IO CMS COSMOS DAB DISK DISK-FILE DLM FILE GS GSVOL HSMS ISAM MSCF NET-DEVICE NSM PCA PERIODIC-TASK PFA POSIX RESPONSETIME SERVICETIME SVC SYSSTAT TASK TCP-IP TLM UTM VM USER FILE USER ISAM USER TASK Output exclusively to file x x Online output Name of the online report Selection Only privileged of additional reusers ports BCAM CONNECTION CHANNEL CMS x x (1) x x x x DAB DISK FILE D
SM2 monitoring programs BCAM-CONNECTION 3.2 Privileged SM2 monitoring programs BCAM-CONNECTION Monitored data on connection sets The BCAM-CONNECTION monitoring program supplies monitored data for connections that are combined in connection sets. It provides monitored variables for DCAM applications (with NEA names) and socket applications (with port numbers) only. Information is recorded on INWAIT, REACT, INPROC and OUTPROC times.
BCAM-CONNECTION SM2 monitoring programs The last value in the list of ranges specifies the overflow limit. All monitored variables that exceed this limit are included under the last range. The bucket parameters in BCAM can be specified by both SM2 and other applications. It is also possible to disable monitored data acquisition entirely. The SET-BCAM-CONNECTION-PARAMETER statement contains the *UNCHANGED operand value.
SM2 monitoring programs BCAM-CONNECTION Examples of monitoring program definitions Example 1 SET-BCAM-CONNECTION-PARAMETER INWAIT-BUCKETS = *UNCHANGED, REACT-BUCKETS = *UNCHANGED, INPROC-BUCKETS = *UNCHANGED, OUTPROC-BUCKETS = *UNCHANGED ADD-BCAM-CONNECTION-SET SET-NAME = setname1, CONNECTION-SELECTION = *BY-NEA-NAME ( CONNECTION-NAME = *SPECIFIED ( LOCAL-APPLICATION = $DIALOG, PARTNER-APPLICATION = *ANY)), CONNECTION-TYPE = *REMOTE, HOST-SELECTION = *SPECIFIED ( LOCAL-HOST-NAME = *LOCAL, PAR
CHANNEL-IO SM2 monitoring programs Example 2 REMOVE-BCAM-CONNECTION-SET SET-NAME = *ALL SET-BCAM-CONNECTION-PARAMETER ADD-BCAM-CONNECTION-SET SET-NAME = setname2, CONNECTION-SELECTION = *BY-PORT-NUMBER( PORT-NUMBER = *SPECIFIED ( LOCAL-PORT-NUMBER = 5000, PARTNER-PORT-NUMBER = *ANY)), CONNECTION-TYPE = *BOTH, HOST-SELECTION = *SPECIFIED ( LOCAL-HOST-NAME = *LOCAL, PARTNER-HOST-NAME = hostname2) CHANGE-MEASUREMENT-PROGRAM TYPE = *BCAM-CONNECTION These statements end the current monitoring process and
SM2 monitoring programs COSMOS COSMOS Monitored data on the system for bottleneck analysis COSMOS is an event-driven monitoring program for recording detailed system data that is required particularly for bottleneck analyses of OLTP applications. It collects monitored data for all tasks, for task groups (which can be selected by user ID, category, or job name), or for individual tasks.
DISK-FILE SM2 monitoring programs Due to the large amount of data generated and the resulting high load on the CPU, this monitoring program should be used for short monitoring operations only (between half an hour and one hour), and only on a small number of disk devices. Note The only access values recorded are ones where an I/O chain begins with a search command (SEEK). This is usually the case for most access attempts, with the exception of the following instances: 1. When formatting disks (VOLIN) 2.
SM2 monitoring programs FILE FILE Monitored data on file access for selected files This monitoring program provides information on the number and average duration of file access, provided that access was by way of the I/O output system of privileged PAM (PPAM). This includes file access using the methods EAM (Evanescent Access Method) and ISAM (Indexed Sequential Access Method).
ISAM SM2 monitoring programs ISAM Monitored data on ISAM pools When the BS2000 component NK-ISAM is installed, the monitoring program for ISAM pools provides information on the performance of the ISAM buffer management facility. ISAM buffer management is aimed at reducing the physical I/O operations involved in accessing ISAM files.
SM2 monitoring programs PCA PCA Monitored data on 3419/21 disk controllers under PCA This monitoring program records monitored data on 3419/21 disk controllers managed by the PCA (Peripheral Cache Administrator) subsystem. It is used to record statistics on the ADM PFA cache areas (Administrator Controlled Performant File Access).
PFA SM2 monitoring programs PFA Monitored data on caches under User PFA User PFA (User Controlled Performant File Access) allows users to assign performance attributes to files, thus converting them into hiperfiles (High Performance Files). The idea behind hiperfiles is that file access is accelerated by buffering the file in a high-speed cache in order to avoid the slow disk input/output operations.
SM2 monitoring programs RESPONSETIME RESPONSETIME Monitored data on the BCAM pool The RESPONSETIME monitoring program records information on response times, think times, transactions times, and wait times in the BCAM pool. It supplies useful monitored data for dialog-oriented DCAM applications only (with NEA names). The response time is understood to mean the time between the receipt of a message by the host and the sending of a response to the partner application.
RESPONSETIME SM2 monitoring programs Example: Calculating the time values TI TO1 TO2 TR TO3 TO4 TI,next t TI Input time stamp TO Output time stamp TR Time stamp of the current receive action in the BCAM application RT1 = TO1-TI RT2 = RT2, TO2-TO1, TO3-TO2, TO4-TO3 Response time (definition 2) TrT = TO4-TI Transaction time ThT = TI,next-TO4 Think time WT = TR-TI Wait time Response time (definition 1) The outputs at times TO1,2 cannot refer to the input at time TI because the latt
SM2 monitoring programs RESPONSETIME Wait times within the communications host and data transfer times cannot be taken into consideration. Example: Responses to a /SHOW-FILE-ATTRIBUTES command SHOW-FILE-ATTRIBUTES 30 :V:$ABCxxxxx.BEISP Response time as per def. 1 54 :V:$ABCxxxxx.MAN.1 60 :V:$ABCxxxxx.MAN.2 Response time as per def. 2 60 :V:$ABCxxxxx.MAN.3 30 :V:$ABCxxxxx.MAN.4 Transaction time 30 :V:$ABCxxxxx.MAN.5 30 :V:$ABCxxxxx.MAN.6 51 :V:$ABCxxxxx.MAN.7 12 :V:$ABCxxxxx.MAN5.1 12 :V:$ABCxxxxx.
RESPONSETIME SM2 monitoring programs – The message "NOTE: CONNECTION NUMBER TOO LOW" will be issued in the SM2 output report. Each of the RESPONSETIME screens (see description of the RESPONSETIME report) will show the same message. The message is output only if no interactions were recorded during the monitoring cycle in question. – An indication to this effect will be given in the SM2 response record at the end of this monitoring cycle.
SM2 monitoring programs RESPONSETIME This monitoring program supplies statistics for each connection set. In addition, the set of all connections is monitored on an ongoing basis. When selecting which connections are to be monitored, the SM2 administrator can define up to 15 connection sets. (*ALL,*ALL,*ALL) is always set automatically as the additional connection set.
SERVICETIME SM2 monitoring programs Example 2 REMOVE-CONNECTION-SET SET-NAME=*ALL MODIFY-RESPONSETIME-PARAMETER DEFINITION=*2 ADD-CONNECTION-SET SET-NAME=setname,SET-DEFINITION=*EXCEPT-CONNECTION, CONNECTION-SET=($OMNIS,*ALL,*ALL) CHANGE-MEASUREMENT-PROGRAM TYPE=*RESPONSETIME The above statements terminate the RESPONSETIME monitoring program (apart from *GLOBAL) and restart it, monitoring all connections with the exception of the $OMNIS application.
SM2 monitoring programs SVC In the case of processors with DCS in which there are several guest systems running under VM2000, the SERVICETIME monitoring program can only be started by one of these guest systems. Any attempts to start this function from a second guest system will be accepted without an error message, but no DCS-specific monitored data will be returned.
TASK SM2 monitoring programs TASK Task-specific monitored data The purpose of this function is to provide task-specific variables, from which the resource requirements of individual tasks can be determined. This data can be used for the following purposes: – – – to determine which tasks most frequently use specific resources to optimize operation by relocating loads as input data for simulation models or analytic calculations.
SM2 monitoring programs TLM TLM Monitored data on locks The TLM (TASK LOCK MANAGER) monitoring program records monitored data on locks managed by the Task Lock Manager. The occupation and average queue length of each lock are determined. The monitored data returned will be of interest only to performance specialists, since detailed knowledge of the internal workings of the system is required to interpret it.
VM SM2 monitoring programs DB-specific utilization figures (UDS and SESAM only) are only supplied if the following conditions are met: – – – – BS2000 Accounting is active. The UTM accounting record UTMA is switched on (using the BS2000 command MODIFY-ACCOUNTING-PARAMETERS SET-RECORD-TYPE=UTMA). UTM Accounting is switched on (using the KDCAPPL statement, parameter ACC=ON). Monitored-data acquisition is enabled in SESAM (using the statement ACC,TP=ON,CPU).
SM2 monitoring programs FILE 3.3 Nonprivileged SM2 monitoring programs The following instructions must be heeded when using nonprivileged monitoring programs. You should also refer to the descriptions of the corresponding privileged monitoring programs for a better understanding of monitoring-program-specific features and variants.
TASK SM2 monitoring programs SM2 does not check whether an ISAM pool exists when a user tries to include it; in other words an ISAM pool can be included in the monitoring process even before it has been created. If an ISAM pool which has been included does not exist during the monitoring cycle, all its monitored data will be listed with blanks.
4 SM2 operation 4.1 Starting and terminating SM2 4.1.1 Starting the program SM2 is called with the following BS2000 command : START-SM2 Format START-SM2 VERSION = *STD / / / ,MONJV = *NONE / ,CPU-LIMIT = *JOB-REST / Operands VERSION = Specifies the version of SM2 to be called. VERSION = *STD The current version is called.
Starting and terminating SM2 SM2 operation MONJV = Specifies the name of the job variable to be monitored in the SM2 run. The job variable must already be cataloged. MONJV = *NONE No job variable is specified. MONJV = Specifies the name of a job variable already cataloged. CPU-LIMIT = Specifies the CPU time required for the SM2 run. In interactive mode, the user is notified by the system if this time is exceeded. In batch mode, the SM2 run is terminated.
SM2 operation Overview 4.2 Overview of SM2 operation After the program load message, SM2 prompts you to enter statements. Each caller (privileged or nonprivileged user, see section “Users” on page 12) is initially taken to the analysis subinterval of SM2.
Typical SM2 run SM2 operation Typical SM2 run Start SM2 /START-SM2 SM2 monitoring task set up internally (in first SM2 call during system run) Switch to administration facility Set monitoring cycle Open SM2 output file Start monitoring programs Switch to analysis subinterval Select online reports CALL-ADMINISTRATION-PART //MODIFY-MEASUREMENT-PERIODS OFFLINE-PERIOD= //OPEN-LOG-FILE FILE= //START-MEASUREMENT-PROGRAM TYPE= //CALL-EVALUATION-PART REPORT
SM2 operation Statements for SM2 adminstrators 4.3 Statements for SM2 administrators These statements are used by SM2 administrators to control data acquisition by SM2.
Statements for SM2 adminstrators 62 SM2 operation Statement Function ADD-BCAM-CONNECTION-SET Add a connection set for BCAM-CONNECTION monitoring ADD-CONNECTION-SET Add a connection set (applications and partner systems) for RESPONSETIME monitoring ADD-COSMOS-EVENT Define events for monitored-data acquisition ADD-FILE Define a file to be monitored ADD-ISAM-POOL Define an ISAM pool to be monitored MODIFY-COSMOS-PARAMETER Modify the parameters for COSMOS monitoring MODIFY-RESPONSETIME- PARAMET
SM2 operation Statements for SM2 adminstrators Statements for preparing, starting, and stopping monitoring programs Once you have defined the objects to be monitored, the monitoring program run can be started. Certain preparations are recommended for the COSMOS monitoring program to ensure that it starts quickly and without errors.
Statements for SM2 adminstrators SM2 operation Statements for assigning privileges At the beginning of the program, the nonprivileged user is not allowed to monitor tasks, files or ISAM pools. But by using the MODIFY-USER-ADMISSION statement, the primary SM2 administrator can grant or withdraw permission for all BS2000 users to monitor tasks under their own ID, files and ISAM pools.
SM2 operation Statements for SM2 adminstrators Statement for terminating the SM2 program The END statement is used to terminate the SM2 session. However, monitoring operations which have already been initiated are not affected, i.e. they continue to run. Statement Function END Terminate the SM2 run The following sections describe the statements for SM2 administrators in alphabetical order.
ADD-BCAM-CONNECTION-SET Statements for SM2 administrators ADD-BCAM-CONNECTION-SET Add connection set for BCAM-CONNECTION monitoring Function This statement is used to define a connection set which is to be added to the BCAMCONNECTION monitoring program definition.
Statements for SM2 administrators ADD-BCAM-CONNECTION-SET Operands SET-NAME = Defines a name for the selected connection set. CONNECTION-SELECTION = Defines the type of connection set to be monitored. CONNECTION-SELECTION = *BY-NEA-NAME(...) Defines a selection of connections in accordance with the application name. CONNECTION-NAME = list-poss(16): *SPECIFIED(...) LOCAL-APPLICATION = *ANY / *ANY: No special local application is selected.
ADD-BCAM-CONNECTION-SET Statements for SM2 administrators HOST-SELECTION = Defines the names of the hosts between which the connections to be monitored should exist. HOST-SELECTION = *ANY No special host name is selected. HOST-SELECTION = *SPECIFIED(...) LOCAL-HOST-NAME = *LOCAL / *LOCAL: The local host name should be used. : Specifies the name of the local host. With some connections, the local processor name may differ from the host name.
Statements for SM2 administrators ADD-CONNECTION-SET ADD-CONNECTION-SET Add connection set for RESPONSETIME monitoring Function This statement is used to define a connection set which is to be added to the RESPONSETIME monitoring program definition. A connection set consists of one or more (as many as five) connection groups. The connection set can be either positively defined (i.e. all groups specified in this connection set are monitored) or negatively defined (i.e.
ADD-CONNECTION-SET Statements for SM2 administrators Format ADD-CONNECTION-SET SET-NAME = ,SET-DEFINITION = *BY-CONNECTION / *EXCEPT-CONNECTION ,CONNECTION-SET = list-poss(5): *CONNECTION(...) *CONNECTION(...) APPLICATION = *ALL / ,PARTNER = *ALL / ,PROCESSOR = *ALL / ,CONNECTION-TYPE = *REMOTE / *LOCAL / *BOTH Operands SET-NAME =
Statements for SM2 administrators ADD-CONNECTION-SET PROCESSOR = *ALL / *ALL: No special partner processor is selected. : Specifies the name of the partner processor which has been selected. An asterisk (*) is also permitted as the last character in a wildcard specification. CONNECTION-TYPE = Specifies the type of connection to be taken into consideration for the connection set.
ADD-COSMOS-EVENT Statements for SM2 administrators ADD-COSMOS-EVENT Define events for monitored-data acquisition Function This statement is used to define events which are to be added to the COSMOS monitoring program definition.
Statements for SM2 administrators ADD-FILE ADD-FILE Define file to be monitored Function This statement is used to define a file which is to be added to the FILE monitoring program definition. This monitoring program allows you to define up to 16 files for monitoring. If this number is exceeded, the statement is rejected and a corresponding message is issued. Format ADD-FILE FILE-NAME = Operands FILE-NAME = Name of the file whose access values are to be monitored.
ADD-ISAM-POOL Statements for SM2 administrators ADD-ISAM-POOL Define ISAM pool to be monitored Function This statement is used to define an ISAM pool which is to be added to the ISAM monitoring program definition. This monitoring program allows you to define up to 16 ISAM pools for monitoring. If this number is exceeded, the statement is rejected and a message is issued. Format ADD-ISAM-POOL POOL-NAME = ,SCOPE = *HOST-SYSTEM / *TASK(...) / *USER(...) *TASK(...
Statements for SM2 administrators ADD-ISAM-POOL SCOPE = *USER(...) The pool is a user-specific ISAM pool. USER-ID = Specifies the user ID under which the ISAM pool was set up. This must be specified without the “$” sign. CAT-ID = Specifies the catalog ID of the public volume set to which the ISAM pool has been assigned. The user ID must be specified without the “$” sign. CAT-ID = *HOME-PVS The ID here is the catalog ID of the home pubset. CAT-ID =
CALL-ADMINISTRATION-PART Statements for SM2 administrators CALL-ADMINISTRATION-PART Switch from evaluation part to administration facility Function This statement is used to switch from the evaluation part to the administration facility, which provides an SDF statement interface. To switch back to the analysis subinterval, use the CALL-EVALUATION-PART command.
Statements for SM2 administrators CALL-EVALUATION-PART CALL-EVALUATION-PART Switch from administration facility to evaluation part Function This statement is used to switch from the administration facility to the evaluation part, i.e. after this statement is entered all statements required for online analysis can be entered. To switch back to SDF statement mode for administration purposes, use the CALL-ADMINISTRATION-PART command.
CHANGE-MEASUREMENT-PROGRAM Statements for SM2 administrators CHANGE-MEASUREMENT-PROGRAM Stop current monitoring program run and restart it with new monitored objects Function This statement is used to stop the current monitoring program run and restart it using newly defined monitored objects/monitoring parameters. The current monitoring cycle is interrupted.
Statements for SM2 administrators CHANGE-MEASUREMENT-PROGRAM TYPE = *ISAM The ISAM monitoring program is restarted with a new range of ISAM pools. TYPE = *PERIODIC-TASK The PERIODIC-TASK monitoring program is restarted with a new range of tasks. TYPE = *RESPONSETIME The RESPONSETIME monitoring program is restarted with a new set of parameters or a new range of connection sets. TYPE = *SERVICETIME The SERVICETIME monitoring program is restarted with a new range of devices.
CLOSE-LOG-FILE Statements for SM2 administrators CLOSE-LOG-FILE Close SM2 output file Function This statement is used to close an SM2 output file. The current monitoring cycle is interrupted. Format CLOSE-LOG-FILE Note: When the SM2 output file is closed, all monitoring programs are stopped and the monitored data is written exclusively to the SM2 output file (see table “Overview of the SM2 monitoring programs” on page 34).
Statements for SM2 administrators END END Terminate SM2 run Function This statement is used to terminate SM2 administration. All current measurements are continued using the currently defined monitoring parameters. This is also the case if no further user is working with SM2. The only way to terminate SM2 along with the privileged system tasks is to issue the DSSM command /STOP-SUBSYSTEM SUBSYSTEMNAME=SM2.
INITIATE-COSMOS Statements for SM2 administrators INITIATE-COSMOS Prepare COSMOS monitoring program Function The COSMOS monitoring program is fully initiated (prepared), but no events are recorded yet - not even mandatory events. This statement is used to ensure to a large extent that the COSMOS monitoring program subsequently starts without errors and quickly (without mount messages).
Statements for SM2 administrators MODIFY-ADMINISTRATOR-ADMISSION MODIFY-ADMINISTRATOR-ADMISSION Admit additional SM2 administrators Function This statement is used by the SM2 primary administrator to admit additional secondary administrators. Format MODIFY-ADMINISTRATOR-ADMISSION CONCURRENCY = *NO / *YES Operands CONCURRENCY = Specifies whether additional SM2 administrators are to be admitted. CONCURRENCY = *NO No additional SM2 administrators are to be admitted.
MODIFY-COSMOS-PARAMETER Statements for SM2 administrators MODIFY-COSMOS-PARAMETER Modify parameters for COSMOS monitoring Function This statement is used to modify the COSMOS monitoring program definition. It is useful when the SHOW-DEFINED-PARAMETER statement finds parameters that have to be modified. Format (part 1 of 2) MODIFY-COSMOS-PARAMETER TITLE = *UNCHANGED / ,BUFFER-SIZE = *UNCHANGED / ,NUMBER-OF-BUFFERS = *UNCHANGED /
Statements for SM2 administrators MODIFY-COSMOS-PARAMETER (part 2 of 2) ,TASK-SELECTION = *UNCHANGED / *ALL / *SPECIFIED(...) *SPECIFIED(...) ,JOB-NAME = *NOT-SPECIFIED / list-poss(8): ,CATEGORY = *NOT-SPECIFIED / list-poss(8): ,USER-ID = *NOT-SPECIFIED / list-poss(8): TSN = *NOT-SPECIFIED / list-poss(16):
MODIFY-COSMOS-PARAMETER Statements for SM2 administrators BUFFER-SIZE = *UNCHANGED The currently specified number of pages per buffer is not changed. BUFFER-SIZE = Buffers of the specified size (number of pages) are created. NUMBER-OF-BUFFERS = Specifies the number of buffers. NUMBER-OF-BUFFERS = *UNCHANGED The currently specified number of buffers is not changed. NUMBER-OF-BUFFERS = COSMOS creates the specified number of buffers for writing events.
Statements for SM2 administrators MODIFY-COSMOS-PARAMETER OUTPUT = *WRAP-AROUND(...) COSMOS monitored data is written to a file on disk. If the disk space allocated (PRIMARYALLOCATION) is insufficient, the file is overwritten from the top. The secondary allocation (SECONDARY-ALLOCATION) must be set to zero. FILE-NAME = Specifies the file to which COSMOS monitored data is written. OUTPUT = *TAPE(...
MODIFY-COSMOS-PARAMETER Statements for SM2 administrators CATEGORY = The tasks are selected by means of their category. An asterisk (*) is also permitted as the last character in a wildcard specification. CATEGORY = *NOT-SPECIFIED No tasks are selected by means of their category. CATEGORY = list-poss(8): Specifies the categories of the tasks to be monitored. USER-ID = The tasks are selected by means of their user ID.
Statements for SM2 administrators MODIFY-COSMOS-PARAMETER EVENT-SELECTION = Specifies the events to be recorded. Their recording is linked to specific conditions. EVENT-SELECTION = *UNCHANGED The existing values for EVENT-SELECTION are not changed. EVENT-SELECTION = *ALL-BY-ADD-COSMOS-EVENT All open events are recorded. EVENT-SELECTION = *SPECIFIED(...) Only those events that satisfy the specified conditions are recorded.
MODIFY-COSMOS-PARAMETER Statements for SM2 administrators DAB-CACHE-ID = Controls the recording of DAB events on the basis of their DAB cache IDs. DAB-CACHE-ID = *UNCHANGED The currently specified DAB cache IDs are not changed. DAB-CACHE-ID = *ANY The recording of DAB events is independent of their DAB cache IDs. DAB-CACHE-ID = list-poss(8): Only those DAB events with the specified DAB cache IDs are recorded.
Statements for SM2 administrators MODIFY-COSMOS-PARAMETER LOCK-ID = *UNCHANGED The currently specified lock IDs are not changed. LOCK-ID = *ANY The recording of LOCK events is independent of their lock ID. LOCK-ID = list-poss(4): Only those LOCK events with the specified lock IDs are recorded. TLT-DESCRIPTOR = Controls the recording of TLT on the basis of their TLT descriptor (TLT = Task Location Table).
MODIFY-COSMOS-PARAMETER Statements for SM2 administrators UNLOAD = *AT-MEASUREMENT-PROGRAM-STOP The COSMOS subsystem is unloaded at the end of COSMOS monitoring. UNLOAD = *AT-SM2-STOP The COSMOS subsystem is unloaded at the end of SM2 monitoring. MEASUREMENT-TIME = Specifies the duration of the monitoring process. MEASUREMENT-TIME = *UNCHANGED The currently specified duration is not changed. MEASUREMENT-TIME = *NOT-SPECIFIED Monitoring is terminated by the user with the STOP-MEASUREMENT-PROGRAM statement.
Statements for SM2 administrators MODIFY-MEASUREMENT-PERIODS MODIFY-MEASUREMENT-PERIODS Modify SM2 monitoring cycle Function This statement is used to modify the SM2 time periods which control the cyclical acquisition of SM2 monitored data. Format MODIFY-MEASUREMENT-PERIODS OFFLINE-PERIOD = *UNCHANGED / ,ONLINE-PERIOD = *UNCHANGED / *SAME-AS-OFFLINE / ,SAMPLING-PERIOD = *UNCHANGED /
MODIFY-MEASUREMENT-PERIODS Statements for SM2 administrators ONLINE-PERIOD = *SAME-AS-OFFLINE The online cycle is the same as for background monitoring. This setting is the optimum setting for internal management of data. If the online cycle is not required for a longer period of time, this offline setting is selected. ONLINE-PERIOD = Defines an online cycle in seconds.
Statements for SM2 administrators MODIFY-RESPONSETIME-PARAMETER MODIFY-RESPONSETIME-PARAMETER Modify parameters for RESPONSETIME monitoring Function This statement is used to modify the RESPONSETIME monitoring program definition. Format MODIFY-RESPONSETIME-PARAMETER SCOPE = *UNCHANGED / list-poss(2): *BUCKET / *CATEGORY ,DEFINITION = *UNCHANGED / *1 / *2 ,CONNECTION-NUMBER = *UNCHANGED / ,RESPONSETIME-BUCKETS = *UNCHANGED / *STD-LIMITS / list-poss(5):
MODIFY-RESPONSETIME-PARAMETER Statements for SM2 administrators DEFINITION = Defines the type of response time to be monitored. DEFINITION = *UNCHANGED The type of response time defined by this time will not be changed. DEFINITION = *1 The response time valid is the period between user input and the first relevant output. DEFINITION = *2 In addition to the response time defined by the value 1, the periods between output following any entry are output individually as response times.
Statements for SM2 administrators MODIFY-RESPONSETIME-PARAMETER TRANSACTTIME-BUCKETS = Defines the upper limits of up to five ranges (in units of 100ms) in which the transaction times are to be stored by order of magnitude. TRANSACTTIME-BUCKETS = *UNCHANGED The currently defined upper limits of the ranges for transaction times are not changed. TRANSACTTIME-BUCKETS = *STD-LIMITS Sets the upper limits of the ranges for transaction times to 5, 10, 20, 50 and 100.
MODIFY-USER-ADMISSION Statements for SM2 administrators MODIFY-USER-ADMISSION Define authorizations for nonprivileged users Function This statement is used by the primary SM2 administrator to specify which users are permitted to execute user-specific monitoring programs. Format MODIFY-USER-ADMISSION TASK = *UNCHANGED / *ALLOW(...) / *INHIBIT *ALLOW(...) USER-ID = *ALL / list-poss(16): ,FILE = *UNCHANGED / *ALLOW(...) / *INHIBIT *ALLOW(...
Statements for SM2 administrators MODIFY-USER-ADMISSION USER-ID = Specifies the users for whom task monitoring is permitted. An asterisk (*) is also permitted as the last character in a wildcard specification. USER-ID = *ALL Task monitoring is permitted for all BS2000 users. USER-ID = list-poss(16): Task monitoring is permitted for users under the specified user IDs. These must be specified without the “$” sign.
MODIFY-USER-ADMISSION Statements for SM2 administrators ISAM = *ALLOW(...) Monitoring of ISAM pools is permitted for nonprivileged users. USER-ID = Specifies the users for whom the monitoring of ISAM pools is permitted. USER-ID = *ALL Monitoring of ISAM pools is permitted for all BS2000 users. USER-ID = list-poss(16): Monitoring of ISAM pools is permitted for users under the specified user IDs. These must be specified without the “$” sign.
Statements for SM2 administrators OPEN-LOG-FILE OPEN-LOG-FILE Open SM2 output file Function This statement is used to open an SM2 output file. The current monitoring cycle is interrupted. Format OPEN-LOG-FILE FILE = *STD / *BY-LINK-NAME ,BUFFER-OUTPUT = *NORMAL / *IMMEDIATE Operands FILE = An SM2 output file is opened; it includes the options listed below. If any other SM2 output file has already been opened at this point in time, it will be closed immediately. FILE = *STD A SAM file with the name SM2.
OPEN-LOG-FILE Statements for SM2 administrators BUFFER-OUTPUT = Defines file output. BUFFER-OUTPUT = *NORMAL A buffer, when full, is always written to a file. BUFFER-OUTPUT = *IMMEDIATE At the end of each monitoring cycle, a record for identifying the end of the cycle is written, after which the output buffer is output immediately. Even buffers which are not completely filled with data are output. This could lead to block corruption.
Statements for SM2 administrators REMOVE-BCAM-CONNECTION-SET REMOVE-BCAM-CONNECTION-SET Exclude connection set(s) from BCAM-CONNECTION monitoring Function This statement is used to define the connection set(s) to be removed from the BCAM-CONNECTION monitoring program definition. Format REMOVE-BCAM-CONNECTION-SET SET-NAME = *ALL / Operands SET-NAME = Specifies the name of the connection set to be removed from the monitoring program definition.
REMOVE-CONNECTION-SET Statements for SM2 administrators REMOVE-CONNECTION-SET Exclude connection set(s) from RESPONSETIME monitoring Function This statement is used to define the connection set(s) to be removed from the RESPONSETIME monitoring program definition. The connection set *GLOBAL (see also ADD-CONNECTION-SET) cannot be removed. Format REMOVE-CONNECTION-SET SET-NAME = *ALL /
Statements for SM2 administrators REMOVE-COSMOS-EVENT REMOVE-COSMOS-EVENT Remove events from COSMOS monitoring parameters Function This statement is used to define events which are to be removed from the COSMOS monitoring program definition.
REMOVE-COSMOS-EVENT Statements for SM2 administrators EVENT-NAME = list-poss(67): *STANDARD-EVENTS / *ACF / *BCAM / *BCPT / *BLS / *BOUR / *CHTM / *CMD / *CMS / *DAB / *DCAM / *DLM / *EIA / *EIA2 / *EIA3 / *FITC / *GSAC / *HAL / *IDLE / *INTR / *IONQ / *ISEV / *ISPL / *KAI / *LOCK / *MSG / *NSM / *PAGE / *PAM / *PCCC / *PCTC / *PDEA / *PEND / *PIO / *PMIO / *PRGS / *PRGT / *PRTY / *RELM / *REQM / *SDV / *SLOT / *SNAP / *STD1 / *STDI / *STDN / *SVC / *TGMA / *TGMP / *TGMT / *TIC / *TINF / *TLM / *TLT / *TS
Statements for SM2 administrators REMOVE-FILE REMOVE-FILE Remove file(s) from FILE monitoring parameters Function This statement is used to define the file(s) to be removed from the FILE monitoring program definition. Format REMOVE-FILE FILE-NAME = *ALL / Operands FILE-NAME = FILE-NAME = *ALL All files previously included in the monitoring process are now to be excluded. FILE-NAME = Specifies the name of the file to be excluded from the monitoring process.
REMOVE-ISAM-POOL Statements for SM2 administrators REMOVE-ISAM-POOL Remove ISAM pool(s) from ISAM monitoring parameters Function This statement is used to define the ISAM pool(s) to be removed from the ISAM monitoring program definition. Format REMOVE-ISAM-POOL POOL-NAME = *ALL / ,SCOPE = *ANY / *HOST-SYSTEM / *TASK(...) / *USER(...) *TASK(...) TSN = *USER(...) USER-ID = ,CAT-ID = *ANY / *HOME-PVS /
Statements for SM2 administrators REMOVE-ISAM-POOL SCOPE = *TASK(...) The pool is a task-specific ISAM pool. TSN = Specifies the TSN of the task under which the task-specific ISAM pool has been set up. SCOPE = *USER(...) The pool is a user-specific ISAM pool. USER-ID = Specifies the user ID under which the ISAM pool has been set up. This must be specified without the “$” sign.
SELECT-HOSTS Statements for SM2 administrators SELECT-HOSTS Define hosts for SM2 statements and screen output Function This statement is used to define the hosts for which SM2 administration statements are to apply and for which screens are to be output. If reports are output, the selected remote hosts send their monitored data to the local host. The statement only works locally for the user who issues it. Any caller with administration rights can define his or her own list of hosts.
Statements for SM2 administrators SELECT-HOSTS Note The host name uniquely identifies a host in a processor network. This name must be specified in the SELECT-HOSTS statement and is output on the screens as the host name. Note that when an HIPLEX MSCF connection is set up, a processor name must be specified. The processor name can be different from the host name. The processor name only identifies a system locally for one other system, not globally for the whole network.
SET-BCAM-CONNECTION-PARAMETER Statements for SM2 administrators SET-BCAM-CONNECTION-PARAMETER Define BCAM-CONNECTION monitoring parameters Function This statement is used to define the global monitoring parameters for the BCAM-CONNECTION monitoring program. Format SET-BCAM-CONNECTION-PARAMETER INWAIT-BUCKETS = *STD-LIMITS / *UNCHANGED / list-poss(4): ,REACT-BUCKETS = *STD-LIMITS / *UNCHANGED / list-poss(4):
Statements for SM2 administrators SET-BCAM-CONNECTION-PARAMETER REACT-BUCKETS = list-poss(4): Defines the upper limits of the ranges for REACT times. These must be specified in ascending order. INPROC-BUCKETS = Defines the upper limits of up to four ranges (in units of 1 ms) in which the INPROC times are to be stored by order of magnitude. INPROC-BUCKETS = *STD-LIMITS Sets the upper limits of the ranges for INPROC times to 100, 200, 500 and 1000 ms.
SET-CHANNEL-IO-PARAMETER Statements for SM2 administrators SET-CHANNEL-IO-PARAMETER Define CHANNEL-IO monitoring parameters Function This statement is used to define the channels for the CHANNEL-IO monitoring program. Format SET-CHANNEL-IO-PARAMETER CHANNELS = *ALL / list-poss(64): Operands CHANNELS = CHANNELS = *ALL All channels are to be monitored. CHANNELS = list-poss(64): Specifies the channel addresses (channel path IDs) of the channels to be monitored.
Statements for SM2 administrators SET-COSMOS-PARAMETER SET-COSMOS-PARAMETER Define COSMOS monitoring parameters Function This statement is used to define the monitoring parameters for the COSMOS monitoring program. The mandatory events CREA, DEST, INIT, LGON, MMRC, PTSK and STAT are defined automatically. Events specified beforehand with the ADD-COSMOS-EVENT statement remain in the monitoring program definition. The files specified with OUTPUT and ADDITIONAL-INFO=*VM2000 must already be created.
SET-COSMOS-PARAMETER Statements for SM2 administrators (part 2 of 2) *TAPE(...) FILE-NAME = list-poss(16): *STREAM-TAPE(...) FILE-NAME = list-poss(16): ,TASK-SELECTION = *ALL / *SPECIFIED(...) *SPECIFIED(...) JOB-NAME = *NOT-SPECIFIED / list-poss(8): ,CATEGORY = *NOT-SPECIFIED / list-poss(8):
Statements for SM2 administrators SET-COSMOS-PARAMETER Operands TITLE = Specifies the title of the COSMOS monitoring process. TITLE = C’COSMOS’ Sets the title of the COSMOS monitoring process to “COSMOS”. TITLE = Sets the title of the COSMOS monitoring process to the value specified here. BUFFER-SIZE = Specifies the number of 4K pages per buffer. BUFFER-SIZE = 2 The buffers created have a default size of two pages. BUFFER-SIZE =
SET-COSMOS-PARAMETER Statements for SM2 administrators OUTPUT = *DISK(...) The COSMOS monitored data is written sequentially to the files on hard disk; i.e. there is one write task for each output file. If a monitored data buffer is full, a write task is activated that writes the buffer to the appropriate file. FILE-NAME = list-poss(16): Specifies the file(s) to which the COSMOS monitored data is written. OUTPUT = *WRAP-AROUND(...
Statements for SM2 administrators SET-COSMOS-PARAMETER CATEGORY = The tasks are selected by means of their category. CATEGORY = *NOT-SPECIFIED No tasks are selected by means of their category. CATEGORY = list-poss(8): Specifies the categories of the tasks to be monitored. An asterisk (*) is also permitted as the last character in a wildcard specification. USER-ID = The tasks are selected by means of their user ID.
SET-COSMOS-PARAMETER Statements for SM2 administrators EVENT-SELECTION = *ALL-BY-ADD-COSMOS-EVENT All open events are recorded. EVENT-SELECTION = *SPECIFIED(...) Only those events that satisfy the specified conditions are recorded. EIA-INTERRUPT-CLASS = Controls the recording of EIA events on the basis of their interrupt class (IC). EIA-INTERRUPT-CLASS = *ANY The recording of EIA events is independent of their IC.
Statements for SM2 administrators SET-COSMOS-PARAMETER SLOT-MEMORY-CLASS = Controls the recording of SLOT events on the basis of their memory class. SLOT-MEMORY-CLASS = *ANY The recording of SLOT events is independent of their memory class. SLOT-MEMORY-CLASS = list-poss(4): *3 / *4 / *5 / *6 Only those SLOT events with the specified memory classes are recorded. PEND-CODE = Controls the recording of PEND events on the basis of their pend code.
SET-COSMOS-PARAMETER Statements for SM2 administrators TSVC-SVC-NUMBER = list-poss(8): The TSVC events are recorded for the specified SVC numbers. UNLOAD = Specifies the time at which the COSMOS subsystem is to be unloaded. UNLOAD = *AT-MEASUREMENT-PROGRAM-STOP The COSMOS subsystem is unloaded at the end of COSMOS monitoring. UNLOAD = *AT-SM2-STOP The COSMOS subsystem is unloaded at the end of SM2 monitoring. MEASUREMENT-TIME = Specifies the duration of the monitoring process.
Statements for SM2 administrators SET-DISK-PARAMETER SET-DISK-PARAMETER Define DISK monitoring parameters Function This statement is used to define the disk devices for the DISK monitoring program. Format SET-DISK-PARAMETER DEVICES = list-poss(256): Operands DEVICES = list-poss(256): Specifies the mnemonic device names of the disk devices to be monitored.
SET-DISK-FILE-PARAMETER Statements for SM2 administrators SET-DISK-FILE-PARAMETER Define DISK-FILE monitoring parameters Function This statement is used to define the disk devices for the DISK-FILE monitoring program. Format SET-DISK-FILE-PARAMETER DEVICES = list-poss(8): Operands DEVICES = list-poss(8): Specifies the mnemonic device names of the disk devices to be monitored.
Statements for SM2 administrators SET-PERIODIC-TASK-PARAMETER SET-PERIODIC-TASK-PARAMETER Define PERIODIC-TASK monitoring parameters Function This statement is used to define the tasks from which monitored data is to be written to the SM2 output file for the PERIODIC-TASK monitoring program. Format SET-PERIODIC-TASK-PARAMETER LOG-TASKS = *NONE / *ALL / *SPECIFIED(...) *SPECIFIED(...) USER-ID = *NOT-SPECIFIED / list-poss(64):
SET-PERIODIC-TASK-PARAMETER Statements for SM2 administrators JOB-NAME = Tasks are selected on the basis of their job names. JOB-NAME = *NOT-SPECIFIED Tasks are not selected on the basis of their job names. JOB-NAME = list-poss(64): Monitored data on the tasks with the specified job names is written to the SM2 output file.
Statements for SM2 administrators SET-RESPONSETIME-PARAMETER SET-RESPONSETIME-PARAMETER Define RESPONSETIME monitoring parameters Function This statement is used to define the monitoring parameters for the RESPONSETIME monitoring program. Format SET-RESPONSETIME-PARAMETER SCOPE = *BUCKET / list-poss(2): *BUCKET / *CATEGORY ,DEFINITION = *1 / *2 ,CONNECTION-NUMBER = *1024 / ,RESPONSETIME-BUCKETS = *STD-LIMITS / list-poss(5):
SET-RESPONSETIME-PARAMETER Statements for SM2 administrators DEFINITION = Defines the type of response time to be monitored. DEFINITION = *1 This response time is the time between user input and the next output operation. DEFINITION = *2 In addition to the response time defined with 1, the times between follow-up output operations to an input are recorded individually as response times. CONNECTION-NUMBER = Defines the maximum number of connections to be monitored.
Statements for SM2 administrators SET-RESPONSETIME-PARAMETER TRANSACTTIME-BUCKETS = Defines the upper limits of up to five ranges (in units of 100ms) in which the transaction times are to be stored by order of magnitude. TRANSACTTIME-BUCKETS = *STD-LIMITS Sets the upper limits of the ranges for transaction times to 5, 10, 20, 50 and 100. TRANSACTTIME-BUCKETS = list-poss(5): Defines the upper limits of the ranges for transaction times. These must be specified in ascending order.
SET-SERVICETIME-PARAMETER Statements for SM2 administrators SET-SERVICETIME-PARAMETER Define SERVICETIME monitoring parameters Function This statement is used to define the devices for the SERVICETIME monitoring program. Format SET-SERVICETIME-PARAMETER DEVICES = list-poss(256): Operands DEVICES = list-poss(256): Specifies the mnemonic device names of the devices to be monitored.
Statements for SM2 administrators SET-SYSSTAT-PARAMETER SET-SYSSTAT-PARAMETER Define SYSSTAT monitoring parameters Function This statement is used to define the devices for the SYSSTAT monitoring program. Format SET-SYSSTAT-PARAMETER USED-DEVICES = *NONE / *ALL / list-poss(64): *DISK / *TAPE / Operands USED-DEVICES = USED-DEVICES = *NONE No devices are to be monitored by the SYSSTAT monitoring program.
SET-TASK-PARAMETER Statements for SM2 administrators SET-TASK-PARAMETER Define TASK monitoring parameters Function This statement is used to define the tasks and devices for the TASK monitoring program. All tasks can be selected, but this results in a higher system load. Tasks can be explicitly defined using a list of TSNs, user IDs, job names and job classes. Tasks can also be selected for monitoring by specifying a task attribute.
Statements for SM2 administrators SET-TASK-PARAMETER TSN = TSN = *NOT-SPECIFIED No tasks are selected using the TSN. TSN = list-poss(64): Specifies the TSNs of the tasks to be monitored. A task with the specified TSN is, however, only monitored if it already existed when the task monitoring program was started. USER-ID = USER-ID = *NOT-SPECIFIED No tasks are selected using the user ID. USER-ID = list-poss(32): Specifies the user ID of the tasks to be monitored.
SET-TASK-PARAMETER Statements for SM2 administrators TYPE = The tasks to be monitored are selected via their task attribute. All tasks with the attributes specified at selection time using the START-MEASUREMENT-PROGRAM or LOGON command are monitored. If the task attribute of a task is changed in the course of the monitoring program session, this will not influence the measurement itself, i.e. the task is neither excluded from nor included in monitoring as a result.
Statements for SM2 administrators SHOW-ACTIVE-PARAMETER SHOW-ACTIVE-PARAMETER Output active monitoring parameters Function This statement is used to output the current objects and monitoring parameters for each active monitoring program.
SHOW-ACTIVE-PARAMETER Statements for SM2 administrators TYPE = *ISAM Outputs the objects and monitoring parameters for the active privileged ISAM monitoring program. TYPE = *PERIODIC-TASK Outputs the objects and monitoring parameters for the active PERIODIC-TASK monitoring program. TYPE = *RESPONSETIME Outputs the objects and monitoring parameters for the active RESPONSETIME monitoring program. TYPE = *SERVICETIME Outputs the objects for the active SERVICETIME monitoring program.
Statements for SM2 administrators SHOW-DEFINED-PARAMETER SHOW-DEFINED-PARAMETER Output defined monitoring parameters Function This statement is used to output the objects and monitoring parameters currently defined for each definable monitoring program.
SHOW-DEFINED-PARAMETER Statements for SM2 administrators TYPE = *DISK-FILE Outputs the objects for the active DISK-FILE monitoring program. TYPE = *FILE Outputs the objects for the active privileged FILE monitoring program. TYPE = *ISAM Outputs the objects and monitoring parameters for the active privileged ISAM monitoring program. TYPE = *PERIODIC-TASK Outputs the objects and monitoring parameters for the active PERIODIC-TASK monitoring program.
Statements for SM2 administrators SHOW-MEASUREMENT-STATUS SHOW-MEASUREMENT-STATUS Output monitoring status Function This statement is used to output the MEASUREMENT STATUS screen.
SHOW-SELECTED-HOSTS Statements for SM2 administrators SHOW-SELECTED-HOSTS Output selected hosts Function This statement is used to output the hosts selected with the SELECT-HOSTS statement. The display includes the host name, the processor name (from the point of view of the host from which the statement was issued), and the time of the last monitored data queried. If a new file is not available, the message “RSLT NOT VALID” may be output in place of the clock.
Statements for SM2 administrators SHOW-SM2-STATUS SHOW-SM2-STATUS Output status of SM2 system tasks Function This statement is used to output information on the status of individual SM2 system tasks and of the subsystems used by SM2. Format SHOW-SM2-STATUS INFORMATION = *STD / *TASK / *EVENT-TRACE(...) *EVENT-TRACE(...) FROM = *ACTUAL / Operands INFORMATION = Provides information on the status of the SM2 system components.
SHOW-SM2-STATUS Statements for SM2 administrators FROM = Specifies the position as of which the trace entries are to be output. The position specified corresponds to the most recent entry (the one with the highest number). If trace entries which do not yet exist are selected, the most recent ones are output. The fact that the trace buffer is overwritten cyclically means that it is possible that the required entries are no longer all available. The last available entry is marked with the symbol "===>".
Statements for SM2 administrators SHOW-USER-MEASURED-OBJECTS SHOW-USER-MEASURED-OBJECTS Output monitored objects and associated users Function This statement is used to output the objects currently being monitored by users, together with the associated users. Depending on the user’s system privileges (see table “Table of authorizations” on page 13), the display includes either the user’s own objects or all users’ objects.
START-MEASUREMENT-PROGRAM Statements for SM2 administrators START-MEASUREMENT-PROGRAM Start monitoring program run Function This statement is used to start the monitoring programs specified under TYPE.
Statements for SM2 administrators START-MEASUREMENT-PROGRAM TYPE = *DLM Starts the DLM monitoring program. TYPE = *FILE Starts the FILE monitoring program. TYPE = *GS Starts the GS monitoring program. TYPE = *GSVOL Starts the GSVOL monitoring program. TYPE = *HSMS Starts the HSMS monitoring program. TYPE = *ISAM Starts the ISAM monitoring program. TYPE = *MSCF Starts the MSCF monitoring program. TYPE = *NET-DEVICE Starts the NET-DEVICE monitoring program. TYPE = *NSM Starts the NSM monitoring program.
START-MEASUREMENT-PROGRAM Statements for SM2 administrators TYPE = *TASK Starts the TASK monitoring program. TYPE = *TCP-IP Starts the TCP-IP monitoring program. TYPE = *TLM Starts the TLM monitoring program. TYPE = *UTM Starts the UTM monitoring program. TYPE = *VM Starts the VM monitoring program.
Statements for SM2 administrators STOP-MEASUREMENT-PROGRAM STOP-MEASUREMENT-PROGRAM Terminate monitoring program run Function This statement is used to terminate the monitoring programs specified under TYPE.
STOP-MEASUREMENT-PROGRAM Statements for SM2 administrators TYPE = *DISK-FILE Terminates the DISK-FILE monitoring program. TYPE = *DLM Terminates the DLM monitoring program. TYPE = *FILE Terminates the FILE monitoring program. TYPE = *GS Terminates the GS monitoring program. TYPE = *GSVOL Terminates the GSVOL monitoring program. TYPE = *HSMS Terminates the HSMS monitoring program. TYPE = *ISAM Terminates the ISAM monitoring program. TYPE = *MSCF Terminates the MSCF monitoring program.
Statements for SM2 administrators STOP-MEASUREMENT-PROGRAM TYPE = *SYSSTAT Terminates the SYSSTAT monitoring program. TYPE = *TASK Terminates the TASK monitoring program. TYPE = *TCP-IP Terminates the TCP-IP monitoring program. TYPE = *TLM Terminates the TLM monitoring program. TYPE = *UTM Terminates the UTM monitoring program. TYPE = *VM Terminates the VM monitoring program.
Statements for nonprivileged users SM2 operation 4.4 Statements for nonprivileged users These statements enable the nonprivileged user to select monitored data for output and control the screen output. They can also be used by the SM2 administrator provided he/she switches to the analysis subinterval using the CALL-EVALUATION-PART statement.
SM2 operation Statements for nonprivileged users Statement Function CHANGE-ISAM-STATISTICS Include and exclude ISAM pools STOP-ISAM-STATISTICS Terminate the monitoring of ISAM pools Statements for controlling reports The following statements are used to control reports. Statement Function OUTPUT Define the output mode. Reports are output either automatically at regular intervals (automatic output mode) or at the request of the user (controlled mode).
Statements for nonprivileged users SM2 operation In controlled mode, the individual reports are output at the request of the user, i.e. the user can control SM2 report output or enter another statement. The following scroll commands are available for controlling the output of SM2 reports which may comprise one or more screens: 1. ++ selects the first screen of the first report of the next monitoring cycle. 2. - - selects the first screen of the first report of the current monitoring cycle. 3.
SM2 operation Statements for nonprivileged users Starting report output Report output is started with the START or RESTART statement. In the case of the START statement, new monitoring data is obtained from the central buffer of SM2 and then output. In the case of the RESTART statement, reports are output with the data of the last START statement. SM2 enters the monitoring data in output forms called reports. Their format is fixed and cannot be modified by the user.
Statements for nonprivileged users SM2 operation Depending on the output mode and the length of the two cycles, the following situations are possible: A Automatic output mode A1 Monitoring cycle and output cycle have the same length Zeit Meßintervalle Zeit Meßintervalle Ausgabeintervalle Monitored data acquisition and report output take place at intervals of the same length If the system load is high, the time required for output to the terminal may be considerably increased; this may result in t
SM2 operation A3 Statements for nonprivileged users Monitoring cycle shorter than output cycle Zeit Meßintervalle Ausgabeintervalle Monitored data is lost because the central buffer of the monitoring task is cleared faster than the data is output during the output cycle. B Controlled mode If the user does not succeed in having all the reports of a monitoring cycle output before the central buffer is filled again by the monitoring tasks, some monitoring cycles will be lost.
Statements for nonprivileged users SM2 operation Statement for outputting information The STATUS statement outputs the SM2-MEASUREMENT STATUS screen. Statement Function STATUS Output the monitoring status General statements The following statements control the SM2 run of the user (BREAK, END) and provide assistance as required (HELP, REMARK).
Statements for nonprivileged users BREAK BREAK Switch to system mode Function This statement is used to interrupt SM2 processing and switch to the system’s command mode.
CHANGE-ISAM-STATISTICS Statements for nonprivileged users CHANGE-ISAM-STATISTICS Include and exclude ISAM pools Function This statement is used to include and exclude ISAM pools in the monitoring process. ISAM pools can only be monitored if this is permitted by the SM2 primary administrator. If this is the case, the entry ISAM appears in the USER MEASUREMENTS ALLOWED line of the SM2 MEASUREMENT STATUS screen. SM2 supports the simultaneous monitoring of up to 16 ISAM pools for the set of all users.
Statements for nonprivileged users CHANGE-ISAM-STATISTICS =*NONE No ISAM pools are included in the monitoring process (default). =*POOL() Defines which ISAM pools are to be monitored. Up to 16 ISAM pools can be defined in one list. POOL-NAME =poolname1 Defines a pool name up to 8 characters in length. SCOPE Defines the type of ISAM pool. =*HOST-SYSTEM The pool is a global ISAM pool (default). =*TASK() The pool is a task-specific ISAM pool.
DEVICE Statements for nonprivileged users DEVICE Select devices with monitored data Function This statement is used to select the devices and monitored data to be output in the DEVICE report: ● disk devices with the greatest amount of activity during the monitoring cycle (default value) ● other devices with the greatest amount of activity during the monitoring cycle ● devices to which the user has assigned a high output priority The statement also defines devices which are no longer output individua
Statements for nonprivileged users DEVICE Format Operation DEVICE Operands *DISK *ALL + dev-name] [ - + [ dev-name] - Operands *DISK Specifies the monitored data of up to 8 disk devices with the greatest activity during the monitoring cycle. The disk devices are sorted in descending order according to activity, and the DEVICE report includes their monitored data. This operand is predefined at program start time.
DEVICE Statements for nonprivileged users + Defines devices whose monitored data is to be output separately. The monitored data is output only if the device was not active during the monitoring cycle. If the user has assigned a high output priority to less than eight devices and at least eight devices in total were active and the user did not withdraw priority from them, SM2 will take the free space and give it the monitoring data of other active devices.
Statements for nonprivileged users END END Terminate monitoring Function This statement is used to terminate the SM2 run for the user.
FILE Statements for nonprivileged users FILE Monitor files Function This statement is used to select one or more files whose monitored data is to be output in the next monitoring cycle or is no longer to be output. The user may only include files in the monitoring process if this is permitted by the SM2 primary administrator. If this is the case, the entry FILE appears in the USER MEASUREMENTS ALLOWED line of the SM2 MEASUREMENT STATUS screen.
Statements for nonprivileged users HELP HELP Request user help information Function This statement is used to request an overview of all SM2 statements. Format Operation Operands HELP Output includes the statement name followed by a brief explanation of the statement.
OUTPUT Statements for nonprivileged users OUTPUT Define output mode Function This statement is used to: ● define the device (data display terminal and/or printer) to which the reports are output, and ● define the mode of output. Reports are output either automatically at regular intervals (automatic output mode) or at the request of the user (controlled mode).
Statements for nonprivileged users INTERVAL =number OUTPUT Specifies the output mode. Specifies automatic output mode (see page 154). “number” defines the output cycle during which the reports are to be output at regular intervals. This can be an integer between 10 and 3600 seconds. The INTERVAL=number specification is not mandatory. If it is omitted, SM2 inserts the value for the output cycle by using the value of the online monitoring cycle (default).
REMARK Statements for nonprivileged users REMARK Insert remarks Function This statement is used to insert remarks in order to document procedures. Format Operation Operands REMARK [any text] Operands any text 168 Any text can be inserted; the text can extend beyond more than one line. Continuation lines must be marked by means of a hyphen (continuation symbol). See also “Length of the statements” on page 423 of the Appendix.
Statements for nonprivileged users REPORT REPORT Select reports Function This statement is used to select the reports to be output. Format Operation Operands REPORT STD ALL + [ - report-type ] + [ report-type ] - Operands STD Selects the following reports: – – – – ACTIVITY report MEMORY report CHANNEL report DEVICE report for output in the same order as shown above.
REPORT Statements for nonprivileged users + [ report-type]... - Updates the list of reports to be output. “report-type” designates the output reports, the identifiers of which are as follows: Report ID Guarant. abbrev.
Statements for nonprivileged users REPORT Report ID Guarant. abbrev. Report name POSIX POS POSIX report RESPONSE R, RES RESPONSETIME report SHARED_PVS SHA SHARED PVS report SVC SVC report SYMMETRIX SYM SYMMETRIX report TCP_IP TCP TCP/IP report TLM TLM report UTM UTM report VM VM2000 report 1) For nonprivileged users, the PERIODIC TASK report contains only those tasks under their own user ID.
RESTART Statements for nonprivileged users RESTART Start output of selected reports Function This statement is used to start the output of reports with the data of the last START statement. Thus, unlike the START statement, it does not retrieve new monitored data from the central buffer of SM2. The advantage of this for SM2 users is that new control and output statements can take effect before the next monitoring cycle. It only makes sense to use the RESTART statement in controlled mode.
Statements for nonprivileged users SELECT-DAB-CACHE SELECT-DAB-CACHE Select DAB cache Function This statement is used to select one or more DAB caches to be displayed in the DAB report. For each selected DAB cache, a DAB-CACHE report is then output containing monitored data on the subareas or files. Format Operation Operands SELECT-DAB-CACHE cache-id [ADD-CACHE-ID = ] (cache-id1[,cache-id2]...) [,REMOVE-CACHE-ID = cache-id (cache-id1[,cache-id2]...
SELECT-PCA-CACHE Statements for nonprivileged users SELECT-PCA-CACHE Select cache for PCA DEVICE report Function This statement is used to select one or more caches of a controller to be displayed in the PCA CACHE report. For each selected cache, a PCA DEVICE report is then output containing monitored data on the individual devices supported by the cache. Format Operation Operands SELECT-PCA-CACHE *NONE *ALL CACHE = number1 ((CONTROLLER=cont1,CACHE-ID= *ALL )[,...
Statements for nonprivileged users SELECT-PCA-CACHE CACHE-ID=*ALL All caches of the superordinate controller are to be taken into account when outputting the PCA DEVICE report (default). Note It is possible to specify up to 32 pairs of controllers and caches.
SELECT-PCA-CONTROLLER Statements for nonprivileged users SELECT-PCA-CONTROLLER Select controllers for PCA CACHE report Function This statement is used to select one or more controllers to be displayed in the PCA CONTROLLER report. For each selected controller, a PCA CACHE report is then output containing monitored data on the controller caches. Format Operation Operands SELECT-PCACONTROLLER *NONE *ALL CONTROLLER = controller (controller1[,controller2]...
Statements for nonprivileged users SELECT-PERIODIC-TASK-PARAMETER SELECT-PERIODIC-TASK-PARAMETER Select sort criterion and output information for PERIODIC TASK report Function This statement is used to specify the sort criterion and output information for the PERIODIC TASK report. Nonprivileged users can only select tasks belonging to their own user ID. Format Operation SELECT-PERIODICTASK-PARAMETER Operands *ALL USER-ID (userid1[,userid2]...
SELECT-PERIODIC-TASK-PARAMETER =JOB-NAME(...) Statements for nonprivileged users Outputs job names. *ALL: All tasks are output. The job name can only be output if it exists (default). jobname: The tasks with the specified job names (up to 16) are output. SORT Specifies sort criteria. A PERIODIC TASK report is created for each sort criterion specified. =SERVICE-UNITS, CPU, IO, UPG, PAGING-READ The tasks are sorted on the basis of the specified criteria.
Statements for nonprivileged users SELECT-PFA-CACHE SELECT-PFA-CACHE Select PFA cache Function This statement is used to request a PFA CONTROLLER report for specific caches listed in the PFA CACHE report. The PFA CONTROLLER report can only be output for caches served by PCA and provides monitored data for the various controllers assigned to the pubset disks served by the caches.
SELECT-SYMMETRIX-CONTROLLER Statements for nonprivileged users SELECT-SYMMETRIX-CONTROLLER Select SYMMETRIX controllers Function This statement is used to select up to 16 SYMMETRIX controllers to be displayed in the SYMMETRIX CONTROLLER report. For each selected controller, a SYMMETRIX DEVICE report is then output containing monitored data on the individual devices supported by the controller.
Statements for nonprivileged users SELECT-SYMMETRIX-CONTROLLER REMOVE-CONTROLLER-MN =controller-mn Defines the controllers for which SYMMETRIX DEVICE reports are no longer to be output using the first controller mnemonic. The following two mnemonic variants are available: – – alphanum-name 2..2 x-text 4..4 In this statement, you need only specify the first controller mnemonic. It is possible to define up to 16 controller mnemonics.
SELECT-UTM-APPLICATION Statements for nonprivileged users SELECT-UTM-APPLICATION Select UTM applications Function This statement is used to select up to 16 UTM applications to be displayed in the UTM report. For each selected UTM application, a UTM APPLICATION report is then output. Format Operation Operands SELECT-UTMAPPLICATION name [ADD-APPLICATION = ] (name1[,name2]...) [,REMOVE-APPLICATION = name (name1[,name2]...
Statements for nonprivileged users SHOW-USER-MEASURED-OBJECTS SHOW-USER-MEASURED-OBJECTS Output monitored objects Function This statement is used to show an SM2 user the objects he/she is currently monitoring. Format Operation Operands SHOW-USERMEASURED-OBJECTS TYPE = TASK Operands TYPE =TASK U3585-J-Z125-8-76 Outputs the user’s tasks currently being monitored by the userspecific task monitoring program.
START Statements for nonprivileged users START Start report output Function This statement is used to start report output.
Statements for nonprivileged users START-ISAM-STATISTICS START-ISAM-STATISTICS Monitor ISAM pools Function This statement is used to select one or more ISAM pools whose monitored data is to be output in the next monitoring cycle. The user may include ISAM pools in the monitoring process only if the SM2 primary administrator has authorized the monitoring of ISAM pools. If this is the case, the entry ISAM appears in the USER MEASUREMENTS ALLOWED line of the SM2 MEASUREMENT STATUS screen.
START-ISAM-STATISTICS Statements for nonprivileged users Operands POOL =(*POOL(...)) Defines which ISAM pools are to be monitored. Up to 16 ISAM pools can be defined in one list. POOL-NAME =poolname1 SCOPE Defines a pool name of up to 8 characters in length. Defines the type of ISAM pool. =*HOST-SYSTEM The pool is a global ISAM pool (default). =*TASK(...) The pool is a task-specific ISAM pool. The TSN operand defines the task to which the ISAM pool belongs.
Statements for nonprivileged users STATUS STATUS Output monitoring status Function This statement is used to output the MEASUREMENT STATUS screen.
STOP-ISAM-STATISTICS Statements for nonprivileged users STOP-ISAM-STATISTICS Terminate monitoring of ISAM pools Function This statement is used to terminate monitoring of the ISAM pools previously included in the monitoring process. Format Operation Operands STOP-ISAM-STATISTICS Note If permission to monitor the ISAM pools has been withdrawn by the SM2 primary administrator, all ISAM pools previously included in the output are automatically excluded.
SM2 operation Activating user task monitoring 4.5 BS2000 commands for activating user task monitoring Any user can have SM2 monitor tasks under his/her own ID, provided the SM2 primary administrator has given permission for user task monitoring (by issuing the SM2 statement MODIFY-USER-ADMISSION TASK=*ALLOW. The total number of tasks which can be monitored simultaneously is limited to 16).
Activating user task monitoring SM2 operation Formats START-TASK-MEASUREMENT TSN = *OWN / ,FILE = *STD / *BY-LINK-NAME ,PCOUNTER-INTERVAL = *NONE / ,SVC-STATISTICS = *OFF / *ON ,LOAD-INFO = *STD / *DETAILED STOP-TASK-MEASUREMENT TSN = *OWN / Operands TSN = Specifies the task to be monitored or for which monitoring is to be terminated. TSN = *OWN The task invoking the command will be monitored or monitoring of that task will be terminated.
SM2 operation Activating user task monitoring PCOUNTER-INTERVAL = Defines the sampling cycle for command counter statistics (in CPU milliseconds). PCOUNTER-INTERVAL = *NONE The command counter is not activated. PCOUNTER-INTERVAL = Sampling cycle in CPU milliseconds. The only samples recorded are those with the status TU. SVC-STATISTICS = The SVC macros of the task to be measured are recorded and written to the user-specific SM2 output file.
Activating user task monitoring SM2 operation Command return codes (SC2) SC1 0 32 64 64 64 Maincode CMD0001 NPS0050 NPS0044 NPS0045 NPS0046 64 64 64 64 64 NPS0047 NPS0051 NPS0065 NPS0066 NPS0067 Meaning/guaranteed messages No errors System error in SM2 modules, command rejected No authorization for monitoring task, command rejected Task already monitored by SM2 Task monitoring not started by /START-TASKMEASUREMENT, command rejected Specified task does not exist User cannot monitor specified task Cann
SM2 operation Activating user task monitoring Attributes of the user-specific SM2 output file Operand for file creation FILE =*STD FILE =*BY-LINK-NAME Predefined Optional $userid.SM2. TASKSTATISTIK.
Activating user task monitoring SM2 operation Under certain circumstances SM2 can only supply incomplete information or none at all: 194 – If the program to be monitored uses overlay techniques, the module loading information should be recorded using LOAD-INFO=DETAILED. If this is not done, the samples and SVCs for all overlaid modules are assigned to the module loaded at the time monitoring is terminated. – No information will be supplied for modules/subsystems loaded as SHARED.
SM2 operation SM2 output file 4.6 Writing to the SM2 output file Introduction In addition to report output at the terminal and on the printer, consecutive output of monitored data to the SM2 output file is provided for. At file creation time, a system task is generated for writing to the SM2 output file. This system task terminates when the SM2 output file is closed.
SM2 output file SM2 operation SM2 output file with freely selected file attributes Such a file is created with the statement OPEN-LOG-FILE FILE=*BY-LINK-NAME after the name and attributes have been defined with the ADD-FILE-LINK command. It is possible to define – – a PAM file in output mode with a freely selectable name, or a SAM file with freely selectable open mode and file name.
SM2 operation SM2 output file 1) It is advisable to select a file name that indicates the date and time of file creation, so as to facilitate file sequencing in the input order required by SM2U1. 2) Only block lengths of 16 are used. If no block length is specified, this is set to 16 by SM2. If BUFFER-LENGTH is specified without the SPACE operand, SM2 uses the default value 512 for the primary storage allocation and for the secondary storage allocation.
SM2 output file SM2 operation SAM output file The SAM output file format is logically similar to the PAM output file format. An advantage of SAM output files is that they need not be converted before the SM2R1 analysis routine is called (see the chapter “SM2U1 utility routine” in Volume 2 of the SM2 manual [21]). In the OUTPUT open mode, a new SAM output file can be created or a file can be replaced by another file with the same name.
SM2 operation Examples 4.7 SM2 monitoring program: examples Example 1 This simple example illustrates how SM2 is started and stopped again later on. The following default options are used: – – monitoring cycle: 150 seconds sampling cycle: 800 milliseconds Reports A (ACTIVITY), M (MEMORY), C (CHANNEL) and D (DEVICE) are output at the terminal in automatic output mode. SM2 is interrupted after some time with the BREAK function (terminal key) and terminated. /START-SM2 START . (Output of the reports) . .
Examples SM2 operation /START-SM2 CALL-ADMINISTRATION-PART SET-RESPONSETIME-PARAMETER START-MEASUREMENT-PROGRAM TYPE=*RESPONSETIME OPEN-LOG-FILE FILE=*STD END . . . . /START-SM2 CALL-ADMINISTRATION-PART STOP-MEASUREMENT-PROGRAM TYPE=*RESPONSETIME CLOSE-LOG-FILE END Example 3 In this example, SM2 is started with data output to the SM2 output file. The file is given the default name SM2.hostname.yyyy.mm.dd.sss.nn. The monitoring cycle is set to 20 seconds and the sampling cycle to 200 ms.
5 SM2 screen output The monitoring task collects monitored data during an online monitoring cycle, edits it, and enters it in the central buffer when the online monitoring cycle is completed. From the central buffer, each SM2 user task transfers the data into its own buffer and enters it in output forms called reports.
SM2 reports SM2 screen output SM2 reports The monitored data is broken down into factually related groups and entered in various reports. The following reports may be output without the SM2 administrator having to activate an optional monitoring program.
SM2 screen output SM2 reports The following reports can only be output if the SM2 administrator has activated the corresponding optional monitoring program beforehand or authorized the appropriate user monitoring operations (MODIFY-USER-ADMISSION): BCAM CONNECTION report Overview of bucket-specific time statistics and information on data sent and received CATEGORY report Overview of the consumption statistics of all categories CHANNEL report Overview of the current channel occupancy.
SM2 reports 204 SM2 screen output PFA CACHE report Overview of the use of various caches (for more detailed information, see the PFA CONTROLLER report) POSIX report Output of the monitoring data of the POSIX subsystem RESPONSETIME report Overview of the response time behavior throughout the system SVC report Overview of the number of SVCs called SYMMETRIX CONTROLLER report Overview of the utilization of SYMMETRIX controllers (for more detailed information, see the SYMMETRIX DEVICE report) SYMME
SM2 screen output SM2 information screens SM2 information screens The information screens are special in that they contain no monitored data, but provide information on the monitoring run and on the SM2 status. These screens are only output if explicitly requested by the user. The first two screens listed are available in both the analysis subinterval and the administration facility. The others are only available to privileged users in the administration facility.
SM2 information screens SM2 screen output The header line of each screen contains global information, namely: CYCLE Duration of the (online) monitoring cycle in seconds, i.e. period after which the collected values are available for output SAMPLES Number of samples taken within the (online) monitoring cycle These values are output if they are relevant to the current screen. The host name is output in the top left-hand corner. The date and time are output in the top right-hand corner of the screen.
SM2 screen output Output sequence Output sequence Report name Identifiers GLOBAL N O NSM N O SHARED PVS N O M ACTIVITY MEMORY CHANNEL O M 1) O M DEVICE PERIODIC TASK PRIVILEGED FILE M USER FILE P RESPONSETIME M ACF CATEGORIE QUEUE CATEGORIE WSET PCS DAB O M O M CMS O M UTM O M DAB CACHE UTM APPLICATION F F M PRIVILEGED ISAM M USER ISAM P VM2000 M TLM M PCA CONTROLLER O M PCA CACHE F O M PCA DEVICE F O M CPU O SVC M PFA CACHE PFA CONTROLLER F
Output sequence SM2 screen output Report name Identifiers POSIX M CATEGORIE M MSCF M NET DEVICE O DLM M M GSVOL O M GS O M TCP IP O M BCAM CONNECTION O M DISK FILE O M SYMMETRIX CONTROLLER O M O M SYMMETRIX DEVICE F Table 7: Output sequence N: F: O: M: P: Network report Follow-up screen requested by means of a special statement Report containing an overflow screen for further monitored objects Monitoring program must be activated Monitoring process must be permitted for
SM2 reports ACF report 5.1 SM2 reports ACF report This report supplies information on the activation control function (ACF) of the PRIOR task scheduler. The data can be used to assess the internal activation decisions. Data interpretation and consequential actions presuppose intimate familiarity with the activation algorithm used in the PRIOR task scheduler and should therefore be left to system specialists. Report output The REPORT ACF statement is used to request the output of the ACF report.
ACF report SM2 reports PREEMT Number of preemptions per minute INVOCL Number of "long" ACF invocations per minute INVOCS Number of "short" ACF invocations per minute MICTSR Number of micro-time-slice runouts per minute SYSERV Number of system services runouts per minute FVI Number of "Fremd vor Idle" (remote before idle) accesses per minute. "Fremd vor Idle" access: a processor initiates a task from the local Q1 of another processor if its own Q1 is empty, so as not to become idle.
SM2 reports ACTIVITY report ACTIVITY report This report provides the user with an overview of the most important system activities. Report output The REPORT ACTIVITY statement is used to request the output of the ACTIVITY report. POSIX and RESPONSE data can only be output if the corresponding monitoring program is activated. When analyzing the monitoring results, it should be remembered that the SM2 monitoring task is a system task that is kept active for the duration of the whole monitoring process.
ACTIVITY report SM2 reports Monitoring information (VM) This abbreviation will be output in the first line if the system monitored is a VM2000 system. CPU UTILIZATION (2 LM’S) This additional information indicates how many logical machines were active.
SM2 reports ACTIVITY report PCS DATA SRACT Current overall system service rate RDACT Current delay of all jobs in the overall system These fields will not contain any data if PCS was inactive during the last monitoring cycle. IO’S PER SEC These counts indicate the number of input/output operations (EXCP calls).
ACTIVITY report SM2 reports D016ZE04 SM2 ACTIVITY (VM) CYCLE: CPU UTILIZATION ( 2 LM'S) +------+------+------+------+------+ | TU | TPR | SIH | IDLE | /390 | +------+------+------+------+------+ | 22.6%| 22.5%| 10.4%| 44.3%| 0.0%| +------+------+------+------+------+ 120 S PCS DATA +-------+------+ | SRACT |RDACT | +-------+------+ | 42739| 1.
SM2 reports ACTIVITY report TASKS IN SCHEDULER QUEUES #-ACT Average number of all active tasks (including SM2 tasks) CPU-Q Average number of tasks waiting to use the processor(s) and of tasks currently using the processor(s) (task queues 0 and 1, without the SM2 monitoring task) IO-Q Average number of tasks waiting for I/O termination (tasks in task queue 4 with I/O pend code) PAG-Q Average number of tasks waiting for paging (tasks in task queue 3) U3585-J-Z125-8-76 215
ACTIVITY report SM2 reports D016ZE04 SM2 ACTIVITY (VM) CYCLE: CPU UTILIZATION ( 2 LM'S) +------+------+------+------+------+ | TU | TPR | SIH | IDLE | /390 | +------+------+------+------+------+ | 22.6%| 22.5%| 10.4%| 44.3%| 0.0%| +------+------+------+------+------+ 120 S PCS DATA +-------+------+ | SRACT |RDACT | +-------+------+ | 42739| 1.
SM2 reports ACTIVITY report POSIX DATA SCALL/S Number of all system calls per second FORK/S Number of FORK system calls per second These two ACTIVITY report values are the same as the corresponding values of the POSIX screen. These fields will not contain any values if the POSIX monitoring program is not activated.
BCAM CONNECTION report SM2 reports BCAM CONNECTION report This report supplies information on the data sent and received as well as bucket-specific time statistics for defined connection sets. Report output The REPORT BCAM statement is used to request the output of the BCAM CONNECTION report.
SM2 reports BCAM CONNECTION report Monitoring information SET Name of the connection set # CONNECTIONS Number of (active) connections in the connection set. The computation includes only those connections that were active both at the current monitoring time and at the end of the preceding monitoring cycle. IN/OUT Data sent and received TSDU Number of TSDUs per second TSDUs (Transport Data Service Units) correspond to application jobs on BCAM.
CATEGORY report SM2 reports CATEGORY report This report provides an overview of the consumption statistics of the individual categories. For each category, the percentage CPU time and the I/O operations for paging and disk devices are output. Report output The REPORT CATEGORY statement is used to request the output of the CATEGORY report.
SM2 reports CATEGORY report The columns contain the following data: CATEGORY NAME Task category designation CPU-TIME (%) Each category’s percentage of the elapsed time in the monitoring cycle (TU+TPR+SIH+IDLE) PAGING-IO (1/S) Total number of paging I/Os per second of the monitoring cycle The pseudo-category SUM contains all paging I/Os (read, write). In the individual categories, only the paging I/Os of type read are output.
CATEGORY QUEUE report SM2 reports CATEGORY QUEUE report The PRIOR task scheduler uses three criteria for controlling main memory and CPU utilization by the tasks. These criteria are – – – the task category, the multiprogramming level, and the task priority. Detailed information on these criteria can be found in the manuals "Introductory Guide to Systems Support" [6] and “Performance Handbook” [5]. In the following, only information that is relevant for the SM2 reports is discussed.
SM2 reports CATEGORY QUEUE report Report output The REPORT CATQ statement is used to request the output of the CATEGORY QUEUE report. D016ZE04 SM2 CATEGORY QUEUE CYCLE: 120 S SAMPLES: 293 99-03-24 14:30:00 |CATEGORY | TASKS IN SCHEDULER QUEUES | MPL | | NAME |CPU-Q|IO-Q |PAG-Q| ACT | WACT | NADM | ALL | MIN | MAX |WEIGHT| +---------+-----+-----+-----+------+------+------+-------+------+-----+------+ | SUM | 1.7| 2.7| 0.0| 95.0| 0.0| 0.0| 675.6| | | | | SYS | 0.2| 0.2| 0.0| 49.3| 0.0| 0.0| 198.
CATEGORY QUEUE report SM2 reports The columns contain the following data: CATEGORY NAME Task category designation TASK IN SCHEDULER QUEUES CPU-Q Average number of tasks of a category waiting to use the processor(s) and of tasks currently using the processor(s) (task queues 0 and 1, excluding the SM2 monitoring task) IO-Q Average number of tasks of a category waiting for I/O termination (tasks in task queue 4 with I/O pend code) PAG-Q Average number of tasks of a category waiting for paging (tasks i
SM2 reports CATEGORY WSET report CATEGORY WSET-Report Report output The REPORT CATW statement is used to request the output of the CATEGORY WSET report.
CATEGORY WSET report SM2 reports WS-ACT PPC Sum of the average planned page counts of the active tasks in a category UPG Sum of the average used page counts of the active tasks in a category WS-WACT PPC Sum of the average planned page counts of the tasks in a category waiting for activation. UPG Sum of the average used page counts of the tasks in a category waiting for activation. For an explanation of the values PPC and UPG, see “paging in BS2000” on page 452 of the glossary.
SM2 reports CHANNEL report CHANNEL report This report contains monitored data on the activity of block multiplexer I/O channels. Report output The REPORT CHANNEL statement is used to request the output of the CHANNEL report. The values BUSY and NON OVERLAP are recorded by default.
CHANNEL report SM2 reports Monitoring information The values BUSY and NON OVERLAP are recorded by default. All other values are output only if the CHANNEL-IO monitoring program has been activated for the monitored channels. In the case of non-monitored channels, blanks are entered. CHANNEL-PATH-ID Channel address. BUSY Percentage of the monitoring cycle during which the corresponding channel was active.
SM2 reports CMS report CMS report This report supplies performance data on the CMS (Catalog Management System). Data is collected separately for each catalog. A separate screen is output for each PVS (public volume set) imported during the last monitoring cycle and for all private volumes. The home PVS is marked. Detailed information on CMS is contained in the manuals “HIPLEX MSCF” [4] and “Introductory Guide to Systems Support” [6].
CMS report SM2 reports D016ZE04 SM2 CMS CYCLE: CAT-ID: 2OSG(MASTER) 120 S SAMPLES: HIT-RATE: 86.2% 293 99-03-24 14:30:00 #-BMT:128 (RESIDENT) -------+--------+---------+---------+-------+-------+-------+--------+--------REQ. QU| SER. QU| BLOCK QU|USERID QU| CE QU | SFP QU| SMP QU| PH-RD/S| PH-WRT/S -------+--------+---------+---------+-------+-------+-------+--------+--------0.03 | 0.00 | 0.03 | 0.03 | 0.16 | 0.00 | 0.00 | 0.6 | 0.
SM2 reports CMS report #-BMT Number of buffer management tables or buffers used by CMS (refer to the “System Installation” manual [7]) PAGEABLE Buffers are pageable (class 4 memory) or RESIDENT D016ZE04 SM2 CMS CAT-ID: 2OSG(MASTER) Buffers are resident (class 3 memory). Refer to the “System Installation” manual [7]. CYCLE: 120 S SAMPLES: HIT-RATE: 86.2% 293 99-03-24 14:30:00 #-BMT:128 (RESIDENT) -------+--------+---------+---------+-------+-------+-------+--------+--------REQ. QU| SER.
CMS report SM2 reports Monitoring information REQ. QU Average number of requests waiting for the release of a buffer management table or currently using a buffer management table. If the request queue is always long, this means that there are too few buffers compared to the number of CMS calls, i.e. that the number of buffer management tables should be increased. If the maximum number of buffer management tables is already being used, the PVS can be subdivided into smaller pubsets.
SM2 reports CMS report D016ZE04 SM2 CMS CYCLE: CAT-ID: 2OSG(MASTER) 120 S SAMPLES: 293 HIT-RATE: 86.2% 99-03-24 14:30:00 #-BMT:128 (RESIDENT) -------+--------+---------+---------+-------+-------+-------+--------+--------REQ. QU| SER. QU| BLOCK QU|USERID QU| CE QU | SFP QU| SMP QU| PH-RD/S| PH-WRT/S -------+--------+---------+---------+-------+-------+-------+--------+--------0.03 | 0.00 | 0.03 | 0.03 | 0.16 | 0.00 | 0.00 | 0.6 | 0.
CMS report SM2 reports The individual lines contain the following data: RESPONSETIME (MS) Global response times for the above data for files and job variables and for all accesses, regardless of their origin (local or remote computer). 234 LOCAL-FILE (/S) File entry accesses originating from the local computer. JV (/S) Job variable entry accesses originating from the local computer. REMOTE-FILE (/S) File entry accesses originating from a remote computer.
SM2 reports CPU report CPU report The CPU report provides you with an overview of the utilization of the individual processors. Report output The REPORT CPU statement is used to request the output of the CPU report. An overflow screen may be requested for this report.
CPU report SM2 reports NORMED In the NORMED TO 100 % section, the sum of the percentage values for TU, TPR, SIH and IDLE is 100 %. MEASURED The percentage values measured for TU, TPR, SIH and IDLE are output in the MEASURED section. When using VM2000, there may be discrepancies between the NORMED value and the MEASURED value (see also section “SM2 together with VM2000” on page 347).
SM2 reports DAB reports DAB reports These reports provide information on DAB (Disk Access Buffer) activity (for an explanation of the DAB function, please refer to the “DAB” manual [1]). The DAB report outputs access statistics for each DAB cache. The DAB CACHE report contains detailed information on the subareas and files served by a particular DAB cache.
DAB report SM2 reports DAB report This report supplies monitored data on the various DAB caches. Report output The REPORT DAB statement is used to request the output of the DAB report. The report can only be output if the SM2 administrator has started the monitoring process using the statement START-MEASUREMENT-PROGRAM TYPE=*DAB statement. The monitored data output is sorted under the categories READ and WRITE. Overflow screens may be requested for this report.
SM2 reports DAB report RD HIT (%) Percentage of read operations without disk access. SM2 compares the number of read operations for which disk access was not required (as the data to be read was already in the cache) with the total number of read operations in all subareas or files served by the DAB cache.
DAB CACHE report SM2 reports DAB CACHE report This report supplies information on the subareas or files served by a DAB cache. Report output The DAB CACHE report is output only at the explicit request of the SM2 user by means of the SELECT-DAB-CACHE statement (see page 173). After this statement has been entered, the user receives during the next monitoring cycle not only the DAB report, but also the DAB CACHE report for the DAB caches he or she has selected.
SM2 reports DAB CACHE report Monitoring information ID Name of the appropriate DAB cache as selected via the ADD-CACHEID operand of the SELECT-DAB-CACHE statement. If the DAB cache is located in GS (global storage), the name of the partition is also output in brackets. MOD R: The cache is used as a read cache. W: The cache is used as a write cache. W/R: The cache is used as a read/write cache. PFA: The cache is used as a PFA cache.
DAB CACHE report SM2 reports DD017ZE03 SM2 DAB CACHE ID: BUFFER#001 CYCLE: (DAB13V23) 60 S MOD: R 99-03-24 MED:GS SIZE(FIX): 11:11:02 12.0 MB | VSN / FILE |FIRST-HP,LAST-HP |S| READ |RD-HIT| WRITE |WR-HIT|OVER | | | | | (1/S) | (%) | (1/S) | (%) |(1/S)| +---------------------+-----------------+-+-------+------+-------+------+-----+ |*SUMMARY | 11| | 117.2 | 99.4 | 113.7 | 0.0 | 0.
SM2 reports DAB CACHE report Note In order to limit the data recorded, the following modification has been introduced in DAB V6.0A for the DAB-CACHE report: If the cache is created with AREA=*BY-SYSTEM(ADM-PFA) or with CACHEDFILES=*BY-SYSTEM(USER-PFA), the output does not include a list of the files served. Instead, it contains a summary of the entire cache. The (VSN/FILE=*SUMMARY) row of the DAB CACHE report thus contains the same data as the DAB report.
DEVICE report SM2 reports DEVICE report This report contains data on the I/O operations performed with peripheral devices during one monitoring cycle. It counts the number of EXCP calls per second (see glossary, page 448). The user can specify up to eight devices in the DEVICE statement for which the data is to be output separately. If more than 8 devices were active in the monitoring cycle, the mnemonic device names of other devices are displayed in the ACTIVE line.
SM2 reports DEVICE report D016ZE04 SM2 DEVICE CYCLE: 120 S SAMPLES: 293 99-03-24 14:30:00 ----------+--------+--------+--------+--------+--------+----------------------| TOTAL | DISK | PAGE | TAPE | PRINT | OTHER IO(/S) | 402.7 | 210.5 | 0.0 | 0.2 | 0.0 | 192.
DEVICE report SM2 reports D016ZE04 SM2 DEVICE CYCLE: 120 S SAMPLES: 293 99-03-24 14:30:00 ----------+--------+--------+--------+--------+--------+----------------------| TOTAL | DISK | PAGE | TAPE | PRINT | OTHER IO(/S) | 402.7 | 210.5 | 0.0 | 0.2 | 0.0 | 192.
SM2 reports DEVICE report D016ZE04 SM2 DEVICE CYCLE: 120 S SAMPLES: 293 99-03-24 14:30:00 ----------+--------+--------+--------+--------+--------+----------------------| TOTAL | DISK | PAGE | TAPE | PRINT | OTHER IO(/S) | 402.7 | 210.5 | 0.0 | 0.2 | 0.0 | 192.
DISK FILE report SM2 reports DISK FILE report This report contains information on the input/output operations on all files of selected disk devices. Report output The REPORT DISK_FILE statement is used to request the output of the DISK FILE report.
SM2 reports DISK FILE report Monitoring information READ Number of read operations per second WRITE Number of write operations per second FILENAME Name of the monitored file. The first row always contains the value *OVERRUNS. This entry includes all input/output operations that could not be assigned to a file entry because the internal SM2 table was full during the monitoring cycle. It is generally set to zero or to a low value.
DLM report SM2 reports DLM report This report contains monitored data from the DLM (Distributed Lock Manager). Report output The REPORT DLM statement is used to request the output of the DLM report. The report can only be output if the SM2 administrator has activated the monitoring process using the statement START-MEASUREMENT-PROGRAM TYPE=*DLM.
SM2 reports DLM report NUMBER INFORMATION (1/S) Number of information lock requests per second from TU or TPR. The "NSM" column always contains the value 0. NUMBER GRANT EVENTS (1/S) Number of grant events (information about lock allocations) per second via TU contingency, via bourse (or user eventing), from NSM (information about lock allocations on the local host).
FILE reports SM2 reports FILE reports The FILE reports contain monitored data on access to a file. Report output The REPORT FILE statement is used to request the output of the FILE reports.
SM2 reports FILE reports D016ZE04 SM2 PRIVILEGED FILE CYCLE: 120 S 99-03-24 14:30:00 -----+-----+-----+-----+-----+------------------------------------------------WAIT |CHECK|READ |WRITE|TIME | FILENAME -----+-----+-----+-----+-----+------------------------------------------------0.0| 0.0| 0.0| 0.0| *|:2OSX:$TSOS.TSOSCAT 0.0| 0.0| 0.0| 0.0| *|:2OSW:$TSOS.TSOSCAT 0.0| 0.0| 0.0| 0.0| *|:2OS2:$TSOS.TSOSCAT 0.0| 0.0| 0.0| 0.0| *|:2SO6:$TSOS.TSOSCAT 0.0| 0.0| 0.0| 0.0| *|:2OS7:$TSOS.TSOSCAT 0.0| 0.0| 0.
FILE reports TIME SM2 reports Average duration of an input/output operation in milliseconds; * means that no input/output operation has taken place. Note The value shown here represents the logical duration of the input/ output operation from initiation to completion of the job from the point of view of the software. In the case of asynchronous input/ output operations, this may be considerably greater than the hardware time. The < sign indicates that the value cannot be fully accommodated in the field.
SM2 reports GLOBAL report GLOBAL report The GLOBAL report contains data on a host network. It provides the user with an overview of the most important system activities (CPU utilization, I/O rates, size of pageable memory) for each host. Report output The REPORT GLOBAL statement is used to request the output of the GLOBAL report. Overflow screens may also be requested for this report. The SM2 administrator can use the SELECT-HOSTS statement to select the hosts to be displayed in the GLOBAL report.
GS report SM2 reports GS report This report supplies partition-specific monitored data on the utilization of global storage. Report output The REPORT GS statement is used to request the output of the GS report. The report can only be output if the SM2 administrator has activated the monitoring process using the statement START-MEASUREMENT-PROGRAM TYPE=*GS. Overflow screens may also be requested for this report.
SM2 reports GSVOL report GSVOL report This report provides monitored data on emulated volumes in global storage. Report output The REPORT GSVOL statement is used to request the output of the GSVOL reports. This report can only be output if the SM2 administrator has activated the monitoring process using the statement START-MEASUREMENT-PROGRAM TYPE=*GSVOL. Overflow screens may also be requested for this report. The monitored data output is sorted under the categories READ and WRITE.
ISAM reports SM2 reports ISAM reports These reports provide performance data on ISAM buffer management. Report output The REPORT ISAM statement is used to request the output of the ISAM report.
SM2 reports ISAM reports D016ZE04 SM2 PRIVILEGED ISAM CYCLE: 120 S 99-03-24 14:30:00 --------+--+------+----------+--------+-------+--------+--------+-------+-----POOLNAME|SC|CAT-ID| UID/TSN | FIX-OP |FIX-HIT|FIX-WAIT|SLT-WAIT|FXD PGS| SIZE --------+--+------+----------+--------+-------+--------+--------+-------+-----$SYS01 |HS| 2OSL | | 0.3 | 92.1%| 0.0% | 0.0% | 1.2%| 82 SRPMPOOL|TA| 2OSL | RP01 | 0.0 | 99.9%| 0.0% | 0.0% | 0.7%| 138 SESFPOOL|HS| 2OSL | | 0.0 | 99.4%| 0.0% | 0.0% | 0.
ISAM reports SM2 reports FXD PGS Mean percentage of fixed pages relative to the number of all ISAM pool pages used for buffering in the last monitoring cycle SIZE Size of the ISAM pool in 4-KB pages (excluding some administration data) If an ISAM pool is never addressed during a monitoring cycle, the last five columns contain blanks.
SM2 reports MEMORY report MEMORY report This report provides an overview of main memory and virtual address space utilization. Report output The REPORT MEMORY statement is used to request the output of the MEMORY report.
MEMORY report SM2 reports MAIN MEMORY FRAMES TOTAL Total number of 4-Kb pages in main memory PAGEABLE Number of pageable 4-Kb pages in main memory R-ONLY-Q Average number of 4-Kb read-only pages in the free pool (read-only queue) R-WR-Q Average number of 4-Kb read/write pages in the free pool (read/ write queue) SYS-GLOB Average number of system-globally managed 4-Kb page frames TASK-LOC Average number of task-locally managed 4-Kb page frames WORK.
SM2 reports MEMORY report D016ZE04 SM2 MEMORY (SYS) CYCLE: 120 S SAMPLES: 293 MAIN MEMORY FRAMES +--------+---------+--------+--------+----------+----------+ | TOTAL |PAGEABLE |R-ONLY-Q|RD-WR-Q | SYS-GLOB | TASK-LOC | +--------+---------+--------+--------+----------+----------+ | 499713 | 480617 | 37969 | 56452 | 386164 | 0 | +--------+---------+--------+--------+----------+----------+ 99-03-24 14:30:00 WORK.
MEMORY report SM2 reports D016ZE04 SM2 MEMORY (SYS) CYCLE: 120 S SAMPLES: 293 MAIN MEMORY FRAMES +--------+---------+--------+--------+----------+----------+ | TOTAL |PAGEABLE |R-ONLY-Q|RD-WR-Q | SYS-GLOB | TASK-LOC | +--------+---------+--------+--------+----------+----------+ | 499713 | 480617 | 37969 | 56452 | 386164 | 0 | +--------+---------+--------+--------+----------+----------+ 99-03-24 14:30:00 WORK.
SM2 reports MEMORY report PAGE TRANSFERS READ Number of 4-Kb pages read per second WRITE Number of 4-Kb pages written per second Note The sum of read and written pages does not match the IO’S PER SEC PAGE value of the ACTIVITY report. Memory management tries to group up to eight 4-Kb page-out pages (WRITE) for one input/output operation (SDV or START-SUCHANNEL). Each READ causes one 4-Kb page to be transferred, i.e.
MSCF report SM2 reports MSCF report This report contains monitored data from the MSCF subsystem. Report output The REPORT MSCF statement is used to request the output of the MSCF reports. The report can only be output if the SM2 administrator has activated the monitoring process using the statement START-MEASUREMENT-PROGRAM TYPE=*MSCF. D016ZE04 SM2 MSCF CYCLE: +-----------+-----------+ | CALLS | 39.8 /S | +-----------+-----------+ | SHORTAGES | 0.
SM2 reports MSCF report # SERVER TASKS ORIGINAL Number of server tasks originally requested ACTUAL Number of current server tasks OCCUPIED Number of current server tasks which could cause a bottleneck These values merely indicate the status at the end of the monitoring cycle and do not represent the mean value over the entire monitoring cycle.
MSCF report SM2 reports D016ZE04 SM2 MSCF CYCLE: +-----------+-----------+ | CALLS | 39.8 /S | +-----------+-----------+ | SHORTAGES | 0.
SM2 reports NET DEVICE report NET DEVICE report This report provides data on I/O operations of the network devices. The data is recorded for each port, i.e. according to the respective mnemonic device names. Report output The REPORT NET_DEVICE statement is used to request the output of the NET DEVICE report. The report can only be output if the SM2 administrator has activated the monitoring process using the statement START-MEASUREMENT-PROGRAM TYPE=*NET-DEVICE.
NSM report SM2 reports NSM report This report provides data from the NSM (Node Serialization Manager) subsystem for a computer network. Report output The REPORT NSM statement is used to request the output of the NSM report. The report can only be output if the SM2 administrator has activated the monitoring process using the statement START-MEASUREMENT-PROGRAM TYPE=*NSM. Overflow screens may also be requested for this report.
SM2 reports NSM report Monitoring information MAX MSG LENGTH Length of the NSM message buffer in the token in KB USED MSG LENGTH Percentage of the NSM message buffer used CIRC TIME Circulation time of the token in milliseconds This data is output by the first host. HOST Name of the host on which the data is collected DURATION TIME (MS) Dwell time of the token in the host in milliseconds #WAIT MSG Number of messages waiting for space in the token #LOCKSERVER Number of lock servers.
PCA reports SM2 reports PCA reports SM2 collects monitored data on 3419/21 controllers with a cache which are managed by the PCA subsystem. Unlike other SM2 monitoring programs, this information is not hostspecific, rather refers globally to a controller. This must be taken into account particularly when interpreting the data. The PCA CONTROLLER report supplies summary information for all installed 3419/21 controllers.
SM2 reports PCA reports The figure below illustrates the hierarchy of reports and the statements used to request them: PCA CONTROLLER report SELECT-PCA-CONTROLLER PCA CACHE report SELECT-PCA-CACHE PCA DEVICE report U3585-J-Z125-8-76 273
PCA CACHE report SM2 reports PCA CACHE report This report provides monitored data on the caches of selected controllers. Report output The PCA CACHE report is output only at the explicit request of the SM2 user with the help of the SELECT-PCA-CONTROLLER statement (see page 176). This statement is used to output a PCA CONTROLLER report together with a PCA CACHE report for the selected controllers. The PCA CACHE report supplies detailed information on the controller caches.
SM2 reports PCA CACHE report READ H-R. (%) Percentage of hits based on the total number of read operations to be executed as fast reads WRITE (1/S) Total number of write operations (in I/Os per second) FAST W.
PCA CONTROLLER report SM2 reports PCA CONTROLLER report This report provides global monitored data on the individual 3419/21 controllers. One line is output for each controller. Report output The REPORT PCA statement is used to request the output of the PCA CONTROLLER report. The report can only be output if the SM2 administrator has activated the monitoring process using the statement START-MEASUREMENT-PROGRAM TYPE=*PCA. Overflow screens may also be requested for this report.
SM2 reports PCA CONTROLLER report READ H-R (%) Percentage of hits based on the total number of read operations to be executed as fast reads WRITE (1/S) Total number of write operations to disks for which caching is performed (in I/Os per second) FAST W.
PCA DEVICE report SM2 reports PCA DEVICE report This report provides monitored data on the devices of a 3419/21 controller which have been allocated a cache. Report output The PCA DEVICE report is output only at the explicit request of the SM2 user with the help of the SELECT-PCA-CACHE statement (see page 174). This statement is used to output a PCA CONTROLLER report together with a PCA DEVICE report for the selected cache of a controller.
SM2 reports PCA DEVICE report READ (1/S) Total number of read operations (in I/Os per second) C-READ (1/S) Total number of read operations to be executed as fast reads (caching reads) (in I/Os per second) READ H-RATE % Percentage of hits based on the total number of read operations to be executed as fast reads WRITE (1/S) Total number of write operations (in I/Os per second) FAST W.
PCS report SM2 reports PCS report This report provides an overview of the activities of the Performance Control Subsystem. Report output The REPORT PCS statement is used to request the output of the PCS report. The report can only be output if PCS was active during the last monitoring cycle.
SM2 reports PCS report SQPLN (%) System performance percentage planned for this category. (This variable is irrelevant for the SUM category and is therefore replaced by blanks.) SQACT(%) Current percentage of system performance for this category RDACT Current delay of all jobs in this category. If no dilation was sensed, ’**’ is output (see section on “dilation factor” on page 447 of the glossary). (A system-global value is given in the SUM line.
PERIODIC TASK report SM2 reports PERIODIC TASK report This report provides information on the most important consumption statistics of all tasks. Report output The REPORT PERIODIC statement (synonymous with REPORT TASK) is used to request the output of the PERIODIC TASK report.
SM2 reports PERIODIC TASK report Monitoring information The first header line shows the report name and the sort criterion used (CPU, IO, UPG or S-U for service units).
PERIODIC TASK report SM2 reports Monitoring information TSN TSN of the task Depending on whether the output value USER-ID or JOB-NAME was selected in the SELECT-PERIODIC-TASK-PARAMETER statement, the second column contains either USERID User ID of the task or JOB-NAME Job name of the task TYP Current task type at the end of the monitoring cycle SERV-RATE Elapsed service units of the task per second CPU-TIME Task’s percentage of the (TU+TPR+SIH+IDLE) time (without the share of the hypervisor und
SM2 reports PFA reports PFA reports The PFA monitoring program enables SM2 to record monitored data on the use of various caches. These caches can be served by the products DAB and PCA. DAB supports the caches in main memory, expanded storage and global storage. PCA supports the caches in the 3419, 3421, 3860 and SYMMETRIX controllers.
PFA CACHE report SM2 reports PFA CACHE report This report provides an overview of the use of all PFA caches for the products DAB and PCA. The PFA CACHE report only contains data supplied in the same manner from the different products. Report output The REPORT PFA statement is used to request the output of the PFA CACHE report. The report can only be output if the SM2 administrator has activated the monitoring process using the statement START-MEASUREMENT-PROGRAM TYPE=*PFA.
SM2 reports PFA CACHE report BLK SIZE Block size of the cache SIZE Size of the cache READ Number of read operations to hiperfiles (in I/Os per second) RD HIT Percentage of hits in the total number of read operations to hiperfiles WRITE Number of write operations to hiperfiles (in I/Os per second) WR HIT Percentage of fast write operations in the total number of write operations to hiperfiles OVERRUNS Number of unsuccessful attempts to use the cache due to overload (per second) Notes – The n
PFA CONTROLLER report SM2 reports PFA CONTROLLER report This report provides detailed monitored data on a single PFA cache served by PCA and whose pubset disks can be assigned to various controllers. Report output The PFA CONTROLLER report is output only at the explicit request of the SM2 user with the help of the SELECT-PFA-CACHE statement (see page 179). The PFA CACHE report indicates the caches for which subreports can be selected.
SM2 reports PFA CONTROLLER report PREFETCH LENGTH Information on the prefetching strategy (only supported for 3419/21) NONE: No prefetching LOW: A small number of blocks are prefetched HIGH: A large number of blocks are prefetched CTL MN Mnemonic name of the controller or of the CONTROL DEVICE (3419/21) #DEV Number of disk devices supported by the cache SEC NR Cache sector number on this controller (3419/21 only) SIZE Size of the cache sector in this controller in MB (3419/21 only) READ Number of
POSIX report SM2 reports POSIX report Report output The REPORT POSIX statement is used to request the output of the POSIX report. The report can only be output if the SM2 administrator has activated the monitoring process using the statement START-MEASUREMENT-PROGRAM TYPE=*POSIX. D016ZE04 SM2 POSIX CYCLE: -------- OPTION A -------IGET/S NAMEI/S 7.9 133.9 120 S 99-03-24 14:30:00 -------- OPTION M -------MSG/S SEMA/S 0.0 1.
SM2 reports POSIX report OPTION B provides information on buffer utilization: BREAD/S, BWRITE/S Number of data transmissions per second between the system buffer and the hard disk or other block-oriented devices LREAD/S, LWRITE/S Accesses to the system buffer per second RCACHE, WCACHE Cache-memory hit percentage, i.e.
RESPONSETIME report SM2 reports RESPONSETIME report This report contains data on response times, think times, transaction times and wait times for messages in the BCAM pool. Report output The REPORT RESPONSE statement is used to request the output of the RESPONSETIME report.
SM2 reports RESPONSETIME report Example Bucket-specific screen for the selected connection set ($DIALOG,*ALL,*ALL) D016ZE04 SM2 RESPONSETIME (BUCKETS) CYCLE: 120 S 99-03-24 14:30:00 DIALOG APPLICATION: $DIALOG PARTNER: *ALL CONN-TYPE:REMOTE PROCESSOR: *ALL ---------------------------+----------------+----------------+----------------+ | RESP. TIME (1) | THINK TIME | TRANS.
RESPONSETIME report SM2 reports Example Category-specific screen for the selected connection set ($DIALOG,*ALL,*ALL) D016ZE04 SM2 RESPONSETIME (CATEGORY) CYCLE: DIALOG CONN-TYPE:REMOTE 120 S 99-03-24 14:30:00 APPLICATION: $DIALOG PARTNER: *ALL PROCESSOR: *ALL CATGORY| RESPONSE TIME | THINK TIME |TRANSACTION TIME | WAIT TIME NAME | AVG #INT RATE| AVG #INT RATE| AVG #INT RATE| AVG #INT RATE -------+-----------------+-----------------+-----------------+----------------SUM | 0.2 262 2.2| 9.0 249 2.1| 0.
SM2 reports RESPONSETIME report Bucket-specific screen D016ZE04 SM2 RESPONSETIME (BUCKETS) CYCLE: 120 S 99-03-24 14:30:00 *GLOBAL APPLICATION: *ALL PARTNER: *ALL CONN-TYPE:REMOTE PROCESSOR: *ALL ---------------------------+----------------+----------------+----------------+ | RESP. TIME (1) | THINK TIME | TRANS.
RESPONSETIME report SM2 reports NR. INTER Total number of interactions in the monitoring cycle (without overflow data) RATE 1/SEC Number of monitored interactions per second (without overflow data) BUCKET Corresponds to the bucket limits in seconds in which monitored data is arranged in accordance with duration. The last line of the columns (>) contains the overflow data. Data displayed there is not is not used for computing AVG SEC, NR. INTER and RATE 1/SEC.
SM2 reports RESPONSETIME report Category-specific screen D016ZE04 SM2 RESPONSETIME (CATEGORY) CYCLE: *GLOBAL CONN-TYPE:REMOTE 120 S 99-03-24 14:30:00 APPLICATION: *ALL PARTNER: *ALL PROCESSOR: *ALL CATGORY| RESPONSE TIME | THINK TIME |TRANSACTION TIME | WAIT TIME NAME | AVG #INT RATE| AVG #INT RATE| AVG #INT RATE| AVG #INT RATE -------+-----------------+-----------------+-----------------+----------------SUM | 0.1 4583 38.2| 0.6 4581 38.2| 0.1 4563 38.0| 0.0 71 0.6 SYS | 0.1 4255 35.5| 0.1 4252 35.
RESPONSETIME report 298 SM2 reports #INT Total number of transactions during the monitoring cycle (without overflow values) RATE Number of interactions monitored per second (without overflow values) U3585-J-Z125-8-76
SM2 reports SHARED PVS report SHARED PVS report This report contains monitored data on I/O operations on shared pubsets for a host network. Report output The REPORT SHARED_PVS statement is used to request the output of the SHARED PVS report. The SM2 administrator can use the SELECT-HOSTS statement (see page 110) to select the hosts whose monitored data is to be displayed in the report. The header contains information on the local host (if this is selected) or on first host for which valid data is found.
SHARED PVS report SM2 reports Monitoring information The values correspond to those of the DEVICE report and form the sum of the values from the individual hosts. SM2 cannot automatically determine the percentage utilization of the disks (as in the DEVICE report). Each host recognizes only its own accesses to the disk. The disk is already considered active when the I/O chaining starts, even if the system still has to wait until another host has completed its access.
SM2 reports SVC report SVC report This report provides an overview of the SVC calls. Report output The REPORT SVC statement is used to request the output of the SVC report. The report can only be output if the SM2 administrator has activated the monitoring process using the statement START-MEASUREMENT-PROGRAM TYPE=*SVC. The monitored data output is sorted in accordance with the total number of calls from TU and TPR.
SYMMETRIX reports SM2 reports SYMMETRIX reports SM2 collects monitored data on the use of SYMMETRIX controllers. – The SYMMETRIX CONTROLLER report provides summary data on all installed SYMMETRIX controllers. – The SYMMETRIX DEVICE report provides monitored data on the devices of selected controllers. The acquisition of monitored data is controlled by the PFA monitoring program.
SM2 reports SYMMETRIX CONTROLLER report SYMMETRIX CONTROLLER report This report provides an overview of the use of caches in the individual emulated 3860 controllers of a SYMMETRIX subsystem. Report output The REPORT SYMMETRIX statement is used to request the output of the SYMMETRIX CONTROLLER report. The report can only be output if the SM2 administrator has activated the monitoring process using the statement START-MEASUREMENT-PROGRAM TYPE=*PFA. Overflow screens may be requested for this report.
SYMMETRIX CONTROLLER report SM2 reports WR HIT Percentage of write operations that did not need to be delayed (see notes) TOT HIT Percentage of read and write operations completed by the cache in relation to the total number of access operations executed Notes The monitored data output here refers to the controller as a whole, i.e. it includes access operations from other hosts. WR HIT: All write operations are executed via the cache as fast writes.
SM2 reports SYMMETRIX DEVICE report SYMMETRIX DEVICE report This report provides monitored data on the use of caches in the devices of a SYMMETRIX subsystem. Report output The SYMMETRIX DEVICE report is output only at the explicit request of the SM2 user with the help of the SELECT-SYMMETRIX-CONTROLLER statement (see page 180). This statement is used to output a SYMMETRIX CONTROLLER report together with a SYMMETRIX DEVICE report for the selected controllers.
SYMMETRIX DEVICE report SM2 reports Monitoring information CONTROLLER MN Mnemonic name of an emulated 3860 controller. In all SM2 output, two controller mnemonics are always output (separated by a slash) for an emulated 3860 controller. The following two variants are provided: – alphanum-name 2..2 – x-text 4..
SM2 reports TCP/IP report TCP/IP report This report provides the IP and port numbers as well as data on input and output for each TCP/IP connection. Report output The REPORT TCP statement is used to request the output of the TCP/IP report. The report can only be output if the SM2 administrator has activated the monitoring process using the statement START-MEASUREMENT-PROGRAM TYPE=*TCP-IP. Overflow screens may be requested for this report.
TCP/IP report SM2 reports Monitoring information The individual entries have the following meanings: LOCAL IP IP address of the local host REMOTE IP IP address of the remote host REMOTE PORT Port number via which the application on the remote host communicates LOCAL PORT Port number via which the application on the local host communicates INPUT TSDU (/S) Number of TSDUs received. TSDUs (Transport Service Data Units) correspond to jobs of the application on BCAM.
SM2 reports TLM report TLM report This report provides monitored data on the occupation of locks managed by the Task Lock Manager (TLM). Report output The REPORT TLM statement is used to request the output of the TLM report. The report can only be output if the SM2 administrator has activated the monitoring process using the statement START-MEASUREMENT-PROGRAM TYPE=*TLM. The monitored data output is sorted in accordance with OCCUPATIONS. Only one screen is output.
UTM reports SM2 reports UTM reports These reports output application-specific data to the screen. In the following description, you should note that the terms used are the same as those used in UTM. This results in some discrepancies compared with the terms used in the RESPONSETIME reports (e.g. "transaction"). Please refer to the UTM manuals for an explanation of the terms used in UTM. The UTM report provides an overview of all UTM applications which supply data to SM2.
SM2 reports UTM report UTM REPORT This report provides monitored data on UTM applications. Report output The REPORT UTM statement is used to request the output of the UTM report. The report can only be output if the SM2 administrator has activated the monitoring process using the statement START-MEASUREMENT-PROGRAM TYPE=*UTM. The UTM report contains only dialog-oriented monitored data.
UTM report SM2 reports The following three values indicate average percentages of the total time shown under TIME: 312 DB Wait time in UTM for execution of database calls by database systems TAC-CL Wait time as a result of TAC class bottlenecks DDP Wait time in UTM for messages from remote applications (DDP = distributed data processing) # DS Number of dialog steps executed per second #DB-CALL Number of database calls executed per dialog step # TSK Number of tasks currently running for the ap
SM2 reports UTM APPLICATION report UTM APPLICATION report This report provides detailed information on a UTM application. Report output The UTM APPLICATION report is output only at the explicit request of the SM2 user with the help of the SELECT-UTM-APPLICATION statement (see page 182). This statement is used to output a UTM report together with a UTM APPLICATION report for the selected applications. The UTM APPLICATION report supplies detailed information on the UTM applications.
UTM APPLICATION report # DB’S SM2 reports Number of database systems the application works with The following entries are all average values which refer to dialog steps (DIALOG) and asynchronous conversations (ASYNCH). The descriptions of the entries use the term "step" as a general term for both these items.
SM2 reports UTM APPLICATION report The monitored data is set to zero for database systems which do not supply any values. If several database systems are being used, and only some of these provide monitoring data, this should be taken into account when interpreting the average values. The next four values show the application’s throughput (performance data).
VM2000 report SM2 reports VM2000 report This report provides monitored data for the individual virtual machines of a VM2000 system. Report output The REPORT VM statement is used to request the output of the VM2000 report. The report can only be output if the SM2 administrator has activated the monitoring process using the statement START-MEASUREMENT-PROGRAM TYPE=*V . The values for all VMs are only output if SM2 is running on the monitor machine VM1.
SM2 reports VM2000 report Monitoring information On SR2000 (VM2000/SR V1.0A or later), some monitored data has a special significance in the context of VM2000. This is indicated below with “SR2000”. HYPERVISOR IDLE Percentage of ELAPSED TIME accounted for by IDLE time SR2000: Percentage of physically available CPUs which have been identified as unused. Unused CPUs are not assigned to any VM, are in the “detached” state, or belong to an inactive VM.
VM2000 report SM2 reports CPU MEAS Percentage of ELAPSED TIME that can be accounted for by the CPU time of the individual virtual machines. This value represents the share of the entire system. Virtual machines which have not used any CPU time during the monitoring cycle are not listed. Newly started virtual machines are not recorded until the subsequent monitoring cycle is completed. SR2000: The value output here must not exceed that output under “CPU PLAN”, as the CPUs are assigned to guest systems.
SM2 information screens ACTIVE PARAMETER 5.2 SM2 information screens ACTIVE PARAMETER This screen displays the parameters set for the active monitoring programs. As many screens as are necessary are output. If sufficient space is available, all the parameters for one monitoring program are displayed on a single screen. It is only possible to request output from the administration section using the SHOW-ACTIVE-PARAMETER statement.
ACTIVE PARAMETER SM2 information screens BCAM-CONNECTION-SET SET-NAME Name of the selected connection set CONNECTION-TYPE Type of connected to be monitored (REMOTE, LOCAL or BOTH) HOST-SELECTION CONNECTIONSELECTION Hosts between which the connections are established Type of connection set (*BY-PORT-NUMBER or *BY-NEA-NAME) and the selected port numbers or application names CHANNEL-IO PARAMETER CHANNELS Channel addresses for the channels monitored D016ZE04 SM2 ACTIVE PARAMETER COSMOS PARAMETER -------
SM2 information screens ACTIVE PARAMETER NUMBER-OF-BUFFERS Number of buffers ADDITIONAL-INFO Additional data to be included OUTPUT Way in which the COSMOS output files are to be written TASK-SELECTION Conditions on the basis of which the tasks are to be monitored TSN Selection by TSN USER-ID Selection by user ID JOB-NAME Selection by job name CATEGORY Selection by category TYPE Selection by task type EVENT-SELECTION Conditions on the basis of which the events are selected EIA-INTERRUPT-C
ACTIVE PARAMETER SM2 information screens Monitoring information EIA-SVC-NUMBER Selection of EIA events on the basis of the SVC number IO-DEVICE Selection of PMIO, SDV, CHTM and IONQ events on the basis of the mnemonic device name DAB-CACHE-ID Selection of DAB events on the basis of the device VSN MEMORY-CLASS Selection of the REQM and RELM event on the basis of the memory class SLOT-MEMORY-CLASS Selection of the SLOT event on the basis of the memory class PEND-CODE Selection of the PEND event on
SM2 information screens ACTIVE PARAMETER D016ZE04 SM2 ACTIVE PARAMETER DISK-FILE PARAMETER ------------------DEVICES FILE PARAMETER -------------FILENAME 99-03-24 14:20:59 : 430D, 4310, 4312, 4314, 434C, 4350 : :2OSX:$TSOS.TSOSCAT :2OSW:$TSOS.TSOSCAT :2OS2:$TSOS.TSOSCAT :2SO6:$TSOS.TSOSCAT :2OS7:$TSOS.TSOSCAT :2ORZ:$TSOS.TSOSCAT :2OSQ:$TSOS.TSOSCAT :2OSL:$TSOS.EQUISAMQ :2OS6:$TSOS.SYSEAM :2OSX:$TSOS.SYSEAM :2OS2:$TSOS.SYSEAM :2OS7:$TSOS.SYSEAM :2OS6:$NNN.SM2.SAM.MANUAL.V13.
ACTIVE PARAMETER SM2 information screens Monitoring information ISAM PARAMETER POOL-NAME Name of the monitored ISAM pool with the catalog ID of the public volume set to which the ISAM pool is assigned (SCOPE) Defined type of the ISAM pool: *HOST or UI=user-id or TA=tsn PERIODIC-TASK PARAMETER LOG TASKS Tasks whose monitored data is to be written to the SM2 output file Selected tasks are specified under the selection criteria USER-ID and JOB-NAME RESPONSETIME PARAMETER SCOPE Indicates whether the
SM2 information screens ACTIVE PARAMETER D016ZE04 SM2 ACTIVE PARAMETER 99-03-24 CONNECTION SET SET-NAME SET-DEFINITION CONNECTION-TYPE CONNECTION (APPL,PARTNER,PROC) : : : : *GLOBAL BY-CONNECTION REMOTE (*ALL ,*ALL ,*ALL DIALOG BY-CONNECTION REMOTE )($DIALOG ,*ALL CONNECTION SET SET-NAME SET-DEFINITION CONNECTION-TYPE CONNECTION (APPL,PARTNER,PROC) : : : : OMNIS BY-CONNECTION REMOTE ($OMNIS ,*ALL ,*ALL ) 14:20:59 ,*ALL ) SERVICETIME PARAMETER --------------------DEVICES : 430D, 4310, 4312,
ACTIVE PARAMETER SM2 information screens D016ZE04 SM2 ACTIVE PARAMETER SYSSTAT PARAMETER ----------------DEVICES TASK PARAMETER -------------TASK SELECTION DEVICES 99-03-24 14:20:59 : 431C, 4310, 4330, 434B, 434C, 4350, 4354, 4361, 4363, 4370, 4379 : *ALL : 430D, 4310, 4312, 4314, 434C, 4350 Monitoring information SYSSTAT PARAMETER DEVICES Mnemonic device names of the monitored devices or *NONE, *ALL, *TAPE or *DISK TASK PARAMETER TASK SELECTION *ALL: All tasks are monitored.
SM2 information screens DEFINED PARAMETER DEFINED PARAMETER This screen displays the parameters set for the defined monitoring programs. As many screens as are necessary are output. If sufficient space is available, all the parameters for one monitoring program are displayed on a single screen. It is only possible to request output from the administration section using the SHOW-DEFINED-PARAMETER statement.
MEASUREMENT STATUS SM2 information screens MEASUREMENT STATUS This screen provides the user with information on the current status of the measurement at any time. Output to the terminal comprises three parts. The first two parts contain general administration data and the third part provides information on the functions permitted and on monitoring programs which have been defined and which are running.
SM2 information screens MEASUREMENT STATUS NUMBER OF NONPRIVILEGED SM2 USERS Number of nonprivileged users currently working with SM2 Either SM2 GATHERING TASK CREATED AT Date (using the ISO format) and time the monitoring task was created (provided the SM2 monitoring task is active) or SUBSYSTEM SM2 IN DELETE !!! Subsystem SM2 in the DELETE state. With this status, no further users are allowed to log on. Permission for user-specific task monitoring is withdrawn.
MEASUREMENT STATUS SM2 information screens Status data on additional functions SECONDARY ADMINISTRATOR ALLOWED: YES: The primary administrator has permitted other SM2 administrators NO: Parallel SM2 administration is not permitted USER MEASUREMENTS ALLOWED List of the user monitoring programs permitted. Each user sees precisely those user monitoring programs he/she is allowed to use. The following entries are possible: FILE, ISAM, TASK.
SM2 information screens MEASUREMENT STATUS Meaning of abbreviations for the monitoring programs: BCAM CHA-IO CMS COSM+ DAB D-FILE DISK DLM FILE GS GSVOL HSMS ISAM MSCF NDV NSM PCA PERTSK PFA POSIX RTIME SVC SVTIME SYSTEM TASK TCPIP TLM UTM VM BCAM-CONNECTION monitoring program CHANNEL-IO monitoring program CMS monitoring program COSMOS (“+” means that COSMOS has been initialized but not started) DAB monitoring program DISK-FILE monitoring program DISK monitoring program DLM monitoring program FILE monito
SELECTED HOSTS SM2 information screens SELECTED HOSTS This screen displays the hosts which were selected by means of the SELECT-HOSTS statement. The output can only be requested in the administration facility using the SHOW-SELECTED-HOSTS statement.
SM2 information screens STATUS TABLE STATUS TABLE No monitoring data is output in the STATUS TABLE. Output to the terminal comprises two parts. The first part provides the user with information on which SM2 tasks exist and on the status of the subsystems used by SM2. The line containing "MISSED RECORDS" is only output if unwritten records exist. The second part outputs as many of the most recent trace entries as can be accommodated on one screen.
STATUS TABLE SM2 information screens Meanings of the entries for tasks: RUNNING: Task running normally ENDED: Task terminated normally ABENDED: Task terminated abnormally Meanings of the entries for subsystems: IN USE: SM2 is working with the subsystem UNAVAIL: SM2 requires data from the subsystem, but the subsystem is not running UNUSED: SM2 is no longer working with the subsystem (of its own accord) ABENDED: SM2 is no longer working with the subsystem because the subsystem is no longer runn
SM2 information screens STATUS TABLE REASON Reason for the trace entry. In many cases (with TYPE=S-ER) this is the name of the system function which reported an error.
USER MEASURED OBJECTS SM2 information screens USER MEASURED OBJECTS This screen displays the parameters set for the monitoring programs defined by the user. As many screens as are necessary are output. If sufficient space is available, all the parameters for one monitoring program are displayed on a single screen. In the analysis section, only the parameters for the user task statistics are displayed, together with the objects users have activated for themselves.
SM2 information screens USER MEASURED OBJECTS TASK PARAMETER MEASURED TSN TSN of the task being monitored MEASURED USER-ID User ID of the task being monitored MEASURING TSN TSN of the task which initiated monitoring MEASURING USER-ID User ID of the task which initiated monitoring PC-INTERVAL Sampling cycle for program counter statistics in milliseconds, or 0 if the program counter statistics are not activated. SVC-STATISTICS Indicates whether SVC statistics are activated (ON) or deactivated (OFF).
Eine Dokuschablone von Frank Flachenecker by f.f.
6 Notes on SM2 operation 6.1 System resource utilization by SM2 To perform monitoring, SM2 must use the resources of the system to be monitored. This section provides an overview of SM2 resources requirements and information on assessing and restricting the induced system utilization. With regard to system utilization, only the following basic resources are considered: – – – external storage CPU main memory During monitoring, only the resources utilized by the monitoring task are analyzed (i.e.
System resource utilization Notes on SM2 operation 6.1.2 CPU utilization To facilitate understanding of the factors affecting CPU utilization, readers should be familiar with the monitoring methods (see section “Acquisition of monitored data” on page 15). Method based on monitoring cycle At the end of the monitoring cycle, the measured values of the previous monitoring cycle are calculated for all monitoring programs (with the exception of DISK and TASK).
Notes on SM2 operation System resource utilization The event-driven method is used by the monitoring programs CHANNEL-IO, DISK, DISKFILE, ISAM, NET-DEVICE, PERIODIC-TASK, RESPONSETIME, SERVICETIME, SYSSTAT and TASK, as well as for user task statistics. UTM monitoring program If UTM applications are running on the system and these applications provide data for SM2, the following additional load occurs in each UTM task: an additional 500 instructions (approx.
System resource utilization Notes on SM2 operation User task statistics The system load caused by the activation of user task statistics by the BS2000 user with the aid of the /START-TASK-MEASUREMENT command is mainly the result of program counter statistics and SVC statistics. Program counter statistics The system load caused by program counter statistics depends on the following factors: – – the sampling cycle selected the number of tasks monitored 6.1.
Notes on SM2 operation Accuracy of the SM2 data 6.2 Accuracy of the SM2 data This section indicates the major factors affecting the accuracy of the data supplied by SM2 or SM2R1. The accuracy of some particularly important variables is also discussed. Inaccuracies resulting from rounding problems are not considered here. 6.2.
Accuracy of the SM2 data Notes on SM2 operation Monitoring method inaccuracies Different inaccuracies can occur depending on the monitoring method used: 1. Event-driven monitoring method This method supplies very precise data at the cost of increased system workload. Problems can occur only when the duration of events is monitored. Monitoring cycle Monitoring cycle ....
Notes on SM2 operation Accuracy of the SM2 data 6.2.2 Notes on particular variables CPU utilization The term “percentage deviation” used in the following always denotes the absolute deviation, in other words: X and Y have a deviation of P if abs (X-Y) ≤ P. TU/TPR/SIH time, IDLE time, or /390 time with SR2000. The operating system uses timers to determine three time components: the total for TU and TPR times, the SIH time and the IDLE time.
Accuracy of the SM2 data Notes on SM2 operation 6.2.3 Measures for reducing the error sources From the above explanations, the following recommendations can be deduced; they should be observed if high importance is placed on the accuracy of the data. 1. Minimization of marginal problems The monitoring cycles should be long but not too long.
Notes on SM2 operation Special applications (VM2000) 6.3 Special applications 6.3.1 SM2 together with VM2000 If monitoring is executed under VM2000 control within BS2000 systems, the following special considerations are applicable for the implementation of the SM2 program and for the interpretation of the monitored data: – Generally speaking, SM2 is executable under any guest system and provides monitored data relevant to the respective local guest system.
Special applications (VM2000) Notes on SM2 operation Note The corresponding values can also be output by using the VM2000 command SHOWVM-STATUS (see the “VM2000” manual [9]). VM2000 operation on /390 architecture The overall CPU utilization is determined by taking the HYPERVISOR-IDLE value and extrapolating the difference to 100%.
Notes on SM2 operation Special applications (VM2000) Even if system utilization is 100% (Hypervisor-Idle=0%), it makes sense for SM2 to provide an IDLE value for the following reasons: Full utilization of system load can be the result of a low-priority guest system which has highly intense CPU time (in the extreme case: CPU loop), the system always obtaining control as soon as the other guest systems voluntarily revert to IDLE mode.
Special applications (VM2000) Notes on SM2 operation In the case of the CHANNEL-IO monitoring program, the values supplied (e.g. the I/O operations per channel) always refer to the respective guest system. Correlation of these values on channel utilization is not possible, due to the above-mentioned restriction. For CPUs with DCS, the SERVICETIME monitoring program can only be started by one guest system.
Notes on SM2 operation Special applications (VM2000) 6.3.2 VOLUME load with installed DRV The product DRV (Dual Recording by Volume) can be used to keep double copies of disk drives in the form of mirror images. This increases the availability factor for data stored on the disks. Each write request made by DMS is sent to both disks, and each read request is executed on the disk with the shortest access time available (shortest positioning path, lowest queue length prior to the disk drive).
Sample procedures Notes on SM2 operation 6.4 Sample procedures The following procedures serve as examples for automating frequently recurring operations when the SM2 is used in normal computer center operation. They can also be found in the SYSLIB.SM2.130 library. The first procedure starts short-term monitoring with output to a separate file, defining and starting monitoring programs. The second procedure presupposes that the preceding monitoring operation has already been in progress for some time (e.g.
Notes on SM2 operation Sample procedures /START-SM2 REMARK REMARK REMARK ============================================================= **** BRANCH TO ADMINISTRATION PART **** ============================================================= CALL-ADMINISTRATION-PART REMARK REMARK REMARK REMARK ============================================================= **** DEFINE SYSSTAT MONITORING PROGRAM **** **** MONITOR ALL DISKS AND TAPES **** ============================================================= SET-SYSSTA
Sample procedures Notes on SM2 operation SET-RESPONSETIME-PARAMETER ADD-CONNECTION-SET SET-NAME=CONN1,SET-DEFINITION=*BY-CONNECTION, CONNECTION-SET=*CONNECTION(APPLICATION=$DIALOG,PARTNER=*ALL, PROCESSOR=*ALL) ADD-CONNECTION-SET SET-NAME=CONN2,SET-DEFINITION=*BY-CONNECTION, CONNECTION-SET=*CONNECTION(APPLICATION=UTM1,PARTNER=*ALL, PROCESSOR=*ALL) REMARK REMARK REMARK REMARK - ============================================================= **** OPEN SM2 FILE, SPECIFY MONITORING CYCLE AND **** **** SAMPLING
Notes on SM2 operation Sample procedures 2) Terminate short-term monitoring and resume former monitoring operations (SM2.STOP.MEASUREMENT) It is assumed that SM2 was started with the preceding procedure.
Sample procedures REMARK REMARK REMARK REMARK Notes on SM2 operation =========================================================== *** TERMINATE SM2 USER PROGRAM *** *** RENAME CLOSED FILE *** =========================================================== END /MODIFY-FILE-ATTRIBUTES FILE-NAME=SM2.OUTPUT,NEW-NAME=SM2.
Notes on SM2 operation Sample procedures 3) Prepare for SM2R1 analysis with the SM2U1 utility (SM2U1.PREPARE) Update the master output file with all the records with the exception of those for the TASK and DISK monitoring programs. /BEGIN-PROCEDURE LOGGING=C,PARAMETERS=YES(PROCEDURE-PARAMETERS=( / &SM2UIN=SM2.CHANGE,&SM2UTASK=SM2.SAM.TASK,&SM2MASTER=SM2.
Sample procedures /REMARK /REMARK /REMARK /REMARK Notes on SM2 operation ========================================================== *** LOAD SM2U1, CREATE SM2 FILE FOR TASK *** *** ANALYSIS.
Notes on SM2 operation Sample procedures 4) Perform analysis with SM2R1 (SM2R1.EVALUATION) This procedure analyzes the SM2 output file just closed. /BEGIN-PROCEDURE LOGGING=C,PARAMETERS=YES(PROCEDURE-PARAMETERS=( / &SM2OUT=SM2.CHANGE,&SM2R1OUT=SM2R1.OUT,&SM2UTASK=SM2.SAM.TASK, / &SM2R1OTASK=SM2R1.OUT.
Sample procedures Notes on SM2 operation /REMARK ========================================================== /REMARK *** PRINT SM2R1 OUTPUT FILE *** /REMARK ========================================================== /PRINT-DOCUMENT FROM-FILE=&SM2R1OTASK,DELETE-AFTER-PRINT=*YES, / DOCUMENT-FORMAT=*TEXT(LINE-SPACING=*BY-EBCDIC-CONTROL) - /MODIFY-TERMINAL-OPTIONS OVERFLOW-CONTROL=USER-ACKNOWLEDGE /END-PROCEDURE 360 U3585-J-Z125-8-76
7 Variables reports 7.1 Table of monitored variables In the following table, the SM2 monitored variables are shown in relation to the monitoring program, ONLINE report, and SM2R1 report group.
Monitored variables Monitored variable Reports on monitored variables Monitoring program ONLINE report SM2R1 report group Number of I/O operations 1) ACTIVITY, DEVICE DISK, IO, DEVICE Number of paging I/O operations 1) ACTIVITY, ME- IO MORY IOs , DISK Channel utilization and channel data transfer CHANNEL-IO rates CHANNEL CHANNEL Device utilization and data transfer rates 1) DEVICE DISK Length of device queues 1) DEVICE DISK Duration of I/O operations DISK (DISKSTATISTICS)2) Hardw
Reports on monitored variables Monitored variable Monitored variables Monitoring program ONLINE report SM2R1 report group PCS data 1) PCS PCS UTM response times and transaction rates UTM UTM/ APPLICATION UTM Number and duration of send requests via MSCF MSCF MSCF MSCF Data to POSIX POSIX POSIX POSIX Subsystems Lock requests to the DLM DLM DLM DLM Data to synchronization functions in HIPLEX NSM NSM NSM Data to HSMS HSMS (HSMSSTATISTICS)2) Task Number of tasks 1) Length of
Eine Dokuschablone von Frank Flachenecker by f.f.
8 Messages NPC0050 ERROR IN COSMOS-PARAMS Meaning Invalid values in COSMOS-params. The statement has been rejected. NPC0051 NO MEMORY SPACE ALLOCATED FOR FILE: (&00) Meaning Possible reasons: - No memory space has been allocated for the file. - The value of the primary allocation is smaller than the block size.
NPC0055 NPC0055 Messages ’//SET-COSMOS-PARAMETER’ STATEMENT NOT SPECIFIED Meaning The statement //ADD-COSMOS-EVENT, //REMOVE-COSMOS-EVENT, //MODIFY-COSMOS-PARAMETER, //INIT-COSMOS or //START-MEASUREMENT-PROGRAM COSMOS cannot be specified unless //SET-COSMOS-PARAMETER statement is specified. The statement has been rejected. Response Enter the statement //SET-COSMOS-PARAMETER and repeat your original entry.
Messages NPC0061 NPC0061 ERROR IN COSMOS-WRITETASK Meaning The buffer task for the file with linkname ’(&00)’ returns an error. You can determine the detailed error cause using the trace entries of the //SHOW-SM2STATUS function. NPC0062 MONITORING PROGRAM COSMOS ALREADY INITIALIZE. STATEMENT REJECTED Meaning An attempt was made to initialize the monitoring program COSMOS that has already been initialize or start. NPC0063 ERROR DURING START OF UTM MEASUREMENT. MEASUREMENT PROGRAM COSMOS NOT STARTED.
NPC0068 NPC0068 Messages FILE WITH LINKNAME ’COSFIL’ NOT FOUND. Meaning Possible reasons: - The COSMOS measurement file assigned by LINK=COSFIL is not in the COSMOS parameter list. - The COSMOS measurement file assigned by LINK=COSFIL does not exist. Response Enter the statement //SET-COSMOS-PARAMETER with the COSMOS measurement file assigned by LINK=COSFIL as parameter or create a COSMOS measurement file with LINK=COSFIL. NPC0069 ERROR DURING RDTFT-MACROPROCESSING.
Messages NPC0074 NPC0074 ERROR DURING START OF SUBSYSTEM BCAM-COS. MEASUREMENT PROGRAM COSMOS NOT STARTED. Meaning The event BCAM resp. BCPT cannot be opened, because the subsystem BCAM-COS could not be loaded. The instruction //INIT-COSMOS resp. //START-MEASUENT-PROGRAM COSMOS was rejected. BCAM-COS is not installed or has wrong version. Response Install subsystem BCAM-COS first and then start the COSMOS measurement. NPC0075 ERROR DURING START OF SUBSYSTEM DCAM-COS.
NPS0002 NPS0002 Messages NO MORE FILES PERMITTED FOR FILE MONITORING (B) Routing code: R Weight: 99 Meaning SM2 is already monitoring 16 files. NPS0003 USER NOT AUTHORIZED TO MONITOR FILES. STATEMENT REJECTED (B) Routing code: R Weight: 99 Meaning The SM2 administrator has not (yet) permitted file monitoring for this user. NPS0005 SM2 SYSTEM CODE LOCKED. SM2 RUN ABORTED.
Messages NPS0015 NPS0015 SYNTAX ERROR. STATEMENT CONTAINS INVALID OPERAND(S) ’(&00)’ (B) Routing code: R Weight: 99 Meaning The statement has been rejected. NPS0016 NO REPORTS SELECTED FOR OUTPUT (B) Routing code: R Weight: 99 Meaning Report output cannot be started until the appropriate reports have been selected. NPS0018 SYNTAX ERROR. OPERAND MISSING (B) Routing code: R Weight: 99 Meaning A statement has been entered without an essential operand. The statement has been rejected.
NPS0025 NPS0025 Messages SYNTAX ERROR. ’(&00)’ OPERAND TERMINATED INCORRECTLY (B) Routing code: R Weight: 99 Meaning An improperly terminated operand (e.g. comment) was entered in a statement. The statement has been rejected. NPS0026 SYNTAX ERROR. INVALID KEYWORD ’(&00)’ (B) Routing code: R Weight: 99 Meaning The statement has been rejected.
Messages NPS0033 NPS0033 UNEXPECTED END OF INPUT FILE (B) Routing code: R Weight: 99 Meaning Possible reasons: - An end-of-file condition was encountered in batch mode. - In interactive mode with statement input from a file, an end-of-file condition was encountered when attempting to read a continuation line. If the end-of-file condition is encountered while reading the first line of a statement, SYSDTA is set to (PRIMARY) without this message being displayed.
NPS0040 NPS0040 Messages SM2 STXIT: CLASS=(&00), CODE=(&01), LOCATION=(&02). PROGRAM RUN ABORTED (B) Routing code: R Weight: 99 Meaning An error has occurred in the unprivileged program part of SM2. CLASS: event class. CODE: error weight. LOCATION: program counter of the location at which the error occurred. For further information on the STXIT routine see the ’Executive Macros’ manual.
Messages NPS0048 NPS0048 COMMAND EXECUTED. TASK MONITORING STARTED ON (&00) (B) Routing code: R Weight: 50 Meaning (&00): time stamp for the start of monitoring, in the format YYYY-MM-DD HH:MM:SS. Note: Precisely this time stamp will be put out in the task analysis conducted by the SM2-PA analysis routine. NPS0049 COMMAND EXECUTED. TASK MONITORING TERMINATED ON (&00) (B) Routing code: R Weight: 50 Meaning (&00): time stamp for the end of monitoring, in the format YYYY-MM-DD HH:MM:SS.
NPS0053 NPS0053 Messages TOO MANY POOLS SUBMITTED FOR ISAM POOL MONITORING. STATEMENT REJECTED (B) Routing code: R Weight: 99 Meaning ISAM monitoring is limited to a total of 16 ISAM pools. NPS0054 ISAM POOL NOT SUBMITTED. STATEMENT REJECTED (B) Routing code: R Weight: 50 Meaning A user tried to withdraw an ISAM POOL from monitoring which had not been submitted before. NPS0055 USER NOT AUTHORIZED TO MONITOR ISAM BUFFERS.
Messages NPS0065 NPS0065 NO MORE TASKS CAN BE MONITORED Meaning The maximum possible number of tasks which can be monitored by SM2 has been exceeded. Response Either withdraw other tasks from monitoring or wait until some have terminated, and then try the command again. NPS0066 INVALID FILE ATTRIBUTES SPECIFIED FOR USERSPECIFIC SM2 LOGGING FILE Meaning Invalid file attributes have been specified for the userspecific SM2 logging file regarding the block size, record format, FCB type or open type.
NPS0502 NPS0502 Messages SYSTEM ERROR ON CALLING SM2 (B) Routing code: R Weight: 99 Meaning A serious error has occured when calling SM2 Possible reasons: - an unexpected return code was delivered when calling an internal BS2000 system function. - SM2 itself detected an inconsistency in its own logic. The statement has been rejected. Response Contact the SM2 administrator. He can determine the detailed error cause using the trace entries of the //SHOW-SM2-STATUS function.
Messages NPS0515 NPS0515 SM2 SUBSYSTEM NOT AVAILABLE (B) Routing code: R Weight: 99 Meaning A non-privileged user has tried to start SM2 before the system administrator or a SM2 administrator had started the subsystem SM2 or subsystem SM2 was terminated during connection of user. NPS0516 REQUIRED MODULES COULD NOT BE LOADED (B) Routing code: R Weight: 99 Meaning Certain monitoring program modules could not be loaded.
NPS0521 NPS0521 Messages ONLY ’BUFFER-LENGTH=*STD(SIZE=16)’ PERMITTED FOR SM2 LOGGING FILE. STATEMENT REJECTED Meaning SM2 logging files are only permitted with ’BUFFER-LENGTH=*STD(16)’. The value of the BUFFER-LENGTH operand in the /ADD-FILE-LINK command for a nonstandard SM2 logging file is invalid or the existing non-standard SM2 logging file has wrong BUFFER-LENGTH. Response Retry the /ADD-FILE-LIND command without the BUFFER-LENGTH operand and then retry OPEN-LOG-FILE statement.
Messages NPS0528 NPS0528 INVALID DEVICE DEFINITION SPECIFIED FOR DEVICE ’(&00)’ (B) Routing code: R Weight: 99 Meaning When defining a monitoring program, an attempt was made to specify a device that is not valid for this program. The statement has been rejected.
NPS0533 NPS0533 Messages SYSTEM ERROR IN ’/START-TASK-MEASUREMENT’ OR ’/STOP-TASK-MEASUREMENT’ COMMAND: CODE=(&00) Meaning This message is for diagnostic purposes only. NPS0534 MONITORING PROGRAM ’(&00)’ NOT COMPLETELY DEFINED. STATEMENT REJECTED. Meaning An attempt was made to start a not completely defined monitoring program. Response Define montoring program completely and repeat statement. NPS0535 ’//SET-BCAM-CONNECTION-PARAMETERS’ STATEMENT NOT SPECIFIED. STATEMENT REJECTED.
Messages NPS0540 NPS0540 VERSIONS OF SM2 AND VM2000 ARE INCOMPATIBLE. STATEMENT REJECTED Meaning The measurement program VM cannot fetch any VM data. NPS0541 INVALID TASK DEFINITION SPECIFIED FOR TSN ’(&00)’ (B) Routing code: R Weight: 99 Meaning When defining a monitoring program, an attempt was made to specify a task that is not valid for this program. The statement has been rejected. NPS0542 WRONG BUCKET VALUES. STATEMENT REJECTED. Meaning Only 1-4 buckets values may be specified in a list.
NPS0545 NPS0545 Messages VERSIONS OF SM2 TU PART (&00) AND SM2 MODULE LIBRARY (&01) ARE INCOMPATIBLE. SM2 TERMINATED ABNORMALLY (B) Routing code: R Weight: 99 Meaning The version number (&00) of the TU part of SM2 and the version number (&01) of modules in the SM2 module library do not match. NPS0546 WRONG BCAM-VERSION. STATEMENT REJECTED. Meaning The measurement program BCAM-CONNECTION cannot fetch any data by this BCAM-Version.
Messages NPS0551 NPS0551 WARNING: 64 DEVICES SELECTED FOR TASK STATISTICS. SURPLUS DEVICES IGNORED (B) Routing code: R Weight: 50 Meaning More than 64 devices were selected by the DEVICE definition in the //SET-TASKPARAMETER statement. As the number of devices that can be monitored is limited to 64, collection of task statistics begins with exactly 64 devices and any surplus devices are not monitored. The criteria for selecting these 64 devices are described in the BS2000 manual ’SM2’.
NPS0559 NPS0559 Messages WARNING: 256 DEVICES SELECTED AND INVALID DEVICES IN WILDCARD LIST. SURPLUS AND INVALID DEVICES IGNORED Meaning - More than 256 devices were selected by the DEVICE definition in the - //SET-DISK-PARAMETER or //SET-SERVICETIME-PARAMETER statement. - As the number of devices that can be monitored is limited to 256, collection of - corresponding statistics begins with exactly 256 devices and - any surplus devices are not monitored.
Messages NPS0564 NPS0564 WARNING: INVALID DEVICES IN WILDCARD LIST. INVALID DEVICES IGNORED. Meaning In the specified wildcard list some invalid devices were found. Invalid devices are: - devices which are not attached - GS volumes The invalid devices are not monitored. NPS0565 SYNTAX ERROR. INVALID BUCKET VALUES Meaning Only 1-5 bucket values may be specified in a list. The values must be in ascending order. Permissible value range: 1 to 99999. The statement has been rejected.
NPS0569 NPS0569 Messages MORE THAN 15 CONNECTION GROUPS DEFINED Meaning ’(*ALL, *ALL, *ALL)’ is always defined additionally as a connection group. The statement has been rejected. Response Use the //REMOVE-CONNECTION-SET statement to terminate monitoring of superfluous connection groups and repeat your original entry. NPS0570 SYSTEM ERROR WHEN STARTING MONITORING PROGRAM FOR DISK STATISTICS. DISK STATISTICS NOT STARTED Meaning The number of cylinders per volume could not be determined.
Messages NPS0577 NPS0577 TOO MUCH USERS MONITOR THE SAME ISAM POOL Meaning Maximal 64 users can monitor the same ISAM POOL at the same time. Statement rejected. NPS0578 INVALID CACHE-ID. PERMISSIBLE VALUE RANGE: 0 TO 62 Meaning The statement has been rejected. NPS0579 INVALID OBJECT SPECIFICATION IN ’//SET-PERIODIC-TASK-PARAMETER’ STATEMENT Meaning The statement has been rejected.
NPS0600 NPS0600 Messages UNRECOVERABLE ERROR IN SM2 MODULES (B) Routing code: R Weight: 99 Meaning With this message number a SERSLOG record is written. NPS0603 UNKNOWN DATA PASSED THROUGH BOURSE Meaning The contents of bourse parameter RDATA is unknown to the gatherer task. A SERSLOG record is written. NPS0700 Host: ’(&00)’ Meaning This host sends the following SM2 message. NPS0701 SELECTED HOST NOT AVAILABLE. STATEMENT REJECTED Meaning The selected host is not available.
Messages NPS3004 NPS3004 INVALID INPUT FILE ’(&00)’ (B) Routing code: R Weight: 99 Meaning The specified input file is not - a SM2 logging file although SM2 logging files are assumed to be handled - a user logging file although user logging files are assumed to be handled. The statement has been rejected.
NPS3013 NPS3013 Messages NUMBER OF MISSING RECORDS = (&00) (B) Routing code: R Weight: 50 Meaning During processing of the input file, the total number of records which SM2 could not put out is added up. This number is put out when processing has been completed, unless it is zero.
Messages NPS3021 NPS3021 SM2U1 HANDLES SM2 LOGGING FILES NPS3022 FILE(S) ’(&00)’ TRANSFERED TO OUTPUT FILE NPS3023 SM2U1 HANDLES USER LOGGING FILES NPS3024 SPECIFIED ’LAST-INDEX=(&00)’ GREATER THAN HIGHEST FILE INDEX ’(&01)’. OPERAND ’*LAST’ ASSUMED Meaning The specified LAST-INDEX value in the //SEPARATE-FILES statement is greater than the highest file index (&01) in the input file. All the data up to the end of the input file will be transferred to the output file.
NPS4139 NPS4139 Messages SPECIFIED TIMES IN DEFINITION OF TIME WINDOW NOT IN ASCENDING ORDER (B) Routing code: R Weight: 99 Meaning The specified start time of a time window is greater than the corresponding end time.
Messages NPS4310 NPS4310 STATEMENT REJECTED (B) Routing code: R Weight: 99 Meaning The statement is invalid and must be reentered corrected. NPS4311 ERROR DURING STATEMENT ENTRY. SM2R1 TERMINATED ABNORMALLY (B) Routing code: R Weight: 99 Meaning Errors in statement input could not be recovered in procedure or in batch mode. No analysis is possible. NPS4312 ’CONNECTION-SET (&00)’ NOT DEFINED (B) Routing code: R Weight: 99 Meaning The name of the connection set is invalid or has not been defined.
NPS4317 Messages NPS4317 MORE THAN MAXIMUM PERMITTED NUMBER OF ’(&00)’ DEFINED NPS4318 SDF SYNTAX FILE DEFECTIVE OR INCORRECTLY ACCESSED. CONTACT THE SYSTEM ADMINISTRATOR Meaning Either no SDF syntax file has been assigned or the one assigned is invalid or cannot be accessed. NPS4319 SYSTEM ERROR WHEN PROCESSING SDF STATEMENTS. SDF RETURN CODE ’(&00)’ Response Contact the system administrator.
Messages NPS4354 NPS4354 SM2 LOGGING FILE CONTAINS NO CLOSE RECORD. ANALYSIS NOT COMPLETELY Meaning The SM2 logging file was not correctly closed. Possible reasons are - SM2 system task has abnormally terminated - system crash during creation of SM2 logging file. Response The file can be repaired by issuing the command //REPAIR-DISK-FILES FILE-STATUS=*ANY (FILE-NAME=dateiname). Subsequently, a CLOSE record should be attached with SM2U1.
NPS4553 NPS4553 Messages NO MEASUREMENTS FOUND FOR SPECIFIED ’USERID-SET (&00)’ (B) Routing code: R Weight: 50 Meaning The SM2 logging file contains no USER IDs of the specified USER ID set in the given analysis period. NPS4555 NO MEASUREMENTS FOUND FOR QUEUE TRANSITION (B) Routing code: R Weight: 50 Meaning Task queue analysis was requested but the SM2 logging file does not contain any queue records in the given analysis interval.
Messages NPS4652 NPS4652 NO MEASUREMENTS FOUND FOR DISTRIBUTION OF SERVICE TIMES FOR ’(&00)’ (B) Routing code: R Weight: 50 Meaning The disk (&00) for which analysis was requested was not active in the analysis period or was not monitored. NPS4653 NO MEASUREMENTS FOUND FOR DISTRIBUTION OF I/O REQUESTS FOR ’(&00)’ (B) Routing code: R Weight: 50 Meaning The disk (&00) for which analysis was requested was not active in the analysis period or was not monitored.
NPS4801 NPS4801 Messages INSUFFICIENT VIRTUAL ADRESS SPACE FOR ANALYSIS (B) Routing code: R Weight: 99 Meaning The storage space requested by the program could not be made available. The analysis run can be restarted using fewer reports. NPS4853 NO MEASUREMENTS FOUND DURING ANALYSIS INTERVAL FOR ’(&00)’ Meaning SM2 did not monitor the variable (&00) in the specified analysis interval.
9 Installation The SM2 software monitor system is supplied on a product tape with the files required for the SM2 monitoring program and the SM2R1 and SM2U1 utility routines. The following individual files are included: SM2 SM2U1 SM2R1 SYSLNK.SM2.130 SRMLNK.SM2.130 SYSLNK.SM2.130.SM2 SYSLNK.SM2.130.SM2U1 SYSLNK.SM2.130.SM2R1 SYSRMS.SM2.130 SYSNRF.SM2.130 SYSSII.SM2.130 SYSLIB.SM2.130 Prephases for loading and starting the corresponding phases from the libraries listed below SYSDAT.SM2.130.MTFILE SYSMSP.
Installation Installation procedure Standard installation of the SM2 monitoring program is via the product IMON. The following basic steps must be performed when installing without IMON: 1. Read in the product tape. It is recommended that the default user ID (defined using the system parameter DEFLUID) be used as the installation ID for SM2. Alternatively, you can use an ID which has been assigned the monitoring privilege SW-MONITORADMINISTRATION (TSOS has been assigned this privilege by default).
Installation Creating a new DSSM catalog The SM2 monitoring program is loaded and unloaded by the DSSM subsystem management facility. This requires the SM2 declarations in the valid DSSM catalog. These declarations are contained in the file SYSSSC.SM2.130, which is supplied along with the SM2 product tape. The SM2 declarations of file SYSSSC.SM2.130 must not be modified, with the exception of the user ID under which the objects to be dynamically loaded are stored.
Installation Loading and unloading the subsystem The SM2 subsystem is generated and started for the first time under an ID which has been assigned the privilege SW-MONITOR-ADMINISTRATION. This loads the SM2 modules. The BCAM-SM2 subsystem required for the RESPONSETIME monitoring program is only loaded when it is required.
10 Appendix 10.1 SDF syntax description This syntax description is based on SDF Version 4.1A. The syntax of the SDF command/ statement language is explained below in three tables. Table 9: Metasyntax Command and statement formats use certain characters and forms of representation; their meanings are described in Table 9. Table 10: Data types Variable operand values are represented in SDF by means of data types. Each data type represents a certain set of values.
SDF syntax description Appendix Table 11: Suffixes for data types Data type suffixes define additional rules for data type input. They contain a length or interval specification and can be used to limit the set of values (suffix begins with without), extend it (suffix begins with with), or declare a particular task mandatory (suffix begins with mandatory).
Appendix SDF syntax description Metasyntax Representation Meaning Examples UPPERCASE LETTERS Uppercase letters denote keywords (command, statement and operand names, keyword values) and constant operand values. Keywords begin with * HELP-SDF UPPERCASE LETTERS in boldface Uppercase letters printed in boldface denote guaranteed or suggested abbreviations of keywords. GUIDANCE-MODE = *YES = The equals sign connects an operand name with the associated operand values.
SDF syntax description Representation , list-poss(n): Alias: Appendix Meaning Examples A vertical bar identifies related operands within a structure. Its length marks the beginning and end of a structure. A structure may contain further structures. The number of vertical bars preceding an operand corresponds to the depth of the structure. SUPPORT = *TAPE(...) A comma precedes further operands at the same structure level. *TAPE(...) VOLUME = *ANY(...) *ANY(...) ...
Appendix Data types Data types Data type Character set Special rules alphanum-name A…Z 0…9 $, #, @ cat-id A…Z 0…9 command-rest freely selectable Not more than 4 characters; must not begin with the string PUB composed-name A…Z 0…9 $, #, @ hyphen period catalog ID Alphanumeric string that can be split into multiple substrings by means of a period or hyphen. If a file name can also be specified, the string may begin with a catalog ID in the form :cat: (see data type filename).
Data types Appendix Data type Character set Special rules filename A…Z 0…9 $, #, @ hyphen period Input format: file file(no) group [:cat:][$user.] (*abs) group (+rel) (-rel) :cat: optional entry of the catalog identifier; character set limited to A...Z and 0...9; maximum of 4 characters; must be enclosed in colons; default value is the catalog identifier assigned to the user ID, as specified in the user catalog. $user.
Appendix Data types Data type Character set filename (continued) Special rules #file (special case) @file (special case) # or @ used as the first character indicates temporary files or job variables, depending on the system parameter. file(no) tape file name no: version number; character set is A...Z, 0...9, $, #, @. Parentheses must be specified.
Data types Appendix Data type Character set Special rules partial-filename A…Z 0…9 $, #, @ hyphen period Input format: [:cat:][$user.][partname.] :cat: see filename $user. see filename partname optional entry of the initial part of a name common to a number of files or file generation groups in the form: name1.[name2.[...]] namei (see filename). The final character of “partname” must be a period. At least one of the parts :cat:, $user. or partname must be specified. posix-filename A...Z 0...
Appendix Data types Data type Character set Special rules product-version A…Z 0…9 period single quote Input format: [[C]' ][V][n]n.nann[' ] correction status release status where n is a digit and a is a letter. Whether the release and/or correction status may/must be specified depends on the suffixes to the data type (see suffixes without-corr, without-man, mandatory-man and mandatorycorr in Table 11). product-version may be enclosed within single quotes (possibly with a preceding C).
Data types Appendix Data type Character set Special rules x-string Hexadecimal: 00…FF Must be enclosed in single quotes; must be prefixed by the letter X. There may be an odd number of characters. x-text Hexadecimal: 00…FF Must not be enclosed in single quotes; the letter X must not be prefixed. There may be an odd number of characters.
Appendix Suffixes for data types Suffixes for data types Suffix Meaning x..y unit a) with data type integer: interval specification x minimum value permitted for “integer”. x is an (optionally signed) integer. y maximum value permitted for “integer”. y is an (optionally signed) integer. unit with “integer” only: additional units.
Suffixes for data types Suffix Appendix Meaning with (contd.) -wild(n) Parts of names may be replaced by the following wildcards. n denotes the maximum input length when using wildcards. Due to the introduction of the data types posix-filename and posixpathname, SDF now accepts wildcards from the UNIX world (referred to below as POSIX wildcards) in addition to the usual BS2000 wildcards.
Appendix Suffixes for data types Suffix Meaning with-wild(n) (continued) Replaces all strings that match any of the character combinations specified by s. s may also be an empty string. Any such string may also be a range specification “sx:sy” (see above). -s Replaces all strings that do not match the specified string s. The minus sign may only appear at the beginning of string s. Within the data types filename or partial-filename the negated string -s can be used exactly once, i.e.
Suffixes for data types Suffix Appendix Meaning with (contd.) -wildconstr(n) Specification of a constructor (string) that defines how new names are to be constructed from a previously specified selector (i.e. a selection string with wildcards). See also with-wild. n denotes the maximum input length when using wildcards. The constructor may consist of constant strings and patterns. A pattern (character) is replaced by the string that was selected by the corresponding pattern in the selector.
Appendix Suffixes for data types Suffix Meaning with-wildconstr (continued) The following rules must be observed when specifying a constructor: – The constructor must include at least one wildcard of the selector. – If the number of identical wildcards exceeds those in the selector, the index notation must be used. – If the string selected by the wildcard <...> or [...] is to be used in the constructor, the index notation must be selected.
Suffixes for data types Appendix Suffix Meaning with-wildconstr (continued) Examples: Selector Selection Constructor New name A//* AB1 AB2 A.B.C D<3><2> D1 D2 D.CB C./ C.AAD C.ABD C.BAF C.BBF G.<1>.<3>.XY<2> G.A.D.XYA G.A.D.XYB G.B.F.XYA G.B.F.XYB C./ C.AAD C.ABD C.BAF C.BBF G.<1>.<2>.XY<2> G.A.A.XYA G.A.B.XYB G.B.A.XYA G.B.B.XYB A//B ACDB ACEB AC.B A.CB G/XY/ GCXYD GCXYE GCXY. G.XYC 1) 1) The period at the end of the name may violate naming conventions (e.g.
Appendix Suffixes for data types Suffix Meaning without (contd.) -user Specification of a user ID is not permitted. -vers Specification of the version (see “file(no)”) is not permitted for tape files. -wild The file types posix-filename and posix-pathname must not contain a pattern (character). mandatory Certain specifications are necessary for a data type. -corr Input format: [[C]' ][V][n]n.
ISP syntax description Appendix 10.2 ISP syntax description Format description The statements issued to SM2 by nonprivileged users comprise the statement names and, in some statements, additional operands. The statement names and operands must be separated by at least one blank. Depending on the statement concerned, either positional or keyword operands can be used. Keyword operands can be entered in any order.
Appendix ISP syntax description Length of the statements A statement issued to SM2 can extend over more than one line. Continuation lines must be indicated as such by means of a hyphen (continuation character). When statements are entered via a data display terminal, the continuation character must be the last character in the line, i.e. the character immediately preceding the ETX character.
SM2 statements (overview) Appendix 10.3 Overview of SM2 statements The overview is split up in the same way as the descriptions of the statements, separating the statements for the SM2 administrator and those for the nonprivileged user. Overview of statements for the SM2 administrator ADD-BCAM-CONNECTION-SET Add connection set for BCAM-CONNECTION monitoring SET-NAME = ,CONNECTION-SELECTION = *BY-NEA-NAME(...) / *BY-PORT-NUMBER(...) *BY-NEA-NAME(...
Appendix SM2 statements (overview) ADD-CONNECTION-SET - Add connection set for RESPONSETIME monitoring SET-NAME = ,SET-DEFINITION = *BY-CONNECTION / *EXCEPT-CONNECTION ,CONNECTION-SET = list-poss(5): *CONNECTION(...) *CONNECTION(...) APPLICATION = *ALL / ,PARTNER = *ALL / ,PROCESSOR = *ALL /
SM2 statements (overview) Appendix ADD-ISAM-POOL - Define ISAM pool to be monitored POOL-NAME = ,SCOPE = *HOST-SYSTEM / *TASK(...) / *USER(...) *TASK(...) TSN = *USER(...) USER-ID = ,CAT-ID = *HOME-PVS /
Appendix SM2 statements (overview) END - Terminate SM2 run INITIATE-COSMOS - Prepare COSMOS monitoring program MODIFY-ADMINISTRATOR-ADMISSION - Admit additional SM2 administrators CONCURRENCY = *NO / *YES (part 1 of 2) MODIFY-COSMOS-PARAMETER - Modify parameters for COSMOS monitoring TITLE = *UNCHANGED / ,BUFFER-SIZE = *UNCHANGED / ,NUMBER-OF-BUFFERS = *UNCHANGED / ,ADDITIONAL-INFO = *UNCHANGED / *NONE / list-poss(2): *CONFIGURATION / *VM2000(...
SM2 statements (overview) Appendix (part 2 of 2) *STREAM-TAPE(...) FILE-NAME = list-poss(16): ,TASK-SELECTION = *UNCHANGED / *ALL / *SPECIFIED(...) *SPECIFIED(...) ,JOB-NAME = *NOT-SPECIFIED / list-poss(8): ,CATEGORY = *NOT-SPECIFIED / list-poss(8): ,USER-ID = *NOT-SPECIFIED / list-poss(8): TSN = *NOT-SPECIFIED / list-poss(16):
Appendix SM2 statements (overview) MODIFY-MEASUREMENT-PERIODS - Modify SM2 monitoring cycle OFFLINE-PERIOD = *UNCHANGED / ,ONLINE-PERIOD = *UNCHANGED / *SAME-AS-OFFLINE / ,SAMPLING-PERIOD = *UNCHANGED / MODIFY-RESPONSETIME-PARAMETER Modify parameters for RESPONSETIME monitoring SCOPE = *UNCHANGED / list-poss(2): *BUCKET / *CATEGORY ,DEFINITION = *UNCHANGED / *1 / *2 ,CONNECTION-NUMBER = *UNCHANGED /
SM2 statements (overview) Appendix OPEN-LOG-FILE - Open SM2 output file FILE = *STD / *BY-LINK-NAME ,BUFFER-OUTPUT = *NORMAL / *IMMEDIATE REMOVE-BCAM-CONNECTION-SET Exclude connection set from BCAM-CONNECTION monitoring SET-NAME = *ALL / REMOVE-CONNECTION-SET Exclude connection set from RESPONSETIME monitoring SET-NAME = *ALL /
Appendix SM2 statements (overview) REMOVE-ISAM-POOL- Remove ISAM pool(s) from ISAM monitoring parameters POOL-NAME = *ALL / ,SCOPE = *ANY / *HOST-SYSTEM / *TASK(...) / *USER(...) *TASK(...) TSN = *USER(...) USER-ID = ,CAT-ID = *ANY / *HOME-PVS / SELECT-HOSTS - Define hosts for SM2 statements and screen output HOST-NAME = *ALL / *LOCAL / list-poss(16):
SM2 statements (overview) Appendix (part 1 of 2) SET-COSMOS-PARAMETER - Define COSMOS monitoring parameters TITLE = C ’COSMOS’ / ,BUFFER-SIZE = 2 / ,NUMBER-OF-BUFFERS = 2 / ,ADDITIONAL-INFO = *CONFIGURATION / *NONE / list-poss(2): *CONFIGURATION / *VM2000(...) *VM2000(...) FILE-NAME = ,OUTPUT = *DISK (...) / *WRAP-AROUND(...) / *TAPE(...) / *STREAM-TAPE(...) *DISK(...) FILE-NAME = list-poss(16):
Appendix SM2 statements (overview) (part 2 of 2) ,EVENT-SELECTION = *ALL-BY-ADD-COSMOS-EVENT / *SPECIFIED(...) *SPECIFIED(...) EIA-INTERRUPT-CLASS = *ANY / list-poss(5): *SVC / *PROGRAM / *MACHINE-CHECK / *IO / *EXTERNAL ,EIA-SVC-NUMBER = *ANY / list-poss(8): ,IO-DEVICE = *ANY / list-poss(8): ,DAB-CACHE-ID = *ANY / list-poss(8):
SM2 statements (overview) Appendix SET-PERIODIC-TASK-PARAMETER - Define PERIODIC-TASK monitoring parameters LOG-TASKS = *NONE / *ALL / *SPECIFIED(...) *SPECIFIED(...) USER-ID = *NOT-SPECIFIED / list-poss(64): ,JOB-NAME = *NOT-SPECIFIED / list-poss(64): SET-RESPONSETIME-PARAMETER - Define RESPONSETIME monitoring parameters SCOPE = *BUCKET / list-poss(2): *BUCKET / *CATEGORY ,DEFINITION = *1 / *2 ,CONNECTION-NUMBER = 1024 /
Appendix SM2 statements (overview) SET-TASK-PARAMETER - Define TASK monitoring parameters TASK-SELECTION = *ALL / *SPECIFIED(...) *SPECIFIED(...) TSN = *NOT-SPECIFIED / list-poss(64): ,USER-ID = *NOT-SPECIFIED / list-poss(32): ,JOB-NAME = *NOT-SPECIFIED / list-poss(32): ,JOB-CLASS = *NOT-SPECIFIED / list-poss(32):
SM2 statements (overview) Appendix SHOW-SM2-STATUS - Output status of SM2 system tasks INFORMATION = *STD / *TASK / *EVENT-TRACE(...) *EVENT-TRACE(...) FROM = *ACTUAL /
Appendix SM2 statements (overview) Overview of statements for the nonprivileged user Switch to system mode Operation Operands BREAK Activate and deactivate ISAM pools Operation CHANGE-ISAMSTATISTICS Operands *NONE ADD-POOL = (*POOL( POOL-NAME=poolname1 *HOST-SYSTEM [,SCOPE = *TASK(TSN=tsn) *USER *HOME-PVS ,CAT-ID = catid *NONE ,REMOVE-POOL = (*POOL( *OWN ] )[,*P
SM2 statements (overview) Appendix Terminate monitoring Operation Operands END Monitor files Operation Operands FILE NAME=filename [ ,STATS = ON ] [ ] ,STATS = OFF Call user help functions Operation Operands HELP Define output mode Operation OUTPUT Operands TERMINAL Y[ES] [ = ] TER N[O] HARDCOPY Y[ES] [, = N[O] ] HC INTERVAL [number] [, = ] INT C[ONTROLLED] Insert remarks 438 Operation Operands REMARK [any text
Appendix SM2 statements (overview) Select reports Operation REPORT Operands STD ALL + [ - report-type ] + [ report-type ] - Start output of selected reports Operation Operands RESTART Select DAB cache area Operation SELECT-DAB-CACHE Operands cache-id [ADD-CACHE-ID= ] (cache-id1[,cache-id2]...) [,REMOVE-CACHE-ID= cache-id (cache-id1[,cache-id2]...
SM2 statements (overview) Appendix Select controllers for PCA CACHE report Operation Operands SELECT-PCACONTROLLER *NONE *ALL CONTROLLER= controller (controller1[,controller2]...) Select sort criteria and output information of PERIODIC TASK report Operation SELECT-PERIODICTASK-PARAMETER Operands *ALL USER-ID (userid1[,userid2]...) OUTPUT-INFORMATION = *ALL JOB-NAME (jobname1[,jobname2]...
Appendix SM2 statements (overview) Select SYMMETRIX controllers Operation SELECT-SYMMETRIXCONTROLLER Operands controller-mn [ADD-CONTROLLER-MN = ] (controller-mn1[,controller-mn2]...) [,REMOVE-CONTROLLER-MN = controller-mn (controller-mn1[,controller-mn2]...) ] *ALL Select UTM applications Operation SELECT-UTMAPPLICATION Operands name [ADD-APPLICATION= ] (name1[,name2]...) [,REMOVE-APPLICATION= name (name1[,name2]...
SM2 statements (overview) Appendix Monitor ISAM pools Operation START-ISAM-STATISTICS Operands POOL-NAME=poolname1 *HOST-SYSTEM [,SCOPE= *TASK(TSN=tsn) POOL=(*POOL( *USER *HOME-PVS [,CAT-ID= ] catid ] )[,*POOL()]...
Glossary The following terms have been used frequently in this manual. They are explained below: /390 mode Runtime environment of the /390 processor (processor used in the SIEMENS 7.500 system (CISC)). Program execution in /390 mode on SR2000 systems under OSD-SVP takes place under the control of the /390 firmware. The /390 firmware is the firmware component of SINIX-2000 on SR2000 systems under OSD-SVP which is used to map /390 code to RISC code.
Glossary assignment of paging activities to the initiating task The system initiates all paging I/O operations directly in the SIH state. However, SM2 does not assign all paging I/O operations to the SYSTEM category, but sometimes to the initiating task. For SM2, the initiating task is that task which caused a page fault during page access. Two chains have to be distinguished: 1. Only one page is read. The full firmware duration of the input operation is assigned to the initiating task and its category.
Glossary channels Channels are used for data interchange between the CPU, main memory and the peripheral devices. Multiplexer channel (generic term): can handle several I/O operations simultaneously. Byte multiplexer channel (BYMUX): data is transferred in byte-interleaved fashion between main memory and several simultaneously active I/O devices. This type of channel is used to connect slow devices.
Glossary An SDV rejected in SDV fast release mode is ignored; this also results in an increase in waiting time for the device. In "offline seek" mode, the time between the first SDV and the termination message for the second SDV is counted. CPU time and CPU service units on SR2000 On SR2000 systems, the CPU time consumed depends on whether the code is executed in /390 mode (compatibility mode) under the /390 firmware or in RISC mode directly on the RISC CPU.
Glossary dilation factor Dilation factors can be determined for individual tasks, for specific task classes and on a system-global basis. Dwell time Dilation factor = ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ Productive RST Productive RST = productive CPU RST + productive I/O RST For further information on productive RST, see “time equivalent for the productive performance” on page 458. A dilation factor smaller than 1 can occur when a task uses asynchronous I/O. In this case, the task uses 2 or more resources simultaneously.
Glossary 4. Further time spent in Q4 except for boursing, ITC, PASS/VPASS and waiting for response to console message. 5. Wait for activation (time spent in Q5). 6. Wait for admission (time spent in queue Q6). 7. Wait in Q7 for hardware error recovery (HERS). 8. Further time spent in Q12 except for boursing and waiting for response to console message. 9. Hardware duration of I/O operations for paging page transfers.
Glossary global storage (GS) Global storage is a form of semiconductor-based expansion memory which has been made non-volatile by a number of measures. It has an access granularity of 4K and can be expanded up to 2x4 Gbyte depending on the system. As with expanded storage, transfers between global storage and main memory are initiated using machine instructions. This means that an I/O request is processed synchronously if handled from the cache. There is thus no change of task.
Glossary interaction Generic term for wait, response, think, and transaction processes (RESPONSETIME monitoring program). main memory Memory area which can be addressed directly by the CPU. The program instructions are read and processed in this area. overall performance The productive performance and the dilation, i.e.
Glossary page fault BS2000 is an operating system with virtual addressing, i.e. it supports several address spaces simultaneously. The virtual address spaces and the real main memory are managed in units of 4-Kb pages. The DEMAND PAGING method is used for mapping virtual pages onto real memory page frames: When an attempt is made to access a page that is not in main memory, the hardware detects this condition and uses a page fault interrupt to notify the operating system.
Glossary paging in BS2000 The number of addressable virtual pages is usually greater than the number of page frames available in main memory. For the removal of pages which can no longer be kept in main memory, see “page fault” on page 451. The main memory management strategies are based on the assumption that the programs (or tasks) will only address a limited set of the total number of virtual pages within a specific period of time, i.e. that the programs are more or less local.
Glossary The PPC value is again supplied as a measure of how local a task is, but it is less precise here than with task-local management. The check is made and working set pages are removed only if free page frames are required. This is why UPG may become greater than the working set, especially if the main memory is large. The UPG/PPC relationship which exists in task-local management thus does not apply to global management. 3.
Glossary processor states Program interrupts are caused by – – – – – input/output requests calls to the Control System timers errors paging requests The system distinguishes between the following processor states when handling programs and interrupts: TU TPR SIH MEH Processor state for user programs Processor state for program interrupts Recognition state for program interrupts Recognition state for machine errors Interruptible Interruptible; in part non-interruptible Interruptible by MER only
Glossary SDV (Start Device) Instruction which initiates an input/output operation. service times definition (DCS, I/O operations) Detailed monitoring of service times is possible on XS systems with DCS, the interface between the operating system, the I/O processor and the physical devices.
Glossary DQT Device Queue Time HW TIME Hardware service time FPT Function Pending Time FW TIME Firmware service time DDT Device Disconnect Time SW TIME Software service time DCT Device Connect Time RST Remaining Service Time software service time (DCS) See “service times definition (DCS, I/O operations)” on page 455.
Glossary The task queues described in the following contain tasks waiting for an event that is very remote in time before they become ready. These tasks are deactivated, i.e. they have lost the right to use main memory. Q7 Not used Q8 Not used Q9 Not used Q10 Hold queue for tasks placed in the hold state by the system or the operator in an emergency or overload situation. Tasks in the device queue or the WHEN queue.
Glossary time equivalent for the productive performance In determining the RST (resources service time), a distinction is made between the CPU and the peripheral devices as follows: 1. For the CPU the RST is the time in which instructions are processed in the TU and TPR states. This time is called productive CPU RST (the SIH share of the productive performance is not counted; see above). 2. For the peripheral equipment, the RST is the firmware service time of the devices for performing an I/O operation.
Glossary virtual address space subdivision The virtual address space is subdivided as follows: 1. Class 1 memory Resident memory for system module code. The size of this memory segment is specified at system generation time and remains constant for the session. 2. Class 2 memory Paging memory for system module code. The size of this memory segment depends on generation specifications and remains constant for the session. 3.
Eine Dokuschablone von Frank Flachenecker by f.f.
List of Figures Figure 1: SM2 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Figure 2: Collecting monitored data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Figure 3: Relationship between the sampling cycle and the monitoring cycle . . . . . . . .
Eine Dokuschablone von Frank Flachenecker by f.f.
List of Tables Table 1: Authorization table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 Table 2: SM2 monitored variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 Table 3: Monitoring programs used to locate overloaded resources. . . . . . . . . . . . . . . . .28 Table 4: Overview of the SM2 monitoring programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Eine Dokuschablone von Frank Flachenecker by f.f.
Related publications Please apply to your local office for ordering the manuals. [1] DAB V6.1A (BS2000/OSD) Disk Access Buffer User Guide Target group This manual is addressed to systems support. Contents The manual begins with some introductory chapters dealing with DAB caching, the DAB cache media and the DAB functions, and continues with detailed descriptions of the DAB commands.
Related publications [3] BS2000/OSD-BC V2.0A Executive Macros User Guide Target group The manual addresses all BS2000/OSD assembly language programmers. Contents The manual contains a summary of all Executive macros, detailed descriptions of each macro with notes and examples, including job variable macros, and a comprehensive general training section. Order Number U3291-J-Z125-8-76 New functionality about BS2000/OSD V4.
Related publications [6] BS2000/OSD-BC V4.0 Introductory Guide to Systems Support User Guide Target group This manual is addressed to BS2000/OSD systems support staff and operators. Contents The manual covers the following topics relating to the management and monitoring of the BS2000/OSD basic configuration: system initialization, parameter service, job and task control, memory/device/user/file/pubset management, assignment of privileges, accounting and operator functions.
Related publications [9] VM2000 (BS2000/OSD) Virtual Machine System User Guide Target group System administrators and operators in BS2000, VM2000 and VM administrators Contents The manual describes the VM2000 Virtual Machine System for BS2000 guest systems.
Related publications [12] PDN-GA (PDN) Generating a Data Communication System User Guide Target group Generators of data communication systems, network and system administrators Contents This manual describes network generation from the DCAM and PDN viewpoints, as well as the structure and use of KOGS sources, e.g. for ISDN and LAN accesses. It also provides a detailed description of the KOGS macros and illustrates important implementations by means of tailor-made generation examples.
Related publications [14] BS2000/OSD-BC V4.0 Commands, Volume 2, D – MOD-I User Guide Target group This manual is addressed to nonprivileged users and systems support staff. Contents Volume 2 contains the BS2000/OSD commands DECLARE-... to MODIFY-I... (basic configuration and selected products) with the functionality for all privileges. The command and operand functions are described in detail, supported by examples to aid understanding.
Related publications [16] BS2000/OSD-BC V4.0 Commands, Volume 4, S – SH-O User Guide Target group This manual is addressed to nonprivileged users and systems support staff. Contents Volume 4 contains the BS2000/OSD commands SAVE... to SHOW-O... (basic configuration and selected products) with the functionality for all privileges. The command and operand functions are described in detail, supported by examples to aid understanding.
Related publications [18] BS2000/OSD-BC V4.0 Commands, Volume 6, Output in S Variables and SDF-P-BASYS User Guide Target group This manual is addressed to programmers and users who write procedures. Contents Volume 6 contains tables of all S variables that are supplied with values by the SHOW commands in conjunction with structured output. Further chapters deal with: - introduction to working with S variables - SDF-P-BASYS V2.
Related publications [21] SM2 V13.0A (BS2000/OSD) Software Monitor Volume 2: Analysis and Display of SM2 Monitored Data Target group This manual is addressed to users and systems support staff. Contents The monitoring system SM2 supplies users with statistical data on the performance of their DP systems and on resource utilization.
Related publications [23] BS2000/OSD V4.0 Functional Extensions and Supplementary Documentation User Guide Target group This manual is addressed to systems support staff, Assembler programmers and BS2000 users. Contents The manual contains supplementary information for the following manuals, for which there will be no new edition for BS2000/OSD-BC V4.
Index /390 CPU time 446 A ACF report 209 activation 443 activation decision 443 ACTIVE PARAMETER screen 319 ACTIVITY report 211 ADD-CONNECTION-SET statement 69 ADD-COSMOS-EVENT statement 72 ADD-FILE statement 73 ADD-ISAM-POOL statement 74 administration facility 76 switch to 76 admit additional SM2 administrators 83 alias 408 alphanum-name (data type) 409 attributes category 222 attributes of the SM2 output file 195 freely selected 196 preset 195 authorization table 14 B background monitoring 11 backgroun
Index bottleneck analysis 28 boursing mechanism 447 BREAK function 153 BREAK statement 157 BUCKET parameters 35 BYMUX channel 445 byte multiplexer channels 228 C cache for PCA DEVICE report, select 174 cache utilization 43 caching 444 CALL-ADMINISTRATION-PART statement 76 CALL-EVALUATION-PART statement 77 cat (suffix for data type) 420 category 222 CATEGORY QUEUE report 222 CATEGORY report 220 CATEGORY WSET report 225 cat-id (data type) 409 CHANGE-ISAM-STATISTICS statement 158 CHANGE-MEASUREMENT-PROGRAM st
Index control output 152 controlled mode 152, 167 controller select 176 with caches 272 corr (suffix for data type) 420, 421 COSMOS (monitoring program) 39 define monitoring program definition 115 modify monitoring program definiton 84 prepare 82 CPU report 235 CPU service units 446 CPU time 446 CPU utilization 345 c-string (data type) 409 D DAB (monitoring program) 39 DAB CACHE report 240 DAB cache, select 173 DAB report 237 data records 18 data types in SDF 409 date (data type) 409 deactivation 446 defin
Index disk devices define for monitoring 123, 124 DISK FILE report 248 disk statistics 39 DISK-FILE (monitoring program) 40 DLM (monitoring program) 40 DLM report 250 DMS I/O operations 447 DRV implementation 351 dwell time 26, 447 dynamic IO reconfiguration 32 E efficient DP system usage 29 efficient use of SM2 27 END statement 81, 163 event-driven monitoring method 344 events define for monitored data acquisition (COSMOS) 72 remove from monitoring program definition (COSMOS) examples SM2 monitoring progr
Index fixed (data type) 409 forced deactivation 446 format description (SM2) 422 free pool 453 function states 212, 454 G gen (suffix for data type) 420 global index 418 GLOBAL report 255 global storage (GS) 41, 449 GS (monitoring program) 41 GS report 256 GSVOL (monitoring program) 41 GSVOL report 257 H hardware duration 449 hardware service time DCS 449 non-DCS 449 HELP statement 165 hiperfile concept 449 HIPLEX MSCF® 42 host define for SM2 statements and screen output host communication 42 HSMS (monitor
Index inquiry-and-transaction mode 25 insert remarks 168 installation 401 with IMON 402 integer (data type) 411 interaction 45, 450 interactive mode 25 criteria 25 interactive processing 25 internal program name 65 INWAIT time 35 IO reconfiguration 32 ISAM nonprivileged (monitoring program) 55 privileged (monitoring program) 42 ISAM buffer management 42 ISAM pools 42, 56, 158 exclude from the monitoring process (nonprivileged user) 188 excluded, define 108 include and exclude in the monitoring process (non
Index M main memory 450 management 261 utilization 342 man (suffix for data type) 420, 421 management selective 453 system-global 452 task-local 452 mandatory (suffix for data type) 421 MAX MPL 222 mean values 19 MEASUREMENT STATUS screen 139, 328 request 139 memory classes 459 MEMORY report 261 messages 365 metacharacters 422 MIN MPL 222 minimize arm movements 458 MISSED RECORDS 197 MODIFY-ADMINISTRATOR-ADMISSION statement 83 MODIFY-COSMOS-PARAMETER statement 84 MODIFY-MEASUREMENT-PERIODS statement 93 MOD
Index monitoring method 15, 344 based on monitoring cycle 15 based on sampling cycle 15 event-driven 15, 340, 344 sample-driven 344 monitoring program run start 144 terminate 147 monitoring programs 33, 78 stop and restart with new monitored objects monitoring status, output 187 monitoring task, activate 14 MSCF (monitoring program) 42 MSCF report 266 multiprocessor system 229 multiprogramming level 222 multi-step transaction 25 78 N name (data type) 411 NET DEVICE report 269 NET-DEVICE (monitoring progr
Index OPEN-LOG-FILE statement 101 operand keyword 422 positional 422 operation 26 OUTPROC time 35 output cycle 151, 153 output mode automatic 151 define 166 output priority (devices) 160 OUTPUT statement 166 overall performance 450 overhead 450 overview of statements for nonprivileged users 437 of statements for SM2 administrators 424 P page fault 451 real 451 page reclaims 451 paging 452 paging activities, assign 444 paging I/O operations 453 paging memory 453 paging rate 453 PAM output file 197 partial-f
Index PERIODIC TASK report 282 define sort criterion and output information PERIODIC-TASK (monitoring program) 43 PFA (monitoring program) 44 PFA CACHE report 286 PFA cache, select 179 PFA CONTROLLER report 288 PFA reports 285 PGE task 453 positional operands 422 POSIX (monitoring program) 44 POSIX report 290 posix-filename (data type) 412 posix-pathname (data type) 412 PPC 216, 452 primary administrator 12, 83 PRIOR task scheduler 222 privileged user 12 processor states 454 productive CPU RST 458 producti
Index report identifiers 171 REPORT statement 169 reports 153, 201 select 169 request queue 232 request user help information 165 resource service time 450 resource utilization CPU 340 external storage 339 response time 26, 45, 96, 128 response time statistics 49, 95 bucket-specific 95, 127 category-specific 95, 127 define settings 127 examples 49 modify settings 95 RESPONSETIME (monitoring program) RESPONSETIME report 292 RESTART statement 172 RISC mode 454 RST (Resource Service Time) 450 45 S SAM outpu
Index SENSE-SDV 445 sep (suffix for data type) 420 service time 450 service time statistics 50 service times definition (DCS) 455 SERVICETIME (monitoring program) 50 SERVICETIME monitoring values 351 SET-BCAM-CONNECTION-PARAMETER statement 112 SET-CHANNEL-IO-PARAMETER statement 114 SET-COSMOS-PARAMETER statement 115 SET-DISK-FILE-PARAMETER statement 124 SET-DISK-PARAMETER statement 123 SET-PERIODIC-TASK-PARAMETER statement 125 SET-RESPONSETIME-PARAMETER statement 127 SET-SERVICETIME-PARAMETER statement 130
Index SM2 reports 152, 201, 202 SM2 screen output 201 representation of values 206 SM2-PA (analysis program) 189 SM2R1 analysis, prepare 357 software duration 456 software service time DCS 456 non-DCS 456 standard categories 222 standard installation 402 standardized CPU service units 446 standardized CPU time 446 Start Device (SDV) 455 start program 57 start report output 153, 184 for selected reports 172 start SM2 57 START statement 184 START-ISAM-STATISTICS statement 185 START-MEASUREMENT-PROGRAM statem
Index SYMMETRIX report 302 syntax description 405 SYSSTAT (monitoring program) 51 system capacity planning 27 system counters 19 system mode, change to 157 system privilege SWMONADM 12 system resource utilization (SM2) 339 T TASK (monitoring program) 52 task CPU time 446 TASK LOCK MANAGER (monitoring program) 53 task monitoring activating 189 task queues 456 TASK user-specific (monitoring program) 56 tasks and devices for task statistics, define 132 deactivated 457 monitored data acquisition, define 125 TC
Index U under (suffix for data type) 415 UPG 452 user nonprivileged 12 SM2 12 user (suffix for data type) 421 USER MEASURED OBJECTS screen user monitoring programs 55 user task statistics 342 UTC time 19 UTM (monitoring program) 53 UTM APPLICATION report 313 UTM report 310 336 V variables relevant 345 vers (suffix for data type) 421 virtual address space subdivision 459 VM (monitoring program) 54 VM2000 operation 347 VM2000 report 316 VM2000 system 54, 316 VOLUME load 351 vsn (data type) 413 W wait time
Index without-gen (suffix for data type) 420 without-man (suffix for data type) 420 without-odd (suffix for data type) 420 without-sep (suffix for data type) 420 without-user (suffix for data type) 421 without-vers (suffix for data type) 421 with-under (suffix for data type) 415 with-wild(n) (suffix for data type) 416 working set 452 X x-string (data type) 414 x-text (data type) 414 490 U3585-J-Z125-8-76
Contents 1 1.1 1.2 1.3 1.4 1.5 1.6 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Brief description of the SM2 monitoring system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Target group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary of contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 3.3 4 4.1 4.1.1 4.1.2 4.2 4.3 HSMS Monitored data on file migration . . . . . . . . . . . . . . . . . . . . . . . GS Monitored data on access to global storage . . . . . . . . . . . . . . GSVOL Monitored data on volumes in global storage . . . . . . . . . . . . . ISAM Monitored data on ISAM pools . . . . . . . . . . . . . . . . . . . . . . . . MSCF Monitored data on communication between hosts . . . . . . . . . NET-DEVICE Monitored data on network devices . . . . . . . . . . . . . . . . . . . .
Contents CALL-EVALUATION-PART Switch from administration facility to evaluation part . . . . . . . . . . . . . . . . . . . . . . . . . 77 CHANGE-MEASUREMENT-PROGRAM Stop current monitoring program run and restart it with new monitored objects . . . . 78 CLOSE-LOG-FILE Close SM2 output file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 END Terminate SM2 run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 4.4 SET-PERIODIC-TASK-PARAMETER Define PERIODIC-TASK monitoring parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . SET-RESPONSETIME-PARAMETER Define RESPONSETIME monitoring parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . SET-SERVICETIME-PARAMETER Define SERVICETIME monitoring parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SET-SYSSTAT-PARAMETER Define SYSSTAT monitoring parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 4.5 4.6 4.7 5 5.1 REPORT Select reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RESTART Start output of selected reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SELECT-DAB-CACHE Select DAB cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SELECT-PCA-CACHE Select cache for PCA DEVICE report . . . . . . . . . . . . . . . . . . . . . .
Contents 5.2 DAB reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DAB report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DAB CACHE report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DEVICE report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 6 6.1 6.1.1 6.1.2 6.1.3 6.2 6.2.1 6.2.2 6.2.3 6.3 6.3.1 6.3.2 6.3.3 6.3.4 6.4 Notes on SM2 operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System resource utilization by SM2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . External storage utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CPU utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Eine Dokuschablone von Frank Flachenecker by f.f.
SM2 V13.0A (BS2000/OSD) Software Monitor Volume 1: Administration and Operation Target group This manual is addressed to users and systems support staff. Contents The monitoring system SM2 supplies users with statistical data on the performance of their DP systems and on resource utilization. Volume 1 of the manual describes operation of the SM2 monitor, the SM2 monitoring programs and the SM2 screen reports. Analysis and display of the SM2 monitored data are dealt with in Volume 2.
Siemens AG Information and Communication Products Computer Systems User Documentation BS2000 81730 Munich Germany Fax: (0 89) 6 36-4 04 43 e-mail: DOCetc@mchp.siemens.de http://manuals.mchp.siemens.de Submitted by Comments on SM2 V13.