Fix Readme
Abstract
This readme file provides important information about Fix Pack 7 for IBM Workload Scheduler version 9.4.
Content
Note
Before using this information and the product it supports, read the information in Notices.
This edition applies to Fix Pack 7 for version 9, release 4, modification level 0 of IBM Workload Scheduler (program number 5698-WSH) and to all subsequent releases and modifications until otherwise indicated in new editions.
IBM Workload Scheduler Readme File for Fix Pack 7 for version 9.4.0
- Date
- 18 December 2020
- Fix Pack
- 9.4.0-IBM-IWS-FP0007
- Product
- IBM Workload Scheduler version 9.4.0
- General Description
- IBM Workload Scheduler Fix Pack 7 for version 9.4.0
This readme file provides important information about Fix Pack 7 for IBM Workload Scheduler version 9.4.0.
The most up-to-date version of this readme file can be accessed at the following URL: https://www.ibm.com/support/pages/node/6381668
IBM version 9.4.0 Fix Pack 7 supports all product versions indicated in the Release Notes
For the most up-to-date information about supported operating systems, software and hardware requirements, see the 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 V9.4.0, and subsequent Fix Pack.
This section includes the following subsections:
- Features introduced with Fix Pack 7
- Features introduced with Fix Pack 6
- Features introduced with Fix Pack 5
- Features introduced with Fix Pack 4
- Features introduced with Fix Pack 3
- Features introduced with Fix Pack 2
- Features introduced with Fix Pack 1
- Problems fixed in IBM Workload Scheduler Fix Pack 7 for version 9.4.0
- Problems fixed in IBM Workload Scheduler Fix Pack 6 for version 9.4.0
- Problems fixed in IBM Workload Scheduler Fix Pack 5 for version 9.4.0
- Problems fixed in IBM Workload Scheduler Fix Pack 4 for version 9.4.0
- Problems fixed in IBM Workload Scheduler Fix Pack 3 for version 9.4.0
- Problems fixed in IBM Workload Scheduler Fix Pack 2 for version 9.4.0
- Problems fixed in IBM Workload Scheduler Fix Pack 1 for version 9.4.0
- Known limitations and workarounds
Features introduced with Fix Pack 7
- Before upgrading to Fix pack 7 perform the following tasks:
-
On a primary domain manager or a backup master domain manager, in maestrohome/applicationJobPlugIn create a dummy file with twsuser for example: "dummy.txt", create the file in: maestrohome/applicationJobPlugIn like: /opt/IBM/tws/TWA/TWS/applicationJobPlugIn/ and then start the Install.
If you do not perform this step in advance, the installation on the primary domain manager or backup primary domain manager *could* fails with the following errors in the Installation logs file:
chmod: cannot access '/opt/IBM/tws/TWA/TWS/applicationJobPlugIn/*': No such file or directory
The following command failed: chmod go-w /opt/IBM/tws/TWA/TWS/applicationJobPlugIn/*
If you see these error/s, then perform the following steps:- Create the dummy file
- Find . -name "*.statusStep" from maestrohome directory folder and sub-folders and delete them
- Restart the installation
- Windows System Requirements for 9.4 Fix Pack 7
- Windows Job PlugIns failure -APAR IJ30656 On *Windows* only
TWS 9.4 FP7 plug-ins jobs could fail if Visual C++ Redistributable for Visual Studio 2015 package is not installed on the machine, with: (examples) into Joblog: AWSITA039E Cannot find the executor for application "cognos". AWSITA039E Cannot find the executor for application "restful".
Workaround:Install: “Visual C++ Redistributable for Visual Studio 2015†package from here:https://www.microsoft.com/en-us/download/details.aspx?id=48145. See the following technote for additional troubleshooting information: https://www.ibm.com/support/pages/node/6410892.
- A new home for Workload Automation plug-ins
- Automation Hub is a new concept for automating business workflows.
In previous versions, all job plug-ins were provided with the product and obtaining new plug-ins meant you were bound to the product releases.
- A new way to automate your business workflows and a more flexible solution to having only the integrations of your interest integrated in the product.
- If you do not find the integration that you are looking for, you can make a request for it or, you can create it yourself. To create a new integration, you can use the Workload Automation, Lutist Development Kit, and then share your integration with the community.
- Updated version of Installation Manager (IM)
- Fix Pack 7 has been tested using IM 1.9
- IBM SDK for Java
- Fix Pack 7 has been updated with Java 8.0.6.15
- Updated CIT only for Linux platforms
- On Linux, Fix Pack 7 has been updated with CIT 9.2.19
- Updated version of WebSphere Application Server (WAS)
- Fix Pack 7 has been tested using WAS 8.5.5.18
- Updated version of JazzSM
- Fix Pack 7 has been tested using JazzSM 1.1.3 Fix Pack 8
- New DB2 version supported
- Fix Pack 7 has been tested using DB2 11.5 Advanced Workgroup Server Edition (only update installation)
- New OS supported
- RHEL 8 (only Fault Tolerant Agent and Dynamic Agent)
- Updated OpenSSL libraries
- IBM Workload Scheduler Version 9.4 Fix Pack 7 has been updated with OpenSSL version 1.1.1g. IBM Workload Scheduler includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).
- Resolved Common Vulnerabilities and Exposures (CVE)
-
The following CVEs have been resolved with this Fix Pack
- CVE-2012-6708
- CVE-2015-8861
- CVE-2015-9251
- CVE-2016-7103
- CVE-2018-12086
- CVE-2018-14439
- CVE-2018-14718
- CVE-2018-14719
- CVE-2018-14720
- CVE-2018-14721
- CVE-2018-19360
- CVE-2018-19361
- CVE-2018-19362
- CVE-2019-10202
- CVE-2019-11358
- CVE-2019-14379
- CVE-2019-14540
- CVE-2019-14892
- CVE-2019-14893
- CVE-2019-16335
- CVE-2019-16942
- CVE-2019-16943
- CVE-2019-17267
- CVE-2019-17531
- CVE-2019-17571
- CVE-2019-17639
- CVE-2019-19919
- CVE-2019-20330
- CVE-2020-10672
- CVE-2020-10673
- CVE-2020-10968
- CVE-2020-10969
- CVE-2020-11022
- CVE-2020-11023
- CVE-2020-11111
- CVE-2020-11112
- CVE-2020-11113
- CVE-2020-11619
- CVE-2020-11620
- CVE-2020-11979
- CVE-2020-14060
- CVE-2020-14061
- CVE-2020-14062
- CVE-2020-14195
- CVE-2020-14556
- CVE-2020-14577
- CVE-2020-14578
- CVE-2020-14579
- CVE-2020-14581
- CVE-2020-14583
- CVE-2020-14593
- CVE-2020-14621
- CVE-2020-1968
- CVE-2020-2590
- CVE-2020-2601
- CVE-2020-2754
- CVE-2020-2755
- CVE-2020-2756
- CVE-2020-2757
- CVE-2020-2781
- CVE-2020-2800
- CVE-2020-2830
- CVE-2020-4329
- CVE-2020-7656
- CVE-2020-8840
- CVE-2020-9546
- CVE-2020-9547
- CVE-2020-9548
- WS-2014-0034
- WS-2014-0034
- WS-2018-0021
- WS-2019-0064
- WS-2019-0103
- WS-2019-0331
- WS-2019-0332
- The term $SLAVES was removed from the security file and replaced with the term $AGENTS
- Because it is politically incorrect, the term $SLAVES, which applies to all fault-tolerant agents in both the classic and role-based security models, was replaced with the term $AGENTS with the same scope. No change is required to your existing scripts nor environments. For more information, see Configuring user authorization (Security file).
- Satisfying Requests for Enhancements (RFEs)
-
Requests for Enhancements (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.
- RFE WA-87790
- After the first failed attempt to find an available resource, the job FAILS. To enable this new behavior, add the hidden property, Broker.Workstation.Enable.RerunOnAllocFailure, to the BrokerWorkstation.properties file and set the property to "false". By default, the value of this property is "true".
- RFE 143162: Prevent job streams from completing in error when the start condition is not met
- The following new optman option has been added : enStartCondSuccOnDeadline| od You can now prevent job streams from completing in error when the start condition is not met. By Specifying the behavior of the job stream when the start condition is not met and the Start once option is not selected. If you set the option to yes, when the deadline for the start condition is met, the monitoring job is confirmed in Successful status and the job stream is canceled. If you set the option to no, the monitoring job is killed, so both the monitoring job and the job stream change to Error status. The default value is yes in a fresh installation and no in upgrade to maintain compatibility with previous versions. Run JnextPlan to make this change effective.
- RFE 143196: Possibility to select object to be imported during a WAT import
- On wappman you can select the objects to be imported while creating a workload application template and skip unwanted objects. For more information, see Deploying a workload application and wappman.
Serviceability
- WA-88054
- da_test_connection
Run the da_test_connection utility on a dynamic agent to check the connection to a dynamic workload broker or on a dynamic workload broker to check the connection to a dynamic agent.
Syntax- On UNIX operating systems
- da_test_connection.shHOSTNAME[PORT [IS_DA]]
- On Windows operating systems
- da_test_connection.batHOSTNAME[PORT [IS_DA]]
- HOSTNAME
- Specify the hostname of the agent or dynamic workload broker to be checked.
- PORT
- Optionally specify the port on which the connection is to be checked. the default value varies depending on value you specify for the IS_DA parameter:
- IS_DA=TRUE
- In this case the check is performed on the dynamic agent with the specified hostname and the default value of the PORT parameter is 31114.
- IS_DA=FALSE
- In this case the check is performed on the dynamic workload broker with the specified hostname and the default value of the PORT parameter is 31116.
- IS_DA
- Specify whether the workstation whose connection you want to check is a dynamic agent or dynamic workload broker. Use one of the following values:
- TRUE
- Specify TRUE if you want to check the connection of the dynamic agent with the specified hostname. This is the default value.
- FALSE
- Specify FALSE if you want to check the connection of the dynamic workload broker with the specified hostname.
To check the connection for the dynamic agent with IP address 10.18.66.40, run the following command:
da_test_connection.sh 10.18.66.40 31114 TRUE
To check the connection for the dynamic workload broker with hostname
10.18.66.40, run the following command:
da_test_connection.sh 10.14.36.36 31116 FALSE
- WA-88045
- The tracing default level of the Dynamic Agent has increased, and the number of JobManager trace files has increased to 5 - their default size is 10 Mb
- WA-88257
-
Fix Pack 7 has been updated with an improved Windows Data Gather tool.
- WA-88262
- A warning message is issued when makesec command is running with role based security is enabled.
Features introduced with Fix Pack 6
The following new product features, enhancements, and changes are introduced with this Fix Pack:
- MVS package will be shipped with this Fix Pack
- The package will contain the z/OS gateway
- Requirements 121199 and 121197 implementation
- Filemonitor utility now accept global expressions and timeout keyword with hh:mm:ss format.
- Extend the AS400 jobs user interface to allow LDA specification
- On the Dynamic Workload Console, a new field has been added. From this new file, you can specify the Local Data Area (LDA) source to be passed to the AS400 job.
- Cognos support 11.0.13.1
- Fix Pack 6 has been tested using Cognos Analytics 11.0.13. The scenarios already certified with Cognos 10.2.0.1 have successfully ran using Cognos Analytics 11.0.13
- Updated OpenSSL libraries IBM Workload Scheduler has been updated with OpenSSL
- - OpenSSL 1.0.2r 26 February 2019 (1.0.2.18)
- Updated version of WebSphere Application Server (WAS)
- Fix Pack 6 has been tested using WAS 8.5.5.15
- New OS supported
- Windows 2019 (only agent), SLES 15 (only agent)
- Updated version of GSKIT
-
Fix Pack 6 has been updated with GSKIT version 8.0.55.6.
- IBM SDK for Java
-
Fix Pack 6 has been updated with Java version 8.0.5.35.
- Resolved Common Vulnerabilities and Exposures (CVE)
-
The following CVEs have been resolved with this Fix Pack
- CVE-2018-3180
- CVE-2018-5407
- CVE-2019-4031
- CVE-2019-1559
- CVE-2018-1890
- CVE-2018-2426
- CVE-2018-12547
- CVE-2018-2426
- CVE-2018-12547
- CVE-2018-1926
- Updated version of Informatica
- Fix Pack 6 has been tested using Informatica 10.1.1. The scenarios already certified with Informatica 9.x have ran successfully.
Features introduced with Fix Pack 5
The following new product features, enhancements (RFE), and changes are introduced with this Fix Pack:
- Updated version of Installation Manager (IM)
- Fix Pack 5 has been tested using IM 1.8.9
- Updated version of WebSphere Application Server (WAS)
- Fix Pack 5 has been tested using WAS version 8.5.5.14
- Dynamic Agent Docker Image Refresh now available: 9.4.0-IBM-IWS-DOCKER_X86_64_AGENT-FP0005
-
The Docker image for dynamic agents originally made available with IBM Workload Scheduler Version 9.4 Fix Pack 1 has now been refreshed with this fix pack and can be downloaded from IBM Fix Central. For information about preparing and installing the Docker image see the samples provided on GitHub: https://github.com/WAdev0/agent-docker-kit.
For a detailed video about this feature, see the https://www.youtube.com/watch?v=x9pETvgoE7Q&t=video available on the Workload Automation YouTube channel.
- Dynamic Agent ISERIES - ABLE TO MANAGE CHILDS AND NOCHILDS in case of SBMJOB command
-
The following limitation been removed:
The SBMJOB system command, when submitted, always starts a batch job. Do not try to exclude the job monitoring, because if the IBM i agent finds the SBMJOB command in the job definition , it removes and ignores the :CHILDS or :NOCHILDS ending token in the job definition and also ignores the setting of the TWS_NOCHILDS system variable has been removed and now the options can be used in case of SBMJOB.
Now the :CHILDS and :NOCHILDS Options can be used in case of SBMJOB
- Resolved Common Vulnerabilities and Exposures (CVE)
-
The following CVEs have been resolved with this Fix Pack:
- CVE-2018-1656
- CVE-2018-12539
- CVE-2018-1517
- CVE-2018-2973
- CVE-2018-0732
- CVE-2016-0702
- CVE-2018-1426
- CVE-2018-1427
- CVE-2018-1428
- CVE-2017-3736
- CVE-2017-3732
- CVE-2016-0705
- CIT
-
Fix Pack 5 has been updated with CIT version 2.8.0.8000
- Updated version of GSKIT
-
Fix Pack 5 has been updated with GSKIT version 8.0.55.2.
- Updated OpenSSL libraries
-
IBM Workload Scheduler has been updated with OpenSSL version 1.0.2q.
- IBM SDK for Java
-
Fix Pack 5 has been updated with Java version 8.0.5.20.
Features introduced with Fix Pack 4
The following new product features, enhancements (RFE), and changes are introduced with this Fix Pack:
- DevOps made easier with workload applications
-
If you have a few use cases where the workload application templates replicated in your workload environment are a little too rigid, then this new enhancement will add the flexibility you are looking for.
After a workload application is exported into a workload environment, the contents such as, job streams, jobs, and other objects, are created in the environment and an association to the workload application is maintained. This allows for easy subsequent updates and synchronization between the workload application template exported from the source environment and the workload application in the target environment. The workload application can be easily replaced and updated. However, there might be certain circumstances where you prefer not to have an association to the workload application so that the imported objects can be freely updated or deleted.
When importing a workload application template, you can now specify whether you prefer to import only the objects contained in the template, without any ties to the workload application, or to import the objects maintaining their association to the workload application. Even after you have imported the contents of a workload application template into a target environment, removing the association to the original workload application template, you still have some options through the wappman command line that enable you to manage the objects as a whole, such as deleting all of the objects or replacing all of the objects.
These workload application template enhancements are supported when connected to an engine with version 9.4.0.4 or later.
For details about importing a workload application template, see Importing a workload application template. For information about the new options available for wappman see https://www.ibm.com/support/knowledgecenter/en/SSGSPN_9.4.0/com.ibm.tivoli.itws.doc_9.4/distr/src_ref/awsrgwkldappcmd.htm.
- Additional support for agents
- Support for fault-tolerant agents, dynamic agents, and z/OS agents has been extended on Sun Solaris SPARC 64-bit.
- Automatically register agents to pools
-
Starting from version 9.4 Fix Pack 4, you can automatically register dynamic agents in pools by editing a file.
Starting from version 9.4 Fix Pack 1, you can automatically register dynamic agents in pools by editing the pools.properties file located in <TWS_home>/ITA/cpa/config.
The file is composed by a series of lines with a list of pools to which the agent will be automatically registered. To make the changes in this file effective on the agent, you must stop and start the agent.
Because an agent can encounter problems and is not able to register and go online, for example, if it does not find a pool defined in the system, there are options that can be used in the pools.properties file to allow the agent to go online even if some pools are not defined.
This alternative way of registering dynamic agents to a pool can be useful when you need to quickly add more than one agent to a pool, or when you want to associate multiple pools to a dynamic agent.
- Satisfying Requests for Enhancements (RFEs)
-
Requests for Enhancements (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 V9.4 Fix Pack 4 delivers the following RFE:
- RFE 117399: Windows 2016 WSCF cluster support
- Support has been extended to Microsoft Windows Server 2016 Failover Clustering (WSCF) on agents.
To view a complete list of RFEs, new, planned, and delivered, see: RFE online community .
- Option to determine when fileCreated event is sent
- The -modificationCompletedTime option can optionally be specified with the -event fileCreated argument to determine when the fileCreated event is sent. The filemonitor utility is used to check for changes in files (files that are either created or modified). You can now specify the -modificationCompletedTime <seconds> option with the -event fileCreated argument to determine when the fileCreated event is sent. This option is optional and when specified, if a file is created, the event is not sent immediately, but only after the interval of time specified by -modificationCompletedTime<seconds> has elapsed, and during which no subsequent changes were made to the file, which includes the file being deleted and recreated with the same name.
- Managing pools and agent connectivity
-
Starting from IBM Workload Scheduler version 9.4 Fix Pack 4, you can automatically register dynamic agentsin pools by editing a file.
Starting from version 9.4 Fix Pack 1, you can automatically register dynamic agents in pools by editing the pools.properties file located in <TWS_home>/ITA/cpa/config.
The file is composed by a series of lines with a list of pools to which the agent will be automatically registered. To make the changes in this file effective on the agent, you must stop and start the agent.
Because an agent can encounter problems and is not able to register and go online, for example, if it does not find a pool defined in the system, there are options that can be used in the pools.properties file to allow the agent to go online even if some pools are not defined.
This alternative way of registering dynamic agents to a pool can be useful when you need to quickly add more than one agent to a pool, or when you want to associate multiple pools to a dynamic agent.
- New options added to pool.properties
- Two new options, ;optional and ;skip, have been added to the pool.properties file to manage situations where a dynamic agent is unable to link to the master domain manager. The ;optional option discards problematic pools allowing the agent to go online. The ;skip option can be used to maintain a pool in the list of pools, but avoid it being used.
- Updated version of GSKIT
-
Fix Pack 4 has been updated with GSKIT version 8.0.50.88.
- Updated OpenSSL libraries
-
IBM Workload Scheduler has been updated with OpenSSL version 1.0.2o.
- IBM SDK for Java
- Fix Pack 4 has been updated with Java version 8.0.5.10/8.0.5.11, depending on the platform.
Features introduced with Fix Pack 3
The following new product features, enhancements (RFE), and changes are introduced with this Fix Pack:
- Modifying job instances in the plan (RFE 89523)
-
Modify a job instance in the plan before it runs or modify an instance of a job in the plan that has already run and rerun the modified job.
You can modify a job definition in the database whenever and as many times as you want. However, there are times when you need to make changes to the job definition, but it has already been submitted into the plan and runs as is. This results in extra work and lost time in updating the definition in the database and then getting it into the plan to run.
This feature adds the flexibility you need so that you can now make changes to the definition even after it has already been submitted into the plan, maintaining the original definition in the database. With this additional flexibility, you can edit the job definition on-the-fly before it runs or rerun a job with a different definition. This can be done from either the Job Stream Graphical View, the job monitoring view, or from the conman command line.
Maybe you want to substitute the command or script executed by the job with a different one? Maybe you just need to tweak an argument? Maybe you need to rerun a job updating the logon name, priority, or connection server? Whatever the change, this enhancement allows you to quickly react and avoid possible disasters, and increase your productivity by addressing additional scenarios in your workload that were not contemplated at the time you modeled or planned your workload.
For details about how to modify the job definition in the plan using the conman command line, see the commands Altjob and Rerun.
See the video: New opportunities to react and recover on the Workload Automation YouTube channel.
- Easy installation for patches on agents
-
You can now easily install patches on agents using the twsinst command with the -patch option.
- Enhancements to IBM i job monitoring and control (RFE 114590)
-
Monitoring and control facilities for IBM® i jobs have been enhanced to simplify the management of IBM i inquiry messages.
- Automated reply to inquiry messages
-
For the most frequent IBM i inquiry messages, you can define standard rules to automate the reply to the waiting messages. When defining an IBM i job, by using the Workload Designer of the Dynamic Workload Console or the composer command line, you can specify the list of messages for which you want to set up an automated reply. When specifying the automated replies, a new parameter has been added to the job definition: the Message Max Replies parameter. It represents the maximum number of automated replies accepted for a specific message. This new parameter optimizes the management of IBM i inquiry messages.
- Reliable monitoring of IBM i job status changes
-
As an inquiry message receives an automated reply, the IBM i job status changes from SUSP (suspended) to EXEC (executing) and vice versa. All the job status changes are monitored and tracked. This is useful, for example, when you want to create an event rule definition to send an email every time a job status change occurs.
- Improved trace facilities
- Trace facilities for IBM i jobs have been improved. To specify the desired tracking level, customize your IBM i agent by setting the required parameters in the JobManager.ini file, in accordance with the settings on the IBM i system.
For more information, see Scheduling and monitoring jobs on IBM i systems. See the video Simplify workload management for your IBM i Systems.
- New Plug-ins for Cloud Automation
-
Amazon EC2, IBM SoftLayer®, and Microsoft Azure plug-ins are available to manage the provisioning and de-provisioning of virtual machines in the cloud, on as-needed basis.
Customers choose to move their application to the cloud to focus on business optimization. Once in the cloud, applications rely on systems provisioned and de-provisioned to run defined business workflows but unpredictable workload volumes. Customers face a new question: Is it better to over-provision cloud resources with the risk of wasting them, or under-provision with the risk of degrading performance and delay the business process?
How about provisioning just the right amount of resources for only the time-period you need them? Exactly what you need, when you need it, and rather than incur extra costs and waste, de-provision when you’re done, all automatically.
To succeed in this challenge, a new approach is required, that strictly ties business workflows with cloud resource management. While managing a business application, IT organizations need to be able to orchestrate provisioning and de-provisioning of the infrastructure needed by the business application in the cloud.
IBM Workload Scheduler provides three Cloud Automation plug-ins, for different cloud providers, to manage the provisioning and de-provisioning of virtual machines in the cloud, on as-needed basis. By orchestrating the application workflow and the workflow that manages the entire lifecycle of the virtual machines needed by the applications (including the actions: start, stop, snapshot, etc…), IBM Workload Scheduler can increase both business and infrastructure agility. The plug-ins are:
- Plug-in for Amazon Web Services (EC2)
- Plug-in for IBM SoftLayer
- Plug-in for Microsoft Azure
Select your cloud provider, and add one or more jobs in the job stream that automates your business process flow to provide a flexible and dynamic allocation of cloud resources to your workload.
For more information about the Cloud Automation plug-ins, see Scheduling Applications with IBM Workload Automation.
See the video: Workload Scheduler for Cloud Automation on the Workload Automation YouTube channel. More videos are available for the features released with V9.4 Fix Pack 3 on this dedicated playlist: Workload Scheduler V9.4, Fix Pack 3.
- Apache Spark Plug-in
-
With the new IBM Workload Scheduler plug-in for Apache Spark, you can schedule, monitor and control Apache Spark jobs.
Apache Spark a lightning-fast cluster computing technology, designed for fast computation. It is based on Hadoop Map Reduce and extends the MapReduce model to efficiently use it for more types of computations, which includes interactive queries and stream processing. The main feature of Apache Spark is its in-memory cluster computing that increases the processing speed of an application. IBM Workload Scheduler provides a plug-in for Apache Spark that helps you manage your big data processing and analytics. With the plug-in for Apache Spark, you can define, schedule, monitor, and control Apache Spark jobs. Add one or more Apache Spark jobs in the job stream that automates your business process flow to obtain an end-to-end workload management solution.
For details, see Scheduling Applications with IBM Workload Automation.
- Restarting JSR 352 Javaâ„¢ Batch jobs from the point of failure (RFE 110252)
-
You can restart JSR 352 Java Batch jobs from the point of failure.
During the execution of a JSR 352 Java Batch job, when monitoring the job from the Dynamic Workload Console
- More flexibility in managing successors for job actions
-
You can now hold, release and rerun the successors during your job monitoring.
You have a list of all successors for the selected job, view the successors in two separate tables and decide if you want to run all internal successors, all internal and external successors, or a subset of them. By default, all successors are selected. By selecting the mode you can also control how successors are selected: manually, including successors in the same job stream or including successors in other job streams.
For more information about how to rerun successors from the command line, see the listsucc and rerunsucc commands.
- Updated version of WebSphere Application Server (WAS)
-
Fix Pack 3 has been tested using WAS version 8.5.5.13
- Updated OpenSSL libraries
-
IBM Workload Scheduler has been updated with OpenSSL version 1.0.2l.
- Resolved Common Vulnerabilities and Exposures (CVE)
- The following CVEs have been resolved with this Fix Pack:
- CVE-2017-15095
- CVE-2017-7525
- CVE-2017-17485
- Additional support for agents
- Support for Oracle Enterprise Linux version 6.x has been extended to fault-tolerant agents, dynamic agents, and z/OS agents.
Features introduced with Fix Pack 2
The following new product features, enhancements, and changes are introduced with this Fix Pack:
- Support for updated versions of WebSphere Application Server (WAS)
- Fix Pack 2 has been tested using WAS version 8.5.5.12
- Support for updated versions of Dashboard Application Services Hub (DASH)
- Fix Pack 2 has been tested using DASH version 3.1.3.0 CP4
- Support for updated versions of JazzSM
- Fix Pack 2 has been tested using Jazz version 1.1.3
- Rollback procedure
-
Roll back a master domain manager to a previous Fix Pack level or release if the master domain manager was installed with IBM Installation Manager.
To roll back a master domain manager to a previous Fix Pack level or release, you first need to create a backup before installing the new Fix Pack or release. This allows you to then perform a rollback procedure after the Fix Pack or release has been installed.
The roll back procedure is supported starting with Version 9.3 Fix Pack 3.
- Mixed pricing models
-
Easily define different pricing models on workstations in your environment.
According to your IBM Workload Scheduler license, IBM® License Metric Tool helps you maintain your license compliance. By using License Metric Tool, you can generate reports that summarize your license consumption. The generated reports are maintained on the License Metric Tool server and should be periodically reviewed and signed, creating a history for audit purposes in the process. If you are contacted by a third-party software compliance auditor who plans to visit your enterprise to carry out a software audit, ensure that all reports are up-to-date and signed, and then supply copies of reports that cover the time periods that the auditor requests.
You can now take advantage of improved flexibility when defining your pricing model. For each single workstation in your environment, you can define the pricing model to be applied.
When you set the licenseType keyword to by Workstation in optman, you can define for each single workstation the pricing model to be applied to it at the workstation creation time.
The following are requests for enhancements (RFEs) introduced in Fix Pack 2:
- RFE 179819: Database job executor handles stored procedure errors
- Enhance the database job executor to handle stored procedure errors.
- RFE 15616: Actual workstation displayed when monitoring jobs
-
The name of the workstation where a job, scheduled to run on a pool or dynamic pool, actually ran.
When jobs are scheduled to run on pools or dynamic pools, you might want to monitor the job or the workstation where the job ran. Previously, this information was available only in the job log. With this enhancement, the name of the actual workstation where the job ran is also available in a new column in the monitor job query. This detail is available if the job has started or has already run. This information can also be output in reports.
This information can also be useful when you need to determine your license consumption and therefore need to know on which workstation in the pool the job actually ran.
For details about the actual workstation see the columns that can be defined when monitoring jobs in the Dynamic Workload Console. The runtime information contained in the conman showjobs command also contains this information.
- RFE 108425: File monitor support for already created files
- Normally the filemonitor utility runs an initial scan and then runs subsequent scans to detect any new or changed files since the initial scan that match specific criteria. This means that if there are any existing files matching the criteria when the initial scan runs, they are not considered. The utility has been updated with a new parameter to be able to discover existing files during the initial scan that match the criteria and can therefore generate an event. For more information see the -generateEventsOnFirstScan argument for the Filemonitor command.
- RFE 111032: Need ability for File monitor in IWS z/OS to detect file existence on UNC path
- Use the filemonitor utility to check for changes of files (files that were either created or modified). This could be useful when, for example, you want to make sure that a file exists before running a job that processes that file. By defining a job that runs the filemonitor utility, you can implement file dependency, that is, a relationship between a file and an operation in which specific activity on the file determines the starting of the operation.
- RFE 106345: RUN PJP and PVU License Networks in the SAME Network
- Easily define different pricing models on workstations in your environment
- The online product documentation: https://www.ibm.com/support/knowledgecenter/en/SSGSPN_9.4.0/com.ibm.tivoli.itws.doc_9.4/common/src_gi/eqqg1sumenh.htm
- The Workload Automation portfolio What's New page at: https://start.wa.ibmserviceengage.com/ibm/TWSSandbox/wa/wa_whatisnew_v2.jsp.
- Helpful videos demonstrating new features for Workload Automation on the IBM Workload Automation Wiki Media Gallery.
Features introduced with Fix Pack 1
- Job Management Plug-in
-
The new Job Management plug-in is available in the Automation Utilities plug-in category. Automation Utilities are plug-ins that facilitate specific IBM Workload Scheduler operations. Use the Job Management plug-in, to run one of the following actions on any job in the job stream where the Job Management job is running:
Table 1. Actions that you can run on a job - Rerun
- Rerun the job and all its successor jobs
- Rerun the job and its successor jobs in the same job stream
- Release
- Release Dependencies
- Cancel
- Cancel Pending
- Hold
- Kill
- Confirm ABEND
- Confirm SUCC
The Job Management plug-in simplifies recovery scenarios and enables the automation of iterative workflows.
For more information, see Job Management jobs.
- Automation of Iterative Workflows
-
For complex workflows, the iteration of a sequence of jobs within the overall orchestration can be a challenging task. By selecting the option to rerun a job with all its successors jobs in the same job stream, the Job Management plug-in enables iterative processing of a sequence of jobs while a condition is met. It is like a DO WHILE statement in programming languages.
It is just a matter of adding a Job Management job at the end of the sequence of jobs that you want to iterate. The Job Management job requests to rerun the first job in the sequence along with its successor jobs. The iteration is controlled by the output conditions of the first job in the sequence: it stops when the condition is no longer satisfied.
For more information, see Job Management jobs.
- Advanced rerun flexibility
-
The new advanced rerun options help you orchestrate your workflows seamlessly, building recovery logic into the job definition itself and rerunning job successors directly from the Monitor Workload view.
When you create a job definition, you can now specify that you want the job to rerun for a specific number of times and after a specific interval, in case of failure. This ensures that fewer alerts are generated and the workflow continues smoothly. For example, if you have a job that needs to connect to a server which is periodically restarted, you can specify in the job definition that you want the job to rerun for a specific number of times and after a specified interval.
If the parent job ran on a workstation that is part of a pool or a dynamic pool, you can decide whether it must rerun on the same workstation or on a different one. This is because the workload on pools and dynamic pools is assigned dynamically based on a number of criteria and the job might be rerun on a different workstation.
Also, if a job fails, you can identify all its successors at a glance and decide whether you want to rerun the job with its successors. You can rerun either all successors in the same job stream, or all successors overall, both in the same job stream and in other job streams, if any.
For more information about how to specify the rerun options in the job definition from the command line, see Defining job rerun and recovery actions and Controlling job and jo stream processing.
For more information about how to rerun successors from the command line, see the listsucc and rerunsucc commands.
Use the Job Management plug-in to further automate your workflows. With the plug-in, you can perform a number of actions on jobs, such as rerun the job, with or without its successors, release its dependencies, or cancel the job, and many more. For example, in a recovery scenario, you can insert a Job Management job in your workflow. This causes the original job to rerun automatically when the relevant recovery job completes successfully, reducing effort and time consumption.
- Job Stream Submission Plug-in
-
The new Job Stream Submission plug-in is available in the Automation Utilities plug-in category. Automation Utilities are plug-ins that facilitate specific IBM Workload Scheduler operations. Use the Job Stream Submission plug-in to submit a job stream for processing.
By adding the Job Stream Submission plug-in to your workflow, you can automate the submission of a specific job stream, minimizing code scripts and manual effort. Also, you can specify the earliest start time for the job stream and define the variable table associated to the job stream.
For more information, see Job Stream Submission jobs.
- Condition-based workload automation
-
Condition-based workload automation provides a simple and immediate way to have your workflows start at just the right time. You can define in your job stream a condition that, when met, releases the job stream to run as scheduled.
For example, if you have a job stream containing jobs which analyze one or more files, you can have the job stream start only after the file or files have been modified or created. Also, if the job stream contains jobs which process the data in a database, you might want to have the job stream start after enough rows have been written into the database. You can also have IBM Workload Scheduler check repeatedly whether the condition is met.
You can start your workflow based on one of the following conditions:- One or more files being created
- One or more files being modified
- A job completing with its output condition satisfied. You can apply this logic to the job stream or to specific jobs in the job stream.
For more information, see Condition-based workflow automation.
- Monitor file changes using the filemonitor utility
-
Use the filemonitor utility to check for changes of files (files that were either created or modified). This could be useful when, for example, you want to make sure that a file exists before running a job that processes that file. By defining a job that runs the filemonitor utility, you can implement file dependency, that is, a relationship between a file and an operation in which specific activity on the file determines the starting of the operation.
You can use the filemonitor utility as a stand-alone command, or you can set the filemonitor keywords as additional parameters for the start condition of a job stream, either in the Workload Designer or from the composer command line. For more information about the start condition, see Condition-based workflow automation.
For more information, see Filemonitor.
- New keyword for defining the latest start time in job streams
-
The jsuntil keyword defines the latest start time of a job stream. It also determines the behavior of the jobs in the job stream when the job stream is approaching its latest start time. Use the jsuntil keyword to avoid that the job stream is either suppressed, canceled, or set to continue (depending on the action specified in the onuntil keyword) if it starts before its latest start time. For example, if you have a job stream with jsuntil set to 10:00 am, and one of the jobs starts running at 9:59 am, the job and its successors run as scheduled.
This keyword is mutually exclusive with the until keyword.
There is also a major difference with between the until and jsuntil keywords:- If you specify the until keyword in your job stream definition
- This keyword is evaluated also after the job stream has started. As a result, if the latest start time expires before the job stream completes successfully, the action specified in the related onuntil keyword is performed on the job stream and on its jobs, which have not yet started.
- If you specify the jsuntil keyword in your job stream definition
- This keyword is evaluated only once, as soon as all dependencies of the job stream are satisfied and the job stream state changes to READY. If the latest start time defined using the jsuntil keyword has not expired at this time, it is no longer evaluated and the job stream runs independently of it. However, to prevent the job stream from remaining in READY state indefinitely, two days after the time specified in the jsuntil keyword has expired, the job stream is suppressed by default.
For more information, see jsuntil.
- New keyword for defining actions on late jobs
-
The onlate keyword defines the action to be taken on a job in job stream when the job's deadline expires. If the job is running when the deadline expires, it is killed. Killed jobs end in the ABEND state. Any jobs or job streams that are dependent on a killed job are not released. If the dependency on the job is a conditional dependency on the job completing in ABEND state, that dependency is released.
For more information, see onlate.
- Preparing and installing a Docker image for dynamic agents
-
A Docker container automates the task of installing a running dynamic agent, along with everything that is required to run it: code, runtime, system tools, system libraries, and settings.
It provides a mechanism known as a Dockerfile, which is used to codify the steps to install and configure your dynamic agent. This is a plain text file that uses a standard set of commands to perform the all the installation and configuration steps. The resulting Docker image is a static image of the full set of software for the dynamic agent with the exact configuration.
An image is then built to become a Docker Container, which is a unique running instance of the software with its own processes, state, and configuration. You can start as many Docker Containers from a given image as necessary. This gives you the possibility to quickly provision multiple running instances of your software, each with their own processes, state, and configuration, quickly and easily.
For more information, see Creating a Docker image to run dynamic agents.
For a detailed video about this feature, see the Docker Agent for Workload Scheduler video available on the IBM Workload Automation Wiki Media Gallery.
- New options in managing workload applications
- The following new options are available:
- Export a job stream definition as a workload application template
- From the Workload Designer, you can export a job stream definition and save it as a workload application template in a compressed file. The job stream definition can then be imported in another environment.
For more information, see Exporting a job stream definition as a workload application template.
- Rename a workload application during the import process
- A new parameter -workloadApplicationName <workload_application_name> is available for the wappman -import command to rename the workload application during the import process.
For more information, see wappman.
- Modify the mapping file according to rules defined using regular expressions
- You can optionally request that the mapping file produced by the export process is automatically modified by the import process, according to rules defined using regular expressions and specified in ad-hoc files. For more information, see Using regular expressions to modify the mapping file.
- Integration with IBM UrbanCode Deploy
-
Workload applications can be created and then exported so that they can be imported in other IBM Workload Scheduler environments.
To export and import a workload application you can use either the Dynamic Workload Console or the wappman command line.
In alternative to the import process, you can automate the deployment of an application from one environment to another by using the Workload Automation plug-in of the IBM UrbanCode Deploy tool. For details about this plug-in, see the IBM UrbanCode Deploy documentation.
For a comprehensive library of videos about the new features for this release, see the Workload Scheduler version 9.4, Fix Pack 1 playlist available on the IBM Workload Automation Wiki Media Gallery.
- Upgrade from version 8.6
-
IBM Workload Scheduler V9.4 General Availability supported upgrades from V9.x. With this fix pack, support is being extended to V8.6.x instances.
For IBM Workload Scheduler V8.6.x instances, the upgrade is supported only for the primary domain manager using the parallel upgrade method. The direct upgrade is not supported for IBM Workload Scheduler V8.6.x instances. The only supported scenario for the upgrade of a V8.6.x primary domain manager is to install a new primary domain manager configured as a backup. All other components must be upgraded at version 9.3 first, or can optionally remain at 8.6 level. For more information see the Planning and Installation Guide..
- MSSQL database support extended on Linux
- Microsoft SQL Server Enterprise Edition database is now supported on Linux.
- Windows 2016 support
- Windows 2016 is supported on all components.
- RFE 17980
- Restart the job stream from the given job of a job stream. (Internal ID 57221)
- RFE 25295
- Rerun a specific job and all of it successors, both in the same job stream and in other job streams (see the Condition-based Workload Automation feature). (Internal ID 65671)
- RFE 33200
- Create external dependency from the graphical Plan View. (Internal ID 79752)
- RFE 44226
- Need a copy button on the Monitor Jobs panel EDIT JCL. (Internal ID 99136)
- RFE 46521
- Improve recovery options for a job. (Internal ID 103418)
- RFE 65873
- Changed behavior of selections in tables in the Dynamic Workload Console. When performing an action on a selected item in the table, either by right-clicking or from the toolbar, after the action is performed the selection is cleared so that you can perform a different action on a different selection. You can also multi-select items in a table and perform an action on all selected items. (Internal ID 125267)
- RFE 69212
- When rerunning a job in a pool, you can optionally rerun the job on the same workstation where it previously ran (see the Condition-based Workload Automation feature). (Internal ID 130343)
- RFE 78682
- Additional columns are now available when monitoring jobs on multiple engines. (Internal ID 144976)
- RFE 80759
- Hyperlinked properties when updated should auto-refresh automatically in Dynamic Workload Console. (Internal ID 146988 )
- RFE 101904
- Search option improvements in the Dynamic Workload Console Workload Designer allows for object selection before inputting keyword so that the search is run against the object selected. (Internal ID 172565)
- RFE 101905
- The search field in the Dynamic Workload Console Workload Designer now provides user assistance with examples of the syntax that can be used in the field. (Internal ID 172564)
- RFE 104082
- Dynamic Workload Console - Disable IE Compatibility View. (Internal ID 175746)
For more information about new features introduced with this fix pack, see Summary of enhancements.
Helpful videos demonstrating new features for IBM Workload Scheduler is available on Workload Automation YouTube channel.
Problems fixed in IBM Workload Scheduler Fix Pack 7 for version 9.4.0
This section lists APARs and internal defects solved by Fix Pack 7.
This Fix Pack includes a number of fixes for internal defects found by the verification team that mainly cover the following product capabilities:
APAR | ABSTRACT |
IJ02098 | FILE CREATE MONITOR EVENT RULE FAIL ON WINDOWS DA WHEN FILE PATHIS TOO LONG |
IJ06494 | RUNCYCLE GROUP WITHIN A JOBSTREAM IS NOT PICKING UP THE DEFAULT CALENDAR |
IJ09094 | TIME DELAYS WHEN WE USE CONMAN CLI - STREAM IOCTL TIMEOUT |
IJ09112 | CTRL-C CONSIDERED AS "YES" CHOICE IN CANCELLING JOB/JOB STREAMS |
IJ12616 | ERROR IN DISPLAYING JOBSTATUS IF MORE THAN ONE ENGINE IS SELECTED |
IJ13185 | WORKSTATION CLASS IS ALLOWED FOR WORKSTATION ARGUMENT IN "CONMAN SUBMIT SCHED". |
IJ13551 | MIRRORING DEFECT ON IWS/DWC 9.4.0 FP05. FOR JOB TRANSITIONS FENCE TO READY, THE STATUS IS NOT PROPERLY REFLECTED IN THE DWC |
IJ14395 | CARRYFORWARDED JOBSTREAMS IN HOLD STATE THAT WERE SUBMITTED WITH AN ALIAS MAY CAUSE A DB DEADLOCK WHEN PASSING TO READY STATE AN |
IJ15693 | AWSJCO198I IS DISPLAYED WHEN CPU LIMIT IS "SYSTEM" |
IJ16123 | CORRECTION FOR APAR IV98210 CAUSES SIGNIFICANT PLAN MIRRORING DELAYS WHEN A SPIKE OF MIRRORING GENERATED EVENTS OCCUR |
IJ16181 | JBXTRACT AND REP1 EXTRA CHAR CAUSES CORE DUMPS |
IJ16207 | GETTING AWSBDW031I MESSAGE WHEN RUNNING SAP JOB AFTER INSTALL |
IJ16731: | AWSJOM019E ON VIEW TASK FOR EVENT RULE WHEN FILTERING BY TIMERANGE IS NOT ALLOWED FOR FILTER "RULEINSTANCEFILTER.TIME_RAN |
IJ17162 | VIEWING PREDECESSOR INFORMATION IN THE PRODUCTION PLAN CAUSES WAS HANG |
IJ17285 | MULTIPLE FILEMONITOR CONNECTIONS TO DB COULD EXIT 0 IGNORING TIMEOUT SETTING |
IJ17317 | AFTER WAS UPDATE TO 8.5.5.14 WAS CRASH ON JOBSTREAMVIEW AND CONTINOUS REFRESH WHEN THE CUSTOMER HAS ABOUT MORE THAN 250 USER |
IJ17325 | PLANMAN CHECKSYNC CAN FAIL IF OPENS DEPENDENCIES IN THE DATABASE FROM PREVIOUS DAYS ARE INCORRECT |
IJ17387 | WORKLOAD AUTOMATION TEMPLATE IMPORT REPLACE FAILS WITH TWO SCHEDULES HAVING A NEW OBJECT CROSS REFERECED |
IJ17474 | DBCS PROMPT MESSAGE TEXT IS GARBLED ON DWC |
IJ17526 | IP VALIDATE ON HP PLATFORM |
IJ17690 | WHEN YOU RE-OPEN A JOB WITH SERVER:PORT THE PORT IS NOT SHOWN ON DWC |
IJ17820 | IWS 9.4.0 FP0006: "IBM WORKLOAD AUTOMATION API" SWAGGER UI IS BLANK |
IJ18008 | MAKEPLAN IS ASSEMBLING SOME JOB STREAM WITH JOIN OPTION ON THE CURRENT PLAN INCORRECTLY, WHILE THEY ENTER CORRECTLY IF ADDED BY DWC |
IJ18045 | THE BROKER ON THE DDM GETS UNLINKED (AND THE AGENTS WON'T BE LINKING TOO) AFTER THE STARTUP. |
IJ18206 | ALTER PASSWORD IN PLAN FAILS WHEN THE WORKSTATION IS NOT SPECIFIED IN THE USER DEFINITION |
IJ18246 | COMPOSER/DATAMIGRATE FAILS IF RUNCYCLE NAME IS LONG |
IJ18285 | SCHEDULE VERSION NOT CREATED IMPORTING WORKLOAD APPLICATION |
IJ18307 | JOB FAILS BATCHMAN MESSAGE"DATABASE FIELD EXCEEDS COLUMN BOUNDS" |
IJ18312 | CONMAN SJ/SS RETURNS ELAPSE TIME AS 00:60 INSTEAD OF 01:00, IF ACTUAL ELAPSE TIME IS BETWEEN 00:59:01 AND 00:59:59 |
IJ18482 | REST API CORRUPT AGENT POOL |
IJ18508 | CANNOT UPDATE THE LOCKED JOB STREAM WITH REST API |
IJ18697 | API /MODEL/JOBDEFINITION/HEADER/QUERY DOES NOT INCLUDE @OBJECT-COUNT" IN THE RESPONSE HEADER |
IJ18750 | WORKLOAD TEMPLATE MIGRATION 'KILL IF DEADLINE EXPIRES' CHECKED |
IJ18804 | MAILBOX.MSG CORRUPTION CAUSING MAILMAN FAILURE |
IJ19330 | USERS UTILITY NOT ALLOWING PERIOD (.) IN USERNAME |
IJ19735 | FILE SYSTEM EVENT RULES DOESN'T WORK |
IJ19766 | WEBSERVICE PLUG-IN FAILS DUE TO WEBSERVICE VERSION |
IJ20119 | WLB JOBS RUNNING TWICE IN MS-PROD |
IJ20428 | JOBS RUN TO SUCCESS ON POWERCENTER SIDE, BUT IWS STATUS IS ERROR |
IJ20834 | A PROBLEM IN THE SUBMISSION OF JOBSTREAM FROM EVENT RULE. |
IJ20952 | WAS IS CRASHING DUE TO A STACK FOUND IN JAVA STACK FRAMES IN LIBTWSPLANJNI.SO CREATED |
IJ21081 | COMPOSER REPLACE DOES NOT RETURN EXPECTED SYNTAX ERROR |
IJ21099 | A JOBSTREAM THAT IS IN WAITING FOR THE PREDECESSOR AND REACHES THE DEADLINE,CONTINUES TO RUN INDEFINETELY IF THE PREDECESSOR DOES END |
IJ21126 | SOMETIME SUBMITTED JOBSTREAMS CANNOT BE ADDED INTO THE PLAN OR REMAIN IN ADD STATE |
IJ21156 | ONLY ONE POOL MEMBER USED FOR FILE CHECK ACTIONS |
IJ21210 | UNISON_SCHED_IA DOES NOT HOLD THE DATE+TIME OF THE JOB ENTERED IN THE PLAN |
IJ21238 | DESCRIPTION OF UNISON_SCHED_IA IS NOT CORRECT |
IJ21346 | MIRRORING IMPROVEMENT FOR FILE DEPENDENCIES MANAGEMENT AFTER THE RESYNC OPERATION |
IJ21348 | MIRRORING IMPROVEMENT ON THE CANCEL OPERATION MANAGEMENT |
IJ21519 | TABLES IN PLN SCHEMA CARRYING OVER TOO MANY ROWS |
IJ21530 | TWS_ENV.SH SHOULD ADD SYSTEM PATHS AT THE END OF LIBRARY PATHS LOADED BY AN APPLICATION. |
IJ21592 | RESTART_STARTCOND ABENDS IF THE SAME JS NAME WITH FUTURE VALIDFROM IS REGISTERED |
IJ21596 | CROSS D/Z DEPENDENCY BEHAVIOR IN THE TIME WINDOW 01:00 - 02:00 |
IJ22162 | USING DWC 9.4.0.06 IT IS NOT POSSIBLE TO CHANGE PRIORITY FOR NEW JOB AFTER SUBMITTING A RERUN JOB |
IJ22165 | FM - WAS 8.5.5.13 HOLDING "DELETED" SPACE |
IJ22363 | COMPOSER VALIDATE RUNCYCLEGROUP DOESN'T WORK FOR 9.4 FIX PACK 5 |
IJ22431 | FAILS CHECK PREREQ CENTOS LINUX RELEASE 7.4.1708 (CORE) |
IJ22504 | MIRRORING - CANCEL JOB WITH RESOURCE DEPENDENCY GENERATES TOO MANY EVENTS IN SOME SPECIFIC CASES |
IJ22635 | JOBMAN CORE DUMP DURING OPENS FILE CHECK |
IJ22679 | RMSTDLIST SCRIPT MAY CAUSE THE REMOVAL OF SOME DIRECTORIES/FILES THAT CONATINS SPACES |
IJ22680 | CANNOT EDIT JOBD IN CURRENT PLAN IF JOBS ARE RESIDING INTO DAS |
IJ22904 | ADDING OR MODIFYING SECURITY DOMAINS CONTAINING JUST "EXCLUDE" FILTER IN COMMON, THEN THE FILTERS ARE REMOVED |
IJ22987 | JOBMANAGER ON WINDOWS HAS MEMORY LEAK WHEN FILE DEPENDENCIES HAVE TO BE RESOLVED ON DYNAMIC AGENT |
IJ23032 | FILE TRANSFER JOB USING SSL TO TRANSFER FILES IS LEAVING |
IJ23084 | JAVACORE IS GENERATED BY THE LIBTWSPLANJNI.SO |
IJ23360 | WAS IS CREATING CORE FILES. APPSERVMAN RESTARTS WITHOUT ISSUE AND NO APPARENT EFFECT ON FUNCTION |
IJ23393 | INSTALLATION PROCEDURE FOR AGENT ON IBMI DOES NEED TO BE REVIEWED FOR INSTALLATION ON SYSTEMS WITH NOT ENGLISH LOCALE |
IJ23518 | DDRIVEN ALWAYS SEND AN XML WITH <JMGR:RESOURCEGROUP> ITEM LIST GREATER THAN 0 EVEN WHEN NO CHANGES ARE PRESENT |
IJ23565 | DEADLOCKS OCCURING DUE TO PARALLEL CANCEL OF DIFFERENT INSTANCES OF THE SAME JOB STREAM WHEN JOBS HAVE OPENS DEPS |
IJ23755 | A WRONG FULLYQUALIFIEDNAME ON A DYNAMICAGENT COULD CAUSE OUTOFMEMORY ISSUES ON THE MASTER |
IJ23799 | INITIAL VERSION NOT SHOWN AFTER UPGRADING |
IJ23845 | OUTPUT CONDITIONS ARE NOT PROPERLY EVALUATED WHEN A DYNAMIC JOB IS KILLED ON DA |
IJ23925 | Update JRE for Oracle CPU jul 19, oct 19, jan 20. |
IJ23927: | MONMAN OCCASIONALLY CRASHES AT THE BEGINNING OF THE DAY WHEN IS GOING TO SWITCH ITS TRACE FILE, FROM THE OLD ONE TO THE NEW ONE |
IJ24063 | PLANBOX.MSG IS NOT A VALID CHOICE FOR THE WEB GUI EDITOR AND IS ALSO REJECTED IN THE XML VIA COMPOSER. |
IJ24075 | TWS MIRRORING ON OPENS WITH QUALIFIER CONTAINING A BACKSLASH |
IJ24130 | WAS ON MASTER OR BACKUP COULD SUFFER FROM A HANGUP CAUSED BY GETENGINEINFO |
IJ24193 | FAILED RERUN JOBS ARE AUTOMATICALLY RERUN (INDEFINITELY) EVEN IF THEY HAVE BEEN DEFINED AS RECOVERY STOP |
IJ24341 | RETRIEVE JOBLOG BEHAVIOR WHEN SET BEHINDFIREWALL ON FTA |
IJ24344 | ECHO $(("$TEMPF") DOES NOT WORK WHEN RUN VIA A JOB ON SOLARIS 11.4 |
IJ24617 | STEP 5 INTO "UPGRADING CLUSTER NODES MANUALLY" IS WRONG |
IJ24734 | DEADLOCK RECORDS ARE STORED DEADLOCK RECORDS ARE STORED INTO LOGS WHILE DELETING OLD PLAN FROM DATABASE |
IJ24741 | "GET STATEMENT" IN THE JOB DEFINITION RETRIEVES ONLY BODY NOT IN THE HEADER |
IJ24806 | CONMAN RERUN UTILITY IS TRIGGERING AN ADDITIONAL AN ADDITIONAL INSTANCE ON "REPEAT RANGE" JOBS / AT DEPENDENCIES REMOVING THE RERUN OPERATION |
IJ24854 | JOB STREAM WITH FDIGNORE KEYWORD ON ITS TOP OF RUNCYCLE WILL NOT BE ADDED TO THE PLAN |
IJ24876 | EVENTRULE GENERIC ACTION PLUG-IN "RUN COMMAND" IS GETTING FAILED WITH ERROR CODE "9009" ON WINDOWS |
IJ25063 | WHEN A REMOTE EXCEPTION IS THROWN FROM THE EJB, THE TWS JOB ENDS IN SUCC INSTEAD OF ENDING IN ERROR |
IJ25089 | WHILE USING RAPID7 NETWORK FIREWALL PROTECTION, WORKLOAD BROKER ABRUPTLY DISCONNECTS. |
IJ25131 | MIRRORING SCHEDULE STATUS DOES NOT REFLECT THE CORRECT STATE VERSUS THE JOB STATUS |
IJ25137 | OLD LOGS FILES BEING UPDATED AFTER FINAL IN 9.5 ENVIRONMENT |
IJ25267 | WAS DOES CRASH ON BMDM WHILE SUBMITTING A JS WITH A RECOVERY RUN |
IJ25450 | POWERCENTER JOBS APPEAR TO END ON POWERCENTER, BUT REMAINS IN EXEC ON IWS |
IJ25487 | BATCHMAN IS NOT CORRECTLY MANAGING THE ERROR AWSBHT018E WHEN A JOB IS MODIFIED ON THE FLY <TASK STRING OR LOGON USER HAS CHANGED |
IJ25488 | CHECKSYNC JOB ABEND |
IJ25679 | CONMAN FORMAT ERROR |
IJ25914 | SUCCESSOR JOB NOT RELEASED AFTER CONDITIONAL DEPENDENCY HAS BEEN MET ON DA WHILE FINAL IS RUNNING |
IJ26153 | 9.4.7 JOBS THAT ARE HELD IS SHOWING INCORRECT OUTPUT ON DWC |
IJ26359 | JOBSTREAMINPLAN QUERY DIDN'T HAVE THE REQUIRED HOW-MANY FIELD IN THE MANDATORY PARAMETERS |
IJ26422 | MONMAN ALLOCATING HUGE NUMBER OF FILES (ALL SYMPHONY FILES)-OLD SYMPHONY FILES |
IJ27011 | EVENT ACTION MAILSENDER SUBJECT IS GARBLED WITH QUOTED-PRINTABLE ENCODING |
IJ27250 | APPLYING DWC 9.4.0 FP0006, "IBM WORKLOAD AUTOMATION API" SWAGGER UI BECOMES BLANK (DWC to zOS) |
IJ27254 | CARRYFORWARD NOT TAKING FORWARD ABEND JOB WHEN IT IS SECOND RUN (RERUN) |
IJ27720 | HIGH CPU CONSUMPTION FOR JOBMANAGER PROCESS WHILE CHECKING THE EXISTENCE OF MANY FILES TO RESOLVE "OPEN" DEPENDENCIES |
IJ28346 | ISERIES JOBS COMPLETION TIME DEPENDS ON THE NUMBER OF ELEMENTS IN OUTQ |
IJ28481 | CHANGEING DB2 TO ORACLE PROCEDURE JNEXTPLAN JAVA NULL POINTER EXCEPTION |
IJ28771 | DYNAMIC AGENT FREQUENTLY GOES OFFLINE |
DEFECT | ABSTRACT |
WA-79361 | APPSCAN FOUND PHISHING THROUG FRAMES ON AJAXSERVICEDISPATCHERSERVLET |
WA-79362 | APPSCAN FOUND MISSING SECURE ATTRIBUTE IN ENCRYPTED SESSION (SSL) COOKIE |
WA-79508 | APPSCAN FOUND CROSS-SITE REQUEST FORGERY |
WA-80076 | WHITESOURCE SHOWS VULNERABILITY ISSUE ON WHITESOURCE SHOWS VULNERABILITY ISSUE ON JQERY JAVASCRIPT |
WA-85104 | IWS JOB FAIL IF THE SALESFORCE JOB IS IN HOLDING |
WA-85771 | THE TWS_INST_PULL_INFO DOES NOT WORK ON WINDOWS |
WA-86702 | UPDATE BUILD AND PACKAGING DUE TO PLUG-INS CHANGES |
WA-86720 | UPDATE TIMEZONE TO LATEST VERSION 2020a |
WA-86729 | UPDATE THE JACKSON LIBRARY |
WA-86907 | NEED TO DOCUMENT STEP BY STEP SAP UPGRADE SCENARIO |
WA-87691 | BROKER UNLINKS DURING PORT SCAN |
WA-87997 | UPDATE SSM TO LATEST VERSION 4.0.1-236 (JUN 2020) |
WA-88004 | WHITESOURCE SOURCE SHOWS VULNERABILITY ISSUE ON JACKSON LIB |
WA-88038 | ADD NEW CERTIFICATES (VALID TO 2023) |
WA-88055 | APPSCAN FOUND CROSS-SITE REQUEST FORGERY ON CONTENTRENDER.DO |
WA-88257 | MAKE GATHER ON WINDOWS WORK |
WA-88258 | TEST CONNECTION DA/BROKER AND VICEVERSA |
WA-88260 | MORE TRACE IN SCRIPT FOR CENTRALIZED UPDATE |
WA-88261 | IMPROVE DA TRACES |
WA-88262 | DISABLE MAKESEC IF ROLE BASED SECURITY |
WA-89090 | WHITESOURCE SHOWS VULNERABILITY ON LOG4J-1.2.15.JAR |
WA-89092 | WHITESOURCE SHOWS VULNERABILITY ON COMMONS-FILEUPLOAD-1.3.3.JAR |
WA-89319 | REMOVE SLAVE WORD FROM DWC |
WA-89357 | UPDATE CIT TO SUPPORT RHEL 8 PLATFORM |
WA-90245 | INCORRECT TIMEOUT MANAGEMENT ON RESPOSITORY EXCLUSIVE ACCESS FOR FILEMONITOR |
WA-90376 | MONMAN HANG IN WINDOWS |
WA-90642 | UNEXPECTED JOB STATUS AFTER DEADLINE |
WA-90979 | WHITESOURCE SHOWS VULNERABILITY ISSUE ON ISSUE ON JQUERY-1.10.2.MIN.JS |
WA-91423 | WHITESOURCE SHOWS VULNERABILITY ISSUE ON ISSUE ON ANT-1.9.4.JAR |
WA-91423 | WHITESOURCE SHOWS VULNERABILITY ISSUE ON ISSUE ON ANT-1.9.4.JAR |
Problems fixed in IBM Workload Scheduler Fix Pack 6 for version 9.4.0
This section lists APARs and internal defects solved by Fix Pack 6.
This Fix Pack includes a number of fixes for internal defects found by the verification team that mainly cover the following product capabilities:
APAR | ABSTRACT |
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 |
IJ04103: | AGENT INSTALL FAILS WITH AWSFAB231E (NFS_NOT_AVAILABLE) ERROR |
IJ04230: | PERFORMING CANCEL PENDING DELAYS WHEN BATCHMAN DOES NOT HAVE WORK TO DO |
IJ04537: | IBM_I PACKAGEDEPLOY.SH ISSUE. |
IJ06229: | DDM AUTOMATICALLY CREATES AGAIN MASTERAGENTS WORKSTATION BUT IT'S LINKED TO THE WRONG HOST ID. |
IJ06492: | CUSTOM CONFIGURE TASKS (SET AUTO REFRESH) AND (ENABLE PERIODIC REFRESH) ARE ONLY WORKING AFTER THE FIRST INTERVAL |
IJ07067: | JOBS WITHOUT AT TIME START AN HOUR EARLY ON DST CHANGE WHEN ENPREVENTSTART=YES |
IJ07377: | ZCENTRIC AGENTS DO NOT RECONNECT AFTER SYSTEM REBOOT |
IJ07385: | MULTIPLE VULNERABILITIES FOUND IN OPENSSL |
IJ07394: | EVENT MONITORING EIF PORT DOES NOT RESPECT SSL SETTINGS |
IJ07532: | Extend the AS400 jobs user interface to allow LDA specification |
IJ07907: | THE STATUS IS "ERROR ABEND", THOUGH A FINISHED JOB EXIT WITH 0 |
IJ07948: | PLUG-INS CREATES TOO MANY ENTRIES IN JAZZSM DIRECTORY |
IJ07966: | PLANMAN RESYNC IS FAILING - AWSJCL075E SYMPHONY FILE LOAD HAS FAILED... AWSJDB818E AN INTERNAL ERROR HAS OCCURRED SQLCODE=-302 |
IJ08161: | IMPROVE THE JOBMANAGER.INI.BAK FILE CREATION MECHANISM |
IJ08195: | CMDLAUNCHER PROGRAM IN TWS/BIN CAN ALLOW A NOT ROOT USER TO LAUNCH COMMANDS IMPERSONATING |
IJ08197: | PLAN MIRRORING ISSUE. COMPLETED JOB STREAM REMAINS IN READY |
IJ08496: | OVERLAP DOES NOT WORK CORRECTLY IF THE SCHEDULE IS DEFINED FOR A CPU THAT IS NO A MANAGER. |
IJ09680: | INSTALL ISSUE EXISTS WITH SPACES WITH INSTALL FOR A USER THAT BELONGS TO A GROUP THAT HAS A SPACE IN NAME OF GROUP. |
IJ09759: | DRAFT FLAG IS REMOVED WHEN RENAMING JOBSTREAM FROM ONE CPU TO ANOTHER |
IJ11152: | HOW-MANY=0" RETURNS BLANK RESULT ON THE PLAN OBJECT QUERY REST API. |
IJ11203: | SUBMIT A REMOTE COMMAND JOB CONTAINING THE # CHAR E.G. ECHO #HOSTNAMEWITH RXA STAYS IN EXEC (HANG) FOR EVER. |
IJ11230: | TWS CENTRALIZED UPGRADE FAILURE FROM 9.4 FP3 ONLY TO HIGHER LEVEL. |
IJ11456: | OPENSSL: 1.0.2q 20 NOV 2018) - TWS 9.1 FP2 Libeay32.dll NOT FOUND ON WINDOWS PLATFORM |
IJ11482: | UNABLE TO LOAD PREDECESSOR JOBS FROM A BKM IN DWC 9.4.04. AWSUI0796E THE SPECIFIED ACTION CANNOT BE PERFORMED. |
IJ11908: | TWS DEPENDENCIES REMOVED WHEN UPGRADING RUNCYCLE IN A JOBSTYREAM BEFORE THE FINAL RUN TIME |
IJ12048: | HIGH LOAD OF DATASTAGE JOBS (2100+) CAUSES MEMORY LEAK AND JOB FAILURES |
IJ12793: | ON A DDM, THE SCHEDULE TIMEZONE SPECIFICATION FOR THE UNTIL IS NOT ENFORCED, AND USES THE UNDERLYING TIMEZONE OF THE PROCESSES. |
IJ12856: | MEMORY LEAK IN WAS WITH IWS SECURITY GROUPS AND LARGE NUMBER OF OS GROUPS |
IJ12956: | SEARCH" DOES NOT RETURN ANY JOB DEFINITIONS ON "RERUN JOB" JOB DEFINITION SEARCH ON IE11 IF JAPANESE ENGINE NAME USED. |
IJ13299: | JOB DEPENDENCY NOT WORKING PROPERLY IN TDWC |
IJ13301: | CLUSTER ENABLER: MICROSOFT VISUAL C++ 2005 INFORMATION NEEDS TO BE UPDATED. |
IJ13393: | DDM QUERY TO MDL.MPR_MODEL_PROPERTIES WHEN AGENT SENDS RESOURCE INFORMATION |
IJ13578: | MAKEPLAN HANGS AFTER INTRODUCING A SCHEDULE WITH A RUN CYCLEGROUP INTO THE PLAN THAT INCLUDES An "AND" at the end. |
IJ13958: | DA INSTALLATION - OS VERSION CHECKPREREQ FAILS ON CENTOS LINUX RELEASE 7.4.1708 |
IJ14140: | SSL CONNECTION ENABLED BETWEEN DM AND FTAS. IF CONNECTION ISSUE OCCUR THE DM MAILMAN PROCESS DOESN'T MANAGE TIMEOUT ERROR |
IJ14147: | AFTER UPGRADING DA'S TO 9.4.0.3 THAT SUPPORT OUR OLFM AGENTS THE OPERATING UNIT IS NO LONGER GETTING POPULATED IN OLFM |
IJ14282: | JOBS ARE RANDOMLY KILLED WITH EXIT 143 |
IJ14465: | CENTRALIZED AGENT UPDATE IS NOT UPDATING ALL FILES |
IJ14630: | EVENT RULES OCCASSIONALLY SUBMIT THE WRONG JOB STREAM. |
IJ14905: | WAS SERVER GOES DOWN UNEXPECTEDLY |
IJ15443: | RUNCYCLES WITH EVERY DID NOT WORK |
IJ15658: | TICKET TS002042152: INCORRECT JOB_HISTORY_V ON ORACLE RDBMS |
IJ15697: | UNABLE TO ADD CONDITION VALUE WITH "CONTAINS" FOR JOB TYPE "SAP JOB ON DYNAMIC WORKSTATIONS" |
IJ15789: | RUNNING CURL THROWS THE FOLLOWING ERROR: $ CURL GOOGLE.COM CURL:(2) FAILED INITIALIZATION |
IJ16230: | FTP JOBS WITH WILDCARDS ON DSNAME FAIL AWKFTE037E |
IJ16419: | STAGEMAN EXIT WITH RETURN CODE 1 |
IJ16431: | DWC 9.4 FP05 "SUBMIT PREDEFINED JOSBTREAM" PANEL THE selected variable from VARTAB IS OVERRIDEN BY THE DEFAULT MAIN_TABLE VAR |
IJ16502: | SYMPHONY CORRUPTION CAUSES BATCHMAN CRASHING WITH AWSBHT095E BATCHMAN COULD NOT ACCESS THE MAILBOX FILE SYMPHONY.MSG |
IV83963: | DELETE SOURCE FILE AFTER TRANSFER FAILS - WINDOWS FILE TRANSFER JOBS |
IV93833: | REMOVE FROM SYSTEMOUT.LOG NOT USEFUL MESSAGES. |
IV95283: | MAKEPLAN FAILING AFTER RUNNING A LONG TIME DUE TO USE OF EVERYENDTIME |
DEFECT | ABSTRACT |
WA-78114: | Update OpenSSL version |
WA-78131: | Update JRE |
WA-78137: | Update GSKIT |
WA-78181: | CLONE - Job Stream View live update is returning always the full list of jobs |
WA-79108: | 94FP6: Solaris Opteron Prereq Check not found Solaris Version |
WA-79279: | Engine 9.5: "Maximum Duration Action" of a job in plan (with deadline) is not correctly saved |
WA-79431: | tasklaucher infinite loop on Windows |
WA-79761: | CVE-2019-4031 IBM Workload Scheduler TASKLAUNCHER contains a vulnerability. |
WA-80077: | WhiteSource shows vulnerability issue on cdx-signature.api |
WA-80387: | Missing new version SLES 15 and Windows 2019 in the agent prereq scan: |
WA-80596: | 9.4 Documentation: OPENS filename lenght is 120 characters instead of 145 byte |
WA-80647: | sjrf_is_mpe_job flag is still evaluated in symaccs |
WA-80658: | r3batch:Segmentation fault having a clear text password in the opts file |
Problems fixed in IBM Workload Scheduler Fix Pack 5 for version 9.4.0
This section lists APARs and internal defects solved by Fix Pack 5.
- Installation
- Auditing
- Mirroring
APAR | ABSTRACT |
IJ05421: | ITM AGENT HAS DOCKQDS FILE THAT HAS JOB NUMBER AS 7 CHARACTERS INSTEAD OF 8 CHARACTERS |
IJ06809: | COMMENTS IN SCHEDULE DEFINTIONS ARE BEING MOVED TO THE TOP OF THE NEXT SCHEDULE IN THE LIST |
IJ07282: | DEFAULT VARIABLE TABLE OVERRIDES THE PREVIOUSLY SPECIFIED VARIABLE TABLE |
IJ07504: | DOCUMENT INFORMATION ABOUT CARRYFORWARD BEHAVIOR OF JOBSTREAM WITHOUT JOB DEFINED |
IJ07531: | DA ISERIES BE ABLE TO MANAGE CHILDS AND NOCHILDS |
IJ07860: | JSR352: ADD USERID AND PASSWORD SUPPORT TO CONNECTION WITH PROXY |
IJ08187: | AUDIT:ENDBAUDIT OPTMAN OPTION DOES NOT WORK |
IJ08651: | FTP ON WIN UPLOAD AND DELETE DOES NOT WORK |
IJ08663: | CHANGES ARE NEEDED INTO LOCALOPTS AND DOCUMENTATION TOO FOR THE HOST FIELD |
IJ08821: | TWS 9.4 FILEMONITOR ISSUE ON CONCURRENT EXECUTION |
IJ08860: | INCLUDE THE NEW TIME CHANGES TZDATA2018E INTO TWS RELEASE |
IJ09114 : | WRONG HELP GUIDE ABOUT FREEDAYS OPTION FOR RUN CYCLE GROUP OBJECT. x |
IJ09121: | UPDATE DOCUMENTATION THAT COMPLETION OF INSTALL REMOVES SEVERALFOLDERS IN /OPT/IBM |
IJ09416: | USING THE ALTER JOB FEATURE CAUSES MAILBOX.MSG TO FILL |
IJ09641: | JOBS IN PLAN SHOWING MAXDUR=00:00 MINDUR=00:00 WHERE NOT DEFINED |
IJ09715: | SEGMENTATION FAULT(COREDUMP) WHEN EXECUTING CONMAN -GUI 'SETSYM 10&SJ @#@;LOGON' 1>SJ_LOGON.TXT 2>&1 |
IJ09742: | UNABLE TO INCLUDE A '/' (SLASH) IN THE SEARCH STRING WHEN FILTERING ON 'SCHEDULED TIME' AFTER UPGRADE TO DWC 9.4.X |
IJ10141: | ORACLE EBS NULLPOINTER |
IJ10311: | FILE_STARTCOND JOB ABENDS WITH AN EXCLUSIVE ACCESS TO THE REPOSITORY ERROR. |
IJ10729: | JRE 7.0.10.30: SCRIPT ADDS IJ10729 EVERY TIME IT'S EXECUTED |
IJ11248: | JOBMANAGER CORE DUMP WITH SIGNAL 6 |
IJ11281: | (MASTERAGENTS#)RESTART_STARTCOND JOB FAILS WITH AWSBHT001E AND AWKTSA050E JCL ERROR. |
IJ11361: | FTA CENTRALIZED UPDATE FAILS FOR TWS FTA 9.4FP3 AND FP4 |
IV86277: | IWS 9.3 AND PEOPLETOOLS 8.53 CONNECTION ISSUE. |
DEFECT | ABSTRACT |
WA-76195: | WhiteSource: update version needed for commons-logging-1.0.4.jar |
WA-76196: | WhiteSource: security vulnerability found on jackson-databind-2.9.4.jar |
WA-76199: | WA-76199 WhiteSource: update version needed for commons-io-1.3.2.jar |
WA-76200: | WhiteSource: security vulnerability found on commons-collections-2.1.jar |
WA-76284: | WhiteSource: security vulnerability found on camel-core-2.16.1.jar |
WA-76326: | PERF: JobManager memory leak 0.8 MB/min @300Jobs/min workload |
WA-76589: | Incorrect job statuses from DWC after suppression of a job chain |
WA-76691: | 94FP5: need to evaluate disk space needed for centralized update |
WA-76762: | WhiteSource: security vulnerability on derby-10.1.2.1.jar |
WA-77400: | WhiteSource: security vulnerability found on commons-io libs |
Problems fixed in IBM Workload Scheduler Fix Pack 4 for version 9.4.0
This section lists APARs and internal defects solved by Fix Pack 4.
This Fix Pack includes a number of fixes for internal defects found by the verification team that mainly cover the following product capabilities: installation, auditing, and mirroring.
APAR | ABSTRACT |
IJ00214: | FILETRANSFER JOB RESULTS IN ABEND WITH THE ERROR AWSITA036W |
IJ00465: | SEARCH FOR LIST WORKLOAD DEFINITION LIMITS RESULT TO 250 ITEMS |
IJ00778: | BAD BEHAVIOR OF CONDITIONAL DEPENDENCIES |
IJ01507: | MIRRORING CACHE CLEANUP CANNOT BE CUSTOMIZED |
IJ03479: | ISSUE WHEN OPEN A COMPLEX VARIANT SAP |
IJ03767: | EXCLUDE RUNCYCLE DOES NOT SUPPORT EVERY AND EVERYENDTIME |
IJ04677: | DATE IN HEADER/FOOTER ARE ENCODED IN EUC, ALTHOUGH LANG IS UTF-8 ON SOLARIS 10. |
IJ04771: | MONITOR EVENT RULE (IN PLAN) SHOWS ONLY 250 EVENT RULES |
IJ04904: | TWS 9.4 FP2 ZLINUX S390 COMPOSER CONMAN TAKE TOO MUCH TIME TO START |
IJ05296: | MDM COULD CRASH IF A LARGE QUERY OF PROMPT (LIKE 60000) IS DONE AGAINST AN ARCHIVED PLAN |
IJ05392: | JOBLOG TO BE CREATED WITH 600 LEVEL PERMISSION |
IJ05397: | DURING JNEXTPLAN A DEADLOCK OCCURED |
IJ05459: | CHANGED BEHAVIOR FOR COMPOSER ADDING JOB-LEVEL RESOURCE DEPENDENCY |
IJ05783: | COMPOSER DOES NOT RETURN A CORRECT TOTAL NUMBER OF OBJECTS UPDATED |
IJ05797: | AFTER 940 FP03 ON DYNAMIC ISERIES OS400 AGENT, ALL SBMJOB EXIT WITH UNABLE TO GET THE COMPLETION MESSAGE CPC1221 |
IJ05805: | COMPOSER REPLACE ON A SCHED ERRORS ON DUPLICATE RUN CYCLE NAME |
IJ06438: | DBCS CAN NOT BE USED IN RUNCYCLE WHEN IMPORTING DEFINITIONS USING COMPOSER |
IJ06672: | |
IV93679: | SSMAGENT CANNOT STAY UP ON SUN4U |
IV93828: | FILE DESCRIPTORS NOT BEING CLOSED ON OLD LOG FILES WHEN LOG SWITCH OCCURS |
IV99201: | TWS 9.4 FP1 UPGRADE OF A BACKUP MDM TO 9.4 FP1 CAUSES DA ON BKMD M LINK ISSUES. |
IV99357: | JOB STATUS SHOW WAIT OF EXEC REGARDLESS OF ACTUAL STATUS |
DEFECT | ABSTRACT |
WA-71497: | Incorrect job status after suppression of a predecessor job |
WA-71566: | Data set monitor-create event rule: rule is not sent if * is in workstation |
WA-71616: | Conman crash issuing altpass command |
WA-71618: | nullPointerException issuing a conman listsucc command |
WA-71632: | Unexpected blank spaces in conman output using jobs with conditional dependencies in OR |
WA-71775: | ITA core dump on Solaris Sparc performing an agent shutdown |
WA-72020: | Batchman crash running automation suite after JnextPlan execution |
WA-72045: | Unexpected error executing a job with resubmit job plug-in |
WA-72052: | Missing loop performed running the resubmit job |
Problems fixed in IBM Workload Scheduler Fix Pack 3 for version 9.4.0
This section lists APARs and internal defects solved by Fix Pack 3.
This Fix Pack includes a number of fixes for internal defects found by the verification team that mainly cover the following product capabilities: installation, auditing, and mirroring.
APAR | ABSTRACT |
IV91745 | CONMAN SJ; INFO WRONG FORMAT |
IJ02038 | BACKWARD COMPATIBILITY FOR FILETRANSFERS JOBS: JOBS DEFINED IN 9.X MASTERS ARE NOT RUNNING ON 8.6 AGENTS, RETURNING AWKSUL020E |
IJ00114 | UNIXSSH XA AGENTS - RCCONDSUCC ENABLEMENT CODE ADDED AS COMMENT TO UNIXSSH SCRIPT |
IV98325 | REP11 INCLUDING JOB STREAMS IN "DRAFT" STATE |
IV98138 | EXCLUDE CALENDARS ARE BEING IGNORED BY REP11 |
IJ00338 | JOB STREAM IS PLANNED UNEXPECTEDLY ON EXCEPT CALENDAR DATE |
IJ03479 | ISSUE WHEN OPEN A COMPLEX VARIANT SAP |
IJ02712 | TWS ELEVATED PRIVILEGES (SETGID AND SETUID PROGRAMS) LIBRARIES HAVE INSECURE LOCATIONS IN RPATH (.) |
IJ02596 | INCREASE ROBUSTNESS OF TSAMP MONITORCOMMAND |
IJ01535 | TWS ZCENTRIC AGENT STOP WORKING AFTER Z/OS SERVER IPL/REBOOT/NETWORK DISCONNECT |
IJ01061 | IMPLEMENT THE LOGIC OF APAR IV88912 IN JOBMANRC FILE |
IJ00336 | MSSQL SUPPORT DOES NOT INCLUDE ANY LANGUAGE SUPPORT |
IJ00950 | IF A TRIAL PLAN EXTENSION IS LONGER THAN 3 MINS IT CAN BE EXECUTED TWICE |
IJ00910 | MIRRORING: IF A SUB_QUEUE BECAME FULL A DEADLOCK COULD OCCURR |
IJ03167 | ERRONEOUS WARNING MESSAGE AWSBHX032W THE STARTED DATE OF THE FOLLOWING JOB IS NULL |
IJ03583 | USING OFFSETS FROM WORKDAYS WHEN CREATING RUNCYCLE GROUPS USING COMPOSER RESULTS IN INCORRECT DATES BEING SELECTED |
IJ02415 | OPENS ON DYNAMIC AGENTS AND POOLS WITH DYNAMICAGENTSSTAYS IN ASKED STATE WHEN BATCHMAN IS NOT ABLE TO COMMUNICATEWITH BROKER |
IJ01506 | JOBS ON POOL WORKSTATIONS ARE STUCK ON WAIT STATE |
IV94273 | AWSJIM920E ERROR DURING THE INSTALL OF A NEW 9.2-FP02 BACKUP MASTER WITH ORACLE. |
IJ02042 | IWS WEB SERVICE FAILS WHERE OUTPUTCONDITION IS SET TO NULL |
IJ02011 | OPENSSL FLAG IN TWS/BIN FOLDER HAS SUID FLAG |
IJ01948 | SERVER.MSG NOT CLEARING WHEN WORKLOAD ASSURANCE IS ACTIVE |
IJ03999 | REST API JOB STREAM issue |
IJ04395 | RERUN TOOK UP TO 2 MINUTES |
IJ03686 | LOCALOPTS FILE DOES CONTAIN REFERENCE TO THE MOZART DIRECTORY, BUT THE MOZART DIRECTORY IS NOT CREATED IN INSTALLING AGENTS. |
IJ03531 | AWSITA141E ON MDM ADHOC CONMAN SBD WITH RCCONDSUCC ON AIX DA ONLY WITH TWS9402. THE JCLFILE IS EMPTY, TWSRCMAP IS CORRECT. |
IJ00572 | BACKUPINSTANCE.SH/RESTOREINSTANCE.SH SCRIPTS ASSUME DEFAULT |
IJ02494 | JOB EVENT CODES 123-127 NEED TO BE ADDED TO THE DOCUMENTATION |
IJ04102 | DWC DISPLAYS NEGATIVE PROMPT NUMBERS |
DEFECT | ABSTRACT |
WA-71497 | Incorrect job status after suppression of a predecessor job |
WA-71566 | Data set monitor-create event rule: rule is not sent if * is in workstation |
WA-71616 | Conman crash issuing altpass command |
WA-71618 | nullPointerException issuing a conman listsucc command |
WA-71632 | Unexpected blank spaces in conman output using jobs with conditional dependencies in OR |
WA-71775 | ITA core dump on Solaris Sparc performing an agent shutdown |
WA-72020 | Batchman crash running automation suite after JnextPlan execution |
WA-72045 | Unexpected error executing a job with resubmit job plug-in |
WA-72052 | Missing loop performed running the resubmit job |
Problems fixed in IBM Workload Scheduler Fix Pack 2 for version 9.4.0
This section lists APARs and internal defects solved by Fix Pack 2.
This Fix Pack includes a number of fixes for internal defects found by the verification team that mainly cover the following product capabilities: installation, auditing, and mirroring.
APAR | ABSTRACT |
IJ00606 | The Filedep on a pool or dynamic pool remains unresolved in case one agent in the pool is down |
IV98138 | EXCLUDE CALENDARS ARE BEING IGNORED BY REP11 |
IV98325 | REP11 INCLUDING JOB STREAMS IN "DRAFT" STATE |
IJ00392 | Filecheck dependency (OPENS) on file on dynamic agent remains in "asked" even if the file is present |
IJ00463 | IWS SERVICE ON FTA FAILS TO START ON 9.4 |
IJ00166 | A HUGE NUMBER OF FILEDEP HAS A NEGATIVE IMPACT ON MIRRORING |
IV87038 | TWS 9.2 JVM CRASH AND JAVA CORE IS GENERATED |
IV83728 | JOBlog archived zip file is readable only for TWS user |
IV99870 | TWS 9.4 GA&FP1 COMPOSER MANAGES ONLY THE USER ON THE ACL DEFINITION |
IV98396 | CP: ./PREREQUISITES/UNIX_LINUX/DWC_09000000.CFG.TPL: A FILE OR IN THE PATH NAME DOES NOT EXIST |
IJ00078 | IWS composer 9.4 fp1 fails on replace character when find an incorrect one |
IV99644 | Job status mismatch between DWC & conman |
IV99590 | ROLE BASED SECURITY COMPOSER OUTPUT RETURNS NULL VALUES FOR GROUPS |
IV98735 | TWS PREREQ SCANNER IS UNABLE TO READ THE OS.FILE.FUSER PROPERTY |
IV98671 | USEROPTS FILE IS CREATED WITH AN INCORRECT NAME |
IV97712 | conman sr @#@ coredump on AIX 7 when 1 holder of resource exist (of type job) |
IV90852 | THE XRXTRCT COMMAND DOES NOT DISPLAY THE INTERNETWORK DEPENDENCIES |
IV94011 | TWS 9.X HANDLE MUTEX LEAKS ON GSKIT WINDOWS |
IV99112 | TWS REST API GETJOB IS SLOW WHEN THE JOBKEY IS USED |
IV98229 | ENHANCE THE TWS BROKER SERVICEABILITY |
IV98043 | REMOTE CLI COMPOSER.EXE FUNCTIONALITY DOES NOT OPERATE PROPERLY |
IV98210 | ORACLE DATABASE DEADLOCK OCCURRING WHEN CANCELLING A CARRIED FORWARD JS WITH EXTERNAL DEPENDENCIES |
IV98945 | CHECKSYNC ABENDS WITH RC=8 |
IV98476 | EVENTS LOST ON A DISTRIBUTED TWS ZCENTRIC WORKSTATION |
IV98172 | IWS PACKAGE CONTAINS VULNERABLE TOOL "UNZIP.EXE" ACCORDING TO CVE-2005-2475 : UNZIP 5.52 FROM FEB 2005. THIS MUST BE REMOVED |
IV98395 | JobManager occasionally fails to start when ExecutorsMinThreads in JobMananger.ini is high (more than 600) |
IJ00599 | PLN.PFDP tables not cleaned up by mirroring plan delete |
IV97903 | TWS EVENTPROCESSOR COULD HANG IF A NETWORK ISSUE OCCURS |
IV98265 | MONMAN MEMORY LEAK WHEN STARTS R3EVMAN.EXE |
IV78030 | When DST starts, if SOD falls on the hour missing, plan is extended for 24 hours instead than for 23 |
IV98646 | IWS 9.3-FP03 IMPLEMENTED A CHANGE IN DEFAULT BEHAVIOR OF THE EXECUTECMD.SH COMMAND PER APAR IV87679 |
IV98638 | PLAN MIRRORING STALLS FOLLOWING A SWITCHMGR FOR A SUB-DOMAIN MANAGER |
IV94783 | NMAN REPORTS AWSBCX013E ERROR WHEN PARSING EVENT 51 RELATING |
IV95276 | add tls11 and tls12 in localopts for fta |
IJ00716 | It is necessary to update OpenSSL libraries in IBM Workload Scheduler build because of the following vulnerabilities of OpenSSL: CVE-2016-3732 and CVE-2016-3735 |
Problems fixed in IBM Workload Scheduler Fix Pack 1 for version 9.4.0
This section lists APARs and internal defects solved by Fix Pack 1.
This Fix Pack includes a number of fixes for internal defects found by the verification team that mainly cover the following product capabilities: installation, auditing, and mirroring.
APAR | ABSTRACT |
IV69128 | THE NET SERVICE NAME MAX LENGTH IN CONFIGURING DB DURING INSTALLATION CANNOT BE GREATER THAN NINE. |
IV81576 | NETMAN FOR A 8.6 WINDOWS AGENT NEVER RELEASES MEMORY AFTER RUNNING CONMAN SJ;STDLIST ON IT |
IV93078 | A composer hanging could negatively affect the WAS startup (EDWA)" |
IV73429 | DEADLOCK ON THREADS ON JOBMANAGER CAUSING AGENTS TO HANG |
IV76015 | JOB STREAM CONTAINING A PARTICULAR OPENS DEPENDENCY ENCOUNTERS AN AWSJPL525W ERROR IF AD HOC SUBMITTED |
IV78321 | UPDATE ZONE INFO ACCORDING TO LATEST CHANGES FOR 2015 |
IV81521 | ERROR IMPORTING INTO TWS 9.1 VIA WAPPMAN DEFINITIONS.XML |
IV82747 | JobManagerGW DOES NOT START UP BECAUSE JOBMANAGERGW.INI IS EMPTY |
IV83754 | THE TWS MONMAN PROCESS IS EXPERIENCING A RANDOM FAILURE DURING THE SWITCH OF THE STDLIST AT FINAL |
IV83761 | TWS LIBJOBMANAGERCORENEEDS TO HAVE 555 AS PERMISSION |
IV83962 | DISPLAY ALERTS UNTIL A JOB COMPLETES |
IV86072 | UNABLE TO INCREASE SIZE AND/OR NUMBER OF Z/CENTRIC AGENT LOG/TRACE FILES ON WINDOWS SYSTEMS |
IV86852 | AWSJOM200E ERROR OCCURS IF AT AND EVERYENDTIME ARE DEFINED ACROSS 00:00 WHEN SOD IS NOT 0000 |
IV87679 | GENERIC ACTION PLUG-IN SCRIPT EXECUTECMD.SH ON AIX HAS ROOT ENV |
IV88912 | Dynamic jobs fail with 126 on AIX |
IV88971 | INSTALL OF DYNAMIC AGENT ON WINDOWS TESTS VALUE FOR TWS_THISCPU |
IV89009 | SYNCHRONIZATION BETWEEN DEPENDENCIES AND JOB/JOBSTREAM |
IV89649 | WEBSPHERE RECYCLES AFTER A NORMAL RESTART IN WORKLOAD SCHEDULER |
IV89492 | MSSQL UPDATESTATS GIVES WARNING AWSJPL804W |
IV89990 | PLANMAN CONFIRM HANGS |
IV90602 | JOB SUBMITTED INTO CARRYFORWARD SCHEDULE NOT SHOWING CORRECT STATUS |
IV90614 | DYNAMIC AGENT HAS PROBLEMS IN MANAGING OPEN DEPENDENCY EXECUTING EXTERNAL PROGRAMS |
IV90830 | USERPROFILE IS NOT LOADED FOR XAGENT RUNNING ON WINDOWS |
IV90870 | ESTIMATED DURATION WRONG ON MONITOR JOBS IN DYNAMIC WORKLOAD CONSOLE AND CONMAN |
IV91018 | JOBRUNSTATISTICS REPORT FOR JOB DURATION ALWAYS SHOWS TWO PARTS INSTEAD OF THREE AS SHOWNN HH:MM:SS |
IV91072 | CONMAN SBD TO WINDOWS FTA TRUNCATES THE CONMAND LINE WITH TWSRCMAP |
IV91175 | INSTALLING AGENT, PRE-REQ SCANNER FAILS IF THE <TWAHOME> DIRECTORY PATH CONTAINS A (.) CHARACTER |
IV91219 | MB EVENTS SENT BY 9.3FP1 CAUSES RANDOM UNLINK OF PRE-9.3FP1 FTA |
IV91269 | CORRUPT JMJOBTABLEDIR CAN CAUSE JOBMANAGER TO CORE |
IV92161 | STAGEMAN CRASHES IF enCarryForward = NO |
IV92306 | MIRRORBOX.MSG SIZE INCREASE IF MANY FILE DEPENDENCIES ARE DEFINED IN THE WORKLOAD |
IV92352 | AFTER SWITCH MASTER SOME DYNAMIC JOBS REMAIN IN EXEC STATUS ON COMPOSER |
IV92358 | UPDATE CURL COMPONENT FOR CVE-2016-8616 CVE-2016-8624 AND CVE-2016-8621 |
IV92378 | AFTER PLANMAN RESYNC XA-EXTENDED AGENT ARE SET UNLINKED ON DWC MONITOR JOBS/CPUS THOUGH CONMAN STATUS IS CORRECT |
IV92447 | NEED TO EXPLAIN HOW "OVERLAP DONOTSTART" WORKS IN DETAIL |
IV92455 | BROKER AGENTS WILL NOT LINK TO BACKUP DOMAIN MANAGER |
IV92859 | IWS 9.4 SILENT INSTALL RESPONSE FILE REFERENCES IBM JAVA.V70. |
IV93048 | stageman can cause A JOB STREAM to be put at pri=0 |
IV93052 | Unable to view joblog from DWC/conman when job defined on XA hosted by DWB using jsdl and with resources |
IV93337 | POOR PERFORMANCE OF PLANDELETE ON ORACLE |
IV93482 | AWSJDB810E ERROR ENCOUNTERED WHILE RUNNING SWITCHPLAN ON MDM INSTALLED AS A BACKUP MDM DURING A PARALLEL UPGRADE |
IV93505 | LFTA NOT LINKED IF CENTRALIZED SECURITY IS ENABLED |
IV93578 | ITA NOT UPDATED TO 64-BIT IF UPGRADE FROM TWS 8.6 FP4 TO 9.2+ |
IV95368 | DA/POOL jobs erroneously in ABEND close to MAKEPLAN/SWITCHPLAN |
IV93890 | MAILSENDERPLUG-IN DOES NOT SET FULLY-QUALIFIED NAME OF THE CLIENTSENDING THE MAIL.THIS CAUSES ISSUE IN HELO PART OF SMTP SERVER |
IV93899 | ONOVERLAP DONOTSTART STREAM STAYS ON HOLD WHEN STREAM JOBS ARE MIXED IN LINUX AND WINDOWS |
IV95378 | MODIFY TWS WINDOWS SERVICE |
Known limitations and work arounds
The following are software limitations and work arounds that affect Workload Scheduler . For the latest V9.4 General Availability release, see the product Release Notes at http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27048863.
- 9.4 Fix Pack 7:
- Time Delays occurs when using conman CLI - Stream ioctl timeout
-
In instances where you are using one composer CLI and one conman CLI at time, logger options need to be changed from:
. *.trhd.className = ccg_multiproc_filehandler *.loggerhd.className = ccg_multiproc_filehandler .
. *.trhd.className = ccg_filehandler *.loggerhd.className = ccg_filehandler .
- 9.4 Fix Pack 6:
-
- Upgrading to versions 9.5 GA or 9.5 FP1 from an upgraded version 9.4 FP6 with an MSSQL or Informix database
- If you have upgraded to version 9.4 FP6 from version 9.4 GA or from any fix pack earlier than FP6, and are using an MSSQL or Informix database, apply 9.4 FP7 before upgrading to versions 9.5 GA or 9.5 FP1.
- 9.4 Fix Pack 4:
-
- Incorrect job status after completion in success of a predecessor job
-
- Define the following job definitions:
$JOBS AGT1#CDJ_FIRST_PRED DOCOMMAND "netstat -an" STREAMLOGON "ITAuser" TASKTYPE UNIX RECOVERY STOP SUCCOUTPUTCOND STATUS_OK "RC=0" OUTPUTCOND STATUS_NOT_OK "(RC>0) or (RC=-1)" AGT1#CDJ_PRED DOCOMMAND "netstat -an" STREAMLOGON "ITAuser" TASKTYPE UNIX RECOVERY STOP SUCCOUTPUTCOND STATUS_OK "RC=0" OUTPUTCOND STATUS_NOT_OK "(RC>0) or (RC=-1)" RECOVERY STOP AGT1#CDJ7 DOCOMMAND "netstat -an" STREAMLOGON "ITAuser" TASKTYPE UNIX RECOVERY STOP SUCCOUTPUTCOND STATUS_OK "RC=0" OUTPUTCOND STATUS_NOT_OK "(RC>0) or (RC=-1)" RECOVERY STOP
- Define the following job streams definitions:
SCHEDULE AGT1#JS_FEX : AGT1#CDJ_FIRST_PRED END SCHEDULE AGT1#JS_EXT : AGT1#CDJ_PRED FOLLOWS AGT1#JS_FEX.CDJ_FIRST_PRED IF ABEND END SCHEDULE AGT1#CDJS7 FOLLOWS AGT1#JS_EXT.CDJ_PRED IF STATUS_OK : AGT1#CDJ7 END
- Submit the job stream: AGT1#JS_FEX and wait the job: AGT1#JS_FEX.CDJ_FIRST_PRED ends in success state.
- Submit the job stream: AGT1#JS_EXT and wait the job: AGT1#JS_EXT.CDJ_PRED ends in suppress state because of the not satisfied conditional dependency
- Submit the job stream: AGT1#CDJS7 and wait the job: AGT1#CDJS7.CDJ7 ends in suppress state because of suppression of its predecessor
After the last step the status of : AGT1#CDJS7.CDJ7 job is displayed in suppress using the command: conman sj AGT1#CDJS7.CDJ7 and in HOLD state from the Dynamic Workload Console.
After the last step the status of AGT1#CDJS7.CDJ7 job is displayed in suppress using the command:
conman sj AGT1#CDJS7.CDJ7 and in HOLD state from the Dynamic Workload Console.
- Define the following job definitions:
- 9.4.0 Fix Pack 3
-
- SSH protocol fails to perform remote command (71149)
- File transfer and remote command do not work with the following version of SSH: 5.3p1 release 123.3l6_9
- Usage for the command altjob is incomplete(70578)
- Azure plug-in does not work after changing the default SSL (70807)
- When trying to change the default SSL protocol to the Java Client Application, editing
TWA\TWS\JavaExt9.4.0.03\jre\jre\lib\security\java.security
- 9.4.0 Fix Pack 2
-
- Changing language in Windows environment does not change IBM Workload Scheduler language as well (184736)
- In a Windows environment, if you change the language from English to another language, IBM Workload Scheduler does not change the language, but remains in English.
Workaround: To work around this problem, add the LANG environment variable and set it as new preferred language.
- Japanese, Chinese, Korean Language: Warning message in installation panel: the temporary directory does not have at least 5 MB (184727)
- Running the installation or the upgrade of IBM Workload Scheduler 9.4 Fix Pack 2, in Chinese, Korean and Japanese language, the Prerequisite Scan displays a warning message:
The scan cannot be run for different reasons: the temporary directory does not have at least 5 MB, the system registries are corrupted. Analyze the Installation Manager log files to see more details on the error. Check the Troubleshooting section of the Planning and Installation for a solution.
Despite this message the installation or the update process completes successfully. - Installation setup IBM Workload Scheduler fails if there is another IBM Workload Scheduler instance (184059)
- When trying to install IBM Workload Scheduler 9.4 GA + Fix Pack 2 on a workstation where a primary domain manager instance already exists, the installation fails.
Workaround: When launching the script to run Installation Manager, ensure that the script is launched from the folder where you unzipped the Fix Pack Image and specify the path to the folder where you unzipped the General Availability image.
- Unexpected success message written in stderr instead of stdout (180169)
- When using the composer command line, a message of success is erroneously written to the Standard Error instead of Standard Output.
- 9.4.0 Fix Pack 1
-
- IV60757: AFTER SWITCHING MANAGER CANNOT BROWSE JOBLOGS
-
Conman cannot retrieve job logs in archived plans for jobs which ran on dynamic agents if the primary domain manager in the archived plan is different from the current primary.
- 178943: Agent installation does not find prerequisite 32 bit libraries on LINUX PPC64LE SELS 12 SP2
- On LINUX PPC64LE workstations, the installation might fail because the following 32 bit libraries are missing with the following info in the log file/opt/IBM/TWA_twsuser/logs/result.txt:
The prerequisite fails because the 32 bit libraries are not available. os.lib.libstdc.so.5_32 FAIL Unavailable /usr/lib/libstdc++.so.5 os.lib.libstdc.so.6_32 FAIL Unavailable /usr/lib/libstdc++.so.6 os.strings.libstdc FAIL Unavailable /usr/lib/libstdc++.so.6: GLIBCXX_3.4.6
Workaround: To work around this problem,restart the installation using the twsinst script with the -skipcheckprereq parameter.
- 178681: JobStream re-submission does not work when the original job stream containing the start condition is defined on a workstation class
- If you define a job stream for a workstation class specifying a start condition, you must select the Start Once option.
- 177195: supported number of concurrent filemonitor commands
- If you plan to run hundreds of job streams containing start conditions on the same agent, you might want to take into consideration the resource overhead due to the filemonitor process.
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
+---9.4.0-IBM-IWS-DWC-README-FP0007.zip
|
+---9.4.0-IBM-IWSDOCKER_X86_64_AGENT-FP0007.zip
|
+---9.4.0-IBM-IWS-AIX-FP0007.zip
|
+---9.4.0-IBM-IWS-HPIA64-FP0007.zip
|
+---9.4.0-IBM-IWS-LINUX390-FP0007.zip
|
+---9.4.0-IBM-IWS-LINUXPPC-FP0007.zip
|
+---9.4.0-IBM-IWS-LINUX_X86_64-FP0007.zip
|
+---9.4.0-IBM-IWS-SOLARIS_I386-FP0007.zip
|
+---9.4.0-IBM-IWS-SOLARIS_AGENT-FP0007.zip
|
+---9.4.0-IBM-IWS-SOLARIS_ZOS_AGENT-FP0007.zip
|
+---9.4.0-IBM-IWS-WINDOWS_X86_64-FP0007.zip
|
+---9.4.0-IBM-IWS-AIX_AGENT-FP0007.zip
|
+---9.4.0-IBM-IWS-HPIA74_AGENT-FP0007.zip
|
+---9.4.0-IBM-IWS-IBM_I_AGENT-FP0007.zip
|
+---9.4.0-IBM-IWS-LINUXPPC_LE_AGENT-FP0007.zip
|
+---9.4.0-IBM-IWS-LNX_PPC_AGENT-FP0007.zip
|
+---9.4.0-IBM-IWS-LNX_S390_AGENT-FP0007.zip
|
+---9.4.0-IBM-IWS-LNX_X87_74_AGENT-FP0007.zip
|
+---9.4.0-IBM-IWS-SOL_I386_AGENT-FP0007.zip
|
+---9.4.0-IBM-IWS-WIN_X86_64_AGENT-FP0007.zip
|
+---9.4.0-IBM-IWS-AIX_ZOS_AGENT-FP0007.tar
|
+---9.4.0-IBM-IWS-HPIA64_ZOS_AGENT-FP0007.tar
|
+---9.4.0-IBM-IWS-IBM_I_ZOS_AGENT-FP0007.tar
|
+---9.4.0-IBM-IWS-LINUXPPC_LE_ZOS_AGENT-FP0007.tar
|
+---9.4.0-IBM-IWS-LNX_PPC_ZOS_AGENT-FP0007.tar
|
+---9.4.0-IBM-IWS-LNX_S390_ZOS_AGENT-FP0007.tar
|
+---9.4.0-IBM-IWS-LNX_X86_64_ZOS_AGENT-FP0007.tar
|
+---9.4.0-IBM-IWS-SOL_I386_ZOS_AGENT-FP0007.tar
|
+---9.4.0-IBM-IWS-WIN_X86_64_ZOS_AGENT-FP0007.zip
Installing the Fix Pack
This section describes how to apply Fix Pack 7 to IBM Workload Scheduler.
- Installation notes
- Interoperability notes
- Disk space requirements
- Installation methods
- Installing IBM Workload Scheduler v9.4FP7 for the first time using the IBM Installation Manager wizard
- Installing the Fix Pack on the IBM Workload Scheduler General Availability version 9.4 using the IBM Installation Manager wizard
- Installing the Fix Pack on an IBM Workload Scheduler version earlier than 9.4 using the IBM Installation Manager wizard
- Installing the Fix Pack using IBM Installation Manager silent installation
- Installing the Fix Pack on agents using the twsinst script
- Uninstalling the entire IBM Workload Scheduler instance
- Installation log files
Installation notes
- Before installing the Fix Pack, ensure you have installed the required prerequisite software. To obtain the latest information about software requirements for IBM Workload Scheduler, run the Software Requirements report and browse to the relevant section.
- Before installing this Fix Pack on IBM Workload Scheduler for z/OS agent, check the Dynamic Workload Console installation notes for the recommended upgrade procedure.
- 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: IZ99634: FUSER -XF DOESNT RETURN RESULTS FOR LOCAL WPAR FS APPLIES TO AIX 7100-01.
- 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)
- If you get an error message indicating permission denied for the installation process, to run a script in the tws_tools directory as a user, different from the root user because this user does not have write, read, and execute rights in this directory, you must:
- Extract the eImages to a directory where all users have write, read, and execute rights.
- Restart the installation process from this directory.
- During the upgrade of the primary domain manager, the installation process attempts to retrieve information from your environment. If the installation fails to perform the retrieve, and you have recently upgraded WebSphere® Application Server to version 8.5.5.4, then you need to stop, start, and stop again, the WebSphere Application Server, and then restart the upgrade installation process for the master.
- When installing the Fix Pack on a Solaris operating system where an Oracle database is used, the installation must be performed using a connection that is not in SSL between the machine where the installation is being performed and the machine where the Oracle database is installed.
- When upgrading the primary domain manager to V9.4 by using Installation Manager, a Java fresh install is required before proceeding with the primary domain manager upgrade. When upgrading the primary domain manager to V9.4, run the following steps:
- Upgrade WebSphere Application Server to V8.5.5.9.
- Perform a fresh install of Java V8.0.2.10.
- Upgrade the primary domain manager to V9.4.
- 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.
- 168833: When installing this Fix Pack on AIX V7.2, ensure that you have WebSphere V8.5.5.8 and DB2 V10.5 Fix Pack 7 installed.
- 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.
- If the IBM Workload Scheduler environment is configured in SSL, it is necessary that localopts "SSL Encryption Cipher" is set to TLSv1.2 before upgrading to: MDM, BKMDM, DDM, or FTA. If "SSL Encryption Cipher" is not used but one of "ssl tls12 cipher" "ssl tls11 cipher" "ssl tls10 cipher" is used, make sure it is set to HIGH before upgrading. 9.4 fix pack7 uses a new version of OpenSSL libraries (1.1.1) that are not compatible with the weaker ciphers in 1.0.0 OpenSSL libraries.
-
- On Windows the following commands do not exist under the: <TWA_HOME>\TWS\_uninstall\ACTIONTOOLS directory.
- backupInstance.cmd and restoreInstance.cmd
You can find backupInstance.cmd and restoreInstance.cmd under IWS images in the following zip file: com.ibm.tws.backups.windows_9.4.x.xxxxxxxxxxxx.zip under TWS/native.
Interoperability notes
IBM Workload Scheduler version 9.4.0 Fix Pack 7 supports all product versions indicated in the IBM Workload Scheduler version 9.4 Release Notes which can be accessed at the following link: http://www-01.ibm.com/support/docview.wss?uid=swg27048863#h3interop_tables.
Disk space requirements
For the most up-to-date information about disk space and memory requirements, generate a dynamic hardware requirements report from the IBM Software Product Compatibility Reports web site at the following URL: http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/hardwareReqsForProduct?deliverableId=196702D00EBC11E58BF1AF9D8B1D437A&osPlatforms=AIX|HP|IBM%20i|Linux|Solaris|Windows|z/OS&duComponentIds=S002|S001|A005|A003|A004.
<TWA_HOME>/TWS + <TWA_HOME>/TDWB + <TWA_HOME>/wastools + <TWA_HOME>/properties
Operating System | Installation directory | Temporary directory |
---|---|---|
AIX | 2,5 GB | 1,5 GB |
HP-UX | 2,5 GB | 1,5 GB |
Solaris | 1.5 MB | 800 MB |
Microsoft Windows | 2 GB | 1 GB |
Linux | 1,5 GB | 800 MB |
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 |
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 |
Installation methods
- For primary domain manager or dynamic domain manger or their backups:
-
- Installing IBM Workload Scheduler v9.4FP7 for the first time using the IBM Installation Manager wizard
- Installing the Fix Pack on the IBM Workload Scheduler General Availability version 9.4 using the IBM Installation Manager wizard
- Installing the Fix Pack on an IBM Workload Scheduler version earlier than 9.4 using the IBM Installation Manager wizard
- Installing the Fix Pack using IBM Installation Manager silent installation.
- For fault-tolerant agent, dynamic agent or domain manager:
Before Installing
- Unlink the host on which you are installing the Fix Pack from the network.
- Shut down IBM Workload Scheduler.
- Run the following commands, depending on your configuration:
- primary domain manager or dynamic domain manger or their backups:
-
- On Windows operating systems:
-
conman "unlink @; noask" conman "stop; wait" conman "stopmon;wait" ShutDownLwa.cmd stopServer.bat
- On UNIX and Linux operating systems:
-
conman "unlink @; noask" conman "stop; wait" conman "stopmon;wait" conman "shut;wait" ShutDownLwa ./stopServer.sh
- Fault-tolerant agent or domain manager:
-
- On Windows operating systems:
-
conman "unlink @; noask" conman "stop; wait" conman "stopmon;wait" ShutDownLwa.cmd
- On UNIX and Linux operating systems:
-
conman "unlink @; noask" conman "stop; wait" conman "stopmon;wait" conman "shut;wait" ShutDownLwa
- IBM Workload Scheduler for z/OS agent or IBM Workload Scheduler dynamic agent:
-
- On Windows operating systems:
-
ShutDownLwa.cmd
- On UNIX and Linux operating systems:
-
ShutDownLwa
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 .
- Delete the content of the following directory: <TWA_HOME>/TWS/ITA/cpa/temp/ipc, where <TWA_HOME> is the IBM Workload Scheduler installation directory.
- 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 IBM Workload Scheduler for z/OS 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, manually create the SQL database tables following the procedure in the Planning and Installation guide that best suits your environment. To update or upgrade the database schema, follow the directions in this section.
- primary domain manager or backup primary domain manager:
-
- IBM Workload Scheduler tables
- Dynamic workload broker tables.
- Dynamic domain manager or backup dynamic domain manager:
- Dynamic workload broker tables.
For a DB2 or Oracle database, the database tables can be created or upgraded at the same time as when you install or update the product component using either the Installation Manager wizard or the silent installation, or you can choose to create or update the database tables manually, and then install and update the component at a later time. For Informix® Dynamic Server and Microsoft SQL Server databases, the database tables must be created or updated manually, before installing the product.
Creating the database tables for DB2 and Oracle
About this task
- DB2
- Creating the IBM Workload Scheduler and the dynamic workload broker database tables involves the following high-level steps:
- Customize the properties file.
- Generate the SQL files.
- Create the SQL tables.
- Oracle
- Creating the IBM Workload Scheduler and the dynamic workload broker database tables involves the following high-level steps:
- Customize the properties file.
- Generate the SQL files.
- Create the SQL tables.
Updating or upgrading the database schema for DB2 or Oracle
Starting with the previous Fix Pack, a new method for updating and upgrading the IBM Workload Scheduler and the dynamic workload broker database schema is provided for DB2 and Oracle databases. The update or upgrade can be performed manually before you install the product component Fix Pack or, using the Installation Manager wizard or silent installation, the schema is updated during the Fix Pack installation procedure.
Before you begin
About this task
- Modify the upgradeDB2IWSDB.properties or the upgradeOracleIWSDB.properties file assigning the appropriate values to the parameters.
- Run the launchUpgradeIWSDB.bat or the launchUpgradeIWSDB.sh script to generate and apply the SQL statements. Optionally, you can choose to only generate the statements and apply them later, but before installing the product component Fix Pack.
To update or upgrade the IBM Workload Scheduler and the dynamic workload broker database tables, run the following procedure:
Procedure
What to do next
Creating and upgrading the database tables for Informix and Microsoft SQL
Create or update the database tables manually before installing the product.
About this task
- Informix Dynamic Server
- Creating the IBM Workload Scheduler and the dynamic workload broker database tables involves the following high-level steps:
- Customize the properties file.
- Generate the SQL files.
- Create the SQL tables.
- Microsoft SQL Server
- Creating the IBM Workload Scheduler and the dynamic workload broker database tables involves the following high-level steps:
- Customize the properties file.
- Generate the SQL files.
- Create the SQL tables.
Extract the eImages for the IBM Workload Scheduler for z/OS Agent and Dynamic Agent on IBM i operating systems
- 9.4.0-IBM-IWS-IBM_I_ZOS_AGENT-FP0007.tar: The IBM Workload Scheduler for z/OS Agent on IBM iimage.
- 9.4.0-IBM-IWS-IBM_I_AGENT-FP0007.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 Workload Scheduler for z/OS Agent
- "tar xvf 9.4.0-IBM-IWS-IBM_I_ZOS_AGENT-FP0007.tar"
- Dynamic agent
- "unzip 9.4.0-IBM-IWS-IBM_I_ZOS_AGENT-FP0007.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 9.4.0-IBM-IWS-IBM_I_AGENT-FP0007.zip file, or untar the 9.4.0-IBM-IWS-IBM_I_ZOS_AGENT-FP0007.tar.
Installing IBM Workload Scheduler v9.4FP7 for the first time using the IBM Installation Manager wizard
- Complete the actions described in section Before Installing.
-
Download the IBM Workload Scheduler version 9.4 General Availability eImage from http://www.ibm.com/software/passportadvantage/ specific for the operating system and extract it into a path of your choice
-
Download the TAR or ZIP file specific for the operating system from http://www.ibm.com/software/passportadvantage/ and extract it. To extract the .tar file, ensure that you use the GNU version of the TAR command. Otherwise, if you extract the file using a version other than GNU, your fix pack installation fails. If you are installing on a UNIX operating system, run the following command:
chmod -R 755 <imagesDir>
- Depending on the type of operating system, run the following command:
- On Windows operating systems:
- From the directory where you extracted the files, run setupTWS.cmd -gapath <extraction_path>.
- On UNIX and Linux operating systems:
- From the directory where you extracted the files, run setupTWS.sh -gapath <extraction_path>.
The IBM Installation Manager window opens.
- Select the packages you want to install and the click Next to continue.
- In the Validating Results page, check that all the prerequisites are fulfilled and then click Next to continue.
- In the Licenses page, read the license agreement for the selected package. If you agree to the terms of all the license agreements, click I accept the terms in the license agreements and then click Next.
- In the Install Packages page, type the directory where you want to install the product and then click Next to continue.
- In the Features page, select the IBM Workload Scheduler features:
- primary domain manager
- dynamic domain manager
- Complete the available fields in the following panels:
- For primary domain manager
-
- User information
- Primary configuration
- Database configuration
- WebSphere profile configuration
- WebSphere ports configuration
- Disk space check
- For dynamic domain manager
-
- User information
- Dynamic domain manager configuration
- Database configuration
- WebSphere profile configuration
- WebSphere ports configuration
- Disk space check
- In the Summary page, review your choices before upgrading the product package. To change any choices that you made on previous pages, click Back and make the changes. When you are satisfied with your installation choices, click Install to install the packages.
- Ignore any request to create the WebSphere Application Server administrator user.
- Click Finish to complete the installation.
Installing the Fix Pack on an IBM Workload Scheduler version earlier than 9.4 using the IBM Installation Manager wizard
Before you begin
- Linux and Solaris: LD_LIBRARY_PATH. For example:
export ORACLE_HOME=/oracle/app/oracle/product/12.1.0/dbhome_1 export LD_LIBRARY_PATH=/oracle/app/oracle/product/12.1.0/dbhome_1/lib
- AIX: LIBPATH
- HP-UX: SHLIBPATH
- Windows: PATH
About this task
Procedure
Installing the Fix Pack on the IBM Workload Scheduler General Availability version 9.4 using the IBM Installation Manager wizard
Before you begin
- Linux and Solaris: LD_LIBRARY_PATH. For example:
export ORACLE_HOME=/oracle/app/oracle/product/12.1.0/dbhome_1 export LD_LIBRARY_PATH=/oracle/app/oracle/product/12.1.0/dbhome_1/lib
- AIX: LIBPATH
- HP-UX: SHLIBPATH
- Windows: PATH
About this task
Procedure
Results
An error occurred while restoring the IBM Workload Scheduler instance
from the backup, located in the folder <backup_folder>
where <backup_folder> is the folder where the IBM Workload Scheduler backup files are located.
- Check that you have right permissions for the IBM Workload Scheduler installation path, that there is enough disk space, and that no process is locking the files located in the IBM Workload Scheduler installation path.
- Access the <backup_folder> and remove the folders with the same names as those located in the IBM Workload Scheduler installation folder.
- Copy all the folders from the <backup_folder> to the IBM Workload Scheduler installation folder.
- Rerun the Fix Pack installation steps.
Installing the Fix Pack using IBM Installation Manager silent installation
Apply the Fix Pack using the Installation Manager silent installation method.
Before you begin
- Supported operating system.
- Sufficient RAM.
- Sufficient swap file space.
- Disk space for the creation of the installation and temporary directories passed in input to the script.
- On Windows operating systems:
- Run the following command:
iwsPrereqCheck.bat -instdir <TWA_HOME> -tmpdir <tmp>
- On UNIX or Linux operating systems:
- Run the following command:
iwsPrereqCheck.sh -instdir <TWA_HOME> -tmpdir <tmp>
- <TWA_HOME>
- Represents the product installation directory.
- <tmp>
- Represents the temporary folder on the system where you are running the installation.
About this task
<server>
<!-- The IBM Workload Scheduler repository. -->
<!-- Insert the value of the directory where you downloaded the
IBM Workload Scheduler image. -->
<repository location='/tmp/Images/TWS94ga/TWS/disk1'/>
<!-- Define the location where you store the current IBM Workload Scheduler
fixpack eImages -->
<repository location='/tmp/Images/TWS94fp7/TWS'/>
</server>
- Open the Preferences panel in Installation Manager.
- From the Repositories page, select and remove the repository location in error.
- Correct the repository location in the response file.
- Rerun the silent installation.
Response File Name | Description | Required Images | |||
---|---|---|---|---|---|
9.4 GA | 9.4 FP7 | Installation Manager | WebSphere Application Server | ||
IWS94_UPDATE_<component_name>
_from94_<os_name>.xml |
This response file applies the Fix Pack to version 9.4 component bringing it to the 9.4 FP7 level. | ✓ | ✓ | ||
IWS94_UPGRADE_<component_name>
_from9x_<os_name>.xml |
This response file upgrades a version 9.1 or 9.2 component to the 9.4 FP7 level. | ✓ | ✓ | ||
IWS93_UPGRADE_<component_name>
_from86_<os_name>.xml |
This response file upgrades a version 8.6 component to the 9.4 FP7 level. | ✓ | ✓ | ||
IWS93_UPGRADE_<component_name>
_from851_<os_name>.xml |
This response file upgrades a version 8.5.1 component to the 9.4 FP7 level. | ✓ | ✓ | ||
IWS94_FRESH_<component_name>
_<os_name>.xml |
This response file performs a fresh installation of the version 9.4 GA product plus Fix Pack 7. Use this installation if you have WebSphere Application Server and Installation Manager already installed. | ✓ | ✓ | ||
IWS94_FRESH_FULL_<component_name>
_<os_name>.xml |
This response file performs a first time fresh installation of the version 9.4 GA product, Fix Pack 7, WebSphere Application Server, and Installation Manager. WebSphere Application Server must be purchased separately. | ✓ | ✓ | ✓ | ✓ |
Name | Description | Permitted Values |
---|---|---|
user.dbJDBCDB2AdminUser | The user name of the administrator of the DB2 server instance. | db2inst1 |
user.dbJDBCDB2AdminPassword | The DB2 administrator password. | For more information about encrypting passwords using Installation Manager, see Encrypting user passwords for response files. |
user.dbJDBCPort | Optional, type the TCPIP port number only if DB2 is configured to use an SSL connection. | 50000 |
user.db2PlanTableSpaceName | The name of the DB2 instance tablespace for storing plan data. | TWS_PLAN |
ser.db2PlanTableSpacePath | The relative path of the DB2 instance tablespace for storing plan data. Only for upgrades from IBM Workload Scheduler versions 8.5.1 and 8.6. | TWS_PLAN |
Name | Description | Permitted Values |
---|---|---|
user.dbJDBCOraclePassword | The Oracle IBM Workload Scheduler user that accesses the IBM Workload Scheduler schema. | For more information about encrypting passwords using Installation Manager, see Encrypting user passwords for response files. |
user.oraclePlanTableSpace | The name of the tablespace for storing plan data. | USERS |
Procedure
After installing the Fix Pack
After you have installed the Fix Pack for the primary domain manager or backup domain manager, create the event and the event rules related to the centralized agent update feature. This procedure enables you to monitor future updates of fault-tolerant and dynamic agents using the centralized agent update method.
Before you begin
About this task
Procedure
What to do next
Installing the Fix Pack on agents using the twsinst script
- To show command usage:
-
- On Windows operating systems:
-
cscript twsinst.vbs -u | -v
- On UNIX and Linux operating systems:
-
./twsinst -u | -v
- To install a Fix Pack:
-
- On Windows operating systems:
-
cscript twsinst -update -uname TWS_user -password user_password [-domain user_domain] [-inst_dir installation_dir [-recovInstReg {true | false}]] [-wait <minutes>] [-lang <lang_id>]
- On UNIX and Linux operating systems:
-
./twsinst -update -uname TWS_user [-inst_dir installation_dir [-recovInstReg {true | false}]] [-wait <minutes>][-lang <lang_id>]
- -update
- Upgrades an existing agent that was installed using the twsinst script.
- -uname TWS_user
- The name of the user for which IBM Workload Scheduler is upgraded.
- -password user_password
- Windows operating systems only. The password of the user for which you are upgrading IBM Workload Scheduler.
- -domain user_domain
- Windows operating systems only. The domain name of the IBM Workload Scheduler user. The default is the name of the workstation on which you are upgrading the product.
- -inst_dir installation_dir [-recovInstReg true | false ]
- The name of the directory where you installed IBM Workload Scheduler. When installing the Fix Pack the inst_dir parameter is used:
- If the installation process cannot retrieve the product installation location from the registries.
- If you need to re-create the IBM Workload Scheduler registries again before the Fix Pack installation. Set the value of recovInstReg to true if you want to re-create the registry files while performing a Fix Pack installation on a fault-tolerant agent.
- -wait minutes
- The number of minutes that the product waits for jobs that are running to complete before starting the Fix Pack installation. If the jobs do not complete during this interval the installation process does not proceed and an error message is displayed. Valid values are integers or -1 for the product to wait indefinitely. The default is 60.
- -lang lang_id
- The language used for the twinst messages displayed. The default is the value of the system variable LANG. If the language catalog for the value you specified is missing, the default C language catalog is used.
twsinst for Windows is a Visual Basic Script (VBS) that you can run in CScript and WScript mode. The IBM Workload Scheduler user is automatically created. The software is installed by default in the IBM Workload Scheduler installation directory. The default value is %ProgramFiles%\IBM\TWA. If you enabled the Security Warning, a dialog box is displayed during the installation. In this case, answer Run to continue.
- Run twsinst with the options you need for your Fix Pack installation scenario.
- On IBM i operating systems, if you are installing the Fix Pack on a IBM Workload Scheduler for z/OS Agent or a IBM Workload Scheduler Dynamic Agent, after you complete the actions described in the section Extract the eImages for the IBM Workload Scheduler for z/OS Agent and Dynamic Agent on IBM i operating systems, run the twsinst script from the QSH shell.
-
When the agent upgrade completes, if your agent is a fault-tolerant agent, you have to restart all the IBM Workload Scheduler processes and services, with exception of netman that restarts automatically.
- On Windows operating systems:
mailman, batchman, writer, jobman,stageman, JOBMON, tokensrv, batchup, monman
- On UNIX operating systems:
mailman, batchman, writer, jobman, JOBMAN, stageman, monman.
- On Windows operating systems:
Installing the Fix Pack on multiple fault-tolerant and dynamic agents
You can install Fix Packs for multiple fault-tolerant agent and dynamic agent instances, by downloading a package on the primary domain manager workstation and updating the multiple agent instances by running an action from the Dynamic Workload Console. You can also schedule the centralized update of multiple agent instances, by using the Dynamic Workload Console or the command line.
Before you begin
In the primary domain manager Security file, you must have manage authorization for all the agent workstations for TWS_master_user, root, or Administrator users. If your primary domain manager is a version 9.3.0 or later fresh installation, the authorization role is automatically added to the Security file. If your primary domain manager is an upgraded version 9.3.0 or later instance, you must manually add the authorization. For more information about the manage keyword usage, see the Object type - cpu topic in the IBM Workload Scheduler Administration. For an example of a primary domain manager Security file, see topic about the security file on the primary domain manager to install Fix Pack or upgrade fault-tolerant agents and dynamic agents in the IBM Workload Scheduler Administration.
About this task
Procedure
Results
- Check the operator log messages console:
- Click The following event rules are triggered:
- UPDATESUCCESS
- When the workstation is successfully updated
- UPDATEFAILURE
- When an error occurs
- UPDATERUNNING
- With the information about the update process status
and check the messages related to the agent workstation update.
- Check the workstation version changes:
- After the next plan update, in the Monitor Workstations view of the Dynamic Workload Console, you can check the updated version in the Version column of the selected agent. Otherwise, if you do not want to wait for the next plan update to see the updated version, run the command JnextPlan -for 0000 with the -noremove option.
- On Windows operating systems:
- <TWA_home>\TWS\logs\centralized_update.log
- On UNIX operating systems:
- <TWA_home>/TWS/logs/centralized_update.log
Rolling back a primary domain manager installation
This topic describes how to roll back a primary domain manager to a previous Fix Pack level or release.
Before you begin
About this task
The rollback procedure is supported for a primary domain manager that was installed using IBM Installation Manager. When upgrading the primary domain manager, the installation also upgrades the database. After the rollback procedure, the database remains at the newer Fix Pack level or release and is not rolled back. It is still compatible with the primary domain manager at the previous level.
You can revert back to an earlier version of an installed Fix Pack or release on the primary domain manager by performing the following rollback procedure.
Procedure
Results
Uninstalling the entire IBM Workload Scheduler instance
- Primary domain manager or dynamic domain manger or their backups:
- To uninstall using the IBM Installation Manager, see IBM Workload Scheduler.
- Fault-tolerant agent or domain manager:
- To uninstall the entire IBM Workload Scheduler instance, use the twsinst -uninst -uname username command from the TWS_home directory, where username is the name of the user for which the IBM Workload Scheduler agent is uninstalled.
Installation log files
- Log file for primary domain managers, dynamic domain managers, and their backups:
- On Windows operating systems:
-
C:\ProgramData\IBM\InstallationManager\logs\<YYYYMMDD_HHMM>.xml
Note: The folder ProgramData is a hidden folder. - On UNIX and Linux operating systems:
-
/var/ibm/InstallationManager/logs/<YYYYMMDD_HHMM>.xml
- Log file for fault-tolerant agents and dynamic agents:
- On Windows operating systems:
-
%Temp%\TWA\tws9400\ twsinst_<operating_system>_<TWS_user>^9.4.0.n.log
- On UNIX and Linux operating systems:
-
/tmp/TWA/tws9400/ twsinst_<operating_system>_<TWS_user>^9.4.0.n.log
- <operating_system>
- is the operating system running on the workstation where you are applying the Fix Pack.
- <TWS_user>
- is the name of the user for which IBM Workload Scheduler was installed (the name you supplied during installation).
- n
- is the Fix Pack number.
Documentation updates for IBM Workload Scheduler Fix Pack 6 version 9.4.0
The following are documentation updates as a result of the APARs and fixes in this fix pack. All additions or changes to the documentation as a result of previous fix packs have been integrated into the online product documentation available in IBM Workload Automation product information.
- WA-78015 - MONITORING WORKLOAD AUTO-REFRESH HELP SYSTEM DISPLAYS INCORRECT VALUES
- In the Web UI online help, section :
Should be corrected the value of displayed auto-refresh (00:15) in 00:30, because 15 seconds are a not permitted value.
the auto-refresh values are displayed incorrectly. The correct values are 30 to 7200 seconds, instead of 300 seconds.
- WA-79747 - MS VC++ 2005 INSTALLATION IS SHOWN INCORRECTLY IN MANUAL
- In the High Availability Cluster Environments , section: , section: states that MS VC++ 2005 is installed automatically when the enabler is installed, this is incorrect and has now been updated to: Install Microsoft Visual C++ 2005 manually on all nodes. Install Microsoft Visual C++ 2008 manually on remote nodes. To allow you to switch to the other nodes in the cluster, the package must be installed on them as well.
- WA-79747 - CLEARER EXPLANATION REQUIRED FOR WHICH USER MUST BE A MEMBER OF ADMIN GROUP.
- In the Planning and Installation Guide, section: , section: , clearer explanation explains required rights about the user who performs installation and TWS admin user separately. TWS admin user needs to be a member of administrative group.
- WA-79747 - AUTOMATION PROCESS NOT RUNNING - MONITOR, CHECK FOR UNPLANNED STOP ONLY
- In the User's Guide and Reference, section: , Table 3 has been updated as follows:
TivoliWorkloadSchedulerProcessNotRunning | A specified process is not running.
Note: Only unplanned stop will trigger the event.
|
- WA-80596 - OPENS FILENAME LENGTH IS 120 CHARACTERS INSTEAD OF 145 BYTE
- In the User's Guide and Reference, section:
The combination of the path of the file and the qualifiers cannot exceed 120 characters, and the name of the file cannot exceed 28 characters.
to:The combination of the path of the file and the qualifiers cannot exceed 145 characters, and the name of the file cannot exceed 28 characters.
, the Comments section has been updated from:
- WA-78459 - REQUIREMENTS 121199 AND 121197 IMPLEMENTATION
- In the User's Guide and Reference, section:
filemonitor -path path_to_monitor [-exitOnPathToMonitorNotFound]
to:
filemonitor {-path path_to_monitor | -epath path_to_monitor} [-exitOnPathToMonitorNotFound]
[timeout seconds] (add a blank)
from:[-timeout seconds]
to:
[-timeoutseconds | time_of_the_day][-preserveEventsOnDelete]
The following section has been added:
, the following section have been updated from:
- -epath path_to_monitor
- The path where the files to be processed are located, always specified with slashes (/) as separators. Backslashes (\) are not allowed as separators, even if you are indicating a Windows path. To include more files in the monitoring process, store all the files in the directory set with the -epath argument.
The following syntax rules apply:
- Paths containing blank or special characters must be specified within double quotation marks.
- Wildcard characters question mark (?) and asterisk (*) are supported.
- Any character other than backslash (\), question mark (?), asterisk (*), square brackets ([ ]) or a backslash at the end of the value (\) is intended exactly as it is written. For example, MYpath is not equivalent to mypath.
- Use the syntax [class description] to indicate a single character as follows:
- [range_of_characters]
- A range of characters separated by a minus sign (-). For example, A-B or 1-9.
- [list_of_characters]
- A string of characters. For example, ABC or 1aX.
- The characters exclamation mark (!) and caret (^) are used to reverse the sense. For example, [!A-Z] matches a single character that is not equivalent to any letter from A to Z. [!F] matches any character that is not F.
For example:- -epath /mypath/myp?th/e[!1].txt
- -epath /mypath/my[1-9]path/e[A-Z].txt
- -epath c:/mypath/p?th/e[!1].txt
Documentation updates for IBM Workload Scheduler Fix Pack 7 version 9.4.0
The following are documentation updates as a result of the APARs and fixes in this fix pack. All additions or changes to the documentation as a result of previous fix packs have been integrated into the online product documentation available in IBM Workload Automation product information.
- WA-87103 (IJ17099): Required time format within REST API.EditCommentAssignMoreOp
-
All properties related to time require values in GMT format within REST API as input. Examples of time format: "2019-06-21T09:00:00Z" -> With Z, it is considered as GMT. "2019-06-21T09:00:00" -> Without Z, it is considered as local time. REST API output returns in GMT format, however it returns with “Zâ€.
- WA-87066 (IJ24129): TWA permission files for /tmp folder document
-
In Administration Guide >Data maintenance> Maintaining the file system, the following has been added under the > Temporary files section:
This directory also contains the IBM Workload Scheduler installation files and log files, it is primarily used to handle temporary files that composer CLI creates as a work repository when it is invoked to perform CRUD actions against the IBM Workload Scheduler modeling objects. Directory rights are set to 777 to allow all users running the composer to have access. For security reasons the composer CLI is defined by using the sticky bit, so the files it creates can be owned by users different from the IBM Workload Scheduler installation user. IBM Workload Scheduler conman can be used by any user therefore the folder is 777. If the users eligible to use conman/composer are inserted into the IBM Workload Scheduler group then the permission can be set to 774. In that way, only these users will be able to run conman/composer commands
- WA-87506 (IJ24617): Step 5 "upgrading cluster notes manually" is incorrect
- The High Availability Cluster Environments manual has been updated > IBM Workload Scheduler with Windows cluster >Upgrading agents to a new version and available fix packs >Upgrading cluster nodes manually" paragraph, step #5. The sub-step described at point b. has to be executed from the machine on which the agent was installed the first time only .
- WA-82172 (IJ18328): Step by step SAP upgrade scenario
- The Scheduling Applications with IBM Workload Automation manual has been updated > Integration with SAP > Access method for SAP > Configuring the SAP R/3 environment under the section > Importing ABAP/4 function modules into SAP The following has been added: To uninstall the transport you can use the STMS transaction as shown here:https://help.sap.com/viewer/4a368c163b08418890a406d413933ba7/7.3.20/en-US/a35d2b0cde7211d184800000e8a57770.html
- WA-86831 (IJ23393): Installation procedure for agent on IBMi needs to be reviewed for installation on systems with not English locale
- In the Planning and Installation Guide > Chapter 13 > Installing agent on IBM i systems > About this task, the following step has been added at Step 6 (that will become step 7):
-
If your machine's primary language is other than English, carry out these steps:
- Add English as secondary language.
- Ensure that when connecting to the environment the Host Code-Page is set to 037
- Before starting the installation, verify that the Qshell session is configured correctly and type the following command in the <yorfilename> :
echo " key key2 " | sed 's/ *$//g' | sed 's/[ *//g'
- Run the <yorfilename>
- The environment is configured in the correct way if the output is: "key key2".
-
- WA-88578 - How to configure the DWC 9.5.x to use Single Sign-On with a 9.4.x in Admin Guide
- A new section has been created in the Administration Guide showing the steps on >How to configure the Dynamic Workload Console 9.5.x to use Single Sign-On with a 9.4.x engine (master domain manager). You can find the new section here:https://www.ibm.com/support/knowledgecenter/SSGSPN_9.5.0/com.ibm.tivoli.itws.doc_9.5/distr/src_ad/awsadtdwcSSOenable.htm
- WA-90210 (IJ28181): Rerun job is not launched after recovery job failed
- In the User's Guide and Reference >Defining objects in the database >Defining scheduling objects> section > Next Job definition, after "You can specify the recovery job's workstation if it is different from the parent job's workstation..." the following has been added: Note: It is important that both workstations are on full status..
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: http://www.ibm.com/software/support
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
- 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 Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
US
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.
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.
Portions of this code are derived from IBM Corp. Sample Programs.
© Copyright IBM Corp. _enter the year or years_.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.
IT Infrastructure Library is a Registered Trade Mark of AXELOS Limited.
Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
![]() |
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. |
Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom.
ITIL is a Registered Trade Mark of AXELOS Limited.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Terms and conditions for product documentation
Permissions for the use of these publications are granted subject to the following terms and conditions.
Applicability
These terms and conditions are in addition to any terms of use for the IBM website.
Personal use
You may reproduce these publications for your personal, noncommercial use provided that all proprietary notices are preserved. You may not distribute, display or make derivative work of these publications, or any portion thereof, without the express consent of IBM.
Commercial use
You may reproduce, distribute and display these publications solely within your enterprise provided that all proprietary notices are preserved. You may not make derivative works of these publications, or reproduce, distribute or display these publications or any portion thereof outside your enterprise, without the express consent of IBM.
Rights
Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either express or implied, to the publications or any information, data, software or other intellectual property contained therein.
IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of the publications is detrimental to its interest or, as determined by IBM, these 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.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.
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.
![]() |
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.
Was this topic helpful?
Document Information
Modified date:
21 April 2023
UID
ibm16381668