The following new product features, enhancements (RFE), and changes are introduced with this Fix Pack:

Updated version of Installation Manager (IM)

Fix Pack 5 has been tested using IM 1.8.9

Updated version of WebSphere Application Server (WAS)

Fix Pack 5 has been tested using WAS version 8.5.5.14

The following new product features, enhancements, and changes are introduced with this Fix Pack:

DevOps made easier with workload applications

If you have a few use cases where the workload application templates replicated in your workload environment are a little too rigid, then this new enhancement will add the flexibility you are looking for.

After a workload application is exported into a workload environment, the contents such as, job streams, jobs, and other objects, are created in the environment and an association to the workload application is maintained. This allows for easy subsequent updates and synchronization between the workload application template exported from the source environment and the workload application in the target environment. The workload application can be easily replaced and updated. However, there might be certain circumstances where you prefer not to have an association to the workload application so that the imported objects can be freely updated or deleted.

When importing a workload application template, you can now specify whether you prefer to import only the objects contained in the template, without any ties to the workload application, or to import the objects maintaining their association to the workload application. Even after you have imported the contents of a workload application template into a target environment, removing the association to the original workload application template, you still have some options through the wappman command line that enable you to manage the objects as a whole, such as deleting all of the objects or replacing all of the objects.

These workload application template enhancements are supported when connected to an engine with version 9.4.0.4 or later

For details about importing a workload application template, see https://workloadautomation.hcldoc.com/help/index.jsp?topic=%2Fcom.hcl.wa.doc_9.4%2Fdistr%2Fsrc_tsweb%2FGeneral_Help%2FImporting_wkld_template_t.htm . For information about the new options available for wappman see https://workloadautomation.hcldoc.com/help/index.jsp?topic=%2Fcom.hcl.wa.doc_9.4%2Fdistr%2Fsrc_tsweb%2FGeneral_Help%2FImporting_wkld_template_t.htm .

Support for Dashboard Application Services Hub (DASH)

Fix Pack 4 has been tested using DASH version 3.1.3.0 Cumulative Patch-6.

Additional support for agents

Support for fault-tolerant agents, dynamic agents, and z/OS agents has been extended on Sun Solaris SPARC 64-bit.

Satisfying Requests for Enhancements (RFEs)

HCL Workload Automation satisfies Requests for Enhancements (RFEs).

Requests for Enhancements (RFEs) give customers the opportunity to collaborate directly with the product development team and other users. The team prioritizes and develops new product features based on proposals made by customers.

HCL Workload Automation V9.4 Fix Pack 4 delivers the following RFE:

RFE 117399: Windows 2016 WSCF cluster support

Support has been extended to Microsoft Windows Server 2016 Failover Clustering (WSCF) on agents.

Managing pools and agent connectivity

Starting from HCL Workload Automation version 9.4 Fix Pack 4, you can automatically register dynamic agents in pools by editing a file.

Starting from version 9.4 Fix Pack 1, you can automatically register dynamic agents in pools by editing the pools.properties file located in <TWS_home>/ITA/cpa/config.

The file is composed by a series of lines with a list of pools to which the agent will be automatically registered. To make the changes in this file effective on the agent, you must stop and start the agent.

Because an agent can encounter problems and is not able to register and go online, for example, if it does not find a pool defined in the system, there are options that can be used in the pools.properties file to allow the agent to go online even if some pools are not defined.

This alternative way of registering dynamic agents to a pool can be useful when you need to quickly add more than one agent to a pool, or when you want to associate multiple pools to a dynamic agent.

The following new product features, enhancements, and changes are introduced with this Fix Pack:

Extra opportunities for modifying job definitions already in the plan

Modify a job instance in the plan before it runs or modify an instance of a job in the plan that has already run and rerun the modified job.

You can modify a job definition in the database whenever and as many times as you want. However, there are times when you need to make changes to the job definition, but it has already been submitted into the plan and runs as is. This results in extra work and lost time in updating the definition in the database and then getting it into the plan to run.

This feature adds the flexibility you need so that you can now make changes to the definition even after it has already been submitted into the plan, maintaining the original definition in the database. With this additional flexibility, you can edit the job definition on-the-fly before it runs or rerun a job with a different definition. This can be done from either the Job Stream Graphical View, the job monitoring view, or from the conman command line.

