Fixed an issue where running the configureDb.sh script failed if the database administrator password (--dbadminuserpw) or database user password (--dbpassword) contained a dollar sign ($). Previously, this caused the script to stop processing and return an error during the database configuration for the Dynamic Workload Console. The script has been updated to correctly process passwords containing this special character.

A defect in the agent installation script caused the procedure to fail on IBM i environments because the script could not correctly parse the output of the java -version command.

A defect in the twsinst script caused the registry recovery operation (-recovInstReg true) to fail and return error code 5. When attempting to restore corrupted registry files, the twsinst script triggered an incorrect subroutine, resulting in the misleading error: "ERROR: TWS instance to enable for Cluster Installation is not a8.6.x.x/9.1.x.x version. Therefore no action will be performed."

A defect in the agent upgrade process caused the installation to fail when attempting to process the P12 certificate file. The failure occurred because the bundled OpenSSL utility available on the agent encountered an unsupported encryption algorithm during the processing of the certificate file.

The uninstallation procedure failed to remove the cit.ini file after the uninstallation of a non-root instance. This configuration file retained an incorrect path to the common inventory technology (CIT) component, leading to configuration errors.

This issue typically occurred when a high number of dynamic agents were configured in the environment. The root cause was linked to the exhaustion of available HTTP connections.

Fixed an issue where performing a centralized agent update unexpectedly created an empty /tmp/TWS directory. Previously, this folder was generated even when the default working directory parameter (-work_dir) was used, which should only target the $HOME/tmp directory. The update process has been corrected to prevent the creation of this unnecessary folder.

Fixed an issue on Windows operating systems where new installations of the z-centric agent incorrectly assigned port 512 as the default dynamic domain manager port. Previously, this caused the agent to fill the logs with AWSITA081E errors because it continuously attempted to send resource information to an incorrect URL. The installation process has been updated to correctly set the port to 0 by default in the ResourceAdvisorUrl parameter of the JobManager.ini configuration file.

The upgrade of dynamic agents erroneously reported successful completion with message AWSFAB033I, even when the installation process failed due to critical disk space issues.

After installing or updating a dynamic agent on Windows, the required directory for Java logs was not created, causing the loss of JavaExecutor logs.

The –dbsslconnection parameter in the configuredb or serverinst commands was available only on UNIX operating systems.

A defect caused the installation of the backup master domain manager to fail during a parallel upgrade, returning the AWKCLI102E error. The underlying cause was a bug in the code which failed during the encryption of the password when the password string length was exactly 16 characters or a multiple of 16 (for example 32, 48).

Fixed an issue where installing a dynamic agent on Windows Server 2016 failed with a missing prerequisites error. Previously, the checkPrereq.json configuration file incorrectly omitted Windows Server 2016 from the list of supported operating systems, conflicting with the product documentation. The prerequisite check file has been updated to correctly recognize Windows Server 2016 as a supported operating system, allowing the installation to proceed successfully.

Fixed an issue in the installation process where dynamic agents were automatically configured and started despite the user requesting only a fault-tolerant agent. Previously, when certificates were downloaded automatically during installation, the process bypassed the user's explicit parameter selection (the fta agent type) and defaulted to installing both agent types. This resulted in unintended dynamic agent proliferation in the database and the production plan for customers who did not intend to use dynamic scheduling features. The installation script has been updated to correctly process the user's parameter selection, ensuring that only the requested fault-tolerant agent is configured and started.

Fixed an issue on Windows operating systems where running the users.exe -build command on a fault-tolerant agent connected to an IBM Z Workload Scheduler controller failed and returned an AWSDEG463E error

A defect was introduced during the upgrade of the fault-tolerant agent installed on a Windows operating system, which caused file dependencies to fail resolution. The issue occurred on Windows Server 2016 when jobs defined to run on a dynamic pool utilized a file dependency pointing to a shared file system (UNC path). The internal file check mechanism erroneously failed to verify the existence of files, resulting in the unwanted nF (No File) status.

Fixed an issue where using the certman command to generate certificates incorrectly changed the permissions of all existing files to 644 recursively within the folder specified by the -outpath parameter. This failure could disrupt the IBM Workload Scheduler environment if the command was run in a non-empty directory.

A defect in the scheduling object modification logic caused the OUTPUTCOND keyword to be erroneously replaced by the SUCCOUTPUTCOND keyword when an administrator used the OCLI (modify or add) commands.

A defect prevents plan management scripts (including JnextPlan, MakePlan, SwitchPlan, UpdateStats, and CreatePostReports) from correctly deleting the CONSLOG file.

Fixed an issue where running the wa_pull_info data gathering script generated an excessively large datagather_summary.log file, which significantly inflated the size of the resulting archive.

