Softpanorama

May the source be with you, but remember the KISS principle ;-)
Home Switchboard Unix Administration Red Hat TCP/IP Networks Neoliberalism Toxic Managers
(slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and  bastardization of classic Unix

TWS Logfile Adapter

News Recommended Links Reference TEC Documentation TEC Rules Programming
Operations with Adapter: Starting, Stopping and Reloading Starting the adapter Stopping the adapter Adapter files Installation

TWS Logfile adapter

Tivoli Workload Scheduler TWS integration with TEC   Default rules
Format file Troubleshooting the UNIX logfile postmsg adapter Humor Etc

TWS logfile adapter is installed in version TWS 8.2  by so called Tivoli Plus module, which provides events parsing to TEC.  The logadapters installation includes a set of predefined message formats, event classes, TEC rules and actions that can be taken of particular types of messages. 

Installation directory

cd /opt/tivoli/lcf/bin/aix4-r1/TME/TEC/adapters/bin/

 Start stop

./tivoli/lcf/bin/aix4-r1/TME/TEC/adapters/bin/init.tecad_logfile [start|stop]

TWS logfile adapter is installed in two directories:

binary and scripts

/opt/tivoli/lcf//bin/aix4-r1/TME/TEC/adapters/bin/

drwxr-xr-x    2 root     system         4096 Mar 08 2005  ./
drwxr-xr-x    4 root     system          256 Jan 05 2005  ../
-rwxr-xr-x    1 root     system        11161 Jan 05 2005  init.tec_gwr*
-rwxr-xr-x    1 root     system        32305 Jan 24 2005  init.tecad_logfile*
-rwxr-xr-x    1 root     system       339951 Jan 05 2005  tec_gwr*
-rwxr-xr-x    1 root     system         1694 Jan 05 2005  tec_gwr.diag*
-rwxr-xr-x    1 root     system        59179 Jan 05 2005  tecad-remove-gwr.sh*
-rwxr-xr-x    1 root     system        67984 Jan 24 2005  tecad-remove-logfile.sh*
-rwxr-xr-x    1 root     system       744882 Jan 24 2005  tecad_logfile*
-rwxr-xr-x    1 root     system         2884 Jan 24 2005  update_conf*

configuration files

/opt/tivoli/lcf/bin/aix4-r1/TME/TEC/adapters/etc/

root@nti2171:/opt/tivoli/lcf # find . -name "tecad*"
./bin/aix4-r1/TME/TEC/adapters/etc/C/tecad_logfile.fmt
./bin/aix4-r1/TME/TEC/adapters/etc/C/tecad_logfile.fmt.pre.MAESTRO
./bin/aix4-r1/TME/TEC/adapters/etc/de/tecad_logfile.fmt
./bin/aix4-r1/TME/TEC/adapters/etc/es/tecad_logfile.fmt
./bin/aix4-r1/TME/TEC/adapters/etc/fr/tecad_logfile.fmt
./bin/aix4-r1/TME/TEC/adapters/etc/it/tecad_logfile.fmt
./bin/aix4-r1/TME/TEC/adapters/etc/ja/tecad_logfile.fmt
./bin/aix4-r1/TME/TEC/adapters/etc/ko/tecad_logfile.fmt
./bin/aix4-r1/TME/TEC/adapters/etc/pt_Br/tecad_logfile.fmt
./bin/aix4-r1/TME/TEC/adapters/etc/zh_CN/tecad_logfile.fmt
./bin/aix4-r1/TME/TEC/adapters/etc/zh_TW/tecad_logfile.fmt
tecad_logfile.conf
./bin/aix4-r1/TME/TEC/adapters/etc/tecad_logfile.err
./bin/aix4-r1/TME/TEC/adapters/etc/tecad_logfile.cds
./bin/aix4-r1/TME/TEC/adapters/etc/tecad_logfile.conf.pre.MAESTRO
./bin/aix4-r1/TME/TEC/adapters/etc/tecad_logfile.cds.pre.MAESTRO
./bin/aix4-r1/TME/TEC/adapters/etc/tecad_logfile.err.ORIG
./bin/aix4-r1/TME/TEC/adapters/etc/tecad_logfile.cds.post.MAESTRO
./bin/aix4-r1/TME/TEC/adapters/etc/tecad_logfile.conf.post.MAESTRO

Startup files include

Configuration file:

root@nti2171:/opt/tivoli/lcf/bin/aix4-r1/TME/TEC/adapters/etc # ll
total 576
drwxr-xr-x   12 root     system         4096 May 01 2006  ./
drwxr-xr-x    4 root     system          256 Jan 05 2005  ../
drwxr-xr-x    2 root     system          256 Jan 24 2005  C/
drwxr-xr-x    2 root     system          256 Jan 24 2005  de/
drwxr-xr-x    2 root     system          256 Jan 24 2005  es/
drwxr-xr-x    2 root     system          256 Jan 24 2005  fr/
drwxr-xr-x    2 root     system          256 Jan 24 2005  it/
drwxr-xr-x    2 root     system          256 Jan 24 2005  ja/
drwxr-xr-x    2 root     system          256 Jan 24 2005  ko/
drwxr-xr-x    2 root     system          256 Jan 24 2005  pt_Br/
-rw-r--r--    1 root     system        87224 Jan 24 2005  tecad_logfile.cds
-rw-r--r--    1 root     system        87224 Jan 24 2005  tecad_logfile.cds.post.MAESTRO
-rw-r--r--    1 root     system        87224 Jan 24 2005  tecad_logfile.cds.pre.MAESTRO
-rw-r--r--    1 root     system          400 Jan 24 2005  tecad_logfile.conf
-rw-r--r--    1 root     system          400 Jan 24 2005  tecad_logfile.conf.post.MAESTRO
-rw-r--r--    1 root     system          400 Jan 24 2005  tecad_logfile.conf.pre.MAESTRO
-rw-r--r--    1 root     system         2497 Sep 07 2005  tecad_logfile.err
-rw-r--r--    1 root     system         2541 May 26 2005  tecad_logfile.err.ORIG
drwxr-xr-x    2 root     system          256 Jan 24 2005  zh_CN/
drwxr-xr-x    2 root     system          256 Jan 24 2005  zh_TW/
File itself:
# Wed Jan  5 10:28:52 2005
#
# tecad_logfile Configuration
#
TransportList=t1_
t1_Type=LCF
t1_Channels=c1_
c1_ServerLocation=@EventServer
EventMaxSize=4096
BufEvtPath=/etc/Tivoli/tec/tecad_logfile@.cache
PollInterval=30
Pre37Server=no
FQDomain=NO
#
Filter:Class=Logfile_Base
Filter:Class=Logfile_Sendmail
Filter:Class=Amd_Unmounted
Filter:Class=Amd_Mounted


LogSources=/opt/tivoli/TWS/event.log

Cache: the file specified by the BufEvtPath parameter in the tecad_logfile.conf file,

/etc/Tivoli/tec/tecad_logfile@.cache

Setting Up the TEC logfile adapters

When you have installed the TEC logfile adapter on a workstation, a set of configuration steps must be performed to enable that adapter to manage the job scheduling events. For information on how to install the TEC logfile adapter, refer to the IBM(R) Tivoli Enterprise Console(R) Installation Guide.

The Tivoli Workload Scheduler Plus Module provides you with two tasks that allow you to automatically perform this setup activity, the Configure non-TME adapter task (if you installed a non-TME logfile adapter on the workstation) or the Configure non-TME adapter task (if you installed a TME logfile adapter on the workstation). These tasks perform the following actions on the TEC logfile adapter:

  1. Copies the BmEvents.conf file from TWS_Home/config directory (on Windows(R) platforms) or TWS_Home/OV directory (on UNIX(R) platforms) into the TWS_Home directory, if not already present
  2. Adds into the BmEvents.conf file the following lines, if still commented:
    FILE = TWS_Home/event.log
    EVENTS = 51 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 
    118 119 120 121 122 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 
    201 202 203 204 251 252 301
    This file contains the configuration information used by the batchman process to determine which information must be logged and where. The value of the FILE field contains the path and name of the log file for the scheduling events while the EVENTS field contains all event numbers that will be logged by the batchman process.
  3. Stops the TEC logfile adapter
  4. Customizes the TEC logfile adapter Configuration file
    tec_adapter_installation_path/etc/tecad_logfile.conf
    by adding the Tivoli Workload Scheduler log file specification in the Logsource field:
    LogSource=TWS_Home/event.log
    and specifying the value for the PollInterval as follows:
     PollInterval=10
    This file contains the configuration information necessary for the TEC logfile adapter to gather the scheduling information logged by the batchman process.
  5. Makes a backup copy named
    tec_adapter_installation_path/etc/locale_directory/tecad_logfile.fmt.pre.MAESTRO
    of the TEC logfile adapter FMT file
    tec_adapter_installation_path/etc/locale_directory/tecad_logfile.fmt
    and adds to this tecad_logfile.fmt file the format definitions for scheduling events provided by the Tivoli Workload Scheduler Plus Module and stored in the maestro.fmt (if on Unix platform) or maestront.fmt (if on Windows platform). In this way the TEC logfile adapter is enabled to manage the new formats provided by the Tivoli Workload Scheduler Plus Module for the scheduling events.
  6. Makes a backup copy named
    tec_adapter_installation_path/etc/locale_directory/tecad_logfile.cds.pre.MAESTRO
    of the TEC logfile adapter Class Definition Statement (CDS) file
    tec_adapter_installation_path/etc/locale_directory/tecad_logfile.cds
    and generates again the new CDS file from the tecad_logfile.fmt updated with the formats provided by the Tivoli Workload Scheduler Plus Module. In this way the TEC logfile adapter is enabled to map incoming raw events to new scheduling event classes and to define these events' attributes before forwarding the events to the TEC event server.
  7. Restarts the TEC logfile adapter to update it with the new configuration setup.

To perform these setup, activities using the tasks provided by the Tivoli Workload Scheduler Plus Module open the TWS Plus for Tivoli window and perform the instructions provided in the following sections according to the kind of TEC logfile adapter you installed on the workstation.

Note:

Restart the Tivoli Workload Scheduler processes on the workstation to enable the batchman process to log the scheduling information in the log file.

Configuring a TME logfile adapter

  1. Access the Modify subscribers window from the Configure TME(R) adapter icon to check on which subscribers where the command is to run
  2. Run the Configure TME adapter command.

Configuring a non-TME logfile adapter

To configure a non-TME logfile adapter on a Tivoli Workload Scheduler system:

  1. Run the Configure non-TME adapter command.
  2. In the Configure non-TME adapter window, specify the path to the directory where you installed the non-TME logfile adapter on the system where you want to run the command
  3. Click set and close to run the command.
  4. When prompted for a port number, type 5529 (required by default).

Job scheduling events

This section describes the events that are generated by using to the information stored in the log file specified in the BmEvents.conf configuration file stored on the system where you installed the TEC logfile adapter.

An important aspect to be considered when configuring the integration with the TEC using event adapters is whether to monitor only the master domain manager or every Tivoli Workload Scheduler agent.

If you integrate only the master domain manager, all the events coming from the entire scheduling environment are reported because the log file on a master domain manager logs the information from the entire scheduling network. On the TEC event server and TEC event console all events will therefore look as if they come from the master domain manager, regardless of which Tivoli Workload Scheduler agent they originate from. The workstation name, job name, and job stream name are still reported to TEC, but as a part of the message inside the event.

If, instead, you install a TEC logfile adapter on every Tivoli Workload Scheduler agent, this results in a duplication of events coming from the master domain manager, and from each agent. Creating and using a TEC that detects these duplicated events, based on job_name, job_cpu, schedule_name, and schedule_cpu, and keeps just the event coming from the log file on the Tivoli Workload Scheduler agent, helps you to handle this problem. The same consideration also applies if you decide to integrate the backup master domain manager, if defined, because the log file on a backup master domain manager logs the information from the entire scheduling network. For information on creating new rules for the TEC refer to the IBM Tivoli Enterprise Console Rule Builder's Guide. For information on how to define a backup master domain manager refer to IBM Tivoli Workload Scheduler: Planning and Installation Guide.

Figure 19 describes how an event is generated. It shows the TEC logfile adapter installed on the master domain manager. This is to ensure that all the information about the job scheduling execution across the entire scheduling environment is available inside the log file on that workstation. You can decide, however, to install the TEC logfile adapter on another workstation in your scheduling environment, depending on your environment and business needs, refer to Mapping your scheduling environment into the Tivoli environment for additional information.

Figure 19. Event Generation Flow  

The logic that is used to generate job scheduling events is the following:

For some error conditions on event informing that the alarm condition is ended is also stored in the log file and passed to the TEC event server via the TEC logfile adapter. This kind of event is called a clearing event. It ends on the TEC event console any related problem events.

The following table describes the events and rules provided by the Tivoli Workload Scheduler Plus Module.

The text of the message that is assigned by the FMT file to the event is shown in bold. The text message is the one that is sent by the TEC logfile adapter to TEC event server and then to the TEC event console. The percent sign (%s) in the messages indicates a variable. The name of each variable follows the message between brackets.

 

"TWS process %s has been reset on host %s" (program_name, host_name)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Process_Reset.
  • HARMLESS.
  • TWS daemon process reset.
"TWS process %s has been reset on host %s" (program_name, host_name)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Process_Reset.
  • HARMLESS.
  • TWS NT daemon process reset.
"TWS process %s is gone on host %s" (program_name, host_name)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Process_Gone.
  • CRITICAL.
  • TWS process gone.
"TWS process %s has abended on host %s" (program_name, host_name)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Process_Abend.
  • CRITICAL.
  • TWS process abends.
"Job %s.%s failed, no recovery specified" (schedule_name, job_name)
  • Event Class:
  • Event Severity:
  • Automated Action (UNIX only):
  • Event Description:
  • Correlation Activity:
  • TWS_Job_Abend.
  • CRITICAL.
  • Send job stdlist to user TWS.
  • Job failed, no recovery specified.
  • If this job had abended more than once within a 24 hour time window, send a TWS_Job_Repeated_Failure event.
"Job %s.%s failed, recovery job will be run then schedule %s will be stopped" (schedule_name, job_name, schedule_name)
  • Event Class:
  • Event Severity:
  • Automated Action (UNIX only):
  • Event Description:
  • Correlation Activity:
  • TWS_Job_Abend.
  • CRITICAL.
  • Send job stdlist to user TWS.
  • Job failed, recovery job runs, and schedule stops
  • If this job had abended more than once within a 24 hour time window, send a TWS_Job_Repeated_Failure event.
"Job %s.%s failed, this job will be rerun" (schedule_name, job_name)
  • Event Class:
  • Event Severity:
  • Automated Action (UNIX only):
  • Event Description:
  • Correlation Activity:
  • TWS_Job_Abend.
  • CRITICAL.
  • Send job stdlist to user TWS .
  • Job failed, the job is rerun.
  • If this job had abended more than once within a 24 hour time window, send a TWS_Job_Repeated_Failure event.
"Job %s.%s failed, this job will be rerun after the recovery job" (schedule_name, job_name)
  • Event Class:
  • Event Severity:
  • Automated Action (UNIX only):
  • Event Description:
  • Correlation Activity:
  • TWS_Job_Abend.
  • CRITICAL.
  • Send job stdlist to user TWS.
  • Job failed, recovery job is run, and the job is run again.
  • If this job had abended more than once within a 24 hour time window, send a TWS_Job_Repeated_Failure event.
"Job %s.%s failed, continuing with schedule %s" (schedule_name, job_name, schedule_name)
  • Event Class:
  • Event Severity:
  • Automated Action (UNIX only):
  • Event Description:
  • Correlation Activity:
  • TWS_Job_Abend.
  • CRITICAL.
  • Send job stdlist to user TWS.
  • Job failed, the schedule proceeds.
  • If this job had abended more than once within a 24 hour time window, send a TWS_Job_Repeated_Failure event.
"Job %s.%s failed, running recovery job then continuing with schedule %s" (schedule_name, job_name, schedule_name)
  • Event Class:
  • Event Severity:
  • Automated Action (UNIX only):
  • Event Description:
  • Correlation Activity:
  • TWS_Job_Abend.
  • CRITICAL.
  • Send job stdlist to user TWS.
  • Job failed, recovery job runs, schedule proceeds
  • If this job had abended more than once within a 24 hour time window, send a TWS_Job_Repeated_Failure event.
"Failure while rerunning failed job %s.%s" (schedule_name, job_name)
  • Event Class:
  • Event Severity:
  • Automated Action (UNIX only):
  • Event Description:
  • Correlation Activity:
  • TWS_Job_Abend.
  • CRITICAL.
  • Send job stdlist to user TWS.
  • Rerun of abended job abends.
  • If this job had abended more than once within a 24 hour time window, send a TWS_Job_Repeated_Failure event.
"Failure while recovering job %s.%s" (schedule_name, job_name)
  • Event Class:
  • Event Severity:
  • Automated Action (UNIX only):
  • Event Description:
  • Correlation Activity:
  • TWS_Job_Abend.
  • CRITICAL.
  • Send job stdlist to user TWS.
  • Recovery job abends.
  • If this job had abended more than once within a 24 hour time window, send a TWS_Job_Repeated_Failure event.
"Multiple failures of Job %s#%s in 24 hour period" (schedule_name, job_name)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Job_Repeated_Failure.
  • CRITICAL.
  • Same job fails more than once in 24 hours.
"Job %s.%s did not start" (schedule_name, job_name)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Job_Failed.
  • CRITICAL.
  • Job failed to start.
"Job %s.%s has started on CPU %s" (schedule_name, job_name, cpu_name)
  • Event Class:
  • Event Severity:
  • Event Description:
  • Correlation Activity:
  • TWS_Job_Launched.
  • HARMLESS.
  • Job started.
  • Clearing Event - Close open job prompt events related to this job.
"Job %s.%s has successfully completed on CPU %s" (schedule_name, job_name, cpu_name)
  • Event Class:
  • Event Severity:
  • Event Description:
  • Correlation Activity:
  • TWS_Job_Done.
  • HARMLESS.
  • Job completed successfully.
  • Clearing Event - Close open job started events for this job and auto-acknowledge this event.
"Job %s.%s suspended on CPU %s" (schedule_name, job_name, cpu_name)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Job_Suspended.
  • WARNING.
  • Job suspended, the until time expired (default option suppress).
"Job %s.%s is late on CPU %s" (scheduler_name, job_cpu)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Job_Late.
  • WARNING.
  • Job late, the deadline time expired before the job completed.
"Job %s.%s:until (continue) expired on CPU %s", schedule_name, job_name, job_cpu
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Job_Until_Cont.
  • WARNING.
  • Job until time expired (option continue).
"Job %s.%s:until (cancel) expired on CPU %s", schedule_name, job_name, job_cpu
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Job_Until_Canc.
  • WARNING.
  • Job until time expired (option cancel).
(TWS Prompt Message)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Job_Recovery_Prompt.
  • WARNING.
  • Job recovery prompt issued.
"Schedule %s suspended", (schedule_name)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Schedule_Susp.
  • WARNING
  • Schedule suspended, the until time expired (default option suppress).
"Schedule %s is late", (schedule_name)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Schedule_Late.
  • WARNING
  • Schedule late, the deadline time expired before the schedule completion.
"Schedule %s until(continue) expired", (schedule_name)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Schedule_Until_Cont.
  • WARNING.
  • Schedule until time expired (option continue).
"Schedule %s until (cancel) expired", (schedule_name)
  • Event Description:
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Schedule_Until_Canc.
  • WARNING.
  • Schedule until time expired (option cancel).
"Schedule %s has failed" (schedule_name)
  • Event Class:
  • Event Severity:
  • Event Description:
  • Correlation Activity:
  • TWS_Schedule_Abend.
  • CRITICAL.
  • Schedule abends.
  • If event is not acknowledged within 15 minutes, send mail to TWS_user (UNIX only).
"Schedule %s is stuck" (schedule_name)
  • Event Class:
  • Event Severity:
  • Event Description:
  • Correlation Activity:
  • TWS_Schedule_Stuck.
  • CRITICAL.
  • Schedule stuck.
  • If event is not acknowledged within 15 minutes, send mail to TWS_user (UNIX only).
"Schedule %s has started" (schedule_name)
  • Event Class:
  • Event Severity:
  • Event Description:
  • Correlation Activity:
  • TWS_Schedule_Started.
  • HARMLESS.
  • Schedule started.
  • Clearing Event - Close all related pending schedule, or schedule abend events related to this schedule.
"Schedule %s has completed" (schedule_name)
  • Event Class:
  • Event Severity:
  • Event Description:
  • Correlation Activity:
  • TWS_Schedule_Done.
  • HARMLESS.
  • Schedule completed successfully.
  • Clearing Event - Close all related schedule started events and auto-acknowledge this event.
(Global Prompt Message)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Global_Prompt.
  • WARNING
  • Global prompt issued.
(Schedule Prompt's Message)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Schedule_Prompt.
  • WARNING.
  • Schedule prompt issued.
(Job Recovery Prompt's Message)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Job_Prompt.
  • WARNING.
  • Job recovery prompt issued.
"Comm link from %s to %s unlinked for unknown reason" (hostname, to_cpu)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Link_Dropped.
  • WARNING.
  • TWS link to CPU dropped for unknown reason.
"Comm link from %s to %s unlinked via unlink command" (hostname, to_cpu)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Link_Dropped.
  • HARMLESS.
  • TWS link to CPU dropped by unlink command.
"Comm link from %s to %s dropped due to error" (hostname, to_cpu)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Link_Dropped.
  • CRITICAL.
  • TWS link to CPU dropped due to error.
"Comm link from %s to %s established" (hostname, to_cpu)
  • Event Class:
  • Event Severity:
  • Event Description:
  • Correlation Activity:
  • TWS_Link_Established.
  • HARMLESS.
  • TWS CPU link to CPU established.
  • Close related TWS_Link_Dropped or TWS_Link_Failed events and auto-acknowledge this event.
"Comm link from %s to %s down for unknown reason" (hostname, to_cpu)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Link_Failed.
  • CRITICAL.
  • TWS link to CPU failed for unknown reason.
"Comm link from %s to %s down due to unlink" (hostname, to_cpu)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Link_Failed.
  • HARMLESS.
  • TWS link to CPU failed due to unlink.
"Comm link from %s to %s down due to error" (hostname, to_cpu)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Link_Failed.
  • CRITICAL.
  • TWS CPU link to CPU failed due to error.
"Active manager % for domain %" (cpu_name, domain_name)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Domain_Manager_Switch.
  • HARMLESS.
  • TWS domain manager switch has occurred.
Long duration for Job %s.%s on CPU %s. (schedule_name, job_name, job_cpu)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Job_Launched.
  • WARNING.
  • If after a time equal to estimated duration, the job is still in exec status, a new message is generated.
Job %s.%s on CPU %s, could miss its deadline. (schedule_name, job_name, job_cpu)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Job_Ready, TWS_Job_Hold
  • WARNING.
  • If the job has a deadline and the sum of job estimated start time and estimated duration is greater than the deadline time, a new message is generated.
Job %s.%s on CPU %s, could miss its deadline. (schedule_name, job_name, job_cpu)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Job_Ready, TWS_Job_Hold.
  • WARNING
  • If the job has a deadline and the sum of job estimated/effective start time and estimated duration is greater than the deadline time, a new message is generated.
Start delay of Job %s.%s on CPU %s. (schedule_name, job_name, job_cpu)
  • Event Class:
  • Event Severity:
  • Event Description:
  • TWS_Job_Ready.
  • WARNING
  • If the job is still in ready status, after n minutes a new message is generated. The default value for n is 10.

Default criteria that control the correlation of events and the automatic responses can be changed by editing the file maestro_plus.rls (in UNIX environments) or maestront_plus.rls (in Windows environments) file. These RLS files are created during Tivoli Workload Scheduler Plus Module installation and compiled with the BAROC file containing the event classes for the Tivoli Workload Scheduler events on the TEC event server when the Setup Event Server for TWS task is run. Before modifying either of these two files, make a backup copy of the original file and test the modified copy in your sample test environment.

For example, in the last event described in the table you can change the n value, the number of seconds the job has to be in ready state to trigger a new message, by modifying the rule job_ready_open set for the TWS_Job_Ready event class.

rule: job_ready_open : ( 
     		description: 'Start a timer rule for ready',

			event: _event of_class 'TWS_Job_Ready'
   					where [

								 status: outside ['CLOSED'],
								 schedule_name: _schedule_name,
								 job_cpu: _job_cpu,
								 job_name: _job_name
						],
			reception_action: (
						set_timer(_event,600,'ready event')
			)
		).

For example, by changing the value from 600 to 1200 in the set_timer predicates of the reception_action action, and then by recompiling and reloading the Rule Base you change from 600 to 1200 the number of seconds the job has to be in ready state to trigger a new message.

Refer to Tivoli Workload Scheduler Planning and Installation Guide for additional information about maestro_plus.rls and maestront_plus.rls files. Refer to Tivoli Enterprise Console(R) User's Guide and Tivoli Enterprise Console Rule Builder's Guide for details about rules commands.

NEWS CONTENTS

Old News

Problem: Errors in the way the TEC logfile adapter matches job scheduling events. Solution: To solve this problem compare the $TECADHOME/etc/<locale>/<tecad>.fmt and the $TECADHOME/etc/<tecad>.cds files. The same events, in the same order should be listed in both of them. If they are not completely aligned then:

Recommended Links

Plus Module User's Guide

IBM - Debugging Tivoli Enterprise Console 3.9 logfile adapter problems by Sandi Comsudi



Etc

Society

Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy

Quotes

War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotesSomerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose BierceBernard Shaw : Mark Twain Quotes

Bulletin:

Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law

History:

Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOSProgramming Languages History : PL/1 : Simula 67 : C : History of GCC developmentScripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-MonthHow to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Haterís Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D


Copyright © 1996-2020 by Softpanorama Society. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.

This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...

You can use PayPal to to buy a cup of coffee for authors of this site

Disclaimer:

The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: March 12, 2019