Release Notes
Abstract
This document lists the latest information that could not be included in the product documentation together with known product limitations and possible workarounds.
Content
The Release Notes for the IBM Workload Scheduler Dynamic Workload Console version 9.3 contain the following topics:
- Interoperability tables
- Fix packs
- Software limitations and their workarounds
- Tivoli Common Reporting
- Installation and upgrade limitations and their workarounds
- Graphical views limitations and their workarounds
- Event management limitations and their workarounds
- Reporting limitations and their workarounds
- Globalization Notes
- 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 Knowledge Center.
You are strongly recommended to maintain all IBM Workload Scheduler components at the latest fix pack level.
Notes:IBM Tivoli Workload Scheduler for Applications and IBM Tivoli Workload Scheduler Plug-in for Informatica PowerCenter are no longer separate installable components. All of the access methods and plug-ins formerly packaged with IBM Tivoli Workload Scheduler for Applications V8.6 and IBM Tivoli Workload Scheduler Plug-in for Informatica PowerCenter V8.6 are now automatically included in the IBM Workload Scheduler Version 9.3 installation.
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 | IBM Workload Scheduler backup dynamic domain manager |
BKM | IBM Workload Scheduler backup master domain manager |
DA | Dynamic agent |
DDM | IBM Workload Scheduler dynamic domain manager |
DM | IBM Workload Scheduler domain manager |
FP | Fix pack |
FTA | IBM Workload Scheduler fault-tolerant agent |
MDM | IBM Workload Scheduler master domain manager |
SDK | Eclipse-based Integration Workbench |
TDWB | IBM Dynamic Workload Broker |
TDWC | Dynamic Workload Console |
IWS | IBM Workload Scheduler |
IWS for Apps | IBM Workload Scheduler for Applications |
IWS distr Agent for z/OS | IBM Workload Scheduler distributed - Agent for z/OS |
z/OS Conn | IBM Workload Scheduler z/OS® connector feature |
z/OS Controller | IBM Workload Scheduler for z/OS Controller |
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
MDM/DDM/DM/FTA
|
MDM/DM/FTA
|
||
DWC 9.3 |
9.3, 9.2, 9.1, 8.6
|
8.5.1
|
|
|
IBM Workload Scheduler for z/OS: compatibility
Dynamic Workload Console
|
z/OS connector
|
TWS for z/OS
|
DWC 9.3 |
9.3 |
9.3
9.2 9.1 8.6 8.5.1 |
- Notes:
- The z/OS connector version must be the same as the Dynamic Workload Console version. When you install Dynamic Workload Console V9.3, the z/OS connector is also automatically installed.
- The IBM Workload Scheduler for z/OS version must be equal to or earlier than the Dynamic Workload Console version.
IBM Dynamic Workload Console Command-line client: compatibility
MDM |
||||
Command-line client, version 9.3 |
9.3*
|
|||
Command-line client, version 9.2 |
9.2*
|
|||
Command-line client, version 9.1 |
9.1*
|
|||
* The V9.3, V9.2 and V9.1 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 IBM Workload Scheduler, and the Dynamic Workload Console including links to the related readmes files, see Fix Central.
Software limitations and their workarounds |
This section contains product limitations not resolved with this release of Dynamic Workload Console, and their workarounds (where applicable):
- Error while opening the TCR administrator panel after a successful installation of the Dynamic Workload Console (131760).
After a successful installation of the Dynamic Workload Console and its prerequisites, trying to open the TCR administrator panel, the following error message is displayed:
Error!
Refresh Edit Minimize Maximize
PF-VAL-6171 Error retrieving metadata for the target fragment.
Details | Retry | Hide this message.
Details
DashboardException
PF-VAL-6171 Error retrieving metadata for the target fragment.A defect has been opened to Jazz for Service Management development team (59497).
Workaround
To circumvent the problem, rename or remove the following jar file:
BirtAdapterB.jar presente in questo path:/reporting/lib/birt-runtime-2_2_2/ReportEngine/lib - Jazz for Service Management fresh installation might take a long time to complete (131495).
-
Depending on your hardware configuration, the fresh installation of Jazz for Service Management - one of the DWC prerequisites - might take from 2 to 4 hours to complete. It might appear to be hanging during the step Updating IBM Dashboard Application Services Hub Service, but it is just a step that takes a long time to complete.
A defect has been opened to Jazz for Service Management development team (59464).
This defect is fixed in IBM Workload Scheduler version 9.3, Fix Pack 1.
- Tivoli Common Reporting Installation fails on Linux for missing prerequisites (130480).
-
For Linux operating system, Tivoli Common Reporting installation fails for missing prerequisites. The error message is the following:
CRIMA1217E: A problem occurred during the execution of the /opt/IBM/JazzSM/install/reporting_services/tcrWrapperInstall.xml file. - After using Common Reporting the DWC icons do not work (111553)
- Carry out the following steps to reproduce:
- Install TCR
- From the DWC click Reporting Reporting > Common Reporting. The IBM Cognos Connection interface is displayed
- Close the Cognos interface >
Workaround: Refer to the following technote for more information: http://www-01.ibm.com/support/docview.wss?uid=swg21660616This defect is fixed in IBM Workload Scheduler, version 9.3 Fix Pack 1.
-
- 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:
- 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
- Locate the variables:
java.net.preferIPv4Addresses
andjava.net.preferIPv6Addresses
- Set the variables as follows:
- Pure IPv6 environment
java.net.preferIPv4Addresses=false
java.net.preferIPv6Addresses=true
- Pure IPv4 environment
java.net.preferIPv4Addresses=true
java.net.preferIPv6Addresses=false
- Mixed IPv4 and IPv6 environments
java.net.preferIPv4Addresses=false
java.net.preferIPv6Addresses=false
- Stop and restart the application server, using the commands stopappserver
and startappserver
- Open the following file for editing:
Job stream editing limitations with IBM Workload Scheduler for z/OS- In Dynamic Workload Console for z/OS there is no job stream editor available to manage jobs within the job stream in a plan. As a consequence, on z/OS, there is no Submit and Edit option available within the Predefined Job Stream action.
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.
Special character validation problems with IBM Workload Scheduler for z/OS- In z/OS environments, during task creation or editing, a few special characters might not be validated by Dynamic Workload Console. As a consequence, an error might occur on the z/OS connector causing the result table of the task to be empty. This happens when the code page of the z/OS engine is not the same as the code page of the z/OS connector client. Invalid characters are those that map the hexadecimal values 0x7B, 0x5B, 0x7C in all supported EBCDIC code pages (for example #, $, @ for IBM-37 EBCDIC codepage).
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/dwc_server_name.pid
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)
Occasionally batchman wrongly counts the number of succ jobs in case of every jobs and after a restart. (IV64818)
This defect is fixed in IBM Workload Scheduler version 9.3, Fix Pack 1.
For Unix operating system, during the upgrade from V9.1 or
V9.2 to V9.3, if there are files or directories in the path Inst_Dir/TWS/ITA/cpa/temp/ipc
, these files or directories are not copied into the backup directory and the upgrade fails.
Workaround
To circumvent the problem, before upgrading to V9.3, perform the following steps:- Stop all processes.
- Check if there are files or directories in the path
Inst_Dir/TWS/ITA/cpa/temp/ipc
and, if any, remove them. - Perform the upgrade to V9.3.
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 IBM 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 Tivoli Common Reporting Reports
Installation and upgrade limitations, problems, and their workarounds |
The following are limitations that affect the installation and upgrade of the Dynamic Workload Console:
- Problems connecting to back-level engines
- Dynamic Workload Console V9.3 cannot connect to previous versions of IBM Workload Scheduler engines. For more information see Technote: How Connect TDWC 9.3 to TWS Engine 8.6 or 9.x.
Graphical views limitations and their workarounds |
The following are software limitations that affect the graphical views of Dynamic Workload Console on all operating systems:
Workload Designer does not open
- IBM Workload Scheduler for z/OS version 8.5 and z/OS Connector version
8.5.0
-status information about dependency links and condition nodes is not available. As a consequence, the "Show/Hide Dependency Status" button is not available.
-dependency links originating from the same predecessor job and pointing to the same condition node are collapsed into a single dependency link.
-"Delete" action is not available on dependency links poining to a condition node.
-rule information is not available on condition nodes. - IBM Workload Scheduler for z/OS version 8.5 and z/OS Connector version
8.5.1
-status information about dependency links, other than condition dependencies, is not available. As a consequence, the "Show/Hide Dependency Status" button is not available.
Globalization notes |
This section describes software limitations, problems, and workarounds for international versions of Dynamic Workload Console.
- Some simplified Chinese characters are missing or corrupted when using Google Chrome or Apple iPad Safari browser
When you access the Self-Service Catalog or Self-Service Dashboard form a mobile device that uses the Google Chrome or Apple iPad Safari borwser, if you use the GB18030 Simplified Chinese character set, the characters that you type might be missing or corrupted.
Cause: Google Chrome and Apple iPad Safari do not fully support GB18030 Simplified Chinese.
Solution: Ensure that you are using a browser that supports GB18030 Simplified Chinese character set. - The Dynamic Workload Console installation fails if you specify a
user name for the WebSphere Application Server that contains Arabic characters.
(43052)
Documentation Updates |
All updates to the IBM Workload Scheduler documentation that are required for version 9.3 are included in the editions of the publications at the IBM Knowledge Center.
APARs fixed in this release |
APARs fixed in this release Dynamic Workload Console V9.3 includes APARs fixed in V9.2, plus the following:
- IV56113: SUBMITTING 2ND JOBSTREAM FROM SAME DISPLAY AFTER SUBMITTING THE 1ST JOBSTREAM WILL CAUSE RESUBMISSION OF THE 1ST JOBSTREAM NAME
- IV61550: HOLD ACTION IS GRAY OUT AND CANNOT PERFORM "HOLD" FOR JOBS ON TWS 9.1.0 FP0001/TDWC 9.1.0 FP0001 ENVIRONMENT
- IV65189: SATURDAY OR SUNDAY AS NON-WORKING DAY CHECK BOX DOES NOT WORK
- IV62662: COMPLEX VARIANT ARE NOT DISPLAY BY TDWC
- IV71729: ISSUES WITH VARIANTS' QUOTES BEING DROPPED FROM DEFINITIONS SAVED THROUGH TDWC
- IV69186: AFTER APPLY OF Z/OS PTF UI16455 THE TDWC GETS AN DIALOG ERROR WHEN VIEWING SAP JOBS THROUGH TDWC
- IV36472: CLASSCASTEXCEPTION WTEXTCOMPONENT INCOMPATIBLE WITH WCHECKBOXLIST
- IV38108: TDWC SAP JOB LISTING SORTED BY DATE DISCOUNTING YEAR
- IV43461: REMOTE SERVER NAME IS AVAILABLE FOR DISTRIBUTED SYSTEMS
- IV43882:WHEN QUERYING JOBSTREAMS WITH THE TDWC, SAME JOBSTREAMS ARE DISPLAYED MULTIPLE TIMES IF YOU SELECT ALL STATUSES.
- IV43883:JOBSTREAM DATE IS NOT STORED CORRECTLY
- IV44824: JOBS RUN AT WRONG TIME ON DAY DST SHIFT BACK IN SYDNEY
- IV45156: TDWC EWAS SYSTEMOUT. LOG GETS SERIES OF [DASHBOARD] MESSAGES REPEATING EVERY FEW SECONDS
- Porting of IV46431
- IV49674: CUSTOM SQL REPORT ERRORS IN DWC 9.1
- IV49985: AFTER UPGRADE TO FP2 - CAN NO LONGER ACCESS "JOB RUN HISTORY"
- IV51978: SCREEN COVERS ALL THE MONITOR
- IV51982: PAGEMGR THREADS IN TDWC WAIT WITHOUT TIMEOUT
- IV52907: TDWC INTERPRETS DEFAULT CALENDAR HOLIDAYS AS WORKDAYS
Original Publication Date
29 May 2015
Was this topic helpful?
Document Information
Modified date:
29 September 2018
UID
swg27045183