Maybe you want to substitute the command or script executed by the job with a different one? Maybe you just need to tweak an argument? Maybe you need to rerun a job updating the logon name, priority, or connection server? Whatever the change, this enhancement allows you to quickly react and avoid possible disasters, and increase your productivity by addressing additional scenarios in your workload that were not contemplated at the time you modeled or planned your workload.

For details about how to modify the job definition in the plan see XYZ

Troubleshooting stalled jobs

Quickly identify what is holding back jobs that are ready to run but, for some unknown reason, do not run.

Sometimes your jobs are all ready to go, but for some anomalous reason, they do not start. A job can sometimes encounter specific circumstances where, although everything seems to be in check, there is still something that needs to be done before the job can start. You know that any dependencies it might have on predecessors have been resolved, you also know that the start time has come and gone, but something else is holding it back.

A new action is available when monitoring jobs that helps you identify what those circumstances might be. In addition to problem determination, it also helps you in resolving the problem. Sometimes it is as simple as tweaking the limit, other times a workstation needs to be linked, or maybe the jobman process is down. Whatever the reason might be, you can save time in determining the problem and identifying the solution with a new action available from the Dynamic Workload Console, “Why a job does not start”.

Enhancements to IBM I job monitoring and control

Monitoring and control facilities for IBM i jobs have been enhanced to simplify the management of IBM i inquiry messages.

Automated reply to inquiry messages

For the most frequent IBM i inquiry messages, you can define standard rules to automate the reply to the waiting messages. When defining an IBM i job, by using the Workload Designer of 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. When specifying the automated replies, a new parameter has been added to the job definition: the Message Max Replies parameter. It represents the maximum number of automated replies accepted for a specific message. This new parameter optimizes the management of IBM i inquiry messages.

For example, when you set a wrong reply to a message in the job definition, IBM i system keeps on sending out the same inquiry message repeatedly, while waiting for the correct reply. To avoid this issue, HCL Workload Automation has now the capability to intercept and disable the wrong reply and require, with a prompt, a direct reply from the Dynamic Workload Console. The job remains in SUSP (suspended) status until the correct reply is provided.

Reliable monitoring of IBM i job status changes

As an inquiry message receives an automated reply, the IBM i job status changes from SUSP (suspended) to EXEC (executing) and vice versa. All the job status changes are monitored and tracked. This is useful, for example, when you want to create an event rule definition to send an email every time a job status change occurs.

Improved trace facilities

Trace facilities for IBM i jobs have been improved. To specify the desired tracking level, customize your IBM i agent by setting the required parameters in the JobManager.ini file, in accordance with the settings on the IBM i system.

New Plug-ins for Cloud Automation

Amazon EC2, IBM SoftLayer, and Microsoft Azure plug-ins are available to manage the provisioning and de-provisioning of virtual machines in the cloud, on as-needed basis.

Customers choose to move their application to the cloud to focus on business optimization. Once in the cloud, applications rely on systems provisioned and de-provisioned to run defined business workflows but unpredictable workload volumes. Customers face a new question: Is it better to over-provision cloud resources with the risk of wasting them, or under-provision with the risk of degrading performance and delay the business process?

How about provisioning just the right amount of resources for only the time-period you need them? Exactly what you need, when you need it, and rather than incur extra costs and waste, de-provision when you’re done, all automatically.

To succeed in this challenge, a new approach is required, that strictly ties business workflows with cloud resource management. While managing a business application, IT organizations need to be able to orchestrate provisioning and de-provisioning of the infrastructure needed by the business application in the cloud.

HCL Workload Automation provides three Cloud Automation plug-ins, for different cloud providers, to manage the provisioning and de-provisioning of virtual machines in the cloud, on as-needed basis. By orchestrating the application workflow and the workflow that manages the entire lifecycle of the virtual machines needed by the applications (including the actions: start, stop, snapshot, etc…), HCL Workload Automation can increase both business and infrastructure agility. The plug-ins are:

• Plug-in for Amazon Web Services (EC2)
• Plug-in for IBM SoftLayer
• Plug-in for Microsoft Azure

