Fix Readme

Abstract

This document provides important information about IBM Workload Scheduler Version 10.2.4

Content

IBM Workload Scheduler version 10.2.4 Release Notes

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

Note: The official IBM documentation is set to be released shortly, and the links pointing to it in this document are not yet functional.

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.4
APARs and defects fixed in version 10.2.4
Resolved Common Vulnerabilities and Exposures (CVEs)
Interoperability tables
Known limitations and workarounds
Package structure
Installing and upgrading to version 10.2.4
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.4

IBM Workload Scheduler version 10.2.4 contains the enhancements listed in IBM Workload Scheduler version 10.2.4 contains the following enhancements:

Dynamic Workload Console and master domain manager are not supported on AIX operating systems in version 10.2.4. However, support will be reinstated in version 10.2.5.

Performance optimization

Tests conducted on IBM Workload Scheduler version 10.2.4 have highlighted the following performance enhancements compared to the previous version:

Improved dynamic agent memory management: In IBM Workload Scheduler version 10.2.3, the dynamic agent would consume 300 MB of memory daily without releasing it when handling 600,000 job submissions.; With the new 10.2.4 version, under the same load of 600,000 job submissions, not only the dynamic agent now releases memory, but it also exhibits negligible memory consumption.
Orchestration Monitor query performance boost: Query results displayed in the Orchestration Monitor now appear in one-third of the time compared to the Workload Monitor.
Note: Data taken from test environments. The time represents the user process duration, starting from opening the monitor interface to obtaining a query result with 250 entries.

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

APARs and defects fixed in version 10.2.4

This section lists APARs resolved in version 10.2.4.

