IBM Support

Dynamic Workload Console Version 10.2.8 Release Notes

Release Notes


Abstract

Dynamic Workload Console Version 10.2.8 Release Notes

Content

Dynamic Workload Console version 10.2.8 Release Notes

Release date: July 27, 2026

This document provides important information about Dynamic Workload Console version 10.2.8.

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

For a detailed list of enhancements available in version 10.2.8, see Summary of enhancements.

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

APARs and defects fixed in version 10.2.8

This section lists APARs resolved in version 10.2.8

Table 1. APARs addressed in version 10.2.8
CodeDescription
IJ57788
Fixed an issue where the prerequisite check during a Dynamic Workload Console upgrade from V10.2.4 to V10.2.6 failed due to inaccurate disk space requirements.

Previously, upgrading the Dynamic Workload Console to version 10.2.6 incorrectly demanded 5.144 GB of disk space during the prerequisite verification phase, triggering an installation failure despite the documented requirement being lower. The prerequisite check properties have been updated to properly align with actual hardware requirements.

IJ57888
Fixed an issue in the Workload Designer where specific imported run cycle groups caused page crashes.

Previously, importing certain monthly interval run cycle groups via ocli model caused the Workload Designer page to fail with an error when opened. This issue has been fixed to correctly interpret complex run cycle logic, preventing workspace page freezes.

IJ58024
Fixed an issue where the Dynamic Workload Console displayed incorrect timestamps when connected to a z/OS engine.

Previously, target scheduling data monitored on active workloads controlled by a z/OS engine displayed time values that deviated from actual system schedules. This issue has been fixed to show precise and synchronized timestamps across Dynamic Workload Console components.

IJ58098
Fixed an issue in the Workload Designer where authorized folders were not displayed for users belonging to multiple groups.

Previously, when a user was assigned to two different security groups with varying access controls, only a limited number of folders appeared in the Workload Designer interface. The display logic has been updated to correctly evaluate multiple group permissions so that all accessible folders are populated accurately in the Workload Designer.

IJ58142
Updated Best Practices documentation for managing Dynamic Workload Console query tasks

Documentation has been updated to outline proper routine cleanups, SQL task deletion procedures, and the processing of built-in database reorganization scripts.

IJ58407
Fixed an issue where users were blocked from creating or saving filters on shared engine connections.

Previously, sharing an engine connection with a specific user rather than a group prevented that user from successfully saving query filters. This issue has been fixed to enable individual accounts to manage filter settings natively.

IJ58413
Fixed an issue in the Graphical Designer where Korean characters were displayed with corruption.

Previously, localized Korean text was corrupted under Graphical Designer > Blocks > Automation Utility within the Job Management and Job Stream Submission areas. This issue has been fixed upstream to properly support character sets and prevent garbled text string rendering.

IJ58479
Fixed an issue where the Dynamic Workload Console was unreachable after upgrading within a load balancer network environment.

Previously, attempts to access the Dynamic Workload Console returned a unreachable page error because deployment configurations set an invalid selector type. The deployment chart templates have been corrected to remove the mismatched selector property, successfully restoring login page accessibility.

IJ58586
Fixed an issue where Liberty server log files were continually filled with resource-not-found exceptions.

Previously, an incorrect internal endpoint mapping path caused WebSphere Application Server Liberty log files to repeatedly log jakarta.ws.rs.NotFoundException: RESTEASY003210 errors for the route /ui/ui/. The internal mapping paths have been corrected to resolve paths properly and eliminate unnecessary error log generation.

IJ58588
Fixed an issue where the Dynamic Workload Console was vulnerable to Cross-Site Scripting (XSS) and HTML injection.

Previously, some vulnerabilities within Predefined Reports, Security Domains, and Roles menus allowed bypassing character restrictions via direct HTTP request alteration. This vulnerability has been fixed to mitigate malicious code processing and arbitrary markup injection.

IJ58592
Fixed an issue where Broker Monitoring menus unexpectedly displayed in English within the Japanese localized Dynamic Workload Console.

Previously, users running the Dynamic Workload Console in Japanese observed that the Broker Monitoring sub-menus under the Monitoring & Reporting section remained untranslated in English. This issue has been fixed to ensure all target components are properly translated and displayed in Japanese.

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

IJ58816
Fixed the TdwcGlobalSettings.xml.template file path in documentation

Previously, the topic about customizing the global settings mentioned an incorrect path for the TdwcGlobalSettings.xml.template. The documentation has been updated to reflect the correct path of the file.

KB0129864
Fixed an issue where the Workload Designer rejected time dependency parameters between 12:00 and 12:59.

