Release Notes for HCL Dynamic Workload Console, version 9.4

Release Notes


This document supplies the release notes for HCL Dynamic Workload Console, version 9.4. It lists the latest information that could not be included in the product documentation, together with known product limitations and possible workarounds.


The Release Notes for HCL Workload Automation Dynamic Workload Console, version 9.4, contain the following topics:

Product publications

To download the appropriate package for your operating system, see HCL License Portal.

For detailed system requirements for all operating systems, see Detailed System Requirements.

To access the HCL Workload Automation documentation, see Product Documentation.

A complete list of new or changed functions in this release are documented in Summary of Enhancements.

You are strongly recommended to maintain all HCL Workload Automation components at the latest fix pack level.

Interoperability tables


Support at level of older product or component: For all products and components described in this section, the level of support is at that of the older product or component.

In the tables in this section the following acronyms are used:
BDDM HCL Workload Automation backup dynamic domain manager
BKM HCL Workload Automation backup master domain manager
DA Dynamic agent
DDM HCL Workload Automation dynamic domain manager
DM HCL Workload Automation domain manager
FP Fix pack
FTA HCL Workload Automation fault-tolerant agent
MDM HCL Workload Automation master domain manager
SDK Eclipse-based Integration Workbench
TDWB HCL Dynamic Workload Broker
TDWC Dynamic Workload Console
TWS HCL Workload Automation
TWS for Apps HCL Workload Automation for Applications
TWS for z/OS Agent HCL Workload Automation for z/OS Agent
z/OS Conn HCL Workload Automation z/OS® connector feature
z/OS Controller HCL Workload Automation for z/OS Controller

Supported Browsers

To obtain the most up-to-date information about supported browsers and related versions, see the Detailed System Requirements page.

The following tables are available:

Dynamic Workload Console: compatibility

DWC 9.4

HCL Dynamic Workload Console Command-line client: compatibility



Command-line client, version 9.4

* The V9.4 command-line client is automatically installed when you install a fault-tolerant agent. A command-line .zip file is also provided if you want to install it as a standalone component.

Fix packs released for this version of the product

To find the fix packs released for HCL Workload Automation and the Dynamic Workload Console, including links to the related readmes files, see HCL License Portal.

Information you must know before installing.


Consider the following information before installing HCL Workload Automation V9.4:

For HCL Workload Automation V9.4, default settings for role-based security model are as follows:

Master domain manager V9.4 fresh install
For master domain manager V9.4 fresh install, the role-based security model is enabled by default (enRoleBasedSecurityFileCreation optman global option is set to yes).

Master domain manager parallel upgrade to V9.4
For the fresh install of a new master domain manager V9.4 configured as backup, the role-based security model is disabled by default (enRoleBasedSecurityFileCreation optman global option is set to no).

For details about the enRoleBasedSecurityFileCreation optman global option, see the Product Documentation.

Software limitations and their workarounds


This section contains product limitations not resolved with this release of the Dynamic Workload Console, and their workarounds (where applicable):

Communication problems with the engine when using IPv6
If you are using Dynamic Workload Console in environments where you are using the IPv6 protocol or in mixed environments where both the IPv4 and IPv6 protocols are in use, you might experience connection problems.

Workaround: To fix this problem set a configuration parameter in the application server, as follows:

  1. Open the following file for editing: $TWA_HOME/eWAS/profiles/jazzsm_profile/config/cells/jazzsm_cell_name/ nodes/jazzsm_node_name/servers/server1/server.xml
  2. Locate the variables: and
  3. Set the variables as follows:
    Pure IPv6 environment
    Pure IPv4 environment
    Mixed IPv4 and IPv6 environments
  4. Stop and restart the application server, using the commands stopappserver and startappserver

Incorrect selection of jobs in manage browsed workstations panel
In the panel to manage browsed workstations, when you select Jobs from the More Actions menu, the displayed list shows all the jobs belonging to job streams defined on the selected workstation, and not just the jobs running on it.

Stop of application server hangs
The command that stops the embedded WebSphere Application Server hosting Dynamic Workload Console might hang or end due to a timeout. This can occur randomly after several days of activity. It might be necessary to stop the server manually. The server process ID to stop is stored in the following file: $TWA_HOME/eWAS/profiles/jazzsm_profile/logs/ffdc/

Bookmarked tasks may not work using Internet Explorer
If you have tasks bookmarked with Dynamic Workload Console "Add to bookmark" feature, this might not work with the new Dynamic Workload Console version. You can use another browser to use the feature.

What if: update screen help "Show Job" (128426)
In the contextual online help for the General Filter for Jobs panel, the name of the field "Exclude complete" should read "Exclude completed (z/OS only) and Until first completed (distributed only)"

Launching a portlet results in error message: "This portlet page is not ready. Please try again.".
When launching a portlet, such as clicking the Manage Engine link from the single entry point page from the Dynamic Workload Console, or when launching the Dynamic Monitoring Query portlet from Application Lab, the portlet does not respond immediately and returns the error message: "This portlet page is not ready. Please try again." Repeating the request several times eventually produces the portlet and its contents correctly.

Dynamic Workload Console workload dashboard unable to establish a connection with the master domain manager
Unexpected security exception in Dynamic Workload Console SystemOut.log due to security exception after a trusted login

Adding a new dependency from the Monitor Workload entry the search does not work correctly if there is more than one job stream with the same name
When trying to add dependencies to a job or a job stream from the Monitor Workload entry, if the job stream selected in the search panel has the same name as another job stream, the search reports all jobs related to all job streams with the same name.

Jazz for Service Management Dashboard Application Services Hub (DASH) in high availability mode becomes unresponsive during workload execution with hundreds of users accessing the database simultaneously
When multiple threads access the database to retrieve the data, it makes the system become unresponsive. This is a known DASH problem and a workaround to resolving the problem is documented in the technote Jazz for Service Management DASH hub in HA mode becomes unresponsive during workload execution with more than 300 users accessing the database simultaneously.

Dynamic Workload Console installation fails on Windows 10 (166339)
Dynamic Workload Console installation fails on Windows 10 if JazzSm is installed in a virtual directory (i.e. C:\Program Files). A pop up appears asking for the credential, to circumvent the problem, insert the JazzSm credentials or install both Dynamic Workload Console and JazzSm in a non-virtual directory.

Application Lab limitation by using Internet Explorer (156948)
If both Application Lab and Workload Designer panels are opened and you take action in the Application Lab (i.e. enhance your workload), the objects shown in the panels could not be the same, if you are using Internet Explorer.

Production and forecast plan reports do not work by using REST API (168178)
Dynamic Workload Console v9.4 uses REST API protocol, but production and forecast plan reports do not work with this protocol. To circumvent the problem, run reports by using reportcli command. The fix will be available in a short period of time and the link to download the fix will be provided.

The import Workload Application Template panel is not shown when there is only one engine (168208)
The workaround is to define another engine or duplicate the same engine with a different name.


Tivoli Common Reporting

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


Before you install the Reporting Services package, ensure you run IBM Prerequisite Scanner. IBM Prerequisite Scanner is a stand-alone prerequisite checking tool that analyzes system environments before the installation or upgrade of an HCL product. For more information, see the section about running the Prerequisite Scanner manually in the Jazz for Service Management documentation. For detailed information on Tivoli Common Reporting available within the Dynamic Workload Console, see the Product Documentation.

All updates to the HCL Workload Automation documentation that are required for version 9.4 are included in the Product Documentation.

Installation limitations problems and their workarounds

APARs fixed in this release

APARs fixed in this release Dynamic Workload Console V9.4:

© Copyright HCL Technologies Limited 2016, 2018.