Fixed an issue in the Orchestration CLI where running a comprehensive job search query took an excessively long time to complete. Previously, when a user executed the showjobs (sj) command to filter for all jobs in a FAIL state across all folders and workstations, the system experienced significant performance degradation and delayed the display of results. The Orchestration CLI has been updated to optimize query processing, allowing users to successfully retrieve extensive job status reports in a timely manner without encountering performance delays.

Fixed an issue in the Orchestration CLI where searching for jobs within a specific folder failed if any of the jobs were in a waiting state. Previously, when a user executed the showjobs (sj) command with a folder filter, the system encountered an unexpected internal error if it processed jobs that were waiting to run, preventing the results from being displayed. The Orchestration CLI has been updated to correctly process all valid job states, allowing users to successfully retrieve and view job data regardless of their current execution status.

Fixed an issue where deploying the product components using Kubernetes Helm charts failed or incorrectly overwrote custom secrets. Previously, when using a custom Kubernetes secret containing SSL certificates and the SSL_PASSWORD environment variable, the deployment returned a duplicate name warning because the variable was defined twice in the dynamic agent's statefulSet.yaml configuration template. The Helm chart has been updated to remove the duplicate variable definition, ensuring that deployments complete successfully when using custom secrets.

Fixed an issue where the certificate rotation mechanism failed for the Dynamic Workload Console and the IBM Workload Scheduler engine in Kubernetes environments. Previously, if the useCustomizedCert parameter was set to true and the certDuration and certRenewBefore parameters were configured with values lower than the defaults, the certificates did not rotate automatically. This failure caused the connection between the Dynamic Workload Console and the engine to drop.

Fixed an issue where some jobs incorrectly remained stuck in a WAIT status after a database High Availability Disaster Recovery (HADR) switchover. Previously, if the database connection closed during the switchover, the job dispatcher failed to update the job properties and stopped progressing, returning AWKJDB802E and AWKJDE109E database connection errors.

Fixed an issue where the system stalled and entered a deadlock state when a certificate download was initiated by the dynamic domain manager. This failure occurred because the resource thread became incorrectly blocked while attempting to simultaneously install and verify the new certificates.

Fixed an issue where submitting jobs from IBM Z Workload Scheduler to a dynamic domain manager sporadically failed. This failure occurred because the dynamic domain manager lost its JDBC connection to the database, which resulted in repeated transaction rollbacks and database unique constraint violations (AWKJDE102E and AWKJDB604E).

Fixed an issue on AIX operating systems where jobs failed after migrating from a fault-tolerant agent to a z-centric agent because the task launcher failed to export the UNISON_DIR environment variable. Previously, users had to implement a manual workaround by creating a .jobmanrc local configuration script to properly export the variable before running the job. The task launcher has been updated to automatically export this environment variable, ensuring jobs run successfully without requiring manual intervention.

Fixed an issue on AIX operating systems where the agent randomly crashed and generated a core dump file due to resource allocation errors. Previously, when encountering thread creation or memory availability issues, the agent processes stopped unexpectedly. This caused the agent to log resource errors in the ita_trace.log file and return AWSITA112I, AWSITA111I, and AWSITA052I stopped messages in the JobManager_message.log file. The issue has been resolved to ensure the agent remains stable under these conditions.

Fixed an issue where executable jobs failed to start when both standard output and standard error redirection were configured. Previously, specifying both redirection paths caused the job to fail and return an AWSITA028E error containing an AWSITA069E job monitor internal error (return code 8). Although the output log files were successfully created on the agent, the actual application script was prevented from running. The issue has been resolved so that configuring standard output and standard error redirection no longer interferes with script execution.

Fixed an issue where dynamic agents incorrectly stopped sending job status updates to the master domain manager during persistent connection issues. Previously, if a connection issue persisted, the agent logged AWSITA366E errors and stopped retrying to send updates after a maximum of one hour, bypassing the expected default behavior of retrying for up to 10 days. Consequently, the master domain manager displayed incorrect statuses for jobs executed on the affected dynamic agents.

Fixed an issue where using the confirm command to change a job status to successful (SUCC) updated the incorrect job instance if the job had already been rerun. Previously, if a job had rerun instances (generated manually or automatically via a recovery option), the mirroring component incorrectly applied the status update to the most recent rerun instance instead of the explicitly selected job. As a result, the selected job retained its old status (such as ABEND), and AWSJSY404E and AWSBIN076E errors were written to the messages.log file. The mirroring component has been updated to ensure that status changes are accurately applied to the specific job instance selected.

