Release Notes for HCL Workload Automation, version 9.4

Release Notes

Abstract

This document supplies the release notes for HCL Workload Automation, version 9.4.

Content

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

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 the Product Documentation.

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

Interoperability tables
Top

The level of support provided for the products and components listed in the interoperability tables covers all the shown versions.

In the tables in this section the following acronyms are used:
DA HCL Workload Automation dynamic agent
DDM HCL Workload Automation dynamic domain manager or backup dynamic domain manager
DM HCL Workload Automation domain manager
DWC Dynamic Workload Console
FTA HCL Workload Automation fault-tolerant agent
MDM HCL Workload Automation master domain manager or backup master domain manager
TWS for z/OS Agent HCL Workload Automation for z/OS Agent

HCL Workload Automation: compatibility

 

MDM

DDM

DM

FTA

DA

TWS for z/OS Agent

TWS for Apps
MDM 9.4
 
9.4
9.4
9.4
9.4
 
 
DM 9.4
9.4
 
 
9.4
 
 
 
FTA 9.4
9.4
9.4
9.4
 
 
 
 
DA 9.4
9.4
9.4
9.4
 
 
 
 
DDM 9.4
9.4
 
 
9.4
9.4
 
 

Dynamic Workload Console: compatibility

 
MDM/DDM/DM/FTA
DWC 9.4
9.4

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

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.

Dynamic Workload Console V9.4 uses Restful protocol
Dynamic Workload Console V9.4 uses Restful protocol to connect to the server. The default port has changed from 31117 to 31116.

Installation limitations and problems, and their workarounds.
Top

The following are limitations and problems that might affect the installation or upgrade of HCL Workload Automation, and their workarounds (when available):


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.

Unexpected duplication of keys in localopts file after agent restore (167236).

After an agent update with the command:
twsinst -restore -uname twsuser -acceptlicense yes
the localopts contains some unexpected duplicated keywords.

Workaround

Delete the duplicated entries from the localopts file.

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.

Two defects have been opened to Jazz for Service Management development team (59346 and 59497).

Workaround

To circumvent the problem, install the following libraries:

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

Software limitations and problems, and their workarounds.
Top

The following are software limitations and problems that might affect HCL Workload Automation, and their workarounds (when available):

File monitor provider events: older event configurations might stay active on workstations after rule redeployment (34103).

If you deployed rules containing event types from the FileMonitor event provider, and then you redeploy rules that no longer include these file monitoring events, you might find that, despite the new configurations, the local monitoring agents still forward the file monitoring events to the event processor. The event processor correctly ignores these events, accordingly with the new configuration specifications deployed on the server; however, a certain amount of CPU time and bandwidth are needlessly misused.

The status of the local monitoring configuration on the agent is corrected when one of the following occurs:


Some data is not migrated when you migrate database from DB2® to Oracle, or to Informix® Dynamic Server, or vice versa (38017)

Neither of the two migration procedures migrate the following information from the source database:

"Absolute" keyword required to resolve time zones correctly with enLegacyStartOfDayEvaluation set (41192).

If the master domain manager of your network runs with the enLegacyStartOfDayEvaluation and enTimeZone options set to yes to convert the startOfDay time set on the master domain manager to the local time zone set on each workstation across the network, and you submit a job or job stream with the at keyword, you must also add the absolute keyword to make sure that the submission times are resolved correctly.

The absolute keyword specifies that the start date is based on the calendar day rather than on the production day.

File monitor provider events: if you specify a file path with forward slashes (/) in an event rule definition, on Windows workstations this results in the failed detection of the file (53843).

This is due to the fact the SSM agent is not currently designed to automatically convert the slash sign to be Windows compatible when running the rule.

Workaround

Use backward slashes when you specify file paths in the definitions of rules that run on Windows systems.

Problems when International Date Line West time zone is used (80881).

HCL Workload Automation is unable to manage the Date Line West time zone (UTC -12).


On Windows 2012: all cli not supported on Windows power shell (95772).

On Windows 2012, the HCL Workload Automation command lines are not supported in the Windows Power shell. They work only in the traditional shell.

File transfer job submitted on a Windows agent ends in error.

When endpoint protection software is active on a Windows agent workstation, the FTP connection is blocked by Java™. A Java technology bug reporting this issue can be accessed at http://bugs.java.com/bugdatabase/view_bug.do?bug_id=7077696.

The following are software limitations and problems that might affect the Plug-in for Informatica PowerCenter which is included in the HCL Workload Automation Version 9.4 installation:

Cannot submit Informatica PowerCenter jobs after a Web Services Hub restart

Following a restart of the Web Services Hub, the Plug-in for Informatica jobs launched from the command line end in FAIL state (Error state in the Dynamic Workload Console) and return the following exception in the job log: 

AWKIPC005E Failed to run workflow.
---------------------------------------
Remote Exception
----------------------------------------

To enable the correct submission of plug-in jobs, after restarting the Hub, connect to the Informatica PowerCenter Web Services Hub URL and follow these steps:

  1. In the Navigator pane, expand Web Service -> Batch WebService, and then click Integration WebService.
  2. In the Operations pane, click Try-It from the toolbar.
  3. In the Web Service Operations Navigator pane, click login.
  4. Fill out the form in the right pane, specifying the required information in the UserName, RepositoryName, and Password text fields.
  5. Click Send.
  6. In the SOAP Response pane, copy the value for the SessionId tag.
  7. In the Web Service Operations Navigator pane, click getWorkflowLog.
  8. Paste the value copied previously in the SessionId text field and then enter the required information in the FolderName, WorkflowName, Timeout, and ServiceName text fields.
  9. Click Send.

    You can now submit jobs safely again.

The problem is due to an Informatica Powercenter defect, for which change request 296859 is outstanding. A formal solution to the problem should be provided by the Informatica HotFix that will address this change request.

The following are software limitations and problems that might affect HCL Workload Automation access methods and plug-ins included in the HCL Workload Automation Version 9.4 installation:

Intercepted jobs cannot be relaunched in a z/OS environment (60698).

The process of defining relaunch criteria and collecting and relaunching intercepted jobs is supported only in distributed environments and not in z/OS environments.

A request to rerun a process chain is made from the Dynamic Workload Console, but the operation is set to start (61976).

Rerunning a process chain from the Dynamic Workload Console where the operation in IBM Workload Scheduler for z/OS is linked to a special resource that is not available results in the operation being set to start.

On AIX 6.1, batchman process does not correctly recognize the time zone of the local workstation (IZ70267)
On AIX 6.1, the batchman process does not correctly recognize the time zone of the local machine that is set to GMT, even if, in the HCL Workload Automation CPU definition, it is correctly set to the correct timezone. You see the following message in the stdlist log : "10:29:39 24.11.2015|BATCHMAN:AWSBHT126I Time in CPU TZ (America/Chicago): 2015/11/24 04:29 10:29:39 24.11.2015|BATCHMAN:AWSBHT127I Time in system TZ (America/Chicago): 2015/11/24 10:29 10:29:39 24.11.2015|BATCHMAN:+ 10:29:39 24.11.2015|BATCHMAN:+ AWSBHT128I Local time zone time differs from workstation time zone time by 360 minutes."

Batchman does not recognize the correct time zone because AIX 6.1 uses (International Components for Unicode) ICU libraries to manage the timezone of the system, and these ICU libraries are in conflict with the HCL Workload Automation libraries.

Workaround:

Export the TZ environment variable before starting HCL Workload Automation to the old POSIX format, for example, CST6CDT. This is an example of a POSIX name convention instead of an Olson name convention (for example America/Chicago). It avoids the new default TimeZone management through the ICU libraries in AIX 6.1, by switching to the old POSIX one (as in AIX 5.x).

APARS Fixed in this release

Documentation updates
Top

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


© Copyright HCL Technologies Limited 2016, 2018.