Release Notes

Abstract

This document provides important information about IBM Workload Scheduler Version 10.2.8

Content

IBM Workload Scheduler version 10.2.8 Release Notes

Release date: July 27, 2026

This document provides important information about IBM® Workload Scheduler version 10.2.8.

You can obtain dynamic and up-to-date reports by browsing to Software Product Compatibility Reports and selecting the information you are interested in.

This document is divided into the following main sections:

Features introduced with version 10.2.8
APARs fixed in version 10.2.8
Defects fixed in version 10.2.8
Resolved Common Vulnerabilities and Exposures (CVEs)
Interoperability tables
Known limitations and workarounds
Package structure
Software requirements for WebSphere Application Server Liberty Base
Installing and upgrading to version 10.2.8
Performing the centralized agent update on a stand-alone fault-tolerant agent
Documentation updates
Contacting IBM Workload Scheduler Software Support
Notices

Documentation Portal Update for IBM Workload Scheduler and IBM Z Workload Scheduler

Effective July 27, 2026, the official documentation for IBM Workload Scheduler and IBM Z Workload Scheduler is returning to the primary IBM Documentation platform: IBM Workload Scheduler V 10.2.8 documentation

Features introduced with version 10.2.8

IBM Workload Scheduler version 10.2.8 contains the following enhancements:

Helpful videos demonstrating new features are available on Workload Automation YouTube channel.

APARs fixed in version 10.2.8

This section lists APARs resolved in version 10.2.8, divided by component.

Table 1. Engine component - APARs fixed in this release
Table 2. Installation process – APARs fixed in this release
Table 3. Command-line component – APARs fixed in this release
Table 4. Docker – APARs fixed in this release
Table 5. dynamic domain manager (broker) – APARs fixed in this release
Table 6. Report CLI– APARs fixed in this release
Table 7. AIDA CLI– APARs fixed in this release
Table 8. Documentation – APARs fixed in this release

Table 1. Engine component - APARs fixed in this release
Code	Description
IJ29440	Fixed premature execution of jobs dependent on start conditions. Previously, when using condition-based workload automation to monitor a job's output condition (such as waiting for a specific return code like `RC=0`), the dependent job or job stream could run prematurely. If the monitoring job ran repeatedly and returned an unsatisfied code (for example, returning `RC=5` every 15 minutes), the start condition keyword did not work as expected and incorrectly released the successor job before the required `RC=0` condition was actually met. This issue is now resolved. The start condition evaluation logic has been updated to ensure that the condition is strictly monitored. Dependent jobs and job streams now correctly wait and only begin processing once the specified start condition job officially completes and exactly satisfies the required output condition
IJ56883 KB0124561	Fixed unexpected job stream instances when using run cycle groups with repeat cycles. Previously, when a job stream used a run cycle group configured with a repeat cycle (for example, utilizing the `AT`, `EVERY`, and `EVERYENDTIME` keywords), the system did not behave as expected. Although the run cycle preview would correctly display the expected scheduled times, the actual execution generated an extra, unexpected instance at the Start of Day (for example, at 00:00). To work around this issue, users had to either define the run cycle directly in the job stream or move the time restrictions and recurrences out of the run cycle group and into the job stream schedule. This issue is now resolved. The scheduling logic has been updated to ensure that when a run cycle group contains a repeat cycle, only the correct, expected job stream instances are generated during actual execution, and no additional Start of Day instances are erroneously created.
IJ58315	Fixed password encryption failure when using the percent symbol (%) with the pwdcrypt command. Previously, encrypting a password that contained a percent symbol (`%`) using the `pwdcrypt` command failed and returned an invalid format character error. This issue occurred because the underlying `enigma` encryption utility did not properly accept the percent symbol in recent versions (such as 10.2.6), despite functioning correctly in older releases. This issue is now resolved. The `pwdcrypt` command has been updated to correctly accept and encrypt passwords that include the percent symbol, successfully generating the encrypted password as expected.
IJ58499	Fixed connection errors when multiple users share the same useropts file for command-line clients Previously, when multiple users on the same IBM Workload Scheduler instance attempted to share and use the same custom useropts file (for example, `.TWS/useropts-service_account`) to supply connection parameters for command-line clients like `conman` and `composer`, the connection failed. The system incorrectly generated `AWSBEH006E` and `AWSBEH027E` errors, stating that the password or connection parameters were missing or not completely defined in the configuration file. This issue is now resolved. The command-line utilities have been updated so that different users on the same instance can successfully access and utilize a shared `useropts` file, allowing `conman` and `composer` to initialize the HTTP or HTTPS connection without encountering missing parameter errors.
IJ58595 - KB0131268	Fixed CPU high utilization during Orchestration CLI model extraction of numerous objects Previously, when using the Orchestration CLI (`ocli`) `model extract` command to export a high number of scheduling objects (such as job streams) into a YAML file on the current backup master domain manager, IBM Workload Scheduler experienced severe performance degradation. The CPU utilization would unexpectedly increase, causing all jobs to fall into a wait state and disrupting normal workload processing. This issue is now resolved. The object extraction process within the Orchestration CLI has been optimized to efficiently handle large quantities of objects. Users can now successfully extract extensive YAML files without causing excessive CPU consumption or interrupting job executions.
IJ58668	Fixed password decryption failure when importing user definitions Previously, when migrating data from an older environment (such as version 10.1 Fix Pack 5) to a newer environment (such as version 10.2.6), importing user definitions with encrypted passwords failed with the error `AWSJOM924E`.This issue occurred when you exported user definitions using the `composer extract` command in conjunction with the `WA_EXPORT_PWD` environment variable, and then attempted to import them into the new environment using the `composer add` command. This issue is now resolved. The `composer add` command now correctly decrypts the provided passwords and successfully imports the user definitions into the new environment as expected.
IJ58678	Fixed code issue causing JnextPlan to fail on Windows. Previously, when running the JnextPlan script on Windows environments (specifically observed in version 10.2.7) to create or extend a production plan, the command would fail if specific arguments were used. Specifically, when passing arguments like `-from`, `TZ` (time zone), and `-for` (such as extending the plan with `-for 2400`), the script encountered a coding error. It returned an error stating `invalid command name "match"` while attempting to parse the command-line arguments within the `JnextPlan.tcl` file, preventing the plan from being generated successfully. This issue is now resolved. The JnextPlan script has been corrected to properly process and parse all command-line arguments, ensuring that production plan generation and extensions complete smoothly without syntax errors.
IJ58750	Fixed an issue where job rerun operations initiated from the Dynamic Workload Console failed to apply the specified priority values. Previously, rerunning a completed job from the Dynamic Workload Console and providing a new priority value resulted in the rerun job being created without the requested priority. This issue has been resolved to ensure that rerun requests consistently apply the newly specified priority value to the rerun job.
IJ58886	Fixed infinite loop issue in AgentCertificateDownloader for Windows dynamic agents. The AgentCertificateDownloader script is used to securely download and deploy certificates in PEM format from the master domain manager to ddynamic agents and fault-tolerant agents. Previously, when running this script to correct mismatched or expired certificates on Windows dynamic agents (specifically observed in IWS 10.2.7), the script would fail to copy the necessary certificate files and instead fall into an infinite loop. This looping behavior caused the `AgentCertificateDownloader_10.2.7.00.log` file to rapidly bloat, repeating specific log entries (such as "echo vars after initLocalVariablesPostInput" and "program called from install dir") tens of thousands of times. The script would remain stuck until it was manually interrupted by an administrator. Prior to this fix, the only workaround was to manually copy the certificates from the master domain manager directly to the dynamic agents. This issue is now resolved. The AgentCertificateDownloader script has been corrected to process certificate discrepancies properly and complete the deployment process without entering a loop state.
KB0103894 - IJ54657	Fixed batchman process failing to switch TWSMERGE.log files on the first day of the month Previously, when the Start of Day (SOD) time was configured to a value other than `0000`, the `batchman` process failed to correctly switch its trace log file on the first day of a new month. By design, IBM Workload Scheduler log files are supposed to switch every day, creating new log files with the new datestamp exactly at the time set in the `startOfDay` global option. However, due to this defect, on the first day of the month (for example, February 1st), `batchman` on both the master domain manager and fault-tolerant agents would continue writing trace messages to the previous date's log file (for example, `20230131_TWSMERGE.log` in the `stdlist/traces` directory) instead of creating the new month's file (`20230201_TWSMERGE.log`). While other control processes like `jobman` switched their logs correctly, `batchman` would not recover and switch to the correct date pattern until the second day of the month. This issue is now resolved. The `batchman` process has been updated to properly handle month-end and start-of-day calculations. It now correctly switches to the new date's `TWSMERGE.log` file on the first day of every month at the specified SOD time, ensuring trace files are generated consistently across all processes.
KB0130577	Fixed an issue where successors were not displayed during multiple job stream submissions Fixed an issue where the interface failed to display successors when multiple job streams were submitted simultaneously. Previously, in environments configured with an Oracle 19 database, submitting multiple job streams resulted in the successors of those job streams not being displayed. The system has been updated to correctly retrieve and display successors during multiple job stream submissions when using an Oracle 19 database.
KB0130752	Fixed high CPU usage on PostgreSQL and associated job dispatcher errors in messages.log Previously, environments utilizing a PostgreSQL database server could experience unexpectedly high CPU usage. Accompanying this performance degradation, the WebSphere Application Server Liberty `messages.log` file would incorrectly record `AWKJDE163E` errors from the `com.ibm.scheduling.jobdispatcher` component. These errors indicated a failure to cancel job allocations due to a null reference exception (specifically, failing to invoke `java.lang.Object.toString()` because a method return value was null). This issue is now resolved. The job dispatcher logic has been updated to properly handle job allocation cancellations without triggering null reference exceptions. This ensures that the `messages.log` remains free of these unexpected errors and resolves the associated high CPU consumption on the PostgreSQL database server.

