Reporting problems

Some messages suggest that you generate a system memory dump and forward it to IBM Software Support for more help.

If your OMEGAMON product malfunctions, complete the following steps before you call IBM® Software Support:

  • Record the error message number and any error codes that the error message displays.
  • Record output from the DEBUG screen space, when possible.

    To obtain these DEBUG screens, type DEBUG on the INFO-line and press Enter. Your product executes various screen spaces and logs important information to hardcopy.

    Note: For OMEGAMON AI for CICS, OMEGAMON for Db2 on z/OS, OMEGAMON for DBCTL, OMEGAMON for IMS on z/OS, and OMEGAMON for z/OS, or the OMEGAMON AI for CICS TG component, fill in the information on the hardcopy of the first debug screen (DEBUG).
  • Gather any dumps that the OMEGAMON product produces (on cartridge, tape, or hardcopy). You can write product memory dumps to one or more of the following:
    Table 1. Collecting memory dumps
    Products Description
    IBM Z OMEGAMON AI for CICS
    OMEGAMON for Db2 on z/OS
    OMEGAMON for DBCTL
    OMEGAMON for IMS on z/OS
    OMEGAMON for z/OS
    		 The common interface SYSABEND DD statement
    OMEGAMON for Db2 on z/OS OMEGAMON for DBCTLOMEGAMON for IMS on z/OSOMEGAMON for z/OSOMEGAMON for Storage  
    		The O2SNAP data set
    All products The RKLVLOG and RKLVSNAP data sets
    All products MPcc data set

    Be prepared to send the dumps to IBM if a Software Support representative requests you to do so. You can also use FTP to transmit dumps to IBM.

    Note: If you send a cartridge or tape, specify the format, density, and label information.
  • Record any error messages that OMEGAMON product writes to the system log.