The BmEvents configuration file

The BmEvents configuration file is named <TWShome>/BmEvents.conf. Use it to configure HCL Workload Automation production processes on each workstation that has an agent installed. Its contents are described below.

# comment

A comment line.

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 on, then all scheduling events from the scheduling environment are reported. If the value is set to OFF, no job scheduling events are reported from that workstation. If commented, it defaults to MASTER on the master domain manager workstation, while it allows to report all job scheduling events regarding that workstation only on a workstation different from the master domain manager.

EVENT= n [ n ...]

The list of events to be reported. Event numbers must be separated by at least one space. If omitted, the events reported by default are:

51 101 102 105 151 152 155 201 202 203 204 251 252

Event 51 causes mailman and batchman to report the fact that they were restarted. Events 1, 52, and 53 are not valid in this file (see The MAgent configuration file).

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 151 152 155 201 202 203 204 251 252

See Table 1 for a description of events.

PIPE=filename

If set, job scheduling events are written to a FIFO file. To have events sent to the IBM Workload Scheduler/NetView agent, the setting must be:

PIPE=MAGENT.P

CHSCHED=HIGH|LOW

When set to HIGH, batchman sends an event for any schedule status transaction. When set to LOW, batchman only tracks the initial schedule status transactions. For the lifetime of schedule jobs no change of status is reported until the final state is reached. When a job has more than one final state, an event is sent for each. For example, a schedule completes with an ABEND state and event 151 is sent (schedule abended). The job is then rerun and completes successfully. The schedule is completed with a SUCC state and event 154 is sent (schedule completed). The default is HIGH. Table 1 lists the events that are filtered by CHSCHED when it is set to LOW.

Table 1. Events filtered by CHSCHED

Event	Description	Filtered on LOW
151	Schedule abended	NO
152	Schedule is stuck	NO
153	Schedule started	YES
154	Schedule ended	NO
155	Until time expired onuntil = suppr	NO
156	Schedule submitted	YES
157	Schedule cancelled	NO
158	Schedule ready	YES
159	Schedule hold	YES
160	Schedule extrn	YES
161	Schedule is cancel pending	NO
162	Schedule properties changed	YES
163	Schedule is late	NO
164	Until time expired onuntil = continue	NO
165	Until time expired onuntil = cancel	NO

A BmEvents configuration file is included with the HCL Workload Automation software. It contains several comment lines, and a single parameter setting:

PIPE=MAGENT.P

This causes events to be reported as follows:

• If installed on the master, it will report all job scheduling events (101-252) for all workstations in the network. If installed on any other workstation, no job scheduling events will be reported. The process restart event (51) is reported regardless of the workstation type.
• The following events are reported:

  51 101 102 105 151 152 155 201 202 203 204 251 252

• Event information is written to a FIFO file named MAGENT.P, which is read by the IBM Workload Scheduler/NetView agent.