IBM Support

Release Notes for IBM Workload Scheduler Version 10.2.1

Fix Readme


Abstract

This document provides important information about IBM Workload Scheduler version 10.2.1

Content

IBM Workload Scheduler version 10.2.1 Release Notes

Date
December 7, 2023
Release Name
10.2.1-IBM® Workload Scheduler-IWS-2023.12
Product
IBM Workload Scheduler version 10.2.1
General Description
IBM Workload Scheduler 10.2.1
Product versions and components to which the release applies
This release can be applied only on top of IBM Workload Scheduler V10.2.0, and subsequent releases.

This document provides important information about IBM Workload Scheduler version 10.2.1.

The most up-to-date version of this document can be accessed at the following URL: Download Documents, System Requirements, Release Notes.

It is divided into the following sections:

Features introduced with version 10.2.1

APARs and defects fixed in version 10.2.1

Resolved Common Vulnerabilities and Exposures (CVE)

Known limitations and workarounds

Package structure

Installing and upgrading to version 10.2.1

Documentation updates

Contacting IBM Workload Scheduler Software Support

Notices

Features introduced with version 10.2.1

For more information about new features introduced with this release, see Summary of enhancements.

Helpful videos demonstrating new features on Workload Automation YouTube channel.

APARs and defects fixed in version 10.2.1

This section lists APARs resolved in version 10.2.1.