Select your cloud provider, and add one or more jobs in the job stream that automates your business process flow to provide a flexible and dynamic allocation of cloud resources to your workload.

See the video: Workload Scheduler for Cloud Automation on the Workload Automation YouTube channel. More videos are available for the features released with V9.4 Fix Pack 3 on this dedicated playlist: Workload Scheduler V9.4, Fix Pack 3.

Apache Spark Plug-in

With the new HCL Workload Automation plug-in for Apache Spark, you can schedule, monitor and control Apache Spark jobs.

Apache Spark a lightning-fast cluster computing technology, designed for fast computation. It is based on Hadoop Map Reduce and extends the MapReduce model to efficiently use it for more types of computations, which includes interactive queries and stream processing. The main feature of Apache Spark is its in-memory cluster computing that increases the processing speed of an application. HCL Workload Automation provides a plug-in for Apache Spark that helps you manage your big data processing and analytics. With the plug-in for Apache Spark, you can define, schedule, monitor, and control Apache Spark jobs. Add one or more Apache Spark jobs in the job stream that automates your business process flow to obtain an end-to-end workload management solution.

For details, see Scheduling Applications with HCL Workload Automation

Restarting JSR 352 Java Batch jobs from the point of failure

You can restart JSR 352 Java Batch jobs from the point of failure.

During the execution of a JSR 352 Java Batch job, when monitoring the job from the Dynamic Workload Console

Replying to messages for IBM i child jobs

Support for replying to messages for an IBM i parent job was introduced in a previous release. With this release, the same support is extended to IBM i child jobs. When an IBM i job is in SUSP (suspended) status, waiting for a reply to a message, you can reply to the message for parent and child jobs from the Dynamic Workload Console when monitoring the parent job.

Specifying dependencies that link a job to a job stream or a job stream to a job

Dynamic Workload Console enhanced for z/OS users with application dependencies support.

Setting the Manually Hold, NOP, and Critical options in the AD database

You can now set the Manually Hold, NOP, and Critical options for a job directly in the Application Description database, from either the Options or Variable Duration and Deadline section.

REST API for z/OS users

Already available in the distributed environment and now available in a z/OS environment, a set of fully functional APIs that are implemented based on Representational State Transfer (REST) services. The REST API helps you easily integrate workload scheduling capabilities with external products and solutions.

For more information about new features introduced with this Fix Pack, see Summary of enhancements.

Helpful videos demonstrating new features for HCL Workload Automation is available on Workload Automation YouTube channel.

Extended support for the following product releases

• Windows 2016.
• WebSphere Application Server 8.5.5 FP 11. For a fresh installation of the Dynamic Workload Console version 9.4.0 Fix Pack 1 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.

Enhancements to What-if Analysis

Fix Pack 1 delivers a number of enhancements in the What-if Analysis Gantt view.

What-if analysis available from non-critical jobs in a z/OS environment

In addition to launching the What-if analysis from any critical job in a z/OS environment, you can now also launch it from any non-critical job that is part of the critical network.

Assess impact on critical jobs quickly by narrowing the display of successors to only critical jobs

Show the impact only on critical jobs, excluding all other successor jobs. Viewing the impact in this way narrows the results to display only the most critical and also improves performance when there is a high number of successor jobs to display.

Optimizing performance with the capability of excluding predecessors from the view

An new option has been added to the Tdwcglobalsettings.xml file, whatIfAutoLoadPreds, that enables you to manage whether or not you want to automatically load predecessors in the view. The default setting is to avoid loading predecessors which, in the case of hundreds of predecessors, results in optimized performance.

Setting the Earliest Start Time to the Estimated Start Time calculated by the server

Even if all predecessors are not displayed in the view, you can still consider the impact of predecessors on a job's earliest start time. The server calculates an estimated start time for the job and through a new action named "Set Earliest Start Time to Server Estimation", you can set the job's earliest start time, to the time calculated by the server as the estimated start time.

For information about What-if analysis capabilities see Analyzing the impact of changes on your environment.

Customizable Dashboard

The following Dashboard filters are now available in a Dynamic Workload Console connected to a z/OS engine:

• Job name
• Owner
• Job stream name
• Workstation name

