ATFEXTR command: extract OMEGAMON V5.3 ATF Enhanced Summary records from IMS log

Transcription

1 ATFEXTR command: extract OMEGAMON V5.3 ATF Enhanced Summary records from IMS log Last changed: 31 January 2017, 11:10 AM The following changes to IMS Performance Analyzer V4R4 take effect when the fix for APAR PI63797 is applied. Support is added to allow extract of data from the OMEGAMON XE for IMS on z/os V5.3 ATF Enhanced Summary record introduced by APAR OA This support is in the form of two commands that are specified using the batch interface: ATFCODE: Command to specify the ATF log prefix. ATFEXTR: Command to create CSV extracts from ATF Enhanced Summary records in an IMS log. Requirement To use these options with IMS Performance Analyzer V4R4 you must apply the fix for APAR PI Background OMEGAMON v530 introduced functionality to create an Enhanced ATF Summary record in the IMS Log. This enhanced summary record includes a fixed part followed by up to six repeating sections. APAR PI63797 introduces a facility to extract data from these new records and produce a series of files in CSV format so that ATF data can be loaded into analytical engines such as DB2. One CSV file is always produced for the fixed or header part of the record, as well as one CSV file for each repeating section that is requested. Structure of Extended ATF Summary records The data in an ATF record is hierarchical: one transaction can use many databases, and each database may have had a variety of calls made against it. Therefore one record cannot be represented simply as a single row in a CSV file. Section Description 1 Fixed section The start of the log record contains the log code, subsystem, and time stamp. Also includes: - Details about the transaction: who ran it and when, as well as tokens to uniquely identify the unit-of-work. - Overall response time and resource usage performance measurements. - Information about what other sections to expect in the remainder of the record. 2 DBD Databases referenced by the transaction. 3 DLI DB DLI DB Call types, counts, elapsed times, and CPU times. 4 DLI TM DLI TM Call types, counts, elapsed times, and CPU times. 5 DB2 DB2 Call types, counts, elapsed times, and CPU times. 6 MQ MQ Call types, counts, elapsed times, and CPU times. 7 Other Other counts, elapsed times, and CPU times. Page 1 of 6

2 Format of CSV extract files Records in the CSV extract files that originate from the same source record can be correlated using a common key. The correlating key includes all the subfields in the Correlation ID and the Recovery Token: AESCORID AESCORPST AESCORTIME AESCREID AESCREOASN AESCRECOMN IEDE IEDE A The first CSV file contains the key and the fixed part of the record. HEADER CSV: KEY AESSTART AESELAPS AESTRAN AESPSB IEDE,0001, CEXTCONV CEXTPGM Subsequent CSV files contain the key and the content from each repeating section. DBD CSV: KEY IEDE,0001,2016 AESXSDBN DI21PART DLIDB CSV: KEY AESXSDLT AESXSDLG AESXSDLN AESXSDLE AESXSDLC IEDE,0001,2016 GHU READ IEDE,0001,2016 ISRT INSERT DLITM CSV: KEY AESXSDLT AESXSDLG AESXSDLN AESXSDLE AESXSDLC IEDE,0001,2016 GU GU IEDE,0001,2016 ISRT ISRT DB2 CSV: KEY AESXSDLT AESXSD2N AESXSD2E AESXSD2C IEDE,0001,2016 SELECT/FETCH IEDE,0001,2016 UPDATE Page 2 of 6

3 MQ CSV: KEY AESXSMQT AESXSD2N AESXSD2E AESXSD2C IEDE,0001,2016 MQGET IEDE,0001,2016 MQOPEN OTHER CSV: KEY AESXSOT AESXSOF AESXSON AESXSOBP AESXSOE IEDE,0001,2016 VSAM I/O IWAIT Bit flags expanded IMSPALOG commands and parameters Use the ATFCODE command to specify the log code prefix to identify ATF records in the log file. This command is required. ATC is an alias for the ATFCODE command. IMSPALOG ATFCODE ATC(xx) where xx is the OMEGAMON ATF User log record code Use the ATFEXTR command to specify which repeating sections are to be written to CSV files. IMSPALOG ATFEXTR( LABELS NOLABELS, SECTIONS(DBD, DLIDB, DLITM, DB2, MQ, OTHER)) Parameters LABELS SECTIONS (Optional). Write a list of the field names at the start of each extract. By default no labels are produced. (Optional). Specify which repeating sections in the log record are to be written to CSV extract files. Any combination of section names can be specified, but there must be one DD statement provided in the JCL corresponding to each CSV section that is specified. There is no keyword for the HEADER section because it is produced by default, but the ATFHEAD DD statement must always be specified. The following table correlates ATF section names with the DD statement required for the IMS PA extract job: Page 3 of 6