Table 1. APARs addressed in version 10.2.1
APAR NUMBER DESCRIPTION
IJ26359 JobStreamInPlan query didn't have the required How-Many field in the mandatory parameters
IJ29124 JOIN DEPENDENCIES LOADED INCORRECTLY DURING FINAL EXECUTION
IJ31613 JNEXTPLAN SCRIPT ACCEPTS INVALID OPTIONS
IJ33053 RESTFUL API ""SUBMIT JOB STREAM"" - NOT POSSIBLE TO SUBMIT WITH TIME RESTRICTION FILTERS
IJ40824 OPENSHIFT DYNAMIC AGENT JOB ABEND WITH AWKKUP024I AND AWKKUP020I MESSAGE
IJ41358 KB0099742 - TWS 9.4,95,10.1 STREAMS ARE NOT BEING ADDED TO THE PLAN DURING FINAL EVEN IF RUN CYCLE IS ALREADY DEFINED
IJ41797 9.5 ON WINDOWS SUBMIT JS FINAL FROM DWC CAN CAUSE MDM CRASH
IJ42166 ConfigureDB fails with java.lang.IllegalArgumentException: Unsupported protocolSSL_TLSv2 (DB2 ONLY)
IJ44514 KILL FAILS ONLY TO JOBS DEFINED UNDER FOLDERS
IJ45023 CONDITIONAL DEPENDENCY (DOCOND) DOES REMAIN UNDEFINED IF ANY OTHER DEPENDENCY IS NOT SATISFIED TOO
IJ45095 CONFIGURING TO USE THE SAME LTPA TOKEN_KEYS
IJ46158 UNABLE TO REGISTER NEW HP-UX AGENT DUE TO ISSUES WITH WS_WSCANHW.SH SCRIPT
IJ46420 FTA LOCALOPTS PERMISSION USER AND GROUP ARE SHOWING AS A ROOT IN 10.1
IJ46693 TWS R3BATCH STOP WORKING WHEN USING THE NEW RFC 7.50 PATCH LEVEL 11
IJ46698 STARTUPLWA/SHUTDOWNLWA FAILS TO START/STOP EDWA SSM AGENT AFTER UPGRADE FTA
IJ46714 CHECKSYNC JOB ABEND WITH ERROR AWSJCL075E AFTER CHANGING TWSUSER PASSWORD
IJ47034 SERVERINST: WAINST216E --WAPASSWORD CONTAINS INCORRECT CHARACTERS (ASTERISK '*')
IJ47130 ISSUE WITH V10.1.0.2 FILETRANFER (SENT IS OK BUT RECEIVE IS NOT)
IJ47135 EVEN CHANGING CONMAN TRACE AND LOG LEVELS TO WARNING, INFO MESSAGES ARE STORED INTO LOGS
IJ47142 REGARDING ITERATIVE JS SETTINGS
IJ47148 ADHOC PROMPTS CREATED WHEN PREDECESSOT FALLS OFF PLAN CREATED AT TOP LEVEL FOLDER
IJ47233 A CHANGE IN A RESOURCE QUANTITY IN THE DATABASE IS NOT ALSO IMPLEMENTED IN THE PLAN AFTER JNEXTPLAN
IJ47252 REPORTS GIVING INCORRECT OUTPUT WHEN THE BROWSER LANGUAGE IS KOREAN
IJ47271 INFORMATION ON COMPATIBILITY LIMITATIONS BETWEEN COMPOSER 10.1 AND 9.4 IS NOT LINKED TO THE INTEROPERABILITY TABLE
IJ47315 INCORRECT RESULT ON DWC FOR USER WITH MODIFY PRIVILEGE
IJ47323 ENCRYPTION OF SYMPHONY FILE IN ENVIRONMENTS WHERE A LARGE NUMBER OF NEEDS AND PROMPTS, ARE USED CAN INCREASE CPU % AND CAUSE INT
IJ47325 USEROPTS FILE IS CREATED WITH A PERMISSION READABLE BY OTHER USER
IJ47467 DATA GATHER OUTPUT DELETED WHEN OUTPUT AND WORKDIR PARMS HAS SAME VALUE
IJ47471 NOT ABLE TO ADD DEPENDENCY THROUGH CONMAN USING JOB STREAM ID
IJ47481 DBUSER IS NOT AUTOMATICALLY GRANTED ALL NEEDED ACCESS TO IBM Workload Scheduler TABLES ON THE DATABASE SERVER
IJ47505 MDM LIBERTY CRASHES DURING AN IWS COMPOSER REPLACE COMMAND PROCESSING
IJ47537 OPENS FILE DEPENDENCY IN WINDOWS NOT WORKING AFTER UPGRADING FROM 9.4.X TO 10.1.X
IJ47582 AIDA HOW TO ADD KPI CATEGORY
IJ47583 EVENT RULE DOCUMENTATION MISS SOME IMPORTANT NOTICE
IJ47644 AWSUI0145E ERROR ON SUBMITTING STREAM USING VARIABLES AFTER 10.1.0.2 UPGRADE
IJ47659 AUTOMATION HUB SALESFORCE PLUGIN DOCUMENTATION IS MISSING THE RESTRESOURCE URL MAPPING INSTRUCTIONS IN APEX FUNCTIONS
IJ47663 UNABLE TO MONITOR UPGRADE FTA/DA VIA DWC UPDATE AGENT
IJ47683 WRONG STEPS LISTED AT HTTPS://WWW.IBM.COM/DOCS/EN/WORKLOAD-AUTOMATION/9.5.0?TOPIC=EXAMPLES-EXAMPLE-10-UPGRADING-AGENTS-IN-CLUST
IJ47709 AIDA THE PLAN TIME FOR RETRAINING CAN NOT BE CHANGED
IJ47757 VULNERABILITY IN GUAVA (CVE-2023-2976)
IJ47841 IWS 10.1 DOCUMENT ABOUT AUDIT LOG
IJ47952 DWC 9.5 FIXPACK 6 INSTALL ISSUE ON AIX 7.1
IJ48414 AIDA PROPHET_ORCHESTRATOR ""ALERT-SCHEDULE"" PARAMETER SHOULD BE ""SCHEDULE_ALERT""
IJ48417 AGENTCERTIFICATEDOWNLOADER SCRIPT REQUIRES --DISPLAYNAME PARAMETER
IJ48418 REMOTE COMMAND PLUGIN RETURNS -1 WHEN THE RETURN CODE IS 1
IJ48456 WAS CONSTANTLY CRASHES - LIBTWSPLANJNI.SO TENTATIVE FIX
IJ48491 THIS DESCRIPTION IS SAME ON V9.5 AND V10.1 IN DOCUMENT, BUT CONTENT IS DIFFERENT FOR 9.5
IJ48505 UPGRADING Z-CENTRIC AGENTS FOR SUPPORTED OS RELEASES FROM IWS 9.4.0.XX TO 10.1.0.XX
IJ48550 UNABLE TO ADD NEW AGENT THROUGH COMPOSER IN 9.5 FP3
IJ48586 AIDA DOCUMENTATION FOR ALERT DEFINITION
IJ48603 AIDA - MDM LIBERTY CAN NOT BE STARTED IF EXPOSING METRICS ACCORDNG TO THE AIDA DOCUMENTATION TO MODIFY PROMETHEUS.XML
IJ48628 WEBSPHERE MQ PLUGIN | UPGRADE AGENT FROM 9.X TO 10.1 DID NOT SET INTO ITA.INI THE 2 KEYWORDS ARE MISSING
IJ48750 ALL THE KPIS REMAINS DISPLAYED AS "NEVER TRAINED" UNDER COMBINATION OF IWS ENGINE V10.2 AND AIDA V10.2
IJ48777 IN CONMAN SS ONLY SOME JOB STREAMS IS NOT DISPLAYED
IJ48841 CONMAN SBS GENERATED JAVACORE WITH THE COMPILERJNI.CPL_CREATESYM NEW FUNCTION
IJ48945 THE FOLLOWING ERROR IS LOGGED IN WINDOWS VIEWER EVERY TIME A DAILY JOB IS EXECUTED
IJ48989 INCORRECT INFO ON THE DOCUMENTATION FOR UPDATING THE DWC
IJ49034 FAILING TO GET THE BACKUP VALUE, THE ESTIMATED TIME IS SET TO THE DEFAULT ONE, WHICH IS 0
IJ49064 POTENTIAL EDWAPROXY COMMUNICATION FAILURE WHEN FTA CENTRALIZED UPDATE IS GOING THROUGH DM
IJ49067 ALL THE KPIS REMAINS DISPLAYED AS ""NEVER TRAINED"" UNDER COMBINATION OF IWS ENGINE V10.1 FP3 AND AIDA V10.2
KB0106666 Single Signon does not work when replicaset is 2 (for wa-console)