Higher level of control over the What-If Analysis

A new optman global option is available to administrators, to make the What-If Analysis feature optional in your environment.

Administrator's level of control over the What-If Analysis has increased with 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 What-if analysis capabilities see Analyzing the impact of changes on your environment.

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 Disable the What-if Analysis

Revamped Graphical Views

Enhancements made to the graphical view of your database objects has been extended to the plan to provide a consistent view and user experience.

Consistent views and revamped user experience across graphical views: Job Stream View, Preproduction Plan View, Show Plan View, Modelling Graphical View

Simple shapes to easily identify objects have been used, new icons to improve the interaction and quickly identify actions have been created, new colors and background to better visualize the objects have been applied.

Merge Impact View with the Job Stream View to provide a more comprehensive view for monitoring and recovery actions

In previous releases the Impact View and Job Stream View were provided as separate views to monitor the progress of your job streams in the plan. With this release, the Impact View has been merged with the Job Stream View to provide a single view from where you can analyze one or more job streams, jobs, dependencies and also analyze the impact a job stream and its jobs can have on the rest of the plan. This view is available in both distributed and z/OS environments.

Automatic refresh in Job Stream View

In previous releases, any actions performed in this view that affect the plan required a manual refresh of the view using the Refresh option. With this release, the view is automatically refreshed so that the information is always up-to-date. The automatic refresh is supported only on connections to engines at the Version 9.4 Fix Pack 1 level or later.

Persistent layout

The flexibility of the layout of the graphical view from the Workload Designer in distributed environments enables you to reposition objects in whichever way is most useful or meaningful for you. If you save your layout in the Workload Designer, the same layout or positioning is maintained when you open the same job stream in the Job Stream View.

Some tips to optimize the performance of the new Graphical Views

When working with job streams with more than 500 objects (jobs, job streams and dependencies), to optimize the application performance of the new Graphical Views it is recommended that you follow some tips:

Choose Google Chrome

Chrome has better performance compared to other browsers. In some cases, it is 4 times faster than other browsers to open Graphical Views containing complex objects. Also, using Mozilla Firefox is preferable to Microsoft Internet Explorer or Microsoft Edge.

Customize and save the job stream layout

When viewing job streams in the Job Stream View, first customize and save the job stream layout in the Workload Designer modelling graphical view and then open it in the Job Stream View where the same layout is reused to achieve better performance.

Use Graphical Views on a powerful client in terms of CPU and RAM

Adequately set the hardware configuration of the client machine from which the Dynamic Workload Console is accessed.

For more information see Graphical Views in the plan.

Advanced rerun flexibility

The new advanced rerun options help you orchestrate your workflows seamlessly, building recovery logic into the job definition itself and rerunning job successors directly from the Monitor Workload view.

When you create a job definition, you can now specify that you want the job to rerun for a specific number of times and after a specific interval, in case of failure. This ensures that fewer alerts are generated and the workflow continues smoothly. For example, if you have a job that needs to connect to a server which is periodically restarted, you can specify in the job definition that you want the job to rerun for a specific number of times and after a specified interval.

If the parent job ran on a workstation that is part of a pool or a dynamic pool, you can decide whether it must rerun on the same workstation or on a different one. This is because the workload on pools and dynamic pools is assigned dynamically based on a number of criteria and the job might be rerun on a different workstation.

Also, if a job fails, you can identify all its successors at a glance and decide whether you want to rerun the job with its successors. You can rerun either all successors in the same job stream, or all successors overall, both in the same job stream and in other job streams, if any.

For more information about how to specify the rerun options in the job definition from the Dynamic Workload Console, see Controlling job and job stream processing.

New automation utilities

HCL Workload Automation Job Management Plug-in

The new Job Management plug-in is available in the Automation Utilities plug-in category. Automation Utilities are plug-ins that facilitate specific operations. Use the Job Management plug-in, to run one of the following actions on any job in the job stream where the Job Management job is running:

• Rerun
• Rerun the job and all its successor jobs
• Rerun the job and its successor jobs in the same job stream
• Release
• Release Dependencies
• Cancel
• Cancel Pending
• Hold
• Kill
• Confirm ABEND
• Confirm SUCC

