Skip to Content

MainView Logger

TOM uses the MainView Logger to write records to the default MVLOGGER MainView LOG. The use of the MainView Logger is optional for TOM and TOM messages are written to the TOM PAS job log and the z/OS system log when the MainView Logger is not active.

See the MainView Administration Guide for information about the MainView Logger.

TOM distributes a log reporting utility MAMLXRPT that allows you to select specific records from the MainView LOG and to specify individual fields to extract from each of the selected records. BBSAMP member MAMLXRPT formats the extracted fields into columns and writes those formatted columns of the selected records to a sequential data set.

Along with the SELECT and WHERE control cards in the SYSIN DD, you can specify the FROM control card to indicate from which MV Logger (and its logspace) on the system to obtain the messages:

FROM(SSID=logger-ssid,LSPACEID=iiiiiiii)

where

  • logger-ssid is the value of the MV Logger BBIPARM LOGGERxx member LOGSSID parameter
  • iiiiiiii is the value of the MV Logger BBIPARM LOGGERxx member LOGSPACE parameter.
Warning

Note

The MainView Logger has a default parameter setting of 3 for the MAXPERSEC parameter in BBPARM member LOGGER00. There are times when TOM activity can result in messages that come at a higher rate than the default setting. When this occurs, it is possible that not all of the messages are written out to the Logger and that all audit messages, or TOM debugging messages might not appear.

The documentation for the utility is in the sample JCL included in BBSAMP member MAMLXRPT.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

MainView AutoOPERATOR 8.2