HCL Workload Automation version 10.2.2 Release Notes

This document provides important information about HCL Workload Automation version 10.2.2.

The most up-to-date version of this document can be accessed at the following URL: Product Requirements. This page also contains a series of links to important product requirements documentation.

It is divided into the following main sections:

Features introduced with version 10.2.2

HCL Workload Automation version 10.2.2 includes the following enhancements:

Helpful videos demonstrating new features on https://www.youtube.com/user/workloadautomation2.

Important information for version 10.2.2

FIPS compliance is not supported in the current product version. This is because OpenSSL 3.0 libraries do not provide a FIPS-compliant validation algorithm for P12 certificates. Development is in progress with the aim of supporting FIPS in upcoming releases. For more information, see Summary of enhancements.

Important information for version 10.2.3

Red Hat Enterprise Linux (RHEL) 7 is going out of support in June 2024. As a result, it will no longer be supported in HCL Workload Automation version 10.2.3.

APARs and defects fixed in version 10.2.2

This section lists APARs resolved in version 10.2.2.

Table 1. APARs addressed in version 10.2.2
APAR NUMBER DESCRIPTION
IJ41345 RECOVERY OPTION RERUN NOT WORKING AS EXPECTED
IJ43756 ACTUAL DURATION WHICH SHOULD SHOW UP IN HH.MM.SS SHOWS INSTEAD A WHOLE NUMBER VALUE
IJ44428 PREDEFINED JOB RUN HISTORY REPORT COLUMN HEADERISSUE
IJ46180 CENTRALIZED UPDATE DOWNLOAD FAILS FROM 9.5 FP6 WHEN ENEVENTPROCESSORHTTPSPROTOCOL IS SET TO NO
IJ46641 SUCCESSFUL REMOTE COMMANDS REPORT AS FAILURE AFTER UPGRADE FROM 9.5 FP5 TO 9.5 FP6
IJ46647 TWS TIMEZONE UPDATE ON 10.2.2
IJ47035 SERVERINST: WAINST216E --WAPASSWORD CONTAINS INCORRECT CHARACTERS (EQUAL SIGN '=')
IJ47037 JOB DEPENDENCY MISSING POST DST CHANGE
IJ47731 CHECKSYNC JOB FAILED IN IWS 10.1 FP02 - AWSJCL075E ERRORS
IJ47970 THE AGENT UPGRADE CAUSING MULTIPLE WORKSTATIONS GOING UNLINKED DURING UPGRADE FROM 9.4 TO 10.1
IJ48889 APPLICATION SERVER CRASHES AND THEN SOMETIMES AUTO RESTARTS ITSELF AND SOMETIMES IT DOES NOT
IJ48900 CERTIFICATE ISSUE WHILE SCALING UP KUBERNETES ENVIRONMENT
IJ49033 HCL Workload Automation FILE WATCHING DOES NOT WORK FOR FILES LARGER THAN 2GB.
IJ49105 ISSUE IN HOLDING THE JOBS USING CONMAN
IJ49106 SWITCHMGR DDM TO BDDM DOESNT WORK CORRECTLY AT 9.5 FP6 SEC FIX FIXES (SECURITY-202212 +TS013441722_95FP6SEC_IJ45754 NOV)
IJ49118 DWCINST.VBS AND SERVERINST.VBS ASSUMES SQLSERVER AUTHENTICATIONMODE
IJ49416 COMPOSER HANG ISSUE-QUERYING FOR MORE THAN 1000 DATABASE OBJECTS
IJ49417 WILDCARD OPENS DEPENDENCY FAILS WHEN GOING THROUGH UNIXLOCL METHOD
IJ49484 JOBS THAT COMPLETE IN LESS THAN ONE MINUTE ARE NOT REPORTED IN CONMAN CLI, DWC, AND JOBRUNHISTORY REPORT
IJ49545 THERE IS A TRANSLATION OF "EXCLUSIVE" WAS CHANGED
IJ49559 REPORTCLI COMMAND ABENDS WITH UNSUPPORTEDDATATYPEEXCEPTION
IJ49622 HEARTBEATS ARE NOT BEING UPDATED WHILE GENERATING NEW PLAN DUE TO THE DATABASE BEING LOCKED BY PLANNER PROCESS
IJ49695 MULTIPLE JOIN WITH DEPENDENCIES LOADED INCORRECTLY DURING FINAL EXECUTION
IJ49716 DOCUMENTATION - CONFIGURING FOR A DB2 DATABASE IN HADR
IJ49784 EVENT ACTION FOR EMAIL PLUG-IN FAILED TO SEND EMAIL AND COMPLETED WITH ERRORS: NULL
IJ49807 THE DOCUMENTATION IS AMBIGUOUS ABOUT THE ADMINISTRATOR ROLE REQUIRED BY THE IWA INSTANCE OWNER USER, TWSUSER
IJ49866 VULNERABILITY IN KUBECTL (PRISMA-2022-0227)
IJ49928 IT SHOULD BE INCLUDED IN THE DOCUMENTATION TO AVOID SPECIAL CHAR ACTERS FOR DBUSER PASSWORD
IJ49958 MULTIPLE VULNERABILITIES IN JAVA (CVE-2023-21930, CVE-2023-21967, CVE-2023-21954, CVE-2023-21939, CVE-2023-21968, CVE-2023-21937)
IJ49993 USER CREATED HOLIDAYS CALENDAR OVERRIDES DEFAULT ONE REGARDLESS IF LOCATED UNDER ROOT FOLDER OR ANY OTHER FOLDERS
IJ49994 BKM INITIATING EVENT PROCESSOR MANAGER EVEN WHILE IN UNLINKED STATUS
IJ50022 UPGRADE ISSUE FROM 10.2.0 TO 10.2.1 REGARDING THE ENHANCEMENT OF THE CERTIFICATE
IJ50366 BATCHMAN ON BACKUP MDM NOT STOPPING DURING SOME SWITCHMGR OPERATIONS
IJ50462 INCONSISTENCY WITH THE DOCUMENTATION FOR GLOBAL OPTIONS PARAMETER ENROLEBASEDSECURITYFILECREATION / RS
IJ50462 INCONSISTENCY WITH THE DOCUMENTATION FOR GLOBAL OPTIONS PARAMETER ENROLEBASEDSECURITYFILECREATION / RS
IJ50570 NEED TO UPDATE THE STEP 1. TO INCLUDE PATH FOR 9.X MDM SYSTEM
IJ50573 INCORRECT STEPS WRITTEN ON THE LONG-TERM SWITCH
IJ50578 TYPO IN ./CONFIGUREDB.SH SCRIPT UNDER THIS DOCUMENTATION CREATING THE DATABASE FOR ORACLE FOR THE DYNAMIC WORKLOAD CONSOLE
IJ50640 DOCUMENTATION FOR DATAIMPORT COMMAND HAS MISLEADING USAGE AND EXAMPLE
IJ50643 INCONSISTENCIES WITH INSTALLATION DOCUMENTATION FOR MDM AND DWC
IJ50765 GETTING AWSBIA389E AND AWSITA399E WHEN RUNNING COMPOSER COMMANDS
KB0095077 REST API Issues with Member with a # character in name does not work
KB0104364 - IJ47383 Liberty Stale connection issue showing SLQ exception in messages.log
KB0108566 Supported Software - PeopleSoft Version
KB0110408 HWA helm install enableSingleInstaceNetwork: true fails

Resolved Common Vulnerabilities and Exposures (CVE)

The following CVEs have been resolved:
  1. CVE-2012-5783
  2. CVE-2022-48468
  3. CVE-2022-48564
  4. CVE-2023-21930
  5. CVE-2023-21937
  6. CVE-2023-21939
  7. CVE-2023-21954
  8. CVE-2023-21967
  9. CVE-2023-21968
  10. CVE-2023-27043
  11. CVE-2023-40217
  12. CVE-2023-43804
  13. CVE-2023-45286
  14. CVE-2023-45803
  15. CVE-2023-48795
  16. CVE-2023-51775
  17. CVE-2023-5363
  18. CVE-2024-1023
  19. CVE-2024-24786
  20. CVE-2024-25710
  21. CVE-2024-26308
  22. CVE-2024-2700
  23. CVE-2024-29025
  24. CVE-2024-29025
  25. PRISMA-2022-0227
  26. WS-2014-0065

Interoperability tables

In the tables in this section the following acronyms are used:
Table 2. Acronym table
Acronym Extended form
DA Dynamic agent
DDM dynamic domain manager or backup dynamic domain manager
DM domain manager
DWC Dynamic Workload Console
FTA fault-tolerant agent
MDM master domain manager
ZWS agent HCL Workload Automation agent for z/OS
Compatibility is supported on the latest available release level for each HCL Workload Automation release listed in the table.

On AIX systems, ensure the system library XL C++ Runtime, version 16.1.0.7 or later, is installed.

Table 3. Compatibility table for HCL Workload Automation
Component MDM DDM DM FTA DA ZWS agent
MDM 10.2.2 10.2.1, 10.2, 10.1, 9.5, 9.4 10.2.1,10.2, 10.1, 9.5, 9.4 10.2.1,10.2, 10.1, 9.5, 9.4** 10.2.1,10.2, 10.1, 9.5, 9.4 9.4
DM 10.2.2 10.2.1,10.2, 10.1, 9.5, 9.4 10.2.1,10.2, 10.1, 9.5, 9.4**
FTA 10.2.2 10.2.1,10.2, 10.1, 9.5, 9.4* 10.2.1,10.2, 10.1, 9.5, 9.4 10.2.1,10.2, 10.1, 9.5, 9.4
DA 10.2.2 10.2.1,10.2, 10.1, 9.5, 9.4 10.2.1,10.2, 10.1, 9.5, 9.4 10.2.1,10.2, 10.1, 9.5, 9.4
DDM 10.2.2 10.2.1,10.2, 10.1, 9.5, 9.4 10.2.1,10.2, 10.1, 9.5, 9.4** 10.2.1,10.2, 10.1, 9.5, 9.4

*The composer command line of the agent at version 10.2.2 works correctly with master domain managers at version 9.5 and later.

**Compatibility on v9.4 Limited fault-tolerant agents for IBM i is not supported.

Table 4. Compatibility table for Dynamic Workload Console
Component MDM DDM
DWC 10.2.2 10.2.1, 10.2, 10.1, 9.5 FP2 and later, 9.4 10.2.1, 10.2, 10.1, 9.5 FP2 and later
Table 5. Compatibility table for AIDA
Component MDM DDM DWC
AIDA 10.2.2 10.2.1, 10.2, 10.1 10.2.1, 10.2, 10.1 10.2.1, 10.2, 10.1
Compatibility scenarios and limitations

You are strongly recommended to maintain all HCL Workload Automation components at the latest version level as regular maintenance activity. Keeping your environment consistent also ensures you can implement the new features available with each release.

Known limitations and workarounds

The following are software limitations and workarounds that affect HCL Workload Automation 10.2.2:
Mixed-version environment with a master domain manager at a version earlier than 9.5 FP4
Before you install a component at version 10.2.2 in an environment with a master domain manager at a version earlier than 9.5 FP4, install the fix for IJ47731 on the back-level master domain manager. To obtain the fix for your product version, contact Software Support.
Rest API submit job stream not possible with time restriction filters
Submitting a job stream with restful API is not possible when using time restriction filters.
Workaround
The Rest API is POST /plan/{planId}/jobstream/{jobstreamId}/action/submit_jobstream with the jobstreamId as NONE value, the planId where the job stream has to be submitted and the body with the SubmitJobStreamInfo as following:
{
"inputArrivalTime": "2023-07-04018:01:29.371Z",
"alias": "JSALIAS",
"jobstream":
{ *RESPONSE_OF_MAKEJOBSTREAM* }
}
To avoid inserting manually all jobs definitions, use the response of the Rest API POST /plan/{planId}/jobstream/{jobstreamId}/action/make_jobstream that requires the jobstreamId, the planId and the following body:
{ "inputArrivalTime": "2023-07-04T08:01:29.371Z", "alias": "JSALIAS" }
The response of the make_jobstream Rest API can be used as a job stream field in the submit_jobstream API body. Before calling the Rest API it is necessary to replace all the occurrences of timeRestriction with the correct ones and whatever you need to change for the submission.
Pool workstation details defined on the dynamic domain manager are not visible after switching the dynamic domain manager to backup dynamic domain manager
When you install a dynamic domain manager and then switch it to backup dynamic domain manager, the operation seems to be successful if you check the environment from the command line, but in the dynamic domain manager database some fields in the PPS_PRODUCT_PROPERTIES table are not correctly updated and still refer to the workstation which was previously the dynamic domain manager. An error similar to the following is returned:
AWSJOM177E An error occurred getting the definition of the workstation 
"<POOL_NAME>". The workload broker server is currently unreachable.
Workaround
To work around the problem, perform the following steps:
  1. Retrieve the domain ID by running a query similar to the following:
    select hex(CAST(DOM_ID as VARCHAR(100))) 
as DOM_ID,DOM_NAME from MDL.DOM_DOMAINS  order by DOM_NAME
  2. Check that the domain ID is correct.
  3. Correct the following fields in the table:
    DomainManager.Workstation.Name
    This is the workstation name of the new dynamic domain manager. Verify the current value is the expected one. You can obtain this value using the conman command line or from the MDL.WKS_WORKSTATIONS table on the master domain manager.
    MasterDomainManager.HostName
    This is the full qualified host name or the IP of the new master domain manager. Verify the current value is the expected one. You can obtain this value using the conman command line or from the MDL.WKS_WORKSTATIONS table on the master domain manager.
    MasterDomainManager.Name
    This is the workstation name of the new master domain manager. Verify the current value is the expected one. You can obtain this value using the conman command line or from the MDL.WKS_WORKSTATIONS table on the master domain manager.
    MasterDomainManager.URIs
    This is the list of the master domain managers to be contacted by the dynamic domain manager The list must contain in the first position the new master domain manager and in second position the new backup master domain manager
    DomainManager.Workstation.Address
    This is the full qualified host name or the IP of the new dynamic domain manager.
Event-driven Workload Automation: the event is not triggered if the login value contains a domain
Domain names are not supported in login values.
Workaround
To work around this problem, use a wild card in place of the user domain name, as shown in the following example:

<attributeFilter name="Login" operator="eq">
               <value>*ITAuser</value>
</attributeFilter>
Resource CLI on agents not configured correctly
The resource CLI on agents might occasionally work erratically because of a problem in updating the configuration file.
Workaround
On the master domain manager, copy the CLIConfig.properties file from the TWA_DATA_DIR/broker/config folder to the TWA_DATA_DIR/TDWB_CLI/config folder.
Installing or linking a fault-tolerant agent earlier than 10.2 in an environment configured with new default or new custom certificates
If you install or link a fault-tolerant agent earlier than V10.2 to an environment with a master domain manager at version 10.2.1 or later using new custom or new default certificates, you need to manually install the certificates on the fault-tolerant agent. To perform the manual installation, you can follow the steps below:
  1. Shut down the workstation of the fault-tolerant agent
  2. Create a backup of the localopt file
  3. Create a new folder under the target fault-tolerant agent as in the following example: <TWS_DATA_DIR>/<new_cert_folder>
  4. From the master domain manager, copy the files under TWA_DATA_DIR/ssl/depot
  5. Paste the TWA_DATA_DIR/ssl/depot files from the master domain manager into the <TWS_DATA_DIR>/<new_cert_folder> new directory
  6. Update the localopts file of the fault-tolerant agent by changing the values of the following properties:
      • SSL Key: <TWS_DATA_DIR>/<new_cert_folder>/tls.key
      • SSL Certificate: <TWS_DATA_DIR>/<new_cert_folder>/tls.crt
      • SSL key pwd: <TWS_DATA_DIR>/<new_cert_folder>/tls.sth
      • SSL CA certificate: <TWS_DATA_DIR>/<new_cert_folder>/ca.crt
  7. Turn on the workstation of the fault-tolerant agent.
The centralized update on a fault-tolerant agent V10.2.1 is not supported
The centralized update on a fault-tolerant agent V10.2.1 is not supported, regardless of the operating system.

Package structure

For a detailed list of available packages, see the HWA_10.2.2_QuickStartGuide.zip document available from Flexnet or from HCL Software.

Installing and upgrading to version 10.2.2

This section describes how to install or upgrade to version 10.2.2 to HCL Workload Automation.

Installation notes
  • Before installing the release, ensure you have installed the required prerequisite software. To obtain the latest information about software requirements, see Product Requirements.
  • If you are upgrading to the current version from versions earlier than or equal to 9.5FP3, you have to upgrade first to 10.2 GA.
  • If you are upgrading to the current version from versions later than or equal to 9.5FP4, you can perform the upgrade as usual.
  • The formal test phase was performed using WebSphere Application Server Liberty 24.0.0.3.
    Note: Version 24.0.0.3 does not support installation paths containing spaces, for example C:\Program Files. If you installed any HCL Workload Automation components in a path containing spaces, do not upgrade WebSphere Application Server Liberty to version 24.0.0.3. You can continue using HCL Workload Automation with earlier versions.
    The minimum required WebSphere Application Server Liberty version to successfully install the package is 23.0.0.9.
  • On UNIX™ operating systems, the database administrator must have read and run privileges for the HCL Workload Automation installation path. If this is not the case, the installation fails. (54367)
After the installation completes, verify the following information:
  • This release installs a new version of the file tws_env.sh (tws_env.cmd) and also creates a backup file named, tws_env.sh.bk (tws_env.cmd.bk), which are both saved to the TWA_HOME/TWS directory, where TWA_HOME is the HCL Workload Automation installation directory. After completing the installation, if you have modified the original version, merge the content of the new version with the content of the customized version to carry your customized content into the new version.
  • When merging the two versions as described above, ensure you do not modify the paths to OpenSSL libraries.
  • Only on Windows™ operating systems, to correctly display double-byte character set (DBCS) characters, perform the following actions:
    • Set the LANG environment variable to the DBCS language code you want to use, for example, set LANG=zh_CN.
    • Set the TWS_TISDIR environment variable to the HCL Workload Automation home directory, for example, set TWS_TISDIR=C:\FTA\TWS.
    • Open the Control Panel window and click Clock, Language, and Region.
    • Click Region and Language.
    • In the Format tab, choose from the Format drop-down list the language you want to use.
    • In the Keyboards and Languages tab, under Display Language, click install and follow the steps to install the DBCS language pack you want to use.
    • In the Administrative tab, click Change system locale and, from the drop-down list, choose the language (system locale) you want to use.
    Note that all the settings must be consistent, that is they must refer to the same DBCS language setting. After you have completed these changes, reboot your workstation to have the changes take effect.
  • When installing a dynamic agent or a fault-tolerant agent, ensure that the agent name does not start with a number. If the name of the dynamic agent starts with a number, use the -displayname parameter at installation time to specify a different name. If the name of the fault-tolerant agent starts with a number, use the --thiscpu parameter at installation time to specify a different name.

Installation and upgrade procedures

You can install the release using the procedure described in Installing from the CLI.

You can upgrade to the current release using the procedure described in Upgrading from the CLI.

If upgrading from a version earlier than 10.x on which you are using default certificates in your environment, convert the certificates before you start the upgrade, as described in Converting default certificates.

If your environment consists of components at various version levels, see Upgrading in a mixed-version environment when using default certificates.

If you plan to install on or upgrade an HCL Workload Automation component on a workstation running RHEL 9 or later with default certificates, see Installation or upgrade fails on RHEL version 9 and later.

If you are performing a parallel upgrade from version 9.4, ensure you set the Broker.Workstation.PortSSL property to false in the BrokerWorkstation.properties file, as described in Ensuring communication in your environment.

Disk space requirements

For the most up-to-date information about disk space and memory requirements, see Hardware Requirements Report.

Performing the centralized agent update

Before performing a centralized update on fix packs or upgrade on releases on a stand-alone fault-tolerant agent to V10.2.2, there are procedures to follow according to the version of the fault-tolerant agent from which you want to upgrade.
Note: When upgrading a dynamic agent together with a fault-tolerant agent to V10.2.2, if you start the upgrade from the dynamic agent there are no further steps required. The same applies when performing an upgrade of the fault-tolerant agent starting from a dynamic agent.
The table below shows which procedure you must follow to perform the upgrade, according to the fault-tolerant agent version.
Table 6. Steps required before performing the centralized agent update on a stand-alone fault-tolerant agent
Stand-alone fault-tolerant agent version Required steps
V9.5 Fix Pack 4 up to V9.5 Fix Pack 6 If not already enabled, enable the use of the HTTPS protocol to connect to the event processor server. For more information about enabling enEventProcessorHttpsProtocol | eh, see Global options - detailed description
V9.5 Fix Pack 7 No steps required.
V10.1 up to V10.1 Fix Pack 3 If not already enabled, enable the use of the HTTPS protocol to connect to the event processor server. For more information about enabling enEventProcessorHttpsProtocol | eh, see Global options - detailed description.

Then, from the same workstation where the fault-tolerant agent

is installed, copy the TWSClientKeyStore files from TWA_DATA_DIR/ssl/GSKit to TWA_DATA_DIR/ITA/cpa/ita/cert.
Note: The owner of the new TWSClientKeyStore files and the permissions granted must be the same of the existing files.
V10.1 Fix Pack 4 If not already enabled, enable the use of the HTTPS protocol to connect to the event processor server. For more information about enabling enEventProcessorHttpsProtocol | eh, see Global options - detailed description.
Then, download the curl file from Defect Article KB0112633 and save it inside TWS/ITA/cpa/ita.
Note: The owner of the new curl file and the permissions granted must be the same of the existing curl file.
V10.2 If not already enabled, enable the use of the HTTPS protocol to connect to the event processor server. For more information about enabling enEventProcessorHttpsProtocol | eh, see Global options - detailed description.
Then, download the curl file from Defect Article KB0112633 and save it inside TWS/ITA/cpa/ita.
Note: The owner of the new curl file and the permissions granted must be the same of the existing curl file.
V10.2.1 Not supported.

Documentation updates

Any additions or changes to the documentation as a result of this release have been integrated into the online product documentation available in HCL Workload Automation product information.

Contacting HCL Workload Automation Software Support

Refer to the HCL Workload Automation Support page: Software Support.

Notices

This information was developed for products and services offered in the US. This material might be available from HCL Workload Automation in other languages. However, you may be required to own a copy of the product or product version in that language in order to access it.

HCL Workload Automation may not offer the products, services, or features discussed in this document in other countries. Consult your local HCL Workload Automation representative for information on the products and services currently available in your area. Any reference to an HCL Workload Automation product, program, or service is not intended to state or imply that only that HCL Workload Automation product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any HCL Workload Automation intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-HCL Workload Automation product, program, or service.

HCL Workload Automation may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

HCL
330 Potrero Ave.
Sunnyvale, CA 94085
USA
Attention: Office of the General Counsel

For license inquiries regarding double-byte character set (DBCS) information, contact the HCL Workload Automation Intellectual Property Department in your country or send inquiries, in writing, to:

HCL
330 Potrero Ave.
Sunnyvale, CA 94085
USA
Attention: Office of the General Counsel

HCL TECHNOLOGIES LTD. PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. HCL Workload Automation may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-HCL Workload Automation websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this HCL Workload Automation product and use of those websites is at your own risk.

HCL Workload Automation may use or distribute any of the information you provide in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

HCL
330 Potrero Ave.
Sunnyvale, CA 94085
USA
Attention: Office of the General Counsel

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by HCL Workload Automation under terms of the HCL Workload Automation Customer Agreement, HCL Workload Automation International Program License Agreement or any equivalent agreement between us.

The performance data discussed herein is presented as derived under specific operating conditions. Actual results may vary.

Information concerning non-HCL Workload Automation products was obtained from the suppliers of those products, their published announcements or other publicly available sources. HCL Workload Automation has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-HCL Workload Automation products. Questions on the capabilities of non-HCL Workload Automation products should be addressed to the suppliers of those products.

This information is for planning purposes only. The information herein is subject to change before the products described become available.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to actual people or business enterprises is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to HCL Workload Automation, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. HCL Workload Automation, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. HCL Workload Automation shall not be liable for any damages arising out of your use of the sample programs.

© IBM Workload Scheduler 2006, 2016. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.


© Copyright HCL Technologies Limited 2016, 2024.
Portions of this code are derived from HCL Workload Automation Sample Programs.

Trademarks

HCL, and other HCL graphics, logos, and service names including "hcltech.com" are trademarks of HCL. Except as specifically permitted herein, these Trademarks may not be used without the prior written permission from HCL. All other trademarks not owned by HCL that appear on this website are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by HCL.

Adobe™, the Adobe™ logo, PostScript™, and the PostScript™ logo are either registered trademarks or trademarks of Adobe™ Systems Incorporated in the United States, and/or other countries.

IT Infrastructure Library™ is a Registered Trade Mark of AXELOS Limited.

Linear Tape-Open™, LTO™, the LTO™ Logo, Ultrium™, and the Ultrium™ logo are trademarks of HP, IBM® Corp. and Quantum in the U.S. and other countries.

Intel™, Intel™ logo, Intel Inside™, Intel Inside™ logo, Intel Centrino™, Intel Centrino™ logo, Celeron™, Intel Xeon™, Intel SpeedStep™, Itanium™, and Pentium™ are trademarks or registered trademarks of Intel™ Corporation or its subsidiaries in the United States and other countries.

Linux™ is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft™, Windows™, Windows NT™, and the Windows™ logo are trademarks of Microsoft™ Corporation in the United States, other countries, or both.


Java Logo
 Java™ and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.

Cell Broadband Engine™ is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom.

ITIL™ is a Registered Trade Mark of AXELOS Limited.

UNIX™ is a registered trademark of The Open Group in the United States and other countries.

Terms and conditions for product documentation
Permissions for the use of these publications are granted subject to the following terms and conditions.
Applicability
These terms and conditions are in addition to any terms of use for the HCL Workload Automation website.
Personal use
You may reproduce these publications for your personal, noncommercial use provided that all proprietary notices are preserved. You may not distribute, display or make derivative work of these publications, or any portion thereof, without the express consent of HCL Workload Automation.
Commercial use
You may reproduce, distribute and display these publications solely within your enterprise provided that all proprietary notices are preserved. You may not make derivative works of these publications, or reproduce, distribute or display these publications or any portion thereof outside your enterprise, without the express consent of HCL Workload Automation.
Rights

Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either express or implied, to the publications or any information, data, software or other intellectual property contained therein.

HCL Workload Automation reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of the publications is detrimental to its interest or, as determined by HCL Workload Automation, the above instructions are not being properly followed.

You may not download, export or re-export this information except in full compliance with all applicable laws and regulations, including all United States export laws and regulations.

HCL Workload Automation MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.