HCL Workload Automation 10.1 Fix Pack 1 Readme File

Date: December 2, 2022

Fix Pack Name: 10.1.0-HCL-IWS-FP0001
Product: HCL Workload Automation version 10.1.0
General Description: HCL Workload Automation Fix Pack 1 for version 10.1.0
Product versions and components to which the Fix Pack applies: This Fix Pack can be applied only on top of HCL Workload Automation V10.1.0, and subsequent Fix Packs.

This readme file provides important information about Fix Pack 1 for HCL Workload Automation version 10.1.0

The most up-to-date version of this readme can be accessed at the following URL: Fix Pack readmes.

HCL Workload Automation version 10.1.0 Fix Pack 1 supports all product versions indicated in the Release Notes for HCL Workload Automation.

It is divided into the following sections:

Features introduced with Fix Pack 1

Changed features and feature capabilities

Satisfying Requests for Enhancements (RFEs)

Resolved Common Vulnerabilities and Exposures (CVE)

APARs and defects fixed in Fix Pack 1

Known limitations and workarounds

Fix pack structure

Installing the Fix Pack

Documentation updates

Contacting HCL Software Support

Notices

Features introduced with Fix Pack 1

The following features have been introduced with Fix Pack 1:

Changed features and feature capabilities

The following features have changed or have been introduced or removed since the General Availability version:

REST APIs documentation automatically integrated into the product documentation: Information about REST APIs is automatically extracted from the code and integrated into the documentation at HCL Workload Automation API for easier reading and increased retrievability.

File Proxies now selected randomly in the Managed File Transfer integration: By default, the integration uses the File Proxy specified by the dynamic domain manager. You can also optionally define a list of preferred File Proxies to be used instead of the default list.; The File Proxy is selected randomly in the list provided by the dynamic domain manager. If you provided a custom list, the random selection is performed only on your list.; The random selection mechanism ensures higher tolerance for peaks in workload and workstation failures. For more information, see File Transfer Integration on Automation Hub.

Default storing mechanism of job log changed: When you perform a fresh installation, by default the job log is stored in memory instead of being stored in a file, as in the previous releases. This ensures compliance with the PCI standard. For more information, see the section about log files and archived files in Administration Guide.

Enhanced security with the conn_verify property: You can now optionally set the conn_verify property to 1 or 2, so that the agent must provide valid certificates in order to establish an SSL connection. The default value is 0, which means that no verification is performed on certificates.

Hostname verification for File Proxy: You can now optionally enable a check on the hostname defined for the certificates used by File Proxy. To enable the verification, create the Java system property named wa.fileproxy.enforceSSLhostnameVerify and set it to true.

Hostname verification for the mail sender plug-in: You can now optionally define the MAILPLUGIN_ENABLE_HOST_VERIFICATION property in the TWSConfig.properties file to enable the verification of the hostname of the SMTP server. If you set the property to yes, hostname verification is enabled, if you set it to no, no verification is performed. The default value for fresh installations is yes.

Higher security for job integrations

The Verify host name check box is selected by default in some integrations. Starting from version 10.1 Fix Pack 1, to increase the security standard provided by the product, this selection starts a check on the data contained in the keystore file. Ensure you provide the correct path and credentials to the keystore file in the Certificates section for the following integrations:

JSR 352 Java Batch
Restful
Job Management
Job Stream Submission
Variable Table

If the information in the Credentials section is not correct, this causes the job to fail with an error similar to the following:

AWKJMJ041E An error occurred during the Job submission. 
The error was "AWKSPI006E Keystore authentication failed. The error message is 
"No certificates provided, cannot verify the hostname."

If your integrations fail after upgrading to Fix Pack 1, you have the following options:

deselect the Verify host name check box.
provide the correct path and credentials to the keystore file.

Supported WebSphere Application Server Liberty Base versions: HCL Workload Automation Version 10.1 Fix Pack 1 was formally tested by using WebSphere Application Server Liberty Base 22.0.0.10 and 22.0.0.11. The minimum required WebSphere Liberty version to successfully install the fixpack is 22.0.0.3 or later.

