Release Notes
Abstract
IBM Workload Scheduler Version 9.5 Release Notes
Content
The Release Notes for IBM Workload Scheduler, version 9.5 contain the following topics:
- Interoperability tables
- Fix packs
- Installation limitations and problems, and their workarounds
- Software limitations,problems, and workarounds
- APARs fixed in this release
- Documentation updates
- IBM Workload Automation components deployed into IBM Cloud Private
To download the appropriate package for your operating system, see the IBM® Workload Scheduler download page.
For detailed system requirements for all supported operating systems, see the Detailed System Requirements page.
To access the IBM Workload Scheduler documentation, see the online product documentation.
A complete list of new or changed functions in this release are documented in the Summary of enhancements. More information about new features, including helpful demo videos, can be found on the IBM Workload Automation What's New page. See also the V9.5 dedicated playlist on the Workload Automation YouTube channel.
Note: Only a parallel upgrade is supported starting from version 9.3 or 9.4 to version 9.5. A direct upgrade is not supported. You are strongly recommended to maintain all IBM Workload Scheduler components at the latest fix pack level.
Interoperability tables |
The level of support provided for the products and components listed in the interoperability tables covers all the shown versions.
In the tables in this section the following acronyms are used:
| DA | IBM Workload Scheduler dynamic agent |
| DDM | IBM Workload Scheduler dynamic domain manager or backup dynamic domain manager |
| DM | IBM Workload Scheduler domain manager |
| DWC | Dynamic Workload Console |
| FTA | IBM Workload Scheduler fault-tolerant agent |
| MDM | IBM Workload Scheduler master domain manager or backup master domain manager |
| ZWS Agent | IBM Z Workload Scheduler Agent |
IBM Workload Scheduler: compatibility
Note that only a parallel upgrade is supported starting from version 9.3 or 9.4 to version 9.5.
Compatibility is supported on the latest available fix pack for each IBM Workload Scheduler release listed in the table:
|
MDM |
DDM |
DM |
FTA |
DA |
ZWS Agent |
|
| MDM 9.5 |
9.5, 9.4, 9.3
|
9.5, 9.4, 9.3
|
9.5, 9.4, 9.3
|
9.5, 9.4, 9.3*
|
9.5, 9.4
|
|
| DM 9.5 |
9.5, 9.4
|
9.5, 9.4, 9.3
|
||||
| FTA 9.5 |
9.5, 9.4, 9.3
|
9.5, 9.4, 9.3
|
9.5, 9.4, 9.3
|
|||
| DA 9.5 |
9.5, 9.4, 9.3
|
9.5, 9.4, 9.3
|
9.5, 9.4, 9.3
|
|||
| DDM 9.5 |
9.5, 9.4
|
9.5, 9.4, 9.3
|
9.5, 9.4, 9.3
|
*Plug-ins on dynamic agents at 9.3 level are not supported with master domain managers at 9.5 level and cannot work with master domain managers at 9.5 level because of an incompatible Java version.
Dynamic Workload Console: compatibility
Compatibility is supported on the latest available fix pack for each release listed in the table:
|
MDM
|
DDM | |||
| DWC 9.5 |
9.5, 9.4
|
9.5 FP1 | ||
|
||||
Compatibility scenarios and limitations
You are strongly recommended to maintain all IBM Workload Scheduler components at the latest fix pack level as regular maintenance activity. Keeping your environment consistent also ensures you can implement the new features available with 9.5 FP2, such as organizing your scheduling objects in folders.
If you are using the composer command line of the agent, the following limitation applies:
• The composer command at version 9.5 FP2 works correctly with master domain managers at version 9.4.0.2 and later, but only for the following scheduling objects: jobs, job streams, run cycle groups. The remaining objects are not managed. If you need to manage these objects, use composer951 to communicate with master domain managers at version 9.4.0.2 and later. Communication with master domain managers at version 9.4 GA or 9.4 FP1 is not supported.
Environment with agents at version 9.5 FP2 and master domain managers at version 9.3
• The composer command on the agents is not supported and cannot communicate with the master domain manager.
Environment with agents at version 9.3 and 9.4 and master domain managers at version 9.5 FP2
The following considerations apply:
• Agents at version 9.3 and 9.4 work correctly with master domain managers at version 9.5 FP2. However, if you plan to store your scheduling objects in folders, note that agents at versions earlier than 9.5 FP2 can manage only objects stored in root because folders are not supported. In addition, the composer command should be connected to a backup master domain manager at version 9.5 FP2.
Fix packs released for this version of the product
To find the fix packs released for IBM Workload Scheduler, and the Dynamic Workload Console including links to the related readmes files, see Fix Central.
Installation limitations and problems, and their workarounds. |
The following are limitations and problems that might affect the installation or upgrade of IBM Workload Scheduler, and their workarounds (when available):
- SAP intercepted job XBP 3.0
-
If you plan to use the job interception collector BC-XBP 3.0 to collect and restart jobs, create the r3batch_icp folder in the TWS_home/methods/ path with the correct access rights.
- Supported characters in passwords
- The following characters are supported when defining passwords for users of master components and Dynamic Workload Console:
on Windows operating systems: Supported characters for the password are alphanumeric, dash (-), underscore (_) characters, and ()|?*~+.
on UNIX operating systems: alphanumeric, dash (-), underscore (_) characters, and ()|?=*~+.
- National characters support
- Due to a limitation in WebSphere Application Server Liberty Base, national characters are not supported when defining installation directory, working directory and data directory. For more information, see Runtime environment known issues and restrictions.
- Incorrect localopts port after dynamic domain manager installation on Windows
-
If you modify the default port for the dynamic domain manager at installation time, the value is disregarded in the localopts file, which stores the default port number.
To work around this problem, perform the following steps:
- Browse to the General attributes for CLI connections section in the localopts file.
- Modify the following line with the correct port number:
PORT = <correct_port_number> # Protocol port
The updated setting is maintained in subsequent installations.
Software limitations, problems, and workarounds |
The following are software limitations and problems that might affect IBM Workload Scheduler, and where available, a workaround to address the problem:
-
The limited fault-tolerant agent is no longer available on IBM i
- The limited fault-tolerant agent that runs on the IBM i operating system is no longer available and is replaced by the dynamic agent. The limited fault-tolerant agent on IBM i continues to be supported up to and including version 9.4. See the related documentation: https://www.ibm.com/docs/en/workload-scheduler/9.4.0?topic=limited-fault-tolerant-agent-i.
-
APAR IJ24378 - The remote command plug-in v9.5 does not work on Windows systems.
On IBM Workload Scheduler v9.5.x, the remote command plug-in does not work on Windows systems. To be able to use it, three workarounds are available:
- Workaround 1: Download from Automation Hub plug-in version 9.5.0.4, which works correctly on Windows operating systems.- Workaround 2: Install the SSH server on all Windows machines where you want to run the remote command plug-in, for plug-in versions earlier than 9.5.0.4.- Workaround 3: Replace the content of the javaExt plugin directory (ibm jvm) v9.5.x with the content of the directory v9.4, for plug-in versions earlier than 9.5.0.4.
- The Dynamic Workload Broker user interface and command line are not supported for the current release
- The listed components, also known as Broker cli and Broker UI, are not supported in version 9.5. To be able to use these components, install version 9.5, Fix Pack 1.
- < Note: To make Broker CLI and Broker UI work, both Dynamic Workload Console and master domain manager should be updated to the version 9.5, Fix Pack 1.
- Limitations for the folders feature
-
- If a job stream is present in several folders, you cannot distinguish the relevant folder.
- Folders are not available in cross dependencies and reporting.
The integrations described in manual Integrating with other products might be impacted by the new field size for some scheduling objects. The size of the fields listed below has changed from 16 to 817 bytes with the introduction of folder support. Impacted fields are as follows:
- workstation
- schedCpu
- origSchedName
- schedName
- jobCPU
- prompt
- needs
Each of these fields in IBM Workload Scheduler events will be reported into the BmEvents.conf file with a length of 817 bytes. If no folder were specified, the field will be printed as 817 with blank values.
APARS Fixed in this release |
- 1IJ05797: After installing Version 9.4, Fix Pack 3, all SBMJOB submitted on dynamic agents on IBM iSeries return the following in stdlit output: "Unable to get the completion message CPC1221 for the command <SBMJOB"
- IJ00338: Jobstream is planned unexpectedly on dates set as Except.
- IJ01507: cannot customize the cache cleanup settings for plan data replication in the database (aka mirroring).
- IJ01984: Plan view does not refresh automatically if browser and tws engine time are not synchronized
- IJ03479: ISSUE WHEN OPENING A COMPLEX VARIANT SAP
- IJ03587: NM IPVALIDATE=FULL : NETMAN LOCALOPTS PARAMETER BREAKS THE DYNAMIC BROKER LOCALHOST 127.0.0.1 LINK : AWSEDW053E AWSEDW090E
- IJ03892: JS EVERY ONOVERLAP DONOTSTART NOT CANCELLING TO CATCH UP JS'SLOGGED
- IJ04085: CREATE EVENT RULES DOES RUN ONLY IN ENGLISH.
- IJ04333: On Windows systems, file transfer jobs use 100% CPU.
- IJ04393: stageman does not remove JS after untilDays if carryStates SUCC
- IJ04395: JOB RERUN IS SLOW BECAUSE IT IS USING USELESS SQL
- IJ04677: DATE IN HEADER/FOOTER ARE ENCODED IN EUC, ALTHOUGH LANG IS UTF-8 ON SOLARIS 10.
- IJ05421: ITM agent has dockqds file that has job number as 7 characters instead of 8 characters
- IJ05783: Composer does not return the correct total number of updated objects.
- IJ05797: AFTER 940 FP03 ON DYNAMIC ISERIES OS400 AGENT, ALL SBMJOB EXIT WITH UNABLE TO GET THE COMPLETION MESSAGE CPC1221
- IJ06020: Batchman goes down after switchplan while processing OA event.
- IJ07067: JOBS WITHOUT AT TIME START AN HOUR EARLY ON DST CHANGE WHEN ENPREVENTSTART=YES
- IJ07104: THE JOB RUN HISTORY'S "ACTUAL START" AND "ACTUAL END" TIME ARE REVERSED
- IJ07122: BATCHMAN HAS A CLEAN STOP IMMEDIATELY AFTER JNEXTPLAN.
- IJ07282: Default variable table overrides the previously specified variable table.
- IJ07531: DA Iseries be able to manage CHILDS and NOCHILDS
- IJ07532: Extend the AS400 jobs user interface to allow LDA specification.
- IJ07860: JSR352: ADD USERID AND PASSWORD SUPPORT TO CONNECTION WITH PROXY
- IJ07907: TWS: THE STATUS IS "ERROR ABEND", THOUGH A FINISHED JOB EXIT WITH 0
- IJ08187: Auditing: enDbAudit optman option does not work.
- IJ08474: EVENT RULE THAT LOOKS FOR FILE IN AN UNC PATH WAS NOT SEEN
- IJ08663: CHANGES ARE NEEDED INTO LOCALOPTS AND DOCUMENTATION TOO FOR THE HOST FIELD
- IJ09120: Jobs in hold status display incorrect actual start value.
- IJ09416: Modifying a job instance in the plan using the altjob command can cause flooding of the mailbox.msg message queue.
- ij09641: Error in the value of job minimum and maximum duration (mindur and maxdur) after editing the job.
- IJ10141: Oracle EBS job completes in error with many concurrent submissions.
- IJ10311: A job containing a start condition occasionally fails with message: AWSITA418E Cannot obtain exclusive access to the repository.
- IJ12048: HIGH LOAD OF DATASTAGE JOBS (2100+) CAUSES MEMORY LEAK AND JOB FAILURES
- IJ12856: MEMORY LEAK IN WAS WITH IWS SECURITY GROUPS AND LARGE NUMBER OF OS GROUPS
- IV99439: Wrong date into "Actual Start" on listing jobs on a ZOS Connector. The value read is the actual input arrival instead of the correct one.
Documentation updates |
All updates to the IBM Workload Scheduler documentation that are required for version 9.5 are included in the editions of the publications in online IBM Knowledge Center.
IBM Workload Automation components deployed into IBM Cloud Private |
Upgrading the helm chart from version 1.0.0 to 1.0.1
In the chart 1.0.1, images have been refreshed but their version is not changed; thus, the pull of the new image with the same version must be forced.
To upgrade the helm chart from version 1.0.0 to 1.0.1 and force the image pull, import the ppa-ibm-workload-automation-prod-1.0.1.tar.gz and then proceed as follows:
- Server and agent components: upgrade the chart from the Helm release page, scale the StatefulSet down to 0 to destroy the pod and then scale it up to 1 to create a new pod which pulls the new image from the repository.
- Console component: access the database connected to the console and run the following statements:
db2 connect to <DWC_database_name>
db2 ALTER TABLE TDWC.REP_REPORTFILES RENAME COLUMN FILE TO FILECONTENT
db2 reorg table TDWC.REP_REPORTFILES
where <DWC_database_name> is the database name used at the database creation
Note: the above statements are applicable to DB2 only. If you have the console database running on a RDBMS different from DB2, please contact Workload Automation Support Team.
Upgrade the chart from the Helm release page; upgrading it, the StatefulSet pod is automatically restarted and the new image is automatically pulled from the repository.
© Copyright International Business Machines Corporation 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, 2021.
Was this topic helpful?
Document Information
Modified date:
04 November 2021
UID
ibm10733052