Configuring and Installing Optional Components › Configuration Tasks for Optional Base Components › Set Up Interfaces to Tivoli OMEGAMON XE › Interface to Exception Analysis Process

Interface to Exception Analysis Process

The AOF cannot directly automate OMEGAMON exception messages because they are not routed through z/OS console support. Fortunately, all Tivoli OMEGAMON XE on z/OS products support a log file onto which they write a copy of their logical exception screen at the end of each analysis interval. The size of the OMEGAMON logical screen is one of its startup parameters (LROWS), and users typically set it to a size much greater than the number of lines on the physical screen. Thus, while important exception messages may not appear on the physical screen of an OMEGAMON for lack of room, they will fit on the OMEGAMON logical screen and therefore are written to the log file.