Batch SMF records contain information about jobs, programs, TSO sessions, system tasks, APPC/MVS ASCH scheduled Transaction Programs (TPs), and measured usage license charges. These records are generated when certain events occur during the life cycle of an address space. The activities of a job from reader input to system purge are made up of many events that are recorded as separate SMF records. These SMF records are interdependent and must all be used to completely reconstruct the job, TSO session, started task, or APPC/MVS TP. Figure 6-2 shows events in the life cycle of a job and the SMF records that are created for those events. Two views or perspectives of ASCH scheduled Transaction Programs (TPs) are supported by SMF. The address space perspective of the TP execution is provided by the type 30 records, while the per transaction perspective is provided by the SMF type 33 APPC/MVS TP Accounting record. Figure 6-3 shows the flow of events in the life of an APPC/MVS ASCH standard scheduled Transaction Program (TP). Figure 6-4 shows the flow of events in the life of an APPC/MVS ASCH multi-trans scheduled Transaction Program (TP).
* Job Submission | | | * Job Initiation (Type 30-1) | | | | | | * Step Termination (Type 30-4) | | | | | | | | | * Step Termination (Type 30-4) | | | | | | | | | | | | * Job Termination (Type 30-5) | | | | | | | | | | \\ > TIME > /----------------------+---------+-------------+-------------+-------------+------+----------------------------------/ | | | | | | | | | | | * Interval Last (Type 30-3) | | | | | | | | | * Interval (Type 30-2) | | | | | | | | | | | | | | | * Interval (Type 30-2) | | | | | | | | | | | * Interval (Type 30-2) | | | | | | | | | | | * Interval Last (Type 30-3) | | | | | * Interval (Type 30-2)
Figure 6-3. Job, Started Task, or Session Flow Using Type 30 Records
*** APPC/MVS ASCH Standard Scheduled TP SMF Recording *** * APPC/MVS ASCH Standard TP Request Recognized by APPC | | | * ASCH TP Initiation (Type 30-1) | | | | | | * TP Step Termination (Type 30-4) | | | | | | | | |* APPC/MVS TP Accounting (Type 33) | | || | | || | | ||* TP Job Termination (Type 30-5) | | ||| | | ||| | | ||| * JES Output Writer (Type 6) | | ||| | | | ||| | | | ||| | * TP Purge (Type 26) | | ||| | | | | ||| | | | | ||| | | \\ > TIME > /------------------------+---------------+---+---------------------------/ | | | | | | | | | | | | | | * TP Last Interval (Type 30-3) | | | | | * TP Interval (Type 30-2) | | * TP Interval (Type 30-2)
Figure 6-4. APPC/MVS ASCH Standard Scheduled Transaction Program (TP) Flow
*** APPC/MVS ASCH Multi-trans Scheduled TP SMF Recording *** EVENT * APPC/MVS ASCH Multi-trans TP Request Recognized by APPC | | * TP Initiation | | | | * Get Trans | | | | | | * Get Trans | | | | | | | | * Get Trans | | | | | | | | | | * Ret Trans | | | | | | | | | | | | * Get Trans | | | | | | | | | | | | | | * Get Trans | | | | | | | | | | | | | | | | * Ret Trans * Output Writer (Type 6) | | | | | | | | | | | | | | | | | | | * TP End | * Purge (Type 26) | | | | | | | | | | | | \\ > TIME > /--------+-----+-----+-----+-----+--+--+-----+-----+-----++++--------------------------------------/ | | | | | | | | | |||| | | | | | | | | | |||* TP Job End (Type 30-5) | | | | | | | | | ||| | | | | | | | | | ||* TP Step End (Type 30-4) | | | | | | | | | || | | | | | | | | | |* TP Last Interval (Type 30-3) | | | | | | | | | | | | | | | | | | | * Type 33 Shell | | | | | | | | | | | | | | | | | * Type 33 TP | | | | | | | | | | | | | | | * Type 33 TP 33 TP | | | | | | | | | | | | | * Type 33 Shell | | | | | | | | | | | * Interval (Type 30-2) | | | | | | | | | * Type 33 TP | | | | | | | * Type 33 TP | | | | | * Type 33 TP | | | * Type 33 Shell | + Job Initiation (Type 30-1)
Figure 6-5. APPC/MVS ASCH Multi-trans Scheduled Transaction Program (TP) Flow The first group of Batch SMF record types is the execution type records. These record types contain measurement data from the reader start timestamp up to the termination of the job. MVS/SE2 and later versions of MVS should produce and use SMF type 30 records. SMF TYPE 30 RECORD The SMF type 30 record, or Common Address Space Work Record, has six subtypes, the first five of which are used by CA MICS. o SMF Type 30 Subtype 1 - Initiation Record The SMF type 30 subtype 1 record is written when an initiator selects a batch job, a started task begins, a TSO user logs on, or an APPC/MVS ASCH scheduled TP is selected by an APPC initiator. It contains user identification, programmer's name, accounting information from the JOB statement, and RACF and ACF2-related information. o SMF Type 30 Subtype 2 - Interval Record If interval SMF recording is active (see Section 6.2.1.3) and a step has not completed within the interval time period (normally 15, 30, or 60 minutes), an SMF type 30 subtype 2 record is written showing resources consumed over the interval. This SMF record contains all of the same resource measurements as the SMF type 30 subtype 4 step end record, except for the initiator CPU time measures, the amount of SYSIN card images read by the reader, and data space storage. The SMF type 30 interval records can be synchronized to be written at any minute of the hour. When synchronization is in effect, the first interval record for a step may represent less than a complete interval. The first interval record is written at a time dictated by the SYS1.PARMLIB(SYNCPARM) value. Any subsequent subtype 2 records for the step will represent complete intervals. o SMF Type 30 Subtype 3 - Interval End Record If interval SMF recording is active (see Section 6.2.1.3) and a step ends, a SMF type 30 subtype 3 interval record is written. It contains measures of resource consumption since either the start of the step or end of the previous interval. If a step ends before the specified interval duration has elapsed, no SMF type 30 subtype 2 records are produced. A single SMF type 30 subtype 3 interval end record is produced. It contains all of the same resource measurements as the SMF type 30 subtype 4 step end record, except for a few values (see section 10.2.4, USRSSF4 exit). o SMF Type 30 Subtype 4 - Step End Record The SMF type 30 subtype 4 record is written at the end of each job step, TSO session, and started task to record such resource-related data as elapsed time, CPU time, main storage allocated and used, EXCP count by device address, paging activity for the step, and usage data for products registered with IBM's Measured Usage License Charging (MULC) subsystem. It is written at normal or abnormal termination of the job step or system task. o SMF Type 30 Subtype 5 - Job Termination Record The SMF type 30 subtype 5 record is written at the end of each job execution to summarize its resource usage. This record includes the start and stop time for processing of the job by the Reader/Interpreter, the job initiation time and date, the number of steps in the job, accounting information, and the completion code of the last step of the job. It is written at the normal termination of the job. o SMF Type 33 - APPC/MVS TP Accounting Record The SMF type 33 record is produced once for each APPC/MVS ASCH standard scheduled TP and represents the complete resource utilization for the TP. For multi-trans TPs, the TP remains in execution between conversation requests from partner TPs. This type of TP is composed of two parts, the TP portion and the multi-trans shell portion. An SMF type 33 record is produced at the completion of each conversation from a requesting partner TP. It is also produced at the completion of each execution of the multi-trans shell portion of the TP. Type 33 records produced for standard TPs and the TP portion of multi-trans TPs contain timestamp information for each event from the moment that APPC/MVS first became aware of the TP request through TP completion. Resource utilization information is limited, but complete accountability of the requesting partner TP is provided. This record is similar to the transaction records provided by applications such as CICS and IMS. The type 33 records produced for the shell portion of a multi-trans TP provide only generic accounting information and minimal timestamps since the shell execution is not related to any particular partner TP. o SMF Type 6 - Output Writer The SMF type 6 record is written when a writer has finished processing a SYSOUT class or a form within a class. It includes the date and time the writer began processing this job, the number of records written per form number and class, an I/O error flag, and the total number of data sets processed by the writer for this job. CA MICS currently reads JES2, JES3, External Writer, and PSF generated SMF type 6 records. o SMF Type 25 - JES3 Device Allocation The SMF type 25 record is written for each job processed by JES3 main device scheduling and is written after JES3 has scheduled devices for this job. One type 25 record is written for all device allocations required through the user's DD statements for the job. This record contains allocation-related information such as the number of tape and disk volumes fetched and mounted, and the time and date of JES3 device verification. o SMF Type 26 - Job Purge The SMF type 26 record is written at job purge time after all SYSOUT for the job is processed. This record may be written much later than the other SMF records on the job because it is not written until all the SYSOUT is processed, including held SYSOUT. This record is critical because it indicates the end of a job and it contains timestamp and network information about the entire job that is not available elsewhere. This record contains operation information such as JES job class, and the start and stop times and dates for the reader, the converter, the execution processor, and the output processor. o SMF Type 89 - Usage Data SMF type 89 records are generated at specified intervals (maximum one hour) and collect usage information about software products registered with IBM's Measured Usage License Charging (MULC) subsystem. IBM provides a utility program (IFAURP) that both manages the archival of SMF type 89 records and analyzes the record contents to determine IBM software product usage levels and corresponding licensing rates.
|
Copyright © 2014 CA.
All rights reserved.
|
|