Re-loading monitoring data
The Configure Non-TME adapter and Configure TME® adapter commands set up the file BmEvents.conf in the
TWShome
directory. This configuration file determines the information that
the production processes (batchman
and mailman
) write in the
TWSHome/log_source_file
file and how this information is written. By
default, this file is the event.log
file, .
- Modify the FILE field in the
BmEvents.conf
file and restart the HCL Workload Automation processes - Modify the LogSource field in the
tecad_logfile.conf
file and restarting the Tivoli Enterprise Console logfile adapter.
In the BmEvents.conf
file the # sign
represents a comment. Remove the # sign to uncomment a line.
The contents of this file are also used by other Tivoli® applications that manage events, that HCL Workload Automation can interact with, such as IBM® Tivoli® NetView® and IBM® Tivoli® Business Systems Management.
BmEvents.conf
file
are described below: - OPTIONS=MASTER|OFF
- If
the value is set to
MASTER
then all job scheduling events gathered by that workstation are reported. If that workstation is the master domain manager or the backup master domain manager, with Full Status option switched on, then all scheduling events for all workstations are reported.If the value is set to
OFF
, the job scheduling events are reported only if they relate to the workstation where the file is configured.If commented, it defaults to
MASTER
on the master domain manager workstation, and toOFF
on a workstation other than the master domain manager. - LOGGING=ALL|KEY
- Disables
or enables the key flag filter mechanism.
If set to
ALL
then all events from all jobs and job streams are logged.If set toKEY
the event logging is enabled only for those jobs and job streams that are marked as key. The key flag is used to identify the most critical jobs or job streams. To set it in the job or job stream properties use:- The
keywords
KEYSCHED
(for job streams) andKEYJOB
(for jobs) from the HCL Workload Automation command line interface. - The job
Monitored
check box and job streamMonitored
check box from the Dynamic Workload Console.
- The
keywords
- SYMEVNTS=YES|NO
- If
set to
YES
it tells the production process, batchman, to report the jobs and job streams status events immediately after having generated the new production day plan. .Set to
The default value isNO
, if report is not required.NO
. - CHSCHED=HIGH|LOW
- Indicates which events are to be
sent during the job stream lifetime.
During the lifetime of a job stream its status can change several times depending on the status of the jobs it contains.
By using the CHSCHED option you choose how the job stream status change is reported.
If you set it to
HIGH
, during the job stream lifetime an event is sent any time the status of the job stream changes. Because the intermediate status of the job stream can change several times, several events can be sent, each reporting a specific status change. For example, a job stream may go into the READY state several times during its running because its status is related to the status of the jobs it contains. Each time the job stream goes into the READY state, event 153 is sent.If you set it toLOW
, during the job stream lifetime until the final status is reached, only the initial job stream state transaction is tracked. In this way the network traffic of events reporting job stream status changes is heavily reduced. When the CHSCHED value is set toLOW
these are the events that are sent only the first time during the job stream life time:Table 1. CHSCHED event filtered Event number Event Class Description 153 TWS_Schedule_Started
Job stream started 156 TWS_Schedule_Submit
Job stream submitted 158 TWS_Schedule_Ready
Job stream ready 159 TWS_Schedule_Hold
Job stream hold 160 TWS_Schedule_Extern
Job stream external 162 TWS_Schedule
Job stream properties changed For final status of a job stream, regardless of the value set for CHSCHED, all events reporting the final status of the job stream are reported, even if the job stream has more than one final status. For example, if a job contained in the job stream completes with an ABEND state, event 151 is sent (Job stream abended). If that job is then reruns and completes successfully, the job stream completes with a SUCC state and event 154 is sent (Job stream completed).
The default value for CHSCHED is
HIGH
. - EVENT=
n
[n
…] - Identifies
which events to report in the
log_source_file
. Event numbers must be separated by at least one space. If omitted, the events reported by default are:51 101 102 105 111 151 152 155 201 202 203 204 251 252 301
If the EVENT parameter is included, it completely overrides the defaults. To remove only event 102 from the list, for example, you must enter the following:
EVENT=51 101 105 111 151 152 155 201 202 203 204 251 252 301
Note: Event 51 is always reported each time mailman and batchman are restarted, regardless of the filters specified in the EVENT parameter. If you do not wish to notify this event to the TEC event console, you must manually edit themaestro.fmt
file or, for Windows™ environments, themaestro_nt.fmt
file and comment out the following section:
When this section is commented out, the TEC adapter will not send event 51 to the TEC event console.// TWS Event Log FORMAT TWS_Reset 1 %s %s %s* event_type 1 hostname DEFAULT origin DEFAULT agent_id $1 software_version $2 msg PRINTF("TWS has been reset on host %s",hostname) severity HARMLESS END
- FILE=filename
- This option is used specifically when interacting with the Tivoli Enterprise Console. Set it to the path and file name of an ASCII log file. Job scheduling events are written to this ASCII log file which is truncated whenever the batchman and mailman processes are restarted, for example at the end of each production day.
FILE_NO_UTF8 =filename
Use this option instead of the FILE option when you want job scheduling events written in the local language file specified by this parameter.