Fix Readme
Abstract
This document provides important information about IBM Workload Scheduler version 10.2.3
Content
IBM Workload Scheduler version 10.2.3 Release Notes
This document provides important information about IBM® Workload Scheduler version 10.2.3.
The most up-to-date version of this document can be accessed at the following URL: Download Documents, System Requirements, Release Notes.
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.3
- APARs and defects fixed in version 10.2.3
- Resolved Common Vulnerabilities and Exposures (CVEs)
- Interoperability tables
- Known limitations and workarounds
- Package structure
- Installing and upgrading to version 10.2.3
- 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.3
- Discover the Graphical Designer: a brand-new way to design your orchestration
- Elevate your data management with PostgreSQL database
- Unleash the power of the cloud using Amazon RDS for MSSQL
- Customize your interfaces with Private Label Settings
- Certman: the new tool to manage certificates
- Power your Orchestration CLI model commands with the newly supported items
- Explore the new items now available with the scalable and flexible REST APIs V2
- Embedded job definitions for enhanced customization
- Changed features and feature capabilities in version 10.2.3
Dynamic Workload Console and master domain manager are not supported on AIX operating systems in version 10.2.3. However, support will be reinstated in version 10.2.5.
Helpful videos demonstrating new features are available on Workload Automation YouTube channel. See also Discover IBM Workload Scheduler 10.2.3 for an introduction to the release.
APARs and defects fixed in version 10.2.3
This section lists APARs resolved in version 10.2.3.
| APAR NUMBER | DESCRIPTION |
|---|---|
| IJ26882 | Modify command does not create Java runtime folder |
| IJ40708 | Need to display the detailed job logs in case of failed jobs |
| IJ44156 | Broker jobs terminate abruptly with exit=0 |
| IJ45669 | every condition and overlap donotstart parameter do not add a dependency based on plan extension |
| IJ45889 | Integrate description about migrating custom events with information from related technote |
| IJ46370 | Netstat not supported on SLES |
| IJ47151 | conman ads command accepts incorrect values for at dependencies |
| IJ47236 | Nested run cycle groups (rcg) within run cycle definition are not working correctly |
| IJ47670 | Jobs matching the same remote job completed with the same elapse time |
| IJ47697 | The cleanupuserjobs file is missing in version 10.1 fp3 |
| IJ47717 | Azure Databricks plug-in generates a data leak |
| IJ47851 | Restful plug-in should support Mutual TLS authentication |
| IJ47940 | Document specific details for authentication methods, such as oauth2 refresh token |
| IJ48013 | Database plug-in v 10.01.02 and later causes performance problems or job failure when the SQL query output size is large |
| IJ48275 | Editing and saving a custom report automatically modifies the value in the Shared column |
| IJ49194 | The job log returned by REST APIs is garbled |
| IJ49215 | Integration stops abruptly without completing the specified number of runs |
| IJ49509 | Examples in documentation page "Cloning scheduling definitions from one environment to another" are misleading |
| IJ49538 | Unable to install the master domain manager on Linux OS when TWS user is an LDAP/AD user |
| IJ49538 | MSSQL should support domain name user |
| IJ49563 | A delay is observed while the broker is connecting to the master, which impacts dynamic agent communication |
| IJ49718 | Azure Data Factory plug-in jobs are encountering a timeout error |
| IJ49748 | AWS S3 download jobs remain in Executing state indefinitely |
| IJ50366 | Batchman on backup master domain manager does not stop during switchmgr operations |
| IJ50521 | Multiple error number 4 messages found in netman traces |
| IJ50571 | Correction about the documentation steps for switching a domain manager |
| IJ50574 | Manage mpmetrics feature to deal with memory leak issues |
| IJ50626 | SSC job streams showing an incorrect status in plan |
| IJ50637 | Shadow job status is not updated correctly |
| IJ50713 | Incorrect risk level status displayed for critical jobs |
| IJ50805 | r3batch: error creating semaphore on windows |
| IJ50846 | Though remote job completes successfully, local jobs with cross dependency remain in WAIT state |
| IJ50848 | Connection to Azure cloud not working properly |
| IJ51010 | The key length of 9.5 certificates does not work correctly in version 10.2.1 |
| IJ51026 | Incorrect data returned in generated Excel files in Restful API job |
| IJ51038 | Wrong limit of 25 dependencies in a single join is applied in the job streams added to the plan using planner |
| IJ51042 | Daylight savings time (DST) change causes duplicate job stream instances when using repeat every keyword |
| IJ51079 | Bmevents failing at Json validation. The attribute name script is not in the correct Json format. Version : 10.2.1 |
| IJ51158 | Events are no longer processed if event rules are refreshed and redeployed at the same time |
| IJ51185 | Update Remote Command plug-in to use JSch-0.1.55 |
| IJ51193 | Problems in connection between domain manager and fault-tolerant agent |
| IJ51204 | Azure Data Factory plug-in for proxy enhancement |
| IJ51233 | twsmerge.log query not working properly |
| IJ51323 | Problem with the Database plug-in: com.ibm.scheduling.agent.database 10.1.0.03.jar using custom credentials |
| IJ51366 | ILMT tags on Agents are unchanged regardless of the license type setting (PVU or Per Jobs) |
| IJ51367 | Update list of chargeable components in the documentation |
| IJ51400 | Cannot decrypt the variable due to the limit to string length set in the jm_variables file |
| IJ51401 | Makeplan command stops due to runcycle in which the at time is the same as sod time |
| IJ51510 | Dynamic agent problem when upgrading from version 9.4 to 10.2.2 |
| IJ51511 | Upgrading from 9.4 to 10.2.2 is not working and it is not properly documented that it is supported |
| IJ51683 | Step 12 of the procedure for connecting master domain manager to a new database can be misleading |
| IJ51684 | In parallel upgrade of master domain manager, it is not clear on which component the upgrading the database schema step must be executed |
| IJ51685 | New option is needed to retain the running pod in order to retrieve logs from the Kubernetes pod after the job completes. |
| IJ51688 | Z connector problem: only the first variable is resolved correctly when using REST APIs |
| IJ51716 | In the documentation about making switch manager permanent, the location of mozart/globalopts file is wrong |
| IJ51717 | Correct steps about customizing and submitting the optional FINAL job stream in the documentation about upgrading from 9.4 |
| IJ51721 | Explain in the documentation how, after changing the Start of Day, you can validate if all job stream definitions are compatible with the new Start Of Day time |
| IJ51723 | Parallel upgrade from 9.4.0.x to 9.5.0.x or 10.2.x should include steps about how to enable TLS v1.2 |
| IJ51724 | After installing a backup master domain manager when upgrading, there should be steps to ensure connectivity of the backup master domain manager |
| IJ51751 | When setting the workdir parameter to the product installation directory, all data is deleted from the directory. |
| IJ51841 | Connection to Azure Data Factory not working properly |
| IJ51912 | folder attribute type is not supported for action object type |
| IJ51949 - KB0115091- | The master domain manager does not manage correctly permissions on group names containing the slash character |
| IJ51966 | The documentation should provide an example of where the useropts file is located |
| IJ51967 | Incorrect explanation of jnextplan -to command in the documentation |
| IJ52101 | agentcertificatedownloader command does not work properly on Windows operating system due to conflict between root directory and installation directory |
| IJ52185 | Mirroring problem due to delay in processing of batchman update command |
| IJ52210 | conman sj command does not filter pools |
| IJ52360 | Specify in the documentation that TLS v 1.3 is available from v 10.1 FP4 onwards |
| IJ52363 | AWS S3 integration not working when using root user credentials |
| IJ52400 | Both backup master domain manager and master domain manager should be configured to use the same encryption keys |
| IJ52516 | Indexing required for configuredb script for MSSQL to improve database performance and prevent deadlocks |
| IJ52583 | Action performed from Dynamic Workload Console on an object not getting captured in audit logs |
| IJ52593 | The Broker's netman process terminates unexpectedly during a Tenable (Nessus) vulnerability scan. |
| IJ52596 | Upgrade from v 9.5 to v 10.2.2 might fail if the passwords on KDB and JKS are set to the same value |
| IJ52824 | Vulnerability in OpenSSL (CVE-2024-0727) |
| IJ52841 | Correct the information about messages.log file |
| IJ52993 | Actions performed from the Dynamic Workload Console are not captured in plan audit log correctly |
| KB0110142 | Rep7 utility encounters problems when retrieving data from jobs |
| KB0113539 | Runcycle defined with at keyword and +1 Day setting does not recognize the +1 Day offset |
| KB0113664 | The -password parameter is missing from the table in the documentation for installing a new instance for both Windows and Unix/Linux |
| KB0114983 | Successor jobs processing without completion of predecessor jobs |
| IJ52970 | During installation, the apikey parameter is not mutually exclusive with the sslkeyfolder and sslpassword parameters |
Resolved Common Vulnerabilities and Exposures (CVEs)
The following CVEs have been resolved:
- CVE-2023-25193
- CVE-2023-3635
- CVE-2023-39326
- CVE-2023-45288
- CVE-2023-45289
- CVE-2023-45290
- CVE-2024-1023
- CVE-2024-1300
- CVE-2024-24783
- CVE-2024-24784
- CVE-2024-24785
- CVE-2024-24789
- CVE-2024-24790
- CVE-2024-24791
- CVE-2024-2700
- CVE-2024-34155
- CVE-2024-34156
- CVE-2024-34158
- CVE-2024-47535
- CVE-2024-47554
- CVE-2024-5642
- CVE-2024-7254
- IBM Workload Scheduler uses Dojo version 1.14.9CVE2020123450, which includes CVE 2020-123450.
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.3 |
|
|
|
| 9.4.0.x | |
| DM 10.2.3 |
|
| ||||
| FTA 10.2.3 |
|
|
| |||
| DA 10.2.3 |
|
|
| |||
| DDM 10.2.3 |
|
|
|
*The composer command line of the agent at version 10.2.3 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.3 | 10.x.x | 10.x.x | 10.x.x |
It's 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
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.3 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.
Resource CLI on agents not configured correctly
The resource CLI on agents might occasionally work erratically because of a problem in updating the configuration file.
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.
When installing agents on Amazon Linux 2 operating systems an error is returned by the prerequisites check
The installation script returns an error when checking prerequisites on Amazon Linux 2 operating systems. This happens because this operating system is not recognized by the script as a valid operating system.
To work around this problem, bypass the prerequisites check by using the
-skipcheckprereqparameter when running thetwinstscript.Issue while saving a Snowflake plug-in job
While attempting to save a Snowflake plug-in job definition, an error occurs resulting in the job definition not being saved.
Issue while saving an Apache Airflow plug-in job
While attempting to save an Apache Airflow plug-in job definition, an error occurs resulting in the job definition not being saved.
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.
Package structure
For a detailed list of available packages, see the 10.2.3 Quick Start Guide document available from IBM Fix Central.
Installing and upgrading to version 10.2.3
This section describes how to install or upgrade to version 10.2.3.
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 24.0.0.9. The minimum required WebSphere Application Server Liberty version to successfully install the package is 24.0.0.9.
- Support for WebSphere Application Server Liberty Base version 25.0.0.3 will be available starting with the upcoming release of IBM Workload Scheduler version 10.2.4.
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, perform the following steps after upgrading to version 10.2.3:
- 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.
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.3, 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.4 Fix Pack 6 up to V9.5 Fix Pack 4 | Apply APAR IJ33383 |
| 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, 2024.
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.
 | 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.
Was this topic helpful?
Document Information
Modified date:
02 December 2025
UID
ibm17172679