There are no new features introduced with this fix pack.

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

Extended support for the following product releases

• WebSphere Application Server 8.5.5 FP 11.

  For a fresh installation of the Dynamic Workload Console version 9.3.0 Fix Pack 3 with WebSphere Application Server 8.5.5 FP 11, see the section about Known limitations and workarounds.

• Jazz for Service Management 1.1.3 CP2
• Installation Manager 1.1.8.6

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 Dynamic Workload Console 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 Dynamic Workload Console Fix Pack 3 for version 9.3.0

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 and improved web interfaces

The Workload Designer and Dynamic Workload Console interfaces have undergone some visual and usability improvements. The Workload Designer has been completely redesigned to improve your user experience. The new interface features a Welcome page which directs you to the main tasks to get you started with just one click. A similar function is available in the Welcome page for the Dynamic Workload Console, which provides a single entry point for accessing all your IBM Workload Scheduler web interfaces. For more information see Designing your workload available in the online product documentation 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.

Creating a URL to launch the Plan View in context

You can create a URL to launch the Dynamic Workload Console and have it directly open the Plan View. You can then include this URL in an external application, for example, to quickly and easily access the Plan View. For more information see Creating a URL to launch the Plan View in context available in the online product documentation in IBM Knowledge Center.

Auto-complete for workstation names and user ID

An auto-complete function is now available for workstation names and user ID in job definitions in Workload Designer.

Managing Workload Security with Dynamic Workload Console

You can manage security settings in your environment by using Dynamic Workload Console

From the navigation toolbar -> Administration -> Workload Environment Design, select Manage Workload Security. Here you can create and manage security objects in the database.

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.

Tooltips and online help do assist you while accomplishing security tasks.

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 managers.

For more information see Managing workload security available in the online product documentation in IBM Knowledge Center.

Restarting Informatica PowerCenter jobs from the point of failure

When monitoring an Informatica PowerCenter job from Dynamic Workload Console, you can display detailed information about the Informatica PowerCenter workflow and run actions either on the workflow, or on any first-level tasks that are in the workflow, if these are sessions or worklets.

If the Informatica PowerCenter workflow fails, you can restart it from the failed task. For more information see Monitoring IBM Workload Scheduler jobs that run Informatica PowerCenter workflows available in the online product documentation in IBM Knowledge Center.

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.

Single Entry Point

You're going back and forth between user interfaces and you're having trouble keeping track of which URL corresponds to which UI. Do you find yourself guessing or trying to remember the URL to access the mobile applications? Application Lab? The Dynamic Workload Console? The guessing game is over. The Single Entry Point is a single web-based page that provides direct access to all of the IBM Workload Scheduler user interfaces.

Single Entry Point is a role-based interface that you can access from any computer in your environment by using a web browser through the secure HTTPS.

Single Entry Point provides quick links to the most important Dynamic Workload Console tasks: connect your engines, design your workload, monitor your workload, and dashboard. With Single Entry Point you can access the mobile applications through the link or the Qrcode. Define your engine and your environment ID in the Single Entry Point interface, and access your Application Lab environment.

For more information see IBM Workload Scheduler user interfaces available in the online product documentation available in IBM Knowledge Center.

Tivoli Common Reporting reports extended to MS SQL databases

Tivoli Common Reporting is an optional integration service of Jazz for Service Management extension for IBM WebSphere, which is installed with WebSphere Application Server.

Tivoli Common Reporting provides a web user interface functioning as a portal for IBM Cognos and allows you to administer, run, customize, and create IBM Workload Scheduler reports. Previously the reports were available only for IBM DB2 databases and now the support is extended to include also Microsoft SQL Server databases in a distributed environment. The reports include:

• Job Run History
• Job Run Statistics Chart
• Job Run Statistics Table

For more information see Tivoli Common Reporting reports available in the online product documentation available in IBM Knowledge Center.

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.

Implementing What-if Analysis changes to the plan

