5.3 The Oracle TMA TCP for IMS Message Log
The TMA TCP for IMS product uses a message log dataset to record
all messages issued. Normally, the message log
(DDNAME=MSGLOG) is allocated to a disk dataset, but it
can be allocated to another destination (such as
sysout) if desired.
The message log is primarily intended for historical use; that is, as a means to review TMA TCP for IMS activity after-the-fact. The message log remains open for output during the entire execution of TMA TCP for IMS. Consequently, messages cannot ordinarily be viewed interactively (for example, using ISPF Browse) due to the dataset disposition and/or buffering of messages by z/OS.
The MSGLEVEL parameter of the SYSTEM
statement in the configuration file controls the type of messages
written to the log. Specifying a MSGLEVEL of 4 causes
all informational and error messages to be recorded. Specifying a
MSGLEVEL of 2 records only error messages. A
MSGLEVEL of 0 (zero) suppresses all logging. Under
normal circumstances, a MSGLEVEL of 4 should be
specified.
You may elect to have messages appended to the existing log
(thus preserving messages from previous executions of TMA TCP for
IMS) by coding DISP=MOD in the MSGLOG DD
statement in the JCL for TMA TCP for IMS. Alternatively, coding
DISP=OLD or DISP=SHR causes the log to be
overwritten, discarding any messages from a previous execution of
TMA TCP for IMS.