The Job Management plug-in simplifies recovery scenarios and enables the automation of iterative workflows. For example, in a recovery scenario, you can insert a Job Management job in your workflow. This causes the original job to rerun automatically when the relevant recovery job completes successfully, reducing effort and time consumption.

For more information see Job Management jobs.

Job Stream Submission Plug-in

The new Job Stream Submission plug-in is available in the Automation Utilities plug-in category. Automation Utilities are plug-ins that facilitate specific operations. Use the Job Stream Submission plug-in, to submit a job stream for processing.

By adding the Job Stream Submission plug-in to your workflow, you can automate the submission of a specific job stream, minimizing code scripts and manual effort. Also, you can specify the earliest start time for the job stream and define the variable table associated to the job stream.

For more information see Job Stream Submission jobs.

Condition-based workload automation

Condition-based workload automation provides a simple and immediate way to have your workflows start at just the right time. You can define in your job stream a condition that, when met, releases the job stream to run as scheduled.

For example, if you have a job stream containing jobs which analyze one or more files, you can have the job stream start only after the file or files have been modified or created. Also, if the job stream contains jobs which process the data in a database, you might want to have the job stream start after enough rows have been written into the database. You can also have HCL Workload Automation check repeatedly whether the condition is met.

You can start your workflow based on one of the following conditions:

• One or more files being created.
• One or more files being modified.
• A job completing with its output condition satisfied. You can apply this logic to the job stream or to specific jobs in the job stream.

For more information, see Condition-based workflow automation.

New option for defining the latest start time in job streams

The Apply to each job check box defines the latest start time of a job stream. It also determines the behavior of the jobs in the job stream when the job stream is approaching its latest start time. Select the Apply to each job check box to avoid your job stream being suppressed if it starts right before its latest start time and the duration of one or more jobs in it exceeds the latest start time.

For more information, see the online help for the job stream properties panel in the Workload Designer.

New option for defining actions on late jobs

The Kill if deadline expires check box defines the action to be taken on a job in job stream when the job's deadline expires. If the job is running when the deadline expires, it is killed. Killed jobs end in the ABEND state. Any jobs or job streams that are dependent on a killed job are not released. If the dependency on the job is a conditional dependency on the job completing in ABEND state, that dependency is released.

For more information, see the online help for the job properties panel in the Workload Designer.

New options in managing workload applications

The following new options are available:

Export a job stream definition as a workload application template

From the Workload Designer, you can export a job stream definition and save it as a workload application template in a compressed file. The job stream definition can then be imported in another environment.

For more information, see Exporting a job stream definition as a workload application template.

Rename a workload application during the import process

A new parameter -workloadApplicationName <workload_application_name> is available for the wappman -import command to rename the workload application during the import process.

For more information about new features introduced with this Fix Pack, see Summary of enhancements.

Helpful videos demonstrating new features for HCL Workload Automation is available on Workload Automation YouTube channel.

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

This Fix Pack includes a number of fixes for internal defects found by the verification team that mainly cover the following product capabilities: installation, auditing, and mirroring.

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

This Fix Pack includes a number of fixes for internal defects found by the verification team that mainly cover the following product capabilities: installation, auditing, and mirroring.

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

This Fix Pack includes a number of fixes for internal defects found by the verification team that mainly cover the following product capabilities: installation, auditing, and mirroring.

This Fix Pack includes a number of fixes for internal defects found by the verification team that mainly cover the following product capabilities: installation, auditing, and mirroring.

This section lists APARs solved by Fix Pack 2.

This Fix Pack includes a number of fixes for internal defects found by the verification team that mainly cover the following product capabilities: installation, auditing, and mirroring.

This section lists APARs solved by Fix Pack 1.

List of APARs fixed:

IV60757

AFTER SWITCHING MANAGER CANNOT BROWSE JOBLOGS FOR ALL DYNAMIC JOBS RUN ON THE MASTER

IV72221

CUSTOMIZE THE SEARCH NUMBER OF ELEMENTS IN THE WORKLOAD DESIGNER

IV84906

SELF-SERVICE CATALOG LINK ON MOBILE IS NOT WORKING FROM MAIN PAGE

IV90870

