Note
Before using this information and the product it supports, read the information in Notices.
This edition applies to Fix Pack 1 for version 10.1.0 release, modification level 1 of IBM® Workload Scheduler (program number 5698-WSH) and to all subsequent releases and modifications until otherwise indicated in new editions.
IBM Workload Scheduler version 10.1.0 Readme File for Fix Pack 1
- Date
- December 2, 2022
- Fix Pack
- 10.1.0-IBM-IWS-FP0001
- Product
- IBM Workload Scheduler version 10.1.0
- General Description
- IBM Workload Scheduler Fix Pack 1 for version 10.1.0
IBM Common Inventory Technology scanner ceases HP support from January 2023. Find more information in the Known limitations and workarounds section of this readme
This readme file provides important information about Fix Pack 1 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.
It is divided into the following sections:
IBM Workload Scheduler version 10.1.0 Fix Pack 1 supports all product versions indicated in the IBM Workload Scheduler Release Notes.
For the most up-to-date information about supported operating systems, software and hardware requirements, see IBM Workload Scheduler Detailed System Requirements.
Review this section thoroughly before installing or using this Fix Pack.
About this Fix Pack
This section contains information specific for this Fix Pack including what has been modified or introduced, what has been fixed, product versions or components to which the Fix Pack applies, and compatibility issues, if any.
- 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 section includes the following subsections:
Features introduced with Fix Pack 1
- Version 10.1.0 Fix Pack 1 delivers the following enhancements:
-
- Changed features and feature capabilities
- A list of features changed since the previous release.
-
The following features have changed or have been introduced or removed since the previous release:
- REST APIs documentation automatically integrated into the product documentation
- Information about REST APIs is automatically extracted from the code and integrated into the documentation at IBM Workload Scheduler API for easier reading and increased retrievability.
- File Proxies now selected randomly in the Managed File Transfer integration
- By default, the integration uses the File Proxy specified by the dynamic domain manager. You can also optionally define a list of preferred File Proxies to be used instead of the default list.
- The File Proxy is selected randomly in the list provided by the dynamic domain manager. If you provided a custom list, the random selection is performed only on your list.
- The random selection mechanism ensures higher tolerance for peaks in workload and workstation failures. For more information, see File Transfer Integration on Automation Hub.
- Default storing mechanism of job log changed
- When you perform a fresh installation, by default the job log is stored in memory instead of being stored in a file, as in the previous releases. This ensures compliance with the PCI standard. For more information, see the section about log files and archived files in Administration Guide.
- Enhanced security with the conn_verify property
- You can now optionally set the conn_verify property to 1 or 2, so that the agent must provide valid certificates in order to establish an SSL connection. The default value is 0, which means that no verification is performed on certificates.
- Hostname verification for File Proxy
- You can now optionally enable a check on the hostname defined for the certificates used by File Proxy. To enable the verification, create the Java system property named wa.fileproxy.enforceSSLhostnameVerify and set it to true.
- Hostname verification for the mail sender plug-in
- You can now optionally define the MAILPLUGIN_ENABLE_HOST_VERIFICATION property in the TWSConfig.properties file to enable the verification of the hostname of the SMTP server. If you set the property to yes, hostname verification is enabled, if you set it to no, no verification is performed. The default value for fresh installations is yes.
-
- Supported WebSphere Application Server Liberty Base versions
- IBM Workload Scheduler Version 10.1 Fix Pack 1 was formally tested by using WebSphere Application Server Liberty Base 22.0.0.10 and 22.0.0.11. The minimum required WebSphere® Liberty version to successfully install the fixpack is 22.0.0.3 or later.
-
Higher security for job integrations
The
Verify host name check box is selected by default in some integrations. Starting from version 10.1 Fix Pack 1, to increase the security standard provided by the product, this selection starts a check on the data contained in the keystore file. Ensure you provide the correct path and credentials to the keystore file in the
Certificates section for the following integrations:
- JSR 352 Java Batch
- Restful Job Management
- Job Stream Submission
- Variable Table
If the information in the
Credentials section is not correct, this causes the job to fail with an error similar to the following:
AWKJMJ041E An error occurred during the Job submission. The error was "AWKSPI006E Keystore authentication failed. The error message is "No certificates provided, cannot verify the hostname."
If your integrations fail after upgrading to Fix Pack 1, you have the following options:
- deselect the Verify host name check box.
- provide the correct path and credentials to the keystore file.
Satisfying Requests for Enhancements (RFEs)
RFEs give customers the opportunity to collaborate directly with the product development team and other users. The team prioritizes and develops new product features based on proposals made by customers. IBM Workload Scheduler V10.1 Fix Pack 1 delivers the following RFEs:
- RFE 149367 - Installation of dynamic agents on Windows operating systems using Local System Account
- You can now install dynamic agents on Windows operating systems without providing a specific user. This means that you no longer need to provide twsuser credentials to the operator performing the installation. Moreover, the password no longer expires, ensuring a smooth running of your jobs. For more information, see the section about agent installation parameters in IBM Workload Scheduler: Planning and Installation.
- RFE 69917 - Interactive jobs supported on dynamic agents installed on Windows operating systems
- You can now determine the behavior of native and executable jobs starting interactive programs on dynamic agents installed on Windows operating systems. Interactive programs run only if the job user has an active session open when the job runs. If there is no active session for the job user, the job behavior is defined by the new RunInteractiveJobOnInvalidSession property in the
JobManager.ini
file. You can set the property to true
to enable jobs to start interactive programs even if there is no active session for the job user. Alternatively, set the property to false
to prevent jobs from starting interactive programs if there is no active session for the job user. This feature was already available for fault-tolerant agents and is now also available by default for dynamic agents. For more information about enabling and disabling this feature, see the section about configuring properties of the native job launcher [NativeJobLauncher] in Administration Guide.
- For example, consider a job which consists of both interactive instructions (for example, using a text editor), and batch instructions, which run in background when the job is launched. If you set the RunInteractiveJobOnInvalidSession property to true, batch instructions can run even if the interactive part is not displayed because the user does not have an active session at the moment.
- RFE 60060 - dynamic agents to track the workload on the local system
- This capability is now available using the Orchestration CLI, as described in the section in this readme about Orchestration CLI.
To view a complete list of RFEs, new, planned, and delivered, see: RFE online community.
- Resolved Common Vulnerabilities and Exposures (CVE)
-
CVE-2020-36518
CVE-2022-42003
CVE-2022-42004
CVE-2022-36033
CVE-2022-27664
CVE-2022-32149
CVE-2022-3171
Problems fixed in IBM Workload Scheduler Fix Pack 1 for version 10.1.0
This section lists APARs and internal defects solved by Fix Pack 1.
Table 1. APARs addressed in Fix Pack 1
APAR |
ABSTRACT |
IJ40204 |
REPORT SHARING IS NOT PROVIDING A COMPLETE LIST OF AD GROUPS |
IJ35581 |
MAIL SENT BY EVENT RULE, JAPANESE MAIL BODY IS GARBLED |
IJ39387 |
JOBSTREAM SUBMITTING TWICE IN THE PLAN |
IJ36425 |
EVENT 128 IS PRODUCED IN EVENTS.LOG WHEN WAS IS RESTARTED FOR FIRST TIME FOR ALREADY COMPLETED JOBS WITH CRITICAL AND DEADLINE PARAMETER
|
IJ40756 |
PSP CREATION FAILED USING THE SAMPLE YAML "CUSTOM PODSECURITYPOLICY DEFINITION" |
IJ40130 |
DEPENDENCY INCONSISTENCY FOR JOBSTREAMS |
IJ39156 |
MFT - ISSUE CONNECTING TO REMOTE SERVER VIA KEYSTORE THAT NO NEED PASSWORD |
IJ38859 |
JOB PRIORITY IS AUTOMATICALLY CHANGED TO ZERO (0) AFTER JNEXTPLAN
|
IJ40389 |
SECURITY FILE WITH A " ' " (SINGLE QUOTE) VIA MAKESEC <TEXT FILE> DOES NOT REPORT AN ERROR |
IJ32304 |
FORECAST PLAN PROBLEM IN JOBSTREAM RUN CYCLE GROUP
|
IJ37881 |
JLOG ARBITRARY FILE CREATION |
IJ40795 |
SEGMENTATION FAULT AFTER OPERATOR COMMAND |
IJ38340 |
CUSTOMER HAS APPLIED FP05 TO IWS9.5 FP03 ON AIX. THEY RAN THE COMPOSER COMMANDS AND IT STARTED A NEW LINE AT PORT NUMBER LINE |
IJ39558 |
CONMAN SJ ON A SPECIFIC JOB ENDS WITH A SEGMENTATION FAULT
|
IJ40702 |
COLLECTOR.SH IS FILLING THE FILE SYSTEM ASSOCIATED WITH THE IWSDATA DIRECTORY |
IJ38854 |
AWKJDB801E AN INTERNAL ERROR ACCESS DB. THE INTERNAL ERROR IS: EXCEPTION OCCURRED DURING BIGDECIMAL CONVERSION |
IJ36453 |
DYNAMIC AGENT (JOBMANAGER PROCESS) NOT ABLE TO HANDLE SPECIAL CHARACTERS |
IJ40826 |
EVENTRULE ACTION SENDMAIL GETTING FAILED WITH "IOEXCEPTION ON IWS 10.1.0.00 |
IJ38346 |
JOBMANAGER PROCESS AUTO-RESTART EVERY FEW SECONDS |
IJ42056 |
SOMETIMES JOBS SUBMITTED WITH A SUBMIT JOB OPERATION (SBJ) REMAINS IN ADD STATE
|
IJ38758 |
9.5 MDM CRASHES WITH JAVACORE DUE TO SYM_CLOSE FUNCTION WHEN WORKLOAD IS TRIED TO BE RETRIEVED |
IJ37269 |
IJ30299 NOT WORKING ON 9.5 FP5 |
IJ40326 |
WAT NULL POINTER EXCEPTION UPDATING A JS
|
KB0100213 |
SUPPORT BOOLEAN DATATYPE FOR STORED PROCEDURE PARAMETER
|
IJ40991 |
AXWAY ST JOBS GO IN ABEND
|
IJ40992 |
UNABLE TO USE PREDEFINED USER ID AND PASSWORD IN AXWAY PLUGIN
|
IJ42370 |
SUPPORT FOR IWS 10.1 + MSSQL SERVER 2019 EE |
IJ38960 |
UPDATE OPENSSL |
IJ36545 |
MAGENT PROCESS UNABLE TO READ EVENTS WRITTEN TO MAGENT.P |
IJ42365 |
IWS 10.1 WINDOWS CLUSTER ENABLER MICROSOFT@ VISUAL C++ 2005 PREREQUISITE PACKAGE IS OBSOLETE |
IJ41494 |
MODIFY THE INFORMATION ABOUT ON-PREMISE FTA CONNECT TO ON-CLOUD MDM |
IJ34871 |
TWS9.5 FP0004 JOB ABEND WITH ERROR */SCRIPT.SH: CANNOT EXECUTE [TEXT FILE BUSY] |
IJ42173 |
JNEXTPLAN -FOR EXTENSION IS NOT CONSIDERED FOR NEXT FINAL RUN |
IJ25454 |
NETMAN SERVICE NAME NOT UPDATED ON SECONDARY SERVER IN A WINDOWS CLUSTER AFTER UPGRADE
|
IJ39134 |
MFT RECEIVE JOB ISSUE IN THE ABSOLUTE PATH RESOLUTION USING A "LOCAL USER" DIFFERENT BY TWS USER |
IJ39955 |
SLOWNESS IN CONMAN COMMANDS RELATED TO JOBS WHEN STREAM NAME MENTIONED AS "@" IN MASTER
|
IJ42213 |
IWS 10.1 NEW INSTALL FAILS WHEN USING USE_ENCRYPTION=FALSE |
IJ36977 |
CONMAN CAUSES HIGH CPU UTILIZATION WHEN THE PARENT PROCESS IS KILLED |
IJ41676 |
DELAY IN "CONMAN SJ" REPLY WHEN THE SCHEDTIME IS ADDED TO THE QUERY
|
IJ37364 |
JDBC POOL EXHAUSTION BECAUSE CONNECTIONS ARE NOT RELEASED
|
IJ39468 |
WORKLOAD AUTOMATION OPERATOR V1.5.14 |
IJ41305 |
TWS 10.1 GA BROKER SSL HANG |
IJ40775 |
EVENT RULES DEFINED IN FOLDERS ARE NOT CAPTURED BY DATAGATHER SCRIPT COMING WITH PRODUCT IN VERSION 9.5: TWS_INST_PULL_INFO.SH |
IJ39712 |
REGULAR EXPRESSIONS DO NOT WORK IN REPORT'S FILTERS CRITERIA WITH 10.1 VERSION |
IJ38164 |
IWS AGENT UNLINK WHEN A VERY LONG DOMAINNAME RETURN FROM CITSCAN.UNABLE_TO_CREATE_ENTITY LOGGED AT MDM |
IJ41353 |
10.1 GA AND 9.5 JOB SUBMISSION COULD BE DELAYED ON DA |
IJ38201 |
LICENSE TYPE OF EXTENDED AGENT <X-AGENT> IS DIFFERENT FROM HOST WORKSTATION <FTA> |
IJ42383 |
QUESTION FOR ARTICLE OF 'PER JOB LICENSE MODEL' |
IJ13994 |
WINDOWS FILE DEPENDENCY THAT INCLUDES TWO BACKSLASHES DOES NOT GET RESOLVED |
IJ20203 |
CONMAN DISPLAYING A CORRUPTED USER NAME AFTER A JOB HAS LAUNCHED AND COMPLETED |
IJ31864 |
ON ZCENTRIC JOBLOG IS DELETED AT THE MAXAGE EVEN IF THE JOB IS STILL RUNNING |
IJ41671 |
NUMBEROFROWS JOB PROPERTY HAS BEEN REPLACED WITH THE "ROWSNUMBER" JOB PROPERTY IN DATABASE JOB EXECUTOR PLUGIN WITH 9.5 FP6 |
IJ41352 |
10.1 GW RANDOMLY DOWN NOT ABLE TO AUTOMATICALLY RESTART ITSELF.JOBS SUBMISSION FAILURE ON THE AGENTS.ISSUE ON 9.5 GW ALSO |
IJ39471 |
IF UNIQUENAME IS NULL? IT FAILS TO LIST THE PERSONALIZEDREPORT |
IJ41483 |
START_TWS.SH AND STOP_TWS.SH SCRIPTS CORRECTIONS NEEDED |
IJ42255 |
AUDIT JUSTIFICATION IS NOT LOGGED IN THE FILE |
IJ43774 |
ABSOLUTE KEYWORD NO LONGER WORKS IN 9.4 OR 9.5 |
IJ42478 |
AFTER INSTALLING FP6, DATABASE PLUGIN IS NOT ABLE TO RUN MSSQL STORED PROCEDURES ANYMORE |
IJ41037 |
THE JOBSTREAM END TIME REFLECTED IN THE CONSOLE IS DIFFERENT FROM ITS ACTUAL END TIME BASED ON THE LOGS |
IJ39791 |
SEVERAL DYNAMIC JOBS REMAIN IN INTRO STATUS WHEN SUBMITTED DURING A DB FAILOVER, SWITCHMGR OPERATION OF LIBERTY RESTART |
IJ41361 |
DOC APAR: REVISION OF DOCUMENTS REGARDING JVMOPTIONS ON JOBMANAGER.INI |
KB0099406 |
CANNOT KILL A SAP JOB DEFINED ON A WINDOWS DA
|
IJ43687 |
INSTALLING THE MDM WITH SELF-SIGN CERTS |
KB0100860 |
HWA FILE TRANSFERRECEIVE "INVALID CROSS-DEVICE LINK" WHEN DOING A MOVE FILE AFTER TRANSFER
|
IJ44002 |
USE OF THE "AGENTID" COMMAND LINE PARAMETER USED WITH THE "TWSINST" AGENT INSTALLATION SCRIPT REQUIRES A CHARACTER LIMITATION. |
IJ44023 |
CVE-2022-27664: golang |
IJ44021 |
CVE-2022-32149: golang |
IJ44027 |
CVE-2022-36033: jsoup-1.14.2 |
IJ44025 |
CVE-2022-3171: protobuf-java |
Backward compatibility
This fix pack delivers support for scheduling objects in folders, including workstations. When monitoring workstations from a back-level agent workstation, the output displays the workstation unique identifier and not the workstation name for those workstations that were defined in folders different from the root folder. To identify the corresponding workstation name, run the conman command using the showid filter, showcpu ;showid
, from an updated agent workstation.
Known limitations and workarounds
The following are software limitations and workarounds that affect IBM Workload Scheduler version 10.1.0 Fix Pack 1. For a list of known problems and limitations documented for the V10.1.0 General Availability release, see the product Release Notes at IBM Workload Scheduler Release Notes.
- WebSphere Liberty minimum required version
- the minimum required WebSphere Liberty version to successfully install the fixpack is 22.0.0.3.
- IBM Common Inventory Technology scanner ceases HP support
- IBM Common Inventory Technology scanner does not support HP operating systems starting from January 1st 2023. The IBM Workload Scheduler dynamic agent utilizes IBM Common Invetory Technology to collect system configuration data used in the definiton of dynamic pools. For customers using dynamic agents on HP and dynamic pools, we strongly recommend to review dynamic pool workstation definitions. If their requirements are based on filesystems, especially network or remote filesystems, we strongly recommend to remove the HP dynamic agent from the dynamic pool, since management of the requirements may not be accurate.
- APAR IJ39106
- When installing using the keystore and truststore files, customers are required to manually configure these files prior the installation setup. If providing custom .jks files, it is the customers responsibility to provide such .jks files equipped with all the CA certificates they need in the truststore. For more information see Installing the master domain manager and backup master domain manager.
- Agent Installation and Custom Certs on Upgraded MDM
-
If you plan to install a dynamic agent which uses custom certificates and connect it to a master domain manager which uses custom certificates and has been updated to version 10.1 FP1, you need to add the public part of the default certificates into the master domain manager truststore. This ensures communication between agent and master.
To import the public part of the default certificates, perform the following steps on the master domain manager:
-
On the agent, list the labels within the KDB certificate:
"gsk8capicmd_64 -cert -list -db TWSClientKeyStore.kdb"
An output similar to the following is returned:
"Certificates found
- default, -personal, ! trusted, # secret key"
! server
The public label is preceded by the "-" sign. In our example, the public label is "client".
-
On the agent, optionally, check the details for the "client" label, as follows:
"gsk8capicmd_64 -cert -list -db TWSClientKeyStore.kdb -label client"
-
On the agent, extract the "client" label to a file of your choice, as follows:
"gsk8capicmd_64 -cert -extract db TWSClienKeystore.kdb -label client -target my_file.cer"
-
On the master domain manager, import the file to the Liberty truststore JKS of the master domain manager using the keytool command, as follows:
"keytool -importcert -file my_file.cer -keystore <TWA_HOME>/usr/servers/engineServer/resources/security/TWSServerTrustFile.jks -alias my_certs -trustcacerts"
- On the master domain manager, type yes when requested to trust the imported certificate.
- You have now successfully imported the public part of the default certificates into the master domain manager truststore.
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 Fix Central
You can find and download the packages listed below at this link:
Fix Central
This is the structure of the Fix Pack for the engine on Fix Central:
+---10.1.0.1-2022.11-README.zip
|
+---10.1.0.1-2022.11-IWS-AGENT-IBMi.zip
|
+---10.1.0.1-2022.11-IWS-SERVER-AIX.zip
|
+---10.1.0.1-2022.11-IWS-AGENT-AIX.zip
|
+---10.1.0.1-2022.11-IWS-BATCH_REPORT-AIX.zip
|
+---10.1.0.1-2022.11-IWS-AGENT-HPIA64.zip
|
+---10.1.0.1-2022.11-IWS-AGENT-SOLARIS.zip
|
+---10.1.0.1-2022.11-IWS-SERVER-LNX_X86_64.zip
|
+---10.1.0.1-2022.11-IWS-AGENT-LNX_X86_64.zip
|
+---10.1.0.1-2022.11-IWS-FILEPROXY-LNX_X86_64.zip
|
+---10.1.0.1-2022.11-IWS-OCLI-LNX_X86_64.zip
|
+---10.1.0.1-2022.11-IWS-BATCH_REPORT-LNX_X86_64.zip
|
+---10.1.0.1-2022.11-IWS-SERVER-LNX_Z.zip
|
+---10.1.0.1-2022.11-IWS-AGENT-LNX_Z.zip
|
+---10.1.0.1-2022.11-IWS-FILEPROXY-LNX_Z.zip
|
+---10.1.0.1-2022.11-IWS-BATCH_REPORT-LNX_Z.zip
|
+---10.1.0.1-2022.11-IWS-BATCH_REPORT-LNX_X86_64.tar
|
+---10.1.0.1-2022.11-IWS-SERVER-WINDOWS.zip
|
+---10.1.0.1-2022.11-IWS-AGENT-WINDOWS.zip
|
+---10.1.0.1-2022.11-IWS-FILEPROXY-WINDOWS.zip
|
+---10.1.0.1-2022.11-IWS-OCLI-WINDOWS.zip
|
+---10.1.0.1-2022.11-IWS-BATCH_REPORTS-WINDOWS.zip
|
+---10.1.0.1-2022.11-IWS-AGENT-LNX_PPC_LE.zip
|
+---10.1.0.1-2022.11-IWS-OCLI-MACx86.zip
|
+---10.1.0.1-2022.11-IWS-OCLI-MACARM.zip
|
+---10.1.0.1-2022.11-IWS-BATCH_REPORTS-Z_USS.tar
|
+---10.1.0.1-2022.11-IWS-ZAGENT-IBMi.zip
|
+---10.1.0.1-2022.11-IWS-ZAGENT-AIX.zip
|
+---10.1.0.1-2022.11-IWS-ZAGENT-LNX_Z.zip
|
+---10.1.0.1-2022.11-IWS-ZAGENT-HPIA64.zip
|
+---10.1.0.1-2022.11-IWS-ZAGENT-SOLARIS.zip
|
+---10.1.0.1-2022.11-IWS-ZAGENT-LNX_X86_64.zip
|
+---10.1.0.1-2022.11-IWS-ZAGENT-WINDOWS.zip
|
+---10.1.0.1-2022.11-IWS-ZAGENT-LNX_PPC_LE.zip
|
+---10.1.0.1-2022.11-IWS-DOCKER-ZAGENT-LNX_X86_64.zip
|
+---10.1.0.1-2022.11-IWS-DOCKER-ZAGENT-LNX_Z.zip
|
+---10.1.0.1-2022.11-IWS-DOCKER-SERVER-LNX_X86_64.zip
|
+---10.1.0.1-2022.11-IWS-DOCKER-AGENT-LNX_X86_64.zip
|
+---10.1.0.1-2022.11-IWS-DOCKER-AIDA-LNX_X86_64.zip
|
+---10.1.0.1-2022.11-IWS-DOCKER-FILEPROXY-LNX_X86_64.zip
|
+---10.1.0.1-2022.11-IWS-DOCKER-SERVER-LNX_Z.zip
|
+---10.1.0.1-2022.11-IWS-DOCKER-AGENT-LNX_Z.zip
|
+---10.1.0.1-2022.11-IWS-DOCKER-AIDA-LNX_Z.zip
|
+---10.1.0.1-2022.11-IWS-DOCKER-FILEPROXY-LNX_Z.zip
|
+---10.1.0.1-2022.11-IWS-OCLI-MACARM.zip
|
+---10.1.0.1-2022.11-IWS-OCLI-MACx86.zip
|
+---10.1.0.1-2022.11-IWS-OCLI-MACx86.zip
|
+---10.1.0.1-2022.11-IWS-OCLI-MACARM.zip
|
+---10.1.0.1-2022.11-IWS-OCLI-MACx86.zip
|
+---10.1.0.1-2022.11-IWS-OCLI-MACARM.zip
Installing the Fix Pack
This section describes how to apply Fix Pack 1 to IBM Workload Scheduler.
The section is divided into the following subsections:
Installation notes
When installing the IBM Workload Scheduler Fix Pack, follow these recommendations:
- 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 Software Requirements report and browse to the relevant section.
- The minimum required WebSphere Liberty version to successfully install the fixpack is 22.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).
- Before installing this Fix Pack on AIX® V7.1 operating systems, you must apply the patch for APAR IZ99634. For more information, see: APAR IZ99634.
- 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. (54367)
After the Fix Pack installation completes, verify the following information:
- 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.0 Fix Pack 1 supports all product versions indicated in the IBM Workload Scheduler version 10.1.0 Fix Pack 1 Release Notes which can be accessed at the following link: Release Notes.
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 Fix Pack installation, ensure that 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
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 2. Disk space requirements for installing a master domain manager or a backup master Fix Pack
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 Fix Pack for IBM Workload Scheduler 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 the Fix Pack for IBM Workload Scheduler 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 Fix Pack installation requires also 300 MB free disk space in the temporary directory /var/tmp
.
Installation methods
Before Installing
Before installing the Fix Pack using any of the methods described in the following sections, perform the following actions:
- If you have jobs scheduled to run on the instance you are upgrading, make sure that they have completed otherwise some processes, such as
jobmon
or joblnch
, might still be active.
- Download the appropriate ZIP files for the operating system from IBM Fix Central.
- Extract the content of the ZIP files into a directory, using one of the extraction tools available on your system or downloadable from the Internet. The tool you use must be able to keep the file permissions on the extracted files, for example, infozip.
Note:
- If you want to install the Fix Pack on IBM i, to untar the eImages, see Extract the eImages for the Z Agent and Dynamic Agent on IBM i operating systems.
- To extract the .zip file onto a Windows 64-bit system, ensure that the eImage is not located on the desktop because the Windows operating system extract tool has a problem. Choose another directory into which to extract the Fix Pack eImage.
Creating or updating the IBM Workload Scheduler database schema
Before launching any of the installation methods, create or update the database schema.
Before applying the Fix Pack, create the database schema by following the procedure described in the Creating and updating the database tables chapter in the IBM Workload Scheduler: Planning and Installation guide.
If the database already exists, update the database by running the following command:
- On Windows operating systems
-
cscript configureDb.vbs --rdbmstype db_type --dbhostname db_hostname
--dbport db_port --dbname db_name --dbuser db_user
--dbpassword db_password --dbadminuser db_administrator
--dbadminuserpw db_administrator_password
- On UNIX operating systems
-
./configureDb.sh --rdbmstype db_type --dbhostname db_hostname
--dbport db_port --dbname db_name --dbuser db_user
--dbpassword db_password --dbadminuser db_administrator
--dbadminuserpw db_administrator_password
If a new version of the database is available, update to it by following the procedure described in the Upgrading the database schema chapter in the IBM Workload Scheduler: Planning and Installation guide.
Extract the Images for the IBM Z Workload Scheduler Agent and Dynamic Agent on IBM i operating systems
The following packages are available with this Fix Pack:
- 10.1.0-IBM-IWS-IBM_I_ZOS_AGENT-FP0001.tar: The IBM Z Workload Scheduler Agent on IBM iimage.
- 10.1.0-IBM-IWS-IBM_I_AGENT-FP0001.zip: The dynamic agent on IBM i image. This package also contains an extraction tool executable that can be copied to the IBM i workstation.
To untar or unzip the Fix Pack eImages, you can use the PASE shell or the AIXterm.
- Using PASE shell:
-
- Open the PASE shell.
- Run the command:
"CALL QP2TERM"
- Locate the folder where you downloaded the Fix Pack eImage and run the command:
- IBM Z Workload Scheduler Agent
- "tar xvf 10.1.0-IBM-IWS-IBM_I_ZOS_AGENT-FP0001.tar"
- Dynamic agent
- "unzip 10.1.0-IBM-IWS-IBM_I_ZOS_AGENT-FP0001.zip"
- Exit from the PASE shell.
- Using AIXterm:
-
- Start the Xserver on your desktop.
- On the iSeries machine, open a QSH shell and export the display.
- In QSH shell, go to the directory /QopenSys and run the command:
"aixterm -sb"
- A pop-up window is displayed on your desktop. Using this pop-up window, unzip the 10.1.0-IBM-IWS-IBM_I_AGENT-FP0001.zip file, or untar the 10.1.0-IBM-IWS-IBM_I_ZOS_AGENT-FP0001.tar.
Rolling back an applied fix pack
This topic describes how to roll back an applied fix pack to a previous version.
Documentation updates for IBM Workload Scheduler Fix Pack 1 for version 10.1.0
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 Documentation.
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 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 Corp.) (2022).
Portions of this code are derived from IBM Corp. Sample Programs.
© Copyright IBM Corp. _2022_.
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 http://www.ibm.com/legal/copytrade.html.
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](javcomp.gif) |
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.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at http://www.ibm.com/legal/copytrade.html.
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.
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.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
![](javcomp.gif) |
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. |
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"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.1"}]