IBM Tivoli Workload Scheduler: Readme File for Fix Pack 3maestro.tivoli.free.fr/root/TWS_CCT/8.6.0-TIV-TWS-FP0003...Documentation updates for Tivoli Workload Scheduler Fix Pack 1 for

IBM Tivoli Workload Scheduler

Readme File for Fix Pack 3Version 8.6.0

��

IBM Tivoli Workload Scheduler

Readme File for Fix Pack 3Version 8.6.0

��

Note

Before using this information and the product it supports, read the information in “Notices” on page 61.

This edition applies to Fix Pack 3 for version 8, release 6, modification level 0 of IBM Tivoli Workload Scheduler(program number 5698-WSH) and to all subsequent releases and modifications until otherwise indicated in neweditions.

© Copyright IBM Corporation 2011, 2013.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

IBM Tivoli Workload Scheduler Readme File for Fix Pack 3 for version 8.6.0 . . . . . . 1About this fix pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

New default certificates (TrustStore and KeyStore) . . . . . . . . . . . . . . . . . . . . . . 2Features introduced with Fix Pack 3 . . . . . . . . . . . . . . . . . . . . . . . . . . 2Features introduced with Fix Pack 2 . . . . . . . . . . . . . . . . . . . . . . . . . . 3Features introduced with Fix Pack 1 . . . . . . . . . . . . . . . . . . . . . . . . . . 6Problems fixed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

APARs and defects fixed in Tivoli Workload Scheduler Fix Pack 3 for version 8.6.0 . . . . . . . . . . 8APARs and defects fixed in Tivoli Workload Scheduler Fix Pack 2 for version 8.6.0 . . . . . . . . . 12APARs and defects fixed in Tivoli Workload Scheduler Fix Pack 1 for version 8.6.0 . . . . . . . . . 14

Known limitations and workarounds . . . . . . . . . . . . . . . . . . . . . . . . . . 17Compatibility with earlier versions . . . . . . . . . . . . . . . . . . . . . . . . . . 22Globalization notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Fix pack structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Fix pack files available for Tivoli Workload Scheduler using Fix Central . . . . . . . . . . . . . . 23Fix pack files available for batch reports using Fix Central. . . . . . . . . . . . . . . . . . . 23Fix pack file available for Tivoli Endpoint Manager using Fix Central . . . . . . . . . . . . . . . 24

Installing the fix pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Creating a fix pack installation package for a specific Tivoli Workload Scheduler component . . . . . . . 24Downloading and replacing files from GAFixes directory . . . . . . . . . . . . . . . . . . . 26Installation notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Disk space requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Updating the Tivoli Workload Scheduler database . . . . . . . . . . . . . . . . . . . . . 32Performing a safe fix pack installation . . . . . . . . . . . . . . . . . . . . . . . . . 37

Customizing the safe fix pack installation using the wizard . . . . . . . . . . . . . . . . . 38Customizing the safe fix pack installation using the silent method . . . . . . . . . . . . . . . 38Customizing the safe fix pack installation using twspatch . . . . . . . . . . . . . . . . . . 38

Installation actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Product actions when applying the fix pack . . . . . . . . . . . . . . . . . . . . . . 40Product actions when undoing the fix pack. . . . . . . . . . . . . . . . . . . . . . . 42

Before Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Untar the eImages for the Tivoli Workload Scheduler for z/OS Agent and Dynamic Agent on IBM ioperating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Installing using the ISMP wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Installing using the ISMP silent installation . . . . . . . . . . . . . . . . . . . . . . . . 45Installing using the twspatch script . . . . . . . . . . . . . . . . . . . . . . . . . . 45Installing using Software Distribution . . . . . . . . . . . . . . . . . . . . . . . . . 47Installing using IBM Endpoint Manager . . . . . . . . . . . . . . . . . . . . . . . . . 48Installing the fix pack on fault-tolerant agents when there are corrupt registry files . . . . . . . . . . 48

Re-creating the registry files using the installation wizard . . . . . . . . . . . . . . . . . . 49Re-creating registry files using silent fix pack installation . . . . . . . . . . . . . . . . . . 49Re-creating registry files using twspatch . . . . . . . . . . . . . . . . . . . . . . . . 50

Configuring properties for the dynamic workload broker command line . . . . . . . . . . . . . . 51Rolling back the fix pack installation . . . . . . . . . . . . . . . . . . . . . . . . . . 51Uninstalling the entire Tivoli Workload Scheduler instance . . . . . . . . . . . . . . . . . . 51Installation log files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Documentation updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Documentation updates for Tivoli Workload Scheduler Fix Pack 3 for version 8.6.0 . . . . . . . . . . 52Documentation updates for Tivoli Workload Scheduler Fix Pack 2 for version 8.6.0 . . . . . . . . . . 57Documentation updates for Tivoli Workload Scheduler Fix Pack 1 for version 8.6.0 . . . . . . . . . . 57

Contacting IBM Software Support . . . . . . . . . . . . . . . . . . . . . . . . 59

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

© Copyright IBM Corp. 2011, 2013 iii

iv IBM Tivoli Workload Scheduler: Readme File for Fix Pack 3

IBM Tivoli Workload Scheduler Readme File for Fix Pack 3 forversion 8.6.0

Date 29 November 2013

Fix Pack8.6.0-TIV-TWS-FP0003

ProductIBM® Tivoli® Workload Scheduler version 8.6.0

General DescriptionIBM Tivoli Workload Scheduler Fix Pack 3 for version 8.6.0

This readme file provides important information about Fix Pack 3 for IBM TivoliWorkload Scheduler version 8.6.0.

This readme file is the most current information for the fix pack and takesprecedence over all other documentation for Tivoli Workload Scheduler version8.6.0 Fix Pack 3.

It is divided into the following sections:v “About this fix pack”v “Fix pack structure” on page 22v “Installing the fix pack” on page 24v “Documentation updates” on page 52

Review this section thoroughly before installing or using this Fix Pack.

About this fix packThis section contains information specific for this fix pack including what has beenmodified or introduced, what has been fixed, product versions or components towhich the fix pack applies, and compatibility issues, if any.

Product versions and components to which the fix pack appliesThis fix pack can be applied only on top of Tivoli Workload SchedulerV8.6.0 GA, or Fix Pack 1, or Fix Pack 2.

This section includes the following subsections:v “Features introduced with Fix Pack 3” on page 2v “Features introduced with Fix Pack 2” on page 3v “Features introduced with Fix Pack 1” on page 6v “Problems fixed” on page 8v “Known limitations and workarounds” on page 17v “Globalization notes” on page 22

© Copyright IBM Corp. 2011, 2013 1

New default certificates (TrustStore and KeyStore)The default certificates that were released with Tivoli Workload Scheduler V8.3.0, V8.4.0,V8.5.0, V8.5.1, and V8.6.0 general availability expire on February 10, 2014, but youmust renew them before December 10, 2013 due to the embedded WebSphere ApplicationServer automatic renewing mechanism that generates new random certificates to use twomonths before the expiration date.

Tivoli Workload Scheduler Fix Pack 3 installs updated versions of the defaultcertificates (TrustStore and KeyStore) that expire in 2032.

After the fix pack installation, until February 10, 2014, the Tivoli WorkloadScheduler instance communicates with all the other involved Tivoli WorkloadScheduler components where the first part of the procedure described in thefollowing alerts has been completed:v http://www.ibm.com/support/docview.wss?uid=swg21628636v http://www.ibm.com/support/docview.wss?uid=swg21628601

After February 10, 2014 the overall procedure to renew the default certificates musthave been completed on those components, or the related Fix Pack 3 must havebeen applied, or those components must have been upgraded to V9.1.

After Dynamic Workload Console Fix Pack 3 installation, if you try to install TivoliWorkload Scheduler V8.6 General Availability components to have an integratedinstance in the same directory, your installation might hang without completing ifyou have not performed the prerequisite actions described in section "New defaultcertificates (TrustStore and KeyStore)" of Dynamic Workload Console Fix Pack 3Readme. To recover from this problem, perform the following actions:1. Stop the V8.6 General Availability component installation.2. Stop the WebSphere Application Server.3. You are asked to accept the new client truststore for the Dynamic Workload

Console. To accept the new truststore during the running of stopServer.bat onWindows operating systems and stopServer.sh on UNIX and Linux operatingsystems, reply "y" to the prompt Add signer to the trust store now? (y/n).

4. Start the WebSphere Application Server.5. Start again the installation with the option -resume:

On UNIX and LINUX operating systems:SETUP.exe -resume

On Windows operating systems:./SETUP.bin -resume

6. In the window that lists the installation steps, set to success all the stepspreceding the step "Propagate the security policies of the application to theJACC provider in the embedded WebSphere Application Server".

7. Click the button Run All.

Features introduced with Fix Pack 3Registry regeneration

When installing this fix pack, if the Tivoli Workload Scheduler instance isnot discovered and the fix pack installation fails, before running again thefix pack installation you must specify the instance installation directory, forexample: /inst_dir/TWA_home. The following registries are regenerated:v /etc/TWS/TWSRegistry.dat

2 IBM Tivoli Workload Scheduler: Readme File for Fix Pack 3

http://www.ibm.com/support/docview.wss?uid=swg21628636

http://www.ibm.com/support/docview.wss?uid=swg21628601

v /etc/TWA/twainstance0.TWA.properties

v /etc/teb/teb_tws_cpa_agent_mdm86.ini

v .swdis

For shared instances, only the Tivoli Workload Scheduler registries areregenerated and software distribution packets are put in committed status.

This feature can be used either with the installation wizard, specifying theinstallation directory, or with a script using the following syntax:twspatch -recovInstReg <boolean_value> -inst_dir <directory> [-wait <minutes>][-lang <lang_id>]

where:

<boolean_value>is the option to upgrade the product when the registry files arecorrupted. Possible values: yes | no

<directory>is the Tivoli Workload Scheduler installation directory.

<minutes>is the number of minutes that the installation process waits forrunning jobs to complete before launching the fix pack installation.

<lang_id>is the code related to the language used to display installationmessages.

Added the support for multibyte file transferThis feature adds the support for multibyte code page translation duringfile transfers to and from ASCII-based hosts and z/OS operating systemsthat usually use the EBCDIC format. You can specify, in the job definitionpane of an FTP job type, if a multibyte data connection is required for thefile transfer by checking the option Multibyte data encoding. To use thisfeature in an end-to-end with z-centric capabilities environment, you mustinstall APAR PI05603 on the z/OS controller.

Features introduced with Fix Pack 2For an overview about the new features introduced with this fix pack, see:

http://pic.dhe.ibm.com/infocenter/tivihelp/v47r1/topic/com.ibm.tivoli.itws.doc_8.6.0.2/common/src_gi/eqqg1sumenh.htm

New job types supportedRemote Command and Provisioning job types can now be created and runusing the Dynamic Workload Console or the command line.

Provisioning jobs span physical computers, virtual machines, and privateand public cloud environments creating an on-demand environment. Thisjob type integrates with IBM SmartCloud® Provisioning.

Remote Command jobs are jobs that can run on remote computers withoutrequiring the installation of any agent.

Variable resolution at run timeIn addition to assigning values to variables defined in a job definitionwhen the job is added to the plan, you can also specify variables in aformat that allows for the variable to be resolved at job submission time.Variables defined in the job definition assume the most updated value

IBM Tivoli Workload Scheduler Readme File for Fix Pack 3 for version 8.6.0 3



assigned to the variable in the related variable table. This means you canalso take advantage of assigning different values to variables that aredefined in different jobs contained in the same job stream. Assuming thereare other jobs in the job stream responsible for updating the value of thevariable in the variable table, each job assigns the value of the variablecurrently present in the variable table when the job runs.

Monitoring anomalous behavior in running jobsThe management of running jobs does not only include monitoring jobs toensure they complete successfully, but there are also other mechanisms tocheck for anomalous behavior such as jobs that run much longer thanexpected, and jobs that finish much too early. In response to theseconditions, Tivoli Workload Scheduler provides you with further control bynotifying you when these conditions are met, and enabling you toautomatically trigger a response. Two new keywords have been added tothe job stream definition, maxdur and mindur to monitor these conditionsand new events with automatic responses to these conditions.

Improved recovery procedureRecovering the plan using the last archived Symphony® file can result in amore complete recovery. In addition to using the latest archived plan, anyevents that were logged throughout the day are written to a new messagefile. The last archived Symphony file is copied into the current Symphonyfile and then JnextPlan is run to apply the events queued in the evtlog.msgfile.

Integration with Tivoli System Automation for Multiplatforms to deliver ahigh-availability environment with automatic failover of all components

Tivoli Workload Scheduler consists of multiple built-in high-availabilityfeatures that you use to switch components to other workstations in theTivoli Workload Scheduler network, however, when combined with TivoliSystem Automation for Multiplatforms and tailored policies, the recoveryoperations are regulated by a third-party with more insight into the state ofall critical components, and the process of switching components to otheravailable workstations in the Tivoli Workload Scheduler network isautomatic and requires less time.

Automatic mechanisms for upgrades, fix pack installations, and rollbacks withTivoli Endpoint Manager

Tivoli Workload Scheduler integrates with Tivoli Endpoint Manager on allsupported operating systems to provide unified, real-time visibility andenforcement to deploy and manage upgrades to all endpoints from a singleconsole.

Child job monitoring on IBM i dynamic agentsWhen you submit a command on an IBM i agent, the command mightstart one or more batch jobs. The IBM i agent monitors these batch jobs,which are referred to as child jobs. When searching and monitoring anychild jobs that are started, the IBM i agent uses a high percentage of itsprocessing time. Starting from Tivoli Workload Scheduler Fix Pack 2, youcan instruct the IBM i agent to not search and monitor child jobs, andhence improve the performance of the agent. You can exclude child jobmonitoring either at the agent level for all the commands or at the jobdefinition level for a single command.

Added the possibility to load the user profile on a fault-tolerant agent onWindows systems

Only on Windows systems, this feature allows you to add or remove theuser profile on a fault-tolerant agent. When enabled, Tivoli Workload


Scheduler loads the user profile and the user environment variables foreach job run by the agent. Roaming profiles are not supported.

Enable the feature by setting the jm load user profile property to on inthe localopts file, as in the following example:jm load user profile=on

Using SSL for event-driven workload automation (EDWA) behind firewallsThis feature allows a domain manager to be run as a reverse proxy forHyperText Transfer Protocol (HTTP) and Event Integration Facility (EIF)protocols, forwarding traffic to the Event Processor. A new option, enabledusing the optman command-line program, allows you to choose ifworkstations that are behind a firewall must connect to the domainmanager instead of to the event processor, causing the new proxy on thedomain manager to forward its traffic to the event processor.

The incoming traffic is rerouted as follows:v If an agent is behind a firewall, the traffic is routed to the domain

manager on the agent. If an agent is not behind a firewall, the traffic issent directly to the event processor.

v If domain managers have child nodes behind a firewall, the traffic isrerouted to the event processor.

v Primary domain managers always reroute traffic to the current eventprocessor.

v Lower level domain managers reroute traffic to upper level domainmanagers if they are behind a firewall, or to the event processor if theyare not behind a firewall.

To use this feature, perform the following steps:1. Enable the feature by setting the optman option to yes. The default

value is no:enEventDrivenWorkloadAutomationProxy | pr = {yes|no}

2. In the workstation definition in the database for the agent, set thebehindfirewall attribute to ON.

3. Configure OpenSSL or GSKit on the domain manager.For additional information about setting options for SSL in thelocalopts file, see http://pic.dhe.ibm.com/infocenter/tivihelp/v47r1/topic/com.ibm.tivoli.itws.doc_8.6.0.2/awsadlocaloptset.htm.

Broker SQL OptimizationThe broker job submission and the broker job archiving processes havebeen improved by performing an optimization of specific SQL statements.

Monitoring jobs enhancementFor broker job type and for Job Submission Description Language (JSDL)template jobs, the full JSDL with all variables substituted are now loggedin the header of the job log with the keyword TASK.

Resource CLI enhancementThe broker resource command line interface (CLI) has been improved byadding the support for the switching manager scenario.

Before this fix pack, the resource CLI was configured, at installation time,to contact the broker server running on the Master domain manager. Forthis reason, after the switching manager command, the resource CLI wasunable to contact the broker server on the primary Master domainmanager and was not configured to contact the new broker server runningon the backup Master domain manager.


http://pic.dhe.ibm.com/infocenter/tivihelp/v47r1/topic/com.ibm.tivoli.itws.doc_8.6.0.2/awsadlocaloptset.htm

http://pic.dhe.ibm.com/infocenter/tivihelp/v47r1/topic/com.ibm.tivoli.itws.doc_8.6.0.2/awsadlocaloptset.htm

Starting from this fix pack, you can define in the CLIConfig.properties filethe backup broker servers to be contacted by the resource CLI if thecurrent broker server does not respond. To configure the resource CLI tocontact the backup servers in case of failure, you must specify in theCLIConfig.properties file the connection properties for each backupbroker server. List the same properties specified for the broker serverrunning on the primary Master domain manager.

Specify the following connection properties:ITDWBServerHostITDWBServerPortITDWBServerSecurePortuse_secureconnectiontdwb_usertdwb_pwd

For backup servers, the same ordinal number must be appended to eachproperty name associated to the same backup server.

In the following example, in the CLIConfig.properties file is specified thebroker server running on the primary Master domain manager and twobackup broker servers:# Properties of the Broker Server running on the primary Master domain managerITDWBServerHost = BrokerServer.mycompany.comITDWBServerPort = 51117ITDWBServerSecurePort = 51118use_secureconnection = truetdwb_user = tdwbUsertdwb_pwd = xxxx

# First (_1) Backup Broker Server PropertiesITDWBServerHost_1 = FirstBackupBrokerServer.mycompany.comITDWBServerPort_1 = 41117ITDWBServerSecurePort_1 = 41118use_secureconnection_1 = falsetdwb_user_1 = backup1TdwbUsertdwb_pwd_1 = yyyy

# Second (_2) Backup Broker Server PropertiesITDWBServerHost_2 = SecondBackupBrokerServer.mycompany.comITDWBServerPort_2 = 61117ITDWBServerSecurePort_2 = 61118use_secureconnection_2 = falsetdwb_user_2 = backup2TdwbUsertdwb_pwd_2 = zzzz

You can define a maximum of 10 broker servers. To prevent the resourceCLI from contacting unavailable servers, the name of the last successfullycontacted broker server is saved in the ITDWBLastGoodServerHost propertyof the CLIConfig.properties file.

Features introduced with Fix Pack 1All the features introduced with Fix Pack 1 are described in the updated manualsin the information center:

http://publib.boulder.ibm.com/infocenter/tivihelp/v47r1/index.jsp?topic=/com.ibm.tivoli.itws.doc_8.6.0.1/welcome_TWA.html

The following list contains details about some of these features:




Authorizing the user to save the credentials for a job type with advancedoptions in a centralized location

In Tivoli Workload Scheduler version 8.6, when defining a job withadvanced options, you specify and save the username and password in thecredentials section of the job definition. If the password for a specific userchanges, you must update all the job definitions for that user.

In Tivoli Workload Scheduler version 8.6.0 Fix Pack 1, the databaseadministrator can save the password, provided in a job definition, in acentralized location. Regardless of the operating system of the dynamicagent running the job, the username and password values, provided in thecredentials section of the job, are saved in a user definition on thedatabase. The password value for the job credentials is resolved at runtime with the value stored in the database. For more information about thisfeature, see Tivoli Workload Scheduler: User's Guide and Reference. To use thisfeature, you must have the authorization set in the Security file to performUSE actions on USEROBJ objects. For further information,.see the TivoliWorkload Scheduler: Administration Guide.

The fix pack installation does not update the Security file installed on themaster domain manager. If you want to include a new security statement,or add a new access keyword to a statement, you must do it manually.

After the fix pack installation, if you need to update the Security file with anew authorization, follow these steps:1. Log in as TWSUser on your master domain manager and set the Tivoli

Workload Scheduler environment.2. Extract the Security file using the command:

dumpsec > sec_file

where sec_file is the text file created by the dumpsec command.3. Edit the file sec_file to insert the access keyword USE in the USEROBJ

statement:userobj access=display,modify, altpass, use

4. Save your changes in the file sec_file.5. Build you security file for your master domain manager using the

makesec command.makesec sec_file

6. If you have centralized security feature enabled, distribute the Securityfile to the entire network.

Manually setting the environment in a dynamic agent to run the param andtwstrace commands

Tivoli Workload Scheduler version 8.6.0 Fix Pack 1 installs two newcommand lines to manage a dynamic agent:v The param command line, which creates and manages variables and user

passwords locally. For more information about this feature, see TivoliWorkload Scheduler: User's Guide and Reference.

v The twstrace command line, which modifies the settings for tracing atrun time. For more information about this feature, see Tivoli WorkloadScheduler: User's Guide and Reference.

The existing file in your agent instance:v <tws_install_dir>\TWS\tws_env.bat for Windows operating systemsv <tws_install_dir>/TWS/tws_env.sh for UNIX operating systems


that are used to set the Tivoli Workload Scheduler environment, must beupdated to support these commands.

The fix pack installation program copies a new version of the existing file,that contains the valid settings to run the commands, into the<tws_install_dir>/TWS/config directory.

Manually, you either add the new settings to your existing file or mergethe old and new versions of the file.

Profiler implemented to monitor connector APIs and EDWA rule builder timeconsumption

A profiler has been implemented to monitor connector APIs and the rulebuilder time consumption related to event-driven workload automation(EDWA). This profiler can be enabled or modified by setting the followingproperties located in the <tws_install_dir>/eWAS/profiles/TIPProfile/properties/TWSConfig.properties file:com.ibm.tws.util.profiling={true|false}com.ibm.tws.util.profiling.verbose={true|false}com.ibm.tws.util.profiling.interval=xx

where xx is a value expressed in minutes in the range from 1 to 1440. If theproperty com.ibm.tws.util.profiling.verbose is set to true, the profilerwrites verbose information in the file <tws_install_dir>/TWS/profiling.txt.

As a default, after the fix pack is installed, the profiler is disabled and noproperty is added to the <tws_install_dir>/eWAS/profiles/TIPProfile/properties/TWSConfig.properties file.

Problems fixedThis section lists all APARs and internal defects solved by this fix pack. Foradditional information about documentation APARs and internal defects, see“Documentation updates” on page 52.

This section also provides information about the procedure for downloading andreplacing GA fixes before starting the Tivoli Workload Scheduler version 8.6.0installation. See “Downloading and replacing files from GAFixes directory” onpage 26.

This section includes the following topic:v “APARs and defects fixed in Tivoli Workload Scheduler Fix Pack 3 for version

8.6.0”v “APARs and defects fixed in Tivoli Workload Scheduler Fix Pack 2 for version

8.6.0” on page 12v “APARs and defects fixed in Tivoli Workload Scheduler Fix Pack 1 for version

8.6.0” on page 14

APARs and defects fixed in Tivoli Workload Scheduler Fix Pack 3for version 8.6.0This section lists APARs and internal defects solved by Fix Pack 3.

List of APARs fixed:

v IV19053: Conman crashes when piped with "more" and lines=-1.v IV20588: Critical job already in plan when workstation is ignored results

in DWC AWSJCS011E "java.lang.NullPointerException".


v IV20902: Opens dependency treating an environment variableincorrectly.

v IV24757: ChangHostProperties accepts equal port values for differentports.

v IV27106: TWS bkm install fails to retrieve tablespace names if the db2user contains special characters.

v IV28201: Problem with tcl used in makeplan.cmd.v IV28691: TWS uninstall program does not delete the version

subdirectory.v IV29250: Cancelling js with pend option does not release dependency.v IV30948: Conman -gui generates a segmentation fault.v IV31688: Job name truncated for event 203 when job name contains

underscore or hyphen characters.v IV32349: Z-centric agent on UNIX does not respect the umask it creates.v IV32416: On Windows DM sinfonia become corrupted after it switch

copy.v IV32430: Resource modifications issued during switchplan.v IV33046: Unable to create jobs with advanced options in broker.v IV33056: Unable to migrate or add DWC users who are authenticated

through pam using LDAP.v IV33159: After a machine failover zCentric could not restart well at first

start.v IV33168: Reptr reports unrun jobs start time in mdm tz instead of fta tz.v IV33265: reprt -post incorrectly shows pending predecessor instance.v IV33271: Output for interactive jobs scheduled on dynamic agents is

different if same job has been submitted on a FTA.v IV33732: Parameters with ampersand -&- and quotes -"- are not resolved

well at JNextPlan.v IV33862: FTP JobExecutor add support for multibyte file transfer.v IV33962: AWSUI5017E unable to save the event rule if minlength not 1.v IV34013: Fix pack installation for mdm and bmdm starts jobManager

anyway.v IV34095: Datastage job listings in DWC are incosistent in results,

intermittently diplay error, including AWKDSE020Ev IV34829: JSC shows permissions error when changing a job priority with

altpri security setting.v IV35486: Job stream elapsed time is not correct.v IV35722: TWS has several world-writeable (777 permissions) that are not

allowable for customer's environment.v IV36364: Unixssh or Unixrsh jobs schedule via zcentric failed.v IV36450: ChangeDataSourceProperties.sh doe not change

SecurityMechanism.v IV36517: DatabaseJobExecutor jobs go in FAIL if they execute a stored

procedure without parameters with error AWKDBE006E.v IV36534: DWC plan reports show mdm timefor other timezone fta jobs.v IV36624: Time restrictions are not applied after making changes in jsc

under job stream properties.v IV37071: Global prompt does not work as expected.


v IV37292: Prevent the failure of zcentric jobs in case of filesystem full.v IV37443: AWSBHT228W message in twsmerge although the jobstream

already ran.v IV37453: Problem with tcl used in createpostreport.cmd.v IV37648: TWS processes abend if bmevents.conf events parameter

contains more than 50 events.v IV37819: TWS upgrade oto 8.6 does not remove tlm signature of

previous releases.v IV37859: During DST change TWS does not switch from epoch

scheduling.v IV38461: Stageman error TWS 8.6 FP2.v IV39263: At/until time is not correct for eet on the day after dst change.v IV39528: Unixssh or Unixrsh jobs schedule via zcentric failed.v IV40159: Composer does not accept "etc/gmt+" time zones.v IV40269: Slow SSH transfer of file due to processing local file.v IV41597: A recovery interactive job is launched as not interactive.v IV41929: Interactive jobs do not work if the streamlogon has a domain.v IV42438: Parameter deletion performed in DWC not recorded in audit

logs.v IV42786: LogMessageWritten event component not working after 8.6 fp2

installed.v IV43150: High cpu usage of jobmon due to a local tcp scan on jobmon

port.v IV43483: Change elapsed (seconds) to elapsed (minutes) in rep1.v IV43547: If a z/OS job ends with jcl or jcli the return code is set to 0.v IV44485: Error submitting schedules with alias 16 characters long on Aix

platforms.v IV44771: Makeplan failed due to an error in the code that can corrupt

the memory.v IV44802: Makeplan hangs.v IV44813: GSKit Encrypted Record Length Vulnerability.v IV44814: A vulnerability in relation to PKCS#12 operations and insertion

of Trust Anchor's exists with GSKit.v IV44823: OpenSSL versions prior to 1.0.0 do not follow best security

practises and need to upgrade.v IV44824: Jobs run at wrong time of day of DST shift back in Sydney.v IV444825: Potential security exposure with IBM WebSphere application

server after installing PM44303.v IV45042: Data collector tws_inst_pull_info.cmd is launched at final or

jnextplan time.v IV45220: Rmstdlist intermittently fails on windows clusters attempting

to remove locked file clu_offline.log.v IV45240: TWS on Windos error message on Windows event viewer.v IV45544: EDWA correlator match the event rule file on Windows agent

in case sensitive way.v IV45486: OpenSSL released fixes for 3 security vulnerabilities.v IV46103: Jobman is not able to find the ljuser definition in r3batch opts.v IV46504: Discrepancy between the output of rep1 and tdwc.


v IV46535: Update of the broker workstation even if the workstation notchanged.

v IV47074: startevtproc fails if thiscpu line in localopts has a comment.v IV47926: Composer validation errors when stream contains deadline

<days>.v IV47998: Job failed when jobname consists of special characters.v IV48720: Jobmon memory leaks for xa jobs and random crashes.v IV49858: Jobmanager does not start after reboot on Linux.v IV49950: Summary advisory for Oracle April and Oracle February 2013.v IV50202: Unable to process log message written events that contain an

equal sign in text string.v IV50242: Tws/Dwc ewas 86fp2 and 851fp5 on hp crash in groups

authenticating/authoring.v IV50769: Altpass "username" causes a core dump if enplanaudit is

enabled.v IZ33462: Unison_job environment variable incorrectly set.v IZ76319: TWS datecalc did not work on AIX.v IZ81893: Composer user security consistency checks not behaving the

same in jsc.

List of defects fixed:

v 70342: Ddriven: job ends in FAILED instead of SUCC -NullPointerException broker.

v 72719: post install checked tool defects on win64.v 75572: Error in long term switch handled by TSAMP when the name of

the workstation contained the string FTA, which breaks the updates inthe database for the long term switch.

v 77903: enEmptySchedsAreSucc=YES do not carryforward jobtream inhold state.

v 78114: Allow to cleanup tsamp resources while they are still active.v 78563: conman rerun: "at" and "pri" arguments ignoredv 79199: MDM WebSphere hangs repeatedly.v 82190: Some certificates are replaced.v 83368: Agent registration failure if the agent already exists.v 83841: Parentworkstation not filled during link breaks event rule.v 83906: TWS upgrade to 8.6 does not remove tlm signature of previous

releases.v 84522: AWSFAB025E message during installation.v 84550: Enhance messages on ChnageHostProperties.v 84927: Resource CLI: add network interfaces to computers details output

- RFE 81901.v 85369: Upgrade OpenSSL to version y.v 86705: reprt -post doesn't show X-AGENT (report 10A).v 86735: twsClusterUpg.vbs does not work well with blank.v 87766: Introduce a log message in the SystemOut.log related to the

validate.v 87880: Rule "file create" doesn't work.v 88312: Stop workstation issue.


v 88897: Security Exposure for JavaDoc.v 89912: On hp ita batchman goes down and generates a core.v 90334: New certificates.v 90487: New TSAMP policies porting.v 90900: Change the AWSJPL526W in trace.v 90903: Serviceability stageman.v 91292: FTP jobexecutor: add support for multibyte file transfer.v 92357: Interactive jobs wrong behavior with Win domain users.

APARs and defects fixed in Tivoli Workload Scheduler Fix Pack 2for version 8.6.0This section lists APARs and internal defects solved by Fix Pack 2.


v IV10778: DATABASE ERRORS GENERATED FROM TDWB.v IV12460: AWSJSYS514E ON OPENING JOBLOG OR PROPERTIES.v IV16852: REMOVE ICON ABOUT MULTIPLE FILE NAME IN THE

EVENT RULE FILENAMEFILECREATED,FILEDELETE,FILEMODIFICATIONCOMPLETEDETC.

v IV17252: LOGMAN CORE DUMPS DURING UPDATESTATS.v IV17967: REP11 DOES NOT OUTPUT CORRECT INFORMATION ON

WINDOWS 2008 R2.v IV18363: ADD THE CAPABILITY TO JOBMON TO LOAD THE USER

PROFILE ON WIN.v IV18644: REPTR -POST -DETAIL (10B) IS NOT DISPLAYING

COMPLETE JOB ID WHEN MAESTRO_OUTPUT_STYLE=LONG.v IV18646: FOLLOWS DEPENDENCY IS NOT HONORED IF JOB NAME

IS CHINESE.v IV19237: WEBSPHERE (JAVA) CRASHES INTERMITTENTLY RELATED

TO A MEMORY ALLOCATION FAILURE.v IV20588: CRITICAL JOB ALREADY IN PLAN WHEN WORKSTATION

IS IGNORED RESULTS IN TDWC AWSJCS011E"JAVA.LANG.NULLPOINTEREXCEPTION".

v IV20855: JOB IS REMOVED FROM JOBSTREAM THAT RUNS ONIGNORED FTA.

v IV20902: OPENS DEPENDENCY TREATING AN ENVIRONMENTVARIABLE INCORRECTLY.

v IV22018: CONMAN STOPAPP KEPT MSG ON APPSERVMAN QUEUE.v IV22822: MONMAN DONT SENT ERROR, "UNKWON STATUS" FOR

ALL JOBS.v IV23017: ERROR WHEN SUBMITTING JOBSTREAM USING

WORKSTATION CLASS.v IV23995: TWS FAILED TO RUN DB2 STORAGE PROCEDURE WHICH

INCLUDE OUTPUT PARAMETER.v IV24400: KILL JOB NOT TERMINATING PROCESSES WITH

WINDOWS TWS 8.4 FP06.v IV24925: FILE DETECTION EVENT TRIGGER DOES NOT WORK

PROPERLY.


v IV24951: JCL FIELD TRUNCATED IN THE HEADER OF THE BROKERJOB LOG.

v IV24995: MONITOR OF "RUNNING" STATUS EVENT RULE SEND 2EMAILS NOT 1.

v IV25204: TSM JOBS FAIL IF THE TSM OBJECT CONTAINS "\" CHAR.v IV25226: TWS MDM LEAKS MEMORY WHEN TDWC IS USED TO

QUERY THE PLAN AND THEQUERY RETURNS LESS OBJECTS THANTHE FILTER SELECTS FOR.

v IV25904: AFTER APPLYING FP01 TO 8.6 TDWC ENGINES ARE NOLONGER AVAILABLE,AND AFTER A NEW ENGINE IS CREATED ITIS NOT AVAILABLE.

v IV26764: "AWSBII005E UNDEFINED PARAMETER" CAUSESNATIVE_STERR.LOG GROWTH.

v IV27261: TMP , TEMP WITH BLANK SPACE GONE IN FAIL THE TWS8.5 FIXPACK.

v IV27605: JOBLOG UNRETRIEVABLE WITH ERROR AWSBIO027E THEOBJECT "<JOBNAME> COULD NOT BE FOUND.".

v IV27652: THE DEFAULT VALUE FOR TIMEOUT IN LOCALOPTSDOES NOT MATCH ACTUALDEFAULT.

v IV27906: FORECAST GENERATION UPDATES PREPRODUCTIONTABLE INCORRECTLY.

v IV28102: "ALIAS" ON "SUBMIT JOB STREAM INTO PLAN -PROPERTIES" IS NOT UPDATED AFTER UPDATING "ALIAS" ON"SUBMIT JOB STREAM INTO PLAN".

v IV28167: WINDOWS COMMAND JOB WITH BRACKET "(" GONE INABEND.

v IV28176: TWS 8.6 FP01 WHEN USING DOMAIN USER ANDTWSPATCH DOESNT INSTALL.

v IV28639: USERS ARE UNABLE TO RERUN, SUBMIT OR CONFIRMJOBS.

v IV29253: TWS 86 MDM RANDOMLY CRASHES PERFORMING PLANOPERATIONS.

v IV29255: TWS 86 MDM RANDOMLY CRASHES PERFORMINGCONCURRENTOPERATION LIKE QUERIES AND SUBMISSIONS.

v IV29556: UNEXPECTED TRACE BACKUP AFTER MAILMAN ORNETMAN RESTART.

v IV33031: EDWA: SSMAGENT STOP/START AFTER JNEXTPLAN.v IV31312: CREATING ER VIA TDWC 8.6, SETTING MULTIPLE

VARIABLE EVENTS FOR THE ACTION CAN CAUSE MULTIPLEBRACKETS OR INCORRECT VARIABLES.

v IV31942: DELETE JOB ON A TABLE MDL.JSF_JS_INST_FORECASTCAUSES EWAS HANG.

v IV31950: CAN'T VIEW BROKER JOBLOGS.v IV32318: COMPOSER CREATE TERMINATES WITH CORE

INTERMITTENLY AT GETBYTES.

List of defects fixed:

v 67954: Wrong duration of dynamic jobs on DST switch-off day.v 67975: Shadow jobs in ERROR state appear as Undecided in the

dashboard.


v 67979: Unable to perform a import of a job stream containing specialchars.

APARs and defects fixed in Tivoli Workload Scheduler Fix Pack 1for version 8.6.0This section lists APARs and internal defects solved by Fix Pack 1. Some APARsand internal defects need for resolution the GA fixed files, located under the\CD_number\GAFixes directory. For more details, see the “Downloading andreplacing files from GAFixes directory” on page 26.


v IV00371: ERROR AWSBCZ111E ENCOUNTERED WHEN CREATING AVARIABLE TABLE USING COMPOSER ADD.

v IV00639: ISSUE WITH RERUN OF JOBS, AFTER LATEST START TIME,WHICH INCLUDEAN EVERY" FREQUENCY, AND SUPPRESS AFTERLATEST START TIME.

v IV00662: "CONMAN SC;GETMON" FAILS WITH NO MSG:/USR/LOCAL/TWS851/MAE851/TWS/SYMPHONY,,,0,.

v IV00921: 8.5.1 FP2 OPENS HAS DOUBLE QUOTES AROUND THE FILENAME.

v IV01408: AFTER APPLYING 8.5 FP02 JOB STREAMS ARE NOTREMOVED FROM PLAN AFTER UNTIL TIME REACHED.

v IV01550: AFTER SWITCHMGR, SEVERAL DM'S FAIL TO LINKAUTOMATICALLY, AND REQUIRE A MANUAL RELINK.

v IV01873:JOB SUBMITTED WITH ALIAS VIA TDWC DOES NOT SHOWTHE ORIGINAL JOBNAME IN THE PLAN AUDIT LOG ORTWSMERGE.

v IV01885:TDWB AGENT GIVES AWSITA082E ERROR WHEN TWOHARDWARE SCAN HAPPENS WITHIN SECONDS OF EACH OTHER.

v IV02089: EWAS UPGRADE FAILS DUE TO NOT ENOUGH FREE DISKSPACE.

v IV02340: Time of predecessor jobs and dependency prompts on JSC andTDWC are in GMT

v IV02406: INTERNETWORK DEPS DONT WORK USING SCHEDTIMEWITH MULTIPLE JS.

v IV02414: MDM THREADS HANG WHEN AN ERROR READINGFROM SYMPHONY FILE OCCURS WHILE JOB LOGS ARERETRIEVED.

v IV02797: IN E2E ENVIRONMENT, CENTRALIZED SCRIPTS RUN ONUNIXLOCL EXTENDEDAGENTS (XAS), ONLY COMPLETE THE FIRSTLINE.

v IV03447: MAKEPLAN AND SWITCHPLAN SUCCEED WHENPLANMAN WAILS WITH AWSBEH021E ERROR.

v IV03559: SSMAGENT DOESN'T WORK IF TWS INSTALL PATH IS TOOLONG

v IV03894: DOES_NOT_MATCH IS IGNORED WHEN MULTIPLES AREUSED.

v IV06620: FIX THE MECHANISM USAGE TO CREATE THE JOB ALIASDURING ADHOC SUBMISSION.

v IV06734: CONNECTION ERROR LOGGED EVERY FIVE MINUTES IFDATABASE IS NOT AVAILABLE.


v IV06847: AWSJCO111E HAPPENS ON SAVING EVENT RULETHROUGH TDWC.

v IV07182: STAGEMAN FAILED WITH AWSBHV021E.v IV07279: TEMPORARY FILE IS CREATED AND NOT REMOVED BY

"COMPOSER REPLACE" OF JOBS.v IV07336: ZCENTRIC AGENT INSTALLATION IMAGE FOR WINDOWS

64 BIT VERSION .v IV07340: MAILMAN CORE DUMP AFTER FAILED LINK ATTEMPT TO

FTA CHECKHEALTHSTATUS FAILURE ON MDM MAILMAN LEADSTO COREDUMP.

v IV07655: Memory leak in netman process when starting a service.v IV07688: AWSJMR003E A TRANSPORT PROBLEM WAS FOUND -

GSKIT LIBRARIES.v IV07874: ERROR 500 WHEN ADDING JOB VIA COMPOSER.v IV07888: WINDOWS 'CPCH' COMMAND DOES NOT WORK AT

ZCENTRIC WORKSTATIONS.v IV08543: TSM INTEGRATION: TSM JOBS ABENDING WHEN PASSING

THE MIDNIGHT.v IV08700: TWS WEBSERVICE API RETURNS EPOCH DATE FOR START

AND END TIMES.v IV08995: CONMAN ALTPRI IS LOST WHILE SYMPHONY SWITCH.v IV09145: TWA_ENV SCRIPT FAILS TO SET PATH.v IV09379: AFTER SETTING A NEW UNTIL TIME, UNTIL DOES NOT

OCCUR AT A NEW UNTIL TIME.v IV09453: LATEST START TIME NOT WORKING CORRECTLY.v IV09908: PARAMETERS FILE DOES NOT GET IMPORTED IN TWS

8.5.1 UPGRADE USING TWSINST.SH.v IV10349: CONMAN RERUN FROM BEHAVES DIFFERENTLY THAN

JSC/TDWC RERUN FROM.v IV10400: DELAY IN VIEWING JOBLOG IN JSC ON HPUX.v IV10403: JOBMON HANG AFTER THE CLUSTER FAILOVER.v IV10438: FILEMODIFICATIONCOMPLETE EVENT RULES NOT

TRIGGER ON FTA.v IV10460: CONMAN CAN NOT LOAD ICU LIBRARIES.v IV11228: JOBMAN CRASHES WITH ERROR AWSBIK007E.v IV12331: MISSING JAR FILE WHEN USING JAVA API WITH TWS 8.6.v IV12413: IN THE CURRENT PLAN, "RELEASE JOB" COMMANDS ARE

DISCARDED FROM THE PREVIOUS DAY'S PRODUCTION PLAN INTIVOLI WORKLOAD SCHEDULER.

v IV12500: RUNCYCLES WITH RULE BYWORKDAY OR BYFREEDAY, INSOME CIRCUMSTANCES CAN SLOW-DOWN THE PLAN CREATION.

v IV12548: COMPOSER VALIDATE ON SCHEDULE'S FLAT FILEGENERATES AN ICALENDARERROR SYNTAX ERROR WHEN THERUN CYCLE IS LONGER THAN 128 BYTES.

v IV12564: EWAS IS NOT ABLE TO AUTHENTICATE LDAP GROUPMEMBERS FOR TWS.

v IV13189: INSTALLTEB.CMD FAILS ON WINDOWS WHILE INSTALLTWS 8.6 GA.


v IV13294: ZCENTRIC AGENT JOBS WITH STDERROR- ANDSTDOUTPUT-CARD EXECUTING POWERSHELL SCRIPTS HANGAND HAVE TO BE KILLED.

v IV13825: CONMAN TELLOP ADDS LINE BREAK.v IV13950: INLINE SCRIPTS WITH CURLY BRACKETS CAUSE JOB

FAILURE.v IV14569: INTERNETWORK DEPENDENCIES ARE NOT BEING

CLEARED WHEN CANCELED.v IV15366: TDWC 8.6 RUNNING A REPORT ON A CURRENT PLAN

WITH A LARGE SYMPHONY FILE RETURNS NO RESULTS.v IV15451: AWSBCV012E ON CHILD DM FOLLOWING SWITCHMGR.v IV15710: MVS OPENS DEPENDENCY IS NOT RECOGNIZED.v IV15887: JOBMANGER CRASH DUE SIGPIPE IF THE

COMMUNICATIONS WITH THE BROKER IS BROKEN, FOREXAMPLE NO TRUSTED CERTIFICATE.

v IV16134: AFTER CONMAN SUBMIT INPUTS BAD RECORD INTOSYMPHONY FILE.

v IV16852: REMOVE ICON ABOUT MULTIPLE FILE NAME IN THEEVENT RULE FILENAMEFILECREATED,FILEDELETE,FILEMODIFICATIONCOMPLETEDETC.

v IV17252: LOGMAN CORE DUMPS DURING UPDATESTATS.v IV17638: TWS 8.6:JOBS WITH AT BETWEEN 0000 AND SOD GET

START TIME ONE DAY LATE.v IV17907: MAKEPLAN RETURN 0 EVEN IF THE PLAN WAS NOT

CREATED AT ALL.v IV19237: WEBSPHERE (JAVA) CRASHES INTERMITTENTL.v IZ95386: TDWC SHOULD SHOW DEPENDENCIES AS THEY APPEAR

ON CONMAN.v IZ95391: WINDOWS OS ENVIRONMENT VARIABLE ARE

DUPLICATED SINCE KB ARTICLE HTTP://SUPPORT.MICROSOFT.COM/KB/2505238.

v IZ96555: TIMEOUT CONDITIONS RELATED TO ROUTER PROCESSUSED TO DOWNLOAD CENTRALIZED SCRIPTS. SIMILAR TO Z/OSAPAR PM30205.

v IZ97073: ZCENTRIC JOBS WITH '$ IN THE NAME GO IN ERROR.v IZ97356: ROUTER STUCK AFTER A PROBLEM CONNECTING THE

AGENT.v IZ98358: RMSTDLIST FAILS ON TWS 8.5.1 FP1 WINDOWS 2003

CLUSTER.v IZ98964: TWS JOBNUMBER INVALID IN EVENT.LOG ON LINUX

64BIT.v IZ99233: EVENT RULE ALLOWS JOB SUBMIT WHEN JOBSTREAM

SPECIFIED DOES NOT EXIST.v IZ99333: DELAY IN JOB STARTING EVEN THOUGH CANCEL

PENDING DEPENDENCY HAS BEEN PROCESSED.v IZ99697: THE NUMBER OF FILE DEPENDENCIES UNRESOLVED IS

SET TO 1, ALTHOUGH ALL OF THEM ARE RESOLVED.v IZ99755: NEW OPTION TO SKIP JOB EVERY INSTANCE IN LATE.


v IZ99893: LOG MESSAGE WRITTEN EVENT TRIGGERS 1 TRAP FOR NMESSAGES INSTEAD OF 1 TRAP PER MESSAGE.

v PM53893: TWS 8.6 and DWC 8.6: sharing eWAS hung.The Tivoli Workload Scheduler and Dynamic Workload Consoleinstances sharing the same Websphere Application Server, might becomeunresponsive after some days. This issue has been solved by this fixpack that embeds the new Tivoli Integrated Portal level.

List of defects fixed:This list contains the defects that fixed some of the limitations reported inthe Tivoli Workload Scheduler Version 8.6.0 Release Notes:v 52510: AWKRAA207E The EMF framework is not initialized properly

while starting Java Job for each job submitted on a zCentricv 52782: Was loop performing multiple EDWA actionsv 54123: Timeout during Symphony download.v 55321: event.log after JnexPlan,stop/start was, doesn't workv 55478: SCHEDULED TIME OF THE PREDECESSOR JOB IN GMT ON

TDWC.v 55750: 20110630_TWSMERGE.log have wrong group and onwer.v 55997: Composer tmp files should not be world-writable.v 56056: 851FP3 with Oracle fails to migrate to 86 (ORA-02443).v 58293: JobManager on DDM WIN2008 64bit dump continouslyv 58295: Solaris x86 JobManager dies after a while.v 58670: TWS trace folder increases size indefinitelyv 59723: master eWAS HANG: requesting a JOBLOG output of a database

job on 86FP1 agent and old master 8.6v 59846: Base: GVT: Unable to submit jobs on a workstation more than one

time CMVC(56476)v 59680: JnextPlan doesn't work after upgrade from TWS 851fp1 to 8.6GA.v 59763: SSO doesn't work (from TDWC 86 FP1) after master upgrade to

86 GA. See “Downloading and replacing files from GAFixes directory”on page 26.

v 59789: ssmagent dies to manage 50K events (1000 rules, 50 files)v 60190: Java Runtime Exception performing a pick list and executing java

jobs on HPIA64 machinev 60585: JobManager hang after submission of multiple java jobsv 60834: CIT step fails if you install TWS 86 GA after a TWS 86 fp1

installation on the same machine.v 60869: The apply FP1 operation fails on a Windows 64 bit machine.

Known limitations and workaroundsThe following are software limitations and workarounds that affect TivoliWorkload Scheduler version 8.6.0 Fix Pack 3:

During installation:

Fix Pack 3 installation in shared platforms (92777)Only for shared installations, you must perform the GeneralAvailability installation on all the shared platforms before applyingthis fix pack to any environment.


Fix Pack installation process overrides the resource cli and the Openssldefault certificates

The fix pack installation overrides the following sample certificates:

Truststore:

v <INSTALL_DIR>\TDWB_CLI\certs\TWSClientTrustFile.jks

v <INSTALL_DIR>\TWS\ssl\OpenSSL\TWSTrustCertificates.cer

Keystore:

v <INSTALL_DIR>\TDWB_CLI\certs\TWSClientKeyFile.jks

v <INSTALL_DIR>\TWS\ssl\OpenSSL\TWSClient.keyv <INSTALL_DIR>\TWS\ssl\OpenSSL\TWSClient.cer

Where <INSTALL_DIR> is the IBM Tivoli Workload Schedulerinstallation directory.

Notes:

1. If you have your own certificates named as the default samplescertificates saved in the default directory, the fix packinstallation process overrides your own resource cli andOpenssl certificates. Before installing the fix pack, back up yourresource cli and Openssl certificates and restore them afterinstalling the fix pack.

2. If you already performed the procedure to renew the defaultcertificates by using the 8.6.0-TIV-TWA-CERTIFICATES packagedownloaded from Fix Central, the fix pack installation processoverrides your renewed resource cli and Openssl defaultcertificates. Before installing the fix pack, back up your resourcecli and Openssl certificates and restore them after installing thefix pack.

Installation at step 0 doesn't stop with Tivoli Workload Schedulercommand lines opened (60595)

On AIX 6100-04-00 operating systems, the IBM Tivoli WorkloadScheduler fix pack installation might fail:

apply actionat step 0

rollback actionat step 12

One possible cause is that the process is unable to recognizewhether a file is locked, and is therefore unable to verify if the IBMTivoli Workload Scheduler command lines are open or if IBMTivoli Workload Scheduler jobs are running. Before installingrunning the fix pack, update the AIX operating system to a laterversion.

twspatch output completely corrupted on some Windows platforms(59219)

On platforms running Windows Vista, Windows 2008, or Windows2007, the output of the twspatch command is corrupt.


Workaround 1: Open the generated file with an editor supportingthe UTF-8 character set.

Workaround 2:v Redirect the output of the twspatch command to a filev Open a command prompt window and type chcp 65001

v Open the generated file with no errors

Missing config.ini settings after fix pack apply and undo (60221)If you apply the fix pack and then undo it, the original<tws_install_dir>\TWS\JavaExt\eclipse\configuration\config.ini file is restored. If, after the fix pack is applied andbefore it is undone, you installed any plug-in, the settings relatedto this plug-in are lost.

You can recover these settings from the <tws_install_dir>\TWS\JavaExt\eclipse\configuration\config.ini.tomerge file andmanually merge its content with the tws\javaext\eclipse\configuration\config.ini file.

Missing file after rollback from Fix Pack 2 to Fix Pack 1 (70043)If you rollback from Fix Pack 2 to Fix Pack 1 the following file ismissing: properties\version\Tivoli_Workload_Scheduler_Core.8.6.0.1

Fault-Tolerant Agent not working with distributor connector (61632)If you install this fix pack on a fault-tolerant agent and then installthe distributed connector, the fault-tolerant agent might have anunexpected behaviour.

Workaround: To avoid this, first install the distributed connectorand later apply this fix pack.

At run time:

Jobs

v The SmartCloud Provisioning job does not support the Power®

VM Hypervisor.v If you create a remote job using the Windows protocol and this

job runs a script that creates a long job log, the job might take along time to complete.

Remote command job - RSH protocolOn UNIX operating systems, the RSH protocol may use portsranging from 1 to 1024 only if you are authenticated as the rootuser. An user different from the root user must use a port numbergreater than 1024.

FIPS operational modeOn Solaris x86 with Intel chipset, FIPS operational mode is notsupported for Event Driven Workload Automation (EDWA) fileevents because of a limitation in the GSKit component on Solarisx86.

Recovering a corrupted plan from the latest archived plan

v Some Tivoli Workload Scheduler events that were triggeredbefore applying the recovery procedure, might be triggeredagain after the recovery procedure has completed. This limitationconcerns those events that are not managed through a messagequeue, for example, UNTIL, DEADLINE, and MAXDUR.


v Jobs that are in EXEC status when running the recoveryprocedure might appear duplicated in the recovered plan, oneinstance in the original job stream, and the second one inUSERJOBS. Should this occur, one of the two instances mightnot complete and must be deleted manually.

v Prompts in the recovered plan might have a prompt numberdifferent from the prompt number in the original plan. To avoida mismatch, prompt reply events are not recovered.

Windows rights requirements

v To run Tivoli Workload Scheduler command lines, in addition tostandard Windows rights to login to the server, users must havethe Impersonate a client after authentication right granted.By default, this is granted only to Administrators members. Thisis required to impersonate Tivoli Workload Scheduler users andto access Tivoli Workload Scheduler Symphony and Mailbox.This applies to both Windows 2003 and Windows 2008 operatingsystems with User Access Control (UAC) disabled. On Windows2008, by default the User Access Control is enabled, and theImpersonate a client after authentication right is notavailable to the user unless the command shell is started withthe parameter start as administrator. After that, users canauthenticate with their own userid.

v On both Windows 2003 and Windows 2008 operating systems,users must have the logon as batch right to create job processes.In addition, users must have Read and Read & Execute access tocmd.exe to use the BATCH built-in group.

v If a recovery is needed, to manage Tivoli Workload Scheduleragents, users must be in the Administrators group or be grantedto run the command runas as the user twsuser to reset the TivoliWorkload Scheduler files.

Message AWSBCU035E corrupted in languages different from EnglishThe messageAWSBCU035E Opening <object_name>, error: <error_name>

is corrupted when displayed in languages different from English.

Interactive jobs fail if user is not logged in to the active desktop sessionOn Windows 2008, Windows Vista and Windows 7 operatingsystems, before running an interactive job the user must be alreadylogged in to the desktop session where you plan to run theinteractive job. (IV37787)

Group authenticationOn HP-UX version 11iv3 operating systems, based on PA-RISCarchitecture releases subsequent September 2003 or Itaniumarchitecture, if you do a group authentication you must be surethat each line contained in the /etc/group file is not longer than4096 characters. (91244 - IV50242)

During uninstallation:

Graphical rollback might get stuck at times (RTC 61813)If you perform a graphical rollback of this fix pack, the processmight get stopped at the step Start the Tivoli WorkloadScheduler instance but the startup completes successfully. Thereason is that the machine has exhausted its resources.


Workaround: Kill the installation process, resume it, and run theother remaining steps.

Rollbacks on AIX might fail randomly (RTC 87962)Only on AIX operating systems, a rollback process might failbecause it cannot rename a locked file. This happens becauseshared libraries can still be located in the shared memory evenafter all the related applications have been shut down.

Workaround: Use the utility slibclean to unload from the sharedmemory any libraries that are no longer referenced. This utilityrequires no parameters.

After upgrade:

Certificates problem when upgrading a master domain manager V8.5.1, abackup master domain manager V8.5.1, a dynamic agent V8.5.1, and aTivoli Workload Scheduler for z/OS agent V8.5.1 to V8.6:

Problem description: The Tivoli Workload Scheduler installation orupgrade process V8.5.1 for the master domain manager, the backupmaster domain manager, the dynamic agent, and the TivoliWorkload Scheduler for z/OS agent, creates the followingcertificate:v On Windows operating systems:

<INSTALL_DIR>\TWS\ITA\TWSClientKeyStore.kdb

v On UNIX and Linux operating systems:<INSTALL_DIR>/TWS/ITA/bin/TWSClientKeyStore.kdb

where <INSTALL_DIR> is the directory where you installed the TivoliWorkload Scheduler instance.

The Tivoli Workload Scheduler installation or upgrade process V8.6for the master domain manager, the backup master domainmanager, the dynamic agent, and the Tivoli Workload Schedulerfor z/OS agent, creates the same certificate in the followingdifferent directories:v On Windows operating systems:

<INSTALL_DIR>\TWS\ITA\cpa\TWSClientKeyStore.kdb

v On UNIX and Linux operating systems:<INSTALL_DIR>/TWS/ITA/cpa/bin/TWSClientKeyStore.kdb

where <INSTALL_DIR> is the directory where you installed the TivoliWorkload Scheduler instance.

If you have already renewed the default certificates, either byusing the Procedure to renew the default certificates in adistributed environment or by using the Procedure to renew thedefault certificates for distributed components used in a z/OSenvironment for V8.5.1 or you used your own certificates, and youupgrade your Tivoli Workload Scheduler instance to V8.6, theTivoli Workload Scheduler ITA processes V8.6 use the incorrectdefault certificate installed in the new directory.

Problem solution: To manage the incorrect default certificate, afterthe master domain manager, backup master domain manager,dynamic agent, and Tivoli Workload Scheduler for z/OS agentupgrade process to V8.6, perform the following procedure:


1. Stop the Tivoli Workload Scheduler agent processes that use theincorrect default certificate by running:v On Windows operating systems:

ShutdownLwa.bat

v On UNIX and Linux operating systems:ShutdownLwa

For more information about the command syntax, see User'sGuide and Reference.

2. Modify the default certificate, by copying theTWSClientKeyStore.kdb file:v On Windows operating systems, from the directory

<INSTALL_DIR>\TWS\ITA\bin to the directory<INSTALL_DIR>\TWS\ITA\cpa\bin

v On UNIX and Linux operating systems, from the directory<INSTALL_DIR>/TWS/ITA to the directory <INSTALL_DIR>/TWS/ITA/cpa

where <INSTALL_DIR> is the directory where you installed theTivoli Workload Scheduler instance.

3. Start the Tivoli Workload Scheduler agent processes that usethe modified default certificate by running:v On Windows operating systems:

StartUpLwa.bat

v On UNIX and Linux operating systems:StartUpLwa

For more information about the command syntax, see User'sGuide and Reference.

Compatibility with earlier versionsThe following are compatibility issues with earlier versions of the product.

The maxdur and mindur job stream definition keywords work with the followingcomponent versions:v Master domain manager version 8.6.0.2v Dynamic agents version 8.5.1.4 or laterv Fault tolerant agents version 8.6.0.2 or later

On fault tolerant agents version 8.6.0.1 or earlier, ONMAXDUR KILL on the Masterdomain manager displays the [MaxDurationExceeded] and [KillSubmitted] flags,but the job remains in EXEC status because it is not killed locally. Two events, JobExceeded Maximum Duration and Job Did not Reach Minimum Duration, do notwork.

Globalization notesNone.

Fix pack structureThis section describes the structure of the images contained in this fix pack.


Fix pack files available for Tivoli Workload Scheduler usingFix Central

This is the structure of the fix pack for the engine on Fix Central:+---8.6.0-TIV-TWS-FP0003.README (this file in text format)|+---8.6.0-TIV-TWS-FP0003.pdf (this file in pdf format)|+---8.6.0-TIV-TWS-FP0003.VSR|+---8.6.0-TIV-TWS-AIX-FP0003.zip|+---8.6.0-TIV-TWS-HPUX-FP0003.zip|+---8.6.0-TIV-TWS-HPIA64-FP0003.zip|+---8.6.0-TIV-TWS-LINUX_I386-FP0003.zip|+---8.6.0-TIV-TWS-LINUX_PPC-FP0003.zip|+---8.6.0-TIV-TWS-LINUX_S390-FP0003.zip|+---8.6.0-TIV-TWS-LINUX_X86_64-FP0003.zip|+---8.6.0-TIV-TWS-SOLARIS-FP0003.zip|+---8.6.0-TIV-TWS-SOLARIS_I386-FP0003.zip|+---8.6.0-TIV-TWS-WINDOWS-FP0003.zip|+---8.6.0-TIV-TWS-WINDOWS_X86_64-FP0003.zip|+---8.6.0-TIV-TWS-IBM_I-FP0003.tar|+---8.6.0-TIV-WSSDK-WINDOWS-FP003.zip|+---8.6.0-TIV-WSSDK-WINDOWS_X86_64-FP003.zip|+---8.6.0-TIV-WSSDK-LINUX_X86_64-FP003.zip|+---8.6.0-TIV-WSSDK-LINUX_I386-FP003.zip

Fix pack files available for batch reports using Fix CentralThis is the structure of the fix pack for batch reports on Fix Central; they have notchanged since Fix Pack 1:+---8.6.0-TIV-REPCLI-SOLARIS_I386-FP0001.tar|+---8.6.0-TIV-REPCLI-AIX-FP0001.tar|+---8.6.0-TIV-REPCLI-WINDOWS-FP0001.zip|+---8.6.0-TIV-REPCLI-LINUX_PPC-FP0001.tar|+---8.6.0-TIV-REPCLI-HPUX-FP0001.tar|+---8.6.0-TIV-REPCLI-SOLARIS-FP0001.tar|+---8.6.0-TIV-REPCLI-LINUX_X86_64-FP0001.tar|+---8.6.0-TIV-REPCLI-HPIA64-FP0001.tar|+---8.6.0-TIV-REPCLI-WINDOWS_X86_64-FP0001.zip|


+---8.6.0-TIV-REPCLI-LINUX_I386-FP0001.tar|+---8.6.0-TIV-REPCLI-LINUX_S390-FP0001.tar

Fix pack file available for Tivoli Endpoint Manager using FixCentral

This is the structure of the fix pack for Tivoli Endpoint Manager Analyses andFixlets for Tivoli Workload Scheduler Agents patch management on Fix Central:+---8.6.0-TIV-TWS-TEM-FP0003.zip

Installing the fix packThis section describes how to apply Fix Pack 3 to Tivoli Workload Schedulerversion 8.6.0.

The section is divided into the following subsections:v “Creating a fix pack installation package for a specific Tivoli Workload Scheduler

component”v “Downloading and replacing files from GAFixes directory” on page 26v “Installation notes” on page 27v “Disk space requirements” on page 30v “Updating the Tivoli Workload Scheduler database” on page 32v “Performing a safe fix pack installation” on page 37v “Product actions when applying the fix pack” on page 40v “Installation actions” on page 39v “Installing using the ISMP wizard” on page 44v “Installing using the ISMP silent installation” on page 45v “Installing using the twspatch script” on page 45v “Installing using Software Distribution” on page 47v “Installing the fix pack on fault-tolerant agents when there are corrupt registry

files” on page 48v “Configuring properties for the dynamic workload broker command line” on

page 51v “Rolling back the fix pack installation” on page 51v “Uninstalling the entire Tivoli Workload Scheduler instance” on page 51v “Installation log files” on page 51

Creating a fix pack installation package for a specific TivoliWorkload Scheduler component

In Tivoli Workload Scheduler version 8.6, you could choose to download either theeImage for the platform, which contains the installation package for all thecomponents for that platform, or just the specific eImage for the component yourequire. In Tivoli Workload Scheduler version 8.6 Fix Pack 3, you must downloadthe eImages for the platform and you can use this package to install Fix Pack 3 forall the components or you can create the specific installation package for thecomponent you need, by running a script located in the Fix Pack 3 eImages.

The Tivoli Workload Scheduler version 8.6 Fix Pack 3 eImages contain a script foreach platform, which creates the specific package for the component from theoriginal fix pack eImages.


Before installing Tivoli Workload Scheduler version 8.6, if you want to create aspecific component image to install, perform the following procedure:1. Download locally Tivoli Workload Scheduler version 8.6 Fix Pack 3 images.2. From the <platform>\tws_tools\ directory, run:

Windows operating systemcreateTWSFPImage.bat -type fta|agent[-destination <NEW_IMAGE_DIR>][-removeSetup true|false]

UNIX and Linux operating systemscreateTWSFPImage.sh -type fta|agent[-destination <NEW_IMAGE_DIR>][-removeSetup true|false]

where

type This parameter is required. Specify fta for fault-tolerant agentimage or agent for Tivoli Workload Scheduler agent (agent,dynamic agent, or agent for z/OS).

destinationThis parameter is optional. Specify the absolute path for thefolder that contains the new image. The default is the folderwhere the current image is located and the script runs. If thedestination is not specified, the script removes locally the filesnot needed for the image type chosen.

removeSetupThis parameter is optional. Specify that the new image does notcontain the ISMP file SETUP.exe for Windows operating systemsor SETUP.bin for UNIX operating systems. The default is falseand the new image created contains the ISMP file.

Example 1On a Windows machine, if you want to create the image to install Fix Pack3 on a fault-tolerant agent installed on an AIX operating system, usingtwspatch script, perform the following actions:1. Download the Fix Pack 3 eImage for the AIX platform on the Windows

machine.2. To create the Fault-Tolerant Agent component image on the directory

C:\Documents and Settings\Administrator, from the directoryAIX\tws_tools\ , run:createTWSFPImage.bat -type fta-destination "C:\Documents and Settings\Administrator"-removeSetup true

Note: In this example you set removeSetup to true because, to install withtwspatch, you do not need the file SETUP.bin.

Example 2On a Windows machine, if you want to create, the image to install FixPack 3 for an Agent for z/OS installed on a Windows operating system,using the wizard, perform the following actions:1. Download the Fix Pack 3 eImage for the Windows platform on the

Windows machine.2. To create the Agent for z/OS component image on the directory

C:\Documents and Settings\Administrator, from the directoryWindows\tws_tools\ run:


createTWSFPImage.bat -type agent-destination "C:\Documents and Settings\Administrator"

Downloading and replacing files from GAFixes directoryThe Tivoli Workload Scheduler version 8.6 Fix Pack 3 images contain the directoryGAFixes, which includes the fixed files for General Availability installation.

Before restarting the Tivoli Workload Scheduler version 8.6 installation, performthe following procedure:1. Download locally Tivoli Workload Scheduler version 8.6 images.2. Download locally Tivoli Workload Scheduler version 8.6 Fix Pack 3 images.3. Go to the GAFixes directory and perform the actions described below:

92352 On Oracle RDBMS, the upgrade of Tivoli Workload Scheduler to TivoliWorkload Scheduler V8.6 or later versions might fail if the MDL_USERname is written in lower case in the customized SQL script. To avoidthis issue, write always the name in upper case. Fix Pack 3 imagesprovide the files to fix the problem if the MDL_USER name is writtenin lower case.v Replace the following file:

– GAFixes\tws_tools\oracle\check_FKJHRJOD01.sql

in the directory <platform>\TWS\<platform> of Tivoli WorkloadScheduler version 8.6 images.

71479 If in your Tivoli Workload Automation instance you have a DynamicWorkload Console version 8.4 installed with default options and stillusing the File Registry as User Authentication method, you might havean issue upgrading the Tivoli Workload Scheduler to version 8.6. Toavoid this issue, change the file <TWS_86_IMAGES>\TWS\<platform>\tws_tools\ChangeSecurityProperties.jacl with that one providedwith Tivoli Workload Scheduler version 8.6 Fix Pack 3 images in thefollowing path: <TWS86_FP02_IMAGES>\<platform>\GAFixes\tws_tools\ChangeSecurityProperties.jacl.

69898 The Tivoli Workload Scheduler upgrade to version 8.6 on ORACLEwith the partitioning support enabled, might fail during the "Configurethe Tivoli Workload Scheduler Database" step due to an issue related tothe discovery of the tablespace name. This issue is caused by the wrongvalue of the tablespace name retrieved during the upgrade process. TheFix Pack 3 images provide the file to address this problemv Replace the following file:

– GAFixes\tws_tools\oracle\query_catalog.sql

in the directory <platform>\TWS\<platform>\tws_tools\oracle ofTivoli Workload Scheduler version 8.6 images.

59763 If you have an earlier version of Dynamic Workload Console and TivoliWorkload Scheduler installed that share the same LDAP user Registryand they are configured to use SSO (Single Sign-On) and you upgradethe Dynamic Workload Console, the Tivoli Workload Scheduler or bothto version 8.6.0, the SSO configuration is lost. Fix Pack 3 imagesprovide the files to fix the problem.v Replace the following file:

– GAFixes\tws_tools\ChangeSecurityProperties.jacl


in the directory <platform>\TWS\<platform>\tws_tools of TivoliWorkload Scheduler version 8.6 images.

59608 On Windows operating systems, Tivoli Workload Scheduler version 8.6installation fails if you use the SYSTEM user. Fix Pack 3 images providethe files to fix the problem.v Replace the following file:

– GAFixes\twsinst.vbs


56084 The installation of a Dynamic agent on an Iseries machine, using thetwsinst method on a QP2TERM fails, because the installation process isunable to start the agent. Fix Pack 3 images provide the files to fix theproblem.v Replace the following file:

– GAFixes\twsinst


4. If step 3 completed successfully, start the installation from Tivoli WorkloadScheduler version 8.6 images.

5. If step 4 completed successfully, start the fix pack installation from TivoliWorkload Scheduler version 8.6 Fix Pack 3 images.

Installation notesWhen installing the Tivoli Workload Scheduler, follow these recommendations:v The fix pack installation overrides the following sample certificates:

Truststore:

– <INSTALL_DIR>\TDWB_CLI\certs\TWSClientTrustFile.jks– <INSTALL_DIR>\TWS\ssl\OpenSSL\TWSTrustCertificates.cer

Keystore:

– <INSTALL_DIR>\TDWB_CLI\certs\TWSClientKeyFile.jks– <INSTALL_DIR>\TWS\ssl\OpenSSL\TWSClient.key– <INSTALL_DIR>\TWS\ssl\OpenSSL\TWSClient.cer

Where <INSTALL_DIR> is the IBM Tivoli Workload Scheduler installationdirectory. For more information about to solve the problem, see Known limitationsand workarounds section.

v Before installing the Tivoli Workload Scheduler Fix Pack 3, if you have notinstalled the Tivoli Workload Scheduler Fix Pack 1 for version 8.6.0, you mustperform the following actions:

You installed the batch reports version 8.6.0

1. Rename the directory TWSBatchReportCli, where you installed thebatch reports version 8.6.0 to TWSBatchReportCli_old.

2. In the directory TWSBatchReportCli, download the file8.6.0-TIV-REPCLI-<operating system>-FP0001.tar version 8.6 FixPack 1 images where operating system is the platform where you wantto perform the installation.


3. To extract the package in the directory TWSBatchReportCli, see TivoliWorkload Scheduler: User's guide and Reference > Getting reports andstatistics > Running reports and batch reports > Running batch reportsfrom the command line interface

4. Back up the TWSBatchReportCli\config\common.properties file andall the templates stored in TWSBatchReportCli\reports\templates.

5. Merge the TWSBatchReportCli\config\common.properties file withthe TWSBatchReportCli_old\config\common.properties file.

6. Copy the customized files from TWSBatchReportCli_old\reports\templates to TWSBatchReportCli\reports\templates.

You do not have the batch reports version 8.6.0 installed

1. In the directory TWSBatchReportCli, download the file8.6-TIV-REPCLI-<operating system>-FP0001.tar version 8.6 Fix Pack1 images, where operating system is the operating system on whichyou want to perform the installation.

2. For more information, see TWSBatchReportCli, see Tivoli WorkloadScheduler: User's guide and Reference > Getting reports and statistics >Running reports and batch reports > Running batch reports from thecommand line interface.

v On UNIX only: Before installing the Tivoli Workload Scheduler fix pack version8.6.0.02, ensure that your umask is set to 022. To verify that umask is set to thecorrect value, from a command prompt run the umask command. If the value isdifferent from 022, modify it by running:umask 022

v On UNIX operating systems, the data base administrator must have read andrun privileges for the Tivoli Workload Scheduler installation path; otherwise theinstallation fails. (54367)

v On UNIX operating systems, the installation might fail with a messageindicating that there is a problem when validating the Java Virtual Machine(JVM). This might be caused by a timeout problem. The InstallShield wizarduses a default timeout of 5 seconds during its operations to validate the versionof Java Virtual Machine that you have installed, which might be insufficient.Before launching the installation wizard again, increase the timeout value byrunning the following command:-is:jvmtimer 100

This extends the timeout to 100 seconds, and if you still get the same errormessage, increase it to 200 seconds.On workstations running Linux Red Hat 64-bit, if the problem persists, set thevariable setenforce to 0 using the following command:/usr/sbin/setenforce 0

and then launch the installation again.v To install, undo, and commit the fix pack, use the same installation method

(ISMP, twspatch) that you used to install the General Availability version.

Note: If you install the fix pack with the action APPLY using the installationmethod twspatch, to roll back to the previous level, use the commandtwspatch -undo. To uninstall the entire Tivoli Workload Schedulerinstance, use the command twspatch remove, but note that this action isnot intended to remove the applied fix pack without also uninstalling theinstance (51112).


v On Windows operating systems, do not install from a Samba diskv On HP-UX, systems, the default value for the kernel parameter max_thread_proc

is 64. Set this value to at least 128 otherwise the installation can fail and causeJava™ to generate a core dump.

v If you get an error message indicating insufficient space for the installationwizard temporary data in the default /tmp directory, you can launch theinstallation wizard with the is flag and set an alternative temporary directory.For example, SETUP.sh [-is:tempdir <temporary_directory>]. For additionalinformation about disk and space requirements for the installation, see Detailedsystem requirements.

v If you get an error message indicating permission denied for the installationprocess, to run a script in the tws_tools directory as a user, different from theroot user because this user does not have write, read, and execute rights in thisdirectory, you must:1. Unzip the eImages in a directory where all users have write, read, and

execute rights.2. Restart the installation process from this directory.

v Before updating the Tivoli Workload Scheduler services and DLL, it is stronglyadvised to put the Tivoli Workload Scheduler resources offline and the nodes inpause. (IV09792)

After the fix pack installation completes, verify the following information:v On IBM i operating systems, if you want to install the fix pack on the Tivoli

Workload Scheduler for z/OS Agent and Tivoli Workload Scheduler DynamicAgent, verify that the User profile used as TWSUser is not a member of a groupprofile. Set the group profile associated with the TWSUser to *NONE. If theTWSUser is a member of a group, the fix pack installation fails.

v After installing the fix pack, the last line of the TWS_home/version/patch.info filecontains: 8.6.0-TIV-TWS-FP0002.

v During the fix pack installation the following file is removed and a new one iscreated when the WebSphere® Application Server is restarted:TWA_home/eWAS/profiles/TIPPprofile/temp/TWS/EIFListener/eif.templ

If you previously modified the property BuffEvtmaxSize, after installing the fixpack you must set it again in the new file, as described in the IBM TivoliWorkload Scheduler Administration Guide, Chapter 9, Administrative tasks, sectionManaging the event processor. (38192)

v On Windows systems, jobs that belong to Final jobstream, go into abend state ifthe Master domain manager is installed in a directory other than the C: drive.Workaround: To solve this problem, merge the content of these files:<tws_home>\ResetPlan.cmd<tws_home>\JnextPlan.cmd<tws_home>\MakePlan.cmd<tws_home>\SwitchPlan.cmd<tws_home>\CreatePostReports.cmd<tws_home>\UpdateStats.cmd

with those under <tws_home>\config. They are not replaced by fix packinstallation because they can be customized. (53435)

v There is a mismatch for some Tivoli Workload Scheduler environment variables.

UNISONHOMEOn Windows operating systems, it does not exist or is blank.


On UNIX operating systems, it is the value of the UNISONHOMEvariable, set in the user environment. If not specified, its value is set tothe user home directory.

This variable must have, on all operating systems, the value of the pathwhere the Tivoli Workload Scheduler instance is installed.

HOMEThis variable is not documented for Windows operating systems, but isthe path where the Tivoli Workload Scheduler instance is installed.

On UNIX operating systems it is the user home directory. (53442)v To grant permissions to users on the updated database views, run the dbgrant

script again after the fix pack installation, only if the following conditions areboth satisfied:– The database used by Tivoli Workload Scheduler is DB2®.– The dbgrant script was already run before installing this fix pack. (38487)

v Only on Windows operating systems, after the fix pack installation, a newversion of file twa_env.bat is created in the following directory:<tws_home>\TWS\config. If you customized the original file <tws_home>\twa_env.bat, you must merge the content of these files to keep yourcustomization. (55999)

v Only on UNIX operating systems, after the fix pack installation, a new versionof file tws_env.sh is created in the following directory: TWS_home/config. If youhave customized the original file TWS_home/tws_env.sh, you must merge thecontent of these files to keep your customization. (56791)

v After the fix pack installation, if you run the command conman sc;info, it showsthe old product version. To get the updated version, wait for the next plan to becreated and distributed. However, the updated version is in the file<tws_home>\version\patch.info immediately after the fix pack installation. (RTC59988)

v After installing the fix pack on a fault tolerant agent with all configured clusternodes, the output shows the old product version for the DLLs installed on eachnode. In any case, the nodes are updated and if you run again the command toshow the version, you get the current product version. (RTC 59999)

v When connecting to the Dynamic Workload Console V8.6 Fix Pack 3, using thesame browser previously used to connect before the fix pack installation, thebrowser might still display page elements related to the Dynamic WorkloadConsole V8.6. This behaviour is not expected to cause any product malfunctions;however, to prevent it, clear the browser cache. (RTC 61420)

v When installing Tivoli Workload Scheduler V8.6 General Availability (GA) on afault tolerant agent using the twsinst installation script, the license directory isnot created and the license files are not copied on the fault tolerant agent. If youwant to access these files, you can find a copy on the installation CDs in thedirectory TWS/License. (RTC 61947)

v Only on Windows operating systems, the fix pack installation fails if theWindows environment variable PATH does not contain the folder%WINDIR%\SYSTEM32. (IV27352)

Disk space requirementsBefore starting the fix pack installation, ensure that you have the following spaceavailable in the file system:


Table 1. Disk space requirements for installing a Master domain manager or a backupmaster fix pack

OperatingSystem

Installationdirectory

Softwaredistributioninstallationdirectory Temporary directory

AIX® 2 GB 400 MB 500 MB

HP-UX 2.5 GB 400 MB 720 MB

Solaris 2 GB 400 MB 720 MB

MicrosoftWindows

2 GB 400 MB 500 MB

Linux 2 GB 400 MB 500 MB

Table 2. Disk space requirements for installing Tivoli Workload Scheduler agents and theJava Extension fix pack

OperatingSystem



AIX 1500 MB 300 MB 40 MB

HP-UX 1700 MB 300 MB 40 MB

Solaris 1500 MB 300 MB 40 MB

MicrosoftWindows

1500 MB 300 MB 40 MB

Linux 1500 MB 300 MB 40 MB

Table 3. Disk space requirements for installing Tivoli Workload Scheduler agents fix pack

OperatingSystem



AIX 20 MB 80 MB 40 MB

HP-UX 20 MB 80 MB 40 MB


MicrosoftWindows

20 MB 80 MB 40 MB


Table 4. Disk space requirements for installing the Tivoli Workload Scheduler for z/OS agentfix pack

OperatingSystem



AIX 20 MB 20 MB 40 MB

HP-UX 500 MB 20 MB 40 MB



Table 4. Disk space requirements for installing the Tivoli Workload Scheduler for z/OS agentfix pack (continued)

OperatingSystem



MicrosoftWindows

20 MB 20 MB 40 MB


Note: Only on HP and Solaris operating systems, the fix pack installation requiresalso 300 MB free disk space in the temporary directory /var/tmp.

Updating the Tivoli Workload Scheduler databaseThe features released with Fix Pack 3 require that the Tivoli Workload Schedulerdatabase is updated to the latest level. If you have manually created the database(following the procedure described in the Planning and Installation Guide), youmust upgrade it manually. Before launching the fix pack installation, depending onthe type and version of the database you have installed, run the followingcommands to update the database to the latest level required by the current fixpack.

If you have not manually created the Tivoli Workload Scheduler database, noadditional actions are required and the fix pack installation updates automaticallythe database.

DB2 These are the steps to be performed to upgrade the database to the latestlevel if your database is DB2. Run the appropriate set of commandsdepending on the database version you have installed:

Version 8.6.0.00 (8.6 General Availability)

1. Copy the SQL files from the Tivoli Workload Scheduler imagesa. Copy the following Tivoli Workload Scheduler SQL files:

upgrade_ANY_FKJHRJOD01.sqlupgrade_ANY_JHRJODIDNULL.sqlupgrade_ANY_JOBMAXDUR.sql

from <TWA_FP_IMAGE_DIR>\<platform>\tws_tools to<TMP_DIR>\sql.

b. Copy the following Tivoli Dynamic Workload Broker SQLfiles:upgrade_ANY_ZANRDRTIME.sqlupgrade_8.6.0.00_8.6.0.01.sqlupgrade_ANY_IBROKERJOB04.sql

from <TWA_FP_IMAGE_DIR>\<platform>\tws_tools\tdwb to<TMP_DIR>\tdwb\sql.

2. Customize the SQL filesOpen the file <TMP_DIR>\tdwb\sql\upgrade_ANY_ZANRDRTIME.sqland change with the right value all the occurrences of thefollowing place holder strings:@TWS_TS_NAME@@DB_USER@


where:v TWS_TS_NAME is the name of the DB2 instance table space. This

table space is used to store scheduling objects and eventrules. For information about DB2 table spaces, see the DB2documentation. The default table space name is TWS_DATA.When the administrator installs the product, he must specifythis value in the Tablespace name field.

v DB_USER: If you are creating the database tables beforeinstalling the product, specify the user that must have accessto the Tivoli Workload Scheduler database. When theadministrator installs the product, he must specify this valuein the DB2 server administrator user field. On Windowsoperating system, the default value is db2admin. On UNIXand Linux operating systems, the default value is db2inst1;verify that you can switch to this user and that he can loadthe DB2 environment.If you are upgrading the database tables before upgradingthe product, specify the user that you used when youinstalled the version of the product you are upgrading. Whenyou later upgrade the product, you can specify a userdifferent from the one you specified in the DB_USER field, butit must have database access permissions.

3. Run the SQL filesa. For Tivoli Workload Scheduler, run the following

commands:db2 -v -t -f <TMP_DIR>\sql\upgrade_ANY_FKJHRJOD01.sqldb2 -v -t -f <TMP_DIR>\sql\upgrade_ANY_JHRJODIDNULL.sqldb2 -v -t -f <TMP_DIR>\sql\upgrade_ANY_JOBMAXDUR.sql

