Note

Before using this information and the product it supports, read the information in Notices.

This edition applies to Fix Pack 5 for version 9, release 5, modification level 0 of HCL Workload Automation (program number 5698-WSH) and to all subsequent releases and modifications until otherwise indicated in new editions.

HCL Workload Automation version 9.5.0 Readme File for Fix Pack 5

Date
December 21, 2021
Fix Pack
9.5.0-HCL-IWS-FP0005
Product
HCL Workload Automation version 9.5.0
General Description
HCL Workload Automation Fix Pack 5 for version 9.5.0

This readme file provides important information about Fix Pack 5 for HCL Workload Automation version 9.5.0.

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

HCL Workload Automation version 9.5.0 Fix Pack 5 supports all product versions indicated in the HCL Workload Automation version 9.5 Release Notes which can be accessed at the following link: Release Notes for HCL Workload Automation.

For the most up-to-date information about supported operating systems, software and hardware requirements, see the Detailed system requirements document at the following URL: Detailed System Requirements for HCL Workload Automation, version 9.5.

Review this section thoroughly before installing or using this Fix Pack.

About this Fix Pack

This section contains information specific for this Fix Pack including what has been modified or introduced, what has been fixed, product versions or components to which the Fix Pack applies, and compatibility issues, if any.

Product versions and components to which the Fix Pack applies
This Fix Pack can be applied only on top of HCL Workload Automation V9.5.0, and subsequent Fix Packs.

This section includes the following subsections:

Features introduced with Fix Pack 5

Version 9.5 Fix Pack 5 delivers the following enhancements:

Version 9.5 Fix Pack 5 delivers the following enhancements:
  • Support for OneDB pre-defined and customized reports
  • Setting up master domain manager and dynamic domain manager (broker) in SSL mode. For more information, see Configuring your master domain manager and broker in SSL mode.
  • Enhanced security for the job log. For more information, see PCI standard.
  • Support for OneDB, Version 2.0.1.0
  • The support statement for SAP S/4HANA, on-premise edition, has been extended to 2020 and future fix packs, based on SAP_BASIS 7.55 component.
Changed features and feature capabilities
Supported WebSphere Application Server Liberty Base versions
HCL Workload Automation Version 9.5 Fix Pack 5 was formally tested by using WebSphere Application Server Liberty Base 21.0.0.10 and 21.0.0.11.
Updated OpenSSL libraries
HCL Workload Automation Version 9.5 Fix Pack 5 has been updated with OpenSSL libraries version 1.1.1l 24 Aug 2021 (1.1.1.12)

