IBM Support

Readme file for IBM Workload Scheduler Version 10.1 Fix Pack 6

Fix Readme


Abstract

This readme file provides important information about Fix Pack 6 for IBM Workload Scheduler version 10.1.0

Content

IBM Workload Scheduler 10.1 Fix Pack 6 Readme File

Date

June, 2025

 

Fix Pack Name

10.1.0-IWS-FP0006

 

Product

IBM Workload Scheduler version 10.1.0.06

 

General Description

IBM Workload Scheduler Fix Pack 6 for version 10.1.0

 

Product versions and components to which the Fix Pack applies

This Fix Pack can be applied only on top of IBM Workload Scheduler V10.1.0, and subsequent Fix Packs.

 

This readme file provides important information about Fix Pack 6 for IBM Workload Scheduler version 10.1.0

The most up-to-date version of this readme can be accessed at the following URL: Fix Pack readmes.

IBM Workload Scheduler version 10.1.0 Fix Pack 6 supports all product versions indicated in the IBM Workload Scheduler Release Notes.

 

It is divided into the following sections:

Changed features and feature capabilities

APARs and defects fixed in V10.1 Fix Pack 6

Resolved Common Vulnerabilities and Exposures (CVE)

Known limitations and workarounds

Fix Pack structure

Installing the Fix Pack

Documentation updates

Contacting IBM Software Support

Notices

 

Changed features and feature capabilities

Supported WebSphere Application Server Liberty Base versions

IBM Workload Scheduler 10.1 Fix Pack 6 was formally tested by using WebSphere Application Server Liberty Base 25.0.0.4.

 

Updated OpenSSL libraries

IBM Workload Scheduler 10.1 Fix Pack 6 has been updated with OpenSSL libraries version to 1.1.1.25 (means 1.1.1zb).

 

OpenJDK Runtime Environment

IBM Workload Scheduler 10.1 Fix Pack 6 has been updated with OpenJDK "11.0.26+4" 2025-01-21

 

OpenJ9

IBM Workload Scheduler 10.1 Fix Pack 6 has been updated with OpenJ9 0.49.0

 

GSKit

IBM Workload Scheduler 10.1 Fix Pack 6 has been updated with GSKit "8.0.60.4" 2024-11-20.

 

Updated JDBC drivers

IBM Workload Scheduler 10.1 Fix Pack 6 has been updated with JDBC drivers for:

  • DB2: 4.34.30

 

PeopleSoft PeopleTools

IBM Workload Scheduler 10.1 Fix Pack 6 has been tested with PeopleSoft PeopleTools 8.61.

 

SAP Remote Function Call

IBM Workload Scheduler 10.1 Fix Pack 6 has been tested with SAP RFC 7.50 Patch Level 15.

 

IBM Semeru Runtimes

IBM Workload Scheduler 10.1 Fix Pack 6 has been tested with IBM Semeru Runtime Open Edition 11.0.22.0

 

 

 

APARs and defects fixed in V10.1 Fix Pack 6

This section lists APARs resolved in V10.1 Fix Pack 6.

 

