The LOG statement enables the logging of initialization statements that are read by CA MIM. There are no parameters for this statement.
CA MIM usually records its startup values in the system log through MIM0079 messages because the default value for MIMINIT LOGPARAMETERS is YES. However, if you want to prevent these startup messages, then specify LOGPARAMETERS=NO on the MIMINIT statement on the PARM parameter of the startup procedure, or on the z/OS START command for CA MIM.
To provide more granular control over which statements are logged to the system log, a sequence of NOLOG/LOG statements can be used. MIMINIT LOGPARAMETERS can be specified only in the MIMINIT member of the MIMPARMS data set. However, the NOLOG and LOG statements can be placed in any member of the MIMPARMS and MIMMSGS data sets to control the logging of statements read from that member. Additionally, MIMINIT LOGPARAMETERS= is only applicable during CA MIM initialization. The NOLOG and LOG statements are effective during any phase of CA MIM execution.
Any number of NOLOG or LOG statements can appear in a single MIMPARMS or MIMMSGS input member. By default, when CA MIM begins reading a new member, it logs, through a MIM0079 message, all statements in that member. To suppress logging of all statements in any given input member, place a NOLOG statement as the first statement in that member. To suppress selected portions of any input member, place a NOLOG statement immediately preceding those statements for which you want logging to be suppressed. To re-enable logging, place a LOG statement immediately after the last statement for which logging is to be suppressed.
During CA MIM initialization processing, NOLOG/LOG processing is ignored for any messages that are suppressed through a MIMINIT LOGPARAMETERS=NO specification.
NOLOG and LOG statements have an effect only on the MIMPARMS or MIMMSGS input member in which they are specified. Any new input member that is processed as a result of an INCLUDE member statement does, by default, have its statements logged, even if the previous member has a NOLOG in effect when the INCLUDE statement is encountered. To continue the suppression of statement logging in the included member, a NOLOG statement should be placed as the first statement in the included member. Conversely, if logging is in effect when an INCLUDE member statement is encountered, and the included member suppresses statement logging with a NOLOG statement but does not re-enable statement logging with a LOG statement prior to the end of file, statement logging resumes when CA MIM returns to reading statements from the original member.
This statement has the following format:
LOG
Usage Notes: LOG Statement
Example: LOG Statement
To selectively control the logging of a group of statements from the MIMCMNDS data set, specify the NOLOG, LOG statements in pairs:
NOLOG /* Suppress statement logging */ SETOPTION MIM SETTRACE=BLKIO SETOPTION MIM SETPRINT=BLKIO SETOPTION MIM TRACE=ON LOG /* Resume statement logging */ SETOPTION MODE=DEMAND SETOPTION CYCLE=1,INTERVAL=1 NOLOG /* Suppress statement logging again */ SETOPTION CMDTIMEOUT=NONE
|
Copyright © 2014 CA.
All rights reserved.
|
|