Resolved Common Vulnerabilities and Exposures (CVE)

The following CVEs have been resolved:
  • CVE-2023-2976

Known limitations and workarounds

The following are software limitations and workarounds that affect IBM Workload Scheduler 10.2.1:
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.1 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 on 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.
Rest API submit job stream not possible with time restriction filters
Submitting a job stream with restful API is not possible when using time restriction filters.
Workaround
The Rest API is POST /plan/{planId}/jobstream/{jobstreamId}/action/submit_jobstream with the jobstreamId as NONE value, the planId where the job stream has to be submitted and the body with the SubmitJobStreamInfo as following: 
{
"inputArrivalTime": "2023-07-04018:01:29.371Z",
"alias": "JSALIAS",
"jobstream":
{ *RESPONSE_OF_MAKEJOBSTREAM* }
}
To avoid inserting manually all jobs definitions, use the response of the Rest API POST /plan/{planId}/jobstream/{jobstreamId}/action/make_jobstream that requires the jobstreamId, the planId and the following body:
{ "inputArrivalTime": "2023-07-04T08:01:29.371Z", "alias": "JSALIAS" }
The response of the make_jobstream Rest API can be used as a job stream field in the submit_jobstream API body. Before calling the Rest API it is necessary to replace all the occurrences of timeRestriction with the correct ones and whatever you need to change for the submission.
Pool workstation details defined on the dynamic domain manager are not visible after switching the dynamic domain manager to backup dynamic domain manager
When you install a dynamic domain manager and then switch it to backup dynamic domain manager, the operation seems to be successful if you check the environment from the command line, but in the dynamic domain manager database some fields in the PPS_PRODUCT_PROPERTIES table are not correctly updated and still refer to the workstation which was previously the dynamic domain manager. An error similar to the following is returned: 
AWSJOM177E An error occurred getting the definition of the workstation 
"<POOL_NAME>". The workload broker server is currently unreachable.
Workaround
To work around the problem, perform the following steps:
  1. Retrieve the domain ID by running a query similar to the following: 
    select hex(CAST(DOM_ID as VARCHAR(100))) 