Table 1. APARs addressed in V10.1 Fix Pack 6
APARABSTRACT
IJ26882Modify command does not create the Java runtime folder.
IJ35540tdwcinst.sh --work_dir is not working when only /tmp is used as a working directory.
IJ40708Show the detailed job logs with the "SET SERVEROUTPUT ON" in case of failed jobs.
IJ42602Incorrect URLs displayed during Helm Chart installation.
IJ43998Incorrect output of composer validate compared to composer add/replace when Start of Day is not equal to 0000.
IJ47035Serverinst: wainst216e --wapassword contains incorrect characters such as equal sign =.
IJ47501conman altpass allows user passwords longer than 31 characters.
IJ47827Audit log output contents during Dynamic Workload Console operation in IBM Workload Scheduler V10.1.
IJ48013Plug-in database 10.01.02 and upper level causes job manager to go 100% CPUs or job failure when the SQL database job query output size is considerable.
IJ48789The agent does not send the status of jobs to the master.
IJ48837Error 8 occurs due to a TaskLauncher issue related to the file descriptor number.
IJ49194Job logs returned from REST API are garbled or unreadable.
IJ49215Loop job terminates without executing the specified number of runs.
IJ50713Incorrect 'risk level' status shown for critical jobs.
IJ51042Spring Daylight Saving Time change causes duplicate job stream instances when using the repeat every option.
IJ51079BmEvents are failing JSON validation because the attribute name "script" is not in right JSON format in V10.2.1.
IJ51193Connection issue between domain manager and fault-tolerant agent.
IJ51210RMSTDLIST script is failing with IBM Workload Scheduler V10.1 fix pack 3 and IBM Workload Scheduler V9.5 fix pack 7.
IJ51303According to POSIX standard, user names should be 8 characters or less on AIX server.
IJ51323Problem with the DB plug-in 'COM.IBM.SCHEDULING.AGENT.DATABASE 10.1.0.03.JAR' when using custom credentials.
IJ51366ILMT cannot find the SWID tag corresponding to IBM Workload Scheduler Agent V10.2.
IJ51367ILMT is unable to detect the SWID tag for IBM Workload Scheduler Agent V10.2.0, even though it's mentioned in the documentation.
IJ51401The makeplan command abends due to a runcycle where the "at time" is equal to the Start Of Day.
IJ51653Issue related to extracting the default certificate.
IJ51751Specifying the iws installation directory as the value for parameter for the "WORKDIR" parameter, incorrectly deletes all data from that directory.
IJ51796A V10.x dynamic agent is not able to register itself when installed on fresh machine with -noroot option.
IJ51841Issue related to the connection to Azure Data Factory.
IJ51912Issue related to security functions derived from the TWS security file.
IJ52044A RESTful job created using Dynamic Workload Console is failing with a java.lang.NullPointerException due to a capital "R" in the job definition.
IJ52101The AgentCertificateDownloader is broken for Windows when the root directory is used as the installation directory.
IJ52185There is a mirroring issue caused by a delay in processing "batchman update command" events of type "BU".
IJ52210The conman sj command does not work correctly when filtering on pools.
IJ52213Users are getting journal entries related to authority failure errors on AS400 agents.
IJ52360The Backup Master becomes unlinked with the error: "AWSITA248E AN ERROR OCCURRED INVOKING A GET HTTP REQUEST. THE ERROR IS "SSL CONNECT ERROR"".
IJ52400The Broker Master Domain Manager and the Master Domain Manager should be configured to use the same encryption keys for consistency.
IJ52593The Broker's netman process terminates unexpectedly during a Tenable (Nessus) vulnerability scan.
IJ52596Upgrade from V9.5 to V10.2.2 might fail if the passwords for the KDB (Key Database) and JKS (Java KeyStore) are identical.
IJ52841The documentation link provided needs to be updated.
IJ53095AWSITA173E cannot update the specified trace property value because of the "500" error.
IJ53096Job streams are not displayed when searching for their exact name; they only appear when using wildcard characters in the search.
IJ53111Jobs in the "INTRO" state are not being managed correctly after a Liberty server restart.
IJ53114Thread deadlocks might occur on a dynamic domain manager connected to a Z controller, blocking notifications.
IJ53119Documentation needs to be updated to clarify the behavior of the ONOVERLAP DONOTSTART option.
IJ53169The "TECEVENTFORWARDER ACTIONS" are missing from the Table of Contents section of the documentation.
IJ53170The numbering in Table #2 of the documentation for the complete procedure of switching a Domain Manager is confusing.
IJ53250Issue with incorrect internal record pointing when joins are applied to the job stream: "AWSBHT009E Batchman has found a non-valid dependency type".
IJ53326Dynamic Workload Console does not update the status of a job when it is confirmed succ from a fault-tolerant agent.
IJ53367When using a REST API to add a job stream in an active directory database with run cycle and variable table, the job stream is added with empty variable table.
IJ53388configuredb.sh script gets error WAINST104I if there is a the "$" wildcard character within the password.
IJ53424Audit logs contain information in a JSON-escaped format.
IJ53473The centralized update or fix pack installation mode of IBM Workload Scheduler should bypass the user check by default for smoother installations.
IJ53580The opens (-S %P) command does not produce the expected results when the search string is * or *.* and the destination folder contains subfolders.
IJ53694Incorrect timestamps are recorded in the Audit Details Report and the database.
IJ53988The backup master domain manager stops responding and produces Java core dumps.
IJ54273Jobs on Dynamic Agents installed with a custom certificate fail to submit successfully after the Liberty certificate is renewed.
IJ54798The following error appears in Liberty logs: "AWSJCS016E THE VALUE OF THE PROPERTY "ENABLE_DATABASE_GET_OPERATIONS_AUDIT" IS NOT CORRECT" .
KB0090326In Global Options - Licensing Configuration, the short names for LICENSEPROXYSERVERPORT and LICENSEPROXYPASSWORD are the same.
KB0106120After upgrading an agent from V10.1 GA to V10.1 Fix Pack 3, the Dynamic Workload Console does not display the correct agent version.
KB0106485An "Unsupported protocolSSL_TLS" error occurs when generating reports on containerized IBM Workload Scheduler V10.1 fix pack 3.
KB0110142The REP7 utility has an issue retrieving data on jobs.
KB0113539Run cycles with an "AT" time and a "+1 day" offset are not correctly recognizing the "+1 day" offset.
KB0114983Successor jobs are being processed even if their predecessor jobs have not completed successfully.

 

 

