The CA MIM Logging Facility

MIM has two logs for collecting information:
cmfzs
CA MIM for z/OS
has two logs for collecting information:
  • The Message logs, which collect messages about
    CA MIM for z/OS
    activities.
  • Trace logs, which collect diagnostic information about
    CA MIM for z/OS
    .
Collect Data in the
CA MIM for z/OS
Logs.
A log is a set of sequential files that collects information about
CA MIM for z/OS
. Two types of logs are provided:
  • The Message logs collect messages about commands that are issued to
    CA MIM for z/OS
    and its responses to those commands. They also collect
    CA MIM for z/OS
    messages that indicate potential problems or significant events.
  • Trace logs collect diagnostic information about
    CA MIM for z/OS
    . CA Support uses this information.
Default Logs Provided by
CA MIM for z/OS
.
By default,
CA MIM for z/OS
provides two types of logs:
  • A message log named MIMLOG, defined as a class A SYSOUT data set.
    CA MIM for z/OS
    automatically directs messages to this log unless you remove the log (through a REMOVELOG command) or you provide a different message log.
  • A trace log named MIMTRC, defined as a class A SYSOUT data set. This trace log is allocated when tracing is turned on, or when an ADDLOG command is issued.
CA MIM for z/OS
provides you with these default logs.
  • Only define these logs when using a cataloged data set or when directing to a different SYSOUT class. If you are using the Early Start mechanism, review the ADDLOG command documentation for considerations.
Characteristics of
CA MIM for z/OS
Logs
All
CA MIM for z/OS
logs have the following generic characteristics:
  • Each log can contain up to four cataloged data sets or a single SYSOUT data set. When more than one cataloged data set is used, they must share the same logical record length (LRECL).
  • CA MIM for z/OS
    automatically switches to a new file when the current file becomes full. However,
    CA MIM for z/OS
    overwrites data when all files become full.
  • Each system must have its own log files. Log files cannot be shared between different
    CA MIM for z/OS
    copies running on the same or different systems.
  • The log files must not be multi-volume data sets.
Additional Considerations for Logs
When setting up your logs, keep in mind the following information:
  • The order in which you define log files to
    CA MIM for z/OS
    determines which file
    CA MIM for z/OS
    uses first.
  • If a
    CA MIM for z/OS
    log is allocated to a data set, allocate the log with RECFM=FB,LRECL=132,BLKSIZE=15972.
Manipulating Log Files
Multiple operator commands can be used to manipulate the various log files within
CA MIM for z/OS
. These commands include ADDLOG, OPENLOG, SWITCHLOG, CLOSELOG, PRINTLOG, REMOVELOG, and WRITELOG. For more information, see the
CA MIM for z/OS
Statement and Command Reference Guid
e for commands details.
MIMLOG Considerations
  • Earlier releases of
    CA MIM for z/OS
    were not able to provide a MIM job log when starting with SUB=MSTR. Now the messages are queued internally until JES is available, when
    CA MIM for z/OS
    is started with SUB=MSTR before JES. The default is to write the queued message to SYSOUT A. To send the MIMLOG messages to a different class or to a data set on a disk, use the ADDLOG command. If you are using the Early Start mechanism, review the ADDLOG command documentation for considerations.
  • If
    CA MIM for z/OS
    is started as SUB=MSTR before JES, it obtains an STC number as soon as JES becomes available.
  • If JES terminates while
    CA MIM for z/OS
    is active,
    CA MIM for z/OS
    automatically disconnects from JES and queue messages internally, until JES is restarted. Operations do not need to take any special action when restarting JES while
    CA MIM for z/OS
    is active.
    The MIMLOG can be eliminated by placing the following command at the top of the init member:
    ADDLOG MIMLOG DSNAME=NULLFILE
    MIM log messages go to the syslog.
    • CA MIM for z/OS
      messages with Route Code 11 are in the JESYSMSG log and the MIMLOG.
    • CA MIM for z/OS
      messages which are issued before initialization completes, are in the JESMSGLG log.