Release Notes for HCL Workload Automation, version 9.5
Release Notes
Abstract
This document supplies the release notes for HCL Workload Automation, version 9.5.
Content
The Release Notes for HCL Workload Automation, version 9.5 contain the following topics:
To download the appropriate package for your operating system, see HCL License Portal.
For detailed system requirements for all operating systems, see the Detailed System Requirements document availanble at Product Requirements.
To access the HCL Workload Automation documentation, see the Product Documentation.
A complete list of new or changed functions in this release are documented in the Summary of Enhancements. Helpful videos are also available on the Workload Automation YouTube channel.
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 |
HCL Workload Automation dynamic agent |
| DDM |
HCL Workload Automation dynamic domain manager or backup dynamic domain manager |
| DM |
HCL Workload Automation domain manager |
| DWC |
Dynamic Workload Console |
| FTA |
HCL Workload Automation fault-tolerant agent |
| MDM |
HCL Workload Automation master domain manager or backup master domain manager |
| ZWS Agent |
HCL Z Workload Automation Agent |
HCL Workload Automation: compatibility
|
MDM
|
DDM
|
DM
|
FTA
|
DA
|
ZWS Agent
|
| MDM 9.5 |
|
9.5, 9.4
|
9.5, 9.4
|
9.5, 9.4
|
9.5, 9.4
|
9.5, 9.4
|
| DM 9.5 |
9.5, 9.4
|
|
|
9.5, 9.4
|
|
|
| FTA 9.5 |
9.5, 9.4
|
9.5, 9.4
|
9.5, 9.4
|
|
|
|
| DA 9.5 |
9.5, 9.4
|
9.5, 9.4
|
9.5, 9.4
|
|
|
|
| DDM 9.5 |
9.5, 9.4
|
|
|
9.5, 9.4
|
9.5, 9.4
|
|
Dynamic Workload Console: compatibility
|
MDM
|
DDM |
| DWC 9.5 |
9.5, 9.4
|
9.5 FP1 |
- Note:
-
IBM Workload Scheduler V9.5 is fully compatible with Versions 9.5, 9.4 with the exception of the Dynamic Workload Broker UI and CLI capabilities which are not supported by an MDM 9.4 nor an MDM 9.5. These capabilities are supported with both the MDM and DWC at the V9.5 Fix Pack 1 level or later.
|
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.
Environment with agents at version 9.5 FP2 and master domain managers at version 9.4
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.
• After renaming resources or prompts from a master domain manager at version 95 FP2, you cannot reference nor use them on agents at version 9.3 and 9.4.
Mixed environment with agents at versions earlier than 9.5 FP2
• To use the folders feature, ensure that master domain manager, backup master domain manager, and domain managers are at version 9.5 FP2 level.
Fix packs released for this version of the product
To find the fix packs released for HCL Workload Automation, and the Dynamic Workload Console including links to the related readmes files, see HCL License Portal.
Information you must know before upgrading.
|
|
Consider the following information before installing or upgrading to HCL Workload Automation V9.5. Note that only a parallel upgrade is supported starting from version 9.x releases to the version 9.5 release.
Installation limitations and problems, and their workarounds.
|
|
The following are limitations and problems that might affect the installation or upgrade of HCL Workload Automation, 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: alphanumeric, dash (-), underscore ()?*~+..
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.
Software limitations and problems, and their workarounds.
|
|
The following are software limitations and problems that might affect HCL Workload Automation, and their workarounds (when available):
- 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.
- Some field names are longer due to folder support
-
The integrations described in 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:
- Folders are not available in cross dependencies and reporting.
- workstation
- schedCpu
- origSchedName
- schedName
- jobCPU
- prompt
- needs
Each of these fields in HCL Workload Automation 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: Pplan view does not refresh automatically if browser and tws engine time are not synchronized
- IJ02930: Plan data replication in the database (aka mirroring): a job is shown as completed even though job number and start date are missing.
- 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.
All updates to the HCL Workload Automation documentation that are required for
version 9.5 are included in the Product Documentation.
© Copyright HCL Technologies Limited 2016, 2019.