Table 2. Defects addressed in V10.1 Fix Pack 6
DefectsABSTRACT
WA-131183Resource CLI fails but no error message is displayed.
WA-132352Integration with PeopleSoft version 9.20 running on PeopleTools version 8.61.03 is no longer functioning correctly with IBM Workload Scheduler.
WA-133326The datagather package is missing essential files.
WA-135376Impossibility to decrypt user password in plug-ins.
WA-136239The conman stdlist command is unable to retrieve the job log for jobs running on Windows systems.
WA-136401The conman getmon command does not display the active event rules that are configured on a dynamic agent.
WA-136789A dynamic agent encounters an error and is unable to save a job with the specified ID ("c7ea4c80-4f45-11ef-bdde-a3a3cef8cafa") in its job store.
WA-136938In IBM Workload Scheduler V10.1 Fix Pack 5, the registration process between the master domain manager and dynamic agent fails after a fresh installation of the master domain manager on Linux systems running Liberty versions 24.0.0.8 and 24.0.0.9.
WA-138533Change trace level in nipcutil.c component.
WA-138694Batchman crashes after triggering a Job Status Change event rule.
WA-140640Huge size of job XA trace file after the job run.
WA-140895The schedlog folder is not being included in the generated datagather zip file.
WA-141414J2EE job fails with error "AWKRAA208E".
WA-141702In IBM Workload Scheduler V10.2.4 and V10.1 Fix Pack 6, a long sleep interval causes excessive disk space consumption.
WA-142723The GSKit version in ITA build must be the same used in the dynamic agent build.
WA-142812The installation of the master domain manager on a Linux system with an Informix database fails because the bootstrap port is already in use by another process.
WA-143293The installation of the Master on an AIX operating system has failed.
WA-143962Porting memory leak and performance for dynamic agent.
WA-145085The MAKEPLAN process, responsible for generating the production plan, fails when a job stream has an "AT" dependency that relies on a run cycle definition.
WA-145267Installing DA-only in HPUX, the installation succeeds but Job Manager returns the following errors: AWSITA082E, AWSITA104E, and AWSITA105E.

 

Resolved Common Vulnerabilities and Exposures (CVE)

The following CVEs have been resolved:
 
  • CVE-2024-11187
  • CVE-2024-22329
  • CVE-2024-22354
  • CVE-2024-24791
  • CVE-2024-34155
  • CVE-2024-34156
  • CVE-2024-34158
  • CVE-2024-4032
  • CVE-2024-45338
  • CVE-2024-47535
  • CVE-2024-47554
  • CVE-2024-47554
  • CVE-2024-6531
  • CVE-2025-22870
  • CVE-2025-22871
  • CVE-2025-22872
  • CVE-2025-23184
  • CVE-2025-24970
  • CVE-2025-25193
  • WS-2022-0468

 

Known limitations and workarounds

The following are software limitations and workarounds that affect IBM Workload Scheduler version 10.1 Fix Pack 6.

 

Installation and upgrade problems with provided drivers for MS SQL and Azure SQL database

 

When installing fresh or upgrading to version 10.1 Fick Pack 6, you might encounter an error similar to the following if you are using MS SQL on premise or 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.

Workaround

 

You can perform ONE of the following actions:

  • either add the following strings in the CLIConfig.properties file available in the IBM Workload Scheduler image in the \broker\config path:

    • com.ibm.tdwb.dao.rdbms.encrypt=TRUE
    • com.ibm.tdwb.dao.rdbms.trustServerCertificate=TRUE

    and re run the installation.

  • Or use the database drivers provided with version 10.1 Fix Pack 5. To select these drivers, specify the path to the 10.1 Fix Pack 5 drivers using the --dbdriverpath parameter when running the installation.
 