Satisfying Requests for Enhancements (RFEs)

RFEs give customers the opportunity to collaborate directly with the product development team and other users. The team prioritizes and develops new product features based on proposals made by customers. HCL Workload Automation V10.1 Fix Pack 1 delivers the following RFEs:

RFE 149367 - Installation of dynamic agents on Windows operating systems using Local System Account: You can now install dynamic agents on Windows operating systems without providing a specific user. This means that you no longer need to provide twsuser credentials to the operator performing the installation. Moreover, the password no longer expires, ensuring a smooth running of your jobs. For more information, see the section about agent installation parameters in HCL Workload Automation: Planning and Installation.
RFE 69917 - Interactive jobs supported on dynamic agents installed on Windows operating systems: You can now determine the behavior of native and executable jobs starting interactive programs on dynamic agents installed on Windows operating systems. Interactive programs run only if the job user has an active session open when the job runs. If there is no active session for the job user, the job behavior is defined by the new RunInteractiveJobOnInvalidSession property in the JobManager.ini file. You can set the property to true to enable jobs to start interactive programs even if there is no active session for the job user. Alternatively, set the property to false to prevent jobs from starting interactive programs if there is no active session for the job user. This feature was already available for fault-tolerant agents and is now also available by default for dynamic agents. For more information about enabling and disabling this feature, see the section about configuring properties of the native job launcher [NativeJobLauncher] in Administration Guide.; For example, consider a job which consists of both interactive instructions (for example, using a text editor), and batch instructions, which run in background when the job is launched. If you set the RunInteractiveJobOnInvalidSession property to true, batch instructions can run even if the interactive part is not displayed because the user does not have an active session at the moment.
RFE 60060 - dynamic agents to track the workload on the local system: This capability is now available using the Orchestration CLI, as described in the section in this readme about Orchestration CLI.

To submit a new RFE, write us here: HWAinfo@hcl.com

Resolved Common Vulnerabilities and Exposures (CVE)

The following CVEs have been resolved:

CVE-2020-36518
CVE-2022-42003
CVE-2022-42004
CVE-2022-36033
CVE-2022-27664
CVE-2022-32149
CVE-2022-3171

APARs and defects fixed in Fix Pack 1

This section lists APARs and internal defects resolved by Fix Pack 1.