Previously, attempting to set a boundary for an Earliest Start or Latest Start requirement between the hours of 12:00 and 12:59 inside the Time Restrictions properties panel threw a validation failure error. This issue has been fixed to recognize these values as valid intervals, allowing settings to be saved without manual overrides.

KB0130897
Fixed an issue in the Graphical Designer where importing an unmodified YAML configuration file caused workspace errors.

Previously, exporting an item definition and immediately re-importing that identical file into the workspace resulted in either a blank panel or an incorrect warning that stated that the workspace version was not support merging. This issue has been fixed to successfully process YAML configuration imports without error messages or anomalies.

KB0131475
Fixed an issue where generated Dynamic Workload Console reports contained junk characters in time-related data columns.

Previously, opening or viewing a newly created report from the Dynamic Workload Console revealed corrupt junk characters within the time columns. This issue has been fixed to handle encoding formats properly and display time formats without degradation.

KB0131637
Fixed an issue where right-clicking inside the Job Stream view incorrectly displayed the native operating system context menu.

Previously, performing a right-click inside the Job Stream layout panel or blue lines triggered the native browser context menu instead of the IBM Workload Scheduler context menu. Event tracking has been modified so that right-clicks reliably launch the correct application control menus directly.

Fixed defects

The following defects have been resolved. To view additional information about each defect, click on the defect description:

Table 2. Fixed defects
Defect numberDescription
WA-162229
Fixed an issue where the Dynamic Workload Console installation failed when using Helm charts.

Previously, attempting to install Dynamic Workload Console version 10.2.7 via Helm charts failed during the installation, throwing configuration and instance startup errors. This issue has been fixed to properly configure and initialize Dynamic Workload Console instances during deployment.

WA-161730
Fixed an issue where No operation icon is displayed incorrectly in the Job stream view.

Previously, when viewing job streams from the Job stream view, No operations jobs were rendered with an improper icon. This issue has been fixed to display the correct NOP job indicator.

WA-151352
Fixed an issue in the Graphical Designer where environment variables were lost upon saving a job definition.

Previously, adding environment variables to a job definition in the Graphical Designer resulted in the variables being omitted when saved or opened. This issue has been fixed to properly retain, display, and save environment variables.

WA-149612
Fixed an issue where job environment variables created via ocli model were not displayed or preserved in the designers.

Previously, job definitions containing environment variables created via ocli model failed to display those variables when opened in the Graphical Designer or Workload Designer. The issue has been fixed to properly pass environment variable attributes to the user interfaces.

Other minor fixes

Resolved an issue where the Resolve the variables at runtime flag was not visible on the Graphical Designer.

Resolved Common Vulnerabilities and Exposures (CVE)

The following CVEs have been resolved:

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

Interoperability tables

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

Table 4. Acronym table
AcronymExtended form
DDMdynamic domain manager or backup dynamic domain manager
DWCDynamic Workload Console
MDMmaster domain manager

 

Dynamic Workload Console compatibility is supported on each release version listed in the table:

 
 MDMDDM
DWC 10.2.810.2.x, 10.1.x10.2.x, 10.1.x

The following table shows which components are compatible with previous Dynamic Workload Console versions:

 
Engine versionManage Workload DefinitionsWorkload DesignerGraphical DesignerMonitor WorkloadOrchestration Monitor
IBM Workload Scheduler v10.2.6 onward 
IBM Workload Scheduler v10.2.3 onward
IBM Workload Scheduler v10.x ✔ from v10.2.x
IBM Workload Scheduler z/OS v10.2 
IBM Workload Scheduler z/OS v10.1  

 

Compatibility scenarios and limitations

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

Known limitations and workarounds

The following are software limitations and workarounds that affect Dynamic Workload Console 10.2.8:

Duplicate folders displayed in Orchestration Monitor tree view

When navigating the tree view in the Orchestration Monitor, nested folders may appear multiple times. This occurs when when the optman parameter enListSecChk is set to YES and security roles are assigned to users or groups.

Subfolders not visible in lookups when enListSecChk is enabled

In Dynamic Workload Console V10.2.5, when the optman parameter enListSecChk is set to YES and the security domain is based on folders and subfolders, subfolders are not visible when attempting to select or search for objects, for example, while creating a new object in the Workload Designer. Although the folders are visible in the main navigation, they do not appear in the lookup.

Deployment failure when submitting more than one job stream with dependencies

In the Graphical Designer, an issue occurs when creating a dependency from a new job or job stream to an object that already exists. During the deployment, only the new objects are saved, and an error message regarding the dependency appears.

Duplicate successor cards displayed in the Dependencies section

In the Orchestration Monitor, the Dependencies section incorrectly displays a duplicate card for successor objects. When viewing a job stream that contains a successor, the same successor card is displayed twice instead of once.

Authentication failure after certificate rotation due to JWT validation error