Installations on Linux S390 requiring a WebSphere Application Server Liberty version equal or prior to 2025.0.0.01

 

When installing IBM Workload Scheduler on Linux S390 operative systems, you must use a WebSphere Application Server Liberty version that is equal or prior to 2025.0.0.01.

 

 

Issue when installing agents previous to V10.2

 
 

After the installation or upgrade of an agent to V10.1 Fix Pack 6, any new installation of an agent of a version previous to V10.2 results in the agent not being able to schedule items.

 

Workaround

 

In the ita.ini file, disable the FIPS configuration by setting fips_enable to no.

 

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

 

Mixed-version environment with a master domain manager at a version earlier than 9.5 Fix Pack 4

Before you install a component at version 10.1 Fix Pack 6 in an environment with a master domain manager at a version earlier than 9.5 Fix Pack 4, install the fix for IJ47731 on the back-level master domain manager.

The fix is available on IBM Fix Central for version 9.4 Fix Pack 7. For other product versions, contact Software Support. For more information, see IJ47731: CHECKSYNC JOB FAILED IN IWS 10.1 FP02 - AWSJCL075E ERROR.

Impossibility to configure an on-premises and cloud mixed environment on V10.1 Fix Pack 6

When configuring an on-premises and Kubernetes mixed environment on version 10.1 Fix Pack 6, an issue occurs during the installation of the IBM Workload Scheduler on-premises agent. The installation fails when the on-premises agent tries to download Kubernetes certificates.

If you want your IBM Workload Scheduler on-premises agent to connect to a Kubernetes environment, you must perform the configuration using at least a V10.2.2 environment.

 

APAR IJ49049 - Limiting the number of objects retrieved by queries

monitorMaxObjectsPM property only limits the number of results for archived plans queries. The property does not affect current plan queries. For more information, see Limit the number of objects retrieved by queries.

 

APAR IJ50461 - Dynamic Workload Console installation on Windows fails if the master domain manager is already installed in the same installation path.

The installation of the Dynamic Workload Console on a Windows operating system might fail if the path selected for the installation already contains an IBM Workload Scheduler instance.

Workaround

To avoid the installation issue, you must install the Dynamic Workload Console on a path that does not contain any IBM Workload Scheduler instance.

 

Issue when moving from certificate authentication to JWT authentication if the agent was installed using custom certificates.

If you installed the agent using custom certificates, and therefore a custom password, the AgentCertificateDownloader script fails because the script has an hardcoded password value that is default.

Workaround

To avoid the issue, before running the AgentCertificateDownloader script, perform the following workaround:

On Windows operating systems

  1. Create a backup copy of the AgentCertificateDownloader.vbs script.
  2. Open the original AgentCertificateDownloader.vbs script.
  3. In sslPassword = "default", replace the "default" value with the current custom password.
  4. Run the AgentCertificateDownloader.vbs script.

On UNIX operating systems

  1. Create a backup copy of the AgentCertificateDownloader.sh script.
  2. Open the original AgentCertificateDownloader.sh script.
  3. In SSL_PASSWORD=default, replace the default value with the current custom password.
  4. Run the AgentCertificateDownloader.sh script.

 

Issue during the installation of a dynamic agent on IBM i.

When installing a dynamic agent V10.1 Fix Pack 1 and V10.1 Fix Pack 3 on IBM i, if the JWT parameter is set to true, the installation completes, but the agent is not registered.

Workaround

To overcome the issue, run the AgentCertificateDownloader script with the JWT parameter set to false.

 

Issue when scheduling jobs on Oracle PeopleSoft Enterprise PeopleTools version 8.61.

An issue may occur when scheduling jobs on PeopleSoft, causing jobs to go in ABEND status. Moreover, the following error message appears in the job logs:

PeopleSoft Message 1:DOWNbea.jolt.ServiceException: Invalid Session.

Workaround

Perform a check on PeopleSoft to investigate the problem. If you find the following error:

bea.jolt.JoltException: ERROR: When environment variable TM_ALLOW_NOTLS is not set, an SSL connection must be specified.

 

You can overcome the issue by performing the following workaround:

 

On Windows operating system

Add the -DTM_ALLOW_NOTLS=Y java property to the psagent.cmd script.

 

On UNIX operating system