The IBM Workload Scheduler What-if Analysis shows activities displayed against time and gives you a visual representation of your plan at a glance in real time. Running the What-if Analysis before implementing the actual plan shows your predicted results at a glance. By seeing the results beforehand you can plan for any potential problems before you start. Any changes that you make in What-if Analysis are applied only for simulation purposes until you use the option "Apply changes" to the actual plan.

The jobs are visually displayed in a Gantt chart. A Gantt chart is a time and activity bar chart that illustrates a project schedule. It displays the current status of critical jobs, the planned start and end times, deadline, and the risk level associated to each critical job. For more information, see Analyzing the impact of changes on your environment.

Convert Crontab files and Windows Task Scheduler jobs

You can use the Dynamic Workload Console to read Crontab files or Windows Task Scheduler jobs and convert them into IBM Workload Scheduler objects. The jobs are added to your workload with the same specifications as the original jobs. The job streams reflect the time definition of the Cron or Windows Task Scheduler commands. You can then modify, schedule, and monitor them together with all your other objects. For more information, see Import Cron and Windows Task Scheduler.

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 SUSPENDED status. This status indicates that the job is running while waiting for input. When the input is received, the job status changes to Running.

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 jobs are monitored 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.

Miscellaneous enhancements:

Graphical view enhancements (RFE 134705)

Viewing and printing large job streams from a graphical view has been improved. Changes have been made to the general layout including making external dependencies easier to view, changing the size of the graphical elements so that the entire job or job stream name is no longer truncated, and improving the zoom level so that you can zoom further on larger job streams.

Persistent settings for column resizing (RFE 114136)

Resizing columns is sometimes necessary, for example, to display the complete name of a job or job stream name. With this fix pack, any resizing you apply to a column is maintained throughout the current session and for all subsequent sessions. The same resizing is automatically applied to other views displaying the same information.

Job display improvement

The filter to show jobs regardless of their rerun status has been restored.

For more information about new features introduced with this fix pack, see Dynamic Workload Console 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:

APAR number	Abstract
IJ00226:	MANY ISSUES AND IMPROVEMENTS WITH VARIANT ON SAP JOBS
IJ00338:	JOBSTREAM IS PLANNED UNEXPECTEDLY ON EXCEPT CALENDAR DATE
IJ02081:	JOB RERUN FROM IMPACT VIEW FAILS WITH AWSUI6401E
IJ03408:	DWC 9.3 RUN CYCLE PREVIEW ISSUE
IJ03889:	TDWCGLOBALSETTINGS MONITOR PARAMETERS ARE NOT TAKING EFFECT ON TDWC
IJ13299:	JOB DEPENDENCY NOT WORKING PROPERLY IN TDWC
IJ13912:	UNABLE TO IMPORT SELF SERVICE CATALOGS WHEN THERE IS NO ASSOCIATE
IJ22077:	JCL RETRIEVED FROM MODEL DOESN'T HAVE A LEADING SPACES
IV87759:	DWC UNABLE TO EDIT A JOB THAT RUNS A SCRIPT IN WORKLOAD DESIGNER IN IE11, MESSAGE AWSUI6158W
IV97159:	EXTERNAL JOB STREAM DEPENDENCY WITH ABSOLUTE INTERVAL CANNOT BE SAVED IN DWC
IV98330:	DWC A NOT STANDARD CONTEXT ROOT DOES NOT WORK AFTER UPDATE
IV99439:	INCORRECT DATA INTO ACTUAL START ON LISTING JOBS ON ZOSENGINES

List of defects fixed:

Defect number	Abstract
WA-84938:	APPSCAN: CROSS-SITE SCRIPTING ON SSMANAGEMENT.JSP
WA-84940:	APPSCAN: CROSS-SITE REQUEST FORGERY ON SSMANAGEMENT.JSP AND OTHERS
WA-84942:	APPSCAN: LINK INJECTION ON SSMANAGEMENT.JSP
WA-84961:	APPSCAN: PHISHING THROUGH FRAMES ON SSMANAGEMENT.JSP
WA-85322:	CROSS SITE SCRIPTING AT IBM TVOLI v9.3.0.3 AT ENGINE PARAMETER

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

