Orb Data – The Chapel Grenville Court, Britwell Road, Burnham, Bucks SL1 8DF, UK.
Tel: 01628 550450 email: info@orb-data.com
Knowledge Base
|
An introduction to TWS 8.6 command line reporting TWS 8.6 provides a new command line reporting function that aims to simply creating reports from data within the TWS database. This article provides an overview of the functionality and a summary of the "out of the box" (OOTB) reports. |
|
TWS command line environment variables The default output displayed from the TWS conman command when using the command line leaves a lot to be desired as it truncates the names of the jobs and job streams. This tip looks at the TWS command line environment variables that can be used to make the output more readable. |
| Since TWS 8.3 duplicate job stream and job names ahve been supported in the TWS plan. Whilst this has brought some major advantages in the overall TWS management, it has introduced some additional complexity when using the TWS command line interface as the syntax for managing these duplicates names has changed. This tip provides some pointers in how to use the SCHEDID command option to ease this complexity. |
| Starting with TWS 8.3 IBM introduced some major architecturial changes to the Tivoli Workload Scheduler (TWS) for the distributed platforms. Amongst these changes was the introduction of WebSphere Application Server (WAS). This tip discusses the use of WebSphere with TWS. |
|
Although the Job Scheduling Console (JSC) is no longer being developed (last supported verison is for TWS 8.4 Fix Pack 3), there are a lot of customers that are continuing to use it whilst preparing their migration to the Tivoli Dynamic Workload Console (TDWC) or equivalent (e.g. TWS/Webadmin).
This article shows how to configure the necessary ports to allow the JSC to function with TWS 8.5 and higher. |
|
TWS 8.x placing stdlist on a different file system Following installation of TWS (e.g. MDM, FTA) the stdlist directory containing the job log output from TWS executed jobs is located within the TWS installation directory. For many years TWS best practices have recommended moving the stdlist directory to a different file system to avoid the possibility of filling up the file system when jobs generate large amounts of job output - this can cause corruption of the TWS control files if the file system fills completely and TWS is unable to write to the control files. This tip looks at how to move the stdlist directory to a different file system on the Windows and Linux platforms. |
|
TWS 8.4 and ITM 6.x Integration - Part 1 Integrating TWS 8.4 with IBM Tivoli Monitoring v6.x |
| TWS 8.4 introduced the sendevent command to support integration of events from bespoke or third party applications that do not have direct TWS integration. This tip looks at the configuration of the sendevent command as supplied by the TWS remote CLI component and discusses how to support alternative event servers in the case of TWS MDM failover to the backup MDM. |
|
DB2 SQL5005C System error after installing TWS After installing TWS on Windows 2008 Server all users that are not members of the DB2ADMNS group receive DB2 SQL5005C System error after login. this tip explains why this error occurs, how to remove the error for all users not members of the DB2ADMNS group and how to, optionally, add the autostart back for selected users. Although this error occurs after installing DB2 for TWS, the error could (and probably will) occur for any product that requires DB2 installation on Windows 2008 Server. The solution provided here is applicable to those products as well. |
|
Executing a command as a TWS event rule action This tip looks at how to troubleshoot issues when executing a command as an action to a TWS event rule. TWS provides the ability to execute a command as a built-in GenericAction action that can be coded as the response to any satisfied TWS event rule (single, sequence or set). However, it can prove a little bit troublesome to get this functionality working as desired.
This tip is applicable to TWS 8.4 and higher. |
 | |
