![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
You can also process your SMF records as TIBCO Object Service Broker import tables and generate your own reports.
• The JCL used is similar to member S6BSMF shipped in the JCL data set. The program name changes depending on the report type.JCL used to produce a TIBCO Object Service Broker statistics report is shipped as the S6BSMF member in the JCL data set. You can modify the JCL as follows to produce the required reports:
• The last two characters of the program name are the decimal digits of the principal TIBCO Object Service Broker subtype reported by the program, for example, S6BSMF49.
• The EXEC statement PARM=nn controls the number of lines per report page, for example, PARM=60. The words LINES PER PAGE appear as a comment only.
• Specifying PARM=0 (or a number less than header lines + 1) results in report lines without headings. You can use this for re-processing report information (with //REPORT to a data set, instead of SYSOUT).TIBCO Object Service Broker SMF record extraction and sorting are described in the sort sequence recommended for all the TIBCO Object Service Broker SMF reporting utilities. You could also re-sort to a temporary file to meet your particular reporting requirements.S6BSMFEX is recommended over IFASMFDP in most instances because of its specific capabilities and because it always treats its sequential input file as read-only. S6BSMFEX, however, cannot extract data from VSAM SMF collection data sets.IFASMFDP is the standard z/OS‑supplied utility program for off-loading and initializing SMF collection data sets. It can also be used to extract SMF data by SMF record types, or date and time ranges. Because of its powerful capabilities, it is generally not available in some installations.
Use IFASMFDP with extreme care when SMF VSAM collection data sets are referenced to avoid unintentional re-initialization of the collection data sets. Re-initialization of VSAM //DUMPIN data sets can occur by default (subject to local data set access security controls) if //SYSIN or the INDD statements are omitted or through certain INDD statement options. This could cause permanent loss of all SMF records in the collection data sets.The //DUMPIN statement used in member S6BSMF in the JCL data set assumes that you want to extract TIBCO Object Service Broker SMF records directly from an SMF collection data set. SMF is usually extracted from an archive file, which if non-VSAM, is not subject to re-initialization. Modify this statement to reflect the location of your SMF records.The //SYSIN DD statement references an assumed TIBCO Object Service Broker SMF record type of 255. This value depends upon the setting of SMFRECORD in the Data Object Broker parameters. Refer to Reviewing SMF Record Subtypes for more information about how the SMF record type number is specified.TIBCO Object Service Broker for z/OS Utilities for usage information, sample JCL, and sample reports for the utilities mentioned above.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |