The following new product features, enhancements, and changes are introduced with this fix pack:

Updated version of DB2 support

Fix Pack 4 has been tested using DB2 11.1.

Updated OpenSSL libraries IBM Workload Automation has been updated with OpenSSL

OpenSSL 1.0.2t 10 September 2019 (1.0.2.20).

Updated version of GSKIT

Fix Pack 4 has been updated with GSKIT version 8.0.55.6.

IBM SDK for Java

Fix Pack 4 has been updated with Java version 7.0.10.55.

Resolved Common Vulnerabilities and Exposures (CVE)

The following CVEs have been resolved with this Fix Pack.

• CVE-2016-0705
• CVE-2016-0799
• CVE-2016-2108
• CVE-2016-2842
• CVE-2016-3732
• CVE-2016-3735
• CVE-2016-8616
• CVE-2016-8621
• CVE-2016-8624
• CVE-2017-7525
• CVE-2018-12539
• CVE-2018-1517
• CVE-2018-1656
• CVE-2018-2783
• CVE-2018-2973
• CVE-2019-4031
• CVE-2019-4608

The following new product features, enhancements, and changes are introduced with this fix pack:

MSSQL database support extended on Linux AMD64

Microsoft SQL Server Enterprise Edition database is now supported on Linux AMD64.

166128: Fix for “Agent upgrade with minimal scheduling disruption” for dynamic Java™ job plug-ins

With this fix pack, a fix has been delivered so that V9.3 FP3 dynamic agents can be upgraded to the V9.4 level or later, even when the dynamic agents are running Java job plug-ins.

Higher level of control over the What-if Analysis Gantt view

Administrator's have more control over the What-If Analysis view through the introduction of a new optman global option. By setting the optman enWhatIf | wi global option to no, administrators can centrally disable the What-If Analysis feature, which is enabled by default in your environment to simulate and evaluate the impact of changes on the current plan. You have to run "JnextPlan" to make the change effective.

For information about the interaction of the enWhatIf | wi global option with the enWorkloadServiceAssurance | wa global option, which enables or disables privileged processing of mission-critical jobs and their predecessors, see Documentation updates for IBM Workload Automation Fix Pack 3 for version 9.3.0.

Load balancer support for Informatica PowerCenter plug-in

In the properties file for Informatica PowerCenter plug-in (PowerCenterJobExecutor.properties ) you can specify the parameters to customize the plug-in when the Informatica Web Services Hub is behind a load balancer. For details about the parameters that you can specify, see Documentation updates for IBM Workload Automation Fix Pack 3 for version 9.3.0.

Support for the following product releases

• WebSphere® Application Server, version 8.5.5, fix pack 11
• Jazz™ SM, version 1.1.3, cp 2
• Installation Manager, version 1.1.8.6

New optional keywords for defining the secure connection protocol type and the related cipher on fault-tolerant agents

Add the keywords to the localopts file to explicitly define the secure connection protocol and the ciphers to be used with that specific protocol.

OpenSSL libraries updated

To address OpenSSL vulnerabilities, the OpenSSL libraries used by IBM Workload Automation have been updated from version 1.0.2g to 1.0.2j.

Added support for Windows Server 2016

Fault-tolerant agent and Dynamic Agent are now supported

Added support for CentOS Linux release 7.1, 7.2, and 7.3

Fault-tolerant agent and Dynamic Agent are now supported

Added support for Oracle Linux 7.2

Fault-tolerant agent and Dynamic Agent are now supported

The following new product features, enhancements, and changes are introduced with this fix pack:

Defining and managing IBM Workload Scheduler security with role-based security model

You can define and update your security file according to the role-based security model, by using the Manage Workload Security interface from the Dynamic Workload Console or the composer command-line program.

With the role-based security model you can update your security file with the security objects that you define in the master domain manager database, in a quick and easy way. You can define your security objects by using the Manage Workload Security interface from the Dynamic Workload Console or the composer command-line program. Enable the role-based security model by setting the optman enRoleBasedSecurityFileCreation global option to yes.

According to the role-based security model, the security objects that you can define are:

Security roles

Each role represents a certain level of authorization and includes the set of actions that users or groups can do.

Security domains

Each domain represents the set of scheduling objects that users or groups can manage.

Access control lists

Each access control list is defined assigning roles to users or groups, on a certain security domain.

When the security file is updated on the master domain manager, the security settings on the master domain manager are automatically synchronized with the backup master domain manager.

For more information see the online product documentation available in Getting started with Security.

Hybrid Workload Automation

Pick a mixture of Workload Automation on Cloud and on Premises and reduce IT costs with hybrid scheduling management. Hybrid Workload Automation allows you to use a common User Interface to manage both on Premises and on Cloud engines.

You can monitor and execute actions in plan on the following objects: job, critical job, workstation, resource, prompt, job stream, file, and domain. The same efficient workload managed in the on premises environment can be scheduled to run in the on cloud environment.

You can transfer your workload from your on premises environment to your Workload Automation on Cloud through a simple import procedure. The workload is instantly reproduced and it is ready to be employed on your agents. Handling your workload in the on Cloud environment is a more cost effective way to utilize resources in the cloud only when you need them without relying on an on premises infrastructure. Workload Automation on Cloud reduces IT infrastructure costs, and it is a solution for utilizing resources only when you have a business need to run your workload.

For more information about Hybrid Workload Automation see Hybrid scheduling environment in the online product documentation in IBM Knowledge Center.

New method for updating DB2 and Oracle database schema

When creating, upgrading, or updating the master domain manager and its backup, or the dynamic domain manager and its backup, the database schema must also be created, upgraded, or updated.

If you typically update your database tables manually before updating the IBM Workload Scheduler components in your environment, then you can use this new method which includes a script that quickly generates the required SQL statements in an SQL file and optionally applies them directly to the database in a single step.

The advantages of this new update method are:

• A single script that dynamically generates the SQL statements and applies them directly to the database. Optionally, you can configure the script to generate only and then apply them at a later time but before installing the product component.
• The script can be run and rerun as many times as needed without any cleanup required between runs. For example, if for some reason a database object is corrupt, you can rerun the script to regenerate the SQL file and apply it.
• For DB2 databases, this method eliminates the requirement of installing a DB2 client to update a database located on a remote DB2 server. The script works using the JDBC drivers and connecting directly to the database server minimizing the overhead in installing and maintaining a database client.
  Important: If you already use a DB2 client and want to take advantage of this new method and eliminate it, ensure that you do not change the location of your JDBC driver. If you change the location, then remember to change it also in the WebSphere Application Server. If instead your WebSphere Application Server does not point to the JDBC driver, then you can proceed to uninstall your DB2 client.
• Use this method as a stand-alone tool to check the consistency of the database schema. The database administrator can verify if the database schema has changed and repair any inconsistencies.

Installing, updating, or upgrading the product components using either the Installation Manager wizard or the silent installation methods automatically upgrades the database tables using this same method.

For more information about this method of upgrading the database schema, see Updating or upgrading the database schema for DB2 or Oracle.

Reply to a message for an IBM i job from Dynamic Workload Console

When an IBM i job is in SUSP (suspended) status, waiting for a reply to a message, you can reply to the message directly from the Monitor Workload of the Dynamic Workload Console. For more information see Scheduling jobs on IBM i in the online product documentation available in IBM Knowledge Center.

Automatic reply to waiting messages for an IBM i job

You can define standard rules to automate the reply to waiting messages for an IBM i job. When defining an IBM i job, by using the Dynamic Workload Console or the composer command line, you can specify the list of messages for which you want to set up an automated reply. In the output job log you can see the messages queued by IBM i system and the replies sent automatically by the job. For more information see IBM i jobs in the online product documentation available in IBM Knowledge Center.

Running a script when a job completes

In many scenarios, when a job completes, you might want to run one or more actions, by using the information related to the job completion. For this purpose, you can write a script file and store it in a directory of the agent file system. The script is run every time that a job completes, either successfully or unsuccessfully. The script runs with the same credentials as the agent user that is running the job. For more information see Running a script when a job completes in the online product documentation available in IBM Knowledge Center.

Checking prerequisites before running a silent installation

The silent installation method is an unattended installation that does not require user intervention, however, to ensure that the installation is not halted because of missing or insufficient system requirements, you can now run a script that checks for product system requirements before initiating the installation. The prerequisite check script is available for master domain manager and Dynamic Workload Console installations and checks requirements such as:

• Supported operating system.
• Sufficient RAM.
• Sufficient swap file space.
• Disk space for the creation of the installation and temporary directories passed in input to the script.

See Disk space requirements for details about the product system requirements. For more information about the procedure for running the prerequisite check see Installing the fix pack using IBM Installation Manager silent installation.

IBM Workload Scheduler Plug-in for Apache Oozie

With the new IBM Workload Scheduler plug-in for Apache Oozie, you can schedule, monitor, and control Oozie workflows and Hadoop jobs such as Hive, MapReduce, Pig, and Sqoop. As Hadoop adoption continues to expand, Hadoop jobs are growing in volume and complexity. To optimize their execution, different Hadoop jobs can be organized into a single logical unit of work, called a workflow. Apache Oozie is a powerful tool that creates and manages complex workflows of Hadoop jobs. However, it is fundamental to integrate Oozie workflows with the rest of the business process flow. With the new plug-in for Oozie, workflows and Hadoop jobs can be managed the same way as any other IBM Workload Scheduler job, extending the central management of the company workload to the Hadoop environment. For more information see Apache Oozie jobs in the online product documentation available in IBM Knowledge Center. In addition, see a practical example of the plug-in demonstrated in a business scenario and short and informative video: IBM Workload Scheduler Plug-in for Apache Oozie.

Support for TLS 1.2 protocol

To comply with the US government SP 800-131 security standard, you can configure the WebSphere Application Server to support the Transport Layer Security (TLS) 1.2. Previously this type of configuration caused communication errors between the command line and the agents. With this fix pack, IBM Workload Scheduler now supports this type of configuration.

OpenSSL libraries updated

To address OpenSSL vulnerabilities, the OpenSSL libraries used by IBM Workload Scheduler have been updated from version 1.0.2d to 1.0.2g.

New keyword added to local options file to address running commands in file dependencies as root

With Fix Pack 2, a new keyword named, jm file no root, has been introduced to allow or prevent jobman from executing commands in file dependencies as root user. The default setting is to prevent jobman from executing commands specified by jm file no root =no in the localopts file. For more information see Localopts details.

New behavior for the tws_env.sh file

This fix pack installs a new version of the file tws_env.sh in the directory <TWA_HOME>/TWS, where <TWA_HOME> is the IBM Workload Scheduler installation directory. Before installing the fix pack, ensure you have created a backup file if you have modified the original version. After installing the fix pack, merge the content of the new version with the content of the original version to carry your customized content into the new version (157029).

Extended operating system support

With this fix pack, the following operating systems are supported:

• IBM AIX®V7.2: master domain manager and agents
• Microsoft Windows 10: dynamic agent
• Linux Ubuntu V14.2: dynamic agent
• SUSE Linux Enterprise Server V12: master domain manager and agents

For the most updated information about supported operating systems, generate a dynamic report from the Software Product Compatibility Reports web site containing the list of supported operating systems.

Conditional dependencies (RFE 103337)

With IBM Workload Scheduler you can define jobs to run when and as often as necessary. Sometimes some jobs might have to wait for other jobs to finish successfully before they start. Add even more flexibility to your job flows by choosing which job to run depending on the result of the job status or output of a previous job. Whenever you have conditions that specify whether or not a segment of your job flow should run, then that is a conditional dependency. When specifying dependencies, you can define job flows with alternative branches based on conditions, specifically to achieve the same results as using IF/THEN/ELSE statements. You can use return codes, job status, output variables, and job log content as conditional logic elements to determine the start of a successor job. In addition to providing flexibility to your job flows, the Graphical View provides a graphical representation of the relationships between the jobs and job streams, including the dependencies and conditions. This at-a-glance view of your job flow is easy to read and you can also edit your job flow from this view. For more information, see Applying conditional branching logic.

New job plug-ins

IBM Workload Scheduler Plug-in for Liberty

With the new IBM Workload Scheduler plug-in for JSR 352 Java Batch (plug-in for Liberty), you can schedule, run, and monitor your Java Batch applications and integrate them into more complex, composite batch workflows. For more information, see Schedule, execute, and monitor your Java Batch applications with IBM Workload Automation.

IBM Workload Scheduler Plug-in for MQTT

IBM Workload Scheduler integrates with MQTT to provide centralized management of your "Internet of Things" devices. MQTT is a publish and subscribe, simple, and lightweight messaging protocol. For more information, see Monitor and control your "Internet of Things" devices.

WebSphere Application Server tools enhancements (RFE 33301)

Credentials required to submit WebSphere Application Server tools (wastools) scripts supplied with the product are now optional when you submit the scripts to run. WebSphere Application Server administration scripts, such as starting and stopping the WebSphere Application Server, supplied with IBM Workload Scheduler retrieve the credentials stored in the soap.client.props file located in the properties directory of the WebSphere Application Server profile to avoid the necessity of supplying a user name and clear text password in the command line.

In addition to added security protection, the enhancement eliminates the maintenance costs associated with frequent password changes. The user ID and password are now optional and the credentials are retrieved from the soap.client.props file. However, unlike the master domain manager installation where the soap.client.props file is automatically customized with these credentials, the Dynamic Workload Console requires you to manually customize the soap.client.props file with the credentials to be able to use this enhancement. For more information, see Application server - starting and stopping.

Scheduling the centralized agent update

You can schedule the centralized update of multiple agent instances by creating a centralized agent update job, either by using the Dynamic Workload Console or the composer command line. When a job runs, it forwards to the master domain manager the Update agent request for all the fault-tolerant agent or dynamic agent instances that you selected, and then completes. For more information, see Scheduling the centralized agent update.

IBM i enhancements

Checking IBM i jobs that are waiting for a message reply

You can now use the Dynamic Workload Console and conman showjobs command line to check if an IBM i job is waiting for a reply to a message. An IBM i job that is waiting for a message reply is in the SUSP (suspended) status. This status indicates that the job is running while waiting for input. When the input is received, the job status changes to EXEC (executing).

Viewing the message for which an IBM i job is waiting for a reply

You can also view the message for which the IBM i job is waiting for a reply. The message text and the reply are written into the corresponding IBM Workload Scheduler job log, so that the IBM Workload Scheduler operator knows the exact message the IBM i job is waiting for.

Specifying the name of the queue where IBM i jobs are monitored

You can specify the name of the queue where the monitoring agent component runs by using the customizable property MonitorQueueName in the native job launcher section of the JobManager.ini file. If you do not specify this property, the default queue (QBATCH) is used.

For more information, see Scheduling jobs on IBM i systems.

IBM Workload Scheduler integration with IBM Tivoli® Monitoring: situation refactoring and new view associations

With this fix pack, two scripts are provided, ITMCreateSituations and ITMSetSeverity, that create the default situations for monitoring IBM Workload Scheduler processes and that associate these default situations to a respective severity and not automatically to a critical severity as with past releases. The default situations can be associated to a physical or logical view of your choice on the Tivoli Enterprise Portal. For more information, see How to create IBM Workload Scheduler default situations.

For more information about new features introduced with this fix pack, see IBM Workload Scheduler version 9.3 Fix Pack 1 enhancements.

Helpful videos demonstrating new features for IBM Workload Scheduler is available on Workload Automation channel.

This section lists APARs and internal defects solved by Fix Pack 4.

List of APARs fixed:

IJ00166:	DWC VIEWS AFFECTED BY LARGE FILE DEPENDENCIES
IJ00392:	FILECHECK DEPENDENCY (OPENS) ON FILE ON DYNAMIC AGENT REMAINS IN "ASKED" EVEN IF THE FILE IS PRESENT
IJ00599:	MIRRORING: THE NUMBER OF ROWS IN PLN.PFDP TABLE COULD INCREASE INDEFINITELY
IJ00716:	MULTILE VULNERABILITIES FOUND IN OPENSSL
IJ00910:	MIRRORING: IF A SUB_QUEUE BECAME FULL A DEADLOCK COULD OCCURR
IJ00914:	CENTRALIZED AGENT UPDATE NOT ALWAYS WORKING IN TWS 9.3 FP3
IJ00950:	IF A TRIAL PLAN EXTENSION IS LONGER THAN 3 MINS IT CAN BE EXECUTED TWICE
IJ01061:	IMPLEMENT THE LOGIC OF APAR IV88912 IN JOBMANRC FILE
IJ01506:	JOBS ON POOL WORKSTATIONS ARE STUCK ON WAIT STATE
IJ01507:	MIRRORING CACHE CLEANUP CANNOT BE CUSTOMIZED
IJ01535:	TWS ZCENTRIC AGENT STOP WORKING AFTER Z/OS SERVER IPL/REBOOT/NETWORK DISCONNECT
IJ01950:	JOBMANAGER_MESSAGE.LOG JOBMANAGER_TRACE.LOG MISSING ON WINDOWS ZCENTRIC AGENT
IJ02038:	BACKWARD COMPATIBILITY FOR FILETRANSFERS JOBS: JOBS DEFINED IN 9.X MASTERS ARE NOT RUNNING ON 8.6 AGENTS, RETURNING AWKSUL020E
IJ02098	FILE CREATE MONITOR EVENT RULE FAIL ON WINDOWS DA WHEN FILE PATHIS TOO LONG
IJ02415:	OPENS ON DYNAMIC AGENTS AND POOLS WITH DYNAMICAGENTSSTAYS IN ASKED STATE WHEN BATCHMAN IS NOT ABLE TO COMMUNICATEWITH BROKER
IJ02494:	JOB EVENT CODES 123-127 NEED TO BE ADDED TO THE DOCUMENTATION
IJ02596:	INCREASE ROBUSTNESS OF TSAMP MONITORCOMMAND
IJ02685:	APACHE COMMONS FILEUPLOAD VULNERABILITY
IJ02712:	TWS ELEVATED PRIVILEGES (SETGID AND SETUID PROGRAMS) LIBRARIES HAVE INSECURE LOCATIONS IN RPATH (.)
IJ03167:	ERRONEOUS WARNING MESSAGE AWSBHX032W THE STARTED DATE OF THE FOLLOWING JOB IS NULL
IJ03587:	NM IPVALIDATE=FULL : NETMAN LOCALOPTS PARAMETER BREAKS THE DYNAMIC BROKER LOCALHOST 127.0.0.1 LINK : AWSEDW053E AWSEDW090E
IJ03892:	JS EVERY ONOVERLAP DONOTSTART NOT CANCELLING TO CATCH UP JS'SLOGGED
IJ04102:	DWC DISPLAYS NEGATIVE PROMPT NUMBERS
IJ04677:	DATE IN HEADER/FOOTER ARE ENCODED IN EUC, ALTHOUGH LANG IS UTF-8 ON SOLARIS 10.
IJ05354:	DATASTAGE PLUG-IN DISTIBUTED WITH FP3 IS CORRUPTED
IJ05392:	JOBLOG TO BE CREATED WITH 600 LEVEL PERMISSION
IJ05421:	ITM AGENT HAS DOCKQDS FILE THAT HAS JOB NUMBER AS 7 CHARACTERS INSTEAD OF 8 CHARACTERS
IJ06473:	UPDATE GSKIT VERSION 8.0.55.6
IJ06494:	RUNCYCLE GROUP WITHIN A JOBSTREAM IS NOT PICKING UP THE DEFAULT CALENDAR
IJ06643:	CVE-2017-7525 FOUND ON TWS 9.3 FP3
IJ06799:	IF CONTEXTROOT KEY IS NOT PRESENT IN THE COMMON.PROPERTIES FILE, MESSAGE SHOWING WHERE THE REPORT IS GENERATED IS MISSING A SLASH
IJ07067:	JOBS WITHOUT AT TIME START AN HOUR EARLY ON DST CHANGE WHEN ENPREVENTSTART=YES
IJ07377:	ZCENTRIC AGENTS DO NOT RECONNECT AFTER SYSTEM REBOOT
IJ07385:	MULTIPLE VULNERABILITIES FOUND IN OPENSSL
IJ07745:	DYNAMIC AGENT JAVAEXT POTENTIALLY AFFECTED BY CVE-2018-2783
IJ08161:	IMPROVE THE JOBMANAGER.INI.BAK FILE CREATION MECHANISM
IJ08474:	EVENT RULE THAT LOOKS FOR FILE IN AN UNC PATH WAS NOT SEEN
IJ08496:	ONOVERLAP DONOTART DOES NOT WORK CORRECTLY IF THE SCHEDULE IS DEFINED FOR A CPU THAT IS NO A MANAGER.
IJ09715:	SEGMENTATION FAULT(COREDUMP) WHEN EXECUTING CONMAN -GUI 'SETSYM 10&SJ @#@;LOGON' 1>SJ_LOGON.TXT 2>&1
IJ10469:	INSTALL OF FIXPACK 9.3 FP03 FAILS AT DYNAMIC AGENT UPDATE
IJ10729:	TWS IS POTENTIALLY AFFECTED BY CVE-2018-1656, CVE-2018-12539, CVE-2018-1517, CVE-2018-2973
IJ11203:	SUBMIT A REMOTE COMMAND JOB CONTAINING THE £ CHAR E.G. ECHO £HOSTNAMEWITH RXA STAYS IN EXEC (HANG) FOR EVER
IJ11281:	(MASTERAGENTS#)RESTART_STARTCOND JOB FAILS WITH AWSBHT001E AND AWKTSA050E JCL ERROR.
IJ11466:	DEADLOCK ISSUES IN RUNNING APIS
IJ11908:	TWS DEPENDENCIES REMOVED WHEN UPGRADING RUNCYCLE IN A JOBSTYREAM BEFORE THE FINAL RUN TIME
IJ12048:	HIGH LOAD OF DATASTAGE JOBS (2100+) CAUSES MEMORY LEAK AND JOB FAILURES
IJ14140:	SSL CONNECTION ENABLED BETWEEN DM AND FTAS. IF CONNECTION ISSUE OCCUR THE DM MAILMAN PROCESS DOESN'T MANAGE TIMEOUT ERROR
IJ14147:	AFTER UPGRADING DA'S TO 9.4.0.3 THAT SUPPORT OUR OLFM AGENTS THE OPERATING UNIT IS NO LONGER GETTING POPULATED IN OLFM
IJ14630:	EVENT RULES OCCASSIONALLY SUBMIT THE WRONG JOB STREAM
IJ14905:	WAS SERVER GOES DOWN UNEXPECTEDLY
IJ15085:	CVE-2019-4031 IBM WORKLOAD SCHEDULER TASKLAUNCHER CONTAINS A VULNERABILTY
IJ15789:	RUNNING CURL THROWS THE FOLLOWING ERROR: $ CURL GOOGLE.COM CURL:(2) FAILED INITIALIZATION
IJ16123:	CORRECTION FOR APAR IV98210 CAUSES SIGNIFICANT PLAN MIRRORING DELAYS WHEN A SPIKE OF MIRRORING GENERATED EVENTS OCCUR
IJ17325:	PLAYMAN CHECKSYNC CAN FAIL IF OPENS DEPENDENCIES IN THE DATABASE FROM PREVIOUS DAYS ARE INCORRECT
IJ17527:	EVENT RULE REPORTS ERROR AWSJCS011E JAVA.LANG.NULLPOINTEREXCEPTION
IJ18837:	SALESFORCE JOB SUCCEEDS ON SF SIDE, BUT SHOWS ABEND ON TWS SIDE
IJ20119:	WLB JOBS RUNNING TWICE IN MS-PROD
IJ20834:	A PROBLEM IN THE SUBMISSION OF JOBSTREAM FROM EVENT RULE.
IJ21249:	MDM 9.3 DOES NOT HANDLE CORRECTLY THE RETURN CODE FROM JOBS SUBMITTED BY D-DRIVEN ZOS AGENT 9.4
IJ21346:	MIRRORING IMPROVEMENT FOR FILE DEPENDENCIES MANAGEMENT AFTER THE RESYNC OPERATION
IJ21348:	MIRRORING IMPROVEMENT ON CANCEL OPERATION MANAGEMENT
IJ21519:	TABLES IN PLN SCHEMA CARRYING OVER TOO MANY ROWS
IJ22504:	MIRRORING - CANCEL JOB WITH RESOURCE DEPENDENCY GENERATES TOO MANY EVENTS IN SOME SPECIFIC CASES
IV81197:	JOBMANAGER SUDDENLY TERMINATES WITH CORE
IV82812:	TWS PLUG-INS DO NOT PERFORM A QUIT ACTION FOR FTP JOBS RUN THROUGH TWS UPON LOGOUT OR DISCONNECT OF THE SESSION.
IV83728:	JOBLOG ARCHIVED ZIP FILE IS READBLE ONLY FOR TWS USER
IV90274:	JOBSTREAMS WITH AT + DAYS AND VALIDFROM NOT IN PLAN
IV92358:	UPDATE CURL COMPONENT FOR CVE-2016-8616 CVE-2016-8624 AND CVE-2016-8621
IV92453:	HISTORY OF DIRECT QUERY ON MONITOR WORKLOAD IS WRONG
IV95075:	DOCUMENT INCORRECTLY STATES THE USE OF WILDCARD FOR WORKSTATION IN CONMAN DDS
IV98210:	DEADLOCKS WITH CANCEL JS
IV98265:	MONMAN MEMORY LEAK WHEN STARTS R3EVMAN.EXE
IV98395:	JOBMANAGER OCCATIONALLY FAILS TO START WHEN EXECUTORSMINTHREADS IN JOBMANAGER.INI IS HIGH (MORE THAN 600)
IV98476:	EVENTS LOST ON A DISTRIBUTED TWS ZCENTRIC WORKSTATION
IV98638:	PLAN MIRRORING STALLS FOLLOWING A SWITCHMGR FOR A SUB-DOMAIN MANAGER
IV98646:	IWS 9.3-FP03 IMPLEMENTED A CHANGE IN DEFAULT BEHAVIOR OF THE
IV99033:	CVE-2016-0705 CVE-2016-2108 CVE-2016-0799 CVE-2016-2842 ARE PRESENT ON< TWSHOME>/EDWA/SSM AND <TWSHOME>/TWS/SSM
IV99439:	INCORRECT DATE INTO ACTUAL START ON LISTING JOBS ON ZOSENGINES

List of defects fixed:

WA-68813:	MIRRORING LOCKEXCEPTION MUST BE A PLANRECOVERABLEEXCEPTION
WA-73363:	INCORRECT SQL STATEMENTS FOR LICENSING ON TWS 9.3
WA-81570:	UPDATE OPENSSL VERSION
WA-81585:	UPDATE JRE - 7.0.10.55
WA-81587:	UPDATE TIMEZONE TABLE
WA-81590:	UPDATE GSKIT 8.0.55.6
WA-83415:	NO JOBLOG AVAILABLE ON DA
WA-84407:	EVENT RULE DOES NOT WORK
WA-84814:	WHITESOURCE VULNERABILITY ON HANDLEBARS-2.0.0.MIN.JS
WA-85103:	IWS JOB FAILS IF THE SALESFORCE JOB IS IN HOLDING
WA-85322:	CROSS SITE SCRIPTING AT IBM TIVOLI v9.3.0.3 AT ENGINE PARAMETER

This section lists APARs and internal defects solved by Fix Pack 3.

List of APARs fixed:

IV51793	WHEN UPGRADING BROKER FROM 8.5.1 TO 8.6 UNIQUE AGENT ID CHANGES
IV55930	TWSCHECKINSTANCE*.CMD CANNOT BE USED IN NESTED SCRIPTS TO CHECK IF JOBS ARE RUNNING.
IV60757	AFTER SWITCHING MANAGER CANNOT BROWSE JOBLOGS FOR ALL DYNAMIC
IV62103	CPU LIMIT "SYS" DOES NOT WORK AS DOCUMENTED FOR X-AGENTS
IV69128	THE NET SERVICE NAME MAX LENGTH IN CONFIGURING DB DURING INSTALLATION CANNOT BE GREATED THAN NINE.
IV69518	AFTER JNEXTPLAN XA IS UNLINKED BY TDWC ONLY DISPLAY PROBLEM
IV73429	DEADLOCK ON THREADS ON JOBMANAGER CAUSING AGENTS HUNGING
IV74715	The validation of dynamic pool definition create or update the database.
IV76015	JOB STREAM CONTAINING A PARTICULAR OPENS DEPENDENCY ENCOUNTERS
IV76919	ADD TIMEOUT TO ITA AGENT CONNECTIONS
IV76934	AFTER SUCCESSFULLY RUNNING Z/CENTRIC AGENT JOB CREATED SYSOUT CONTAINS SYSOUT FOR MUTIPLE JOBS
IV78030	When DST starts, if SOD falls on the hour missing, plan is extended for 24 hours instead than for 23.
IV78321	UPDATE ZONE INFO ACCORDING TO LATEST CHANGES FOR 2015
IV79081	COMPOSER VALIDATE ERRONEOUSLY GIVING WARNINGS
IV79937	ORACLE DEADLOCK PERFORMING RESOURCE SCAN
IV79949	CAN NOT RETRIEVE /ETC/GROUP IF GROUP CONTAINS A LOT OF MEMBERS
IV80090	BATCHUP DOESD NOT START AT CONMAN START IF COMPUTERNAME IN UPPERCASE AND HOSTNAME IN LOWER CASE
IV80208	AWKIPC005E FAILED TO RUN WORKFLOW ERROR ENCOUNTERED WHEN ATTEMPTING TO RUN INFORMATICA JOBS
IV80942	9.3 DOCUMENTATION NEEDS TO SHOW 8.5.1 RESPONSE FILE AVAILABLE ONLY WITH 9.3 FP01
IV81025	NEED TO DOCUMENT ABOUT A BEHAVIOR OF BROKER COMPONENTS WHEN ENSWFAULTTOL=YES.
IV81521	ERROR IMPORTING INTO TWS 9.1 VIA WAPPMAN DEFINITIONS.XML
IV81576	NETMAN FOR A 8.6 WINDOWS AGENT NEVER RELEASES MEMORY AFTERRUNNING CONMAN SJ;STDLIST ON IT
IV81774	ADHOC JOBS ARE ALLOWED TO BE SUBMITTED INTO THE USERJOBS JOBSTREAM ALTHOUGH NO FURTHER ...
IV82159	DYNAMIC AGENT PSAGENT JOBS STILL RUNNING ON PS SHOW ABEND IN TWS
IV82641	OPENSSL RELEASED FIXES FOR SECURITY VULNERABILITIES
IV82747	JOBMANGERGW DOES NOT START UP BECAUSE JOBMANAGERGW.INI IS EMPTY.
IV82925	JOB ASSIGNED INCORRECT SECONDARY GROUP(S) WHEN RUNNING DYNAMIC /ZCENTRIC JOBS AS A USER OTHER THAN THE
IV83084	ASSIGNMENT OF A NULL VALUE TO A NOT NULL COLUMN DURING UPDATESTATS
IV83151	DWC FIX PACK README MISSING DETAIL ON HOW TO INSTALL PREREQUISITES
IV83441	PROBLEM WITH TCL USED IN RMSTDLIST.CMD.
IV83554	TWS 9.3 FP1 INSTALLATION IS CAUSING AWSJPU004E ERRORS LOGGED NTO SYSTEMOUT.LOG. ANY IMPACT ON PRODUCT
IV83557	MOVEHISTORYDATA DOES NOT RUN M(MAUALLY NEITHER AUTOMATICALLY)
IV83728	Joblog archived zip file is readable only for tws user
IV83754	THE TWS MONMAN PROCESS IS EXPERIENCING A RANDOM FAILURE DURING THE SWITCH OF THE STDLIST AT FINAL
IV83761	TWS LIBJOBMANAGERCORENEEDS TO HAVE 555 AS PERMISSION
IV83962	DISPLAY ALERTS UNTIL A JOB COMPLETE
IV84208	RANDOMLY ON Z-CENTRIC WE GET FOLLOWING MESSAGE: "NO JOBS STARTED UNDER THE SUBMITTED USER COMMAND
IV84256	CONMAN SJ WHEN RUN AGAINST JS CONTAINING JOBS DEFINED ON
IV84268	UPDATESTATS POOR PERFORMANCE WITH 9.3/9.3FP1
IV84530	TWSENGINEMODEL WILL NOT START IF TWSCONFIG.PROPERTIES CONTAINS ASPACE AFTER RDBMSNAME ...
IV84674	AWSBHT019E SHOULD BE A WARNING MESSAGE NOT AN ERROR MESSAGE
IV84891	MOVEHISTORYDATA.SH ENHANCEMENT ON ORACLE: DELETE ROWS IN SET
IV84905	NUMBER OF "PREDECESSOR JOBS AND JOB STREAMS" AND "SUCCESSORS" IS DIFFERENT IN DWC
IV84911	REP11 SHOW INCORRECT SCHEDULE ON END OF MONTH
IV85018	TWS 9.3 MESSAGES GUIDE DOCUMENT EEWO1028I AND EEW01029I
IV85275	SAP JOBS FOR DYNAMIC AGENT REMAINS IN READY STATE CONSUME CPU LIMIT.
IV85492	UNABLE TO SAVE RCG WHEN USING 2 RUNCYCLES IN SAME SUBSET WITH LOGICAL AND
IV85587	FTP-JOBS ARE RETURNING AWKFTE043E ERROR EVEN IF THE FILE IS SUCCESSFULLY TRANSFERRED.
IV85666	JOBMANAGER CORE AFTER TWS 9.3 FP2 FOR JOB THAT CONTAINS PASSWD L ONGER THEN 31 CHARACTERS INTO JSDL
IV85751	jobstatuschanged event rules with tbsmeventforwarder action gives a string index out of range
IV85789	DWC QUERIES/GETS THAT ARE LOCKING ROWS
IV85855	BATCHMAN IS FAILING WITH ERROR: AWSBCU011E RECORD FROM /OPT/WFA/TWS/TWS/SYMPHONY RECORD 32768 (RM)
IV86067	WINDOWS AGENT FAILS TO UPGRADE FROM 8.5.1 FP003 TO 9.2 FP2
IV86073	Not possible to retrieve joblog of jobs run by qsecofr
IV86277	IWS 9.3 AND PEOPLETOOLS 8.53 CONNECTION ISSUE.
IV86478	IGNORE THE ALIAS FLAG IF AN ALIAS IS NOT PROVIDED BY THE UI/SBS
IV86692	UPDATESTATS JOB ABENDS ON IWS MDM 9.3 FP0001 WITH EXIT STATUS:8 AWSJCS011E JAVA.LANG.NULLPOINTEREXCEPTION
IV87038	TWS 9.2 JVM CRASH AND JAVA CORE IS GENERATED
IV87386	SCHEDULE RECALL FORMATTING IN EVENT.LOG FILE (EVENT ID 203) FOR 9.2.0
IV87526	CAN NOT VIEW ANY ARGUMENTS FOR DYNAMIC JOBS BY DWC
IV87532	DEADLOCK USING FILE DEPENDENDENCIES + MIRRORING.
IV87558	TWS 9.3 FP1 AND FP2 UPDATESTATS TAKE A LOT OF TIME TO BE COMPLETED AND INCREASE EVERY DAY
IV87671	MISSING PARAMETERS IN TWAINSTANCE#.TWA.PROPERTIES UPGRADE FAILS
IV87679	GENERIC ACTION PLUG-IN SCRIPT EXECUTECMD.SH ON AIX HAS ROOT ENV
IV87846	WRONG TRANSLATION IN FRENCH ON EVENT DEFINTION OF JOB STATUS TDWC 9.3 FP2
IV88310	TABLESPACE TWS_PLAN KEEP INCREASES
IV88884	TASK STRING THAT IS LONGER THAN 256 CHARCATERS.
IV88912	Dynamic jobs fails with 126 on AIX
IV88971	INSTALL OF DYNAMIC AGENT ON WINDOWS TESTS VALUE FOR TWS_THISCPU
IV89007	EWAS CRASHED DUE TO A SEGMENTATION ERROR
IV89009	SYNCHRONIZATION BETWEEN DEPENDENCIES AND JOB/JOBSTREAM
IV89073	EVERY JOBSTREAM AT IS AFFECTED BY SOD TIME
IV89137	UPGRADE TO TWS 9.X AGENT FAILURE IF TWS 8.X IS INSTALLED WITH SPB PROCEDURE AS "FTA CLASSIC" ONLY
IV89332	TEST CONNECTION FAILURE UPGRADING TO 9.3 FIX PACK 2 FOR ORACLE DATABASE
IV89492	UPDATESTATS GIVES WARNING AWSJPL804W
IV89536	WAS 8.5.5.8 AND DB2 10.5 FP07 ARE REQUIRED TO USE ON AIX 7.2.
IV89577	TWS MASTER/DOMAIN MANAGER 9.3 FP1 OR GREATER CAN CAUSE FTA UNLINK
IV89649	WEBSPHERE RECYCLES AFTER A NORMAL RESTART IN WORKLOAD SCHEDULER
IV89805	SWITCHPLAN PERFORMANCE FIXES
IV89809	OPENING JOBSTREAMS IN DWC YIELD CONVERTEREXCEPTION ERROR
IV89920	AFTER APPLYING 9.3.0 FIXPACK 02 AN AWSJCS011E ERROR IS ENCOUNTERED WHEN ATTEMPTING TO RENAME A JOB
IV89934	COMPOSER RECEIVES BAD FILE DESCRIPTOR" AND "PERMISSION DENIED"
IV89967	WHEN USING A TIME STAMP VARIABLE IN THE MAIL SENDER PLUGIN
IV89990	PLANMAN CONFIRM HANGS
IV90180	PROBLEM WITH RUNCYCLE GROUPS
IV90317	A PREVIOUS JOBSTREAM WAS SUBMITTED AGAIN.
IV90559	Incorrect job order in a job stream after job rename
IV90602	JOB SUBMITTED INTO CARRYFORWARD SCHEDULE NOT SHOWING CORRECT status
IV90614	DYNAMIC AGENT HAS PROBLEMS TO MANAGE OPEN DEPENDENCY EXECUTING EXETRNAL PROGRAMS
IV90830	USERPROFILE IS NOT LOADED FOR XAGENT RUNNING ON WINDOWS.
IV90870	ESTIMATED DURATION WRONG
IV90945	APPS IS NOT WORKING WITH PEOPLESOFT VERSIONS BEFORE 8.5
IV90991	AWSITA245E "CURL ERROR 35" ON DEPLOY EDWA RULES ON DA AND WITH ENEVENTPROCESSORHTTPSPROTOCOL / EH = NO (HTTPS DISABLED)
IV91052	MULTIPLE VULNERABILITIES IN OPENSSL
IV91072	CONMAN SBD TO WINDOWS FTA TRUNCATES THE CONMAND LINE WITH TWSRCMAP
IV91175	INSTALLING AGENT PRE-REQ SCANNER FAILS IF THE <TWAHOME> DIRECTORY PATH CONTAINS A . CHARACTER
IV91210	Incorrect job stream status after jobs completion
IV91219	MB EVENTS SENT BY 9.3FP1 CAUSES RANDOM UNLINK OF PRE-9.3FP1 FTA
IV91269	CORRUPT JMJOBTABLEDIR CAN CAUSE JOBMANAGER TO CORE
IV91351	RERUN JOB RETURNS AWSJDB101E OBJECT NOT FOUND ERROR ON TDWC.
IV91691	SAP PI JOB STATUS FOR CHECK CHANNEL STATUS (CHANNELSTATE) IS NOT WORKING CORRECTLY
IV92161	stageman crashes if enCarryForward = NO
IV92306	MIRRORBOX.MSG SIZE INCREASE IF MANY FILE DEPENDENCIES ARE DEFINED IN THE WORKLOAD
IV92352	AFTER SWITCH MASTER SOME DYNAMIC JOBS REMAIN IN EXEC STATUS ON COMPOSER
IV92358	UPDATE CURL COMPONENT FOR CVE-2016-8616 CVE-2016-8624 AND CVE-2016-8621
IV92374	JOB STREAMS STAY IN READY IN NOP SCENARIO
IV92378	AFTER PLANMAN RESYNC XA ON MDM ARE SEEN UNLINKED
IV92415	PENDING CANCELLATION FLAG INCORRECTLY DISPLAYED FROM DWC
IV92455	BROKER AGENTS WILL NOT LINK TO BACKUP DOMAIN MANAGER
IV93048	stageman can cause CondDep JS to be put at pri=0
IV93052	Unable to view joblog from DWC/conman when job defined on XA hosted by DWB using jsdl and with resources
IV93078	A composer hanging could negatively affect the WAS startup (EDWA)
IV93337	POOR PERFORMANCE OF PLANDELETE ON ORACLE
IV93482	AWSJDB810E ERROR ENCOUNTERED WHILE RUNNING SWITCHPLAN ON MDM
IV93505	LFTA NOT LINKED IF CENTRALIZED SECURITY IS ENABLED
IV93578	ITA NOT UPDATED TO 64-BIT IF UPGRADE FROM TWS 8.6 FP4 TO 9.2+
IV93828	FILE DESCRIPTORS NOT BEING CLOSED ON OLD LOG FILES WHEN LOG SWITCH OCCURS
IV93890	MAILSENDERPLUGIN - SMTP Helo command rejected: need fully-qualified hostname
IV93899	ONOVERLAP DONOTSTART STREAM STAYS ON HOLD WHEN STREAM JOBS ARE MIXED IN LINUX AND WINDOWS.
IV95138	Dynamic Agent - OPENS and PIPE not work
IV95276	Add tls11 and tls12 in localopts for fta
IV95368	DA/POOL jobs erroneously in ABEND close to MAKEPLAN/SWITCHPLAN
IV95378	MODIFY TWS WINDOWS SERVICE
IV96098	Mirroring "Bu" events can lock table PLN.PWKS when mirroring cache is empty
IV97080	PLAN INCORRECTLY EXTENDED BY 36 HOURS AFTER APPLYING FP03

List of defects fixed:

Defect number	ABSTRACT
161584	Wrong statement to generate the SLMTag file
164876	Java null pointer exception when change name of job defined into a job stream
166128	Java job does not start after stop/start agent while a previous java job is running
166131	JobManager behaves incorrectly after stop/start agent (Linux)
166176	Unexpected job abend termination after agent reconnect
166181	Missing JobManager process restart on AIX platform after reconnect of a java job
166189	Wrong behavior of JobManager process on HP
166344	Hang during Jnextplan / ResetPlan
166783	Rest API: Java null pointer exception creating a trial plan
166786	ElapseTime not correct in the plan for DistributedShadowJob
166787	Agent Upgrade: failure during the Workload Scheduler registry validation
167123	Incorrect job stream status after jobs completion
167182	Informatica job types do not work with load balancer
167185	Datastage plug-in memory usage consumption
167251	REST API: Missing ConnDuplicationException trying to modify a job stream with valid from using an existing key
167284	No message for ConnValidationException creating an event rule
167317	Mirroring LockException must be a PlanRecoverableException
167344	EventRule not saved. ConnmodelEjbLocalImpl could not be found
167446	Missing auditing on file for conman commands related to conditional dependencies
167484	What-If: Make the Critical Path building synchronous with itself
167485	What-If: Add a limited cache for archived Critical network
167486	What-If: Allow WSA also on backup master
167447	REST API: NullPointerException instead of ConnValidationException using job.setJobDefinitionKey(null)
167448	REST API: ConnException instead of ConnIntegrityException for DOMAIN error test cases
167524	jobstore.sh AWKCLI034E Unable to read the default configuration file
167782	Informatica job types do not require to load logs into job log
167944	MSSQL Support on Linux 9.3 FP3
167957	MSSQL: exportserverdata.bat does not work
167958	Modify installation (twsinst) to allow installation of FTA and DA with an hostname starting with a number
168231	Dynamic agents request and download in loop EDWA configuration from Broker
169443	Missing INW dependency shown after job stream submission having a join conditions
169445	Mirroring: java.lang.Integer incompatible with java.lang.Long using ddj every by conman
169446	Missing job stream dependency revalidation after job rerun
169447	Incorrect isPendingCancellation() value after cancel of a job stream
169448	Incorrect job stream dependencies status inside a join condition with mirroring enabled
169490	OPENSSL IV91052
169506	Wrong fix pack versioning
169512	spaceUsed.exe crash during installation of fp3 on master
169518	Composer warning at start time for cclog issue
169558	Increase WebSphere Application Server heap size for MDM and Dynamic Workload Console
169560	Agent Installation: failure during check of OS prerequisites. (Ubuntu)
170164	MDM on Windows platform does not work in SSL mode
170321	Mismatch between the number of To Run Jobs from mirroring and symphony after a submission of a job with recovery job and recovery rerun
170322	Mirroring: InternalDependencyInPlanDifferences status wrong after EVERY job suppressed in HOLD status
170323	Incorrect dependency status submitting a job having repeat every clause
170324	Batchman goes down after conman rerun from action
170595	Batchman update failure
170783	Joblog does not work AWSBIN080E An internal error occurred processing scribner packets
170813	Installation failure on CIT : Not able to stop CIT
170854	Composer warning messages running it at same time from 2 different shell
171193	JobInPlanFilters.RERUN does not work
171293	Output errors when multiple Composer commands are invoked at the same time
171442	RERUN FLEX: What-if Analysis and listsucc do not work after JnextPlan -for 0000
172398	Forward compatibility: Error message during REST connection DWC 93FP3 to Engine 94FP1
172635	Misleading successful message when DWC installation fails
173038	Mirroring: Different Critical Start value
173149	planman resync erroneously resolves condDeps
173516	Improve the Dependency Status - "Join Satisfied" help
173548	Mirroring: Duplicate File dependencies
173673	Exception needs to be handled when submitting a job stream with a particular open dependency
173859	Add EMF initialization to the DWB Startup starter
173892	Master Domain Manager with an hostname starting with a number does't work
174435	Unable to release or delete FileDep through DWC
174438	Job stream is put in Waiting with no Dependencies even if Resources are greater than available
174456	Mirroring: wrong isUntilUsed and getStatus for js after JnextPlan
174462	RERUN FLEX: unexpected job shown in rerunsucc preview having a repeat every clause
174465	Incorrect job stream status displayed by mirroring after a cancel pending of a job in EXEC
174468	Incorrect dependency status after adddep on a job in exec
174608	Change the mirroring cache size default to 20k
174770	stdlist quickly grows when collector is invoked multiple times
175040	Dynamic Workload Console version is different from FP installed
175288	What-if error 500 on DWC 93FP3 + JazzSM 1.1.3.0 + Cumulative patch1
175345	Mirroring: Incorrect Predecessor Dependency status with rerun
176039	Incorrect behavior for new join dependencies evaluation
176340	Incorrect job and job stream statuses for a job with confirmed clause
176343	High Number of File Dependencies scenario Quality Plan Goal A1 not matched after having applied the hotfix provided by L3 - performance issue with a mirroring query
176369	Incorrect job status after rerun
176666	Update SAMP policies
176920	Incorrect number of running jobs after job rerun
176939	Wrong user.dwbPort default value in backup MDM response file.
176979	Installation fails during update
177337	Incorrect isEvery field after rerun of a job
177352	MIRRORING REPEATEVERY: Wrong abend prompt key after manual rerun and repeatevery
177353	COMPOSER REST - Unexpected output trying to delete a job stream referenced by a WAT
177378	PERF: composer add action get a core dump due to out of memory
177499	Backward compatibility DWC941 Engine 93FP3: Error message adding object using REST connection
178044	TWS upgrade scripts do not remove the old libz libraries
178063	SwaggerUI does not work

This section lists APARs and internal defects solved by Fix Pack 2.

List of APARs fixed:

• IV63324: Conman security enhancement.
• IV69005: PACKAGEDEPLOY.SH ENDS WITH ERROR ABOUT BAD PARAMETERS IF "COMPANY NAME" FIELD CONTAINS BLANK.
• IV70849: batchman and jobman fail on all Windows fault-tolerant agents if adddep with at= .
• IV73696: TWS FAULT-TOLERANT AGENT 9.2 INSTALLED ON 2012R2 SERVER FAILING ON INSTALL TO D: DRIVE.
• IV74504: APAR AFTER SETTING FENCE TO SYS, THEN RUNNING A PLANMAN RESYNC, CAUSES TWS TO ERROR.
• IV76571: ERROR: 'UNRECOGNIZED COMMAND LINE ARGUMENT "-NOROOT"' WITH LINUX 9.3 DYNAMIC WORKLOAD CONSOLE INSTALL USING SETUPDWC.SH -NOROOT.
• IV77219: PROMPTSTATUSCHANGED EVENT LOST IF THE PROMPT HAS DOUBLE QUOTES.
• IV77843: DATABASE MIRRORING - JOBSTREAMS/JOBS NOT REPLICATED.
• IV78333: dataextract on a XA workstation defined on a $MASTER does not work.
• IV78611: PROBLEMS WHEN USING RUNCYCLE GROUPS AND FREEDAYS CALENDAR.
• IV78964: Standard Agent reports multiple error messages - AWSBDW014E Jobman found a mailbox record in the Courier.msg file in an unrecognizable format, and was unable to process it.
• IV79427: SIGNIFICANT DELAY WORKING WITH COMPOSER DEFINITIONS FOR POOL WORKSTATIONS.
• IV79699: DYNAMIC AGENT JOB HAS UNEXPECTED VALUE FOR TIVOLI_JOB_DATE.
• IV79707: Failure in migrating/fix pack installing on Oracle partitioned database.
• IV79890: REPORT8 RUN BY CREATEPOSTREPORTS FAILS WITH A SEGMENTATION FAULT.
• IV79935: TWS is resolving only 10 open dependency per second, while in TWS 8.5.1 hundreds were resolved. This causes a strong delay in job submissions.
• IV79937: ORACLE DEADLOCK PERFORMING RESOURCE SCAN.
• IV80134: PATCH.INFO FILE IS NOT CREATED/UPDATED WHEN APPLYING IWS 9.3.0.
• IV80208: AWKIPC005E FAILED TO RUN WORKFLOW ERROR ENCOUNTERED WHEN ATTEMPTING TO RUN INFORMATICA JOBS.
• IV80796: untiljs flag is wrongly set after sbs from master domain manager 8.5.1.
• IV81244 :"REPLY YES TO XXXXX" (XXXXX=PROMPT) ACTION DOES NOT WORK AFTER APPLYING FIX PACK. TWS IS INCORRECTLY MANAGING PROMPT RELATED EVENTS.
• IV81322: remote cli not compatible with old master.
• IV81480: The TWS upgrade process should not overwrite the jobmanrc file (150769).
• IV81525: AWSJPL720E ERROR FROM UPDATESTATS/LOGMAN WHEN USING MSSQL DATABASE.
• IV81746: SINFONIA.XXXX FILLS THE MDM FILESYSTEM CAUSING TWS WAS ISSUES.
• IV81748: MAKEPLAN SLOW: OPTIMIZE THE JOB OUTPUT CONDITIONS LOADING.
• IV81748: MAKEPLAN SLOW: REMOVE THE DUPLICATE JDP LOAD DURING THE JSI LOAD.
• IV81749: WRONG INDEX IPJOR_02 COULD SLOW DOWN PLANMAN RESYNC/CHECKSYN IF SEVERAL EVERY/RERUN JOB ARE USED.
• IV81765: DB CONNECTION IS GETTING LOST DURING MIRRORING, IF IT IS NOT CLEANED UP AND IT CAN BE REUSED, THIS CAN CAUSE EVENTS TO BE LOST.
• IV81843: UNABLE TO USE SPECIAL CHARACTERS IN ZOS SHADOW JOB NAMES.
• IV82544: RESYNC SLOW: REMOVE USELESS SELECT CURRENT_TIMESTAMP.
• IV82796: COMPOSER UPDATES CAUSING DATABASE DEADLOCK.

List of defects fixed:

• 131874: Incorrect job properties for a Sterling job.
• 133107: Dynamic agents request and download in loop EDWA configuration from Broker.
• 133419: Error message for wdlssp installing or restoring an agent for Linux if /lib/ld-linux.so.2 is missing
• 133442: Wrong process name value submitting a Sterling job.
• 133709: Missing maxdur values shown from conman commands with high value of percentage.
• 133713: Old product name is present installing MDM with launchpad.
• 147887: Failure when upgrading and updating Tivoli Workload Scheduler version 9.1 to version 9.x on an Oracle partitioned DB.
• 151386: Manual database creation: Dynamic domain manager create when executed by DBA prompts for password (DB2).
• 151390: PLANMAN RESYNC: In some cases, after a failure, database connections are not properly cleaned up.
• 153889: maxArchivedPlan in TdwcGlobalSettings.
• 154063: APAR Regression: Failure when upgrading and updating Tivoli Workload Scheduler version 9.1 to version 9.x on an Oracle partitioned DB.

This section lists APARs and internal defects solved by Fix Pack 1. For additional information about documentation APARs and internal defects, see Documentation updates for IBM Workload Automation Fix Pack 1 for version 9.3.0.

List of APARs fixed:

• IV77863: TWS WEBSPHERE CRASHED DUE TO A NATIVE MEMORY CORRUPTION WHILE ACCESSING A .MSG FILE.
• IV77609: Agent process crashes after port scan on AIX and Solaris.
• IV77219 : PROMPTSTATUSCHANGED EVENT LOST IF THE PROMPT HAS DOUBLE QUOTES .
• IV77093: WHEN LOGMAN IS RUN AGAINST A LIVE SYMPHONY FILE STATISTICS ARE NOT RECORDED FOR JOBS WHICH COMPLETE WHILE LOGMAN IS RUNNING.
• IV76762: Broker server does not link.
• IV76744: Add an index for DWB.JOB_BROKER_JOBS.
• IV76743: BRANCH JOB ERRORS.
• IV76687: Increase the robustness of batchman to manage corrupted dependencies.
• IV75946: TCLSH84.EXE CALLED FROM REP8.CMD HANGS ON EXIT.
• IV75238: Increase the robustness of connector to manage corrupted dependencies.
• IV74788: SUBMIT "EVERY 0000" JOB FROM TDWC RUNS ONLY ONCE INSTEAD OF EVERY.
• IV74774: REPLYING TO A PROMPT FROM THE TWSACTIONPROVIDER FAILS.
• IV74756: BATCHMAN EVENT 305 IS ALWAYS LOGGED TO EVENTS LOG.
• IV74723: UNABLE TO UPGRADE TWS 8.5.1 TO 9.1 ON HP-UX WITH INSTALLATION MANAGER 1.6.3.1.
• IV74721: EVENT 203 JOB NAME TRUNCATED FOR EVENT 203 WHEN JOB NAME LENGTH IS LONGER .
• IV74489: UNABLE TO SUBMIT ISERIES JOBS WITH PARAMETERS.
• IV74466: TWS 9.2 HAS INCORRECT PERMISSIONS IN THE TWS/TMP DIRECTORY.
• IV74101: TWS 9.3 TWS_INST_PULL_INFO HANGS.
• IV73920: EVENT RULES ARE STUCK WITH OLD DDM AFTER A SWITCHMGR.
• IV73926: DYNAMIC JOB WITH NOT FOUND EXECUTABLE SCRIPT CREATES DEFUNCT PROCESS.
• IV73190: netman crashes during port scan.
• IV73111: Increase mirroring cache performance.
• IV72859: monman performance improvement.
• IV72533: twsClusterAdm.log is not flushed, and saved only at exit.
• IV71543: NATIVE LEAK WHEN TWS RUNS FOR A LONG TIME.
• IV71470: JOBS WITH OPENS DEP RUN INSTEAD OF CANCELLING AFTER A CANCEL PEND, FOLLOWED BY A RELEASE DEPS PERFORMED AGAINST THE JOB.
• IV70832: TWS ADMIN USER IS USED TO CHECK AN EXISTENCE OF SCRIPTNAME INSTEAD OF STREAMLOGON USER.
• IV68941: Create dbreorg for broker tables
• IV68058: sbs of a jobstream on a workstation set to IGNORE but still in the plan fails.
• IV67024: SAP JOBS FOR DYNAMIC AGENT REMAIN IN READY STATE CONSUME CPU LIMIT.
• IV66331: events-message.jar filenotfound exception during server startup.
• IV62180: MBCS characters are garbled when running twsinst with "-LANG JA" or system environment LANG=JA on Japanese Windows operating system.
• IV54835: INSTALLATION FAILS WITH MISSING MSVCR71.DLL .
• IV52812: SHUTWOWN_CLU.CMD DOES NOT STOP TOKENSERVICE.
• IV73302: CPU UTILIZATION COULD BE WRONG DUE TO INCORRECT CALCULATIONS.
• IV77654: Missing ITMCreatesituations.

List of defects fixed:

• 131495: Jazz for Service Management fresh installation might take a long time to complete.
• 132608: Tivoli Common Reporting: the scanner misses some required libs on RHEL 6.2.
• 133843: JnextPlan -> deleting 1.4 10ˆ6 entries from .JHR_JOB_HISTORY_RUNS cause db2 error because exhausting db2 transactions log.
• 134827: resource usage holders capping to 32 causes mirroring thorughout to be decreased and overhead DB CPU consumption
• 136230: Events not processed and discarded if the monbox.msg queue is full
• 136971: during FINAL lots of Sinfonia.xxxx files are generated
• 137459: IBMi agents: an error occurs trying to connect the agents by test connection
• 137853: DWB thread used to move job history data to archive stops to work properly
• 138792: Direct upgrade MDM 851fp -> 93: Restore step delete the backup.zip and the user cannot restore the old instance
• 141026: Scheduling Centralized Agent Update Job: Test connection does not work when reopening the job in Workload Editor
• 141209: Windows7 onPremise: installation fails if user's password contains special characters
• 142040: SAP BO: Internal server error when add attachment option is selected
• 144320: Change the select to poll to prevent crash in case of fd >1024.
• 143030: "java.lang.ArrayIndexOutOfBoundsException" after Resetplan and Jnextpla doesn't allow to schedule anything on dynamic agents
• 143095: "errno 9" while executing "sleep 1" command on AIX node with high concurrency
• 143153: Monitoring of jobs in Hybrid configuration: dependencies don't work well when Context-ObjectCount is set to 0
• 143277: more than 10K mirroring updates have been lost during standard performance workload
• 143809: MDM 93FP1 Build doesn't contains files to manage manually the db upgrade
• 144214: DWB thread used to move job history data to archive stops to work properly
• 144558: Error in the Start / Stop / Link / Unlink operations for the Monitoring Domain
• 144729: Planman checksync hangs on Windows operating systems.
• 144785: NOP: The CANCP status does not allow some scenarios.
• 144860: Upgrade to 93 FP1 hangs on Windows with Oracle db
• 144973: FTA Fresh: failure during installLWAAction.sh
• 145005: Rollback does not work correctly, after upgrade from 91FP1 to 93FP1 on Windows
• 145008: Rollback does not work correctly, after upgrade from 86FP2 to 93FP1 on Linux
• 145054: DA fresh installation no-root: JobManager doesn't start
• 145059: After MDM installation FENCE is set to GO.
• 145194: Incorrect job stream and dependency status working with pending predecessors.
• 145203: Wrong status for JS with Until suppressed jobs
• 145581: Every donostart is affected by the until issue on job stream
• 145600: param CLI hangs on FTA installed on windows
• 146147: Response files contains a real workstation name
• 146254: The MDM update remove the libraries in the method folder
• 146259: Incorrect profile name in the upgrade response file from 8.6 for MDM and DDM
• 146723: Incorrect owner assigned to the localopts file during installation
• 146750: FileTransfer job created on 931 fails on agent with version minor than 93
• 146812: MDM installation failed on Windows with error "AWSJIM901E: File C:\twsapps\tws\tws\TWS\TSAMP does not exist".
• 146915: Dependencies: defining an every option the condition are not correctly evaluated
• 146985: Agent javacore dump on Linux X64
• 147280: IBMi: File transfer job doesn't work
• 147314: JobStreamInPlan --> getNumberOfJobDependencies(): Source Plan Symph = 0 Dest Plan DB = -1
• 147489: Override estimation: the month table is filling the n-1 day
• 144168: SwitchBroker does not work in 9.1 FP2.
• 144167: AWSFAB025E message returned during installation.
• 144150: Increase the stack size for the WebSphere Application Server on Linux.
• 144133: Installation fails during update FTA 9.1 FP1 to FTA 9.1 FP2.
• 143851: SwitchBroker does not work.
• 143651: monman improvement: send cpu name of dynamic agent.
• 143631: Randomic Crash caused by GC on method calls local variable when GC runs.
• 143586: The addBrokerWorkstation always sends a full scan.
• 143074: TWS86 iSeries z-centric agent requires filewatch to run via OS/400®.

The following are software limitations and workarounds that affect IBM Workload Automation version 9.3.0 Fix Pack 1, 2, 3 and 4. For a list of known problems and limitations documented for the V9.3 General Availability release, refer to the product Release Notes®.

9.3.0 Fix Pack 4:

IJ10469: Fixpack 9.3 installation fails when dynamic agent is updated

Workaround: Before installing 9.3 Fixpack 3 dynamic agent on AIX, ensure that $BASEPATH value is empty.

Installing 9.3 FP4 dynamic or FTA agents on Windows platform

To install 9.3 FP4 dynamic or FTA agents on Windows platform, you need to download and install vcredist_x64.exe libraries

9.3.0 Fix Pack 3:

169512: spaceUsed.exe crash during installation of fix pack 3 on a master domain manager

When installing the fix pack, ensure the installation path is not longer than 260 characters. This is due to a Windows limitation. See note: https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.85%29.aspx#maxpath.

178283: Composer requires environment variables to be set

To have the composer command line function correctly, you need to set a number of environment variables either through submitting some commands or running the tws_env script. To set the variables:

Submit the following commands:

On UNIX:

  UNISONHOME=<TWS_HOME_DIR_PATH>  PATH=$UNISONHOME:$UNISONHOME/bin:$PATH;  export PATH  ITA_CFG=$UNISONHOME/ITA/cpa/ita/ita.ini  export ITA_CFG 

On Windows:

  set UNISONHOME=<TWS_HOME_DIR_PATH>  set ITA_CFG=%UNISONHOME%\ITA\cpa\ita\ita.ini  set PATH=%UNISONHOME%\bin;%UNISONHOME%\ITA\cpa\ita;%PATH%

OR

Run the tws_env script:

On UNIX:

  ./<TWS_HOME_DIR_PATH>/tws_env.sh

On Windows:

  \<TWS_HOME_DIR_PATH>\tws_env.cmd

where the default value of <TWS_HOME_DIR_PATH>is: /opt/IBM/TWA/TWS on UNIX and C:\Program Files\IBM\TWA\TWS on Windows.

9.3.0 Fix Pack 2:

Error installing fix pack on Solaris operating system with an Oracle database

When installing the fix pack on a Solaris operating system where an Oracle database is used, the installation must be performed using a connection that is not in SSL between the machine where the installation is being performed and the machine where the Oracle database is installed. (156227)

During the upgrade of the master domain manager, the installation process fails to retrieve information if the WebSphere Application Server was upgraded to V8.5.5.4

During the upgrade of the master domain manager, the installation process attempts to retrieve information from your environment. If the installation fails to perform the retrieve, and you have recently upgraded WebSphere Application Server to version 8.5.5.4, then you need to stop, start, and stop again, the WebSphere Application Server, and then restart the upgrade installation process for the master. (152994)

Centralized agent update of a dynamic agent fails to update agent on AIX with no root mode

Dynamic agent updates performed using the centralized agent update method from the Dynamic Workload Console fail on AIX operating systems in no root mode.

Workaround: Update the dynamic agent manually using the twsinst script.

Dynamic agent workstation name or cpuname is regenerated when upgrading from V8.5.1 to V9.3 Fix Pack 2

When upgrading a V8.5.1 master domain manager, backup master domain manager, dynamic domain manager, or backup dynamic domain manager to V9.3 Fix Pack 2, the -displayname <agent_name>option used to assign the agent name by the twsinst installation script, is ignored. The result is that the agent display name is automatically generated and cannot be assigned during the upgrade. This mainly affects dynamic jobs that were defined using JSDL templates in V8.5.1. (157695)

Workaround: Perform the following steps on each agent:

1. Stop the agent by issuing the following command:

   On UNIX:

     ./ShutDownLwa

   On Windows:

     shutdownlwa  

2. Rename the agent by assigning the name to the ComputerSystemDisplayName property in the JobManager.ini agent configuration file.
3. Restart the agent by issuing the following command:

   On UNIX:

     ./StartUpLwa.sh

   On Windows:

     startuplwa 

9.3.0 Fix Pack 1

Apache Commons Collections Vulnerability

WebSphere Application Server uses Apache Commons Collections which was found to contain a remotely exploitable vulnerability.

Workaround: To mitigate this problem, you must install the fix found in this technote: https://www-304.ibm.com/support/docview.wss?uid=swg24041257.

File transfer job submitted on a Windows agent ends in error

When endpoint protection software is active on a Windows agent workstation, the FTP connection is blocked by Java. A Java technology bug reporting this issue can be accessed at http://bugs.java.com/bugdatabase/view_bug.do?bug_id=7077696.

Centralized agent update fails on a dynamic agent, on UNIX operating systems, previously upgraded to the version 9.3 General Availability (GA) level

When applying version 9.3 Fix Pack 1 using the centralized agent update method on a dynamic agent only (without the fault-tolerant agent), on a UNIX operating system, that was upgraded to the version 9.3 GA level from a previous version, the update fails.

Workaround: Install the update manually on the agent workstation.

Centralized agent update not supported on IBM i

Launching the centralized agent update on an IBM i agent, the update fails.

Workaround: Install the update manually on the agent workstation.

On IBM i agent workstations the sendevent utility command requires manually setting

The sendevent utility command does not work unless an environment variable is set manually first.

Workaround: To use the utility command, sendevent, from the command line (./TWS/CLI/bin/sendevent) on IBM i, you must first set the environment variable QIBM_MULTI_THREADED to Y to alert the QShell to allow multithreading by submitting the following command:

  export QIBM_MULTI_THREADED=Y

When centralized agent update of a fault-tolerant agent fails, the restore operation sets the fence priority option to go

When a fault-tolerant agent is updated using the centralized agent update method, and the update fails, the fault-tolerant agent is restored to the previous release level, and the fence priority option is to go.

You can manually reset the fence priority option from the Dynamic Workload Console or using the conman command line. You can do this directly from the master domain manager rather than connecting to the agent workstation.

Job dependency status incorrectly reported after job execution

If plan replication is disabled, and you have a job or job stream running on a fault-tolerant agent, and there are conditional dependences defined, when monitoring the status of the job or job stream, some dependencies might report an undefined dependency status, even if the dependencies have been evaluated. The job or job stream status event might arrive on the master domain manager before the dependencies are evaluated.

Workaround: Decrease the value of the bm look option, for example to 5, in the localopts on the master domain manager so that batchman checks on the dependencies of the other workstations more frequently before the job or job stream status event arrives on the master domain manager.

IBM Workload Automation version 9.3.0 Fix Pack 4 supports all product versions indicated in the IBM Workload Automation version 9.3 Release Notes which can be accessed at the following link: http://www-01.ibm.com/support/docview.wss?uid=swg27045180#h3interop_tables.

For the most up-to-date information about disk space and memory requirements, generate a dynamic hardware requirements report from the IBM Software Product Compatibility Reports web site at the following URL: http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/hardwareReqsForProduct?deliverableId=1393949467532&osPlatforms=AIX|HP|IBM%20i|Linux|Solaris|Windows|z/OS&duComponentIds=S002|S001|A005|A003|A004.

  <TWA_HOME>/TWS + <TWA_HOME>/TDWB + <TWA_HOME>/wastools + <TWA_HOME>/properties

Master domain manager or dynamic domain manger or their backups:

To uninstall using the IBM Installation Manager, see Planning and Installation.

Fault-tolerant agent or domain manager:

To uninstall the entire IBM Workload Automation instance, use the twsinst -uninst -uname username command from the TWS_home directory, where username is the name of the user for which the IBM Workload Automation agent is uninstalled.

The following are the changes to the documentation as a result of the APARs and fixes in this fix pack. The complete library at the version 9.3 fix pack 4 level is available in IBM Knowledge Center.