Fixed an issue in the REST API where retrieving a z/OS shadow job definition returned an incomplete payload. Previously, when a user performed a GET request to the /twsd/api/v2/model/jobdefinition endpoint for a z/OS shadow job, the system incorrectly omitted the task object from the response. This missing data caused subsequent updates via PUT requests to fail with an AWSJOM001E internal error, preventing users from modifying any fields of the shadow job. The API has been updated to correctly process and return the task object for z/OS shadow jobs, allowing users to successfully retrieve and update these job definitions without encountering errors.

Fixed an issue where the product documentation did not specify the required job types for using the $this.stdlist variable to analyze job log content. Previously, the documentation stated that the variable could be used on dynamic agent workstations to evaluate the succoutputcond and outputcond parameters, but did not mention the limitations for standard UNIX and Windows jobs. The documentation has been updated to clarify that this variable is only supported when defining an executable job or a job type with advanced options, whereas standard UNIX and Windows job types support only the return code (RC) variable.

Fixed an issue where the product documentation did not clearly explain the difference in behavior when the enExpandedResources (or er) global option was set to yes versus no. The documentation has been updated to clarify that a job or job stream can request a maximum of 1024 resource units, which are converted at run time into holders containing up to 32 units each. Setting the option to yes allows a maximum of 60 concurrent holders at a time, whereas setting it to no restricts the maximum to 32 concurrent holders.

Fixed an issue where the product documentation did not specify that the onoverlap donotstart option must not be used if the job stream is defined on a , domain manager, dynamic agent, pool, or dynamic pool in a domain other than the master domain. Previously, using this option in lower-level domains could cause job stream instances to be incorrectly canceled after their jobs had already run, due to standard delays in status reporting across the network hierarchy. The documentation has been updated to clearly state this limitation.

Fixed an issue on Windows operating systems where submitting a job with multiple commands joined by the && operator incorrectly executed only the first command. Previously, any command following the && operator was truncated and ignored on a fault-tolerant agent. This issue was resolved by updating the jobmanrc.cmd standard configuration script to correctly process and execute the entire command string. This information was added in the documentation.

Fixed an issue where the product documentation incorrectly listed the metric name for running workstations. Previously, the documentation referred to the metric as application_wa_workstation_running instead of the correct name, application_wa_workstation_running_boolean. The documentation has been updated to reflect the actual metric name.

Added information in the documentation about the requirement that only one certificate must be present in the TWSServerKeyFile.p12 or TWSServerKeyFile.jks keystore before upgrading the master domain manager. Previously, if multiple certificates were present in the keystore when upgrading using the serverinst.sh script, the upgrade failed and returned WACOMM006E and WACERT052E errors. The documentation has been updated to include the prerequisite steps for preparing the keystore prior to an upgrade.

Fixed an issue on Windows operating systems where the IBM Common Platform Agent service failed to start during system boot. This failure occurred when the service was configured to run under a domain user account, because the network or domain controller was not yet available during startup. To resolve this issue, the service startup type has been changed from Automatic to Automatic (Delayed Start) and this information wads aded in the product documentation.

Fixed an issue where the product documentation did not specify that the Dynamic Workload Console and the master domain manager must be installed in different Oracle database schemas. Previously, sharing the same schema during a Dynamic Workload Console upgrade caused the configureDb script to fail because it did not properly account for the existing master domain manager objects. The documentation has been updated to clearly state this limitation and recommend using separate schemas.

Fixed an issue where the interoperability table in the Dynamic Workload Console release notes contained an incorrect title. The title previously stated that the table showed components compatible with previous Dynamic Workload Console versions. The documentation has been updated to correctly indicate that the table shows components compatible with previous master domain manager versions.

Fixed an issue where upgrading the master domain manager from version 10.2.5 to 10.2.6 resulted in mismatched versions of the RESTful plug-in files. Previously, if the plug-in had been manually updated before the upgrade, the installation process incorrectly downgraded the com.ibm.scheduling.agent.restful_*.jar file in the TWS/JavaExt/eclipse/plugins/ directory, while the correct, updated version was retained in the TWS/applicationJobPlugIn/ directory.

Fixed an issue where the product documentation for Report 10B - Actual Production Detail incorrectly stated that the job run time was displayed in an hh:mm format. The documentation has been updated to correctly reflect that the run time is displayed in an mm:ss format.

Fixed a discrepancy in the product documentation where the authentication_config.xml file was incorrectly referenced as authorization_config.xml. The documentation has been updated to display the correct file name.

Fixed an issue where product documentation was missing for several automatic failover tuning parameters. The documentation has been updated to include the descriptions and tuning guidelines for the com.hcl.tws.failover.master.polling, com.hcl.tws.failover.master.treshold, com.hcl.tws.failover.event.polling, and com.hcl.tws.failover.event.treshold parameters configured in the TWSConfig.properties file.