4 ATF Section name SECTION parameter ddname for CSV file keyword DBD section DBD //ATFDBD DLI DB section DLIDB //ATFDLIDB DLI TM section DLITM //ATFDLITM DB2 section DB2 //ATFDB2 MQ section MQ //ATFMQ OTHER section OTHER //ATFOTHER Messages IPI0423I Command info ****** No ATF Enhanced Summary log code specified, default set to X'A0' If 'A0' is not the correct code to identify ATF Enhanced Summary records in the IMS log, use the IMSPALOG ATFCODE command to specify the log code before reissuing the ATFEXTR command. IPI0424E Command error ***** ATFMQ Required ATF Enhanced Summary Extract DDname not specified in JCL Example JCL The SECTION parameter specified an ATF section for which there is no corresponding DD statement in the JCL. The following JCL shows a sample job to extract ATF Enhanced Summary records. To use this sample, replace the tokens with appropriate values for your site. <hlq> The high-level qualifier for IMS PA data sets. <input.log> The IMS SLDS containing the ATF Enhanced Summary records. <prefix> A common prefix for your CSV extract data sets. <xx> The code to identify OMEGAMON Enhanced Summary records in the IMS SLDS. Specify either the LABELS or NOLABELS keyword and delete the other. Page 4 of 6

5 //IPI JOB (ACCOUNT),'NAME' //* //* IMS PA ATF Extract to CSV //* //IPI EXEC PGM=IPIMAIN,PARM='V141' //STEPLIB DD DSN=<hlq>.SIPILINK,DISP=SHR //LOGIN DD DSN=<input.log>,DISP=SHR //ATFHEAD DD DSN=<prefix>.ATFHEAD.CSV,DISP=SHR //ATFDBD DD DSN=<prefix>.ATFDBD.CSV,DISP=SHR //ATFDLIDB DD DSN=<prefix>.ATFDLIDB.CSV,DISP=SHR //ATFDLITM DD DSN=<prefix>.ATFDLITM.CSV,DISP=SHR //ATFDB2 DD DSN=<prefix>.ATFDB2.CSV,DISP=SHR //ATFMQ DD DSN=<prefix>.ATFMQ.CSV,DISP=SHR //ATFOTHER DD DSN=<prefix>.ATFOTHER.CSV,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //IPICMD DD * IMSPALOG ATFCODE ATC(<xx>) IMSPALOG ATFEXTR( LABELS NOLABELS, SECTIONS(DBD, DLIDB, DLITM, DB2, MQ, OTHER)) IMSPALOG EXECUTE /* Sample DDL and DB2 load utility members A DB2 DDL sample is provided in the SIPISAMP library to define a sample DB2 database and tables for the ATF data. DB2 load utility samples are also provided to load the ATF CSV data into this DB2 Database. The sample DDL and DB2 load utility members are: IPIESDDL IPIESLD IPIESLD1 IPIESLD2 IPIESLD3 IPIESLD4 IPIESLD5 IPIESLD6 DDL skeleton to define the DB2 database and tables HEADER table LOAD skeleton DBD table LOAD skeleton DLIDB table LOAD skeleton DLITM table LOAD skeleton DB2 table LOAD skeleton MQ table LOAD skeleton OTHER table LOAD skeleton A combination of INTEGER and DECIMAL data types are used for numeric data. Fields identified as Flag bytes are expanded into bit strings of CHAR format where each bit is represented as either 1=ON or 0=OFF. Page 5 of 6

6 The following DDL-style data types can be used: TIMESTAMP TIME CHAR VARCHAR INTEGER DECIMAL(16,6) Date and time timestamp Time Character with a known length; includes hexadecimal strings Character with an unknown or variable length Integer count Number of seconds, with fractions of seconds after the decimal point and a maximum precision of one microsecond Page 6 of 6