List of APARs fixed:

APAR number	Abstract
176489	REST: Missing jsdl format saving a job from DWC with REST connection
IV94433	LIST WORKLOAD DEFINTIONS DOES NOT DISPLAY
IV72221	CUSTOMIZE THE SEARCH NUMBER OF ELEMENTS IN THE WORKLOAD EDITOR
IV91499	WHAT IF FUNCTION CAUSING PERFORMANCE ISSUE
IV71729	ISSUES WITH VARIANTS' QUOTES BEING DROPPED FROM DEFINITIONS SAVED THROUGH TDWC
IV89798	"CHOOSE ENGINE" IN "ALL CONFIGURED TASK" DOESN'T WORKS CORRECTLY WITH CREDENTIALS SHARED
IV90353	WHEN DWC IS CONFIGURED TO USE DB, QUERY TASK PERFOMANCE IS SLOW
IV89873	VARIOUS PROBLEMS WITH IMPORTING CRONTAB DEFINITION.
IV81646	CANNOT CLOSE SIMULTANEOUSLY MULTIPLE TASKS
IV84906	SELF-SERVICE CATALOG LINK ON MOBILE IS NOT WORKING FROM MAIN PAGE
IV67423	TDWC SAVES CAPITAL LETTERS IN JOBID AS SMALL LETTERS IN SAP JOB DEFINITION
IV85511	Actual End Time incorrect for job run history in DWC
IV89871	OPENING JOBSTREAMS IN DWC YIELD CONVERTEREXCEPTION ERROR
IV89497	DATE VALUE CHANGES FOR VARIBLE TABLE USING DWC VIEW MODE WHILE THE TABLE IS MODIFIED/LOCKED BY ANOTHER USER
IV91527	WHEN EXPORTING THE WEBUI USERS PREFERENCES THE FILE IS CUT
IV90997	CUSTOM ACTION FOR DYNAMIC WORKLOAD CONSOLE POPS UP SCREEN WITHOUT SCROLLBAR
IV90846	VIEW PREPRODUCTION PLAN" DOES NOT ALLOW TO CHOOSE THE ENGINE
IV92221	MANY ENGINE DEFINITIONS CAUSE PROBLEMS FOR MONITOR WORKLOAD
IV93638	DYNAMIC WORKLOAD CONSOLE HISTORICAL REPORT SHOWS THE ACTUAL START TIME INCORRECTLY FOR JOBS THAT STARTED PRIOR TO DAYLIGHT SAVING TIME (DST)
IV94803	DYNAMIC WORKLOAD CONSOLE MONITORING VIEW DOES NOT SHOW A JOB RERUN WITH A SPECIFIC TIME ASSIGNED
IV94804	DYNAMIC WORKLOAD CONSOLE JOB STREAM VIEW SHOWS THE FIRST RERUN ONLY

List of defects fixed:

Defect number	Abstract
168111	Missing job stream dependency revalidation after job rerun
167486	What-If: Allow WSA also on backup master
167485	What-If: Add a limited cache for archived Critical network
167484	What-If: Make the Critical Path building synchronous with itself

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

List of APARs fixed:

• IV80576: CRASH DURING PLAN VIEW OF A LARGE QUERY OF JOBSTREAM
• IV69069: DYNAMIC WORKLOAD CONSOLE UPGRADE FAILS DUE TO EWAS START ERROR XMN TOO LARGE
• IV80208: AWKIPC005E FAILED TO RUN WORKFLOW ERROR ENCOUNTERED WHEN ATTEMPTING TO RUN INFORMATICA ...
• IV81244: "REPLY YES TO XXXXX" (XXXXX=PROMPT) ACTION DOES NOT WORK AFTER
• IV81313: EVENT RULE LAUNCHING Z/OS JOB GETS ERROR AWSZAP006E AFTER
• IV77219: PROMPTSTATUSCHANGED EVENT LOST IF THE PROMPT HAS DOUBLE QUOTES
• IV76571: ERROR: 'UNRECOGNIZED COMMAND LINE ARGUMENT "-NOROOT"' WITH LINUX 9.3 TDWC INSTALL USING 'SETUPDWC.SH -NOROOT'. IV81197 JOBMANAGER SUDDENLY TERMINATES WITH CORE
• IV78611: PROBLEMS WHEN USING RUNCYCLE GROUPS AND FREEDAYS CALENDAR
• IV81843: UNABLE TO USE SPECIAL CHARACTERS IN Z/OS SHADOW JOB NAMES IN
• IV81843: DYNAMIC WORKLOAD CONSOLE 9.3 W/ IBM WORKLOAD SCHEDULER FOR Z/OS RETURNS SQL ERROR -206 FROM JOB HISTORY VIEW

List of APARs fixed in a z/OS environment:

• IBMi agent:
  • PI56945: CRITICAL JOB EXTENDED STATUS NOT UPDATED FOR SUSPENDED EVENT
  • PI62211: SUPPORT SUSPENDED STATUS IN A CONFIGURATION WITH DYNAMIC DOMAIN MANAGER
  • PI62823: SUPPORT SUSPENDED STATUS IN A CONFIGURATION WITH ALTERNATE WORKSTATION
• PI61504: SUPPORT INFORMATICA PLUG-IN ACTIONS FROM DYNAMIC WORKLOAD CONSOLE

List of defects fixed:

• 126590: EQQA540W has been changed in ERROR so the save of operation record in job stream and current plan should be stopped.
• 130480: TCR Installation fails on Linux for missing prerequisites.
• 131495: JazzSM fresh installation takes long time.
• 133721: Old product's name is present in the more info panel during Dynamic Workload Console installation.

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

List of APARs fixed:

• IV74788: SUBMIT "EVERY 0000" JOB FROM TDWC RUNS ONLY ONCE INSTEAD OF EVERY.
• IV73206: When you change the LPAR z/OS® connector, the DWC does not sent the pifInit.

List of defects fixed:

• 141274: Workload Designer - create job stream errors.
• 141277: Workload Designer - absolute and relative interval doesn't work on conditional dependency.
• 144780: By DWC, cannot release a dependency.
• 144463: DWC silent installation 93FP1 one shot: failure during z-connector installation.
• 138468: TDWC Upgrade from 851fp5 to 9.3 failure.
• 146907: SSD - cannot create new dashboard using Google Chrome.
• 118719: [DASH 56273] DWC - Workload Dashboard shows blank portlet in staging environment.
• 136243: The scripts that customize SQL uses a wrong name as JRE home dir.
• 145505: ING-TEST - DWC loads the same results even if you change the Engine Connection.
• 136245: What if: canceled job status is not correct.
• 146757: What if - the jobs have an incorrect duration.
• 147024: What if - incorrect js status using IE
• 146760: What if: wrong estimated duration for job in running state.
• 142003: IWS 9.3.1 - DWC 9.3 GA and DWC 9.3 FP1 installation blocked if there are more than one node on JazzSM profile.
• 144077: DWC 9.3.1, migrating DWC 9.1 FP2 to DWC 9.3 FP1 rollback does not work.

The following are software limitations and workarounds that affect Dynamic Workload Console 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 Dynamic Workload Console V9.3 Release Notes.

Technote 1667999 has been published with the steps needed to configure the Dynamic Workload Console to use all the authenticated portal user roles.

Read this section thoroughly before installing this fix pack.

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

Before starting the fix pack installation, ensure that you have the following space available in the file system. The values indicated in the table show the disk space required by the Dynamic Workload Console alone. For the disk space required by other components, see the relevant documentation. 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: https://www.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.

If the installation fails because of lack of free disk space, you must stop the installation, free space on your disk, and start the installation again.