Dynamic Workload Console Version 10.2.0 Release Notes

Content

The Release Notes for the IBM Workload Scheduler Dynamic Workload Console version 10.2.0 contain the following topics:

• Interoperability tables
• Software limitations and their workarounds
• Documentation Updates
• APAR fixed in this release

Product publications

To download the appropriate package for your operating system, see the Dynamic Workload Console download page.

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

To access the IBM Workload Scheduler documentation, see the online IBM Documentation.

A complete list of new or changed functions in this release are documented in the Summary of enhancements. More information about new features, including helpful demo videos, can be found on the IBM Workload Automation What's New page. See also the V10.2.0 dedicated playlist on the Workload Automation YouTube channel.

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

Dynamic Workload Console version number

The Dynamic Workload Console version number is 10.2.0.0-2023.07. The convention of this new format is: <release_number>-<year><month>.
From now on, the Dynamic Workload Console will be released more frequently independent from the Fix Packs.

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:

Supported Browsers

To obtain the most up-to-date information about supported browsers and related versions, generate the Detailed System Requirements dynamic report from the Software Product Compatibility Reports web page, click the Prerequisites tab, and select Web Browsers.

The following tables are available:

• Dynamic Workload Console: compatibility
• IBM Workload Scheduler for z/OS: compatibility
• IBM Workload Scheduler Command-line client: compatibility

Dynamic Workload Console: compatibility

Compatibility is supported on the latest available fix pack for each release listed in the table:

Compatibility considerations with version 9.4 

When you have a backup master domain manager at the V10.2 version level, but the master domain manager is still at a previous product version level (version 9.4), problems can occur when monitoring objects that support the definition in a folder such as, prompts, workstations, and resources, as well as objects that contain the workstation in their object identifier, for example, job streams. More specifically, these objects are not displayed in the results of the monitoring query on the plan if you use filters in your query.

Solution: Upgrade the master domain manager to the V10.2 level, and then run planman resynch to resolve the issue.

IBM Workload Scheduler for z/OS: compatibility

Compatibility is supported on the latest available fix pack for each release listed in the table:

To find the fix packs released for IBM Workload Scheduler, and the Dynamic Workload Console including links to the related readmes files, see Fix Central.

Note: To connect the Dynamic Workload Console V10.1 Fix Pack 1 to IBM Z Workload Scheduler V9.3, you must first install the PTF PH52456 on IBM Z Workload Scheduler V9.3.

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

The File Transfer plug-in is unable to locate the destination path "\ALIAS"

The File Transfer plug-in is unable to validate the destination path: "\ALIAS", where "ALIAS" identifies a remote path defined via IIS on a Windows operating system.
During the job execution, the File Transfer plug-in validates the destination path provided in the job definition. These controls, involve the parent folder of the destination path. By using an ALIAS, the plug-in is unable to resolve the parent folder and all the controls fail.
Workaround: To avoid this issue there are two workarounds available:

1. Set the destination path by adding an additional folder after the \ALIAS: \ALIAS\test_folder\
2. Change the path pointed by the ALIAS. 
   For example, if it identifies a path like: \ALIAS = \\server\Folder1\Folder2\, this should be changed to: \ALIAS = \\server\Folder1\

In this way the destination path set in the job can change in \ALIAS\Folder2\ and the path validation works fine.

Table customization

The table customization in the user settings applies to the Monitor Workload page only. It does not affect the new Orchestration Monitor page.

Delete and Release option

In the Orchestration Monitor page, when you click on the option delete and release dependencies, an error occurs and the dependencies are not released. This is a limitation for jobs with success status.

Save query error

In the Orchestration Monitor, saving a query might throw an error. This is a limitation only for the engines using informix or OneDB.

List actions for API Keys are allowed without display access

A user with an empty security role (SECURITYROLE) and FILENODISPLAY ACL can see the API Keys of other users from Dynamic Workload Console.

Possible memory leak on the DB2 temporary table space

Intensive usage of the Orchestration Monitor might cause a memory leak on the default system temporary table space (TEMPSPACE1).

Workaround: Limit the space amount allocated for queries by changing the DB2 configuration.