Table 1. **APARs addressed in version 10.2.4**
APAR NUMBER	DESCRIPTION
IJ43998	Incorrect output from the Composer validate command compared to Composer add/replace when SOD is not set to 0000.
IJ44931	Flexera report incorrectly lists SWIDTAG files for Z-agents, requiring clarification.
IJ48837	TaskLauncher issue causes error 8 due to excessive file descriptor usage.
IJ52213	AS400 agent generates journal entries for authority failure errors.
IJ52318	Job names truncated to 22 characters when checking job streams and jobs from the Workload Designer.
IJ52437	Enigma encryption in R3Batch still relies on the outdated 3DES algorithm.
IJ53095	AWSITA173E error prevents updating the specified trace property value due to HTTP 500 status.
IJ53096	Job streams do not appear when searching by exact name but are visible when using wildcards.
IJ53102	Documentation incorrectly lists `<TWA_HOME>\TWS\SSL\OPENSSL` as the default certificate location.
IJ53103	Dynamic agent installation examples in version 10.2.1 documentation are incorrect.
IJ53111	Jobs in the INTRO state are not managed properly during a Liberty restart.
IJ53119	Documentation update required for the OnOverlap DoNotStart feature.
IJ53152	Security vulnerability in SSRF (CVE-2024-22329).
IJ53153	Security vulnerability in XXE (CVE-2024-22354).
IJ53154	Security vulnerability in DOS (CVE-2024-22354).
IJ53155	Security vulnerability identified in Microsoft Azure Storage (CVE-2012-5783).
IJ53168	Event rule example count should be six, not seven, in the documentation.
IJ53169	TECEVENTFORWARDER event missing in the table of contents in the documentation
IJ53170	Confusing numbering in table #2 within IBM Workload Scheduler documentation for domain manager switching procedure.
IJ53181	IBM Workload Scheduler installation requires a local user account.
IJ53206	Cipher problem after upgrading from v 10.1.4 to v 10.2.3
IJ53210	Missing `-TDWBPORT` and `-TDWBHOSTNAME` parameters needed to download certificates during agent installation in version 10.2 FP X.
IJ53215	'Unix type' jobs fail to run on dynamic workstations following the 10.2.3 upgrade.
IJ53220	Documentation discrepancy noted in IBM Workload Scheduler Docs for error handling.
IJ53224	Upgrade from 10.1 FP5 to 10.2.3 failed during JKS to P12 certificate conversion.
IJ53249	Documentation discrepancy regarding upgrading in a mixed-version environment using default certificates.
IJ53250	Incorrect internal record mapping due to improper joins applied to JobStream AWSBHT009E.
IJ53334	Security vulnerability in OpenSSL (CVE-2024-4603).
IJ53335	Documentation update needed for directories created outside of `TWA_HOME` during installation.
IJ53339	Security vulnerability in GlibC (CVE-2024-33602).
IJ53340	Security vulnerability in GlibC (CVE-2024-33599).
IJ53343	Security vulnerability in GlibC (CVE-2024-33600).
IJ53344	Security vulnerability in GlibC (CVE-2024-2961).
IJ53345	Multiple RHEL vulnerabilities identified (CVE-2022-48564, CVE-2023-40217, CVE-2023-43804, CVE-2023-45803, CVE-2023-25193).
IJ53367	REST API fails to add an application in AD correctly; the variable table remains empty.
IJ53424	Correct JSON format needed for TWSDATA/AUDIT plan and database files.
IJ53442	Dynamic agent upgrade from 10.1.0 to 10.2.3 fails on Amazon Linux 2 OS.
IJ53473	Centralized update/fixpack install mode in Workload Automation should skip the user check by default.
IJ53477	Job rename function does not work correctly; references still point to the original job name.
IJ53517	AES encryption in ConMan/Composer version 10.2.2 does not function as expected.
IJ53540	TWS temporary files are not deleted as expected.
IJ53564	Typographical error found in the Composer add command documentation.
IJ53566	Missing dependency module `/usr/lib/libssl.a(libssl64.so.3)` prevents loading on AIX MDM-server (OS release 7200-05-07-2346).
IJ53580	OPENS (-S %P) command does not return expected results when the search string is `` or `.*`, and the destination folder contains subdirectories.
IJ53722	KB0119468 The agent is indicated as linked, but it is not actually linked
IJ53788	Master installation hangs when performed by a non-root user.
IJ53800	Objects are visible in version 9.5 without adding to a list; in version 10.2.2, they are not visible unless explicitly listed in the security file.
IJ53808	Long-term no-operation feature does not work for jobstreams/jobs outside the root folder.
IJ54167	CertMan utility fails to concatenate certificate files into a single readable file, resulting in corruption.
IJ54171	Cannot submit job on Windows when password contains '&' character
KB0090326	Licensing configuration options have duplicate short names for `licenseProxyServerPort` and `licenseProxyPassword`.
KB0117251	Restful API polling jobs intermittently fail with error 401 upon callback.

Fixed defects

The following defects have been resolved:

Table 2. Fixed defects
DEFECT NUMBER	DESCRIPTION
WA-122999	[OCLI] ocli plan ss "@#JS;deps;logon" does not work
WA-123000	[OCLI] ocli plan ss "@#JS;deps;Keys" does not work
WA-130192	[OCLI] In the Rerun Step thrre are missing flags on show job command
WA-136347	[LaunchJobExecutor] In v 10.2.3, in Action tab, the Get applications button is not working
WA-136720	[Plug-ins serviceability] Generic error messages are returned in Test Connection issues, without specify each message for each error occurred
WA-138535	Change trace level for nipcutil.c: the trace fills in the TWSMerge logs with useless traces.
WA-138995	The dynamic agent continuously restarts when ita.ini is not configured with certificates
WA-140078	[OCLI] ocli plan ss "@#JS;deps" does not show job details
WA-140998	[OCLI Model] Error returned when creating a job stream with non-working days
WA-140999	[OCLI Model] OCLI model extract command returns an unexpected error
WA-141000	[OCLI Model] Valid from field is not updated after changing the date format
WA-141102	10.2.4 - API V2 - querying job streams by jobs.workstation or jobs.name or dependencies always returns all jobs
WA-141353	Administration menu -database cpnstraint violation when creating security domains
WA-141369	[OCLI Model] display command with Valid to option does not display the job as expected
WA-141400	No backup is performed for traces in methods folder when running the datagather command
WA-141592	API - The following error is returned: AWSJCS042E An invalid value has been specified for the OQL string null when creating a job stream
WA-141859	REST API V2: OQL query filters are not documented
WA-142006	OCLI extract js command returns wrong results
WA-142257	[OCLI Model] Error returned when performing an extract command with OCLI model using valid from option
WA-143034	The security file is not automatically updated when updating security using Dynamic Workload Console and a load balancer
WA-143460	Wrong .ear file used in build
WA-143463	Graphical Designer: Duplicate credential problems with PostgreSQL database. Note: This issue has been resolved for new installations; however, it may reoccur during upgrades. Our development team is actively working on a permanent solution and will address it as soon as possible.
WA-143774	[OCLI] An error is returned when running show jobs in OCLI command line
WA-143854	Workflow Details REST API v2 does not work
WA-144199	CVE-2025-22869 found