Add the -DTM_ALLOW_NOTLS=Y java property to the psagent script.

 

Example

$JAVA_DIR/java $JVM_FLAGS -DnoLogCmd=true -Dtws.data.dir="$UNISONWORK/" -Dtws.dir="$METHODS_DIR/" -classpath $CPATH com.ibm.tivoli.PeopleSoft.Agent.PSAgent "$@"

To overcome the issue, you must change the psagent script as follows:

$JAVA_DIR/java $JVM_FLAGS -DTM_ALLOW_NOTLS=Y -DnoLogCmd=true -Dtws.data.dir="$UNISONWORK/" -Dtws.dir="$METHODS_DIR/" -classpath $CPATH com.ibm.tivoli.PeopleSoft.Agent.PSAgent "$@"

 

Doubled triggered events.

When creating an event rule using Job Stream Status Changed with filter on status RUNNING, instead of triggering only one event, two events may be triggered for the same job stream instance.

Fresh installation of a dynamic agent version 10.1 Fix Pack x not working properly with a master domain manager at a later version

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 master domain manager at a later version
  • The dynamic agents are using either:
    • default certificates, or
    • certificates downloaded using the AgentCertificateDownloader script or the wauser and wapassword parameters at installation time

If both the above conditions are met, jobs submitted on the dynamic agents might remain in WAIT status indefinitely. An error similar to the following is stored in the ITA_trace.log file:

2025-08-07 18:00:42.819+05:30 net_request_newthread: net_accept_ssl: 
error 127507: Error while accepting SSL connection

 

Solution

To solve this problem, run the AgentCertificateDownloader script on the dynamic agents.

Prevention strategy

To avoid encountering this problem, use one of the following approaches:

Disable JWT-based authentication

Install the dynamic agents using the wauser and wapassword parameters and setting the jwt parameter to false.

Use SSL Certificates

  1. Download the certificates from the master domain manager to the dynamic agents.
  2. 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 a later version fails

You may encounter problems when upgrading your dynamic agents from v 10.1 Fix Pack x to a later version if the dynamic agents meet both of the following conditions:

  • The dynamic agents are a 10.x version and are connected to a master domain manager at a later version
  • The dynamic agents are using either:
    • default certificates, or
    • certificates downloaded using the AgentCertificateDownloader script or the wauser and wapassword parameters at installation time

If both the above conditions are met, the upgrade process fails when upgrading the agents to version to a later version. A message similar to the following is displayed:

AWSFAB518E The certificates provided as input for the fresh installation, or already used by the
product during the upgrade process, are not compatible with FIPS mode. If you want to proceed 
with the installation without enabling FIPS, set the enablefips parameter to false and restart
the installation.

 

This message indicates a general certificate compatibility issue. While it references FIPS mode, the error may not necessarily be caused by FIPS-specific settings.

Prevention strategy

To avoid encountering this problem, run the AgentCertificateDownloader script on the agents before upgrading,

 

Fix Pack structure

This section describes the structure of the images contained in this Fix Pack.

Fix Pack files available for IBM Workload Scheduler using FixCentral

 
 