IPv6 issue

When a user tries to create a engine connection with IPv6 hostname, the system throws a validation error as the new engine connection does not support IPv6 address as a hostname.

You cannot install the Dynamic Workload Console using a shell in which you previously ran the twa_env command.
 
 
This limitation is due to the twa_env command, which sets the data_dir variable to the data dir of the master domain manager.
If you need to install the master domain manager and Dynamic Workload Console on the same workstation, you can work around this limitation in one of the following ways:
 
- use the tws_env command instead of the twa_env command.
- specify the --data_dir parameter when running both serverinst and dwcinst commands, so that you can specify a different value for the data dir.
 
If you need to install the Dynamic Workload Console with the default values (without specifying the --data_dir parameter), using a shell from which you previously installed the master domain manager, ensure that the DATA_DIR variable is not set in the shell. To verify this, run the echo $DATA_DIR command.

Documentation Updates

Top

In the Planning and Installation manual, section Reference, add the following commands:

uninstall

Use this command to uninstall the File Proxy.

fileproxystop

Use this command to stop the File Proxy.

The unistall command syntax is as follows:

UNIX

./uninstall -inst_dir installation_directory [-lang language]

WINDOWS

uninstall.exe -inst_dir installation_directory [-lang language]

where

-inst_dir is the directory where the File Proxy is installed.

-lang is the language in which the messages returned by the command are displayed

The command removes all data related to the File Proxy and leaves the data_dir unchanged.

The fileproxystop command syntax is as follows:

UNIX

./fileproxystop

WINDOWS

fileproxystop.exe

In the Planning and Installation manual, section Reference, File Proxy installation - fileproxyinst script topic, note that the following parameters are required, even though they are documented as optional:

inst_dir
acceptlicense

All other updates to the IBM Workload Scheduler documentation that are required for version 10.2.0 are included in the editions of the publications at online IBM Documentation.

APARs fixed in this release Dynamic Workload Console V10.2.0:

• IJ29387: SRVE0190E FRENCH MENU FOR ZOS RESOURCES DEFINITIONS
• IJ33332: DWC 9.4 URL ALLOWS CODE INSERT FROM BROWSER
• IJ36331: DWC MEMORY LEAK IN ON-PREM SSO ENVIRONMENT
• IJ41417: CORRUPTED ENGINE NAME ON CUSTOM SQL REPORTING ISSUE
• IJ41705: DWC DASHBOARD DISPLAYS INCONSISTENT DATA IF MULTIPLE ZOS ENGINES ARE DEFINED BUT ONLY SOME OF THEM ARE USED IN THE DISPLAY
• IJ43500: DWC USER CAN NOT SELECT STATUS IN MONITOR WORKLOAD WHEN LANGUAGE SETTING IS TRADITIONAL CHINESE
• IJ43780: DWC 9.5.05 CHECK BOXES AND OPTION BUTTONS ARE MISSING DURING FILTER EDITING
• IJ44325: THE OUTPUT CONDITIONS OF JOB DEFINITIONS DISAPPEAR IN DWC
• IJ44369: DIFFERENT JOBS GET COMPARED WHEN OPEN MULTIPLE JOBS
• IJ44579: DATA CORRUPTION WHEN EDITING CUSTOM SQL REPORT QUERY
• IJ45637: USING DYNAMIC WORKLOAD CONSOLE 10.1.01 SUPPLYING LONG VALUES PASTED INTO "COMMAND" FIELD OF NATIVE JOB TYPES DO NOT WRAP IN THE BROWSER
• IJ46140: CLEARTEXT USER AND PASSWORD DATA TRANSMISSION VIA DWC URL POST METHOD
• IJ46407: UNABLE TO DELETE A REPORT WITH STRANGE CHARACTERS
• IJ46852: MANAGE WORKLOAD DEFINITIONS DISPLAYS AN ERROR AND DOES NOT OPEN
• KB0102848: Filtered workstations with timer is not working as expected
• KB0104369: Unable to create a widget using REST API datasource

Top

© Copyright International Business Machines Corporation 2006, 2016. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Copyright © 2016, 2023 HCL Technologies Limited.