as DOM_ID,DOM_NAME from MDL.DOM_DOMAINS  order by DOM_NAME
  2. Check that the domain ID is correct.
  3. Correct the following fields in the table:
    DomainManager.Workstation.Name
    This is the workstation name of the new dynamic domain manager. Verify the current value is the expected one. You can obtain this value using the conman command line or from the MDL.WKS_WORKSTATIONS table on the master domain manager.
    MasterDomainManager.HostName
    This is the full qualified host name or the IP of the new master domain manager. Verify the current value is the expected one. You can obtain this value using the conman command line or from the MDL.WKS_WORKSTATIONS table on the master domain manager.
    MasterDomainManager.Name
    This is the workstation name of the new master domain manager. Verify the current value is the expected one. You can obtain this value using the conman command line or from the MDL.WKS_WORKSTATIONS table on the master domain manager.
    MasterDomainManager.URIs
    This is the list of the master domain managers to be contacted by the dynamic domain manager The list must contain in the first position the new master domain manager and in second position the new backup master domain manager
    DomainManager.Workstation.Address
    This is the full qualified host name or the IP of the new dynamic domain manager.
For more information, see the technote available at Pool Workstation Details defined under the DDM are not Visible After Upgrade to 10.1
Event-driven Workload Automation: the event is not triggered if the login value contains a domain
Domain names are not supported in login values.
Workaround
To work around this problem, use a wild card in place of the user domain name, as shown in the following example: 

<attributeFilter name="Login" operator="eq">
               <value>*ITAuser</value>
</attributeFilter>
Dynamic agents upgraded from v 10.1 to 10.2.1 cannot connect to the master domain manager
This problem is caused by a parameter located in the ita.ini file, which must be deleted. Stop the agent, delete the ssl_ciphers parameter, and restart the agent.
 

Event action for email plug-in fails
Event action for email plug-in fails to send emails and completes with error null.

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:
  1. Shut down the workstation of the fault-tolerant agent
  2. Create a backup of the localopt file
  3. Create a new folder under the target fault-tolerant agent as in the following example: <TWS_DATA_DIR>/<new_cert_folder>
  4. From the master domain manager, copy the files under TWA_DATA_DIR/ssl/depot
  5. Paste the TWA_DATA_DIR/ssl/depot files from the master domain manager into the <TWS_DATA_DIR>/<new_cert_folder> new directory
  6. 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
  7. Turn on the workstation of the fault-tolerant agent.

Package structure

For a detailed list of available packages, see the 10.2.1 Quick Start Guide (Part number M0GNCML) document available in IBM Fix Central.

Installing and upgrading to version 10.2.1

This section describes how to apply version 10.2.1 to IBM Workload Scheduler.

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.
  • If you are upgrading to version 10.2.1 from versions earlier than or equal to 9.5FP3, you have to upgrade first to 10.2 GA.
  • If you are upgrading to version 10.2.1 from versions later than or equal to 9.5FP4, you can perform the upgrade as usual.
  • The minimum required WebSphere® Liberty version to successfully install the release is 23.0.0.3 or later.
  •  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.
  • If you use WebSphere Application Server Liberty version 24.0.0.7 or above, add the verifyHostname="false" parameter to the ssl_config.xml file, in the twaSSLSettings section. See the following example: 
    <ssl id="twaSSLSettings" keyStoreRef="twaKeyStore" trustStoreRef="twaTrustStore" sslProtocol="TLSv1.2" clientAuthenticationSupported="true" verifyHostname="false"/>
    The file is located in<installation_directory>/usr/servers/engineServer/configDropins/overrides. This problem is solved in IBM Workload Scheduler version 10.2.3 and later.
  • Before installing this release on AIX V7.1 operating systems, apply the patch for APAR IZ99634. For more information, see: APAR IZ99634.
  • Before you install on UNIX™ operating systems, ensure that 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 following command: 
    umask 022
  • On UNIX operating systems, the database administrator must have read and run privileges for the IBM Workload Scheduler installation path. If this is not the case, the installation fails. (54367)
After the installation completes, verify the following information:
  • This release 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 completing the installation, if you have modified the original version, merge the content of the new version with the content of the customized version to carry your customized content into the new version.
  • When merging the two versions as described above, ensure you do not modify the paths to OpenSSL libraries.
  • On IBM i operating systems, if you want to install the release 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 installation fails.
  • Only on Windows™ operating systems, to correctly display double-byte character set (DBCS) characters, 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 consistent, 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.