+----10.1.0.06-README.zip
|
+---10.1.0.06-IWS-AGENT-IBMi.zip
|
+---10.1.0.06-IWS-SERVER-AIX.zip
|
+---10.1.0.06-IWS-AGENT-AIX.zip
|
+---10.1.0.06-IWS-BATCH_REPORT-AIX.tar
|
+---10.1.0.06-IWS-AGENT-HPIA64.zip
|
+---10.1.0.06-IWS-AGENT-SOLARIS.zip
|
+---10.1.0.06-IWS-SERVER-LNX_X86_64.zip
|
+---10.1.0.06-IWS-AGENT-LNX_X86_64.zip
|
+---10.2.4-IWS-FILEPROXY-LNX_X86_64.zip
|
+---10.1.0.06-IWS-OCLI-LNX_X86_64.zip
|
+---10.1.0.06-IWS-BATCH_REPORT-LNX_X86_64.tar
|
+---10.1.0.06-IWS-SERVER-LNX_Z.zip
|
+---10.1.0.06-IWS-AGENT-LNX_Z.zip
|
+---10.2.4-IWS-FILEPROXY-LNX_Z.zip
|
+---10.1.0.06-IWS-BATCH_REPORT-LNX_Z.tar
|
+---10.1.0.06-IWS-SERVER-WINDOWS.zip
|
+---10.1.0.06-IWS-AGENT-WINDOWS.zip
|
+---10.2.4-IWS-FILEPROXY-WINDOWS.zip
|
+---10.1.0.06-IWS-OCLI-WINDOWS.zip
|
+---10.1.0.06-IWS-BATCH_REPORTS-WINDOWS.zip
|
+---10.1.0.06-IWS-AGENT-LNX_PPC_LE.zip
|
+---10.1.0.06-IWS-OCLI-MACx86.zip
|
+---10.1.0.06-IWS-OCLI-MACARM.zip
|
+---10.1.0.06-IWS-BATCH_REPORTS-Z_USS.tar
|
+---10.1.0.06-IWS-ZAGENT-IBMi.zip
|
+---10.1.0.06-IWS-ZAGENT-AIX.zip
|
+---10.1.0.06-IWS-ZAGENT-LNX_Z.zip
|
+---10.1.0.06-IWS-ZAGENT-HPIA64.zip
|
+---10.1.0.06-IWS-ZAGENT-SOLARIS.zip
|
+---10.1.0.06-IWS-ZAGENT-LNX_X86_64.zip
|
+---10.1.0.06-IWS-ZAGENT-WINDOWS.zip
|
+---10.1.0.06-IWS-ZAGENT-LNX_PPC_LE.zip
|
+---10.1.0.06-IWS-DOCKER-ZAGENT-LNX_X86_64.zip
|
+---10.1.0.06-IWS-DOCKER-ZAGENT-LNX_Z.zip
|
+---10.1.0.06-IWS-DOCKER-SERVER-LNX_X86_64.zip
|
+---10.1.0.06-IWS-DOCKER-AGENT-LNX_X86_64.zip
|
+---10.2.4-IWS-DOCKER-AI_Data_Advisor-LNX_X86_64.tar.gz
|
+---10.2.4-IWS-DOCKER-FILEPROXY-LNX_X86_64.zip
|
+---10.1.0.06-IWS-DOCKER-SERVER-LNX_Z.zip
|
+---10.1.0.06-IWS-DOCKER-AGENT-LNX_Z.zip
|
+---10.2.4-IWS-DOCKER-AI_Data_Advisor-LNX_Z.tar.gz
|
+---10.2.4-IWS-DOCKER-FILEPROXY-LNX_Z.zip

 

Note: The AI Data Advisor packages and the File Proxy packages contain the latest version available for AI Data Advisor and File Proxy, that is V10.2.4.

 

Installing the Fix Pack

This section describes how to apply Fix Pack 6 to IBM Workload Scheduler.

Installation notes

 
  • Before installing the Fix Pack, ensure you have installed the required prerequisite software. To obtain the latest information about software requirements for IBM Workload Scheduler, run the Detailed Software Requirements report and browse to the relevant section.
  • The minimum required WebSphere® Application Server Liberty version to successfully install the Fix Pack is 24.0.0.3 or later.
  • This Fix Pack supports DB2 Advanced Enterprise Server Edition, Version 10.5 on HP-UX and Sun Solaris operating systems only. It is available for download from the Passport Advantage web site with part number: CNED3ML. After the installation of DB2 Advanced Enterprise Server Edition, Version 10.5, you must manually apply the license activation key (.lic file). The license key must be downloaded separately from the Passport Advantage web site. The part number related to the license activation key is CNED3ML. The key must be registered using the db2licm command. See Applying DB2 licenses licenses for the procedure to register the key.

    If you already have installed DB2 Advanced Workgroup Server Edition, you can switch this license with a DB2 Advanced Enterprise Server Edition license, by following the procedure in Updating licenses. Note that when the procedure references the product-identifier as in step 3:db2licm -a product-identifier, replace the product-identifier with the file representing the license activation key (.lic).

  • On UNIX™ operating systems, before installing the IBM Workload Scheduler Fix Pack, ensure that your umask is set to 022. To verify that umask is set to the correct value, from a command prompt, run the umask command. If the value is different from 022, modify it by running the command:

    umask 022
  • On UNIX operating systems, the database administrator must have read and run privileges for the IBM Workload Scheduler installation path; otherwise the installation fails.
  • When installing on Solaris or AIX operating systems, message logs as /usr/sbin/nslookup are returned. These message logs are normal and do not impact the installation.
  • This Fix Pack installs a new version of the file tws_env.sh (tws_env.cmd) and also creates a backup file named, tws_env.sh.bk (tws_env.cmd.bk), which are both saved to the TWA_HOME/TWS directory, where TWA_HOME is the IBM Workload Scheduler installation directory. After installing the Fix Pack, if you have modified the original version, merge the content of the new version with the content of the original version to carry your customized content into the new version.
  • On IBM i operating systems, if you want to install the Fix Pack on the agent for z/OS and IBM Workload Scheduler Dynamic Agent, verify that the user profile used as TWSUser is not a member of a group profile. Set the group profile associated with the TWSUser to *NONE. If the TWSUser is a member of a group, the Fix Pack installation fails.
  • Only on Windows™ operating systems, to correctly display double-byte character set (DBCS) characters, you must perform the following actions:

    • Set the LANG environment variable to the DBCS language code you want to use, for example, set LANG=zh_CN.
    • Set the TWS_TISDIR environment variable to the IBM Workload Scheduler home directory, for example, set TWS_TISDIR=C:\FTA\TWS.
    • Open the Control Panel window and click Clock, Language, and Region.
    • Click Region and Language.
    • In the Format tab, choose from the Format drop-down list the language you want to use.
    • In the Keyboards and Languages tab, under Display Language, click install and follow the steps to install the DBCS language pack you want to use.
    • In the Administrative tab, click Change system locale and, from the drop-down list, choose the language (system locale) you want to use.

    Note that all the settings must be coherent, that is they must refer to the same DBCS language setting. After you have completed these changes, reboot your workstation to have the changes take effect.

  • When installing a dynamic agent or a fault-tolerant agent, ensure that the agent name does not start with a number. If the name of the dynamic agent starts with a number, use the -displayname parameter at installation time to specify a different name. If the name of the fault-tolerant agent starts with a number, use the --thiscpu parameter at installation time to specify a different name.