In cloud environments, the Dynamic Workload Console authentication fails following a certificate rotation. This occurs because the system cannot find the new keys needed to verify user access tokens. This problem happens every time the certificates are updated.

Workaround:

To restore access and enable the Dynamic Workload Console to work again, restart WebSphere Application Server Liberty.

Removed the prefilled value for the Job stream field in Submit Predefined Job

To resolve APAR IJ52941 in version 10.2.6, the prefilled value /JOBS was removed from the Job stream field of Submit Predefined Job.

Workaround

Since the Job stream field is no longer automatically populated, you must manually enter the value.

Blank lines in Design menu after update

After updating the Dynamic Workload Console to version 10.2.8, blank lines can appear between items in the Design menu, corresponding to the pages of the Workload Definitions section that were removed in V10.2.8 release. This issue occurs if custom roles created in a previous version reference menu items that are now removed.

Workaround

From the Manage Roles page, open any custom role, then save without making any change. After saving, the blank lines corresponding to the removed Workload Definitions pages disappear.

Restart action fails with wildcards

When monitoring a File Transfer job from the Dynamic Workload Console, the Workflow Details panel displays information about the transfer of individual files. If you use wildcards instead of a specific file name and the job step fails, you cannot restart the step.

Workaround

You can rerun the entire job using the Rerun button in the Monitor jobs panel.

SAP jobs cannot be created nor edited from the Graphical Designer

SAP job definitions cannot be created nor edited from the Graphical Designer.

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

Installation of the Dynamic Workload Console on z/OS fails if the LONGNAME variable differs from root or the installing user

When installing the Dynamic Workload Console on a z/Os environment, the installation fails with the following error message:

WAINST051E The installation cannot run because the user
        running the installation script must either be the root user or the same user <username>
        specified for the --user parameter.

This issue occurs if the LOGNAME variable on the installation host is set to a value other than root or the actual user running the installation script.

Workaround:

Unset or clear the LOGNAME environment variable before running the installation script.

Error occurs when updating job stream properties in z/OS Federator Orchestration Monitor

On z/OS systems, an error occurs in the Federator-mirrored Orchestration Monitor when attempting to change the priority of a job stream. This issue is encountered after clicking the job stream name hyperlink and modifying the priority field. The system fails to save the change and displays an error message instead of updating the object.

Impossibility to generate reports on Dynamic Workload Console installed on z/OS systems

The generation of reports in the Dynamic Workload Console fails when the Dynamic Workload Console is installed on z/OS systems.

Federator does not always perform the automatic clean up of archived records

Archived records that are stored by the Federator into the database used, if any, are not always auto deleted according to the cleanup policy set in the fed_variables.xml file.

Workaround

To delete those records, you must run the extend command, or perform a plan refresh.

Federator does not clean up database from old engines

Old engines that are stored by the Federator into the database used, if any, are not deleted.

Workaround

To delete those records, you must manually run a query on the database.

Discovered z/OS engines are only usable in the Orchestration Monitor

After you have registered a z/OS engine to the Federator, it is added to the list of discovered engines, which are only usable in the Orchestration Monitor. To make all the other Dynamic Workload Console functions available to z/OS engines, you must define them manually on the Dynamic Workload Console.

Package structure

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

Installing and upgrading to version 10.2.8

This section describes how to install and upgrade the Dynamic Workload Console to version 10.2.8.

Before getting started, verify that the following requirements are met:

  • The Dynamic Workload Console is active.
  • No user is connected to the Dynamic Workload Console to prevent the data related to their working session from being lost.

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.

Installation notes

  • Ensure you have installed the required prerequisite software. To obtain the latest information about software requirements for IBM Workload Scheduler, run the Detailed System Requirements report and browse to the relevant section.
  • 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.

  1. Browse to the datasource.xml template.
  2. Open the file with a text editor and perform the following changes:
    1. Add the lines listed below after the db.driver.path parameter:

      <variable name="db.encrypt" value="false"/>
      <variable name="db.trustServerCertificate" value="false"/>
    2. Append the following strings at the end of the value of the mssql.URL parameter:

      ;encrypt=${db.encrypt};trustServerCertificate=${db.trustServerCertificate}
    3. 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}"
  3. Stop and restart WebSphere Application Server Liberty to make the changes effective.

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:

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

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

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

  1. 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 5. Defining the alias for custom certificates
Current status of ssl_config.xml fileSteps 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:

  1. Add the following entry:

    <variable name="serverkeyalias" value="server"/>
  2. 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.

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: http://www.ibm.com/software/support

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

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

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

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.

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 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, 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 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":"a8m50000000KzAMAA0","label":"Components-\u003EDWC"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"10.2.8"}]

Document Information

Modified date:
27 July 2026

UID

ibm17280606