Table 1. APARs addressed in Fix Pack 1
APAR	ABSTRACT
IJ40204	REPORT SHARING IS NOT PROVIDING A COMPLETE LIST OF AD GROUPS
IJ35581	MAIL SENT BY EVENT RULE, JAPANESE MAIL BODY IS GARBLED
IJ39387	JOBSTREAM SUBMITTING TWICE IN THE PLAN
IJ36425	EVENT 128 IS PRODUCED IN EVENTS.LOG WHEN WAS IS RESTARTED FOR FIRST TIME FOR ALREADY COMPLETED JOBS WITH CRITICAL AND DEADLINE PARAMETER
IJ40756	PSP CREATION FAILED USING THE SAMPLE YAML "CUSTOM PODSECURITYPOLICY DEFINITION"
IJ40130	DEPENDENCY INCONSISTENCY FOR JOBSTREAMS
IJ39156	MFT - ISSUE CONNECTING TO REMOTE SERVER VIA KEYSTORE THAT NO NEED PASSWORD
IJ38859	JOB PRIORITY IS AUTOMATICALLY CHANGED TO ZERO (0) AFTER JNEXTPLAN
IJ40389	SECURITY FILE WITH A " ' " (SINGLE QUOTE) VIA MAKESEC <TEXT FILE> DOES NOT REPORT AN ERROR
IJ32304	FORECAST PLAN PROBLEM IN JOBSTREAM RUN CYCLE GROUP
IJ37881	JLOG ARBITRARY FILE CREATION
IJ40795	SEGMENTATION FAULT AFTER OPERATOR COMMAND
IJ38340	CUSTOMER HAS APPLIED FP05 TO IWS9.5 FP03 ON AIX. THEY RAN THE COMPOSER COMMANDS AND IT STARTED A NEW LINE AT PORT NUMBER LINE
IJ39558	CONMAN SJ ON A SPECIFIC JOB ENDS WITH A SEGMENTATION FAULT
IJ40702	COLLECTOR.SH IS FILLING THE FILE SYSTEM ASSOCIATED WITH THE IWSDATA DIRECTORY
IJ38854	AWKJDB801E AN INTERNAL ERROR ACCESS DB. THE INTERNAL ERROR IS: EXCEPTION OCCURRED DURING BIGDECIMAL CONVERSION
IJ36453	DYNAMIC AGENT (JOBMANAGER PROCESS) NOT ABLE TO HANDLE SPECIAL CHARACTERS
IJ40826	EVENTRULE ACTION SENDMAIL GETTING FAILED WITH "IOEXCEPTION ON IWS 10.1.0.00
IJ38346	JOBMANAGER PROCESS AUTO-RESTART EVERY FEW SECONDS
IJ42056	SOMETIMES JOBS SUBMITTED WITH A SUBMIT JOB OPERATION (SBJ) REMAINS IN ADD STATE
IJ38758	9.5 MDM CRASHES WITH JAVACORE DUE TO SYM_CLOSE FUNCTION WHEN WORKLOAD IS TRIED TO BE RETRIEVED
IJ37269	IJ30299 NOT WORKING ON 9.5 FP5
IJ40326	WAT NULL POINTER EXCEPTION UPDATING A JS
KB0100213	SUPPORT BOOLEAN DATATYPE FOR STORED PROCEDURE PARAMETER
IJ40991	AXWAY ST JOBS GO IN ABEND
IJ40992	UNABLE TO USE PREDEFINED USER ID AND PASSWORD IN AXWAY PLUGIN
IJ42370	SUPPORT FOR IWS 10.1 + MSSQL SERVER 2019 EE
IJ38960	UPDATE OPENSSL
IJ36545	MAGENT PROCESS UNABLE TO READ EVENTS WRITTEN TO MAGENT.P
IJ42365	IWS 10.1 WINDOWS CLUSTER ENABLER MICROSOFT@ VISUAL C++ 2005 PREREQUISITE PACKAGE IS OBSOLETE
IJ41494	MODIFY THE INFORMATION ABOUT ON-PREMISE FTA CONNECT TO ON-CLOUD MDM
IJ34871	TWS9.5 FP0004 JOB ABEND WITH ERROR */SCRIPT.SH: CANNOT EXECUTE [TEXT FILE BUSY]
IJ42173	JNEXTPLAN -FOR EXTENSION IS NOT CONSIDERED FOR NEXT FINAL RUN
IJ25454	NETMAN SERVICE NAME NOT UPDATED ON SECONDARY SERVER IN A WINDOWS CLUSTER AFTER UPGRADE
IJ39134	MFT RECEIVE JOB ISSUE IN THE ABSOLUTE PATH RESOLUTION USING A "LOCAL USER" DIFFERENT BY TWS USER
IJ39955	SLOWNESS IN CONMAN COMMANDS RELATED TO JOBS WHEN STREAM NAME MENTIONED AS "@" IN MASTER
IJ42213	IWS 10.1 NEW INSTALL FAILS WHEN USING USE_ENCRYPTION=FALSE
IJ36977	CONMAN CAUSES HIGH CPU UTILIZATION WHEN THE PARENT PROCESS IS KILLED
IJ41676	DELAY IN "CONMAN SJ" REPLY WHEN THE SCHEDTIME IS ADDED TO THE QUERY
IJ37364	JDBC POOL EXHAUSTION BECAUSE CONNECTIONS ARE NOT RELEASED
IJ39468	WORKLOAD AUTOMATION OPERATOR V1.5.14
IJ41305	TWS 10.1 GA BROKER SSL HANG
IJ40775	EVENT RULES DEFINED IN FOLDERS ARE NOT CAPTURED BY DATAGATHER SCRIPT COMING WITH PRODUCT IN VERSION 9.5: TWS_INST_PULL_INFO.SH
IJ39712	REGULAR EXPRESSIONS DO NOT WORK IN REPORT'S FILTERS CRITERIA WITH 10.1 VERSION
IJ38164	IWS AGENT UNLINK WHEN A VERY LONG DOMAINNAME RETURN FROM CITSCAN.UNABLE_TO_CREATE_ENTITY LOGGED AT MDM
IJ41353	10.1 GA AND 9.5 JOB SUBMISSION COULD BE DELAYED ON DA
IJ38201	LICENSE TYPE OF EXTENDED AGENT <X-AGENT> IS DIFFERENT FROM HOST WORKSTATION <FTA>
IJ42383	QUESTION FOR ARTICLE OF 'PER JOB LICENSE MODEL'
IJ13994	WINDOWS FILE DEPENDENCY THAT INCLUDES TWO BACKSLASHES DOES NOT GET RESOLVED
IJ20203	CONMAN DISPLAYING A CORRUPTED USER NAME AFTER A JOB HAS LAUNCHED AND COMPLETED
IJ31864	ON ZCENTRIC JOBLOG IS DELETED AT THE MAXAGE EVEN IF THE JOB IS STILL RUNNING
IJ41671	NUMBEROFROWS JOB PROPERTY HAS BEEN REPLACED WITH THE "ROWSNUMBER" JOB PROPERTY IN DATABASE JOB EXECUTOR PLUGIN WITH 9.5 FP6
IJ41352	10.1 GW RANDOMLY DOWN NOT ABLE TO AUTOMATICALLY RESTART ITSELF.JOBS SUBMISSION FAILURE ON THE AGENTS.ISSUE ON 9.5 GW ALSO
IJ39471	IF UNIQUENAME IS NULL? IT FAILS TO LIST THE PERSONALIZEDREPORT
IJ41483	START_TWS.SH AND STOP_TWS.SH SCRIPTS CORRECTIONS NEEDED
IJ42255	AUDIT JUSTIFICATION IS NOT LOGGED IN THE FILE
IJ43774	ABSOLUTE KEYWORD NO LONGER WORKS IN 9.4 OR 9.5
IJ42478	AFTER INSTALLING FP6, DATABASE PLUGIN IS NOT ABLE TO RUN MSSQL STORED PROCEDURES ANYMORE
IJ41037	THE JOBSTREAM END TIME REFLECTED IN THE CONSOLE IS DIFFERENT FROM ITS ACTUAL END TIME BASED ON THE LOGS
IJ39791	SEVERAL DYNAMIC JOBS REMAIN IN INTRO STATUS WHEN SUBMITTED DURING A DB FAILOVER, SWITCHMGR OPERATION OF LIBERTY RESTART
IJ41361	DOC APAR: REVISION OF DOCUMENTS REGARDING JVMOPTIONS ON JOBMANAGER.INI
KB0099406	CANNOT KILL A SAP JOB DEFINED ON A WINDOWS DA
IJ43687	INSTALLING THE MDM WITH SELF-SIGN CERTS
KB0100860	HWA FILE TRANSFERRECEIVE "INVALID CROSS-DEVICE LINK" WHEN DOING A MOVE FILE AFTER TRANSFER
IJ44002	USE OF THE "AGENTID" COMMAND LINE PARAMETER USED WITH THE "TWSINST" AGENT INSTALLATION SCRIPT REQUIRES A CHARACTER LIMITATION.
IJ44023	CVE-2022-27664: golang
IJ44021	CVE-2022-32149: golang
IJ44027	CVE-2022-36033: jsoup-1.14.2
IJ44025	CVE-2022-3171: protobuf-java

Known limitations and workarounds

The following are software limitations and workarounds that affect HCL Workload Automation version 10.1.0 Fix Pack 1.

WebSphere Liberty minimum required version

the minimum required WebSphere Liberty version to successfully install the fixpack is 22.0.0.3.

IBM Common Inventory Technology scanner ceases HP support

IBM Common Inventory Technology scanner does not support HP operating systems starting from January 1st 2023. The HCL Workload Automation dynamic agent utilizes IBM Common Invetory Technology to collect system configuration data used in the definiton of dynamic pools. For customers using dynamic agents on HP and dynamic pools, we strongly recommend to review dynamic pool workstation definitions. If their requirements are based on filesystems, especially network or remote filesystems, we strongly recommend to remove the HP dynamic agent from the dynamic pool, since management of the requirements may not be accurate.

APAR IJ39106

When installing using the keystore and truststore files, customers are required to manually configure these files prior the installation setup. If providing custom .jks files, it is the customers responsibility to provide such .jks files equipped with all the CA certificates they need in the truststore. For more information see Installing the master domain manager and backup master domain manager.

Agent Installation and Custom Certs on Upgraded MDM

If you plan to install a dynamic agent which uses custom certificates and connect it to a master domain manager which uses custom certificates and has been updated to version 10.1 FP1, you need to add the public part of the default certificates into the master domain manager truststore. This ensures communication between agent and master.

To import the public part of the default certificates, perform the following steps on the master domain manager:

On the agent, list the labels within the KDB certificate:

"gsk8capicmd_64 -cert -list -db TWSClientKeyStore.kdb"

An output similar to the following is returned:

"Certificates found
- default, -personal, ! trusted, # secret key"
! server
- client
The public label is preceded by the "-" sign. In our example, the public label is "client".
On the agent, optionally, check the details for the "client" label, as follows:

"gsk8capicmd_64 -cert -list -db TWSClientKeyStore.kdb -label client"
On the agent, extract the "client" label to a file of your choice, as follows:

"gsk8capicmd_64 -cert -extract db TWSClienKeystore.kdb -label client -target my_file.cer"
On the master domain manager, import the file to the Liberty truststore JKS of the master domain manager using the keytool command, as follows:

"keytool -importcert -file my_file.cer -keystore <TWA_HOME>/usr/servers/engineServer/resources/security/TWSServerTrustFile.jks -alias my_certs -trustcacerts"
On the master domain manager, type yes when requested to trust the imported certificate.

You have now successfully imported the public part of the default certificates into the master domain manager truststore.

APAR IJ46851 - The centralized update fails

The centralized update performed on a fault-tolerant agent, without the dynamic agent installed, fails due to the incorrect SSL certificates folder.

Workaround:Copy the TWSClientKeyStore files in the following folder and run the centralize update again:

Windows: From <TWA_home>\TWS\ssl\GSKit to <TWA_home>\TWS\ITA\cpa\ita\cert\
Unix: From <TWA_DATA_DIR>/ssl/GSKit to <TWA_DATA_DIR>/ITA/cpa/ita/cert/

Fix pack structure

This section describes the structure of the images contained in this Fix pack.

Fix Pack files available for HCL Workload Automation by using HCL License Portal

Following is the structure of the Fix Pack on Flexnet:

Readme file and WebSphere Liberty package
AIX components
IBMi components
Linux components
Linux components on Docker
Windows components
z/OS Components
Mac components
DB2 components

Table 2. **Readme file and WebSphere Liberty package**
Name	Description
HWA_10.1.0.1_ReadmeFirst	Readme file with download instructions
WEBSPHERE_LIBERTY_BASE 22.0.0.11	WebSphere Liberty application server

Table 3. AIX components
Name	Description
HWA_10.1.0.1_AIX_AGENT_2022.11	HCL Workload Automation Agent V10.1.0.1 for AIX

Table 4. IBM i components
Name	Description
HWA_10.1.0.1_IBM_I_AGENT_2022.11	HCL Workload Automation Agent V10.1.0.1 for IBM i

Table 5. Linux components
Name	Description
HCL Workload Automation 10.1.0.1 LINUX	LINUX distribution
HWA_10.1.0.1_MDM_LINUX_X86_64_2022.11	Workload Automation V10.1.0.1 FOR LINUX
HWA_10.1.0.1_OCLI_LINUX_X86_64_2022.11	Orchestration CLI (OCLI) V10.1.0.1 for Linux X86-64
HWA_10.1.0.1_LNX_PPC64LE_AGENT _2022.11	HCL Workload Automation Agent V10.1.0.1 for Linux on POWER
HWA_10.1.0.1_LINUX_X86_64_BatchReportCli_2022.11	Batch Report CLI V10.1.0.1 for Linux X86-64
HWA_10.1.0.1_LNX_S390_AGENT_2022.11	HCL Workload Automation Agent V10.1.0.1 for IBM Z
HWA_10.1.0.1_LNX_X86_64_AGENT_2022.11	Workload Automation Agent V10.1.0.1 for Linux on x86-64
HWA_10.1.0.1_FILE_PROXY_LINUX_X86_64_2022.11	File Proxy V10.1.0.1 for Linux X86-64

Table 6. Linux components on Docker
Name	Description
HCL Workload Automation 10.1.0.1 LINUX	LINUX distribution
HWA_10.1.0.1_DOCKER_MDM_LINUX_X86_64_2022.11	Workload Automation V10.1.0.1 for LINUX on Docker
HWA_10.1.0.1_DOCKER_Agent_LINUX_X86_64_2022.11	Agent V10.1.0.1 for Linux on x86-64 on Docker
HWA_10.1.0.1_DOCKER_Agent_LINUX_S390_2022.11	Agent V10.1.0.1 for Linux on IBM Z on Docker
HWA_10.1.0.1_DOCKER_FILE_PROXY_LINUX_S390_2022.11	File Proxy V10.1.0.1 for Linux on IBM Z on Docker
HWA_10.1.0.1_DOCKER_FILE_PROXY_LINUX_X86_64_2022.11	File Proxy V10.1.0.1 for Linux X86-64 on Docker
HWA_10.1.0.1_DOCKER_AIDA_LINUX_S390_2022.11	AIDA V10.1.0.1 for Linux on IBM Z on Docker
HWA_10.1.0.1_DOCKER_AIDA_LINUX_X86_64_2022.11	AIDA V10.1.0.1 for Linux X86-64 on Docker

Table 7. Windows™ components
Name	Description
HCL Workload Automation 10.1.0.1 WINDOWS	WINDOWS distribution
HWA_10.1.0.1_MDM_WINDOWS_X86_64_2022.11	Workload Automation V10.1.0.1 for WINDOWS
HWA_10.1.0.1_WINDOWS_X86_64_BatchReportCli_2022.11	HCL Workload Automation V10.1.0.1 Batch Reports Command Lines
HWA_10.1.0.1_WIN_X86_64_AGENT_2022.11	HCL Workload Automation Agent V10.1.0.1 for Windows x64
HWA_10.1.0.1_OCLI_WINDOWS_X86_64_2022.11	Orchestration CLI (OCLI) V10.1.0.1 for Windows X86-64
HWA_10.1.0.1_FILE_PROXY_WINDOWS_X86_64_2022.11	File Proxy V10.1.0.1 for Windows X86-64

Table 8. ™z/OS Components
Name	Description
HCL Workload Automation V10.1.0.1 z/OS	z/OS distribution
HWA_10.1.0.1_ZSYSTEM_BatchReportCli_2022.11	Batch Report CLI V10.1.0.1 for Z System

Table 9. **Mac components**
Name	Description
HWA_10.1.0.1_OCLI_MAC_2022.11	Orchestration CLI (OCLI) V10.1.0.1 for MAC
HWA_10.1.0.1_OCLI_MAC_X86_64_2022.11	Orchestration CLI (OCLI) V10.1.0.1 for MAC ARM
HWA_10.1.0.1_OCLI_MAC_ARM_64_2022.11	Orchestration CLI (OCLI) V10.1.0.1 for MAC x86

Table 10. **DB2 components**
Name	Description
IBM_DB2_StandardEd_11.5.7_LNX	IBM® DB2® Standard Edition - Restricted Use for Linux® 11.5 on AMD64 and Intel® EM64T systems (x64)
IBM_DB2_Activation_11.5.7	IBM® DB2® Standard Edition 11.5 - Restricted Use - Activation
IBM_DB2_StandardEd_11.5.7_WIN	IBM® DB2® Standard Edition - Restricted Use 11.5 for Windows® on AMD64 and Intel® EM64T systems (x64)

Installing the Fix Pack

This section describes how to apply Fix Pack 1 to HCL Workload Automation.

Installation notes

Before installing the Fix Pack, ensure you have installed the required prerequisite software. To obtain the latest information about software requirements for HCL Workload Automation, see Product Requirements.
The minimum required WebSphere Liberty version to successfully install the fixpack is 22.0.0.3 or later.
Before installing this Fix Pack on AIX® V7.1 operating systems, you must apply the patch for APAR IZ99634. For more information, see: APAR IZ99634.
On UNIX™ operating systems, before installing the HCL Workload Automation Fix Pack, ensure that your umask is set to 022. To verify that umask is set to the correct value, from a command prompt, run the umask command. If the value is different from 022, modify it by running the command:
```
umask 022
```
On UNIX™ operating systems, the database administrator must have read and run privileges for the HCL Workload Automation installation path; otherwise the installation fails. (54367)

After the Fix Pack installation completes, verify the following information:

This Fix Pack 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 installing the Fix Pack, if you have modified the original version, merge the content of the new version with the content of the original version to carry your customized content into the new version.
Only on Windows™ operating systems, to correctly display double-byte character set (DBCS) characters, you must 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 coherent, 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.

Interoperability notes: HCL Workload Automation version 10.1.0 Fix Pack 1 supports all product versions indicated in the version 10.1.0 Fix Pack 1 Release Notes which can be accessed at the following link: Release Notes for HCL Workload Automation.

Installation methods

You can install the Fix Pack using one of the following methods:

For master domain manager or its backup:: see Updating the master domain manager and its backup
For dynamic domain manager or its backup:: see Updating the dynamic domain manager
For fault-tolerant agent, dynamic agent or domain manager:: see Updating agents

Disk space requirements

For the most up-to-date information about disk space and memory requirements, see the Supported Hardware document in Product Requirements.

Before starting the Fix Pack installation, ensure that you have the necessary disk space available on the file system. Consider that the disk space check calculated by the installation considers the entire space occupied by the TWA_HOME directory. The space required by the backup is the sum of the following directories:

TWA_HOME/TWS + TWA_HOME/TDWB + TWA_HOME/wastools + TWA_HOME/properties

If the installation fails because of lack of free disk space, you must stop the installation, free space on your disk, and start the installation again.

In addition to the disk space in the following table, the installation requires an additional 600 MB on the file system where the IMShared directory is located.

Table 11. Disk space requirements for installing a master domain manager or a backup master Fix Pack
Operating System	Installation directory	Temporary directory
AIX®	2,5 GB	1,5 GB
Microsoft® Windows®	2 GB	1 GB
Linux®	1,5 GB	800 MB

Table 12. Disk space requirements for installing the Fix Pack for HCL Workload Automation fault-tolerant agents
Operating System	Installation directory	Temporary directory
AIX®	900 MB	400 MB
Microsoft® Windows®	700 MB	350 MB
Linux®	720 MB	350 MB

Table 13. Disk space requirements for installing the Fix Pack for HCL Workload Automation dynamic agents and z/OS agents
Operating System	Installation directory	Temporary directory
AIX®	600 MB	250 MB
Microsoft® Windows®	800 MB	400 MB
Linux®	600 MB	250 MB

Documentation updates

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

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

HCL 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 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 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 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 product and use of those websites is at your own risk.

HCL 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 under terms of the HCL Customer Agreement, HCL 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 products was obtained from the suppliers of those products, their published announcements or other publicly available sources. HCL has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-HCL products. Questions on the capabilities of non-HCL 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.

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, 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, 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 shall not be liable for any damages arising out of your use of the 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™ 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 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.

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.

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