b. For Tivoli Dynamic Workload Broker, run the followingcommands:db2 -v -t -f <TMP_DIR>\tdwb\sql\upgrade_ANY_ZANRDRTIME.sqldb2 -v -t -f <TMP_DIR>\tdwb\sql\upgrade_8.6.0.00_8.6.0.01.sqldb2 -v -t -f <TMP_DIR>\tdwb\sql\upgrade_ANY_IBROKERJOB04.sql

Version 8.6.0.01 (8.6 Fix Pack 1) or 8.6.0.02 (8.6 Fix Pack 2)

1. Copy the SQL files from the Tivoli Workload Scheduler imagesa. Copy the following Tivoli Workload Scheduler SQL file:

upgrade_ANY_JOBMAXDUR.sql

from <TWA_FP_IMAGE_DIR>\<platform>\tws_tools to<TMP_DIR>\sql.

b. Copy the following Tivoli Dynamic Workload Broker SQLfile:upgrade_ANY_IBROKERJOB04.sql

from <TWA_FP_IMAGE_DIR>\<platform>\tws_tools\tdwb to<TMP_DIR>\tdwb\sql.

2. Run the SQL filesa. For Tivoli Workload Scheduler, run the following command:

db2 -v -t -f <sql_directory>\sql\upgrade_ANY_JOBMAXDUR.sql

b. For Tivoli Dynamic Workload Broker, run the followingcommand:db2 -v -t -f <sql_directory>\DWB\sql\upgrade_ANY_IBROKERJOB04.sql


ORACLEThese are the steps to be performed to upgrade the database to the latestlevel if your database is Oracle. Run the appropriate set of commandsdepending on the database version you have installed:

Version 8.6.0.00 (8.6 General Availability)

1. Copy the SQL files from the Tivoli Workload Scheduler imagesa. Copy the following Tivoli Workload Scheduler SQL files:

upgrade_ANY_FKJHRJOD01.sqlupgrade_ANY_JHRJODIDNULL.sqlupgrade_ANY_JOBMAXDUR.sql

from <TWA_FP_IMAGE_DIR>\<platform>\tws_tools\oracle to<TMP_DIR>\sql.

b. Copy the following Tivoli Dynamic Workload Broker SQLfiles:upgrade_8.6.0.00_8.6.0.01.sqlupgrade_ANY_IBROKERJOB03.sqlupgrade_ANY_IBROKERJOB04.sql

from <TWA_FP_IMAGE_DIR>\<platform>\tws_tools\tdwb\oracle to <TMP_DIR>\tdwb\sql.

2. Customize the SQL filesOpen the following files:<TMP_DIR>\sql\upgrade_ANY_FKJHRJOD01.sql<TMP_DIR>\sql\upgrade_ANY_JHRJODIDNULL.sql<TMP_DIR>\sql\upgrade_ANY_JOBMAXDUR.sql<TMP_DIR>\tdwb\sql/upgrade_8.6.0.00_8.6.0.01.sql<TMP_DIR>\tdwb\sql/upgrade_ANY_IBROKERJOB03.sql<TMP_DIR>\tdwb\sql/upgrade_ANY_IBROKERJOB04.sql

and change with the right value all the occurrences of thefollowing place holder string:@MDL_USER@

where:v MDL_USER is the database administrator user name, for

example: SYSTEM, that access the Tivoli Workload Schedulerand the Dynamic Workload Broker database. This user mustbe created on Oracle and is not an operating system user.When the administrator installs the product, he must specifythis value in the Oracle administrator user field.

3. Run the SQL filesa. For Tivoli Workload Scheduler, run the following

commands:sqlplus -L <TWS_MDL_USER>\<TWS_MDL_PW>@<ORACLE_NET_SERVICE_NAME> @<TMP_DIR>\sql\upgrade_ANY_FKJHRJOD01.sql

sqlplus -L <TWS_MDL_USER>\<TWS_MDL_PW>@<ORACLE_NET_SERVICE_NAME> @<TMP_DIR>\sql\upgrade_ANY_JHRJODIDNULL.sql

sqlplus -L <TWS_MDL_USER>\<TWS_MDL_PW>@<ORACLE_NET_SERVICE_NAME> @<TMP_DIR>\sql\upgrade_ANY_JOBMAXDUR.sql


b. For Tivoli Dynamic Workload Broker, run the followingcommands:sqlplus -L <TWS_MDL_USER>\<TWS_MDL_PW>@<ORACLE_NET_SERVICE_NAME> @<TMP_DIR>\tdwb\sql\upgrade_8.6.0.00_8.6.0.01.sql

sqlplus -L <TWS_MDL_USER>\<TWS_MDL_PW>@<ORACLE_NET_SERVICE_NAME> @<TMP_DIR>\tdwb\sql\upgrade_ANY_IBROKERJOB03.sql

sqlplus -L <TWS_MDL_USER>\<TWS_MDL_PW>@<ORACLE_NET_SERVICE_NAME> @<TMP_DIR>\tdwb\sql\upgrade_ANY_IBROKERJOB04.sql

where:v TWS_MDL_USER is the user you specified in the MDL_USER

field of the property file.v TWS_MDL_PW is the password of the MDL_USER.v ORACLE_NET_SERVICE_NAME is the name used by clients to

identify an Oracle Net server and the specific systemidentifier or database for the Oracle Net connection. A netservice name is mapped to a port number and protocol. Itis also known as connect string, database alias, host string,or service name. At installation time, the administratormust specify this value in the Net service name field.If your Oracle database is installed on the same systemwhere you are installing your master domain manager ora backup master, the net service name is the name ofyour Oracle database..If your Oracle database is installed on the same systemwhere you are installing your dynamic domain manageror a backup dynamic domain manager, the net servicename is the name of your Oracle database.If your Oracle database is not installed on the systemwhere you are installing your master domain manager ora backup master, the net service name is the aliasconfigured for the connection to the remote database.If your Oracle database is not installed on the systemwhere you are installing your dynamic domain manageror a backup dynamic domain manager, the net servicename is the alias configured for the connection to theremote database.

Version 8.6.0.01 (8.6 Fix Pack 1) or 8.6.0.02 (8.6 Fix Pack 2)

1. Copy the SQL files from the Tivoli Workload Scheduler imagesa. Copy the following Tivoli Workload Scheduler SQL file:

upgrade_ANY_JOBMAXDUR.sql

from <TWA_FP_IMAGE_DIR>\<platform>\tws_tools\oracle to<TMP_DIR>\sql.

b. Copy the following Tivoli Dynamic Workload Broker SQLfiles:upgrade_ANY_IBROKERJOB04.sql


from <TWA_FP_IMAGE_DIR>\<platform>\tws_tools\tdwb\oracle to <TMP_DIR>\tdwb\sql.

2. Customize the SQL filesOpen the following files:<TMP_DIR>\sql\upgrade_ANY_JOBMAXDUR.sql<TMP_DIR>\tdwb\sql/upgrade_ANY_IBROKERJOB04.sql

and change with the right value all the occurrences of thefollowing place holder string:@MDL_USER@

where:v MDL_USER is the database administrator user name, for

example: SYSTEM, that access the Tivoli Workload Schedulerand the Dynamic Workload Broker database. This user mustbe created on Oracle and is not an operating system user.When the administrator installs the product, he must specifythis value in the Oracle administrator user field.

3. Run the SQL filesa. For Tivoli Workload Scheduler, run the following command:

sqlplus -L <TWS_MDL_USER>\<TWS_MDL_PW>@<ORACLE_NET_SERVICE_NAME> @<TMP_DIR>\sql\upgrade_ANY_JOBMAXDUR.sql

b. For Tivoli Dynamic Workload Broker, run the followingcommand:sqlplus -L <TWS_MDL_USER>\<TWS_MDL_PW>@<ORACLE_NET_SERVICE_NAME> @<TMP_DIR>\tdwb\sql\upgrade_ANY_IBROKERJOB04.sql

where:v TWS_MDL_USER is the user you specified in the MDL_USER

field of the property file.v TWS_MDL_PW is the password of the MDL_USER.v ORACLE_NET_SERVICE_NAME is the name used by clients to

identify an Oracle Net server and the specific systemidentifier or database for the Oracle Net connection. A netservice name is mapped to a port number and protocol. Itis also known as connect string, database alias, host string,or service name. At installation time, the administratormust specify this value in the Net service name field.If your Oracle database is installed on the same systemwhere you are installing your master domain manager ora backup master, the net service name is the name ofyour Oracle database..If your Oracle database is installed on the same systemwhere you are installing your dynamic domain manageror a backup dynamic domain manager, the net servicename is the name of your Oracle database.If your Oracle database is not installed on the systemwhere you are installing your master domain manager ora backup master, the net service name is the aliasconfigured for the connection to the remote database.If your Oracle database is not installed on the systemwhere you are installing your dynamic domain manager


or a backup dynamic domain manager, the net servicename is the alias configured for the connection to theremote database.

Performing a safe fix pack installationTivoli Workload Scheduler installs fix packs in safe mode, to ensure integrity of therunning processes.

Before starting the installation, the product performs the following actions:v Checks if there are command lines currently running.v Prevents other jobs from starting by setting the job fence on the workstation to

the go (101) value.v Checks if there are jobs running. If there are, it waits 60 minutes and checks

again. If all the jobs do not complete during this interval, the fix packinstallation does not proceed and an error message is displayed. If you want tochange this value, specify the number of minutes when you run the setup,perform a silent installation, or using twpatch script. This value can be an integeror you can specify the value -1 for the product to wait indefinitely. The defaultis 60. To customize the number of minutes the installer waits for running jobs tocomplete, see:– “Customizing the safe fix pack installation using the wizard” on page 38.– “Customizing the safe fix pack installation using the silent method” on page

38.– “Customizing the safe fix pack installation using twspatch” on page 38.

Note: The safe fix pack installation is available with all the installation methodsexcept using Software Distribution.

v Checks if there are processes running. If there are, it stops them.

If all these checks are passed, Tivoli Workload Scheduler starts the fix packinstallation.

If the fix pack installation completes successfully, after the Batchman processrestarts, the job fence on the workstation is set to its original value because there isa synchronization between the Batchman message queues and Symphony file forthe job fence value. The installation process does not start the Batchman processand to set the original job fence on your workstation, run:conman "start"

If the fix pack installation does not complete successfully, either because the checksare not passed or an error has been reached, the job fence is not set to the originalvalue and you must:v Set the job fence manually to its original value.v Perform the steps to correct the errors and resume the fix pack installation.

To have the Fault Tolerant Agent available again to schedule, you must link againthe host from the Master Domain Manager.

Note: If the fix pack installation is successful and you do not restart the Batchmanprocess, there is no a synchronization between the Batchman messagequeues and the Symphony file for the job fence value, which is set to GO. Ifyou perform an undo fix pack action, without restarting the Batchmanprocess, for the installation process the original job fence value is GO and,


after the undo action, when Batchman restarts the workstation fence iswrongly set to GO and the jobs do not start.

Customizing the safe fix pack installation using the wizardTo modify the number of minutes the installer waits for running jobs to complete,when you run the installation wizard, perform the following steps:

From the installation DVD or from the downloaded images, run one of thefollowing commands:

Windows operating systemFrom the WINDOWS directory, run:SETUP.exe -W checkJobsLoop.wait=value

UNIX and Linux operating systemsFrom the operating_system directory, run:SETUP.bin -W checkJobsLoop.wait=value

Customizing the safe fix pack installation using the silentmethodTo modify the number of minutes the installer waits for running jobs, when yourun a silent fix pack installation method, perform the following steps:1. Copy the response file to a local directory, according to your operating system:

v patchInstall.txt

2. Edit the response file by specifying the parameter: -WcheckJobsLoop.wait=value.

3. Save the file with your changes.4. Enter the following command:

Windows operating systemsSETUP.exe -options local_dir\patchInstall.txt -silent

where patchinstall.txt is the name of the response file to use for fix packinstallation. The SETUP.exe file is located in TWS\operating_system.

UNIX and Linux operating systems./SETUP.bin -options local_dir/patchInstall.txt -silent

where patchInstall.txt is the name of the response file to use for fixpack installation. The SETUP.bin file is located in theTWS/operating_system directory.

Customizing the safe fix pack installation using twspatchTo modify the number of minutes the installer waits for running jobs to complete,when you run the twspatch script, perform the following steps:

From the installation DVD or from the downloaded images, run one of thefollowing commands:

Windows operating systemFrom the WINDOWS directory, run:twspatch.vbs -install -uname TWS_user -wait minutes

UNIX and Linux operating systemsFrom the operating_system directory, run:./twspatch -install -uname TWS_user -wait minutes


Installation actionsWhen you install the fix pack, you can perform one of the following actions:

APPLYUse this action to install the fix pack without making it permanent.“Product actions when applying the fix pack” on page 40 lists the actionsthe product performs when you apply the fix pack.

ROLLBACKUse this action to roll back to the previous level if you did not committedit.

COMMITUse this action to make the fix pack permanent. A rollback operation is nolonger possible.

REPAIRUse this action (only after the Commit action) to restore an existing TivoliWorkload Scheduler instance to the current committed level when aproblem arises with the binary files. It forces an APPLY operation even ifthe current fix pack is already applied. It is used to repair the currentlyinstalled product.

Depending on the fix pack installation state, you can perform the actions shown inthe table below.

Table 5. Fix pack installation state

Initial state Action Final State Final StateGeneralAvailability Pack

- apply ICU ICH

ICU commit IC -

ICU undo - IC

IC repair IC -

where:

ICU Installed undoable

IC Installed and committed

ICH Installed, committed, and hidden

If you have a Tivoli Workload Scheduler fix pack installed in "undoable mode"(ICU state) on your machine and you are applying a more recent Tivoli WorkloadScheduler fix pack on it, all the changes that you made when installing theprevious Tivoli Workload Scheduler fix pack are committed before applying thenewer ones. Therefore, if you undo the fix pack you last installed, you restore theprevious fix pack changes. These changes are permanent.

The fix pack installation is recorded in the TWSRegistry.dat file by adding thefollowing lines:/Tivoli/Workload_Scheduler/tws_user_DN_FixpackName=FP_TWS_$(SWD-OS-NAME)_$(tws_user).8.6.$(patch_id)

where:

$(SWD-OS-NAME)Specifies the operating system where you are installing.


$(tws_user)Specifies the Tivoli Workload Scheduler instance owner.

$(patch_id)Specifies the Tivoli Workload Scheduler fix pack number.

Before repairing a fix pack installation, ensure that:v The processes listed in Table 6 are inactive:

Table 6. Inactive processes

Windows UNIX

netman netman

monman monman

ssmagent ssmagent

writer writer

batchman batchman

batchup batchup

JOBMAN JOBMAN

JOBMON

tokensrv

scribner scribner

agent agent

JobManager JobManager

v The files listed in Table 7 are available under TWS_home/bin and are not corrupt(40042):

Table 7. Files available under TWS_home/bin

Windows UNIX

conman conman

composer (on themaster)

composer (on the master)

setown.cmd libatrc.so

setown.exe libicu*.so

oslayer.dll libHTTP*.soinstmecho

icudt*.dll mecho

HTTPChannel.dll composer

HTTPSSLChannel.dll

HTTPTransport.dll

libatrc.dll

msv*.dll

agent agent

JobManager JobManager

Product actions when applying the fix packThe installer performs the following actions when you APPLY the fix pack:


1. Checks if there are any command lines running for the selected TivoliWorkload Scheduler instance.

2. Retrieves the value of the job fence on the workstation for the selected TivoliWorkload Scheduler instance.

3. Sets the value of the job fence on the workstation to the GO value for theselected Tivoli Workload Scheduler instance.

4. Checks if there are any jobs running for the selected Tivoli WorkloadScheduler instance.

5. Stops the embedded version of WebSphere Application Server.6. Stops the Tivoli Workload Scheduler agent.7. Stops the Tivoli Workload Scheduler instance.8. Checks if there are any processes running for the selected Tivoli Workload

Scheduler instance.9. Backs up the profile for the embedded WebSphere Application Server.

10. Updates the embedded version of IBM WebSphere Application Server UPDIV7.0.0.23.

11. Updates the embedded version of IBM WebSphere Application ServerFP0000023.

12. Updates the embedded version of IBM WebSphere Application ServerIFPM60715.

13. Updates the embedded version of IBM WebSphere Application ServerIFPM71296.

14. Updates the embedded version of IBM WebSphere Application Server SDKFP0000023.

15. Installs the Tivoli Workload Scheduler modeling and planning server, version8.6.

