Download Tivoli Workload Scheduler: Troubleshooting Guide

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Transcript
If the rule is in active status go to Step 7: Has the new monitoring
configuration been deployed to the workstation?.
2. Action: If the rule is in error status, activate the Tivoli Workload
Scheduler trace, collect the log files in the <TWA_home>/TWS/stdlist
directory and contact IBM Software Support for assistance.
Step 7: Has the new monitoring configuration been deployed to the
workstation?
If the rule is active, check if the new monitoring configuration has been
deployed to the workstation.
1. The deployment of a new monitoring configuration can be checked in
either of these ways:
v Check in the <TWA_home>/TWS/monconf if the configuration is present
v Check in the SystemOut file in <TWA_home>/WAS/TWSprofile/logs/
server1. Look for the message:
[9/3/07 9:50:00:796 CEST] 00000020 sendEventReadyConfiguration(wsInPlanIds, zipsToDeploy)
AWSDPM001I The workstation "CPU_MASTER" has been notified about
a new available configuration.
If the message is present for the workstation in question after the
time when the rule was made available for deployment, then the
new configuration has been deployed.
If the configuration has been deployed, go to Step 8: Has the deploy of
the new monitoring configuration worked correctly?.
2. Action: If the configuration has not been deployed, deploy it with the
conman deploy command:
%deploy
AWSBHU470I A deployconf command was issued for MASTER_CPU.
Check that the event rule is now being processed correctly. If not, go to
Step 8: Has the deploy of the new monitoring configuration worked
correctly?.
Step 8: Has the deploy of the new monitoring configuration worked correctly?
If the new monitoring configuration has been deployed, check that the
deployment was successful:
1. Check in the <TWA_home>/TWS/stdlist/traces/<date>_TWSMERGE.log,
and look for the most recent occurrence of these 2 messages:
09:51:57 03.09.2008|MONMAN:INFO:=== DEPLOY ===> CPU_MASTER has been notified
of the availability of the new monitoring configuration.
09:51:57 03.09.2008|MONMAN:INFO:=== DEPLOY ===> The zip file d:\TWS\twsuser\monconf\deployconf.zip
has been successfully downloaded.
If you find these messages, referring to the workstation in question,
and occurring after the time when the rule was deployed, then the rule
has been successfully deployed to the workstation: go to Step 9: Is the
SSM agent running (for rules with FileMonitor plug-in-related events
only?).
2. Actions: If you find messages that indicate an error, follow one of these
actions:
Message indicates that the server could not be contacted or that the
action has been resubmitted by monman
You find one of the following messages:
128
Tivoli Workload Scheduler: Troubleshooting Guide
Document related concepts
no text concepts found