Table 2. Installation process – APARs fixed in this release
Code	Description
IJ53108	Added missing HTTP security headers to prevent data leakage and phishing attacks. Previously, specific HTTP security headers were missing from the application, which was identified during penetration testing. The missing headers included the `Permissions-Policy` header (used to explicitly restrict the APIs that the site's code can access) and the `Referrer-Policy` header. The absence of these security headers increased the potential risk for cross data leakage, unauthorized data tracking, and phishing attacks. This issue is now resolved. The `Permissions-Policy` and `Referrer-Policy` HTTP headers have been implemented to explicitly define allowed website functionality and ensure a more secure environment against vulnerabilities.
IJ58709	Fixed incorrect prerequisite validation preventing Dynamic Workload Console and master domain manager installation or upgrade on SLES 15. Previously, when attempting to install or upgrade the Dynamic Workload Console or master domain manager to version 10.2.6 on SUSE Linux Enterprise Server (SLES) 15, the prerequisite validation phase could incorrectly fail. This occurred because the installation package's prerequisite definitions did not properly include Dynamic Workload Console and master domain manager in the list of supported components for SLES 15, causing the installer to mistakenly reject valid environments and terminate the deployment. To work around this, users had to manually bypass the system scanner using the `-skipcheckprereq true` parameter during the installation command. This issue is now resolved. The prerequisite configuration in the installation package has been updated to correctly identify SLES 15 as a supported operating system for both Dynamic Workload Console and master domain manager. This ensures that installations and upgrades proceed successfully without requiring a manual prerequisite bypass.
IJ58742	Fixed installation and upgrade failure on AIX systems caused by group ownership syntax. Previously, when installing or upgrading IBM Workload Scheduler components (such as a dynamic agent) to versions 10.2.6 or 10.2.7 on an AIX system, the process could fail during the Java extension installation. This issue occurred because the script attempted to change file ownership using a user-and-group syntax (for example, `chown -R user:group`). Unlike other standard UNIX systems, AIX strictly rejects this syntax if the specified group is not defined. If the agent user did not have a group assigned, this caused the command to fail and the upgrade to terminate. This issue is now resolved. The installation and upgrade scripts have been updated to handle ownership changes correctly on AIX and OS400 systems (by omitting the group syntax when no group is defined), ensuring that the deployment completes successfully without failing on group ownership assignments.
KB0131669	Fixed dynamic agent installation failure when using the apikey option. Previously, when installing a dynamic agent on version 10.2.7 and using the apikey parameter to automatically authenticate with the master domain manager and download certificates, the installation failed. Although the AgentCertificateDownloader.sh script executed and successfully generated the `wa_certificates.zip` archive, the installer unexpectedly halted with a `WAINST0246E` error. This occurred because the system incorrectly reported that the tls.sth file—which is required to store the password in Base64 encoding—was missing and the SSL password was blank. To bypass this, users had to manually supply the certificates by performing the installation with the -sslkeysfolder and -sslpassword parameters. This issue is now resolved. The installation process has been updated to ensure that when using the apikey option, the required password stash file (tls.sth) is properly handled and downloaded, allowing the dynamic agent installation to complete successfully without requiring manual certificate workarounds.

Table 3. Command-line component – APARs fixed in this release
Code	Description
IJ47501	Fixed password length validation for the conman altpass command Previously, when using the `conman altpass` command to alter a user object's password in the production plan, the system incorrectly accepted passwords longer than the documented 30-byte limit when they were provided via an explicit command string (for example, `altpass workstation#user;"password"`).This issue is now resolved. The `altpass` command has been updated to correctly enforce the maximum password length. Attempting to set a password that exceeds the allowed limit now properly causes the operation to fail, preventing the system from saving incorrect data.
IJ55696	Fixed password length limitation for the altpass command outside of conman. Previously, when altering a user object's password in the production plan, setting a 31-character password using the altpass command only worked when executed interactively from within the conman utility. Attempting to run the command externally from the command prompt failed for 31-character passwords, although it worked correctly for passwords that were 30 characters or shorter. This issue is now resolved. The altpass command has been updated to correctly process and apply passwords of 31 characters or more regardless of whether the command is executed interactively from inside conman or from an external command prompt.
IJ57335	Fixed certificate validation failure during Windows agent installation caused by trailing backslashes. Previously, installing a Windows dynamic agent might fail during the certificate validation step, generating a `WACOMM001E` error. This issue occurred when the certificate directory path provided in the `-sslkeysfolder` parameter was enclosed in double quotes and ended with a backslash (for example, `"E:\ProgramFiles\IBM\default_certs\"`). The trailing backslash incorrectly escaped the closing double quote, causing the `certman` utility to receive an incorrect path string and fail the validation. This issue is now resolved. The installation process and `certman` utility have been updated to correctly handle and parse double-quoted paths ending with a backslash, ensuring that the certificate validation succeeds and the agent installation completes as expected.
IJ57925	Fixed plain text password exposure in audit logs when using the conman altpass command with a space Previously, when using the `conman altpass` command to change a user object password in the production plan, separating the username and the new password with a space instead of a semicolon (for example, `conman "altpass username 'password'"`) caused a security vulnerability. Although the command completed successfully, the new password was incorrectly recorded in plain text within the audit logs (specifically in the `actionDependentContents` field of the JSON log files). The proper masking behavior—where the password is automatically replaced with asterisks (`********`)—only occurred when using the documented semicolon syntax (for example, `conman "altpass username;"password""`). This issue is now resolved. The audit logging mechanism has been updated to properly detect and mask the password regardless of whether a space or a semicolon is used to separate the arguments in the `altpass` command. This ensures that passwords are consistently encrypted and never exposed in plain text within the audit logs.
IJ58057	Fixed incorrect help output and syntax for the wa_pull_info command Previously, querying the help information for the wa_pull_info data collection utility displayed incorrect syntax for the `-isroot` parameter (showing `-isroot <true\|false>` instead of the correct `-isroot=true\|false`). Furthermore, the utility did not accept the `-?` flag to display the help information, despite it being documented as a valid flag. This issue is now resolved. The utility has been updated so that the command's help output and accepted flags correctly match the correct behavior and the official product documentation.
IJ58381	Fixed daily REPORT8.EXE error events during FINAL job stream run on Windows master domain managers. Previously, executing the daily FINAL job stream on a Windows master domain manager generated `REPORT8.EXE` error events in the Windows Event Viewer, even though the FINAL and FINALPOSTREPORTS job streams completed successfully. This issue occurred because the `rep8` utility code prevented the archived Symphony files from being read correctly, causing the process to hang or terminate prematurely. This issue is now resolved. The `rep8` utility has been updated to correctly read the Symphony files without hanging or terminating, ensuring that the reporting processes complete successfully and eliminating the daily error events.
IJ58629	Fixed fault-tolerant agent installation failure caused by the certman command. Previously, installing a fault-tolerant agent (such as version 10.2.6) could unexpectedly fail on certain servers. This issue occurred because the certman command encountered a runtime error (`panic: runtime error: slice bounds out of range`) during the certificate installation process when attempting to run the `certman extract` command to extract certificates to the output path. This issue is now resolved. The certman command has been updated to correctly process the certificate extraction without triggering a runtime error, ensuring that the fault-tolerant agent installation can complete successfully as expected.
IJ58725 - KB0131631	Fixed incorrect default port indicated in Orchestration CLI missing port error message Previously, if a user did not specify a port for the Orchestration CLI using its `config.yaml` file, IBM Workload Scheduler prompted a `WSMRC023W` error message stating that port 443 would be used by default. However, this message was misleading because the actual default port for IBM Workload Scheduler command-line clients is 31116, and the default port for HCL Universal Orchestrator is 8443.This issue is now resolved. The error prompt has been updated to correctly reflect the appropriate default port values when a port is left empty in the configuration file, eliminating confusion for users connecting to IBM Workload Scheduler or HCL Universal Orchestrator environments.
IJ58754	Fixed incorrect rerun attempt display in job properties Previously, when checking a job properties using the `conman sj` (showjobs) command with the `;props` argument (for example, `conman "sj @#<job_number>;PROPS"`), IBM Workload Scheduler displayed incorrect rerun attempt information. Even if a job was configured for multiple reruns and was currently on a later attempt (such as rerun 46 of 1000), the runtime information in the output would incorrectly show it as the first attempt (for example, displaying "Rerun Options = Recovery Job, Rerun 1 of 1000"). This issue is now resolved. The command output has been updated to correctly track and display the current rerun attempt, ensuring that the job properties accurately reflect the exact number of reruns that have been performed.
KB0132002	Fixed OCLI authentication failures for personal API keys in Okta/Keycloak containerized environments. Previously, users attempting to authenticate to the Orchestration CLI using personal API keys in an Okta or Keycloak-based containerized environment would encounter an authentication failure (error `AWSMRC021E`). While the default administrative `wauser` API key worked successfully, personal API keys caused the WebSphere Application Server Liberty `messages.log` to report an `EntityNotFoundException` and a `CWWKS1106A` error, indicating that the user ID was invalid or could not be found in the registry. This issue is now resolved. The configuration has been corrected so that personal API keys can authenticate successfully without encountering registry mapping errors.

Table 4. Docker – APARs fixed in this release
Code	Description
IJ58327	Performance degradation in the conman sj command when managing a huge amount of CPUs and folders. Previously, users experienced significantly low performance and slow response times when running the conman sj (showjobs) command in environments configured with a massive number of workstations (referred to as CPUs) and folders. The conman sj command is heavily used by administrators to monitor and display the status of jobs in the production plan. However, when the environment scaled up to include a huge hierarchy of folders used to organize these workstations and scheduling objects, the command's execution speed degraded. This issue is now resolved. The processing of the conman sj command has been optimized to efficiently handle large-scale environments with vast amounts of CPUs and complex folder structures, ensuring that job status queries complete quickly and without performance bottlenecks.
KB0132259	Fixed issue causing manual ACL entries to be lost after an upgrade. Previously, in 10.2.7 environments utilizing a master domain manager and the Dynamic Workload Console, Access Control List (ACL) entries that were manually configured through the Dynamic Workload Console would be lost after performing an upgrade. Specifically, following a WebSphere Application Server Liberty upgrade and subsequent POD restart, administrators would find that all manually configured ACL entries had been removed and were no longer present in the engine security file. This issue is now resolved. The system has been corrected to ensure that ACL configurations remain persistent and are properly retained across standard pod restarts, recycles, and full upgrades.

Table 5. dynamic domain manager (broker) – APARs fixed in this release
Code	Description
IJ57884	Fixed missing certificate expiration date for dynamic agents connected to a dynamic domain manager. Previously, the certificate expiration date for dynamic agents connected to a dynamic domain manager was not visible. Even after running the Update agent action, the expiration date failed to populate in the Orchestration Monitor screen. This issue is now resolved. The certificate expiration date now correctly populates and displays in the Orchestration Monitor for dynamic agents connected to a dynamic domain manager, allowing you to accurately track when certificates expire and easily verify the success of agent certificate updates.
IJ57890	Fixed suppression of standard error messages in dynamic workload broker scripts. Previously, when running the `exportserverdata.sh` and `importserverdata.sh` scripts (located in the `{TWA_HOME}/TDWB/bin` directory), any standard error messages generated by the commands were suppressed and not visible to the user. This issue occurred because the standard error output was being redirected to `/dev/null` within the scripts. This issue is now resolved. The standard error redirection has been removed from these scripts, ensuring that all generated errors are properly printed to the console to assist with troubleshooting and debugging.
IJ58187	Fixed erroneous "404 Not Found" messages in the dynamic domain manager messages.log file Previously, updating to version 10.2.6 introduced unexpected error conditions into the dynamic domain manager messages.log file. Specifically,IBM Workload Scheduler incorrectly logged a "404 Not Found" error from the `com.ibm.scheduling.master.rest.impl.MasterRESTImplE` component when attempting to invoke the `updateWorkstationToPlan` REST service for dynamic agents. Despite generating these error logs, the messages were entirely benign and did not cause any functional issues or impact actual workload processing. This issue is now resolved. The system has been updated to prevent these erroneous and misleading messages from being unnecessarily recorded in the messages.log file, ensuring cleaner and more accurate diagnostic logs.
IJ58730 - KB0131641	Fixed database deadlocks and delayed scheduling during massive agent resource scans Previously, a database deadlock could occur when a large volume of full resource scans arrived simultaneously from multiple agents (such as after long periods of disconnection or following hardware changes). This deadlock involved the `ARE_ABSTRACT_RESOURCES` table and resulted in significant scheduling delays, causing jobs to remain stuck in a `WAIT+` status and generating `RDBMS_LOCK_PROBLEM` errors in the logs. This issue is now resolved. The database operations are now handled correctly and appropriate indexing is utilized during massive agent scans, preventing deadlocks on the `ARE_ABSTRACT_RESOURCES` table and ensuring that jobs are scheduled without unnecessary delays.

Table 6. Report CLI– APARs fixed in this release
Code	Description
KB0130879	Added PostgreSQL configuration section to the reportcli common.properties file Previously, when setting up command line reporting using the reportcli utility, the common.properties configuration file did not include a dedicated section for PostgreSQL databases. To connect to a PostgreSQL database, users had to manually define the database type (`DatabaseType=POSTGRES`) and configure the remaining connection parameters themselves as a workaround. This issue is now resolved. The common.properties template file has been updated to include a predefined configuration section specifically for PostgreSQL, ensuring that the command line reporting utility can be configured directly without requiring manual parameter workarounds.
KB0131193	Fixed reportcli crashing with out-of-memory errors when processing large reports. Previously, when users attempted to run a large Custom SQL report using the command-line reporting utility (reportcli), the process would frequently fail and crash. Specifically, the Java process running reportcli would exhaust its allocated memory, resulting in a `java.lang.OutOfMemoryError: Java heap space` exception and generating Java dump files. This prevented the successful generation of extensive reports. This issue is now resolved. The reportcli utility has been optimized to properly handle and process large Custom SQL reports without exhausting the available Java heap space, ensuring that massive reports can be generated successfully without crashing.

Table 7. AIDA CLI– APARs fixed in this release
Code	Description
KB0129799	Configurable tolerance values added to AIDA to prevent false anomaly detection. Previously, when the AI Data Advisor (AIDA) component analyzed trends by comparing observed KPI data points with expected values, its algorithms evaluated these metrics using strict decimals without any buffer. Because of this, if the Predictor service calculated a fractional expected value (such as 0.25) but the actual measured value was 0, the system would incorrectly flag the minor discrepancy as a violation. This caused the dashboard to display false anomalies for most KPIs, even when the actual deviation was virtually zero. This issue is now resolved. The AIDA code has been enhanced to include the ability to configure a tolerance value for KPI evaluations. This tolerance is evaluated as the maximum between a fixed and a dynamic value (for example, allowing a 5% deviation of the maximum expected value). With this enhancement, minor decimal variances are safely ignored (for instance, if 1000 jobs are predicted and 1050 are executed, it falls within a 5% tolerance and is not flagged), ensuring the dashboard accurately reports true anomalies without unnecessary alerts.

Table 8. Documentation – APARs fixed in this release
Code	Description
IJ57779	Added missing documentation for dynamic pool optimization policies and sub-fields. Previously, the product documentation lacked detailed information regarding dynamic pool optimization policies and their specific configuration sub-fields. Specifically, essential details and explanations were missing for the following fields: Optimization More options Logical Resources Ordered Workstations File Systems This issue is now resolved. The documentation has been appropriately updated to include the necessary details for configuring dynamic pool optimization policies and all of their related sub-fields.
IJ58167	Corrected the documented logman command syntax in the recovery procedure. The logman command is used to log job statistics from a production plan log file. Previously, the product documentation for the recovery procedure using logman contained a defect. It incorrectly instructed users to execute the logman -prod command. This documentation issue is now resolved. The recovery procedure guide has been updated to accurately reflect the correct step. Users are now properly instructed to run the command as logman prod <Symphony-file-or-equivalent-schedlog> to ensure the command targets the correct archived Symphony file or scheduling log located in the `schedlog` directory.
IJ58269	Corrected the documented location of the exportserverdata script. Previously, the product documentation for the exportserverdata command incorrectly identified its default location on UNIX systems. It stated that if you did not specify a path for the `-exportFile` parameter, the temporary file would be created in the <TWS_DATA>/TDWB_CLI/bin directory. However, this `bin` folder does not actually exist under that path. This documentation issue is now resolved. The documentation has been updated to accurately state that the exportserverdata script is located in the TWA_home/TDWB/bin.
IJ58309	Updated documentation for maximum r3password length. Previously, the product documentation for the SAP access method local configuration options incorrectly stated that the `r3password` (the password for the SAP `r3user`) had a maximum length of eight characters. This issue is now resolved. The documentation has been updated to accurately reflect the correct password length limits. The maximum password length for the `r3password` parameter is now 40 characters for un-encrypted passwords, and up to 72 characters for encrypted passwords.
IJ58323	Updated documentation regarding Job Output Condition evaluation limits for RESTful jobs. Previously, the product documentation did not explicitly warn that evaluating Job Output Conditions (such as checking the `this.stdlist` variable) for RESTful jobs with long polling intervals could result in false negative statuses. Because the dynamic workload broker restricts the scanning of exceptionally large logs to prevent performance degradation, success patterns positioned too deep within a large log file might not be found. This causes the job to fail its defined output condition (evaluating to `SUCCESS : false`) even if the underlying cloud or REST execution completed successfully. This issue is now resolved. The product documentation for advanced job types has been updated to explicitly note this limitation, advising users that output condition string matching might fail on exceptionally large logs generated by extended polling intervals.
WA-57867	Corrected documentation for the enPreventStart global option. Previously, the product documentation incorrectly described the behavior of the enPreventStart global option when it is set to `yes`. The manuals stated that job streams without an `at` time constraint would wait for the `startOfDay` (SOD) time on their scheduled date before starting. However, the actual product behavior is that these job streams will start at 00:00 of the scheduled date and do not wait for the SOD, provided they are free from dependencies. This defect is now resolved by updating the Reference Guide and related readmes to accurately reflect the true system behavior. The documentation now correctly clarifies that when enPreventStart=yes, a job stream cannot start before 00:00 on the scheduled system date, even if it is free from dependencies.

Defects fixed in version 10.2.8

This section lists defects resolved in version 10.2.8, divided by component.

Table 9. Command-line interface – Defects fixed in this release
Table 10. Documentation – Defects fixed in this release
Table 11. Dynamic domain manager – Defects fixed in this release
Table 12. Engine – Defects fixed in this release
Table 13. Installation – Defects fixed in this release
Table 14. REST APIs – Defects fixed in this release

Table 9. Command-line interface – Defects fixed in this release
Code	Description
WA-163763	Fixed certman crash caused by directories sharing the control script name. Previously, the certman utility could unexpectedly end in error because it was unable to determine whether it was launched from the product image or from a classic installation. This issue occurred when certman encountered a directory in the path with the exact same name as the control script used to perform the check. By mistakenly identifying the directory as the script file, the path handling logic failed. This issue is now resolved. The certman utility has been updated to correctly differentiate between a directory and a file. This ensures it accurately identifies its launch context without breaking the control logic, crashing, or incorrectly setting the component to an unknown state.

Table 10. Documentation – Defects fixed in this release
Code	Description
WA-57867	Corrected documentation for the enPreventStart global option. Previously, the product documentation incorrectly described the behavior of the enPreventStart global option when it is set to `yes`. The manuals stated that job streams without an `at` time constraint would wait for the `startOfDay` (SOD) time on their scheduled date before starting. However, the actual product behavior is that these job streams will start at 00:00 of the scheduled date and do not wait for the SOD, provided they are free from dependencies. This defect is now resolved by updating the Reference Guide and related readmes to accurately reflect the true system behavior. The documentation now correctly clarifies that when enPreventStart=yes, a job stream cannot start before 00:00 on the scheduled system date, even if it is free from dependencies.

Table 11. Dynamic domain manager – Defects fixed in this release
Code	Description
WA-161704	Fixed `NullPointerException` during job allocation cancellation. Previously, a `NullPointerException` could occur in the job dispatcher when attempting to cancel a job allocation. This happened because a null value was unexpectedly returned when evaluating the endpoint reference type, which generated an `AWKJDE163E` error in the logs. This defect had a severe impact on performance, causing the database to reach 100% CPU usage and completely halting scheduling operations. This issue is now resolved. The allocation cancellation logic has been updated to correctly handle these reference values, preventing the null pointer error, eliminating the excessive database CPU consumption, and ensuring that scheduling operations continue without interruption.
WA-164313	Fixed deadlock on Oracle 19 databases during delete operations. Previously, a deadlock could occur in the dynamic domain manager (DWB) when performing delete operations on the `ARE_ABSTRACT_RESOURCES` table within an Oracle 19 database environment. This issue is now resolved. Delete operations on the `ARE_ABSTRACT_RESOURCES` table are now handled correctly, preventing deadlocks from occurring on Oracle 19 databases.

Table 12. Engine – Defects fixed in this release
Code	Description
WA-160877	Fixed missing job stream information in plan audit files during multiple job stream submissions. Previously, when performing a multiple job stream submission scenario, the plan audit files located in the `/home/wauser/wadata/audit/plan/` directory were not updated with the relevant job stream information. This issue is now resolved. The multiple job stream submission process has been updated to ensure that all job stream details are correctly logged in the plan audit files when submitting multiple job streams.
WA-160878	Fixed missing plan audit information and justification notes during multiple job stream submissions. Previously, when performing a multiple job stream submission scenario, the plan audit information and justification notes were not correctly saved to the database. As a result, the plan audit files located in the /home/wauser/wadata/audit/plan/ directory were not updated with the relevant job stream submission details. This issue is now resolved. The multiple job stream submission process has been updated to ensure that all plan audit information and user justifications are correctly recorded in the database and logged in the appropriate audit files.
WA-161551	Fixed incomplete multiple job stream submission when using run cycles. Previously, when using the Orchestration Monitor to submit multiple job stream instances generated by a run cycle, an issue prevented all the instances from being successfully submitted. Even if multiple instances were generated and selected for submission, only the first instance was actually added to the production plan. This issue is now resolved. The multiple job stream submission service has been updated to ensure that when multiple instances are generated by a run cycle and submitted, all selected instances are correctly added to the plan. The number of submitted job streams now accurately matches the expected amount on the Orchestration Monitor page.

Table 13. Installation – Defects fixed in this release
Code	Description
WA-165038	Fixed infinite loop and system freeze caused by AgentCertificateDownloader during upgrade Previously, during an upgrade from version 10.2.6 to 10.2.7, the `AgentCertificateDownloader` script—which is used to securely download and deploy certificates from the master domain manager to dynamic and fault-tolerant agents—could unexpectedly enter an infinite loop. This behavior caused the entire system to freeze and prevented the upgrade process from proceeding. This issue is now resolved. The `AgentCertificateDownloader` component has been updated to successfully process and download the required certificates without entering a loop, ensuring that the upgrade process completes smoothly and without interruption.

Table 14. REST APIs – Defects fixed in this release
Code	Description
WA-142355	Fixed folder filtering issues for jobs and job streams in Orchestration CLIand REST APIs v2 Previously, when attempting to filter jobs or job streams organized within folders (for example, when querying multiple job streams or sequence rerunning jobs), the filters did not work correctly in the Orchestration CLI and REST APIs v2. Unlike the conman utility, which successfully retrieved information using standard wildcard filters at any folder level (such as `ss @#/SAP/@` or `sj @#/SAP/SAP@`), `ocli` and APIs v2 failed to return the expected results unless specific folder-level filters were omitted (for example, incorrectly requiring `ocli plan ss @#/SAP/`). This inconsistent behavior affected all actions on jobs and job streams that relied on these filters. This issue is now resolved. The Orchestration CLI and REST APIs v2 have been updated to properly process and apply filters at any folder level. Users can now successfully use the exact same filtering syntax in ocli and API v2 as they do in conman, ensuring consistent and accurate retrieval of job and job stream information across all interfaces.

Resolved Common Vulnerabilities and Exposures (CVEs)

The following CVEs have been resolved:

Table 15. List of resolved vulnerabilities by severity
CVE ID	Severity
CVE-2025-8677	High
CVE-2026-29111	High
CVE-2026-33636	High
CVE-2026-33811	High
CVE-2026-34982	High
CVE-2026-35385	High
CVE-2026-39822	High
CVE-2026-39827	High
CVE-2026-42198	High
CVE-2026-42504	High
CVE-2026-42583	High
CVE-2026-43869	High
CVE-2026-47244	High
CVE-2026-4786	High
CVE-2026-4878	High
CVE-2026-54512	High
CVE-2026-5450	Medium
CVE-2026-45292	Medium
CVE-2026-54515	Medium

Interoperability tables

In the tables in this section the following acronyms are used:

Table 16. **Acronym table**
Acronym	Extended form
DA	Dynamic agent
DDM	dynamic domain manager or backup dynamic domain manager
DM	domain manager
DWC	Dynamic Workload Console
FTA	fault-tolerant agent
MDM	master domain manager
BKM	backup master domain manager
ZWS agent	IBM Z Workload Scheduler Agent (also known as z-centric agent)

Compatibility is supported on the latest available release level for each IBM Workload Scheduler release listed in the table:

Table 17. **Compatibility table for** **IBM Workload Scheduler**
Component	MDM	DDM	DM	FTA	DA	ZWS agent
MDM 10.2.8		10.`x.x` 9.5.0.`x` *()**	10.`x.x` 9.5.0.`x` *()**	10.`x.x` 9.5.0.`x` *()**	10.`x.x` 9.5.0.`x` *()**	10.`x.x` 9.5.0.`x` *()**
DM 10.2.8	10.`x.x`			10.`x.x`
FTA 10.2.8	10.`x.x`	10.`x.x`	10.`x.x`
DA 10.2.8	10.`x.x`	10.`x.x`	10.`x.x`
DDM 10.2.8	10.`x.x`			10.`x.x`	10.`x.x`

(*) Important information regarding agents at 9.5 version

If you currently have agents at 9.5 version, read the following information:

Support for 9.5 agents is limited to the upgrade period.
The required upgrade approach is the top-down approach. For more information, see Choosing how to upgrade your network.
The recommended upgrade procedure is a parallel upgrade. For more information, see Parallel upgrade from version 9.5.0.x or 10.x.x to version 10.2.8.

Table 18. **Compatibility table for OCLI**
Component	MDM
OCLI 10.2.8 OCLI 10.2.7 OCLI 10.2.6	10.2.8

The Orchestration CLI version must be equal to or lower than the master domain manager version. The Orchestration CLI can run at most two versions below the master domain manager. Using an Orchestration CLI that is newer than, or more than two versions older than, the master domain manager is not supported.

Table 19. **Compatibility table for AIDA**
Component	MDM	DDM	DWC
AIDA 10.2.8	10.`x.x`	10.`x.x`	10.`x.x`

Compatibility scenarios and limitations

It is highly recommended to keep all IBM Workload Scheduler components updated to the latest version as part of regular maintenance. This not only maintains a consistent environment but also enables you to utilize new features introduced in each release.

Known limitations and workarounds

The following are software limitations and workarounds that affect IBM Workload Scheduler 10.2.8:

Mixed-version environment with a master domain manager at a version earlier than 9.5 FP4

Before you install a component at version 10.2.8 in an environment with a master domain manager at a version earlier than 9.5 FP4, install the fix for IJ47731 on the back-level master domain manager.

Fix availability is as follows:

For version 9.4 FP7, the fix is available from IBM Fix Central.
For other product versions, contact Software Support.

For more information, see IJ47731: CHECKSYNC JOB FAILED IN IWS 10.1 FP02 - AWSJCL075E ERROR

Event-driven workload automation (EDWA) proxy does not support HTTPS connections

Event-driven workload automation (EDWA) proxy supports only HTTP connections. As a result, SSL communication is not supported.

The centralized update on a stand-alone fault-tolerant agent V10.2.1 is not supported

The centralized update on a fault-tolerant agent V10.2.1 is not supported, regardless of the operating system. For more information about upgrading from different versions, see Performing the centralized agent update on a stand-alone fault-tolerant agent.

Pool connection issues with CyberArk

If you are using a pool as a gateway to communicate with CyberArk and an agent within the pool loses connection to the CyberArk server, the job assigned to that specific agent fails. For instance, if an agent remains up and running but stops communicating with CyberArk, any jobs assigned to that agent that require a connection to CyberArk fails. This occurs because the pool lacks the ability to verify whether its agents are connected to the CyberArk server.

Folder filtering discrepancy in Command Line Interfaces

Filtering for jobs and job streams within folders with Orchestration CLI or REST APIs V2 using conman syntax might not work as expected, returning different results from the ones retrieved using conman.

Japanese characters might display incorrectly in job logs on Windows for Dynamic Workload Console and fault-tolerant agents

Job logs containing Japanese characters might appear garbled when viewed in the Dynamic Workload Console or when using the command line on fault-tolerant agents running on Windows operating systems.

Workaround

To resolve this issue, set a Windows environment variable that points to the IBM Workload Scheduler home directory, for example:

TWS_TISDIR=C:\FTA\TWS

Unresolved dependency state with shadow jobs and start of day setting

Successor jobs remain permanently in the HOLD state, even after the shadow job predecessors successfully complete. This happens specifically when the job stream execution crosses the customized Start of Day boundary due to the job rerun logic. The product correctly updates the final status of the shadow job to SUCC, but the dependency is not released when the related scheduling event occurs close to or across the startOfDay. The job is effectively orphaned in the queue, stuck in HOLD despite having met its only prerequisite.

ABENDPROMPT Failure to Suppress RERUN on AIX operating systems

On AIX operating systems, the presence of an ABENDPROMPT setting fails to correctly block the automatic execution of the RECOVERY RERUN action when a job terminates in the ABEND state.

The job manager fails to prioritize the prompt mechanism, which should transition the job to a waiting state and generate an immediate ASKED prompt, thereby overriding or delaying the automatic RERUN defined in the recovery policy.

This failure results in an uncontrolled automatic rerun, bypassing the required human intervention point defined by the ABENDPROMPT setting.

Database job connection tests to Microsoft SQL Server might fail with an SSL certificate error

A known limitation exists where testing the connection for a Database job to a Microsoft SQL Server database might fail. When this occurs, the system returns an AWKDBE023E error indicating that the database driver could not establish a secure connection using Secure Sockets Layer (SSL) encryption. This issue occurs when the encrypt connection property is set to true and the trustServerCertificate property is set to false, but the driver cannot find a valid certification path to the requested target.

Jobs incorrectly display a Cancel Pending status after being unmarked as a No operation (UNNOP) and rerun

A known limitation exists where the Orchestration CLI incorrectly displays a job's internal status as Cancel Pending after the job has had its No operation (NOP) property removed and is rerun. When a user marks a job as a No operation (using the nop command), it is subsequently set to a Cancelled status. If the user then removes the NOP property (using the unnop command) and reruns the job (using the rerun or rr command), the job correctly executes but inaccurately retains a Cancel Pending internal status instead of updating to Success.

Error importing users with Orchestration CLI after exporting with composer

When you use the composer extract command with the password argument and a passphrase, user definitions are saved to a file with their passwords in an encrypted format. However, if you attempt to import these definitions back into the database using the ocli model replace command, the process fails. The Orchestration CLI incorrectly evaluates the length of the long, encrypted password string and generates an error stating that the password length exceeds the maximum allowed limit of 31 bytes.

Slow shutdown of the writer process on Windows agents of type both

A problem might occur when attempting to stop an agent configured as type both on a Windows operating system. When launching the shutdown.cmd script to stop the local processes, users may experience a significant delay. While other control processes terminate quickly, the writer process, which is responsible for handling incoming messages and passing them to the local mailman, takes an unusually long time to stop.

Package structure

For a detailed list of available packages, see the 10.2.8 Quick Start Guide document available from IBM Fix Central.

Software requirements for WebSphere Application Server Liberty Base

WebSphere Application Server Liberty Base adopts a continuous delivery model where new versions are deployed on a monthly basis.

During formal testing, IBM Workload Scheduler and the Dynamic Workload Console were tested by using WebSphere Application Server Liberty Base 26.0.0.6.

For the Dynamic Workload Console installed in a z/OS environment, the minimum required version is WebSphere Application Server Liberty Base 26.0.0.3.

For more information about which subsequent versions of WebSphere Application Server Liberty Base can be used in the future, see Recommended updates for WebSphere Application Server.

Installing and upgrading to version 10.2.8

This section describes how to install or upgrade to version 10.2.8.

Before installing the release, ensure you have installed the required prerequisite software. To obtain the latest information about system requirements, run the Detailed System Requirements report and browse to the relevant section.

Installation notes

If you use Oracle AI Database 26ai, you can improve performance by setting the parameters listed in Optimizing performance for Oracle AI Database 26ai.
Before performing an upgrade, check whether the ssl_config.xml file is present in the overrides folder. If the file is present, check the verifyHostname option in the twaSSLSettings section. The verifyHostname must be set to false, as shown in the following example:
```
<ssl id="twaSSLSettings" keyStoreRef="twaKeyStore" trustStoreRef="twaTrustStore" 
sslProtocol="TLSv1.2" clientAuthenticationSupported="true" verifyHostname="false"/>
```

Upgrade notes

Review the following points before upgrading.

MSSQL notes

If you are using MSSQL and are upgrading from a release earlier than 10.2.3, perform the steps listed below after upgrading to version 10.2.8. If you are using MSSQL and are upgrading from release 10.2.3 or a release later than 10.2.3, you can ignore the steps listed below.

Browse to the datasource.xml template.

Open the file with a text editor and perform the following changes:

Add the lines listed below after the db.driver.path parameter:

<variable name="db.encrypt" value="false"/>
<variable name="db.trustServerCertificate" value="false"/>

Append the following strings at the end of the value of the mssql.URL parameter:
```
;encrypt=${db.encrypt};trustServerCertificate=${db.trustServerCertificate}
```

Add the lines listed below after the integratedSecurity parameter:

encrypt="${db.encrypt}"
trustServerCertificate="${db.trustServerCertificate}"

The resulting file looks as follows. The modified sections are highlighted in bold:

...	
	<variable name="db.driver.path" value="<db_driver_path>"/>
	<variable name="db.encrypt" value="false"/>
	<variable name="db.trustServerCertificate" value="false"/>
	<variable name="mssql.URL" value="jdbc:sqlserver://${db.serverName}:${db.portNumber};databaseName=${db.databaseName}
       ;encrypt=${db.encrypt};trustServerCertificate=${db.trustServerCertificate}"/>

	<jndiEntry value="MSSQL" jndiName="db.type" />
...
		    integratedSecurity="false"
		    encrypt="${db.encrypt}"
		    trustServerCertificate="${db.trustServerCertificate}"

Stop and restart WebSphere Application Server Liberty to make the changes effective.

Verify your Single Sign-On settings

When upgrading to Dynamic Workload Console version 10.2.5, if the previous environment is configured for Single Sign-On (SSO) using ltpa.keys, perform the following steps:

Copy the ltpa.keys file either from the master domain manager to the workstation hosting the Dynamic Workload Console, or vice versa, depending on your configuration.
After copying, restart the IBM Workload Scheduler processes on the component where the ltpa.keys file was updated to complete the SSO setup.

Check the alias of your custom certificate before upgrading

Before you upgrade the master domain manager or Dynamic Workload Console, verify the alias you use for your custom certificates. Failure to do so might cause the master domain manager and Dynamic Workload Console to fail at start time and return one of the following errors: CWPKI0024E: The server certificate alias is invalid. or CWPKI0024E: The server certificate alias specified by the attribute serverKeyAlias is either not found in KeyStore or it is invalid.

On UNIX operating systems, you can run the following example command to verify the alias:

Browse to the following paths, depending on the component:

master domain manager: <TWA_DATA_DIR>/usr/servers/engineServer/resources/security
Dynamic Workload Console: <TWA_DATA_DIR>/usr/servers/dwcServer/resources/security

Run the following command:

openssl pkcs12 -in TWSServerKeyFile.p12 -nokeys -info | grep server

On Windows operating systems, you can run the following example command to verify the alias:

Browse to the following paths, depending on the component:

master domain manager: <TWA_home>\usr\servers\engineServer\resources\security
Dynamic Workload Console: <TWA_home>\usr\servers\dwcServer\resources\security

Run the following command:
```
certutil -dump keyfile.p12
```

If a key with the alias server is present, no additional steps are required. The custom certificate with alias server is used by the master domain manager and Dynamic Workload Console.

If your custom certificates use aliases other than server, you can encounter the following situations:

Table 20. Defining the alias for custom certificates
Current status of `ssl_config.xml` file	Steps to be performed
You do not have a customized version of the `ssl_config.xml` file in the overrides folder.	On both master domain manager and Dynamic Workload Console, create a new file named serverkeyalias. xml in the overrides folder with the following content: `<server description="sslSettings_custom_serverkeyalias"> <variable name="serverkeyalias" value="<your_alias>"/> </server>`
You already have a customized version of the `ssl_config.xml` file in the overrides folder.	On both master domain manager and Dynamic Workload Console, edit the `ssl_config.xml` file in the overrides folder as follows: Add the following entry: `<variable name="serverkeyalias" value="server"/>` Change the following entry `<ssl id="twaSSLSettings" keyStoreRef="twaKeyStore" trustStoreRef="twaTrustStore" sslProtocol="${sslprotocols}" clientAuthenticationSupported="true" verifyHostname="false"/>` to read as follows (changes highlighted in bold): `<ssl id="twaSSLSettings" serverKeyAlias="${serverkeyalias}" keyStoreRef="twaKeyStore" trustStoreRef="twaTrustStore" sslProtocol="${sslprotocols}" clientAuthenticationSupported="true" verifyHostname="false"/>`

You can now proceed with the upgrade.

Installation and upgrade procedures

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

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

Disk space requirements

To obtain the latest information about permanent disk space requirements when installing on supported operating systems, run the Hardware requirements report and click on the relevant operating system link.

Performing the centralized agent update on a stand-alone fault-tolerant agent

Before performing a centralized update on fix packs or upgrade on releases on a stand-alone fault-tolerant agent to 10.2.8, there are procedures to follow according to the version of the fault-tolerant agent from which you want to upgrade.

Note: When upgrading a dynamic agent together with a fault-tolerant agent to 10.2.8, if you start the upgrade from the dynamic agent there are no further steps required. The same applies when performing an upgrade of the fault-tolerant agent starting from a dynamic agent.

The table below shows which procedure you must follow to perform the upgrade, according to the fault-tolerant agent version.

Table 21. **Steps required before performing the centralized agent update on a stand-alone** **fault-tolerant agent**
Stand-alone fault-tolerant agent version	Required steps
V9.5 Fix Pack 4 up to V9.5 Fix Pack 6	If not already enabled, enable the use of the HTTPS protocol to connect to the event processor server. For more information about enabling enEventProcessorHttpsProtocol \| eh, see Global options - detailed description
V9.5 Fix Pack 7	No steps required.
V10.1 up to V10.1 Fix Pack 3	If not already enabled, enable the use of the HTTPS protocol to connect to the event processor server. For more information about enabling enEventProcessorHttpsProtocol \| eh, see Global options - detailed description. Then, from the same workstation where the fault-tolerant agent is installed, copy the TWSClientKeyStore files from `TWA_DATA_DIR`/ssl/GSKit to `TWA_DATA_DIR`/ITA/cpa/ita/cert. Note: The owner of the new TWSClientKeyStore files and the permissions granted must be the same of the existing files.
V10.1 Fix Pack 4	If not already enabled, enable the use of the HTTPS protocol to connect to the event processor server. For more information about enabling enEventProcessorHttpsProtocol \| eh, see Global options - detailed description. Then, download the curl file from APAR IJ50967 and save it inside TWS/ITA/cpa/ita. Note: The owner of the new curl file and the permissions granted must be the same of the existing curl file.
V10.2	If not already enabled, enable the use of the HTTPS protocol to connect to the event processor server. For more information about enabling enEventProcessorHttpsProtocol \| eh, see Global options - detailed description. Then, download the curl file from APAR IJ50967 and save it inside TWS/ITA/cpa/ita. Note: The owner of the new curl file and the permissions granted must be the same of the existing curl file.
V10.2.1	Not supported.
V10.2.2 and later	No additional procedure required.

Documentation updates

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

Contacting IBM Workload Scheduler Software Support

Before contacting IBM Software Support with a problem, refer to the IBM Software Support site by accessing the following Web address: https://www.ibm.com/support/home/

To access IBM support, click the IBM support link at the bottom right of the page.

If you want to contact IBM Software Support, see the IBM Software Support Handbook at the following Web site: http://techsupport.services.ibm.com/guides/handbook.html

The guide provides information about how to contact IBM Software Support, depending on the severity of your problem, and the following information:

Registration and eligibility.
Telephone numbers, depending on the country in which you are located.
Information you must have before contacting IBM Software Support.

Notices

This information was developed for products and services offered in the US. This material might be available from IBM Workload Scheduler 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.

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

IBM Workload Scheduler 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:

IBM Director of Licensing
IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
US

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

Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan

INTERNATIONAL BUSINESS MACHINES CORPORATION 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. IBM Workload Scheduler 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-IBM Workload Scheduler 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 IBM Workload Scheduler product and use of those websites is at your own risk.

IBM Workload Scheduler 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:

IBM Director of Licensing
IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
US

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

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

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

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM Workload Scheduler, 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. IBM Workload Scheduler, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM Workload Scheduler shall not be liable for any damages arising out of your use of the sample programs.

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

Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

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

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

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

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

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

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

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

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

ITIL™ is a Registered Trade Mark of AXELOS Limited.

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

Terms and conditions for product documentation: Permissions for the use of these publications are granted subject to the following terms and conditions.

Applicability: These terms and conditions are in addition to any terms of use for the IBM Workload Scheduler 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 IBM Workload Scheduler.

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 IBM Workload Scheduler.

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.

IBM Workload Scheduler 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 IBM Workload Scheduler, 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.

IBM Workload Scheduler 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.

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSGSPN","label":"IBM Workload Scheduler"},"ARM Category":[{"code":"a8m3p000000UoZVAA0","label":"Continuous Delivery"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF012","label":"IBM i"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"10.2.8"}]

Tips

Release Notes for IBM Workload Scheduler 10.2.8