Interoperability notes

 

IBM Workload Scheduler version 10.1 Fix Pack 6 supports all product versions indicated in the IBM Workload Scheduler version 10.1.0 Release Notes which can be accessed at the following link: Release Notes.

Installation methods

For master domain manager or its backup:

see Updating the master domain manager and its backup

For dynamic domain manager or its backup:

see Updating the dynamic domain manager

For fault-tolerant agent, dynamic agent or domain manager:

see Updating agents

Disk space requirements

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

TWA_HOME/TWS + TWA_HOME/TDWB + TWA_HOME/wastools + TWA_HOME/properties

If the installation fails because of lack of free disk space, you must stop the installation, free space on your disk, and start the installation again.

In addition to the disk space in the following table, the installation requires an additional 600 MB on the file system where the IMShared directory is located.

 

Table 3. Disk space requirements for installing a master domain manager or a backup master Fix Pack
Operating SystemInstallation directoryTemporary directory
AIX®2,5 GB1,5 GB
Microsoft® Windows2 GB1 GB
Linux®1,5 GB800 MB

 

 

Table 4. Disk space requirements for installing the Fix Pack for IBM Workload Scheduler fault-tolerant agents
Operating SystemInstallation directoryTemporary directory
AIX900 MB400 MB
HP-UX1.3 GB400 MB
Solaris920 MB400 MB
Microsoft Windows700 MB350 MB
Linux720 MB350 MB

 

 

Table 5. Disk space requirements for installing the Fix Pack for IBM Workload Scheduler dynamic agents and z/OS agents
Operating SystemInstallation directoryTemporary directory
AIX600 MB250 MB
HP-UX920 MB400 MB
Solaris580 MB120 MB
Microsoft Windows800 MB400 MB
Linux600 MB250 MB
 

 

 

Documentation updates

Any additions or changes to the documentation as a result of this Fix Pack have been integrated into the online product documentation available in IBM Knowledge Center.

Contacting IBM 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 https://www.ibm.com/support/home/ Software Support.

Notices

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

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

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

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

 

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

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

 

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

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

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

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

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

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

 

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

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

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

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

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

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

COPYRIGHT LICENSE:

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

© (IBM) (2025).
Portions of this code are derived from IBM Sample Programs.
© Copyright IBM Corp. _2025_.

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

Personal use

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

Commercial use

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

Rights

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

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

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

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

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSGSPN","label":"IBM Workload Scheduler"},"ARM Category":[{"code":"a8m0z0000008ZuOAAU","label":"Fixpacks"}],"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.1.0.6"}]

Document Information

Modified date:
19 December 2025

UID

ibm17235404