HCL Workload Automation includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (https://www.openssl.org/).

IBM WebSphere® SDK Java Technology Edition
IBM Workload Scheduler Version 9.5 Fix Pack 5 has been updated with WebSphere SDK Java Technology Edition version 8.0.6.36
OpenJ9/OpenJDK Runtime Environment
IBM Workload Scheduler Version 9.5 Fix Pack 5 has been updated with OpenJ9 version 1.8.0_302
HCL Clara integration
HCL Clara is an Intelligent Virtual Assistant that improves the HCL Workload Automation customer experience with natural language processing interactions, enabling customized self-service automation with immediate 24x7 response as L1 and L2 assistant. Clara is the product expert users can consult to learn HCL Workload Automation capabilities and execute routine tasks. Find out more about HCL Clara at https://help.hcltechsw.com/solutions/clara/index.html
HCL HERO integration
HCL HERO (HEalthcheck & Runbook Optimizer) effectively helps HCL Workload Automation Administrators monitor the health of their servers and perform informed recovery actions with specialized runbooks, keeping Workload Automation environments responsive and reliable. By providing both actual KPIs and AI-powered trend estimation of KPIs, HERO enables the prediction of potential problems. Find out more about HCL HERO at https://help.hcltechsw.com/solutions/hero/index.html
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 V9.5 Fix Pack 5 delivers the following RFEs:

RFE 116956 - Integrate dynamic agents authentication with Kerberos
A new integration with Kerberos is now available on Automation Hub. You can use it to communicate securely over an insecure network by leveraging the Kerberos Authentication Protocol for submitting jobs on dynamic agents.
RFE 149991 - Add support for group authority on IBM i DA
When specifying the user that runs a job on the IBM i workstation, you can define a user which is part of an operating system group.
RFE 150599 - Workstation should show offline for agent pools connected to a dynamic domain manager

A new API on the dynamic domain manager is now available. The API checks if there is at least one agent available for a given pool, so the caller can determine if the pool workstation is online or offline, same as for z-centric or dynamic agents.

Resolved Common Vulnerabilities and Exposures (CVE)
  • CVE-2021-39239
  • CVE-2019-17571
  • CVE-2017-9735
  • CVE-2020-27216
  • CVE-2021-28165
  • CVE-2021-34428
  • CVE-2018-12536
  • CVE-2019-10241
  • CVE-2019-10246
  • CVE-2019-10247
  • CVE-2017-7656
  • CVE-2017-765
  • CVE-2017-7658
  • CVE-2021-33813

Serviceability items

  • A new filter has been added to Makeplan script. It only picks up statistics related to the days the plan is going to be extended in, without loading all job statistics.

Features introduced with Fix Pack 4

Version 9.5 Fix Pack 4 delivers the following enhancements:

HCL Workload Automation V9.5 Fix Pack 4 delivers the following Enhancements:

Changed features and feature capabilities

Updated OpenSSL libraries
HCL Workload Automation Version 9.5 Fix Pack 4 has been updated with OpenSSL libraries. HCL Workload Automation includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (https://www.openssl.org/).
OpenJDK Runtime Environment
Fix Pack 4 has been updated with Java version 1.8.0_282
Supported WebSphere Application Server Liberty Base version
HCL Workload Automation Version 9.5 Fix Pack 4 was formally tested using WebSphere Application Server Liberty Base version 21.0.0.4 and 21.0.0.5.
New database version supported
Support has been added for MSSQL, version 19.
Satisfying Requests for Enhancements (RFEs)

Satisfying Requests for Enhancements (RFEs) Requests for Enhancements (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.

Improve status management for jobs running on IBM i in case submitted jobs are lost
The status management for jobs running on IBM i has been improved to support monitoring of jobs lost after submission.
Support for userid in IBM i job
AllowRoot (AllowQsecofr) feature for IBM i agents has been implemented.
Unexpected error message after wappman -export is now fixed
The wappman export command works as expected and the WAT files are correctly exported.
Certificate validation on agents
Dynamic and z-centric agents can now ensure the certificate they receive is valid and has been issued by a recognized CA. For more information, see Customizing the SSL connection between the agents and the Z controller when using your certificates
Notifications are now available in the Dynamic Workload Console about the status of your connections to the Flexera license server
Connection to the license server is crucial to your workload. You can now check the status of the connection in real time. For more information, see How do I verify my connection to the license server?.
Resolved Common Vulnerabilities and Exposures (CVE)
  • CVE-2018-15494
  • CVE-2020-14779
  • CVE-2020-14781
  • CVE-2020-14782
  • CVE-2020-14792
  • CVE-2020-14797
  • CVE-2020-1971
  • CVE-2020-2773
  • CVE-2020-5258
  • CVE-2020-5258
  • CVE-2021-20349
  • CVE-2021-2161
  • CVE-2021-23840
  • CVE-2021-23841
  • CVE-2021-26296
  • CVE-2021-3449
  • CVE-2021-3450

Serviceability items

  • New DebugDir parameter added to JobManager.ini file to enable tracing for the dynamic agent to help determine what information is being sent to and from a dynamic agent workstation.
  • Fixed APAR IJ28142 with improved support for jobs randomly failing on AIX.

Features introduced with Fix Pack 3

Version 9.5 Fix Pack 3 delivers the following enhancements:
Changed features and feature capabilities
New Web site for the HCL Workload AutomationHCL product documentation
The latest version of the HCL Workload Automation product documentation, version 9.5 Fix Pack 3/SPE3 can be found on the HCL Software Product Documentation web site at https://help.hcltechsw.com/workloadautomation/welcome/index.html. The former website, https://workloadautomation.hcldoc.com/help/index.jsp, continues to host previous versions of the product documentation (version 9.4.0.x).
Support for file transfer jobs on agents at Version 9.3
Agents at Version 9.3 can run existing file transfer jobs without problems. Jobs you create or edit from the Dynamic Workload Console at Version 9.5, Fix Pack 3 are not supported on agents at Version 9.3, but you can work around this problem by saving the jobs in the composer command line after editing them with the Dynamic Workload Console. The best practice is applying the latest fix pack level to the agents.
Skip objects when importing a workload application template
You can select the objects within a workload application template you do not want to import, both from the Dynamic Workload Console and wappman command. If you choose to skip an object, an object with the same name must be present in the target environment, otherwise an error message is returned. For more information, see wappman.
New optman option to specify the default licensing model for HCL Workload Automation workstations
You can now use the defaultWksLicenseType option to specify the default licensing model to be applied to HCL Workload Automation workstations. In a Docker environment, this causes all workstations to be created with the value assigned to the defaultWksLicenseType option. For more information, see Global options - detailed description.
The term $SLAVES was removed from the security file and replaced with the term $AGENTS
Because it is politically incorrect, the term $SLAVES, which applies to all fault-tolerant agents in both the classic and role-based security models, was replaced with the term $AGENTS with the same scope. No change is required to your existing scripts nor environments. For more information, see Configuring user authorization (Security file).
Improvements in time zone management for external follows dependencies for jobs and job streams
When the product evaluates matching criteria to resolve external follows dependencies it compares the start times using local time if both job stream instances use the same timezone, or it uses UTC in case they use different timezones. For more information, see Managing external follows dependencies for jobs and job streams.
Support for proxy servers when contacting the license server
You can now use a proxy server when contacting the license server. This is especially useful when your HCL Workload Automation environment cannot connect to the Internet. To set up communication with the proxy server, use the licenseProxyPassword, licenseProxyServer, licenseProxyServerPort, licenseProxyUser global options. For more information about global options, see setting global options .
Satisfying Requests for Enhancements (RFEs)

Requests for Enhancements (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 V9.5 Fix Pack 3 delivers the following RFEs:
RFE 18054: Custom role privileges
Now you can define new custom roles, assign specific privileges to a set of users, and also assign privileges outside the scope of the existing system role.
RFE 116406: Add state=cancl on showjobs command
You can now filter jobs which are in canceled status. For more information, see wildcards.
REF 116762: Improvements for Event Driven Workload Automation
You can now optionally modify the event processor server, for example to use a load balancer, by adding the Broker.Workstation.evtproc property in the BrokerWorkstation.properties file. For more information, see BrokerWorkstation.properties file.
RFE 117719: End time column available for job streams in monitoring panel
This column is available when creating a job task, with this enhancements the end time column is also available for job streams.
RFE 123642: DWC historical reports' self-cleaning option
A new self-cleaning property has been enabled to remove all temporary files created after a report generation.
RFE 124339: New Graphical View order settings.
Now you can reorganize the dependencies view in the Graphical View by clicking on the Graphical view button and choosing the order in which you want to see them. The available options are:
  • From right to left
  • From left to right
  • From top to bottom
  • From bottom to top

By default, it is set to from top to bottom.

You can also edit the TdwcGlobalSettings.xml file to customize the default Graphical View settings.

RFE 126163: DWC user with read only access locks out an ISPF user with modify privilege
z/OS environment only. Now if you open a list of job dependencies from the Dynamic Workload Console, the related ISPF panel is locked and it is not possible to edit dependencies until the job dependencies panel is closed.
RFE 85329 / RFE 130134: Ability to clean the query history

When you have a very high number of past queries saved in the Query drop-down list, it is not easy to find the query that you really need. With this fix pack, you can manage the list either by removing single queries or clearing all the query history.

RFE 133936: Enhancement to composer binary to allow schedule objects to be pulled via "Active" or "DRAFT" status
Two new filters (draft and active) are now available with the composer command to filter job stream in draft or active status. For more information, see filters and wildcards.
RFE 134893: default licensing model for HCL Workload Automation workstations
You can now specify the default licensing model for IBM® Workload Scheduler workstations. By setting appropriately the values of the defaultWksLicenseType and licenseType global options, you can define the default licensing model to be applied to each workstation at creation time. For more information, see the detailed description of global options.
RFE 137834: Modify the configureDB upgrade script to include any Subsequent additional IDs
Modify the configureDB database upgrade script to include any additional Subsequent Database IDs for DB2. In the script which translates 9.3 database to the 9.5 structure, capture the roles assigned to the views before they were dropped and recreate them so you can reassign those roles at the end of the process. It should also assign those roles to any new views created. For more information, see How can I avoid providing the database administrator credentials when creating the database with DB2
RFE 139348: The report output limit has been improved to avoid Dynamic Workload Console issues

The default value for the Enable output limit checkbox has been increased from 5000 to 10000. This enables you to obtain the expected report output, and the Dynamic Workload Console to continue to work correctly without issues.

Furthermore, if a different default value is needed, a user with administration grants can uncomment the new SQL_REPORT_HTML_FORMAT_RESULT_MAX_NUMBER key in the TDWCGlobalsettings.xml file and enter the desired default value (either higher or lower to the default 10000).
Note: For HTML format, the SQL_REPORT_HTML_FORMAT_RESULT_MAX_NUMBER key is valid for all reports. For PDF format, the key is valid for Custom reports only.

If you want to generate a report with less than 30000 records, you can use both HTML and PDF formats. If you want to generate a report with more than 30000 records, use only the PDF format to avoid reliability issues with the browser.

For further information about how to modify the TDWCGlobalsettings.xml file, see the Customizing your global settings section in the Dynamic Workload Console User's Guide.

RFE 140107, 140108: Ability to perform actions on engines in the Dynamic Workload Console through a script or API call
To be able to schedule and run HCL Workload Automation processes in an automated way without having to log in to the Dynamic Workload Console, you can now perform actions such as create/edit, share/unshare, and delete on an engine through a script or by calling an API.
RFE 140216: Update optman global Options through REST API
You can now use REST APIs to update global options, in addition to the standard optman command.
RFE 141849: Justification fields for Workload Application Template import operation
You can now maintain an audit trail recording any changes and the related justifications while creating workload application templates with the wappman command. For more information, see wappman .
RFE 143098: Add all authenticated users
Simply adding a line into the authentication file, now it is possible to add all new users to a group and - without any other configuration - they will be authorized to login into the Dynamic Workload Console.

From now it is not necessary to assign a role to every single user. If the user registry already contains groups of users that are properly defined for using the console, it is possible to assign roles to groups too. If groups are not available in the user registry, then the special role all authenticated users can be used to assign roles to all the users at once.

For more information, see the Configuring roles to access the Dynamic Workload Console

RFE 143162: Prevent job streams from completing in error when the start condition is not met
The new enStartCondSuccOnDeadline global option is now available to specify if you want your job stream to be cancelled when the start condition is not met, even if the Start once option is not selected. By setting this option, you can avoid that your job stream completes in error due to just one failed run, also in the case when it previously ran successfully several times. With the new enStartCondSuccOnDeadline global option set to yes, when the deadline for the start condition is met, the monitoring job is confirmed in SUCC status and the job stream is canceled. When the option is set to no, the monitoring job is killed, so both the monitoring job and the job stream change to ABEND status. For more information, see Global options - detailed description.
RFE 143169/143839: Managing an event rule in the Dynamic Workload Console
Usability improvements for event rule actions such as editing, duplicating, and deleting event rules in the Dynamic Workload Console Workload Designer. In addition, more space is now provided in the properties section for events and actions.
RFE 143196: possibility to select object to be imported during a WAT import
You can now select the objects to be imported while creating a workload application template and skip unwanted objects. For more information, see wappman.
RFE 143260: Latest Start included in the critical path list and hot list
To identify problems related to a critical path that has a potential or high risk, the Latest Start time is now included in the critical path, in the hot list, and in the results of a monitor critical job query in the Dynamic Workload Console. The time before which the job must start is displayed provided all dependencies are satisfied.
RFE 142794
HCL Workload Automation Version 9.5 Fix Pack 3 has been updated with OpenSSL version 1.1.1g.

HCL Workload Automation includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (https://www.openssl.org/).

RFE 148080: Provides the capability to constrain a product component pod to run on particular nodes
The nodeAffinityRequired parameter has been added to the configurable parameters that can be customized when deploying product components with containers. With this parameter, you can determine on which nodes a component can be deployed using custom labels on nodes and label selectors specified in pods. Red Hat OpenShiftAmazon EKSAzure AKS

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

Entitlement to Db2 V11.5
With HCL Workload Automation, version 9.5, Fix Pack 3, you are entitled to use Db2 V11.5 Standard Edition.
Supported WebSphere Application Server Liberty Base version
HCL Workload Automation Version 9.5 Fix Pack 3 was formally tested using WebSphere Application Server Liberty Base version 20.0.0.10. and 20.0.0.11.
Updated OpenSSL libraries
HCL Workload Automation Version 9.5 Fix Pack 3 has been updated with OpenSSL version 1.1.1g.

HCL Workload Automation includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (https://www.openssl.org/).

CIT
Fix Pack 3 has been updated with CIT version 9.2.21.0000.
Updated version of GSKIT
Fix Pack 3 has been updated with GSKIT version 8.0.55.6.
OpenJDK Runtime Environment
Fix Pack 3 has been updated with Java version 1.8.0_265-b01.
Resolved Common Vulnerabilities and Exposures (CVE)
The following CVEs have been resolved with this fix pack:
Java
  • CVE-2020-2800
  • CVE-2020-2754
  • CVE-2020-2757
  • CVE-2020-2781
  • CVE-2020-2830
  • CVE-2020-2755
  • CVE-2020-2756
  • CVE-2020-4329
  • CVE-2020-14583
  • CVE-2020-14581
  • CVE-2019-17639
  • CVE-2020-14593
  • CVE-2020-14577
  • CVE-2020-14579
  • CVE-2020-14578
  • CVE-2020-14621
  • CVE-2020-14556
  • CVE-2020-2601
  • CVE-2020-2590
UBI
CVE-2020-16122
OpenSSL
CVE-2020-1968

For more information about new features introduced with this fix pack, see Summary of enhancements.

Helpful videos demonstrating new features for HCL Workload Automation is available on Workload Automation YouTube channel.

Features introduced with Fix Pack 2

Automation Hub: the future of automation

For more information about the new automation command center, see Automation Hub: the future of automation

Workload Automation Lutist Development Kit: do-it-yourself!

For more information about the new tool that enables you to create and publish your own integrations, see Workload Automation, Lutist Development Kit: do-it-yourself!

Continuous operation with automatic failover

For more information about the automatic switchover, see Continuous operation with automatic failover

Organize scheduling objects in workflow folders

For more information about folders, see Organize scheduling objects in workflow folders

Enhance security with encrypted passwords

For more information about password encrypting, see Enhance security with encrypted passwords

Enable support for long object names in the security file

For more information about scheduling object names, see Enable support for long object names in the security file

Deploying HCLWorkload Automation components on Red Hat OpenShift v. 4.x

For further details about the deployment on OpenShift refer to Deploying HCL Workload Automation components on Red Hat OpenShift

Changed features and feature capabilities
A new home for Workload Automation plug-ins
Automation Hub is a new concept for automating business workflows.

In previous versions, all job plug-ins were provided with the product and obtaining new plug-ins meant you were bound to the product releases.

With Fix Pack 2, you can still access the usual plug-ins from the product, but going forward, any updates, and the related documentation, can be found on Automation Hub. Furthermore, the continuous delivery of new plug-ins - now called integrations - enables you to download and use new integrations in the product, at any time.

A new way to automate your business workflows and a more flexible solution to having only the integrations of your interest integrated in the product.

But that is not all, if you do not find the integration that you are looking for, you can make a request for it or, you can create it yourself. To create a new integration, you can use the Workload Automation, Lutist Development Kit, and then share your integration with the community.

Let's automate more and automate better.

Identifying workstations, resources, and prompts
Fix pack 2 adds the support for defining scheduling objects in folders. As a consequence, workstations, resources, and prompts are no longer identified in the plan solely by their names, but also by the folder in which they are defined. The name and folder association is mapped to a unique identifier. In the localopts file, the this_cpu option is the unique identifier of the workstation. You can verify the unique identifier for workstations, resources, and prompts by submitting the composer list command, together with the ;showid filter, or by submitting the conman commands: showcpus, showresources, and showprompts, together with the ;showid filter.

Identifying workstations and resources by their unique identifier avoids the problem that occurred in previous versions when objects were renamed in the plan. For example, if an object was renamed and then carried forward to a new production plan, references to the old object name were lost. With the implementation of the unique identifier, this will no longer occur and dependencies will be correctly resolved. However, if a workstation or resource is renamed, its new name is visible to all V9.5FP2 instances (or later), but earlier instances continue to see the old name of the object.

For examples, see the conman showcpus command and the composer list command in the User's Guide and Reference.
Modification of the use of wildcards in workstation classes
With the introduction of folders in which to define workstation classes, a change has taken place with respect to the use of wildcards in specifying members of a workstation class. While in the previous releases, wildcards included all workstations, starting from version 9.5, Fix Pack 2, wildcards include all the workstations defined in the same folder (including sub-folders, if any) as the workstation class definition.

For more information about the use of wildcards in workstation classes, see the topic about workstation class definition in User's Guide and Reference.

Extended agent installed with a master domain manager
With a fresh installation of a master domain manager on Linux and UNIX, a new extended agent is installed on the master domain manager workstation which is used to communicate where to run the FINAL job stream. With an extended agent, the $MASTER keyword can be used to indicate that the agent's host workstation is the master domain manager. If the role of the master domain manager is switched to another workstation, then the $MASTER keyword automatically detects the new master domain manager. This change is to facilitate the automatic failover feature. See automatic failover in the Administration Guide.
Scheduling objects defined using REST APIs
Starting from product version 9.5, Fix Pack 2, the composer command line to create object definitions uses REST APIs. This means that when you create a definition using composer, new APIs are used, which are not compatible with the APIs installed on master domain managers with previous product versions. As a result, you cannot use a composer at version 9.5, Fix Pack 2 level, to create a definitions on a master domain manager where a previous version of the product is installed. This change applies to the following object definitions:
  • calendar
  • domain
  • prompt
  • resource
  • variable table
  • variable and parameter
  • Windows user
  • workstation
  • workstation class
The default value for the mm resolve master local options has changed
With this fix pack, the default value for the mm resolve master local option in the localopts file has changed from no to yes.
Create a JSDL job definition
To create a JSDL job definition in HCL Workload Automation using the Job Brokering Definition Console refer to the previous documentation releases.
Remove deleted folders, prompts, workstations, and resources from the database
When deleting a workstation, if the workstation is still in the plan, then another workstation cannot be renamed with the name of the deleted workstation for the number of days specified by the global option folderDays. However, a brand new workstation can be created with the name of the deleted workstation. This behavior applies only to dynamic agents, pools, and dynamic pools. The default value is 10 days.

When deleting a folder, a prompt, or resource, if there are still objects in the plan that reference these objects, then another folder, prompt, or resource cannot be renamed with the name of the deleted folder, prompt or resource for the number of days specified by folderDays. However, a brand new folder, prompt, or resource can be created with the name of the deleted object. .

Satisfying Requests for Enhancements (RFEs)

Requests for Enhancements (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 V9.5 Fix Pack 2 delivers the following RFEs:
RFE 138951: Support for an existing Oracle user
When creating and populating the Oracle database schema during a fresh installation of the server or Dynamic Workload Console component, by default a check is performed to detect if the Workload Automation Oracle user already exists. If the Oracle user is found, but it does not contain the Workload Automation schema, the database schema is not created for this user. If no user is found, the installation creates the Oracle user and the Workload Automation schema. This behavior can be configured using the -skipdbcheck parameter in the installation scripts. By default this parameter is set to false. If this parameter is set to true, the installation creates the Workload Automation schema even if the existing Oracle user does not contain the Workload Automation schema.
RFE 132029: Add run number check within MakePlan before locking the database

The MakePlan process was modified to perform a check on the previous day run number and comparing it with the new run number ensuring it has increased by 1. If the new run number is not reflected in the database, MakePlan should abend. This check must be done prior to the locking of the database by Planner.

RFE 136191: JS EVERY DONOTSTART is not using untilDays. Allow configuration of the value for the global option untilDays for job streams
The untilDays option removes obsolete job and job stream instances from the plan. In previous versions, a hardcoded value of 2 days was set for job streams that did not have an until time set, resulting in cancellation of the job stream after two days. In the case of a job stream with the EVERY ONOVERLAP DONOTSTART keywords, if one or more jobs defined in the job stream abend, and are not resolved within the 2-day period specified by UntilDays, then the abended jobs are not carried forward and the job stream is canceled. This global option can now be configured for the number of days most appropriate for your scheduling environment. If you require maintaining a job stream longer than the number of days specified by untilDays, you can explicitly set an until time for that specific job stream.

For jobs, either you set an until time at the job level, or it assumes the until time of its job stream. If no until time is set for either job or job stream, then the until time is calculated by adding the setting for untilDays to the time the job enters the production plan.

With the release of this fix pack, the global option untilDays is now configurable. The default value is 0. If the default value is used, then for jobs, no default time is set for the until time (latest start time). For job streams, if the default is used, then the default until time is 2 days. See the Administration Guide for more information about the untilDays global option
RFE 120948: Intercept SAP jobs by SAP users, and limit executions on TWS by "n" jobs per user
Control and limit the number of jobs submitted by each user. When the established number of jobs for the specific user is exceeded, the jobs are queued and submitted at a later time. To implement this feature, two new options have been added in the options file:
MAX_JOBS_TO_RELEASE_FOR_USER
Defines the maximum number of jobs released for each user each time the release job is submitted. If this option is less than or equal to 0, the option is ignored and all jobs are released when the release job is submitted.
RELEASE_ALL_INTERCEPTED_JOBS_FOR_REQUEST
Releases jobs for each user on a cyclic basis, based on the number of jobs specified in the max_jobs_to_release_for_user option. The default value is ON, which means that all jobs are submitted for each user:
  • If the max_jobs_to_release_for_user option is less than or equal to 0, all jobs are released for each user.
  • If the max_jobs_to_release_for_user option is higher than 0, the specified number of jobs is submitted for each user on a cyclic basis. For example, if max_jobs_to_release_for_user=5, the first 5 jobs are submitted for each user, then the following 5 jobs for each user, and so on, until all jobs for all users are submitted.
If this option is set to OFF, it releases for each user only the number of jobs specified in the max_jobs_to_release_for_user option. The remaining jobs are submitted only when a new release job is submitted:
  • If the max_jobs_to_release_for_user option is less than or equal to 0, all jobs are released for each user.
  • If the max_jobs_to_release_for_user option is higher than 0, only the specified number of jobs is submitted, then no other job is submitted until the new release job. If max_jobs_to_release_for_user=5, the first 5 jobs are submitted for each user, then no other job is submitted until the new release job.

For more information, see the section about defining configuration options in Scheduling Applications with IBM Workload Automation.

RFE 140942: Ability to remove/control rerun option for broker jobs
By default, when a broker job fails because of a missing resource, the product attempts to find an available resource every 600 seconds, rerunning the job each time. With this enhancement, after the first failed attempt to find an available resource, the job FAILS. To enable this new behavior, add the hidden property, Broker.Workstation.Enable.RerunOnAllocFailure, to the BrokerWorkstation.properties file and set the property to "false". By default, the value of this property is "true".
RFE 137732: Wappman functionality does not support the replacing or modifying of an existing job stream
In HCL Workload Automation 9.3 Fix Pack 3, wappman import/export and replace is used for continuous deployment across environments. After the upgrade to V94FP5, wappman cannot be used to modify the existing job stream definitions and its related objects like resources and jobs. With HCL Workload Automation 9.5 Fix Pack 2, the import, export and replace with wappman has been reintroduced.
RFE 140989: Add an SSH client in the DOCKER image of the IBM Z Workload Scheduler Agent (z-centric)
An SSH client has been added to the IBM Z Workload Scheduler Agent DOCKER image which allows secure and encrypted remote connections.
RFE 128243: Job run numbers are not unique on a single agent in the plan when you have a very high number of rerun jobs
When you have a very high number of rerun jobs, accessing information about a specific job instance, specifying the CPUNAME and the job number, does not provide the expected result. With this fix pack, the job number is not considered an identifying factor when running conman commands. When submitting a conman command, you are prompted to confirm a selection of results that correspond to the filters specified with the exception of conman show commands (for example, conman showjob),where you are not prompted for confirmation but, instead, all results corresponding to the filters specified are displayed.

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

Updated version of WebSphere Application Server Liberty Base
HCL Workload Automation version 9.5 fix pack 2 was formally tested using WebSphere Application Server Liberty Base version 19.0.0.12, 20.0.0.2 and 20.0.03. Because of a known issue affecting version 20.0.0.1, APAR PH21281, we strongly recommend you avoid using it.

For more information about new features introduced with this fix pack, see Summary of enhancements.

Helpful videos demonstrating new features for HCL Workload Automation is available on Workload Automation YouTube channel.

Features introduced with Fix Pack 1

Renaming and moving jobs and job streams into folders

You might have used simple to complex naming conventions when creating job and job stream names to easily identify and manage them. With character length restrictions for these names, creative abbreviations are required to stay within the limits. This can often lead to unreadable names.

You can now migrate multiple jobs and job streams, in batch mode, whose names contain common pattern matching into specified folders and sub-folders, where the folder names are extracted from the job and job stream names themselves. Naming folders by using tokens from the job and job stream names frees up characters so that you can rename jobs and job streams with more meaningful names, in addition to the folder names.

To rename and move jobs and job streams into folders, the composer rename command has been extended to support wildcard characters. The wildcard characters are used to replace pattern matching tokens in the job and job stream names and enable you to migrate the jobs and job streams in bulk, rather than one at a time. A ;preview option is provided to test the command before actually running it to ensure you obtain the expected result.

For more information see Organizing jobs and job streams into folders

File transfer job plug-in enhancements
Version 9.5 Fix Pack 1 delivers the following enhancements to the File transfer job plug-in:
RFE 124923: Appending text to an existing file
The file transfer job plug-in now includes an option to append the data contained in the transferred file to the existing file on the destination system. This avoids overwriting the existing file and preserves any changes that were made to the file prior to the transfer. The option applies to file transfers of type download and for files encoded as text.
Deleting a source file after an upload transfer
An option has been added to specify if you want to delete the source files after a file transfer of type "upload".
RFE 127294: Specifying FTP SIte subcommands
An option has been added for file transfers originating from a distributed environment to a z/OS target workstation, using the FTP protocol, to specify SIte subcommands. For example, you can specify a subcommand to define primary and secondary space allocations.
Deploying HCL Workload Automation Agent on Red Hat OpenShift v. 3.x

The HCL Workload Automation agent container can be deployed onto OpenShift, a container application platform based on Kubernetes and useful to orchestrate containers.

For further details about the deployment on OpenShift refer to Deploying HCL Workload Automation Agent on Red Hat OpenShift

Delegating administrator privileges on folders to other users

The HCL Workload Automation administrator can grant permissions to a user on a folder so that the user can freely create new access control lists or modify existing access control lists on the folder or any sub-folders to which the user has been delegated administrator permissions. The user can in turn give access to the folder or sub-folder to other users by specifying an existing role to which the user wants to grant the access, as well as the folder. In this way, the HCL Workload Automation administrator can delegate the security to various organizations in the business to other users who can act independently as administrators for that organization.

A new access type "acl" has been added for folder objects. With this type of access, users can create access control lists for the folder assigned to them by assigning predefined roles to users and groups on the entire folder hierarchy or on specific sub-folders.

For more information about delegating permissions on folders, see Granting administrator permissions to a user on a folder

Satisfying Requests for Enhancements (RFEs)

Requests for Enhancements (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 V9.5 Fix Pack 1 delivers the following RFEs:
RFE 124923
Appending text to an existing file. For details, see File transfer job plug-in ehnancements
RFE 127294
Specifying FTP SIte subcommands. See for more details. File transfer job plug-in enhancements for more details.
RFE 123295
Delete file on server after download. See File transfer job plug-in enhancements for more details.

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

Broker CLI commands
The resource and jobstore commands have been reactivated.
Note: To make Broker cli and Broker UI work, both Dynamic Workload Console and master domain manager should be updated to the version 9.5, Fix Pack 1.
Updated version of WebSphere Application Server Liberty Base
HCL Workload Automation version 9.5 fix pack 1 has been tested using WebSphere Application Server Liberty Base version 19.0.0.4 and 19.0.0.5
Updated version of Informatica
Fix Pack 1 has been tested using Informatica 10.1.1. The scenarios already certified with Informatica 9.x have ran successfully

For more information about new features introduced with this fix pack, see Summary of enhancements.

Helpful videos demonstrating new features for HCL Workload Automation is available on Workload Automation YouTube channel.

Problems fixed in HCL Workload Automation Fix Pack 5 for version 9.5.0

This section lists APARs and internal defects solved by Fix Pack 5.

Table 1. APARs addressed in Fix Pack 5
APAR ABSTRACT
IJ06492 CUSTOM CONFIGURE TASK (SET AUTO REFRESH) AND (ENABLE PERIODIC REFRESH) ARE ONLY WORKING AFTER THE FIRST INTERVAL
IJ11426 "POST /MODEL/JOBSTREAM/HEADER/QUERY" FAILS WHEN ABSTRACTID IS USED IN JOB STREAM FILTER
IJ22165 FM - WAS 8.5.5.13 HOLDING "DELETED" SPACE
IJ22363 COMPOSER VALIDATE RUNCYCLEGROUP DOESN'T WORK FOR 9.4 FIX PACK 5
IJ25781 REQUIRED BODY FIELDS ON REST CALL ARE NOT SPECIFIED
IJ26422 MONMAN ALLOCATING HUGE NUMBER OF FILES (ALL SYMPHONY FILES)-OLD SYMPHONY FILES
IJ28256 JOBMANAGER CANNOT START BECAUSE CIT SCAN 0 CORE RESULT
IJ28943 DOCUMENTATION FOR GLOBALOPTION "ENPREVENTSTART"
IJ30770 DWC: UNABLE TO RESTORE TO PREVIOUS VERSION FOR USER OBJECT, "RESTORE" BUTTON MISSING
IJ31005 IF THE DYNAMIC AGENT GATEWAY NAME CONTAINS THE CHARACTER "-", IT WILL NOT WORK AS EXPECTED
IJ31250 CHANGES AND CLARIFICATION NEEDED FOR CONFIGUREDBDB2Z.TEMPLATE TO COMPLY WITH DB2 FOR Z/OS
IJ31969 JOB STREAM SUBMISSION IS ALLOWED ON DELETED RESOURCE WITHOUT ANY VALIDATION PERFORMED
IJ32535 WHEN THE STREAM IS INSIDE A FOLDER PATH, THE JOB "JOB STREAM SUBMISSION" ABENDS WITH -6 (AWKJSJ044E AWKJSJ048E)
IJ32914 CONMAN INFORMATIONAL MESSAGE NOT BEING SUPRESSED
IJ32942 JOB STREAM SHOWS IT IS SUCCESSFUL WHILE JOB IS STILL IN EXEC STATE
IJ32943 DYNAMIC AGENT SSH FILETRANSFER MEMORY LEAK
IJ33053 REST API "SUBMIT JOB STREAM" - NOT POSSIBLE TO SUBMIT WITH TIME RESTRICTION FILTERS
IJ33141 IWS JOBS ON IBM I DO NOT COMPLETE EVEN IF LAUNCHED JOBS DID
IJ33147 MISSING RUNCYCLE WHEN USING RUN CYCLE GROUP (RCG) ALONG WITH DELAY FOR DAYS -1
IJ33291 RETURN CODE OF 500 FROM RESTAPI DELETE OF JOB STREAM FOR TWSZ
IJ33483 INSTALLING DWC ON Z/OS GETS "WAINST015E THE FOLLOWING COMMAND FAILED: CP -R "
IJ33534 FORECAST PLAN IS NOT WORKING AS EXPECTED. JOB STREAMS ARE MISSING FOR SOME WORKSTATIONS
IJ33576 SCHEDULE'S END TIME PRINTED EARLIER TIMING THAN THE LAST JOB'S END TIME IN IWS94 FP6
IJ33578 IN DWCINST SCRIPT, -SKIPCHECKPREREQ VALUE MUST BE SPECIFIED IN ALL CAPITAL LETTERS "TRUE" OR IT DOES NOT WORK
IJ33584 FTA JOB STATUS INCONSISTENT WITH MDM AFTER CONFRIM SUCC ON DWC
IJ33750 SKIPCHECKEMPTYDIR PARAMETER MISSING IN IWS 9.5 INSTALLATION DOCUMENTATION
IJ33951 MOVE OPTION IS NOT WORKING ON FILE TRANSFER PLUGIN
IJ34135 ENEXPANDEDRESOURCES / ER-YES BUT IN MERGE.LOG ERROR IS FOR 32 HOLDERS, HOWEVER 60 JOBS DO EXECUTE AT A TIME IN THE CURRENT PLAN
IJ34150 COMPLETELY NEW AGENT INSTALLATION ON IBM I FAILS (WCITINST_OS400 NO SUCH FILE OR DIRECTORY)
IJ34228 SQL BASED DB JOBS ENDING WITH "AWKDBE011E SQL JOB EXECUTION ERROR "NULL""
IJ34309 VALID SAMPLE OF TDWCGLOBALSETTINGS.XML
IJ34406 WRONG BEHAVIOUR IN INSTALLING A BMDM IF THE MASTER FILE INTO SERVERINST CONTAINS JUST BLANK CHARACTERS
IJ34619 UPDATE DOCUMENTATION TO CONSIDER FOLDER SUPPORT WHEN CREATING CUSTOM URLS
IJ34682 MISLEADING AWKFTE039E ERROR MESSAGE RETURNED BY FILETRANSFER PLUGIN WHEN PORTS ARE CLOSED ON FIREWALL
IJ34794 FILETRANSFER PLUGIN DOES NOT RETAIN GRANTS ASSIGED TO THE FILE IF THE FILE IS REPLACED
IJ34828 DWC 9.5 FP4 WILL NOT INSTALL CORRECTLY ON Z/OS
IJ34844 PERFORMANCE DEGRADATION QUERYING ALTERNATE PLANS FROM DWC, WHEN THE ALTERNATE PLANS ARE BIG
IJ34851 EXTENDED AGENT JOBS ABENDING AFTER SWITCHING DOMAIN MANAGERS
IJ34893 TWS 9.5 FP4 ONLY: WHEN SSL IS ENABLED BETWEEN EVENT PROCESS AND AGENT SOME EVENT CAN BE LOST AND MONMAN IS NO LONGER RESPONDING
IJ34916 AGENT UPGRADE FAILS DUE TO DOMAIN CONFLICT
IJ34924 CURRENT PLAN EXTENTION TOOK UP TO 1 HOUR
IJ34942 WHILE UPGRADING FROM DWC 9.5 FP2 TO FP3 THE DWCUSER WAS CHANGED FROM DWCUSER TO DWCADMIN
IJ34964 COMMA IS NOT A VALID CHARACTER TO BE USED IN WINDOWS AGENT INSTALLATION USING THE TWSINST.VBS SCRIPT
IJ34965 THE DOCUMENTATION NOW INCLUDES A LIST OF ALL USED PORTS FOR TWA COMPONENTS
IJ35447 CANNOT RUN START_TWS.SH ON REDHAT 8.X
IJ35500 AGENT NOT RESPONDING PERIODICALLY WITH ITA ERROR "THE SEMAPHORE TIMEOUT PERIOD HAS EXPIRED"
IJ35509 UPDATE JDK
IJ35516 ADHOC JOB SUBMITTED WITHOUT A FOLDER VIA DWC 9.5 AND HAVING THE MDM AS A SECURITY FILE LIKE 9.3/9.4 GENERATES ERROR
IJ35591 UPDATE LIBERTY VERSION IN IWS CONTAINERS
IJ35597 AGENT DOES NOT START IF NETWORK SERVICES ARE DOWN
IJ35626 HANDLE LEAK CAUSING AGENT DOWN
IJ35671 TWS ENGINE IS STUCK
IJ35680 SWITCHPLAN JOB CAUSES FINAL JOB STREAM ABEND (AWSBHV004E) DUE TO STAGEMAN CARRYFORWARD JOB STREAM RECORD EVALUATION AND CORRUPT SYMPHONY FILE
IJ35701 SHADOW JOBS FROM Z WHEN TRACKING D JOBS DON'T SEEM TO BE USING THE CURRENT PLAN AND USE LAST RUN OF OLD VERSION OF D JOB STREAM
IJ35717 DYNAMIC JOBS REMAIN IN INTRO AFTER DB SWITCH IN DR PROCEDURE
IJ35757 JOB STREAM SUBMISSION JOB EXECUTION GENERATES TWO JOBS JOB STREAMS, ONE CORRECT AND ONE IN ADD STATE
IJ35878 WHEN USING TWS 9.5 FP03 OR HIGHER FTP FAILS USING DATASETS IN MAINFRAME WITH LRECL=0
IJ36200 BLANK SPACES ON CN VALUE FOR INTERMEDIATE CERTIFICATE CAUSES ISSUE WITH PULLING/MODIFYING POOL WORKSTATION DEFINITION
IJ36244 JOBS ON DDRIVEN ARE GETTING STUCK IN INTRO, READY STATUS IN PROD WHEN INCREASING THE LIMIT
IJ35671

TWS ENGINE IS STUCK

IJ35516

ADHOC JOB SUBMIT WITHOUT A FOLDER VIA DWC9.5 HAVING THE MDM A SECURITY FILE LIKE 9.3/9.4 GENERATES ERROR.

Table 2. Fixed Defects
DEFECT ABSTRACT
WA-92500 MONITOR WORKLOAD: THE SPECIAL CHARACTER IS MISSING IN THE USER NAME
WA-94536 EVENT RULES NOT TRIGGERING IF EIF IS IN SSL - MONMAN PART
WA-95658 NEED TO ADD DESCRIPTION TO OPTIONAL DEFINITION OF DB_DRIVER_PATH IN ALL THE PROPERTIES AND TEMPLATE FILES
WA-95764 UNEXPECTED ERROR SAVING A JOB STREAM DEFINITION WITH AN INW DEPENDENCY
WA-95806 UNEXPECTED "/" IS IMPORTED IN EVENTRULE WORKSTATION FILTER AFTER WAPPMAN -IMPORT
WA-96509 9.5 FP4: DYNAMIC AGENT IBMI NO LONGER WORKS AFTER PROLONGED USAGE
WA-96824 CONFIDENCE FACTOR ON ZOS IS 1000.0%
WA-97026 MODIFY MESSAGE AWSJCL064I TO USE THE WORD "PREPRODUCTION" INSTEAD OF "PRODUCTION"
WA-97198 JOB MANAGER GENERATES A CORE DUMP WHEN NO PROCESSOR IS FOUND BY CIT
WA-97214 CONFIGUREDB ON WIN MSSQL END SUCCESSFULLY EVEN IF THE LAUNCHUPGRADEIWSDB.BAT FAILS
WA-97227 JOB STREAM SUBMISSION PLUGIN JOB ENDS IN ABEND ON DOCKER ENVIRONMENT
WA-97366 FLEXERA CHECK ON 14 DAYS WITH NO JOBS TO SEND COMPOSER SHOULD WORK
WA-97421 ADD MESSAGE ABOUT JOBS SENT TO FLEXERA SERVER IN THE HWA SERVER LOG
WA-97455 FLEXERA RECOVERY TOOL COULD NOT MODIFY WAS_FIRST_START_DATE
WA-97724 SDO CHANGES FOR GETAGENTSTATUS NEW API
WA-97727 INCORRECT .XML FORMAT IN THE AUTH_OPENLDAP_CONFIG.XML
WA-97790 CONMAN SC - SEGMENTATION FAULT
WA-97791 CONFIGUREDB IN UPDATE STATES "THE DATABASE HAS BEEN SUCCESSFULLY CREATED"
WA-97792 DOCKER SERVER IMAGE FAILS TO INSTALL WHILE USING CUSTOM CERTIFICATES
WA-98013 CONMAN AND COMPOSER DO NOT WORK ON IBM I
WA-98542 UNEXPECTED CHARACTER DEFINING A VARIABLE TABLE ON Z/OS ENGINE CONNECTIONS
WA-98793 MODIFY OWNER FOR CONMAN AND COMPOSER ON IBM I
WA-98807 SCAN VULNERABILITY 95FP5 TWS PROJECTS- JDOM-1.0.JAR
WA-99250 ADD LOG TO SHOW INFORMATION FOR SSL CONNECTION
WA-99287 TRACE.LOG FILE SHOWS ALL INFORMATION FROM JOB LOGS
WA-99367 9.5 FP4: EVENT RULES NOT TRIGGERING IF EIF IS IN SSL - SSMAGENT PART
WA-99402 DIRECT CONNECTION FROM BROKER TO DA (USING GATEWAY) FOR WORKFLOW DETAILS
WA-99442 UPGRADING MDM OR BKM DOES NOT MODIFY THE TLS VERSION ON LOCALOPTS
WA-99473 INIT.CFG IS OVERWRITTEN WHEN UPGRADING DA (LINUX)
WA-99720 TWSCLIENTKEYSTOREJKS.JKS ON AGENT SHOULD WORK OUT OF THE BOX
WA-99723 WE REMOVED LICENSE_SERVER_ID VALUE FROM SERVERINST COMMAND LOG ON DOCKER ENVIRONMENT
WA-99734 TRIVY VULNERABILITY PLUGINS - KUBERNETES_9.5.0.03.JAR
WA-99738 TRIVY VULNERABILITY PLUGINS - AZUREDATABRICKS_9.5.0.03.JAR
WA-99750 TRIVY VULNERABILITY PLUGINS - AZURESTORAGE_9.5.0.04.JAR
WA-99751 TRIVY VULNERABILITY PLUGINS - COMPRESSION_9.5.0.05.JAR
WA-99754 TRIVY VULNERABILITY PLUGINS -AGENT.AZURE_9.5.0.04.JAR
WA-99765 TRIVY VULNERABILITY PLUGINS - AZURERESOURCEMANAGER_9.5.0.03.JAR
WA-99766 TRIVY VULNERABILITY PLUGINS - AZURERESOURCEMANAGER_9.5.0.04.JAR
WA-99804 INSTALL ONEDB2 ON DOCKER ENVIRONMENT
WA-99818 DELETE CALENDAR WITH ALL NULL , NULL POINTER EXCEPTION
WA-99867 SYMPHONY FILE IS NOT ADDED TO THE ZIP FILE ON WINDOWS
WA-99928 REPORTCLI - REPORT GENERATION FAILS ON ONEDB
WA-99930 WSS SCAN VULNERABILITY _ TWS95FP5 IBM - JENA-CORE-2.7.4.JAR
WA-99965 AWSJCS011E AN INTERNAL ERROR HAS OCCURRED. THE ERROR IS THE FOLLOWING: "JAVA.LANG.STRINGINDEXOUTOFBOUNDSEXCEPTION". RC=255
WA-99969 MDM WIN IBM Workload Scheduler AN ERROR OCCURRED CHECKING THE SIGNATURE SENT BY LOGMAN
WA-100008 IMPLEMENT THE INSTALLATION WITH PEM CERTIFICATES WITH A STASHED PASSWORD
WA-100029 GET<OBJECTS>BYKEY NOT AUDITED
WA-100056 TWSMSG@A3E28BF WAS NOT FOUND IN THE MESSAGE CATALOG
WA-100057 /OPT/WAUTILS/WA_COMMON.ENV: LINE 613: [: TOO MANY ARGUMENTS FROM INSTALLATION LOGS WAS REMOVED FROM DOCKER ENVIRONMENT
WA-100108 INSTALLATION WITH PEM CERTIFICATE DOENS'T WORK FOR DWC ON DOCKER ENVIRONMENT
WA-100119 TRIVY VULNERABILITY ENGINE - (TIVOLI_MDM_LINUX_X86_64/USR/SERVERS/ENGINESERVER/APPS/TWSENGINEMODEL.JAR
WA-100120 TRIVY VULNERABILITY ENGINE - COM.IBM.SCHEDULING.AGENT.CORE_9.5.0.05.JAR
WA-100121 TRIVY VULNERABILITY PLUGINS - ORG.ECLIPSE.JETTY.HTTP_9.2.13.V20150730.JAR
WA-100123 TRIVY VULNERABILITY PLUGINS - ORG.ECLIPSE.JETTY.IO_9.2.13.V20150730.JAR
WA-100128 TRIVY VULNERABILITY PLUGINS - ORG.ECLIPSE.JETTY.SERVER_9.2.13.V20150730.JAR
WA-100130 TRIVY VULNERABILITY PLUGINS - (TIVOLI_ECLIPSE_LINUX_X86_64/TWS/JAVAEXT/ECLIPSE/PLUGINS/ORG.ECLIPSE.JETTY.UTIL_9.2.13.V20150730.JAR)
WA-100134 INSTALLATION WITH PEM CERTIFICATE DOESN'T WORK FOR DYNAMIC AGENT ON DOCKER ENVIRONMENT
WA-100141 ADD REWORK IMPLEMENTATION OF ADDITIONAL CAS FEATURE ON DOCKER ENVIRONMENT
WA-100180 IMPORT CERTIFICATE LOGS SHOULD BE REDIRECTED TO STDERR /STDLOG FILE FOR SERVER AND AGENT ON DOCKER ENVIRONMENT
WA-100183 MISSING ENVIRONMENT PARAMETER INTO INSTALLATION AGENT LOGS ON DOCKER ENVIRONMENT
WA-100221 THE CONFIGURATION FILES IN THE REGISTRY ARE NOT UPDATED CORRECTLY
WA-100244 AFTER INSTALLATION IMPORTSERVERCERT COMMAND DOES NOT WORK AS EXPECTED
WA-100245 USER IS NOT AUTHORIZED TO PERFORM COMPOSER RENAME MASTERAGENTS WORKSTATION
WA-100255 SSL CONNECT ERRORS IN COMPOSER COMMANDS
WA-100262 MASTER AND CONSOLE INSTALLATION WITH PEM CERTIFICATE DOESN'T WORK ON KUBERNETES ENVIRONMENT
WA-100274 REPORTCLI - AUDIT REPORTS FILTERS DO NOT INCLUDE NEW ACTIONS
WA-100298 FIX MESSAGES (REVIEW DONE) FOR FLEXERA
WA-100317 FOLDER SECURITY TOO RESTRICTIVE
WA-100318 SBS MIGHT REQUIRE "ADD" RIGHT ON FOLDER
WA-100367 INIT.CFG IS OVERWRITTEN WHEN UPGRADING FTA (LINUX)
WA-100403 TRIVY VULNERABILITY PLUGINS - COM.IBM.SCHEDULING.AGENT.DATABASE_9.5.0.05
WA-100473 OPENSSL 1.1.1L (1.1.1.12) WAS NOT POSSIBLE TO ESTABLISH AN SSL COMMUNICATION ON AIX
WA-100477 DOCKER: CP: CANNOT STAT '/OPT/WAUTILS/CERTS/*': NO SUCH FILE OR DIRECTORY
WA-100528 INIT.CFG IS OVERWRITTEN DURING UPGRADE DA AND FTA (WINDOWS)
WA-100583 EVENT RULES NOT TRIGGERING IF EIF IS IN SSL ON FTA SOLARIS OPTERON
WA-100619 AWSJOM177E AN ERROR OCCURRED GETTING THE DEFINITION OF THE WORKSTATION "MASTERAGENTS". THE WORKLOAD BROKER SERVER IS CURRENTLY UNREACHABLE
WA-100620 THE JOBLOG IS NOT RETRIEVED WHEN THE MDM AIX AND EXTERNAL FTA ARE CONFIGURED IN SSL
WA-100624 CONFIGUREDB ON WIN MSSQL ENDS SUCCESSFULLY EVEN IF THE LAUNCHUPGRADEIWSDB SCRIPT FAILS ON UNIX
WA-100647 MSSQL NEW DRIVER FAILS
WA-100655 WINDOWS AGENT FRESH HANGED ON 9.5 FP 5
WA-100662 CONFIGUREDB FAILS ON SERVER INSTALLATION
WA-100697 BROKERSSL DOES NOT WORK IF LIBERTY IS CONFIGURED WITH AES PASSWORD ENCRYPTION
WA-100737 UPDATING FTA 9.5 FP4 TO 9.5 FP5 FAILS ON SOLARIS OPTERON
WA-100817 UNISTALL FAILS ON WINDOWS
WA-100852 INSTALLATION WITH PROPERTIES FILE FAILS BECAUSE THERE ARE TOO MANY SPACES AFTER HTTPSPORT
WA-100856 DYNAMIC JOBS RUN TWICE
WA-101027 DBLIGHT TOOL WITH NEW DRIVER WITH MSSQL FAILS WITH RC=13
WA-101078 UNEXPECTED MESSAGES DURING CONFIGUREDB ON AIX
WA-101135 REMOTE BROKER RESOURCE CLI FAILS WITH SSL EXCEPTIONS ON DOCKER
WA-101219 KERBEROS JM TRACES STORE PASSWORD IN CLEAR TEXT
WA-101229 NOCLASSDEFFOUNDERROR OCCURRED EXECUTING AN EJB JOB ON 9.5 AGENTS
WA-101249 LOGGER INITIALISATION FAIL FOR CYBERARK
WA-101304 KERBEROS TRACE UNABLE TO WRITE ON THE SPECIFIED PATH RETURNING GARBAGE TO BROKER
WA-101338 WSS SCAN VULNERABILITY _ TWS95FP5 IBM - LOG4J-1.2.17.REDHAT-3.JAR
WA-101486 CONFIGURE NEW ONEDB PARAMETER FOR SERVER AND DWC ON DOCKER ENVIRONMENT
WA-101513 DWCINST PERMISSION DENIED ON WINDOWS UPDATE
WA-101517 DWC AND MASTER INSTALLATION FAILED WITH ONEDB DATABASE
WA-101557 DA AGENT NOT WORKING WITHOUT USER WHEN KERBEROS IS ENABLED
WA-101576 JOB RUN STATISTICS REPORT ON ONEDB THROWS ERROR
WA-101621 DYNAMIC AGENTS DO NOT SEND "FILECREATED" EVENTS TO EVENT PROCESSOR WHEN SSL IS ENABLED
WA-101629 WSS SCAN VULNERABILITY-TWS 95FP5 IBM - GSON-2.8.5.JAR , GSON-2.8.2.JAR
WA-101667 KERBEROS AUTH METHOD NOT DISPLAYED IN JOBLOG WHEN THE AUTHENTICATION FAILS
WA-101712 AGENT-SERVER CONNECTION ISSUES ON JOBS SUBMISSION
WA-101795 UPDATE JDK FOR HP

Problems fixed in HCL Workload Automation Fix Pack 4 for version 9.5.0

This section lists APARs and internal defects solved by Fix Pack 4.

Table 3. APARs addressed in Fix Pack 4
APAR ABSTRACT
IJ07357 EVENT 153 IS NOT LOGGED FOR MDM JOB STREAM
IJ08046 ORACLE PERFORMANCE IMPROVEMENT DURING FINAL PROCESSING
IJ11514 AWSUI0833E AND AWSJSY514E ERRORS OCCUR ON WORKLOAD MONITOR ACCESSING DBCS NAME TRIAL/FORECAST PLAN
IJ11561 "RUN" AND "EDIT" BUTTONS GO OUTSIDE OF BROWSER AREA ON MONITOR JOBSTREAMS/JOBS WINDOW.
IJ17450 JOBPROP IAWSTZ IS NOT BEING INTERPETED AS THE SCHEDULE DATE IF A SCHEDULE IS SUBMITTED WITH PRIORITY 0 AND THEN RELEASED
IJ17474 DBCS PROMPT MESSAGE TEXT IS GARBLED ON DWC
IJ18828 JOB_STREAM_IDENTIFIER and DEP_JOB_STREAM_IDENTIFIER ARE ALWAYS IDENTICAL EVEN WHEN IT INVOLVES DIFFERENT JOB STREAM IN THE DEPENDENCY
IJ20225 USER WANTS TO CREATE A SORT FEATURE IN SWAGGER API
IJ20732 TIMEZONE FIELD IS "NONE" ON MANAGE WORKLOAD DEFINITIONS (DWC) WHEN VIEWING THE JOBSTREAM
IJ20779 CENTRALIZED UPDATE ON WIN CPUS ARE FAILING BECAUSE OF A MISMATCHBETWEEN THE VALUE RETURNED FROM SSMAGENT AND TWSREGISTRY.DAT
IJ21061 JOBSTREAM "CREATE LIKE SELECTED" ON WORKLOAD DESIGNER DOES NOT WORK.
IJ21596 CROSS D/Z DEPENDENCY BEHAVIOR IN THE TIME WINDOW 01:00 - 02:00
IJ23360 WAS IS CREATING CORE FILES. APPSERVMAN RESTARTS WITHOUT ISSUE AND NO APPARENT EFFECT ON FUNCTION
IJ23565 DEADLOCKS OCCURING DUE TO PARALLEL CANCEL OF DIFFERENT INSTANCES OF THE SAME JOB STREAM WHEN JOBS HAVE OPENS DEPS
IJ23755 A WRONG FULLYQUALIFIEDNAME ON A DYNAMICAGENT COULD CAUSE OUTOFMEMORY ISSUES ON THE MASTER.
IJ24075 TWS MIRRORING ON OPENS WITH QUALIFIER CONTAINING A BACKSLASH
IJ24341 RETRIEVE JOBLOG BEHAVIOR WHEN SET BEHINDFIREWALL ON ON FTA
IJ25131 MIRRORING SCHEDULE STATUS DOES NOT REFLECT THE CORRECT STATE VERSUS THE JOB STATUS
IJ26357 IWSHOME/CONFIG/IWA_INIT_IWSUSER SCRIPT HAS NOT BEEN UPDATED FOR 9.5.0
IJ26950 MIRRORING - DEPENDENCIES NOT UPDATED IN CASE OF DATABASE DEADLOCK
IJ28142 JOB FAILED WITH EXIT STATUS: 127 SCRIPT.SH: CANNOT EXECUTE [TEXT FILE BUSY]
IJ28464 API CALLS: COMPLEX FILTERS NOT WORKING
IJ28475 COMPATIBILITY OF IWS 9.5 WITH SUSE LINUX ENTERPRISE SERVER 15 SP2
IJ28561 DWC 9.5 FP2 OBJECT VERSION HISTORY NOT VISIBLE
IJ28666 ORACLE EBS JOB PARAMETER IS NOT PASSING CORRECTLY FROM IWA TO ORACLE
IJ28693 REPTR -POST -DETAILS RESULT SHOWS INCORRECT ACTUAL RUN TIME VALUE AND FORMAT
IJ28925 BOOKMARK ICON DOES NOT GREY OUT WHEN ARCHIVED PLAN IS SELECTED
IJ28944 MAILMAN TIMEOUT FOR SYMPHONY TAKING LONG TIME TO BE PROCESS IN THE BRIDGE
IJ28947 TWS 9.5 FP2 WORKLOAD APPLICATION TEMPLATE EXPORT IN XML DEFINITION RANDOMLY -HARDCODED- VALUES INSTEAD OF VARIABLES
IJ29098 JOB MANAGEMENT PLUGIN JOB FAILED WITH THE ERROR MESSAGE AWKJMJ043E IF ITS MONITORED JOB ABEND
IJ29119 IWS 9.5.0.1 EXECUTABLE JOB DOES NOT DISPLAY NOR CLONE PARAMETERS IN DWC WORKLOAD DEFINITIONS
IJ29545 COMPATIBILITY BETWEEN IWS AND INFOSPHERE INFORMATION SERVERCOMPATIBILITY BETWEEN IWS AND INFOSPHERE INFORMATION SERVER
IJ29791 RESTART_STARTCOND JOBS ABEND WITH MISSING OR WRONG CREDENTIALS
IJ30074 PARAMETER WITH A "NULL" VALUE IS NOT PASSED TO ORACLE WHILE SUBMITTING EBS ORACLE JOBS - SHOWS BLANK INSTEAD
IJ30187 MDM LIBERTY TERMINATES WITH JAVACORE WHEN LOADING LARGE NUMBER OF JOBS IN ALTERNATE PLAN
IJ30295 PERSONALIZED REPORTS RETURN ERRORS ON IWS/DWC 9502 USING ORACLE19C
IJ30299 COMPOSER EXTRACT OPTION FOR USERS/USER DOES NOT WORK CORRECTLY AS DOCUMENTED WHEN USED ALONG WITH "PASSWORD" OPTION IN 9.5
IJ30356 TWS 9.5 WA_PULL_INFO DID NOT COLLECT SYSTEM_INFO DIR WHEN EXECUTED FROM NON -ROOT USER
IJ30367 ADHOC JOB SUBMITTED THROUGH DWC SHOWING AS NULL IN DB TABLE
IJ30380 ZCENTRIC AGENT: JOBMANAGER TERMINATES WITH SIGNAL 6 ON AIX PLATFORM
IJ30421 DATETIME FORMAT FOR REST CHANGED BETWEEN 9.5.0.1 AND 9.5.0.3
IJ30491 STERLING PLUGIN DOESN'T WAIT STERLING JOB PROCESS EXECUTION COMPLETION
IJ30661 IN IWS 9.5 JOB STREAM LATE EVENTS(163) ARE FORMATTED DIFFERENTLY FROM THE WAY THEY WERE IN 9.3.x
IJ30692 TWS LOG FILE START TIME NOT CHANGED AFTER SOD CHANGE
IJ30714 ADHOC PROMP ON SCHEDULES ARE NOT NOT CHECKED AGAINST THE SCEDULER FOLDER SECURITY
IJ30755 SPECIAL CHARACTER SEMICOLON (;) IGNORED IN CREATION OF NEW EVENT RULE IN DWC 9.5 FP02
IJ30756 THE RECOVERY ACTION ON DWC AGAINST THE OBJECT LIKE WORK STATION CLASS OR RESOURCE USING THE VERSION FEATUREFAILS
IJ30771 ZCENTRIC AGENT INSTALLATION FAILS ON SOLARIS SPARK SERVER WITH PREREQUISITE CHECK
IJ30791 UPDATE JAVA JRE
IJ30794 STACK OVERFLOW VIA TIS_CODESET
IJ30803 PREDEFINED SUBMIT JOBSTREAM FAILS WITH AWSJSY508E
IJ30805 ZCENTRIC SSL PEER NAME VALIDATION
IJ30827 JOB STREAM NOT LOADING INTO PLAN
IJ30895 FILE MONITOR EVENT RULE NOT TRIGGERING
IJ30902 9.5 COMPOSER VALIDATE RETURN AWSJDB810E
IJ30909 AWSJSY508E ERROR MESSAGE WHEN ANSWERING ADHOC PROMP ON A JOB IN A FOLDER
IJ30920 DWC SHOWS ERROR WHEN DISPLAYING JOBLOG FOR THE FIRST TIME
IJ30949 CREATE LIKE BUTTON NOT WORKING IN DWC FOR ORACLE E-BUSINESS JOB DEFINITION ON DA WITH FTA
IJ30951 TWS 9.5 FP3 FILE TRANSFER JOB ISSUE USING "WINDOWS" PROTOCOL
IJ30952 TWS 9.5 FP3 FILE TRANSFER JOB ISSUE - USER AUTHENTICATION ERROR
IJ30957 TWS 9.5 JOBSTREAM STARTCOND COULD FAILS ON ON-PREMISE & DOCKER WHEN A GW IS PRESENT. FAILURE ALSO IN JS SUBMIT PLUGIN
IJ30991 AWKAZR008E GET VIRTURAL MACHINES FAILED IWS 9.4 FP5
IJ31007 TWS ON RED HAT 8.2 AND UPPER LEVEL COULD FAIL AT START TIME WITH ERROR AS (SU: CANNOT OPEN SESSION: MODULE IS UNKNOWN)
IJ31055 TWSGATEWAY NAME THAT CONTAINS "-" DID NOT WORK.ISSUE ALSO ON CERTS CUSTOM IF CNAME CONTAINS "-".GW AND AGENT DID NOT TALK
IJ31130 TWS 9.5 AD HOC PROMPT DISPLAY ON PROMPT VIEWS DISABLED BY DEFAULT FOR SECURITY REASONS
IJ31169 FILEWAILEWATCH ERROR DUE TO MISSING MOZART DIRECTORY
IJ31219 SPOOL LIST NOT GETTING CAPTURED IN TWS LOGS
IJ31522 9.5 FP3 FILETRANSFER PLUGIN DOES MAKE FILE NAMES CASE SENSITIVE ON WINDOWS PLATFORMS
IJ31632 "CENTRALISEDAGENT UPDATE" PLUGIN JOB FAILS TO UPDATE AGENTS
IJ31838 NO OPTION TO SELECT THE NUMBER OF DAYS IN MANAGE PREDEFINED REPORTS --> JOB RUN HISTORY REPORT DURING INITIAL REPORT CREATION
IJ31850 SUCC IBMI JOBS FAILS ON IWS (CEE9901 AND MCH3601 IN OUT.FILE)
IJ31865 JOBS FAILING ON A 9.5 X-AGENT RUNNING ON SUNOS 5.10
IJ31867 95- RMSTDLIST SCRIPT FAILING WITH IWS 9.4 FP07 AND IWS 9.5 FP03
IJ31869 TWS 9.5 FP3 MDM WINDOWS CRASH ON BROWSEJOBLOG AGAINST EXTERNAL AGENT WHEN SSL IS ON. ISSUE WITH OPENSSL 1.1.1G
IJ31907 LIBERTY JAVACORE BY TWSPLANAPI:INI:MAE_ADDSCHEDULEINSTANCE
IJ31991 VARTABLE LIST DATE VALUE CHANGED TO FUTURE YEAR IF SWITCH OR TANGLE BETWEEN TWO OPENED TABLE VIEWS IN THE WORKLOAD DESIGNER
IJ32086 WAT: THE WS IN FILE MONITOR EVENS ARE NOT NOT MAPPED IN THE DEST ENV (AWSJCO026E IN SOME CASES)
IJ32099 ERROR MIGRATING TWS DATABASE OBJECT (JOBSTREAMS) USING DATAIMPORT SCRIPT
IJ32303 AFTER THE STREAM NAME IS CHANGED, THE EVENT RULE WHICH HAS THE ACTION SUBMITTING TO THE STREAM DOES NOT WORK AFTER JNEXTPLAN
IJ32333 TWS 9.5 DWC REPORT FROM PLAN COULD HANG WHEN BIG REPORTS WITHOUTANY FILTERS ARE EXECUTED
IJ32526 THE SETTING OF DWC 9.5 WHICH WAS INSTALLED USING NON-ROOT USER WILL BE OVERRIDEN IF UPGRADE TO FP3
IJ33146 BROKER JOBS GO ABEND EVEN WITH EXIT 0 WITH WLP BOUNCE
KB0090396 API - GET - ISSUES WITH VARIABLES NOT GETTING PICKED UP IN API JOBS https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0090396
KB0091187 THE LICENCE CAN BE LOCKED BEFORE THE GRACE PERIOD WITH AWKFLX004E MESSAGE https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0091187
Table 4. Fixed Defects
DEFECT ABSTRACT
WA-91812 UNEXPECTED ERROR ESTABLISHED A CONNECTION TO THE REMOTE SERVICE AFTER JONMANAGEMENT PLUGIN SUBMISSION
WA-91838 INSTALL_TEMPLATES FOLDER SHOULD BE NOT CREATED AFTER A FRESH DWC INSTALLATION
WA-92380 UPDATE TIMEZONE TO VERSION 2021A
WA-92446 XCOMPATIBILITY OF IWS 9.5 WITH SUSE LINUX ENTERPRISE SERVER 15 SP2
WA-92446 UNEXPECTED ERROR MESSAGE AFTER WAPPMAN -EXPORT
WA-92575 GROUP IS SUCCESSFULLY UPDATED WHEN EDIT (ALL TYPE REPORT) ONLY BUT NOT ABLE TO UPDATE WITH SHARE BUTTON BECAUSE 'AVAILBLE GROUPS' TEXT BOX IS NOT PRESENT IN PREDEFINED REPORT ON DWC FP3
WA-96192 OUTPUT CONDITION IN "CONDITION MET" CONSIDERED AS SUCCESS COND

Problems fixed in HCL Workload Automation Fix Pack 3 for version 9.5.0

This section lists APARs and internal defects solved by Fix Pack 3.

Table 5. APARs addressed in Fix Pack 3
APAR ABSTRACT
IJ02098 The event rule monitoring file creation fails on Windows dynamic agent when the file path is too long
IJ06494 Run cycle group within a job stream is not picking up the default calendar
IJ07966 planman resync command fails with messages: AWSJCL075E Symphony file load has failed... AWSJDB818E an internal error has occurred SQLCODE=-302
IJ14395 Carryforwarded jobstreams in hold state that were submitted with an alias may cause a DB deadlock when passing to ready state
IJ16181 rep1 command creates core files
IJ18246 composer datamigrate fails if runcycle name is long
IJ18307 Job fails with the following message"database field exceeds column bounds"
IJ18482 REST API not working properly when creating an agent pool
IJ18508 put /model/jobstream/{jobstreamId}
IJ18697 API /model/jobdefinition/header/query do not include @object-count" in the response header
IJ18750 Workload template migration 'kill if deadline expires' option automatically selected
IJ19659 TWS/OV/customize script needs to be updated to support data_dir
IJ19735 File System event rules do not work
IJ20428 Jobs complete successfully on PowerCenter side, but IBM Workload SchedulerHCL Workload Automation status is error
IJ20952 WAS is crashing due to a stack found in Java stack frames in libtwsplanjni.so
IJ21126 Sometimes submitted job streams cannot be added into the plan or remain in add state
IJ21530 tws_env.sh should add system paths at the end of library paths loaded by an application.
IJ21592 RESTART_STARTCOND ends in error if the same job stream name with a future valid from date is added to the database
IJ22679 rmstdlist script may cause the removal of some directories or files that contains spaces
IJ22680 On AIX systems, the following error is returned when editing jobs: AWSJSY501E Incorrect data was detected while performing the Symphony plan operation "rerunJobInstance".
IJ22904 Adding or modifying security domains containing just "exclude" filter in common, causes the filters to b removed
IJ23032 File transfer job using SSL to transfer files is leaving established SSL connections hanging between the two systems
IJ23084 Javacore encountered when running JnextPlan
IJ23160 EQQX550 no variable duration or deadline was specified with z/OS engine
IJ23518 Ddriven always send an xml file with jmgr:resourcegroup item list greater than 0 even when no changes are present
IJ23799 Missing initial version information for objects in the Workload Designer after upgrading
IJ23845 Output conditions are not properly evaluated when a dynamic job is killed on dynamic agent
IJ24240 File processed by file transfer job is always recognized as a 0-byte file
IJ24378 Windows protocol (SMB1) is not working with Remote command 9.5.01 plug-in. Download from Automation Hub plug-in version 9.5.0.4, which works correctly on Windows operating systems.
IJ24540 Launching a Database Job using dbStatement, the statement is executed twice.
IJ24734 Deadlock records are stored into logs while deleting old plan from database
IJ24770 Wrong error message returned by composer validate command
IJ24806 conman rerun command is triggering an additional instance on "repeat range" jobs with at dependency, removing the rerun operation
IJ24854

When a job stream uses several run cycles if the r un cycle that use FDIGNORE is not the first (in alphabetical sorting), it is not added to the plan.

IJ24888 On the agent side, received messages AWSBDW303I and AWSBDY116I and no documentation available for those messages
IJ25063 When a remote exception is thrown from the EJB, the job ends in successful status instead of ending in error
IJ25089 While using Rapid7 network firewall protection, Workload Broker abruptly disconnects.
IJ25137 Old logs files being updated after FINAL in 9.5
IJ25158 tws_env.cmd does not set Java home
IJ25267 WebSphere Application Server Liberty Base crashes on backup master domain manager while submitting a job stream with a recovery run
IJ25371 Readme documentation for Docker containers does not detail how to get the correct image tag
IJ25389 Version 9.5 FP 2 conman poor performance for sj and ss commands
IJ25411 Symphony file load taking a long time to complete for 9.5 FP 2 mirroring resync issue
IJ25450 PowerCenter jobs appear to complete on PowerCenter, but remains in exec in IBM Workload SchedulerHCL Workload Automation
IJ25451 Importing calendars, the dates are shifted by -1 day, only when the timezone is different from UTC
IJ25487 batchman is not correctly managing the error AWSBHT018E when a job is modified on the fly and task string or logon user has changed
IJ25488 The checksync job operation ends abruptly in error
IJ25535 API procedure always returns a success message, but no list is provided
IJ25537 Wrong time range definition for the job stream and run cycle.
IJ25550 Version 9.5 and later: MDM installation fails on AIX with native memory error or no clear evidence
IJ25679 conman format error
IJ25702 Java plugin JSR352 at Version 9.5 FP 2 plug-in does not work with master domain manager lower than Version 9.5 FP 1
IJ25914 Successor jobs not released after conditional dependency has been met on dynamic agent while FINAL js is running
IJ25970 REST API is not adding variable table to the submitted job stream
IJ26011 In version 9.5 FP 2 backup master, the CPU filter in security settings does not work
IJ26023 TWS 9.5 FP2 forecast plan did not include jobs and job streams defined on folder. only root jobs and job streams are included into forecast plan
IJ26099 The dash (-) symbol is not accepted when installing Version 9.5 FP 2 and using command line option --wapassword.
IJ26190 altpass command does not allow us to push a new password
IJ26191 composer validate fails if the user is specified without workstation field
IJ26338 Version 9.5 FP 2 error when validating a composer file with an existing user id that contains encrypted password
IJ26347 When updating calendars via composer changing days causes all days in the calendar to go back one day prior than expected
IJ26707 File transfer job type file permission changed in Version 9.5
IJ26846 systemout.log file fills up when the CPU is set to ignore.
IJ26881 Password not required for upgrades when using twsinst.vbs -u command
IJ26964 composer not showing proper results when using filter to show job streams associated with calendars
IJ26970 Owner of root-owned files in tws/bin changed to twsuser if --data_dir value is the same as the tws directory created under --inst_dir
IJ27011 Event action mailsender subject is garbled with quoted-printable encoding and is not readable
IJ27254 Carryforward not taking forward ABEND job at second run (rerun)
IJ27644 File transfer jobs to z/OS mainframe fail when used with upload in text mode
IJ27688 Report output in .csv format is limited to 10.000 lines
IJ27720 High CPU consumption for jobmanager process while checking for the existence of many files to resolve open dependencies
IJ27843 A new option is needed in Liberty instance start script to clear the OSGI cached data
IJ28339 CIT scan issue for dynamic agents at Version 9.5.0.2
IJ28419 Using $THISCPU variable inside the security file, makesec command deletes the whole row
IJ28443 The auth_ad_config.xml comments ref to the wrong name of wauser_variable.xml
IJ28452 When running command exportserverdata, the Server.properties file already created with root as owner by default
IJ28771 DYNAMIC AGENT FREQUENTLY GOES OFFLINE
IJ28910 Error tracking parameter set to N when adding operations using REST APIs
IJ29127 SQL Error during upgrade from Version 9.4 FP6 to Version 9.5.0.2
IJ29406 The checksync job operation ends in error with return code = 8 and results in garbled characters in the plan
Table 6. Fixed Defects
DEFECT ABSTRACT
WA-87117 PowerCenter job failure on Linux PPC
WA-87179 Missing error message submitting an AWS job
WA-87180 Incorrect job status submitting an AWS job
WA-87202 Missing validation saving an AWS job
WA-87946 Add a description that explains to use / (slash) in TableSpace properties in ConfigureDB for MsSQL databases.
WA-87948 Installation fails due to the encrypted passwords and the = (equals) sign that truncates values in the properties file.
WA-88023 If db_port value is left blank, the default value is 50000 for all databases.
WA-88046 Wrong description of the path format to be used in the agents' reinstall option.
WA-88049 Improve the MsSQL template to make the IWS_TS_PATH parameter more understandable and lead users to write the correct value.
WA-88107 WLP_INSTALL_DIR property is missing in the ConfigureDB property file for windows.
WA-89912 Wrong schema location for WebServices and OSLC plug-ins
WA-90285 Missing message when a Sterling job remains indefinitely in HELD status
WA-91560 Whitesource vulnerability log4j-1.2.17.jar on Cognos plugin - Library log4j-1.2.17.jar is to be updated with version "1.2.17.redhat-3"
WA-91561 Whitesource vulnerability log4j-1.2.17.jar on ws-JobExecutor plugin - Library log4j-1.2.17.jar is to be updated with version "1.2.17.redhat-3"
WA-91563 Whitesource vulnerability httpclient-4.5.11.jar on AWS JobExecutor plugin - Library httpclient-4.5.11.jar is to be updated with version 4.5.13
WA-91564 Whitesource vulnerability org.eclipse.paho.client.mqttv3-1.0.2.jar on MQTT JobExecutor plugin - Library org.eclipse.paho.client.mqttv3-1.0.2.jar is to be updated with version "1.2.5"
WA-91565 Whitesource vulnerability xercesImpl-2.9.1.jar on Cognos JobExecutor plugin - Library xercesImpl-2.9.1.jar is to be updated with version "xerces:xercesImpl:2.12.0.SP3"
WA-91681 Wrong schema location for OSLC Provisioning plug-in
WA-91719 Whitesource vulnerabilities for TWS PowerCenterJobExecutor

Problems fixed in HCL Workload Automation Fix Pack 2 for version 9.5.0

This section lists APARs and internal defects solved by Fix Pack 2.

Table 7. APARs addressed in Fix Pack 2
APAR ABSTRACT
IJ08195 cmdLauncher program in TWS/BIN can allow a not root user to launch commands as root
IJ11908 IWS dependencies are removed when upgrading a runcycle in a job stream before the final run
IJ09112 Canceling jobs and job streams, CTRL-c is considered as yes answer to the cancel confirmation question
IJ12793 On DDM, the schedule timezone specification for UNTIL is not enforced, and it uses the underlying timezone of the processes
IJ13551 Mirroring defect on IWS/DWC 9.4.0 FP05. For job transitions fence to ready, the status is not properly reflected in the DWC
IJ16123 APAR IV98210 correction causes significant plan mirroring delays when a spike of mirroring generated events occur
IJ17247 File transfer jobs to z/OS with ssh protocol truncate files with lrecl greater than 128
IJ17325 Planman checksync can fail if OPENS dependencies from previous days are incorrect in the database
IJ17348 Composer validate with syntax flag fails on dependencies
IJ17407 HTWGT0009E file does not exist error when running jobs on Peoplesoft agents
IJ17670 SENDEVENT event rule fails in 9.5 at encrypting password
IJ17722 POST /{ENGINE}/PLAN/{PLANID}/JOBSTREAM/ACTION/ADD_JOBSTREAM? Rest API gets an error using VARIABLESTOBESUBSTITUTED
IJ17723 Rest API "GET" ON A RESOURCE returns a blank value in defaultAvailability f
IJ17795 The swagger codegen tool returns an error on EVENTRULEFILTER
IJ17791 EJB job status is incorrect in 9.4.0.06 plug-in ported from 9.5.0.00
IJ18008 Join condition compiler.c case TS002519455
IJ18045 The broker on DDM gets unlinked (and the agents will not be linked too) after the start up
IJ18226 Return code 127 for all actions called through GENERICEVENTPLUGIN
IJ18247 "REPTR" command looks for SYMNEW/SYMPHONY in old directory <TWAHOME>/TWS
IJ18285 Importing Workload Application, schedule version is not created
IJ18312 Conman SJ/SS returns elapse time as 00:60 instead of 01:00, if actual elapse time is between 00:59:01 and 00:59:59
IJ18334 Vaerbose message every job
IJ18424 TWS cumulative doc APAR 9.5
IJ18804 MAILBOX.MSG corruption causes MAILMAN failure
IJ18837 Salesforce job succeeds on SF side, but it is in ABEND on IWS side
IJ19134 In a remote engine, the shadow job status is not updated
IJ19621 Conman submit commands fail with AWSBHU710E when into argument uses a job stram ID
IJ19633 Job stream repeat is not working when EVERY is defined directly at run cycle group level in job stream definition
IJ19649 TSAMP on TWS 9.5 FP1 scripts are not present into TWS 9.5 FP1 installation
IJ19654 Runcycle group within a job stream is not picking up the default holidays calendar
IJ19944 WORKSTATIONINPLANAVAILABILITYINTERVALS is missing in the PLAN/CURRENT/WORKSTATION/QUERY call
IJ20064 Upgrade of DB2 failed upon executing configureDB.sh for IWS 9.5 upgrade
IJ20065 ITM integration does not work in IWS v. 9.5
IJ20119 WLB jobs run twice in MS-Prod
IJ20175 DWCINST.SH fails with liberty version error if LANG=JA_JP.UTF-8. Same for ENGINE
IJ20351 Date format on Rest APIs has changed since 9.3 and is currently formally incorrect
IJ20446 9.5 installation: home variable not resolving properly on windows agents
IJ20538 File transfer jobs does not run remotely if wildchars are used
IJ20586 twsinst cannot be used with new msvc versions
IJ20834 Issue in submitting job streams from event rules
IJ21081 Composer replace does not return expected syntax error
IJ21082 Event rule action to trigger sbs for event sent through a gateway fails with UNAUTHENTICATED error
IJ21156 Setting the trace mode for TWSProfile to tws_broker_all showsthat the same member of a POOL workstation is selected for a file check test defined for the POOL.
IJ21301 Installing v. 9.5 it is necessary to have the installation directory empty, while it was not required in past IWS/TWS versions
IJ21346 Mirroring improvement for file dependencies management after the resync operation
IJ21348 Mirroring improvement on the cancel operation management
IJ21480 On SAP jobs, the mail address field is nullified when using RERUNSTEP for a job
IJ21519 Tables in PLN schema are carrying over too many rows
IJ21775 IWS processes do not start automatically using the START_TWS.SH script after a failover
IJ22079 9.5 documentation on Docker run/Docker compose is insufficient to have a zcentric container restarting correctly
IJ22223 FILE_STARTCOND did not work with FOLDER
IJ22431 Check prereq fails on CentOS Linux release 7.4.1708 (Core)
IJ22534 Adding a job stream definition as dependency that matches a job or job stream that does not exist, the 'The object "js=MDM95#RN_TEST_EXT_DEP2" already exists' error is returned.
IJ22635 JOBMAN core dump during OPENS file check
IJ22828 ORA-00955 error when upgrading to IWS 9.5.0.01 using an Oracle database
IJ23003 When a variable is used within a job, it is not possible to add an application by using Rest API
IJ23561 Processes hold the files, not of the current day, in the stdlist/logs directory
IJ24196 Event rule of type "update event" doesn't work.

Problems fixed in HCL Workload Automation Fix Pack 1 for version 9.5.0

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

This Fix Pack includes a number of fixes for internal defects found by the verification team that mainly cover the following product capabilities: installation, auditing, and mirroring.

APAR ABSTRACT
IJ16502 Symphony corruption causes a batchman crashing.
IJ13958 CHECKPREREQ command fails on CentOS Linux 7.4.1708
IJ16233 Extra backward slashes "\" are added each time a customer edits the event rule.
IJ16230 Wildcards on DSNAME causes a FTP job failure.
IJ15085 A local user without root privileges can write files in the file system as root.
WA-80434 TaskLauncher continues to monitor a windows job, even if the job completed.
IJ12956 In case of Japanese engine name, performing a job definition search on rerun job, no result is returned. The issue occurs only on IE11 browser.
IJ15789 Running the CURL command from an Unix machine causes a "CURL: FAILED INITIALIZATION" error.
IJ14140 In case of SSL connection issues, the domain manager mailman process continues to try to establish a connection.
IJ14282 Jobs are randomly killed with exit code 143.
IJ14630 Event rules occasionally submit the wrong job stream.
IJ14147 Upgrading to version 9.4.0.3, the operating unit is no longer getting populated in OLFM.
IJ11203 Remote command job containing the "£" char stays in EXEC hang due to RXA issue.
IV93833 Remove meaningless messages from systemout.log.
IJ11152 "HOW-MANY=0" returns blank result on the plan object query rest API.
IJ11230 The FTA centralized upgrade fails when upgrading from version 9.4 fix pack 3 to later versions.
IJ07067 Job stream, with scheduled time before DST time change, starts before the scheduled time.
IJ08161 Improve the jobmanager.ini.bak file creation mechanism.
IJ07385 Multiple vulnerabilities have been found in OpenSSL.
IJ07377 Zcentric agent does note reconnect after rebooting an Unix system where the agent is installed.
IJ06229 Installing a 9.4 master domain manager, a MASTERAGENTS workstation is automatically created. Deleting the MASTERAGENTS CPU and installing a dynamic domain manager, a new MASTERAGENTS workstation is automatically created but it is linked to the wrong host ID and causes an error.
IJ04537 Sometimes the twsinst.sh script check fails even if there are no problems.
IJ04230 Cancelling pending job streams takes more time if batchman is not performing activities.
IV83963 After a file transfer job has run on a windows environment, the deletion of the source file fails.

Backward compatibility

This fix pack delivers support for scheduling objects in folders, including workstations. When monitoring workstations from a back-level agent workstation, the output displays the workstation unique identifier and not the workstation name for those workstations that were defined in folders different from the root folder. To identify the corresponding workstation name, run the conman command using the showid filter, showcpu ;showid, from an updated agent workstation.

Known limitations and workarounds

The following are software limitations and workarounds that affect HCL Workload Automation version 9.5.0 Fix Pack 5 and previous versions.

9.5 Fix Pack 5

Some field names are longer due to folder support
The integrations described in manual Integrating with Other Products might be impacted by the new field size for some scheduling objects. The size of the fields listed below has changed from 16 to 817 bytes with the introduction of folder support. The impacted fields are:
  • workstation
  • schedCpu
  • origSchedName
  • schedName
  • jobCPU
  • prompt
  • needs

Each of these fields in Workload Automation events will be reported into the BmEvents.conf file with a length of 817 bytes. If no folder were specified, the field will be printed as 817 with blank values.

No Monitor Operator Messages available when updating with Centralized Update process with the event processor configured in SSL mode
When running the Centralized Agent Update from version 95 Fix Pack 4 to version 95 Fix Pack 5 with the event processor configured in SSL mode, no Monitor Operator Messages are displayed for either fault-tolerant agents and dynamic agents.
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": "2021-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": "2021-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.

An agent for z/OS (also known as d-driven agent) might encounter problems connecting to master domain manager or dynamic domain manager.
The error logged in Liberty messages.log file is no cipher suites in common.

Workaround

To allow communication between the components, perform the following steps on the master domain manager or dynamic domain manager:

    • Create a backup copy of the file <TWA home>/usr/servers/engineServer/wa.java.security and remove the original file.
    • Create a backup copy of the file <TWA home>/TWS/JavaExt/jre/jre/lib/security/java.security and remove the original file.
    • Restart the Liberty process.
Communication issues between dynamic domain manager and Z controller
To allow communication between dynamic domain manager and Z controller, perform the following steps on the dynamic domain manager:
  • Create a backup copy of the file <TWA home>/usr/servers/engineServer/wa.java.security and remove the original file.
  • Restart the Liberty process.
Problem when installing a master domain manager pointing to a Local License server
If you plan to install the Flexera server on your local network, ensure you import the Flexera certificate on the master domain manager. You can perform this operation using one of the following methods:

Retrieving the certificate and storing it on the master domain manager

Perform the following steps:
  1. Open the 443 port for allowing communication between the master domain manager and the on-cloud Flexera server.
  2. Install the master domain manager with the serverinst command as described in Typical installation scenario. Specify the license server ID parameter (--licenseserverid), but do not specify the license server URL parameter (--licenseserverurl). This ensures the master domain manager automatically connects to the default on-cloud license server.
  3. Import the certificate from the on-cloud Flexera server to the master domain manager using the following command:
    keytool -importcert -file server.certs 
    -keystore usr/servers/engineServer/resources/security/TWSServerTrustFile.jks -alias "server_alias"
  4. Stop and restart WebSphere Application Server Liberty Base.
  5. Use the optman command to modify the licenseServerUrl property to point to the Flexera Local License Server. This option takes effect immediately. For more information about optman options, see Global options - detailed description.

Importing the Flexera certificate as a custom certificate

Perform the following steps:
  1. Create a subfolder named additionalCAs on the workstation where you plan to install the master domain manager.
  2. Generate the certificate on the local Flexera server.
  3. Export the certificate using the following command:
    keytool -exportcert -keystore custom_path/keystore.jks 
    -alias server-alias -file custom_path/certificate.crt
  4. Copy the certificate to the additionalCAs folder on the workstation where you plan to install the master domain manager.
  5. Use the serverinst command to install the master domain manager and retrieve the Flexera certificate from the additionalCAs subfolder. Consider the following example:
    ./serverinst.sh --wauser wa_user --acceptlicense yes --dbname db_name --dbuser db_user --dbport db_port 
    --dbhostname db_hostname --rdbmstype db_type --dbpassword db_passowrd --wapassword wa_password --wlpdir wlp_dir  --licenseserverid license_server_ID 
    --sslkeysfolder certificate_files_path --sslpassword keystore_truststore_password --licenseserverurl license_server_URL
A domain manager containing also a mailman server might display an incorrect status in the Dynamic Workload Console
In some specific situations, for example when IBM Workload Schedulerhas been stopped, the domain manager might appear unlinked from the Dynamic Workload Console, while it is correctly linked. To work around this problem, manually link the domain manager from the Dynamic Workload Console.
Incorrect dependency status after modifications on dependencies
If you manually add and remove several times the same dependencies from a job or job stream in the plan, their status might not be always accurate. This mismatch might occur when replicating plan data in the database, the process also known as mirroring. However, the status of the job and of the job stream containing those dependencies is accurate. You can solve this problem by issuing a planman resync command.
MSSQL database configuration error on Windows operating systems
When configuring the MSSQL database on a master domain manager installed on a Windows operating system, you might encounter the following error message, which causes the configuration process to fail:
WAINST087E No suitable drivers found
To work around this problem, perform the following steps:
  1. Browse to the launchUpgradeIWSDB.bat file, located in TWS_image\dblighttool.
  2. Add the DB_HOME_DIR:"=%\mssql-jdbc-9.4.0.jre8.jar string to line 23 in the launchUpgradeIWSDB.bat file:
    set CLASSPATH="%PACKAGE_DIR:"=%\jars\IWSDBUpgradelib.jar";
    "%DB_HOME_DIR:"=%\ojdbc6.jar";"%DB_HOME_DIR:"=%\ojdbc5.jar";
    "%DB_HOME_DIR:"=%\ojdbc7.jar";"%DB_HOME_DIR:"=%\ojdbc8.jar";
    "%DB_HOME_DIR:"=%\ojdbc14.jar";
    "%DB_HOME_DIR:"=%\classes12.zip";
    "%DB_HOME_DIR:"=%\db2jcc4.jar";
    "%DB_HOME_DIR:"=%\db2jcc.jar";
    "%DB_HOME_DIR:"=%\db2jcc_license_cisuz.jar";
    "%DB_HOME_DIR:"=%\sqljdbc4.jar";
    "%DB_HOME_DIR:"=%\mssql-jdbc-6.4.0.jre8.jar";
    "%DB_HOME_DIR:"=%\mssql-jdbc-9.4.0.jre8.jar";
    "%DB_HOME_DIR:"=%\onedb-jdbc-8.1.1.1.jar";
    "%DB_HOME_DIR:"=%\log4j-core-2.16.0.jar";
    "%DB_HOME_DIR:"=%\log4j-api-2.16.0.jar";
    "%DB_HOME_DIR:"=%\bson-3.12.7.jar"
  3. Launch the configuredb script again.
Increased size for LRPR_RECORD_PROPERTIES and LLRC_LOG_RECORDS entries
Starting from 95 FP5, all user action involving displaying objects from the Dynamic Workload Console, APIs and CLI are audited.

This can lead to an increased size for LRPR_RECORD_PROPERTIES and LLRC_LOG_RECORDS entries.

To work around this problem, you can modify the number of days for keeping audit history data in the database by modifying the auditHistory optman option. For more information about this option, see Global options - detailed description.

9.5 Fix Pack 4:

If the Dynamic Agent Gateway name contains the character "-", it will not work as expected.

If you encounter this problem, re-install the Dynamic Agent Gateway without using the character "-" in the Dynamic Agent Gateway name to resolve this issue. If you are using custom certificates to enable the Dynamic Agent Gateway communication, then you need to renew the custom certificates.

Submitting Jobstreams from RESTAPI immediately executes the Jobstream even when you enter the arrival time.

The Jobstream will start immediately and not on the scheduled time when using REST API: /plan/{planId}/jobstream/{jobstreamId}/action/submit_jobstream"

The engine will accept the time parameters and execute the Jobstream according to its scheduled time only when you replace jobStreamId with none in the API endpoint.

EJB and PowerCenter plugins create their own property files with wrong permissions.

When you import the 9.5 FP4 EJB and PowerCenter plug-ins into the 9.4 FP7 agents (in <TWS_HOME>/applicationJobPlugIn folder), and submit their job in <TWS_HOME>/JavaExt/cfg, folders are created with their own properties files with correct ownerships but wrong permissions: - EjbJobExecutor.properties - PowerCenterJobExecutor.properties.

To avoid this issue, it is recommended to change the permission to 755, which provides read and execute access for all and write access for the owner of the file.

Upgrading your master domain manager from a version earlier than 95FP4
Before performing the upgrade, run the Flexera Analysis tool to ensure that the LICENSE_JOBS_NUMBER parameter is equal to 0. For more information about the tool, see Flexera Analysis tool
Limitation for agents using a remote gateway
Only for version 9.5 Fix Pack 4, if you install your agents so that they communicate with the master through a remote gateway, ensure that they can reach the master directly at installation time. For more information, see the section about dynamic agent gateway installation examples in Planning and Installation Guide.

9.5 Fix Pack 3:

SAP jobs running on extended agents located in folders are not supported
No workaround is currently available.
Restoring multiple agent on same workstation
If you have more than one agent on the same workstation and plan to perform a restore operation, using the -restore option of the twsinst command, ensure you run the command from a brand new shell.
Event-driven workload automation: only the latest matching criteria are saved in the event processor
If you create an event rule with several matching criteria and save it, when you re-open the event rule, only the latest matching criteria are saved in the event processor.
Updated latest start time is not displayed in the table
If you edit the latest start time of a critical job, the modification is not displayed in the Monitor Workload table.
Creating a monitoring object, no SMSE job is shown if a workstation has been defined as a filter
When creating a monitoring object using the Job Monitoring Setup panel, the SMSE jobs table does not show any result if in the Job Definition field a workstation has been defined as a filter.

Workaround: To correctly retrieve SMSE jobs by using a workstation as a filter, add an asterisk (*) before the number sign (#), for example WKSNAME*#JOB_NAME.

9.5 Fix Pack 2:

datacalc utility does not support calendars defined in a folder different from the root
The datecalc utility command only supports calendars that are defined in the root (/) folder.
The IBM Workload Scheduler agent for z/OS cannot be defined in a folder other than the root (/) folder
The definition of a IBM Workload Scheduler agent for z/OS workstation is not supported in a folder other than the root (/) folder. You can, however, schedule jobs and job streams defined in folders on an IBM Workload Scheduler agent for z/OS workstation.
Problems when using filters during the upgrade phase
During the upgrade phase where you have a backup master domain manager at the V9.5FP2, but the master domain manager is still at a previous product version level, problems can occur when monitoring objects that support the definition in a folder such as, prompts, workstations, and resources, as well as objects that contain the workstation in their object identifier, for example, job streams. More specifically these objects are not displayed in the results of the monitoring query on the plan if you use filters in your query.

Workaround: Upgrade the master to the V9.5FP2 level, and then run planman resynch to resolve the issue.

Following a temporary switch manager operation to the backup master domain manager, MakePlan fails after the next plan generation
In an environment where the automatic failover feature is enabled, if you perform a temporary switch from the master to the backup, and do not make it a permanent switch before the next JnextPlan, then when the XA (extended agent) runs the FINAL job stream, the MakePlan script ends in ABEND and a new plan is not generated. This occurs because the automatic failover feature runs the FINAL from an XA defined on $MASTER and the XA does not recognize that a switch has occurred and continues to refer to the original master.

Workaround: Modify the XA workstation definition in the database to set the new master as the current and make the switch permanent. The old master should be set as FTA and the new one as MANAGER.

Dependencies cannot be resolved when a workstation is set to IGNORE
If a workstation is set to IGNORE, the dependency resolution does not work since it cannot be evaluated by the batchman process. Furthermore, conman ads/adj considers the workstation not present in the plan and prevents you to add dependencies on IGNORED workstations. The deletion and release can be performed on dependencies defined on IGNORED workstations.
The EEW0107E error occurs and the option editor does not work
Using the option editor the following error could occur:
EEW0107E the password cannot be longer than forty characters error new file can not be correctly saved, old option files can not be opened
This occurs because the option editor does not work with the following option file types:
  • PeopleSoft (psagent)
  • SAP R/3 (r3batch)
  • z/OS® (mvsjes and mvsopc)

Workaround: For both SAP and PeopleSoft option files, you can create or edit files by using the option editor available in the XA task tab of the Access Method job type. For z/OS®, you can create or edit files by using a file editor instead of the option editor.

Job streams with resources that are not yet into the production plan cannot be submitted
You cannot submit a job stream defined on a workstation class if the job stream contains resources defined on the workstation class and the resources have not yet entered into the production plan.

Workaround: Define the job stream in the database and wait until the production plan is generated. After the plan is generated, submit the job stream as usual.

Collecting intercepted SAP jobs periodically is supported only for XA workstations on root
You can retrieve intercepted SAP jobs and relaunches them only for XA workstations defined on the root folder.
APAR IJ24378: Remote command job cannot be used with SMB1
In IBM Workload Scheduler v. 9.5.x, a remote command job that runs on a Windows workstation that is configured to use SMB1 fails.

Workaround: To make the remote command job work, use an SSH server, or download from Automation Hub plug-in version 9.5.0.4, which works correctly on Windows operating systems.

APAR IJ19659: Tivoli Netview integration configuration files need to be copied to the TWA_DATA_DIR folder
With IBM Workload Scheduler v 9.5.x, a new default behavior has been implemented with regard to the storage of product data and data generated by IBM Workload Scheduler, such as logs and configuration files. For this reason, the BmEvents.conf and MAgent.conf configuration files need to be copied to the TWA_DATA_DIR path otherwise, the Tivoli NetView MAgent does not work.

Furthermore, upgrading the Tivoli NetView Magent, the MAGENT.P and StartUp files are overwritten.

Workaround: To make Tivoli NetView Magent work and to avoid the loss of data, proceed as follows:
  1. Run the customized startup script: <TWA_home>/TWS/OV/customize
  2. Copy the BmEvents.conf file from the <TWA_home>/TWS/BmEvents.conf directory, and paste it into TWA_DATA_DIR. Then you can customize the file according to your needs.
    Note: Even if you define FILE=TWA_DATA_DIR/event.log and PIPE=TWA_DATA_DIR/MAGENT.P into the BMEvents.conf file, the MAGENT.P is located in the <TWA_home>/TWS folder.
  3. Copy the MAgent.conf file from the <TWA_home>/TWS/ MAgent.conf directory, and paste it into TWA_DATA_DIR. Then you can customize the file according to your needs.
Once all IBM Workload Scheduler processes are restarted, the following files are generated:
  • TWA_DATA_DIR /event.log
  • <TWA_home >/TWS/MAGENT.P
Upgrading the Tivoli NetView Magent, the MAGENT.P file and StartUp file are overwritten. Modify the ownership of the StartUp script to be owned by IWA_owner_user>, and then to avoid data loss, copy both files from the <TWA_home>/TWS/ directory, and paste them into TWA_DATA_DIR.
9.5 Fix Pack 1:
An incorrect run number is sent to Flexera and causes the engine functionality to stop
If you have migrated a master domain manager from product version 9.5 Fix Pack 1 to the latest fix pack level and encounter the error message AWKFLX002E One or more job run numbers are missing in the job count, then an error has occurred in calculating the job run number. The updateStats script of the first FINALPOSTREPORTS could end after the switchPlan script of the FINAL job stream, thus the job run number changes before the end of the updateStats script. Flexera server finds that the run number is not the expected one and stops the engine functionality.

This problem does not apply if you perform a fresh installation of the master domain manager at 9.5, Fix Pack 2 level. The problem applies only if you have migrated a master domain manager from product version 9.5 Fix Pack 1 to the latest fix pack level.

Workaround: to make the job run number reliable, the FINAL and FINALPOSTREPORTS should be modified as follows:
  • The FINAL's FOLLOWS dependency must be changed from WKS#FINAL.SWITCHPLAN PREVIOUS to FOLLOWS WKS#FINALPOSTREPORTS.UPDATESTATS FROM 2359 - 1 DAYS TO 2358 job.
    Following an example of the complete FINAL definition:
    SCHEDULE WKS#FINAL
            DESCRIPTION "Added by composer."
            ON RUNCYCLE RC1 "FREQ=DAILY;"
            AT 2359
            CARRYFORWARD
            FOLLOWS WKS#FINALPOSTREPORTS.UPDATESTATS FROM 2359 - 1 DAYS TO 2358
            :
            WKS#STARTAPPSERVER
     
            WKS#MAKEPLAN
            FOLLOWS STARTAPPSERVER
     
            WKS#SWITCHPLAN
            FOLLOWS MAKEPLAN
    
  • The FINALPOSTREPORTS.UPDATESTATS job must be set to have a RECOVERY STOP option instead of the RECOVERY CONTINUE one.
    Following an example of the complete UPDATESTATS definition:
    WKS#UPDATESTATS
            SCRIPTNAME "/opt/HCL/WA95/TWS/UpdateStats"
            STREAMLOGON wauser
            DESCRIPTION "Added by composer."
            TASKTYPE UNIX
            RECOVERY STOP
            FOLLOWS CHECKSYNC
    

Jobs are not able to run on a domain manager after a repeat rerun

If the recovery job workstation is a dynamic agent, to make jobs run on a domain manager after a repeat rerun, the dynamic agent must belong to the same domain as the parent job workstation.

SendMail action is not performed due to a missing WebSphere Application Server Liberty Base third-party library

When an event rule includes sending a user an email as the triggered action in response to the occurrence of the event, the email is not sent due to the absence of a WebSphere Application Server Liberty Base third-party library.
Workaround: to load the missing third-party library available in Liberty, you must define the API type visibility in the section of the server.xml file that is related to the TWSEngineModel.ear deployment. Set the apiTypeVisibility attribute of the classloader element to third-party as follows:
<enterpriseApplication id="TWSEngineModel" location="TWSEngineModel.ear" name="TWSEngineModel"> <classloader apiTypeVisibility="+third-party" commonLibraryRef="DBDriverLibs, libs.native" delegation="parentFirst"  privateLibraryRef="libs.sdo, libs.plugin, libs.jackson, twa-properties, libs.ccmdb, libs.emf, libs.jlog, libs.act">
</classloader>

Once the change has been performed, restart the WebSphere Application Server Liberty Base

A communication failure could occur when removing an ACL defined on a deleted folder

Removing an ACL defined on a deleted folder from the DWC, you could receive the following error message:
"AWSUI0833E The operation could not be completed. There has been a communication failure. The internal message is: AWSJDB201E The object "acl=/FOLDER1_1/+F" cannot be locked, updated, or deleted because it is locked by user "null"."
Workaround: to remove the ACL and avoid communication issues, perform the following steps:
  1. Recreate the deleted folder.
  2. Delete the ACL defined on the folder you just recreated.
  3. Delete the folder.

A fully qualified path length of a folder cannot be longer than 254 chars

The folder path cannot be longer than 254 chars, otherwise a security file corruption occurs.

The CWWKS4001I information message is logged several times in the messages.log file

In case of Dynamic Workload Console concurrent users generating more than 15 pages/second traffic, the CWWKS4001I information message is logged several times in the WebSphere Application Server Liberty Base messages.log of the master domain manager. This behaviour makes the log file difficult to read and might cause potential performance impacts on Dynamic Workload Console response time.

Upgrading to versions 9.5 GA or 9.5 FP1 from an upgraded version 9.4 FP6 with an MSSQL or Informix database
If you have upgraded to version 9.4 FP6 from version 9.4 GA or from any fix pack earlier than FP6, and are using an MSSQL or Informix database, apply 9.4 FP7 before upgrading to versions 9.5 GA or 9.5 FP1.

Fix pack structure

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

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

This is the structure of the Fix Pack for the engine on HCL License Portal:
Table 8. Readme file and WebSphere Liberty package
Name Description
HWA_9505_ReadmeFirst Readme file with download instructions
HWA_9505_WEBSPHERE_LIBERTY WebSphere Liberty application server

Table 9. AIX components
Name Description
HWA_9505_AIX_BatchReportCli HCL Workload Automation 9.5.0.5 Batch Reports Command Lines
HWA_9505_AIX_AGENT

HCL Workload Automation Agent 9.5.0.5,

Remote CLI and Workload Automation for Applications for AIX

Table 10. IBM i components
Name Description
HWA_9505_IBM_I_AGENT HCL Workload Automation Agent 9.5.0.5 for IBM i

Table 11. Linux components
Name Description
HCL Workload Automation 9.5 LINUX LINUX distribution
HWA_9505_MDM_LINUX_X86_64 Workload Automation 9.5.0.5 FOR LINUX
HWA_9505_LINUX390_BatchReportCli HCL Workload Automation 9.5.0.5 Batch Reports Command Lines
HWA_9505_LINUX_X86_64_BatchReportCli HCL Workload Automation 9.5.0.5 Batch Reports Command Lines
HWA_9505_LNX_PPC64LE_AGENT HCL Workload Automation Agent 9.5.0.5, Remote CLI and Workload Automation for Applications for Linux on POWER (little endian)
HWA_9505_LNX_S390_AGENT HCL Workload Automation Agent 9.5.0.5, Remote CLI and Workload Automation for Applications for Linux on System z9 and System z
HWA_9505_LNX_X86_64_AGENT Workload Automation Agent 9.5.0.5, Remote CLI and Workload Automation for Applications for Linux on x86-64

Table 12. Linux components on Docker
Name Description
HCL Workload Automation 9.5 LINUX LINUX distribution
HWA_9505_DOCKER_MDM_LINUX_X86_64 Workload Automation 9.5.0.5 FOR LINUX on Docker
HWA_9505_DOCKER_LNX_X86_64_AGENT Workload Automation Agent 9.5.0.5, Remote CLI and Workload Automation for Applications for Linux on x86-64 on Docker

Table 13. Windows™ components
Name Description
HCL Workload Automation 9.5 WINDOWS WINDOWS distribution
HWA_9505_MDM_WINDOWS_X86_64 Workload Automation 9.5.0.5 FOR WINDOWS
HWA_9505_WINDOWS_X86_64_BatchReportCli HCL Workload Automation 9.5.0.5 Batch Reports Command Lines
HWA_9505_WIN_X86_64_AGENT HCL Workload Automation Agent 9.5.0.5, Remote CLI and Workload Automation for Applications for Windows x64

Table 14. zOS components
Name Description
HWA_9505_Zsystem_BatchReportCli HCL Workload Automation 9.5.0.5 Batch Reports Command Lines

Table 15. OpenShift components
Name Description
HWA_9505_OpenShift_Agent.zip Workload Automation for Openshift 9.5.0.5 - agent only
HWA_9505_OpenShift_Server_UI_Agent.zip Workload Automation for Openshift 9.5.0.5 - Server, UI and agent

Installing the Fix Pack

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

The section is divided into the following subsections:

Installation notes

When installing the HCL Workload Automation Fix Pack, follow these recommendations:
  • 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.
  • 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 9.5.0 Fix Pack 5 supports all product versions indicated in the version 9.5 Release Notes which can be accessed at the following link: Release Notes for HCL Workload Automation.

Disk space requirements

For the most up-to-date information about disk space and memory requirements, see the hardware requirements at the following URL: Hardware 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
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 16. 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 17. 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 18. 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

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

Configuring your master domain manager and broker in SSL mode

If you plan to install your master domain manager, Version 9.5 Fix Pack 5 in SSL mode or plan to upgrade to Version 9.5 Fix Pack 5 and set up your master domain manager and broker in SSL mode, perform the following steps:
  1. Install the master domain manager or upgrade your current master domain manager to version 9.5.0.5
  2. Replace the values of the following parameters in the localopts file with the following values:
    • nm SSL full port = 31113
    • SSL key =TWA_home/TWS/ssl/OpenSSL/TWSClient.key
    • SSL certificate = TWA_home/TWS/ssl/OpenSSL/TWSClient.cer
    • SSL key pwd = TWA_home/TWS/ssl/OpenSSL/password.sth
    • SSL CA certificate = TWA_home/TWS/ssl/OpenSSL/TWSTrustCertificates.cer
    • SSL random seed =TWA_home/TWS/ssl/OpenSSL/TWS.rnd
    • SSL Encryption Cipher = TLSv1.2
    For more information about the localopts file, see Setting local options
  3. Modify the master domain manager and broker using the composer mod command, as follows:
    CCPUNAME your_master_domain_manager_workstation
    
      DESCRIPTION "MANAGER CPU"
    
      OS UNIX
    
      NODE localhost TCPADDR 31111
    
      SECUREADDR 31113
    
      DOMAIN MASTERDM
    
      FOR MAESTRO
    
        TYPE MANAGER
    
        AUTOLINK ON
    
        BEHINDFIREWALL OFF
    
        SECURITYLEVEL FORCE_ENABLED
    
        FULLSTATUS ON
    
    END
    CPUNAME your_broker_workstation
    
      DESCRIPTION "This workstation was automatically created."
    
      OS OTHER
    
      NODE localhost TCPADDR 41114
    
      SECUREADDR 41114
    
      DOMAIN MASTERDM
    
      FOR MAESTRO
    
        TYPE BROKER
    
        AUTOLINK ON
    
        BEHINDFIREWALL OFF
    
        SECURITYLEVEL FORCE_ENABLED
    
        FULLSTATUS OFF
    
    END
  4. Modify the Broker.Workstation.PortSSL parameter in the BrokerWorkstation.properties file from false to true.

    The Broker.Workstation.PortSSL parameter specifies the port used by the broker server to listen to the incoming traffic (equivalent to the Netman port) in SSL mode. It is first assigned at installation time. This port number must always be the same for all the broker servers that you define in your HCL Workload Automation network (one with the master domain manager and one with every backup master domain manager you install) to ensure consistency when you switch masters.

  5. Stop and start WebSphere Application Server Liberty Base, as described in Application server - starting and stopping.
  6. Stop and start all HCL Workload Automation processes.
  7. Run
    Jnextplan -for 0000

Before Installing

Before installing the Fix Pack using any of the methods described in the following sections, perform the following actions:
  1. If you have jobs scheduled to run on the instance you are upgrading, make sure that they have completed otherwise some processes, such as jobmon or joblnch, might still be active.
  2. Download the appropriate ZIP files for the operating system from HCL License Portal .
  3. Extract the content of the ZIP files into a directory, using one of the extraction tools available on your system or downloadable from the Internet. The tool you use must be able to keep the file permissions on the extracted files, for example, infozip.
    Note:
    • If you want to install the Fix Pack on IBM i, to untar the eImages, see Extract the eImages for the Z Agent and Dynamic Agent on IBM i operating systems.
    • To extract the .zip file onto a Windows 64-bit system, ensure that the eImage is not located on the desktop because the Windows operating system extract tool has a problem. Choose another directory into which to extract the Fix Pack eImage.

Creating or updating the HCL Workload Automation database schema

Before launching any of the installation methods, create or update the database schema.

Before applying the Fix Pack, create the database schema by following the procedure described in the Creating and updating the database tables chapter in the HCL Workload Automation guide.

If the database already exists, update the database by running the following command:
On Windows operating systems
cscript configureDb.vbs --rdbmstype db_type --dbhostname db_hostname 
--dbport db_port --dbname db_name --dbuser db_user 
--dbpassword db_password --dbadminuser db_administrator 
--dbadminuserpw db_administrator_password
On UNIX operating systems
./configureDb.sh --rdbmstype db_type --dbhostname db_hostname 
--dbport db_port --dbname db_name --dbuser db_user 
--dbpassword db_password --dbadminuser db_administrator 
--dbadminuserpw db_administrator_password

If a new version of the database is available, update to it by following the procedure described in the Upgrading the database schema chapter in the HCL Workload Automation guide.

Extract the Images for the Agent and Dynamic Agent on IBM i operating systems

The following package is available with this Fix Pack:
  • HWA95_FP2IBM_I_AGENT.zip: The dynamic agent on IBM i image. This package also contains an extraction tool executable that can be copied to the IBM i workstation.

To untar or unzip the Fix Pack eImages, you can use the PASE shell or the AIXterm.

Using PASE shell:
  1. Open the PASE shell.
  2. Run the command:
    "CALL QP2TERM"
  3. Locate the folder where you downloaded the Fix Pack eImage and run the command:
    Dynamic agent
    "unzip HWA95_FP2_IBM_I_AGENT.zip"
  4. Exit from the PASE shell.
Using AIXterm:
  1. Start the Xserver on your desktop.
  2. On the iSeries machine, open a QSH shell and export the display.
  3. In QSH shell, go to the directory /QopenSys and run the command:
    "aixterm -sb"
  4. A pop-up window is displayed on your desktop. Using this pop-up window, unzip the HWA95_FP2_IBM_I_AGENT.zip file, or untar the HWA95_FP2_IBM_I_AGENT.zip.

Rolling back an applied fix pack

This topic describes how to roll back an applied fix pack to a previous version.

You can revert back to an earlier version of an installed Fix Pack or release by using one of the following methods:
For master domain manager or its backup:
see Rolling back the master domain manager and its backup
For dynamic domain manager or its backup:
see Rolling back the dynamic domain manager

Documentation updates for HCL Workload Automation Fix Pack 5 for version 9.5.0

Deploying with containers

In the readme files for Amazon Web Services (AWS) Elastic Kubernetes Service (EKS) (Amazon EKS), Azure Kubernetes Service (AKS), Google GKE, and Red Hat OpenShift, available at the following link:Deploying with containers

add the following sentence:
"To ensure the Dynamic Workload Console logout page redirects to the login page, modify the value of the logout url string available in file authentication_config.xml:
<jndiEntry value="${logout.url}" jndiName="logout.url" />
where the logout url string in jndiName should be replaced with the logout URL of the provider."

Planning and installation

Setting the -skipcheckemptydir parameter

In the master domain manager installation parameters - serverinst script section, add the following parameter:
skipcheckemptydir
Set this parameter to true to avoid checking whether the installation directory is empty. By default, this parameter is false, because starting from version 9.5 the installation directory must be empty. If you set this parameter to true and the installation directory is not empty, the installation process might fail.

Supported characters for the -password parameter

In the Agent installation parameters - twsinst script section, the list of supported characters for the -password parameter should be changed to exclude commas.

Default values for the configureDB script in a z/OS environment

In the Database configuration - configureDB script section, add the following information:

The default values for the following parameters in a z/OS environment are:
  • iwstsname = TWSDATA
  • iwstspath = TWSDATA
  • DB_ADMIN_USER = SYSADM

Additional port information

In the Master components installation - serverinst script section, add the following information:

Communication Agent-Master:
  • 31111 - incoming/outcoming Netman port (localopts)
  • 31115 - HTTP_PORT
  • 31116 - HTTPS Protocol port (localopts)
  • 31113 - port used to listen for incoming SSL connections. This value must match the one defined in the nm SSL port local option of the workstation
  • 31131 - eventProcessorEIFPort specifies the Job Manager Event Integration Facility (EIF) port number. (optman ls)
  • 31132 - -gweifport gateway_eif_port. Specifies the Job Manager Event Integration Facility (EIF) port number. The default value is 31132. The valid range is 1 to 65535
  • 5529 - EIF Probe server port. Used in event rule management
dynamic domain manager:
  • 31114 - dynamic domain manager JobManager port (ssl_port in the ita.ini file)
  • 31117 - dynamic domain manager ResourceAdvisor port (used for JobStatus Update and ResourcesStatus Update)
  • 41114 - BROKER_NETMAN_PORT – The TCP/IP port number used by the netman process to listen to communication from the dynamic domain manager
  • 35116 - CLI connections (localopts)
Dynamic Workload Console
  • 9444 - HTTP_PORT
  • 9443 - HTTPS_PORT
  • 12809 - bootstrap port
  • 19402 - bootstrap security port, to be used for connecting to the Z connector
event-driven workload automation
  • 31131 - HTTP/HTTPS Config Deploy port

--data_dir parameter in dwcinst script also applicable to z/OS environments

In section Dynamic Workload Console installation - dwcinst script, the --data_dir parameter applies also to z/OS environments, so the UNIX symbol next to it should be removed.

User's Guide and Reference

Description attribute

In the following sections:
  • Job stream definition keyword details > Description
  • Defining scheduling objects > Job definition
replace "120 characters" with "120 bytes" in the explanation of the description attribute.

Description of the validfrom/validto keyword

In the validfrom/validto section, add the following sentence to the description of the validfrom/validto keyword:

"It also defines the first date the instances in the preproduction plan are included in the current plan."

Full validation of workstation definition available only in the Dynamic Workload Console

In the Workstation definition section, add the following sentence: "The composer command cannot perform full validation of the workstation definition. If you need validation on the workstation, use the Dynamic Workload Console to create it."

Incorrect syntax for the job stream - startcond keyword

In section Job stream definition, in the syntax of the job stream the startcond keyword must be located after the except keyword and changed as follows:
[startcond filecreated | filemodified  [folder/]workstation_name#file_name 
          user username 
          interval seconds 
          [(alias startcond_jobname 
          rerun batch outfile outputfilename 
          params "filemonitor additional parameters")] |
   startcond job  [folder/]workstation_name#[folder/]job_name
          outcond  joboutputcondition 
          interval seconds 
          [(alias startcond_jobname rerun)]]   

Incorrect syntax for the job stream - at keyword

The absolute|abs parameter must be removed from the syntax. Also, the following sentence must be removed from the explanation:

If the backup 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, you must add the absolute keyword to make it work when you submit a job or a job stream.

Incorrect syntax for the job stream - until keyword

The absolute|abs parameter must be removed from the syntax.

Administration guide

PCI standard

In the Log files and Archived files section, the following paragraph should be added to the existing text after the first paragraph:

When generating a job log in the monitoring section of the Dynamic Workload Console, by default the master domain manager generates a temporary file in the /tmp folder for the job log for each submitted job.

You can optionally avoid the temporary download of the job log on the master domain manager if the job log contains confidential information. This ensures compliance with the PCI standard.

Follow these steps to change this behavior:
  1. Set the com.ibm.tws.conn.plan.output.logtype property in the TWSConfig.properties file to memory
  2. Stop and start all the HCL Workload Automation processes
The temporary job log file will be loaded into memory, not leaving any track within the server system and console file. This will result in the product returning to PCI requirements. If no request arrives within the timeout specified in the ccom.ibm.tws.conn.plan.output.timeout, the operation is canceled.

Network configuration availability

After a system reboot, network services might be slow to start and if the agent starts when network services are not yet ready, the agent cannot work properly.

To prevent this problem, the agent waits sixty seconds and then retries to retrieve the network configuration. The agent repeats this operation for 5 times, that is, it waits for a total of 5 minutes for the network configuration to become available. If all attempts fail, the agent stops working.

You can configure the number of times the agent waits for network configuration availability in the ITA section of the ita.ini file, as follows:
  1. Browse to the path where the ita.ini file is located:
    On UNIX operating systems
    TWA_DATA_DIR/ITA/cpa/ita/ita.ini
    On Windows™ operating systems
    TWA_homeTWS\ITA\cpa\config\ita.ini
  2. Edit the setting for the net_conf_wait parameter defining the number of times the agent retries to retrieve the network configuration, waiting sixty seconds between each attempt. If the number of attempts you have defined expires without the agent being able to retrieve the network configuration, the agent stops working.

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.

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

© (HCL Ltd.) (2020).
Portions of this code are derived from HCL Ltd. Sample Programs.
© Copyright HCL Ltd. _2020_.

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

Trademarks

HCL, the HCL logo, and ibm.com are trademarks or registered trademarks of HCL Technologies Ltd. in the United States, other countries, or both. If these and other HCL trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by HCL at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries.

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.

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.

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.

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

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