16. Installs with Rollback FP_LWA_<platform>.SPB.17. Installs CIT scanners.18. Installs with Rollback FP_Eclipse_<platform>.SPB.19. Installs with Rollback the IBM Tivoli Workload Scheduler scheduling engine.20. Installs with Rollback IBM Tivoli Workload Scheduler scheduling engine

National Language Support.21. Installs with Rollback FP_TDWB_<platform>.SPB.22. Customizes the SQL scripts used to configure the Tivoli Workload Scheduler

database.23. Customizes the SQL scripts used to configure the Tivoli Workload Scheduler

broker database.24. Configures the Tivoli Workload Scheduler database.25. Configures the Tivoli Workload Scheduler broker database.26. Propagates the security policies of the applications to the JACC provider in

the embedded WebSphere Application Server.27. Starts the embedded WebSphere Application Server.28. Creates uninstaller.29. Configures the Tivoli Workload Scheduler instance.30. Updates the default Tivoli Workload Scheduler Trust Stores.31. Updates the default Trust Store certificates32. Starts the Tivoli Workload Scheduler instance.33. Starts the Tivoli Workload Scheduler agent.


34. Completes and clean the Tivoli Workload Scheduler instance.35. Updates the Tivoli Workload Automation registry.36. Resets the value of the job fence on the workstation to the original value for

the selected Tivoli Workload Scheduler instance.37. Updates the patch.info file.

Product actions when undoing the fix packThe installer performs the following actions when you UNDO the fix pack:1. Checks if there are any command lines running for the selected Tivoli

Workload Scheduler instance.2. Retrieves the value of the job fence on the workstation for the selected Tivoli

Workload Scheduler instance.3. Sets the value of the job fence on the workstation to the GO value for the

selected Tivoli Workload Scheduler instance.4. Checks if there are any jobs running for the selected Tivoli Workload

Scheduler instance.5. Stops the embedded version of WebSphere Application Server.6. Stops the Tivoli Workload Scheduler agent.7. Stops the Tivoli Workload Scheduler instance.8. Checks if there are any jobs running for the selected Tivoli Workload

Scheduler instance.9. Rolls back FP_LWA_<platform>.SPB.

10. Updates the patch.info file.11. Installs CIT scanners.12. Rolls back FP_Eclipse_<platform>.SPB.13. Rolls back the IBM Tivoli Workload Scheduler scheduling engine.14. Updates the patch.info file.15. Rolls back IBM Tivoli Workload Scheduler scheduling engine National

Language Support.16. Rolls back FP_TDWB_<platform>.SPB.17. Restores the profile for the embedded WebSphere Application Server.18. Starts the embedded version of WebSphere Application Server.19. Starts the Tivoli Workload Scheduler instance.20. Starts the Tivoli Workload Scheduler agent.21. Completes and cleans the Tivoli Workload Scheduler instance.22. Updates the Tivoli Workload Automation registry.23. Resets the value of the job fence on the workstation to the original value for

the selected Tivoli Workload Scheduler instance.24. Updates the patch.info file.

Note: The UNDO action restores the old Trust Store certificates, updated duringthe Apply fix pack action.

Before InstallingBefore installing the fix pack using all the methods described in the followingsections, perform the following actions:1. Unlink the host on which you are installing the fix pack from the Tivoli

Workload Scheduler network


2. Shut down Tivoli Workload Scheduler. Run the following commands,depending on your configuration:v If you installed only the Tivoli Workload Scheduler for z/OS Agent or the

Tivoli Workload Scheduler Dynamic agent, run the following command:

On Windows operating systems:ShutdownLwa.cmd

On UNIX and Linux operating systems:ShutDownLwa

v If you have any other configuration, run the following command:

On Windows operating systems:conman "unlink @; noask"conman "stop; wait"conman "stopmon;wait"ShutdownLwa.cmd

On UNIX and Linux operating systems:conman "unlink @; noask"conman "stop; wait"conman "stopmon;wait"conman "shut;wait"ShutDownLwa

If you have jobs scheduled to run on the instance you are upgrading, makesure that they have completed otherwise some processes, such as jobmon orjoblnch, might still be active.

3. Download the ZIP file specific for the operating system.4. Extract the content of the ZIP files into a directory, using one of the unzip tools

available on your system or downloadable from the Internet. The tool you usemust be able to keep the file permissions on the extracted files, for example,infozip. You can find the unzip tool also on the DVD and the eImages of TivoliWorkload Scheduler V8.6 in the directory TWS\<operating_system>\tws_tools,where <operating_system> is the operating system for which you want toinstall the product.

Note: If you want to install the fix pack on IBM i, to untar the eImages, see“Untar the eImages for the Tivoli Workload Scheduler for z/OS Agentand Dynamic Agent on IBM i operating systems.”

5. If you are installing on a UNIX operating system, run the following command:chmod -R 755 <imagesDir>

Untar the eImages for the Tivoli Workload Scheduler for z/OSAgent and Dynamic Agent on IBM i operating systemsTo untar the TWS86_IBM_I.tar fix pack eImage, you can use the PASE shell or theAIXterm.

Using PASE shell:

1. Open the PASE shell.2. Run the command:

"CALL QP2TERM"

3. Locate the folder where you downloaded the file TWS86_IBM_I.tarand run the command:"tar xvf TWS86_IBM_I.tar"

4. Exit from the PASE shell.

Using AIXterm:


1. Start the Xserver on your desktop.2. On the iSeries machine, open a QSH shell and export the display.3. In QSH shell, go to the directory /QopenSys and run the command:

"aixterm -sb"

4. A pop-up window is displayed on your desktop. Using this pop-upwindow, untar the TWS86_IBM_I.tar file.

Installing using the ISMP wizardAfter you have completed the actions described in the section “Before Installing”on page 42, if you want to install the fix pack using the interactive wizard, performthe following steps:1. Unlink the host on which you are installing the fix pack from the Tivoli

Workload Scheduler network2. Shut down Tivoli Workload Scheduler. Run the following commands,

depending on your configuration:v If you installed only the Tivoli Workload Scheduler for z/OS agent, run the

following command:

On Windows operating systems:ShutdownLwa.cmd

On UNIX and Linux operating systems:ShutDownLwa

v If you have any other configuration, run the following command:

On Windows operating systems:conman "unlink @; noask"conman "stop; wait"conman "stopmon;wait"ShutdownLwa.cmd

On UNIX and Linux operating systems:conman "unlink @; noask"conman "stop; wait"conman "stopmon;wait"conman "shut;wait"ShutDownLwa

If you have jobs scheduled to run on the instance you are upgrading, makesure that they have completed otherwise some processes, such as jobmon orjoblnch, might still be active.

3. Download the TAR or ZIP file specific for the operating system and unpack it.To extract the .tar file, ensure that you use the GNU version of the TARcommand. Otherwise, if you unpack the file using a version other than GNU,your fix pack installation fails. If you are installing on a UNIX operatingsystem, run the following command:chmod -R 755 <imagesDir>

4. Depending on the type of operating system, to launch the wizard, run thefollowing command:

On Windows operating systems:SETUP.exe

On UNIX and Linux operating systems:./SETUP.bin

The installation starts.5. Follow the instructions provided on the panel.


6. Click Finish to complete the installation.

Installing using the ISMP silent installationAfter you have completed the actions described in the section “Before Installing”on page 42, if you want to want to install the fix pack in silent mode use silentinstallation. Silent installation requires the customization of a response file. Theresponse file includes all the information required to run the installation withoutuser intervention.

You are provided with the patchInstall.txt sample response file located underthe RESPONSEFILES directory.

Create your response file or customize the response file to include the optionsrequired to complete the installation.

Run the following command from the path were the SETUP file is located to startthe installation in silent mode:v On Windows operating systems:

setup.exe -options response_file -silent

where response_file is the full path name of the response file that you customizedwith your environment settings.

v On UNIX and Linux operating systems:./SETUP.bin -options response_file -silent

where response_file is the full path name of the response file that you customizedwith your environment settings.

Table 8 lists the keywords that you can set in the -WdisplayActions.selectedAction="APPLY" parameter to customize the response filefor your needs:

Table 8. Parameters

KEYWORD SCENARIO

APPLY Install an undoable fix pack

UNDO Roll back to the previous level if you did notcommit it.

COMMIT Make the fix pack permanent. An UNDOoperation is no longer possible.

APPLY_AND_COMMIT Repair an installed and committed fix pack.Note: This action is available only when youinstall a fix pack. It is not available on GeneralAvailability (GA) versions.

Installing using the twspatch scriptYou can use the twspatch script file to install the agents.

To show command usage:

On Windows operating systems:twspatch.vbs -u

On UNIX and Linux operating systems:./twspatch -u


To install a fix pack:

On Windows operating systems:twspatch.vbs -install -uname TWS_user [-inst_dir installation_dir[-recovInstReg {true | false}]] [-wait <minutes>] [-lang <lang_id>]

twspatch.vbs -{undo | commit | remove | repair} -uname TWS_user[-lang <lang_id>]

On UNIX and Linux operating systems:./twspatch -install -uname TWS_user [-inst_dir installation_dir[-recovInstReg {true | false}]] [-wait <minutes>][-lang <lang_id>]

./twspatch -{undo | commit | remove | repair}-uname TWS_user [-lang <lang_id>]

Where:

install Install an undoable fix pack

undo Roll back an undoable image of the fix pack.

commitMake the fix pack permanent. An UNDO operation is nolonger possible.

removeUninstall the Tivoli Workload Scheduler instance.

repair Repair an installed and committed fix pack when aproblem occurs with the binary files. Forces an APPLYoperation even if the current fix pack is already applied. Itis used to repair the currently-installed product.

-uname TWS_userThe name of the user you used to install the TivoliWorkload Scheduler instance.

-inst_dir installation_dir [-recovInstReg true | false ]The name of the directory where you installed TivoliWorkload Scheduler. When installing the fix pack theinst_dir is used:v If the installation process cannot retrieve the product

install location from the registries.v If you need to re-create the Tivoli Workload Scheduler

registries again before the fix pack installation. Set thevalue of the recovInstReg to true if you want to re-createthe registry files while performing a fix pack installationon a fault-tolerant agent. See “Re-creating registry filesusing twspatch” on page 50.

-wait minutesThe number of minutes that the product waits for jobs thatare running to complete before starting the fix packinstallation. If the jobs do not complete during this intervalthe installation process does not proceed and an errormessage is displayed. Valid values are integers or -1 for theproduct to wait indefinitely. The default is 60.

-lang lang_idThe language used for the twspatch messages displayed.The default is the value of the system variable LANG. If


the language catalog for the value you specified is missing,the default C language catalog is used.

twspatch for Windows is a Visual Basic Script (VBS) that you can run inCScript and WScript mode.

After you have completed the actions described in the section “Before Installing”on page 42, perform the following action:v Run twspatch with the options you need for your fix pack installation scenario.

Note: On IBM i operating systems, if you are installing the fix pack on a TivoliWorkload Scheduler for z/OS Agent or a Tivoli Workload SchedulerDynamic Agent, after you have completed the actions described in thesection “Untar the eImages for the Tivoli Workload Scheduler for z/OSAgent and Dynamic Agent on IBM i operating systems” on page 43, run thetwspatch from the QSH shell.

Installing using Software DistributionAfter you have completed the actions described in the section “Before Installing”on page 42, to install the fix pack using Software Distribution, run the followingcommands depending on your configuration:v If you installed only the Tivoli Workload Scheduler for z/OS agent:

wdinstsp -f -uy -D execActionTools=false-D tws_user=<TWS_USER>-D install_dir=<TWS_HOME>-n <INST_PKG_NAME_LWA> <SPB_FILE_NAME_LWA>

v If you installed the Tivoli Workload Scheduler for z/OS agent or the TivoliWorkload Scheduler Dynamic agent and the Java Extension:wdinstsp -f -uy -D execActionTools=false

-D tws_user=<TWS_USER>-D install_dir=<TWS_HOME>-n <INST_PKG_NAME_LWA> <SPB_FILE_NAME_LWA>

followed by this command:wdinstsp -f -uy -D tws_user=<TWS_USER>

-D install_dir=<TWS_HOME>-n <INST_PKG_NAME_JAVA> <SPB_FILE_NAME_JAVA>

v If you installed only the fault-tolerant agent:wdinstsp -f -uy -D execActionTools=false-D tws_user=<TWS_USER>-D install_dir=<TWS_HOME> <CPU_TYPE_DEF>-n <INST_PKG_NAME> <SPB_FILE_NAME>

v If you installed the fault-tolerant agent and the Java Extension:wdinstsp -f -uy -D execActionTools=false

-D tws_user=<TWS_USER>-D install_dir=<TWS_HOME>-n <INST_PKG_NAME_LWA> <SPB_FILE_NAME_LWA>

followed by this command:wdinstsp -f -uy -D execActionTools=false

-D tws_user=<TWS_USER>-D install_dir=<TWS_HOME> <CPU_TYPE_DEF>-n <INST_PKG_NAME> <SPB_FILE_NAME>

and followed by this command:


wdinstsp -f -uy -D tws_user=<TWS_USER>-D install_dir=<TWS_HOME>-n <INST_PKG_NAME_JAVA> <SPB_FILE_NAME_JAVA>

where:

<CPU_TYPE_DEF>-D st_agent=<true or false>-D ft_agent=<true or false>-D master=<true or false>-D bkm_agent=<true or false>

<INST_PKG_NAME>FP_TWS_<INST_INTERP>_<TWS_USER>.8.6.<PATCH_NUMBER>

<INST_PKG_NAME_LWA>FP_LWA_<INST_INTERP>_<TWS_USER>.8.6.<PATCH_NUMBER>

<INST_PKG_NAME_JAVA>FP_Eclipse_<INST_INTERP>_<TWS_USER>.8.6.<PATCH_NUMBER>

<INST_INTERP>AIX | HPIA64 | HPUX | LINUX_I386 | LINUX_S390 |

LINUX_PPC | LINUX_X86_64 | SOLARIS_I386 |SOLARIS | WINDOW_X86_64 | WINDOWS

<PATCH_NUMBER>fixpack level (e.g. 01)

<SPB_FILE_NAME><spb file path>FP_TWS_<INST_INTERP>.SPB

<SPB_FILE_NAME_LWA><spb file path>FP_LWA_<INST_INTERP>.SPB

<SPB_FILE_NAME_JAVA><spb file path>FP_Eclipse_<INST_INTERP>.SPB

Installing using IBM Endpoint ManagerUse the IBM Endpoint Manager Analyses and Fixlets for IBM Tivoli WorkloadScheduler agents patch management to take advantage of:v The IBM Endpoint Manager functions to view and analyze Tivoli Workload

Scheduler information about all the agents installed on IBM Endpoint Managerendpoints.

v The Fixlets to automatically find all the Tivoli Workload Scheduler agents onwhich to install Tivoli Workload Scheduler V8.6 Fix Packs. When the Fixletsbecome relevant, you can choose to schedule or run immediately a TivoliWorkload Scheduler Fix Pack installation.

IBM Endpoint Manager provides unified, real-time visibility and enforcement todeploy and manage patches to all endpoints from a single console.

For more information about applying patches to Tivoli Workload Scheduler usingIBM Endpoint Manager, see the document entitled Tivoli Endpoint Manager Analysesand Fixlets for Tivoli Workload Scheduler Agents patch management available on FixCentral.

Installing the fix pack on fault-tolerant agents when there arecorrupt registry files

If you tried to install the fix pack on a stand-alone, fault-tolerant agent (an agentthat is not shared with other components or does not have the connector feature)


and received an error message that states that an instance of Tivoli WorkloadScheduler cannot be found, this might be caused by a corrupt registry file. It ispossible to install the fix pack on a stand-alone, fault-tolerant agent that hascorrupt registry files without having to re-install the product. Tivoli WorkloadScheduler has a recovery option that you can run to re-create the necessary files.You can also use this option when installing the fix pack on nodes in clusterenvironments, where the node on which you want to perform the fix packinstallation is unavailable or is in an inconsistent state. The recovery optionre-creates the registry files and the Software Distribution information withouthaving to reinstall the product.

You can run the recovery option when using any of the following fix packinstallation methods:v “Installing using the ISMP wizard” on page 44v “Installing using the ISMP silent installation” on page 45v “Installing using the twspatch script” on page 45

Re-creating the registry files using the installation wizardIf you want to re-create the registry files while performing a fix pack installationon a fault-tolerant agent using the installation wizard, perform the following steps:1. From the installation DVD or from the downloaded images, run one of the

following commands:

Windows operating systems

v TWS\operating_system\SETUP.exe -WdisplaylActions.installationDirH=TWA_home -WrecovInstReg.run=true