Resolved Common Vulnerabilities and Exposures (CVEs)

The following CVEs have been resolved:

CVE-2024-45336
CVE-2024-45337
CVE-2024-45338
CVE-2024-45341
CVE-2025-22870
CVE-2025-22871
CVE-2025-23184
CVE-2025-24970
CVE-2025-25193
CVE-2025-27363

Interoperability tables

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

Table 3. **Acronym table**
Acronym	Extended form
DA	Dynamic agent
DDM	dynamic domain manager or backup dynamic domain manager
DM	domain manager
DWC	Dynamic Workload Console
FTA	fault-tolerant agent
MDM	master domain manager
BKM	backup master domain manager
ZWS agent	IBM Z Workload Scheduler Agent

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

Table 4. **Compatibility table for IBM Workload Scheduler**
Component	MDM	DDM	DM	FTA	DA	ZWS agent
MDM 10.2.4		10.`x.x` 9.5.0.`x` 9.4.0.`x`	10.`x.x` 9.5.0.`x` 9.4.0.`x`	10.`x.x` 9.5.0.`x` 9.4.0.`x`**	10.`x.x` 9.5.0.`x` 9.4.0.`x`	9.4.0.`x`
DM 10.2.4	10.`x.x` 9.5.0.`x` 9.4.0.`x`			10.`x.x` 9.5.0.`x` 9.4.0.`x`**
FTA 10.2.4	10.`x.x` 9.5.0.`x` 9.4.0.`x`*	10.`x.x` 9.5.0.`x` 9.4.0.`x`	10.`x.x` 9.5.0.`x` 9.4.0.`x`
DA 10.2.4	10.`x.x` 9.5.0.`x` 9.4.0.`x`	10.`x.x` 9.5.0.`x` 9.4.0.`x`	10.`x.x` 9.5.0.`x` 9.4.0.`x`
DDM 10.2.4	10.`x.x` 9.5.0.`x` 9.4.0.`x`			10.`x.x` 9.5.0.`x` 9.4.0.`x`**	10.`x.x` 9.5.0.`x` 9.4.0.`x`

*The composer command line of the agent at version 10.2.4 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.

Note: Version 9.4 is no longer supported. It appears in this table with a recommendation to upgrade to a currently supported version.

Table 5. **Compatibility table for AIDA**
Component	MDM	DDM	DWC
AIDA 10.2.4	10.`x.x`	10.`x.x`	10.`x.x`

Compatibility scenarios and limitations

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

Known limitations and workarounds

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

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

Unexpected duplicate entries in database indexes when upgrading and using a PostgreSQL database

Duplicate entries may unexpectedly appear in database indexes when performing an upgrade and using a PostgreSQL database.

Jobs and dependencies in job streams might not be displayed when using composer display or extract commands with a PostgreSQL database