Installation and upgrade methods

You can install the release using the procedure described in Installing IBM Workload Scheduler.

You can upgrade to this release using the procedure described in Upgrading.

If your environment consists of components at various version levels, see Upgrading in a mixed-version environment when using default certificates.

On Windows operating systems, if you are upgrading from any version earlier than 10.2 GA, before you perform the upgrade, check if the TWSServerKeyFile.p12 and TWSServerTrustFile.p12 files are present in any of the following folders:
master domain manager
  • installation directory
  • \usr\servers\engineServer\resources\security
Dynamic Workload Console
  • installation directory
  • \usr\servers\dwcServer\resources\security
If one or both files are present, remove them before you start the upgrade.
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

Before starting the installation, ensure you have the necessary disk space available on the file system. Consider that the disk space check calculated by the installation considers the entire space occupied by the TWA_HOME directory. The space required by the backup is the sum of the following directories: 
TWA_HOME/TWS + TWA_HOME/TDWB + TWA_HOME/wastools + TWA_HOME/properties

If the installation fails because of lack of free disk space, 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 available on the file system where the IMShared directory is located. *Note: The composer command line of the agent at version 10.2 works correctly with master domain managers at version 9.5 and later.

Table 2. Disk space requirements for installing a master domain manager or a backup master
Operating System Installation directory Temporary directory
AIX 2,5 GB 1,5 GB
Microsoft® Windows 2 GB 1 GB
Linux® 1,5 GB 800 MB
Table 3. Disk space requirements for installing the fault-tolerant agents
Operating System Installation directory Temporary directory
AIX 900 MB 400 MB
HP-UX 1.3 GB 400 MB
Solaris 920 MB 400 MB
Microsoft Windows 700 MB 350 MB
Linux 720 MB 350 MB
Table 4. Disk space requirements for installing dynamic agents and z/OS agents
Operating System Installation directory Temporary directory
AIX 600 MB 250 MB
HP-UX 920 MB 400 MB
Solaris 580 MB 120 MB
Microsoft Windows 800 MB 400 MB
Linux 600 MB 250 MB
Note: Only on HP and Solaris operating systems, the installation requires also 300 MB free disk space in the temporary directory /var/tmp.

Compatibility

Compatibility is supported on the latest available fix pack for each IBM Workload Scheduler release listed in the table:
Table 5. Compatibility
MDM DDM DM FTA DA ZWS Agent
MDM 10.2 10.2, 10.1, 9.5, 9.4 10.2, 10.1, 9.5, 9.4 10.2, 10.1, 9.5, 9.4 10.2, 10.1, 9.5, 9.4 9.4
DM 10.2 10.2, 10.1, 9.5, 9.4 10.2, 10.1, 9.5, 9.4
FTA 10.2 10.2, 10.1, 9.5, 9.4* 10.2, 10.1, 9.5, 9.4 10.2, 10.1, 9.5, 9.4
DA 10.2 10.2, 10.1, 9.5, 9.4 10.2, 10.1, 9.5, 9.4 10.2, 10.1, 9.5, 9.4
DDM 10.2 10.2, 10.1, 9.5, 9.4 10.2, 10.1, 9.5, 9.4 10.2, 10.1, 9.5, 9.4

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

Performing the centralized agent update

Before performing a centralized update on fix packs or upgrade on releases on a stand-alone fault-tolerant agent to the current version, 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 the current version, 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.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, search for the APAR number IJ50967 on IBM Fix Central, download the curl file 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, search for the APAR number IJ50967 on IBM Fix Central, download the curl file 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.

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, 2023.
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 Logo		 Java™ and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.

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

ITIL™ is a Registered Trade Mark of AXELOS Limited.

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

Terms and conditions for product documentation
Permissions for the use of these publications are granted subject to the following terms and conditions.
Applicability
These terms and conditions are in addition to any terms of use for the IBM 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.1"}]

Document Information

Modified date:
28 July 2025

UID

ibm17032127

Page Feedback