TWS8.5 Planning and Installation

Tivoli IBM Tivoli Workload Scheduler

Version 8.5
Planning and Installation
SC32-1273-08
Tivoli IBM Tivoli Workload Scheduler
®

Version 8.5
Planning and Installation
SC32-1273-08
Note
Before using this information and the product it supports, read the information in “Notices” on page 333.
This edition applies to version 8, release 5, modification level 0, of IBM Tivoli Workload Scheduler (program
number 5698-WSH) and to all subsequent releases and modifications until otherwise indicated in new editions.
This edition replaces SC32-1273-07.
© Copyright International Business Machines Corporation 1991, 2008.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
List of figures. . . . . . . . . . . . vii | Chapter 3. Preparing . . . . . . . . . 23
| Installation overview . . . . . . . . . . . 23
List of tables . . . . . . . . . . . . ix | Installation considerations . . . . . . . . . 23
| Symlink options . . . . . . . . . . . . 24
| Engine coexistence and upgrade notes . . . . 25
About this publication . . . . . . . . xi
| Installation media . . . . . . . . . . . . 26
What is new in this release . . . . . . . . . xi
| Instances of Tivoli Workload Automation . . . . 26
| What is new in this publication . . . . . . . . xi
| Relational database management systems . . . . 27
| What is new in version 8.5 . . . . . . . . xi
| Installation log files. . . . . . . . . . . . 28
Who should read this publication . . . . . . . xi
| InstallShield wizard installation and
Publications . . . . . . . . . . . . . . xii
| uninstallation log files . . . . . . . . . . 28
Accessibility . . . . . . . . . . . . . . xii
| TWSINST log files . . . . . . . . . . . 28
Tivoli technical training . . . . . . . . . . xii
| Software package block log files . . . . . . 29
Support information . . . . . . . . . . . xii
| WebSphere Application Server installation log
| files . . . . . . . . . . . . . . . . 29
Part 1. Planning . . . . . . . . . . 1 | DB2 installation log files . . . . . . . . . 29
Chapter 1. Network planning . . . . . . 3 Chapter 4. Installing . . . . . . . . . 31

| Tivoli Workload Scheduler environment . . . . . 3 Installing DB2 . . . . . . . . . . . . . 31
| Tivoli Workload Scheduler interfaces . . . . . 6 | Using the installation wizard . . . . . . . . 31
Planning domains . . . . . . . . . . . . 7 | Installing a new master domain manager or
Localized processing in your domain . . . . . 7 | backup master . . . . . . . . . . . . 31
Considerations in planning domains . . . . . 7 | Installing a new agent or domain manager . . . 40
Single domain network . . . . . . . . . . 9 | Installing a command line client . . . . . . 41
Multiple domain network . . . . . . . . 10 | Adding a new feature . . . . . . . . . . 42
Workstation classes . . . . . . . . . . . . 12 | Performing a silent installation . . . . . . . . 44
Time zone considerations . . . . . . . . . . 12 | Silent installation using response file templates 44
| Silent installation using an automatically
Chapter 2. Prerequisite information . . 13 | generated response file . . . . . . . . . 47
Selecting your installation method . . . . . . . 13 | Installing non-integratable agents using twsinst . . 48
Launchpad . . . . . . . . . . . . . 13 | Non-integratable agents . . . . . . . . . 48
Installation wizard . . . . . . . . . . . 14 | Installing a new non-integratable agent . . . . 48
Silent mode . . . . . . . . . . . . . 14 Installing agents using Software Distribution . . . 50
twsinst script for non-integratable agents on Software packages and parameters . . . . . 50
UNIX and Linux. . . . . . . . . . . . 14 Installation procedure . . . . . . . . . . 52
Software Distribution software package blocks Installing language packs . . . . . . . . . 53
(SPBs) . . . . . . . . . . . . . . . 14
User authorization requirements . . . . . . . 14 Chapter 5. Upgrading . . . . . . . . 55
Authorization roles for running the installation, Upgrading a version 8.2 or 8.2.1 master domain
uninstallation, and upgrade wizards . . . . . 15 manager instance . . . . . . . . . . . . 55
Authorization roles for data import after Upgrading Overview . . . . . . . . . . 55
upgrading from version 8.2 . . . . . . . . 15 Master and backup master domain manager
Authorization roles for running the twsinst script 15 upgrade scenarios . . . . . . . . . . . 58
Authorization roles for Software Distribution . . 16 Deciding how to upgrade the database . . . . 59
Tivoli Workload Scheduler user. . . . . . . . 16 | Configuring the security file for new functions 63
Windows users domain rights and structure . . 16 Preparing the upgrade environment . . . . . 63
Considerations for Windows domain controllers | New directory structure . . . . . . . . . 63
running Microsoft Active Directory . . . . . 17 Performing a parallel upgrade . . . . . . . 66
Checking environment settings for Windows | Performing a direct upgrade. . . . . . . . 75
Vista users. . . . . . . . . . . . . . 17 Data import - problem resolving . . . . . . 84
Installation paths and product instances . . . . . 18 Post-upgrade issues . . . . . . . . . . 90
Windows services . . . . . . . . . . . . 19 | Upgrading a version 8.3 or 8.4 master domain
| manager instance . . . . . . . . . . . . 90
| Upgrading overview . . . . . . . . . . 90
Part 2. Tivoli Workload Scheduler 21
© Copyright IBM Corp. 1991, 2008 iii

| Master and backup domain manager upgrade Problems installing on HP-UX . . . . . . . 144
| scenarios . . . . . . . . . . . . . . 93 Problems installing on Sun Solaris . . . . . 145
| Configuring the security file for new functions 95 Problems installing on Linux . . . . . . . 145
| Preparing to upgrade . . . . . . . . . . 95 Problems with the silent installation . . . . . 146
| New directory structure . . . . . . . . . 96 Problems with installations using the twsinst
| Performing a parallel upgrade . . . . . . . 98 script . . . . . . . . . . . . . . . 146
| Performing a direct upgrade . . . . . . . 102 Problems installing the application server . . . 146
Upgrading backup master domain manager . . . 108 Other installation problems. . . . . . . . 147
Upgrading agents and domain managers . . . . 108 Upgrade problems. . . . . . . . . . . 155
| New directory structure . . . . . . . . . 109 Migration problems . . . . . . . . . . 158
Unlinking and stopping Tivoli Workload Uninstallation problems . . . . . . . . . 162
Scheduler when upgrading agent workstations . 110 Fix pack installation problems . . . . . . . 164
| Upgrading agents using the installation wizard 111 Security implications of the installation . . . . . 165
Upgrading agents using a silent installation . . 112 Verifying the installation . . . . . . . . . 165
Upgrading non-integratable agents using twsinst 112 Uninstalling Tivoli Workload Scheduler manually 166
Upgrading non-integratable agents using Uninstalling manually on Windows . . . . . 167
Software Distribution . . . . . . . . . . 114 Uninstalling manually on UNIX . . . . . . 169
| Upgrading a command line client . . . . . . 116 Uninstalling Tivoli Workload Scheduler connectors
manually . . . . . . . . . . . . . . . 171
Chapter 6. Configuring . . . . . . . 117 Uninstalling the connector manually on UNIX 171
Setting the environment variables . . . . . . 117 Uninstalling the connector manually on
Configuring a master domain manager . . . . . 117 Windows . . . . . . . . . . . . . . 172
Configuring a backup master domain manager . . 118 Removing Windows registry keys . . . . . . 173
Configuring an agent . . . . . . . . . . . 119
| Configuring a command line client . . . . . . 120 Chapter 9. Installation, uninstallation,
Configuring WebSphere Application Server . . . 120 and upgrade messages . . . . . . . 175
IBM Tivoli message format . . . . . . . . . 175
Chapter 7. Uninstalling . . . . . . . 121 Message number . . . . . . . . . . . 175
Uninstalling using the wizard . . . . . . . . 121 Message text . . . . . . . . . . . . 176
Performing a silent uninstallation . . . . . . 122 Message help . . . . . . . . . . . . 177
Uninstalling agents using the twsinst script . . . 122 Installation (InstallShield wizard) common
Uninstalling using the Software Distribution CLI 123 messages - JIC . . . . . . . . . . . . . 177
Uninstalling a command line client . . . . . . 124 Installation (InstallShield wizard) messages - JIS 183
Installation messages (twsinst) - FAB . . . . . 236
Chapter 8. Troubleshooting Installation messages (fix pack) - FAF . . . . . 244
installation, migration, and
uninstallation . . . . . . . . . . . 125 Part 3. Tivoli Dynamic Workload
| Log files of installation processes . . . . . . . 125 Console . . . . . . . . . . . . . 249
| Packaging log files for support . . . . . . 125
| Recovering a failed interactive InstallShield wizard Chapter 10. Preparing . . . . . . . . 251
| installation . . . . . . . . . . . . . . 125 | Overview of Tivoli Dynamic Workload Console 251
| The Step List window . . . . . . . . . 126 | Installation overview . . . . . . . . . . . 251
| The Step window . . . . . . . . . . . 128 Installation considerations . . . . . . . . . 252
| Correcting a failed step and continuing the Selecting your installation method . . . . . 253
| installation . . . . . . . . . . . . . 131 | Instances of Tivoli Workload Automation . . . 253
| Deciding whether to resume the wizard or | Installation media . . . . . . . . . . . 254
| rerun it . . . . . . . . . . . . . . 132 Tivoli Dynamic Workload Broker supported
| Deciding whether to resume immediately or exit servers . . . . . . . . . . . . . . 255
| and resume later . . . . . . . . . . . 133 | Installation log files . . . . . . . . . . 255
| Stopping and resuming an interactive
| installation . . . . . . . . . . . . . 134
| Example procedure for resolving a problem . . 135
Chapter 11. Installing . . . . . . . . 257
Recovering a failed silent InstallShield wizard Installing Tivoli Dynamic Workload Console . . . 257
installation . . . . . . . . . . . . . . 135 | Using the launchpad . . . . . . . . . . 257
Recovering a failed upgrade . . . . . . . . 136 | Using the installation wizard . . . . . . . 257
Problem scenarios: install, reinstall, upgrade, Performing a silent installation . . . . . . 262
migrate, and uninstall . . . . . . . . . . 136 Post-installation steps to connect to Tivoli
Problems installing on Windows . . . . . . 137 Workload Scheduler Version 8.3 Fix Pack 3 . . . 263
Problems installing on AIX . . . . . . . . 142 Accessing Tivoli Dynamic Workload Console . . . 265
Problems installing on UNIX . . . . . . . 143
iv IBM Tivoli Workload Scheduler Planning and Installation

Quick steps to define a Tivoli Workload Overview of the scheduling scenarios . . . . . 303
Scheduler engine connection . . . . . . . 266 Creating and working with the production plan 303
Quick steps to define a Tivoli Dynamic | Scenario 1: Creating the production plan and
Workload Broker server connection . . . . . 267 | viewing its contents . . . . . . . . . . 304
| Starting and stopping Tivoli Dynamic Workload Running the scheduling scenarios . . . . . . 304
| Console . . . . . . . . . . . . . . . 269 Scenario 2: Starting and stopping Tivoli
Workload Scheduler processes . . . . . . . 304
| Chapter 12. Configuring . . . . . . . 271 Scenario 3: Scheduling basics, how jobs are
scheduled, and run order of jobs . . . . . . 305
Scenario 4: Advanced scheduling, dependencies
| Chapter 13. Upgrading . . . . . . . 273
from prompts, files, and resources . . . . . 305
| Upgrading with an embedded WebSphere
Scenario 5: Time dependencies and run cycles 305
| Application Server . . . . . . . . . . . 273
Scenario 6: Manual submission of jobs, job
| New directory structure . . . . . . . . . 273
streams, and commands . . . . . . . . . 306
| Upgrading using the installation wizard . . . 274
Scenario 7: Recovery options and recovery jobs 306
| Upgrading with an external instance of WebSphere
Scenario 8: Event-driven scheduling . . . . . 307
| Application Server . . . . . . . . . . . 275
| Scenario 9: Using variable tables . . . . . . 307
| Upgrading using the installation wizard . . . 275
Removing tutorial objects from the database . . . 308
Chapter 14. Uninstalling . . . . . . . 277 Appendix A. Registry file . . . . . . 309

Uninstalling using the wizard . . . . . . . . 277
Uninstalling in silent mode . . . . . . . . . 279
| Appendix B. Response file properties 311
| General . . . . . . . . . . . . . . . 311
Chapter 15. Troubleshooting the
| Tivoli Workload Scheduler response file properties 311
installation and uninstallation . . . . 281 | Tivoli Dynamic Workload Console response file
Installation and uninstallation log and trace files 281 | properties . . . . . . . . . . . . . . 319
Recovering a failed InstallShield wizard installation 281
Recovering a failed upgrade . . . . . . . . 281
| Appendix C. Installing Tivoli Workload
| Uninstalling Tivoli Dynamic Workload Console
| and the embedded WebSphere Application Server | Scheduler Integration Workbench . . 325
| manually . . . . . . . . . . . . . . . 282 | Installing Tivoli Workload Scheduler Integration
Troubleshooting scenarios . . . . . . . . . 283 | Workbench with the bundled version of Eclipse . . 325
Problems with the launchpad . . . . . . . 283 | Installing Tivoli Workload Scheduler Integration
Problems with the interactive wizard . . . . 283 | Workbench with an existing instance of Eclipse . . 325
Problems with the silent installation . . . . . 286
Problems with the uninstallation . . . . . . 287 | Appendix D. Discovering installed
| products . . . . . . . . . . . . . 327
Chapter 16. Installation, and
uninstallation messages. . . . . . . 289 | Appendix E. Files backed up during
Installation (InstallShield wizard) common | upgrade. . . . . . . . . . . . . . 329
messages - JIC . . . . . . . . . . . . . 289
Installation (InstallShield wizard) messages - UI | Appendix F. DB2 tablespace relative
(001–100) . . . . . . . . . . . . . . . 289
| paths . . . . . . . . . . . . . . . 331
Part 4. Tutorials . . . . . . . . . 299 Notices . . . . . . . . . . . . . . 333

Notices and information about vendor products,
Chapter 17. Using the Tivoli Workload components, and code . . . . . . . . . . 334
Scheduler tutorial utility . . . . . . . 301 Trademarks . . . . . . . . . . . . . . 334
Populating your Tivoli Workload Scheduler
database . . . . . . . . . . . . . . . 301 Index . . . . . . . . . . . . . . . 337
Objects used by the Tivoli Workload Scheduler
tutorial scenarios . . . . . . . . . . . 302
Contents v
vi IBM Tivoli Workload Scheduler Planning and Installation
List of figures
| 1. Graphical overview of Tivoli Workload | 6. Overview of procedure for upgrading from
| Scheduler environment . . . . . . . . . 4 | version 8.3 or 8.4. . . . . . . . . . . 92
2. Single domain topology . . . . . . . . . 9 | 7. Wizard panel after an installation failure 126
3. Single domain topology on multiple sites 10 | 8. Step List window showing a failed step 127
4. Multiple domain topology . . . . . . . 11 | 9. Step status tab . . . . . . . . . . . 128
| 5. Overview of procedure for upgrading from | 10. Step properties tab . . . . . . . . . . 129
| version 8.2.x . . . . . . . . . . . . 57 | 11. Step output tab . . . . . . . . . . . 130
© Copyright IBM Corp. 1991, 2008 vii

viii IBM Tivoli Workload Scheduler Planning and Installation
List of tables
1. Required authorization roles for running the 17. Data and behavior mapping for job definitions 87
installation wizard . . . . . . . . . . 15 18. Data and behavior mapping for Windows
2. Required authorization roles for running the users . . . . . . . . . . . . . . . 87
installation wizard . . . . . . . . . . 15 19. Data and behavior mapping for resources 87
3. Required authorization roles for running 20. Data and behavior mapping for job streams 88
twsinst . . . . . . . . . . . . . . 15 21. Data and behavior mapping for jobs . . . . 88
4. Required authorization roles for Software 22. Data and behavior mapping for dependencies 89
Distribution . . . . . . . . . . . . 16 | 23. Installing into an existing instance of Tivoli
| 5. Symlink options . . . . . . . . . . . 25 | Workload Automation . . . . . . . . 253
| 6. Upgrade availability for Tivoli Workload | 24. Installing into an instance outside Tivoli
| Scheduler components . . . . . . . . . 25 | Workload Automation . . . . . . . . 254
| 7. Installing into an existing instance of Tivoli | 25. Installation log files . . . . . . . . . 255
| Workload Automation . . . . . . . . . 26 | 26. Tivoli Dynamic Workload Console response
| 8. Installation log files . . . . . . . . . . 28 | files . . . . . . . . . . . . . . . 262
9. DB2 Setup files . . . . . . . . . . . 31 | 27. Objects downloaded by the tutorial utility 302
| 10. Optional installable features and components 42 | 28. List of scheduling scenarios . . . . . . . 303
| 11. Response files . . . . . . . . . . . . 44 29. Registry file attributes . . . . . . . . 309
12. SPB installation parameters . . . . . . . 51 | 30. Tivoli Workload Scheduler response file
13. List of parameters to install language packs 53 | properties . . . . . . . . . . . . . 312
14. Data and behavior mapping for domains 85 | 31. Tivoli Dynamic Workload Console response
15. Data and behavior mapping for workstations 86 | file properties . . . . . . . . . . . 319
16. Data and behavior mapping for workstation
classes . . . . . . . . . . . . . . 86
© Copyright IBM Corp. 1991, 2008 ix

x IBM Tivoli Workload Scheduler Planning and Installation
About this publication
This IBM® Tivoli® Workload Scheduler Planning and Installation provides information
for planning, installing, migrating, and configuring an IBM Tivoli Workload
Scheduler network.
What is new in this release

For information about the new or changed functions in this release, see Tivoli
Workload Automation: Overview.
For information about the APARs that this release addresses, see the Tivoli
Workload Scheduler Download Document.
| What is new in this publication

| This section describes what has changed in this publication since version 8.4.
| Note: Changed or added text is marked by a revision bar in the left margin.
| What is new in version 8.5

| The following changes were made:
| v The material in this publication has been reorganized and now contains
| information about Tivoli Workload Scheduler, Tivoli Dynamic Workload Console,
| troubleshooting, and installation messages.
| v Information about ongoing administration tasks has been moved into the Tivoli
| Workload Scheduler: Administration Guide.
| v New topics in this publication include information about:
| – The new launchpad.
| – The updated installation wizards, especially the Tivoli Dynamic Workload
| Console wizard.
| – The new installation directory structure and the concept of Tivoli Workload
| Automation instances.
| – How to install DB2 from the launchpad. DB2 is no longer integrated in the
| product installation.
| – The new response files, targeted at specific installation scenarios.
| – How to use the new automatically generated response files.
| – Installing Tivoli Workload Scheduler Integration Workbench.
| – Discovering installed products.
| – Files backed up during the upgrade procedure.
Who should read this publication

This guide is intended for the following audience:
v Tivoli Workload Scheduler IT administrators who plan for and install the
network
v Tivoli Dynamic Workload Console IT administrators who plan for and install the
product
© Copyright IBM Corp. 1991, 2008 xi

Who should read this publication
v Specialists who plan the network topology

v IT administrators who install the network
v System architects
Publications
Full details of Tivoli Workload Scheduler publications can be found in Tivoli
Workload Automation: Publications. This document also contains information on the
conventions used in the publications.
A glossary of terms used in the product can be found in Tivoli Workload Automation:
Glossary.
Both of these are in the Information Center as separate publications.
Accessibility
Accessibility features help users with a physical disability, such as restricted
mobility or limited vision, to use software products successfully. With this product,
you can use assistive technologies to hear and navigate the interface. You can also
use the keyboard instead of the mouse to operate all features of the graphical user
interface.
For full information with respect to the Tivoli Dynamic Workload Console, see the
Accessibility Appendix in the Tivoli Workload Scheduler: User's Guide and Reference,
SC32-1274.
For full information with respect to the Job Scheduling Console, see the
Accessibility Appendix in the Tivoli Workload Scheduler: Job Scheduling Console User’s
Guide.
Tivoli technical training

For Tivoli technical training information, refer to the following IBM Tivoli
Education Web site:
http://www.ibm.com/software/tivoli/education
Support information
If you have a problem with your IBM software, you want to resolve it quickly. IBM
provides the following ways for you to obtain the support you need:
v Searching knowledge bases: You can search across a large collection of known
problems and workarounds, Technotes, and other information.
v Obtaining fixes: You can locate the latest fixes that are already available for your
product.
v Contacting IBM Software Support: If you still cannot solve your problem, and
you need to work with someone from IBM, you can use a variety of ways to
contact IBM Software Support.
xii IBM Tivoli Workload Scheduler Planning and Installation

Part 1. Planning
This part provides an overview of the Tivoli Workload Automation environment
and describes how to plan for the installation. It contains the following chapters:
v Chapter 1, “Network planning,” on page 3
v Chapter 2, “Prerequisite information,” on page 13
© Copyright IBM Corp. 1991, 2008 1

2 IBM Tivoli Workload Scheduler Planning and Installation
Chapter 1. Network planning
This section provides information to help you plan your Tivoli Workload Scheduler
network.
| Tivoli Workload Scheduler environment

| A Tivoli Workload Scheduler network consists of a set of linked workstations on
| which you perform job processing. A network is composed of one or more
| domains, each having a domain manager workstation acting as a management hub,
| and one or more agent workstations.
| Figure 1 on page 4 gives a graphical overview of the Tivoli Workload Scheduler

| environment:
|

Network planning
User Interfaces
Web browser
Command-line Tivoli Dynamic Master Domain

client (remote) Workload Console
(MD)
Database
Command Master domain

manager
line
Backup master
domain manager
Agents (agent)
Child domain
manager (agent) Child domain
(Dn)
Example domain hierarchy
Agents Backup domain
MD manager (agent)
D1 D2 Child domain
manager
(agent)
D3 D4 D5
Child domain
D6 (Dn) - and so on
|
| Figure 1. Graphical overview of Tivoli Workload Scheduler environment
|
| In Figure 1 the master domain is shown with its principle components, and two
| levels of subdomain. The available user interfaces are also indicated. An example is
| provided of the basic domain hierarchical structure, where each domain is named
| "D1", "D2, and so on. All of these concepts are explained in detail later in this
| section.
| The objects in the Tivoli Workload Scheduler environment are as follows:

| Master domain manager
| The master domain manager is the highest level workstation of a Tivoli
| Workload Scheduler network. It contains or connects to the relational
| database that stores scheduling object definitions. It creates or updates a
| production file when the plan is created or extended and then distributes
| the file to the network. It performs all logging and reporting for the
| network. It can perform the role of event processing server for the
| event-driven workload automation feature.

Network planning
| Backup master domain manager

| Define a backup master domain manager at installation to point to either
| the database being used by the master domain manager or to a mirror of
| that database. In this way the backup master domain manager has the
| latest data available to it at all times.
| A connector to the Tivoli Dynamic Workload Console is installed
| automatically on the backup master.
| Domain manager
| In a multi-domain network all domains below the master domain have an
| agent configured to be a domain manager to manage the workstations in
| its domain. Each domain manager is an agent in the domain of the next
| higher level.
| Backup domain manager
| If your domain manager experiences problems, you can configure any
| fault-tolerant agent as the domain manager and switch to it with a simple
| procedure.
| Agent An agent is a workstation in the network that runs the jobs which are
| controlled by Tivoli Workload Scheduler. Install an agent by choosing the
| agent installation. Later, you can define it in the database as a specific type
| of agent. There are several different types of agents:
| Fault-tolerant agent
| Fault-tolerant agents are capable of resolving local dependencies
| and launching its jobs in the absence of a domain manager. With a
| simple reconfiguration they can serve as subordinate domain
| managers (see above). All of the agents with special roles (master
| domain manager, backup master domain manager, domain
| manager, backup domain manager) can also behave as
| fault-tolerant agents with jobs scheduled on them.
| Standard agent
| An agent workstation launches jobs only under the direction of its
| domain manager.
| Extended agent
| Extended agents are logical definitions (hosted by a physical
| workstation) used to extend job processing to selected applications
| (SAP R/3, Oracle E-Business Suite, PeopleSoft, and z/OS®). For
| information about installing an extended agent, see Tivoli Workload
| Scheduler for Applications: User’s Guide.
| Installing integratable agents and non-integratable agents
| Any of the above agents can be considered integratable or non-integratable
| agents. The following is a description of both types of agents.
| Integratable agent
| Integratable agents are installed by the InstallShield wizard or by
| silent installation. You can add the distributed connector to this
| kind of agent to use Tivoli Dynamic Workload Console or the Job
| Scheduling Console and integrate them with other Tivoli Workload
| Automation components.
| Non-integratable agent
| Non-integratable agents are agents which you install with the
| twsinst non-JVM command-line script or the Software Distribution
| method. These agents are installed outside the Tivoli Workload
Chapter 1. Network planning 5

Network planning
| Automation instance infrastructure (see “Installation paths and

| product instances” on page 18). Since you cannot add the
| distributed connector as a feature, they cannot be controlled from
| the Tivoli Dynamic Workload Console or the Job Scheduling
| Console. Once installed in this way they can only be updated or
| uninstalled in the same way. For more information, see “Installing
| non-integratable agents using twsinst” on page 48.
| Note: The terminology non-integratable only refers to their

| installation environment; in all other respects they are
| fully-functional agents.
| Tivoli Workload Scheduler interfaces

| Tivoli Workload Scheduler includes the following user interfaces from which you
| manage your production environment:
| Master domain manager command line
| The master domain manager command line is installed automatically when
| you install the master domain manager. This command line interface is run
| only from the workstation serving as the master domain manager. From
| the command line, you can manage the processes of the master domain
| manager. Note that a backup master domain manager command line also
| exists on the backup master domain manager.
| Tivoli Dynamic Workload Console
| Tivoli Dynamic Workload Console is a Web-based interface used to control
| scheduling activities and manage the production environment in the Tivoli
| Workload Scheduler distributed and z/OS environments, as well as Tivoli
| Dynamic Workload Broker. You can interface with the console from any
| system in the network where a supported Web browser is installed. For
| more information, see Part 3, “Tivoli Dynamic Workload Console,” on page
| 249.
| Job Scheduling Console
| The Job Scheduling Console is an interface for creating, modifying,
| monitoring, controlling, and deleting Tivoli Workload Scheduler objects.
| See Tivoli Workload Scheduler: Job Scheduling Console User’s Guide.
| Command line client
| The command line client is a component of Tivoli Workload Scheduler that
| allows you to implement commands on the master domain manager from
| another workstation. It can be installed on any workstation in the network,
| including those that include no other Tivoli Workload Scheduler
| component.
| Additionally, Tivoli Workload Automation contains the z/OS connector, which is a

| component that provides a bridge between Tivoli Workload Scheduler for z/OS
| and the Tivoli Dynamic Workload Console. For more information, see the IBM
| Tivoli Workload Scheduler Job Scheduling Console User’s Guide.
| For a more detailed description of the Tivoli Workload Scheduler components, see
| Overview.

Network planning
Planning domains
A Tivoli Workload Scheduler network contains at least one master domain
manager that acts as a management hub for the product. Additional domains can
be used to divide a widely distributed network into locally-managed groups of
workstations.
In a single domain configuration, the master domain manager maintains

communications with all of the workstations in the network.
In a multiple domain configuration, the master domain manager communicates

with the workstations in its domain and all immediately subordinate domain
managers. The subordinate domain managers communicate with the workstations
in their domains and their immediately subordinate domain managers, and so on.
Domain managers report all of the activities of the domain to the master. Using
multiple domains reduces network traffic and the load on the master by reducing
the number of direct communications between the master domain manager and
workstations. Multiple domains also provide fault-tolerance by limiting the outage
caused by losing a domain manager in a single domain. To limit the effects further,
you can designate backup domain managers to take over if domain managers fail.
When you define a new domain, you must identify the parent domain and the
domain manager. The parent domain is the domain directly above the new domain
in the domain hierarchy. All communications to and from a domain are routed
through the parent domain manager.
Localized processing in your domain

Localized processing is separating your scheduling needs based on a common set
of characteristics, such as geographical locations, business functions, and
application groupings. Group related processing can limit the amount of
interdependency information that needs to be communicated between domains.
The benefits of localized domains are:

Decreased network traffic
Keeping processing localized to domains eliminates the need for frequent
inter-domain communication.
Tighter security and simplified administration
Security and administration can be defined at and limited to the domain
level. Instead of network-wide or workstation-specific administration, you
can have domain administration.
Optimized network and workstation fault-tolerance
In a multiple domain network, you can define backups for each domain
manager so that problems in one domain do not disrupt operations in
other domains.
Considerations in planning domains

In planning your Tivoli Workload Scheduler network, consider the following:
Number of workstations, applications, and jobs
Consider the number of workstations that comprise the network and the
number of applications and jobs that the network runs. If you have a small
number of workstations, or a small number of applications to control, you
do not need multiple domains.

Network planning
Number of geographic locations

Consider the number of geographic locations covered by your network and
the reliability and efficiency of communication between the locations.
Multiple geographic locations is one of the primary reasons for choosing a
multiple domain architecture. One domain for each geographical location is
a common configuration. A single domain architecture relies on the
network maintaining continuous processing.
Time zones
When your network is spread across multiple geographic locations in
different time zones, decide whether to activate the time zone feature. See
“Time zone considerations” on page 12.
Centralized or decentralized management
You can manage single or multiple domain networks from a single master
domain manager. If you want to manage multiple locations separately, you
can consider the installation of a separate Tivoli Workload Scheduler
network at each location. Some decentralized management is possible in a
stand-alone Tivoli Workload Scheduler network by mounting or sharing
file systems.
Types of applications
Consider the types of applications that are run by Tivoli Workload
Scheduler. If you have multiple applications that are distinctly separate
from each other, you might choose to put them in separate domains.
Windows® network
When you have a Windows network, you might want your Tivoli
Workload Scheduler domains to mirror your Windows domains.
System performance and other criteria
You can define multiple domains to localize systems based on performance
or operating system type.
Amount of network traffic
If your network traffic is manageable, having multiple domains is less
important.
Dependencies between jobs
Consider if you need to plan for job dependencies that cross system
boundaries, geographical boundaries, or application boundaries. For
example, does the start of Job1 on workstation1 depend on the completion
of Job2 running on workstation2. The degree of interdependence between
jobs is an important consideration when planning your network. If you use
multiple domains, try to keep interdependent objects in the same domain,
thereby decreasing network traffic and improving use of the domain
architecture. See the IBM Tivoli Workload Scheduler Job Scheduling Console
User’s Guide.
Level of fault-tolerance required
A disadvantage of the single domain configuration is the reliance on a
single domain manager. In a multi-domain network, the loss of a single
domain manager affects only the agents in its domain.
Firewalls
When your network contains firewalls, plan the structure of your domains
around the firewalls. See Tivoli Workload Scheduler: Administration Guide.

Network planning
Secure Sockets Layer (SSL) encryption

If you want to use SSL encryption in your network, plan your domains in
accordance with the protocol. See Tivoli Workload Scheduler: Administration
Guide.
Single domain network

A single domain network consists of a master domain manager and any number of
agents. Figure 2 shows an example of a single domain network. A single domain
network is well-suited to companies that have few locations and business
functions. All communication in the network is routed through the master domain
manager. With a single location, you are concerned only with the reliability of your
local network and the amount of traffic it can handle.
Master
Domain
Manager
Agents
Figure 2. Single domain topology
Single domain networks can be combined with other networks, single or multiple
domain, to meet multiple site requirements. Tivoli Workload Scheduler supports
internetwork dependencies between jobs running on different networks.

Network planning
Example 1
Atlanta Backup Master

Master Domain Manager
Domain
Manager
Tivoli Dynamic
Workload Console Agent
Denver
Agent Agent Agent
Or:
Example 2
Atlanta Denver
Master Master
Domain Domain
Manager Manager
Backup
Master
Domain
Manager
Agent Agent Agent Agent
Figure 3. Single domain topology on multiple sites
Example 1 shows a single domain network. The master domain manager is located
in Atlanta, along with several agents. There are also agents located in Denver. The
agents in Denver depend on the master domain manager in Atlanta to resolve all
interagent dependencies, even though the dependencies might be on jobs that run
in Denver. An alternative would be to create separate single domain networks in
Atlanta and Denver, as shown in example 2.
Multiple domain network

Multiple domain networks are especially suited to companies that span multiple
locations, departments, or business functions. A multiple domain network consists
of a master domain manager, any number of lower tier domain managers, and any
number of agents in each domain. Agents communicate only with their domain

Network planning
managers, and domain managers communicate with their parent domain

managers. The hierarchy of domains can go down to any number of levels.
Master domain
Atlanta Backup Master
Master Domain Manager
Domain
Manager
Tivoli Dynamic
Workload Console
Agent
Second-level Domain Domain

Manager Los Manager
domains
Angeles
Denver
Agent
Agent Agent Agent Agent
Third-level Domain Aurora Domain

domains Manager Domain Manager
Manager
New Burbank
York
Agent Agent Agent Agent Agent Agent
Figure 4. Multiple domain topology
As Figure 4 illustrates, the master domain manager is located in Atlanta. The

master domain manager contains the database files used to document the
scheduling objects, and distributes the Symphony file to its agents and the domain
managers in Denver and Los Angeles. The Denver and Los Angeles domain
managers then distribute the Symphony file to their agents and subordinate
domain managers in New York, Aurora, and Burbank. The master domain
manager in Atlanta is responsible for broadcasting inter-domain information
throughout the network.

Network planning
All communication to and from the Boulder domain manager is routed through its
parent domain manager in Denver. If there are schedules or jobs in the Boulder
domain that are dependent on schedules or jobs in the Aurora domain, those
dependencies are resolved by the Denver domain manager. Most inter-agent
dependencies are handled locally by the lower tier domain managers, greatly
reducing traffic on the network.
Workstation classes
Workstations are organized into domains to make your network management
easier and more efficient. However, the domain name is not one of the selection
criteria when choosing where to run a job or job stream. If you want to group
workstations together because they have similar job scheduling characteristics, use
a workstation class. Any number of workstations can be grouped in a class, and a
workstation can be in many classes. Jobs and job streams can be assigned to run on
a specific workstation class.
For example, you could set up workstation classes to group workstations according
to:
v Your internal departmental structure, so that you could define a job that would
be run on all the workstations in a department
v The software installed on them, so that you could define a job that would be run
on all the workstations that had a particular application installed
v The role of the user, so that you could define a job that would be run on all the
workstations belonging to, for example, managers
In this example, an individual workstation could be in one workstation class for its
department, another for its user, and several others for the software installed on it.
Time zone considerations

Time zone support is an optional feature that is enabled by default. It allows you
to manage workloads at a global level. For information about how to set the time
zone, see Tivoli Workload Scheduler: Administration Guide.
Time zone implementation also enables easy scheduling across multiple time
zones. For a description of how the time zone works, refer to the User's Guide and
Reference.

Chapter 2. Prerequisite information
This chapter provides an overview of the prerequisites you need to check before
you begin installing Tivoli Workload Scheduler. For a detailed list of supported
operating systems and product prerequisites, see the download documentation and
release notes. This chapter includes the following topics:
v “Selecting your installation method”
v “User authorization requirements” on page 14
v “Tivoli Workload Scheduler user” on page 16
v “Installation paths and product instances” on page 18
v “Windows services” on page 19
Selecting your installation method

You can install Tivoli Workload Scheduler using one of the following methods:
Launchpad
| The launchpad is the starting point for installing products that are part of Tivoli
| Workload Automation, as well as DB2®. Using the launchpad, you can:
| v Install or upgrade all Tivoli Workload Scheduler components
| v Install or upgrade Tivoli Dynamic Workload Broker
| v Install or upgrade Tivoli Dynamic Workload Console
| v Install the Job Scheduling Console
| v Install DB2
| v Access product information
The launchpad automatically accesses and runs the related installation setup file in
interactive mode.
The launchpad requires some additional installation prerequisites. For more

information, see the Tivoli Workload Scheduler System Requirements Document at
http://www.ibm.com/support/docview.wss?rs=672&uid=swg27012175.
Note: When running the launchpad on UNIX® and Linux® operating systems,
make sure you export the browser location to the BROWSER environment
variable.
If you have autorun enabled, the launchpad starts automatically., To start the
launchpad installation program, perform the following steps:
1. From the DVD, run the launchpad as follows:
Windows
From the root directory of the DVD, run launchpad.exe.
UNIX From the root directory of the DVD, run launchpad.sh.
The launchpad is displayed.
2. Click Install IBM Tivoli Workload Scheduler in the left frame of the
launchpad.
3. Click on one of the displayed links to install the following:

Prerequisite information
v IBM Tivoli Workload Scheduler components (master domain manager,

backup master domain manager, fault tolerant agents, command line client,
connector, and language packs)
v Tivoli Dynamic Workload Console
v IBM Tivoli Workload Scheduler Job Scheduling Console
v IBM Tivoli Workload Scheduler Job Scheduling Console Language Pack
The related installation program starts. To proceed with the installation of the
selected Tivoli Workload Scheduler component, follow the instructions
described in the following sections.
To access information about product installation prerequisites, click the different

options in the left frame of the launchpad.
Installation wizard
Install Tivoli Workload Scheduler master domain managers, backup masters,
agents, connectors, and Tivoli Dynamic Workload Console by launching the
individual setup files for each supported platform.
You can use the installation wizard in interactive or silent mode. In interactive
mode, the wizard guides you through the installation steps. In silent mode, a
response file provides the relevant information to the installation process, which is
run in background.
This method of installation uses a Java™ Virtual Machine, and therefore has specific
system requirements. See Chapter 2, “Prerequisite information,” on page 13 for
details about installation requirements.
Silent mode
Customize a response file by adding all the configuration settings to be used during
installation. Then, from the command line, run the setup command. Using this
method you can run the installation unattended and in the background. For more
information, see “Performing a silent installation” on page 44.
twsinst script for non-integratable agents on UNIX and Linux

Use the twsinst script to install non-integratable agents on UNIX and Linux
operating systems. For information about non-integratable agents, see
“Non-integratable agents” on page 48. This method does not use a Java Virtual
Machine and can be used instead of the installation wizard. See “Installing
non-integratable agents using twsinst” on page 48.
Software Distribution software package blocks (SPBs)

Install non-integratable agents using the Software Distribution component of IBM
Tivoli Configuration Manager, versions 4.1, 4.2, 4.2.1, 4.2.2, or 4.2.3 by distributing
software package blocks. See “Installing agents using Software Distribution” on
page 50.
User authorization requirements

Depending on the installation method you choose, check the authorization roles
before beginning the installation procedure.

Authorization roles for running the installation, uninstallation,

and upgrade wizards
Table 1 provides the authorization roles required to use the installation wizard
method of installation.
Table 1. Required authorization roles for running the installation wizard
Activity Required role
Installing using the wizard v Windows: your login account must be a
member of the Windows Administrators group
Upgrading from version 8.3 and
or domain administrators with Act as Part of
higher
the Operating System.
v UNIX and Linux: root access
Upgrading from version 8.2 with an v Windows: your login account must be a
automatic data import member of the Windows Administrators group
| v Write rights to the TWS_PATH/bin
v Access, replace, and modify rights on all
database objects that are to be imported into the
new database
Authorization roles for data import after upgrading from

version 8.2
Table 2 provides the authorization roles required to import the database objects
after upgrading from version 8.2.
Table 2. Required authorization roles for running the installation wizard
Data import using the datamigrate v Windows: your login account must be a
command member of the Windows Administrators group
| v Write rights to the TWS_PATH/bin
v Access, replace, and modify rights on all
database objects that are to be imported into the
new database
Authorization roles for running the twsinst script

Table 3 provides the authorization roles required to use the twsinst method of
installation.
Table 3. Required authorization roles for running twsinst
Running the twsinst script root access
Chapter 2. Prerequisite information 15

Authorization roles for Software Distribution

Table 4 provides the authorization roles required to use the Software Distribution
method of installation.
Table 4. Required authorization roles for Software Distribution
Using Software Distribution to install a admin, senior, or super
software package block
v Windows: your login account must be a
member of the Windows Administrators
group with Act as Part of the Operating
System.
Tivoli Workload Scheduler user

On UNIX and Linux operating systems, regardless of the method of installation
you choose, the Tivoli Workload Scheduler user must be created manually before
running the installation. Use the appropriate UNIX and Linux operating system
commands to create the user.
Note: Some operating systems require that for users with a password, the
password must be changed at the first login.
Windows users domain rights and structure

If you install on Windows operating systems, consider the constraints listed next.
Do not install two agents on the same system using the same user, one on local
system and one defined on the domain with the same name..
The Windows user performing the installation must:

v For a local TWSuser, be a member of the local administrative group
v For a domain TWSuser, be a member of the domain administrative groups in the
domain controller
All Windows 2003 TWSusers need the following user rights. They may be granted
locally. Domain level policies always override local policies, so it may be required
to grant these rights from the domain:
v Act as part of the operating system
v Allow logon locally
v Impersonate a client after authentication right
v Log on:
– Locally
– As batch job
– As service
v Replace process level token
Note: These rights will be granted during the install, but you can confirm them
manually.

Considerations for Windows domain controllers running

Microsoft Active Directory
If you want to install Tivoli Workload Scheduler fault-tolerant agents on
workstations where users that run jobs are domain users and the domain controller
is running Microsoft® Active Directory, decide how to install the agents and
configure the domain so that the jobmon process can obtain the correct information
to let the users run jobs.
Before running a job, jobmon must retrieve information about the user running the
job. If the user is a domain user and the domain controller is running Microsoft
Active Directory, whether the user information can be retrieved depends on the
information in the access control list (ACL) of that user. The main jobmon process
that runs the job is started as the local system account (AUTHORITY\SYSTEM),
but it immediately impersonates the <TWS_user> that owns the fault-tolerant
agent. This means that for jobmon to successfully launch the job, the <TWS_user>
must have an access control entry (ACE) in the ACL of the user for which it is
trying to retrieve information.
To resolve this issue, perform one of the following actions:

Enable the <TWS_user> to access a set of users that run jobs
On the domain server, edit the ACL of all users that run jobs on the
workstation and add an ACE for the <TWS_user> for each. In this case,
only the specified users can run the jobs submitted by jobmon.
Allow all users to run jobs submitted by jobmon by using the
TWS_BYPASS_DC=TRUE system variable
Create the TWS_BYPASS_DC=TRUE system variable, with a value not null,
and reboot the workstation. In this case, jobmon obtains the user
information without performing the security check for the ACE in the ACL
of the user. All the local and the domain users can run the jobs submitted
by jobmon.
Allow all users to run jobs submitted by jobmon setting the <TWS_user> as a
domain user
Set up the <TWS_user> as a Windows domain user and install the instance
of Tivoli Workload Scheduler using the <TWS_user>. In this case, all
authenticated users on the domain controller can access the default ACL
for a domain user. Jobs can then be launched by the local or the domain
users. All the local and the domain users can run the jobs submitted by
jobmon.
Exclude the workstation from the security check on users ACL
On the domain server, add the host name of the workstation where the
fault-tolerant agent is installed to the Pre-Windows 2000-Compatible Access
Group. In this way from a security point of view, the domain controller
interacts with this workstation as if it was in a Windows domain which
does not support Active Directory. In this case, all the local and the domain
users can run the jobs submitted by jobmon. In addition, the domain
controller does not prevent any local or domain user from running other
processes that are not controlled by Tivoli Workload Scheduler.
Checking environment settings for Windows Vista users

Before you install Tivoli Workload Scheduler on a Windows Vista workstation that
does not belong to a Windows domain, make sure that the workstation name and
the domain name are both registered in uppercase in the Windows environment
settings. When the workstation is not in a Windows domain, the

COMPUTERNAME and USERDOMAIN values are identical, but on Vista the

USERDOMAIN value is sometimes in lowercase even if the COMPUTERNAME is
in uppercase.
To resolve this issue, perform the following actions:

1. Open a DOS command prompt shell.
2. Run the set command to display the Windows environment settings.
3. Check that the USERDOMAIN value is in uppercase. If this is not the case,
follow this workaround to correct it:
4. Run the set command to change the value of COMPUTERNAME to a
temporary host name of your choice:
set /p COMPUTERNAME=MYTEMPHOST
5. Restart the system.
6. Run the set command again as in step 4 replacing the temporary host name
with the original one.
7. Restart the system.
8. Check that the USERDOMAIN value is now in uppercase.
Installation paths and product instances

| Tivoli Workload Scheduler installs files for the <TWS_user> in the directory
| <selected path>\TWS\ and <selected path>\eWAS\, where <selected path> is the
| installation location.
| On Windows operating systems, the default installation location for a new

| installation is c:\Program Files\ibm\TWA\.
| On UNIX operating systems, the default installation location is /opt/ibm/TWA/.
| On Linux operating systems, the product is installed into the directory chosen
| during installation. The default installation location is /opt/ibm/TWA/.
| Each instance of a Tivoli Workload Scheduler component can exist only once in a
| TWA directory. Multiple instances of the product can be installed on a single
| workstation only if a unique <TWS_user> and installation path are used to create a
| separate instance.
| Each instance of Tivoli Workload Automation can contain the following:

| v One instance of the embedded WebSphere Application Server on which can run:
| – One instance of a master domain manager, backup domain manager, domain
| manager with distributed connector, or agent with distributed connector
| – One instance of Tivoli Dynamic Workload Console
| v If no other Tivoli Workload Scheduler component (master domain manager,
| backup domain manager, domain manager with distributed connector, or agent
| with distributed connector) is installed, one instance of a domain manager or
| agent without a distributed connector
| Only one Tivoli Dynamic Workload Console can be installed on a workstation and
| can be installed as follows:
| v In an existing Tivoli Workload Automation instance
| v In a new Tivoli Workload Automation instance

Tivoli Workload Automation information
| v Outside any Tivoli Workload Automation instance, using an existing external

| instance of WebSphere Application Server
| If you install a new Tivoli Workload Scheduler instance onto a computer that has
| an existing TWA directory, a new default installation directory is created as TWA1,
| TWA2, and so on.
| Note: In this and other manuals, the Tivoli Workload Automation instance
| directory is refered to as TWA_home.
| For example, if you have already installed Tivoli Workload Scheduler in the
| /opt/ibm/TWA directory, the next attempt to install Tivoli Workload Scheduler on
| this workstation results in an installation directory of /opt/ibm/TWA1. However,
| if you originally installed Tivoli Dynamic Workload Console into the
| /TWA/TDWC directory, you can install a new instance of Tivoli Workload
| Scheduler in the /opt/ibm/TWA/TWS directory. The same situation applies to
| each product or component in Tivoli Workload Automation: Tivoli Workload
| Scheduler, and Tivoli Dynamic Workload Console. Only one instance of each
| product or component can exist in any instance of a TWA directory.
| Note: Instances of Tivoli Workload Scheduler are recorded only in the registry file.
| Former versions of Tivoli Workload Scheduler were registered both in the
| registry file and in the components file.
Windows services
An installation on Windows operating systems registers the following services with
the Windows Service Control Manager:
v Tivoli Workload Scheduler (for <TWS_user>)
v Tivoli Netman (for <TWS_user>)
v Tivoli Token Service (for <TWS_user>)
v Tivoli Workload Scheduler SSM Agent (for <TWS_user>)
v Autotrace Runtime
v WebSphere Application Server (for <TWS_user>)
Note: An existing service that has the same name as the new service will be
overwritten during installation.
The Service Control Manager maintains its own user password database. If the
<TWS_user> password is changed following installation, you must use the Services
applet in the Control Panel to assign the new password for the Tivoli Token
Service and Tivoli Workload Scheduler (for <TWS_user>). For more information,
see the section on changing the <TWS_user> in Administration Guide.

Part 2. Tivoli Workload Scheduler
This part describes how to install, upgrade, configure, and uninstall Tivoli
Workload Scheduler. It also contains sections on troubleshooting and messages. It
is composed of the following chapters:
v Chapter 3, “Preparing,” on page 23
v Chapter 4, “Installing,” on page 31
v “Upgrading a version 8.2 or 8.2.1 master domain manager instance” on page 55
v “Upgrading a version 8.3 or 8.4 master domain manager instance” on page 90
v “Upgrading agents and domain managers” on page 108
v “Upgrading a command line client” on page 116
v Chapter 6, “Configuring,” on page 117
v Chapter 7, “Uninstalling,” on page 121
v Chapter 8, “Troubleshooting installation, migration, and uninstallation,” on page
125
v Chapter 9, “Installation, uninstallation, and upgrade messages,” on page 175

|
| Chapter 3. Preparing
| This chapter provides a brief overview of an installation and some specific
| environment considerations. It contains the following sections:
| v “Installation overview”
| v “Installation considerations”
| v “Installation media” on page 26
| v “Instances of Tivoli Workload Automation” on page 26
| v “Relational database management systems” on page 27
| v “Installation log files” on page 255
|
| Installation overview
| Perform the following steps to prepare, install, and configure Tivoli Workload
| Scheduler:
| 1. Confirm the configuration of your network to determine what type of
| workstation to install. See Chapter 1, “Network planning,” on page 3.
| 2. Check the installation prerequisites to verify that your system is compliant. You
| can find prerequisite information in the Tivoli Workload Scheduler
| downloadable documentation at http://www.ibm.com/support/
| docview.wss?rs=672&uid=swg24016672.
| 3. Decide if you want to use a DB2 database or an Oracle database.
| 4. Decide if you are installing into an existing instance of Tivoli Workload
| Automation or are installing a new instance of Tivoli Workload Automation.
| 5. Collect the information necessary to fill in the required fields during the
| installation.
| 6. Install Tivoli Workload Scheduler following the instructions provided in
| Chapter 4, “Installing,” on page 31.
| 7. Perform any configuration required for the workstation type you installed. See
| Chapter 6, “Configuring,” on page 117.
|
| Installation considerations
| Before you begin the installation using the installation wizard, consider the
| following items that might apply to your specific environment.
| Installing on Windows
| If you are installing on Windows, consider the following items.
| v If you are using Windows Terminal Services, set the install user with the
| command: change user /install
| v If you are installing a Windows domain user, Microsoft Computer
| Browser Service must be active. This is required for WebSphere
| Application Server authentication.
| Installing on UNIX and Linux
| If you are installing on HP-UX operation systems, check that the
| MAXDSIZ parameter is set to a minimum of 128 MB.

Preparing
| If you get an error message indicating insufficient space for the installation
| wizard temporary data in the default /tmp directory, you can launch the
| installation wizard with the -is flag and set an alternative temporary
| directory. For example: SETUP.sh [-is:tempdir temporary_directory]. For
| additional information about disk and space requirements for the
| installation, refer to Chapter 2, “Prerequisite information,” on page 13.
| Installing with DB2 or installing several computers from a mounted shared
| directory
| The installation DVDs include two types of installation scripts:
| operating_system/SETUP.bin and SETUP.sh.
| Choosing language settings
| If you want to use characters of a specific language locale in the
| installation path field, the language you choose for the installation wizard
| must match the language locale settings of the workstation you are
| installing.
| Installation errors
| If the installation ends with an error, do not use the Close icon on the top
| right to exit the session because this prevents the installation summary log
| file from being created.
| Performing silent installations
| When you install the latest version of Tivoli Workload Scheduler, you can
| create a response file based on the parameters of the initial installation.
| You can then use this customized response file to run silent installations
| using the same parameters. Before running the initial installation, you
| might want to consider this feature. For more information, see “Performing
| a silent installation” on page 44.
| Mapped drives
| When you copy the image of a specific operating system onto the
| workstation for installation using the wizard, you must copy the complete
| DVD contents to the drive from where you run your installation. When the
| drive is a UNC mapped drive, the remote path must be mapped to a drive
| on the installation workstation. For a complete list of the supported
| operating systems and their prerequisites, see the Tivoli Dynamic
| Workload Console System Requirements Document at
| http://www.ibm.com/support/docview.wss?rs=672&uid=swg27012176.
| Remote installation
| You cannot install Tivoli Workload Scheduler on a Windows workstation
| from a remote Samba-mounted file system.
| Installing for end-to-end scheduling
| If you are installing Tivoli Workload Scheduler on a workstation used as a
| distributed agent for end-to-end scheduling, specify OPCMASTER as the
| name of the master domain manager during the installation process. For
| further information about installing for end-to-end scheduling, refer to
| Tivoli Workload Scheduler Scheduling End-to-end.
| Symlink options
| Several of the installation methods include the symlink options. The link option
| determines the path used to create links to the Tivoli Workload Scheduler utility
| commands. Table 5 on page 25 lists the available options.

Preparing
| Table 5. Symlink options

| Variable Default
| /TWA/TWS/bin/at usr/bin/mat
| /TWA/TWS/bin/batch usr/bin/mbatch
| /TWA/TWS/bin/datecalc usr/bin/datecalc
| /TWA/TWS/bin/jobstdl usr/bin/jobstdl
| /TWA/TWS/bin/maestro usr/bin/maestro
| /TWA/TWS/bin/mdemon usr/bin/mdemon
| /TWA/TWS/bin/morestdl usr/bin/morestdl
| /TWA/TWS/bin/muser usr/bin/muser
| /TWA/TWS/bin/parms usr/bin/parms
|
| Engine coexistence and upgrade notes

| This section contains information about coexistence with older versions and
| upgrade possibilities.
| Coexistence with previous versions

| The current version of the Tivoli Workload Scheduler distributed engine can be
| installed on any workstation containing a prior version, provided that both the
| <TWS_user>, the nm port, and the installation path are different from those of the
| previous versions.
| Upgrading existing versions

| The upgrade of a Tivoli Workload Scheduler network can be performed top-down
| or bottom-up. The advantages and disadvantages of these approaches are
| discussed in Chapter 5, “Upgrading,” on page 55.
| Table 6 shows the versions of Tivoli Workload Scheduler components that can be
| upgraded to the current version:
| Table 6. Upgrade availability for Tivoli Workload Scheduler components
| Recommended fix pack
| Component Version level
| Tivoli Workload Scheduler 8.2 11
| engine (master domain
| 8.2.1 3
| manager, backup master
| domain manager, 8.3 5
|| fault-tolerant agent) 8.4 GA
| Connector Upgrade available from version 8.3
|
| v If you are using Tivoli Workload Scheduler components at a lower fix pack level,
| install the fix pack at the indicated level, or higher.
| v If you are using Tivoli Workload Scheduler components from a previous version
| not supported in Table 6, consider these options:
| – Replace them with a fresh installation of the latest component
| – Upgrade them as follows:
| 1. Upgrade them to one of the supported upgrade platforms, using the
| upgrade programs and procedures documented for that platform.
| 2. Apply the necessary fix packs, as shown in Table 6.
Chapter 3. Preparing 25
Preparing
| 3. Upgrade them to the current version.

|
| Installation media
| Tivoli Workload Scheduler is packaged into multiple DVDs, one for each of the
| supported operating systems. Depending on the operating system, the installation
| DVDs contain some or all the following directories:
| TWS Contains the files necessary to install Tivoli Workload Scheduler
| TDWC
| Contains the files necessary to install Tivoli Dynamic Workload Console
| DB2 Contains the files necessary to install DB2
| DB2_activation
| Contains the files necessary for DB2 activation
| Integrations
| Contains the files necessary to integrate Tivoli Workload Scheduler with
| other Tivoli products
| launchpad
| Contains launchpad-specific code
| Integration Workbench
| Contains the files necessary to install Tivoli Workload Scheduler
| Integration Workbench
| For a complete list of DVDs and supported operating systems, see the Tivoli
| Workload Scheduler downloadable documentation.
|
| Instances of Tivoli Workload Automation
| During the installation of Tivoli Workload Scheduler decide if you want to install
| into an existing instance of Tivoli Workload Automation or to create a new
| instance. For information see, “Installation paths and product instances” on page
| 18.
| If you are installing into an existing instance of Tivoli Workload Automation, you
| can install certain products or components, depending on the products or
| components that currently exist in that instance. Table 7 describes the actions that
| you can perform in each different scenario.
| Table 7. Installing into an existing instance of Tivoli Workload Automation
| If the existing Tivoli Workload Automation
| instance contains: You can perform the following:
| A previous version of a Tivoli Workload Upgrade that component.
| Scheduler component
| A Tivoli Workload Scheduler version 8.5 Take no action. It is not possible to install
| backup master or master domain manager Tivoli Workload Scheduler in this case.
| A Tivoli Workload Scheduler version 8.5 Add the connector feature.
| agent (with no connector)
| agent with connector Tivoli Workload Scheduler in this case.
| non-integratable agent Tivoli Workload Scheduler in this case.

Preparing
| Table 7. Installing into an existing instance of Tivoli Workload Automation (continued)

| Tivoli Dynamic Workload Console version Install a Tivoli Workload Scheduler
| 8.5 component on a common embedded
| WebSphere Application Server.
| Tivoli Dynamic Workload Console version Take no action. It is not possible to install
| 8.5 on an existing external WebSphere Tivoli Workload Scheduler in this case.
| Application Server
| A current version of the command line client Add a language pack feature.
|
| Note: The advantage of installing a product or component into an existing instance

| of Tivoli Workload Automation is that all of the data that is required to
| configure the component is already present and displayed in the wizard. In
| some cases, data from the existing instance is reused automatically. In other
| cases, data is retrieved as default values that you can choose to use or edit.
|
| Relational database management systems
| A relational database management system (RDBMS) is a prerequisite of the master
| domain manager and backup master. The RDBMS can be one of the following:
| DB2 Enterprise Server Edition
| A version of DB2 is bundled with the installation DVD. For information
| about the launchpad, see “Selecting your installation method” on page 13.
| You can install DB2 in the following ways:
| Server Install DB2 Server and the master domain manager on the same
| workstation.
| Client Install DB2 Server on one workstation. DB2 client and the master
| domain manager on a different workstation. The advantage of this
| configuration is that you can easily switch between your master
| domain manager and your backup master if necessary.
| Oracle
| Install Oracle and the master domain manager on the same computer. You
| can install Oracle in the following ways:
| Oracle Enterprise Edition
| The advantage of choosing Oracle Enterprise Edition is that you
| can implement the Oracle Partitioning feature to improve the
| performance of event-driven workload automation. This will
| improve rule management performance, in particular the following
| queries: event_rule_instance, action_run and operator_messages.
| For information about event-driven workload automation, see
| Overview.
| Oracle Standard Edition
| Oracle Standard Edition does not include the Oracle Partitioning
| feature. Installing this edition does not improve the performance of
| event-driven workload automation.
| For supported versions, see the Tivoli Workload Scheduler System Requirements
| Document at http://www.ibm.com/support/docview.wss?rs=672
| &uid=swg27012175.
Preparing
| You must install the RDBMS prior to installing Tivoli Workload Scheduler. During
| the installation of Tivoli Workload Scheduler, identify the instance of the RDBMS
| you want to use.
| Note: If you already have an RDBMS and want to upgrade it, you must upgrade it
| after you upgrade Tivoli Workload Scheduler. For information about
| upgrading the RDBMS, refer to the data maintenance chapter in the Tivoli
|
| Installation log files
| The type of log files you find on your system depends on the type of installation
| you performed. This section describes the logs associated with the different
| installations.
| For more information about log files, refer to the Administration Guide.
| InstallShield wizard installation and uninstallation log files

| You can check the following log files for information about the installation. Details
| of the installation process are kept in log files on the local workstation in the
| following directories:
| Tivoli Workload Scheduler
| UNIX: /tmp/TWA/tws85
| Windows: c:\Documents and Settings\installing_user\Local
| Settings\Temp\TWA\tws85
| Table 8 lists the InstallShield wizard log files.

| Table 8. Installation log files
| Log file name Content
| twsismp.log Tivoli Workload Scheduler installation trace file
| summary.log Tivoli Workload Scheduler installation log file
|
| For multiple installations on the same workstation, the log header and footer
| indicate the user ID (<TWS_user>) for which the installation was performed.
| Note: If you are running a silent installation and the response file you are using
| does not have the correct syntax, the installation fails without producing a
| log file.
| TWSINST log files

| The twsinst log file is as follows:
| <tempDir>/TWA/tws85/twsinst_<operating_system>_<TWS_user>^8.5.0.00.log,
| where:
| <tempDir>
| The user temporary directory:
| UNIX /tmp
| Windows The default value is: %TEMP%\TWA\tws85

Installation log files location
| <operating_system>
| The operating system.
| <TWS_user>
| The name of the user for which Tivoli Workload Scheduler was installed
| (the name you supplied during installation)
| Software package block log files

| The IBM Tivoli Configuration Manager software package blocks log files are as
| follows:
| v <tempDir>/TWA/tws85/FP_TWS_<operating_system>_<TWS_user>^8.5.0.00.log
| (agent SPB log file)
| v <tempDir>/TWA/tws85/TWS_LP_<TWS_user>^8.5.0.00.log (agent NLS SPB log file)
| where:
| <tempDir>
| The user temporary directory:
| UNIX /tmp
| Windows The default value is: %TEMP%\TWA\tws85
| <operating_system>
| The operating system.
| <TWS_user>
| The name of the user for which Tivoli Workload Scheduler was installed
| (the name you supplied during installation)
| WebSphere Application Server installation log files

| The application server installation has no log. However, if you update the
| application server, for example during the application of a Tivoli Workload
| Scheduler fix pack, a log is created which gives information about the update. The
| log can be found in the directory <TWS_home>/eWAS/logs/update, where you will
| find a directory that identifies the fix pack that has been installed, for example:
| 6.0.2-WS-WASEmbeded-AixPPC32-FP0000007.install, which contains a log file called
| /updatelog.txt.
| The log for the startup of the application server can be found at:
| <TWS_home>/eWAS/profiles/twaprofile/logs/SERVERNAME/startServer.log
| where SERVERNAME is:

| v twaserver in the first instance of Tivoli Workload Automation
| v twaserver1, twaserver2... for subsequent instances of Tivoli Workload Automation
| Note: In the case of an upgrade, SERVERNAME is the name of the previous

| server, for example server1.
| DB2 installation log files

| For information about DB2 installation log files, see the DB2 documentation.
Chapter 4. Installing
This chapter describes how to perform a first-time installation of the current
version of Tivoli Workload Scheduler. It contains the following sections:
v “Using the installation wizard”
v “Performing a silent installation” on page 44
v “Installing non-integratable agents using twsinst” on page 48
v “Installing agents using Software Distribution” on page 50
Installing DB2
For detailed information about DB2, see the DB2 documentation at
http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp.
To install DB2, you can choose one of the following options:

v Use the launchpad. See “Launchpad” on page 13.
v Manually launch the DB2 server installation on the product DVD. The setup files
for DB2 are on the product DVDs as follows:
Table 9. DB2 Setup files
Operating System Setup file
®
AIX , HP-UX/IA64, SunOS/SPARC, DB2/server/db2setup
SunOS/SPARC64, all Linux operating
systems
SunOS/AMD64 DB2/ese/db2setup
Windows/x86 and windows/AMD64 DB2\\SERVER\\setup.exe
| Using the installation wizard

| This section describes how to install Tivoli Workload Scheduler components using
| the installation wizard. The installation wizard runs on all supported operating
| systems. Refer to http://www.ibm.com/support/docview.wss?rs=672
| &uid=swg27012175 for a complete list of supported operating systems.
| Installing a new master domain manager or backup master

| For a graphical installation, from the installation DVD, start the launchpad as
| described in “Launchpad” on page 13 and select the Tivoli Workload Scheduler
| installation.
| Or, run the setup for the operating system on which you are installing. From the
| TWS directory on the DVD, perform the following:
| v On Windows: WINDOWS\SETUP.exe or SETUP.cmd
| v On UNIX and Linux: SETUP.sh or operating_system/SETUP.bin.
| Notes:
| 1. If you want to automatically create a custom response file to run silent
| installations, see “Performing a silent installation” on page 44.

Installing using the installation wizard
| 2. At the end of the installation, a summary screen appears and you are unable to
| click Back to return to the previous wizard screens.
| 3. Your RDBMS must be running when you install Tivoli Workload Scheduler.
| There are three basic installation steps for the master domain or backup master
| installation process. Follow each of the procedures as follows:
| 1. “Tivoli Workload Scheduler steps”
| 2. “WebSphere Application Server steps” on page 34
| 3. “RDBMS steps” on page 35
| This section is divided into subsections. Refer to the section that corresponds to
| the RDBMS you are using.
| v “Installing for a DB2 database server” on page 35
| v “Installing for a DB2 database client” on page 36
| v “Installing for an Oracle database” on page 38
| Tivoli Workload Scheduler steps

| Complete the following Tivoli Workload Scheduler data fields.
| User name
| Specify the Tivoli Workload Scheduler user name. User name can contain
| alphanumeric, dash (-), and underscore (_) characters. The first character of
| the user name must be a letter.
| v On Windows systems, if this user account does not already exist, it is
| automatically created by the installation wizard. If installing on a
| Windows server in a domain, do not define a domain and local ID with
| the same user_name. If you specify a domain user, define the name as
| domain_name\user_name. If you specify a local user, define the name as
| system_name\user_name. Type and confirm the password.
| v On UNIX and Linux operating systems, this user account must be
| created manually before running the installation. Create a user with a
| home directory and group. By default, Tivoli Workload Scheduler is
| installed in TWA_home.
| Note: If you are installing into a new instance of Tivoli Workload

| Automation, the Tivoli Workload Scheduler user name and
| password are also used as the WebSphere Application Server
| administrator user name and password.
| Password
| Specify the Tivoli Workload Scheduler password. The password must
| comply with the password policy in your Local Security Settings. Spaces
| are not permitted.
| Password for FTAs on Windows
| Password for users on Windows FTAs may include alphanumeric,
| dash (-), and underscore (_) characters, and ()!?=^*/~ [] $`+;:.,@.
| Password for master, backup master, FTAs, other platforms
| Password for users on platform independent masters, backup
| masters, and non-Windows FTAs may include any alphanumeric,
| dash (-), underscore (_) characters, and ()!?=*~+..
| Company
| The name of the company. Spaces are allowed and the maximum field
| length is 40 characters.

| This workstation name

| The name of the workstation where you are installing the instance. The
| default is the hostname of the workstation. The name you specify here is
| the name of the Tivoli Workload Scheduler workstation as it will be known
| in the database. Spaces are not allowed and the maximum field length is
| 16 characters. It can contain alphanumeric, dash (-), and underscore (_)
| characters. The first character must be a letter.
| Master domain manager name
| The name of the master domain manager workstation. This field is
| required if you are installing a backup manager. If you are not installing a
| backup manager, this field is greyed out. Spaces are not allowed and the
| maximum field length is 16 characters. The first character cannot be
| numeric.
| TCP/IP port number
| The TCP/IP port number used by the netman process. The default value is
| 31111. The valid range is from 0 to 65535.
| Note: If you change this value, all default port number values in the
| application server port information panel are changed to reflect the
| new range. For example, if you specify 42111 as TCP/IP Port
| Number, the default for HTTP transport becomes 42125, the default
| for HTTPS becomes 42126, and so on.
| v Add the default job stream "FINAL" to add the final job stream to the
| database. This option allows the automatic production plan extension at
| the end of each current production plan processing. By default, this box
| remains unchecked. This option is available only if you are installing a
| master domain manager.
| Note: During the installation, if you have identified an existing Tivoli

| Workload Scheduler database that has a final job stream, the
| installation will NOT overwrite it.
| v Automatically generate all the other Tivoli Workload Scheduler ports
| If you check this box, all the ports needed by WebSphere Application
| Server are automatically generated using the default values and the
| application server port information panel is not displayed. The
| installation procedure checks for the availability of the ports in the
| specified port range. If one or more ports are in use by other
| applications, you are prompted to enter a new port number. By default,
| this box is checked.
| If you have not requested to generate ports automatically, specify the
| values for the ports used by the application server embedded in the Tivoli
| Workload Scheduler instance. Accept the default values unless you know
| that they are already in use by other applications.
| Installation directory
| Enter the name of the directory where the Tivoli Workload Scheduler
| instance will be installed for the specified user. On UNIX and Linux
| systems, the default directory is the user home directory. On Windows
| systems, the default directory is C:\Program Files\ibm\TWA. On UNIX and
| Linux systems, optionally check Create symbolic links to create links in
| the /usr/bin directory. Any existing Tivoli Workload Scheduler symbolic
| links are overwritten. The maximum field length is 46 characters and the
| name must not contain numbers. Parentheses () are not allowed.
Chapter 4. Installing 33
| Spaces are allowed however, Tivoli Workload Scheduler for Applications

| version 8.2.1 or earlier cannot be installed on the current version of Tivoli
| Workload Scheduler if the directory path contains spaces.
| On Windows, the name must be longer than three characters, the second
| character must be :, and the third character must be \..
| On UNIX and Linux, the name must be longer than one character and the
| first character must be /.
| WebSphere Application Server steps

| The following fields are provided for WebSphere Application Server data. The
| fields you complete depend upon whether you are installing into a new instance of
| Tivoli Workload Automation or an existing instance.
| The installation procedure checks for the availability of the ports in the specified
| port range. If one or more ports are in use by other applications, you are prompted
| to enter a new port number.
| New instance
| If you are installing into a new instance of Tivoli Workload Automation ,
| provide the following information.
| HTTP transport
| The port for the HTTP transport. It is used by the composer
| command line interface when this protocol is selected. The default
| value is 31115.
| HTTPS transport
| The port for the secure HTTP transport. It is used by the composer
| command line interface when this protocol is selected. The default
| value is 31116.
| Bootstrap
| The port for the bootstrap or RMI. It is used by the graphical user
| interfaces. The default value is 31117.
| SOAP connector
| The port for the application server protocol SOAP connector. The
| default value is 31118.
| SAS Server Authentication Listener
| The port used by the Secure Association Services (SAS) to listen for
| inbound authentication requests. The default value is 31119.
| CSIV2 Server Authentication Listener
| The port on which the Common Secure Interoperability Version 2
| (CSIV2) service listens for inbound server authentication requests.
| The default value is 31120.
| CSIV2 Client Authentication Listener
| (CSIV2) service listens for inbound client authentication requests.
| ORB Listener
| The port used for RMI over IIOP communication. The default
| value is 31122.
| Administration HTTP transport
| The administrative console port. The default value is 31123.

| Administration HTTPS transport

| The administrative console secure port. The default value is 31124.
| Event Processor
| The port used by the event management processor to receive
| events. The default value is 31131. This parameter is not requested
| if you are installing a backup master domain manager.
| Existing instance
| If you are installing into an existing instance of Tivoli Workload
| Automation, you are only required to provide the WebSphere Application
| Server administrator user name and password. The port data is retrieved
| automatically from the existing WebSphere Application Server instance. If
| you do not know the user name, you can click Retrieve on the appropriate
| panel to populate this field, although you must still provide the password.
| Note that if you click Retrieve, you might have to wait for the field to
| populate.
| RDBMS steps
| This section is divided into subsections. Refer to the section that corresponds to the
| RDBMS you are using.
| v “Installing for a DB2 database server”
| v “Installing for a DB2 database client” on page 36
| v “Installing for an Oracle database” on page 38
| Installing for a DB2 database server: When you are installing for an existing
| database, perform the steps described in “Tivoli Workload Scheduler steps” on
| page 32. The following list describes the fields that you might need to complete
| during the installation.
| DB2 discovery
| Type or Browse for the directory where the existing DB2 instance is
| installed. If you have more than one DB2 instance installed, make sure you
| provide the fully qualified path to the DB2 instance you want. This path
| must identify a tree in the DB2 structure that includes the db2level.exe
| file.
| Instance name
| The name of the DB2 server instance.
| Instance port
| The TCP/IP port number used to communicate with the DB2 instance. The
| default is 50000.
| DB2 server administrator user
| The user name of the administrator of the DB2 server instance. This user
| can also be any user having SYSADM or SYSCTRL authority on the DB2
| server. On UNIX, verify that you are able to switch to this user and that it
| can load the DB2 environment.
| DB2 server administrator password
| The password of the DB2 server administrator user, or of the user with
| SYSADM or SYSCTRL authority. You are asked to confirm the password.
| Database name
| The name of the DB2 database. The maximum length is five characters.
| You can use an existing DB2 database instance if its name does not exceed
| five characters. When you are installing a backup master, this database
| must be the same as the master domain manager database. For information
| about DB2 database names, refer to the DB2 documentation.
| Specify advanced configuration parameters for the IBM Tivoli Workload
| Scheduler database
| Select this option if you want to specify the following advanced
| parameters:
| Tablespace name
| The name of the DB2 instance tablespace. This tablespace is used
| to store scheduling objects and event rules. For information about
| DB2 table spaces, refer to the DB2 documentation.
| Tablespace path
| The relative path of the DB2 table space. The path can be a relative
| or an absolute path. When the table space path is an absolute path,
| the DB2 administrator user must have complete access rights to the
| directory where the table space is installed. See Appendix F, “DB2
| tablespace relative paths,” on page 331.
| The default table space path name is TWS_DATA. The default table space
| temporary directory is TWS_TEMP. For UNIX and Linux operating
| systems, make sure that the DB2 Administrator has write access to the
| directory above the table space directory.
| Tablespace used to store event logs
| Specify the name and path of the DB2 table space where Tivoli Workload
| Scheduler event logs are to be stored. These logs include data about event
| rule instances, triggered actions, and operator messages displayed by Tivoli
| Dynamic Workload Console. Data from the logs can be used to create
| reports. You can view report data using Tivoli Dynamic Workload Console.
| Report tablespace name
| The name of the table space for storing report data. The default
| name is TWS_LOG.
| Report tablespace path
| The path of the table space for storing report data. The default
| path is TWS_LOG. The path can be a relative or an absolute path.
| When the table space path is an absolute path the DB2
| administrator user must have complete access rights to the
| directory where the table space is installed. See Appendix F, “DB2
| tablespace relative paths,” on page 331. Note that the report
| tablespace path cannot be the same as the tablespace path.
| Installing for a DB2 database client: If you are installing a backup master, you
| install a DB2 client that must link to the DB2 server installed on the master domain
| manager.
| When you are installing with an existing database, perform the steps described in
| “Tivoli Workload Scheduler steps” on page 32. The following list describes the
| fields that you might need to complete during the installation.
| DB2 discovery
| Type or Browse for the directory where the existing DB2 instance is
| installed. If you have more than one DB2 instance installed, make sure you
| provide the fully qualified path to the DB2 instance you want. This path
| must identify a tree in the DB2 structure that includes the db2level.exe
| file.

| Remote database server

| The IP address or host name of the workstation where the DB2 server is
| installed.
| Remote database port
| The TCP/IP port number that the remote DB2 server instance uses to
| communicate.
| Identify the user on the remote DB2 server to be used by the installation for
| DB2 administration tasks
| Provide the following data:
| DB2 server administrator user
| The user name of the administrator of the DB2 server instance.
| This user can also be any user having SYSADM or SYSCTRL
| authority on the DB2 server. On UNIX, verify that you are able to
| switch to this user and that it can load the DB2 environment.
| DB2 server administrator password
| The password of the DB2 server administrator user, or of the user
| with SYSADM or SYSCTRL authority. You are asked to confirm the
| password.
| Identify the user on the DB2 client to be used by the installation for
| DB2 administration tasks
| Specify the user on the DB2 client to be used by the installation for
| DB2 administration tasks. Provide the following data:
| DB2 client administrator user
| The user name of the DB2 administrator of the DB2 client
| instance. The user id must contain the following login
| properties:
| -login='true'
| -rlogin='true'
| DB2 client administrator password
| The password of the DB2 administrator of the DB2 client
| instance.
| Note: The password must comply with the password

| policy in your Local Security Settings, otherwise the
| installation fails.
| Identify the user on the DB2 server to be used by Tivoli
| Workload Scheduler to access the database, if different from the
| DB2 Server Administration User
| Select this option when the DB2 server user used to access
| Tivoli Workload Scheduler is different from the DB2 Server
| Administration User. Provide the following data:
| Tivoli Workload Scheduler DB2 user
| The user name of the Tivoli Workload Scheduler
| DB2 user.
| Tivoli Workload Scheduler DB2 password
| The password of the Tivoli Workload Scheduler
| DB2 user.
| Database name
| The name of the DB2 database. The maximum length is five
| characters. You can use an existing DB2 database instance if its
| name does not exceed five characters. When you are installing a
| backup master, this database must be the same as the master
| domain manager database. For information about DB2 database
| names, refer to the DB2 documentation.
| Specify advanced configuration parameters for the IBM Tivoli Workload
| Scheduler database
| Select this option if you want to specify the following advanced
| parameters:
| Tablespace name
| The name of the DB2 instance table space. For information
| about DB2 table spaces, refer to the DB2 documentation.
| Tablespace path
| The relative path of the DB2 table space. The path can be a
| relative or an absolute path. When the table space path is
| an absolute path, the DB2 administrator user must have
| complete access rights to the directory where the table
| space is installed. See Appendix F, “DB2 tablespace relative
| paths,” on page 331.
| The default table space path name is TWS_DATA. The default table
| space temporary directory is TWS_TEMP. For UNIX and Linux
| operating systems, make sure that the DB2 Administrator has write
| access to the directory above the table space directory.
| Tablespace used to store event logs
| Specify the name and path of the DB2 table space where Tivoli
| Workload Scheduler event logs are to be stored. These logs are
| used to create reports. You can view report data using the Tivoli
| Dynamic Workload Console.
| The name of the table space for storing report data. The
| default name is TWS_LOG.
| The path of the table space for storing report data. The
| default path is TWS_LOG. The path can be a relative or an
| absolute path. When the table space path is an absolute
| path, the DB2 administrator user must have complete
| access rights to the directory where the table space is
| installed. See Appendix F, “DB2 tablespace relative paths,”
| on page 331.
| Installing for an Oracle database:
| When you are installing for an Oracle database both for server and client, follow
| the installation wizard prompts. The following list describes the fields that you
| might need to complete during the installation.
| Installation path
| Specify the path of an Oracle installation that satisfies the Tivoli Workload
| Scheduler prerequisites. The fully-qualified path must identify a tree in the
| Oracle structure that includes the sqlplus executable.
| Net service name
| The name used by clients to identify an Oracle Net server and the specific
| system identifier or database for the Oracle Net connection. A net service
| name is mapped to a port number and protocol. It is also known as a

| connect string, database alias, host string, or service name.
| If your Oracle database is installed on the same system where you are
| installing your master domain manager or a backup master, the net service
| name is the name of your Oracle database.
| If your Oracle database is not installed on the system where you are
| installing your master domain manager or a backup master, the net service
| name is the alias configured for the connection to the remote database.
| Contact your database administrator to obtain the correct net service name.
| Oracle administrator user
| The database administrator user name (such as SYSTEM) required to
| authenticate to the Oracle database. This account must already exist.
| Oracle administrator user password
| The database administrator user password required to authenticate to the
| Oracle database.
| Tivoli Workload Scheduler Oracle user
| The owner of the Tivoli Workload Scheduler schema. The name must
| comply with the Oracle naming rules.
| If you are installing a master domain manager and you leave this field
| blank, this name is defaulted to <TWS_user>. If you are installing a backup
| master, you are required to enter the same name that is used in the master
| domain manager.
| On a fresh installation of a master domain manager this user does not exist
| in the database. If this is not the case, it means that there already is a
| master domain manager or a backup master instance pointing to the same
| database with this user name. If your existing Tivoli Workload Scheduler
| instance is version 8.3 or 8.4, the installation process upgrades the current
| database schema to the new schema.
| If your existing instance is the current version, the installation process
| assumes that the schema is at the right level and does not create the
| database objects (tables, views, clusters, procedures, indexes, and so on) for
| Tivoli Workload Scheduler.
| Tivoli Workload Scheduler Oracle user password
| The password for the Tivoli Workload Scheduler Oracle user. It must
| comply with the Oracle naming rules.
| Create the Tivoli Workload Scheduler schema using the Oracle Partitioning
| option If you are installing on Oracle Enterprise Edition, you can choose to
| implement the Oracle Partitioning option to improve the performance of
| event-driven workload automation. For information about event-driven
| workload automation, see Overview.
| Tivoli Workload Scheduler data tablespace
| The name that identifies the Tivoli Workload Scheduler data table space.
| This table space must have been previously created by the database
| administrator. The default for this field is USERS.
| Tivoli Workload Scheduler reports tablespace
| The name that identifies the Tivoli Workload Scheduler table space where
| report data is to be stored. You can view the report data using the Tivoli
| This table space must have been previously created by the database
| administrator. The default value for this field is USERS.
| Tivoli Workload Scheduler temporary tablespace
| The name that identifies the Tivoli Workload Scheduler temporary table
| space. This table space must have been previously created by the database
| administrator. The default value for this field is TEMP.
| Installing a new agent or domain manager

| For a graphical installation, from the installation DVD, start the launchpad as
| installation.
| TWS directory on the DVD, peform the following:
| Follow the installation wizard screens to complete the installation. The following
| list describes the fields that you might need to complete during the installation.
| To install a new agent or domain manager, perform the following steps:
| Note: At the end of the installation, a summary screen appears and you are unable
| to click Back to return to the previous wizard screens.
| User name and password
| Specify the Tivoli Workload Scheduler user name and password. Spaces are
| not permitted.
| v On Windows systems, if this user account does not already exist, it is
| automatically created by the installation wizard. If you specify a domain
| user specify the name as domain_name\user_name. If you are installing in
| a domain controller the user name must always be domain_name\
| user_name. If you specify a local user with the same name as a domain
| user, the local user must first be created manually by an administrator
| and then specified as system_name\user_name. Type and confirm the
| password.
| Note: The password must comply with the password policy in your
| Local Security Settings, otherwise the installation fails.
| v On UNIX and Linux operating systems, this user account must be
| created manually before running the installation. Create a user with a
| home directory. By default, Tivoli Workload Scheduler is installed under
| the HOME directory of the selected user.
| Note: If you are installing an agent in an instance of Tivoli Workload

| Automation where the Tivoli Dynamic Workload Console is already
| installed, and you intend later to add the Connector feature to the
| agent, you are strongly advised to use, as the <TWS_user> of the
| agent, the same user as you used as the WebSphere Application
| Server administration user when you installed the Tivoli Dynamic
| Workload Console. It will make the WebSphere Application Server
| administration easier to perform if the names are the same (this is

| the default situation if you install a Tivoli Workload Scheduler

| component that uses WebSphere Application Server before the Tivoli
| Dynamic Workload Console).
| Company
| The name of the company.
| This workstation name
| The name of the workstation where you are installing the instance. The
| default is the hostname of the workstation. The name you specify here is
| the name of the Tivoli Workload Scheduler workstation as it will be known
| in the database.
| Master domain manager name
| The name of the master domain manager to which the workstation
| belongs.
| TCP/IP port number
| The TCP/IP Port Number. The default value is 31111.
| Installing a command line client

| The command line client is a component of Tivoli Workload Scheduler that
| implements many of the commands used on the master domain manager. It can be
| installed on any workstation that satisfies its prerequisites, including workstations
| where no other Tivoli Workload Scheduler components are installed. It
| communicates by TCP/IP with the command line server, which is part of the
| master domain manager. Install the command line client using the installation
| wizard or in silent mode.
| The information required to make the connection with the master domain manager
| must be defined either in the local options file or supplied as parameters to the
| command.
| The commands you can use are the following:

| v Composer
| v Optman
| v Planman showinfo and unlock (the other planman commands must be run
| locally on the master domain manager)
| Note: The command line client is different from and independent from the ability
| to use conman locally on an agent to manage the local Symphony file and
| local jobs.
| Running the interactive installation

| To install a command line client on an existing installation, perform the following
| steps:
| 1. For a graphical installation, from the installation DVD, start the launchpad as
| installation.
| Or, run the setup for the operating system on which you are installing. From
| the TWS directory on the DVD, peform the following:
| 2. Follow the installation wizard screens to complete the installation. The
| following list describes the fields that you might need to complete during the
| installation.
| Remote Host
| The TCP/IP address or host name of the workstation where the Tivoli
| Workload Scheduler engine is installed.
| Remote Port
| The HTTP or HTTPS port number used to connect to the workstation
| where the master domain manager is installed. This port number must
| match the values defined for the master domain manager.
| User Name
| The user name used to connect to the workstation where the master
| domain manager is installed. This user should be a valid user listed in
| the security file on the master domain manager.
| Password
| The password used to connect to the workstation where the master
| domain manager is installed.
| Adding a new feature

| To add a new feature, from the installation DVD, start the launchpad as described
| in “Launchpad” on page 13 and select the Tivoli Workload Scheduler installation.
| TWS directory on the DVD, peform the following:
| Alternatively, start the launchpad as described in “Launchpad” on page 13.
| In the installation wizard, choose to work with the existing Tivoli Workload
| Automation instance.
| Table 10. Optional installable features and components
| Feature Description
| Tivoli Workload Scheduler The Job Scheduling Console communicates with the
| connector Tivoli Workload Scheduler system through the
| connector. It translates instructions entered through the
| console into scheduler commands.
| Language Packs for the The English language pack and the language locale of
| command-line client the operating system are installed by default. You can
| also install any of the supported languages.
|
| Adding a connector
| To add a connector instance to an existing installation, perform the following steps:
| 1. For a graphical installation, from the installation DVD, start the launchpad as
| installation.
| Or, run the setup for the operating system on which you are installing. From
| the TWS directory on the DVD, peform the following:
| installation.

| Add a New Feature

| Select the agent on which you want to add the connector. Add
| connector is displayed.
| TWSuser password
| The password of the <TWS_user>.
| Note: If the <TWS_user> of the agent on which you are adding the
| Connector is different from the WebSphere Application Server
| administration user you used when you installed the Tivoli
| Dynamic Workload Console, you should make a note to pay
| especial attention when performing administration activities on
| WebSphere Application Server to always use the WebSphere
| Application Server administration user's credentials, not the
| credentials of the <TWS_user>. You should also note that in these
| circumstances you might experience a small problem during the
| uninstallation of the Connector (see “The uninstallation of the
| Connector fails in the "Start the embedded WebSphere
| Application server" step” on page 163).
| HTTP transport
| The port for the HTTP transport. The default value is 31115.
| HTTPS transport
| The port for the secure HTTP transport. The default value is 31116.
| Bootstrap
| The port for the bootstrap or RMI. The default value is 31117.
| SOAP connector
| (CSIV2) service listens for inbound server authentication requests. The
| (CSIV2) service listens for inbound client authentication requests. The
| ORB Listener
| The port used for RMI over IIOP communication. The default value is
| 31122.
| Note: The installation procedure checks for the availability of the ports in the
| specified port range. If one or more ports are in use by other applications,
| you are prompted to enter a new port number.
| Adding language packs to a command line client

| To add language packs to a command line client, perform the following steps:
| 1. From the installation DVD, run the setup for the operating system on which
| you are installing:
| v On Windows, WINDOWS\SETUP.exe
| v On UNIX and Linux, SETUP.bin
| 2. Select the installation wizard language. Click OK.
| 3. Read the welcome information. Click Next.
| 4. Read and accept the license agreement. Click Next.
| 5. From the drop-down list, select an existing command line client. Existing
| installations are identified by the installation path. Note that the option Add
| langPack is automatically selected.
| 6. Select the additional languages to install. Click Next.
| 7. Review the installation settings. Click Next.
| 8. When the installation completes, a panel displays a successful installation or
| indicates the location of the log file if the installation was unsuccessful. Click
| Finish.
| Performing a silent installation

| A silent installation runs according to parameters set in a response file. The
| response file includes all the installation information required to run the
| installation without user intervention.
| There are two ways to customize a response file to satisfy your installation
| requirements:
| v Edit an existing response file template provided on the installation DVDs. See
| “Silent installation using response file templates.”
| v Automatically create a customized response file by running the installation
| wizard. See “Silent installation using an automatically generated response file”
| on page 47.
| Silent installation using response file templates

| Edit the response file templates provided on the installation DVDs in the
| \tws\responsefiles\ directory. Instructions for customizing the files are included
| in the files as commented text. For details about response file properties, see
| Appendix B, “Response file properties,” on page 311.
| Table 11 lists the response files and the types of installation each performs by
| platform:
| Table 11. Response files
| Type of installation Response file to use
| Installing on UNIX
| Command line client with language TWS85_CLI_LP_UNIX.txt
| packs
| Command line client (no language TWS85_CLI_UNIX.txt
| packs installed)
| Fresh agent on existing TWA instance TWS85_FRESH_Agent_existTWA_UNIX.txt
| Fresh agent on new TWA instance TWS85_FRESH_Agent_newTWA_UNIX.txt

| Table 11. Response files (continued)

| Fresh backup master domain manager TWS85_FRESH_BACKUP_MDM_existTWA_UNIX.txt
| on existing TWA instance
| Fresh backup master domain manager TWS85_FRESH_BACKUP_MDM_newTWA_UNIX.txt
| on new TWA instance
| Fresh connector with no Tivoli Dynamic TWS85_FRESH_Conn_NO_TDWC_UNIX.txt
| Workload Console installed
| Fresh connector on Tivoli Dynamic TWS85_FRESH_Conn_ON_TDWC_UNIX.txt
| Workload Console
| Fresh master domain manager on TWS85_FRESH_MDM_existTWA_UNIX.txt
| existing TWA instance
| Fresh master domain manager on new TWS85_FRESH_MDM_newTWA_UNIX.txt
| TWA instance
| SDK TWS85_SDK_UNIX.txt
| Uninstall an agent TWS85_UNINSTALL_Agent.txt
| Upgrade an agent TWS85_UPGRADE_Agent_UNIX.txt
| Upgrade a backup master domain TWS85_UPGRADE_BACKUP_MDM_82_UNIX.txt
| manager from version 8.2
| Upgrade a backup master domain TWS85_UPGRADE_BACKUP_MDM_83plus_UNIX.txt
| manager from version 8.3 and higher
| Upgrade a command line client TWS85_UPGRADE_CLI_UNIX.txt
| Upgrade a connector TWS85_UPGRADE_Connector_UNIX.txt
| Upgrade a master domain manager TWS85_UPGRADE_MDM_82_UNIX.txt
| from version 8.2
| Upgrade a master domain manager TWS85_UPGRADE_MDM_83plus_UNIX.txt
| from version 8.3 and higher
| Command line client with language TWS85_CLI_LP_WIN.txt
| packs
| Command line client (no language TWS85_CLI_WIN.txt
| packs installed)
| Fresh agent on existing TWA instance TWS85_FRESH_Agent_existTWA_WIN.txt
| Fresh agent on new TWA instance TWS85_FRESH_Agent_newTWA_WIN.txt
| Fresh backup master domain manager TWS85_FRESH_BACKUP_MDM_existTWA_WIN.txt
| Fresh backup master domain manager TWS85_FRESH_BACKUP_MDM_newTWA_WIN.txt
| on new TWA instance
| Fresh connector with no Tivoli Dynamic TWS85_FRESH_Conn_NO_TDWC_WIN.txt
| Workload Console installed
| Fresh connector on Tivoli Dynamic TWS85_FRESH_Conn_ON_TDWC_WIN.txt
| Workload Console
| Fresh master domain manager on TWS85_FRESH_MDM_existTWA_WIN.txt
| existing TWA instance
| Fresh master domain manager on new TWS85_FRESH_MDM_newTWA_WIN.txt
| TWA instance
| SDK TWS85_SDK_WIN.txt
| Table 11. Response files (continued)

| Uninstall an agent TWS85_UNINSTALL_Agent.txt
| Upgrade an agent TWS85_UPGRADE_Agent_WIN.txt
| Upgrade a command line client TWS85_UPGRADE_CLI_WIN.txt
| Upgrade a backup master domain TWS85_UPGRADE_BACKUP_MDM_82_WIN.txt
| manager from version 8.2
| Upgrade a backup master domain TWS85_UPGRADE_BACKUP_MDM_83plus_WIN.txt
| manager from version 8.3 and higher
| Upgrade a command line client TWS85_UPGRADE_CLI_WIN.txt
| Upgrade a connector TWS85_UPGRADE_Connector_WIN.txt
| Upgrade a master domain manager TWS85_UPGRADE_MDM_82_WIN.txt
| from version 8.2
| Upgrade a master domain manager TWS85_UPGRADE_MDM_83plus_WIN.txt
| from version 8.3 and higher
|
| Note: When you are performing a silent installation on UNIX zSeries® systems,
| you must first save the response file in UTF 8 format.
| To perform a silent installation using a response file template, perform the

| following steps:
| 1. Copy the relevant response file to a local directory and edit it to meet the needs
| of your environment.
| Note: Be sure to review the license agreement information included in the

| installation media. To accept the terms of the license agreement, set the
| licenseAccepted parameter to true in the response file you are using.
| This value is required to complete the silent installation successfully.
| 2. Save the file with your changes.
| 3. Enter the following command:
|| Windows SETUP.exe -options <local_dir>\response_file.txt -silent
| where response_file.txt is the name of the response file to be created. The

| SETUP.exe file is located in the WINDOWS directory. See “Installation
| media” on page 26.
| UNIX and ./SETUP.bin -options <local_dir>/response_file.txt -silent
| Linux
| SETUP.sh file is located in the root directory of the relevant installation
| DVD. See “Installation media” on page 26.
|
| 4. Review the installation messages in the summary.log file to check that
| installation was successful.
| 5. At the end of a successful installation, perform one of the following
| configuration tasks, depending on the type of agent you installed:
| v “Configuring a master domain manager” on page 117
| v “Configuring an agent” on page 119.
| Note: If you are installing an agent in an instance of Tivoli Workload Automation

| where the Tivoli Dynamic Workload Console is already installed, and you

| intend later to add the Connector feature to the agent, you are strongly
| advised to use, as the <TWS_user> of the agent, the same user as you used
| as the WebSphere Application Server administration user when you installed
| the Tivoli Dynamic Workload Console. It will make the WebSphere
| Application Server administration easier to perform if the names are the
| same (this is the default situation if you install a Tivoli Workload Scheduler
| component that uses WebSphere Application Server before the Tivoli
| Dynamic Workload Console).
| Silent installation using an automatically generated response

| file
| During the initial installation of the current version of Tivoli Workload Scheduler,
| you can create a response file based on the parameters of the initial installation.
| You use this response file to run subsequent installations with the same
| parameters. Creating an automatically generated response file is recommended
| because all input is automatically validated by the program.
| To perform a silent installation using an automatically generated response file,

| perform the following steps:
| 1. Perform the initial installation using the following command:
|| Windows SETUP.exe -options-record <local_dir>\response_file.txt

| SETUP.exe file is located in the WINDOWS directory. See “Installation
| media” on page 26.
| UNIX and ./SETUP.bin -options-record <local_dir>/response_file.txt
| Linux
| SETUP.sh file is located in the root directory of the relevant installation
| DVD. See “Installation media” on page 26.
|
| The installation wizard is launched. Follow the prompts and complete the
| installation (see “Using the installation wizard” on page 31). A response file is
| created in the directory that you specified in the setup command.
| Although the response file contains the parameters that you entered in the
| installation wizard, be aware that you might need to edit the file for each
| subsequent installation. This depends on the configuration of each workstation.
| Note: The response file that is created will contain unencrypted password
| information.
| 2. For all subsequent installations, enter the following command:
|| Windows SETUP.exe -options <local_dir>\response_file.txt -silent
| UNIX and ./SETUP.bin -options <local_dir>/response_file.txt -silent
| Linux
|
| 3. After each silent installation, review the installation messages in the
| summary.log file to check that installation was successful.
| 4. At the end of a successful installation, perform one of the following
| configuration tasks, depending on the type of agent you installed:
| v “Configuring a master domain manager” on page 117
| v “Configuring an agent” on page 119.
Installing non-integratable agents using twsinst
| Installing non-integratable agents using twsinst

| This section explains the command line method of installing a non-integratable
| agent using the twsinst script. It contains the following subsections:
| v “Non-integratable agents”
| v “Installing a new non-integratable agent”
| Non-integratable agents
| A non-integratable agent is a fully functional agent that can be installed, updated,
| or uninstalled with the twsinst non-Java command-line script. It can be configured
| as a domain manager, but cannot have a connector added to it. It is installed in its
| own path, independent of any other Tivoli Workload Automation products or
| components installed on the same system.
| Installing a new non-integratable agent

| You can use the twsinst script to install non-integratable agents on UNIX and
| Linux.
| Use twsinst to install non-integratable agents only if you do not run a JVM on the
| workstation. If this is not your situation, you might choose to perform a silent
| installation instead. See “Performing a silent installation” on page 44.
| Agents installed using twsinst can only be uninstalled using twsinst. Agents
| installed using twsinst do not support the connector feature.
| Refer to http://www.ibm.com/support/docview.wss?rs=672&uid=swg27012175 for

| a complete list of supported operating systems.
| During the installation process, twsinst creates a file in the /TWA/TWS directory for
| each of the installation steps. If you stop and restart the installation, the installation
| process starts from the installation step where it was stopped.
| To install a non-integratable agent, perform the following steps:

| 1. Insert the DVD for your operating system. See “Installation media” on page 26.
| 2. Create the Tivoli Workload Scheduler user. The software is installed by default
| in the user’s home directory, referred to as /TWA/TWS.
| User: <TWS_user>
| Home: /TWA/TWS (for example: /opt/TWA/TWS)
| 3. Log in as root on the operating system where you want to install.
| 4. Run the twsinst script.
| A successful installation using the twsinst issues the return code RC = 0. A failed
| installation issues the return code RC = 1. In the case of a failed installation, refer
| to Chapter 9, “Installation, uninstallation, and upgrade messages,” on page 175.
| Synopsis:
| Show command usage and version
| twsinst -u | -v
| Install a new instance
| twsinst -new -uname <username>
| [-thiscpu <workstation>]
| [-master <workstation>]

| [-port <port_number>]
| [-company <company_name>]
| [-inst_dir <install_dir>]
| [-lang <lang_id>]
| [-create_link]
| [-skip_usercheck]
| [-reset_perm]
| Parameters:
| -u Displays command usage information and exits.
| -v Displays the command version and exits.
| -new Specifies the type of installation to perform:
| -new A fresh installation of Tivoli Workload Scheduler, version 8.5.
| Installs an agent or master and all supported language packs.
| -uname <username>
| The name of the user for which Tivoli Workload Scheduler is installed,
| updated, or uninstalled. This user name is not to be confused with the user
| performing the installation logged on as root. For a new installation, this
| user account must be created manually before running the installation.
| Create a user with a home directory. Tivoli Workload Scheduler is installed
| by default under the HOME directory of the specified user.
| -thiscpu <workstation>
| The name of the Tivoli Workload Scheduler workstation of this installation.
| The name cannot exceed 16 characters. This name is registered in the
| localopts file. If not specified, the default value is the hostname of the
| workstation.
| master <workstation>
| The workstation name of the master domain manager. This name cannot
| exceed 16 characters and cannot contain spaces. If not specified, the default
| value is MASTER.
| -port <port_number>
| The TCP/IP port number. This number is registered in the localopts file.
| -company <company_name>
| The name of the company. The company name cannot contain blank
| characters. The name appears in program headers and reports. If not
| specified, the default name is COMPANY.
| -inst_dir <install_dir>
| The directory of the Tivoli Workload Scheduler installation. This path
| cannot contain blanks. If not specified, the path is set to the username home
| directory.
| -lang <lang_id>
| The language in which the twsinst messages are displayed. If not
| specified, the system LANG is used. If the related catalog is missing, the
| default C language catalog is used.
| Note: This is the language in which the installation log is recorded, and
| not the language of the installed engine instance. twsinst installs all
| languages as default.
| -create_link
| Create the symlink between /usr/bin/at and <install_dir>/TWS/bin/at.
| See Table 5 on page 25 for more information.
| -skip_usercheck
| Skip the check of the user in the /etc/password file or using the su
| command. Enable this option if the authentication process within your
| organization is not standard, thereby disabling the default authentication
| option.
| -reset_perm
| Reset the permissions of the libatrc library.
| Examples: For example, a sample twsinst script for installing a new

| non-integratable agent workstation:
| ./twsinst -new -uname <TWS_user> -thiscpu phughes -master TWSmdm
| -port 37124 -company IBM
|
Installing agents using Software Distribution
This section describes how to install non-integratable agents using Software
Distribution software package blocks.
Software packages and parameters

Non-integratable agents can be installed distributing a software package block
(SPB), using the Software Distribution component of Tivoli Configuration Manager,
Versions 4.1, 4.2, 4.2.1, 4.2.2, or 4.2.3. You can distribute the SPB, using either the
command line interface or from the Tivoli desktop.
Note: Do not modify the SPB supplied with the product.
An SPB exists for each supported operating system located on the installation disks
under the directory of the operating system. The SPBs are named according to the
operating system: Tivoli_TWS_<operating_system>.SPB. For the packages to be
distributed, they must be imported in software package profiles . The software
package profiles must be named according to the operating system and user:
FP_TWS_<operating_system>_<TWS_user>.8.5.00. Possible values for operating
system are:
v AIX
v HP
v SOLARIS
v WINDOWS
v LINUX_I386
v LINUX_PPC
v LINUX_S390
v SOLARIS_I386
v HPIA64
v LINUX_X86_64
v WINDOWS_X86_64
An SPB also exists to install language packs: Tivoli_TWS_LP.SPB. The software

package profiles must be named according to the user:
Tivoli_TWS_LP_<TWS_user>.8.5.00. The language pack software package block is
located in the root directory of the installation DVD.

Software Distribution installation
Tivoli Workload Scheduler installation parameters are defined as default variables

in the software package. Table 12 is a list of installation parameters.
Table 12. SPB installation parameters
Variable Description
installer Windows operating systems only. The user ID of the
installer of Tivoli Workload Scheduler. The default
value is Administrator.
install_dir Required. The fully qualified path to the location of
the Tivoli Workload Scheduler installation. This path
cannot contain blanks. On Windows workstations, the
path is created if it does not already exist. On UNIX
and Linux operating systems, the path is the same as
the user’s home directory. The default values are:
v Windows: $(system_drive)\win32app1TWS\
<TWS_user>
v UNIX and Linux: opt/TWS/<TWS_user>
tws_user Required. The user name for which Tivoli Workload
Scheduler instance is being installed. On Windows
systems, if this user account does not already exist, it
is automatically created. If you specify a domain user
or domain controller, you must specify the domain in
the domain variable. If you specify a local user with
the same name as a domain user, the local user must
first be created manually by an administrator and then
identified as <system_name>\<user_name>.
On UNIX and Linux operating systems, this user

account must be created manually before running the
installation.
The default value is <user_name>.

domain Optional unless the user is a domain user. Windows
operating systems only. The domain name of the user.
If you specify a domain user, specify the name as
domain_name\<user_name>. The default value is
<computer_name>.
backup_dir Optional. Indicates the location to where the current
installation is copied before it is upgraded. The default
value is <install_dir>_backup_<TWS_user>.
pwd (for Windows only) Required for Windows operating systems when
performing a first time install. The password
associated with the <TWS_user> user name. The SPB
password variable is passed to the pwd variable.
ft_agent Required. This parameter must always be set to true.
company Optional. The company name. This name appears in

program headers and reports. The default value is
COMPANY.
this_cpu Required. The name of the workstation on which you
are performing the installation. The name cannot
exceed 16 characters and cannot contain spaces. The
default value is THIS_CPU.
master_cpu Optional. The name of the master domain manager.
The name cannot exceed 16 characters and cannot
contain spaces. The default is MASTER.
Table 12. SPB installation parameters (continued)

Variable Description
tcp_port Required. The TCP/IP port number used by the
instance being installed. When installing more than
one instance on the same workstation, use different
port numbers for each instance. It must be an
unassigned 16-bit value in the range 1-65535. The
default value is 31111.
fresh_install Required. Indicates if this is a first time install. To
perform a fresh installation, specify true. To perform
an upgrade, specify false. The default value is true.
upgrade Required. Indicates if the install is an upgrade. To
perform an upgrade, specify true. To perform a fresh
installation, specify false. The default value is false.
from_release When you specify upgrade=”true”, you must also
specify from_release indicating the release of the
existing instance. The default value is 8.2 and the
format is 8.x.x.
backup Optional. Indicates a backup. For a fresh install,
specify false. The default value is false.
Notes:
1. fresh_install and upgrade are mutually exclusive.
2. The variables that are not documented here are for debugging purposes only.
See Administration Guide.
Installation procedure
When installing, the installation procedure checks that there is sufficient space for
the Tivoli Workload Scheduler engine to be installed. It does not, however, check
that there is sufficient space for the Configuration Manager backup directory
specified in the swdis.ini file. Before you begin installing, make sure that there is
enough space available in the directory specified in the backup_dir parameter in
the swdis.ini file according to the operating system. Refer to the Tivoli
Configuration Manager documentation for these space requirements.
To perform the installation, complete the following steps:

1. Create a software package profile:
FP_TWS_<operating_system>_<TWS_user>.8.5.00 where operating_system is the
operating system where you are installing and <TWS_user> is the user of the
installation.
2. Import the software package block using the wimpspo command. When you
import the software package block, you must pass the name of the profile to
wimpspo so that the Configuration Manager endpoint catalogs the name
correctly.
3. Install the software package block using the wdinstsp command.
Note that the supplied software packages must be installed as COMMITTED. The
packages cannot be installed as UNDOABLE because the UNDO action does not
rollback the product registry entries.
4. Perform the steps in “Configuring an agent” on page 119.

Note: For complete instructions on performing these tasks, refer to wimpspo and
wdinstsp in the IBM Tivoli Configuration Manager, Reference Manual for
Software Distribution, and the IBM Tivoli Configuration Manager, User’s Guide
for Software Distribution.
Syntax
The following are examples of the settings required to perform a fresh installation
of an agent on Windows and UNIX workstations. See Table 12 on page 51 for a
description of the parameters.
Windows
The following Windows example describes an installation with the user
<TWS_user> and the endpoint Tivoli_TWS_WINDOWS.
wdinstsp -f -uy -D install_dir=″C:\ibm\TWS\twsuser\TWS″ -D
tws_user=″twsuser″ -D password=″twspasswd″ -D
company=″company_name″ -D this_cpu=″CPU_name″ -D
master_cpu=″MTMDM″ -D tcp_port=″33311″ -D domain=″domain_name″
-n ″FP_TWS_WINDOWS_twsuser.8.5.0.00″ ″C:\Output\TWS_VLAST\
WINDOWS\Tivoli_TWS_WINDOWS.SPB″
UNIX The following UNIX example describes an installation with the user
<TWS_user> and the endpoint Tivoli_TWS_LINUX_I386.
wdinstsp -f -uy -D install_dir=/home/twsuser/TWS -D tws_user=twsuser
-D company=company_name -D this_cpu=cpu_name -D
master_cpu=MTMDM -D tcp_port=33311 -D serverName=server1 -n
FP_TWS_WINDOWS_twsuser.8.5.0.00 /mnt/gsa/home/s/l/user1/web/
public/SPB_INSTALL/LINUX_I386/Tivoli_TWS_LINUX_I386.SPB
Installing language packs

You can install language packs using Software Distribution. Locate the
Tivoli_TWS_LP.SPB software package block in the root directory of the DVD, and
then customize the following parameters before you install.
Table 13. List of parameters to install language packs
Default variable Description Required Default value
zh_CN Chinese, Simplified Specify true for the false
languages to install.
it Italian The default value for
all other languages is
ko Korean false.
es Spanish
zh_TW Chinese, Traditional
ja Japanese
pt_BR Brazilian Portuguese
de German
fr French
ALL_LANG All of the above

languages.
Table 13. List of parameters to install language packs (continued)

Default variable Description Required Default value
tws_user The user name for Yes $(user_name)
which the specified
language pack is
being installed.
install_dir The fully qualified Yes $(program_files)
path to which the
specified language
packs are installed.
The following is the syntax required to install all languages:

wdinstsp -D install_dir="Installation Path" -D tws_user="UserName"
[-D zh_C =true ... -D de=true | ALL_LANG=true] Tivoli_TWS_LP.SPB [subscribers...]
The following is the syntax required to install Italian and German language packs:
wdinstsp -D install_dir="Installation Path" -D tws_user="UserName"
[-D it =true | -D de=true] Tivoli_TWS_LP.SPB [subscribers...]

Chapter 5. Upgrading
This chapter describes how to upgrade Tivoli Workload Scheduler. It is divided
into the following sections:
v “Upgrading a version 8.2 or 8.2.1 master domain manager instance”
v “Upgrading a version 8.3 or 8.4 master domain manager instance” on page 90
v “Upgrading backup master domain manager” on page 108
v “Upgrading agents and domain managers” on page 108
Upgrading a version 8.2 or 8.2.1 master domain manager instance

This chapter describes how to upgrade master domain managers and backup
master domain managers from Tivoli Workload Scheduler 8.2 or 8.2.1 to the
current version. If you have components of Tivoli Workload Scheduler that are at
an earlier version than 8.2 you must first upgrade them to version 8.4 before
upgrading to the current version.
The upgrade from version 8.3 or 8.4 to the current version is described in
“Upgrading a version 8.3 or 8.4 master domain manager instance” on page 90.
To upgrade agents from all supported versions, refer to the procedures described
in “Upgrading agents and domain managers” on page 108.
To upgrade a command line client, follow the procedures described in “Upgrading

a command line client” on page 116.
The upgrade is described in the following topics:

v “Upgrading Overview”
v “Preparing the upgrade environment” on page 63
v “New directory structure” on page 63
v “Performing a parallel upgrade” on page 66
v “Performing a direct upgrade” on page 75
v “Data import - problem resolving” on page 84
v “Post-upgrade issues” on page 90
Upgrading Overview
This section provides an overview of the upgrade of an existing instance of Tivoli
Workload Scheduler version 8.2 or 8.2.1 (hereafter called 8.2.x).
The overview is provided under the following topics:

v “Upgrading from the top or from the bottom”
v “Component upgrade procedures” on page 56
Upgrading from the top or from the bottom

The current version of Tivoli Workload Scheduler supports backward compatibility
so you can upgrade your network in either of the following ways:
Top-down
Upgrade the master domain manager and backup master domain manager,
and then progressively upgrade the agents. Many of the new functions
Overview of upgrade
introduced in the current version become available for each agent as it is

upgraded. The disadvantage is that the same level of function is not
available to all agents at the same time.
Bottom-up
Upgrade the agents first, and when all have been upgraded, upgrade the
master domain manager and backup master domain manager. Many of the
new functions introduced in the current version are not available until the
whole network has been upgraded.
| Component upgrade procedures

| The following diagram shows the steps you perform to upgrade your Tivoli
| Workload Scheduler version 8.2.x to 8.5.
| Note: For a high-level overview of the upgrade procedure, see the upgrade section
| of the launchpad.

Overview of upgrade
|
Upgrade MDM
Start with a from V8.2 or V8.2.1
running V8.2 MDM
Do you have
prerequisite No
RDBMS support?
Optionally export
Install RDBMS TMF user data from
Yes support old security file
Upgrade security file

for event processing
Upgrade (new in 8.4)
Direct
type?
Parallel Migrate run number

and old globalopts
file
Run wizard to
install fresh MDM
Stop scheduling
processes
Resolve data
import
discrepancies
Define new MDM as

FTA in old database
MDM upgrade
wizard
Upgrade
type?
Suspend changes to Run wizard to
scheduling objects upgrade MDM
in old system Parallel
Has Jnextday run Direct

since fresh MDM No
Manual Database import was installed?
automatic or
manual? Wait for next
Jnextday to run
Yes
Automatic
Import Mozart data Database is imported Switch manager

directly into new automatically as part from 8.2 MDM to
TWS database of upgrade 8.5 MDM
Rebuild the plan in

the new MDM
Restart scheduling
MDM completely
upgraded to V8.5
|
| Figure 5. Overview of procedure for upgrading from version 8.2.x
|
Chapter 5. Upgrading 57
Overview of upgrade
Master and backup master domain manager upgrade

scenarios
Choose one of these two upgrade scenarios:
v “Parallel upgrade - minimizing the impact on scheduling”
v “Direct upgrade - minimizing the work to be done and the resource usage” on
page 59
Parallel upgrade - minimizing the impact on scheduling

Steps Advantages Disadvantages
1. Install a fresh master domain manager, v Your old v It is a longer

creating a new database. environment is process that
2. Define the new master domain manager operational involves some
as an agent in the old database. throughout the manual
entire upgrade configuration
3. Import the scheduling and configuration
process. activities.
data from the previous version.
v Each step is a
4. Optionally, export TMF user data from
single unit that can
the old security file.
be reversed.
5. Migrate the run number and globalopts
v You can easily
files.
upgrade hardware
6. Complete your security file by merging at the same time
old and new security settings you perform the
7. Complete your migrated environment parallel upgrade.
by solving any data import problems
8. Switch the domain manager to the new
(fresh) master.
9. Optionally, install or upgrade the
backup master.
Deciding where to install the new master domain manager and the relational
database (RDBMS): Both the fresh installation of the master domain manager and
the new relational database can be made on the same computer as the existing
master domain manager or on a new computer. Consider the following points:
v If you choose a new computer for the master domain manager you have the
opportunity to provide a new and better-performing platform. However, to
upgrade the old Tivoli Workload Scheduler database you will need to mount it
as a file system on the new computer, or make a file transfer of the old database
files to the new computer.
v Choosing the same computer for the master domain manager makes the old
database upgrade easier. If you choose to do this, install the new master domain
manager with a different <TWS_user> from the existing instance.
v Installing the relational database on a separate computer from the master
domain manager:
– is good for the overall performance, provided that the link between the
master domain manager and the relational database server computer is high
speed.
– allows you to recover immediately from any failures of the master. You can
switch to your backup master domain manager without any loss of database
data.
The parallel upgrade is described in “Performing a parallel upgrade” on page 66.

Overview of upgrade
Direct upgrade - minimizing the work to be done and the

resource usage
How its done Advantages Disadvantages
1. Unlink the old master domain manager v Quicker and v Scheduling might
2. Upgrade the master domain manager, simpler than the be delayed for
automatically importing the scheduling parallel upgrade. those activities
and configuration data from the v Does not require involving the
previous version. the use of master domain
additional manager
3. If you prefer, the data import can be
performed as a separate step, giving you computer resources
more control over it.
4. Resolve any data import problems
5. Optionally export the Tivoli
Management Framework users
6. Complete your migrated environment
by merging old and new security file
settings.
7. Rebuild the plan to make the upgraded
master domain manager operational.
8. Optionally upgrade the backup master
domain manager.
The direct upgrade is described in “Performing a direct upgrade” on page 75.
Deciding how to upgrade the database

The upgrade of the master domain manager from version 8.2.x not only upgrades
the component, but also imports the version 8.2.x Mozart database into a new
RDBMS, using DB2 or Oracle support. This is the most complex and
time-consuming part of the upgrade.
The main advantage of this new infrastructure is that using an RDBMS avoids data
inconsistencies. Furthermore, you can separate the database onto a different
computer, helping to spread the workload and improving the performance of the
master domain manager. It also enables you to designate a backup master domain
manager that is configured to access the same database. Switching the master
domain manager is now a much quicker process with reduced risk of data loss.
The import of the database can be performed automatically by the upgrade process
or manually after the master domain manager is upgraded. The manual process is
performed object type by object type, giving you maximum control.
Before you upgrade your installation, read the topics in this section. Topics are:
v “Choosing the relational database management system to host the Tivoli
Workload Scheduler database”
v “Understanding the steps in the data import” on page 60
v “Data import scenarios” on page 61
Choosing the relational database management system to host

the Tivoli Workload Scheduler database
The considerations that help you to choose the appropriate RDBMS (DB2 or
Oracle) that will host the new database are the same for an upgraded instance of
Tivoli Workload Scheduler as they are for the installation of a fresh instance.
Choosing your RDBMS
Therefore, read the information in “Relational database management systems” on

page 27 and then return to this point and continue with the next section.
Understanding the steps in the data import

The data import requires the following steps. These steps are performed regardless
of whether you are importing the data manually, or the upgrade wizard is doing
them for you. If you are using the update wizard for a direct upgrade, the
following steps are performed automatically.
Import the configuration files
Your 8.2.x instance has two configuration files that must be migrated:
Run number file
This field contains the run number used by Symphony and is
automatically incremented every time you run Jnextday. It is used
in much the same way in version 8.5, but to preserve continuity
you must import it.
Globalopts file
This contains the global options used by the master domain
manager. In version 8.5 it is replaced by a database table, but the
values must be imported.
Version 8.5 is supplied with the optman miggrunnb and optman miggopts
subcommands that import these files.
Export the object data (not Windows users) from the Mozart database
The object data is extracted from the 8.2.x database using a specially
enhanced version of the 8.2.x composer, called composer821, which is
bundled with the current version. Do not use the original composer
command for the migration. The create subcommand is used to create text
files that contain the object data definitions.
Export the Windows user data from the Mozart database
If you use composer or composer821 to export the Windows users in the
database, they are exported without passwords. This is the normal, secure,
behavior of composer. For this reason, a migration utility, migrutility
get_users, has been provided which extracts the Windows user data with
their passwords (encrypted).
Export the Tivoli Management Framework user data from the Security file
In your version 8.2.x Security file, you might have Tivoli Management
Framework administrators defined (used to assign rights to users who
access the Job Scheduling Console). If you do not have the local user
account names in the current Security file, these must be migrated by a
tool that substitutes each Tivoli Management Framework administrator
with a local user account associated with those users. The users are
exported first using the dumpsec command on the 8.2.x system. Secondly,
the migrfwkuser utility does the account substitution. The output of the
migrfwkuser utility is a security file containing the migrated users and
your existing settings. You must then merge this information with the new
security settings to build your final security file.
Import the object data into the new database
The object and Windows user data in the text files is imported into the
new database using the datamigrate utility. This follows the stricter
validation of the new database and identifies any logical discrepancies that
were caused by the less strict validation in the 8.2.x system. In nearly all
cases the utility is able to modify some aspect of the object and add it to
the new database. A report of the discrepancies is produced so that you
Choosing your RDBMS
can fix the problems. You can choose to accept the way that the tool has
dealt with the problem, or use the facilities of the current version to
modify the object.
For example, when mapping job definitions, if the workstation of the job
does not exist, the job is not created in the database. However, if the
recovery job does not exist, the job is created but a warning is issued.
The datamigrate utility has these options
v To migrate directly from the version 8.2.x database, or from the text files
created by composer821 and migrutility get_users.
v To migrate each object type one-by-one, or to import all object data in
one command.
Notes:
1. If an 8.2.x workstation has the same name of the new master domain
manager, it will not be migrated. All jobs defined on that workstation
will be defined under the master domain manager workstation
2. In the direct upgrade scenario, the workstation definition of the old
master domain manager will be replaced by a new definition of a
master with the same workstation name but with default values. Before
you begin the upgrade you should save the old master domain
manager definition so that you can restore these values to your new
master domain manager.
3. In a parallel upgrade scenario, if the new master domain manager
workstation has the same name of the old master domain manager
workstation, the tool will not migrate the old master domain manager
definition.
4. The data import in a large environment or an environment with slow
network speeds might take hours to complete, whether you do the
import manually or automatically
Import the Tivoli Management Framework user data to the Security file
The makesec command is used to create the final Security file from the file
created by the migrfwkuser utility merged with the new security settings.
Data import scenarios

Given the different options described in the previous sections, there are a number
of data import scenarios, depending on whether you want a parallel or direct
upgrade, and how closely you want to follow and control the activity:
Manually import data for a parallel upgrade
For a parallel upgrade, the manual import can be made in either of these
modes:
Manual import direct from Mozart - scenario PD
If the new and the old instances of Tivoli Workload Scheduler are
on the same computer, or you can mount the file system of the
version 8.2.x instance on the system where the version 8.5 instance
is installed, you can perform the manual import directly from the
old Mozart database to the new RDBMS. To do this the two
workstations must have the same system byte order. Either both
systems must be big-endian, or both systems must be little-endian,
but not one of each.
1. Migrate the configuration files to the new database
Choosing your data import method
2. If you have Tivoli Management Framework users in

version8.2.x, that do not have their local account name in the
Security file, export them to text files.
3. Directly import all the object data into the new database.
4. Complete your security configuration for the new environment.
This procedure is described in “Parallel 3D: Manually importing
the Mozart data directly - scenario P3D” on page 67.
Manual import from an unlinked system - scenario PU
If the new and the old instances of Tivoli Workload Scheduler are
on different computers and you cannot mount the file system of
the previous instance on the new instance, you do the import in
these stages:
1. Migrate the configuration files to the new database by copying
the files from the instance of Tivoli Workload Scheduler 8.2.x to
the version 8.5 instance, and then using the version 8.5
commands to import them into the 8.5 database.
2. Export the object data (not Windows users) from version 8.2.x
into text files
3. Export the version 8.2.x Windows user data into a text file
4. If you have Tivoli Management Framework users in version
8.2.x, export them to text files.
5. Move all the text files to the system where the version 8.5
master domain manager is installed.
6. Import all the object data into the new database from the text
files
7. Complete your security configuration for the new environment.
This procedure is described in “Parallel 3U: Manually importing
the 8.2.x data indirectly from an unlinked system - scenario P3U”
on page 68.
Manually import data for a direct upgrade
If you have chosen the direct upgrade, the upgrade wizard automatically
exports the 8.2.x object data to text files in a directory of your choice. You
can opt to manually import these files rather than to let the wizard do the
automatic import for you.
Note: When you select to import the data manually, the upgraded master
has no master workstation defined in the database and only the
composer command is available.
The procedure is as follows:
1. If you have Tivoli Management Framework users in version 8.2.x,
export them to text files.
2. Directly import all the object data into the new database.
3. Import the Tivoli Management Framework users into the database from
the text files
This procedure is described in “Direct 3: Importing the 8.2.x data manually
(optional)” on page 80.
Automatic import for a direct upgrade
If you are performing a direct upgrade, and you do not want to follow the
import process but want it to run in background, you can select an

automatic import during the upgrade of the existing instance of the master
domain manager. You can check the status of the import after completion.
| Configuring the security file for new functions

| During the upgrade procedure you will need to configure the security file for new
| functions. Configuring the security file requires the following:
| Configuring for event-driven workload automation
| Configuring for event-driven workload automation applies only when
| migrating from version 8.3. You must modify the security file to include
| new security statements for the event management and reporting features.
| If you have specific security settings in your V8.3 environment, these
| settings must be manually merged with the new settings before you build
| the final security file for your current environment. The statements you
| add manually might vary depending on your security settings and on
| whether you have chosen the parallel or direct upgrade scenario, as
| explained in the following sections.
| Setting the default variable table
| Setting variable tables applies to both version 8.3 and 8.4. The upgraded
| security file includes the new default statement for variable tables. A
| variable table is an object that groups together multiple variables. Known
| as global parameters in previous versions, these objects are now called
| variables in version 8.5. Local parameters are managed as before, but the
| PARMS statement in the security file is now ignored. Any global
| parameters that were defined in your previous database have become
| elements of the default variable table, and a security statement for the table
| has been added to the security file. You can choose to customize the user
| permissions to this table (by default, all users have full permission).
| Note: The workload assurance feature is deactivated if a V8.5 master domain

| manager is created by migrating from a previous release. It is active if you
| are performing a fresh installation.
Preparing the upgrade environment

This section describes the tasks you need to consider to prepare the version 8.2.x
environment for an upgrade.
Linux kernel
If you are upgrading in a Linux environment that uses the
LD_ASSUME_KERNEL=2.4.1 environment variable, upgrade to the current
version in a shell that also uses the LD_ASSUME_KERNEL=2.4.1
environment variable.
Ensure your current Tivoli Workload Scheduler installations are in correct state
When you are upgrading your current environment, make sure the
software package is in the COMMIT state (not in the UNDOABLE state). If it is in
the UNDOABLE state, you must accept it to change its state to COMMIT, before
you upgrade to the current version.
| New directory structure

| This section describes the new program directory structure and the new directory
| structure for SSL files.
| Program directory
| The new directory structure applies only to upgrades on the embedded version of
| IBM Websphere Application Server, upgrades via ISMP, and twsinst. Upgrades on
| external instances of WebSphere Application Server are not affected by the new
| structure. It also does not affect the installation via SPB.
| When you upgrade to the current version, a new program directory structure is
| created. During the upgrade process, Tivoli Workload Scheduler is moved from the
| old directory structure and then updated into the new directory structure.
| On Windows operating systems, the default location for the upgrade is c:\Program
| Files\ibm\TWA\TWS\.
| On UNIX and Linux operating systems, the product is installed in the user's home
| directory. The default location for the upgrade is /opt/ibm/TWA/TWS/.
| Note that the WebSphere Application Server located inside the installation
| directory is renamed from appserver to eWAS.
| For example, on Windows, if you originally installed Tivoli Workload Scheduler

| into the directory c:\Program Files\IBM\TWS, you have a directory structure as
| follows:
| c:\Program Files\IBM\TWS\bin
| c:\Program Files\IBM\TWS\config
| c:\Program Files\IBM\TWS\uninstall
| c:\Program Files\IBM\TWS\AppServer
| c:\Program Files\IBM\TWS\wastools
|
| When you upgrade Tivoli Workload Scheduler, the new directory structure is:
| c:\Program Files\IBM\TWA\TWS\bin
| c:\Program Files\IBM\TWA\TWS\config
| c:\Program Files\IBM\TWA\TWS\uninstall
| c:\Program Files\IBM\eWAS
| c:\Program Files\IBM\wastools
|
| On UNIX, if you originally installed Tivoli Workload Scheduler into

| /export/home/TWS, you have a directory structure as follows:
| /export/home/twsuser/bin
| /export/home/twsuser/config
| /export/home/twsuser/_uninstall
| /export/home/twsuser/appserver
| /export/home/twsuser/wastools
|
| /export/home/twsuser/TWS/bin
| /export/home/twsuser/TWS/config
| /export/home/twsuser/TWS/_uninstall
| /export/home/twsuser/eWAS
|
| If you have any custom configurations (for example, custom scripts or backup
| processes) existing in your Tivoli Workload Scheduler structure, you must update
| them so that they work in the new directory structure.

| If you have a FINAL schedule, during the upgrade, it is downloaded during the
| installation. The default FINAL is reused. A backup copy of the schedule is created
| with the name SFinal.extract in the new installation directory.
| Note: On UNIX operating systems, you can create symbolic links to the new
| directory structure until the scheduling environment is updated by
| performing the In -s command from the old installation directory. For
| example:
| In -s bin TWS/bin
| In -s config TWS/config
| For more information about installation paths, see “Installation paths and product
| instances” on page 18.
| Directory for SSL files

| When you upgrade to the current version, a new directory for SSL files is created.
| The following describes the old and new directory structures depending on
| whether you have chosen the default installation path or have customized the
| installation path.
| If you are using the default installation path, the TWSServerTrustFile.jks and
| TWSServerKeyFile.jks files are located as follows. Note that in these cases, the
| values of keyFileName and trustFileName in the security properties are already set
| to default.
| Previous directory structure
| v TWSInstallationPath\AppServer\profiles\twsprofile\etc\
| TWSServerTrustFile.jks
| v TWSInstallationPath\\AppServer\profiles\twsprofile\etc\
| TWSServerKeyFile.jks
| v TWSInstallationPath\eWAS\profiles\twaprofile\etc\
| If you are using a customized installation path, the TWSServerTrustFile.jks and

| TWSServerKeyFile.jks files are located as follows. The old keys are left in their
| original directories but are also copied to the new directory. The location
| parameters of WebSphere Application Server will be set to the default path which
| is ${USER_INSTALL_ROOT}/etc/KEYNAME. Note that the values of keyFileName
| and trustFileName in the security properties are set to the default paths which are
| ${USER_INSTALL_ROOT}/etc/TWSServerKeyFile.jks and ${USER_INSTALL_ROOT}/etc/
| TWSServerTrustFile.jks.
| v CustomzedInstallationPath\TWSServerTrustFile.jks
| v CustomizedInstallationPath\TWSServerKeyFile.jks
| v TWSnstallationPath\eWAS\profiles\twaprofile\etc\
Parallel upgrade from V8.2.x
Performing a parallel upgrade

This section describes how to upgrade your environment using a parallel scenario.
The parallel scenario consists of the following procedures:
v “Parallel 1: Installing a new version 8.5 master domain manager”
v “Parallel 2: Creating a workstation definition for new master domain manager in
old domain”
v Import the version 8.2.x database performing one of the following procedures,
depending on the type of import:
– “Parallel 3D: Manually importing the Mozart data directly - scenario P3D” on
page 67
– “Parallel 3U: Manually importing the 8.2.x data indirectly from an unlinked
system - scenario P3U” on page 68
v “Parallel 4: Optionally exporting Tivoli Management Framework user data from
the security file” on page 71
v “Parallel 5: Preparing the old security file for switching the manager” on page 72
v “Parallel 6: Migrating the run number and global options” on page 73
v “Parallel 7: Data import- resolving problems” on page 73
v “Parallel 8: Switching the master domain manager” on page 73
v “Parallel 9: Building the final security file for the new environment” on page 74
v “Parallel 10: Customizing the optional final job stream” on page 75
v “Parallel 11: Rebuilding the plan” on page 75
| Parallel 1: Installing a new version 8.5 master domain manager

| Install a master domain manager either on the same workstation where the
| existing master domain manager was installed, or on a different one. See
| “Deciding where to install the new master domain manager and the relational
| database (RDBMS)” on page 58 for information about the advantages and
| disadvantages of these options.
| See Chapter 4, “Installing,” on page 31 for instructions on how to do this, bearing

| the following points in mind:
| v If you choose to install the new instance on the same computer, install it with a
| different <TWS_user> from the existing instance.
| v The workstation name of the new master domain manager must be different
| from the workstation name of the old master domain manager.
| v Install your RDBMS before starting the installation of the master domain
| manager.
| v If you have a final schedule in your old environment and want to continue
| using it in the new environment, see “Parallel 8: Switching the master domain
| manager” on page 73.
| Parallel 2: Creating a workstation definition for new master

| domain manager in old domain
| After the installation has completed, use composer in version 8.2.x to create a
| definition for the new master domain manager as a full status agent in the domain
| of the old master domain manager. The new workstation definition must be
| activated by a new plan creation before proceeding with the upgrade.

Parallel upgrade: direct manual data import
| Parallel 3D: Manually importing the Mozart data directly -

| scenario P3D
| If the new and the old instances of the master domain manager are on the same
| system, or you can mount the file system of the old instance on the new instance,
| perform the following procedures:
| Use this procedure to import object data from a previous version into the Tivoli
| Workload Scheduler v8.5 database in a parallel upgrade. When the Tivoli Workload
| Scheduler is on another workstation, you must mount the directory of the version
| 8.2.x environment on the version 8.5 system. To do this the two workstations must
| have the same system byte order. If they do not, you must use the indirect import
| option (see “Parallel 3U: Manually importing the 8.2.x data indirectly from an
| unlinked system - scenario P3U” on page 68).
| To import the data directly, follow these steps:

| 1. On the version 8.5 system, log in as a user that has full access to the database
| of both the old and the new Tivoli Workload Scheduler environments.
| 2. Set the Tivoli Workload Scheduler environment using the tws_env command.
| See the Tivoli Workload Scheduler: User's Guide and Reference for detailed
| information about the command.
| 3. Use the datamigrate command to import the data directly from the existing
| Mozart file.
| This step can be performed object type by object type or in a single command
| for all object types:
| Importing object data directly from Mozart in steps
| The syntax of the command is as follows:
| datamigrate object_type -path TWS_8.2.x_main_dir [-tmppath temp_path]
| where:
| object_type
| Is the type of object you are importing. Possible values are:
| v calendars
| v topology workstations
| v parms
| v prompts
| v resources
| v users
| v jobs
| v job streams
| You must run the command for all the object types indicated.
| TWS_8.2.x_main_dir
| Indicates the root directory of the previous Tivoli Workload
| Scheduler version.
| temp_path
| Is the temporary path where datamigrate stores the files during
| the migration process. The default is <TWS_home>/tmp in UNIX
| systems and <TWS_home>\tmp in Windows systems.
| Importing object data directly from Mozart in a single command
| datamigrate -path TWS_8.2.x_main_dir [-tmppath temp_path]
Parallel upgrade: direct manual data import
| where:
| TWS_8.2.x_main_dir
| Indicates the root directory of the previous Tivoli Workload
| Scheduler version.
| temp_path
| Is the temporary path where datamigrate stores the files during
| the migration process. The default is <TWS_home>/tmp in UNIX
| systems and <TWS_home>\tmp in Windows systems.
| Parallel 3U: Manually importing the 8.2.x data indirectly from an

| unlinked system - scenario P3U
| If the new and the old instances of the master domain manager are not on the
| same system, and you cannot mount the file system of the old instance on the new
| instance, follow these procedures:
| v “P3U-1: Exporting the 8.2.x object data to flat text files”
| v “P3U-2: Exporting the 8.2.x Windows user data to text files” on page 69
| v “P3U-3: Moving the text files to the system where the new master domain
| manager is installed” on page 70
| v “P3U-4: Importing object data from exported data files” on page 70
| P3U-1: Exporting the 8.2.x object data to flat text files: When you are performing
| a parallel upgrade you must first manually export the old data to flat text files and
| then import the flat text files into the new database. This step describes how to
| export the data manually.
| The data export is performed by a special version of the composer command,

| called composer821. The normal 8.2.x version of composer must not be used. The
| composer821 command is located on the appropriate installation DVD according to
| the operating system where the instance of Tivoli Workload Scheduler you are
| upgrading is installed. To export the data using the composer821 command,
| perform the following steps:
| 1. Log in as the <TWS_user>.
| 3. Locate the file on the appropriate installation DVD (see “Installation media” on
| page 26 for details):
| CDn\operating_system\bin\composer821
| 4. Copy the file into the directory where the old version 8.2.x composer is
| installed.
| 5. Assign to composer821 the same rights that the old composer has.
| 6. Use the composer821 create command to export the data. The data you export
| consists of the following:
| v Topology (workstations, workstation classes, and domains)
| v Prompts, calendars, parameters, resources
| v Jobs
| v Job streams
| Note: Users are not migrated with composer create. See “P3U-2: Exporting
| the 8.2.x Windows user data to text files” on page 69 for details.

Parallel upgrade: indirect manual data import
| composer821 create topology_filename from cpu=@

| composer821 create prompts_filename from prompt
| composer821 create calendar_filename from calendar
| composer821 create parms_filename from parms
| composer821 create resources_filename from resources
| composer821 create jobs_filename from jobs=@#@
| composer821 create scheds_filename from sched=@#@
| where:
| topology_filename
| Is the name of the file that is to contain the topology data of the Tivoli
| Workload Scheduler instance you are upgrading (from cpu=@ indicates
| all workstations, workstation classes, and domains).
| prompts_filename
| Is the name of the file that is to contain the prompts of the Tivoli
| Workload Scheduler instance you are upgrading (from prompt
| indicates all prompts).
| calendar_filename
| Is the name of the file that is to contain the calendars of the Tivoli
| Workload Scheduler instance you are upgrading (from calendar
| indicates all calendars).
| parms_filename
| Is the name of the file that is to contain the parameters of the Tivoli
| Workload Scheduler instance you are upgrading (from parms indicates
| all parameters).
| resources_filename
| Is the name of the file that is to contain the resources of the Tivoli
| Workload Scheduler instance you are upgrading (from resources
| indicates all resources).
| jobs_filename
| Is the name of the file that is to contain the jobs of the Tivoli Workload
| Scheduler instance you are upgrading (from jobs=@#@ indicates all
| jobs).
| scheds_filename
| Is the name of the file that is to contain the job streams of the Tivoli
| Workload Scheduler instance you are upgrading (from scheds=@#@
| indicates all schedules).
| The output files are used in the import step.
| P3U-2: Exporting the 8.2.x Windows user data to text files: The composer821
| create option for Windows users exports user details without their passwords. To
| include the Windows user passwords, follow these steps:
| 3. Clean up the Windows user definitions, eliminating users that are no longer
| valid. The Tivoli Workload Scheduler: User's Guide and Reference describes how to
| remove user definitions from the database.
| 4. Locate the migrutility utility command in the following tar file on the
| appropriate installation DVD (see “Installation media” on page 26 for details).
| CDn\operating_system\utilities\migrtool.tar
| 5. Uncompress the file and place it in a directory where you want to save the
| Windows users.
| 6. Use the command as follows:
| migrutility get_users TWS_8.2.x_user_mozart_file users_filename
| where:
| TWS_8.2.x_user_mozart_file
| The complete path to file userdata located in <TWShome>/network/
| userdata.
| users_filename
| A name of your choice for the output file to be created by migrutility.
| It includes the encrypted passwords.
| The migrutility command extracts the Windows users (and their passwords) from
| the Tivoli Workload Scheduler network and stores them in users_filename. You will
| need users_filename to import the Windows users into the RDBMS of Tivoli
| Workload Scheduler version 8.5.
| P3U-3: Moving the text files to the system where the new master domain
| manager is installed: Move all the text files created in “P3U-1: Exporting the 8.2.x
| object data to flat text files” on page 68 and “P3U-2: Exporting the 8.2.x Windows
| user data to text files” on page 69 to any directory in the system where the new
| master domain manager is installed.
| P3U-4: Importing object data from exported data files: To perform this step you
| must have completed “P3U-1: Exporting the 8.2.x object data to flat text files” on
| page 68, “P3U-2: Exporting the 8.2.x Windows user data to text files” on page 69,.
| and “P3U-3: Moving the text files to the system where the new master domain
| manager is installed.”
| Perform these steps:

| 1. On the new system, log in as a user that has access to the exported object data
| files and the new Tivoli Workload Scheduler environment.
| 3. Use the datamigrate command to import the data from the dumped files.
| The syntax and order of the commands to use are:
| datamigrate -topology topology_filename [-tmppath temp_path]
| datamigrate -prompts prompts_filename [-tmppath temp_path]
| datamigrate -calendars calendars_filename [-tmppath temp_path]
| datamigrate -parms parms_filename [-tmppath temp_path]
| datamigrate -resources resources_filename [-tmppath temp_path]
| datamigrate -users users_filename [-tmppath temp_path]
| datamigrate -jobs jobs_filename [-tmppath temp_path]
| datamigrate -scheds scheds_filename [-tmppath temp_path]
| where:
| topology_filename
| Is the name of the topology file created by composer821 in the export
| process.
| prompts_filename
| Is the name of the prompts file created by composer821 in the export
| process.

| calendars_filename
| Is the name of the calendars file created by composer821 in the export
| process.
| parms_filename
| Is the name of the parameters file created by composer821 in the export
| process.
| Is the name of the resources file created by composer821 in the export
| process.
| users_filename
| Is the name of the Windows users file created with the migrutility
| utility in the export process.
| jobs_filename
| Is the name of the jobs file created by composer821 in the export
| process.
| scheds_filename
| Is the name of the job streams file created by composer821 in the
| export process.
| temp_path
| Is the temporary path where datamigrate stores the files during the
| migrate process. The default is <TWS_home>\tmp in Windows systems
| and<TWS_home>/tmp in UNIX systems.
| Parallel 4: Optionally exporting Tivoli Management Framework

| user data from the security file
| If you have customized user security settings based on Tivoli Management
| Framework Administrator IDs rather than user IDs in your security file, you can
| perform the following steps to transfer the current settings to a file which you can
| then import into your new Tivoli Workload Scheduler environment.
| To extract the Tivoli Management Framework users, perform the following steps:
| 2. Set the Tivoli Management Framework environment:
| v On Windows, run setup_env from c:\windows\system32\drivers\etc\Tivoli
| v On UNIX, run setup_env.sh from /etc/Tivoli
| 4. Run the Tivoli Workload Scheduler utility dumpsec to export the user
| information to a flat text file (input_security_file) as follows:
| dumpsec > input_security_file
| where:
| input_security_file
| Is the text file created by the dumpsec command.
| 5. Locate the migrfwkuser utility command in the following tar file on the
| appropriate installation DVD (see “Installation media” on page 26 for details):
| 6. Uncompress the tar file in a directory on the version 8.2.x environment.
| 7. On Windows systems only, run the bash command
| 8. Run setup_env.cmd on Windows or . ./setup_env on UNIX
| 9. Run the migrfwkuser script as follows:
| migrfwkuser -in input_security_file -out output_security_file
| [-cpu workstation] [-hostname local_hostname]
| where:
| Is the file created using the dumpsec command in step 4.
| output_security_file
| Is the security file that is created by the migrfwkuser script.
| workstation
| Is the name of the local workstation where the login data added by the
| tool is defined. If you do not specify a workstation, the data is taken
| from a localopts file if present in the same directory where the
| migrfwkuser script is located. If there is no localopts file, the
| workstation is set to the first 8 characters of the local host name.
| Note: If you do not specify a workstation, the data is taken from a

| localopts file located in the same directory as the migrfwkuser
| script.
| local_hostname
| Is the fully qualified host name of the Tivoli Management Framework
| users to be extracted. Login data for users with this host name or with
| this host name and domain name and the host name valid for all
| computers are extracted. If you do not specify the local host name,
| migrfwkuser retrieves the host name from the local computer and
| matches login data for computers with that host name and any domain
| name.
| Note: After you run the command, the output_security_file contains only the
| framework users and the user definitions of your 8.2.x environment. You
| must manually merge this information with the new Tivoli Workload
| Scheduler security settings before you import your final security file into
| the new environment.
| Parallel 5: Preparing the old security file for switching the

| manager
| For Tivoli Workload Scheduler to switch correctly, you must add the new
| <TWS_user> into the old security file. The new TWS_user is the one that you used
| when you installed the master domain manager.
| Perform the following steps:

| 1. On the old master domain manager, log in as the old <TWS_user> and set the
| Tivoli Workload Scheduler environment. Add the <TWS_user> of the new
| master domain manager to the old security file.
| 2. If you have centralized security, distribute the security file. If you do not have
| centralized security, copy the compiled security file to your newly installed
| master domain manager, overwriting the version that is there.
| 3. Wait for the scheduled JnextDay to distribute the Symphony file.

| Parallel 6: Migrating the run number and global options

| Use this procedure to migrate the Tivoli Workload Scheduler run number and
| globalopts files to the current version.
| 1. On the new master domain manager, log in as a user that has full access to the
| database of both the old and the new Tivoli Workload Scheduler environments.
| 3. Either mount TWS_8.2.x_main_dir on the local system or copy the files
| globalopts and runmsgno from the old V8.2.x to the new V8.5 temporary
| directory
| 4. Use the optman command to import the installation run number and global
| options.
| optman miggrunnb <input_directory>
| optman miggopts <input_directory>
| where:
| <input_directory>
| is either the mounted V8.2 directory or the temp directory where you
| copied the files.
| Parallel 7: Data import- resolving problems

| At this point in the parallel upgrade check the quality of the migrated data, as
| described in “Data import - problem resolving” on page 84. When this process is
| complete, return to this parallel upgrade procedure, the next step of which is
| “Parallel 8: Switching the master domain manager.”
| Parallel 8: Switching the master domain manager

| To switch from the old master domain manager to the new one, perform the
| following steps:
| 1. On the old master domain manager, run the following command:
| conman switchmgr MASTERDM;new_master_cpu_name
| where new_master_cpu_name is the name of the workstation where the new

| 2. On the new master domain manager, ensure that the carry forward option is
| set to ALL, by running the following command:
| optman chg cf=ALL
| See Tivoli Workload Scheduler: Administration Guide.

| 3. On the new master domain manager, create a plan with 0 extension period that
| begins at the end of the current plan, by running the following command:
| JnextPlan -from start_time -for 0000
| where start_time is the date and time when the current plan ends. For example,
| if Jnextday ran, and the plan was created from today at 06:00 until tomorrow at
| 05:59 the start_time of the new plan must be tomorrow, at the default time of
| 06:00.
| 4. On the new master domain manager, reset the carry forward option to the
| value you assigned before running Step 2.
Data mapping: problem resolution
| 5. If you have a final schedule in your old environment and want to continue
| using it in the new environment, submit the following commands on the new
| master domain manager:
| a. composer "add FINAL"
| b. conman "cs old_master_cpu_name#final"
| where old_master_cpu_name is the name of the workstation where the old

| c. conman "sbs final"
| 6. Because you are adding a new final schedule, it is important that the old final
| schedule does not run. To avoid this, either delete the old final schedule from
| the database or set the priority to 0. To delete the old final schedule, run the
| following command:
| composer "del sched=old_master_cpu_name#final"
| where old_master_cpu_name is the name of the workstation where the old master
| domain manager resides.
| Parallel 9: Building the final security file for the new environment
| Version 8.5 introduces new security statements for the event management,
| reporting features, and variable tables. If you have specific security settings in your
| 8.2.x environment, these settings must be manually merged with the new settings
| before you build the final security file to be used in your new environment. The
| statements you might have to add manually vary depending on your specific
| security settings.
| If you ran the migrfwkuser utility on your old security file, you must merge the
| information contained in the output_security_file with the new security settings into
| a single text file.

| 1. On the new master domain manager, log in as the new <TWS_user> and set the
| Tivoli Workload Scheduler environment. Extract the new security file on the
| new master using the following V8.5 command:
| dumpsec > sec_file
| where sec_file is the text file created by the dumpsec command.

| 2. Add the following statements to the sec_file:
| REPORT NAME=@ ACCESS=DISPLAY
| EVENTRULE NAME=@ ACCESS=ADD,DELETE,DISPLAY,MODIFY,LIST,UNLOCK
| ACTION PROVIDER=@ ACCESS=DISPLAY,SUBMIT,USE,LIST
| EVENT PROVIDER=@ ACCESS=USE
|
| VARTABLE NAME=@ ACCESS=ADD,DELETE,DISPLAY,MODIFY,USE,LIST,UNLOCK
| 3. Check that the user permissions of the new statements are correct.
| 4. If you ran the procedure described in “Parallel 4: Optionally exporting Tivoli
| Management Framework user data from the security file” on page 71, perform
| the following:
| a. Transfer the output_security_file you obtained from your old system to the
| new master domain manager system.
| b. Open the output_security_file and copy into the sec_file the Tivoli
| Management Framework user statements.
| 5. Save your changes to the sec_file.

Data mapping: problem resolution
| 6. Build your final security file for your new master domain manager using the
| V8.5 makesec command:
| makesec sec_file
| 7. If you have centralized security, distribute the security file and run JnextPlan
| -from start_time -for 0000.
| 8. If you want to use EDWA, enable it using optman.
| Parallel 10: Customizing the optional final job stream

| If you had an old final job stream, no matter what it is called, it is now in the new
| database referring to the old master domain manager workstation. In addition, if
| you selected the option to create it when you installed the master domain manager,
| you will have a new final job stream called FINAL referring to the new master
| domain manager,
| If your old final job stream was customized or is not called FINAL, you must
| perform some customization steps. Depending on your situation, perform the
| following:
| If you had a customized final job stream in your database:
| 1. Edit the new FINAL job stream with composer or Tivoli Dynamic
| Workload Console.
| 2. View the old final job stream with composer or Tivoli Dynamic
| Workload Console.
| 3. Make the corresponding customizations to the new FINAL job stream.
| 4. Save your new FINAL job stream with a name of your choice.
| 5. Delete your old final job stream.
| If you had a final job stream that is not customized:
| 1. Delete your old final job stream with composer or Tivoli Dynamic
| Workload Console.
| 2. If necessary, rename the new FINAL job stream with the name of your
| old final job stream with composer or Tivoli Dynamic Workload
| Console.
| Parallel 11: Rebuilding the plan

| To rebuild the plan, perform the following:
| 1. Set optman cf to all.
| 2. Run JnextPlan -from <old_plan_start_date> -for 0000.
| 3. Run the submit job stream command for the final job stream.
| Performing a direct upgrade

| This section describes how to upgrade your environment directly. The upgrade
| consists of the following procedures:
| v “Direct 1: Unlinking the 8.2.x master domain manager from its agents and
| stopping it” on page 76
| v “Direct 2: Upgrading the master domain manager” on page 77
| v “Direct 3: Importing the 8.2.x data manually (optional)” on page 80
| v “Direct 4: Exporting Tivoli Management Framework user data from the security
| file (optional)” on page 81
| v “Direct 5: Completing the security configuration for the new environment” on
| page 82
| v “Direct 6: Data import - resolving problems” on page 83
Direct upgrade from V8.2.x
| v “Direct 7: Customizing the optional final job stream” on page 83

| v “Direct 8: Rebuilding the plan for the upgraded master domain manager” on
| page 84
| Direct 1: Unlinking the 8.2.x master domain manager from its

| agents and stopping it
| Before upgrading, you must unlink all workstations from the master domain
| manager and stop it.
| Note: Do not use the UNIX kill command to stop Tivoli Workload Scheduler
| processes.
| Follow these steps:

| 2. Unlink all workstations in the domain:
| From the Job Scheduling Console
| a. Run a Status of all Domains plan list. The Status of all Domains
| table opens.
| b. Right-click the domain you want to unlink and select Unlink
| Workstations from the pop-up menu.
| From the command line of the master domain manager
| Issue the following command:
| conman "unlink @;noask"
| 3. Stop the master domain manager:
| a. Select the master domain manager workstation
| b. Right-click the workstation and select Stop from the pop-up menu.
| conman “stop;wait”
| 4. From the command line of the master domain manager, stop the netman
| process as follows:
| v On Windows, run the shutdown.cmd command from the Tivoli Workload
| Scheduler home directory.
| v On UNIX, run:
| conman “shut;wait"
| 5. Verify that all services and processes are not running, as follows:
| v On Windows, type the command:
| <drive>\unsupported\listproc.exe
| Where:
| <drive>
| is the TWS_homedirectory
| Verify that the following processes are not running: netman, mailman,
| batchman, writer, jobman, stageman, JOBMON, batchup.
| Note: In a Windows environment, the Tivoli Token Server service must be

| running.

Direct upgrade from V8.2.x
| Also, ensure that no system programs are accessing the directory or

| subdirectories, including the command prompt, and that in Windows
| Explorer the Administrative Tools→Services panel is not open.
| v On UNIX, type the command:
| ps -ef | grep <TWA_home>/TWS/bin/jobman
| batchman, writer, jobman, JOBMAN, stageman.
| Note: In a Windows environment, the Tivoli Token Server service must be

| running.
| Direct 2: Upgrading the master domain manager

| This section describes how to upgrade a master domain manager. When the
| upgrade procedure is successful it is not possible to roll back to the previous
| version. Rollback is only possible for upgrades that fail.
| Note: Since rollback is not possible on successful upgrades, ensure that you have a
| complete backup of your Tivoli Workload Scheduler environment in case
| there is a problem, but it was not severe enough to cause the upgrade to
| fail.
| You can upgrade a master domain manager using the following installation
| methods:
| v “D2-W: Upgrading a master domain manager using the installation wizard”
| v “D2-S: Upgrading the master domain manager using a silent installation” on
| page 79
| D2-W: Upgrading a master domain manager using the installation wizard:

| During the upgrade procedure, the installation wizard backs up all the master data
| and configuration information, installs the new product code, and optionally
| dumps old scheduling data and configuration information. When the upgrade
| procedure is successful it is not possible to roll back to the previous version.
| Rollback is only possible for upgrades that fail.
| This procedure can be used to upgrade either a master domain manager or a

| backup master domain manager. Steps or considerations which apply only for the
| master domain manager upgrade are indicated by "Master only:",
| The steps are as follows:

| 1. If you are upgrading in a Windows environment, check that the Tivoli Token
| Server service is running.
| 2. Insert the installation DVD and run the setup for your operating system:
| v On Windows, WINDOWS\SETUP.exe
| v On UNIX and Linux, operating_system/SETUP.bin
| v Alternatively, start the launchpad as follows and select the Tivoli Workload
| Scheduler installation:
| On Windows systems
| from the root directory of the DVD run launchpad.exe.
| On UNIX systems
| From the root directory of the DVD run launchpad.sh.
| 3. The installation wizard is launched. Follow the prompts to continue with the
| upgrade. Note the following acronyms:
Upgrading a master domain manager using the installation wizard
| MDM Master domain manager

| BKM Backup master domain manager
| 4. Master only: If you are installing a master domain manager, specify the
| information necessary to perform the upgrade. Provide the following data:
| Back up the previous Tivoli Workload Scheduler instance
| Select whether to back up the previous instance.
| Back up Destination Directory
| When you select to back up the previous instance, specify the directory
| where the backup is located.
| Export Destination Directory
| The upgrade always exports the object data into text files, whether you
| want to import it automatically or manually. Specify the directory
| where you want the object data files to be saved. The default path is:
| v %TEMP%\tws85\datamigration in Windows systems
| v $TMP/tws85/datamigration in UNIX systems
| Automatically import data from the version being upgraded
| Clear this option only if you want to manually import the version 8.2.x
| object data into the RDBMS. For more information about making this
| choice see “Deciding how to upgrade the database” on page 59.
| Click Next.
| 5. Type the password of the Tivoli Workload Scheduler user for which you want
| to upgrade the instance. Click Next.
| 6. Specify the following application server port information. Accept the default
| values unless you know that the default ports are already in use. If you need to
| provide different values, any valid port number can be used:
| HTTP transport
| The port for the HTTP transport. The default value is 31115.
| HTTPS transport
| The port for the secure HTTP transport. The default value is 31116.
| Bootstrap
| The port for the bootstrap or RMI. The default value is 31117.
| SOAP connector
| ORB Listener

| Event Processor
| The default value is 31131. This port is not used by backup master
| domain managers. Click Next.
| 7. Specify the relevant RDBMS data for the database installation type or
| configuration you are performing. See “Installing a new master domain
| manager or backup master” on page 31. You must choose which type of
| database support (DB2 or Oracle), optionally choose a DB2 component to
| install, and supply the appropriate configuration information.
| 8. Review the summary data. Note the following considerations:
| v If an installation step fails, you might be able to correct the problem and
| resume the installation. If the installation fails, before taking any action, see
| Chapter 8, “Troubleshooting installation, migration, and uninstallation,” on
| page 125 to understand the implications of any action.
| v Every time you run an installation, you overwrite any recovery data that was
| stored from any previous installation. If a previous installation is incomplete
| for any reason, and you run a new installation action (even for a different
| component), it will be impossible for you to complete the previous
| installation (by resuming a failed step, for example).
| v Master only: If you are installing a master domain manager and you have
| chosen the automatic data import, the import is performed as a separate step
| in the installation process. In a large environment or an environment with
| slow network speeds, this step might take some hours to complete.
| During this step, note that the wizard's progress bar appears to be stopped at
| 97% complete while the import is being performed. This is normal. If you
| think the data import process might have failed, use system tools to
| determine if the datamigrate and composer processes are still running.
| 9. When the installation completes successfully, an appropriate panel is displayed.
| If the installation is unsuccessful, see Chapter 8, “Troubleshooting installation,
| migration, and uninstallation,” on page 125.
| Master only: If you are installing a master domain manager and you chose to
| import data automatically, a panel might be displayed indicating that the data
| has not been migrated cleanly. In this case, check the information in the
| directory indicated in the panel. See “Data import - problem resolving” on page
| 84.
| D2-S: Upgrading the master domain manager using a silent installation: To

| upgrade a master domain manager using a silent installation follow the procedure
| described in “Performing a silent installation” on page 44 using the response file
| TWS85_UPGRADE_MDM.txt.
| If you choose to import data automatically, and errors occur during the data
| migration process, Tivoli Workload Scheduler creates the following file:
| Windows %TEMP%\TWA\tws85\migrationErrors
| UNIX %TEMP%/TWA/tws85... /migrationErrors
| Check the information in the directory indicated in the file. See “Data import -
| problem resolving” on page 84.
| For more information about choosing to import data automatically or manually, see
| “Deciding how to upgrade the database” on page 59.
| Direct 3: Importing the 8.2.x data manually (optional)

| If you did not import the data automatically during the upgrade, perform these
| steps:
| 1. On the upgraded master domain manager, set the Tivoli Workload Scheduler
| environment using the tws_env command. See the Tivoli Workload Scheduler:
| User's Guide and Reference for detailed information about the command.
| 2. Define the master domain manager workstation using the composer command
| interface as follows:
| v UNIX:
| composer rep cpudef_unix
| v Windows:
| composer rep cpudef_wnt
| where:
| cpudef_unix
| is the text file containing the workstation definition for the master
| domain manager in UNIX environments
| cpudef_wnt
| is the text file containing the workstation definition for the master
| domain manager in Windows environments
| These files were created during the upgrade process.

| 3. Use the datamigrate command to import the data from the exported text files.
| These files were created by the installation wizard and stored in the path
| specified in the Export Destination Directory field. See “D2-W: Upgrading a
| master domain manager using the installation wizard” on page 77.
| The syntax and order of the commands to use are:
| datamigrate -topology topology_filename [-tmppath temp_path]
| datamigrate -prompts prompts_filename [-tmppath temp_path]
| datamigrate -calendars calendars_filename [-tmppath temp_path]
| datamigrate -parms parms_filename [-tmppath temp_path]
| datamigrate -resources resources_filename [-tmppath temp_path]
| datamigrate -users users_filename [-tmppath temp_path]
| datamigrate -jobs jobs_filename [-tmppath temp_path]
| datamigrate -scheds scheds_filename [-tmppath temp_path]
| where:
| topology_filename
| is the name of the topology file created by composer821 in the export
| process.
| prompts_filename
| is the name of the prompts file created by composer821 in the export
| process.
| calendars_filename
| is the name of the calendars file created by composer821 in the export
| process.
| parms_filename
| is the name of the parameters file created by composer821 in the export
| process.
| is the name of the resources file created by composer821 in the export
| process.

| users_filename
| is the name of the Windows users file created with the migrutility
| utility in the export process.
| jobs_filename
| is the name of the jobs file created by composer821 in the export
| process.
| scheds_filename
| is the name of the job streams file created by composer821 in the export
| process.
| temp_path
| is the temporary path where datamigrate stores the files during the
| migrate process. The default is <TWS_home>/tmp in UNIX systems. In
| Windows systems the default is <TWS_home>\tmp .
| Direct 4: Exporting Tivoli Management Framework user data from

| the security file (optional)
| If you have customized user security settings based on Tivoli Management
| Framework Administrator IDs rather than user IDs in your security file, you can
| perform the following steps to transfer the current settings to a file which you can
| then import into your new Tivoli Workload Scheduler environment.
| To extract the Tivoli Management Framework users, perform the following steps:
| 2. Set the Tivoli Management Framework environment:
| v On Windows, run setup_env from c:\windows\system32\drivers\etc\Tivoli
| v On UNIX, run setup_env.sh from /etc/Tivoli
| 4. Run the Tivoli Workload Scheduler utility dumpsec to export the user
| information to a flat text file (input_security_file) as follows:
| dumpsec > input_security_file
| where:
| Is the text file created by the dumpsec command.
| 5. Locate the migrfwkuser utility command in the following tar file on the
| appropriate installation DVD (see “Installation media” on page 26 for details):
| 6. Uncompress the tar file in a directory on the version 8.2.x environment.
| 7. On Windows systems only, run the bash command
| 8. Run setup_env.cmd on Windows or . ./setup_env on UNIX
| 9. Run the migrfwkuser script as follows:
| migrfwkuser -in input_security_file -out output_security_file
| [-cpu workstation] [-hostname local_hostname]
| where:
| Is the file created using the dumpsec command in step 4.
| output_security_file
| Is the security file that is created by the migrfwkuser script.
| workstation
| Is the name of the local workstation where the login data added by the
| tool is defined. If you do not specify a workstation, the data is taken
| from a localopts file if present in the same directory where the
| migrfwkuser script is located. If there is no localopts file, the
| workstation is set to the first 8 characters of the local host name.
| Note: If you do not specify a workstation, the data is taken from a

| localopts file located in the same directory as the migrfwkuser
| script.
| local_hostname
| Is the fully qualified host name of the Tivoli Management Framework
| users to be extracted. Login data for users with this host name or with
| this host name and domain name and the host name valid for all
| computers are extracted. If you do not specify the local host name,
| migrfwkuser retrieves the host name from the local computer and
| matches login data for computers with that host name and any domain
| name.
| Note: After you run the command, the output_security_file contains only the
| framework users and the user definitions of your 8.2.x environment. You
| must manually merge this information with the new Tivoli Workload
| Scheduler security settings before you import your final security file into
| the new environment.
| Direct 5: Completing the security configuration for the new

| environment
| Version 8.5 includes new security statements for the event management and
| variable tables. If you have specific security settings in your 8.2.x environment,
| these settings must be manually merged with the new settings before you build
| the final security file to be used in your new environment. The statements you
| might have to add manually vary depending on your specific security settings.
| Perform the following:

| 1. Log in as <TWS_user> on your upgraded master domain manager and set the
| Tivoli Workload Scheduler environment.
| 2. If you have centralized security enabled, extract the new security file on the

| 3. Edit the sec_file, and insert the following statements:
|

| 5. If you ran the procedure described in “Direct 4: Exporting Tivoli Management

| Framework user data from the security file (optional)” on page 81, perform the
| following:
| a. Transfer the output_security_file you obtained from your old system to the
| new master domain manager system.
| b. Open the output_security_file and copy into the sec_file the Tivoli
| Management Framework user statements.
| makesec sec_file
| 8. If you have centralized security, distribute the security file (you will run
| JnextPlan in a later step).
| Direct 6: Data import - resolving problems

| At this point in the direct upgrade, check the quality of the imported data, as
| described in “Data import - problem resolving” on page 84. When this process is
| complete, return to this parallel upgrade procedure, the next step of which is
| “Direct 8: Rebuilding the plan for the upgraded master domain manager” on page
| 84.
| Direct 7: Customizing the optional final job stream

| If you had an old final job stream, no matter what it is called, it is now in the new
| database. If your old final job stream is not called FINAL, a new FINAL job stream
| has been added to the database. If your old final job stream is called FINAL, the
| new final job stream will either not have been added, or will have been
| overwritten by the old final job stream when it was migrated. However, you can
| use the source for the new final job stream to merge the functions of your old final
| job stream with the syntax of your new final job stream. The source is located in
| the file <TWA_home>/TWS/Sfinal. This is a flat text file containing the job stream
| definitions ready for import with composer.
| If your old final job stream was customized, you must perform some
| customization steps to create the new file. Depending on your situation, perform
| the following
| Your old customized final job stream is not called FINAL:
| 1. Edit your new FINAL job stream using composer or Tivoli Dynamic
| Workload Console.
| 2. View your old final job stream using composer or Tivoli Dynamic
| Workload Console.
| 3. Make the corresponding customizations to the new final job stream.
| 4. Save your new final job stream either as FINAL or with a name of your
| choice.
| Your old customized final job stream is called FINAL:
| 1. Change the name of your old FINAL job stream to some other name.
| 2. Add the FINAL job stream from the SFinal file using composer or
| Tivoli Dynamic Workload Console.
| 3. View your old final job stream using composer or Tivoli Dynamic
| Workload Console.
Data mapping - problem resolution
| 4. Make the corresponding customizations to the new final job stream.

| 5. Save your new final job stream either as FINAL or with a name of your
| choice.
| Direct 8: Rebuilding the plan for the upgraded master domain

| manager
| To rebuild the plan, perform the following:
| 1. Set optman cf to all.
| 2. Run JnextPlan -from <old_plan_start_date> -for 0000.
| 3. Run the submit job stream command for the final job stream.
Data import - problem resolving

This section describes how you validate the data import and correct any
inconsistencies.
The information in this section assumes that the data import has successfully
completed. For problems relating to the running of the data import, refer to Tivoli
Workload Scheduler Administration and Troubleshooting.
The topics in this section are as follows:

v “Data import log files”
v “Object data inconsistencies and recovery” on page 85
Data import log files

During the automatic data import the following log files are created in
the<TWS_home>/tmp directory in UNIX environments or <TWS_home>\tmp in
Windows environments. If you have chosen a manual import and have specified a
different value in the temp_path parameter, the files are created in the path you
indicated.
datamigrate_object_nnnnnn.log
Contains all the messages created during the import process, where
object is the database object and nnnnnn is an identifier of each
datamigrate run.
datamigrate_object_nnnnnn.err
Contains the error messages created during the data import
process, where object is the database object and nnnnnn is an
identifier of each datamigrate run.
The database object files are the following:

v CALENDARS
v JOBS
v PARMS
v PROMPTS
v RESOURCES
v SCHEDS
v TOPOLOGY
v USERS
You only need to fix situations that are reported as errors during the data import
process.

Data import- problem resolution
Note: Because each error is logged for each step of the migration process the
reported number of errors is greater than the true level.
Object data inconsistencies and recovery

This section describes how any inconsistencies in the imported 8.2.x data are
mapped to 8.5, and any manual recovery actions required. These actions must be
performed before you can commence scheduling with version 8.5.
In most cases the discrepancies between the two versions can be traced to
inconsistencies in the previous database. The information in the Mapping column of
each object-type table below tells you how the data import has dealt with any
inconsistencies. You have two options for correcting these inconsistencies:
v Correct the inconsistency in Tivoli Workload Scheduler, version 8.5
v Correct the inconsistency in Tivoli Workload Scheduler, version 8.2.x and redo
the import. If you want to take this option you must first remove the imported
data from the database before redoing the import.
The mapping is organized by object type:

v “Mapping domains”
v “Mapping workstations”
v “Mapping workstation classes” on page 86
v “Mapping job definitions” on page 87
v “Mapping Windows users” on page 87
v “Mapping resources” on page 87
v “Mapping job streams” on page 87
v “Mapping jobs” on page 88
v “Mapping dependencies” on page 89
Mapping domains: Table 14 lists the mapping and behavioral differences between
v8.2.x and v8.5 domains and when a recovery action might be required.
Table 14. Data and behavior mapping for domains
Configuration v8.2.x behavior v8.5 behavior Mapping
Domains with no manager. Definition allowed, As for v8.2.x No mapping is required.
domains not added to plan.
Workstations are moved to
the Master Domain;
sub-domains are moved
under the Master Domain.
Domain has a manager Possible (adding or Not possible. If the domain refers to a workstation
defined in a different changing workstation later). that exists, data import modifies the
domain, or the manager is Compiler assigned to the workstation to point to the
manager of more than one latest domain definition. workstation. If the domain refers to a
domain. workstation that does not exist, the
domain is left without a manager.
A parent domain does not Possible (removing the Not possible. Data import issues a warning and
exist. domain later). Compiler uses the Master Domain as parent.
uses the Master Domain as
parent.
Mapping workstations: Table 15 on page 86 lists the mapping and behavioral

differences between v8.2.x and v8.5 workstations and when a recovery action
might be required.
Inconsistencies in the imported data
Table 15. Data and behavior mapping for workstations

Workstation domain does Possible (removing domain Not possible. Data import links the workstation to
not exist. later). Compiler links the the Master Domain and issues a
workstation to the Master warning.
Domain.
Workstation is a domain Possible as the compiler The full status If the Domain Manager is a standard
manager but is not a changes the workstation to flag is agent, data import issues a warning
fault-tolerant agent or does a full status fault-tolerant automatically set and the full status flag is set to true. If
not have full status set. agent. to true when a the Domain Manager is an extended
Domain Manager agent the workstation is not promoted
is saved. to an fault-tolerant agent.
Standard agent with no Possible as the compiler The domain is If the domain is null and host is not,
domain but host specified. sets the domain to the mandatory and data import sets the domain as the
domain of the hosting the host ignored. hosting workstation domain.
workstation and moves the
workstation under the
Domain Manager of the
domain.
Extended agent with Possible. Domain is not Data import ignores the domain.
domain specified. possible.
Host of an extended agent Possible (removing host Not possible. Data import assigns the workstation to
or standard agent does not workstation later). the MASTER workstation.
exist. Extended agents are hosted
by the MASTER
workstation.
The workstation operating composer treats all of these Operating Data import considers all of the
system is one of the operating systems as UNIX. systems are operating systems as UNIX.
following: modified to
v MPEV UNIX.
v MPEXL
v MPIX
v MPEIX
v POSIX
v HPUX
v AIX
Mapping workstation classes: Table 16 lists the mapping and behavioral

differences between v8.2.x and v8.5 workstation classes and when a recovery
action might be required.
Table 16. Data and behavior mapping for workstation classes
Some or all of the Possible (removing Not possible. If one or more of the workstations do
workstations in the workstations later). not exist, data import ignores them,
workstation class do not saves the workstation class and issues
exist. a warning. If no workstation exist the
workstation class is created empty.
Note: If you have a version v8.2.x workstation class with a name longer than 128
bytes, the composer command treats the list member as two separate items
and creates two incorrect workstation classes. If you used the composer821
command this problem should not occur.

Mapping job definitions: Table 17 lists the mapping and behavioral differences
between v8.2.x and v8.5 job definitions and when a recovery action might be
required.
Table 17. Data and behavior mapping for job definitions
The workstation or Possible (removing Not possible. Data import does not add the job
workstation class does not workstation later). The definition and issues an error. Data
exist. compiler does not add the import proceeds.
job to Symphony. Ad hoc
subs goes into error. If the
job is part of a job stream
the job is added to the plan
and remains in READY
state. Any jobs depending
on it, remain in the HOLD
state.
The recovery job does not Possible (removing job Not possible. Data import ignores the recovery job
exist. definition later). The and issues a warning.
compiler does not add the
job to the Symphony. Ad
hoc subs goes into error.
Mapping Windows users: Table 18 lists the mapping and behavioral differences
between v8.2.x and v8.5 Windows users and when a recovery action might be
required.
Table 18. Data and behavior mapping for Windows users
The Windows user Possible (removing Not possible. Data import ignores the Windows user
workstation does not exist. workstation later). The and issues an error. Data import
compiler adds the user, but proceeds.
it can not be used by any
jobman.
Mapping resources: Table 19 lists the mapping and behavioral differences

between v8.2.x and v8.5 resources and when a recovery action might be required.
Table 19. Data and behavior mapping for resources
The workstation or Possible (removing Not possible. Data import ignores the resources and
workstation class of the workstation later). The issues an error. Data import proceeds.
resource does not exist. resource are added to the
plan.
Mapping job streams: Table 20 on page 88 lists the mapping and behavioral
differences between v8.2.x and v8.5 job streams and when a recovery action might
be required.
Table 20. Data and behavior mapping for job streams

The workstation or Possible (removing Not possible. Data import ignores the job stream
workstation class of the job workstation later). The and issues an error. Data import
stream does not exist. compiler does not add the proceeds.
job stream.
The job stream refers to a Possible (removing the Not possible. Data import sets the free days
free days calendar that calendar later). The calendar to null an issues a warning.
does not exist. compiler adds the job
stream to the plan.
The calendar run cycle Possible (removing the Not possible. Data import adds the job stream to the
refers to a calendar that calendar later). The plan without that run cycle and issues
does not exist. compiler does not add the a warning.
job stream to the plan.
The job stream contains job Possible (adding new job Not possible. During the data import process the job
definitions that are defined streams containing the definitions are discarded. No warning
in different ways in same job definition with is issued because the job definitions
multiple job streams. different specifications). are loaded before loading the job
The latest job definition is stream.
added to the plan.
The job stream has a Possible (the dependency is Not possible. The job stream is imported, the file
dependency on a file with a accepted by composer, but dependency is dropped and the
name that is longer than 28 is deleted when Jnextday is priority is set to 0. Data import
characters. run). proceeds.
The job stream is defined This scenario is improbable Not possible. Data import ignores the job stream
on a workstation class and in a production and issues an error. Data import
has one or more jobs also environment. The compiler proceeds.
defined on a workstation exits without completing
class. plan creation.
Mapping jobs: Table 21 lists the mapping and behavioral differences between
v8.2.x and v8.5 jobs and when a recovery action might be required.
Table 21. Data and behavior mapping for jobs
The job has a dependency Possible (the dependency is Not possible. The job stream is imported, the file
on a file with a name that accepted by composer, but dependency is dropped and the
is longer than 28 characters. is deleted when Jnextday is priority is set to 0. Data import
run). proceeds.
The job refers to a job Possible (removing the job Not possible. Data import replaces the job definition
definition that does not definition later). The with a dummy job definition and sets
exist. compiler substitutes the job the job priority to 0, guaranteeing that
with a dummy job in the successors are not run. The job name
FAIL state. is:
TWS_INITIAL_DUMMY_JOBDEFINITION
With the following definition:

TWS_INITIAL_DUMMY_JOBDEFINITION"
"DOCOMMAND DUMMY_TASK"
"STREAMLOGON
DUMMY_USER"

Mapping dependencies: Table 22 lists the mapping and behavioral differences

between v8.2.x and v8.5 dependencies and when a recovery action might be
required.
Table 22. Data and behavior mapping for dependencies
An external dependency Possible, dependency is not Not possible. Data import removes the dependency
refers to a job or a job added to the plan. and issues a warning.
stream that does not exist.
An Inter network Possible, dependency is not Not possible. Data import removes the dependency
dependency uses a added to the plan. and issues a warning.
workstation that does not
exist.
A dependency refers to a Possible, the prompt is Not possible Data import creates a dummy prompt
prompt in a job or a job added to the plan. When with the text "The prompt prompt
stream that does not exist. other dependencies are referenced as a dependency by job
resolved, the job stream stream job_stream does not exist. A
goes into the STUCK state, dummy prompt is added and the
and the job remains in migrated job stream is modified to refer
READY state. to it".
A dependency refers to a Possible, the resource is Not possible. Data import creates the resource with
resource in a job or a job added to the plan. When the same name and an availability of 0.
stream that does not exist. other dependencies are If workstation to which the resource
resolved, the job stream belongs does not exist it is associated to
goes into the READY state, the MASTER workstation, and a
and the job remains in warning is issued. The description is
HOLD state. "Resource created during initial
upgrade".
A file dependency refers to Possible, the file is added Not possible. Data import issues a warning and
a workstation that does not to the plan. When other assign the file dependency to the file:
exist. dependencies are resolved, TWS_INITIAL_UPGRADE _DUMMY_FILE
the job stream goes into the
READY state, and the job defined on the MASTER workstation.
remains in HOLD state.
A job or job stream refer to Possible, the substitution is Possible, the None.
a parameter that does not not done. substitution is
exist. not done.
Inter-network dependencies Possible, the job stream is Not possible. Data import creates a dummy extended
are defined on added to the plan in the agent with an nonexistent access
workstations that are not ERROR state. method:
extended agents. CPUNAME TWS_DUMMY_XAGENT DESCRIPTION
"this is a dummy xagent with
a dummy method created during
initial upgrade"
OS OTHER
NODE DUMMY_NODE TCPADDR 31111
FOR MAESTRO HOST $MASTER ACCESS
"__DUMMY_METHOD__"
TYPE X-AGENT
AUTOLINK OFF
BEHINDFIREWALL OFF
FULLSTATUS OFF
END
Post-upgrade issues
This section describes any issues that you must resolve after the migration is
complete.
Integrating with NetView

After you migrate, if you integrate with NetView®, the new NetView StartUp must
be merged with the old StartUp file. Migration saves the old file as
StartUp.toMerge, see Tivoli Workload Scheduler: Integrating with Other Products for
more details.
Maximizing DB2 database efficiency

If you have migrated a database containing a large number of jobs or job streams,
and the database support is DB2, run the dbrunstats utility to maximize the
efficiency of the database.
The DB2 database has been set up to maintain itself, so there is little user
maintenance to do. However, the process of importing data does not necessarily
organize the database in the most efficient way. In normal running, DB2
periodically checks the database by running an internal routine. DB2 determines
when this routine must be run using a default policy. Using the statistical
information that DB2 discovers by running this routine, it adjusts its internal
processing parameters to maximize its performance. To avoid having to wait for
the default policy for running the routine, you can do it manually. The routine is
imbedded in a tool called dbrunstats, which can be run to improve performance
while DB2 is processing data without causing any interruption.
See Tivoli Workload Scheduler: Administration Guide for instructions on how to run
this utility.
| Upgrading a version 8.3 or 8.4 master domain manager instance

| This section describes how to upgrade master domain managers and backup
| master domain managers from Tivoli Workload Scheduler version 8.3 or 8.4 to
| version 8.5. The upgrade of version 8.2 to version 8.5 is described in “Upgrading a
| version 8.2 or 8.2.1 master domain manager instance” on page 55.
| To upgrade agents from all supported versions, refer to the procedures described
| in “Upgrading agents and domain managers” on page 108.
| This section is divided into the following subsections:

| v “Upgrading overview”
| v “Preparing to upgrade” on page 95
| v “New directory structure” on page 96
| v “Performing a parallel upgrade” on page 98
| v “Performing a direct upgrade” on page 102
| Upgrading overview
| This section provides an overview of the upgrade of an existing version of Tivoli
| Workload Scheduler v8.3 or v8.4 instance. It is divided into the following sections:
| v “Choosing how to migrate your network” on page 91
| v “Component upgrade procedures” on page 91

Upgrade overview
| Choosing how to migrate your network

| Tivoli Workload Scheduler versions 8.3 and 8.4 support backward compatibility so
| you can decide to upgrade your network in either of the following ways:
| Top-down
| Upgrade the master domain manager and backup master domain manager,
| and then progressively upgrade the agents. Many of the new functions
| introduced in the current version become available for each agent as it is
| upgraded. The disadvantage is that the same functions are not available to
| all agents at the same time.
| Bottom-up
| Upgrade the agents first, and then upgrade the master domain manager
| and backup master domain manager. The new functions introduced in the
| current version are not available until the whole network has been
| upgraded.
| Component upgrade procedures

| The following diagram shows the steps you can perform to upgrade your Tivoli
| Workload Scheduler version 8.3 or 8.4 to version 8.5:
| The following lists the Tivoli Workload Scheduler components and where to find
| their corresponding upgrade procedures in this document.
Upgrade overview
|
Upgrade MDM
Start with running from V8.3 or V8.4
V8.3 or V8.4 MDM
Upgrade
Direct
type?
Parallel Upgrade MDM
Stop scheduling
BKM exists?? processes
Upgrade
Yes Direct
type?
No
Upgrade BKM to Parallel

Install BKM V8.5
V8.5
Run switch manager

to switch back to
upgraded MDM
Define new BKM in

old database
Was first switch

manager (*) made No
Rebuild the plan in the permanent?
MDM to send the
Symphony file to the
BKM
Yes
Make the second

Run switch manager switch manager
permanent
Can upgrade be Which version

completed in being
plan cycle? upgraded?
No V8.3
Yes V8.4
Make switch Upgrade security file

manager permanent for event processing
(*) (new in V8.4)
Restart scheduling
MDM upgraded
to V8.5
|
| Figure 6. Overview of procedure for upgrading from version 8.3 or 8.4
|
|

Upgrade overview
| Master and backup domain manager upgrade scenarios

| There are several factors to consider before you upgrade your master domain
| manager and backup master domain manager. The following section describes
| these factors and outlines the available upgrade scenarios.
| This section provides two upgrade scenarios from which you must choose:
| v “Parallel upgrade scenario - minimizing the impact on scheduling”
| v “Direct upgrade scenario - minimizing the time to upgrade” on page 94
| Parallel upgrade scenario - minimizing the impact on scheduling

| A parallel upgrade allows you to maintain the integrity of your previous master
| domain manager until you are confident with the new environment. The upgrade
| is staged and allows you to work in coexistence with your old environment.
| In the parallel scenario described in the following sections, you start by upgrading
| your existing backup domain manager or by installing a new Tivoli Workload
| Scheduler backup domain manager. Your new or upgraded backup master domain
| manager then assumes the role of your old master domain manager. You then have
| the choice of making this new environment permanent. Alternatively, you can
| upgrade and restore the old master domain manager to its original role.
| This sequence of operations is designed to minimize your out-of-service time and

| to ensure data integrity. The parallel upgrade involves a limited number of manual
| steps but has the advantage of maintaining the integrity of your current
| environment.
Parallel upgrade scenario
|| Steps Advantages Disadvantages
| 1. Perform one of the following v Allows the v Involves some

| depending on whether or not you coexistence of the manual
| already have a backup master domain old master with the configuration steps
| manager in your version 8.3 or 8.4 new environment
|| environment: v Allows you to
| v Upgrade your current version 8.3 or choose a new and
| 8.4 backup master domain manager better performing
| referencing the existing version 8.3 or platform for your
| 8.4 database. new master
|| v Install a fresh backup master domain domain manager
| manager , that points to the existing v It is a reversible
| version 8.3 or 8.4 database. process
| 2. Switch your manager to the new backup v Automatically
| master domain manager. updates the
|| 3. Make the switch manager permanent. database schema
| which is fully
| 4. Decide what your final configuration
| compatible for old
| will be. You have the following options:
| and new versions
| v Upgrade your old master domain
| v Allows a great
| manager and resume your original
| degree of flexibility.
| configuration restoring the upgraded
| You can choose to
| master domain manager. Then, switch
| not upgrade the
| to upgraded master domain manager
| old master domain
| so that the original configuration will
| manager.
| be restored.
| v You can easily
| v Do not upgrade the master domain
| upgrade hardware
| manager and install a new backup
| at the same time
| master domain manager.
| you perform the
|| v Do not upgrade the master domain parallel upgrade
| manager and have no backup master
| domain manager.
| 5. Complete your security configuration by
| merging old and new security settings.
|
| Direct upgrade scenario - minimizing the time to upgrade

| The direct upgrade scenario allows you to upgrade your current environment
| quickly, reducing manual intervention. The procedure automatically upgrades your
| network and database information using the input you provide. The installation
| wizard is the simplest way of approaching this type of upgrade because it guides
| you through the process.
|| Steps Advantages Disadvantages
| 1. Unlink the old master domain manager v Quicker and v Scheduling might
| and then stop it. simpler than the be delayed for
|| 2. Upgrade the master domain manager, parallel upgrade. those activities
|| automatically importing the scheduling involving the
|| and configuration data from the master domain
|| previous version. manager
| 3. Complete the security configuration by
| merging old and new security settings.
| 4. Upgrade the backup master domain
| manager.
|

Direct upgrade scenario
| Configuring the security file for new functions

| During the upgrade procedure you will need to configure the security file for new
| functions. Configuring the security file requires the following:
| Configuring for event-driven workload automation
| Configuring for event-driven workload automation applies only to version
| 8.3. You must modify the security file to include new security statements
| for the event management and reporting features. If you have specific
| security settings in your V8.3 environment, these settings must be
| manually merged with the new settings before you build the final security
| file for your current environment. The statements you add manually might
| vary depending on your security settings and on whether you have chosen
| the parallel or direct upgrade scenario, as explained in the following
| sections.
| Setting the default variable table
| Setting variable tables applies to both version 8.3 and 8.4. The upgraded
| security file includes the new default statement for variable tables. A
| variable table is an object that groups together multiple variables. Known
| as global parameters in previous versions, these objects are now called
| variables in version 8.5. Local parameters are managed as before, and the
| old parameters statement from the previous security file continues to
| manage their security aspects. Any global parameters that were defined in
| your previous database have become elements of the default variable table,
| and a security statement for the table has been added to the security file.
| You can choose to customize the user permissions to this table (by default,
| all users have full permission).
| Preparing to upgrade
| Before you begin the upgrade process, complete the following tasks as appropriate:
| Perform a backup of your database
| Before you begin the upgrade process, perform a backup of your current
| Tivoli Workload Scheduler database, referring to the Oracle or DB2
| documentation.
| Linux kernel
| If you are upgrading in a Linux environment that uses the
| LD_ASSUME_KERNEL=2.4.1 environment variable, upgrade to the current
| version of Tivoli Workload Scheduler in a shell that also uses the
| LD_ASSUME_KERNEL=2.4.1 environment variable.
| Ensure your current Tivoli Workload Scheduler installations are in the correct
| state When you are upgrading your current environment, make sure the
| software package is in the COMMIT state. If it is in the UNDOABLE state, you
| must accept it to change its state to COMMIT before you upgrade to the
| current version. To check the state, perform the following:
| 1. From <TWA_dir>/TWS/_uninstall/CLI, run the command:
| swd_env.bat or /swd_env.sh as appropriate.
| 2. Run the command: wdlssp
| 3. Search for the following lines:
| DISSE0164I Name : TWS_LP_twsuser
| DISSE0165I Version : 8.4.0.00
| DISSE0166I State : IC---
|
| ----------------------------------------
Before upgrading
|
| DISSE0164I Name : FP_TWS_WINDOWS_twsuser
| DISSE0166I State : IC---
| 4. Ensure that the state of the package is IC.

| Program directory
| directory. The default location for the upgrade is /opt/ibmTWA/TWS/.
| For example, if you originally installed Tivoli Workload Scheduler into the
| directory c:\Program Files\IBM\TWS, you have a directory structure as follows:
| c:\Program Files\IBM\TWS\bin
| c:\Program Files\IBM\TWS\config
| c:\Program Files\IBM\TWS\uninstall
| c:\Program Files\IBM\TWS\AppServer
| c:\Program Files\IBM\TWS\wastools
|
| c:\Program Files\IBM\TWA\TWS\bin
| c:\Program Files\IBM\TWA\TWS\config
| c:\Program Files\IBM\TWA\TWS\uninstall
| c:\Program Files\IBM\eWAS
| c:\Program Files\IBM\wastools
|
| On UNIX, if you originally installed Tivoli Workload Scheduler into

| /export/home/TWS, you have a directory structure as follows:
| /export/home/twsuser/bin
| /export/home/twsuser/config
| /export/home/twsuser/_uninstall
| /export/home/twsuser/appserver
|

Before upgrading
| /export/home/twsuser/TWS/bin
| /export/home/twsuser/TWS/config
| /export/home/twsuser/TWS/_uninstall
| /export/home/twsuser/eWAS
|
| If you have a FINAL schedule, during the upgrade, it is downloaded during the
| installation. The default FINAL is reused. A backup copy of the schedule is created
| with the name SFinal.extract in the new installation directory
| Note: On UNIX operating systems, you can create symbolic links to the new
| directory structure until the scheduling environment is updated by
| performing the In -s command from the old installation directory. For
| example:
| In -s bin TWS/bin
| In -s config TWS/config

| to default.

|
Before upgrading
| Performing a parallel upgrade

| This section describes how to upgrade your environment using a parallel upgrade
| scenario. The scenario consists of the following procedures:
| v “Parallel 1: Setting up your backup master domain manager”
| – “Parallel 1a: Installing a new backup master domain manager”
| or
| – “Parallel 1b: Upgrading your current version 8.3 or 8.4 backup master domain
| manager” on page 99
| v “Parallel 2: Preparing the old security file for switching the manager” on page 99
| v “Parallel 3: Switching the master domain manager to the new backup master”
| on page 99
| v “Parallel 4: Making the switch manager permanent” on page 99
| v “Parallel 5: Upgrading your version 8.3 or 8.4 master domain manager” on page
| 100
| v “Parallel 6: Switching back to the old master domain manager (optional)” on
| page 100
| v “Parallel 7: Customizing the optional final job stream” on page 101
| v “Parallel 8: Building the final security file for the new environment” on page 102
| Parallel 1: Setting up your backup master domain manager

| This step is divided into two alternative substeps, depending on whether you
| already have a backup master domain manager in your version 8.3 or 8.4
| environment:
| Parallel 1a: Installing a new backup master domain manager: The purpose of
| this step is to install a fresh backup master domain manager and attach it to your
| current version 8.3 or 8.4 network.
| This backup master domain manager points to your existing Tivoli Workload
| Scheduler database and will become your new master domain manager.
| Parallel 1a-1: Installing a fresh backup master domain manager
| To install a new backup master domain manager refer to the procedures
| described in Chapter 4, “Installing,” on page 31. Specifically, refer to the
| procedure described in “Tivoli Workload Scheduler steps” on page 32 and
| subsequent sections depending on whether you are using a DB2 or an
| Oracle database. Ensure that your new backup master domain manager
| points to your current Tivoli Workload Scheduler database instance.
| Parallel 1a-2: Define a new backup master domain manager in the database
| Define your new backup master domain manager as a full status agent in
| the domain of your version 8.3 or 8.4 master domain manager, using the
| composer command interface.

Parallel upgrade from V8.3 and 8.4
| Parallel 1b: Upgrading your current version 8.3 or 8.4 backup master domain
| manager: To upgrade your current backup master domain manager, follow the
| procedure described in “Direct 2: Upgrading the master domain manager” on page
| 104 using your preferred installation method.
| Parallel 2: Preparing the old security file for switching the

| manager
| For Tivoli Workload Scheduler to switch correctly, you must add the new
| <TWS_user> into the old security file. The new <TWS_user> is the one that you
| used when you installed the master domain manager.

| 1. On the old master domain manager, log in as the old <TWS_user> and set the
| Tivoli Workload Scheduler environment. Add the <TWS_user> of the new
| master domain manager to the old security file.
| 2. If you have centralized security, distribute the security file to all agents. If you
| do not have centralized security, copy the compiled security file to the installed
| or upgraded backup master domain manager, overwriting the version that is
| there.
| 3. Check that the optman cf option is set to all
| 4. Run JnextPlan -for 0000 or wait until the end of the production plan.
| Parallel 3: Switching the master domain manager to the new

| backup master
| Switch to your new backup master domain manager, which now becomes your
| master domain manager, by issuing the following command on your old version
| 8.3 or 8.4 master domain manager:
| conman
| switchmgr masterdm;new_mgr_cpu
| where new_mgr_cpu is the name of the workstation of your new or upgraded

| backup master domain manager.
| If you are upgrading from V8.4 and the event processor is being hosted on the old
| master domain manager or backup master domain manager, you must run
| switchevtprocessor to switch the event processor in the same way.
| Parallel 4: Making the switch manager permanent

| In the preceding step you have promoted your upgraded backup master domain
| manager to the role of master domain manager.
| Whether you perform this current step, depends on your situation as follows:
| v If you want to make switch manager permanent because you want the new
| master domain manager to become the old backup master domain manager,
| complete this step.
| v If you do not want to make the switch manager permanent, but you cannot
| complete the upgrade procedure before the next JnextPlan, complete this step,
| but later reverse it after you have completed all the remaining upgrade steps.
| v If you do not want to make the switch manager permanent and you can
| complete the upgrade procedure before the next JnextPlan, do NOT run this
| procedure. Note that you must still edit the FINAL job stream to include the
| updated installation paths.
| To make this configuration fully operational and persistant through JnextPlan, you
| must perform the following steps:
| On the new master domain manager, referred to as new_mgr_cpu:

| 1. Edit the localopts file and modify the following entry as shown:
| DEFAULTWS=new_mgr_cpu
| where new_mgr_cpu is the workstation name of the new master. See Tivoli
| 2. Change the workstation definition of the old master using composer:
| modify cpu=old_mgr_cpu
| and substitute type=manager with type=fta

| 3. Repeat the preceding step, this time to modify the workstation definition of the
| new master and substitute type=fta with type=manager.
| 4. Rebuild the plan to activate the changes to the database:
| JnextPlan -for 0000
| After this step, your backup master domain manager has become the master
| domain manager of the new environment. Before you proceed to the next step,
| decide what to do with your old master domain manager. You have three
| alternatives:
| v Keep the new manager as the master domain manager of your new environment
| and your old master domain manager as a full status agent, upgrading it later to
| the new version. Proceed to “Parallel 7: Customizing the optional final job
| stream” on page 101.
| v Keep the new manager as the master domain manager of your new environment
| and upgrade the old master to become the new backup master domain manager.
| Proceed to “Parallel 7: Customizing the optional final job stream” on page 101
| before upgrading the old master domain manager. After completing the upgrade
| of the master domain manager, proceed to “Upgrading backup master domain
| manager” on page 108.
| v Upgrade your old master domain manager and restore the original configuration
| in the new environment. Proceed to the next step.
| Parallel 5: Upgrading your version 8.3 or 8.4 master domain

| manager
| This step is optional. Alternatively, you can install a new backup master domain
| manager. To upgrade your version 8.3 or 8.4 master domain manager (which is
| now your backup master domain manager), perform the following steps:
| 1. From the new master domain manager, unlink the old master workstation
| conman "unlink old_mdm_cpu"
| 2. Upgrade your old master domain manager to the current version using the
| procedure described in “Direct 2: Upgrading the master domain manager” on
| page 104.
| 3. Link the upgraded master domain manager to the network
| conman "link old_mdm_cpu"
| Parallel 6: Switching back to the old master domain manager

| (optional)
| This step is optional. You can switch back to your old master domain manager that
| has now been upgraded. To do this, perform the following steps:

| 1. From the upgraded master domain manager switch the master domain
| manager:
| conman
| switchmgr masterdm;old_mdm_cpu
| 2. To restore your upgraded master domain manager to its role permanently,
| perform the steps outlined in “Parallel 4: Making the switch manager
| permanent” on page 99, this time for the master workstation.
| Parallel 7: Customizing the optional final job stream

| If your old final job stream is called FINAL, a backup copy has been made of it in
| Sfinal.extract and it has been upgraded to V8.5. If it was customized, you must
| check that the customizations have been correctly upgraded. If it is not called
| FINAL, you must merge the functions of your old final job stream with the syntax
| of your new FINAL job stream. Depending on your situation, perform the
| following steps:
| If you had a customized job stream called FINAL in your database:
| Workload Console.
| 2. Edit the file Sfinal.extract with a text editor.
| 4. Save your new FINAL job stream.
| If you had a customized final job stream called something other than FINAL in
| your database:
| Workload Console.
| 2. Edit your old final job stream with composer or Tivoli Dynamic
| Workload Console.
| 3. Merge the two job streams so that your new final job stream has the
| same name and customizations as before (if you want to preserve the
| naming), plus the new required attributes from the new FINAL job
| stream.
| 4. Save your new final job stream.
| 5. Delete the old final job stream.
| If you had a final job stream called something other than FINAL in your
| database, but it is not customized:
| Workload Console.
| 2. Rename the new FINAL job stream with the name of your old final job
| stream with composer or Tivoli Dynamic Workload Console.
| If you had a final job stream called FINAL in your database, but it is not
| customized:
| Take no action because the FINAL job stream has already been edited by
| the installation or upgrade procedure.
| In all cases, now perform one of the following:

| v Run ResetPlan.
| v Use conman to delete your old final job stream instances and submit new
| instances to replace them.
| Note: You will run JnextPlan in “Parallel 8: Building the final security file for the
| new environment” on page 102.
| Parallel 8: Building the final security file for the new environment
| Version 8.5 introduces new security statements for the event management (V8.4)
| and variable tables (V8.5). If you have specific security settings in your V8.3 or
| V8.4 environment, these settings must be manually merged with the new settings
| before you build the final security file to be used in your new environment. The

| 1. On the new master domain manager, log in as the new <TWS_user> and set the
| Tivoli Workload Scheduler environment. Extract the new security file on the

| 2. Add the following statements to the sec_file.
| If you are migrating from V8.3, add the following statements:
| If you are migrating from either environment, add the following statement:
| makesec sec_file
| 6. If you have centralized security, distribute the security file.
| 7. Run JnextPlan -for 0000 to update the Symphony file on the agents.
| Performing a direct upgrade

| This section describes how to upgrade your environment using a direct scenario. It
| is divided into the following procedures:
| 1. “Direct 1: Unlinking the master domain manager from the network and
| stopping it”
| 2. “Direct 2: Upgrading the master domain manager” on page 104
| 3. “Direct 3: Customizing the optional final job stream” on page 107
| 4. “Direct 4: Completing the security configuration for the new environment” on
| page 107
| Direct 1: Unlinking the master domain manager from the network

| and stopping it
| Before commencing the upgrade, you must unlink all workstations from the master
| domain manager and stop it.
| Follow these steps:

| 2. Unlink all workstations in the domain:

Direct upgrade from V8.3 and 8.4
| From Tivoli Dynamic Workload Console

| From the Engine Selection Panel, select all workstations and click
| Unlink.
| a. Run a Status of all Domains plan list. The Status of all Domains
| table opens.
| b. Right-click the domain you want to unlink and select Unlink
| Workstations from the pop up menu.
| conman "unlink @;noask"
| 3. Stop the master domain manager:
| From Tivoli Dynamic Workload Console
| From the Engine Selection Panel, select all workstations and click Stop.
| a. Select the master domain manager workstation
| b. Right-click the workstation and select Stop from the pop-up menu.
| conman “stop;wait”
| 4. From the command line of the master domain manager, stop the netman
| process as follows:
| v On UNIX, run:
| conman “shut"
| Note: Do not use the UNIX kill command to stop Tivoli Workload Scheduler
| processes.
| v On Windows, run the shutdown.cmd command from the Tivoli Workload
| Scheduler home directory.
| 5. If you are upgrading from version 8.4, stop the SSM Agent as follows:
| v On Windows, stop the Windows service: Tivoli Workload Scheduler SSM
| Agent (for <TWS_user>).
| v On UNIX, run stopmon to stop the agent.
| 6. Verify that all services and processes are not running, as follows:
| v On UNIX, type the command:
| ps -u <TWS_user>
| batchman, writer, jobman, JOBMAN, stageman.
| v On Windows, type the command:
| <drive>\unsupported\listproc.exe
| where <drive> is the Tivoli Workload Scheduler home directory. Verify that
| the following processes are not running: netman, mailman, batchman, writer,
| jobman, stageman, JOBMON, tokensrv, batchup.
| Also, ensure that no system programs are accessing the directory or
| subdirectories, including the command prompt, and that in Windows
| Explorer the Administrative Tools→Services panel is not open.

| Direct 2: Upgrading the master domain manager

| This section describes how to upgrade a master domain manager.
| You can upgrade a master domain manager using the following installation
| methods:
| v “Upgrading a master domain manager or backup master using the installation
| wizard”
| v “Upgrading a master domain manager or backup master domain manager using
| the silent installation” on page 106
| Upgrading a master domain manager or backup master using the installation

| wizard: To upgrade a Tivoli Workload Scheduler master domain manager from
| version 8.3 or 8.4 perform the following steps.
| 1. Insert the installation DVD and run the setup for your operating system:
| v On Windows operating systems, WINDOWS\SETUP.exe
| v On UNIX and Linux operating systems, SETUP.bin.
| v Alternatively, start the launchpad as follows and select the Tivoli Workload
| On Windows systems
| from the root directory of the DVD run launchpad.exe.
| On UNIX systems
| From the root directory of the DVD run launchpad.sh.
| installation. Some fields might not apply to your upgrade depending on
| whether your old version is 8.3 or 8.4.
| Back up the previous Tivoli Workload Scheduler instance
| Select whether to back up the previous instance.
| Backup Destination Directory
| When you select to back up the previous instance, specify the directory
| where the backup is to be located.
| Backup profile destination directory
| The upgrade procedure performs a backup of your WebSphere®
| Application Server 6.0.2 (WAS) profile. Your current settings are
| transferred to the new WebSphere Application Server automatically. A
| default backup path is provided for you. If you want to save the profile
| to a different path, specify it in this field. Click Next.
| Tivoli Workload Scheduler user password
| Type the password of the Tivoli Workload Scheduler user for which
| you are upgrading the instance.
| WebSphere Application Server (WAS) authentication user name and
| password
| If you have changed the WebSphere Application Server (WAS)
| authentication user name and password from your previous
| installation, enter the new user name and password. If you have not
| changed these WebSphere Application Server values in your current
| installation, leave these fields blank.


| Applies only to version 8.3. The port used by the Secure Association
| Services (SAS) to listen for inbound authentication requests. The default
| value is 31119.
| Applies only to version 8.3. The port on which the Common Secure
| Interoperability Version 2 (CSIV2) service listens for inbound server
| authentication requests. The default value is 31120.
| Applies only to version 8.3. The port on which the Common Secure
| Interoperability Version 2 (CSIV2) service listens for inbound client
| authentication requests. The default value is 31121.
| ORB Listener
| Applies only to version 8.3. The port used for RMI over IIOP
| communication. The default value is 31122.
| Applies only to version 8.3. The administrative console port. The
| Applies only to version 8.3. The administrative console secure port. The
| Event Processor
| Applies only to version 8.3. This port is used by the event management
| feature. The default value is 31131. This port is not requested for
| backup master domain managers.
| RDBMS installation path
| Depending on the type of RDBMS you are using, specify the following
| information:
| For DB2:
| DB2 Server administrator user
| The user name of the administrator of the DB2 server instance.
| This user can also be any user having SYSADM or SYSCTRL
| authority on the DB2 server. On UNIX, verify that you are able
| to switch to this user and that it can load the DB2 environment.
| DB2 Server administrator password
| The password of the DB2 server administrator user, or of the
| user with SYSADM or SYSCTRL authority. You are asked to
| confirm the password.
| Note: The DB2 installation path will be discovered automatically by the

| upgrade procedure.
| If you have a DB2 Enterprise client installed on a UNIX platform,
| specify also the DB2 local client user name .
| For Oracle:
| Installation path
| Specify the path of an Oracle installation that satisfies the Tivoli
| Workload Scheduler prerequisites. The fully-qualified path must
| identify a tree in the Oracle structure that includes the sqlplus
| executable.

| Oracle Administrator User

| The name of the Oracle Administrator user
| Oracle Administrator user password
| The password of the Oracle Administrator user. You are asked
| to confirm the password.
| Tivoli Workload Scheduler database information
| Applies only when upgrading from version 8.3. Specify the following
| information needed to update the Tivoli Workload Scheduler database:
| For DB2:
| The name of the tablespace used to store event logs
| The path of the tablespace used to store event logs.
| Note: If you are upgrading from Tivoli Workload Scheduler version 8.3
| fix pack 1 or higher, the DB2 installation path will be discovered
| automatically by the upgrade procedure.
| For Oracle:
| Installation path
| Specify the path of an Oracle installation that satisfies the Tivoli
| Workload Scheduler prerequisites. The fully-qualified path must
| identify a tree in the Oracle structure that includes the sqlplus
| executable.
| Tivoli Workload Scheduler Oracle user password
| The password of the Tivoli Workload Scheduler Oracle user
| Create the Tivoli Workload Scheduler schema using the Oracle
| Partitioning option
| If you are upgrading version 8.3 on Oracle Enterprise Edition
| and have not implemented the Oracle Partitioning feature, you
| can do so at this point. Implementing this feature improves the
| performance of event-driven workload automation. Note that
| the partitioning option must already be installed into the Oracle
| instance. For information about event-driven workload
| automation, see Overview.
| If you are upgrading version 8.4, this option is not available
| because the database schema of the event-driven workload
| automation already exists. To implement the Oracle Partitioning
| feature, see Administration Guide.
| Tivoli Workload Scheduler report tablespace
| The path of the Oracle tablespace for Tivoli Workload Scheduler
| reports.
| Upgrading a master domain manager or backup master domain manager using

| the silent installation: To upgrade your Tivoli Workload Scheduler master
| domain manager or backup master domain manager instance, use one of the
| following response files:
| v TWS85_UPGRADE_MDM.txt
| v TWS85_UPGRADE_BACKUP_MDM.txt
| and follow the procedure described in “Performing a silent installation” on page
| 44.
| Direct 3: Customizing the optional final job stream

| If your old final job stream is called FINAL, a backup copy has been made of it in
| Sfinal.extract and it has been upgraded to V8.5. If it was customized, you must
| check that the customizations have been correctly upgraded. If it is not called
| FINAL, you must merge the functions of your old final job stream with the syntax
| of your new FINAL job stream. Depending on your situation, perform the
| following steps:
| If you had a customized job stream called FINAL in your database:
| Workload Console.
| 2. Edit the file Sfinal.extract with a text editor.
| 4. Save your new FINAL job stream.
| If you had a customized final job stream called something other than FINAL in
| your database:
| Workload Console.
| 2. Edit your old final job stream with composer or Tivoli Dynamic
| Workload Console.
| 3. Merge the two job streams so that your new final job stream has the
| same name and customizations as before (if you want to preserve the
| naming), plus the new required attributes from the new FINAL job
| stream.
| 4. Save your new final job stream.
| 5. Delete the old final job stream.
| If you had a final job stream called something other than FINAL in your
| database, but it is not customized:
| Workload Console.
| 2. Rename the new FINAL job stream with the name of your old final job
| stream with composer or Tivoli Dynamic Workload Console.
| If you had a final job stream called FINAL in your database, but it is not
| customized:
| Take no action because the FINAL job stream has already been edited by
| the installation or upgrade procedure.
| In all cases, now perform one of the following:

| v Run ResetPlan.
| v Use conman to delete your old final job stream instances and submit new
| instances to replace them.
| Note: You will run JnextPlan in “Direct 4: Completing the security configuration
| for the new environment.”
| Direct 4: Completing the security configuration for the new

| environment
| Version 8.5 includes new security statements for the event management and
| variable tables. If you have specific security settings in your V8.3 or V8.4
| environment, these settings must be manually merged with the new settings before

| you build the final security file to be used in your new environment. The
| Perform the following:

| 1. Log in as <TWS_user> on your upgraded master domain manager and set the
| Tivoli Workload Scheduler environment.
| 2. If you have centralized security enabled, extract the new security file on the

| 3. Edit the sec_file, and insert the following statements:
| If you are upgrading from V8.3, add the following statements:
| If you are upgrading from either environment, add the following statement:
| makesec sec_file
| 7. If you have centralized security, distribute the security file.
| 8. Run JnextPlan -for 0000 to distribute the Symphony file to the agents.
Upgrading backup master domain manager

Run upgrade wizard.
The procedure for upgrading a backup master domain manager is similar to the
procedure for upgrading a master domain manager. The only difference is that
when you upgrade a backup master domain manager, you do not have to perform
any database migration steps.
Upgrading agents and domain managers

This section describes how to upgrade agents and domain managers. Before you
upgrade agents, ensure you performed the procedure described in “Unlinking and
stopping Tivoli Workload Scheduler when upgrading agent workstations” on page
110. When the upgrade procedure is successful, it is not possible to roll back to the
previous version. Rollback is only possible for upgrades that fail. The following
describes the new directory structure and how to upgrade agents using the various
installation methods:
v “New directory structure” on page 109
v “Unlinking and stopping Tivoli Workload Scheduler when upgrading agent
workstations” on page 110
v “Upgrading agents using the installation wizard” on page 111
v “Upgrading agents using a silent installation” on page 112

v “Upgrading non-integratable agents using twsinst” on page 112

v “Upgrading non-integratable agents using Software Distribution” on page 114

| Program directory
| directory. The default location for the upgrade is /opt/ibm/TWA/TWS/.

| to default.


Unlinking and stopping Tivoli Workload Scheduler when

upgrading agent workstations
Before you perform an upgrade on an agent workstation ensure that all Tivoli
Workload Scheduler processes and services are stopped. If you have jobs that are
currently running, the related processes must be stopped manually or you must
wait until the jobs are complete.
Note: Do not use the UNIX kill command to stop Tivoli Workload Scheduler
processes.
To stop Tivoli Workload Scheduler processes and services, follow these steps:
1. Unlink the target workstation from the other workstations in the network. Or,
from the command line of the master domain manager, enter the following
command:
conman "unlink workstationname;noask"
2. Stop the target workstation. Or, from the command line of the master domain
manager, log in as <TWS_user> and enter the following command:
conman “stop workstationname;wait”
3. If you are upgrading from version 8.4, stop the SSM Agent as follows:
v On Windows, stop the Windows service: Tivoli Workload Scheduler SSM
Agent (for <TWS_user>).
v On UNIX, run stopmon to stop the agent.
4. Stop the netman process as follows:
v On UNIX, run:
conman “shut;wait workstationname"
v On Windows, from the Tivoli Workload Scheduler home directory, run the
shutdown.cmd.
5. If you are updating an agent, remove (unmount) any NTFS mounted directories
from the master domain manager.
6. If you are upgrading an installation that includes the connector, stop the
connector.
To verify if any services and processes are still running, perform the following
steps:

Unlinking and stopping Tivoli Workload Scheduler
v On UNIX, enter the command:

ps -u <TWS_user>
v On Windows, enter the command:
<drive>unsupported\listproc.exe
Verify that the following processes are not running: netman, mailman, batchman,
writer, jobman, stageman, JOBMON, tokensrv, batchup.
Also, ensure that there are no system programs accessing the directory or
subdirectories, including the command prompt. In Windows Explorer, the
Administrative Tools→Services panel must be closed.
Notes:
1. If you are upgrading in a Windows environment, the Tivoli Token Server
must be running.
2. Before you upgrade, make sure that the conman command line is not
running
| Upgrading agents using the installation wizard

| To upgrade an agent using the installation wizard, run setup for the operating
| system on which you are upgrading:
| Alternatively, start the launchpad as follows and select the Tivoli Workload
| Windows
| From the root directory of the DVD, run launchpad.exe.
| UNIX From the root directory of the DVD, run launchpad.sh.
| When the installation wizard is launched, follow the prompts to complete the
| upgrade.
| Upgrading an agent with connector using the installation wizard

| To upgrade a Tivoli Workload Scheduler version 8.3 or 8.4 agent with a connector
| using the installation wizard, run setup for the operating system on which you are
| upgrading:
| Windows
| Note: During the upgrade, you are prompted for the WebSphere Application
| Server administration user name and password.
| Follow the installation wizard panels to complete the installation. The following
| list describes the fields that you might need to complete during the installation.

Unlinking and stopping Tivoli Workload Scheduler
| Backup profile destination directory

| This information is needed to perform a backup of your WebSphere
| Application Server (WAS) profile. Your current settings are transferred to
| WebSphere Application Server automatically.
| Tivoli Workload Scheduler user password
| Enter the password of the Tivoli Workload Scheduler user for which you
| are upgrading the agent and connector instance. If you changed the
| WebSphere Application Server authentication user name and password
| from your previous installation, you must supply them here. If you did not
| change these values in your installation, leave these fields blank.
| The port on which the Common Secure Interoperability Version 2 (CSIV2)
| service listens for inbound server authentication requests. The default
| value is 31120.
| The port on which the Common Secure Interoperability Version 2 (CSIV2)
| service listens for inbound client authentication requests. The default value
| is 31121.
| ORB Listener
| The port used for RMI over IIOP communication. The default value is
| 31122.
| Upgrading agents using a silent installation

To upgrade an agent using a silent installation, follow the procedure described in
“Performing a silent installation” on page 44 with the appropriate response files:
v TWS85_UPGRADE_Agent.txt for a Tivoli Workload Scheduler 8.2.x, 8.3, or
8.4agent
v TWS85_UPGRADE_Connector.txt for a Tivoli Workload Scheduler 8.3 or 8.4
agent with connector
Upgrading non-integratable agents using twsinst

Use this procedure to upgrade non-integratable agents on all supported UNIX
operating systems. For information about non-integratable agents, see
“Non-integratable agents” on page 48. This procedure uses the command line
twsinst script to upgrade. Refer to http://www.ibm.com/support/
docview.wss?rs=672&uid=swg27012175 for a list of supported operating systems
and requirements.
To upgrade agents using the twsinst script, perform the following steps:
1. Insert the installation DVD according to the operating system. See “Installation
media” on page 26
2. Run the script from the directory <DVD_ROOT>/TWS/<operating_system>
3. Run the twsinst script as follows:

Upgrading non-integratable agents with twsinst
Upgrade an instance
twsinst -update -uname username
[-inst_dir install_dir]
[-backup_dir backup_dir]
[-nobackup_dir]
[-lang lang-id]
[-create_link]
[-skip_usercheck]
[-reset_perm]
-update
Upgrades an existing non-integratable agent installation .
-uname
The name of the user for which Tivoli Workload Scheduler is being
updated. The software is updated in this user’s home directory. This
user name is not to be confused with the user performing the upgrade.
-inst_dir
The directory of the Tivoli Workload Scheduler installation. This path
cannot contain blanks. If not specified, the path is set to the username
home directory.
-backup_dir
An alternative directory (which must be created manually) as the
destination for the backup copy of a previous version.
If you do not specify this option when running an upgrade, the
following default value is used:
$BACKUP_DIR = $INST_DIR_backup_$TWS_USER
where:
v $INST_DIR is the installation path (the user home directory on UNIX
and Linux).
v $TWS_USER is the user name.
For example:
$INST_DIR=/opt/TWS/TWS82
$TWS_USER=user82
$BACKUP_DIR=/opt/TWS/TWS82_backup_user82
$BACKUP_SUBDIR=/opt/TWS/TWS88_backup_user82/TWS82
In the backup directory you must also create a subdirectory to include

as the latest directory of the installation path.
-nobackup_dir
No backup is made.
-lang The language in which the twsinst messages are displayed. If not
specified, the system LANG is used. If the related catalog is missing,
the default C language catalog is used.
Note: The -lang option does not relate to the supported language
packs. By default, all supported language packs are installed
when you install using the twsinst script.
-create_link
| Create the symlink between /usr/bin/mat and /TWA/TWS/bin/at. See
Table 5 on page 25 for more information.
-skip_usercheck
Skip the check of the user in the /etc/password file or using the su

Upgrading non-integratable agents with twsinst
command. Enable this option if the authentication process within your

organization is not standard, thereby disabling the default
authentication option.
-reset_perm
Reset the permissions of the libatrc library.
For example, a sample twsinst script to upgrade a version 8.2 fault-tolerant
agent to a version 8.4 agent workstation:
./twsinst -update -uname <TWS_user>
Upgrading non-integratable agents using Software

Distribution
A number of Tivoli Workload Scheduler parameters are used by the software
package block to perform the upgrade. You can assign values to each variable to
reflect the installation that is being upgraded, otherwise the default value is
assigned.
When you upgrade agents using Software Distribution, the following variables are
required:
v install_dir
v tws_user
v pwd (This parameter is not required in a UNIX upgrade.)
v fresh_install
v upgrade
v from_release
To perform the upgrade, complete the following steps:

1. Create a software package profile that has the following name:
FP_TWS_operating_system_<TWS_user>.8.5.00
where: operating_system is the operating system where you are installing and
<TWS_user> is the user of the installation.
When you import the software package block, you must pass the name of the
profile to wimpspo so that the Configuration Manager endpoint catalogs the
name correctly.
2. Import the software package block using the wimpspo command.
3. Install the software package block using the wdinstsp command.
Note: When upgrading using the wdinstsp command, make sure to specify the
install_dir variable. If you installed the previous version in a directory
other than the default and you do not specify install_dir, Tivoli Workload
Scheduler is installed as a fresh installation.
For complete instructions on performing these tasks, refer to the IBM Tivoli
Configuration Manager, Reference Manual for Software Distribution and the IBM Tivoli
Configuration Manager, User’s Guide for Software Distribution.
Syntax
The following is an example of the settings required to upgrade a Tivoli Workload
Scheduler, version 8.2 fault-tolerant agent to Tivoli Workload Scheduler, version 8.5
on Windows and UNIX workstation. See “Software packages and parameters” on
page 50 for a description of the parameters.

Upgrading using Software Distribution
Windows
The following Windows example describes an installation with the user
<TWS_user> and the endpoint Tivoli_TWS_WINDOWS.
wdinstsp -f -uy -D install_dir=″C:\ibm\TWS\twsuser\TWS″ -D
from_release=″8.4″ -D tws_user=″twsuser″ -D password=″twspasswd″ -D
company=″company_name″ -D this_cpu=″cpu_name″ -D
master_cpu=″MTMDM″ -D fresh_install=″false″ -D upgrade=″true″ -D
tcp_port=″33311″ -D domain=″domain_name″ -n
″FP_TWS_WINDOWS_twsuser.8.5.0.00″ ″C:\Output\TWS_VLAST\
WINDOWS\Tivoli_TWS_WINDOWS.SPB″
UNIX The following UNIX example describes an installation with the user
<TWS_user> and the endpoint Tivoli_TWS_LINUX_I386
wdinstsp -f -uy -D install_dir=/home/twsuser/TWS -D from_release=8.4
-D tws_user=twsuser -D company=company_name -D this_cpu=cpu_name
-D master_cpu=MTMDM -D fresh_install=false -D upgrade=true -D
tcp_port=33311 -n FP_TWS_WINDOWS_twsuser.8.5.0.00
/mnt/gsa/home/s/l/user1/web/public/SPB_INSTALL/LINUX_I386/
Tivoli_TWS_LINUX_I386.SPB

Upgrading using Software Distribution
| Upgrading a command line client

| This section describes how to upgrade a command line client.
| To upgrade a Tivoli Workload Scheduler version 8.3 or version 8.4 command line
| client using the installation wizard, run the setup for the operating system on
| which you are upgrading:
| Windows
| When the installation wizard is launched, follow the prompts to complete the
| upgrade.
| To upgrade a command line client using the silent installation, follow the
| procedure described in “Performing a silent installation” on page 44 using the
| TWS85_UPGRADE_CLI.txt response file.

Chapter 6. Configuring
This chapter describes configuring after the installation is complete. It is divided
v “Setting the environment variables”
v “Configuring a master domain manager”
v “Configuring a backup master domain manager” on page 118
v “Configuring an agent” on page 119
v “Configuring a command line client” on page 120
v “Configuring WebSphere Application Server” on page 120
Setting the environment variables

| Before you configure your Tivoli Workload Scheduler components, you must set
| the environment variables.
On Windows operating systems, run the tws_env.cmd shell script to set up both
the PATH and TWS_TISDIR variables. For example, if Tivoli Workload Scheduler is
installed in the c:\Program Files\ibm\TWA\TWS directory, the PATH variable is set
as follows:
c:\Program Files\ibm\TWA\TWS;c:\Program Files\ibm\TWA\TWS\bin
Note: If you have more than one version of Tivoli Workload Scheduler installed on
your computer, make sure TWS_TISDIR points to the latest one. This
ensures that the most recent character set conversion tables are used.
On UNIX and Linux operating systems, source the tws_env shell script to set up
both the PATH and TWS_TISDIR variables. For example, if Tivoli Workload
Scheduler is installed in the default directory /opt/ibm/TWA/TWS directory,
tws_env.sh sets the variables as follows:
PATH=/opt/ibm/TWA/TWS:/opt/ibm/TWA/TWS/bin:$PATH
export PATH
TWS_TISDIR=/opt//opt/ibm/TWA/TWS
export TWS_TISDIR
The tws_env script has two versions:

v tws_env.sh for Bourne and Korn shell environments
v tws_env.csh for C Shell environments
Configuring a master domain manager

After you have installed a master domain manager, if you did not select to
automatically add the final job stream during installation and want to do so,
follow the steps in this section to add the final job stream to the database and run
JnextPlan. This job stream is placed in production every day and runs JnextPlan
prior to the start of a new day. The installation creates the FINAL file in the
| /TWA/TWS directory on your workstation containing the final job stream definition.
You can use FINAL or create and customize a new file. See Tivoli Workload Scheduler:
User's Guide and Reference for details about customizing the final job stream.

Configuring a master domain manager
The following is an example of how to configure a master domain manager after

installation:
1. Log in as <TWS_user>.
2. Set the environment variables. See “Setting the environment variables” on page
117.
3. Run the composer command.
4. Add the final job stream definition to the database by running the following
command:
add FINAL
where FINAL is the name of the file containing the definition of the Final job
stream.
5. Exit the composer command line.
6. Run the JnextPlan job:
JnextPlan
You can automate this step after installation. See Tivoli Workload Scheduler:
User's Guide and Reference.
7. When JnextPlan completes, check the status of Tivoli Workload Scheduler:
conman status
If Tivoli Workload Scheduler started correctly the status returned by the

command is Batchman=LIVES.
8. Raise the workstation limit value to allow jobs to run. The default job limit
after installation is 0, so no jobs are permitted to run at a time. Raise the job
limit to allow jobs to run, for example to 10 jobs:
conman "limit ;10"
If no workstation name is specified for the limit command, the default value is
the current login workstation.
Note: If priority of jobs is equal to HI (100) or GO (101), they will disregard the
limit and run despite a limit=0, unless fence>=priority.
| Additionally, the following configuration procedures might be necessary. For

| information about these procedures, see Tivoli Workload Scheduler: Administration
| Guide.
| v Customizing and configuring global, local, and user options
| v Customizing and configuring user authentication to allow users authorization on
| actions and objects, and to configure LDAP
| v Setting connection security to enable SSL for inter-component communications
Configuring a backup master domain manager

After you have installed a backup master domain manager, perform the following
configuration steps:
1. Log in as <TWS_user> on your master domain manager
2. Add the backup master username and password to the useropts file. See Tivoli
Workload Scheduler: User's Guide and Reference.
3. Set the environment variables by running tws_env

Configuring a backup master
4. Define the backup master as a full status autolink fault-tolerant agent in the
Tivoli Workload Scheduler database, using the composer command interface or
the Job Scheduling Console. In this example using composer :
composer
new
5. Type the workstation definition in the text editor, for example:
cpuname DM1
os UNIX
node domain1
description "Fault-tolerant Agent"
for Maestro
type FTA
autolink on
end
For more information about workstation definitions, refer to the Tivoli Workload
Scheduler Reference Guide.
6. Run JnextPlan -for 0000 to include the backup master workstation in the plan
and to send the Symphony file to it.
7. Change the workstation limit to allow jobs to run on the workstation. For
example, set the number of jobs to run concurrently on the workstation to 10:
composer "limit DM1;10
Note: If you are logged into the backup master, DM1 is not required.

| Guide.
Configuring an agent
After installing an agent, define the workstation in the database and link the
workstation from the master. You can perform this task by using the Job
Scheduling Console or the command line interface. Refer to the Tivoli Workload
Scheduler Job Scheduling Console User’s Guide for information. The following is an
example of how to configure an agent after installation using the command line
interface:
1. Log in to the master domain manager as <TWS_user>.
2. Set the environment variables by running tws_env.sh.
3. Create the workstation definition in the Tivoli Workload Scheduler database.
Open a command line window and enter the following commands:
composer
new
4. Type the workstation definition in the text editor. For example:
CPUNAME F235007_00
DESCRIPTION "fault tolerant agent"
OS UNIX
NODE lab235007
TCPADDR 31111
DOMAIN MASTERDM
FOR MAESTRO
Chapter 6. Configuring 119

Configuring an agent
TYPE FTA
AUTOLINK ON
BEHINDFIREWALL OFF
FULLSTATUS OFF
END
Run JnextPlan with the option -for 0000 to add the agent workstation definition
to the plan and to send the Symphony file to it. For more information about
workstation definitions, refer to the Tivoli Workload Scheduler Reference Guide.
5. If you set the autolink parameter to OFF, issue the link command from the
master domain manager to link the agent and to download the Symphony file
to it:
conman “link workstation”
6. Change the workstation limit to allow jobs to run on the workstation. For
example, set the number of jobs to run concurrently on the workstation to 10:
composer "limit F235007_00;10

| Guide.
| Configuring a command line client

| The following configuration procedures might be necessary for a command line
| client. For information about these procedures, see Tivoli Workload Scheduler:
| Administration Guide.
| v Customizing and configuring global and local options
Configuring WebSphere Application Server

| If, after installing, you have more than one instance of WebSphere Application
| Server managing any Tivoli Workload Automation products, you must ensure that
| they have the same LTPA token_keys. See the Tivoli Workload Scheduler:

Chapter 7. Uninstalling
This chapter describes how you uninstall Tivoli Workload Scheduler. It is divided
v “Uninstalling using the wizard”
v “Performing a silent uninstallation” on page 122
v “Uninstalling agents using the twsinst script” on page 122
v “Uninstalling using the Software Distribution CLI” on page 123
v “Uninstalling a command line client” on page 124
The uninstaller program is created during the install procedure. Wherever possible,
use the same method you chose to install the product when uninstalling the
product. For example, if you installed the product using the installation wizard,
use the uninstaller program to subsequently remove the product.
Uninstalling the product does not remove files created after Tivoli Workload
Scheduler was installed, nor files that are open at the time of uninstall. If you do
not need those files, you have to remove them manually. If you intend to reinstall
and need to use the files, make a backup before starting the installation process.
The uninstallation does not remove your DB2 or Oracle database.
Notes:
1. The Tivoli Workload Scheduler engine is a prerequisite for other products and
features you can install, such as Tivoli Workload Scheduler for Applications
and the connector. Before you uninstall the engine, uninstall all the additional
features.
2. Refer to the Tivoli Workload Scheduler: Administration Guide for information about
removing Tivoli Workload Scheduler manually.
Uninstalling using the wizard

The uninstaller program removes product files, registry keys, and services. It
removes the binaries related to the Tivoli Workload Scheduler agent installed, the
distributed connector, and the language packs.
To uninstall Tivoli Workload Scheduler, perform the following steps:

1. Ensure that all Tivoli Workload Scheduler processes and services are stopped,
and that there are no active or pending jobs. For information about stopping
the processes and services see Administration Guide.
| 2. Navigate to the twshome path.
3. Run the uninstall script:
v On Windows operating systems:
uninstaller.exe
v On UNIX and Linux operating systems:
./uninstall.bin
4. Select the Tivoli Workload Scheduler instance you want to uninstall:
v If you are uninstalling a master domain manager, the wizard removes the
selected instance and any additional feature installed for that instance. Note
that if you are uninstalling from an integrated Tivoli Workload Automation,

the embedded WebSphere Application Server is not removed. Only Tivoli

Workload Scheduler applications are removed
v If you are uninstalling an agent, you can choose if you want to uninstall the
connector only, or both the agent and connector simultaneously.
For UNIX and Linux operating systems, uninstall is performed in the language of
the locale and not the language set during the installation phase. If you want to
uninstall agents in a language other than the locale of the machine, use the twsinst
script as follows:
| </TWA/TWS>./twsinst -uninst -uname <user_name> -lang <language>
where language is the language of the uninstallation. For a detailed description of

all the available parameters for the twsinst script, see “Uninstalling agents using
the twsinst script.”
Performing a silent uninstallation

For a silent uninstallation of a master domain manager or backup master domain
manager, perform the following steps:
| 2. Navigate to the /TWA/TWS/_uninstall path.
3. Enter the following command:
v On Windows operating systems:
uninstaller.exe -silent
v On UNIX and Linux operating systems:
./uninstall.bin -silent
For a silent uninstallation of an agent, a connector, or both, perform the following

steps:
and that there are no active or pending jobs.
| 2. Copy the TWS85_UNINSTALL_Agent.txt response file from the installation DVD
in the \tws\responsefiles\ directory to a local directory and edit it as
appropriate.
3. Save the file with your changes.
| 4. Navigate to the /TWA/TWS/_uninstall path.
| 5. Enter the following command:
| v On Windows operating systems:
| uninstaller.exe -options <local_dir>\TWS85_UNINSTALL_Agent.txt -silent
| v On UNIX and Linux operating systems:
| ./uninstall.bin -options <local_dir>/TWS85_UNINSTALL_Agent.txt -silent
Note: If you want to reinstall after performing a silent uninstallation, you must
first close and reopen the shell to correctly reset the environment variables.
Uninstalling agents using the twsinst script

Follow these steps to uninstall Tivoli Workload Scheduler agents using the twsinst
script. Note that only agents installed using twsinst can be uninstalled using
twsinst.

Uninstalling using the twsinst script
| 2. Log in as root and change your directory to <installation_path>/TWA/TWS
3. From the TWS directory, run the twsinst script as follows:
twsinst -uninst -uname <username>
[-lang <lang_id>]
[-skip_usercheck]
-uninst
Uninstalls Tivoli Workload Scheduler.
-uname <username>
The name of the user for which Tivoli Workload Scheduler is uninstalled. This
user name is not to be confused with the user performing the uninstallation
logged on as root.
-lang <lang_id>
The language in which the twsinst messages are displayed. If not specified,
the system LANG is used. If the related catalog is missing, the default C
language catalog is used.
Note: The -lang option is not to be confused with the Tivoli Workload
Scheduler supported language packs.
-skip_usercheck
Skip the check of the user in the /etc/password file or using the su command.
The following is an example of a twsinst script that uninstalls the Tivoli Workload
Scheduler agent, originally installed for user named twsuser:
./twsinst -uninst -uname <TWS_user>
Uninstalling using the Software Distribution CLI

You can uninstall Tivoli Workload Scheduler using a Software
Distribution/Configuration Manager command. To uninstall a software package
from a disconnected target, use the command wdrmvsp. Tivoli Workload
Scheduler uses the disconnected catalog.
Ensure that all Tivoli Workload Scheduler processes and services are stopped, and
that there are no active or pending jobs. For information about stopping the
processes and services see Administration Guide.
For example, to uninstall on UNIX, perform the following:

conman "stop;wait"
conman "shut;wait"
Ensure all processes are down.
As root:
cd <twshome>/_uninstall/CLI. ./swd_env
To display package names and versions: wdlssp
wdrmvsp -f packagename.version
Chapter 7. Uninstalling 123

Uninstalling using the Software Distribution CLI
The software package block that installs language packs can also be removed in
this way. Refer to Administration Guide for information about removing Tivoli
Workload Scheduler manually.
Uninstalling a command line client

You can uninstall a command line client using the uninstallation wizard or by
performing a silent uninstallation. To uninstall a command line client perform the
following steps:
1. Navigate to the CLI_home/_uninstall path, where CLI_home is the installation
path of your command line client .
2. To uninstall using the wizard, run the uninstaller command:
On Windows operating systems:
uninstaller.exe
On UNIX and Linux operating systems:
./uninstall.bin
Note: For a silent installation, use the -silent flag.

Chapter 8. Troubleshooting installation, migration, and
uninstallation
This chapter describes issues dealing with the installation, removal, and
configuration of IBM Tivoli Workload Scheduler and its prerequisites. It is divided
into the following topics:
v “Log files of installation processes”
v “Recovering a failed interactive InstallShield wizard installation”
v “Recovering a failed silent InstallShield wizard installation” on page 135
v “Recovering a failed upgrade” on page 136
v “Problem scenarios: install, reinstall, upgrade, migrate, and uninstall” on page
136
v “Security implications of the installation” on page 165
v “Verifying the installation” on page 165
v “Uninstalling Tivoli Workload Scheduler manually” on page 166
v “Uninstalling Tivoli Workload Scheduler connectors manually” on page 171
v “Removing Windows registry keys” on page 173
For information on issues about the DB2 installation, see the DB2 product
documentation.
| Log files of installation processes

| Log files of the installation processes have a different naming convention,
| depending on the installation method. For information about the different log files
| associated with the different installations, see “Installation log files” on page 255.
| Packaging log files for support

| If a problem occurs with an installation that you cannot resolve, IBM Software
| Support might ask you to send them all of the installation log files. Include the
| following:
| v For Tivoli Workload Scheduler, all of the files and subdirectories in the
| <tempDir>/TWA/tws85 directory.
| v For Tivoli Dynamic Workload Console, all of the files and subdirectories in the
| or the <tempDir>/TWA/tdwc85 directory.
| v The software package block log files.
| v The DB2 installation log.
| v The installation log of the embedded WebSphere Application Server.
| Note: Do not remove, add, or modify files in the <tempDir>/TWA/tws85 directory

| because this might cause an installation to fail, or prevent the recovery of a
| failed installation.
| Recovering a failed interactive InstallShield wizard installation

| This section describes how to recover a failed interactive installation.

Recovering failed installation with wizard
| If an operation fails during the installation, the wizard opens the following panel:
|
|
|
| Figure 7. Wizard panel after an installation failure
|
| Note: If you are using the interactive wizard, do not close the wizard panel by
| clicking on the Close icon: . If you do, the wizard is unable to save the
| troubleshooting information that you need for a resume. Instead, if you are
| sure you want to quit the installation, click Quit installation.
| You can use the debug mode of the wizard to see which steps of the installation
| have failed. You can correct errors that have occurred and resume those installation
| steps that have not completed successfully, without leaving the wizard.
| You can choose to do this immediately the failure occurs, or close the window and
| recover the situation later.
| The procedure is described in the following sections:

| v “The Step List window”
| v “The Step window” on page 128
| v “Correcting a failed step and continuing the installation” on page 131
| v “Deciding whether to resume the wizard or rerun it” on page 132
| v “Deciding whether to resume immediately or exit and resume later” on page 133
| v “Stopping and resuming an interactive installation” on page 134
| v “Example procedure for resolving a problem” on page 135
| The Step List window

| The Step List window opens either when an installation fails, or when you are
| resuming an installation that had previously been stopped (see “Stopping and
| resuming an interactive installation” on page 134). Figure 8 on page 127 shows an
| example of the Step List window when an installation step has failed:
|

|
| Figure 8. Step List window showing a failed step
|
| The Step List window is organized as follows:
| Step # The installation sequence.
| Description
| The description of the installation step. The steps of the Tivoli Workload
| Scheduler installation are described in Chapter 4, “Installing,” on page 31.
| Target The workstation where the installation is being run.
| Status The step status. It can be one of the following:
| Ready The step is ready to be installed.
| Success
| The step has successfully completed.
| Error The step completed, but errors were detected.
| Held A step that prerequisites another step has failed. Do not set this
| state.
| Run next
| Start the next step in the list that has a status set to Ready.
| Run all
| Start, in sequence, all the steps in the list that have a status set to Ready.
| Stop Use this to stop the step processing while a step is being processed. The
| step returns to the Ready status.
| Stop on error
| If selected, stops the processing of any step or steps that you run in the
| event of an error.
| Search by status
| Select the status you want to view, then click Search. The step list displays
| the first step in the step list with the selected status.
Chapter 8. Troubleshooting installation, migration, and uninstallation 127

| Status
| The status of the installation processing engine. It can be one of the
| following:
| Waiting
| User action is required.
| Running
| Installation of a step is in progress.
| Stopping
| After the current step, the engine stops.
| Searching
| The engine is searching for product images.
| Details
| For each status, shows the number of steps in that status. Also displays the
| total number of steps.
| For information about each individual step, double-click the step to open the Step
| window.
| The Step window

| If you double-click a step in the Step List window, The Step window opens. It has
| three tabs:
| Status tab
| The Status tab shows the status of the installation step (Ready, Success, Error, or
| Held). You can change the status from Error to Ready if the condition that caused
| a step to fail has been removed. This is an example of the tab:
|
|
|
| Figure 9. Step status tab
|
| Properties tab
| The Properties tab gives the user parameters required by the step. These might be
| the parameters you have input in the installation wizard, or values that the wizard
| has determined according to the logic of its operations. This is an example of the
| tab:
|

|
| Figure 10. Step properties tab
|
| For example, in this tab the property DB2 Client Flag is an internal property
| determined by the wizard.
| The properties are of three types:

| A command
| Some of the steps have properties that include a command string. This
| must never be edited. The command string has positional parameters and
| generated parameters. If you change even one character the command
| might fail.
| Editable parameters
| These are parameters that are used by the step, but can be edited by you.
| The name of the parameter is the same as the name used on the wizard
| panel when you input the data.
| Internal parameters
| These are parameters generated by the wizard. They are recognizable
| because you did not input them in the wizard panels. For example, the DB2
| Client Flag in the above example screen is an internal flag which tells the
| step whether it is to install the DB2 Server or DB2 Client. These must never
| be edited. They might be linked to other parameters in a way that is not
| obvious to you.
| Output tab
| The Output tab shows the output and any errors that occurred for the installation
| step, and also the commands that were performed by the installation. This is an
| example of the tab:
|

|
| Figure 11. Step output tab
|
| The Output tab has the following entries:
| Time Stamp
| The time that the command was run.
| Return code
| The return code for the operation:
| 0 OK
| 1-9 Error

| DiagRecord
| A unique point of failure identification. This can be quoted to IBM
| Software Support if you need to request assistance.
| Command
| The command that failed.
| Command output
| Any output from the command (such as a return code or an error message
| number)
| Error log
| Shows a list of errors that occurred during the installation of the step.
| Correcting a failed step and continuing the installation

| To correct a failed step and continue the installation, use the following procedure:
| 1. Use the Output tab to determine what problem occurred.
| 2. Consult the sections in this guide that describe how to resolve problems found
| with the installation or the help for the error message that has been displayed.
| 3. If the solution to the problem requires you to change one of the values that you
| entered in the installation wizard, consult “Deciding whether to resume the
| wizard or rerun it” on page 132 and determine from the guidelines there, if you
| should rerun the wizard from scratch, or if it is appropriate to correct the value
| and resume the wizard. If the latter, follow this procedure:
| a. Select the Properties tab and make the required changes. Click Apply.
| The error description might make reference to a property that is not
| available for editing in the step that failed. In this case you must do the
| following:
| 1) Close the Step window.
| 2) Double-click the preceding step and check if the Properties tab contains
| the property you require. If it does not, then close the Step window and
| try the next preceding step; continuing until you locate the property to
| change.
| When you find the property, change its value and then continue with
| the rest of the steps in this procedure, from the step that you have modified,
| not from the step that failed.
| b. Double-click each of the other steps in the installation in turn and click the
| Properties tab for the step. If the step includes the property whose value
| you changed above, change the value of the property accordingly and click
| Apply. This is necessary because the step properties are not interlinked.
| c. For each modified step, lick the Status tab, change the Status to Ready, then
| click Apply. The Step list is redisplayed.
| 4. If instead, the solution to the problem does not require you to change any of
| the values that you entered in the installation wizard, resolve the problem
| outside the wizard, then change the Status to Ready and click Apply. The Step
| list is redisplayed.
| 5. Determine which is the earliest step in Ready status.
| 6. If you want to run just the first step in Ready status, to ensure, for example,
| that the change you made has worked, click Run next. This runs the first step
| in the step list (in step number order) with a status of Ready. When the step
| finishes successfully you run the other steps in the installation in the same way,
| in sequence, or use Run all.

| 7. To resume the installation in one go, click Run all. The wizard attempts to
| complete all outstanding steps, starting with the first step in Ready status.
| Deciding whether to resume the wizard or rerun it

| The fact that the wizard has a facility that allows you to diagnose the problem,
| correct it, and resume it, does not mean that you must do so. There are a number
| of scenarios when it is quicker to rerun the wizard, or you are more sure of success
| by doing so. This section helps you to decide which is the best action to take.
| Note: Diagnosing and resuming a failed installation is a process that must be

| guided, either by following the instructions in the sections that follow in this
| manual, or by following instructions from IBM Software Support.
| The facility to diagnose, correct, and resume a failed installation can be very
| useful for you, but if it is not done correctly can require more work than
| simply rerunning it.
| The following sections detail different installation scenarios and suggest the best
| way to proceed.
| Installing an agent or the command line client

| If you are installing an agent or the command line client, it is always easier to
| rerun, rather than resume, a failed installation. This is because the steps are few,
| and can all be rerun.
| Installing a master domain manager, a backup master domain

| manager, or the connector
| If you are installing a master domain manager, a backup master domain manager,
| or the connector, you must follow these guidelines:
| Reason for failure: Consider the reason for failure and what is needed to fix the
| problem:
| External reason
| If the wizard has failed for an external reason, that you can correct, you
| can always resume from the failed step.
| For example, in an installation of the master domain manager, the database
| support that you chose in the wizard must be running during the
| installation. When you supply the information to identify the RDBMS
| instance, the wizard checks that it is running and gives an error if not.
| However, if the RDBMS support stops running for any reason, after the
| wizard has checked it is running, but before the wizard starts to install the
| Tivoli Workload Scheduler database, the wizard stops. To resolve the
| problem, restart the RDBMS support and resume the installation from the
| failed step.
| Non-valid installation data
| If the wizard fails because data supplied to the wizard is not valid, you
| must consider which data is not valid:
| <TWS_user> ID or password
| If there are any problems with the <TWS_user> ID or password,
| you must quit the installation and rerun it. Many of the steps have
| the <TWS_user> as a property, and because many crucial factors in
| the installation are linked to the <TWS_user>, you must not try to
| change the ID and then resume.

| Installation directory
| Like the <TWS_user> ID, this is important to the installation. If the
| supplied value has some problem you must quit the installation
| and rerun it.
| Ports The ports used by the embedded WebSphere Application Server
| are checked at the moment you input them, but if one of them
| becomes busy by the time the wizard starts to configure the
| embedded WebSphere Application Server, the installation stops. In
| this case, you can proceed to change the value of the port being
| used in the step and resume the installation, because the ports are
| only used in one step.
| Database data
| The data relating to the configuration of the RDBMS support and
| the installation of the Tivoli Workload Scheduler database might be
| used in any or all of the database-related steps. Look at the names
| of the steps to determine which they are. If you change a value in
| one, open them all and check if the value is used in others.
| Other data
| For all other installation data, check every step to determine where
| the data item is being used.
| If in doubt, rerun the installation.
| Where is the problem: Follow these guidelines depending on where, in the

| installation, the problem occurs:
| Early steps
| Generally, if the problem occurs in one of the early steps, it is almost as
| quick, and generally more reliable, to rerun the installation, than correct
| the data and resume it.
| After the database has successfully been installed
| If the problem occurs after the database has been successfully installed, but
| you want to rerun the installation, or resume from some point before the
| database configuration steps, there is no need to drop or uncatalog the
| database because the wizard finds the existing database and continues.
| Cleaning up before a rerun: If you decide to rerun, there should be no need to

| clean up anything. All the data structures that are installed can be overwritten.
| Deciding whether to resume immediately or exit and resume

| later
| If you decide to diagnose, correct, and resume the wizard, you can choose to do it
| immediately, or to quit the installation and resolve the problem later:
| Diagnose failure
| If you choose to diagnose the failure immediately, the Step List window is
| opened. See “The Step List window” on page 126 for more details.
| Quit installation
| If you select to quit the installation, a summary of the progress of the
| installation is displayed, and the InstallShield wizard is closed.

| You can discover the reason for the failure by looking in the installation
| log files, correct the problem, and later perform a restart of the installation
| using the resume option, see “Stopping and resuming an interactive
| installation.”
| Note these considerations:
| v Do not close the panel by clicking on the Close icon: . If you do, the wizard
| is unable to save the troubleshooting information that you need for the resume.
| Instead, if you are sure you want to quit the installation, click Quit installation.
| v You can only resume the most recent installation attempt regardless of the
| component it was installing. Every time you click Next on the Summary panel
| when running an installation of any component, any previous troubleshooting
| information about a previous installation of any component is overwritten. If
| you want to be able to resume multiple installations on the same computer, back
| up the entire <tempDir>/TWA/tws85 directory after each installation attempt has
| stopped, and then, for each installation you need to resume, restore this data
| from the backup and resume the installation.
| Stopping and resuming an interactive installation

| You can stop and resume an installation at any time. For example:
| v The installation is running successfully but you want to pause it and resume it
| later
| v The installation has failed and you want to reboot the computer to correct a
| problem
| To stop an interactive installation that is running click Stop. The wizard asks you if
| you want to quit the installation after the current step is completed. If you reply
| Yes, the installation completes the step being performed and then displays a
| summary panel of the completed activities. Click Finish to exit.
| To stop an installation that has just failed, select Quit installation, click Next, and
| confirm your decision.
| To stop an installation that is on the Step List window, click Cancel, and confirm
| your decision.
| To resume the installation, enter the following command:
| <setup_file_name> -resume
| where <setup_file_name> is one of the following:

| Windows setup.exe
| UNIX SETUP.bin
| The InstallShield wizard recognizes that a previous installation has not completed,
| and the Step List window opens. From here you can continue the previous
| installation at the point where it stopped. If the steps in the Step List window have
| no errors, you can resume the installation; otherwise you must correct the error
| that caused the installation steps to fail, before resuming those steps. See “The Step
| List window” on page 126 for details.

| Example procedure for resolving a problem

| This section describes an example procedure for resolving a problem and finishing
| the installation.
| Assume that you are upgrading an existing instance of Tivoli Workload Scheduler
| version 8.3, using DB2, and the "Configure the Tivoli Workload Scheduler instance"
| step has failed. This could be for a number of reasons. The procedure for resolving
| the problem starts when the installation stops and the Diagnose Failure window
| opens (see Figure 7 on page 126).
| 1. On the Diagnose Failure window, select Diagnose failure and click Next. The
| Step List window opens (see Figure 8 on page 127).
| 2. Double-click the step that failed, in this case the "Configure the Tivoli Workload
| Scheduler instance" step.
| 3. Click the Output tab (see Figure 11 on page 130) and determine the cause of
| the problem.
| 4. Fix the problem. For this scenario it is assumed that the workstation name that
| you originally supplied to the installation wizard is not valid. Click the
| Properties tab and change the workstation name to a valid value. Click Apply.
| 5. Change the Status on the Status tab (see Figure 9 on page 128) to Ready, and
| click Apply. The Step List window opens again. This time the status of all the
| steps yet to be performed is set to Ready.
| 6. Double-click the other steps in turn and click their Properties tab. If you find
| the workstation name field, change the value as you did for the failed "Configure
| the Tivoli Workload Scheduler instance" step. Click Apply.
| 7. In this case, the steps that you changed have not yet been run, so the earliest
| step you changed is also the step that failed. The status of this step is already
| set to "Ready", so there is nothing further to do.
| 8. When you have checked the properties for the affected steps, click Run all. The
| installation wizard resumes and completes the installation.
Recovering a failed silent InstallShield wizard installation

If the silent wizard stops, follow this procedure:
1. Open the installation log and establish at what point the installation failed. The
location of the installation log files is described in “Installation log files” on
page 28.
The installation is performed in two distinct phases:
Validation phase
The input parameters are validated, but no installation action is taken.
In the log file the validation of the input parameters is indicated by the
action: validateFields.
Step execution phase
The installation is performed in a series of steps. In the log, each step
starts with a message that begins "Running step:".
2. When you have discovered what the problem is, and in what phase it started,
determine how to resolve it. You might have to correct a parameter or change
something in the installation environment (for example, create more disk
space).

Recovering a failed silent installation
3. When you have resolved the problem, you can rerun or resume the wizard. To
determine which you should do, see “Deciding whether to resume the wizard
or rerun it” on page 132. Follow these instructions for how to proceed after
making the decision:
Rerun the wizard
You must rerun the wizard if the error was found in the Validation phase.
If the wizard was in the Step execution phase you can always rerun it,
but you must consider that the wizard attempts to redo each step.
Thus, you might need to clean up the installation environment after the
failed installation before rerunning it.
If you need to change an input parameter, edit the response file. Then
rerun the wizard, just reissuing the silent wizard command as you
issued it originally.
Resume the wizard
You can only resume the wizard if the error was found in the Step
execution phase. The resume option uses the interactive wizard. You
cannot resume the wizard silently, because an interaction is required to
resume the failed step.
To resume the wizard, reissue the silent wizard command as you issued
it originally, with these changes:
v Add the parameter -resume
v Remove the parameter -silent when you ran it originally. If you do
not remove this parameter, the installation cannot resume.
The Step list window of the interactive wizard is displayed, where you
can optionally change the values of the data input parameters, and
resume the installation at the failed step. See “The Step List window”
on page 126, and follow the instructions in that section.
Recovering a failed upgrade

In the case of a failed upgrade, contact IBM Software Support.
Problem scenarios: install, reinstall, upgrade, migrate, and uninstall

This section contains known problem scenarios that could occur with the install,
reinstall, upgrade, migrate, and uninstall of Tivoli Workload Scheduler
components. It is divided into these topics:
v “Problems installing on Windows” on page 137
v “Problems installing on UNIX” on page 143
v “Problems installing on HP-UX” on page 144
v “Problems installing on Sun Solaris” on page 145
v “Problems installing on Linux” on page 145
v “Problems with the silent installation” on page 146
v “Problems with installations using the twsinst script” on page 146
v “Problems installing the application server” on page 146
v “Other installation problems” on page 147
v “Upgrade problems” on page 155
v “Migration problems” on page 158
v “Uninstallation problems” on page 162

Problem scenarios
v “Fix pack installation problems” on page 164
Problems installing on Windows

The following sections describe problems that could occur when installing on
Windows, and their workarounds:
v “An installation on Windows fails.”
v “The installation fails on Windows because of Autotrace.”
v “Installation fails because the host name is truncated” on page 138
v “An InstallShield wizard installation fails with the message "CMW3202E
Command failed."” on page 138.
v “The InstallShield wizard commit step fails on Windows with AWSDEQ024E
error” on page 139.
v “The installation on Windows receives the warning AWSGAB005W” on page
139.
v “On a Windows 2003 domain, the application server installation fails with an
apparent credentials problem but the credentials are correct” on page 140
v “The user account is not created on Windows 2000 with system error 56b” on
page 140
v “The user account is not created on Windows - create it manually” on page 140.
v “User account-related issues for Windows 2003” on page 141.
v “The Windows services fail to start after installation” on page 142
An installation on Windows fails

You have tried to install the product using the InstallShield wizard on a Windows
workstation, but the installation has failed.
Cause and solution
A possible cause of a failure of an InstallShield wizard installation on Windows is

that the Services window of the Administrative Tools in the Control Panel is open.
This is because, with the window open, the Services registry cannot be updated.
Close the Services window and do one of the following:

v If you have selected the wizard option to recover a failed installation by
rerunning the step that failed, you can now set the status of that step to ″Ready″
and resume the step (see “Recovering a failed interactive InstallShield wizard
installation” on page 125)
v If you have completely stopped the installation, you can resume it (see
“Stopping and resuming an interactive installation” on page 134).
The installation fails on Windows because of Autotrace

An installation on a Windows operating system fails because of a problem
installing Autotrace.
Cause and solution
Autotrace might already be installed on the target workstation, in the target

location, and at the latest version, probably as a result of a previous installation of
Tivoli Workload Scheduler. Normally, the installation process recognizes this
installation and skips the step of upgrading Autotrace. However, it has been
known for the installation process to stop with an error apparently indicating that
the Autotrace installation has failed, even though the correct version is in place.

Installing on Windows
If the Autotrace installation fails, check that Autotrace is at the correct version; see
Tivoli Workload Scheduler: Troubleshooting Guide for details. Then proceed as follows:
v If Autotrace is not at the correct version, uninstall it and repeat the Tivoli
Workload Scheduler installation step.
v If Autotrace is at the correct version, you need to modify the Tivoli Workload
Scheduler installation so that it omits the Autotrace installation, and repeat the
installation step, as follows:
1. Locate the following script:
<TWS_8.5_IMAGE_DIR>/ACTIONTOOLS/twsConfigAction.cmd
where <TWS_8.5_IMAGE_DIR> is the directory containing the installation

DVD (as appropriate) image.
2. Edit the script with a text editor.
3. Locate and comment out the following lines:
call %TWS_HOME%/trace/atinstall.exe --quietcopy %TWS_HOME%/trace

if not %errorlevel%==0 echo "atinstall.exe"&&exit %errorlevel%
4. Repeat the installation step. The Autotrace installation is not attempted.
Installation fails because the host name is truncated

You are installing a Tivoli Workload Scheduler component with the InstallShield
wizard on a system where you have defined a host name longer than 15
characters. The installation fails because of a host name mismatch.
Cause and solution
This problem is caused by Windows. When you define a host name Windows
places no limit on the length of the host name. However, if you supply a host
name longer than 15 characters, when you reboot the Windows system to make the
host name active, Windows truncates the host name to 15 characters, and logs a
message in the system log. If you do not notice that message, you will not know
that the name has been truncated, and will supply the full version of the host
name on the installation panel.
Unfortunately, the Windows Java classes that use that supplied long host name do
not truncate the name, so report a mismatch.
To resolve the problem, do one of the following:

v Specifically rename the host name to 15 characters or less, reboot the computer
and restart the installation
v If the truncated name is acceptable, use the step restart facility (see “Recovering
a failed interactive InstallShield wizard installation” on page 125 or “Recovering
a failed silent InstallShield wizard installation” on page 135) to modify the
supplied host name to its truncated form, and continue the installation.
An InstallShield wizard installation fails with the message

"CMW3202E Command failed."
You are running an InstallShield wizard installation on Windows and the wizard
fails in the step "Configure the Tivoli Workload Scheduler instance", with error
messages like the following:
"atinstall.exe"
CMW3202E Command failed.

Cause and solution
A possible cause for this problem is that a file (not a directory) exists on the
installation drive with the name <drive_letter>\program (for example,
D:\program. Delete or rename this file and resume the installation at the failed
step.
The InstallShield wizard commit step fails on Windows with

AWSDEQ024E error
You are installing Tivoli Workload Scheduler on Windows with the InstallShield
wizard, interactive or silent. The commit step fails, and the error log includes a
message similar to the following :
AWSDEQ024E Error owner is not of type user in :.
"makesec failed with error code: 1"
Cause and solution
The problem is probably caused by a non-valid setting of the TMP environment

variable. For example, the above version of message AWSDEQ024E is produced if the
value of the TMP variable is set to C.\tmp instead of C:\tmp.
To resolve the problem, quit the installation wizard, uninstall Tivoli Workload
Scheduler and rerun the installation wizard. You cannot just correct the TMP
variable and resume the installation. If you have problems running the
uninstallation, see “Uninstalling Tivoli Workload Scheduler manually” on page 166.
The installation on Windows receives the warning AWSGAB005W

An installation on Windows receives the following error:
AWSGAB005E The account cannot be verified automatically. >

Check that the supplied login and password are valid and >
satisfy the local security policy.
Cause and solution
This is a known Windows limitation, dependent upon the security settings of your
Windows workstations. The password you supplied for the <TWS_user> might be
perfectly valid, but the installation wizard is unable to validate it.
The problem does not block the installation. If you are using the interactive
wizard, the installation displays this message; giving you the option to click Next
to continue. If you are using the silent option, the installation goes ahead.
To resolve the problem, take the following steps:

1. After the installation has completed, check whether the supplied password was
correct. If it was, you need do no more.
2. If the password was incorrect, when the product tries to start the Windows
services it has created, the services fail. Use the Windows facilities to modify
the password used by these services so that it matches the password of the
<TWS_user>. To do this perform these steps for each service:
a. In the Windows Services panel, locate the Tivoli Workload Scheduler service
with the incorrect password.
b. Access the properties of this service, for example by right-clicking the
service and selecting Properties.
c. Click the Log On tab.
d. Enter and confirm the correct values for the password.

e. Start the service.
On a Windows 2003 domain, the application server installation

fails with an apparent credentials problem but the credentials are
correct
You are installing on a Windows 2003 domain any Tivoli Workload Scheduler
component that also installs the application server, but the installation fails at the
step where the application server is being installed. The error message given is:
com.ibm.websphere.security.auth.WSLoginFailedException:
Authentication failed for user mdm84 with the following error message
Logon failure: unknown user name or bad password.
When you check the credentials you find that the User ID and password are
correct.
Cause and solution
A possible cause for this problem is that you have not installed SP2 on Windows
2003. Without SP2, Windows has a known bug that when it sets the "impersonate a
client after authentication" right, it also deletes the network connection icon, so that
the installation cannot communicate with the application server. SP2 is a
prerequisite of the installation.
Do the following:
1. Install Windows 2003 SP2
2. Make sure that the "impersonate a client after authentication" right is applied
not only to the <TWS_user> but also the Administrators group, and the Service
system account.
3. Rerun the installation.
The user account is not created on Windows 2000 with system

error 56b
On Windows 2000 operating systems, you are running an InstallShield wizard
installation specifying a domain user (domain\user) as the <TWS_user>. The
installation fails at the user account creation stage giving the following message:
WARNING: USER DOES NOT EXIST #System error <56b>
Cause and solution
The problem is actually caused by a synchronization error between the Windows

2000 domain server and client. The account creation process and the process that
adds the account to the appropriate user group are not synchronized, giving the
impression that the account creation has failed.
Normally, by the time you have noted the error, the account creation has been
completed. So, to resolve this problem, just set the user account creation step of the
installation to ″ready″ and continue the installation.
However, if the process fails for a second time, you must create the user manually,
and then resume the failed step.
The user account is not created on Windows - create it manually

On Windows operating systems, the installation automatically creates the Tivoli
Workload Scheduler user with the appropriate rights, if the user does not already

exist. However, if the installation encountered problems with the creation of the
user, you can perform the following steps.
1. Back out of the installation.
2. Create a local user account with a name of your choice on the workstation
where you want to install Tivoli Workload Scheduler.
Note: You can also use an existing user account. Ensure, however, that this
user is a member of the Windows Administrators group.
3. Grant this <TWS_user> the following advanced user rights:
Act as part of the operating system

Increase quotas
Log on as batch job
Log on as a service
Log on locally
Replace a process level token
4. Rerun the installation, citing the name of the account you created when
requested.
User account-related issues for Windows 2003

In many Windows 2003 systems (for example, Enterprise Edition Standard Edition)
the file C:\Windows\System32\cmd.exe does not have the permission to run a
generic process owned by a generic Windows user. To do this, you must add the
user to the list of users permitted to run the file that schedules the jobs. Perform
one of the following procedures:
v Procedure 1
1. Locate the C:\Windows\system32\cmd.exe file.
2. Right-click the file and select Properties.
3. Select the Security tab.
4. In the Group or User Name section click Add.
5. Add the domain user that needs to be able to run Tivoli Workload Scheduler
jobs.
6. Click OK.
7. Select the Read and execute permission (or higher) for that user.
8. Click Apply OK.
v Procedure 2
1. Using the Windows 2003 user and group management facility, create a group
called, for example, TWS_group (with this you can set "logon as a batch
program" and "log on locally" for easier use)
2. Add your domain user to this group.
3. Add this group to the cmd.exe list of permitted users, as described for the
domain user, above.
v Procedure 3
Use the procedure described above to add the USERS group to the cmd.exe
permitted users (by default all domain users and local users belong to this
group).
v Procedure 4
Use the procedure described above to add the BATCH group to the cmd.exe
permitted users (by default all domain users and local users belong to this
group).

The Windows services fail to start after installation

If the Tivoli Token service and the Tivoli Workload Scheduler for <TWS_user>
services fail to start after installation, there was probably a problem with the
<TWS_user> password. This scenario is described in “The Tivoli Workload
Scheduler services fail to start after installation.”
The Tivoli Workload Scheduler services fail to start after

installation
On Windows, both the Tivoli Token service and the Tivoli Workload Scheduler
for <TWS_user> service (batchup) fail to start for the first time (after a successful
installation).
Cause and solution
During the installation you selected the option to create the <TWS_user>, but an
error was found with the password you supplied (for example, the supplied
password might not have satisfied the security policy on the workstation). You
used the restart facility (see “Recovering a failed interactive InstallShield wizard
installation” on page 125) to recover the situation. On the recovery panel you
entered a different value for the password than the value entered originally. This
value was valid, so the program went ahead and completed the installation.
However, during the completion of the installation, the <TWS_user> was created
using the new password that you entered on the recovery panel, while the services
were created using the original password value.
The reason for this is that when the installation wizard starts the installation steps,
after having accepted the input of all of the installation variables, it creates each of
the steps complete with the properties (variables) required to perform the step. If a
step fails, and the Step List window opens (see “The Step List window” on page
126), the properties that are displayed for one step are quite separate from the
properties of another step. Thus, if you changed the password for one step (for
example, the ″Create the <TWS_user> (Windows only)″ step), you must have also
changed it for all the other steps where it is used (for example, the ″Configure the
Tivoli Workload Scheduler instance″ step (see “Correcting a failed step and
continuing the installation” on page 131).
To resolve this problem after the installation has completed, you must change the
password for the services to the value that you entered on the recovery panel,
following the procedure described in Tivoli Workload Scheduler: Administration Guide.
If you become aware of this problem before the installation is complete, you can
choose either to let the installation go ahead and change the password afterwards,
as described in the previous paragraph, or to exit from the installation, uninstall
whatever you have installed, following the procedures described in the Tivoli
Workload Scheduler: Planning and Installation Guide, and rerun the installation.
Problems installing on AIX

The following problem could occur while installing on AIX:
ISMP installation on AIX hangs

The installation hangs while using the ISMP wizard in interactive mode.
Cause and solution

Problems installing on AIX
If this happens, do the following:

1. Cancel the interactive installation.
2. Follow the instructions provided in “Recovering a failed interactive
InstallShield wizard installation” on page 125 to back out any installation
actions that have already been performed.
3. Perform the installation in silent mode.
Instructions for performing a silent ISMP installation are provided in Chapter 3
of Tivoli Workload Scheduler: Planning and Installation Guide.
Problems installing on UNIX

The following problems could occur:
v “The installation fails on UNIX with a problem validating the Java Virtual
Machine”
v “An incorrect password is supplied for the <TWS_user>on UNIX”
The installation fails on UNIX with a problem validating the Java

Virtual Machine
You are installing on UNIX, and receive a message indicating that there is a
problem validating the Java Virtual Machine (JVM).
Cause and solution
This might be caused by a timeout problem. The InstallShield wizard uses a

default timeout of five seconds during its operations to validate the version of JVM
that you have installed. For a variety of reasons this might be insufficient.
Relaunch the installation wizard (interactive or silent) adding the following

parameter:
-is:jvmtimer 10
This extends the timeout to 10 seconds, and if this does not work, you can try
extending it to 20 seconds. If the JVM still does not validate correctly, contact IBM
Software Support for assistance.
An incorrect password is supplied for the <TWS_user>on UNIX

You have supplied an incorrect password for the <TWS_user> on UNIX. An
appropriate error message is displayed, but it is displayed during the stepped
installation rather than when you input the password. You need to determine how
to recover.
Cause and solution
The <TWS_user> password cannot be checked on UNIX at time of input, for

technical reasons. If an incorrect password is provided, the error is not discovered
until the wizard tries to install the product, after it has already successfully
installed the Tivoli Workload Scheduler database, and the embedded WebSphere
Application Server.
To recover from this situation, do the following:

1. Quit the wizard
2. Delete the application server directory: $WAS_HOME/eWAS/, where $WAS_HOME is
the environment variable that contains the installation path of the embedded
WebSphere Application Server

Problems installing on UNIX
3. Rerun the wizard

4. Supply the correct password for the <TWS_user>, when requested
Problems installing on HP-UX

v “An InstallShield wizard installation cannot start on HP-UX”
v “An InstallShield wizard installation fails on HP-UX with an error installing the
bundled JRE”
v “An InstallShield wizard installation fails on HP-UX with a ″run error″”
An InstallShield wizard installation cannot start on HP-UX

You are trying to install Tivoli Workload Scheduler on HP-UX using the
InstallShield wizard. The wizard does not start.
Cause and solution
This is probably due to insufficient threads being available to the installation

program.
Set the max_thread_proc kernel parameter to a minimum of 128 so that the

installation can start.
See http://www.ibm.com/support/docview.wss?rs=672&uid=swg27012175 for

details of the typical kernel parameters to use to run Tivoli Workload Scheduler on
HP-UX.
An InstallShield wizard installation fails on HP-UX with an error

installing the bundled JRE
You are installing on HP-UX where the required level of JRE is not installed. The
installation wizard tries to install the bundled JRE but fails. The following message
is received:
Bundled JRE is not binary compatible with host OS/Arch or it is corrupt.
Testing bundled JRE failed.
Cause and solution
This problem is probably caused by the HP-UX configuration parameter MAXDSIZ

having been set to a value that is too low. Set the MAXDSIZ configuration parameter
to a minimum of 128 MB, and retry the installation.
An InstallShield wizard installation fails on HP-UX with a ″run

error″
You are trying to install Tivoli Workload Scheduler using the InstallShield wizard
on an AIX or HP-UX operating system. The installation fails giving the following
exception in thread ″main″:
java.lang.NoClassDefFoundError: run error
This problem is described in “An InstallShield wizard installation fails on AIX or

HP-UX with a ″run error″” on page 150

Problems installing on Sun Solaris

The following problem could occur:
An installation fails on Sun Solaris with the error "The command

line parameter, -installRoot, is invalid"
The installation of a component on Sun Solaris fails. The following error messages
are given:
AWSJIS038E: An unspecified internal error has occurred
during the installation process.
ERROR: The command line parameter, -installRoot, is invalid
Use -usage to see the available command line options
ERROR installing WAS Express, check system stderr/stdout
Cause and solution
The problem is possibly caused by an incorrect PATH environment variable, which

has the search path relating to an X/Open specification, for example XPG4, in the
incorrect order.
Consult the Sun Solaris documentation and support Web site and ensure that the
PATH variable is correctly expressed. Correct any error you find and retry the
installation.
Problems installing on Linux

v “An InstallShield wizard installation fails on Linux with an error installing the
bundled JRE”
v “A non-English installation on Linux finishes correctly, but the start of Tivoli
Workload Scheduler gives one or more errors” on page 146
An InstallShield wizard installation fails on Linux with an error

installing the bundled JRE
You are installing on Linux where the required level of JRE is not installed. The
installation wizard tries to install the bundled JRE but fails. The following message
is received:
This application requires a Java Run Time Environment (JRE)
to run. Searching for one on your computer was not successful.
Please use the command line switch -is:javahome to specify
a valid JRE. For more help use the option -is:help.
Note: The solution indicated in this InstallShield wizard message probably does
not work.
Cause and solution
The probable cause is that the bc utility is a prerequisite of the InstallShield

wizard, but is not installed by default on all Linux platforms (on Red Hat Linux,
version 2.1, for example, it is included only in Service Pack 2).
To check for the existence of the utility run this query on the rpm registry: rpm -q
bc
If the utility is missing, consult your operating system's support resources to

determine how to obtain it. When it is successfully installed, rerun the installation.

A non-English installation on Linux finishes correctly, but the

start of Tivoli Workload Scheduler gives one or more errors
You installed a non-English version of Tivoli Workload Scheduler on Linux, but
when the product starts errors are given.
Cause and solution
The problem might be the code page of the workstation. To support languages
other than English, Tivoli Workload Scheduler requires the code page to be UTF8.
Reset the code page and restart the product and you should have no reoccurrence
of this problem.
Problems with the silent installation

The following problem could occur with the silent installation:
Silent installation fails without writing a log

You have launched the silent installation but it fails without writing a log.
Cause and solution
The response file is corrupt, or not syntactically correct.
Correct the syntax of the response file, comparing your version with the supplied
templates, or recreate it from the template if it is not readable.
Problems with installations using the twsinst script

The following problem might occur:
An installation with twsinst fails with a return code that does not
indicate the reason for failure
If an error occurs during an unattended installation process that makes use of the
twsinst script, it can display a return code that is not documented.
Cause and solution
Several twsinst error situations give the same return code that is used in the error
message that gives the failure. The various error situations have not been
documented, because other error messages in the log explain the precise error.
Follow the sequence of installation messages in the log and determine from their
context the reason for the problem. Correct the problem and rerun the installation.
Problems installing the application server

The following problems might occur:
v “The application server profile creation fails”
v “The application server installation fails on a Windows 2003 domain with an
apparent credentials problem but the credentials are correct” on page 147
The application server profile creation fails

The installation stops in the step ″Install with rollback the Tivoli Workload
Scheduler modelling and planning server, version 8.5″ because it cannot create the
application server profile.

Problems installing application server
When you check the application server trace file
$WAS_HOME/profiles/twsprofile.deleted/logs/wsadmin.traceout
you find the following line (it is shown here split into three lines):
[1/17/06 17:16:46:886 CST] 0000000a WorkSpaceMast E

WKSP0020E: Error getting meta data repository root
$WAS_HOME/eWAS/profiles/twsprofile/config/.repository
The variable $WAS_HOME is the directory where the application server is installed.
Cause and solution
This error indicates that the folder repository is missing in the installation of the
embedded WebSphere Application Server. This means that the following folder is
missing or damaged in the path where you placed the installation images:
$PLATFORM_IMAGES_ROOT/EmbeddedExpress/profileTemplates/default/documents/config/.repository
The variable $PLATFORM_IMAGES_ROOT is the location of images for the selected

platform, for example, Solaris.
Compare the corresponding files on the distribution media and the location where
you copied the installation images.
v If the files are different, the copy of the installation images from the distribution
media to the location from which you are using them did not complete correctly.
Ensure there is sufficient disk space. Ensure you are using the binary option if
using ftp. Recopy the files and rerun the Tivoli Workload Scheduler component
installation, or rerun the installation directly from the distribution media.
v If the files are in the same correct path (as indicated above) and are the same,
there might be an internal error; contact IBM Software Support for assistance.
The application server installation fails on a Windows 2003

domain with an apparent credentials problem but the credentials
are correct
You are installing on a Windows 2003 domain any Tivoli Workload Scheduler
component that also installs the application server, but the installation fails at the
step where the application server is being installed. The error message given is:
com.ibm.websphere.security.auth.WSLoginFailedException:
Authentication failed for user mdm84 with the following error message
Logon failure: unknown user name or bad password.
When you check the credentials you find that the User ID and password are
correct.
Cause and solution
See “On a Windows 2003 domain, the application server installation fails with an
apparent credentials problem but the credentials are correct” on page 140 for the
cause and solution.
Other installation problems

The following miscellaneous problems might occur:
v “An installation fails on a UNC mapped drive” on page 148
v “Message ″Error writing file = ″ received” on page 148

Miscellaneous installation problems
v “Message ″Error writing file = 28″ received” on page 149

v “Message AWSFAB037E is received on UNIX” on page 149
v “An installation fails with a problem with the installation images on an NFS
mount” on page 150
v “An InstallShield wizard installation fails on AIX or HP-UX with a ″run error″”
on page 150
v “An InstallShield wizard ″Add feature″ installation fails” on page 150
v “A software package block installation fails with the message: DISSE0324E” on
page 151
v “A software package block installation fails to complete successfully” on page
152
v “The installation fails with the error AWSFAB035E” on page 153
v “The installation fails with the error AWSGAB566E” on page 154
v “The commit step fails” on page 154
v “Miscellaneous failures” on page 154
An installation fails on a UNC mapped drive

You are running an installation with the installation images on a drive mapped
using the Universal Naming Convention (UNC). The wizard fails at the first step.
Cause and solution
The Tivoli Workload Scheduler installation wizard methodology does not support
UNC mapped drives. Rerun the installation from a drive that is not UNC mapped.
Message ″Error writing file = ″ received

When performing any type of installation on any operating system, you might
receive the following error:
Error writing file = There may not be enough temporary disk space.
Try using -is:tempdir to use a temporary directory on a partition
with more disk space.
Note in particular the absence of an error code, which differentiates this message
from a very similar message, with error code 28, that indicates that you are not
logged on as root (see “Message ″Error writing file = 28″ received” on page 149).
Cause and solution
Normally this error means what it says; the solution is as follows.
First, try to redirect the installation to use a different temporary directory, by

adding the -is:tempdir .<temp_dir_path> variable to the installation command.
If this oes not work, you must use one of these two methods to give more space to
the swdis directory:
v Either:
Create a new version in a different file system. The procedure is as follows:
1. Delete or rename both the work and the backup subdirectories and recreate
the directories in a file system with more space in it.
2. Link the new directories to the .swdis directory using the ln -s command.
v Or:

Create a new backup directory in a file system with more space in it, and
modify the /etc/Tivoli/swdis.ini file to point to it.
Ensure to modify the correct section of the swdis.ini file, as follows:
– If you are making a local silent InstallShield wizard installation that uses the
disconnected command line (wdinstsp), modify the value of the backup_dir
key in the [#MOBILE] section.
– If you are making a remote installation using Tivoli Configuration Manager,
you must identify the section relative to the endpoint chosen as the target (for
example, [lab133080_aix]), and modify the backup_dir key in that section.
Message ″Error writing file = 28″ received

When performing any type of installation on any operating system, you might
receive the following error:
Error writing file = 28 There may not be enough temporary disk space.
Try using -is:tempdir to use a temporary directory on a partition
with more disk space.
Note in particular the error code 28, which differentiates this message from a very
similar message, without error code 28, that does indicate disk space problems (see
“Message ″Error writing file = ″ received” on page 148).
Cause and solution
This error does not mean exactly what it says. When performing a silent
installation of a fix pack on UNIX, and possibly in certain other circumstances, this
error message might mean that you are not logged on as root.
Make sure that you are logged onto the workstation as root before running the
silent installation:
/SETUP.bin -options <path_to_patchInstall.txt> -silent
Message AWSFAB037E is received on UNIX

The twsinst script installation fails on UNIX with the following error message:
AWSFAB037E The twsinst script is being run from the wrong directory.
AWSFAB038I Mount the TWS installation CD and run the twsinst utility
placed there.
Cause and solution
These error messages are received when attempting to install Tivoli Workload
Scheduler on a UNIX operating system using the twsinst utility copied from the
installation DVD to the home directory of the user that is nominated as the
<TWS_user> during the installation. The installation fails and no log files are
generated.
You can run twsinst from the following places:

v The Tivoli Workload Scheduler DVD
v A disk image of the DVD
v A copy of the twsinst utility and its associated files placed in any local directory
other than the home directory of the user that is going to be nominated as the
<TWS_user> during the installation.

An installation fails with a problem with the installation images

on an NFS mount
The installation images are on an NFS mount. The installation fails and the log
shows messages similar to the following:
cannot start <file_name>
No such file or directory <file_name>"
where <file_name> is a file in the directory structure of the installation images.
Cause and solution
The NFS mount is corrupt. Refresh the NFS mount by issuing unmount and then
mount commands. Retry the failed step (or the entire installation, depending on
what went wrong and at what point in the installation).
An InstallShield wizard installation fails on AIX or HP-UX with a

″run error″
You are trying to install Tivoli Workload Scheduler using the InstallShield wizard
on an AIX or HP-UX operating system. The installation fails giving the following
exception in thread ″main″:
java.lang.NoClassDefFoundError: run error
Cause and solution
This caused by a combination of display, Java, and binary issues.
To resolve this problem, perform the following steps:

1. Ensure Quality Pack 10 or higher is installed.
2. Run xhost + and re-export the display.
3. Retry the installation using the SETUP.bin binary located at the root of the
DVD.
This copies the appropriate media to /tmp and runs the installation from there.
Note: If you have insufficient space in /tmp, run the SETUP.bin command with
the -is:tempdir .<temp_dir_path> variable.
An InstallShield wizard ″Add feature″ installation fails

You are trying to add a feature to an existing Tivoli Workload Scheduler
installation, using the Add feature option in the wizard. You have started the
wizard from the Tivoli Workload Scheduler DVD, but have previously copied the
DVD image of the feature to your hard disk. When the wizard asks you to supply
the path to the feature installation, you eject the product DVD before supplying the
hard disk path information. The installation fails.
Cause and solution
This is a known problem with the InstallShield wizard. If an installation starts

from a DVD, the InstallShield wizard expects to find a DVD in the DVD drive.
To correct this problem, put the product DVD, or any other DVD, back in the DVD
drive (the InstallShield wizard requires a DVD, but it can be any DVD).

A software package block installation fails with the message:

DISSE0324E
You launched an installation of either the full product, a component, or a fix-pack,
that uses the software package blocks of the software distribution component of
IBM Tivoli Configuration Manager. The installation fails, giving the following
messages:
DISSE0282E Error compressing file <file_name> in the software Package block.
DISSE0324E Cannot create backup package
DISSE0005E Operation unsuccessful
Cause and solution
The installation using a software package block is unable to check that there is
sufficient space for the backup it performs. The backup requires at least 80 MB of
disk space. The directory used for the backup is determined by the parameter
backup_dir in the [#MOBILE] section of the swdis.ini file. The following is an
example of this section of the file:
[#MOBILE]
product_dir=/root/.swdis
working_dir=/root/.swdis/work
backup_dir=/root/.swdis/backup
trace_level=0
trace_size=1000000
send_timeout=300
autopack_dir=/root/.swdis/autopack
staging_dir=root/.swdis/service
user_file_variables=/root/.swdis/swdis.var
import_libraries=spd,libecimp
If there is insufficient space in this directory, the error messages shown above are
displayed.
Because the Tivoli Configuration Manager installation was unable to start, the
restore script twsRestore cannot be used. The recovery procedure is as follows:
1. If you are performing a full-product installation, manually delete the following
files and directories:
v twsRestore.sh or twsRestore.cmd (as appropriate)
v twsRemove.sh or twsRemove.cmd (as appropriate)
v _uninstall directory
2. Resolve the file space problem, as follows.
First, try to redirect the installation to use a different temporary directory, by
adding the -is:tempdir .<temp_dir_path> variable to the installation command.
If this oes not work, you must use one of these two methods to give more
space to the swdis directory:
v Either:
Create a new version in a different file system. The procedure is as follows:
a. Delete or rename both the work and the backup subdirectories and
recreate the directories in a file system with more space in it.
b. Link the new directories to the .swdis directory using the ln -s command.
v Or:
Create a new backup directory in a file system with more space in it, and
modify the /etc/Tivoli/swdis.ini file to point to it.

Ensure to modify the correct section of the swdis.ini file, as follows:

– If you are making a local silent InstallShield wizard installation that uses
the disconnected command line (wdinstsp), modify the value of the
backup_dir key in the [#MOBILE] section.
– If you are making a remote installation using Tivoli Configuration
Manager, you must identify the section relative to the endpoint chosen as
the target (for example, [lab133080_aix]), and modify the backup_dir key in
that section.
3. Run the installation again.
A software package block installation fails to complete

successfully
You launched an installation that uses the software package blocks of the software
distribution component of IBM Tivoli Configuration Manager. The installation fails.
Cause and solution
Problems when installing remotely with a software package block can often be
difficult to solve, because it might be more difficult to set the remote environment
correctly so that the installation runs successfully. For this reason, the software
package block is supplied with a series of keys that switch on or off its installation
activities. These action keys are set by default to true, so that the installation
completes normally. If it fails for a reason that you know you can resolve
afterwards, you can retry it, setting one or more of these keys to false, so that the
installation process does not attempt to perform that or those steps.
For example, if the installation fails when trying to back up the previous
installation, and you know that you can proceed without making a backup, you
can eliminate this action from the installation by setting its action key to false. You
re-launch the installation, which does not perform the backup step, but otherwise
completes successfully.
A description of the processing carried out in each step is given in the Tivoli
Workload Scheduler: Planning and Installation Guide.
Note: The installation steps are always the same, whatever installation method you
use.
The details of the action keys are as follows (set any of them to false to not perform
that action):
execActionTools = ″true″
This controls all of the other keys. If you set it to false, none of the other
actions take place (their settings are ignored).
execTwsStopAction = ″true″
This controls whether or not the installation stops existing Tivoli Workload
Scheduler processes on the target workstation.
execTwsCleanAction = ″true″
This controls whether or not the installation cleans up an existing
installation before upgrading it.
execTwsUndoAction = ″true″
This controls whether or not the undoable installation script is run.

execTwsBackupAction = ″$(backup)″
This controls whether or not the installation takes a backup of an existing
installation before commencing the installation. By default this value is set
to ″false″.
execTwsUserAction = ″true″
This controls whether or not the installation creates or modifies the
<TWS_user> details.
execTwsConfigAction = ″true″
This controls whether or not the installation configures Tivoli Workload
Scheduler after the installation.
execTwsStartUpAction = ″true″
This controls whether or not the installation starts up Tivoli Workload
Scheduler after the installation.
execTwsCommitAction = ″true″
This controls whether or not the installation issues a software distribution
commit action to complete the installation (see the Tivoli Configuration
Manager publications for more details).
When you have resolved the problem, reset these keys to true for any other
installation using the software package block.
See the Tivoli Configuration Manager publications for details of how to change the
values of a parameter in a software package block.
The installation fails with the error AWSFAB035E

You are trying to install Tivoli Workload Scheduler or one of its fix packs. The
installation fails with the following error:
AWSFAB035E The installation has failed. For more details see

the log file: /tmp/tws84/summary.log.
The installation log contains the Software Distribution error message DISSE0006E:
DIS:SENG:0006 Operation unsuccessful: Fatal failure.

Explanation: The operation cannot be completed because of
an internal error (for example, a memory allocation failure)
System Action: Operation failed.
The log also contains details of the last internal command it ran:
+ wdinstsp -f -D promote=false -D upgrade=false -D fresh_install=true
Cause and solution
This is a problem related to incompatibility between the Tivoli Workload Scheduler

installer and the current version of IBM Tivoli Configuration Manager. Follow
these steps:
1. Check the version of Tivoli Configuration Manager that is installed, using the
command wlsinst -ah. Check if any patches are installed.
2. If you are using Tivoli Configuration Manager version 4.2, with fix pack
4.2-SWDGW-F1P1 (or later for the same component), there is a compatibility
problem because the installation of Tivoli Workload Scheduler version 8.4 and

its fix packs are only compatible with the GA version of the Tivoli
Configuration Manager SWDGW component.
In this case you must either choose a different installation method that does not
use Tivoli Configuration Manager or uninstall the Tivoli Configuration
Manager 4.2-SWDGW fix pack or packs until the installation is complete.
3. The Tivoli Workload Scheduler GA and fix pack installation uses the Tivoli
Configuration Manager version 4.2 disconnected command line. A problem has
been discovered with this component which requires you to do the following:
a. Install Tivoli Configuration Manager fix pack 4.2-TCM-FP02 on the
workstation.
b. Run the wconvcat command (described in the 4.2-TCM-FP02.README file)
to restore the functionality of the disconnected command line.
c. Retry the failed installation.
The installation fails with the error AWSGAB566E

You are trying to install Tivoli Workload Scheduler, and the installation fails with
the following error:
AWSGAB566E There is not enough disk space available in the following

supplied directory to complete the installation: <directory_name>.
The installation requires <required_space> megabytes,
but only <available_space> megabytes are available.
Cause and solution
The probable cause of this error is simply that either the file set where the product
is to be installed, or the file set where the temporary installation files are being
written, is not large enough. Information about the disk space requirements is
given in the Tivoli Workload Scheduler System Requirements Document at
http://www.ibm.com/support/docview.wss?rs=672&uid=swg27012175
However, this error is also given if the virtual memory file (sometimes called page
file or swap space) on your hard disk is not large enough.
Thus, if there seems to be sufficient disk space, check also the virtual memory that
you have allocated to the hard disks. The installation requires at least 256 MB of
virtual memory on any operating system.
| The commit step fails

| You are trying to install Tivoli Workload Scheduler, and the commit step fails
| Cause and solution
| If the mapped attribute, LDAPUSERIdMap is different from the login attribute,

| LDAPUserFilter, the commit step fails. You must dump the security file and insert
| the mapped value (see error message). Then, manually perform the failed
| composer command (see error message). Finally, set the failed step as successful
| and resume the installation.
Miscellaneous failures
The installation fails and the cause is not immediately obvious from the log
messages.
Cause and solution

The cause of the failure could be any of the following:

The FTP transfer of the files to the node was not done in binary mode
You copied the install directory from the DVD to the local hard disk using
FTP, but did not specify the binary option. Make sure the entire directory
is transferred by FTP in binary mode.
Note: The directory on the local hard disk can have any name, but it is
important to have a parent directory available for the twsinst
installation, because some temporary files need to be located there.
For example:
/temp/HP-UX
or
/temp/TWS84/HP-UX
There is not enough disk space available for the installation
Check that there is enough disk space for the installation on your chosen
fileset.
See the Tivoli Workload Scheduler System Requirements Document at
http://www.ibm.com/support/docview.wss?rs=672&uid=swg27012175 for
more information about the amount of space necessary for installation.
File names did not retain their original case
On UNIX, check that file names retain their case. For example, the file
″TWS_size.txt″ cannot be ″tws_size.txt″.
One or more required files were not copied from the root of the installation
DVD Check that the number of files copied from the DVD is the same as that on
the DVD. If not, copy the files again.
You launched a second installation before the first one had successfully
finished.
If you launch an installation (of an additional component, for example)
while another installation is still running, both installations might fail, or
the second installation might try and resume the first, as if you had
terminated the first installation part way through and now want to
continue.
Depending on the stage that the first installation reached, you might just
be able to close the second installation and let the first one finish.
However, if one or both have failed, you might need to uninstall and then
start the installation again.
Upgrade problems
The following problems could be encountered.
v “On UNIX operating systems, Tivoli Workload Scheduler does not start after
upgrade” on page 156
v “After upgrade from version 8.2.1, the consoles cannot connect to the master
domain manager” on page 156
v “Variables not resolved after upgrade” on page 157
v “Default variable table not accessible after upgrade” on page 158

Upgrade problems
On UNIX operating systems, Tivoli Workload Scheduler does not

start after upgrade
You have upgraded from version 7.0 or 8.1 on a UNIX operating system, without
specifying the -createlink option in the installation program, but after the upgrade
the product does not start.
Cause and solution
In versions 7.0 and 8.1, the following executable files of Tivoli Workload Scheduler
were placed in the directory <TWS_home>/../bin
maestro
at
batch
datecalc
morestdl
jobstdl
parms
In addition, symbolic links were made to these copies from /usr/bin.
Note: The link to the at and batch files was made as mat and mbatch.
From version 8.2 the executable files are not placed in <TWS_home>/../bin, but in
<TWS_home>/bin. However, the original links remain in /usr/bin, pointing to the
correct files but in the wrong directory. If these links were used in any scripts,
those scripts no longer work in version 8.2 or later versions.
To remake the links in /usr/bin so that they point to the files in <TWS_home>, follow
this procedure:
1. Issue the following commands to delete the old links:
rm /usr/bin/maestro
rm /usr/bin/mat
rm /usr/bin/mbatch
rm /usr/bin/datecalc
rm /usr/bin/morestdl
rm /usr/bin/jobstdl
rm /usr/bin/parms
2. Issue the following commands to make the new links:
ln -f -s <TWS_home>/bin/maestro /usr/bin/maestro
ln -f -s <TWS_home>/bin/at /usr/bin/mat
ln -f -s <TWS_home>/bin/batch /usr/bin/mbatch
ln -f -s <TWS_home>/bin/datecalc /usr/bin/datecalc
ln -f -s <TWS_home>/bin/morestdl /usr/bin/morestdl
ln -f -s <TWS_home>/bin/jobstdl /usr/bin/jobstdl
ln -f -s <TWS_home>/bin/parms /usr/bin/parms
Installations on Windows operating systems are not affected by this problem.
After upgrade from version 8.2.1, the consoles cannot connect to

the master domain manager
You have upgraded the master domain manager from version 8.2.1, but are unable
to connect to the upgraded master domain manager either from the Job Scheduling
Console or the Tivoli Dynamic Workload Console. A message similar to the
following is displayed:

Upgrade problems
WSUI0766E Test connection to [lab236099] : failed.

AWSUI0833E The operation could not be completed.
Reason: AWSJCS011E An internal error has occurred.
The error is the following: "AWSJCS011E An internal error has occurred.
The error is the following: "A communication failure occurred while attempting
to obtain an initial context with the provider URL: "corbaloc:iiop:lab236099:31117".
Make sure that any bootstrap address information in the URL is correct and that the
target name server is running. A bootstrap address with no port specification
defaults to port 2809. Possible causes other than an incorrect bootstrap address or
unavailable name server include the network environment and workstation network
configuration.".".
You have checked that the network is working correctly.
Cause and solution
One possible cause is that the host name is defined differently on the master
domain manager workstation than in the network. In version 8.2.1, the Job
Scheduling Console connected to the master domain manager using a host name
input by the user and saved in the console's connection configuration. The fact that
the host name is defined differently on the workstation is ignored, because the user
supplied the name as used in the network, and made the connection.
During the upgrade, the installation wizard, to avoid your having to supply the
host name, displays it for your confirmation, obtaining it from the host name
stored in the workstation. If you do not notice that it is incorrect, it is that host
name which is stored in the application server's preferences.
When you try and connect from one of the consoles, even though you supply the
correct network name for the connection, the application server looks up its
configuration information and cannot match the workstation's host name, giving
the error shown.
To correct the problem, use the changeHostProperties application server utility to

correct the host name (see Tivoli Workload Scheduler: Administration Guide).
Variables not resolved after upgrade

After upgrading to version 8.5, global variables are not resolved.
Cause and solution
During the upgrade to version 8.5, all the security file statements relating to your
global variables were copied by the install wizard into a default variable table in
the new security file. Global variables are disabled in version 8.5, and can only be
used through the variable tables. If you subsequently rebuilt the security file using
the output from your previous dumpsec as input to the new makesec, you will
have overwritten the security statements relating to your default variable table, so
no user has access to the default variable table.
If you have a backup of your security file from prior to when you ran makesec,
run dumpsec from that, and merge your old dumpsec output file with your new
one, as described in the upgrade procedure in the Tivoli Workload Scheduler:
Planning and Installation Guide.
If you do not have a backup, create the default variable table security statement,
following the instructions about configuring the security file in the Tivoli Workload
Scheduler: Administration Guide.

Upgrade problems
Default variable table not accessible after upgrade

After upgrading to version 8.5, your default variable table is not accessible by any
user.
Cause and solution
This problem has exactly the same cause and solution as the preceding - see
“Variables not resolved after upgrade” on page 157.
Migration problems
This section describes problems and solutions for the running of the migration. It
does not describe problems related to the migrated data. For that, consult the Tivoli
Workload Scheduler: Planning and Installation Guide.
The following problems could be encountered:

v “The migration appears to hang at 97% complete”
v “The migration fails because the user does not have the correct permissions” on
page 159
v “The migration on Linux fails when trying to launch composer” on page 159
v “The miggopts script fails on a UNIX mounted file system with error
AWSBEH115E” on page 159
v “A workstation class is not migrated” on page 160
v “A dependency error is given in migration but the migrated plan runs
successfully” on page 161
v “The migration seems to have migrated some Job Scheduling Services twice” on
page 161
v “Jobs that must wait before starting are duplicated after migration” on page 161
The migration appears to hang at 97% complete

In a large environment the migration step appears to hang with the progress bar at
97%.
Cause and solution
In a large environment the migration step can take a long time - perhaps several
hours - depending on how large an environment, and your network speed. There
are several considerations:
v The progress bar of the step appears to be "stuck" on 97%. This is normal. The
import has probably not failed. Wait for the step to finish.
v If you want to check that all is working properly, use system tools to check that
the datamigrate and composer processes are active, and that the following file is
being written:
<temp_directory>/tws84/datamigration
v Do NOT click Stop, unless you are absolutely sure that the step has failed.
When you click Stop (on any step), the step does not stop immediately but only
after the current step is complete (the step is a script that has already been
launched - it cannot be stopped by a user action on the GUI). So the step
continues until it has finished, but then the wizard processes the Stop action and
puts the wizard in a fail status, even though the step may have completed
successfully.
v To stop the migration process, use the system tools to "kill" the datamigrate
process. The wizard will then fail at that step. The database will by now be

Migration problems
partially migrated. If you stopped a migration of correct data this is not a

problem. If you stopped a migration of incorrect data, you may need to clean up
afterwards, as follows:
– All data is added to the database using the composer create command. This
means that if you have to repeat this step any previous data is overwritten.
– However, if on the second time the step is run the data to be added to the
database is different from that stored the first time you ran the step, it is
possible that incorrect data from the first run is not overwritten. Thus, on
successful completion of the second run, the correct data is present, but there
might be additional incorrect data that you must clean up later.
The migration fails because the user does not have the correct
permissions
You have tried to migrate the database to version 8.5, but the migration has failed.
Cause and solution
One of the possible causes of a failure of the migration is that the user running the
migration does not have sufficient rights. The user must have the following rights:
v Full Tivoli Workload Scheduler rights to run the composer extract command on
all objects in the previous database.
v Write permission in the directory where the extract command writes its files of
extracted data.
v Full Tivoli Workload Scheduler rights to run the composer add command for all
object types.
Change the rights of the user, or choose another user account to run the migration.
The migration on Linux fails when trying to launch composer

You have tried to migrate the database to version 8.5 on Linux, but the migration
has failed at the point where composer on the previous version is to be launched
to create the files of object definitions to be migrated.
Cause and solution
The problem could be the kernel version environment variable. If, on the computer
where the previous version of Tivoli Workload Scheduler is running, the
environment variable LD_ASSUME_KERNEL=2.4.1 is set, you must set the same
variable for the shell from which you run the migration.
Set the variable and rerun the migration.
The miggopts script fails on a UNIX mounted file system with

error AWSBEH115E
You are migrating the global options from a previous version of Tivoli Workload
Scheduler on a UNIX platform, where you have mounted the file system of the
computer where the previous version of Tivoli Workload Scheduler is installed, as
root. The miggopts command fails with the following error:
AWSBEH115E The file <path>/globalopts does not exist or you
do not have read access to the file.
where <path> is the mount path.
Cause and solution

Migration problems
The problem could be the permissions for the mounted drive. The drive must be
mounted in read/write mode.
Remount the drive and rerun the miggopts command.
The datamigrate script does not migrate an object type

You are migrating the database to version 8.5, object type by object type, but after
running the datamigrate command on a specific object type no objects are
migrated.
Cause and solution
A possible reason for this problem is that you have used a keyword in the
datamigrate command that does not match the contents of the file of exported
objects identified in the command.
For example, if you issue the command datamigrate -topology myFile.txt, but
myFile.txt contains details of jobs instead of topology, the migration creates an
empty file and shows that no objects were migrated. This is because datamigrate
makes no attempt to check that the data in the file matches the keyword used.
Rerun the command, making the correct association between keyword and file
contents.
A workstation class is not migrated

You have migrated the database to version 8.5, but a workstation class gave an
error and could not be migrated.
Cause and solution
Check the size of the workstation class in the original database, using the previous
version of composer. If the list of member workstations exceeds 128 bytes, the
workstation class does not migrate correctly, because the migration tool cannot
handle large workstation classes.
To determine if the workstation class has encountered this particular problem, run
the composer extract command on the previous database for the workstation class
that could not be migrated. Expect the output to be something like the following:
CPUCLASS WSCL_23
MEMBERS S235034C S235034B S235034A M134115X F237167A F236148A F235034M F235034L F235034I F235034H F235034G F235034F F235034E F2
35034D F235034C F235034B F235034A F135152B F135152A D235059A D235034B D235034A B235059A
END
Count the bytes in the line commencing "MEMBERS" (including the string
"MEMBERS" and the spaces that separate the workstation names). If the count
exceeds 128 bytes, the workstation class was not migrated because it was too large.
In the above example, the line commencing "MEMBERS" reaches 128 bytes after
the first two bytes of the workstation F235034D. At this point the extract command
has created a new line and has thus split the workstation name into two parts. The
workstation class would fail the migration, because the second line is not in a valid
format.
To resolve this problem choose one of the following options:

Migration problems
Recreate the workstation class manually

Recreate the workstation class in the migrated database manually from
scratch.
Recreate the workstation class using the original data
Follow this procedure:
1. In the previous version of Tivoli Workload Scheduler, use composer to
list the contents of the workstation class.
2. Edit the output from this command to create a definition for the
workstation class in a file. See the Tivoli Workload Scheduler: User's Guide
and Reference for details of the syntax of the workstation class definition.
3. Add this definition to the database using composer.
A dependency error is given in migration but the migrated plan

runs successfully
You have migrated the database to version 8.5, and during migration one or more
dependency errors were given, indicating that the migration was unable to migrate
a dependency correctly from the previous version. However, when you run the
plan in the migrated database, the job or job stream completes successfully.
Cause and solution
This is not an error, because the migration attempts to minimize situations which
would cause a migrated job or job stream to fail. When the migration finds a
dependency which is not valid it does not delete the dependency but sets it to a
dummy job stream defined for the master domain manager. An error message is
produced so that you know that you have an error situation to correct.
Correct the dependency, as required.
The migration seems to have migrated some Job Scheduling

Services twice
You have migrated the database to version 8.5 and after the migration of the Job
Scheduling Services you notice that the migration messages appear to be present
twice.
Cause and solution
The datamigrate command requires two passes to migrate a job stream, running a
different process in each pass. If there are serious errors in the job stream
definition, for example the workstation is missing, such errors are identified by
both passes. Further, the final total of errors and warnings includes each error in
each pass, so it counts two errors for each single error of this type found in both
passes. Altogether, this might give the impression that the migration has been
performed twice, when it just means that the same error was found by two
different migration processes.
You need take no action, other than to correct the errors indicated, whether they
are indicated once or twice.
Jobs that must wait before starting are duplicated after migration
You have migrated a version 8.2.1 database to version 8.5 and after the migration
has completed you notice that jobs that were in the plan and defined to wait a
number of hours, days, weeks, or months after other jobs had completed, are
duplicated.

Migration problems
Cause and solution
To define that a job should run, say, two days after a dependent job, you use the
syntax "at + 2 Days". In versions of Tivoli Workload Scheduler prior to 8.3, jobs
like this went into the plan on the day of the dependent job, and were carried
forward until the date they were due to be run.
However, in the current version, the processing has been changed, and such jobs
are only inserted in the plan on their due dates.
This means that if such a job is already in the plan at time of migration, waiting to
arrive at its due date, it is added to the migrated current plan, as you would
expect. However, on the due date it is added again to the current plan, by the
current processing rules.
To resolve this problem, delete one of the duplicates after the migration.
Uninstallation problems
The following problems can occur when uninstalling
v “An uninstallation on Windows fails”
v “An uninstallation fails during the restore profiles step, because the embedded
WebSphere Application Server was not stopped”
v “The uninstallation of the Connector fails in the "Start the embedded WebSphere
Application server" step” on page 163
An uninstallation on Windows fails

You have tried to uninstall the product using the InstallShield wizard on a
Windows workstation, but the uninstallation has failed.
Cause and solution
A possible cause of a failure of an InstallShield wizard uninstallation on Windows,

is that the Services window of the Administrative Tools in the Control Panel is
open.
Close the Services window. Rerun the uninstallation. If you have any problems,
uninstall the services manually.
An uninstallation fails during the restore profiles step, because

the embedded WebSphere Application Server was not stopped
You have tried to uninstall the product but the uninstallation has failed at the
restore profiles step. The error indicates that the embedded WebSphere Application
Server has not stopped (if this fact is not reported by the log, check whether the
application server has stopped, and if it has not, proceed in the same way).
Cause and solution
The problem is that the profiles cannot be restored while the application server is
running, and the stop of the application server has failed. There are two possible
causes:
v The Windows Service Control Manager was unable to stop the embedded
WebSphere Application Server service before the timeout expired.
v The Windows Service Control Manager has given an error while trying to stop
the service

Uninstall problems
Check the Windows system log files to see if an error is reported by the Windows
Service Manager. If it has, you need to resolve the problem before continuing.
If no error is reported from the Windows Service Control Manager, it must be a

timeout problem.
To solve the problem, do as follows:

1. Open the Windows Services panel
2. Stop the service that runs the embedded WebSphere Application Server from
the panel
3. Close the Windows Services panel
4. Resume the installation from the restore profiles step.
| The uninstallation of the Connector fails in the "Start the

| embedded WebSphere Application server" step
| You are uninstalling the Connector, but the uninstallation fails in the step: "Start the
| embedded WebSphere Application server", with the message:
| AWSJIS038E An internal error has occurred. An unspecified internal error

| has occurred during the installation process.
| ----------- Error log ------------
| Could not open service 'IBMWAS61Service - <TWS_user>'
| reason: The specified service does not exist as an installed service.
| ADMU0116I: Tool information is being logged in file C:\Program

| Files\IBM\TWA\eWAS\profiles\twaprofile\logs\twaserver\startServer.log
| ADMU0128I: Starting tool with the twaprofile profile
| ADMU3100I: Reading configuration for server: twaserver
| ADMU3028I: Conflict detected on port 28880. Likely causes: a) An instance

| of the server twaserver is already running b) some other process is using
| port 28880
| ADMU3027E: An instance of the server may already be running: twaserver
| ADMU0111E: Program exiting with error:

| com.ibm.websphere.management.exception.AdminException: ADMU3027E: An
| instance of the server may already be running: twaserver
| ADMU1211I: To obtain a full trace of the failure, use the -trace option.
| ADMU0211I: Error details may be seen in the file: C:\Program

| Files\IBM\TWA\eWAS\profiles\twaprofile\logs\twaserver\startServer.log
| TWA_EXCEPTION
| CMW3202E Command failed.
| Cause and solution

Uninstall problems
| This problem occurs when the WebSphere Application Server administration user
| ID and the <TWS_user> of the agent on which the Connector was installed are
| different. This can be caused by having installed the Tivoli Dynamic Workload
| Console before the agent, and by not having installed the agent using the
| WebSphere Application Server administration user ID as the <TWS_user> ID.
| To resolve the problem, do the following:

| 1. If you are using the interactive wizard, select the option to use the step restart
| facility. If the step failed in the silent installation, rerun the silent installation
| using the –resume option and omitting the –silent option so that the interactive
| wizard's step restart facility can be used.
| 2. In the step restart facility, select the step that failed and put it into the Successful
| state.
| 3. Click Run next or Run all and let the wizard finish.
| 4. Follow the instructions in the Tivoli Workload Scheduler: Administration Guide for
| stopping and restarting the application server using the stopWas and startWas
| commands, ensuring to use the credentials of the WebSphere Application
| Server administration user.
Fix pack installation problems

This section describes problems and solutions for problems that might occur
during the installation of a fix pack.
The following problem could be encountered:
The update of the embedded WebSphere Application Server fails

during the fix pack installation
You have tried to apply a fix pack, but the installation fails at the step ″Update of
the embedded WebSphere Application Server″. A message similar to the following
is given in the summary.log:
Updating bobcat
ERROR: The script ended abnormally. The reason is:
possible error, 65, launching updateinstaller.
The script exit code is 65
CMW3202E Command failed.
Cause and solution
More information can be found in the fix pack installation log. See “WebSphere
Application Server installation log files” on page 29 for details.
One potential cause of the problem is disk space. Look for the following message
in the fix pack installation log file:
(Aug 30, 2006 12:01:00 PM), UpdateInstaller,
com.ibm.ws.install.ni.ismp.actions.MaintenancePrereqCheckAction, err,
CWUPI0025E: There is insufficient free disk space on the system:
/<TWS_home>/eWAS:
Required: 400 MB
Available: 146 MB
/tmp/:
Required: 250 MB
Available: 311 MB

Fix pack installation problems
Ensure there is enough free disk space on all required file systems and retry the
operation.
Security implications of the installation

There are security implications involved in the installation of Tivoli Workload
Scheduler, because some of the files used by the installation contain unencrypted
passwords. The security exposure scenarios are as follows:
Successful installation
During a successful installation, some temporary files are written with
unencrypted passwords. At the final step they are deleted. The exposure is
the duration, or less, of the installation.
A failed installation which is resumed and finishes successfully.
This is like the successful installation, except that the period of the
exposure is lengthened by the time it takes you to fix whatever is the
problem.
A failed installation which cannot be finished, and from which you have to
recover manually
In this case, the final step to delete the temporary files is not performed, so
the files remain.
A silent installation
You edit a response file, adding unencrypted passwords. The response file
is not deleted, even after a successful installation. The exposure is
permanent unless you delete the file.
The files where you can find unencrypted passwords are the following. They
might not all be present, but you should check for all of them:
Windows <TWS_home>\userdef_wnt
<TEMP_DIR>\TWA/tws85\DB2Response.rsp
<TEMP_DIR>\TWA/tws85\checkdb_root.sh
<TEMP_DIR>\TWA/tws85\checkdbclient.sh
UNIX <TEMP_DIR>/TWA/tws85/DB2Response.rsp
<TEMP_DIR>/TWA/tws85/checkdb_root.sh
<TEMP_DIR>/TWA/tws85/checkdbclient.sh
In addition, on all platforms, the Tivoli Workload Scheduler response file if you
used a silent installation (see the Tivoli Workload Scheduler: Planning and Installation
Guide for details of the template response file names).
Verifying the installation

After installing the product, the installation process proceeds to complete, amongst
other operations, the following configuration tasks:
v Create the main local and global default settings.
v Configure security access.
A default operational Security file is created in the <TWS_home> directory. By
default, it authorizes <TWS_user> and the administrator or root user. It is also
updated when a full InstallShield wizard installation of the connector is
performed.
v Set workstation and user definitions each time you install or promote a IBM
Tivoli Workload Scheduler master domain manager.

Verifying the installation
To make sure that no errors occurred during installation, check the install log file
(see “Installation log files” on page 28 for information about the log files and
where to find them).
The following are examples of checks you can perform to verify the installation,
and the corresponding recovery actions:
Check the main local and global default settings.
If you promoted a workstation from the role of standard agent or
fault-tolerant agents to the role of master domain manager, check that the
master global option is set to the correct workstation name.
If it is wrong, you must manually edit the files to replace the current
values with the correct ones.
Check for the Security file
Check that the default operational security file named Security was
created in the <TWA_home>\tws directory. If this did not happen, create
the file as follows:
1. Set the Tivoli Workload Scheduler environment by running the script
tws_env.
2. Customize the Security file, as follows:
a. Open the file <TWS_home>/config/Security.conf
b. Edit the contents to reflect your environment and requirements
c. Save the file as <TWS_home>/Security.conf
3. Run one of the following commands:
Windows
makesec Security.conf
UNIX
makesec -l Security.conf
Check for workstation and user definitions
Check that your required workstation and user definitions are in place in
the database of the master domain manager. To add missing definitions in
the database, follow the instructions in the Tivoli Workload Scheduler: Job
Scheduling Console User’s Guide or the Tivoli Workload Scheduler: User's Guide
and Reference.
Uninstalling Tivoli Workload Scheduler manually

This section describes how to manually remove an instance of Tivoli Workload
Automation that did not completely uninstall.
The following are possible scenarios from which you might need to recover:
v You removed a previous installation of the product, but the uninstall procedure
did not work properly and records of the previous installation were left on your
system.
v For some reason the uninstallation as described in the Tivoli Workload Scheduler:
Planning and Installation Guide does not work.
v Your installation fails and you cannot recover and finish the installation. In this
event, you must determine which steps completed successfully, and start at the
appropriate point in the uninstallation procedure. See “Correcting a failed step
and continuing the installation” on page 131 for a detailed description of the
steps.

Uninstalling manually
The following provides details for uninstalling manually for the following
operating systems:
v “Uninstalling manually on Windows”
v “Uninstalling manually on UNIX” on page 169
To remove an instance of Tivoli Workload Automation that contains an integrated

installation of Tivoli Workload Scheduler and Tivoli Dynamic Workload Console,
first perform the uninstallation of Tivoli Workload Scheduler as described in
“Uninstalling Tivoli Dynamic Workload Console and the embedded WebSphere
Application Server manually” on page 282. Then, to remove Tivoli Dynamic
Workload Console, perform the following steps:
v On Windows, perform steps 5 and 6 on page 282.
v On UNIX, perform step 4.
If you want to remove Tivoli Workload Scheduler from an instance of Tivoli

Workload Automation without removing the Tivoli Workload Automation instance,
contact IBM Software Support.
Uninstalling manually on Windows

If Add or Remove Programs from the Windows Control Panel fails to uninstall Tivoli
Workload Scheduler, perform the following steps:
1. If you have jobs that are currently running on the workstation, wait for them
to finish. To determine which are not finished, check for jobs that are in the
exec state. When there are no jobs in this state, and you have allowed
sufficient time for all events to be distributed in your network, you can
continue with the rest of the procedure.
2. Log on to the computer where Tivoli Workload Scheduler is installed as a user
in the Administrators group.
3. From the TWS_home/bin directory run the following commands:
conman "unlink workstation;noask"
conman "stop;wait"
conman "stopmon;wait"
conman "shut;wait"
4. Stop the processes that are still active as follows:
a. Open Services from the Windows Control Panel and stop the following
IBM Tivoli Workload Scheduler services:
Tivoli Netman for <TWS_user>

Tivoli Token Service for <TWS_user>
Tivoli Workload Scheduler for <TWS_user>
Tivoli Workload Scheduler SSM Agent for <TWS_user>
b. Run Windows Task Manager from the Windows Task Bar to end all the
processes that are already running after stopping the IBM Tivoli Workload
Scheduler services.
If the End Process action does not work, run the following steps from the
TWS_home/unsupported directory:
1) Run listproc.exe
2) Read the PID number associated to the process that you want to end
3) Run killproc.exe <PID>
5. Stop the WebSphere Application Server using the conman stopappserver
command (see Tivoli Workload Scheduler: User's Guide and Reference)

6. Open the %WINDIR%\system32\TWSRegistry.dat (for Windows 32 bit) or

%WINDIR%\TWSRegistry.dat (for Windows 64 bit) file. Delete all the rows that
contain the name of the <TWS_user>. For example, if the user ID is
<TWS_user>, delete the rows containing twsuser, as shown below:
/Tivoli/Workload_Scheduler/twsuser_DN_objectClass=OU
/Tivoli/Workload_Scheduler/twsuser_DN_PackageName=TWS_WINDOWS_twsuser.8.5.0.00
/Tivoli/Workload_Scheduler/twsuser_DN_MajorVersion=8
/Tivoli/Workload_Scheduler/twsuser_DN_MinorVersion=5
/Tivoli/Workload_Scheduler/twsuser_DN_PatchVersion=
/Tivoli/Workload_Scheduler/twsuser_DN_ProductID=TWS_ENGINE
/Tivoli/Workload_Scheduler/twsuser_DN_ou=twsuser
/Tivoli/Workload_Scheduler/twsuser_DN_InstallationPath=C:\TWS\twsuser
/Tivoli/Workload_Scheduler/twsuser_DN_UserOwner=twsuser
/Tivoli/Workload_Scheduler/twsuser_DN_MaintenanceVersion=0
/Tivoli/Workload_Scheduler/twsuser_DN_Agent=MDM
/Tivoli/Workload_Scheduler/twsuser_DN_LPName=TWS_LP_twsuser.8.5.0.00
/Tivoli/Workload_Scheduler/twsuser_DN_LPList=ALL_LANG
For a full description of the TWSRegistry.dat file, see Appendix A, “Registry

file,” on page 309.
7. Stop and remove the Tivoli Workload Scheduler services by issuing the
following commands:
<TWA_home>\eWAS\bin\WASService.exe -stop <TWS_user>
<TWA_home>\eWAS\bin\WASService.exe -remove <TWS_user>
Ensure that the Windows Services panel is closed when you do this.
8. Navigate to the install_dir and take note of the name of the .id file
twainstancexxx.id. You will need this information later in the procedure.
9. Delete the installation directory and all its contents.
10. Depending on what point the installation or uninstallation process reached
before it failed, you might need to remove the Windows services. See the
instructions for running regedit to do this in “Removing Windows registry
keys” on page 173.
11. Remove the file:
%WINDIR%\TWA\twainstancexxx.properties
where xxx is the name of the file you noted in step 8.

12. If you are performing this procedure because you are cleaning up a failed
installation which could not be completed, you should also delete any files
which contain unencrypted passwords.
<TEMP_DIR>/tws85/checkdb_root.bat
<TEMP_DIR>/tws85/checkdbclient.bat
In addition, on all platforms, delete the Tivoli Workload Scheduler response

file if you used a silent installation.
before it failed, you might need to remove the Add or Remove Programs keys.
To do, this, use the system's facilities:
a. Open the Add or Remove Programs option window from the Windows
Control Panel
b. If Tivoli Workload Scheduler is available on the menu, click Remove on it.

c. As you have, in the previous step, removed the uninstaller, a message is

displayed, asking if you want to remove the Add or Remove Programs keys.
Click "Yes" and the keys are removed.
14. Reboot the workstation to remove the services, any DLLs, any daemons, or
any other executable programs from memory.
Cleaning up the Tivoli Configuration Manager directories on

Windows
If you are cleaning the only instance of IBM Tivoli Workload Scheduler on your
workstation and no other product has been installed using IBM Tivoli Configuration
Manager, you can also remove the C:\swdis directory and the %WINDIR%\swdis.ini
file.
If Tivoli Workload Scheduler is not the only product using the IBM Tivoli
Configuration Manager catalog, use wdrmvsp to remove only the entries related to
Tivoli Workload Scheduler. See the product documentation for IBM Tivoli
Configuration Manager.
Note: If you are at all uncertain whether these directories are used by another
product do not remove them: their continued presence is not harmful; it just
occupies disk space.
Uninstalling manually on UNIX

To uninstall manually, perform the following steps:
1. If you have jobs that are currently running on the workstation, wait for them
to finish. To determine which are not finished, check for jobs that are in the
exec state. When there are no jobs in this state, and you have allowed
sufficient time for all events to be distributed in your network, you can
continue with the rest of the procedure.
2. Log on to the computer where Tivoli Workload Scheduler is installed as root.
3. From the <TWS_home>/bin directory run the following commands:
conman "unlink workstation;noask"
conman "stop;wait"
conman "stopmon;wait"
conman "shut;wait"
4. From a shell script run the following command:
ps -ef grep <TWS_install_dir>/bin/jobman
This checks that the following processes are not active:
batchman
jobman
JOBMAN
mailman
monman
netman
ssmagent
stageman
writer
5. Stop the processes that are still active as follows:

kill -9 <pid>
command (see Tivoli Workload Scheduler: User's Guide and Reference

7. Open /etc/TWS/TWSRegistry.dat and delete all the rows containing the

<TWS_user> user ID. For example, if the user ID is <TWS_user>, delete the
rows containing <TWS_user>, as shown below:
/Tivoli/Workload_Scheduler/twsuser_DN_objectClass=OU
/Tivoli/Workload_Scheduler/twsuser_DN_PackageName=TWS_LINUX_twsuser.8.5.0.00
/Tivoli/Workload_Scheduler/twsuser_DN_MajorVersion=8
/Tivoli/Workload_Scheduler/twsuser_DN_MinorVersion=5
/Tivoli/Workload_Scheduler/twsuser_DN_PatchVersion=
/Tivoli/Workload_Scheduler/twsuser_DN_ProductID=TWS_ENGINE
/Tivoli/Workload_Scheduler/twsuser_DN_ou=twsuser
/Tivoli/Workload_Scheduler/twsuser_DN_InstallationPath=/home/twsuser
/Tivoli/Workload_Scheduler/twsuser_DN_UserOwner=twsuser
/Tivoli/Workload_Scheduler/twsuser_DN_MaintenanceVersion=0
/Tivoli/Workload_Scheduler/twsuser_DN_Agent=MDM
/Tivoli/Workload_Scheduler/twsuser_DN_LPName=TWS_LP_twsuser.8.5.0.00
/Tivoli/Workload_Scheduler/twsuser_DN_LPList=ALL_LANG
For a full description of the TWSRegistry.dat file, see Appendix A, “Registry

file,” on page 309.
8. Navigate to the install_dir and take note of the name of the .id file
twainstancexxx.id. You will need this information later in the procedure.
9. Delete the installation directory as follows:
rm -R <TWS_home>
10. Remove the file:
etc\TWA\twainstancexxx.properties
where xxx is the name of the file you noted in step 8.

<TEMP_DIR>/tws85/checkdb_root.sh
<TEMP_DIR>/tws85/checkdbclient.sh
In addition, on all platforms, delete the Tivoli Workload Scheduler response

file if you used a silent installation.
12. Reboot the workstation to remove the services, any DLLs, any daemons, or
any other executable programs from memory.
Cleaning up the Tivoli Configuration Manager directories on

UNIX
If you are cleaning the only instance of Tivoli Workload Scheduler on your
workstation and no other product has been installed using IBM Tivoli Configuration
Manager, you can also remove the .swdis directory from the root user home
directory and the etc/Tivoli/swdis.ini file.
If Tivoli Workload Scheduler is not the only product using the IBM Tivoli
Configuration Manager catalog, use wdrmvsp to remove only the entries related to
Tivoli Workload Scheduler. See the product documentation for IBM Tivoli
Configuration Manager.

Note: If you are at all uncertain whether these directories are used by another
product do not remove them: their continued presence is not harmful; it just
occupies disk space.
Uninstalling Tivoli Workload Scheduler connectors manually

This section describes how to manually remove an instance of a IBM Tivoli
Workload Scheduler connector that did not completely uninstall.
The following are possible scenarios from which you might need to recover:
v You might have removed a previous installation of the connector, but the
uninstall procedure did not work properly and records of the previous
installation were left on your system.
v For some reason the uninstallation as described in Chapter 4, “Installing,” on
page 31 does not work.
v Your installation fails and you cannot recover and finish the installation. In this
event, you must determine which steps completed successfully, and start at the
appropriate point in the uninstallation procedure. See “Correcting a failed step
and continuing the installation” on page 131 for a detailed description of the
steps.
The following provides details for uninstalling manually for the following
operating systems:
v “Uninstalling the connector manually on UNIX”
v “Uninstalling the connector manually on Windows” on page 172
Uninstalling the connector manually on UNIX

If you need to uninstall a connector manually, perform the following steps:
1. Log on to the computer where Tivoli Workload Scheduler is installed as root.
2. Access the directory: <TWS_home>/wastools
4. Delete the installation directory as follows:
rm -R <TWS_home>
This step is not obligatory, but is just to save space on the file system. If you
are in any doubt about risking deleting other Tivoli Workload Scheduler files,
omit this step.
5. Open /etc/TWS/TWSConnRegistry.dat or the /etc/TWS/TWSZConnRegistry.dat,
depending on whether the connector was for the distributed or the z/OS
product, and delete all the rows containing the <TWS_user> user ID.
<TEMP_DIR>/tws85/checkdb_root.sh
<TEMP_DIR>/tws85/checkdbclient.sh

Uninstall connector manually
In addition, on all platforms, delete the Tivoli Workload Scheduler response file
if you used a silent installation (see Table 11 on page 44 for a details about
response file names).
Uninstalling the connector manually on Windows

If you cannot run the add/remove program from the Windows Control Panel,
perform the following steps:
1. Log on to the computer where Tivoli Workload Scheduler is installed as a user
in the Administrators group.
2. Access the directory: <TWS_home>/wastools
4. Stop and remove the Tivoli Workload Scheduler services by issuing the
following commands:
<TWS_home>\eWAS\bin\WASService.exe -remove(<TWS_user>)
<TWS_home>\eWAS\bin\WASService.exe -remove TWSZCONNECTOR(<TWS_user>)
Ensure that the Windows Services panel is closed when you do this.
5. Open the %WINDIR%\System32\TWSConnRegistry.dat or %WINDIR%\System32\
TWSZConnRegistry.dat file, depending on whether the connector is distributed
or z/OS, and delete all the rows that contain the name of the <TWS_user>.
6. Delete the installation directory and all its contents. This step is not obligatory,
but is just to save space on the file system. If you are in any doubt about
risking deleting other Tivoli Workload Scheduler files, omit this step.
before it failed, you might need to remove the Add or Remove Programs keys. To
do, this, use the system's facilities:
a. Open the Add or Remove Programs option window from the Windows
Control Panel
b. If the Tivoli Workload Scheduler connector or connector for z/OS is
available on the menu, click Remove on it.
c. As you have, in the previous step, removed the uninstaller, a message is
displayed, asking if you want to remove the Add or Remove Programs keys.
Click "Yes" and the keys are removed.
<TWS_home>\userdef_wnt
<TEMP_DIR>\tws85/checkdb_root.sh
<TEMP_DIR>\tws85\checkdbclient.sh
In addition, on all platforms, delete the Tivoli Workload Scheduler response file
if you used a silent installation (see “Performing a silent installation” on page
44 for a details of the template response file names).
9. Reboot the workstation to remove the services, any DLLs, any daemons, or any
other executable programs from memory.

Removing Windows registry keys

During the life of this product it has undergone name changes and has been issued
in a number of versions. There is more than one way to install and uninstall the
product. All this leads to the risk that in upgrading from one version to another
one or more Registry key has been inadvertently left undeleted from the Windows
Registry. This procedure is designed to help you remove these unwanted keys.
Note: Making changes to the Windows Registry can have the effect of making the
operating system unusable. Thus you are strongly advised to back up the Registry
before you start.
A similar procedure is described in “Uninstalling manually on Windows” on page

167; the same objective is achieved using different techniques.
This procedure is designed to identify and remove the keys for the following:
v Maestro™ versions 6.0 and 6.1
v Tivoli Workload Scheduler, versions 7.0, 8.1, 8.2.n, 8.3, and 8.4
Depending upon the version of Maestro or Tivoli Workload Scheduler, and the
version of the operating system, some of the keys in this procedure might have
already been removed by the InstallShield wizard uninstall program. If this is the
case, just skip that step and proceed to the next step in the procedure. Some of the
names of the keys vary depending upon the choices made during the installation
of Maestro or Tivoli Workload Scheduler, so make certain that you are aware of
these original choices when locating the keys.
The procedure is as follows:

1. Stop Tivoli Workload Scheduler completely. The easiest way to do this is as
follows:
a. Change to the <TWS_home>\unsupported directory. In this directory are two
files, listproc.exe and killproc.exe.
b. Copy both of these files into the <TWS_home>\bin directory and set a path to
<TWS_home> and <TWS_home>\bin, using the Windows path command.
c. Type the following command:
listproc | more
A page that looks similar to this is displayed:
PID Command # Handles # Threads

624 netman 86 5
332 tokensrv 62 8
1088 writer 60 2
5688 monman 89 3
5364 ssmagent 210 19
1052 mailman 85 2
936 batchup 57 4
1020 batchman 92 2
1036 JOBMAN 91 2
1312 JOBMON 105 3
This table shows the entire Tivoli Workload Scheduler process tree of a
running fault-tolerant agents.
Note: There are other processes belonging to the operating system and
other applications interspersed between these processes.

d. Write down the process ID (pid) of any TWS processes.

e. Stop the processes by issuing the following command for each running
process: killproc <pid>. Killproc is a more reliable tool than the
corresponding Microsoft tool, which does not always stop runaway
processes.
2. Remove Tivoli Workload Scheduler using the InstallShield wizard
uninstallation.
3. Reboot the workstation.
4. Select Start → Run, type regedit and press the enter key.
5. Select HKEY_LOCAL_MACHINE → Software.
6. Remove the keys from versions of Tivoli Workload Scheduler prior to version
8.3:
a. Locate and select the Unison Software, Inc key, and press the delete key.
b. Close Software.
c. Open System → CurrentControlSet → Services.
d. Locate and select the maestro_<workstation>_<user_ID> key and press the
delete key.
e. Locate and select any key called netman_<system_name>_<user_ID> and
press the delete key. DO NOT delete the key above this key called just
Netman because that belongs to Windows.
f. Locate and select any key called tokensrv_<system_name>_<user_ID> and
press the delete key. If you cannot locate a key of this type, look for keys
called <process_name>_<user_ID> and delete them.
7. Remove the keys from Tivoli Workload Scheduler, versions 8.3 and 8.4:
a. Open System → CurrentControlSet → Services.
b. Locate and select the tws_maestro_<user_ID> key and press the delete key.
c. Locate and select the tws_netman_<user_ID> and press the delete key. DO
NOT delete any other key called Netman because that belongs to Windows.
d. Locate and select the tws_tokensrv_<user_ID> and press the delete key.
8. Close regedit.
9. Reboot the workstation.

Chapter 9. Installation, uninstallation, and upgrade messages
This chapter provides help for the messages issued by the installation,
uninstallation, and upgrade of the Tivoli Workload Scheduler engine.
The chapter is divided into the following sections:

v “IBM Tivoli message format” describes the IBM Tivoli message format used by
Tivoli Workload Scheduler, telling you how the message codes are constructed
and how the message help can be used.
v “Installation (InstallShield wizard) common messages - JIC” on page 177 lists the
messages that could be issued by the InstallShield wizard for either Tivoli
Workload Scheduler or Tivoli Dynamic Workload Console - these are common
messages
v “Installation (InstallShield wizard) messages - JIS” on page 183 lists the
messages that could be issued by the InstallShield wizard
v “Installation messages (twsinst) - FAB” on page 236 lists the messages that could
be issued by twsinst
v “Installation messages (fix pack) - FAF” on page 244 lists the messages that
could be issued by the fix pack installation
Note: This guide does not contain any details of Informational messages, as they
are complete within themselves, and do not need further explanation.
IBM Tivoli message format

This section explains the format of the message that is displayed on your screen or
written in a log file. All messages have a message number and a message text.
Many of the error and warning messages also have help. Only messages with
message help are documented in this part of the guide. The help consists of an
explanation of the message, a description of what the system does, and
information about what you must do to resolve the problem.
These items are described in more detail in the following sections.
Message number
Tivoli Workload Scheduler message numbers (codes) have the following format:
AWS<component_code><numeric_identifier><severity>
where the parts of the message are as follows:

AWS The product prefix. This value is used for all Tivoli Workload Scheduler
messages, except those of the z/OS Connector, which use EQQ (the
product code for IBM Tivoli Workload Manager for z/OS).
<component_code>
The three-digit alphabetic code for the Tivoli Workload Scheduler
component, for example ″JIS″.
<numeric_identifier>
A three-digit numeric identifier that is unique within any combination of
prefix and component code.

Message format
<severity>
The severity indicator, as follows:
I Informational: Informational messages provide users with
information or feedback about normal events that have occurred or
are occurring, or request information from users in cases where the
outcome is not negative, regardless of the response.
Examples:
v The status request is processing.
v The files were successfully transferred.
v Do you want to save your output in file a or in file b?
Note: Informational messages issued by Tivoli Workload Scheduler

are not documented in this guide, as they are complete in
themselves and require no further information or
explanation. This also applies to informational messages
giving the usage of the product’s commands – if you require
more information than is given on the screen, refer to Tivoli
W Warning: Warning messages indicate that potentially undesirable
conditions have occurred or could occur, but the program can
continue. Warning messages often ask users to make decisions
before processing continues.
Examples:
v The replay table could not be sent. The link to Agent_name
proceeds with a reduced replay protocol.
v A file already exists with the same name. Do you want to
overwrite this file?
E Error: Error messages indicate problems that require intervention
or correction before the program can continue.
Examples:
v The specified file could not be found.
v You are out of space on the x drive. The file cannot be saved to
this drive.
An example of an error message number is as follows:

AWSBAT003E
Message text
Every attempt has been made to represent the message text exactly as it appears to
the user in the displayed or written message. Any differences that occur are
usually occasioned by the different layout of the book (in two columns) with
respect to the message display panel or log.
Where the system has included variable information in the message text, this
variable information is represented in this guide by an italicized label, describing
the type of information referred to by the variable.
For example, if the message text that appears on your screen is as follows:
The replay table could not be sent.
The link to TRC8470 proceeds with a reduced replay protocol.

AWSJIC001E • AWSJIC003E
the message text shown in the guide would be as follows:

The replay table could not be sent.
The link to Agent_name proceeds with a reduced replay protocol.
In this case the label Agent_name tells you that the information that is inserted by
the system is the name of the agent which could not receive the replay table.
Message help
This chapter provides help for the error and warning messages. The help for each
message is organized as follows:
Explanation
An explanation, where necessary, of the message text.
System action
A description of what the system or process does as a result of the
condition that caused the message.
Operator response
What you must do in response to the condition that caused the message.
Often you are able to resolve such conditions yourself, but sometimes you
are asked to contact IBM Software Support.
See also
A reference to any Tivoli Workload Scheduler publication that might give
you assistance with understanding or resolving the problem.
Installation (InstallShield wizard) common messages - JIC

This section lists error and warning messages that could be generated by the
installation (InstallShield wizard) of Tivoli Workload Scheduler or the Tivoli
Dynamic Workload Console - they are common to both.
The message component code is JIC.
Silent wizard
AWSJIC001E The supplied password for the user
"user" that the wizard must create does 1. Edit the response file used by the silent
not match the security policy of the wizard. Change the password for the
computer on which you are performing indicated user to one that matches the
the installation. security policy.
2. Rerun the silent wizard.
Explanation: See message.
System action: If you are running the interactive
AWSJIC002W The supplied user exists on the local
wizard, the wizard stops.
computer but does not have the correct
If you are running the silent wizard, the wizard fails. rights.
The installation is attempting to modify
Operator response: Check the security policy on the
the rights.
computer where you are performing the installation.
Proceed as follows:
System action: The wizard continues. When the
Interactive wizard
installation starts, the wizard attempts to modify the
1. Click Back to return to the panel where rights of the "user".
you supplied the indicated user and
password. Operator response: None.
2. Change the password to one that matches
the security policy and confirm it. AWSJIC003E The supplied password is incorrect for
3. Click Next to continue. the supplied user.
Explanation: You have specified an existing user but
Chapter 9. Installation, uninstallation, and upgrade messages 177

the supplied password is not correct for that user. Change the account or its password, or log off and on
again using a different user that has the correct
privileges or whose password has not expired.
If you are running the silent wizard, the wizard fails. Rerun the wizard from scratch.
Operator response: Supply a different password or a
Note:This message might also be given when the Create
different user ID and password.
User step is run. This only occurs if, between the time
Proceed as follows: that the wizard validates the input values for the user
ID and password, and the time it runs the Create User
- Interactive wizard
step, any changes are made to the user ID or its
1. Click OK to close the error pop-up password, either on the computer or in the step
window. properties dialogs as a result of a failed installation.
2. Either change the "user", or its password, This is unlikely to occur, but if it does you must rerun
(or both) so that the correct password is the installation.
supplied for the user.
See also: The chapter on Troubleshooting installation,
3. Click Next to continue. migration, and uninstallation for full details of the
- Silent wizard recovery process from a failed installation.
1. Look in the installation log to see if there is

any additional information AWSJIC006E The user running the installation does
2. Edit the response file used by the silent not have the correct privileges to verify
wizard, changing the "user", or its the privileges of the supplied "user".
password, (or both), so that the correct Explanation: The installation program has verified
password is supplied for the user. that either the "Act as part of the operating system"
3. Rerun the silent wizard. privilege is not required, or is present in the profile of
the user running the installation, but the attempt to
See also: The chapter on Troubleshooting installation, verify the "user" has failed for another reason
migration, and uninstallation in Administration for full associated with privileges. It might be that the user
details of the recovery process from a failed installation. does not have the Windows default Administrator
privileges.
AWSJIC005E The supplied "user" account cannot be System action: If you are running the interactive
verified automatically. This is because wizard, the wizard stops.
the user running the installation
program does not have the "Act as part If you are running the silent wizard, the wizard fails.
of the operating system" privilege, or
Operator response: Add the Windows default
the password of the user has expired.
Administrator privileges to the account of the user
Explanation: The user running an installation on running the installation, or rerun the installation as a
Windows 2000 (but not on Windows XP and later) different user. If you change the account on the
requires the "Act as part of the operating system" computer you will almost certainly need to reboot the
privilege. The check for this privilege also fails if the computer. Thus, in either case, if you are running the
password has expired, whether or not the account has interactive wizard you must stop it, as follows:
the privilege. 1. Click OK to close the error popup window.
System action: If you are running the interactive 2. Click Cancel to exit from the installation.
Change the account, or log off and on again using a
If you are running the silent wizard, the wizard fails.
different user that has the correct privileges.
Operator response: Add the privileges to the account
of the user running the installation, renew the Rerun the wizard from scratch.
password, or rerun the installation as a different user. If
you change the account on the computer you will Note:This message might also be given when the Create
almost certainly need to reboot the computer. Thus, in User step is run. This only occurs if, between the time
all cases, if you are running the interactive wizard you that the wizard validates the input values for the user
must stop it, as follows: ID, and the time it runs the Create User step, any
1. Click OK to close the error popup window. changes are made to the user ID, either on the
computer or in the step properties dialogs as a result of
2. Click Cancel to exit from the installation.
a failed installation. This is unlikely to occur, but if it
does you must rerun the installation.

See also: See Chapter 4, “Installing,” on page 31 for Note:This message might also be given when the Create
details of the privileges required to run the installation. User step is run. This only occurs if, between the time
that the wizard validates the input values for the user
ID, and the time it runs the Create User step, any
migration, and uninstallation for full details of the
changes are made to the user ID, either on the
recovery process from a failed installation.
AWSJIC007E The installation was unable to check the does you must rerun the installation.
existence of the supplied "user".
Explanation: The user running the installation has the migration, and uninstallation in Administration and
correct privileges to verify the existence of the "user", Troubleshooting for full details of the recovery process
but a problem associated with the user ID or password from a failed installation.
has prevented it from doing so. It is possible that the
user name or password you supplied contained special
AWSJIC008E The installation could not modify the
characters or characters that do not belong to the
privileges of the supplied "user".
codeset of the computer. It is possible that the account
management facilities of the computer are in use, not Explanation: You have supplied a "user" that exists on
working or are blocked in some other way. the local computer but has insufficient rights. The
installation has tried to modify those rights but cannot.
Probably, the user that is running the installation does
not have the correct rights to modify the supplied
If you are running the silent wizard, the wizard fails. user’s rights.
Operator response: Ensure the following: System action: If you are running the interactive
v Ensure that the "user" ID and password do not wizard, the wizard stops.
contain any unusual characters that might give If you are running the silent wizard, the wizard fails.
codeset translation problems
v Ensure that the user account management facilities
on the computer are not in use by you or any other
running the installation, or rerun the installation as a
user
different user. If you change the account on the
v Ensure that the user account management facilities computer you will almost certainly need to reboot the
are available and working. To do this, attempt to computer. Thus, in either case, if you are running the
access the details of a user account, but be sure to interactive wizard you must stop it, as follows:
close the account management facilities window
1. Click OK to close the error popup window.
when you have finished
If you have found and fixed a problem with the
account management facilities you can continue the Change the account, or log off and on again using a
installation. Otherwise, close the installation and rerun different user that has the correct privileges.
it as a different user
- Interactive wizard Rerun the wizard from scratch.
Continue the installation Note:This message might also be given when the Create
1. Click OK to close the error popup User step is run. This only occurs if, between the time
window. that the wizard validates the input values for the user
2. Click Next to continue. ID, and the time it runs the Create User step, any
Rerun the installation computer or in the step properties dialogs as a result of
1. Click OK to close the error popup a failed installation. This is unlikely to occur, but if it
window. does you must rerun the installation.
2. Click Cancel to quit the See also: The chapter on Troubleshooting installation,
installation. migration, and uninstallation in Administration and
3. Login as a different user. Troubleshooting for full details of the recovery process
4. Rerun the wizard. from a failed installation.
- Silent wizard
Just rerun the wizard in either case.

dlls are responsible for user account verification).

AWSJIC009E The installation could not add the
Depending on what you find, you might need to
supplied "user" to the "Administrators"
reinstall the operating system before continuing with
group.
the installation. Verify also that the user running the
Explanation: You have supplied a "user" ID that did installation has execute permission for operating system
not exist on the computer and the installation has dlls.
created an account for it. However, it could not add the
Whatever the solution to the problem, rerun the
account to the "Administrators" group. Probably, the
wizard. If you are running the interactive wizard you
user that you are using to run the installation does not
need to stop the installation program. Do this as
have the correct privileges to add a user to that group.
follows:
System action: If you are running the interactive 1. Click OK to close the error popup.
2. Click Cancel to close the wizard.
Rerun the wizard from scratch.
running the installation, or rerun the installation as a Note:This message might also be given when the Create
different user. If you change the account on the User step is run. This only occurs if, between the time
computer you will almost certainly need to reboot the that the wizard validates the input values for the user
computer. Thus, in either case, if you are running the ID, and the time it runs the Create User step, any
interactive wizard you must stop it, as follows: changes are made to the dlls. This is unlikely to occur,
but if it does you must rerun the installation.
AWSJIC011E The supplied "user" could not be
created.
Change the account, or log off and on again using a
different user that has the correct privileges. Explanation: You have supplied a "user" ID that did
not exist on the computer but the installation has not
Rerun the wizard from scratch. been able to create it.
that the wizard validates the input values for the user If you are running the silent wizard, the wizard fails.
Operator response: If you are running the interactive
wizard, look at the Output tab on the failed installation
step for further information. Do the following:
does you must rerun the installation. 1. Note down the error code (so that you can later
find it in Administration and Troubleshooting, if
See also: The chapter on Troubleshooting installation, needed)
migration, and uninstallation in Administration and
2. Click OK to close the error popup window. The
Troubleshooting for full details of the recovery process
Diagnose Failure window is opened.
from a failed installation.
3. Select Diagnose failure and click Next. The Step
List window is opened.
AWSJIC010E The installation could not find an
4. Select the failed installation step and double click it
operating system dll to complete the
to open the Step Status window.
"user" verification tasks.
5. Select the Output tab.
Explanation: The installation needs to use a standard
operating system dynamic link library (dll) to complete If you are running the silent wizard, see the installation
its task of verifying, and if necessary creating, the log file for the error messages that might explain why
supplied user. the user cannot be created.
wizard, the wizard stops. Ensure the following:
If you are running the silent wizard, the wizard fails. v Ensure that the "user" ID and password respect local
security policy
Operator response: Verify that the PATH system v Ensure that the user running the installation has the
variable points to the location of all the operating rights to create a user. Remember to close the
system dlls, and that the dlls are present (your account management facilities before proceeding. If it
operating system documentation might identify which

AWSJIC011E
does not, add those rights, or run the installation 6. On the Status tab set the status to
using a user that has those rights. Ready
7. Click Apply. The Step List
The problem resolution depends on what you found: window is displayed.
- Problems with an existing <user> ID or password 8. Click Run all to resume the
installation from that step.
Supply a different "user" ID and password. As
everything in the installation relates to this - Silent wizard
user, you must rerun the installation, 1. Edit the response file used by the
supplying the new "user" ID. silent wizard, changing the "user"
Proceed as follows: password.
2. Resume the installation adding the
Interactive wizard parameter -resume. The wizard
1. Click OK to close the error popup resumes in interactive mode at the
window. Step List window showing the
2. Click Quit to exit from the failed step.
installation. 3. Follow the procedure described
3. Rerun the installation, supplying a for the interactive wizard to
different "user" ID and password. correct the user ID and resume the
installation.
Silent wizard
- Problems with the user privileges
1. Edit the response file used by the
silent wizard, changing the "user" Choose one of these options:
and its password.
Rerun with a different user
1. If you are running the interactive
- Problems with the password supplied for a <user> wizard you need to stop the
that is being created installation program . Do this as
follows:
Supply a different password.
a. Click OK to close the error
Proceed as follows: popup. The Diagnose Failure
- Interactive wizard window is opened.
1. Click OK to close the error popup b. Click Quit to close the wizard.
window. The Diagnose Failure 2. Log on as a different user with the
window is opened. Windows default Administrator
2. Select Diagnose failure and click privileges.
Next. The Step List window is 3. Rerun the installation without a
opened. resume. You cannot do a step
3. Double-click the failed installation resume of an installation if you
step and the Step Status window have changed the user that is
opens. running it; you must rerun the
installation from scratch.
4. On the Properties tab change the
"user" password. If it is not Add the missing privileges to your user
available for editing, return to profile
previous steps, until you find one 1. If you are running the interactive
where you can edit the value or wizard you need to stop the
values. installation program . Do this as
5. Repeat this step for all other steps, follows:
checking to see if the password is a. Click OK to close the error
included as a property for that popup. The Diagnose Failure
step, and changing it if it is. This window is opened.
is because the installation wizard
b. Click Quit to close the wizard.
creates each step as a separate
action, complete with its 2. Add the necessary privileges to
properties; changing a value on the profile of the user running the
one does not change it installation, so that it has the
automatically also on the others. default Administrator privileges
(you might need to log on as an
Administrator to do this).

3. Reboot the computer. System action: If you are running the interactive
4. Resume the installation adding the wizard, the wizard stops.
parameter -resume. The wizard If you are running the silent wizard, the wizard fails.
resumes in interactive mode at the
Step List window showing the Operator response: Proceed as follows:
failed step. - Interactive wizard
5. Double-click the failed installation 1. Click OK to close the error popup window.
step and the Step Status window
opens. 2. Click Back to return to the previous panel
and change the user to a value no longer
6. On the Status tab set the status to than the maximum length.
Ready
3. Click Next to continue.
window is displayed again. - Silent wizard
8. Click Run all to resume the 1. Edit the response file used by the silent
installation from that step. wizard, changing the user to a value no
longer than the maximum length.
migration, and uninstallation in Administration and 2. Rerun the silent wizard.
from a failed installation. AWSJIC014E The supplied "user" "user_ID" does not
exist on the local computer, but the
AWSJIC012E The supplied "user" name incorrectly installation cannot create this user,
contains a period. because another object exists with the
supplied name.
Explanation: This message indicates that during the
recovery operation of a previously failed installation, Explanation: You have supplied a user ID that does
you modified the "user" name and included a period in not exist. The installation has tried to create a user with
the name. The "user" ID was validated on input, and the supplied ID, but has found another object exists
the presence of a period would not have allowed the (such as a domain or a user group) with the supplied
installation to go ahead. ID.
System action: If you are running the interactive System action: If you are running the interactive
wizard, the wizard stops. wizard, the wizard stops.
If you are running the silent wizard, the wizard fails. If you are running the silent wizard, the wizard fails.
Operator response: You must rerun the wizard, Operator response: Choose a different user ID that
reinputting the "user" ID as follows: does not exist on this computer in any form and rerun
the installation without a resume. You cannot do a step
- Interactive wizard resume of an installation if you have changed the
1. Click OK to close the error popup window. "user", you must rerun the installation from scratch.
2. Click Quit to exit from the installation. Interactive wizard
3. Rerun the installation, resupplying the 1. Close the Step Status window
"user" ID and password. 2. Select Quit installation. The wizard closes.
- Silent wizard 3. Rerun the wizard.
1. Rerun the silent wizard. Silent wizard.
See also: The chapter on Troubleshooting installation, 1. Rerun the silent wizard.
from a failed installation. AWSJIC015E The supplied "user" ID incorrectly
contains a period.
AWSJIC013E The supplied "user" ID is longer than Explanation: This message indicates that during the
the maximum length of maximum_length recovery operation of a previously failed installation,
bytes. you modified the "user" ID and included a period in
the name. The "user" ID was validated on input, and
Explanation: See message. the presence of a period would not have allowed the
installation to go ahead.
maximum_length is the maximum permitted length in
bytes of the "user" ID. System action: If you are running the interactive

AWSJIC016E • AWSJIS002E
If you are running the silent wizard, the wizard fails. page 16 for information about the required
characteristics of the <user>.
Operator response: You must rerun the wizard,
reinputting the "user" ID as follows:
AWSJIC017W The specified user is a domain user.
Check that it has the required rights.
1. Click OK to close the error popup window. See "Administration and
2. Click Quit to exit from the installation. Troubleshooting" for details.
3. Rerun the installation, resupplying the Explanation: A domain user must have the following
"user" ID and password. rights:
- Silent wizard - On a computer that is a member of a domain
Only a domain user can start the application
See also: The chapter on Troubleshooting installation, server process. It must have the following
migration, and uninstallation in Administration and characteristics:
Troubleshooting for full details of the recovery process v It is a member of the domain administrative
from a failed installation. groups in the domain controller
v It has the "Act as part of the operating
AWSJIC016E The supplied "user" does not exist. On system" privilege in the Domain Security
UNIX platforms the user chosen for the Policy on the domain controller
"user" must exist with the correct v It has the "Act as part of the operating
permissions before starting the system" privilege in the Local Security
installation program. Policy on the local computer
Explanation: See message text. v If the server is run as a service, it has the
"Log on as a service" privilege on the local
System action: If you are running the interactive computer.
- On a computer that is a domain controller
It must have the following characteristics:
Operator response: Choose an existing user or create
an account expressly for the installation. You must v It is a member of the domain administrative
rerun the wizard, changing the "user" ID as follows: groups in the domain controller
- Interactive wizard system" privilege in the Domain Security
1. Click OK to close the error popup window. Policy on the domain controller
2. Click Quit to exit from the installation. v If the server is run as a service, it has the
3. Rerun the installation, supplying a "Log on as a service" privilege on the
different "user" ID and its password. domain controller
- Silent wizard System action: The installation panel flow waits for
you to continue.
1. Edit the response file, changing the "user"
ID and its password. Operator response: Check the rights of the domain
2. Rerun the silent wizard. user and click Next to continue.
See also: See “Tivoli Workload Scheduler user” on
Installation (InstallShield wizard) messages - JIS

This chapter lists error and warning messages that could be generated by the
installation (InstallShield wizard).
The message component code is JIS.

command_or_script is the command that has failed. It
AWSJIS002E An internal error has occurred. The
might be an operating system command or a Tivoli
command or script "command_or_script"
Workload Scheduler installation script.
has failed. The exit code is as follows:
"exit_code". exit_code is the error code given by the command or
Contact IBM Software Support. script.

AWSJIS006E • AWSJIS008E

AWSJIS006E No valid instance of Tivoli Workload
Scheduler has been found to upgrade.
If you are running the silent wizard, the wizard fails. Select a valid instance or make a fresh
installation.
Operator response: Proceed as follows:
Explanation: Either no instance of Tivoli Workload
- Interactive wizard Scheduler was found at the indicated location, or the
1. Click OK to close the error message. The instance found is not at the correct version. Only
Diagnose Failure window is opened. versions 8.2, 8.2.1, 8.3 or 8.4 can be upgraded to version
2. If you want to diagnose the problem 8.5. All other versions must first be upgraded to 8.2,
without leaving the wizard (recommended) 8.2.1, 8.3 or 8.4.
select Diagnose failure and click Next, and System action: If you are running the interactive
follow the procedure described in wizard, the wizard stops.
Administration and Troubleshooting for
diagnosing a failed installation. If you are running the silent wizard, the wizard fails.
Otherwise, select Quit installation. The Operator response: Proceed as follows:
wizard closes.
- Silent wizard
1. Click OK to close the error message
Look in the installation log to see if there is window.
any additional information. 2. Click Back to return to the previous panel
and change the Tivoli Workload Scheduler
Check any available information related to the exit_code. instance definition to identify an instance
In the case of an operating system command you might of version 8.2, 8.2.1, 8.3 or 8.4, or choose to
have to consult the operating system documentation. make a fresh installation.
If you have copied the installation images to the local
hard disk or to a remote workstation, ensure that the - Silent wizard
entire disk image was copied, and that the binary 1. Look in the installation log to see if there is
option was set if FTP was used. any additional information
2. Edit the response file used by the silent
If you cannot correct the problem, contact IBM wizard, changing the parameter that
Software Support for assistance. identifies the existing Tivoli Workload
Scheduler instance to an instance of
If you think you can solve the problem, make any version 8.2, 8.2.1, 8.3 or 8.4, or choosing to
necessary corrections to the installation environment. make a fresh installation.
Proceed as follows:
Resume the step that has failed. migration, and uninstallation in Administration and
- Silent wizard from a failed installation.
You cannot troubleshoot a failed installation
with the silent wizard. Instead, do as follows: AWSJIS008E The passwords do not match.
1. Resume the installation adding the Retype the password and the
parameter -resume. The wizard resumes in verification password, ensuring that
interactive mode at the Step List window they are both the same.
showing the failed step.
Explanation: You have supplied a password for the
2. Restart the step that failed. "TWS_user" and have confirmed it, but the passwords
See also: The chapter on Troubleshooting installation, are different.
migration, and uninstallation in Administration and System action: The wizard stops.
from a failed installation. Operator response:
1. Click OK to close the error message.
2. Retype the passwords, ensuring that they are both
the same.

AWSJIS009E The following field: "field_name" is AWSJIS011E The supplied installation path is not
longer than the maximum of max_length valid.
bytes.
Explanation: See message. For example, you might
Explanation: See message. have supplied one or more characters that cannot be
used in a file path.
field_name is the name of the field that is too long.
max_length is the maximum number of bytes it can be.
2. Re-enter the installation path, ensuring that
1. Click OK to close the error message. the path is fully qualified and valid, and
2. Re-enter the indicated field, ensuring that click Next to continue.
it does not exceed the maximum length,
- Silent wizard
and click Next to continue.
1. Edit the response file, and ensure that the
- Silent wizard installation path is fully qualified and
1. Edit the response file, and ensure that the valid.
field does not exceed the maximum length. 2. Rerun the silent wizard.
AWSJIS012E There is insufficient disk space
AWSJIS010E The following field: "field_name" is either available in the directory directory to
not a number or outside the following complete the installation.
range: "from_value - to_value". The installation requires required_space
megabytes, but only available_space
Explanation: See message. megabytes are available.
field_name is the name of the field that is either not a Either make more space available or
number or out of range. change the installation directory.
from_value and to_value indicate the minimum and Explanation: See message.
maximum values it can take. directory is the install directory that has insufficient
System action: If you are running the interactive space.
wizard, the wizard stops. required_space and available_space indicate what space
If you are running the silent wizard, the wizard fails. the installation requires and how much is available.
Operator response: Proceed as follows: System action: If you are running the interactive
2. Re-enter the indicated field, ensuring that Operator response:
the value is a number, that it falls within - Make space in the original path
the indicated range, and click Next to
continue. If you want to persist with the original
installation path, use the operating system’s
- Silent wizard commands and utilities to make more space
1. Edit the response file, and ensure that the available. When you have done this, proceed
field value is a number and falls within the as follows:
indicated range.
Interactive wizard
1. Click OK to close the error
message.
Silent wizard

- Choose another directory 2. Click Back to return to the previous panel

and change the directory of the Tivoli
If you cannot make sufficient space, you need
Workload Scheduler instance, or choose to
to change the installation path to one with
make a fresh installation.
sufficient available space. To do this, proceed
as follows: 3. Click Next to continue.
Interactive wizard - Silent wizard

1. Click OK to close the error 1. Look in the installation log to see if there is
message. any additional information
2. Reenter the installation path, 2. Edit the response file used by the silent
ensuring that the path is fully wizard, changing the parameter that
qualified and valid, and points to identifies the directory of the existing
a directory with sufficient space. Tivoli Workload Scheduler instance, or
Click Next to continue. choosing to make a fresh installation.
Silent wizard
1. Edit the response file, and ensure
that the installation path is fully AWSJIS019E An internal error has occurred. The
qualified and valid, and points to directory to be used for the install
a directory with sufficient space. location of the embedded WebSphere
Application Server does not exist.
Explanation: The install directory for the embedded
WebSphere Application Server is created by the install
AWSJIS017E You are correcting an installation
program within the Tivoli Workload Scheduler install
parameter by editing the parameters of
directory. This message could arise if the directory in
an installation step, but an incorrect
question has not been created correctly, or has been
parameter has been supplied during the
deleted before being used.
correction.
System action: The installation cannot continue.
Operator response: Check the parameters that you
Operator response: Check the installation log to see if
have changed or supplied during the resume of an
there is any further information that helps you to
installation, and ensure that you have supplied valid
understand why the directory could not be found.
values:
v If you locate the error, correct it and continue. The problem is resolved by just rerunning the
installation.
v If you cannot locate the error quit the installation
and resume it. - Rerun the interactive wizard
See also: The chapter on Troubleshooting installation, 1. If you are running the interactive wizard,
migration, and uninstallation in Administration and click OK to close the error message
Troubleshooting for full details of the recovery process window. The Diagnose Failure window is
from a failed installation. opened.
2. Select Quit installation. The wizard closes.
AWSJIS018E An internal error has occurred. The 3. If you previously copied the installation
directory specified as the location of the images to the local hard disk or to a
existing Tivoli Workload Scheduler remote workstation, ensure that the entire
instance does not exist. disk image was copied, and that the binary
option was set if ftp was used.
4. Rerun the wizard.
- Rerun the silent wizard.
1. If you have copied the installation images
If you are running the silent wizard, the wizard fails. to the local hard disk or to a remote
Operator response: Proceed as follows: workstation, ensure that the entire disk
image was copied, and that the binary
- Interactive wizard option was set if ftp was used.
1. Click OK to close the error message. 2. Rerun the silent wizard.

If the problem persists contact IBM Software Support Check that you have copied the installation images
for assistance. correctly to the computer where you are running the
installation wizard.
migration, and uninstallation in Administration and If you are running the interactive wizard, look at the
Troubleshooting for full details of the recovery process Output tab on the failed installation step for further
from a failed installation. information. Do the following:
1. Note down the error code (so that you can later
AWSJIS020E The directory specified as the location find it in Administration, if needed)
of the existing DB2 instance does not 2. Click OK to close the error message window. The
exist. Diagnose Failure window is opened.
Specify the correct location of the DB2 3. Select Diagnose failure and click Next. The Step
instance. List window is opened.
Explanation: See message. 4. Select the failed installation step and double click it
wizard, the wizard stops. 5. Select the Output tab.
If you are running the silent wizard, the wizard fails. If you are running the silent wizard, check the
Operator response: Check the path you supplied for installation log for more information.
the existing DB2 instance that you would like to use
with Tivoli Workload Scheduler. The problem is resolved by just rerunning the
installation.
Proceed as follows:
- Rerun the interactive wizard
1. If you are running the interactive wizard,
1. Click OK to close the error message. close the Step Status window and click
2. Correct the DB2 instance path and click Finish on the Step List window. The
Next to continue. wizard closes.
- Silent wizard 2. If you previously copied the installation
images to the local hard disk or to a
1. Edit the response file, changing the DB2
remote workstation, ensure that the entire
instance path to the correct value.
disk image was copied, and that the binary
2. Rerun the silent wizard. option was set if ftp was used.
application server profile "profile" for the
embedded WebSphere Application 1. If you have copied the installation images
Server could not be created. to the local hard disk or to a remote
workstation, ensure that the entire disk
Explanation: The installation program needs to create image was copied, and that the binary
an application server profile for the embedded option was set if ftp was used.
WebSphere Application Server, and then populate it
with the information specific to Tivoli Workload
Scheduler. This message is displayed because the
If the problem persists contact IBM Software Support
profile could not be created.
for assistance.
If you are running the silent wizard, the wizard fails. Troubleshooting for full details of the recovery process
Operator response: Check that the computer where
you are installing Tivoli Workload Scheduler satisfies
the prerequisite requirements of the embedded AWSJIS022E An internal error has occurred. The
WebSphere Application Server . These can be found by application server profile archive
clicking the System requirements link on the product "profile_archive" for the embedded
information Web page for the embedded WebSphere WebSphere Application Server could
Application Server at www.ibm.com. not be read.
Check that there is sufficient space in the standard Explanation: The installation program needs to create
temporary directory of the computer. an application server profile for the embedded
WebSphere Application Server , and then populate it

AWSJIS023E
with the information specific to Tivoli Workload

Scheduler. This message is displayed because the
update of the configuration of the
profile archive that contains the information needed to
embedded WebSphere Application
populate the profile could not be read.
Server has failed.
Explanation: The embedded WebSphere Application
Server is installed with a default configuration, which
If you are running the silent wizard, the wizard fails. is then updated for Tivoli Workload Scheduler. The
update has failed.
Operator response: Check that you have copied the
installation images correctly to the computer where you System action: If you are running the interactive
are running the installation wizard. wizard, the wizard stops.
If you are running the interactive wizard, look at the If you are running the silent wizard, the wizard fails.
Output tab on the failed installation step for further
Operator response: Check that you have copied the
information. Do the following:
installation images correctly to the computer where you
1. Note down the error code (so that you can later are running the installation wizard.
needed) If you are running the interactive wizard, look at the
2. Click OK to close the error message window. The
needed)
2. Click OK to close the error message window. The
If you are running the silent wizard, check the
installation log for more information. 4. Select the failed installation step and double click it
The problem is resolved by just rerunning the 5. Select the Output tab.
installation.
If you are running the silent wizard, check the
- Rerun the interactive wizard installation log for more information.
close the Step Status window and click The problem is resolved by just rerunning the
Finish on the Step List window. The installation.
wizard closes.
2. If you previously copied the installation
images to the local hard disk or to a 1. If you are running the interactive wizard,
remote workstation, ensure that the entire close the Step Status window and click
disk image was copied, and that the binary Finish on the Step List window. The
option was set if ftp was used. wizard closes.
3. Rerun the wizard. 2. If you previously copied the installation
- Rerun the silent wizard. remote workstation, ensure that the entire
1. If you have copied the installation images disk image was copied, and that the binary
to the local hard disk or to a remote option was set if ftp was used.
workstation, ensure that the entire disk 3. Rerun the wizard.
option was set if ftp was used. - Rerun the silent wizard.
2. Rerun the silent wizard. 1. If you have copied the installation images
to the local hard disk or to a remote
If the problem persists contact IBM Software Support workstation, ensure that the entire disk
for assistance. image was copied, and that the binary
for assistance.

See also: The chapter on Troubleshooting installation, 3. If you have copied the installation
migration, and uninstallation in Administration and images to the local hard disk or to
Troubleshooting for full details of the recovery process a remote workstation, ensure that
from a failed installation. the entire disk image was copied,
and that the binary option was set
if ftp was used.
AWSJIS024E The application server "application_server"
could not be started. 4. Rerun the wizard.
Explanation: The indicated application_server runs - Silent wizard

Tivoli Workload Scheduler on the embedded Resume the step of the silent wizard
WebSphere Application Server, but the application
server could not be started after the installation. You cannot troubleshoot a failed
installation with the silent wizard.
System action: If you are running the interactive Instead, do as follows:
If you are running the silent wizard, the wizard fails. parameter -resume. The wizard
Operator response: Check the application server’s logs
Step List window showing the
to determine why the server could not be started.
failed step.
If you are running the interactive wizard, look at the 2. Resume the step that failed.
information. Do the following: If this does not resolve the problem,
try rerunning the silent wizard, as
follows.
needed) Rerun the silent wizard.
2. Click OK to close the error message window. The 1. If you have copied the installation
Diagnose Failure window is opened. images to the local hard disk or to
3. Select Diagnose failure and click Next. The Step a remote workstation, ensure that
List window is opened. the entire disk image was copied,
if ftp was used.
If you can solve the problem, do so, and proceed as
for assistance.
follows:
You might be able to resume the step, or you might migration, and uninstallation in Administration and
have to rerun the installation from the beginning. Troubleshooting for full details of the recovery process
Restart the step of the interactive wizard AWSJIS025E An internal error has occurred. The
1. On the Status tab set the status to script "script" used by the installation
Ready wizard has failed.
2. Click Apply. The Step List Explanation: See message.
window is displayed.
3. Click Run all to resume the script identifies the script that has failed.
installation from that step. System action: If you are running the interactive
If the problem is not resolved, try
exiting from the wizard and If you are running the silent wizard, the wizard fails.
recommencing the installation, as Operator response: Check the installation log to
follows. determine why the script failed.
Rerun the interactive wizard If you are running the interactive wizard, look at the
1. Close the Step Status window Output tab on the failed installation step for further
2. Select Quit installation. The information. Do the following:
wizard closes.

AWSJIS029E
1. Note down the error code (so that you can later If this does not resolve the problem,
find it in Administration and Troubleshooting, if try rerunning the silent wizard, as
needed) follows.
2. Click OK to close the error message window. The Rerun the silent wizard.
1. If you have copied the installation
3. Select Diagnose failure and click Next. The Step images to the local hard disk or to
List window is opened. a remote workstation, ensure that
4. Select the failed installation step and double click it the entire disk image was copied,
to open the Step Status window. and that the binary option was set
5. Select the Output tab. if ftp was used.
follows: If the problem persists contact IBM Software Support
for assistance.
You might be able to resume the step, or you might
have to rerun the installation from the beginning.
- Interactive wizard Troubleshooting for full details of the recovery process
Resume the step of the interactive wizard
1. On the Status tab set the status to
Ready AWSJIS029E An internal error has occurred. The
directory where the installation expected
2. Click Apply. The Step List to find the JRE files does not exist.
3. Click Run all to resume the Explanation: The installation program is trying to
installation from that step. locate the directory where the Java Runtime
Environment files were unpacked at the beginning of
the installation, but has failed to find it. Either the
unpacking of the installation bundle failed, or the
exiting from the wizard and
directory has subsequently been renamed or deleted.
recommencing the installation, as
follows. System action: If you are running the interactive
Rerun the interactive wizard
1. Close the Step Status window If you are running the silent wizard, the wizard fails.
2. Select Quit installation. The Operator response: If you are running the interactive
wizard closes. wizard, look at the Output tab on the failed installation
3. If you have copied the installation step for further information. Do the following:
images to the local hard disk or to 1. Note down the error code (so that you can later
a remote workstation, ensure that find it in Administration and Troubleshooting, if
the entire disk image was copied, needed)
and that the binary option was set 2. Click OK to close the error message window. The
if ftp was used. Diagnose Failure window is opened.
4. Rerun the wizard. 3. Select Diagnose failure and click Next. The Step
- Silent wizard List window is opened.
Resume the step of the silent wizard
You cannot troubleshoot a failed 5. Select the Output tab.
Instead, do as follows: Ensure that you are not trying to run two installations
1. Resume the installation adding the concurrently, which is not possible.
parameter -resume. The wizard
resumes in interactive mode at the If you can solve the problem, do so, and proceed as
Step List window showing the follows:
failed step.
2. Resume the step that failed. The problem is resolved by just rerunning the
installation.

1. Close the Step Status window The problem is resolved by just rerunning the
2. Select Quit installation. The wizard closes. installation.
3. If you have copied the installation images - Rerun the interactive wizard
to the local hard disk or to a remote 1. Close the Step Status window
option was set if ftp was used. 3. If you have copied the installation images
- Rerun the silent wizard. image was copied, and that the binary
1. If you have copied the installation images option was set if ftp was used.
to the local hard disk or to a remote 4. Rerun the wizard.
option was set if ftp was used. 1. If you have copied the installation images
for assistance
migration, and uninstallation in Administration and If the problem persists contact IBM Software Support
Troubleshooting for full details of the recovery process for assistance
AWSJIS030E An internal error has occurred. The Troubleshooting for full details of the recovery process
build file that the installation program from a failed installation.
expected to find does not exist.
Explanation: The installation program is trying to AWSJIS031E An internal error has occurred. An
locate the build file that was unpacked at the beginning internal program has failed.
of the installation, but has failed to find it. Either the
unpacking of the installation bundle failed, or the file Explanation: See message.
has subsequently been renamed or deleted. System action: If you are running the interactive
System action: If you are running the interactive wizard, the wizard stops.
wizard, the wizard stops. If you are running the silent wizard, the wizard fails.
If you are running the silent wizard, the wizard fails. Operator response: If you are running the interactive
Operator response: If you are running the interactive wizard, look at the Output tab on the failed installation
wizard, look at the Output tab on the failed installation step for further information. Do the following:
step for further information. Do the following: 1. Note down the error code (so that you can later
1. Note down the error code (so that you can later find it in Administration and Troubleshooting, if
find it in Administration and Troubleshooting, if needed)
needed) 2. Click OK to close the error message window. The
2. Click OK to close the error message window. The Diagnose Failure window is opened.
Diagnose Failure window is opened. 3. Select Diagnose failure and click Next. The Step
3. Select Diagnose failure and click Next. The Step List window is opened.
List window is opened. 4. Select the failed installation step and double click it
4. Select the failed installation step and double click it to open the Step Status window.
to open the Step Status window. 5. Select the Output tab.
Ensure that you are not trying to run two installations follows:
concurrently, which is not possible.
You might be able to resume the step, or you might
If you can solve the problem, do so, and proceed as have to rerun the installation from the beginning.
follows: - Interactive wizard

AWSJIS032E

AWSJIS032E An internal error has occurred. An
1. On the Status tab set the status to internal program has not been supplied
Ready with a required parameter.
Explanation: The internal program that creates the
Tivoli Workload Scheduler instance (Ant) is called by
3. Click Run all to resume the the installation program, which supplies the parameters
installation from that step. it requires. One of these parameters is missing. It is
possible that during a previous resume of a failed
If the problem is not resolved, try installation, a required value was inadvertently deleted
exiting from the wizard and from a step or modified.
follows. System action: If you are running the interactive
1. Close the Step Status window
2. Select Quit installation. The Operator response: If you are running the interactive
wizard closes. wizard, look at the Output tab on the failed installation
step for further information. Do the following:
images to the local hard disk or to 1. Note down the error code (so that you can later
a remote workstation, ensure that find it in Administration and Troubleshooting, if
the entire disk image was copied, needed)
and that the binary option was set 2. Click OK to close the error message window. The
if ftp was used. Diagnose Failure window is opened.
4. Rerun the wizard. 3. Select Diagnose failure and click Next. The Step
- Silent wizard
Resume the step of the silent wizard to open the Step Status window.
You cannot troubleshoot a failed 5. Select the Output tab.
Instead, do as follows: If you have already tried resuming this installation,
1. Resume the installation adding the check that you did not inadvertently invalidate any of
parameter -resume. The wizard the step parameters, by looking at the values in the
resumes in interactive mode at the Properties tab on the Step Status panel of the step that
Step List window showing the failed. You might have to return to a previous step to
failed step. be able to modify the field.
2. Resume the step that failed.

If this does not resolve the problem, follows:
follows. In the interactive wizard, if you think you have
corrected an error in the step properties, you might be
Rerun the silent wizard.
able to resume the modified step, or you might have to
1. If you have copied the installation rerun the installation from the beginning.
images to the local hard disk or to
a remote workstation, ensure that - Interactive wizard
the entire disk image was copied, Resume the step of the interactive wizard
if ftp was used.
Ready
for assistance. 3. Click Run all to resume the
migration, and uninstallation in Administration and If the problem is not resolved, try
Troubleshooting for full details of the recovery process exiting from the wizard and
from a failed installation. recommencing the installation, as
follows.

AWSJIS036W • AWSJIS038E
Rerun the interactive wizard System action: If you are running the interactive
1. Close the Step Status window wizard, the wizard stops.
2. Select Quit installation. The If you are running the silent wizard, the wizard fails.
wizard closes.
Operator response: The installation has completed at
3. If you have copied the installation this point, so remedial action is not necessary. The
images to the local hard disk or to temporary files might still be present on your disk, and
a remote workstation, ensure that if you can easily find them and delete them, do so.
the entire disk image was copied, However, they might not be easy to find (if another
and that the binary option was set user or process has changed the directory name) and
if ftp was used. do not occupy enough space to make it worth while
4. Rerun the wizard. spending time searching for and deleting them.
- Silent wizard
AWSJIS038E An internal error has occurred. An
unspecified internal error has occurred
You cannot troubleshoot a failed during the installation process.
Explanation: The installation process has determined
Instead, do as follows:
that an error has occurred, but is unable to give any
1. Resume the installation adding the more-detailed information.
resumes in interactive mode at the System action: If you are running the interactive
Step List window showing the wizard, the wizard stops.
failed step. If you are running the silent wizard, the wizard fails.
If this does not resolve the problem, wizard, look at the Output tab on the failed installation
try rerunning the silent wizard, as step for further information. Do the following:
follows. 1. Note down the error code (so that you can later
Rerun the silent wizard. find it in Administration and Troubleshooting, if
needed)
images to the local hard disk or to 2. Click OK to close the error message window. The
a remote workstation, ensure that Diagnose Failure window is opened.
the entire disk image was copied, 3. Select Diagnose failure and click Next. The Step
and that the binary option was set List window is opened.
if ftp was used. 4. Select the failed installation step and double click it
2. Rerun the silent wizard. to open the Step Status window.
for assistance. Ensure that you are not trying to run two installations
See also: The chapter on Troubleshooting installation, concurrently, which is not possible.
Troubleshooting for full details of the recovery process If you can solve the problem, do so, and proceed as
from a failed installation. follows:
The problem is resolved by just rerunning the

AWSJIS036W The temporary directory created installation.
previously by the Tivoli Workload
Scheduler installation does not exist. - Rerun the interactive wizard
Explanation: The internal program that cleans up after 1. Close the Step Status window
the Tivoli Workload Scheduler instance is trying to 2. Select Quit installation. The wizard closes.
delete the temporary files that the installation used, but 3. If you have copied the installation images
the directory that contains those files cannot be found. to the local hard disk or to a remote
It might have been deleted or renamed during the workstation, ensure that the entire disk
installation by a user or process other than the image was copied, and that the binary
installation. Alternatively, the value of the directory option was set if ftp was used.
name might have been inadvertently changed during
the editing of the data in a step while recovering from
an installation failure. - Rerun the silent wizard.

1. If you have copied the installation images System action: If you are running the interactive
to the local hard disk or to a remote wizard, the wizard stops.
option was set if ftp was used. Operator response: The product cannot run
2. Rerun the silent wizard. successfully without the indicated registry key. You are
strongly advised to treat this as an internal error and
If the problem persists contact IBM Software Support contact IBM Software Support for assistance.
for assistance However, you might decide to attempt to use regedit
See also: The chapter on Troubleshooting installation, to add the key. Bear in mind that Microsoft warn you
migration, and uninstallation in Administration and that the incorrect use of regedit might render the
Troubleshooting for full details of the recovery process computer unusable. If you do decide to go ahead using
from a failed installation. regedit, verify that your Windows registry has the key
HKEY_LOCAL_MACHINE\SOFTWARE
AWSJIS039E Tivoli Workload Scheduler cannot be
. Add it if it does not. Remember to close regedit
started.
before proceeding.
Start it manually.
Explanation: See message. The installation can now be resumed at the failed step,
as follows:
wizard, the wizard stops. - Resume the step of the interactive wizard
If you are running the silent wizard, the wizard fails. 1. Click OK to close the error message
window. The Diagnose Failure window is
However, in both cases the installation is complete, opened.
provided that you can solve the reason why Tivoli
2. Select Diagnose failure and click Next. The
Workload Scheduler cannot be started.
Step List window is opened.
Operator response: Look in the Tivoli Workload 3. Double-click the failed installation step and
Scheduler log files to determine why it cannot be the Step Status window opens.
started. If you can solve the problem that is revealed,
4. On the Status tab set the status to Ready
do so. Then start Tivoli Workload Scheduler manually,
as described in the Reference Manual. 5. Click Apply. The Step List window is
displayed again.
6. Click Run all to resume the installation
from that step.
from a failed installation. - Resume the step of the silent wizard
See also: Reference Manual for a description of how to You cannot troubleshoot a failed installation
start Tivoli Workload Scheduler. with the silent wizard. Instead, do as follows:
AWSJIS041E The installation cannot add the parameter -resume. The wizard resumes in
following key to the Windows registry: interactive mode at the Step List window
registry_key. showing the failed step.
2. Resume the step that failed, as described
Explanation: The installation was attempting to add
above.
the following registry key
\IBM\Tivoli Workload Scheduler If the problem persists contact IBM Software Support
for assistance.
to the standard
HKEY_LOCAL_MACHINE\SOFTWARE
registry key.
The attempt has failed, probably because the standard
HKEY_LOCAL_MACHINE\SOFTWARE AWSJIS042E The installation cannot add the
following key to the Windows registry:
registry_key with values
registry key has been deleted or renamed.
registry_key_values.

Explanation: The installation is attempting to add the the key does not exist or has been renamed.
indicated values to a key it expects to exist. Maybe the
key does not exist or has been renamed.
Operator response: The product cannot run
successfully without deleting the indicated registry key.
Operator response: The product cannot run You are strongly advised to treat this as an internal
successfully without the indicated registry key. You are error and contact IBM Software Support for assistance.
strongly advised to treat this as an internal error and
However, you might decide to attempt to use regedit
contact IBM Software Support for assistance.
to delete the key. Bear in mind that Microsoft warn you
However, you might decide to attempt to use regedit that the incorrect use of regedit might render the
to add the key. Bear in mind that Microsoft warn you computer unusable. If you do decide to go ahead using
that the incorrect use of regedit might render the regedit, verify whether your Windows registry has the
computer unusable. If you do decide to go ahead using indicated key. Delete it if it does. Remember to close
regedit, verify that your Windows registry has the regedit before proceeding.
indicated key. Add it if it does not. Remember to close
The installation can now be resumed at the failed step,
regedit before proceeding.
as follows:
The installation can now be resumed at the failed step,
- Resume the step of the interactive wizard
as follows:
- Resume the step of the interactive wizard The Diagnose Failure window is opened.
1. Click OK to close the error popup window. 2. Select Diagnose failure and click Next. The
The Diagnose Failure window is opened. Step List window is opened.
2. Select Diagnose failure and click Next. The 3. Double-click the failed installation step and
Step List window is opened. the Step Status window opens.
3. Double-click the failed installation step and 4. On the Status tab set the status to Ready
the Step Status window opens.
5. Click Apply. The Step List window is
4. On the Status tab set the status to Ready displayed again.
5. Click Apply. The Step List window is 6. Click Run all to resume the installation
displayed again. from that step.
- Resume the step of the silent wizard
from that step.
You cannot troubleshoot a failed installation
with the silent wizard. Instead, do as follows:
You cannot troubleshoot a failed installation 1. Resume the installation adding the
with the silent wizard. Instead, do as follows: parameter -resume. The wizard resumes in
1. Resume the installation adding the interactive mode at the Step List window
parameter -resume. The wizard resumes in showing the failed step.
interactive mode at the Step List window 2. Resume the step that failed, as described
showing the failed step. above.
above. If the problem persists contact IBM Software Support
for assistance.
for assistance.
See also: The chapter on Troubleshooting installation, Troubleshooting for full details of the recovery process
migration, and uninstallation in Administration and from a failed installation.
AWSJIS044E The installation cannot install the
following Windows service: service_name.
AWSJIS043E The installation cannot delete the
Explanation: The reason might be that you do not
following key from the Windows
have the correct rights to install services, the service
registry: registry_key.
might already exist or the user account name specified
Explanation: The installation is attempting to delete might not exist.
the indicated registry key that it expects to exist. Maybe

AWSJIS045E

AWSJIS045E The installation cannot delete the
following Windows service: service_name.
Explanation: The reason might be that you do not
Operator response: Follow these steps: have the correct rights to delete services, or the service
1. Using the Windows user account management might not exist.
facilities, check that the user performing the System action: If you are running the interactive
installation exists, and has the right to install wizard, the wizard stops.
services. If not, add this right. Remember to close
the user account management facilities window If you are running the silent wizard, the wizard fails.
before proceeding. Operator response: Follow these steps:
2. If the user exists and its rights are correct, open the 1. Using the Windows user account management
Windows Services panel. Check if the indicated facilities, check that the user performing the
service already exists. If it does, probably a previous installation exists, and has the right to delete
uninstallation of Tivoli Workload Scheduler failed, services. If not, add this right. Remember to close
without deleting the service. If you suspect this to the user account management facilities window
be the case, contact IBM Software Support. before proceeding.
Remember to close the Windows Services panel
2. If the user exists and its rights are correct, open the
before proceeding.
Windows Services panel. Check if the indicated
service already exists. If it does not, it might have
If you are able to solve the problem so that the
been manually deleted in error. If you suspect this
installation is capable of installing a service, the
to be the case, contact IBM Software Support.
installation can be resumed at the failed step, as
Remember to close the Windows Services panel
follows:
before proceeding. You are not advised to attempt
- Resume the step of the interactive wizard to add the service manually.
The Diagnose Failure window is opened. If you are able to solve the problem so that the
installation is capable of deleting a service, the
installation can be resumed at the failed step, as
follows:
3. Double-click the failed installation step and
the Step Status window opens. - Resume the step of the interactive wizard
4. On the Status tab set the status to Ready 1. Click OK to close the error popup window.
The Diagnose Failure window is opened.
5. Click Apply. The Step List window is
displayed again. 2. Select Diagnose failure and click Next. The
from that step. 3. Double-click the failed installation step and
You cannot troubleshoot a failed installation 5. Click Apply. The Step List window is
with the silent wizard. Instead, do as follows: displayed again.
1. Resume the installation adding the 6. Click Run all to resume the installation
parameter -resume. The wizard resumes in from that step.
interactive mode at the Step List window
showing the failed step. - Resume the step of the silent wizard
2. Resume the step that failed, as described You cannot troubleshoot a failed installation
above. with the silent wizard. Instead, do as follows:
If the problem persists contact IBM Software Support parameter -resume. The wizard resumes in
for assistance. interactive mode at the Step List window
See also: The chapter on Troubleshooting installation, showing the failed step.
migration, and uninstallation in Administration and 2. Resume the step that failed, as described
Troubleshooting for full details of the recovery process above.
for assistance.


AWSJIS047E The installation encountered an error
running the Tivoli Workload Scheduler
Windows configuration script.
Explanation: The reason for the failure is documented
AWSJIS046E The installation could not find an
in the installation log file.
operating system dll to complete the
user verification tasks. System action: If you are running the interactive
operating system dynamic link library (dll) to complete If you are running the silent wizard, the wizard fails.
its task of verifying, and if necessary creating, the
supplied user.
wizard, look at the Output tab on the failed installation
System action: If you are running the interactive step for further information. Do the following:
wizard, the wizard stops. 1. Note down the error code (so that you can later
If you are running the silent wizard, the wizard fails. find it in Administration and Troubleshooting, if
needed)
Operator response: Verify that the Path system
variable points to the location of all the operating
system dlls, and that the dlls are available. Depending
on what you find, you might need to reinstall the 3. Select Diagnose failure and click Next. The Step
operating system before continuing with the List window is opened.
installation. 4. Select the failed installation step and double click it
If you are able to solve the problem so that the
installation is capable of using the operating system 5. Select the Output tab.
dlls to verify and create users, the installation can be
resumed at the failed step, as follows: If you are running the silent wizard, see the installation
log file for the error messages that explain why the
- Resume the step of the interactive wizard configuration script failed.
The Diagnose Failure window is opened. If you can solve the problem, do so, and proceed as
2. Select Diagnose failure and click Next. The follows.
3. Double-click the failed installation step and You might be able to resume the step, or you might
the Step Status window opens. have to rerun the installation from the beginning.
4. On the Status tab set the status to Ready - Interactive wizard
5. Click Apply. The Step List window is Resume the step of the interactive wizard
displayed again.
6. Click Run all to resume the installation Ready
from that step.
- Resume the step of the silent wizard window is displayed.
You cannot troubleshoot a failed installation 3. Click Run all to resume the
with the silent wizard. Instead, do as follows: installation from that step.
parameter -resume. The wizard resumes in
follows.
above. Rerun the interactive wizard
If the problem persists contact IBM Software Support 2. Select Quit installation. The
for assistance. wizard closes.
See also: The chapter on Troubleshooting installation, 3. If you have copied the installation
migration, and uninstallation in Administration and images to the local hard disk or to
Troubleshooting for full details of the recovery process a remote workstation, ensure that

AWSJIS048E
the entire disk image was copied, 3. Select Diagnose failure and click Next. The Step
and that the binary option was set List window is opened.
if ftp was used. 4. Select the failed installation step and double click it
4. Rerun the wizard. to open the Step Status window.
- Silent wizard 5. Select the Output tab.
Resume the step of the silent wizard If you are running the silent wizard, see the installation
You cannot troubleshoot a failed log file for the error messages that explain why the file
installation with the silent wizard. cannot be read.
Instead, do as follows:
follows.
Step List window showing the You might be able to resume the step, or you might
failed step. have to rerun the installation from the beginning.
2. Resume the step that failed. - Interactive wizard
If this does not resolve the problem, Resume the step of the interactive wizard
try rerunning the silent wizard, as 1. On the Status tab set the status to
follows. Ready
Rerun the silent wizard. 2. Click Apply. The Step List
1. If you have copied the installation window is displayed.
images to the local hard disk or to 3. Click Run all to resume the
a remote workstation, ensure that installation from that step.
the entire disk image was copied,
and that the binary option was set If the problem is not resolved, try
if ftp was used. exiting from the wizard and
2. Rerun the silent wizard. recommencing the installation, as
follows.
If the problem persists contact IBM Software Support Rerun the interactive wizard
for assistance.
See also: The chapter on Troubleshooting installation, 2. Select Quit installation. The
migration, and uninstallation in Administration and wizard closes.
a remote workstation, ensure that
AWSJIS048E The installation cannot read the the entire disk image was copied,
following file: file_name. and that the binary option was set
if ftp was used.
Explanation: The file_name is the fully qualified path
of the file that cannot be read. 4. Rerun the wizard.
System action: If you are running the interactive - Silent wizard

wizard, the wizard stops. Resume the step of the silent wizard
If you are running the silent wizard, the wizard fails. You cannot troubleshoot a failed
Operator response: Verify that the file exists and has installation with the silent wizard.
read permission for the user performing the Instead, do as follows:
installation. Ensure that it has not been locked by 1. Resume the installation adding the
another application, such as a file editor. parameter -resume. The wizard
If you are running the interactive wizard, look at the Step List window showing the
Output tab on the failed installation step for further failed step.
find it in Administration and Troubleshooting, if If this does not resolve the problem,
needed) try rerunning the silent wizard, as
2. Click OK to close the error popup window. The follows.

AWSJIS049E
Rerun the silent wizard. 2. Click Apply. The Step List

1. If you have copied the installation window is displayed.
images to the local hard disk or to 3. Click Run all to resume the
a remote workstation, ensure that installation from that step.
and that the binary option was set If the problem is not resolved, try
if ftp was used. exiting from the wizard and
2. Rerun the silent wizard. recommencing the installation, as
follows.
If the problem persists contact IBM Software Support Rerun the interactive wizard
for assistance.
See also: The chapter on Troubleshooting installation, 2. Select Quit installation. The
migration, and uninstallation in Administration and wizard closes.
AWSJIS049E The installation cannot write the the entire disk image was copied,
following file: file_name. and that the binary option was set
if ftp was used.
Explanation: The file_name is the fully qualified path
of the file that cannot be written. 4. Rerun the wizard.
System action: If you are running the interactive - Silent wizard

wizard, the wizard stops. Resume the step of the silent wizard
If you are running the silent wizard, the wizard fails. You cannot troubleshoot a failed
Operator response: Verify that the user performing installation with the silent wizard.
the installation has write permission for the file. Check Instead, do as follows:
if the file exists, and ensure that it has not been locked 1. Resume the installation adding the
by another application, such as a file editor. parameter -resume. The wizard
If you are running the interactive wizard, look at the
failed step.
find it in Administration and Troubleshooting, if If this does not resolve the problem,
needed) try rerunning the silent wizard, as
2. Click OK to close the error popup window. The follows.
Diagnose Failure window is opened. Rerun the silent wizard.
3. Select Diagnose failure and click Next. The Step 1. If you have copied the installation
List window is opened. images to the local hard disk or to
4. Select the failed installation step and double click it a remote workstation, ensure that
to open the Step Status window. the entire disk image was copied,
5. Select the Output tab. and that the binary option was set
if ftp was used.
If you are running the silent wizard, see the installation 2. Rerun the silent wizard.
log file for the error messages that explain why the file
cannot be written. If the problem persists contact IBM Software Support
for assistance.
follows.
You might be able to resume the step, or you might from a failed installation.
have to rerun the installation from the beginning.
Ready


AWSJIS050E The installation cannot move the
following file: file_name.
Explanation: The file_name is the fully qualified path the entire disk image was copied,
of the file that cannot be moved. and that the binary option was set
if ftp was used.
wizard, the wizard stops. 4. Rerun the wizard.
If you are running the silent wizard, the wizard fails. - Silent wizard
Operator response: Verify that the file being moved Resume the step of the silent wizard
has read permission for the user performing the You cannot troubleshoot a failed
installation. Verify that the directory where the installation with the silent wizard.
installation wants to move the file to has write Instead, do as follows:
permission for the user performing the installation.
If you are running the interactive wizard, look at the parameter -resume. The wizard
Output tab on the failed installation step for further resumes in interactive mode at the
information. Do the following: Step List window showing the
1. Note down the error code (so that you can later failed step.
find it in Administration and Troubleshooting, if 2. Resume the step that failed.
needed)
If this does not resolve the problem,
2. Click OK to close the error popup window. The try rerunning the silent wizard, as
Diagnose Failure window is opened. follows.
5. Select the Output tab. the entire disk image was copied,
If you are running the silent wizard, see the installation if ftp was used.
log file for the error messages that explain why the file
cannot be moved.
for assistance.
follows.
Resume the step of the interactive wizard AWSJIS051E The installation cannot install the
1. On the Status tab set the status to Autotrace software.
Ready
Explanation: See message text.
window is displayed. System action: If you are running the interactive
3. Click Run all to resume the wizard, the wizard stops.
installation from that step. If you are running the silent wizard, the wizard fails.
If the problem is not resolved, try Operator response: If you are running the interactive
exiting from the wizard and wizard, look at the Output tab on the failed installation
recommencing the installation, as step for further information. Do the following:
follows. 1. Note down the error code (so that you can later
Rerun the interactive wizard needed)
1. Close the Step Status window 2. Click OK to close the error popup window. The
2. Select Quit installation. The Diagnose Failure window is opened.
wizard closes. 3. Select Diagnose failure and click Next. The Step

AWSJIS052E
4. Select the failed installation step and double click it 1. If you have copied the installation
to open the Step Status window. images to the local hard disk or to
5. Select the Output tab. a remote workstation, ensure that
If you are running the silent wizard, see the installation and that the binary option was set
log file for the error messages that explain why the if ftp was used.
Autotrace software cannot be installed. 2. Rerun the silent wizard.
If you can solve the problem, do so, and proceed as If the problem persists contact IBM Software Support
follows. for assistance.
- Interactive wizard from a failed installation.

AWSJIS052E Composer could not update the
database.
Ready
2. Click Apply. The Step List Explanation: If you are upgrading this instance of
window is displayed. Tivoli Workload Scheduler, the problem could be that
the user who is performing the upgrade is not
3. Click Run all to resume the
authorized to use composer. The upgrade process needs
to use composer to check the security data contained in
the Security file.
exiting from the wizard and System action: If you are running the interactive
recommencing the installation, as wizard, the wizard stops.
follows.
Operator response: If the user who is performing the
1. Close the Step Status window upgrade is not authorized to use composer, locate and
2. Select Quit installation. The delete the Security file, and resume the final "commit"
wizard closes. phase of the installation. In the absence of a Security
3. If you have copied the installation file the installation recreates it with the correct rights.
images to the local hard disk or to If this not the case you need to find out why the
a remote workstation, ensure that commit phase failed.
and that the binary option was set If you are running the interactive wizard, look at the
if ftp was used. Output tab on the failed installation step for further
- Silent wizard find it in Administration and Troubleshooting, if
Resume the step of the silent wizard needed)
You cannot troubleshoot a failed
Instead, do as follows: 3. Select Diagnose failure and click Next. The Step
parameter -resume. The wizard 4. Select the failed installation step and double click it
resumes in interactive mode at the to open the Step Status window.
Step List window showing the 5. Select the Output tab.
failed step.
2. Resume the step that failed. If you are running the silent wizard, see the installation
log file for the error messages that explain why
If this does not resolve the problem, Composer could not update the database.
follows. If you can solve the problem, do so, and proceed as
Rerun the silent wizard. follows.

AWSJIS053E
You might be able to resume the step, or you might Troubleshooting for full details of the recovery process
have to rerun the installation from the beginning. from a failed installation.
AWSJIS053E The installation could not create the
Security file.
Ready Explanation: See message text.
2. Click Apply. The Step List System action: If you are running the interactive
window is displayed. wizard, the wizard stops.
3. Click Run all to resume the If you are running the silent wizard, the wizard fails.
If the problem is not resolved, try wizard, look at the Output tab on the failed installation
exiting from the wizard and step for further information. Do the following:
recommencing the installation, as 1. Note down the error code (so that you can later
follows. find it in Administration and Troubleshooting, if
needed)
2. Select Quit installation. The
wizard closes.
the entire disk image was copied, 5. Select the Output tab.
if ftp was used. If you are running the silent wizard, see the installation
log file for the error messages that explain why the
Security file could not be created.
- Silent wizard
follows.
installation with the silent wizard. You might be able to resume the step, or you might
Instead, do as follows: have to rerun the installation from the beginning.
1. Resume the installation adding the - Interactive wizard
resumes in interactive mode at the Resume the step of the interactive wizard
Step List window showing the 1. On the Status tab set the status to
failed step. Ready
2. Resume the step that failed. 2. Click Apply. The Step List
If this does not resolve the problem, window is displayed.
try rerunning the silent wizard, as 3. Click Run all to resume the
follows. installation from that step.
1. If you have copied the installation exiting from the wizard and
images to the local hard disk or to recommencing the installation, as
a remote workstation, ensure that follows.
and that the binary option was set Rerun the interactive wizard
if ftp was used. 1. Close the Step Status window
2. Rerun the silent wizard. 2. Select Quit installation. The
wizard closes.
If the problem persists contact IBM Software Support 3. If you have copied the installation
for assistance. images to the local hard disk or to
See also: The chapter on Troubleshooting installation, a remote workstation, ensure that

AWSJIS054E
the entire disk image was copied, 5. Select the Output tab.
if ftp was used. If you are running the silent wizard, see the installation
4. Rerun the wizard. log file for the error messages that explain why the
installation could not run the final installation "commit"
- Silent wizard phase.
You cannot troubleshoot a failed follows.
Instead, do as follows: You might be able to resume the step, or you might
1. Resume the installation adding the have to rerun the installation from the beginning.
resumes in interactive mode at the - Interactive wizard
Step List window showing the Resume the step of the interactive wizard
failed step.
2. Resume the step that failed. Ready
If this does not resolve the problem, 2. Click Apply. The Step List
try rerunning the silent wizard, as window is displayed.
follows. 3. Click Run all to resume the
Rerun the silent wizard. installation from that step.

follows.
if ftp was used. Rerun the interactive wizard
2. Rerun the silent wizard. 1. Close the Step Status window
If the problem persists contact IBM Software Support wizard closes.
for assistance.
See also: The chapter on Troubleshooting installation, images to the local hard disk or to
migration, and uninstallation in Administration and a remote workstation, ensure that
Troubleshooting for full details of the recovery process the entire disk image was copied,
from a failed installation. and that the binary option was set
if ftp was used.
AWSJIS054E The installation could not run the final 4. Rerun the wizard.
installation "commit" phase. - Silent wizard
Explanation: See message text. Resume the step of the silent wizard
System action: If you are running the interactive You cannot troubleshoot a failed
wizard, the wizard stops. installation with the silent wizard.
If you are running the silent wizard, the wizard fails. Instead, do as follows:
Operator response: If you are running the interactive parameter -resume. The wizard
wizard, look at the Output tab on the failed installation resumes in interactive mode at the
step for further information. Do the following: Step List window showing the
1. Note down the error code (so that you can later failed step.
find it in Administration and Troubleshooting, if 2. Resume the step that failed.
needed)
2. Click OK to close the error popup window. The If this does not resolve the problem,
Diagnose Failure window is opened. try rerunning the silent wizard, as
follows.
List window is opened. Rerun the silent wizard.
4. Select the failed installation step and double click it 1. If you have copied the installation
to open the Step Status window. images to the local hard disk or to

the entire disk image was copied, rerunning the installation from the beginning.
and that the binary option was set v If you are running the interactive wizard, click
if ftp was used. Cancel to exit from the wizard.
2. Rerun the silent wizard. v If you are running the silent wizard, the wizard has
already stopped.
for assistance. If you have copied the installation images to the local
See also: The chapter on Troubleshooting installation, hard disk or to a remote workstation, ensure that the
migration, and uninstallation in Administration and entire disk image was copied, and that the binary
Troubleshooting for full details of the recovery process option was set if ftp was used.
Rerun the installation. If the problem persists contact
IBM Software Support.
AWSJIS056E The directory that contains the
Server installation files cannot be AWSJIS058E The script "db2profile" used to create
found. the DB2 environment cannot be found
in the DB2 installation directory.
Explanation: The installation program is trying to
locate the directory where the embedded WebSphere Explanation: The installation program is trying to
Application Server files were unpacked at the locate the db2profile file that contains the DB2
beginning of the installation, but has failed to find it. installation files, but has failed to find it. Either the
Either the unpacking of the installation bundle failed, unpacking of the installation bundle failed, or the file
or the directory has subsequently been renamed or has subsequently been renamed or deleted.
deleted. System action: If you are running the interactive
If you are running the silent wizard, the wizard fails. Operator response: If you are running the interactive
Operator response: The problem might be resolved by wizard, look at the Output tab on the failed installation
rerunning the installation from the beginning. step for further information. Do the following:
v If you are running the interactive wizard, click 1. Note down the error code (so that you can later
Cancel to exit from the wizard. find it in Administration and Troubleshooting, if
needed)
v If you are running the silent wizard, the wizard has
already stopped. 2. Click OK to close the error popup window. The
If you have copied the installation images to the local 3. Select Diagnose failure and click Next. The Step
hard disk or to a remote workstation, ensure that the List window is opened.
entire disk image was copied, and that the binary 4. Select the failed installation step and double click it
option was set if ftp was used. to open the Step Status window.
Rerun the installation. If the problem persists contact
IBM Software Support.
Ensure that you are not trying to run two installations
concurrently, which is not possible.
AWSJIS057E The tar file that contains the embedded
WebSphere Application Server If you can solve the problem, do so, and proceed as
installation files cannot be found. follows:
Explanation: The installation program is trying to
locate the tar file that contains the embedded The problem is resolved by just rerunning the
WebSphere Application Server files, but has failed to installation.
find it. Either the unpacking of the installation bundle - Rerun the interactive wizard
failed, or the file has subsequently been renamed or
deleted.
3. If you have copied the installation images
If you are running the silent wizard, the wizard fails. workstation, ensure that the entire disk
Operator response: The problem might be resolved by option was set if ftp was used.

4. Rerun the wizard. See also: The chapter on Troubleshooting installation,

1. If you have copied the installation images from a failed installation.
image was copied, and that the binary AWSJIS060E The supplied "TWS_user" could not be
option was set if ftp was used. created.
2. Rerun the silent wizard. Explanation: See message.
for assistance
AWSJIS059E The fully qualified domain name of this Operator response: If you are running the interactive
computer is null. The installation wizard, look at the Output tab on the failed installation
requires the fully qualified domain step for further information. Do the following:
name to configure Tivoli Workload 1. Note down the error code (so that you can later
Scheduler correctly. find it in Administration and Troubleshooting, if
Explanation: The computer where you are installing needed)
Tivoli Workload Scheduler is not correctly set up in 2. Click OK to close the error popup window. The
your network with its fully qualified domain name. Diagnose Failure window is opened.
Perhaps you are installing Tivoli Workload Scheduler 3. Select Diagnose failure and click Next. The Step
on a new computer which has not yet been configured List window is opened.
for network access. The installation program requires
the fully qualified domain name (for example,
mycomputer.rome.ibm.com) to be defined on the local
computer to configure Tivoli Workload Scheduler 5. Select the Output tab.
correctly.
If you are running the silent wizard, see the installation
System action: If you are running the interactive log file for the error messages that might explain why
wizard, the wizard stops. the user cannot be created.
The probable cause is that in correcting a failed
Operator response: Resolve the problem by installation using the step resume facility, the
configuring the computer for network access. "TWS_user" ID was changed to a non-valid ID. This is
If you are running the interactive wizard stop the because the ID was checked for validity at input, and
installation program to reconfigure the network access. you would not have been able to start the installation if
Do this as follows: the user ID was not valid.
1. Click OK to close the error popup. The Diagnose
Failure window is opened. The reason why the ID has now been rejected could be
one of the following:
2. Click Quit to close the wizard.
v The user performing the installation does not have
the rights to create a user
Resume either an interactive or a silent installation
from the failed step by rerunning the installation v The supplied user name does not satisfy the
program, adding the parameter -resume. The wizard requirements of the local account policy
resumes in interactive mode at the Step List window v The supplied password of the "TWS_user" does not
showing the failed step. Proceed as follows: satisfy the requirements of the local security policy
1. Double-click the failed installation step and the Step v The Windows account management administration
Status window opens. wizard is open
2. On the Status tab set the status to Ready Correct any errors you find.
3. Click Apply. The Step List window is displayed
again. You might be able to resume the step, or you might
4. Click Run all to resume the installation from that have to rerun the installation from the beginning.
step.
If the problem persists contact IBM Software Support Resume the step of the interactive wizard
for assistance. 1. On the Properties tab change the
"TWS_user" ID. If it is not

AWSJIS061W • AWSJIS063E
available for editing, return to 1. If you have copied the installation

previous steps, until you find one images to the local hard disk or to
where you can edit the value or a remote workstation, ensure that
values. the entire disk image was copied,
2. Repeat this step for all other steps, and that the binary option was set
checking to see if the user account if ftp was used.
is included as a property for that 2. Rerun the silent wizard.
step, and changing it if it is. This
is because the installation wizard If the problem persists contact IBM Software Support
creates each step as a separate for assistance.
action, complete with its
properties; changing a value on
one does not change it AWSJIS061W The supplied "TWS_user" exists on the
automatically also on the others. local computer but does not have the
correct rights.
3. On the Status tab set the status to The installation is attempting to modify
Ready the rights.
window is displayed. Explanation: See message.
5. Click Run all to resume the System action: The wizard continues. When the
installation from that step. installation starts, the wizard attempts to modify the
rights of the "TWS_user".
If the problem is not resolved, try Operator response: None.
follows. AWSJIS063E The supplied password is incorrect for
the supplied "TWS_user".
1. Close the Step Status window Explanation: You have specified an existing user but
the supplied password is not correct for that user.
wizard closes. System action: If you are running the interactive
3. If you have copied the installation wizard, the wizard stops.
images to the local hard disk or to If you are running the silent wizard, the wizard fails.
the entire disk image was copied, Operator response: Supply a different password or a
and that the binary option was set different user ID and password.
if ftp was used. Proceed as follows:
- Silent wizard 1. Click OK to close the error popup window.
Resume the step of the silent wizard 2. Either change the "TWS_user", or its
password, (or both) so that the correct
password is supplied for the user.
Instead, do as follows: 3. Click Next to continue.
1. Resume the installation adding the - Silent wizard
parameter -resume. The wizard 1. Look in the installation log to see if there is
resumes in interactive mode at the any additional information
failed step.
wizard, changing the "TWS_user", or its
2. Follow the procedure described password, (or both), so that the correct
for the interactive wizard to password is supplied for the user.
correct the user ID and resume the
installation.
If this does not resolve the problem,
follows.

does not have the Windows default Administrator

AWSJIS064E The supplied "TWS_user" account
privileges.
cannot be verified automatically. This is
because the user running the System action: If you are running the interactive
installation program does not have the wizard, the wizard stops.
"Act as part of the operating system"
privilege, or the password of the user If you are running the silent wizard, the wizard fails.
has expired. Operator response: Add the Windows default
Explanation: The user running an installation on Administrator privileges to the account of the user
Windows 2000 (but not on Windows XP and later) running the installation, or rerun the installation as a
requires the "Act as part of the operating system" different user. If you change the account on the
privilege. The check for this privilege also fails if the computer you will almost certainly need to reboot the
password has expired, whether or not the account has computer. Thus, in either case, if you are running the
the privilege. interactive wizard you must stop it, as follows:
wizard, the wizard stops. 2. Click Cancel to exit from the installation.
If you are running the silent wizard, the wizard fails. Change the account, or log off and on again using a
Operator response: Add the privileges to the account different user that has the correct privileges.
of the user running the installation, renew the
password, or rerun the installation as a different user. If Rerun the wizard from scratch.
you change the account on the computer you will
almost certainly need to reboot the computer. Thus, in Note:This message might also be given when the Create
all cases, if you are running the interactive wizard you User step is run. This only occurs if, between the time
must stop it, as follows: that the wizard validates the input values for the user
2. Click Cancel to exit from the installation. computer or in the step properties dialogs as a result of
Change the account or its password, or log off and on does you must rerun the installation.
again using a different user that has the correct
privileges or whose password has not expired. See also: See Chapter 4, “Installing,” on page 31 for
details about the privileges required to run the
Rerun the wizard from scratch. installation.
Note:This message might also be given when the Create migration, and uninstallation in Administration and
User step is run. This only occurs if, between the time Troubleshooting for full details of the recovery process
that the wizard validates the input values for the user from a failed installation.
ID and password, and the time it runs the Create User
step, any changes are made to the user ID or its
password, either on the computer or in the step AWSJIS066E The installation was unable to check the
properties dialogs as a result of a failed installation. existence of the supplied "TWS_user".
This is unlikely to occur, but if it does you must rerun Explanation: The user running the installation has the
the installation. correct privileges to verify the existence of the
See also: The chapter on Troubleshooting installation, "TWS_user", but a problem associated with the user ID
migration, and uninstallation in Administration and or password has prevented it from doing so. It is
Troubleshooting for full details of the recovery process possible that the user name or password you supplied
from a failed installation. contained special characters or characters that do not
belong to the codeset of the computer. It is possible that
the account management facilities of the computer are
AWSJIS065E The user running the installation does in use, not working or are blocked in some other way.
not have the correct privileges to verify
the privileges of the supplied System action: If you are running the interactive
"TWS_user". wizard, the wizard stops.
Explanation: The installation program has verified If you are running the silent wizard, the wizard fails.
that either the "Act as part of the operating system" Operator response: Ensure the following:
privilege is not required, or is present in the profile of
v Ensure that the "TWS_user" ID and password do not
the user running the installation, but the attempt to
contain any unusual characters that might give
verify the "TWS_user" has failed for another reason
codeset translation problems
associated with privileges. It might be that the user

v Ensure that the user account management facilities running the installation, or rerun the installation as a
on the computer are not in use by you or any other different user. If you change the account on the
user computer you will almost certainly need to reboot the
v Ensure that the user account management facilities computer. Thus, in either case, if you are running the
are available and working. To do this, attempt to interactive wizard you must stop it, as follows:
access the details of a user account, but be sure to 1. Click OK to close the error popup window.
close the account management facilities window 2. Click Cancel to exit from the installation.
when you have finished
If you have found and fixed a problem with the Change the account, or log off and on again using a
account management facilities you can continue the different user that has the correct privileges.
installation. Otherwise, close the installation and rerun
it as a different user Rerun the wizard from scratch.
Continue the installation User step is run. This only occurs if, between the time
1. Click OK to close the error popup that the wizard validates the input values for the user
window. ID, and the time it runs the Create User step, any
2. Click Next to continue. computer or in the step properties dialogs as a result of
Rerun the installation a failed installation. This is unlikely to occur, but if it
does you must rerun the installation.
1. Click OK to close the error popup
window. See also: The chapter on Troubleshooting installation,
2. Click Cancel to quit the migration, and uninstallation in Administration and
installation. Troubleshooting for full details of the recovery process
3. Login as a different user.
AWSJIS068E The installation could not add the
- Silent wizard supplied "TWS_user" to the
Just rerun the wizard in either case. "Administrators" group.
Explanation: You have supplied a "TWS_user" ID that
Note:This message might also be given when the Create did not exist on the computer and the installation has
User step is run. This only occurs if, between the time created an account for it. However, it could not add the
that the wizard validates the input values for the user account to the "Administrators" group. Probably, the
ID, and the time it runs the Create User step, any user that you are using to run the installation does not
changes are made to the user ID, either on the have the correct privileges to add a user to that group.
a failed installation. This is unlikely to occur, but if it System action: If you are running the interactive
does you must rerun the installation. wizard, the wizard stops.
See also: The chapter on Troubleshooting installation, If you are running the silent wizard, the wizard fails.
migration, and uninstallation in Administration and Operator response: Add the Windows default
Troubleshooting for full details of the recovery process Administrator privileges to the account of the user
from a failed installation. running the installation, or rerun the installation as a
different user. If you change the account on the
AWSJIS067E The installation could not modify the computer you will almost certainly need to reboot the
privileges of the supplied "TWS_user". computer. Thus, in either case, if you are running the
interactive wizard you must stop it, as follows:
Explanation: You have supplied a "TWS_user" that
exists on the local computer but has insufficient rights.
The installation has tried to modify those rights but 2. Click Cancel to exit from the installation.
cannot. Probably, the user that is running the
installation does not have the correct rights to modify Change the account, or log off and on again using a
the supplied user’s rights. different user that has the correct privileges.
System action: If you are running the interactive Rerun the wizard from scratch.
If you are running the silent wizard, the wizard fails. Note:This message might also be given when the Create
Operator response: Add the Windows default that the wizard validates the input values for the user

ID, and the time it runs the Create User step, any Operator response: If you are running the interactive
changes are made to the user ID, either on the wizard, look at the Output tab on the failed installation
computer or in the step properties dialogs as a result of step for further information. Do the following:
a failed installation. This is unlikely to occur, but if it 1. Note down the error code (so that you can later
does you must rerun the installation. find it in Administration and Troubleshooting, if
See also: The chapter on Troubleshooting installation, needed)
migration, and uninstallation in Administration and 2. Click OK to close the error popup window. The
Troubleshooting for full details of the recovery process Diagnose Failure window is opened.
from a failed installation. 3. Select Diagnose failure and click Next. The Step
AWSJIS069E The installation could not find an 4. Select the failed installation step and double click it
operating system dll to complete the to open the Step Status window.
"TWS_user" verification tasks. 5. Select the Output tab.
operating system dynamic link library (dll) to complete If you are running the silent wizard, see the installation
its task of verifying, and if necessary creating, the log file for the error messages that might explain why
supplied user. the user cannot be created.
System action: If you are running the interactive Ensure the following:
v Ensure that the "TWS_user" ID and password respect
If you are running the silent wizard, the wizard fails. local security policy
Operator response: Verify that the PATH system v Ensure that the user running the installation has the
variable points to the location of all the operating rights to create a user. Remember to close the
system dlls, and that the dlls are present (your account management facilities before proceeding. If it
operating system documentation might identify which does not, add those rights, or run the installation
dlls are responsible for user account verification). using a user that has those rights.
Depending on what you find, you might need to
reinstall the operating system before continuing with The problem resolution depends on what you found:
the installation. Verify also that the user running the
- Problems with an existing <TWS_user> ID or
installation has execute permission for operating system
password
dlls.
Supply a different "TWS_user" ID and
Whatever the solution to the problem, rerun the
password. As everything in the installation
wizard. If you are running the interactive wizard you
relates to this user, you must rerun the
need to stop the installation program. Do this as
installation, supplying the new "TWS_user" ID.
follows:
1. Click OK to close the error popup. Proceed as follows:
2. Click Cancel to close the wizard. Interactive wizard
1. Click OK to close the error popup
Rerun the wizard from scratch. window.
2. Click Quit to exit from the
Note:This message might also be given when the Create installation.
that the wizard validates the input values for the user 3. Rerun the installation, supplying a
ID, and the time it runs the Create User step, any different "TWS_user" ID and
changes are made to the dlls. This is unlikely to occur, password.
but if it does you must rerun the installation. Silent wizard
1. Edit the response file used by the
AWSJIS070E The supplied "TWS_user" could not be silent wizard, changing the
created. "TWS_user" and its password.
Explanation: You have supplied a "TWS_user" ID that 2. Rerun the silent wizard.
did not exist on the computer but the installation has - Problems with the password supplied for a
not been able to create it. <TWS_user> that is being created
System action: If you are running the interactive Supply a different password.
Proceed as follows:

AWSJIS071E
1. Click OK to close the error popup 2. Log on as a different user with the
window. The Diagnose Failure Windows default Administrator
window is opened. privileges.
2. Select Diagnose failure and click 3. Rerun the installation without a
Next. The Step List window is resume. You cannot do a step
opened. resume of an installation if you
3. Double-click the failed installation have changed the user that is
step and the Step Status window running it; you must rerun the
opens. installation from scratch.
4. On the Properties tab change the Add the missing privileges to your user
"TWS_user" password. If it is not profile
available for editing, return to 1. If you are running the interactive
previous steps, until you find one wizard you need to stop the
where you can edit the value or installation program . Do this as
values. follows:
5. Repeat this step for all other steps, a. Click OK to close the error
checking to see if the password is popup. The Diagnose Failure
included as a property for that window is opened.
step, and changing it if it is. This
b. Click Quit to close the wizard.
is because the installation wizard
creates each step as a separate 2. Add the necessary privileges to
action, complete with its the profile of the user running the
properties; changing a value on installation, so that it has the
one does not change it default Administrator privileges
automatically also on the others. (you might need to log on as an
Administrator to do this).
Ready 3. Reboot the computer.
7. Click Apply. The Step List 4. Resume the installation adding the
window is displayed. parameter -resume. The wizard
failed step.
- Silent wizard 5. Double-click the failed installation
1. Edit the response file used by the step and the Step Status window
silent wizard, changing the opens.
"TWS_user" password. 6. On the Status tab set the status to
2. Resume the installation adding the Ready
parameter -resume. The wizard 7. Click Apply. The Step List
resumes in interactive mode at the window is displayed again.
failed step.
3. Follow the procedure described
for the interactive wizard to See also: The chapter on Troubleshooting installation,
correct the user ID and resume the migration, and uninstallation in Administration and
installation. Troubleshooting for full details of the recovery process
- Problems with the user privileges
Choose one of these options: AWSJIS071E The supplied "TWS_user" name
Rerun with a different user incorrectly contains a period.
1. If you are running the interactive Explanation: This message indicates that during the
wizard you need to stop the recovery operation of a previously failed installation,
installation program . Do this as you modified the "TWS_user" name and included a
follows: period in the name. The "TWS_user" ID was validated
a. Click OK to close the error on input, and the presence of a period would not have
popup. The Diagnose Failure allowed the installation to go ahead.
window is opened. System action: If you are running the interactive
b. Click Quit to close the wizard. wizard, the wizard stops.

If you are running the silent wizard, the wizard fails. Operator response: Choose a different user ID that
does not exist on this computer in any form and rerun
Operator response: You must rerun the wizard,
the installation without a resume. You cannot do a step
reinputting the "TWS_user" ID as follows:
resume of an installation if you have changed the
- Interactive wizard "TWS_user", you must rerun the installation from
1. Click OK to close the error popup window. scratch.
2. Click Quit to exit from the installation. Interactive wizard

3. Rerun the installation, resupplying the 1. Close the Step Status window
"TWS_user" ID and password. 2. Select Quit installation. The wizard closes.
- Silent wizard 3. Rerun the wizard.
1. Rerun the silent wizard. Silent wizard.
AWSJIS074E The supplied "TWS_user" ID incorrectly
contains a period.
Explanation: This message indicates that during the
AWSJIS072E The supplied "TWS_user" ID is longer
recovery operation of a previously failed installation,
than the maximum length of
you modified the "TWS_user" ID and included a period
maximum_length bytes.
in the name. The "TWS_user" ID was validated on
Explanation: See message. input, and the presence of a period would not have
allowed the installation to go ahead.
maximum_length is the maximum permitted length in
bytes of the "TWS_user" ID. System action: If you are running the interactive
If you are running the silent wizard, the wizard fails. Operator response: You must rerun the wizard,
reinputting the "TWS_user" ID as follows:
2. Click Quit to exit from the installation.
2. Click Back to return to the previous panel
and change the TWS_user to a value no 3. Rerun the installation, resupplying the
longer than the maximum length. "TWS_user" ID and password.
3. Click Next to continue. - Silent wizard
- Silent wizard 1. Rerun the silent wizard.
1. Edit the response file used by the silent See also: The chapter on Troubleshooting installation,
wizard, changing the TWS_user to a value migration, and uninstallation in Administration and
no longer than the maximum length. Troubleshooting for full details of the recovery process
2. Rerun the silent wizard. from a failed installation.
AWSJIS073E The supplied "TWS_user" AWSJIS075E The supplied "TWS_user" does not exist.
"TWS_user_ID" does not exist on the On UNIX platforms the user chosen for
local computer, but the installation the "TWS_user" must exist with the
cannot create this user, because another correct permissions before starting the
object exists with the supplied name. installation program.
Explanation: You have supplied a user ID that does Explanation: See message text.
not exist. The installation has tried to create a user with System action: If you are running the interactive
the supplied ID, but has found another object exists wizard, the wizard stops.
(such as a domain or a user group) with the supplied
ID. If you are running the silent wizard, the wizard fails.
System action: If you are running the interactive Operator response: Choose an existing user or create
wizard, the wizard stops. an account expressly for the installation. You must
rerun the wizard, changing the "TWS_user" ID as
If you are running the silent wizard, the wizard fails. follows:

- Interactive wizard In the latter case you might have to reboot the
1. Click OK to close the error popup window. computer. In either case rerun the installation.
2. Click Quit to exit from the installation. - Interactive wizard
3. Rerun the installation, supplying a 1. Close the Step Status window
different "TWS_user" ID and its password. 2. Select Quit installation. The wizard closes.
- Silent wizard 3. Log on as a user in the "Administrator"
1. Edit the response file, changing the group, and with Administrator rights.
"TWS_user" ID and its password. 4. Rerun the wizard.
2. Rerun the silent wizard. - Silent wizard.
See also: See “Tivoli Workload Scheduler user” on 1. Log on as a user in the "Administrator"
page 16 for information about the required group, and with Administrator rights.
characteristics of the <TWS_user>. 2. Rerun the silent wizard.
AWSJIS076E The supplied port: "port_number" is AWSJIS078E The user running the installation is not
already in use. "root".
Explanation: See message. Explanation: See message.
port_number identifies the port that is already in use. System action: If you are running the interactive
If you are running the silent wizard, the wizard fails. Operator response: The user performing the
Operator response: Supply a different port that is not installation must be "root". Rerun the installation as
in use. "root".
Proceed as follows: - Interactive wizard

3. Log on as root.
2. Change the port.
- Silent wizard.
- Silent wizard
1. Logon as root.
wizard, changing the value of the indicated 2. Rerun the silent wizard.
port.
2. Rerun the silent wizard. AWSJIS079E The supplied ports are not unique.
Specify a different value for each port.
migration, and uninstallation in Administration and Explanation: See message.
port_number identifies the port that is already in use.
AWSJIS077E The user running the installation is not
in the "Administrator" group, or does If you are running the silent wizard, the wizard fails.
not have Administrator rights.
Operator response: Check the port numbers you have
Explanation: See message. used. Make sure that a unique value has been supplied
for each port and that the supplied ports are available.
wizard, the wizard stops. Proceed as follows:
If you are running the silent wizard, the wizard fails. - Interactive wizard
Operator response: The user performing the 1. Click OK to close the error popup window.
installation must be both in the "Administrator" group, 2. Change the port or ports.
and have Administrator rights. Either choose a different 3. Click Next to continue.
Administrator user, or modify the rights, and the
group, (or both), of the user performing the installation. - Silent wizard

1. Edit the response file used by the silent Proceed as follows:

wizard, changing the value of the indicated
port or ports.
2. If you have decided to use a different
directory, change it on the wizard panel.
AWSJIS080E The directory "directory" cannot be
created.
- Silent wizard
1. If you have decided to use a different
directory identifies the directory that cannot be created. directory, edit the response file used by the
System action: If you are running the interactive silent wizard, changing the value of the
wizard, the wizard stops. directory.
Operator response: Ensure the following in the path
AWSJIS082E The following fields "field1" and "field2"
indicated:
cannot contain the same value.
v Ensure that the directory does not already exist.
v Ensure that there is sufficient space in the file set for
the installation. field1 and field2 identify two fields that cannot have the
v Ensure that the user running the installation has same value.
write permission for that path. System action: If you are running the interactive
v Ensure that the directory name is allowed in the wizard, the wizard stops.
system.
When you have located the problem, fix it either by Operator response: Change one or both of the fields
making it possible to use the chosen directory, or by so that they are unique.
deciding to use a different directory, depending on the
Proceed as follows:
nature of the problem.
Proceed as follows: 1. Click OK to close the error popup window.
- Interactive wizard 2. Change one or both of the fields on the
1. Click OK to close the error popup window. wizard panel.
2. If you have decided to use a different 3. Click Next to continue.
directory, change it on the wizard panel. - Silent wizard
3. Click Next to continue. 1. Edit the response file used by the silent
- Silent wizard wizard, changing one or both of the fields.
1. If you have decided to use a different 2. Rerun the silent wizard.
directory, edit the response file used by the
silent wizard, changing the value of the AWSJIS083E The directory "directory" is not a valid
directory. directory.
directory is the directory path you have supplied, which
AWSJIS081E The directory "directory" does not have
is not a valid directory.
write permission.
directory identifies the directory that does not have
write permission for the user running the installation.
Operator response: Choose a different directory.
wizard, the wizard stops. Proceed as follows:
If you are running the silent wizard, the wizard fails. - Interactive wizard
Operator response: Either give write permission in the 1. Click OK to close the error popup window.
directory to the user running the installation, or decide 2. Change the directory on the wizard panel.
to choose a different directory.

3. Click Next to continue. 3. Double-click the failed installation step and

- Silent wizard
wizard, changing the value of the directory. 5. Click Apply. The Step List window is
displayed.
from that step.
AWSJIS084E The command line client for Tivoli
Workload Scheduler, version 8.5 is - Silent wizard
already installed in the specified 1. Resume the installation adding the
installation location. parameter -resume. The wizard resumes in
Explanation: The wizard has found an existing
installation of the command line client in the chosen
installation path. 2. Follow the procedure described for the
interactive wizard and resume the
System action: If you are running the interactive installation.
If you are running the silent wizard, the wizard fails. migration, and uninstallation in Administration and
Operator response: Either stop the installation, or Troubleshooting for full details of the recovery process
choose a different directory. from a failed installation.
To choose a different directory, proceed as follows:

AWSJIS086W The credentials for using the Tivoli
- Interactive wizard Workload Scheduler command line
1. Click OK to close the error popup window. client are already present on this
computer (in the "useropts" file), but
2. Change the directory on the wizard panel.
they are overwritten by this installation.
Explanation: The connection parameters used to
- Silent wizard connect to the command line client are stored in the
1. Edit the response file used by the silent local "useropts" file. When you install the command
wizard, changing the value of the directory. line client they normally contain default values. They
2. Rerun the silent wizard. are now overwritten by the actual values determined
by the installation wizard.
AWSJIS085E The connection to the database has System action: The wizard proceeds.
failed. Check that the DB2 server is Operator response: None.
running and that the user and password
are correct.
AWSJIS088E An error occurred while stopping the
Explanation: The installation is attempting to connect embedded WebSphere Application
to the database but the connection cannot be Server.
established.
wizard, the wizard stops. System action: The uninstallation stops.
If you are running the silent wizard, the wizard fails. Operator response: Check that the credentials
supplied for accessing the embedded WebSphere
Operator response: Check that DB2 is up and Application Server are correct. If they are not, correct
running. Check that the specified user and password them and retry the uninstallation.
have the rights to connect to the database. Start the
database manager, if it is stopped. Connect to the If the credentials are correct, stop the embedded
database with a user that has the rights to connect. WebSphere Application Server by using the appropriate
command, and retry the operation.
If you make a successful connection, resume the
installation at the failed step, as follows: See also: The appropriate publications for the
embedded WebSphere Application Server for
- Interactive wizard information about the commands.

client has been uninstalled by checking the presence of

AWSJIS090E An error occurred while uninstalling the
the <TWS_home>/cli directory. If it does not exist, the
Tivoli Workload Scheduler instance.
command line clienthas been uninstalled without
Explanation: See message. removing the uninstaller. Locate the uninstaller and
delete it.
System action: The uninstallation stops.
If the directory is present, attempt to delete it. If you
Operator response: Check the log for other messages
succeed, the uninstallation is almost complete, so just
that might help you to understand why the action
locate and delete the uninstaller.
failed.
If the directory cannot be deleted, a process has locked
Check that the Tivoli Workload Scheduler instance is
one or more of the files. Check the Tivoli Workload
defined in the IBM Tivoli Configuration Manager
Scheduler processes running on the computer. If any
catalog. To do this, follow this procedure:
processes are running, make sure that they have
1. Set the IBM Tivoli Configuration Manager by completed all activities and stop them. Rerun the
running ./swd_env.sh from the <install_dir>/ uninstallation.
_uninstall/CLI directory.
2. Run the command wdlssp
AWSJIS098E An internal error has occurred. A
3. Check if the instance of Tivoli Workload Scheduler program has failed unexpectedly.
is listed.
If it is not listed, either the instance has already
been uninstalled, or it was not installed correctly. In System action: The installation stops.
the latter case, see Administration and Troubleshooting
Operator response: Contact IBM Software Support.
for details of how to manually complete an
installation that could not be uninstalled normally.
If it is listed, continue the uninstallation using the AWSJIS099E The DB2 response file does not exist:
twsRemove script located in the Explanation: The installation creates a response file to
<install_dir>/_uninstall/ACTIONTOOLS directory. install DB2 silently, based on your input on the DB2
installation wizard panel. This response file cannot be
AWSJIS091E The uninstall wizard could not find any found in the location where it was created. Between the
instances of Tivoli Workload Scheduler installation step that created the file and the installation
on this computer to uninstall. step that needed to use the file, the file was moved,
deleted or renamed.
Explanation: See message. It is possible that Tivoli
Workload Scheduler was not installed correctly, or has System action: If you are running the interactive
already been uninstalled. wizard, the wizard stops.
System action: The uninstallation stops. If you are running the silent wizard, the wizard fails.
Operator response: Determine the original installation Operator response: You must resume the installation
directory and check if it is present. If the installation at the step that creates the DB2 response file, as
directory is present on the computer, and contains data, follows:
Tivoli Workload Scheduler was not installed correctly. - Interactive wizard
In this case, see Administration and Troubleshooting for
instructions on uninstalling Tivoli Workload Scheduler 1. Click OK to close the error popup window.
manually. The Diagnose Failure window is opened.
If the installation directory is not present, or contains Step List window is opened.
no data, Tivoli Workload Scheduler has been
uninstalled without removing the uninstaller. Locate 3. Locate the step entitled: "Create the DB2
the uninstaller and delete it. response file".
4. Double-click the step and the Step Status
window opens.
AWSJIS092E An error has occurred while uninstalling
the Tivoli Workload Scheduler 5. On the Status tab set the status to Ready
command line client. 6. Click Apply. The Step List window is
displayed.
Explanation: See message. It is possible that the Tivoli
Workload Scheduler command line client has already 7. Click Run all to resume the installation
been uninstalled. from that step.
System action: The uninstallation stops. - Silent wizard

Operator response: Check whether the command line parameter -resume. The wizard resumes in

interactive mode at the Step List window 2. Rerun the silent wizard.
2. Follow the procedure described for the AWSJIS101E The supplied existing DB2 installation
interactive wizard and resume the cannot be used because the version is
installation. lower than the minimum supported
See also: The chapter on Troubleshooting installation, version: 9.1. Version 8.2 (8.1 with Fix
migration, and uninstallation in Administration and Pack 7) is supported during the
Troubleshooting for full details of the recovery process installation, but you are advised to
from a failed installation. migrate it to a supported version after
completing the installation (see the
System Requirements document in the
AWSJIS100E You have supplied a path to identify the Information Center for a detailed
supported DB2 installation: DB2_path explanation of the supported versions).
but either no installation exists at that Check the help for this message (in the
location, or the installation that exists is "Messages" manual) to determine the
not a supported version. Supported correct path to supply.
versions are 9.1 and 9.5. Version 8.2 (8.1
with Fix Pack 7) is supported during the Explanation: You have supplied a path to identify the
installation, but you are advised to supported DB2 installation that already exists on this
migrate it to a supported version after computer. The installation that exists is not a supported
completing the installation (see the version: minimum version is 9.1.
System Requirements document in the System action: If you are running the interactive
Information Center for a detailed wizard, the wizard stops.
explanation of the supported versions).
Check the help for this message (in the If you are running the silent wizard, the wizard fails.
"Messages" manual) to determine the Operator response: Either supply a different DB2
correct path to supply. location, or ask the wizard to install DB2 for you. In
Explanation: One possible reason is that you have this latter event, you must ensure that the computer
identified a DB2 directory, but that directory is not the where you are performing the installation satisfies the
one where the instance is installed. The correct DB2 prerequisites.
directory is as follows: In either case, proceed as follows:
UNIX - Interactive wizard
The fully-qualified path must point to the 1. Click OK to close the error popup window.
sqllib directory in the DB2 structure. 2. Change the DB2 location on the wizard
Windows panel or click Back to return to the DB2
Installation Actions panel and choose to
The fully-qualified path must identify a tree in install DB2.
the DB2 structure that includes the
db2level.exe file.
- Silent wizard
wizard, the wizard stops. 1. Edit the response file used by the silent
wizard. Change the DB2 location, or select
If you are running the silent wizard, the wizard fails. the option to install DB2, and supply all
Operator response: If the supplied location is not the required DB2-related information.
correct, supply a different DB2 location. 2. Rerun the silent wizard.
Proceed as follows:
AWSJIS102E The port specified for the DB2 instance
is not in use.
window. Explanation: You have identified the port on which
the DB2 server instance is listening, but that port is not
2. Change the DB2 location on the wizard
in use. Either the DB2 server is not running or you
panel.
have supplied an incorrect port.
- Silent wizard wizard, the wizard stops.
wizard. Change the DB2 location.
Operator response: Check that the DB2 server is

active and the DB2 instance port you have supplied is sufficient space. Check the size of the current
correct. installation to determine how much space is
required.
If the DB2 server is inactive, start the server and
continue the installation. v Check that the directory name is valid for the
operating system. If not, go back and change the
If the DB2 instance port is incorrect, supply a different backup directory name.
instance port and continue the installation.
- Rerun the installation
In either case, proceed as follows:
- Interactive wizard click OK to close the error popup window.
1. Click OK to close the error popup window. 2. Either log on as a different user or change
2. If the DB2 instance port is incorrect, the user permissions.
change it on the wizard panel 3. Rerun the wizard, interactively or silently,
3. Click Next to continue. with a different user.
- Silent wizard - Continue the installation
1. If the DB2 instance port is incorrect, edit Interactive wizard

the response file used by the silent wizard. 1. Click OK to close the error popup
Change the DB2 instance port. window.
2. Rerun the silent wizard. 2. If you need to, change the backup
directory on the wizard panel
Note:This message might also be given during the 3. Click Next to continue.
installation steps that configure DB2 and verify that it
is working correctly. This only occurs if, between the Silent wizard
time that the wizard validates the input values for the 1. If you need to, edit the response
instance port, and the time it runs these steps, the DB2 file used by the silent wizard.
server is stopped or its port changed. This is unlikely Change the backup directory.
to occur, but if it does you must rerun the installation.
AWSJIS103E The installation could not create the

AWSJIS104E The installation could not read the file
backup directory with the supplied
"backup_program_files_list_file" containing
name: "backup_directory"
a list of the files that need to be backed
Explanation: You are running an upgrade and have up.
identified a backup directory that does not yet exist for
Explanation: You are running an upgrade and have
the previous version of Tivoli Workload Scheduler.
identified a backup directory in which to back up the
However, when the wizard tried to create the backup
previous version. To perform the backup the
directory an error was given by the operating system.
installation needs to access and read a file containing a
There might be a problem with permissions or disk
list of the files that need to be backed up. This file is
space.
supplied as part of the installation package. If it cannot
System action: If you are running the interactive be read, it might have been damaged in copying it to
wizard, the wizard stops. the hard disk.
If you are running the silent wizard, the wizard fails. backup_program_files_list_file is the name of the file that
contains a list of the program files to backup.
Operator response: Check the following:
v Check that the user running the installation has System action: If you are running the interactive
permission to create a directory at that location. If wizard, the wizard stops.
not, change the user permissions or choose to run If you are running the silent wizard, the wizard fails.
the installation from a different user. In either case
you might need to exit from the installation (for Operator response: Check if the file exists. If it does
example if you need to reboot your computer after not, or it seems to have been edited or damaged, you
changing user permissions), and rerun it from could attempt to replace it from the version on the
scratch, as described below. product CD, after which you can continue the
installation. However, if this file is missing or damaged,
v Check that there is sufficient disk space in the fileset
it is likely that other files are missing or damaged, as
of the indicated directory. If not, make more space in
well. In this case rerun the installation, either directly
the fileset and continue the installation, or go back
from the CD, or by copying the installation files from
and change the backup directory to a fileset with
the CD to hard disk again, ensuring that you use the
binary option if the copy mode is ftp.

Proceed as follows: Operator response: Check the value of the backup

1. If you are running the interactive wizard, click OK directory path you have chosen. Either choose a
to close the error popup window. Then click Cancel different directory in a shorter path, or change the
to exit from the wizard. directory names in the path of the chosen directory so
that the path is shorter.
2. Rerun the wizard, interactively or silently.
Resume the installation, as follows:
If the problem persists, contact IBM Software Support
for assistance.
AWSJIS105E The installation could not read the file
"backup_config_files_list_file" containing
the names of the configuration files that
need to be backed up. 3. Double-click the "Back up the Tivoli
Workload Scheduler instance selected for
Explanation: You are running an upgrade and have upgrade" step and the Step Status window
identified a backup directory in which to back up the opens.
previous version. To perform the backup the
4. On the Properties tab change the directory
installation needs to access and read a file containing a
path to the new or amended directory you
list of the files that need to be backed up. This file is
have chosen.
supplied as part of the installation package. If it cannot
be read, it might have been damaged in copying it to 5. On the Status tab set the status to Ready
the hard disk. 6. Click Apply. The Step List window is
displayed.
backup_config_files_list_file is the name of the file that
contains a list of the configuration files to backup. 7. Click Run all to resume the installation
from that step.
wizard, the wizard stops. - Silent wizard
parameter -resume. The wizard resumes in
Operator response: Check if the file exists. If it does interactive mode at the Step List window
not, or it seems to have been edited or damaged, you showing the failed step.
could attempt to replace it from the version on the 2. Follow the procedure described for the
product CD, after which you can continue the interactive wizard and resume the
installation. However, if this file is missing or damaged, installation.
from the CD, or by copying the installation files from AWSJIS107E The installation cannot rename the file
the CD to hard disk again, ensuring that you use the "file".
binary option if the copy mode is ftp. Explanation: See message.
Proceed as follows: file identifies the file that could not be renamed.
1. If you are running the interactive wizard, click OK
to close the error popup window. Then click Cancel
to exit from the wizard.
2. Rerun the wizard, interactively or silently. If you are running the silent wizard, the wizard fails.
Operator response: Check that the user running the
If the problem persists, contact IBM Software Support installation has permission to rename a file at that
for assistance. location. If not, change the user permissions or choose
to rerun the installation from a different user. In either
AWSJIS106E The path "backup_directory" supplied for case you might need to exit from the installation (for
the backup directory is too long. example if you need to reboot your computer after
changing user permissions), and rerun it from scratch.
Explanation: You are running an upgrade and have
identified a backup directory that does not yet exist for Proceed as follows:
the previous version of Tivoli Workload Scheduler. 1. If you are running the interactive wizard, click OK
However, the supplied directory path is too long. to close the error popup window. Then click Cancel
to exit from the wizard.
wizard, the wizard stops. 2. Either log on as a different user or change the user
permissions.

3. Rerun the wizard, interactively or silently, with a System action: If you are running the interactive
different user. wizard, the wizard stops.
for assistance. Operator response: Check if the file exists. If it does
not, or it seems to have been edited or damaged, you
could attempt to replace it from the version on the
AWSJIS109E You are trying to install Tivoli Workload
product CD, after which you can continue the
Scheduler on a workstation where one
installation. However, if this file is missing or damaged,
or more agent processes are still
running.
You must stop all Tivoli Workload
from the CD, or by copying the installation files from
Scheduler processes before installing
the CD to hard disk again, ensuring that you use the
another instance or upgrading an
binary option if the copy mode is ftp.
existing instance.
Proceed as follows:
System action: If you are running the interactive to close the error popup window. Than click Cancel
wizard, the wizard stops. to quit the wizard.
If you are running the silent wizard, the wizard fails. 2. Rerun the wizard, interactively or silently.
Operator response: Stop any active processes.

Resume the installation, as follows: for assistance.
1. Click OK to close the error popup window. AWSJIS111E The installation was unable to access
The Diagnose Failure window is opened. one or more Windows processes.
2. Select Diagnose failure and click Next. The Explanation: You are probably running the installation
Step List window is opened. with a Windows system management application open.
3. Double-click the failed step and the Step Possible applications which must be closed include:
Status window opens. Task Manager, Services, Computer Management, and
RegEdit.
5. Click Apply. The Step List window is System action: If you are running the interactive
displayed. wizard, the wizard stops.
6. Click Run all to resume the installation If you are running the silent wizard, the wizard fails.
from that step.
Operator response: Verify if the Windows Task
- Silent wizard Manager, Services, Computer Management, RegEdit or
1. Resume the installation adding the other system management processes are running. If so,
parameter -resume. The wizard resumes in close it or them and continue the installation. If none
interactive mode at the Step List window appear to be open, reboot the workstation and rerun
showing the failed step. the installation.
2. Follow the procedure described for the The following describes how to continue or to rerun
interactive wizard and resume the the installation:
installation.
- Continue the installation
v If you are running the interactive wizard,
AWSJIS110E The installation cannot read the file click OK to close the error popup, and click
"installation_program_files_list_file" that Next to continue.
contains the names of the installation
v If you were running the silent wizard, rerun
programs.
the wizard.
Explanation: The installation needs to access and read
- Rerun the installation
a file containing a list of the installation program files.
If it cannot be read, it might have been damaged in 1. If you are running the interactive wizard,
copying it to the hard disk. click OK to close the error popup window.
2. Reboot the computer.
installation_program_files_list_file is the name of the file
that contains a list of the installation program files. 3. Rerun the wizard, interactively or silently,
with a different user.

v If you were running the silent wizard, rerun the

AWSJIS112E The installation cannot start the process
wizard.
"process_name".
Explanation: The file containing the process might be
missing or corrupt.
available in the directory directory to
process_name identifies the process that cannot be run. perform the installation of the DB2
component.
The installation requires required_space
If you are running the silent wizard, the wizard fails. megabytes are available.
Either make more space available or
Operator response: If you are not running the change the installation directory.
installation from the original CD, delete the copy you
have made of the installation directories and recopy the Explanation: See message.
files from the original CD. If you have ftp’d the install
directory is the install directory that has insufficient
files to the local computer, ensure that you specified the
space.
binary option. Now rerun the installation.
required_space and available_space indicate what space
Proceed as follows:
the installation requires and how much is available.
to close the error popup window. Than click Cancel System action: If you are running the interactive
to quit the wizard. wizard, the wizard stops.
2. Rerun the wizard, interactively or silently. If you are running the silent wizard, the wizard fails.
Operator response:
for assistance. - What to do if you can make space
If you want to persist with the original
AWSJIS113E Either the "userdata" or the installation path, use the operating system’s
"userdata.KEY" file, required for the commands and utilities to make more space
migration of the user information, was available. When you have done this, proceed
not found in the Tivoli Workload as follows:
Scheduler instance to be upgraded. v If you are running the interactive wizard,
Explanation: In order to import the passwords of the click OK to close the error popup, and click
users of the previous version, the upgrade needs to Next to continue.
directly access the userdata and userdata.KEY files, v If you were running the silent wizard, rerun
which form part of the Mozart database of the instance the wizard.
being upgraded.
- What to do if you cannot make space
One, other, or both of these files could not be found.
If you cannot make sufficient space, you need
These files are required for the correct running of the to change the installation path to one with
previous instance of Tivoli Workload Scheduler. more available space. To do this, proceed as
follows:
wizard, the wizard stops. v If you are running the interactive wizard,
click OK to close the error popup, and click
If you are running the silent wizard, the wizard fails. Back to return to where you supplied the
Operator response: Check for the existence of these installation path, change it, ensuring that it
files in the previous instance of Tivoli Workload satisfies the operating system’s requirements
Scheduler. Ensure that the user running the installation for a valid path, and click Next to continue.
has read access to them. If the files have been moved, v If you were running the silent wizard, edit
renamed, or deleted, recover them from a backup of the the response file, changing the installation
previous Tivoli Workload Scheduler instance, and use path so that it satisfies the operating
the facilities in the instance to check that the data in system’s requirements for a valid path.
them is complete. Rerun the silent wizard.
When you have fixed the problem, continue the
installation as follows:
v If you are running the interactive wizard, click OK to
close the error popup, and click Next to continue.


available in the directory directory to directory is the install directory that has insufficient
complete the installation of the DB2 space.
programs.
The installation requires required_space required_space and available_space indicate what space
megabytes, but only available_space the installation requires and how much is available.
megabytes are available. System action: If you are running the interactive
Either make more space available or wizard, the wizard stops.
change the installation directory.
Operator response:
directory is the install directory that has insufficient
space. - What to do if you can make space
required_space and available_space indicate what space If you want to persist with the original
the installation requires and how much is available. installation path, use the operating system’s
commands and utilities to make more space
System action: If you are running the interactive available. When you have done this, proceed
wizard, the wizard stops. as follows:
If you are running the silent wizard, the wizard fails. v If you are running the interactive wizard,
Operator response: Next to continue.
- What to do if you can make space v If you were running the silent wizard, rerun
the wizard.
If you want to persist with the original
installation path, you might be able to use the - What to do if you cannot make space
operating system’s commands and utilities to
make more space available. When you have If you cannot make sufficient space, you need
done this, proceed as follows: to change the installation path to one with
more available space. To do this, proceed as
v If you are running the interactive wizard, follows:
Next to continue. v If you are running the interactive wizard,
v If you were running the silent wizard, rerun Back to return to where you supplied the
the wizard. installation path, change it, ensuring that it
- What to do if you cannot make space satisfies the operating system’s requirements
for a valid path, and click Next to continue.
On Linux and UNIX, the DB2 binaries are
v If you were running the silent wizard, edit
installed on a hard-coded path. If there is
the response file, changing the installation
insufficient space for them, the installation
path so that it satisfies the operating
cannot continue, and you must quit the
system’s requirements for a valid path.
installation and increase the size of the
indicated file system before attempting to
rerun the installation. The path for the binaries
is as follows: AWSJIS117E The supplied port: "port_number" is
registered for use by another application
Linux
in the Services file.
/opt/ibm/db2/V9.5
Explanation: See message.port_number is the port that
UNIX is not free.
/opt/IBM/db2/V9.5 System action: If you are running the interactive
AWSJIS116E There is insufficient disk space If you are running the silent wizard, the wizard fails.
available in the directory directory to
complete the installation of the Tivoli
Workload Scheduler database. Interactive wizard
The installation requires required_space 1. Click OK to close the error popup window.
megabytes are available. 2. Change the indicated port number on the
Either make more space available or wizard panel to a value that is not in use.
change the installation directory. 3. Click Next to continue.

AWSJIS118I • AWSJIS122W
Silent wizard Operator response: Check the rights of the domain

1. Edit the response file used by the silent user and click Next to continue.
wizard. Change the indicated port number
to a value that is not in use. AWSJIS120E The "TWS_user" ID of the previous
2. Rerun the silent wizard. instance of Tivoli Workload Scheduler is
longer than the maximum of max_length
bytes. You cannot upgrade this instance
AWSJIS118I The uninstallation did not remove some
of Tivoli Workload Scheduler.
files that are currently locked. You must
reboot the computer to continue. Explanation: The "TWS_user" in version 8.5 must be
no more than 8 bytes in length. As the "TWS_user" in
Explanation: One or more files are locked by a
the previous instance is longer, you cannot upgrade the
process. However, the uninstallation has determined
instance.
that the files will be deleted after the next reboot. You
must reboot, particularly if you intend to reinstall the System action: The installation stops.
component, or install another component in its place.
Operator response: Click Back to select a different
System action: The uninstallation finishes. instance. Click Cancel to exit from the wizard.
Operator response: After the uninstallation has Perform a fresh installation and then migrate the data
finished, reboot the computer. The locked files are independently from the old instance to the new.
deleted. You can then reinstall the component, or install
See also: Chapter 5, “Upgrading,” on page 55 for
another component in its place.
details of how to migrate data independently.
AWSJIS119W The specified user is a domain user.

AWSJIS122W The user specified for the DB2
Check that it has the required rights.
installation "user" already exists.
See "Administration and
You must be absolutely certain that this
Troubleshooting" for details.
user was created by a previous
Explanation: A domain user must have the following installation of DB2 to go ahead. If in
rights: any doubt, either go back and choose
another user, or delete the user before
- On a computer that is a member of a domain
continuing with the installation, and let
Only a domain user can start the application the wizard create it for you.
server process. It must have the following
Explanation: The attributes and permissions of the
characteristics:
user ID must be correct for using DB2.
v It is a member of the domain administrative
groups in the domain controller user is the user that already exists.
v It has the "Act as part of the operating System action: If you are running the interactive
system" privilege in the Domain Security wizard, the wizard stops.
Policy on the domain controller
system" privilege in the Local Security Operator response: You have three options:
Policy on the local computer - Continue, using the user ID originally chosen
v If the server is run as a service, it has the (created for a previous installation of DB2)
"Log on as a service" privilege on the local v If you are running the interactive wizard,
computer. click OK to close the error popup and click
- On a computer that is a domain controller Next to continue.
v If you were running the silent wizard, rerun
It must have the following characteristics:
the wizard without changing the parameters
v It is a member of the domain administrative or the response file.
groups in the domain controller
- Delete the user ID, letting the wizard create an ID
with the correct attributes
system" privilege in the Domain Security
Policy on the domain controller 1. Delete the user ID using the system’s
facilities
v If the server is run as a service, it has the
"Log on as a service" privilege on the 2. Proceed as follows:
domain controller v If you are running the interactive
wizard, click OK to close the error
System action: The installation panel flow waits for
popup and click Next to continue.
you to continue.

v If you were running the silent wizard,

rerun the wizard without changing the
available in the temporary directory
parameters or the response file.
"directory" to complete the installation.
- Go back and change the user ID The installation requires required_space
v If you are running the interactive wizard, megabytes, but only available_space
click OK to close the error popup, and click megabytes are available.
Back to return to where you supplied the Make more space available in the
user ID, change it to one that was used to temporary installation directory.
create a DB2 instance, and click Next to Explanation: See message.
continue.
directory is the temporary directory that has insufficient
v If you were running the silent wizard, edit
space.
the response file, changing the user ID to
one that was used to create a DB2 instance. required_space and available_space indicate what space
Rerun the silent wizard. the installation requires and how much is available.
AWSJIS123E Unable to find the selected instance to wizard, the wizard stops.
uninstall in the Tivoli Workload
Scheduler registry file. You cannot
uninstall this instance using the wizard. Operator response: Make space in the temporary
directory. Or, on Windows, you can change the location
of the temporary directory, by temporarily or
System action: If you are running the interactive permanently changing the value of the TMP
wizard, the wizard stops. environment variable.
If you are running the silent wizard, the wizard fails. Proceed as follows:
Operator response: If you are running the interactive v If you are running the interactive wizard, click OK to
wizard, cancel the uninstallation. close the error popup, and click Next to continue.
v If you were running the silent wizard, rerun the
Uninstall the instance manually.
wizard.
AWSJIS126E The user ID "user_ID" must not begin
Troubleshooting for instructions on uninstalling Tivoli
with "sys", "ibm", or "sql", as these are
Workload Scheduler manually.
reserved terms.
AWSJIS124E Unable to find the selected instance of
the command line client to uninstall in System action: If you are running the interactive
the Tivoli Workload Scheduler registry wizard, the wizard stops.
file. You cannot uninstall this instance
using the wizard.
Interactive wizard
wizard, the wizard stops. 1. Click OK to close the error popup window.
2. Change the indicated user_ID on the
wizard panel to a value that does not begin
Operator response: If you are running the interactive with any of the indicated values.
wizard, cancel the uninstallation. 3. Click Next to continue.
Uninstall the instance manually. Silent wizard
See also: The chapter on Troubleshooting installation, 1. Edit the response file used by the silent
migration, and uninstallation in Administration and wizard. Change the indicated user_ID to a
Troubleshooting for instructions on uninstalling Tivoli value that does not begin with any of the
Workload Scheduler manually. indicated values.


AWSJIS127E The user ID"user_ID" must not be:
"admins", "guests", "local", "public", or Operator response: Proceed as follows:
"users", nor any SQL key word, as these
are reserved terms. Interactive wizard
2. Provide a valid value for the indicated
System action: If you are running the interactive field.
wizard, the wizard stops. 3. Click Next to continue.
If you are running the silent wizard, the wizard fails. Silent wizard
Operator response: Proceed as follows: 1. Edit the response file used by the silent
wizard. Provide a valid value for the
Interactive wizard
indicated field.
2. Change the indicated user_ID on the
wizard panel to a value that is not any of
the indicated names. AWSJIS130E The field "field_name" must contain a
valid value.
Silent wizard
1. Edit the response file used by the silent System action: If you are running the interactive
wizard. Change the indicated user_ID to a wizard, the wizard stops.
value that is not any of the indicated If you are running the silent wizard, the wizard fails.
names.
2. Rerun the silent wizard. Operator response: Proceed as follows:
Interactive wizard
AWSJIS128E You have specified as the "TWS_user" a 1. Click OK to close the error popup window.
user that already owns an existing Tivoli 2. Provide a valid value for the indicated
Workload Scheduler instance. field.
Click "Back" and specify a different user
for the "TWS_user".
Silent wizard
System action: If you are running the interactive wizard. Provide a valid value for the
wizard, the wizard stops. indicated field.
If you are running the silent wizard, the wizard fails. 2. Rerun the silent wizard.
AWSJIS131E The character "character" is not valid.
Interactive wizard
1. Click OK to close the error popup window. Explanation: See message.
2. Change the <TWS_user> ID on the wizard System action: If you are running the interactive
panel to a value that does not own an wizard, the wizard stops.
existing instance.
Silent wizard
Interactive wizard
wizard. Change the <TWS_user> ID to a 1. Click OK to close the error popup window.
value that does not own an existing 2. Change the indicated character to a valid
instance. one.
2. Rerun the silent wizard. 3. Click Next to continue.
Silent wizard
AWSJIS129E The field "field_name" is required. 1. Edit the response file used by the silent
Explanation: See message. wizard. Change the indicated character to a
valid one.

AWSJIS132E The field "field_name" must not contain AWSJIS134E No feature has been selected. Click
blank characters. "Back" and select a feature to install.
System action: If you are running the interactive System action: The wizard stops.
Operator response:
If you are running the silent wizard, the wizard fails. 1. Click OK to close the error popup window.
Operator response: Proceed as follows: 2. Click Back and select a feature to install.
Interactive wizard 3. Click Next to continue.
2. Remove the blank characters in the AWSJIS135E Unable to establish a connection to host
indicated field. "host_name" on port "port".
Check that the DB2 server is up and
running and that it is listening on this
Silent wizard port.
1. Edit the response file used by the silent Explanation: See message.
wizard. Remove the blank characters in the
indicated field. System action: If you are running the interactive
AWSJIS133E There is not enough space in the Operator response: Check that you have identified the
directory "directory_name". DB2 server correctly. Check that the DB2 server is up
The required space is required_space MB. and running and that it is listening on this port.
The available space is available_space MB.
When the problem has been resolved, proceed as
Explanation: See message. follows:
directory_name identifies the directory with insufficient Interactive wizard
space. 1. Click OK to close the error popup window.
required_space and available_space tell you how much 2. If you have incorrectly identified the DB2
space is needed and how much is available. server, change the server details.
System action: If you are running the interactive 3. Click Next to continue.
wizard, the wizard stops. Silent wizard
If you are running the silent wizard, the wizard fails. 1. If you have incorrectly identified the DB2
server, edit the response file used by the
Operator response: Either make more space in the
silent wizard and change the DB2 server
indicated directory or plan to select a different
details.
directory.
Then proceed as follows:
Interactive wizard AWSJIS136E The supplied password for the user
1. Click OK to close the error popup window. "user" that the wizard must create does
2. If you have chosen to select a different not match the security policy of the
directory, enter the name of, or browse for, computer on which you are performing
a directory with sufficient space. the installation.
3. Click Next to continue. Explanation: See message.
Silent wizard System action: If you are running the interactive

1. If you have chosen to select a different wizard, the wizard stops.
directory, edit the response file used by the If you are running the silent wizard, the wizard fails.
silent wizard and change the installation
directory to one with sufficient space. Operator response: Check the security policy on the
computer where you are performing the installation.
Proceed as follows:
Interactive wizard

1. Click Back to return to the panel where 2. Change the instance name to an existing
you supplied the indicated user and instance.
password. 3. Click Next to continue.
2. Change the password to one that matches
Silent wizard
the security policy and confirm it.
wizard. Change the existing DB2 server
Silent wizard instance name to an existing instance.
1. Edit the response file used by the silent 2. Rerun the silent wizard.
wizard. Change the password for the
indicated user to one that matches the
AWSJIS139E No Oracle Database installation exists at
security policy.
the location "oracle_path". The Oracle
2. Rerun the silent wizard. path must be a search path that includes
the Oracle home directory.
AWSJIS137E The supplied password for the DB2 Explanation: See message.
Administrator "DB2_administrator" is
incorrect. System action: If you are running the interactive
wizard, the wizard stops. Operator response: Check the path you supplied for
the Oracle Database installation with the Oracle
If you are running the silent wizard, the wizard fails. Database administrator. It must be a search path that
Operator response: Check the password you have includes the Oracle home directory.
supplied for the DB2 Administrator. Proceed as follows:
Proceed as follows: Interactive wizard
Interactive wizard 1. Click OK to close the error popup window.
1. Click Back to return to the panel where 2. Change the path to the correct value.
you supplied the indicated user and 3. Click Next to continue.
password.
Silent wizard
2. Change the password for the DB2
Administrator to the correct value. 1. Edit the response file used by the silent
wizard. Change the path to the correct
value.
Silent wizard 2. Rerun the silent wizard.
wizard. Change the password for the DB2
AWSJIS140E The Oracle Database installation that
Administrator to the correct value.
you identified is not a supported
2. Rerun the silent wizard. version. Supported versions are: Oracle
Database 10g Release 2 - Enterprise
AWSJIS138E The specified instance name Edition (10.2.0.x) or later, and Oracle
"instance_name" does not exist on the Database 11g Release 2 - Enterprise
DB2 server. Edition (11.2.0.0) or later. Version 9
Release 2 is supported during the
Explanation: See message. installation, but you are advised to
System action: If you are running the interactive migrate it to a supported version after
wizard, the wizard stops. completing the installation (see the
System Requirements document in the
If you are running the silent wizard, the wizard fails. Information Center for a detailed
Operator response: Check the instance name you have
supplied for the existing DB2 server. Use the DB2 Explanation: See message.
command db2list to list all the instances of the DB2
server. System action: If you are running the interactive
Proceed as follows:
Interactive wizard
Operator response: Check the path you supplied for

the Oracle Database installation. If it is correctly

AWSJIS142E The listener on the Oracle Database
identifying the instance of Oracle you want to use, then
server is not responding to the
the version of that instance is not supported, and you
connection test. This might be caused
must upgrade it to one of the supported versions. If
by:
you cannot upgrade any instance of Oracle to a
an incorrect value specified for the net
supported version you must exit from the wizard and
service name, or the unavailability of
only restart it when you have available a supported
the Oracle server listener.
version of Oracle or DB2, or have planned to install
DB2 with the wizard. Explanation: See message.
If the path you supplied for the Oracle installation is System action: If you are running the interactive
not identifying the instance of Oracle that you want to wizard, the wizard stops.
use, but you can correct it to indicate a supported
instance of Oracle without exiting the wizard, proceed
as follows: Operator response: Check that the Oracle server
listener is available (ask your Oracle administrator if
Interactive wizard
you do not know how). If it is not, get your Oracle
1. Click OK to close the error popup window. server administrator to make the server listener
2. If you were incorrectly identifying the available.
version, change the path to the correct
If the server listener is available, check the supplied net
value.
service name.
Proceed as follows:
Silent wizard
Interactive wizard
1. If you were incorrectly identifying the
version, edit the response file used by the 1. Click OK to close the error popup window.
silent wizard, and change the path to the 2. Change the net service name if it is
correct value. incorrect.
2. Rerun the silent wizard. 3. Click Next to continue.
Silent wizard
AWSJIS141E The value supplied for the input text 1. Edit the response file used by the silent
field input_field is not valid. wizard. Change the net service name if it is
Ensure that the value entered complies incorrect.
with Oracle naming rules.
System action: If you are running the interactive AWSJIS143E The version of the indicated Oracle
wizard, the wizard stops. Database server is not supported.
Supported versions are: Oracle Database
10g Release 2 - Enterprise Edition
Operator response: Check the supplied Oracle data (10.2.0.x) or later, and Oracle Database
field. It must comply with Oracle naming rules. 11g Release 2 - Enterprise Edition
(11.2.0.0) or later. Version 9 Release 2 is
Proceed as follows:
supported during the installation, but
Interactive wizard you are advised to migrate it to a
1. Click OK to close the error popup window. supported version after completing the
installation (see the System
2. Change the input_field to the correct value. Requirements document in the
3. Click Next to continue. Information Center for a detailed
Silent wizard
1. Edit the response file used by the silent Explanation: See message.
wizard. Change the input_field to the System action: If you are running the interactive
correct value. wizard, the wizard stops.
Operator response: Check the version of the Oracle
server. If it is not a supported version you must
upgrade it to one of the supported versions. If you
cannot upgrade any version of the Oracle server to a

supported version you must exit from the wizard and 1. Edit the response file used by the silent
only restart it when you have available a supported wizard. Change the user ID or its
version of Oracle or DB2, or have planned to install password to the correct values.
DB2 with the wizard. 2. Rerun the silent wizard.
If you can make a supported version of the Oracle
server available without exiting the wizard, proceed as AWSJIS146E The DB2 Administrator user name
follows: "user_name" can not start with an
Interactive wizard underscore character "_".
1. Click OK to close the error popup window. Explanation: See message.
2. Click Next to continue. System action: If you are running the interactive
Silent wizard wizard, the wizard stops.
1. Rerun the silent wizard. If you are running the silent wizard, the wizard fails.
AWSJIS144E The specified tablespace tablespace_name
Interactive wizard
does not exist.
2. Supply a valid DB2 Administrator user
System action: If you are running the interactive name.
wizard, the wizard stops. 3. Click Next to continue.
If you are running the silent wizard, the wizard fails. Silent wizard
Operator response: Check the supplied tablespace 1. Edit the response file used by the silent
name. It must be an existing tablespace in your chosen wizard. Supply a valid DB2 Administrator
Oracle instance. user name.
Proceed as follows: 2. Rerun the silent wizard.
Interactive wizard
AWSJIS147E The DB2 Administrator user name
"user_name" can not start with a number.
2. Change the tablespace name to the correct
value. Explanation: See message.
3. Click Next to continue. System action: If you are running the interactive
Silent wizard
1. Edit the response file used by the silent If you are running the silent wizard, the wizard fails.
wizard. Change the tablespace name to the Operator response: Proceed as follows:
correct value.
Interactive wizard
2. Supply a valid DB2 Administrator user
AWSJIS145E The supplied credentials for user
name.
user_ID are not correct.
Silent wizard
wizard. Supply a valid DB2 Administrator
If you are running the silent wizard, the wizard fails. user name.
Operator response: Check the supplied user ID. 2. Rerun the silent wizard.
Proceed as follows:
AWSJIS148E No instances of Tivoli Workload
Interactive wizard Scheduler, version 8.5 have been found
1. Click OK to close the error popup window. to upgrade to fix pack 01.
2. Change the user ID or its password to the Explanation: See message.
correct values.
Silent wizard

If you are running the silent wizard, the wizard fails. If only a few objects have not been
migrated, create these objects in the new
Operator response: Check if there is a valid version of
database using composer.
Tivoli Workload Scheduler, version 8.5 installed on the
computer. Object type not migrated
v If you are certain that a valid version is installed, v If all objects of an object type from the
perhaps the product registry is not correctly database did not migrate, run the
identifying the valid version, in which case you datamigrate command on that object
should contact IBM Software Support for assistance. type.
v If there is a version of Tivoli Workload Scheduler v If the migration failed running either
prior to version 8.5, you must use the product optman miggrunnb or optman
images that allow you to upgrade from a prior miggopts, rerun that command.
version directly to this fix pack.
All object types not migrated
v If there is no version of Tivoli Workload Scheduler
8.5 installed on the computer, you must make a fresh Run the migration manually. The original
installation of Tivoli Workload Scheduler, version 8.5 Mozart database has now been deleted, so
with this fix pack. you must use the version stored in the
backup directory that you identified during
In all of these cases, exit from the wizard. the installation.
If the wizard does not successfully complete the

AWSJIS149E One or more errors have occurred installation (apart from this message), you will have the
during the migration. Check the opportunity to rerun the step that imports the data. To
troubleshooting information in the do this, follow this procedure
directory: "directory".
1. Correct the problem that caused the installation to
Explanation: The installation has verified that one or fail.
more errors have occurred during the migration of the 2. Correct the problem that caused this message to be
previous database. The information about what has displayed, as described above.
occurred can be found in the indicated directory. The
3. Resume the installation from the data import step,
error is likely to be the failure to migrate an object
setting the statuses of all other steps that follow it
type, but it may be limited to a problem with a single
to "Ready".
object. At worst case it might indicate that no data has
been migrated. In most cases the errors indicated by
this message are due to problems with access to the AWSJIS150E The specified user does not exist.
previous database.
wizard, the wizard stops and displays the panel with System action: If you are running the interactive
this message. wizard, the wizard stops.
If you are running the silent wizard, the wizard If you are running the silent wizard, the wizard fails.
completes the installation, but creates a file called Operator response: Proceed as follows:
migrationErrors in the directory where the installation
logs are written (see the Administration and Interactive wizard
Troubleshooting manual for details). 1. Click OK to close the error popup window.
Operator response: Proceed as follows: 2. Change the user name to a valid one.
1. If you are running the interactive wizard, click OK 3. Click Next to continue.
to close the error popup window. The wizard Silent wizard
continues to the finish.
2. Look in the indicated directory and check the files wizard. Change the user name to a valid
that log the success and failure of the various one.
migration steps.
3. Solve the problem that has stopped the data from
being migrated.
AWSJIS151E The specified password for the user is
4. The recovery action depends on the scale of the
wrong.
problem:
Object not migrated

If you are running the silent wizard, the wizard fails. 1. Click OK to close the error popup window.
Operator response: Proceed as follows: 2. Change one or both of the indicated fields
to have the same value.
Interactive wizard
Silent wizard
2. Change the password to the correct one.
wizard. Change one or both of the
Silent wizard indicated fields to have the same value.
1. Edit the response file used by the silent 2. Rerun the silent wizard.
wizard. Change the password to the correct
one.
AWSJIS154E The connection to the DB2 database
2. Rerun the silent wizard. failed. Verify that the following fields
are correct: "database_name",
AWSJIS152E The supplied database schema "db2_admin_user", "db2_admin_password".
schema_name must already exist when If you are using a DB2 Administration
installing a backup master domain Client, verify also that the
manager. "db2_client_user" is correct.
System action: If you are running the interactive System action: If you are running the interactive
wizard, the wizard stops. wizard, the wizard stops.
If you are running the silent wizard, the wizard fails. If you are running the silent wizard, the wizard fails.
Operator response: Check the database schema name Operator response: Proceed as follows:
you have used. It must be an existing schema in the Interactive wizard
chosen Oracle instance.
Proceed as follows: 2. Change any of the indicated fields that are
Interactive wizard incorrect.
1. Click OK to close the error popup window. 3. Click Next to continue.
2. Change the schema_name to the correct one. Silent wizard
3. Click Next to continue. 1. Edit the response file used by the silent
wizard. Change any of the indicated fields
Silent wizard that are incorrect.
1. Edit the response file used by the silent 2. Save the response file.
wizard. Change the schema_name to the
correct one. 3. Rerun the silent wizard.
AWSJIS155E An error occurred unzipping the archive
in the specified directory. Verify that
AWSJIS153E The input fields "field_name1" and you have the required permissions in
"field_name2" must have the same value. the destination directory.
Explanation: This is a generic message indicating that Explanation: See message.
two input fields must have the same value. For
example, if you are installing the DB2 server on UNIX, System action: If you are running the interactive
the DB2 instance name and the ID of the DB2 instance wizard, the wizard stops.
owner must be the same.
Interactive wizard
Operator response: Check the values of the indicated
2. Change any of the indicated fields that are
fields.
incorrect.
Proceed as follows: 3. Click Next to continue.
Interactive wizard Silent wizard

1. Edit the response file used by the silent 1. If you are running the interactive wizard,
wizard. Change any of the indicated fields close the Step Status window and click
that are incorrect. Finish on the Step List window. The
2. Save the response file. wizard closes.
3. Rerun the silent wizard. 2. If you previously copied the installation
remote workstation, ensure that the entire
AWSJIS157E An internal error has occurred. The disk image was copied, and that the binary
application server profile "profile" for the option was set if ftp was used.
Server could not be upgraded.
- Rerun the silent installation.
Explanation: The installation program needs to
upgrade an application server profile for the embedded 1. If you have copied the installation images
WebSphere Application Server, and then populate it to the local hard disk or to a remote
with the information specific to Tivoli Workload workstation, ensure that the entire disk
Scheduler, version 8.5 . This message is displayed image was copied, and that the binary
because the profile could not be upgraded. option was set if ftp was used.
2. Rerun the silent installation.
If you are running the silent installation, the installation for assistance.
fails.
Operator response: Check that the computer where migration, and uninstallation in Administration and
you are installing Tivoli Workload Scheduler satisfies Troubleshooting for full details of the recovery process
the prerequisite requirements of the embedded from a failed installation.
WebSphere Application Server . These can be found by
clicking the System requirements link on the product
AWSJIS158E No additional feature is available for
information Web page for the embedded WebSphere
the selected instance. Click "Back" and
Application Server at www.ibm.com.
select another instance.
Check that there is sufficient space in the standard
temporary directory of the computer.
System action: The wizard stops.
Check that you have copied the installation images
correctly to the computer where you are running the Operator response:
installation wizard. 1. Click Back and select another instance.
If you are running the interactive wizard, look at the 2. Click Cancel to exit the wizard.
AWSJIS159E The port "port_num" has been already
1. Note down the error code (so that you can later specified for the "port_name". Specify a
find it in Administration and Troubleshooting, if different value.
needed)
2. Click OK to close the error message window. The Explanation: See message.
Diagnose Failure window is opened. port_num identifies the port that has been specified and
3. Select Diagnose failure and click Next. The Step is duplicate.
port_name identifies the name of the port containing the
4. Select the failed installation step and double click it duplicate information.
If you are running the silent installation, check the If you are running the silent installation, the installation
installation log for more information. fails.
Operator response: Check the port numbers you have
The problem is resolved by just rerunning the used. Make sure that a unique value has been supplied
installation. for each port and that the supplied ports are available.
- Rerun the interactive wizard Proceed as follows:

1. Click OK to close the error message characters identifies the list of supported characters.
window.
2. Change the port or ports. wizard, the wizard stops.
- Silent installation
Operator response: Change the password of the
1. Edit the response file used by the silent specified user.
installation, changing the value of the
indicated port or ports. Proceed as follows:
2. Rerun the silent installation. - Interactive wizard
AWSJIS160E The supplied Oracle Database window.
installation does not have the 2. Modify the operating system password of
Partitioning Feature enabled. the specified user.
Install and enable this feature on the 3. Click Next to continue.
selected Oracle installation and then
continue or rerun the Tivoli Workload - Silent installation
Scheduler installation. 1. Change the operating system password of
Explanation: See message. the specified user
System action: If you are running the interactive wizard and change the corresponding
wizard, the wizard stops. password field to match the operating
If you are running the silent installation, the installation system password..
fails. 3. Rerun the silent installation.
Operator response: If you are running the interactive See also: The chapter on Troubleshooting installation,
wizard, click OK to close the error message window migration, and uninstallation in Administration and
and Cancel to exit from the wizard. Troubleshooting for full details of the recovery process
Check the Oracle installation you have selected and
install the Partitioning Feature.
AWSJIS164E The supplied installation path is already
Rerun the installation.
being used by another instance of Tivoli
Workload Automation. Choose another
AWSJIS161E The field "field" with value "value" path.
contains national characters.
Explanation: A Tivoli Workload Automation instance
National characters are not supported
can only have one instance of each of its constituent
for this field.
products and components installed in it. To install more
Explanation: See message. than one instance of a product or component, you must
install them in a different path, thereby creating a
second instance of Tivoli Workload Automation.
For example, if you have installed the Tivoli Workload
If you are running the silent installation, the installation
Scheduler master domain manager with the default
fails.
path, it will have been installed in a path that includes
Operator response: If you are running the interactive the token "TWA", which indicates that this is the first
wizard, click OK to close the error popup window and instance of Tivoli Workload Automation products and
Cancel to exit the wizard. components on the system. To install a second Tivoli
Workload Scheduler component choose any other path
Check the Oracle installation you have selected and that is not the same as, or within, the path of the first
install the Partitioning Feature. instance.
Rerun the installation. Note that if the default path includes the token"TWA1",
there are already two instances of Tivoli Workload
Automation on the system on which you cannot install
AWSJIS162E The supplied password contains an the component. To install a third Tivoli Workload
unsupported character. Scheduler component choose any other path that is not
The supported characters are as follows: the same as, or within, the path of the first two
characters instances.


AWSJIS166E No valid action can be performed on the
Tivoli Workload Automation instance
If you are running the silent installation, the installation that has been selected.
fails. Select another valid instance in which to
install the product or component, or
Operator response: Proceed as follows: create a new instance.
- Interactive wizard Explanation: A Tivoli Workload Automation instance
1. Click OK to close the error message. can only have one instance of each of its constituent
2. Reenter the installation path, ensuring that products and components installed in it. To install more
the path does not identify an existing than one instance of a product or component, you must
Tivoli Workload Automation instance, and install them in a different path, thereby creating a
click Next to continue. second instance of Tivoli Workload Automation.
- Silent installation For example, if you have installed the Tivoli Workload
Scheduler master domain manager with the default
1. Edit the response file and ensure that the
path, it will have been installed in a path that includes
path does not identify an existing Tivoli
the token "TWA", which indicates that this is the first
Workload Automation instance.
instance of Tivoli Workload Automation products and
2. Rerun the silent installation. components on the system. To install a second Tivoli
Workload Scheduler component choose any other path
AWSJIS165E No valid instance of Tivoli Workload that is not the same as, or within, the path of the first
Automation has been specified. instance.
Specify a valid instance or install the Note that if the default path includes the token"TWA1",
component in a new instance. there are already two instances of Tivoli Workload
Automation on the system on which you cannot install
Explanation: A Tivoli Workload Automation instance the component. To install a third Tivoli Workload
can only have one instance of each of its constituent Scheduler component choose any other path that is not
products and components installed in it. To install more the same as, or within, the path of the first two
than one instance of a product or component, you must instances.
second instance of Tivoli Workload Automation. System action: If you are running the interactive
For example, if you have installed the Tivoli Workload
Scheduler master domain manager with the default If you are running the silent installation, the installation
path, it will have been installed in a path that includes fails.
the token "TWA", which indicates that this is the first Operator response: Proceed as follows:
instance of Tivoli Workload Automation products and
components on the system. To install a second Tivoli - Interactive wizard
Workload Scheduler component choose any other path 1. Click OK to close the error message.
that is not the same as, or within, the path of the first 2. Reenter the installation path, ensuring that
instance. the path does not identify an existing
Note that if the default path includes the token Tivoli Workload Automation instance. Click
"TWA1", there are already two instances of Tivoli Next to continue.
Workload Automation on the system on which you
cannot install the component. To install a third Tivoli - Silent installation
Workload Scheduler component, choose any other path 1. Edit the response file and ensure that the
that is not the same as, or within, the path of the first installation path does not identify an
two instances. existing Tivoli Workload Automation
System action: The silent installation fails. instance.
1. Edit the response file and ensure that the path does
not identify an existing Tivoli Workload Automation AWSJIS167E The embedded WebSphere Application
instance. Server administration user name was
not found.
Explanation: You have clicked the Retrieve button to
retrieve the embedded WebSphere Application Server
administration user name. The wizard was unable to
retrieve the user name either because the user registry
solution you have chosen does not allow user names to
be kept in the embedded WebSphere Application Server

configuration files, or because the embedded wizard cannot find any component that can be
WebSphere Application Server did not respond upgraded.
correctly.
System action: If the user registry solution you have wizard, the wizard stops.
chosen does not allow user names to be kept in the
embedded WebSphere Application Server configuration
fails.
files, the administration user field in the wizard is
defaulted as "UNKNOWN". Otherwise, the Operator response: Proceed as follows:
administration user field is left blank. 1. If you are running the interactive wizard, click OK
Operator response: Obtain the embedded WebSphere to close the error message. The wizard closes.
Application Server administration user name from the 2. If a Tivoli Workload Scheduler component is
embedded WebSphere Application Server administrator installed on the system, check to determine if the
or other person responsible for maintaining the component in question can be upgraded (some
embedded WebSphere Application Server. Enter the components must be replaced with a fresh
value in the administration user field, enter the installation of the new version).
password and continue. 3. Check also in the manual that the version of the
component is compatible with the upgrade action.
AWSJIS168E You cannot upgrade Tivoli Workload
Scheduler when it is installed in the If none of these actions apply, but the instance of the
root directory. component exists, the registry may be damaged, and
thus is not reporting the presence of the instance.
Explanation: You have selected to upgrade an instance Contact IBM Software Support for assistance.
of a Tivoli Workload Scheduler component but it is
installed in the root directory. The upgrade cannot be
performed, for technical reasons. AWSJIS171W You specified a Tivoli Workload
Scheduler user name different from
System action: If you are running the interactive the embedded WebSphere Application
wizard, the wizard stops. Server administrator user name.
If you are running the silent installation, the installation To allow successful connections to the
fails. integrated engine,
modify the Tivoli Workload Scheduler
Operator response: Proceed as follows: Security file adding
- Interactive wizard the embedded WebSphere Application
Server administrator user name.
2. Do one of the following: Explanation: See message.
v Chose a different instance to upgrade, System action: The wizard completes with this
and click Next to continue. warning.
v Exit from the wizard and run the Operator response: See message.
parallel upgrade, which requires you to
install a fresh instance of the
component.. AWSJIS172E The Tivoli Workload Scheduler Oracle
database administrator user password
- Silent installation must start with an alphabetic character.
1. Do one of the following:
v Chose a different instance to upgrade,
edit the response file to identify it, and System action: If you are running the interactive
rerun the upgrade wizard, the wizard stops.
v Run the parallel upgrade, which requires If you are running the silent wizard, the wizard fails.
you to install a fresh instance of the
component. Operator response: Proceed as follows:
Interactive wizard
AWSJIS170E No instance of a Tivoli Workload 1. Click OK to close the error popup window.
Scheduler component has been found 2. Supply a valid Oracle database
that can be upgraded. The wizard closes administrator password.
when you close the message pop-up.
Explanation: You have selected an upgrade action for
Silent wizard
a component of Tivoli Workload Scheduler, but the

1. Edit the response file used by the silent 2. Edit your old final job stream with composer or the
wizard. Supply a valid Oracle database Tivoli Dynamic Workload Console
administrator password. 3. Merge the two job streams so that your new final
2. Rerun the silent wizard. job stream has the same name and customizations
as before (if you want to preserve the naming), plus
the new required attributes from the new FINAL
AWSJIS173E One or more prerequisite library is
job stream.
missing, as follows:
"list_of_missing_libraries". Obtain and 4. Save your new final job stream.
install the library, and then rerun the
installation. If you had a final job stream called by any name other
than FINAL in your database, but it is not customized,
Explanation: The wizard requires the use of the after completing the installation, proceed as follows:
standard C libraries, at least one of which is missing.
1. Delete your old final job stream with composer or
System action: If you are running the interactive the Tivoli Dynamic Workload Console
wizard, the wizard stops. 2. Rename the FINAL job stream with the name of
If you are running the silent wizard, the wizard fails. your old final job stream with composer or the
Tivoli Dynamic Workload Console
Interactive wizard AWSJIS175W The tablespace path "path" already
1. Click Cancel to close the installation exists and is not empty.
wizard. Check if the selected path contains
2. Add the required libraries to your system. tablespace data of a Tivoli Workload
Scheduler database.
3. Rerun the installation wizard. If yes, continue, otherwise choose
Silent wizard another tablespace path.
1. Add the required libraries to your Explanation: See message.
machine.
path is the path specified for a Tivoli Workload
2. Rerun the silent wizard. Scheduler tablespace.
System action: The installation stops while you
AWSJIS174W If you have a job stream called FINAL determine the correct action to take.
in the database, it has been backed up
to the file "Sfinal.extract" and then Operator response: Check the contents of the specified
overwritten. path:
If your old final job stream was 1. If the path includes tablespace data for a Tivoli
customized, or is not called FINAL, you Workload Scheduler database that you want to use
must perform some customization steps. for the current installation, you can continue.
Explanation: See message. 2. If the path does not include tablespace data for a
Tivoli Workload Scheduler database that you want
System action: See message. If you have a final job to use for the current installation, choose a different
stream but it is not called FINAL, it will not have been path and continue.
backed up.
Operator response: If you had a customized job To check if the specified path is in use by a tablespace
stream called FINAL in your database, after completing in the Tivoli Workload Scheduler database, you can get
the installation, proceed as follows: a DB2 snapshot for tablespaces on the Tivoli Workload
1. Edit the new FINAL job stream with composer or Scheduler database. Please refer to the DB2
the Tivoli Dynamic Workload Console documentation for more information about database
snapshots and monitoring features.
2. Edit the file Sfinal.extract with a text editor
3. Make the corresponding customizations to the new
FINAL job stream. AWSJIS176E The selected tablespace paths are either
equal or one is a subpath of the other:
4. Save your new FINAL job stream. "path1"
"path2". The paths must be different and
If you had a customized final job stream called by any one cannot contain the other.
name other than FINAL in your database, after
completing the installation, proceed as follows: Explanation: See message.
1. Edit the new FINAL job stream with composer or path1 is the path specified for a Tivoli Workload
the Tivoli Dynamic Workload Console Scheduler tablespace.

AWSFAB003E • AWSFAB009E
path2 is the path specified for a Tivoli Workload 3. Continue with the installation.
Scheduler tablespace.
Silent wizard
System action: The installation cannot proceed 1. Choose different values for the tablespace
because either the specified paths are the same or one paths, so that they are not the same and
is a subpath of the other. that one is not a subpath of the other.
Operator response: Proceed as follows: 2. Rerun the silent wizard.
Interactive wizard
1. Click Close to close the Popup Window.
2. Choose different values for the tablespace
paths, so that they are not the same and
that one is not a subpath of the other.
Installation messages (twsinst) - FAB

This chapter lists error and warning messages that could be generated when using
the twsinst script to install the product.
The message component code is FAB.
AWSFAB003E The twsinst script cannot run on this AWSFAB007E The supplied installation type
operating system: operating_system. parameter is not correct. It must be one
of the following: "-new", "-update",
"-uninst".
System action: The twsinst script cannot proceed.
Operator response: Check in the IBM Tivoli Workload
Scheduler Release Notes for details of supported
platforms. Operator response: Check the usage of the twsinst
script by referring to “Installing non-integratable agents
Check to see if any other installation method can be
using twsinst” on page 48, or use the command twsinst
used.
-u to the see a list of the available parameters.
See also: IBM Tivoli Workload Scheduler Release Notes
Rerun the twsinst script, supplying the correct
parameter.
AWSFAB004E Only the user "root" can run the
twsinst script.
AWSFAB008E More than one installation type
Explanation: See message text parameter has been supplied. Supply
only one of the following: "-new",
System action: The twsinst script cannot proceed. "-update", "-uninst".
Operator response: Login as the "root" user and rerun Explanation: See message text.
the twsinst script.
AWSFAB005E No parameters have been specified for Operator response: Check the usage of the twsinst
twsinst. script by referring to “Installing non-integratable agents
Explanation: The twsinst script needs to be supplied -u to the see a list of the available parameters.
with at least one parameter.
System action: The twsinst script cannot proceed. parameter.
Operator response: Check the usage of the twsinst
script by referring to “Installing non-integratable agents AWSFAB009E A parameter to twsinst has been
using twsinst” on page 48, or use the command twsinst supplied that is not appropriate for the
-u to the see a list of the available parameters. supplied installation type. Specify the
Rerun the twsinst script, supplying the correct "installation_parameter" parameter only
parameter. when "installation_type" installation type
is specified.
Explanation: The installation_parameter is a parameter

that you supplied, that is not appropriate for the

AWSFAB014E The following is not a recognizable
supplied installation type.
installation parameter
The installation_type is a list of the only installation "installation_parameter".
types with which you can use the supplied
installation_parameter.
parameter.
parameter.
AWSFAB015E The "-uname" option is missing.

AWSFAB010E An incorrect value has been supplied
for a parameter. The parameter must be Explanation: The indicated parameter is mandatory
as follows: "installation_parameter". for this installation type.
Explanation: The parameter you have supplied is System action: The twsinst script cannot proceed.
correct, and is valid for this installation type. However,
the value supplied for the parameter is not correct.
System action: The twsinst script cannot proceed. using twsinst” on page 48, or use the command twsinst
script by referring to “Installing non-integratable agents Rerun the twsinst script, supplying the correct
using twsinst” on page 48, or use the command twsinst parameter.
Rerun the twsinst script, supplying the correct AWSFAB016E The following user account has been
parameter value. supplied that does not exist on the local
computer: "user_account". You must
create the user account before running
AWSFAB011E The following parameter has been
twsinst.
supplied more than
once:"installation_parameter". Explanation: See message text.
Explanation: See message text. System action: The twsinst script cannot proceed.
System action: The twsinst script cannot proceed. Operator response: Check that the correct account
name was supplied. If it was not, rerun the twsinst
script, supplying the correct account name.
using twsinst” on page 48, or use the command twsinst If the correct account name was supplied, create the
-u to the see a list of the available parameters. account before rerunning the twsinst script.
parameter. AWSFAB017E The script was unable to locate the
home directory of the specified user:
"user_account".
AWSFAB012E The following installation parameter
"installation_parameter" has been supplied Explanation: Tivoli Workload Scheduler is installed in
that is not allowed with the installation the home directory of the TWSUser. The installation
type "-uninst". script cannot locate the home directory of user you
have nominated as the TWSUser.
Operator response: Rerun the twsinst script,
specifying the home directory of the TWSUser using
the inst_dir parameter.
-u to the see a list of the available parameters. If in doubt, check the usage of the twsinst script by
referring to “Installing non-integratable agents using
twsinst” on page 48, or use the command twsinst -u to
parameter.

the see a list of the available parameters. v Or, change the installation type to -new or -uninst, as
appropriate, and rerun the installation.
AWSFAB018E The script was unable to locate the
home directory of the specified user, AWSFAB022E You are running a fresh installation
and the installation directory has not but the installation script has found a
been supplied. Supply the installation previous instance of Tivoli Workload
directory explicitly using the following Scheduler in the following directory:
parameter: "parameter_name". directory_name.
Explanation: See message text. Explanation: You cannot install more than one
instance of Tivoli Workload Scheduler on the same
computer.
specifying the home directory of the TWSUser using
the indicated parameter. Operator response: You can do one of the following:
If in doubt, check the usage of the twsinst script by v Either uninstall the existing instance of Tivoli
referring to “Installing non-integratable agents using Workload Scheduler and then rerun the twsinst script
twsinst” on page 48, or use the command twsinst -u to as a fresh installation.
the see a list of the available parameters. v Or, change the installation type to -update, -uninst,
or -restore, as appropriate, and rerun the installation.
AWSFAB019E The supplied target installation
directory "directory_name does not exist. AWSFAB023E You are trying to run a fresh
installation but the installation script
Explanation: The home directory of the TWSUser
has found one or both of the Tivoli
must exist before running the installation.
Workload Scheduler configuration files
System action: The twsinst script cannot proceed. in the following directory:
directory_name.
Operator response: Create the home directory of the
TWSUser and then rerun the twsinst script. Explanation: This message might indicate that a
previous uninstallation of Tivoli Workload Scheduler
did not complete correctly.
AWSFAB020E You are upgrading Tivoli Workload
Scheduler, but the twsinst script cannot System action: The twsinst script cannot proceed.
locate the configuration file
Operator response: You can do one of the following:
"configuration_file"of the version you are
upgrading. v Either uninstall the existing instance of Tivoli
Workload Scheduler and then rerun the twsinst script
Explanation: See message text. as a fresh installation. If you have already
System action: The twsinst script cannot proceed. uninstalled the product, check the home directory of
the TWSUser, and delete any files and directories
Operator response: Locate the indicated configuration there that belong to Tivoli Workload Scheduler.
file and move it to the correct directory (see the v Or, change the installation type to -update, -uninst,
documentation for the version you are upgrading for or -restore, as appropriate, and rerun the installation.
the exact location of the configuration file). Then rerun
the twsinst script.
AWSFAB024E You are performing a fresh
installation, but the installation script
AWSFAB021E You are trying to run an has found a previous instance of Tivoli
installation_type installation but the Workload Scheduler belongs to the
installation script has not found the following user:"user_name".
Tivoli Workload Scheduler
configuration files belonging to the Explanation: This message might indicate that a
existing instance. previous uninstallation of Tivoli Workload Scheduler
did not complete correctly.
v Either uninstall the existing instance of Tivoli
v Either locate the configuration files (localopts and Workload Scheduler and then rerun the twsinst script
globalopts) and move them into the TWSHome as a fresh installation.
directory before rerunning the twsinst script.

v Or, change the installation type to -update, -uninst, v If the file is corrupt or unreadable, and you have no
or -restore, as appropriate, and rerun the installation. good backup of it, you must uninstall Tivoli
v Or, edit the indicated registry file to delete the Workload Scheduler and make a fresh installation of
previous registry keys. See the chapter on it.
troubleshooting the installation for a description of v If the file is readable but the indicated parameter is
the registry keys. absent, you can add it, and rerun the twsinst script.
See also: The chapter on troubleshooting the v In all other cases contact IBM Software Support.
installation in this manual.
AWSFAB028E The supplied port number is not in
AWSFAB025E You are performing an update or the range 1 - 65535.
uninstall operation, but the installation Explanation: See message text.
script has failed to find a previous
instance of Tivoli Workload Scheduler System action: The twsinst script cannot proceed.
in the Tivoli Workload Scheduler Operator response: Rerun the twsinst script,
registry file. The script expected to find supplying a value for the port number parameter in the
an entry belonging to the following indicated range.
user:"user_name" and in the following
registry file: registry_file_name.
AWSFAB029W The supplied port number
Explanation: Either the user that is performing the "port_number" is normally used by other
operation is not the owner of the existing Tivoli services, such as ftp, or telnet, but will
Workload Scheduler instance, or the Tivoli Workload be used.
Scheduler registry file contains incorrect information.
System action: The twsinst script proceeds using the
Operator response: Check the indicated registry file. port number you supplied.
v If the existing instance is registered for a different
user than that running the installation, either log off Operator response: After the installation has
and log on again as that user, or change the registry completed, you might decide to change the port
file to show your user name. number to a different value by editing the localopts file.
The default value for Tivoli Workload Scheduler is
v If the existing instance is not present at all, or is 31111, but you can use any value between 1 - 65535
corrupt, try uninstalling and reinstalling the instance. that is not being used by another application or service.
AWSFAB026E The following parameter: AWSFAB030E The supplied company name too long.
"first_parameter" cannot be used with the The limit is 40 bytes.
following parameter: "second_parameter".
Operator response: Check the usage of the twsinst supplying a value for the company parameter which is
script by referring to“Installing non-integratable agents not more than 40 bytes.
AWSFAB031E You can not promote an agent from
Rerun the twsinst script, supplying the correct "original_agent_type" to
parameter. "promoted_agent_type".
Explanation: You can only promote a lower type of
AWSFAB027E The installation was unable to retrieve agent to a higher type. For example, you can promote a
the following parameter: "parameter" standard agent to a fault-tolerant agent, but not a
from the following Tivoli Workload fault-tolerant agent to a standard agent. If you need to
Scheduler configuration file: do the latter, uninstall the previous agent and make a
configuration_file. fresh installation of the new agent.
Explanation: See message text. System action: The twsinst script cannot proceed.
System action: The twsinst script cannot proceed. Operator response: Either promote a different agent
Operator response: Check the indicated configuration or uninstall the previous agent and make a fresh
file. installation of the new agent.

v A copy of the twsinst utility and its associated files

AWSFAB032E The installation script was unable to
placed in any local directory other than the home
obtain the name of the TWSuser group
directory of the user that you have nominating as the
from the following component file of
TWSuser in the twsinst parameters.
the existing instance of Tivoli Workload
Scheduler: component_file_name. System action: The twsinst script cannot proceed.
Explanation: See message text. Operator response: Rerun the installation from a
permitted directory.
Operator response: Check the indicated component
AWSFAB039E The installation script was not able to
file.
locate the following file needed set up
v If the file is corrupt or unreadable, and you have no the installation environment: file_name.
good backup of it, you must uninstall Tivoli
Workload Scheduler and make a fresh installation of Explanation: See message text.
it. System action: The twsinst script cannot proceed.
v If the file is readable but the indicated TWSUser
group name is absent, you can add it, and rerun the Operator response: Contact IBM Software Support.
twsinst script.
v In all other cases contact IBM Software Support. AWSFAB040E The installation script has been run
from the wrong directory. Rerun the
script from the following
AWSFAB035E The installation has failed. For more directory:directory_name.
details see the log file: log_file_name.
Explanation: You have run the twsinst script from the
Explanation: An internal error has occurred that has home directory of a different user than that identified
caused the installation to fail. in the -uname parameter. If you wanted that the user
System action: The twsinst script cannot proceed. identified in the -uname parameter is the TWSUser, run
the installation from that user’s home directory.
Operator response: Look in the log file for messages
that indicate the cause of the failure. If you are able to directory_name is the home directory of the user
identify and resolve the problem, rerun the installation. identified in the -uname parameter.
If not, contact IBM Software Support. System action: The twsinst script cannot proceed.
Operator response: Rerun the twsinst installation
AWSFAB036E The uninstallation has failed. For script from the indicated directory.
more details see the log file:
log_file_name.
AWSFAB041E The installation script has detected
Explanation: An internal error has occurred that has that at least one Tivoli Workload
caused the uninstallation to fail. Scheduler process is running. No
System action: The twsinst script cannot proceed. processes can be running when you
perform an installation, upgrade,
Operator response: Look in the log file for messages promotion, restore or uninstallation.
that indicate the cause of the failure. If you are able to
identify and resolve the problem, rerun the Explanation: See message text.
uninstallation. If not, contact IBM Software Support. System action: The twsinst script cannot proceed.
Operator response: Follow the instructions in Tivoli
AWSFAB037E The twsinst script is being run from Workload Scheduler: Administration and Troubleshooting to
the wrong directory. shut down all Tivoli Workload Scheduler processes.
Explanation: You are attempting to install Tivoli See also: Tivoli Workload Scheduler: Administration and
Workload Scheduler on a UNIX platform using the Troubleshooting
twsinst utility copied from the installation CD to the
home directory of the user that you have nominated as
the TWSuser during the installation. This is not AWSFAB042E The installation script has detected
allowed. that at least one Tivoli Workload
Scheduler process is running. No
You can run twsinst from any of the following places: processes can be running when you
v The Tivoli Workload Scheduler CD perform an installation, upgrade,
v A disk image of the CD promotion, restore or uninstallation.

AWSFAB043W • AWSFAB094E

AWSFAB048E The company name cannot contain
Operator response: Follow the instructions in Tivoli blank characters (spaces).
Workload Scheduler: Administration and Troubleshooting to
shut down all Tivoli Workload Scheduler processes.
AWSFAB043W At least one warning message has Operator response: Rerun the twsinst script,
been issued during the installation. supplying a company name that does not contain blank
characters (spaces).
System action: The twsinst script proceeds.
AWSFAB049E The installation directory cannot
Operator response: Check the install log file and read contain blank characters (spaces).
the warning message or messages.
Explanation: If you did not specify the installation
directory explicitly, it means that the home directory of
AWSFAB044W At least one warning message has the TWSuser contains blank characters (spaces).
been issued during the uninstallation.
Operator response: If you have explicitly supplied the
System action: The twsinst script proceeds. installation directory, rerun the twsinst script,
supplying an installation directory that does not
Operator response: Check the install log file and read contain blank characters (spaces).
the warning message or messages.
If the home directory of the TWSuser contains blank
characters (spaces), choose another user as the
AWSFAB046E An inconsistent parameter has been TWSuser, or change the name of the home directory of
used. You cannot specify the "-thiscpu" the TWSuser to not contain blank characters (spaces).
parameter when the "-cputype master"
parameter has been specified.
AWSFAB050E The following parameter: "parameter"
Explanation: See message text. cannot contain more than "number"bytes.
System action: The twsinst script cannot proceed. Explanation: See message text.
Operator response: Check the usage of the twsinst System action: The twsinst script cannot proceed.
using twsinst” on page 48, or use the command twsinst Operator response: Rerun the twsinst script,
-u to the see a list of the available parameters. supplying the indicated parameter with a value not
more than that indicated.
parameter.
AWSFAB094E The -restore parameter cannot be used
either because the previous instance of
AWSFAB047E An inconsistent parameter has been Tivoli Workload Scheduler has not yet
used. When the parameter "-cputype been modified or because the new
agent_type" is specified, the <cpuname> installation has completed successfully.
provided with the "-thiscpu " and the
"-master " parameters must be different. Explanation: The -restore parameter is only used to
restore a backed-up version of a previous instance of
Explanation: See message text. Tivoli Workload Scheduler where an upgrade or
System action: The twsinst script cannot proceed. promotion has failed, and you want to return to that
previous instance.
script by referring to “Installing non-integratable agents System action: The twsinst script cannot proceed.
using twsinst” on page 48, or use the command twsinst Operator response: Check the usage of the twsinst
-u to the see a list of the available parameters. script by referring to“Installing non-integratable agents
Rerun the twsinst script, supplying the correct using twsinst” on page 48, or use the command twsinst
parameter. -u to the see a list of the available parameters.
parameter.

TWSHome. Resolve any problem you find and rerun

AWSFAB095E A parameter is missing. Rerun the
the script.
installation script, adding the following
parameter: "parameter_name".
AWSFAB101E The script was unable to copy the file
"maestro.tar.z" to the Tivoli Workload
System action: The twsinst script cannot proceed. Scheduler home directory (TWSHome).
Operator response: Check the usage of the twsinst Explanation: See message text.
-u to the see a list of the available parameters. Operator response: Check that there is sufficient space
available on the file system of the Tivoli Workload
Rerun the twsinst script, adding the missing parameter.
Scheduler home directory (TWSHome). Check that the
user performing the installation has write access to
AWSFAB098E The values specified for "-master" and TWSHome. Resolve any problem you find and rerun
"-thiscpu" cannot be the same. the script.
Explanation: If you are trying to install a master
domain manager you do not supply the "-master" AWSFAB102E The script was unable to expand the
parameter. If you are trying to install a different type of file "maestro.tar.gz" in the Tivoli
agent, the "-thiscpu" parameter must identify the Workload Scheduler home directory
computer where you are installing the agent, and the (TWSHome).
"-master" parameter must identify the workstation that
is its master domain manager.
Operator response: Check that there is sufficient space
supplying different values for the "-master" and
Scheduler home directory (TWSHome). Resolve any
"-thiscpu" parameters.
problem you find and rerun the script.
AWSFAB099E You have identified an instance of

AWSFAB103E The script was unable to expand the
Tivoli Workload Scheduler that is a
file "maestro.tar.z" in the Tivoli
master domain manager or backup
Workload Scheduler home directory
master domain manager. These cannot
(TWSHome).
be upgraded by twsinst.
Explanation: The twsinst installer can only upgrade
the following: System action: The twsinst script cannot proceed.
v A standard agent to a fault-tolerant agent. Operator response: Check that there is sufficient space
v A fault-tolerant agent to a fault-tolerant agent available on the file system of the Tivoli Workload
v A fault-tolerant agent to a domain manager or Scheduler home directory (TWSHome). Resolve any
backup domain manager problem you find and rerun the script.
v A domain manager or backup domain manager to a
domain manager or backup domain manager AWSFAB104E The script was unable to untar the file
"maestro.tar.gz" in the Tivoli Workload
Scheduler home directory (TWSHome).
Operator response: Rerun the twsinst script, choosing
one of the upgrade solutions listed above.
AWSFAB100E The script was unable to copy the file Operator response: Check that there is sufficient space
"maestro.tar.gz" to the Tivoli Workload available on the file system of the Tivoli Workload
Scheduler home directory (TWSHome). Scheduler home directory (TWSHome). Resolve any
Scheduler home directory (TWSHome). Check that the
user performing the installation has write access to

instance of Tivoli Workload Scheduler, version 8.4, on

AWSFAB105E The script was unable to untar the file
the same workstation.
"maestro.tar.z" in the Tivoli Workload
Scheduler home directory (TWSHome). System action: The twsinst script cannot proceed.
Explanation: See message text. Operator response: Firstly, check that the TWSUser
has been typed correctly. If it is not, retry the
command.
Check if you are performing the upgrade on the correct
computer. If you are not, retry the upgrade from the
Scheduler home directory (TWSHome). Resolve any
correct computer.
If the supplied TWSUser is the one you intended, on
the correct computer, you must be in one of the
AWSFAB106E An incorrect value has been supplied
following scenarios:
for the parameter "-thiscpu".
You are trying to upgrade an instance of Tivoli
Workload Scheduler that has already been upgraded
System action: The twsinst script cannot proceed. to version 8.4
Operator response: Rerun the twsinst script, Verify if this has happened as follows:
supplying a correct value for the "-thiscpu" parameter. 1. Check the instance of Tivoli Workload
See also: “Installing non-integratable agents using Scheduler, version 8.4 on this computer:
twsinst” on page 48 for full details of the syntax of the a. Go to the <TWSHome> directory
twsinst script. b. Run the environment enabling script
tws_env
AWSFAB107E An incorrect value has been supplied c. Run a command such as conman or
for the parameter "-master". composer to display the product
version.
2. If the version is 8.4 you have already
System action: The twsinst script cannot proceed. upgraded the product and can quit the
Operator response: Rerun the twsinst script, wizard.
supplying a correct value for the "-master" parameter. You want to have two instances of the product, one of
See also: “Installing non-integratable agents using which is upgraded from a previous instance
twsinst” on page 48 for full details of the syntax of the To have two instances of the product on the
twsinst script. same computer you must have them installed
under different TWSUsers. Because you cannot
AWSFAB108E The option "-restore" is not allowed on change the TWSUser ID during an upgrade,
operating system "operating_system". you must do the following:
1. Quit this installation.
Explanation: The -restore operation is not allowed as a
parameter to an installation performed on the indicated 2. Uninstall the other fresh installation that
operating system (for example, IRIX64, OSF1 you made.
DYNIX-ptx). 3. Upgrade the old version of Tivoli
Workload Scheduler
4. Install the other fresh instance using a
Operator response: If you need to restore the original different TWSUser.
installation, uninstall the upgraded installation, and
then perform a manual restore of the backup image Your environment contains traces of a previous
stored in the backup directory: "twsuserdir_BACKUP". installation of Tivoli Workload Scheduler that you
thought had been completely uninstalled.
1. Look in the registry_file for the supplied
AWSFAB109E You are performing an upgrade to TWSUser and determine the installation
version 8.4, but the installation script directory
has found a previous instance of Tivoli
Workload Scheduler, version 8.4 in the 2. Check if there is a valid installation in that
registry file "registry_file", belonging to directory.
the same TWSUser: "TWSUser_name". v If there is a valid installation of version
8.4 that you do not want, uninstall it. If
Explanation: A TWSUuser cannot own more than one it will not uninstall using the uninstaller,

AWSFAF003E • AWSFAF011E
follow the instructions in this manual for 3. Rerun the upgrade.

uninstalling the product manually.
v If there is no installation, remove the
entries in the registry_file relating to
version 8.4.
Installation messages (fix pack) - FAF

This chapter lists error and warning messages that could be generated when using
the script to install a fix pack for the product.
The message component code is FAF.

Rerun the twspatch script, supplying the correct
AWSFAF003E The twspatch script cannot run on this
parameter.
operating system: operating_system.
See also: readme file.
System action: The twspatch script cannot proceed.
AWSFAF008E More than one installation type
Operator response: Check in the readme file supplied parameter has been supplied. Supply
with the fix pack for details of supported platforms. only one of the following: "-install",
"-undo", "-commit", "-remove", "-repair.
See also: readmefile.
AWSFAF004E Only the user "root" can run the System action: The twspatch script cannot proceed.
twspatch script.
Operator response: Check the usage of the twspatch
Explanation: See message text script by referring to the readme file supplied with the
fix pack, or use the command twspatch -u to the see a
list of the available parameters.
Operator response: Login as the "root" user and rerun
the twspatch script.
parameter.
AWSFAF005E No parameters have been specified for
twspatch.
AWSFAF010E An incorrect value has been supplied
Explanation: The twspatch script needs to be supplied
for a parameter. The parameter must be
with at least one parameter.
as follows: "installation_parameter".
Explanation: The parameter you have supplied is
Operator response: Check the usage of the twspatch correct, and is valid for this installation type. However,
script by referring to the readme file supplied with the the value supplied for the parameter is not correct.
list of the available parameters.
Operator response: Check the usage of the twspatch
script by referring to the readme supplied with this fix
parameter.
pack, or use the command twspatch -u to the see a list
See also: readme file. of the available parameters.
AWSFAF007E The supplied installation type parameter value.
parameter is not correct. It must be one
of the following: "-install", "-undo",
"-commit", "-remove", "-repair".
AWSFAF011E The following parameter has been
supplied more than
System action: The twspatch script cannot proceed. once:"installation_parameter".
Operator response: Check the usage of the twspatch Explanation: See message text.
script by referring to the readme file supplied with the
list of the available parameters. Operator response: Check the usage of the twspatch

script by referring to the readme file supplied with this Operator response: Check that the correct account
fix pack, or use the command twspatch -u to the see a name was supplied. If it was not, rerun the twspatch
list of the available parameters. script, supplying the correct account name.
Rerun the twspatch script, supplying the correct If the correct account name was supplied, create the
parameter. account before rerunning the twspatch script.
AWSFAF017E The script was unable to locate the
home directory of the specified user:
AWSFAF012E The twspatch fix pack installation
"user_account".
cannot be used because the Tivoli
Workload Scheduler registry file is Explanation: See message text.
missing.
Explanation: The Tivoli Workload Scheduler registry
Operator response: The script has located an entry for
file contains the relevant information that he fix pack
the user in the Tivoli Workload Scheduler registry, but
installation uses to identify and update the existing
the directory that the entry points to does not contain
instance. Without it, the installation cannot go ahead.
an instance of a previous version of Tivoli Workload
System action: The twspatch script cannot proceed. Scheduler. Check that a previous installation of Tivoli
Workload Scheduler exists in the indicated directory. If
the instance for the supplied user exists, but in a
different directory, modify the entry in the Tivoli
AWSFAF014E The following is not a recognizable Workload Scheduler registry file to identify the correct
installation parameter installation directory and rerun the script. Otherwise,
"installation_parameter". contact IBM Software Support for assistance.

AWSFAF019E The script was unable to determine
System action: The twspatch script cannot proceed. the installation type from the Tivoli
Operator response: Check the usage of the twspatch Workload Scheduler registry file "file".
script by referring to the readme file supplied with the Explanation: See message text.
list of the available parameters. System action: The twspatch script cannot proceed.
Rerun the twspatch script, supplying the correct Operator response: Contact IBM Software Support for
parameter. assistance.
AWSFAF020E The script was unable to find the
configuration file configuration_file of the
AWSFAF015E The "-uname" option is missing. Tivoli Workload Scheduler instance to
Explanation: The indicated parameter is mandatory which you want to apply the fix pack.
for this installation type. Explanation: See message text.
System action: The twspatch script cannot proceed. System action: The twspatch script cannot proceed.
Operator response: Check the usage of the twspatch Operator response: Locate the indicated configuration
script by referring to the readme supplied with this fix file and move it to the correct directory (see the
pack, or use the command twspatch -u to the see a list documentation for the version you are upgrading for
of the available parameters. the exact location of the configuration file). Then rerun
Rerun the twspatch script, supplying the correct the twsinst script.
parameter. If you cannot find the file, contact IBM Software
See also: readme file. Support for assistance.
AWSFAF016E The following user account has been

supplied that does not exist on the local
computer: "user_account". Create the user
account before running twspatch.

AWSFAF021E The script has located an entry for the AWSFAF025E No previous instances of Tivoli
user in the Tivoli Workload Scheduler Workload Scheduler belonging to the
registry, but the directory that the entry supplied user "user" have been detected
points to does not contain an instance of in the Tivoli Workload Scheduler
a previous version of Tivoli Workload registry file "file".
Scheduler. Check that a previous
installation of Tivoli Workload
Scheduler exists in the directory System action: The twspatch script cannot proceed.
"directory". If the instance for the
supplied user exists, but in a different Operator response: Check that the supplied user is
directory, modify the entry in the Tivoli the correct owner of the instance of Tivoli Workload
Workload Scheduler registry file to Scheduler on this computer. If not, resubmit the script
identify the correct installation directory supplying the correct user.
and rerun the script. Otherwise, contact If the correct user has been supplied, contact IBM
IBM Software Support for assistance. Software Support for assistance.
System action: The twspatch script cannot proceed. AWSFAF027E The installation_type fix pack
installation has failed. For more details
Operator response: Check that a previous installation see the log file "file".
of Tivoli Workload Scheduler exists in the indicated
directory. If the instance for the supplied user exists, Explanation: See message text.
but in a different directory, modify the entry in the System action: The twspatch script stops without
Tivoli Workload Scheduler registry file to identify the successfully installing the fix pack.
correct installation directory and rerun the script.
Otherwise, contact IBM Software Support for assistance. Operator response: This message will have been
preceded by other messages explaining the nature of
the failure. Follow the Operator Response of those
AWSFAF022E The script was unable to determine messages to determine the appropriate action.
the installation directory from the Tivoli
Workload Scheduler registry file "file".
AWSFAF028W At least one warning message was
Explanation: See message text. issued during the installation_type fix
System action: The twspatch script cannot proceed. pack installation.
Operator response: The script could not find an entry Explanation: See message text.
for the user in the Tivoli Workload Scheduler registry System action: The twspatch script stops. The fix pack
file. Check that you have entered the user name has been installed, but one or more warnings were
correctly. Check that the supplied user owns a previous issued.
version of Tivoli Workload Scheduler installed in his or
her home directory. Check that the Tivoli Workload Operator response: This message will have been
Scheduler registry file contains an entry for the preceded by the specific warning messages. Follow the
installation directory for this user. If you have Operator Response of those messages to determine the
identified the wrong user, rerun the patch installation. appropriate action.
If the correct user has been identified, and owns an old
instance of Tivoli Workload Scheduler, but the registry AWSFAF030E The twspatch script is being run from
has no entry for that user, you cannot install the patch the wrong directory.
and must contact IBM Software Support.
Explanation: This depends on the type of installation
you are performing:
AWSFAF023E The installed component (workstation
type) "installed_component" in the Tivoli -install or -repair
Workload Scheduler registry file "file" is You might be attempting to install a fix pack
not valid. for Tivoli Workload Scheduler on a UNIX
Explanation: See message text. platform using the twspatch utility copied
from the installation CD to the home directory
System action: The twspatch script cannot proceed. of the TWSuser. This is not allowed.
Operator response: Contact IBM Software Support for You can run twspatch from any of the
assistance. following places:
v The Tivoli Workload Scheduler fix pack CD
v A disk image of the CD

v A copy of the twspatch utility and its Operator response: Run twspatch directly from the
associated files placed in any local directory product CD. If the computer where you are installing
other than the home directory of the the product does not have a CD drive, copy either an
TWSuser. image of the CD or just the platform-specific folder to
the target computer; place them anywhere other then
-undo, -commit, or -repair
the home directory of the "TWSuser".
These installation types must be run from the copy of

the twspatch utility that has been installed for you in AWSFAF039E You are performing an uninstall
the home directory of the TWSuser. operation, but the user name you
specified is not correct for the Tivoli
System action: The twspatch script cannot proceed. Workload Scheduler instance you are
Operator response: Rerun the fix pack installation trying to uninstall.
from a permitted directory. Explanation: The user specified with the "-uname"
option is not the owner of the Tivoli Workload
AWSFAF032E The installation script was not able to Scheduler instance you are trying to uninstall.
locate the file "file" needed set up the System action: The twsinst script cannot proceed.
operation environment
"operation_environment". Operator response: Rerun the twsinst uninstallation
script, ensuring that the supplied user name matches
Explanation: See message text. the instance you have requested to uninstall.
AWSFAF033E The installation script has been run

from the wrong directory. You must run
the script from the following
directory:directory_name.
Explanation: The "-undo", "-commit", or "-repair"
installation types must be run from the copy of the
twspatch utility that has been installed for you in the
home directory of the TWSuser.
Operator response: Rerun the twsinst installation
script from the indicated directory.
AWSFAF034W The "remove" operation has been

completed successfully. The Tivoli
Workload Scheduler instance belonging
to the user "user" is now unusable. You
must recover the previous installation
from backup.
System action: The twspatch script has completed
successfully and has removed the instance of Tivoli
Workload Scheduler.
Operator response: You must now recover the
previous instance of Tivoli Workload Scheduler from
backup.
AWSFAF037E The twspatch script is being run from

the wrong directory.

Message format

Part 3. Tivoli Dynamic Workload Console
This part describes how to plan for the installation and install, configure, and
uninstall Tivoli Dynamic Workload Console. It contains the following chapters:
v Chapter 10, “Preparing,” on page 251
v Chapter 11, “Installing,” on page 257
v Chapter 12, “Configuring,” on page 271
v Chapter 13, “Upgrading,” on page 273
v Chapter 14, “Uninstalling,” on page 277
v Chapter 15, “Troubleshooting the installation and uninstallation,” on page 281
v Chapter 16, “Installation, and uninstallation messages,” on page 289

Chapter 10. Preparing
This chapter gives you an overview of what you need to know to prepare for
installation. It consists of the following sections:
v “Overview of Tivoli Dynamic Workload Console”
v “Installation overview”
v “Installation considerations” on page 252
| Overview of Tivoli Dynamic Workload Console

| The Tivoli Dynamic Workload Console is a Web-based user interface that is used
| with the following set of products:
| v Tivoli Workload Scheduler
| v Tivoli Workload Scheduler for z/OS
| v Tivoli Workload Scheduler for Applications
| v Tivoli Dynamic Workload Broker
| You can access Tivoli Workload Scheduler and Tivoli Dynamic Workload Broker
| environments from any location in your network using one of the supported
| browsers connected to the Tivoli Dynamic Workload Console. Tivoli Dynamic
| Workload Console must be installed on a system that can reach either the Tivoli
| Workload Scheduler or the Tivoli Dynamic Workload Broker nodes using network
| connections.
| Installation overview
| Perform the following steps to prepare, install, and configure Tivoli Dynamic
| Workload Console:
| 1. Check the installation prerequisites to verify that your system is compliant. You
| can find prerequisite information in the Tivoli Dynamic Workload Console
| download documentation.
| 2. Collect the information necessary to fill in the required fields during the
| installation.
| 3. Choose the installation method that best suits your needs as described in
| “Selecting your installation method” on page 13.
| 4. Install Tivoli Dynamic Workload Console by following the instructions
| provided in “Installing Tivoli Dynamic Workload Console” on page 257.
| 5. If you plan to communicate with the Tivoli Workload Scheduler or Tivoli
| Workload Scheduler for z/OS connector Version 8.3 Fix Pack 3, perform the
| post-installation steps as described in “Post-installation steps to connect to
| Tivoli Workload Scheduler Version 8.3 Fix Pack 3” on page 263.
| 6. Log in to Tivoli Dynamic Workload Console as described in “Accessing Tivoli
| Dynamic Workload Console” on page 265.
| 7. In the navigation tree on the left, click one of the following:
| Tivoli Workload Scheduler
| To access the Tivoli Workload Scheduler available functions
| Tivoli Dynamic Workload Broker
| To access the Tivoli Dynamic Workload Broker available functions

Preparing
| 8. To effectively manage the functions available in Tivoli Dynamic Workload

| Console, create engine connections to the Tivoli Workload Scheduler and Tivoli
| Dynamic Workload Broker environments that you want to manage. Without
| defining engine connections you can use only a limited set of Tivoli Dynamic
| Workload Console functions. For more information, refer to “Quick steps to
| define a Tivoli Workload Scheduler engine connection” on page 266 and “Quick
| steps to define a Tivoli Dynamic Workload Broker server connection” on page
| 267.
Installation considerations
Tivoli Dynamic Workload Console is a module of the Integrated Solutions Console
which is installed on WebSphere Application Server. Before you begin an
installation or upgrade, consider the following items that might apply to your
specific environment.
v Only one Tivoli Dynamic Workload Console can be installed on a computer and
can be installed as follows:
– In an existing Tivoli Workload Automation instance where the embedded
WebSphere Application Server is already installed
– In an existing Tivoli Workload Automation instance where the embedded
WebSphere Application Server is not already installed
– In a new Tivoli Workload Automation instance
– Outside any Tivoli Workload Automation instance, using an existing external
instance of WebSphere Application Server
v You cannot install more than one instance of the current version of Tivoli
Dynamic Workload Console on the same workstation. If you attempt to install a
new version of Tivoli Dynamic Workload Console onto a workstation that
already has an upgradeable version on it, you will only be able to upgrade it.
v When you upgrade Tivoli Dynamic Workload Console, it is automatically
upgraded into a new instance of Tivoli Workload Automation.
v If you plan to install the Integrated Solutions Console Advanced Edition on an
external WebSphere Application Server, before starting the installation, make
sure that all servers are stopped except for the server associated to the profile
where you plan to install, which must be active.
v If you plan to install Tivoli Dynamic Workload Console on an external
WebSphere Application Server where the Integrated Solutions Console Advanced
Edition is already installed, make sure that the server associated to the profile
where you plan to install is active before starting the installation. Only profiles
that are created as described and without customization are supported.
v You can install the current version of Tivoli Dynamic Workload Console on a
system where a Tivoli Dynamic Workload Console version 8.3 instance is already
installed. This is because instances of Tivoli Dynamic Workload Console with
different versions have different sets of configuration files.
v By default, Tivoli Workload Scheduler is installed on embedded WebSphere
| Application Server using the server name twaserver<n>. If you plan to install on
an external WebSphere Application Server on a system where Tivoli Workload
Scheduler is installed, before installing Tivoli Dynamic Workload Console, ask
your WebSphere Application Server administrator to create a new profile with a
| server name different from twaserver<n>, and use this profile during the
installation, as explained in “Installing on your existing instance of WebSphere
Application Server” on page 260. This is a sample command to create a new
profile referring to a new server name on WebSphere Application Server:

Preparing
installation_directory/eWAS/bin/manageprofiles.sh -create
-profileName "new_profile"
-hostName "hostname"
-nodeName "node_name"
-cellName "cell_name"
-serverName new_server_name
-adminUserName administrator
-adminPassword administrator_password
-enableAdminSecurity true
-templatePath "installation_directory/eWAS/profileTemplates/default"
v You must restart Tivoli Dynamic Workload Console immediately after the
installation if you plan to connect to Internet Protocol version 6 (IPv6) enabled
engines.
Selecting your installation method

You can install Tivoli Dynamic Workload Console using one of the following
methods:
Launchpad
| You can use the launchpad to guide you through the installation of Tivoli
| Dynamic Workload Console, and the Tivoli Workload Scheduler
| components, from a single interface. For more information about how to
| install using the launchpad, see “Launchpad” on page 13.
Installation wizard
You access the installation wizard by running a setup command and
entering the configuration settings to install and configure your
installation. Using this method you can synchronously monitor the
installation processing and results. For more information, see “Using the
installation wizard” on page 257.
This method of installation uses a Java Virtual Machine, and therefore has
specific system requirements. See Chapter 2, “Prerequisite information,” on
page 13 for details on installation requirements.
Silent mode
You can customize a response file by adding all configuration settings to be
used during installation, and then invoke from the command line the setup
command using the -silent keyword. Using this method you can run the
installation unattended and in the background. For more information, see
“Performing a silent installation” on page 262.
| Instances of Tivoli Workload Automation

| During the installation of Tivoli Dynamic Workload Console you might need to
| decide whether to install into an existing instance of Tivoli Workload Automation
| or whether to create a new instance. For information see, “Installation paths and
| product instances” on page 18.
| If you are installing into an existing instance of Tivoli Workload Automation, you
| can install certain components, depending on the components or products that
| currently exist in that instance. Table 23 describes the actions that you can perform
| in each different scenario.
| Table 23. Installing into an existing instance of Tivoli Workload Automation
| Tivoli Dynamic Workload Console version Upgrade
| 8.4

Installation methods
| Table 23. Installing into an existing instance of Tivoli Workload Automation (continued)
| 8.5 Tivoli Dynamic Workload Console in this
| case.
| Tivoli Workload Scheduler version 8.5 Install Tivoli Dynamic Workload Console on
| master domain manager or backup domain a common embedded WebSphere
| manager Application Server
| Tivoli Workload Scheduler version 8.5 agent Install Tivoli Dynamic Workload Console
| and a common instance of the embedded
| WebSphere Application Server
|
| Note: If you install Tivoli Dynamic Workload Console into an instance of Tivoli
| Workload Automation that contains only an agent (and no connector), you
| are prompted to supply all the Websphere Application Server fields.
| Table 24 describes the actions that you can perform in instances of Tivoli Dynamic
| Workload Console installed outside Tivoli Workload Automation.
| Table 24. Installing into an instance outside Tivoli Workload Automation
| Selected component: You can perform the following:
| Tivoli Dynamic Workload Console version Upgrade
| 8.4 on an existing external WebSphere
| 8.5 on an existing external WebSphere Tivoli Dynamic Workload Console in this
| Application Server case.
| A current version of the command line client Take no action. It is not possible to install
| Tivoli Dynamic Workload Console in this
| case.
|
| Installation media
| Tivoli Dynamic Workload Console is packaged into multiple DVDs, one for each of
| the supported operating systems. Each DVD contains:
| v The installable image
| v The setup file
| v The sample response files
| v The launchpad
| For a complete list of DVDs and supported operating systems, see the Tivoli
| Dynamic Workload Console downloadable documentation.
| Notes:
| 1. If you copy or mount the DVD to a system directory, make sure that the path
| name to that directory does not contain the following unsupported characters: {
| } [ ] < > $ | ? ! # * + " / % ’ or non US-ASCII characters.
| 2. If you plan to install on a Windows system from a mapped remote drive, make
| sure you map the remote folder locally on the system where you want to
| install, and then run the installation using the local path.

Installation media
| 3. If you plan to install on Linux, make sure that the files contained in the
| mounted image have executable permission, and that the SETUP.bin file is not
| located in a path with blanks.
Tivoli Dynamic Workload Broker supported servers

Tivoli Dynamic Workload Console works with Tivoli Dynamic Workload Broker
Version 1.2 servers.
| Installation log files

| The type of log files you find on your system depends on the type of installation
| you performed. This section describes the logs associated with the different
| installations.
| For more information about log files, refer to the Administration Guide.
| InstallShield wizard installation and uninstallation log files

| You can check the following log files for information about the installation. Details
| of the installation process are kept in log files on the local computer in the
| following directories:
| Note: The following values are valid only if you have not changed the default
| value of the TEMP system variable.
| Tivoli Dynamic Workload Console
| Windows: %TEMP%\TWA\tdwc85
| UNIX: /tmp/TWA/tdwc85
| Table 25 lists the InstallShield wizard log files.

| Table 25. Installation log files
| Log file name Content
| tdwcinstall.log Tivoli Dynamic Workload Console installation log file
| tdwcuninstall.log Tivoli Dynamic Workload Console uninstallation log file
| securityConfignnnn.log Tivoli Dynamic Workload Console log file containing details
| about the WebSphere Application Server security
| configuration performed during installation. The numeric
| value nnnn is automatically assigned. Access the
| tdwcinstall.log file to see the filename of the
| securityConfignnnn.log file.
| wsadmin.log Tivoli Dynamic Workload Console log file containing details
| about the interaction of the installation with WebSphere
|
| For multiple installations on the same workstation, the log header and footer
| indicate the user ID (<TWS_user>) for which the installation was performed.
| Note: If you are running a silent installation and the response file you are using
| does not have the correct syntax, the installation fails without producing a
| log.

Installation log files location
| Installation log files for the embedded WebSphere Application

| Server
| The application server installation has no log. However, if you update the
| application server, for example during the application of a Tivoli Workload
| Scheduler fix pack, a log is created which gives information about the update. The
| log can be found in the directory <TWS_home>/eWAS/logs/update, where you will
| find a directory that identifies the fix pack that has been installed, for example:
| 6.0.2-WS-WASEmbeded-AixPPC32-FP0000007.install, which contains a log file called
| /updatelog.txt.
| The log for the startup of the application server can be found at:
| <TWS_home>/eWAS/profiles/twaprofile/logs/startServer.log

|
Chapter 11. Installing

This chapter describes how to install Tivoli Dynamic Workload Console. It is
divided into the following sections:
v “Installing Tivoli Dynamic Workload Console”
v “Post-installation steps to connect to Tivoli Workload Scheduler Version 8.3 Fix
Pack 3” on page 263
v “Accessing Tivoli Dynamic Workload Console” on page 265
v “Starting and stopping Tivoli Dynamic Workload Console” on page 269
Installing Tivoli Dynamic Workload Console

This section explains how to install Tivoli Dynamic Workload Console using the
available installation methods. It is divided into the following topics:
v “Using the launchpad”
v “Using the installation wizard”
v “Performing a silent installation” on page 262
| Using the launchpad

| You can install Tivoli Dynamic Workload Broker by installing and running the
| launchpad. For information, see “Launchpad” on page 13.
| Using the installation wizard

| Follow these steps to install Tivoli Dynamic Workload Console using the
| installation wizard:
| 1. Browse to the setup directory and start the installation by running the setup
| file. The installation wizard first checks if there is enough free space available
| in the Java temporary directory. If not, the installation exits, and you must
| increase the size of the Java temporary directory, as described in the Tivoli
| Workload Scheduler System Requirements Document at http://www.ibm.com/
| support/docview.wss?rs=672&uid=swg24018909, before rerunning the
| installation wizard.
| 2. Select the language to use while installing Tivoli Dynamic Workload Console,
| and click OK.
| 3. In the welcome window click Next to continue with the installation.
| 4. Read and accept the license agreement. Click Next.
| 5. Select an installation location. Click Next.
| 6. Select the WebSphere Application Server instance. Choose between the
| following:
| v If you choose to install on a new instance of the embedded WebSphere
| Application Server or if you choose to install on an existing instance of Tivoli
| Workload Automation that does not contain the embedded WebSphere
| Application Server, perform the steps in “Installing on a new instance of the
| embedded WebSphere Application Server” on page 258.
| v If you choose to install on an existing Tivoli Workload Automation instance
| that does contain the embedded WebSphere Application Server, perform the
| steps in “Installing on an existing instance of the embedded WebSphere
| Application Server” on page 260.

Installing using the graphical wizard
| v If you choose to install on top of your existing instance of WebSphere

| Application Server, perform the steps in “Installing on your existing instance
| of WebSphere Application Server” on page 260. For a list of supported
| WebSphere Application Servers, refer to the Tivoli Workload Scheduler
| System Requirements Document at http://www.ibm.com/support/
| docview.wss?rs=672&uid=swg24018909.
| Installing on a new instance of the embedded WebSphere

| The following applies if you are installing into a new Tivoli Workload Automation
| instance or an existing Tivoli Workload Automation instance where the embedded
| WebSphere Application Server has not yet been installed
| Follow these steps if you selected to install the embedded WebSphere Application
| Server and Tivoli Dynamic Workload Console:
| 1. Choose a new path to install into or choose the path of the existing Tivoli
| Workload Automation instance. Choose the path where you want to install,
| from now on referred to as twa_install_dir, or accept the default path, and click
| Next.
| Make sure that the installation path is 32 characters or less in length and that it
| does not contain special characters.
| 2. In the installation choice window, select an installation procedure.
| Default Installation
| If you want to use the default WebSphere Application Server settings,
| proceed with the installation as described in “Default installation.”
| Advanced Installation
| If you want to customize the WebSphere Application Server settings,
| proceed with the installation as described in “Advanced installation”
| on page 259.
| Default installation: Follow these steps to proceed with a default installation:

| 1. Specify the user name and password of the embedded WebSphere Application
| Server user that you want to use as the Tivoli Dynamic Workload Console
| administrator. By default the User Name is wasadmin. Note that the user name
| and password must be operating systems credentials. If the user name and
| password you specify do not exist, a new operating system user will be
| created.
| The User Name must be unique, 3 to 60 characters in length, and contain only
| the characters a-z, A-Z, 0-9, period (.), hyphen (-), underscore (_), and
| double-byte character set (DBCS) characters.
| The password must be 5 to 16 characters in length and contain only the
| characters a-z, A-Z, 0-9, period (.), hyphen (-), and underscore (_).
| Confirm the password and click Next.
| 2. Select an option so that the administrator can access the Tivoli Workload
| Scheduler console, the Tivoli Dynamic Workload Broker console, or both, and
| click Next.
| Note: If you select only one of the two available user interfaces, after installing,
| you can authorize the user to access the other one by assigning one of
| the predefined roles created by the installation process. For more
| information, refer to “Quick steps to define a Tivoli Workload Scheduler
| engine connection” on page 266.

Default installation
| 3. To start the installation, check that the values displayed in the installation
| summary window are correct and click Install.
| 4. When the installation completes successfully, a window opens showing links to
| the user interface on the Integrated Solutions Console portal. For more
| information, refer to “Accessing Tivoli Dynamic Workload Console” on page
| 265. If the installation fails, the window contains the list of the items that were
| not installed and the location of the log file. Click Finish.
| Advanced installation: Perform the following steps to proceed with an advanced

| installation:
| 1. Specify the following port numbers for the embedded WebSphere Application
| Server or accept the default values.
| HTTP transport
| The number of the port that the embedded WebSphere Application
| Server uses for HTTP transport.
| Administrative console
| The HTTP Administrative Console port on the embedded WebSphere
| Application Server .
| HTTPS transport
| The number of the port that the embedded WebSphere Application
| Server uses for secure HTTP transport (HTTPS).
| Administrative Console Secure
| The HTTP Administrative Console secure port on the embedded
| WebSphere Application Server .
| Bootstrap
| The port number for the bootstrap function.
| SOAP connector
| The port number for the Simple Object Access Protocol (SOAP)
| connector on the embedded WebSphere Application Server.
| ORB Listener
| The ORB Listener Port number on the embedded WebSphere
| Application Server.
| SAS SSLPort
| The SAS SSL ServerAuth Listener Port number on the embedded
| The CSIV2 SSL ServerAuth Listener port number on the embedded
| The CSIV2 SSL ClientAuth Listener port number on the embedded
| High Availability Manager Communication
| The High Availability Manager Communication port number for the
| embedded WebSphere Application Server.
| Service Integration
| The Service Integration Port number for the embedded WebSphere

Advanced installation
| Service Integration Secure

| The Service Integration Secure Port number for the embedded
| MQ Transport
| The MQ Transport Port number for the embedded WebSphere
| MQ Transport Secure
| The MQ Transport Secure Port number for the embedded WebSphere
| SIP Container
| The Session Initiation Protocol (SIP) Port number for the embedded
| SIP Container Secure
| The Session Initiation Protocol (SIP) Secure Port number for the
| embedded WebSphere Application Server.
| Click Next.
| 2. Complete the installation by following the steps described in “Default
| installation” on page 258.
| Installing on an existing instance of the embedded WebSphere

| Follow these steps to install Tivoli Dynamic Workload Console on an existing
| instance of the embedded WebSphere Application Server:
| 1. Select the existing Tivoli Workload Automation directory.
| 2. Supply the credentials of the existing instance of the embedded WebSphere
| Note: If you already installed WebSphere Application Server into your existing
| Tivoli Workload Automation instance but do not know the username,
| click Retrieve. The username will be retrieved but you still must provide
| the password. This operation may take a few minutes.
| 3. Select if you want the administrator to access the Tivoli Workload Scheduler
| console, the Tivoli Dynamic Workload Broker console, or both. Click Next.
| Note: If you select one of the two available user interfaces, after installing you
| can authorize the user to access the other user interface by assigning him
| one of the predefined roles created by the installation process. For more
| information, refer to the information about configuring the Tivoli
| Dynamic Workload Console in the Tivoli Workload Scheduler:
| 265. If the installation fails, the window contains a list of the items that were
| Installing on your existing instance of WebSphere Application

| Server
| Follow these steps to install Tivoli Dynamic Workload Console on top of an
| existing WebSphere Application Server instance:

Installing on an existingWebSphere Application Server
| 1. Select the existing WebSphere Application Server instance where you want to
| install Tivoli Dynamic Workload Console by specifying the following values
| (obtain this information from your WebSphere Application Server
| administrator):
| Profile Name
| The name of the WebSphere Application Server profile defining the
| Tivoli Dynamic Workload Console runtime environment. Make sure the
| profile you select has:
| v The administrative console installed. You can also install it after
| creating the profile.
| v The administrative security enabled.
| Server Name
| The name of the server specified in the profile to be used by Tivoli
| Note: WebSphere Application Server requires that the host name and
| server name pair used in a clustered environment must be
| unique. Because twaserver<n> is the hardcoded server name used
| by Tivoli Workload Scheduler, specify a different server name if
| you install Tivoli Dynamic Workload Console on the same
| system where the Tivoli Workload Scheduler connector is
| installed.
| Cell Name
| The name of the group of one or more nodes in an embedded
| WebSphere Application Server distributed network that the node
| belongs to.
| Node Name
| The unique embedded WebSphere Application Server name that
| identifies the system where you want to install.
| 2. Locate the path where the UpdateInstaller wizard is stored. This is a wizard
| invoked by the embedded WebSphere Application Server to install updates.
| 3. Specify the user ID and password of an existing embedded WebSphere
| Application Server user that you want to set as the Tivoli Dynamic Workload
| Console administrator. By default the user ID is wasadmin.
| 4. Select if you want the administrator to access the Tivoli Workload Scheduler
| console, the Tivoli Dynamic Workload Broker console, or both. Click Next.
| Note: If you select one of the two available user interfaces, after installing you
| can authorize the user to access the other user interface by assigning him
| one of the predefined roles created by the installation process. For more
| information, refer to the information about configuring the Tivoli
| Dynamic Workload Console in the Tivoli Workload Scheduler:
| 265. If the installation fails, the window contains a list of the items that were

Installing in silent mode
Performing a silent installation

You can run the installation in unattended mode from the command line by
adding the -silent parameter when running the setup installation file. Perform the
following steps:
v Run the installation as root on UNIX operating systems, or as Administrator on
Windows operating systems.
v Specify all the settings that are prompted when installing using the installation
wizard.
The installation settings are provided using a response file.
| Edit the response file templates provided on the installation DVDs in the
| \tdwc\responsefiles\ directory. Instructions for customizing the files are included
| in the files as commented text. For details about response file properties, see
| Appendix B, “Response file properties,” on page 311.
Table 26 lists the response files and the types of installation each performs by
operating system:
| Table 26. Tivoli Dynamic Workload Console response files
| Installing on UNIX
| Fresh Tivoli Dynamic Workload Console TDWC85_FRESH_existTWA_UNIX.txt
| Fresh Tivoli Dynamic Workload Console TDWC85_FRESH_extWAS_UNIX.txt
| on existing WebSphere Application
| Server
| Fresh Tivoli Dynamic Workload Console TDWC85_FRESH_newTWA_UNIX.txt
| on a new TWA instance
| Uninstall Tivoli Dynamic Workload TDWC85_UNINSTALL.txt
| Console
| Upgrade Tivoli Dynamic Workload TDWC85_UPGRADE_embeddedWAS_UNIX.txt
| Console on embedded WebSphere
| Upgrade Tivoli Dynamic Workload TDWC85_UPGRADE_extWAS_UNIX.txt
| Console on an external Websphere
| Fresh Tivoli Dynamic Workload Console TDWC85_FRESH_existTWA_WIN.txt
| Fresh Tivoli Dynamic Workload Console TDWC85_FRESH_extWAS_WIN.txt
| on existing WebSphere Application
| Server
| Fresh Tivoli Dynamic Workload Console TDWC85_FRESH_newTWA_WIN.txt
| on a new TWA instance
| Uninstall Tivoli Dynamic Workload TDWC85_UNINSTALL.txt
| Console
| Upgrade Tivoli Dynamic Workload TDWC85_UPGRADE_embeddedWAS_WIN.txt
| Console on embedded WebSphere

Installing in silent mode
| Table 26. Tivoli Dynamic Workload Console response files (continued)

| Upgrade Tivoli Dynamic Workload TDWC85_UPGRADE_extWAS_WIN.txt
| Console on an external Websphere
|
| Note: In the upgrade scenarios, choose the WebSphere Application Server type
| (embedded or external) that you originally chose when you installed Tivoli
| Dynamic Workload Console version 8.4.
To install in silent mode, perform these steps on the computer on which you want
to install Tivoli Dynamic Workload Console:
1. Copy the sample response file for that operating system to a local temporary
directory .
2. Customize the options contained in the response file to suit your requirements
and environment. For information about the available options, refer to
Appendix B, “Response file properties,” on page 311.
3. Run the following command:
Windows:
SETUP.exe -silent -options response_file_name
UNIX:
./SETUP.bin -silent -options response_file_name
where response_file_name is the full path name.

4. Check the result of the silent installation as follows:
Windows:
The installation command is asynchronous, meaning that when it is
issued it starts an installation procedure and then ends without
returning any value or message. To know whether or not the silent
installation ran successfully, refer to the installation result reported in
the tdwcinstall.log installation log file stored in the temporary
directory.
UNIX: The installation command is synchronous and it returns 0 if the
installation ran successfully, or a nonzero value if the installation failed.
Note: For information about the installation result, see the tdwcinstall.log
installation log file stored in the temporary directory.
Post-installation steps to connect to Tivoli Workload Scheduler

Version 8.3 Fix Pack 3
To access a Tivoli Workload Scheduler Version 8.3 Fix Pack 3 environment, you
must enable Tivoli Workload Scheduler to work with Tivoli Dynamic Workload
Console.
Notes:
1. These steps are not necessary to connect to a Tivoli Workload Scheduler Version
8.4 environment.
2. If you plan to communicate from the Tivoli Dynamic Workload Console version
8.4 or higher to Tivoli Workload Scheduler, Version 8.3 Fix Pack 3, make sure

Post-installation steps to connect to Tivoli Workload Scheduler 8.3 Fix Pack 3
that the APAR PK47309 is installed on top of the Tivoli Workload Scheduler
engine. For more information, contact IBM Software Support.
3. Before proceeding, it is recommended that you run the backupConfig.sh or
backupConfig.cmd script to backup the Tivoli Workload Scheduler configuration.
For information about how to run these scripts, see Tivoli Workload Scheduler:
Administration Guide.
This task must be run on the system where the Tivoli Workload Scheduler engine
that you want to connect to is installed:
Tivoli Workload Scheduler distributed environment
v On the master domain manager.
v On a full status fault-tolerant agents (FTA) workstation where the Tivoli
Workload Scheduler connector is installed.
Tivoli Workload Scheduler z/OS environment
On the distributed system where the Tivoli Workload Scheduler z/OS
connector is installed.
Perform the following steps:

1. Make sure that the WebSphere Application Server is started on the Tivoli
Workload Scheduler workstation and then run the following script:
On Windows:
As Administrator, from the directory TWS_home\wastools:
webui -operation enable -user TWS_user -password TWS_user_pw
-port TWS_port [-server TWS_server]
On UNIX
As root, from the directory TWS_home/wastools:
./webui.sh -operation enable -user TWS_user -password TWS_user_pw
-port TWS_port [-server TWS_server]
where:
TWS_user The Tivoli Workload Scheduler administrator user ID.
TWS_user_pw The Tivoli Workload Scheduler administrator password.
TWS_port The SOAP port of the embedded WebSphere Application Server
the Tivoli Workload Scheduler is installed on. This is a
mandatory setting when using the enable flag. Its default
values are 31118 for distributed environments, and 31128 for
z/OS environments.
TWS_server The name of the server specified in the embedded WebSphere
Application Server profile used by Tivoli Workload Scheduler.
By default the value assigned to this field is server1.
2. Stop and start the embedded WebSphere Application Server on the Tivoli
Workload Scheduler system where you run the script.
When you have completed these steps, you are ready to create engine connections
for the Tivoli Workload Scheduler workstation and to manage your Tivoli
Workload Scheduler production environment. For information about how to
accomplish these tasks, access Tivoli Dynamic Workload Console online general
help.

Accessing Tivoli Dynamic Workload Console

When the installation completes successfully, a message with links to Integrated
Solutions Console portal is displayed. If you used the silent installation, this
information is stored in the tdwcinstall.log installation log file. For more details
about where to find the installation logs, see “InstallShield wizard installation and
uninstallation log files” on page 255.
From a supported browser, access one of the following links provided by the
installation program:
http://tdwc_system:http_port/ibm/console
https://tdwc_system:https_port/ibm/console
where:
tdwc_system
is the hostname or IP address of the system where you installed Tivoli
Dynamic Workload Console.
http_port
| is the port number used to access Tivoli Dynamic Workload Console using
| an unsecure connection over HTTP. The default value for this port number
| is 29060 if you are installing Tivoli Dynamic Workload Console as a new
| Tivoli Workload Automation instance. If you install Tivoli Dynamic
| Workload Console into an existing Tivoli Workload Automation instance,
| the value for this port is inherited. If the existing Tivoli Workload
| Automation instance contains the current version of Tivoli Workload
| Scheduler using default ports, the value is 31123.
https_port
| is the port number used to access Tivoli Dynamic Workload Console using
| a secure connection over HTTPS. The default value for this port number is
| 29043 if you are installing Tivoli Dynamic Workload Console as a new
| Tivoli Workload Automation instance. If you install Tivoli Dynamic
| Workload Console into an existing Tivoli Workload Automation instance,
| the value for this port is inherited. If the existing Tivoli Workload
| Automation instance contains the current version of Tivoli Workload
| Scheduler using default ports, the value is 31124.
| When connecting to the Integrated Solutions Console using an HTTPS
| connection, if you receive a security alert, proceed with the Tivoli Dynamic
| Workload Console working session. If you receive security information
| windows while navigating through the Integrated Solutions Console,
| choose to display nonsecure items to proceed. If you are using Internet
| Explorer, you can prevent these windows from opening by setting Display
| mixed content to Enable in the Security settings.
In the Integrated Solutions Console login portlet, enter the user ID and password
you specified during the installation, and click Log in.
On the navigation bar on the left, expand the Tivoli Workload Scheduler entry to
access Tivoli Dynamic Workload Console and then Tivoli Workload Scheduler
environments (such as Tivoli Workload Scheduler, Tivoli Workload Scheduler for
z/OS, and Tivoli Workload Scheduler for Applications). Expand the Tivoli
Dynamic Workload Broker entry to access Tivoli Dynamic Workload Broker
environments.

To effectively use the functions of these two products, you must define connections
to the Tivoli Workload Scheduler engines and the Tivoli Dynamic Workload Broker
servers.
Without defining engine connections, you can perform only this limited set of
operations:
On Tivoli Workload Scheduler
Creating browse tasks for
Creating report tasks
Creating event management tasks
Defining user preferences
On Tivoli Dynamic Workload Broker
Defining user preferences
If the user ID you used to connect to Tivoli Dynamic Workload Console has
assigned a role different from TWSWEBUIAdministrator and
TDWBAdministrator, you will see a subset of the available panels. This subset
depends on the authorizations assigned to the role associated to your user ID. For
more information about roles, refer to the information about configuring the Tivoli
Dynamic Workload Console in the Tivoli Workload Scheduler: Administration Guide.
If the user ID you used to connect to Tivoli Dynamic Workload Console has no
role assigned, you will not see the entries for Tivoli Workload Scheduler and Tivoli
Dynamic Workload Broker in the Integrated Solutions Console portal navigation
tree.
Quick steps to define a Tivoli Workload Scheduler engine

connection
After logging in to Tivoli Dynamic Workload Console using the administrator
userid or another userid with assigned TWSWEBUIAdministrator or
TWSWEBUIConfigurator roles, follow the steps below to create an engine
connection to one of your supported Tivoli Workload Scheduler engines.
Note: If you installed Tivoli Dynamic Workload Console into a Tivoli Workload
Automation instance that had the embedded WebSphere Application Server
already installed, the connection to the Tivoli Workload Scheduler
component (for example, master domain manager, backup master domain
manager, or connector) is automatically defined with blank credentials. The
connection is shared with all all Tivoli Dynamic Workload Console users
and no further credentials are needed because Single Sign On is
automatically implemented for the component. The same situation applies if
you install a Tivoli Workload Scheduler component into a Tivoli Workload
Automation instance where the Tivoli Dynamic Workload Console and the
embedded WebSphere Application Server is already installed.
1. To expand the tree, click Tivoli Dynamic Workload Console and Tivoli
Workload Scheduler.
2. Select Quick start
3. Click New Engine.
4. In the Engine Connection Properties window, assign a name to the engine
connection and specify:
Engine Type Either z/OS or distributed. This is the type of the Tivoli
Workload Scheduler engine to connect to.

Hostname The hostname or IP address of system where the distributed

engine or the z/OS connector, for z/OS engine types, runs.
PortNumber The bootstrap port number for Tivoli Workload Scheduler
engine. Default values are 31117 for distributed engine, and
31127 for z/OS connector.
Remote Sever Name
This setting is valid and mandatory only for z/OS engines. This
is the name of the remote server of the engine as it is specified
in the z/OS connector.
Userid and Password
The user ID and password that are used to connect to the
engine. This setting allows access to Tivoli Workload Scheduler
from Tivoli Dynamic Workload Console. The authorization
assigned to the user in the Tivoli Workload Scheduler security
file determines the operations allowed.
If you want to test the connection to the Tivoli Workload Scheduler database
(mandatory for managing reporting and event management functions), you
must select Enable reporting and specify the user credentials.
5. Click Test Connection to check that configuration was successful and that
Tivoli Dynamic Workload Console is communicating with the selected engine.
If the test connection fails, refer to Tivoli Workload Scheduler: Troubleshooting
Guide.
Note: Make sure you run “Post-installation steps to connect to Tivoli Workload
Scheduler Version 8.3 Fix Pack 3” on page 263 before testing the engine
connection if you are connecting to a Tivoli Workload Scheduler version
8.3 Fix Pack 3 engine or z/OS connectors.
Quick steps to define a Tivoli Dynamic Workload Broker

server connection
Tivoli Dynamic Workload Console supports a single connection to one Tivoli
Dynamic Workload Broker engine at any given time for each authorized user. A
different connection is supported for each authorized user.
After having logged in to Tivoli Dynamic Workload Console using the

administrator user ID, or another user ID with assigned TDWBAdministrator or
TDWBConfigurator roles, follow these steps to create an engine connection to a
supported Tivoli Dynamic Workload Broker engine:
1. In Tivoli Dynamic Workload Console, click Tivoli Dynamic Workload Broker
to expand the tree.
2. Select Configuration
3. Click Server connection.
4. In the Server Connection specify:
Hostname It is the host name of the Tivoli Dynamic Workload Broker
server you want to connect to.
Non secure port
It is the non-secure port to be used for connection.
Secure port It is the secure port to be used for connection.

Use Secure Connection

Specify whether a secure connection must be used. For more
information about security, refer to IBM Tivoli Dynamic Workload
Broker: Installation and Configuration Guide.
Username Optionally specify a different user for the server connection.
The connection to the new server is enabled using the
credentials of the user you specified. Each user has access only
one server connection.
Password Specify the password for the authenticated user the connection
applies to.
5. Click OK to save your changes. The server connection you specified is enabled
and is immediately effective.

| Starting and stopping Tivoli Dynamic Workload Console

| To start and stop Tivoli Dynamic Workload Console or an engine, you must start
| and stop the application server instance that they are installed on.
| embedded WebSphere Application Server
| If you installed Tivoli Dynamic Workload Console on the embedded WebSphere

| Application Server, you can start and stop the server as follows:
| Windows
| To stop: install_dir\wastools\stopWas.bat
| To start: install_dir\wastools\start\Was.bat
| UNIX To stop: install_dir/wastools/stopWas.sh
| To start: install_dir/wastools/startWas.sh
| External instance of WebSphere Application Server
| If you are using an external instance of WebSphere Application Server, use the
| following WebSphere Application Server scripts to start and stop an application
| server instance.
| Note: These scripts can also be used to start and stop embedded WebSphere
| Application Server, although, in this case, it is suggested that you use the
| method described above.
| Windows
| ewas_install_dir\bin\stopServer.bat app_server
| -user user_id -password user_id_pw
|
| ewas_install_dir\bin\startServer.bat app_server
| UNIX ewas_install_dir/bin/stopServer.sh app_server
| -user user_id -password user_id_pw
|
| /ewas_install_dir/bin/startServer.sh app_server
| where:
| was_install_dir
| Is the directory where the embedded WebSphere Application Server is
| installed.
| app_server
| Is the server name specified in the WebSphere Application Server profile
| related to Tivoli Dynamic Workload Console or to the engine.
| user_id
| Is the administrator user ID specified when installing Tivoli Dynamic
| Workload Console or the engine.
| user_id_pw
| Is the administrator user ID password specified when installing Tivoli
| Dynamic Workload Console or the engine.


|
| Chapter 12. Configuring

| You can perform the following optional configuration steps at any time after the
| installation.
| v Configuring new users to access Tivoli Dynamic Workload Console
| v Configuring Tivoli Dynamic Workload Console to use a user registry
| v Configuring Tivoli Dynamic Workload Console to use Single Sign-On
| v Securing your communication using Secure Socket Layer protocol
| Note: If, after installing, you have more than one instance of WebSphere
| Application Server managing any Tivoli Workload Automation products,
| you must ensure that they have the same LTPA token_keys.
| For information about configuration, see the Administration Guide.

|
| Chapter 13. Upgrading

| This chapter describes how to upgrade Tivoli Dynamic Workload Console to the
| current version. The upgrade procedure varies depending on if you have installed
| Tivoli Dynamic Workload Console version 8.4 on the embedded WebSphere
| Application Server or an external instance of WebSphere Application Server. The
| chapter is divided into the following sections:
| v “Upgrading with an embedded WebSphere Application Server”
| v “Upgrading with an external instance of WebSphere Application Server” on page
| 275
|
| Upgrading with an embedded WebSphere Application Server
| This section describes the new upgrade directory structure and how to upgrade
| Tivoli Dynamic Workload Console on an embedded WebSphere Application Server.

| Program directory
| When you upgrade Tivoli Dynamic Workload Console to the current version, a
| new program directory structure is created. During the upgrade process,
| components of Tivoli Dynamic Workload Console are moved from the old
| directory structure and then updated into the new directory structure. The Tivoli
| Dynamic Workload Console program files remain in the original installation
| directory.
| processes) existing in your Tivoli Dynamic Workload Console structure, you must
| update them so that they work in the new directory structure.
| For example, if you originally installed Tivoli Dynamic Workload Console into the
| directory c:\Program Files\ibm\tdwc\, you have a directory structure as follows:
| c:\Program Files\IBM\tdwc\AppServer
| c:\Program Files\IBM\tdwc\wastools
| c:\Program Files\IBM\tdwc\_tdwcutils
| c:\Program Files\IBM\tdwc\_tdwcuninst
| c:\Program Files\IBM\tdwc\_jvm
| When you upgrade Tivoli Dynamic Workload Console, the new directory structure
| is:
| :\Program Files\IBM\tdwc\eWAS
| c:\Program Files\IBM\tdwc\wastools
| c:\Program Files\IBM\tdwc\TDWC
| c:\Program Files\IBM\tdwc\_tdwcuninst
| c:\Program Files\IBM\tdwc\_jvm
| The new directory structure includes new WebSphere Application Server tools that
| are common to Tivoli Workload Scheduler. For more information about installation
| paths, see “Installation paths and product instances” on page 18.

Upgrading Tivoli Dynamic Workload Console

| The following describes the old and new directory structures.
| Note: Before upgrading you must backup any customized SSL keys and copy
| them to the default installation path.
| After upgrading, the old SSL files stored in PCKS12 format are imported into new
| SSL files in JKS format.
| Note that the old PCKS12 files are also copied to the new directory as a backup.
| The key.p12 file becomes TWSServerKeyFile.jks. The trust.p12 files becomes
| v TWSInstallationPath\AppServer\profiles\tdwcprofile\config\cells\
| CellName\nodes\NodeName\key.p12
| v TWSInstallationPath\AppServer\profiles\tdwcprofile\config\cells\
| CellName\nodes\NodeName\trust.p12
| v TWSInstallationPath\eWAS\profiles\twaprofile\config\cells\
| DefaultNode\nodes\DefaultNode\key.p12
| v TWSInstallationPath\eWAS\profiles\twaprofile\config\cells\
| DefaultNode\nodes\DefaultNode\trust.p12
| Note: The files key.p12 and trust.p12 will not be used by Tivoli Dynamic
| Workload Console, but will be backed up.
| Upgrading using the installation wizard

| To upgrade using the installation wizard, run the setup for the operating system
| on which you are installing:
| v On Windows: WINDOWS\SETUP.exe
| v Alternatively, start the launchpad as described in “Launchpad” on page 13 and
| select the Tivoli Dynamic Workload Console installation.
| Follow the installation panels to complete the upgrade. The following list describes
| the fields you provide during the upgrade.
| Use an existing instance of Tivoli Dynamic Workload Console
| When you are prompted that a previous version of Tivoli Dynamic
| Workload Console has been found, select Use an existing instance. From
| the drop-down list, choose the instance that you will upgrade.
| Administrative credentials of application server
| Enter the WebSphere Application Server user name and password.
| Backup directory
| Choose a backup directory. This directory contains only configuration

| information and other program-related objects and not WebSphere

| Application Server files. Note that this directory remains on your computer
| even after the upgrade is complete.
| Notes:
| 1. For information about installing into specific environments, see “Instances of
| Tivoli Workload Automation” on page 253.
| 2. During an upgrade on Windows, the WebSphere Application Server Windows
| Service account name in the local OS user registry is changed to the
| administrator user name of the Integrated Solutions Console. If you use a
| custom registry or LDAP registry, the service is upgraded to the installation
| user.
| 3. It is not necessary to manually stop the WebSphere Application Server prior to
| upgrading. During the upgrade procedure, WebSphere Application Server is
| stopped automatically.
|
| Upgrading with an external instance of WebSphere Application Server
| This section describes the upgrade how to upgrade Tivoli Dynamic Workload
| Console on an existing external instance of the WebSphere Application Server.
| Upgrading using the installation wizard

| To upgrade using the installation wizard, run the setup for the operating system
| on which you are installing:
| v On Windows: WINDOWS\SETUP.exe
| v Alternatively, start the launchpad as described in “Launchpad” on page 13 and
| select the Tivoli Dynamic Workload Console installation.
| Follow the installation panels to complete the upgrade. The following list describes
| the fields you provide during the upgrade.
| Use an existing instance of Tivoli Dynamic Workload Console
| When you are prompted that a previous version of Tivoli Dynamic
| Workload Console has been found, select Use an existing instance. From
| the drop-down list, choose the instance that you will upgrade.
| Administrative credentials of application server
| Enter the WebSphere Application Server user name and password.
| Backup directory
| Choose a backup directory. This directory contains only configuration
| information and other program-related objects and not WebSphere
| Application Server files. Note that this directory remains on your computer
| even after the upgrade is complete.
| Notes:
| 1. For information about installing into specific environments, see “Instances of
| Tivoli Workload Automation” on page 253.
| 2. During an upgrade on Windows, the WebSphere Application Server Windows
| Service account name in the local OS user registry is changed to the
| administrator user name of the Integrated Solutions Console. If you use a
| custom registry or LDAP registry, the service is upgraded to the installation
| user.

| 3. It is not necessary to manually stop the WebSphere Application Server prior to

| upgrading. During the upgrade procedure, WebSphere Application Server is
| stopped automatically.

Chapter 14. Uninstalling
This chapter describes how to uninstall Tivoli Dynamic Workload Console. It is
divided into the following sections:
v “Uninstalling using the wizard”
v “Uninstalling in silent mode” on page 279

Perform the following steps to uninstall Tivoli Dynamic Workload Console using
the wizard:
1. Start the server.
2. Start the uninstall as follows:
On Windows:
Perform one of the following:
v From the <TWA_HOME>\TDWC directory, run the command:
uninstall.bat
v From the Control Panel, click Add/Remove Programs. Scroll down
the list of software, and select Tivoli Dynamic Workload Console.
Click Change/Remove.
On UNIX:
From the <TWA_HOME>\TDWC directory, run the command:
uninstall.sh
3. Select the language.
4. Click Next in the Tivoli Dynamic Workload Console uninstall welcome
window.
5. Provide the administrator user name and password you specified during the
Tivoli Dynamic Workload Console installation, and click Next.
6. In the uninstall summary window, check that the directory from where the
product is to be removed and the features to be removed are correct, and then
click Uninstall. If you installed Tivoli Dynamic Workload Console and the
embedded WebSphere Application Server, they are both uninstalled; if you
installed Tivoli Dynamic Workload Console on an external WebSphere
Application Server only the Tivoli Dynamic Workload Console module is
uninstalled.
Note: When uninstalling Tivoli Dynamic Workload Console installed on an

external WebSphere Application Server, the Integrated Solutions Console
Advanced Edition version 7.1 is not removed even though the window
says it is. This is a WebSphere Application Server limitation.
7. When the uninstall completes, a window showing a message about the success
of the operation is displayed. Click Finish to exit the InstallShield Wizard.
Note: On Windows operating systems, as a last step to uninstall, manually remove

the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
Services\IBMWAS61Service - <USERNAME>

Uninstalling Tivoli Dynamic Workload Console
This note applies only when removing Tivoli Dynamic Workload Console
version 8.4 that was generally available on September 2007.

Uninstalling in silent mode

You can perform a silent uninstall of Tivoli Dynamic Workload Console.
Before starting to uninstall ensure that the server is active, and move to a directory
different from the tdwc_install_dir.
Run the uninstall command as follows:

On Windows:
tdwc_install_dir\_tdwcuninst\uninstaller -silent -options
response_file.rsp
On UNIX:
tdwc_install_dir/_tdwcuninst/uninstaller.bin -silent -options
response_file.rsp
Note:
1. On Windows operating systems, as a last step when uninstalling,
manually remove the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
Services\IBMWAS61Service - TDWC
2. On Solaris operating systems, after having uninstalled the product, if
you plan to install it again, it is recommended that you delete the TDWC
directory under /root_dir/InstallShield/Universal.
Chapter 14. Uninstalling 279


Chapter 15. Troubleshooting the installation and uninstallation
This chapter describes how to troubleshoot the installation and uninstallation of
the Tivoli Dynamic Workload Console. It is divided into the following sections:
v “Installation and uninstallation log and trace files”
v “Recovering a failed InstallShield wizard installation”
v “Recovering a failed upgrade”
v “Uninstalling Tivoli Dynamic Workload Console and the embedded WebSphere
Application Server manually” on page 282
v “Troubleshooting scenarios” on page 283
| Note: Refer to the section “Uninstalling Tivoli Dynamic Workload Console and the
| embedded WebSphere Application Server manually” on page 282 to
| manually uninstall or recover from a failed installation.
Installation and uninstallation log and trace files

For information on installation log files, see “Installation log files” on page 255.
Recovering a failed InstallShield wizard installation

The recovery of a failed installation of Tivoli Dynamic Workload Console is
structurally very similar to that described in “Recovering a failed interactive
InstallShield wizard installation” on page 125 and “Recovering a failed silent
InstallShield wizard installation” on page 135 for Tivoli Workload Scheduler.
However, there are some significant differences, which are described in this section.
If the installation fails, follow the instructions in “Correcting a failed step and
continuing the installation” on page 131 up to the point where you want to modify
the values of a step, and then follow these instructions:
1. The values used in each step for the Tivoli Dynamic Workload Console are all
stored in one place - Step 0. So if you discover, for example, that the step that
configures the embedded WebSphere Application Server has failed because a
port is in use, you must go to Step 0 and modify the value for the port in that
step.
2. Set the status of Step 0, plus the status of the step that failed, to Ready.
3. In all cases, run Step 0 in the Step List, using the Run next option. Step 0 uses
the original data, as modified by you, to regenerate all of the scripts that run
the steps.
4. Resume the wizard from the failed step, either running Run all to complete the
installation in one go, or Run next, step by step.
Note: You cannot rerun any step that has completed successfully, other than Step 0.
Recovering a failed upgrade

In the case of a failed upgrade, contact IBM Software Support.

Manually uninstall Tivoli Dynamic Workload Console
| Uninstalling Tivoli Dynamic Workload Console and the embedded

| WebSphere Application Server manually
| Perform the following steps to manually remove an instance of Tivoli Workload
| Automation that contains Tivoli Dynamic Workload Console and uses the
| embedded WebSphere Application Server. In the case of a failed installation, you
| may find some of the steps are unnecessary, depending on when the installation
| failed.
| To remove an instance of Tivoli Workload Automation that contains and integrated

| installation of Tivoli Workload Scheduler and Tivoli Dynamic Workload Console,
| first perform the uninstallation of Tivoli Workload Scheduler as described in
| “Uninstalling Tivoli Workload Scheduler manually” on page 166. Then, to remove
| Tivoli Dynamic Workload Console, perform the following steps:
| v On Windows, perform steps 5 and 6.
| v On UNIX, perform step 4.
| If you want to remove Tivoli Workload Scheduler from an instance of Tivoli

| Workload Automation without removing the Tivoli Workload Automation instance,
| contact IBM Software Support.
| On Windows:
| 1. Stop the server either by running the command:
| install_dir\wastools\stopWas.bat
| 2. If you configured to start and stop the Tivoli Dynamic Workload
| Console as a service, remove the service by running the command:
| cd install_dir\eWAS\AppServer\bin\
| wasservice.exe -remove TDWC_admin_username
| 3. Navigate to the install_dir and take note of the name of the .id file
| twainstancexxx.id. You will need this information later in the procedure.
| 4. Remove the directory:
| install_dir
| C:\Program Files\Common Files\InstallShield\Universal\TDWC
| 6. Delete the following registry key:
| HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
| e625666383dedb70850864e2a6feaa2e1371705039
| 7. Remove the file:
| %ProgramFiles%\TWA\twainstancexxx.properties
| 8. Restart the system.
| On UNIX:
| 1. Stop the server by running the command:
| install_dir/wastools/stopWas.sh
| 2. Navigate to the install_dir and take note of the name of the .id file
| twainstancexxx.id. You will need this information later in the procedure.
| install_dir
| On AIX
| /usr/lib/objrepos/InstallShield/Universal/TDWC

| On all UNIX systems, except AIX

| ROOT_USER_HOME/InstallShield/Universal/TDWC
| 5. Remove the file:
| opt/IBM/TWA/twainstancexxx.properties
|
Troubleshooting scenarios
The troubleshooting scenarios are listed in the following categories:
v “Problems with the launchpad”
v “Problems with the interactive wizard”
v “Problems with the silent installation” on page 286
v “Problems with the uninstallation” on page 287
Problems with the launchpad

The following problems might be encountered while using the launchpad to install
the Tivoli Dynamic Workload Console:
v “Warning messages displayed when using launchpad on Linux”
v “Undefined error when using launchpad on Windows”
Warning messages displayed when using launchpad on Linux

Problem description:
When using launchpad on Linux operating systems warning messages might be

displayed on the standard output.
Cause and solution
You can ignore these messages because they do not indicate any malfunctioning.
Undefined error when using launchpad on Windows

You try to install the Tivoli Dynamic Workload Console on a Windows operating
system using the launchpad and you get an "Undefined" error message. The
launchpad does not start.
Cause and solution
Make sure that the path from where you launched the installation does not contain
folder names longer than eight characters. If it does, then map the path to the
launchpad.exe, and run the launchpad from that new path.
Problems with the interactive wizard

The following problems might be encountered while running the Tivoli Dynamic
Workload Console interactive installation:
v “The Tivoli Dynamic Workload Console installation hangs” on page 284
v “Installation from a remote shared folder fails on Windows” on page 284
v “Installation fails on a Linux 390 system whose hostname is not Fully Qualified
Domain Name” on page 284
v “Java Virtual Machine (JVM) failure when installing with the Tivoli Dynamic
Workload Console on a Red Hat Enterprise Linux (RHEL) Version 5 system” on
page 285
Chapter 15. Troubleshooting the installation and uninstallation 283

v “Tivoli Dynamic Workload Console graphical installation and uninstallation fail

to start on Red Hat Enterprise Linux (RHEL) Version 5 on x86-64” on page 285
v “On Windows the Tivoli Dynamic Workload Console installation fails if you try
to re-install on a different profile of an external WebSphere Application Server”
on page 286
The Tivoli Dynamic Workload Console installation hangs

The installation of Tivoli Dynamic Workload Console does not proceed. This occurs
regardless of the method you used to install.
Cause and solution
Make sure an active personal firewall is not preventing the installation process
from connecting to the network. If it is, allow the connection and then continue
with the installation.
Installation from a remote shared folder fails on Windows

You try to install the Tivoli Dynamic Workload Console on a Windows operating
system from a shared network folder that uses Universal Naming Convention
(UNC). The installation fails.
Cause and solution
You must map the remote folder locally on the Windows system where you want
to install the Tivoli Dynamic Workload Console and then run the installation using
the local path.
Installation fails on a Linux 390 system whose hostname is not

Fully Qualified Domain Name
You try to install the Tivoli Dynamic Workload Console with the embedded
WebSphere Application Server on a server whose hostname is not Fully Qualified
Domain Name. The installation fails and the following error is stored in the
twainstall.log file:
ADMU3011E: Server launched but failed initialization. startServer.log,
SystemOut.log(or job log in zOS) and other log files under
/oracle/ibm/TDWC/eWAS/profiles/twaprofile/logs/tdwcserver
should contain failure information.
WASX7023E: Error creating "SOAP" connection to host "localhost";

exception information:
com.ibm.websphere.management.exception.ConnectorNotAvailableException:
com.ibm.websphere.management.exception.ConnectorNotAvailableException:
ADMC0016E: The system cannot create a SOAP connector to connect to host
localhost at port 28880.
Cause and solution
Run the following command from the system prompt on the Linux 390 system
where you tried to install the Tivoli Dynamic Workload Console:
hostname --fqdn

If the command returns:

hostname: Unknown host
the host name is not resolved. You must specify a hostname with a fully qualified
domain name to install WebSphere Application Server. Update the hostname
notation, as explained in the WebSphere Application Server documentation, and
then rerun the installation.
Java Virtual Machine (JVM) failure when installing with the Tivoli
Dynamic Workload Console on a Red Hat Enterprise Linux
(RHEL) Version 5 system
When working with the Tivoli Dynamic Workload Console on a Red Hat
Enterprise Linux Version 5 system, a user might see the error ″Failed to find VM -
aborting″.
Cause and solution
Red Hat Enterprise Linux Version 5 has a new security feature named ’Security
Enhanced Linux’, or SELinux for short. A weaker version of SELinux was included
in Red Hat Enterprise Linux Version 4, and was disabled by default. Red Hat
Enterprise Linux Version 5 defaults SELinux to enabled. SELinux helps to keep the
host secure from certain types of malicious attacks. However, the default settings
have been known in many cases to prevent Java from running properly.
To fix this issue, you can choose one of the following options:
v Configure SELinux so that it knows that the Tivoli Dynamic Workload Console
Java related processes are acceptable to run.
v Change the mode of SELinux to Permissive by entering setenforce 0 on the
command line. SELinux will be fully enabled again the next time the system is
rebooted or if setenforce 1 is entered on the command line.
Tivoli Dynamic Workload Console graphical installation and

uninstallation fail to start on Red Hat Enterprise Linux (RHEL)
Version 5 on x86-64
When launching the Tivoli Dynamic Workload Console installation or the Tivoli
Dynamic Workload Console uninstall in graphical mode on Red Hat Enterprise
Linux (RHEL) Version 5 x86-64 it might happen that the following error is
displayed:
For the installation:

The installer is unable to run in graphical mode.
Try running the installer with the -console or -silent flag.
For the uninstall:

The uninstaller is unable to run in graphical mode.
Try running the uninstaller with the -console or -silent flag.
Cause and solution
If you run into this problem launch the installation, or the uninstall in silent mode.
For more information refer to “Performing a silent installation” on page 262, and
“Uninstalling in silent mode” on page 279.

On Windows the Tivoli Dynamic Workload Console installation

fails if you try to re-install on a different profile of an external
On a Windows operating system you installed the Tivoli Dynamic Workload

Console on a profile, named ProfileA for example, of an existing WebSphere
Application Server installation. You remove the Tivoli Dynamic Workload Console
successfully and then try to install it on a different profile of the same WebSphere
Application Server. The installation fails.
Cause and solution
This might happen because when you removed the Tivoli Dynamic Workload
Console, some files belonging to ProfileA were not removed. To solve this
problem, stop ProfileA and then launch again the Tivoli Dynamic Workload
Console installation on the other profile.
Problems with the silent installation

The following problems might be encountered while running the Tivoli Dynamic
Workload Console silent installation:
v “The silent uninstall does not work and an error code is returned”
v “PanelUserIsNotRoot message logged in tdwcinstall.log file when running a
silent installation”
The silent uninstall does not work and an error code is returned
If you try to perform a silent uninstall with a response file that does not exist,
either because the file name is incorrect or because you specified the wrong
directory, an error code is returned and the uninstall does not run. Nothing is
logged in the temporary directory and no messages are issued.
Cause and solution
Ensure that you specify a valid response file name.
PanelUserIsNotRoot message logged in tdwcinstall.log file when

running a silent installation
On a system where a silent installation has been attempted the following warning
message is listed in the twainstall.log file:
Install, com.installshield.tdwc.event.dialog.swing.PanelUserIsNotRoot, wrn,
Cause and solution
This message indicates that a user different from the administrator tried to run the
silent installation on that system. Switch to the administrator user ID, root for
UNIX operating systems, or Administrator for Windows operating systems, and
rerun the silent installation.

Problems with the uninstallation

The following problem might be encountered while running the Tivoli Dynamic
Workload Console uninstallation:
v “Uninstall fails on Windows if the installation directory contains the @
character”
v “Tivoli Dynamic Workload Console graphical uninstallation fails to start on Red
Hat Enterprise Linux (RHEL) Version 5 on x86-64”
Uninstall fails on Windows if the installation directory contains

the @ character
When running uninstaller.exe to remove the Tivoli Dynamic Workload Console

installed in a directory that contains the @ character, for example C:\Program
Files\ibm\TDWC\a-.@_~a the uninstall fails and the following error message is
displayed:
CreateProcess failed ==> The system cannot find the file specified.
and the uninstall fails.
Cause and solution
The uninstall fails because ’@’ is a special character for ISMP and so ISMP cannot
manage an installation directory containing this character.
You can bypass the problem by running the uninstall as follows:

"C:\Program Files\ibm\TDWC\a-.@_~a\_jvm\jre\bin\java.exe"
-cp "C:\Pr Fi\ibm\TDWC\a-.@_~a\_tdwcuninst\uninstall.jar" run
Run this command outside the installation directory, otherwise the installation
directory is not removed.
Tivoli Dynamic Workload Console graphical uninstallation fails to

start on Red Hat Enterprise Linux (RHEL) Version 5 on x86-64
When launching the Tivoli Dynamic Workload Console uninstallation in graphical

mode on Red Hat Enterprise Linux (RHEL) Version 5 x86-64 it might happen that
the following error is displayed:
The uninstaller is unable to run in graphical mode.
Try running the uninstaller with the -console or -silent flag.
See “Tivoli Dynamic Workload Console graphical installation and uninstallation

fail to start on Red Hat Enterprise Linux (RHEL) Version 5 on x86-64” on page 285
for the solution.


Chapter 16. Installation, and uninstallation messages
This chapter lists the Tivoli Dynamic Workload Console installation and
uninstallation messages and their descriptions.
For a description of the IBM Tivoli message format, see “IBM Tivoli message
format” on page 175.
This publication does not contain any details of Informational messages, as they
are complete within themselves, and do not need further explanation.
The messages are in two sets:

v “Installation (InstallShield wizard) common messages - JIC”
v “Installation (InstallShield wizard) messages - UI (001–100)”
Installation (InstallShield wizard) common messages - JIC

This section refers to error and warning messages that could be generated by the
installation (InstallShield wizard) of Tivoli Workload Scheduler or the Tivoli
Dynamic Workload Console - they are common to both.
The message component code is JIC.
As they are common, they have only been listed in one place - go to “Installation
(InstallShield wizard) common messages - JIC” on page 177
Installation (InstallShield wizard) messages - UI (001–100)

This section refers to error and warning messages that could be generated by the
installation (InstallShield wizard) of the Tivoli Dynamic Workload Console.
The message component code is UI, in the range 001 to 100.
Re-enter the user name ensuring that it falls

AWSUI0001E The user name has an incorrect
within the supported range, and proceed with
number of characters. The permitted
the installation.
range is between 3 and 60.
Explanation: The value entered as user name does not
AWSUI0002E The user name can only contain the
fall within the permitted range.
following characters: a-z, A-Z, 0-9,
System action: If you are running the graphical period (.), hyphen (-), underscore ( _ )
wizard installation, the installation stops with an error and DBCS characters.
message.
Explanation: The entered value contains characters
If you are running the silent installation, the installation that are not supported.
exits with an error.
System action: If you are running the graphical
Operator response: If you are running: wizard installation, the installation stops with an error
message.
Silent installation
Edit the response file specifying a user name
that falls within the supported range, and
launch a new installation. Operator response: If you are running:
Wizard installation Silent installation

AWSUI0003E • AWSUI0008E
Edit the response file specifying a user name

AWSUI0005E The password and the confirm
that contains only supported characters.
password are not the same.
Wizard installation
Explanation: The confirm password must be the same
Re-enter the user name ensuring that it does as the password.
not contain any unsupported characters, and
System action: The graphical wizard installation, stops
proceed with the installation.
with an error message.
Operator response: Re-enter the password and
AWSUI0003E The password has an incorrect number
confirm password ensuring they are the same, and
of characters. The permitted range is
between 5 and 60.
Explanation: The value entered as password does not
AWSUI0006E The user name cannot be blank.
fall within the permitted range.
Explanation: A value must be entered in the user
name field.
wizard installation, the installation stops with an error
message. System action: If you are running the graphical
message.
Operator response: If you are running:
Silent installation
Edit the response file specifying a password
Silent installation
that falls within the supported range, and
launch a new installation. Edit the response file specifying a valid user
name, and launch a new installation.
Wizard installation
Wizard installation
Re-enter the password ensuring that it falls
within the supported range, and proceed with Enter a valid user name, and proceed with the
the installation. installation.
AWSUI0004E The password can only contain the AWSUI0007E The password cannot be blank.
following characters: a-z, A-Z, 0-9,
Explanation: A value must be entered in the password
period (.), hyphen (-), and underscore
field.
(_).
that are not supported.
message.
message.
exits with an error. Silent installation
Operator response: If you are running: Edit the response file specifying a valid
password, and launch a new installation.
Silent installation
Wizard installation
Edit the response file specifying a password
that contains only supported characters. Enter a valid password, and proceed with the
installation.
Wizard installation
Re-enter the password ensuring that it does
AWSUI0008E The installation path is too long: it
not contain any unsupported characters, and
must be shorter than 74 characters.
Explanation: The value entered as installation path
does not fall within the permitted range.

wizard installation, the installation stops with an error System action: The installation exits with an error.
message.
Operator response: Edit the response file specifying a
If you are running the silent installation, the installation supported installation method.
Operator response: If you are running: AWSUI0014E The TCP/IP port tcpip_port_label is not
valid.
Silent installation
Explanation: The value entered as TCP/IP port is not
Edit the response file specifying an installation
valid.
path that falls within the supported range, and
launch a new installation. System action: If you are running the graphical
Wizard installation
message.
Re-enter the installation path ensuring that it
falls within the supported range, and proceed
with the installation.
AWSUI0009E The installation path contains the Silent installation
following unsupported characters or non
Edit the response file specifying a valid
US-ASCII characters:
TCP/IP port number, and launch a new
unsupported_characters.
installation.
Wizard installation
Re-enter a valid TCP/IP port number, and
message.
AWSUI0015E Port number tcpip_port_value specified
for tcpip_port_name is already in use.
Explanation: The specified TCP/IP port is already
used by another product.
Silent installation
Edit the response file specifying an installation wizard installation, the installation stops with an error
path that contains only supported characters. message.
Wizard installation If you are running the silent installation, the installation
Re-enter the installation path ensuring that it
does not contain any unsupported characters, Operator response: If you are running:
and proceed with the installation.
Silent installation
Edit the response file specifying a new TCP/IP
AWSUI0010E A stand-alone Integrated Solutions
port number, and launch a new installation.
Console has been found: it is not
possible to install a new one. Wizard installation
Explanation: An Integrated Solutions Console cannot Re-enter a new TCP/IP port number, and
be installed on a computer where another Integrated proceed with the installation.
Solutions Console is already present.
System action: The installation exits with an error. AWSUI0016E Port number tcpip_port_value has been
specified for ports: tcpip_port_names.
Operator response: Run a new installation on a
different computer. Explanation: The value entered for TCP/IP port has
already been assigned to the other ports indicated in
the message text.
AWSUI0011E The value install_method specified for
the INSTALL_METHOD variable is not System action: The installation stops with an error
supported. The only supported values message.
are: NEW, ONTWA, and ONWAS.
Operator response: Re-enter a new TCP/IP port
Explanation: The specified INSTALL_METHOD is not number, and proceed with the installation.
valid.
Chapter 16. Installation, and uninstallation messages 291


AWSUI0017E The host name is not valid.
Explanation: message.
Operator response: If you are running the silent installation, the installation
AWSUI0018E You must have administrator privileges Operator response: If you are running:
to run this installation.
Silent installation
Explanation: Administrator’s privileges are required to
Start WebSphere Application Server and
run the installation.
launch a new installation.
Wizard installation
message. Start WebSphere Application Server and
AWSUI0023E The credentials provided for the
Operator response: Login as an Administrator and
administrator are not correct.
Explanation: The values entered as credentials for
AWSUI0019E The service ID can only contain the
WebSphere Application Server are not correct.
following characters: a-z, A-Z and 0-9.
message.
message.
exits with an error. Silent installation
Operator response: If you are running: Edit the response file specifying valid
credentials, and launch a new installation.
Silent installation
Wizard installation
Edit the response file specifying a service ID
that contains only supported characters. Re-enter the credentials ensuring that are
valid, and proceed with the installation.
Wizard installation
Re-enter the service ID ensuring that it does
AWSUI0024E The installation completed, but with
not contain any unsupported characters.
errors. See the previous installation log
messages.
AWSUI0020E The WebSphere Application Server
Explanation: The installation failed due to some
service ID must not be blank.
errors. You can find the error messages in the
Explanation: A value must be entered in the service installation log file, before current error.
ID field.
System action: The system deletes any installed files.
System action: The installation stops with an error
Operator response: Check the errors that caused the
message.
installation failure in the installation log file, fix them
Operator response: Enter a valid service ID, and and run a new installation.
AWSUI0025E The console installation type is not
AWSUI0022E The operation cannot proceed because supported. Use the graphical interactive
WebSphere Application Server is not installation or the silent (response file)
active and it is not possible to check the installation.
specified credentials. Start the server
Explanation: This installation mode is not supported.
before proceeding.
System action: Installation does not start.
Explanation: WebSphere Application Server must be
up and running for the installation to take place. Operator response: Launch a new installation using

one of the supported methods: either the graphical

AWSUI0029E There is no instance of WebSphere
wizard or the silent installation.
Application Server in the specified
directory "directory_name".
AWSUI0026E The uninstallation completed, but with
Explanation: The specified directory does not contain
errors. See the previous installation log
any instance of WebSphere Application Server.
messages.
Explanation: The uninstallation completed but not all
the files have been removed. You can find the error
message.
messages in the log file, before current error.
System action: The system uninstalls the application
but leaves some files to be removed manually.
Operator response: Check the errors that caused the
uninstallation failure in the log file. Optionally, remove Silent installation
the unnecessary files that have not been uninstalled
Edit the response file specifying a different
properly.
directory, and launch a new installation.
Wizard installation
AWSUI0027E An unsupported version of WebSphere
Application Server has been selected. Specify a different directory that contains an
instance of WebSphere Application Server, and
Explanation: The entered version of WebSphere
Application Server is not supported.
AWSUI0030W Unable to verify the TCP/IP port
"tcpip_port_name". Reason: error_message
message.
Explanation: The availability of the specified TCP/IP
port could not be verified.
System action: Installation continues without checking
port availability.
Silent installation
Operator response: Proceed with the installation.
Edit the response file specifying a supported
version of WebSphere Application Server, and
AWSUI0031E The WebSphere Update Installer
location cannot be blank.
Wizard installation
Explanation: A location must be specified for the
Enter a supported version of WebSphere WebSphere Update Installer.
Application Server, and proceed with the
System action: The installation stops with an error
installation.
message.
Operator response: Enter a valid location, and
AWSUI0028E Security is not enabled on the selected
instance of WebSphere Application
Server.
AWSUI0032E One of the parameters for WebSphere
Explanation: The installation of the product requires
Application Server "was_info" was blank.
security to be enabled on the selected instance of
WebSphere Application Server. Explanation: A value must be entered as a parameter
for WebSphere Application Server. The field cannot be
System action: The installation exits with an error.
left blank.
Operator response: Enable security on the selected
instance of WebSphere Application Server or select a
different instance of WebSphere Application Server that
message.
has security enabled.
Silent installation

AWSUI0033W • AWSUI0038E
Edit the response file specifying a parameter, Edit the response file specifying a valid
and launch a new installation. WebSphere Application Server name, and
Wizard installation
Wizard installation
Enter a parameter for WebSphere Application
Server, and proceed with the installation. Specify a valid WebSphere Application Server
name, and proceed with the installation.
AWSUI0033W The installation wizard cannot check
the installation of the selected AWSUI0036E The specified WebSphere Application
WebSphere Application Server. Check Server cell "cell_name" does not exist.
that it is installed correctly.
Explanation: It has been specified a WebSphere
Explanation: It was not possible to verify that Application Server cell that does not exist.
WebSphere Application Server is correctly installed.
System action: Installation continues. wizard installation, the installation stops with an error
message.
Operator response: Check that it is installed correctly,
and proceed with the installation. If you are running the silent installation, the installation
AWSUI0034E The specified WebSphere Application Operator response: If you are running:
Server profile "profile_name" does not
Silent installation
exist.
Edit the response file specifying a valid
WebSphere Application Server cell name, and
Application Server profile that does not exist.
Wizard installation
message. Specify a valid WebSphere Application Server
cell name, and proceed with the installation.
AWSUI0037E The specified WebSphere Application
Server node "node_name" does not exist.
Silent installation
Edit the response file specifying a valid Application Server node that does not exist.
WebSphere Application Server profile name,
and launch a new installation.
Wizard installation message.
Specify a valid WebSphere Application Server If you are running the silent installation, the installation
profile name , and proceed with the exits with an error.
installation.
Silent installation
AWSUI0035E The specified WebSphere Application
Server application server "server_name" Edit the response file specifying a valid
does not exist. WebSphere Application Server node name, and
Application Server that does not exist. Wizard installation
System action: If you are running the graphical Specify a valid WebSphere Application Server
wizard installation, the installation stops with an error node name , and proceed with the installation.
message.
If you are running the silent installation, the installation AWSUI0038E There is no instance of the WebSphere
exits with an error. Update Installer in the specified
directory "directory_name".
Explanation: The specified directory does not contain
Silent installation
any WebSphere Update Installer.

wizard installation, the installation stops with an error System action: The installation fails.
message.
Operator response: Install the Tivoli Dynamic
If you are running the silent installation, the installation Workload Console on this system, and run this
exits with an error. installation again.
AWSUI0045E The prerequisite checking has failed.
Silent installation
Either you are running an unsupported
Edit the response file specifying a valid version of the Tivoli Dynamic Workload
directory, and launch a new installation. Console or this fix pack or higher is
already installed.
Wizard installation
Explanation: It is not possible to install the Tivoli
Specify a valid directory, and proceed with the Dynamic Workload Console Fix Pack 1 more than once
installation. on the same system.
System action: The installation fails.
AWSUI0042E There is insufficient space in the path
file system to complete the installation. Operator response: Uninstall the existing Tivoli
At least required_disk_space is required. Dynamic Workload Console or install the Tivoli
Dynamic Workload Console Fix Pack 1 on a different
Explanation: The specified file system does not have system.
enough available free space for the installation to
complete. Required space is specified in the message.
AWSUI0046E A Windows Service with the specified
System action: If you are running the graphical ID already exists. Specify a different
wizard installation, the installation stops with an error Service ID.
message.
Explanation: A Windows Service ID was specified that
If you are running the silent installation, the installation already exists in the registry.
System action: The graphical wizard installation stops
Operator response: If you are running: with an error message.
Silent installation Operator response: Specify a valid Windows Service
Free the required space on the file system, and ID, and proceed with the installation.
Wizard installation AWSUI0047E A Windows Service with the specified
ID already exists. Specify a different
Free the required space on the file system, and Service ID using the Advanced
proceed with the installation. installation option.
Explanation: The Windows Service ID used to run the
AWSUI0043E The Tivoli Dynamic Workload Console default installation already exists in the registry.
is already installed on this system. You
cannot install another instance. System action: The graphical wizard installation stops
with an error message.
Explanation: It is not possible to install more than one
instance of Tivoli Dynamic Workload Console on the Operator response: Choose the Advanced installation
same system. option, specify a valid Windows Service ID, and
System action: Installation fails.
Operator response: Uninstall the existing Tivoli AWSUI0048E A Windows Service with the specified
Dynamic Workload Console or install the new Tivoli ID already exists. Specify a different
Dynamic Workload Console on a different system. Service ID in the
WAS_SERVICE_NAME variable of the
AWSUI0044E This fix pack cannot be installed response file.
because the Tivoli Dynamic Workload Explanation: The Windows Service ID specified for
Console is not installed on this system. the WAS_SERVICE_NAME variable in the response file
Explanation: It is not possible to install the Tivoli already exists in the registry.
Dynamic Workload Console Fix Pack 1 on a system System action: The silent installation fails with an
where Tivoli Dynamic Workload Console is not error.
installed.
Operator response: Specify a valid Windows Service

ID in the response file, and launch a new installation. Software Support for assistance.
If you are not expecting to identify any existing
AWSUI0051E The silent installation failed. Check instances of Tivoli Workload Automation or previous
the "log_file" file for details. components of Tivoli Workload Scheduler on this
system, you need take no action.
System action: The silent installation fails.
AWSUI0062I An error has occurred. See the log files
Operator response: Check the indicated log file for for details.
details of why the installation failed.
AWSUI0052E The silent uninstallation failed. Check
the log file "logfile"for details. Operator response: See the log file, correct the
problem, and rerun the installation.
System action: The silent uninstallation fails.
AWSUI0063I The uninstallation of "product" failed.
Operator response: Check the indicated log file for See the log file for more details.
details of why the uninstallation failed.
AWSUI0055I The installation of "component" failed.
Operator response: See the log file, correct the
problem, and rerun the uninstallation.
System action: The installation completed with an
error.
AWSUI0064E An error occurred during the
Operator response: Check the log file for details of installation. See the trace file "file" for
why the component installation failed. details.
AWSUI0057I The installation wizard encountered an
System action: See message.
error while unloading files.
Operator response: See the trace file to check the
Explanation: There was an installation problem in the
cause of the error. Fix the problem and rerun the
InstallShield MultiPlatform Product Tree.
installation.
System action: The installation is rolled back.
Operator response: Check the trace_installation.log AWSUI0065I The installation of Tivoli Dynamic
file, resolve the problem, and attempt a new Workload Console is not complete.
installation. Resume the installation and run all the
outstanding steps in order to complete
it.
AWSUI0060E The installation wizard was unable to
determine the installation status. Explanation: See message.
Explanation: The installation wizard is not able to System action: The installation stops.
discover whether any existing instances of Tivoli
Operator response: Use the stepped restart facility to
Workload Automation or previous components of
rerun all of the steps.
Tivoli Workload Scheduler are present on this system,
because an error occurred in the discovery action.
AWSUI0066E The supplied path does not identify an
System action: The installation wizard continues as if
existing instance of Tivoli Workload
the discovery had worked correctly, but had discovered
Automation.
nothing.
Explanation: You are trying to install the Tivoli
Operator response: If you are expecting to identify
Dynamic Workload Console on an existing instance of
any existing instances of Tivoli Workload Automation
Tivoli Workload Automation, but the path you have
or previous components of Tivoli Workload Scheduler
supplied does not contain such an instance.
on this system, stop the installation wizard and try
restarting it. If you are running the silent installation System action: The wizard stops.
wizard, check that the response file is not corrupt, and
Operator response: Either supply a different path for
that the entries correctly identify the actions you want
the instance of Tivoli Workload Automation or choose
to perform. If the problem persists, contact IBM
to install a new instance.

AWSUI0067I • AWSUI0070W
quit the installation, create more space or plan

AWSUI0067I The uninstallation of Tivoli Dynamic
to install in a file system with more space, and
Workload Console is not complete.
rerun the installation.
Please resume the uninstallation and
run all the outstanding steps in order to Silent installation
complete it.
If you are running the silent wizard, check
Explanation: See message. whether the installation completed
successfully. If it did, take no action. If it did
System action: The installation stops.
not, clean up any partial installation, create
Operator response: Use the stepped restart facility to more space and rerun the installation. If
rerun all of the steps. necessary, contact IBM Software Support for
assistance.
AWSUI0068W The installation wizard is not able to
check the disk space available on this AWSUI0069E No valid action can be performed on
platform, because of a technical error. the Tivoli Workload Automation
Check the space requirements detailed instance that has been selected.
in the detailed system requirements Select a valid instance or create a new
document. If you are running the instance.
interactive wizard, and you are sure
Explanation: A Tivoli Workload Automation instance
there is sufficient space, both in the
can only have one instance of each of its constituent
system temporary directory and where
products and components installed in it. To install more
you want to install the Tivoli Dynamic
than one instance of a product or component, you must
Workload Console, close this message
window and click "Next" to continue the
second instance of Tivoli Workload Automation.
installation. Otherwise, quit the wizard,
create more space or change the System action: If you are running the interactive
installation path, and rerun the wizard, the wizard stops.
installation.
Explanation: The installation needs to use a certain fails.
amount of space in the system’s temporary directory
and where the component is to be installed. But in Operator response: Proceed as follows:
attempting to determine whether the space available in - Interactive wizard
the temporary directory is sufficient, an error occurred.
This means not only that the wizard cannot check the
temporary space available, but that it will not be able 2. Reenter the installation path, ensuring that
to check the space available at the install location that the path does not identify a Tivoli
you choose on a later panel. So you must check the Workload Automation instance where the
space available manually. Tivoli Dynamic Workload Console has
already been installed. Click Next to
System action: continue.
Interactive wizard - Silent installation
The interactive installation waits for you to 1. Edit the response file, ensuring that the
click "Next" or "Quit". path does not identify a Tivoli Workload
Automation instance where the Tivoli
Silent installation Dynamic Workload Console has already
The silent wizard displays this message in the been installed..
log and continues with the installation. 2. Rerun the silent installation.
Operator response:
AWSUI0070W The instance of Tivoli Dynamic
Interactive wizard
Workload Console found on this system
If you are running the interactive wizard, cannot be upgraded.
ensure that there is sufficient space in the
Explanation: You have selected to upgrade Tivoli
temporary directory and where you want to
Dynamic Workload Console, but the instance of Tivoli
install the component (see the detailed system
Dynamic Workload Console found on the system
requirements document to determine how
cannot be upgraded.
much space is needed on this platform). If
there is sufficient space, continue the System action: If you are running the interactive
installation. If there is not, or you are not sure, wizard, the wizard stops.

If you are running the silent installation, the installation Operator response: Proceed as follows:
fails. 1. If you are running the interactive wizard, click OK
Operator response: Proceed as follows: to close the error message.
1. If you are running the interactive wizard, click OK 2. Check if an instance of Tivoli Dynamic Workload
to close the error message. Console is present on the system. If not, select to
install a fresh instance of Tivoli Dynamic Workload
2. Check in the detailed system requirements whether
Console, or exit from the installation.
the installed instance of tdwc; can be upgraded. If it
cannot, select to install a fresh instance and then 3. If an instance of Tivoli Dynamic Workload Console
uninstall the old instance. is installed, check in the detailed system
requirements that it can be upgraded. If it cannot,
3. Otherwise, if the instance is capable of being
exit from the wizard, uninstall the old instance, and
upgraded, exit from the installation and try the
install a fresh instance.
installation again. If the problem persists, contact
IBM Software Support for assistance. 4. Otherwise, if the instance is capable of being
AWSUI0071E No instance of Tivoli Dynamic IBM Software Support for assistance.
Workload Console was found on this
system to upgrade.
AWSUI0073E The instance of the Tivoli Dynamic
Explanation: You have selected to upgrade Tivoli Workload Console that you want to
Dynamic Workload Console, but no instance of Tivoli upgrade uses an LDAP user registry.
Dynamic Workload Console can be found on the This scenario is not supported. Install a
system to upgrade. fresh instance of the Tivoli Dynamic
System action: If you are running the interactive Workload Console.
wizard, the wizard stops. Explanation: See message.
If you are running the silent installation, the installation System action: If you are running the graphical
fails. wizard installation, the installation stops with an error
Operator response: Proceed as follows: message.
1. If you are running the interactive wizard, click OK If you are running the silent installation, the installation
to close the error message. exits with an error.
2. Check if an instance of Tivoli Dynamic Workload Operator response: Install a fresh instance of the
Console is present on the system. If not, select to Tivoli Dynamic Workload Console.
install a fresh instance of Tivoli Dynamic Workload
Console, or exit from the installation.
3. If an instance of Tivoli Dynamic Workload Console
is installed, check in the detailed system
requirements that it can be upgraded. If it cannot,
exit from the wizard, uninstall the old instance, and
install a fresh instance.
4. Otherwise, if the instance is capable of being
IBM Software Support for assistance.
AWSUI0072E No instance of Tivoli Dynamic

Workload Console was found on this
system to apply fixpack.
Explanation: You have selected to update Tivoli
Dynamic Workload Console, but no instance of Tivoli
Dynamic Workload Console can be found on the
system to update.
fails.

Part 4. Tutorials
This part describes the Tivoli Workload Scheduler tutorial utility and guides you
through a set of steps to populate and use a stand-alone test environment.

Tutorials

Chapter 17. Using the Tivoli Workload Scheduler tutorial
utility
This section describes the Tivoli Workload Scheduler tutorial utility and guides you
through a set of steps to populate and use a stand-alone test environment. The
tutorial utility is intended for first-time users of Tivoli Workload Scheduler who
want an overview of the features and capabilities of the product in a real
environment. The tutorial utility includes a sample database with predefined
scheduling objects and a set of scenarios that use these objects.
The sampledbsetup.sh or the SAMPLEDBSETUP.CMD script (depending on

whether you are in a UNIX or Windows environment) populates your Tivoli
Workload Scheduler with a set of scheduling objects. The scenario scripts use these
objects in basic scheduling activities. Each scenario is self-contained and can be run
in any order, with the exception of the first scenario which is a prerequisite to all
others.
The Tivoli Workload Scheduler tutorial utility runs only on a master domain
manager. It does not affect any other workstation defined in your Tivoli Workload
Scheduler environment. Each scenario is launched as a separate script file which
uses the conman and composer command interfaces. The syntax and usage of each
command used in the scenarios is explained in detail in the Tivoli Workload
Scheduler: User's Guide and Reference. Before you begin using the utility, read an
overview of Tivoli Workload Scheduler concepts and tasks in Tivoli Workload
Automation: Overview.
This chapter is divided into the following sections:

v “Populating your Tivoli Workload Scheduler database”
v “Overview of the scheduling scenarios” on page 303
v “Creating and working with the production plan” on page 303
v “Running the scheduling scenarios” on page 304
v “Removing tutorial objects from the database” on page 308
Populating your Tivoli Workload Scheduler database

This section describes how you use the utility to populate your Tivoli Workload
Scheduler database.
After you have installed Tivoli Workload Scheduler on the master domain manager
in your test environment you are ready to populate the database.
Follow these steps:

| 1. Go to the TWS_home/TWS/TWSTutorial directory, where TWS_home is the home
| directory of the user for which you installed Tivoli Workload Scheduler.
2. Launch the tutorial utility installation script:
v In a Windows environment:
SAMPLEDBSETUP.CMD
v In a UNIX environment:
sampledbsetup.sh

Populating the database
The script adds a set of scheduling objects with names starting with the string
SMPL, followed by the object type and scenario number so that all objects used in
each scenario are easily identifiable. Some objects are different depending on
whether you are using a UNIX or a Windows environment.
The script performs a check on the database. If any objects with the same name are
found, you are prompted to specify if these objects can be overwritten.
When processing of the script ends successfully, your Tivoli Workload Scheduler
database contains the objects needed to run the scheduling scenarios.
Objects used by the Tivoli Workload Scheduler tutorial

scenarios
After you have successfully installed the Tivoli Workload Scheduler tutorial utility
in your test environment, your database is populated with the following
scheduling objects:
| Table 27. Objects downloaded by the tutorial utility
| Object type Object Names (Total objects)
| Calendar SMPCAL6 (1)
| Variable SMPLHOME, SMPLUSER, SMPLWIN1to
| SMPLWIN4 or SMPLUNX1 to SMPLUNX4,
| SMPLSLEEP, SMPLTMP, SMPLUNX3,
| SMPLPATH, SMPLTMP (6)
| Resource SMPLRES1, SMPLRES2 (2)
| Prompt SMPLPRM4, SMPLPRM5, SMPLPRM6,
| SMPLPRM7 (4)
| Job SMPL_JOB_3_0_1, SMPL_JOB_3_0_2,
| SMPL_JOB_3_0_3, SMPL_JOB_4_0_1,
| SMPL_JOB_9_1_1, SMPL_JOB_EVN,
| SMPL_JOB_ODD, SMPL_JOB_PAIR,
| SMPL_JOB_SBJ, SMPL_JOB_7_0_LAST,
| SMPL_JOB_7_0_RECV (20)
| Job Stream SMPL_SCHED_3_0_1, SMPL_SCHED_3_0_2,
| SMPL_SCHED_4_0_1, SMPL_SCHED_4_0_2,
| SMPL_SCHED_4_0_3, SMPL_SCHED_4_0_S,
| SMPL_SCHED_7_0_1 SMPL_SCHED_7_0_2,
| SMPL_SCHED_5–ODD, SMPL_SCHED_5_EVN,
| SMPL_SCHED_SBS (17)
| Event Rule SMPL_FILTER_RULE (1)
| Variable table SMPL_VAR_TABLE_9_0_1,
| SMPL_VAR_TABLE_9_0_2 (2)
|
You can display each object by running the composer command interface. For
specific information about the syntax of the composer interface, see the Tivoli

Scheduling scenarios overview
Overview of the scheduling scenarios

The following table describes the topics covered in each scenario. Each scenario is
a separate script file.
You must run Scenario 1 first, but you can choose to run the other scenarios in any
order.
| Table 28. List of scheduling scenarios
| Scenario name Script name Topics
| Scenario 1 scenario1.0.bat Creating the production plan
| (Windows)scenario1.0.sh and viewing its contents
| (UNIX) Note: This scenario is a
| prerequisite for all the other
| scenarios in your sequence.
| Scenario 2 scenario2.0.bat Administrative commands:
| (Windows)scenario2.0.sh starting and stopping Tivoli
| (UNIX) Workload Scheduler
| processes
| Scenario 3 scenario3.0.bat Scheduling basics: how jobs
| (Windows)scenario3.0.sh are scheduled, run order of
| (UNIX) jobs
| Scenario 4 scenario4.0.bat Advanced Scheduling:
| (Windows)scenario4.0.sh prompt, file, and resource
| (UNIX) dependencies
| Scenario 5 scenario5.0.bat Time dependencies and run
| (Windows)scenario5.0.sh cycles
| (UNIX)
| Scenario 6 scenario6.0.bat Job submission (jobs, job
| (Windows)scenario6.0.sh streams, ad-hoc jobs)
| (UNIX)
| Scenario 7 scenario7.0.bat Recovery options and
| (Windows)scenario7.0.sh recovery jobs
| (UNIX)
| Scenario 8 scenario8.0.bat Event-driven scheduling
| (Windows)scenario8.0.sh
| (UNIX)
| Scenario 9 scenario9.0.bat Using variable tables
| (Windows)scenario9.0.sh
| (UNIX)
|
Creating and working with the production plan

After you have successfully populated the database, you are ready to run the
Scenario 1, which creates the production plan. The production plan contains the
database objects (jobs and job streams) that are eligible for scheduling.
Scenario 1 is a prerequisite to all other scenarios so you must run it first. The other
scenarios can then be run in any order.
Most commands in the scenarios are given in their short form. Where this is the
case, the full name of the command is shown in parentheses in each scenario
description.
Chapter 17. Using the Tivoli Workload Scheduler tutorial utility 303
Working with the plan
| Scenario 1: Creating the production plan and viewing its

| contents
| The scenario shows you how to:
| v Create and extend a production plan
| v Understand if a plan was created successfully
| v View the contents of a plan
| The scenario performs the following actions:

| v Creates a production plan with a duration of 24 hours
| v Inserts into the plan all the jobs and job streams that the tutorial already added
| in the database with their dependencies
| v Views the contents of the plan
| Commands used in the scenario in their run sequence:

| 1. JnextPlan
| 2. conman sc (showcpus)
| 3. planman showinfo
| 4. conman ss @#SMPL@ (showschedules)
Running the scheduling scenarios

After creating the plan in Scenario 1, the other scenarios use the tutorial objects in
the database by scheduling them in the plan. Each scenario explains different
scheduling concepts. For each command used in the scenarios, the output is
displayed on the screen.
Note: You can run the scenarios in any order because each scenario uses different
objects. However, if you want to run the same scenario more than once in
your sequence, you must reset the plan and run Scenario 1 again before you
rerun the individual scenario. Perform these steps:
1. Run the following command:
ResetPlan -scratch
2. Run the scenario1.0.bat in Windows or the scenario1.0.sh script in UNIX.
Scenario 2: Starting and stopping Tivoli Workload Scheduler

processes
This scenario performs some basic administrative tasks. After each stop or start
command, the status is displayed on the screen.
Scenario tasks and concepts:

v Stopping and starting the Tivoli Workload Scheduler engine
v Stopping and starting the event processor
v Stopping and starting the monitoring agent
v Viewing process status
Commands used in the scenario in their run sequence:

1. "conman stop"
2. "conman status"
3. "conman start"
4. "conman status"
5. "conman stopevtproc" (stopeventprocessor)
6. "conman startevtproc" (starteventprocessor)
7. "conman sc" (showcpus)
8. "conman stopmon;wait"
9. "conman startmon"
For a detailed description of Tivoli Workload Scheduler processes and related

commands, see the Tivoli Workload Scheduler: User's Guide and Reference.
Scenario 3: Scheduling basics, how jobs are scheduled, and

run order of jobs
This scenario performs basic scheduling tasks by showing how you schedule jobs
and how you manage the scheduling sequence.

v Running a job and a job stream on a workstation
v Viewing job status
v Viewing and changing the workstation limit
v Understanding the concept and purpose of dependent job streams and run order
(FOLLOWS)
v Viewing dependency resolution during job runs

1. "conman ss @#SMPL_SCHED_3@" (showschedules)
2. "composer disp sched=@SMPL_SCHED_3_0_2"
3. "conman lc; 10;noask" (limit)
5. "conman sj @#SMPL_SCHED_3_0_@.SMPL_JOB_3_0_@" (showjobs)
6. "conman sj @#SMPL_SCHED_3_0_@.SMPL_JOB_3_0_@" (showjobs
Scenario 4: Advanced scheduling, dependencies from

prompts, files, and resources
This scenario performs advanced scheduling tasks by showing different types of
dependencies in action.

v Viewing and managing prompt dependencies
v Viewing and managing resource dependencies
v Viewing and managing file dependencies
v Understanding resource contention between jobs

1. "composer disp sched= @#SMPL_SCHED_4@"
2. "conman ss @SMPL_SCHED_4@" (showschedules)
3. "conman sp @#SMPLPRM4" (showprompts)
4. "conman reply SMLPRM4;y" (reply)
5. "conman sp @#SMLPRM4" (showprompts)
6. "conman sj @SMPL_SCHED_4_0_@.@" (showjobs)
7. "conman sj @SMPL_SCHED_4_0_@.@" (showjobs)
8. "conman sj @SMPL_SCHED_4_0_S.@" (showjobs)
Scenario 5: Time dependencies and run cycles

This scenario performs advanced scheduling using time dependencies and run
cycles.

v Managing time limits such as AT time and UNTIL time
v Releasing a time dependency
v Using run cycles to plan scheduling activities

1. "conman sj @#SMPL_SCHED_5_0_@.SMPL_JOB_5_0_@" (showjobs)
2. "conman ddj @#SMPL_SCHED_5_0_1.SMPL_JOB_5_0_1;at;noask" (deldep)
3. "conman sj @#SMPL_SCHED_5_0_1.SMPL_JOB_5_0_1" (showjobs)
4. "conman rj @#SMPL_SCHED_5_0_1.SMPL_JOB_5_0_2" (release)
5. "conman sj @#SMPL_SCHED_5_0_1.SMPL_JOB_5_0_2" (showjobs)
6. "conman ss @#SMPL_SCHED_5-@" (showschedules)
Scenario 6: Manual submission of jobs, job streams, and

commands
This scenario uses the submit command to insert jobs, job streams, and ad-hoc jobs
in the plan.

v Submitting a job in the current production plan
v Submitting a job stream in the current production plan
v Submitting a command in the current production plan
v Displaying the job, job stream, and command status in the plan

1. "conman sbj @#SMPL_JOB_SBJ;alias=SMPL_SBJ_ALIAS" (submit)
2. "conman sj @#JOBS.SMPL_ALIAS" (showjobs)
3. "conman sbs @#SMPL_SCHED_SBS;alias=SMPL_SBS_ALIAS" (submit)
4. "conman sj @#SMPL_SBS_ALIAS" (showjobs)
5. "conman sbd "ver"; logon=^SMPLUSER^;alias=SMPL_SBD_ALIAS" (submit)
6. "conman sj @#JOBS.SMPL_SBD_ALIAS" (showjobs)
Note: The value of the logon attribute in step 5 is specified by using a parameter
object. For more information about parameters see the Tivoli Workload
Scheduler: User's Guide and Reference.
Scenario 7: Recovery options and recovery jobs

This scenario shows some examples of recovery options and recovery jobs.

v Defining and using the STOP, CONTINUE, and RERUN recovery options
v Understanding the use of recovery jobs to solve scheduling malfunctions

1. "conman reply SMPLPRM7;y" (reply)
2. "conman sp SMPLPRM7" (showprompts)
3. "conman sj @#SMPL_SCHED_7_0_1.@" (showjobs)

Scenario 8: Event-driven scheduling

This scenario shows some examples of event-driven scheduling.

v Creating a rule and associating an action to the rule
v Understanding the different rule types: Filter, Sequence, and Collection rules
v Processing an action associated to a rule

1. "composer disp erule=SMPL_FILTER_RULE" (display)
2. "planman deploy -scratch"
| 3. "conman sj @#JOBS.SMPL_SBJ_ALIAS2" (showjobs)
| Scenario 9: Using variable tables

| This scenario shows how you use variable tables to:
| v Change the behavior of jobs and job streams based on why they are scheduled
| to run. For example, you can create a job that runs different commands for
| different operating systems.
| v Change the behavior of jobs and job streams based on when they are scheduled
| to run, that is, on which days they run.
| Scenario 9 part 1: Using variable tables to run different

| commands using the same job definition
| This part shows how you use variable tables to create two job streams containing
| the same job definition to launch two different commands. The scenario performs
| the following steps:
| v Creates two variable tables and defines variables inside them.
| v Uses variables inside jobs.
| v Defines two job streams
| v Associates a different variable table to each job stream.
| Commands used in the scenario in their run sequences:

| 1. "composer disp vartable=SMPL_VAR_TABLE_9_0_?" (display)
| 2. "composer disp job=SMPL_JOB_9_0_1" (display)
| 3. "composer disp sched=SMPL_SCHED_9_0_?" (display)
| 4. "conman sj SMPL_SCHED_9_0_1.SMPL_JOB_9_0_1;info" (showjobs)
| 5. "conman sj SMPL_SCHED_9_0_2.SMPL_JOB_9_0_1;info" (showjobs)
| Because the production plan has already been generated, you can see the following
| results:
| v The job added with the SMPL_SCHED_9_0_1 job stream contains the command
| to list the content of the TWSTutorial directory.
| v The job added with the SMPL_SCHED_9_0_2 job stream contains the command
| to list the content of the TWS directory.
| Scenario 9 part 2: Using variable tables to run different

| commands on different days
| This part shows how you use variable tables to have the same job stream
| containing two run cycles to launch two commands based on variable substitution.
| It create a job stream containing a job definition and two different run cycles that
| address two different variable tables. The scenario performs the following steps:
| v Creates two variable tables and defines variables inside them.
| v Uses variables inside jobs.
| v Defines a job stream.
| v Associates a different variable table to each run cycle.
| Commands used in the scenario in their run sequence:

| 1. "composer disp vartable=SMPL_VAR_TABLE_9_0_?" (display)
| 2. "composer disp vartable=MAIN_TABLE" (display)
| 3. "composer disp job=SMPL_JOB_9_1_1" (display)
| 4. "composer disp sched=SMPL_SCHED_9_1_1" (display)
| 5. "conman sj SMPL_SCHED_9_1_1(1000).SMPL_JOB_9_1_1;info (showjobs)
| 6. "conman sj SMPL_SCHED_9_1_1(1200).SMPL_JOB_9_1_1;info (showjobs)
| Because the production plan has already been generated, you can see the following
| results:
| v The job stream added for the run cycle associated to the
| SMPL_VAR_TABLE_9_0_2 variable table contains the SMPL_JOB_9_1_1 job that
| launches the default command.
| v The job stream added for the run cycle associated to the
| SMPL_VAR_TABLE_9_0_1 variable table contains the SMPL_JOB_9_1_1 job that
| launches the command specified within the variable table.
Removing tutorial objects from the database

You can choose to keep the database objects in your environment to use them as
templates for new objects. If, instead, you want to completely remove all tutorial
objects from the database, perform the following steps:
1. Go to the TWS_home/TWS/TWSTutorial directory, where TWS_home is the home
directory of the user for which you installed Tivoli Workload Scheduler.
2. Launch the tutorial utility installation script as follows:
v In a Windows environment:
SAMPLEDBSETUP.CMD -uninstall
v In a UNIX environment:
sampledbsetup.sh -uninstall

Appendix A. Registry file
On UNIX operating systems, when you install Tivoli Workload Scheduler using the
InstallShield wizard or the twsinst script, a check is performed to determine
whether there are other Tivoli Workload Scheduler instances already installed. The
TWSRegistry.dat file stores the history of all instances installed. On Windows
operating systems, this file is stored under the system drive directory, for example,
c:\winnt\system32. On UNIX operating systems, this file is stored in the /etc/TWS
path. The file contains the values of the following attributes that define a Tivoli
Workload Scheduler installation:
Table 29. Registry file attributes
Attribute Value
ProductID TWS_ENGINE
PackageName The name of the software package used to
perform the installation.
InstallationPath The absolute path of the Tivoli Workload
Scheduler instance.
UserOwner The owner of the installation.
MajorVersion Tivoli Workload Scheduler version number.
MinorVersion Tivoli Workload Scheduler release number.
MaintenanceVersion Tivoli Workload Scheduler maintenance
version number.
PatchVersion The latest product patch number installed.
Agent Any one of the following: standard agent,
fault-tolerant agent, master domain manager.
FeatureList The list of optional features installed.
LPName The name of the software package block that
installs the language pack.
LPList A list of all languages installed for the
instance installed.
The following is an example of a TWSRegistry.dat file on a master domain

manager:
/Tivoli/Workload_Scheduler/tws_nord_DN_objectClass=OU
/Tivoli/Workload_Scheduler/tws_nord_DN_PackageName=FP_Windows_tws_nord.8.3.00
/Tivoli/Workload_Scheduler/tws_nord_DN_MajorVersion=8
/Tivoli/Workload_Scheduler/tws_nord_DN_MinorVersion=2
/Tivoli/Workload_Scheduler/tws_nord_DN_PatchVersion=
/Tivoli/Workload_Scheduler/tws_nord_DN_FeatureList=TBSM
/Tivoli/Workload_Scheduler/tws_nord_DN_ProductID=TWS_ENGINE
/Tivoli/Workload_Scheduler/tws_nord_DN_ou=tws_nord
/Tivoli/Workload_Scheduler/tws_nord_DN_InstallationPath=c:\TWS\tws_nord
/Tivoli/Workload_Scheduler/tws_nord_DN_UserOwner=tws_nord
/Tivoli/Workload_Scheduler/tws_nord_DN_MaintenanceVersion=1
/Tivoli/Workload_Scheduler/tws_nord_DN_Agent=MDM

Tutorials

|
| Appendix B. Response file properties

| This appendix describes the properties in the various response files used in the
| silent installation of Tivoli Workload Scheduler and Tivoli Dynamic Workload
| Console The following information is provided:
| v “General”
| v “Tivoli Workload Scheduler response file properties”
| v “Tivoli Dynamic Workload Console response file properties” on page 319
|
| General
| All components of Tivoli Workload Scheduler and Tivoli Dynamic Workload
| Console that can be installed by the InstallShield wizard can also be installed
| silently, using a response file. A response file is a flat text list of property-value
| pairs each of which corresponding to a data item that the wizard needs to
| determine what is to be installed, where, and with what configuration. Silent
| installations can be used to install, upgrade or uninstall components locally, or
| remotely.
| Tivoli Workload Scheduler and Tivoli Dynamic Workload Console components are
| provided with template response files, containing the appropriate properties to
| perform one installation, upgrade, or uninstallation action.
| To perform a silent installation, provide the following command line arguments

| when running the wizard:
| -options "<response_file_name> -silent
| The provided files are template files, so you are recommended to edit the
| properties appropriately, and then save a copy of the file with a file name which
| identifies the component to be installed and the system on which it is to be
| installed.
| The properties have unique names and uses, and are described in the following
| sections. Many of them will contain default values that you can use. The defaults
| are not listed here as they may change, depending on which template file they are
| used in.
| Note: Where the same template file is provided for Windows and UNIX platforms,
| default paths are supplied for both environments, with the keys duplicated
| and one commented out. Note that if you uncomment one and omit to
| comment the other, the wizard will utilize the last of the duplicated keys.
|
| Tivoli Workload Scheduler response file properties
| This section describes the properties used in the Tivoli Workload Scheduler
| response files, in alphabetical order:
| Notes:
| 1. All values must be written between double quotation marks ("), for example:
| cpuCfgPanel.addFINAL="true"
| 2. Properties are written in mixed case for ease of reading, but are not
| case-sensitive

Response file properties: Tivoli Workload Scheduler
| 3. Keywords (for example, "true") used in values, are not case-sensitive.

| Table 30. Tivoli Workload Scheduler response file properties
| Name Description Permitted values
| cpuCfgPanel. Add the final job stream to the database. This
|| addFINAL option allows to perform automatic production
true Add the final job stream
| plan extension at the end of each current false Do not add the final job
| production plan processing. By default, this stream
| box remains unchecked. This option is
| available only if you are installing a master
| domain manager.
| cpuCfgPanel. Company name. See “Tivoli Workload Scheduler
| company steps” on page 32.
|
| cpuCfgPanel. The workstation name of the master domain See “Tivoli Workload Scheduler
| masterCPU manager workstation. When you are installing steps” on page 32.
| a master domain manager, this value must
| have the same value as cpuCfgPanel.thisCPU.
| cpuCfgPanel. The port used by netman on the system on See “Tivoli Workload Scheduler
| tcpPortNumber which the component is installed. steps” on page 32.
|
| cpuCfgPanel. The workstation name of the workstation See “Tivoli Workload Scheduler
| thisCPU where you are installing the component. When steps” on page 32.
| you are installing a master domain manager,
| this value must have the same value as
| cpuCfgPanel.masterCPU.
| db2CheckPrereqs. The installation directory of the DB2 Enterprise See “RDBMS steps” on page 35.
| db2Directory Server or the DB2 Administration Client.
|
| db2ClientCfg. The remote node of the DB2 Administration See “RDBMS steps” on page 35.
| remoteNode Client.
|
| db2ClientCfg. The TCP/IP port number that the remote DB2 See “RDBMS steps” on page 35.
| remotePort server instance uses to communicate.
|
| db2ClientCfg. The user name of the administrator of the DB2 See “RDBMS steps” on page 35.
| db2AdminUser server instance.
|
| db2ClientCfg. The password of the DB2 server administrator See “RDBMS steps” on page 35.
| db2AdminPwd user, or of the user with SYSADM or SYSCTRL
| authority.
|
| db2ClientCfg. The user name of the DB2 administrator of the See “RDBMS steps” on page 35.
| db2LocalAdminUser DB2 client instance.

| Table 30. Tivoli Workload Scheduler response file properties (continued)

| db2ClientCfg. The password of the DB2 administrator of the See “RDBMS steps” on page 35.
| db2LocalAdminPwd DB2 client instance.
|
| db2ClientCfg. The user name of the DB2 user. See “RDBMS steps” on page 35.
| twsDBUser
|
| db2ClientCfg.twsDBPwd The password of the DB2 user. See “RDBMS steps” on page 35.
|
| db2ServerCfg. The name of the DB2 server instance. See “RDBMS steps” on page 35.
| instanceName
|
| db2ServerCfg.instancePort The TCP/IP port number used to See “RDBMS steps” on page 35.
| communicate with the DB2 instance.
|
| db2ServerCfg. The user name of the administrator of the DB2 See “RDBMS steps” on page 35.
| db2AdminUser Server.
|
| db2ServerCfg. The password of the DB2 server administrator See “RDBMS steps” on page 35.
| db2AdminPwd user, or of the user with SYSADM or SYSCTRL
| authority.
|
| InstallationActions. Tivoli Workload Automation instance choice
|| Install_Method new Install the Tivoli Workload
|| Many of the Tivoli Workload Scheduler Scheduler component in a
|| components, including Tivoli Dynamic new instance of Tivoli
|
|| Workload Console, must be installed in an Workload Automation (and
|| instance of Tivoli Workload Automation (see install the infrastructure
|| “Installation paths and product instances” on support)
|| page 18 for an explanation). This property lets ONTWA
|| you choose whether you want to install the Install the Tivoli Workload
|| component in a new instance (installing also Scheduler component in an
|| the embedded WebSphere Application Server existing instance of Tivoli
|| and other infrastructure support), or to install Workload Automation
| the component in an existing instance.
| In the former case, the path you want to use

| for the new instance must be defined in the
| property twsLocationPanel.directory. In the
| latter case you must also identify the path of
| the existing instance, using the property:
| InstallationActions.
| TWA_INSTANCE_PATH
| InstallationActions. The command-line client is registered by TWS It has the following format:
| instanceID with an ID. When you upgrade an instance <remoteHost>:<remoteUser>
| you have to supply this ID.
|
Appendix B. Response file properties 313


| InstallationActions. Tivoli Workload Automation instance path See “Tivoli Workload Scheduler
| TWA_INSTANCE_PATH steps” on page 32.
| Identifies the path where an instance of Tivoli
|| Workload Automation has already been
| installed.
| InstallationActions. The existing TWSUser
| twsUser
| Identifies the TWSUser of an existing
|| component you are upgrading.
| installationComponents. Tivoli Workload Automation instance type.

|| instanceType mdm master domain manager
|| The type of component to install. bkm backup master domain
| manager
| fta agent or domain manager
| cli command-line client
| installLocation Installation path for the Integration Any fully qualified path outside an
| Workbench. instance of Tivoli Workload
| Automation.
| IsOnlyFTAConnector Specify which component is to be uninstalled.
|| ToUninstall. Yes Uninstall just the distributed
|| IsOnlyFTAConnector connector.
| No Uninstall the agent and the
|| distributed connector.
| licenseAccepted Accept license agreement
| true To accept the license
|| To install a component using a response file agreement.
|
|| you must explicitly accept the license false To not accept the license
|| agreement, a copy of which is in the License agreement. In this event the
|| directory of the product install media (DVD or component is not installed.
| downloaded image).
| oracleCheckPrereqs. The installation directory of the Oracle See “Installing for an Oracle
| oracleDirectory database. database” on page 38.
|
| oracleServer The name used by clients to identify an Oracle See “Installing for an Oracle
| CommunicationInfo. Net server and the specific system identifier or database” on page 38.
| netServiceName database for the Oracle Net connection.
|
| oracleServer The database administrator user name (such as See “Installing for an Oracle
| CommunicationInfo. SYSTEM) required to authenticate to the Oracle database” on page 38.
| oracleAdminUser database.
|
| oracleServer The database administrator user password See “Installing for an Oracle
| CommunicationInfo. required to authenticate to the Oracle database. database” on page 38.
| oracleAdminPwd


| SDK_ECLIPSE_BUNDLED Integration Workbench is to be installed with
|| the bundled version of Eclipse.
true To install Integration
| Workbench with the
|
|| Whichever setting you choose, the property bundled version of Eclipse
|| SDK_UPDATESITE must have the opposite false To not install Integration
|| setting. Workbench with the
| bundled version of Eclipse.
| SDK_UPDATESITE Integration Workbench is to be installed as an
|| Eclipse site, without the bundled version of
true To install Integration
|| Eclipse.
Workbench as an Eclipse
| site, without the bundled
|| Whichever setting you choose, the property version of Eclipse
|| SDK_ECLIPSE_BUNDLED must have the opposite false To not install Integration
|| setting. Workbench as an Eclipse site
| selectRDBMSPanel. Choose which type of RDBMS support you "DB2" or "Oracle", not case-sensitive.
| rdbmsSelected want to use, DB2 or Oracle
|
| twsCliCfgPanel. Password of the user identified in
| password twsCliCfgPanel.user
|
| twsCliCfgPanel. The host name or IP address of the
| remoteHost workstation where the master domain
| manager is installed.
|
| twsCliCfgPanel. The listening port of the workstation where the
| remotePort master domain manager is installed.
|
| twsCliCfgPanel. The user ID used to access the master domain
| user manager. Usually the <TWS_user>.
|
| TWSCLILanguagesPanel. Choose command-line client languages: all
|| all languages
true All languages are installed.
| false You want to install specific
|| When installing the language pack on the languages using the
|| command-line client, you can select to install properties below.
| all languages, using this property, or select the
| specific languages you require (see following
| property)
| TWSCLILanguagesPanel. Choose command-line client languages: For each property:
| chineseSimplified specific languages
|| chineseTraditional true The selected language is
|| german When installing the language pack on the installed.
|| french command-line client, you can select to install false The selected language is not
|| italian all languages, using the previous property, or
|| japanese installed.
| select the specific languages you require, using
|| korean
one or more of these properties.
| portuguese
| spanish


| twsCLILocationPanel. The path where you want to install the Any valid, fully qualified path
| directory command-line client. outside any instance of Tivoli
| Workload Automation.
|
| twsDBCfg.dbName The name of the DB2 database. See “RDBMS steps” on page 35.
|
| twsDBCfg.tablespaceName The name of the DB2 instance tablespace. See “RDBMS steps” on page 35.
|
| twsDBCfg.tablespacePath The relative path of the DB2 table space. See “RDBMS steps” on page 35.
|
| twsDBCfg. The name of the table space for storing report See “RDBMS steps” on page 35.
| reportTablespaceName data.
|
| twsDBCfg.report The path of the table space for storing report See “RDBMS steps” on page 35.
| TablespacePath data.
|
| twsLocationPanel. The path where you want to install the fresh Any valid, fully qualified Tivoli
| directory Tivoli Workload Scheduler component. Workload Automation instance path.
|
| twsLocationPanel. Choose whether to create symbolic links (see
|| symLinkOption “Symlink options” on page 24 for more details.
true Symbolic links are created.
| false Symbolic links are not
| created.
| twsOracleDbCfg. The owner of the Tivoli Workload Scheduler See “Installing for an Oracle
| twsDBUser schema. database” on page 38.
|
| twsOracleDbCfg. The database administrator user password See “Installing for an Oracle
| twsDBPwd required to authenticate to the Oracle database. database” on page 38.
|
| twsOracleDbCfg. The name that identifies the Tivoli Workload See “Installing for an Oracle
| twsDataTablespace Scheduler data table space. database” on page 38.
|
| twsReportTablespace Scheduler table space where report data is to database” on page 38.
| be stored.
|
| twsTempTablespace Scheduler temporary table space. database” on page 38.


| twsOracleDbCfg. Specify whether the event-driven workload
|| isPartitioned automation database schema is to be created
true The Oracle Partitioning
|| using the Oracle Partitioning feature.
feature is used when
|| creating the event-driven
| workload automation
| database schema.
| false The Oracle Partitioning
| feature is NOT used when
| creating the event-driven
| workload automation
| database schema.
| twsPortsPanel. Administration HTTP transport port See “WebSphere Application Server
| portAdmin steps” on page 34 for more details.
|
| twsPortsPanel. Administration HTTPS transport port See “WebSphere Application Server
| portAdminSec steps” on page 34 for more details.
|
| twsPortsPanel. Event processor port See “WebSphere Application Server
| portEif steps” on page 34 for more details.
|
| twsPortsPanel. HTTP transport port See “WebSphere Application Server
| portHTTP steps” on page 34 for more details.
|
| twsPortsPanel. HTTPS transport port See “WebSphere Application Server
| portHTTPS steps” on page 34 for more details.
|
| twsPortsPanel. CSIV2 Client Authentication Listener port See “WebSphere Application Server
| portMtlAuth steps” on page 34 for more details.
|
| twsPortsPanel. ORB Listener port See “WebSphere Application Server
| portORB steps” on page 34 for more details.
|
| twsPortsPanel. Bootstrap port See “WebSphere Application Server
| portRMI steps” on page 34 for more details.
|
| twsPortsPanel. SAS Server Authentication Listener port See “WebSphere Application Server
| portSAS steps” on page 34 for more details.
|
| twsPortsPanel. SOAP connector port See “WebSphere Application Server
| portSOAP steps” on page 34 for more details.


| twsPortsPanel. CSIV2 Server Authentication Listener port See “WebSphere Application Server
| portSrvAuth steps” on page 34 for more details.
|
| twsUpgradePanel. Determines if the existing instance of a
|| backupOldInstance component is to be backed up during an
true The existing instance is
|| upgrade.
backed up.
| false The existing instance is not
| backed up.
| twsUpgradePanel. The backup directory used if the existing Any valid fully qualified path
| bckpDirectory instance of a component is to be backed up outside the path of any existing
| during an upgrade. Tivoli Workload Scheduler
| component.
| twsUpgradePanel. The backup directory for the application server Any valid fully qualified path
| bckpProfileDirectory profile (used when upgrading the master outside the path of any existing
| domain manager or backup master domain Tivoli Workload Scheduler
| manager from version 8.3 or 8.4). component.
| twsUpgradePanel. The migration directory used when upgrading Any valid fully qualified path
| dumpDirectory a master domain manager from version 8.2.x. outside the path of any existing
| The Mozart database is exported to this Tivoli Workload Scheduler
| directory as flat text files, and then imported component.
| into the new RDBMS support.
| userUnixCfgPanel. The user ID of the <TWS_user> (on UNIX). The ID must already exist on the
| inputUserName system where the silent wizard will
| be run.
|
| userUnixCfgPanel. The password of the <TWS_user> (on UNIX).
| twsPassword
| userUnixCfgPanel. If the Tivoli Dynamic Workload Console has This will normally be the password
| wasPassword already been installed on an existing instance of the <TWS_user>, unless you have
| of Tivoli Workload Automation, supply the changed it in the embedded
| password of the WebSphere Application Server WebSphere Application Server.
| user ID of the embedded WebSphere
| Application Server that you configured when
| you installed Tivoli Dynamic Workload
| Console (on UNIX).
| userUnixCfgPanel. If the Tivoli Dynamic Workload Console has This will normally be the
| wasUserName already been installed on an existing instance <TWS_user>, unless you have
| WebSphere Application Server user ID of the WebSphere Application Server.
| embedded WebSphere Application Server that
| you configured when you installed Tivoli
| Dynamic Workload Console (on UNIX).
| userWinCfgPanel. The ID of the <TWS_user> - the user that will If this user does not already exist, it
| inputUserName ″own″ the agent on the agent workstation (on will be created. In this case, the
| Windows). format of the ID must follow the
| rules for User IDs on the computer
| where it is to be created.
| userWinCfgPanel. The password of the <TWS_user> (on If the user is to be created, the format
| twsPassword Windows). of the password must follow the
| rules for passwords on the computer
| where it is to be created.


| userWinCfgPanel. If the Tivoli Dynamic Workload Console has This will normally be the password
| wasPassword already been installed on an existing instance of the <TWS_user>, unless you have
| password of the WebSphere Application Server WebSphere Application Server.
| user ID of the embedded WebSphere
| Application Server that you configured when
| you installed Tivoli Dynamic Workload
| Console (on Windows).
| userWinCfgPanel. If the Tivoli Dynamic Workload Console has This will normally be the
| wasUserName already been installed on an existing instance <TWS_user>, unless you have
| WebSphere Application Server user ID of the WebSphere Application Server.
| embedded WebSphere Application Server that
| you configured when you installed Tivoli
| Dynamic Workload Console (on Windows).
|
|
| Tivoli Dynamic Workload Console response file properties
| This section describes the properties used in the Tivoli Dynamic Workload Console
| response files, in alphabetical order:
| Notes:
| 1. All values must be written between double quotation marks ("), for example:
| InstallationActions.INSTALL_METHOD="new"
| 2. Property names are written in mixed case for ease of reading, but are not
| case-sensitive
| 3. Keywords used in values are not case-sensitive.
| Table 31. Tivoli Dynamic Workload Console response file properties
| BOOTSTRAP_ADDRESS The bootstrap port. See “Advanced installation” on page
| 259 for more details.
|
| CREATE_WAS_SERVICE On Windows, the embedded WebSphere
|| Application Server can be defined to start
true A Windows service is
|| automatically at system startup. To do this, set
created to automatically start
|| this property, which creates a Windows service
the embedded WebSphere
|| that starts up the embedded WebSphere
Application Server
| Application Server. false The Windows service is not
| created
| CSIV2_SSL_MUTUALAUTH CSIV2 Client Authentication Listener port. See “Advanced installation” on page
| _LISTENER_ADDRESS 259 for more details.
|
| CSIV2_SSL_SERVERAUTH CSIV2 Server Authentication Listener port See “Advanced installation” on page

Response file properties: Tivoli Dynamic Workload Console
| Table 31. Tivoli Dynamic Workload Console response file properties (continued)
| ENABLE_TDWB Enable Tivoli Dynamic Workload Broker
| true Gives the administrator
|| Tivoli Dynamic Workload Console can be used access to Tivoli Dynamic
|
|| to access either of the following products: Workload Broker
| v Tivoli Workload Scheduler (includes Tivoli false Denies the administrator
| Workload Scheduler for z/OS) access to Tivoli Dynamic
|| v Tivoli Dynamic Workload Broker Workload Broker
| All users must be given specific access to one

| or both of these products.
| It is useful to give these access rights to the

| WebSphere Application Server administrator
| from the outset, so that the administrator can
| immediately perform any tasks that might be
| required:
| ENABLE_TWS Enable Tivoli Workload Scheduler
| true Gives the administrator
|| See the description of "ENABLE_TDWB" access to Tivoli Workload
|
| Scheduler
| false Denies the administrator
| access to Tivoli Workload
| Scheduler
| INSTALL_METHOD Installation instance choice
| new Install the Tivoli Dynamic
|| The Tivoli Dynamic Workload Console must be Workload Console in a new
||
| installed in an instance of Tivoli Workload instance of Tivoli Workload
|| Automation (see “Installation paths and Automation (and install the
|| product instances” on page 18 for an infrastructure support). Use
|| explanation). This property lets you choose this value also when
|| whether you want to install the component in upgrading an existing
|| a new instance (installing also the embedded instance of Tivoli Dynamic
|| WebSphere Application Server and other Workload Console.
|| infrastructure support), or an existing instance. ONTWA
| Install the Tivoli Dynamic
| In the former case, the path you want to use
| Workload Console in an
| for the new instance must be defined in the
| existing instance of Tivoli
| property IS_DESTINATION. In the latter case you
| Workload Automation
| must also identify the path of the existing
| instance, using the property: onwas Install the Tivoli Dynamic
| TWA_INSTANCE_PATH Workload Console on your
| own external supported
|| This property also lets you install the Tivoli version of WebSphere
|| Dynamic Workload Console outside the Tivoli Application Server
| Workload Automation structure, on your own
| external supported version of WebSphere
| Application Server. In this case, the path must
| be supplied using the property
| ISC_APPSERVER_DIR

| IS_BACKUP_DIR Backup directory for upgrade Any valid, fully qualified path
| outside: any existing instance of
| When upgrading the Tivoli Dynamic Workload Tivoli Workload Automation, and the
| Console, the wizard needs to back up the installation path of the Embedded
| application server configuration while it is Version of WebSphere Application
| upgrading the Embedded Version of Server
| WebSphere Application Server (part of the
| Tivoli Dynamic Workload Console upgrade
| process).
| IS_DESTINATION Console installation path Any valid, fully qualified path
| outside any existing instance of Tivoli
|| On a new instance of Tivoli Workload Workload Automation.
| Automation: the path of a new instance of
| Tivoli Workload Automation where the Tivoli
| Dynamic Workload Console is to be installed.
| On your existing external instance of

| WebSphere Application Server: when
| installing the Tivoli Dynamic Workload
| Console on your own external version of
| WebSphere Application Server, supply the
| console installation path.
| This does not have to be a path related to the

| instance of the WebSphere Application Server
| on which you are going to install it. The path
| must not be within an instance of Tivoli
| Workload Automation:
| IS_UPGRADE Boolean property that determines whether the
|| true The wizard will use the
wizard is being run to upgrade an existing
|| instance.
supplied properties to
| upgrade an existing instance
| of Tivoli Dynamic Workload
| Console
| false The wizard will use the
| supplied properties to install
| an instance of Tivoli
| Dynamic Workload Console
| ISC_ADMIN_FULL_USER Your WebSphere Application Server The user ID must exist.
| administrator user ID
|
| On a new instance of Tivoli Workload
| Automation: supply the user ID to be used for
| the Integrated Solutions Console
| administration user

| installing, upgrading, or uninstalling the Tivoli
| Dynamic Workload Console on your own
| external version of WebSphere Application
| Server, supply the existing user ID of the
| Integrated Solutions Console administration
| user.

| ISC_ADMIN_PASSWORD Your WebSphere Application Server
| administrator user password
|
| On a new instance of Tivoli Workload
| Automation: supply the password to be used
| for the Integrated Solutions Console
| administration user

| installing, upgrading, or uninstalling the Tivoli
| Dynamic Workload Console on your own
| external version of WebSphere Application
| Server, supply the password of the user ID of
| the existing Integrated Solutions Console
| administration user.
| ISC_APPSERVER_DIR Existing instance installation directory See “Installing on your existing
| instance of WebSphere Application
| The installation directory of the external Server” on page 260 for more details.
| Integrated Solutions Console on which Tivoli
| Dynamic Workload Console must be installed
| or upgraded.
| licenseAccepted Accept license agreement
| true To accept the license
|| To install the Tivoli Dynamic Workload agreement.
|
|| Console using a response file you must false To not accept the license
|| explicitly accept the license agreement, a copy agreement. In this event the
|| of which is in the License directory of the Tivoli Dynamic Workload
|| product install media (DVD or downloaded Console is not installed.
| image).
| ORB_LISTENER_ADDRESS ORB Listener port See “Advanced installation” on page
|
| SAS_SSL_SERVERAUTH SAS SSLPort See “Advanced installation” on page
|
| SOAP_CONNECTOR_ADDRESS SOAP connector port See “Advanced installation” on page
|
| TWA_INSTANCE_PATH Existing Tivoli Workload Automation instance Any valid, fully qualified Tivoli
| path Workload Automation instance path.
|
| The path of an existing instance of Tivoli
| Workload Automation where the Tivoli
| Dynamic Workload Console is to be installed.
| UPDATE_INSTALLER_DIR The WebSphere Application Server update See “Installing on your existing
| installer path instance of WebSphere Application
| Server” on page 260 for more details.
| The directory of the external WebSphere
| Application Server update installer.
| WAS_CELL_NAME The WebSphere Application Server cell name See “Installing on your existing
|| The external WebSphere Application Server Server” on page 260 for more details.
| cell name.

| WAS_NODE_NAME The WebSphere Application Server node name See “Installing on your existing
| The external WebSphere Application Server Server” on page 260 for more details.
| node name.
| WAS_PROFILE_NAME The WebSphere Application Server profile See “Installing on your existing
| name instance of WebSphere Application
| The external WebSphere Application Server
| profile name.
| WAS_SERVER_NAME The WebSphere Application Server server See “Installing on your existing
| name instance of WebSphere Application
| The external WebSphere Application Server
| server name.
| WC_adminhost Administrative console See “Advanced installation” on page
|
| WC_adminhost_secure Administrative Console Secure See “Advanced installation” on page
|
| WC_defaulthost HTTP transport See “Advanced installation” on page
|
| WC_defaulthost_secure HTTPS transport See “Advanced installation” on page
|
|
|

Tutorials

|
| Appendix C. Installing Tivoli Workload Scheduler Integration

| Workbench
| Use Tivoli Workload Scheduler Integration Workbench to develop event and action
| plug-ins that extend the capabilities of Tivoli Workload Scheduler event-driven
| workload automation. You can also create Java applications that use the Tivoli
| Workload Scheduler Java API.
| You can install Tivoli Workload Scheduler Integration Workbench with the bundled
| version of Eclipse or with an existing instance of Eclipse. This appendix is
| composed of the following sections:
| v “Installing Tivoli Workload Scheduler Integration Workbench with the bundled
| version of Eclipse”
| v “Installing Tivoli Workload Scheduler Integration Workbench with an existing
| instance of Eclipse”
| Note: If you are working with an exported display, to access the Tivoli Workload
| Scheduler Integration Workbench readme file you must have a browser
| running first.
|
| Installing Tivoli Workload Scheduler Integration Workbench with the
| bundled version of Eclipse
| If you do not have the required version of Eclipse on your computer, you can
| install Tivoli Workload Scheduler Integration Workbench bundled with Eclipse for
| local use.
| To install Tivoli Workload Scheduler Integration Workbench with the bundled

| version of Eclipse, perform the following:
| From the installation DVD, navigate to the IntegrationWorkbench directory and

| run the setup file appropriate to your operating system. Alternatively, start the
| launchpad as described in “Launchpad” on page 13 and select the Tivoli Workload
| Scheduler Integrations Workbench installation.
| Follow the prompts to complete the installation wizard. When prompted, select the
| option: Install Integration Workbench.
|
| Installing Tivoli Workload Scheduler Integration Workbench with an
| existing instance of Eclipse
| If you have the required version of Eclipse, you can install Tivoli Workload
| Scheduler Integration Workbench as a plug-in on the existing instance. Users across
| the network can access Tivoli Workload Scheduler Integration Workbench as an
| Eclipse site.
| If you already have Eclipse on your computer, you can install Tivoli Workload
| Scheduler Integration Workbench as a plug-in for an existing instance of Eclipse.
| To install the current version of Tivoli Workload Scheduler Integration Workbench
| into your existing instance of Eclipse, perform the following:

Tivoli Workload Scheduler Integration Workbench
| From the installation DVD, navigate to the IntegrationWorkbench directory and

| run the setup file appropriate to your operating system. Alternatively, start the
| launchpad as described in “Launchpad” on page 13 and select the Tivoli Workload
| Scheduler Integrations Workbench installation.
| Follow the prompts to complete the installation wizard. When prompted, select the
| option: Install Eclipse site.
| Note: To understand how to use the plug-in, see the readme document in Eclipse.
|

|
| Appendix D. Discovering installed products

| If you do not know what products are installed in an instance of Tivoli Workload
| Automation, perform the following procedure to discover what products are
| installed:
| Open a command prompt and change to the following directory on the Tivoli
| Workload Scheduler DVD for the operating system of the computer (if you have
| copied it to hard disk, go to that location): <drive>/<operating_system>/CLI
| Run the following to initialize the Tivoli Configuration Manager environment:

| swd_env.bat/.sh
| Run the following software distribution command to verify which software

| packages have been installed:
| wdlssp
| A list of the software packages is displayed, similar to the following:

| ----------------------------------------
|
| DISSE0164I Name : FP_TWS_WINDOWS_TWS_user
| DISSE0166I State : ICU--
|
| ----------------------------------------
|
| DISSE0164I Name : TWS_LP_TWS_user
| DISSE0166I State : ICU--
|
| ----------------------------------------
| The details of the packages in the list will depend on which packages have been
| installed on this computer. In this case, on a Windows computer, an installation for
| a <TWS_user> called <TWS_user> has been made of the software package blocks
| for the Tivoli Workload Scheduler scheduling engine and the scheduling engine
| National Language Support (LP = Language Pack). The value of State depends on
| whether the package has yet been "committed".
| Run the following to remove a software package:

| wdrmvsp -f <package_name>.<package_version>
| This command does not remove the log files and configuration files used by Tivoli
| Configuration Manager. These remain either within the Tivoli Workload Scheduler
| installation directory, or the system temporary directory.
| Note: If you experience any problem running these commands, or to understand

| more about Tivoli Configuration Manager, consult its documentation, which
| can be found online at http://publib.boulder.ibm.com/tividd/td/
| ConfigurationManager4.2.3.html.
|

Tutorials

|
| Appendix E. Files backed up during upgrade

| During an upgrade, some files will be backed up into a .bk file. For example, the
| file tws_env.cmd will be backed up into the file tws_env.cmd.bk. These backed up
| file are replaced with new files. The following is a list of files backed up during
| the upgrade.
| Windows
| v tws_env.cmd
| v jobmanrc.cmd
| v TWSCCLog.properties (this file is not replaced)
| v Startup.cmd
| v JnextPlan.cmd
| v MakePlan.cmd
| v SwitchPlan.cmd
| v CreatePostReports.cm
| v UpdateStats.cmd
| v ResetPlan.cmd
| v Sfinal
| UNIX
| v tws_env.sh
| v tws_env.csh
| v jobmanrc
| v TWSCCLog.properties (this file is not replaced)
| v StartUp
| v JnextPlan
| v MakePlan
| v SwitchPlan
| v CreatePostReports
| v UpdateStats
| v ResetPlan
| v Sfinal

Tutorials

|
| Appendix F. DB2 tablespace relative paths

| When you create a DB2 tablespace with a relative path, the path is constructed in
| the following way:
| DFTDBPATH\DB2_instance\NODE0000\SQLnnnnn\TABLESPACE_REL_PATH
| where:
| DFTDBPATH
| For Windows operating systems, this is the drive where the DB2 instance is
| installed. For UNIX and Linux operating systems, this is the home instance
| of the DB2 installation.
| DB2_instance
| Is the name of the DB2 instance.
| NODE0000
| Is the directory where DB2 database instances are located.
| SQLnnnn
| Is an incremental directory path that depends on the number of database
| instances.
| TABLESPACE_REL_PATH
| Is the relative path you specified for the tablespace.
| For more information about tablespace relative paths, refer to the DB2
| documentation set.

Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this publication
in other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user’s responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this publication. The furnishing of this publication does not give you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation

Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS

PUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in certain

transactions, therefore, this statement might not apply to you.
This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758 U.S.A.
Such information may be available, subject to appropriate terms and conditions,

including in some cases payment of a fee.
The licensed program described in this publication and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.
Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
Notices and information about vendor products, components, and

code
Notices and information about vendor products, components, and code can be
found by accessing the Tivoli Workload Scheduler Information Center at
http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/
com.ibm.tivoli.itws.doc/welcome.htm, and selecting the Notices item. This displays
an HTML page containing this information for both Tivoli Workload Scheduler and
the Tivoli Dynamic Workload Console.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corporation in the United States, other countries,
or both. If these and other IBM trademarked terms are marked on their first
occurrence in this information with a trademark symbol (® or ™), these symbols
indicate U.S. registered or common law trademarks owned by IBM at the time this
information was published. Such trademarks may also be registered or common
law trademarks in other countries. A current list of IBM trademarks is available on
the Web at ″Copyright and trademark information″ at http://www.ibm.com/legal/
copytrade.shtml.

Adobe®, Acrobat, PostScript® and all Adobe-based trademarks are either registered
trademarks or trademarks of Adobe Systems Incorporated in the United States,
other countries, or both.
Intel®, Intel logo, Intel Inside®, Intel Inside logo, Intel Centrino®, Intel Centrino
logo, Celeron®, Intel Xeon®, Intel SpeedStep®, Itanium®, and Pentium® are
trademarks or registered trademarks of Intel Corporation or its subsidiaries in the
United States and other countries.
Java and all Java-based trademarks and logos are trademarks or

registered trademarks of Sun Microsystems, Inc. in the United States,
other countries, or both.
Linux is a trademark of Linus Torvalds in the United States, other countries, or

both.
Microsoft and Windows are registered trademarks of Microsoft Corporation in the

United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Other company, product, and service names may be trademarks or service marks
of others.
Notices 335
Index
Special characters available functions
for Tivoli Dynamic Workload
commands and scripts (continued)
twsinst, files not being correctly
.swdis, directory, removing 170 Broker 266 copied before running 149, 154
@ character in install directory name, for Tivoli Workload Scheduler 266 unlink
causing Tivoli Dynamic Workload AWSDEQ024E received in commit used before manual
Console uninstallation to fail 287 step 139 uninstallation 169
AWSFAB035E received 153 wconvcat 154
AWSFAB037E received 149 wdlssp, used before manual
Numerics AWSGAB005W received 139 uninstallation 169
4.2-SWDGW-F1P1 fix pack, compatibility AWSGAB566E received 154 wdrmvsp, used before manual
problem 153 AWSJCS011E message given 156 uninstallation 169
4.2-TCM-FP02 fix pack, to solve wlsinst 153
compatibility problem 153 commit step fails 154
56b - system error given during B communication problem between
consoles and master domain
installation 140 backup
manager 156
directory 151
component codes, used in message
backup package creation failed 151
A batch binary file, symbolic links not
numbers 175
composer
accessibility xii created 156
fails on Linux during migration, when
account creation batchman
launched 159
Windows 140 checking if active 169
configuration
Windows 2000 140 bc, utility required by InstallShield
for Tivoli Workload Scheduler Version
add feature installation fails 150 wizard on Linux 145
8.3 Fix Pack 3 263
agent books
connection
extended See publications
to Tivoli Dynamic Workload Broker
See extended agent BOOTSTRAP_ADDRESS response file
servers 267
fault-tolerant property 319
to Tivoli Workload Scheduler 266
See fault-tolerant agent connection to master domain manager
how to uninstall manually 166 fails 156
standard C connector
See standard agent cell name uninstalling manually on
Agent, registry attribute 309 WebSphere Application Server 261 Windows 172
AIX CLI connectors
installation problems 142 parameter, -installRoot, is invalid, uninstall manually 171
InstallShield wizard installation error given on Sun Solaris 145 conventions used in publications xii
fails 150 wdinstsp 52 cpuCfgPanel.addFINAL response file
APARs wimpspo 52 property 312
IY50574 165 cmd.exe, file, cannot be used by cpuCfgPanel.company response file
IY52481 141 Windows 2003 user 141 property 312
application server CMW3202E received 138 cpuCfgPanel.masterCPU response file
credentials problem when installing command line property 312
on Windows 140 See CLI cpuCfgPanel.tcpPortNumber response file
installation fails on Windows 2003 commands property 312
domain with credentials wdinstsp 52, 53 cpuCfgPanel.thisCPU response file
problem 147 wimpspo 52 property 312
installation log files 29, 256 commands and scripts CREATE_WAS_SERVICE response file
installation problem 146 ln property 319
profile creation fails 146 to link directories to the .swdis credentials problem causing installation
at binary file, symbolic links not directory 148, 151 of application server on Windows 2003
created 156 to link product files 156 domain to fail 147
attributes, registry file 309 makesec credentials problem for application server
authorization roles create Security file 166 when installing on Windows 140
installation wizard 15 ps, used before manual CSIV2_SSL_MUTUALAUTH_
Software Distribution 16 uninstallation 169 LISTENER_ADDRESS response file
twsinst 15 shut, used before manual property 319
Autotrace uninstallation 169 CSIV2_SSL_SERVERAUTH_
installation failure causes Tivoli stop LISTENER_ADDRESS response file
Workload Scheduler installation to used before manual property 319
fail 137 uninstallation 169 customer support
See Software Support

D E fix packs (continued)
4.2-TCM-FP02, to solve compatibility
datecalc binary file, symbolic links not education problem 153
created 156 See Tivoli technical training installing using Tivoli Configuration
DB2 ENABLE_TDWB response file Manager
installation log files 29 property 320 incompatibility problem 153
db2CheckPrereqs. db2Directory. response ENABLE_TWS response file insufficient disk space 151
file property 312 property 320 silent installation fails 148, 149
db2ClientCfg. remoteNode. response file end-to-end scheduling 24 format
property 312 error messages messages 175
db2ClientCfg. remotePort. response file definition 176
property 312 error writing file = , error message 148
db2ClientCfg. twsDBPwd. response file error writing file = 28, error
property 313 message 149 G
db2ClientCfg. twsDBUser. response file examples gateway component of software
property 313 language installation 54 distribution, incompatibility 153
db2ClientCfg.db2 AdminPwd. response registry file 309 global options, checking default
file property 312 explanation, message element 177 settings 166
db2ClientCfg.db2 AdminUser. response glossary xii
file property 312
db2ClientCfg.db2 LocalAdminPwd.
response file property 313
F H
FAB messages 236
db2ClientCfg.db2 LocalAdminUser. host name
FAF messages 244
response file property 312 not FQDN causing installation to fail
fault-tolerant domain manager
db2ServerCfg. instanceName response file on Linux 284
See domain manager
property 313 host name defined incorrectly on master
fault-tolerant switch manager
db2ServerCfg.db2Admin User response domain manager 156
See domain manager
file property 313 host name truncated causing installation
FeatureList, registry attribute 309
db2ServerCfg.db2AdminPwd response to fail, Windows 138
file names, case changed during
file property 313 HP-UX
copy 154
db2ServerCfg.instancePort response file installation problems 144
file sets
property 313 InstallShield wizard installation
See files
dependencies in jobs that must wait cannot install JRE 144
file system
before starting, the jobs are duplicated does not start 144
See files
after migration 161 fails 150
files
dependency error fails with a ″run error″ 144
/etc/password 113
given on migration but plan is hung installation on AIX 142
case changed during copy 154
OK 161
cmd.exe 141
directories
FINAL 117
.swdis, removing 170
backup 151
logs I
installation 125 informational messages, definition 176
swdis 151, 169
uninstallation 125 install
work 151
names, case changed during fix pack
disconnected command line, of Tivoli
copy 154 messages 244
Configuration Manager 153
not correctly copied before running InstallShield wizard
disk space
twsinst 149, 154 messages 177, 289
not enough for installation 154
Security messages
DISSE0005E received 151
checking existence of 166 fix pack 244
swdis.ini 53, 169, 170 InstallShield wizard 177, 289
Symphony 11 twsinst 236
temporary twsinst
domain manager
See temporary files messages 236
backup
twsinst, before running not being INSTALL_METHOD response file
See backup domain manager
correctly copied 149, 154 property 320
backup master
TWSRegistry.dat 169, 309 installation
See backup master domain
FINAL adding new features 42
manager
adding 117 advanced 259
master
final job stream AIX, problems 142
See master domain manager
adding 117 application server installation
domains
firewall stopping installation of Tivoli problems 146
topology
Dynamic Workload Console 284 CDs 254
multiple 10
fix pack checking
single 9
messages 244 See installation, verifying
DVDs 26
fix packs consoles cannot connect after upgrade
4.2-SWDGW-F1P1, compatibility from V8.2.1 156
problem 153 correcting a failed step and
continuing 131

installation (continued) installation (continued) installation methods
default 258 of Tivoli Dynamic Workload Console ISMP 14
DVDs 26 fails when installing on different Launchpad 13
example procedure for problem external WebSphere Application Software Distribution 14
resolving 135 Server profile 286 twsinst 14
fails of Tivoli Dynamic Workload Console, installation path 18
″Error writing file = ″ fails to start on Linux RHEL 5 installation wizard
received 148 (x86–64) 285 authorization roles 15
″Error writing file = 28″ on embedded WebSphere Application InstallationActions.Install_Method
received 149 Server 258 response file property 313
application server profile creation on existing instance of embedded InstallationActions.instanceID response
fails 146 WebSphere Application Server 260 file property 313
AWSDEQ024E error received 139 on existing WebSphere Application InstallationActions.TWA_ 314
AWSFAB037E error received 149 Server 260 InstallationActions.twsUser response file
CMW3202E error received 138 problem scenarios 136 property 314
host name truncated 138 problems installing on Windows 137 installationComponents.instanceType
InstallShield wizard on procedure for problem resolving 135 response file property 314
Windows 137 response file properties 311 InstallationPath, registry attribute 309
miscellaneous 154 resuming 134 installLocation response file
NoClassDefFoundError error 150 sample scenarios 252 property 314
recovery using wizard 125 security implications 165 installRoot not valid on Sun Solaris 145
software package block 151, 152 setup file 254 InstallShield wizard
Sun Solaris with error "command silent 44, 262 ″Add feature″ installation fails 150
line parameter, -installRoot, is fails with ″Error writing file = cannot install JRE on HP-UX 144
invalid" 145 ″ 148 cannot install JRE on Linux 145
UNIX with JVM validation fails with ″Error writing file = does not start on HP-UX 144
error 143 28″ 149 fails on AIX or HP-UX with a ″run
Windows because of of Tivoli Dynamic Workload error″ 150
Autotrace 137 Console, problems with 286 fails with ″run error″ 150
with error AWSFAB035E 153 troubleshooting 146 fails with a ″run error″ on
with error AWSGAB566E 154 silent, HP-UX 144
with error DISSE0324E 151 recovering 135 installation and uninstallation log
with installation image problem on software package blocks 50 files 28, 255
NFS mount 150 step list 126 messages 177, 289
from shared folder fails on step window 128 problem using with Tivoli Dynamic
Windows 284 step, failed, correcting and Workload Console 283
hangs (Tivoli Dynamic Workload continuing 131 recovering installation with 125
Console) 284 steps uninstallation fails on Windows 162
hangs on AIX 142 See steps, installation INSTANCE_PATH response file
HP-UX, problems 144 Sun Solaris, problems 145 property 314
images 254 Tivoli Configuration Manager, interactive wizard
in silent mode 253 fails 151, 152 problem using with Tivoli Dynamic
InstallShield wizard Tivoli Dynamic Workload Console log Workload Console 283
″Add feature″ installation files 281 internetwork dependencies 9
fails 150 troubleshooting 125 IS_BACKUP_DIR response file
does not start on HP-UX 144 troubleshooting scenarios 283 property 321
fails on HP-UX with a ″run twsinst IS_DESTINATION response file
error″ 144 fails 149 property 321
JRE does not install on fails with error AWSFAB035E 153 IS_UPGRADE response file
HP-UX 144 fails with error property 321
JRE does not install on Linux 145 AWSGAB566E 154 ISC_ADMIN_FULL_USER response file
Linux troubleshooting 146 property 321
start of Tivoli Workload Scheduler types 258 ISC_ADMIN_PASSWORD response file
gives errors 146 UNIX, problems 143 property 322
Linux, problems 145 upgrading 77 ISC_APPSERVER_DIR response file
log files 28, 125, 255 using launchpad 13, 253 property 322
log files, DB2 29 using response file 262 ISMP
log files, embedded WebSphere Using the installation wizard 31 See InstallShield wizard
Application Server 29, 256 using wizard 253, 257 IsOnlyFTAConnectorToUninstall.
methods 253 verifying 165 IsOnlyFTAConnector response file
miscellaneous problems 147 Windows receives warning property 314
of application server fails on Windows AWSGAB005W 139 IY50574, APAR 165
2003 domain with credentials wizard, rerunning or resuming 132 IY52481, APAR 141
problem 147 wizard, resuming now or later 133
Installation method
twsinst 48
Index 339
J Linux (continued)
InstallShield wizard installation
message format 175
messages
J2SE cannot install JRE 145 codes 175
See Java Runtime Environment migration fails when trying to launch error
Java 2 Platform, Standard Edition composer 159 See error messages
See Java Runtime Environment RHEL 5 (x86–64) install or uninstall of explanation, element 177
Java development kit Tivoli Dynamic Workload Console FAB 236
See Java Runtime Environment fails to start 285 FAF 244
Java Development Kit RHEL 5 installation fails (JVM) 285 fix pack 244
See Java Runtime Environment start of Tivoli Workload Scheduler help 177
Java Runtime Environment gives errors after installation 146 informational
cannot be installed on HP-UX 144 Linux user accounts 16 See informational messages
cannot be installed on Linux 145 ln, command installation (InstallShield
validation problem on UNIX 143 to link directories to the .swdis wizard) 177, 183
Java Virtual Machine directory 148, 151 introduction 175
See Java Runtime Environment to link product files 156 JIC 177
JDK localopts JIS 183
See Java Runtime Environment checking default settings 166 numbers 175
JIC messages 177 Log Analyzer numeric identifier 175
JIS messages 183 description 325 operator response, element 177
Job Scheduling Console log file not written by failed silent see also, element 177
accessibility xii installation 146 severity 175
jobman and JOBMAN log files 28, 255 system action, element 177
checking if active 169 DB2 installation 29 text 176
jobs embedded WebSphere Application Tivoli Workload Scheduler component
that must wait before starting are Server installation 29, 256 codes 175
duplicated after migration 161 installation 125 twsinst 236
jobstdl packaging for support 125 UI (001–100), installation (InstallShield
binary file, symbolic links not Tivoli Dynamic Workload wizard) of Tivoli Dynamic Workload
created 156 Console 281 Console 289
JRE uninstallation 125 warning
See Java Runtime Environment LPList, registry attribute 309 See warning messages
JVM LPName, registry attribute 309 miggopts, fails on UNIX mounted file
See Java Runtime Environment system 159
JVM, causing installation to fail on Linux migration
RHEL 5 285
jvmtimer, need to use for UNIX M fails
Linux when trying to launch
installation 143 maestro
composer 159
binary file, symbolic links not
UNIX mounted file system with
created 156
error AWSBEH115E 159
K mailman
checking if active 169
user permissions 159
kernel parameters, max_thread_proc 144 gives dependency error but plan is
MaintenanceVersion, registry
keys, registry, Windows, removing 173 OK 161
attribute 309
Job Scheduling Services, some seem to
MajorVersion, registry attribute 309
have been migrated twice 161
makesec
L create Security file 166
object type cannot be migrated 160
of jobs that must wait before starting
language packs manual uninstallation
has created duplicates 161
installing 42, 49, 53, 113, 124 agents 166
seems to have migrated some Job
removing 121 connector 171
Scheduling Services twice 161
launchpad master domain manager 166
workstation class cannot be
installation 13 manuals
migrated 160
problems using with Tivoli Dynamic See publications
MinorVersion, registry attribute 309
Workload Console 283 master domain manager
morestdl binary file, symbolic links not
licenseAccepted response file property, backup
created 156
TDWC 322 See backup master domain
licenseAccepted response file property, manager
TWS 314 uninstall manually 166
links master, global option 166 N
symbolic, not created after mat binary file, symbolic links not netman
upgrade 156 created 156 checking if active 169
Linux max_thread_proc kernel parameter 144 network 3
erroneous warning messages MAXDSIZ, configuration parameter NFS mounted installation image,
displayed from launchpad 283 needed for HP-UX 144 installation fails 150
installation fails if host name not mbatch binary file, symbolic links not NoClassDefFoundError error 150
FQDN 284 created 156 node name
installation problems 145 memory WebSphere Application Server 261
virtual, out of 154 non-integratable agents 48

numeric identifier, messages 175 publications xii server name
WebSphere Application Server 261
services
O Q stopping 110
services (Windows)
object type not migrated 160 queues, message
closing panel before using
operator response, message element 177 See message queues
InstallShield wizard 137, 162
optional features
deleting 167
connector 42
fail to start after installation 142
language packs 42
oracleCheckPrereqs. oracleDirectory
R Service Control Manager error 162
Red Hat Enterprise Linux V5, (x86–64), severity code, messages 175
install or uninstall of Tivoli Dynamic shared Windows folder, installation fails
oracleServerCommunication
Workload Console failing on 285 from 284
Info.netServiceName response file
Red Hat Enterprise Linux V5, installation shut, command, used before manual
property 314
failing on (JVM) 285 uninstallation 169
oracleServerCommunication
registry attribute 309 silent installation 44, 253, 262
Info.oracleAdminPwd response file
registry entries, deleting manually fails without writing a log 146
property 314
UNIX 169 troubleshooting 146
oracleServerCommunicationInfo.
Windows 167, 173 silent installation of Tivoli Dynamic
oracleAdminUser response file
registry file Workload Console problems with 286
property 314
attributes 309 silent installation wizard
ORB_LISTENER_ADDRESS response file
example 309 fails with ″Error writing file = ″ 148
property 322
remove fails with ″Error writing file =
output tab, in step window 129
See also uninstallation 28″ 149
manually 282 recovering 135
removing the product 121 silent uninstall 279
P required maintenance SOAP_CONNECTOR_ADDRESS
PackageName, registry attribute 309 See maintenance response file property 322
page file, too small 154 rerun installation wizard, or resume 132 Software Distribution
PanelUserIsNotRoot, referred to in response file missing, causing silent authorization roles 16
message from failing Tivoli Dynamic installation to fail 286 software package block installation and
Workload Console silent wizard 286 response file properties, installation 311 uninstallation log files 29
parameters response files 44 Solaris
-create_link 113 resume installation wizard immediately, installation fails with error "command
-lang 113 or exit and resume later 133 line parameter, -installRoot, is
-reset_perm 114 resume installation wizard, or rerun 132 invalid" 145
-skip_usercheck 113 resuming a stopped installation 134 installation problems 145
parms binary file, symbolic links not RHEL 5 (x86–64), install or uninstall of space, disk
created 156 Tivoli Dynamic Workload Console See disk space
password incorrect for TWS_user on failing on 285 stageman
UNIX 143 RHEL 5, installation failing on checking if active 169
PatchVersion, registry attribute 309 (JVM) 285 starting
pausing an installation 134 run error on installation 150 server 269
planned maintenance run error, failure of installation on Tivoli Dynamic Workload
See maintenance HP-UX 144 Console 269
port number 52 status tab, in step window 128
ports step list
WebSphere Application Server 259
post-installation actions 152
S status 127
using 126
SAS_SSL_SERVERAUTH_
pre-installation actions 152 step window
LISTENER_ADDRESS response file
problem scenarios, installation 136 using 128
property 322
problems step, installation, failed, correcting and
schedules
See troubleshooting continuing 131
See job streams
procedure for resolving installation stepped installation wizard 125
script
problems 135 stop, command
webui 264
product instances 18 used before manual
scripts
ProductID, registry attribute 309 uninstallation 169
See commands and scripts
profile name stopping
SDK_ECLIPSE_BUNDLED response file
WebSphere Application Server 261 an installation 134
property 315
profile, WebSphere Application Server, server 269
SDK_UPDATESITE response file
different, causing Tivoli Dynamic services 110
property 315
Workload Console installation to Tivoli Dynamic Workload
security implications of installation 165
fail 286 Console 269
Security, file
properties tab, in step window 128 structure
checking existence of 166
properties, response file, installation 311 installation DVD structures 26
see also, message element 177
ps, command used before manual summary.log, file 125
selectRDBMSPanel.rdbmsSelected
uninstallation 169
Index 341
Sun Tivoli Workload Scheduler (continued) twsDBCfg.tablespacePath response file
See Solaris user interface selection 261 property 316
support Tivoli Workload Scheduler fails after twsinst
packaging log files for 125 upgrade UNIX 156 authorization roles 15
supported servers Tivoli Workload Scheduler for fails
Tivoli Dynamic Workload Broker 255 Applications 251 ″The twsinst script is being run
swap space, out of 154 Tivoli Workload Scheduler for z/OS 251 from the wrong directory.″ 149
SWDGW component of Tivoli Tivoli Workload Scheduler service for miscellaneous 154
Configuration Manager, TWS_user with error AWSFAB035E 153
incompatibility 153 deleting 167 with error AWSGAB566E 154
swdis, directory fails to start after installation 142 files not being correctly copied before
insufficient space 151 Tivoli Workload Scheduler Version 8.3 Fix running 149, 154
removing 169, 170 Pack 3 installation and uninstallation log
swdis.ini, file, removing 169, 170 configuration 263 files 28
switch manager, fault-tolerant Tokensrv messages 236
See backup domain manager See Tivoli Token Service unattended, troubleshooting 146
symbolic links not created after tools usage 48
upgrade 156 Integration Workbench 325 twsismp.log, file 125
Symphony file 11 training twsLocationPanel.directory response file
syntax See also Tivoli technical training property 316
wdinstsp 53 technical xii twsLocationPanel.symLinkOption
system action, message element 177 troubleshooting response file property 316
system error 56b given during application server installation twsOracleDbCfg. isPartitioned response
installation 140 problems 146 file property 317
fix pack installation 164 twsOracleDbCfg. twsDBPwd response file
installation 125, 137 property 316
T AIX 142
HP-UX 144
twsOracleDbCfg. twsDBUser response file
property 316
tcp port 52
Sun Solaris 145 twsOracleDbCfg.tws DataTablespace
technical training
UNIX 143 response file property 316
See Tivoli technical training
installation scenarios 283 twsOracleDbCfg.tws ReportTablespace
test connection to master domain
installations response file property 316
manager fails 156
Linux 145 twsOracleDbCfg.tws TempTablespace
text files, used for backup and restore
migration 158 response file property 316
See files
miscellaneous installation twsPortsPanel.portAdmin response file
time zone
problems 147 property 317
overview 12
uninstallation 162 twsPortsPanel.portAdminSec response
Tivoli Configuration Manager
upgrading 155 file property 317
incompatibility problem with fix
truncated host name on Windows: twsPortsPanel.portEif response file
packs 153
installation fails 138 property 317
installation fails 151, 152
TWA_INSTANCE_PATH response file twsPortsPanel.portHTTP response file
insufficient disk space 151
property 322 property 317
Tivoli Dynamic Workload Broker
TWS_group Windows user group 141 twsPortsPanel.portHTTPS response file
available functions 266
TWS_user password incorrect on property 317
server connection 267
UNIX 143 twsPortsPanel.portMtlAuth response file
supported servers 255
twsCliCfgPanel.password response file property 317
user interface selection 261
property 315 twsPortsPanel.portORB response file
Tivoli Dynamic Workload Console
twsCliCfgPanel.remoteHost response file property 317
accessibility xii
property 315 twsPortsPanel.portRMI response file
configuration 271
twsCliCfgPanel.remotePort response file property 317
installation and uninstallation log
property 315 twsPortsPanel.portSAS response file
files 281
twsCliCfgPanel.user response file property 317
messages 289
property 315 twsPortsPanel.portSOAP response file
overview 251
TWSCLILanguagesPanel.* response file property 317
starting and stopping 269
properties 315 twsPortsPanel.portSrvAuth response file
troubleshooting 281
twsCLILocationPanel.directory response property 318
uninstall 277
file property 316 TWSRegistry.dat, file 169, 309
user interface 265
TWSConnRegistry.dat 171 twsUpgradePanel.backupOldInstance
Tivoli Message Standard 175
twsDBCfg.dbName response file response file property 318
Tivoli Netman for TWS_user, deleting
property 316 twsUpgradePanel.bckpDirectory response
service 167
twsDBCfg.report TablespaceName file property 318
Tivoli technical training xii
response file property 316 twsUpgradePanel.bckpProfileDirectory
Tivoli Token Service
twsDBCfg.report TablespacePath response response file property 318
fails to start after installation 142
file property 316 twsUpgradePanel.dumpDirectory
for TWS_user, deleting service 167
twsDBCfg.tablespaceName response file response file property 318
Tivoli Workload Scheduler 251
property 316
available functions 266
engine connection 266

TWSUser unlink, command variables (continued)
account creation used before manual language (continued)
Windows 140 uninstallation 169 Korean 53
Windows 2000 140 update of the embedded WebSphere Spanish 53
deleting from registry Application Server fails during the fix tws_user 54
UNIX 169 pack installation 164 Software Package Block
Windows 167 UPDATE_INSTALLER_DIR response file backup 52
unable to use cmd.exe 141 property 322 backup_dir 51
TWSZConnRegistry.dat 171 UpdateInstaller company 51
WebSphere Application Server 261 domain 51
upgrade fresh_install 52
U after, cannot start Tivoli Workload
Scheduler because
from_release 52
ft_agent 51
UI (001–100) messages 289
symbolic links not created 156 install_dir 51
unattended installation using
consoles cannot connect after 156 master_cpu 51
twsinst 146
problems 155, 158, 164 pwd 51
UNC mapped drive, unable to install
recovering 136, 281 tcp_port 52
from 148
troubleshooting 125 this_cpu 51
uninstall
upgrading 77 tws_user 51
clean-up 282
user name upgrade 52
in silent mode 279
creating 51 symlink
manually 282
UserOwner, registry attribute 309 TWA/TWS/bin/at 25
using response file 279
users TWA/TWS/bin/batch 25
using wizard 277
account creation TWA/TWS/bin/datecalc 25
uninstallation
Windows 140 TWA/TWS/bin/jobstdl 25
fails because the embedded
Windows 2000 140 TWA/TWS/bin/maestro 25
WebSphere Application Server not
cmd.exe problem on Windows TWA/TWS/bin/mdemon 25
stopped 162
2003 141 TWA/TWS/bin/morestdl 25
fails in restore profiles step 162
rights TWA/TWS/bin/muser 25
fails using InstallShield wizard on
assignment for TWS_user 140 TWA/TWS/bin/parms 25
Windows 162
TWS_user verifying Tivoli Workload Scheduler
manually
deleting from registry on installation 165
agents 166
UNIX 169 virtual memory, out of 154
connector 171
deleting from registry on
master domain manager 166
Windows 167
of Tivoli Dynamic Workload Console,
fails to start on Linux RHEL 5
rights assignment 140
unable to use cmd.exe 141
W
(x86–64) 285 warning messages
Windows 2003, using cmd.exe 141
of Tivoli Dynamic Workload Console, definition 176
userUnixCfgPanel.inputUserName
problems with 287 WAS_CELL_NAME response file
the connector manually on property 322
userUnixCfgPanel.twsPassword response
Windows 172 WAS_NODE_NAME response file
file property 318
Tivoli Dynamic Workload Console log property 323
userUnixCfgPanel.wasPassword response
files 281 WAS_PROFILE_NAME response file
file property 318
troubleshooting 125 property 323
userUnixCfgPanel.wasUserName
uninstallation of Tivoli Dynamic WAS_SERVER_NAME response file
Workload Console problems with 287 property 323
userWinCfgPanel.inputUserName
uninstalling 121 WC_adminhost response file
UNIX property 323
userWinCfgPanel.twsPassword response
installation fails with JVM validation WC_adminhost_secure response file
file property 318
error 143 property 323
userWinCfgPanel.wasPassword response
installation problems 143 WC_defaulthost response file
file property 319
migration fails on mounted file property 323
userWinCfgPanel.wasUserName response
system with error WC_defaulthost_secure response file
file property 319
AWSBEH115E 159 property 323
password incorrect for wconvcat, command 154
TWS_user 143 wdinstsp
removing software distribution V syntax 53
directories 170 variables wdlssp, comman used before manual
silent fix pack installation fails 148, language uninstallation 169
149 Brazilian Portuguese 53 wdrmvsp, command used before manual
symbolic links not created 156 Chinese, Simplified 53 uninstallation 169
uninstalling manually 169 Chinese, Traditional 53 Web User Interface
UNIX user accounts 16 French 53 See Tivoli Dynamic Workload Console
UNIX, symbolic links not created 156 German 53 WebSphere Application Server
unlink workstations 110 install_dir 54 See also application server
Italian 53 cell name 261
Japanese 53 choosing instance 257
Index 343
WebSphere Application Server (continued)
node name 261
ports 259
profile name 261
server name 261
UpdateInstaller 261
WebSphere Application Server,
installation of Tivoli Dynamic Workload
Console fails when installing on
different profile 286
webui
script 264
Windows
2003 domain, application server
installation fails with credentials
problem 147
2003, cmd.exe 141
cmd.exe on 2003 141
credentials problem for installing on
application server 140
installation
fails because of Autotrace 137
receives warning
AWSGAB005W 139
with InstallShield wizard,
fails 137
installation fails
host name truncated 138
installation of Tivoli Dynamic
Workload Console fails on different
external WebSphere Application
Server profile 286
installation problems 137
registry keys, removing 173
removing software distribution
directories 169
shared folder, installation fails
from 284
undefined error message displayed
from launchpad 283
uninstallation fails because the
Server not stopped 162
uninstallation fails in restore profiles
step 162
uninstallation with InstallShield
wizard fails 162
uninstalling manually 167
uninstalling the connector manually
on 172
wlsinst, command 153
work, directory 151
workstation class not migrated 160
workstations
unlinking 110
writer
checking if active 169

Program Number: 5698-WSH
Printed in USA
SC32-1273-08
Spine information:
IBM Tivoli Workload Scheduler Version 8.5 IBM Tivoli Workload Scheduler Planning and Installation

TWS8.5 Planning and Installation

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TWS8.5 Planning and Installation

Uploaded by

Copyright:

Available Formats

Tivoli IBM Tivoli Workload Scheduler

Planning and Installation

Planning and Installation

Chapter 1. Network planning . . . . . . 3 Chapter 4. Installing . . . . . . . . . 31

© Copyright IBM Corp. 1991, 2008 iii

iv IBM Tivoli Workload Scheduler Planning and Installation

Chapter 14. Uninstalling . . . . . . . 277 Appendix A. Registry file . . . . . . 309

Part 4. Tutorials . . . . . . . . . 299 Notices . . . . . . . . . . . . . . 333

© Copyright IBM Corp. 1991, 2008 vii

© Copyright IBM Corp. 1991, 2008 ix

What is new in this release

| What is new in this publication

| What is new in version 8.5

Who should read this publication

© Copyright IBM Corp. 1991, 2008 xi

v Specialists who plan the network topology

Both of these are in the Information Center as separate publications.

Tivoli technical training

xii IBM Tivoli Workload Scheduler Planning and Installation

© Copyright IBM Corp. 1991, 2008 1

| Tivoli Workload Scheduler environment

| Figure 1 on page 4 gives a graphical overview of the Tivoli Workload Scheduler

© Copyright IBM Corp. 1991, 2008 3

Command-line Tivoli Dynamic Master Domain

Command Master domain

| The objects in the Tivoli Workload Scheduler environment are as follows:

4 IBM Tivoli Workload Scheduler Planning and Installation

| Backup master domain manager

Chapter 1. Network planning 5

| Automation instance infrastructure (see “Installation paths and

| Note: The terminology non-integratable only refers to their

| Tivoli Workload Scheduler interfaces

| Additionally, Tivoli Workload Automation contains the z/OS connector, which is a

6 IBM Tivoli Workload Scheduler Planning and Installation

In a single domain configuration, the master domain manager maintains

In a multiple domain configuration, the master domain manager communicates

Localized processing in your domain

The benefits of localized domains are:

Considerations in planning domains

Chapter 1. Network planning 7

Number of geographic locations

8 IBM Tivoli Workload Scheduler Planning and Installation

Secure Sockets Layer (SSL) encryption

Single domain network

Figure 2. Single domain topology

Chapter 1. Network planning 9

Atlanta Backup Master

Agent Agent Agent

Figure 3. Single domain topology on multiple sites

Multiple domain network

10 IBM Tivoli Workload Scheduler Planning and Installation

managers, and domain managers communicate with their parent domain

Second-level Domain Domain

Third-level Domain Aurora Domain

Agent Agent Agent Agent Agent Agent

Figure 4. Multiple domain topology

As Figure 4 illustrates, the master domain manager is located in Atlanta. The

Chapter 1. Network planning 11

Time zone considerations

12 IBM Tivoli Workload Scheduler Planning and Installation

Selecting your installation method

The launchpad requires some additional installation prerequisites. For more

© Copyright IBM Corp. 1991, 2008 13

v IBM Tivoli Workload Scheduler components (master domain manager,