ESTIMATED DURATION WRONG ON MONITOR JOBS IN DYNAMIC WORKLOAD CONSOLE AND CONMAN

IV92221

MANY ENGINE DEFINITIONS CAUSE PROBLEMs FOR MONITOR WORKLOAD

IV92374

JOB STREAMS STAY IN READY WHEN VIEWED FROM THE DYNAMIC WORKLOAD CONSOLE IN A NOP SCENARIO

IV93052

unable to view joblog from DWC/conman when job defined on XA hosted by DWB using jsdl and with resources

IV93638

DWC HISTORICAL REPORT SHOWING THE ACTUAL START TIME INCORRECTLYFOR JOBS THAT STARTED PRIOR TO DST

IV94433

LIST WORKLOAD DEFINTIONS DOES NOT DISPLAY

IV95222

JOB LOG TRUNCATED AFTER 100 LINES

The following are software limitations and workarounds that affect Dynamic Workload Console version 9.4.0 Fix Pack 1, 2, 3, 4 and 5. For a list of known problems and limitations documented for the V9.4 General Availability release, refer to the https://workloadautomation.hcldoc.com/help/topic/com.hcl.wa.doc_9.4/distrDDguides.html.

9.4 Fix Pack 3:

Null Pointer Exception occurs changing the scheduled time from plan (70349)

When you are monitoring job streams, if you change information about the scheduled time for a job stream and then go back to the list of results containing the job stream, the hyperlink for the job stream might not work.

Workaround: Refresh the page.

Invalid identifier error thrown after saving dependencies for z/OS (70908)

When monitoring your workload, adding or deleting dependencies between jobs and job streams, or between job streams and job streams, the following error might occur and the operation fails:

AWSUI4064E The following error occurred: 
AWSJDB101E The object "invalid identifier" was not found

Job stream dependencies incorrectly displayed - Only for z/OS engines (71113)

When viewing a job stream with more than one job stream predecessor dependency in the What-if Analysis view, only one dependency might be visible. If you delete the dependency, both the visible dependency is deleted, as well as the dependency that is not showing in the view.

Text truncated following a copy and paste (71102)

When editing a job definition, if you copy and paste text into the fields, URL and REST URL, and the number of characters in the text exceed the maximum allowed, then the text actually copied to these fields is truncated and no warning is issued.

Software limitations related to Dashboard Application Services Hub (DASH)

[21563,999,000] SHIFT+TAB does not work properly in the header of the Monitor Workload panel

In the header of the Monitor Workload Panel, the navigation from a tab to another does not work with Shift+Tab.

Workaround: Do not use Shift+Tab but only Tab to move from a item to another.

The same panel opens multiple times in the same view (70823)

If you go to Submit predefined job streams to select a job stream, every time you enable or disable the check-box of specify date and time a new page Submit job stream into plan opens.

9.4 Fix Pack 2:

Query parameter transmitted in SSL Request (177529)

A request, sent over SSL, contains parameters that are transmitted in the Query part of an HTTP request. When sending requests, the browser's history can be used to reveal the URLs that contain the query parameter names and values.

z/OS® engine connection does not work after updating the port number (184418)

If you run the script updateZosEngine.sh in DWC_Instdir/wastools to update the port number of a z/OS engine connection and then install Fix Pack 2, the engine connection from the Dynamic Workload Console fails because the port number has reverted back to the original value before running the updateZosEngine.sh script.

Workaround: After the Fix Pack installation, run the updateZosEngine.sh script again and then restart the WebSphere Application Server.

Monitor job properties panel - change date (185006)

In Monitor job properties panel, if you enter a wrong date format for the start of a job (earliest start - latest start), the system automatically replaces the value specified with the date of the current day without any alert.

From the job stream graphical view with a z/OS engine connection, a job is deleted but remains in the view (185124)

When monitoring a job stream from the job stream graphical view, if you define a dependency between two jobs (in two different job streams) or between a job stream and a job (in a different job stream), and then try to delete the successor job, the job is not deleted from the view although the dependency has been removed.

REST API z/OS (185139, 185140)

Queries related to critical jobs and critical path do not work for the REST API in a z/OS environment.

Close selected job streams object does not work after displaying job stream run cycle preview (185169)

