Fix Readme
Abstract
This document provides important information about IBM Workload Scheduler Version 10.2.5
Content
IBM Workload Scheduler version 10.2.5 Release Notes
This document provides important information about IBM® Workload Scheduler version 10.2.5.
You can obtain dynamic and up-to-date reports by browsing to Software Product Compatibility Reports and selecting the information you are interested in.
- Features introduced with version 10.2.5
- APARs fixed in version 10.2.5
- Resolved Common Vulnerabilities and Exposures (CVEs)
- Interoperability tables
- Known limitations and workarounds
- Package structure
- Installing and upgrading to version 10.2.5
- Performing the centralized agent update on a stand-alone fault-tolerant agent
- Documentation updates
- Contacting IBM Workload Scheduler Software Support
- Notices
Features introduced with version 10.2.5
IBM Workload Scheduler version 10.2.5 contains the following enhancements:
- Advancing security with FIPS 140-3 compliance
- Streamlined engine reporting configuration in administration panel
- Navigating OQL Queries in the Orchestration Monitor
- User Object Credential Management - Ensuring operational continuity and security
- Monitor certificate expiration - Total certificate control
- Changed features, improvements, and RFEs in version 10.2.5
Helpful videos demonstrating new features are available on Workload Automation YouTube channel.
Important information for version 10.2.6
- Manage Workload Definitions
- List Workload Definitions
- Import Workload Application
- Manage Event Rules
- Create Workstations
- List Workstations
APARs fixed in version 10.2.5
This section lists APARs resolved in version 10.2.5.
| Code | Description |
|---|---|
| IJ42602 | Incorrect URLs displayed during installation performed with Helm chart |
| IJ49535 | When a job stream is submitted using the Design -> Workload Definition (New) -> Workload Designer option in Dynamic Workload Console, job stream name and time stamp are not displayed. |
| IJ53913 | Configuring the new master domain manager as a backup: document that the encryption feature is supported starting from v 10.1 |
| IJ54086 | Job streams are carried forward even if in “SUCCESS” state due to conditional dependencies in other scheduling objects |
| IJ54114 | Fault-tolerant agent not incorporated into Windows Server Failover Clustering |
| IJ54205 | Job fails when re-executed using the “STEP” option |
| IJ54273 | Jobs fail to submit from dynamic agents when WebSphere Application Server Liberty certificate is renewed (custom certificates installed) |
| IJ54439 | Agent upgrade from version 10.2.2 to 10.2.3 failed - missing JavaExt folder |
| IJ54480 | The dataimport and dataexport utilities are not working on Windows master domain manager v 10.2.5 and 10.2.2 |
| IJ54505 | SSM Agent version 10.2.4 contains an outdated version of the libcurl library |
| IJ54594 | Agent installation on Windows Server 2025 fails during the prerequisites check phase in version 10.2.4 |
| IJ54627 | Add information about garbled characters in logs in Japanese into the Release Notes |
| IJ54644 | Correct the format of .pem certificate in the documentation - one hyphen is missing in the example |
| IJ54660 | Typo in documentation regarding --skipCheckPrereq installation parameter |
| IJ54761 | Misleading example provided in domain manager configuration documentation |
| IJ54791 | Unable to create logical resources after upgrading from version 9.4 to version 10.2.3 |
| IJ54793 | Job stream View not showing the correct mapping for the successor job stream dependencies |
| IJ54798 | The following error is returned inWebSphere Application Server Liberty log "AWSJCS016E: Invalid value for 'ENABLE_DATABASE_GET_OPERATIONS_AUDIT'" |
| IJ54833 | Red Hat Linux 7.9 wrongly listed as supported operating system during the prerequisite check phase when installing version 10.2.3 |
| IJ54881 | JWT authorization fails to initialize in Swagger UI when executing requests through API v2. |
| IJ54911 | Document correct maximum value for Workload Designer search window |
| IJ54912 | In version 10.2.4, the broker variable TWS.JOB.IA not resolved in UNIX job definitions |
| IJ55016 | The jobmanager.ini file is not updated after upgrading master domain manager and dynamic agents to version 10.2.4. |
| IJ55178 | Web services jobs fail with the following error: java.lang.RuntimeException: need 0 arguments |
| IJ55256 | Error encountered when upgrading the Dynamic Workload Console to version 10.1 FP6 |
| IJ55319 | Upon container restart, the JAR file is removed because it is not part of the container image defined in the Helm chart. |
| KB0120240 | Dynamic Workload Console version 10.2.3 on Kubernetes does not reconnect after POD restart |
| KB0120322 | When using PostgreSQL-16 with version 10.2.3 , the composer add command causes duplicate schedules without warning |
| KB0121067 | Workload Designer sorting error: objects are sorted incorrectly when connecting to a master domain manager using an MSSQL-based database |
| KB0121140 | Remove -acceptlicense parameter in the documentation about moving from WebSphere Application Server Liberty Base to Open Liberty |
| KB0121432 | The collation feature when using PostgreSQL 16 with versions 10.2.3 and 10.2.4 is causing composer to show incorrect output, empty job streams, and missing jobs |
| KB0122107 | Shadow job status does not update correctly |
| KB0122241 | Web services plug-in jobs complete in error after upgrading to version 10.2.4upgrade |
Resolved Common Vulnerabilities and Exposures (CVEs)
The following CVEs have been resolved:
- CVE-2024-52533
- CVE-2025-48924
- CVE-2025-48060
- CVE-2024-23337
- CVE-2025-47273
- CVE-2025-6021
- CVE-2025-49796
- CVE-2025-49794
- CVE-2025-4673
- CVE-2025-0913
- CVE-2025-22874
- CVE-2025-49146
- CVE-2025-22872
- CVE-2025-22871
- CVE-2025-22870
- CVE-2025-48976
Interoperability tables
| 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 |
Compatibility is supported on the latest available release level for each IBM Workload Scheduler release listed in the table:
| Component | MDM | DDM | DM | FTA | DA | ZWS agent |
|---|---|---|---|---|---|---|
| MDM 10.2.5 |
|
|
|
| 9.4.0.x | |
| DM 10.2.5 |
|
| ||||
| FTA 10.2.5 |
|
|
| |||
| DA 10.2.5 |
|
|
| |||
| DDM 10.2.5 |
|
|
|
*The composer command line of the agent at version 10.2.5 works correctly with master domain managers at version 9.5 and later.
**Compatibility on v9.4 Limited fault-tolerant agents for IBM i is not supported.
| Component | MDM | DDM | DWC |
|---|---|---|---|
| AIDA 10.2.5 | 10.x.x | 10.x.x | 10.x.x |
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
Out of memory error can occur on master domain manager at version 10.2.5
The master domain manager at version 10.2.5 can crash with an out of memory error when a high number of dynamic agents are present. To avoid the issue, install the fix for IJ56396. The fix is available from IBM Fix Central .
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.5 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. The fix is available from IBM Fix Central for version 9.4 FP7. 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.
Installing or linking a fault-tolerant agent earlier than 10.2 in an environment configured with new default or new custom certificates
If you install or link a fault-tolerant agent earlier than V10.2 to an environment with a master domain manager at version 10.2.1 or later using new custom or new default certificates, you need to manually install the certificates on the fault-tolerant agent. To perform the manual installation, you can follow the steps below:
- Shut down the workstation of the fault-tolerant agent
- Create a backup of the localopts file
- Create a new folder under the target fault-tolerant agent as in the following example: <TWS_DATA_DIR>/<new_cert_folder>
- From the master domain manager, copy the files under TWA_DATA_DIR/ssl/depot
- Paste the TWA_DATA_DIR/ssl/depot files from the master domain manager into the <TWS_DATA_DIR>/<new_cert_folder> new directory
- Update the localopts file of the fault-tolerant agent by changing the values of the following properties:
-
- SSL Key: <TWS_DATA_DIR>/<new_cert_folder>/tls.key
- SSL Certificate: <TWS_DATA_DIR>/<new_cert_folder>/tls.crt
- SSL key pwd: <TWS_DATA_DIR>/<new_cert_folder>/tls.sth
- SSL CA certificate: <TWS_DATA_DIR>/<new_cert_folder>/ca.crt
-
- Turn on the workstation of the fault-tolerant agent.
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.
ITLM tool incorrectly discovering z-centric agents
After installing a dynamic agent, the ITLM tool might incorrectly discover a z-centric agent. You can find two possible reasons and their workarounds below:
The directory in which you temporary unzipped package images contains a wrong tag
If you did not delete the temporary directory, delete the following file:
The directory in which you installed the package contains a wrong tag
To avoid the issue, delete the
ibm.com_IBM_Z_Workload_Scheduler_Agent-9.5.0.swidtagfile from the following path:
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
conmansyntax might not work as expected, returning different results from the ones retrieved usingconman.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.
Resource CLI commands not supported on Windows workstations
Resource CLI commands are currently not supported on Windows workstations.
Dynamic agents not connecting after certificate rotation when using JWT
If you are using JWT and modify the certificates on the master domain manager, communication with dynamic agents might be interrupted.
Workaround
./AgentCertificateDownloader.sh --jwt false --work_dir <work_dir> --tdwbhostname <tdwbhostname>
--tdwbport <tdwbport> --gwid <gateway_id> --gateway <local|remote|none>
--apikey <API key for authentication with the master domain manager>Problem prevention
Browse to the ita.ini file on the dynamic agent. The file is located in TWA_DATA_DIR/ITA/cpa/ita.
Comment out the jwt_file = line, if existing. Consider the following example:
#jwt_file =Restart the agent.
Installation and upgrade problems with provided drivers for Azure SQL database
When installing fresh or upgrading to version 10.2.4, you might encounter an error similar to the following if you are using Azure SQL database:
AWKCLI102E A database error occurred. The internal error returned by the database manager is: ""encrypt" property is set to "false" and "trustServerCertificate" property is set to "false" but the driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption: Error: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty.You may encounter problems with job submissions if your dynamic agents meet both of the following conditions:
- The dynamic agents are a 10.x version and are connected to a 10.2.5 master domain manager
- The dynamic agents are using either:
- default certificates, or
- certificates downloaded using the AgentCertificateDownloader script or the wauser and wapassword parameters at installation time
Disable JWT-based authentication
Install the dynamic agents using the wauser and wapassword parameters and setting the jwt parameter to false.
Use SSL Certificates
- Download the certificates from the master domain manager to the dynamic agents.
- Install the dynamic agents using the sslkeysfolder and sslpassword parameters to specify the local path to the certificates.
Upgrading dynamic agents version 10.1 Fix Pack x to version 10.2.5 fails
You may encounter problems when upgrading your dynamic agents from v 10.1 Fix Pack x to version 10.2.5 if the dynamic agents meet both of the following conditions:
- The dynamic agents are a 10.x version and are connected to a 10.2.5 master domain manager
- The dynamic agents are using either:
- default certificates, or
- certificates downloaded using the AgentCertificateDownloader script or the wauser and wapassword parameters at installation time
Problems with SAP jobs on extended agents
An error might occur when running SAP jobs on extended agents if the job is defined with a streamlogon user different from the wa user.
When checking the job log, you can find the following error:
*** ERROR 012 *** EEWO0012E The extended agent could not be initialized.
Package structure
For a detailed list of available packages, see the 10.2.5 Quick Start Guide document available from IBM Fix Central.
Installing and upgrading to version 10.2.5
This section describes how to install or upgrade to version 10.2.5.
Installation notes
Before installing the release, ensure you have installed the required prerequisite software. To obtain the latest information about software requirements, run the Detailed Software Requirements report and browse to the relevant section.
The formal test phase was performed using WebSphere Application Server Liberty Base 25.0.0.6. The minimum required version of WebSphere Application Server Liberty Base is 25.0.0.6.
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"/>Depending on the WebSphere Application Server Liberty version you are using, you might encounter the problems described in the following technotes:
Versions equal to or higher than 24.0.0.8
See Possible IWS compatibility issues with Liberty 24.0.0.8 or higher
Versions ranging from 24.0.0.3 to 24.0.0.8
Upgrade 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 the current version. 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.
ltpa.keys, perform the following steps:- copy the
ltpa.keysfile 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.keysfile was updated to complete the SSO setup.
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.5, there are procedures to follow according to the version of the fault-tolerant agent from which you want to upgrade.
| 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.
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 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, 2025.
Portions of this code are derived from IBM Workload Scheduler Sample Programs.
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.
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.
Was this topic helpful?
Document Information
Modified date:
04 November 2025
UID
ibm17240670