v TWS\SETUP.cmd -W displaylActions.installationDir=TWA_home -WrecovInstReg.run=true

where operating_system is the operating system where you want toinstall the fix pack and TWA_home is the directory where TivoliWorkload Scheduler is installed.

UNIX and Linux operating systems

v TWS/operating_system/SETUP.bin -WdisplaylActions.installationDir=TWA_home -WrecovInstReg.run=true

v TWS/SETUP.sh -W displaylActions.installationDir=TWA_home -WrecovInstReg.run=true

where operating_system is the operating system where you want toinstall the fix pack and TWA_home is the directory where TivoliWorkload Scheduler is installed.

Re-creating registry files using silent fix pack installationTo re-create the registry files while performing a fix pack installation on afault-tolerant agent using the silent fix pack installation method, perform thefollowing steps:1. Copy the response file to a local directory, according to your operating system:

v patchInstall.txt

2. Edit the response file by specifying the parameter: -W recovInstReg.run=true

3. Save the file with your changes.4. Enter the following command:


Windows operating systemsSETUP.exe -options local_dir\patchInstall.txt -silent

where patchinstall.txt is the name of the response file to use for fix packinstallation. The SETUP.exe file is located in TWS\operating_system.

UNIX and Linux operating systems./SETUP.bin -options local_dir/patchInstall.txt -silent

where patchInstall.txt is the name of the response file to use for fixpack installation. The SETUP.bin file is located in TWS/operating_system.

5. Review the installation messages in the summary.log file to check that fix packinstallation was successful.

Re-creating registry files using twspatchTo re-create the registry files while performing a fix pack installation on afault-tolerant agent using the twspatch script, perform the following steps:

On Windows operating systems

1. Log in as administrator on the workstation where you want to upgradethe product.

2. From the TWS/operating_system directory of the installation DVD orfrom the downloaded images, run one of the following commands,where operating_system is the operating system where you want toinstall the fix pack, run twspatch using the synopsis described below.

On UNIX and Linux

1. From the TWS/operating_system directory of the installation DVD orfrom the downloaded images, where operating_system is the operatingsystem where you want to install Tivoli Workload Scheduler fix pack,run the twspatch script using the synopsis described below.

Synopsis:

On Windows operating systems:

Show command usage and versiontwspatch.vbs -u | -v

Install fix packtwspatch.vbs -install -uname user_name

[-domain user_domain][-inst_dir install_dir [-recovInstReg true]]

Exampletwspatch.vbs -install -uname twsuser -password qaz12qaz-inst_dir "C:\Program Files\IBM\TWA" -recovInstReg true

On UNIX and Linux

Show command usage and version./twspatch -u | -v

Install fix pack./twspatch -install -uname user_name[-inst_dir install_dir [-recovInstReg true]]

Example./twspatch -install -uname twsuser -inst_dir /opt/IBM/TWA-recovInstReg true


For information about the twspatch parameters, see “Installing using the twspatchscript” on page 45.

Configuring properties for the dynamic workload brokercommand line

This step is required only if you run the dynamic workload broker command line on aWindows system.

The version of the CLIConfig.properties file installed with version 8.5.1 onWindows workstations omits the following keywords:tdwb_usertdwb_pwd

These keywords are required to run commands on the dynamic workload brokercommand line (not if you use the Tivoli Dynamic Workload Console).

This fix pack installs an additional, non-running, instance of CLIConfig.propertieswith the correct keywords in:TWA_home\TDWB\config\config

Copy the tdwb_user and tdwb_pwd keywords from the CLIConfig.propertieslocated in TWA_home\TDWB\config\config into the CLIConfig.properties located inTWA_home\TDWB\config, which is the running instance.

Rolling back the fix pack installationYou can roll back the installation only if you installed it in undoable mode.

To roll back the installation using ISMP, perform the following steps:1. Launch the installation setup for your operating system.2. Select the instance that you want to remove.3. Select the UNDO option.4. Click Finish.

To roll back the installation using the twspatch command from the TWS_homedirectory, use the undo option.

For more information about the rolling back action, see also “Installation notes” onpage 27.

Uninstalling the entire Tivoli Workload Scheduler instanceIf you installed using the twspatch command, to uninstall the entire TivoliWorkload Scheduler instance, use the twspatch remove command from theTWS_home directory.

If you installed using ISMP, to uninstall, see Planning and Installation.

Installation log filesThe following installation log files give you details about the status of the fix packinstallation for the Master domain manager, backup Master domain manager, theagents, and the connector:v Trace file for ISMP installer


On Windows operating systems:%TEMP%\TWA\tws86fixpack\twsismp.log

On UNIX and Linux operating systems:$TMPDIR/TWA/tws86fixpack/twsismp.log

v Log file for ISMP installer

On Windows operating systems:%TEMP%\TWA\tws86fixpack\twsstatus.log

%TEMP%\TWA\tws86fixpack\summary.log

On UNIX and Linux operating systems:$TMPDIR/TWA/tws86fixpack/twsstatus.log

$TMPDIR/TWA/tws86fixpack/summary.log

v Log file for Tivoli Workload Scheduler twspatch installer.

On Windows operating systems:%TEMP%\TWA\tws86fixpack\twspatch_<INST_INTERP>_<TWSuser>^8.6.0.n.log

On UNIX and Linux operating systems:$TMPDIR/TWA/tws86fixpack/twspatch_<INST_INTERP>_<TWSuser>^8.6.0.n.log

where n is the fix pack number. For this fix pack the number is 2.v Log file for Configuration Manager installation.

On Windows operating systems:%TEMP%\FP_TWS_<INST_INTERP>_<TWSuser>^8.6.0.n.log

On UNIX and Linux operating systems:$TMPDIR/FP_TWS_<INST_INTERP>_<TWSuser>^8.6.0.n.log

where n is the fix pack number. For this fix pack the number is 2.

For information about INST_INTERP, see “Installing using Software Distribution” onpage 47.

If you do not set the variable $TMPDIR on the UNIX system then the default /tmp isassumed.

Documentation updatesThese are the fixes for the documentation APARs and internal defects that aremade available in the refreshed product documentation.

They are organized by fix pack number and manual.

Documentation updates for Tivoli Workload Scheduler FixPack 3 for version 8.6.0

This section contains new information and documentation corrections contained inthis fix pack. It is organized by manual:

Tivoli Workload Scheduler Version 8.6.0 Messages and Codes (revised December2012), SC23-9114-05

90903 In chapter "Tivoli Workload Scheduler messages", at the end ofsection "AWSBHV - Stageman messages", add the following newmessage:


AWSBHV083E An internal error has occurred. Stageman hasencountered an error while reading a record from the Symnewfiles. The Production Plan has not been extended correctly.

Explanation:

The most likely cause is that the number of the record it is tryingto read exceeds the maximum value allowed or exceeds the actualnumber of records in the Symnew file. Other possible causes are:v The fstat() or lseek() system calls failed.v The read() system call failed due to a physical I/O error or to a

bad Symnew file descriptor.v The read operation was interrupted by a signal.

System action:

Stageman stops.

Operator response:

This is an internal error. The Symnew file might be corrupt. See thechapter 'Symphony file corruption' in the Troubleshooting Guide.

Tivoli Workload Scheduler Version 8.6.0 Integrating with Other Products,SC23-8904-05

91143 In Chapter "Integrating with Tivoli System Automation forMultiplatforms", make the following changes:v In section "Tivoli System Automation for Multiplatforms

overview", change the following paragraph:The integration with Tivoli System Automation forMultiplatforms requires Tivoli Workload Scheduler V8.6 Fix Pack2 or later and Tivoli System Automation for MultiplatformsV3.2.2 Fix Pack 3 or later. The integration also requires that theTivoli Workload Scheduler instance user is the same on all TivoliWorkload Scheduler instances.to:The integration with Tivoli System Automation forMultiplatforms requires Tivoli Workload Scheduler V8.6 Fix Pack3 or later and Tivoli System Automation for MultiplatformsV3.2.2 Fix Pack 7 or later. The integration also requires that theTivoli Workload Scheduler instance user is the same on all TivoliWorkload Scheduler instances.

v In section "Configuring a master domain manager and backupmaster domain managers cluster", change the following bullet:Tivoli System Automation for Multiplatforms V3.2.2 Fix Pack 3or later is installed on the dynamic domain manager and backupdynamic domain manager instances.to:Tivoli System Automation for Multiplatforms V3.2.2 Fix Pack 7or later is installed on the dynamic domain manager and backupdynamic domain manager instances.Change the following bullet:The Tivoli System Automation for Multiplatforms peer domainTWS is online.to:


The Tivoli System Automation for Multiplatforms peer domainTWS is online and the quorum type of the peer domain is set toQuorumLess.Delete the following bullet:All Tivoli Workload Scheduler components are stopped on themaster domain manager and backup master domain managerinstances.Change the following item:9. As user root, run TWAHome/TWS/TSAMP/createResources.sh onthe following workstations, in the following order:to:9. As user root, run TWAHome/TWS/TSAMP/createResources.sh onany of the following workstations:

v In section "Configuring a dynamic domain manager and backupdynamic domain managers cluster", change the following bullet:Tivoli System Automation for Multiplatforms V3.2.2 Fix Pack 3or later is installed on the dynamic domain manager and backupdynamic domain manager instances.to:Tivoli System Automation for Multiplatforms V3.2.2 Fix Pack 7or later is installed on the dynamic domain manager and backupdynamic domain manager instances.Change the following bullet:The Tivoli System Automation for Multiplatforms peer domainTWS is online.to:The Tivoli System Automation for Multiplatforms peer domainTWS is online and the quorum type of the peer domain is set toQuorumLess.Delete the following bullet:All Tivoli Workload Scheduler components are stopped on themaster domain manager and backup master domain managerinstances.Change the following item:4. As user root, run TWAHome/TWS/TSAMP/createResources.sh onthe following workstations, in the following order:to:4. As user root, run TWAHome/TWS/TSAMP/createResources.sh onany of the following workstations:

Tivoli Workload Scheduler Version 8.6.0 User's Guide, SC32-1274-13

58896 In Chapter "Getting reports and statistics", section "Commanddescription, at the end of rep1 - rep4b command description, atthe end of the Examples section, change from:Elapsed(secs)

to:Elapsed(mins)

90939 In Chapter "Managing objects in the plan - conman", section


"Conman commands", in the description of startbrokerappcommand, do the following changes:v In the "Syntax" section, use this new syntax:

startbrokerapp [domain!]workstation[;wait]v At the bottom of the "Arguments" section, add the following:

wait Specifies to not accept another command until thedynamic workload broker has stopped.

91533 In Chapter "Using utility commands in the dynamic environment",section "resource", in the description of option -query, at the end ofthe list "Retrieves the following additional properties if you addthe -v option", add the following items:v Network interfacesv File systems

91292 In Chapter "Defining objects in the database", section "Definingscheduling objects", subsection "Job definition", make the followingchanges:v In table Required and optional attributes for the definition

of a file transfer job, add the following row after the row forattribute localCodepage:

Table 9. Required and optional attributes for the definition of a file transfer job

enableMultibyteDataEncoding Specifies whether the file transfer requires amultibyte code page data translation.

If you set this option to true, the file transfer ismade after a data connection encoding usingmultibyte code page data translation. The FTPjob executor plug-in sends to the remote FTPserver running on the z/OS system thefollowing FTP commands:

encoding=mbcsRequired for multibyte dataconversion and data type set to ASCII.

mbdataconn(remoteCodepage,localCodepage)Specifies the code pages used on theremote and local workstations.

If you set this option to false, the file transferis made without using multibyte code pagedata translation.The default value is false.

v At the end of the description for RC=-1, add the following:AWKFTE032E

Explanation: The file has not been transferred. Internal protocolerror is: <protocol_error>.System action: Operation not performed.Operator response: Check the internal protocol error for details.

IV45708In Chapter "Managing the production cycle", section "Creating andextending the production plan", subsection "Authorization", in thelist of users delete the last bullet:


v Any Tivoli Workload Scheduler user authorized in the securityfile on the master domain manager as follows:file name=prodsked,Symphony access=build

Tivoli Workload Scheduler Version 8.6.0 Troubleshooting Guide, SC32-1275-13

89180 In Chapter "Troubleshooting dynamic workload scheduling", aftersection "Remote command job fails", add the following section:

On Windows operating systems interactive jobs are not visibleon dynamic agents

On Windows operating systems you are running aninteractive job on a dynamic agent, but no user interface isdisplayed.

Cause and solution:

Ensure that the Interactive Services Detection service isrunning on the dynamic agent, and run the interactive jobagain.

IV34539In Chapter "Troubleshooting dynamic workload scheduling", insection "Troubleshooting common problems", add the followingsubsection:

On HP Itanium operating systems the concurrent submissions ofmany dynamic agent jobs can result in bad performance

On HP Itanium operating systems, if you run a highnumber of dynamic agent jobs scheduled in parallel, theymight fail or cause very bad performance.

Cause and solution:

The agent on HP Itanium operating systems runs incompatibility mode using the ARIES virtual machine,which has some limitations in the number of threads thatcan be created. To solve this limitation, you must modifythe default values used by the virtual machine for theJobManager program. In the same directory where theJobManager program is located, create a file named.ariesrc, edit this file, and add the following line:<JobManagerPath> -aries_ssz <ariesvalue> -heap_ssz <heapvalue>

where

<JobManagerPath>is the absolute path where the JobManager programis located.

<ariesvalue>is the size in kilobytes of the memory stack areafor ARIES native threads that are created toemulate the application's threads.

<heapvalue>is the size in kilobytes of the ARIES heap used forARIES calls to the malloc() function and to allocatespace for ARIES thread creation.

For example, you can write:


/var/tws/twzxq58/TWS/bin/JobManager -aries_ssz 128 -heap_ssz 90000

Ask your system administrator for the values to use, butyou might need to make several attempts to tune yoursystem before finding the values that best suit your needs.After you create and save this file, you must stop and startthe agent.


The manuals were updated with all the features introduced with Fix Pack 2 in theinformation center:



The manuals were updated with all the features introduced with Fix Pack 1 in theinformation center:


The following APARs were fixed:v IV16524: DOCC UPDATE IS REQUIRED THAT "ACTIVEAUTHMECHANISM"

SHOULD BE "LTPA" INSTEAD OF "SWAM".v IV16952: TDWC INSTALL USER REQUIREMENTS DOCUMENTATION

CONSIDERING TWAPAM.







Contacting IBM Software Support

Before contacting IBM Software Support with a problem, refer to the IBM SoftwareSupport site by accessing the following Web address:

http://www.ibm.com/software/support

To access Tivoli support, click the Tivoli support link at the bottom right of thepage.

If you want to contact IBM Software Support, see the IBM Software SupportHandbook at the following Web site:

http://techsupport.services.ibm.com/guides/handbook.html

The guide provides information about how to contact IBM Software Support,depending on the severity of your problem, and the following information:v Registration and eligibility.v Telephone numbers, depending on the country in which you are located.v Information you must have before contacting IBM Software Support.


http://www.ibm.com/software/support

http://techsupport.services.ibm.com/guides/handbook.html


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 document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, 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 beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct 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 itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, 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 document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurement may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

If you are viewing this information in softcopy form, the photographs and colorillustrations might not display.

TrademarksIBM, the IBM logo, and ibm.com® are trademarks or registered trademarks ofInternational Business Machines Corporation in the United States, other countries,or both. If these and other IBM trademarked terms are marked on their firstoccurrence in this information with a trademark symbol (® or ™), these symbolsindicate U.S. registered or common law trademarks owned by IBM at the time thisinformation was published. Such trademarks may also be registered or commonlaw trademarks in other countries. A current list of IBM trademarks is available onthe Web at “http://www.ibm.com/legal/copytrade.shtml." Copyright andtrademark information” at www.ibm.com/legal/copytrade.shtml.


Adobe, the Adobe logo, PostScript and the Postscript logo are either registeredtrademarks or trademarks of Adobe Systems Incorporated in the United States,and/or other countries.

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc., inthe United States, other countries, or both and is used under license therefrom.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks orregistered trademarks of Intel Corporation or its subsidiaries in the United Statesand other countries.

IT Infrastructure Library is a registered trademark of the Central Computer andTelecommunications Agency which is now part of the Office of GovernmentCommerce.

ITIL is a registered trademark, and a registered community trademark of the Officeof Government Commerce, and is registered in the U.S. Patent and TrademarkOffice.

Java and all Java-based trademarks and logos are trademarks orregistered trademarks of Oracle and/or its affiliates.

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo aretrademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.

Notices 63


��

Product Number: 5698-WSH

Printed in USA