In Workload Designer, if you click on Run Cycle Preview tab, select the job stream object in the Workload Designer Working List and click on Close Selected button, the job stream object does not close.

Software limitations related to Dashboard Application Services Hub (DASH)

[DASH 67674] Cross-site request vulnerability (184233)

A defect has been opened against DASH (67674) to address the issue of cross-site request forgery.

[Dash 67677] Cached content can be accessed via HTTPS (184403)

Browsers might store a local cached copy of content received from web servers. Few internet browsers, including Internet Explorer, cache content accessed via HTTPS. If sensitive information in application responses is stored in the local cache, then this might be retrieved by other users who have access to the same system in a future time. A defect has been opened against Dash (67677).

9.4 Fix Pack 1:

After a fresh installation of the Dynamic Workload Console version 9.4.0 Fix Pack 1 with WebSphere® Application Server 8.5.5 FP 11, the administrator cannot view or use any of the portlets

After a fresh installation of the Dynamic Workload Console version 9.4.0 Fix Pack 1 with WebSphere Application Server 8.5.5 FP 11, the administrator cannot view or use any of the portlets. From the Dynamic Workload Console, he can just assign manually one of the following roles to the logged in users:

• TDWBAdministrator
• TWSWEBUIAdministrator
• Administrator
• chartAdministrator
• iscadmins
• samples

To prevent this problem, run the following procedure:

1. Install WebSphere Application Server 8.5.5 FP 11.
2. Apply WebSphere Application Server iFix 30449.999.744.8.5.5.10-WS-WAS-IFPI76481 available on IBM Fix Central.
3. Install Jazz™ for Service Management 1.1.3 CP2.
4. Install the Dynamic Workload Console version 9.4.0 Fix Pack 1.

The iFix enables Jazz for Service Management mapping between Dynamic Workload Console user roles and the administrator role.

If you install the iFix after installing the Dynamic Workload Console, you can manually map user roles and administrator role by running the following commands from the Dashboard Application Services Hub consolecli command line:

Run [JazzSM_Install_path]/ui/bin/tipcli.sh MapUsersToRole 
--username <TDWCadmin> 
--password <TDWCadminpassword> 
--roleName TWSWEBUIAdministrator 
--usersList 
uid=admin,o=defaultWIMFileBasedRealm
Run[JazzSM_Install_path]/ui/bin/tipcli.sh 
--username <TDWCadmin> 
--password <TDWCadminpassword>  
--roleName TDWBAdministrator 
--usersList 
uid=admin,o=defaultWI

Job streams graphically overlap in the graphical view (178184)

When loading job stream B in the graphical view, and job stream B has a dependency on job stream A, if job stream B contains a large number of objects, it might happen that opening job stream B it can graphically overlap job stream A.

Workaround: To workaround this problem, click the auto-layout button to rearrange the graphical view, or manually adjust job stream B layout in the view.

In the Job Stream View, a job stream with hundreds of objects (jobs and dependencies) might not be saved in PNG format (179497)

In the Job Stream View, trying to save a job stream with hundreds of objects (jobs and dependencies), the image might look corrupted and might not be possible to save it.

Workaround: To workaround this problem, save the job stream in SVG format and then use the appropriate tool to convert it from SVG to PNG format.

Disabling the plan mirroring on the engine and submitting a job stream into the current plan, the status of the internal jobs is not updated in the graphical view.

The limitation is due to the fact that, disabling the plan mirroring, the information stored in the database is not available. The same problem happens if the database is down.

For the steps needed to configure the Dynamic Workload Console to use all the authenticated portal user roles see Configuring roles to access the Dynamic Workload Console.

Read this section thoroughly before installing this Fix Pack.

Dynamic Workload Console version 9.4.0 Fix Pack 5 supports all product versions indicated in the Dynamic Workload Console version 9.4 Release Notes which can be accessed at the following link: https://workloadautomation.hcldoc.com/help/topic/com.hcl.wa.doc_9.4/distrDDguides.html.

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, see the hardware requirements at the following URL: https://workloadautomation.hcldoc.com/help/index.jsp?topic=%2Fcom.hcl.wa.doc_9.4%2FHCL_Workload_Automation_Supported_Hardware.htm.

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.