While job and dependency information exists in the database, it might not be visible when using the composer display or extract commands with a PostgreSQL database. This issue is purely visual and does not affect job scheduling: job streams and their respective jobs continue to run as expected when loaded into the plan. The defect solely impacts how job stream details are displayed.

Limitation in embedded jobs support

Embedded jobs not supported by composer, dataextract, and dataimport commands.

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.

Workaround

On the master domain manager, copy the CLIConfig.properties file from the TWA_DATA_DIR/broker/config folder to the TWA_DATA_DIR/TDWB_CLI/config folder.

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:; ibm.com_IBM_Z_Workload_Scheduler_Agent-9.5.0.swidtag
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.swidtag file from the following path:; <IWS_installation_directory>/properties/version

Hyphens not supported in configuredb script when using a PostgreSQL database

When specifying names containing hyphens in the configuredb script for a PostgreSQL database, enclose the name within backslashes and double quotes, as follows: \”user_name\”

Pool connection issues with CyberArk

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

Folder filtering discrepancy in Command Line Interfaces

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

Stored procedures issue

Database stored procedures might not function correctly.

Package structure

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

Installing and upgrading to version 10.2.4

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

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.3. The minimum required version of WebSphere Application Server Liberty Base is 24.0.0.9.
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

See Dynamic Workload Console is not able to open "Monitor Event Rules" nor "Manage workload security" with OpenID authentication

Upgrade notes

If you are using MSSQL, perform the following steps after upgrading to version 10.2.4:

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.4, there are procedures to follow according to the version of the fault-tolerant agent from which you want to upgrade.

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

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

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

Documentation updates

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

Contacting IBM Workload Scheduler Software Support

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

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

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

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

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

Notices

This information was developed for products and services offered in the US. This material might be available from IBM Workload Scheduler in other languages. However, you may be required to own a copy of the product or product version in that language in order to access it.

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

IBM Workload Scheduler may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

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

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

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

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM Workload Scheduler may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Workload Scheduler websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM Workload Scheduler product and use of those websites is at your own risk.

IBM Workload Scheduler may use or distribute any of the information you provide in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

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

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM Workload Scheduler under terms of the IBM Workload Scheduler Customer Agreement, IBM Workload Scheduler International Program License Agreement or any equivalent agreement between us.

The performance data discussed herein is presented as derived under specific operating conditions. Actual results may vary.

Information concerning non-IBM Workload Scheduler products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM Workload Scheduler has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM Workload Scheduler products. Questions on the capabilities of non-IBM Workload Scheduler products should be addressed to the suppliers of those products.

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

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

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM Workload Scheduler, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM Workload Scheduler, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM Workload Scheduler shall not be liable for any damages arising out of your use of the sample programs.

Trademarks

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

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

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

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

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

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

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

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

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

ITIL™ is a Registered Trade Mark of AXELOS Limited.

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

Terms and conditions for product documentation

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

Applicability: These terms and conditions are in addition to any terms of use for the IBM Workload Scheduler website.

Personal use: You may reproduce these publications for your personal, noncommercial use provided that all proprietary notices are preserved. You may not distribute, display or make derivative work of these publications, or any portion thereof, without the express consent of IBM Workload Scheduler.

Commercial use: You may reproduce, distribute and display these publications solely within your enterprise provided that all proprietary notices are preserved. You may not make derivative works of these publications, or reproduce, distribute or display these publications or any portion thereof outside your enterprise, without the express consent of IBM Workload Scheduler.

Rights

Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either express or implied, to the publications or any information, data, software or other intellectual property contained therein.

IBM Workload Scheduler reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of the publications is detrimental to its interest or, as determined by IBM Workload Scheduler, the above instructions are not being properly followed.

You may not download, export or re-export this information except in full compliance with all applicable laws and regulations, including all United States export laws and regulations.

IBM Workload Scheduler MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.

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

Tips

Release Notes for IBM Workload Scheduler Version 10.2.4