Specifies the name of the screen space containing the commands described above. Create an initial screen space and enter the following commands on separate lines following the rules for creating OMEGAMON screen spaces (commands should start in column 2):.Specifies the name of the screen space containing the exception analysis command. OMEGAMON 7.1.0 and OMEGAMON II Configuration for dedicated terminals:Ĭreate an initial screen space and enter the following commands on separate lines following the rules for creating OMEGAMON screen spaces (commands should start in column 2):ĭDNM OPREPORT (or whatever DDNAME is used in proc) You need to issue the LOGON command to OMEGAMON to tell it to write screens to the OxREPORT file. The OMEGAMON logging facility must be turned on.PLM 999999999 in a screen space or preferably use the PAGELIMIT option in the user profile. Set the page limit for the OMEGAMON OxREPORT file to a high number.Consult the appropriate installation guide for the IMS, CICS, and DB2 releases. The commands referenced above may be specific to OMEGAMON for MVS. Note: OMEGAMON installation procedures and actual commands can vary from one platform to another. Use these commands on the actual exception analysis screen for testing, but for production usage, place them in the installation or user profile so that they execute at OMEGAMON startup. SET command and you can set some exception thresholds using the XACB command, the XSET command, or both. You can set some control options with the. All exceptions must be unboxed, either by setting the BOX parameters to NO for all exceptions or by turning boxes off in the installation or user profile.The default value for the LROWS parameter is two times the physical screen minus one the maximum value is 999. Check the LROWS parameter of the OMEGAMON started task JCL to ensure that all exceptions fit on the logical screen that is written to the OxREPORT file.No real 3270 terminal is required, since the EPI is used as a virtual 3270. The EPI session is hidden, so no one can walk up and change the screen. This solution is more complicated to configure, but it eliminates both of the problems associated with a dedicated 3270 terminal. The second drawback is that it requires a locally attached 3270 device.Īn alternative solution is to use the OMEGAMON VTAM interface with an EPI logical terminal. However, this solution has two drawbacks, the first of which is mentioned in the previous paragraph. The simplest way to configure the interface is to have a dedicated session with exception analysis always active. CA OPS/MVS can monitor exceptions only while the exception analysis screen is active. If that terminal often displays other screens, then you risk missing important exceptions when the operators use it for other functions. If you have a dedicated mode terminal next to the console that is always left on the exception analysis screen, use that terminal to provide the exception data. An OMEGAMON session must be active to feed the exception event process.CA OPS/MVS must be started before OMEGAMON.When using the AOF to automate OMEGAMON exceptions, note the following: Use the OMEGAMON User Profile Facility to customize these parameters. Customization includes choosing thresholds and options to create and define a profile. Integrating with Tivoli OMEGAMON XE › Provide OMEGAMON ExceptionsĮnsuring that the correct output is being written to the OxREPORT file requires some OMEGAMON customization.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |