SMF Activity Logging

You can audit the actions of Output Manager users and store this information in SMF records.

Auditable actions include the viewing, printing, emailing, and downloading of archives and reports; the printing and reprinting of report bundles; and the processing of archives or reports in BJTBATCH. Output Manager can capture SMF statistics when any of these actions are performed, and store the captured statistics in SMF records, based on your specifications. Use SMF activity logging to help trace the lifecycle of report data, from the originating job all the way through its eventual hardcopy printing.

The number of pages, lines, and bytes that are viewed, printed, emailed, or processed by a request is based on actual data output, except as noted. The recorded counts do not include values added by the operating system. However, these counts do include the number of pages, lines, and bytes in any banners and PRSET members included with the output. They do not include bundle manifests or recipient manifests. Byte counts include the number of bytes necessary to transport the data to its destination

To enable and configure SMF logging, store a record type value in the BJTCFG table using the BJTCNVPM SBJTSAMP member during Output Manager installation and customization.

You change the record type value using the Output Manager ISPF Policy Administration panels (A.PA). Set the value for the SMF_RECORD_TYPE attribute in the global default configuration (Subsystem name = '*' and type = '*') to a numeric value, 128 - 255, inclusive. Deleting this attribute, or setting it to 0, or specifying an invalid value disables SMF logging.

The SMF accounting records are written as a user-configurable SMF record type with Output Manager specific subsections. For more information on the subsections specific to Output Manager, see SMF Record Layouts.

To trace the lifecycle of report data, combine the information found in the SMF records generated by Output Manager with any SMF type X'06' records generated by eventual output.

Note: All date and time values are stored in local time. If the timezone cannot be determined, it is recorded as obtained.
Note: Enabling SMF logging will have a slight impact on performance.

Security requirements for ITOMweb SMF logging

To write SMF records for ITOMweb, the user ID assigned to the ITOMweb started task requires READ access to RACF® resource profile BPX.SMF in the FACILITY class. For example:
Where ITOMwebid is the user ID that the ITOMweb web server is running under.