IBM Support

Release Notes for IBM Workload Scheduler, version 9.4

Release notes


Abstract

This document supplies the release notes for IBM® Workload Scheduler, version 9.4.

Content

The Release Notes for IBM Workload Scheduler, version 9.4 contain the following topics:

To download the appropriate package for your operating system, see the IBM® Workload Scheduler download page.

For detailed system requirements for all operating systems, see the Detailed System Requirements page.

To access the IBM Workload Scheduler documentation, see the online IBM Knowledge Center.

A complete list of new or changed functions in this release are documented in the Summary of enhancements. More information about new features, including helpful demonstrational videos, can be found on the IBM Workload Automation What's New page. See also the V9.4 dedicated playlist on the Workload Automation YouTube channel.

Note: A direct upgrade is supported starting from version 9.x releases to the version 9.4 release. You are strongly recommended to maintain all IBM Workload Scheduler components at the latest fix pack level.

Interoperability tables

Top

The level of support provided for the products and components listed in the interoperability tables covers all the shown versions.

In the tables in this section the following acronyms are used:

DA IBM Workload Scheduler dynamic agent
DDM IBM Workload Scheduler dynamic domain manager or backup dynamic domain manager
DM IBM Workload Scheduler domain manager
DWC Dynamic Workload Console
FTA IBM Workload Scheduler fault-tolerant agent
MDM IBM Workload Scheduler master domain manager or backup master domain manager

IBM Workload Scheduler: compatibility

 

MDM

DDM

DM

FTA

DA

IBM Workload Scheduler Distributed Agent for z/OS

TWS for Apps

MDM 9.4
 
9.4, 9.3, 9.2, 9.1, 8.6
9.4, 9.3, 9.2, 9.1, 8.6
9.4, 9.3, 9.2, 9.1, 8.6
9.4, 9.3, 9.2, 9.1, 8.6
8.6, 9.4
8.6, 9.4
DM 9.4
9.4, 9.3, 9.2, 9.1, 8.6
 
 
9.4, 9.3, 9.2, 9.1, 8.6
 
 
 
FTA 9.4
9.4, 9.3, 9.2, 9.1, 8.6
9.4, 9.3, 9.2, 9.1, 8.6
9.4, 9.3, 9.2, 9.1, 8.6
 
 
 
 
DA 9.4
9.4, 9.3, 9.2, 9.1, 8.6
9.4, 9.3, 9.2, 9.1, 8.6
9.4, 9.3, 9.2, 9.1, 8.6
 
 
 
 
DDM 9.4
9.4, 9.3, 9.2, 9.1, 8.6
 
 
9.4, 9.3, 9.2, 9.1, 8.6
9.4, 9.3, 9.2, 9.1, 8.6
8.6
 

Dynamic Workload Console: compatibility

 
MDM/DDM/DM/FTA
DWC 9.4
9.4, 9.3, 9.2, 9.1
Notes:
  • In order to connect Dynamic Workload Console V9.4 to versions 9.2 and 9.1 of IBM Workload Scheduler engine, see the following "> Technote.

Fix packs released for this version of the product

To find the fix packs released for IBM Workload Scheduler, and the Dynamic Workload Console including links to the related readmes files, see Fix Central.

Information you must know before upgrading.

Top

The following is information you must know before installing or upgrading to IBM Workload Scheduler V9.4. Note that a direct upgrade is supported starting from version 9.x releases to the version 9.4 release.


When upgrading from previous releases, the new Auditing feature causes three changes in the default optman settings.

auditStore
When you upgrade the master domain manager from a previous release, the default value for this global option is changed. The default value is now both. If you customized the default value in the previous release, the value is overwritten with the new value, with the exception of the auditStore option with the DB value assigned. If the auditStore option was set to DB, this value is maintained and is not overwritten.

enDbAudit
When you upgrade the master domain manager from a previous release, the default value for this global option is changed. The default value is now 1. If you customized the default value in the previous release, the value is overwritten with the new value.

enPlanAudit
When you upgrade the master domain manager from a previous release, the default value for this global option is changed. The default value is now 1. If you customized the default value in the previous release, the value is overwritten with the new value.


For IBM Workload Scheduler V9.4, default settings for role-based security model are as follows:

Master domain manager V9.4 fresh install
For master domain manager V9.4 fresh install, the role-based security model is enabled by default (enRoleBasedSecurityFileCreation optman global option is set to yes).

Master domain manager direct upgrade to V9.4
For master domain manager direct upgrade to V9.4, the role-based security model is disabled by default (enRoleBasedSecurityFileCreation optman global option is set to no).

Master domain manager parallel upgrade to V9.4
For the fresh install of a new master domain manager V9.4 configured as backup, the role-based security model is disabled by default (enRoleBasedSecurityFileCreation optman global option is set to no).

For details about the enRoleBasedSecurityFileCreation optman global option, see ">Global options - detailed description.

Dynamic Workload Console V9.4 uses Restful protocol
Dynamic Workload Console V9.4 uses Restful protocol to connect to the server. The default port is changed from 31117 to 31116.

Installation limitations and problems, and their workarounds.

Top

The following are limitations and problems that might affect the installation or upgrade of IBM Workload Scheduler, and their workarounds (when available):


When upgrading the master domain manager to V9.4 by using Installation Manager, a Java fresh install is required before proceeding with the master domain manager upgrade.

When upgrading the master 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 master domain manager to V9.4.

Dynamic Workload Console installation fails on Windows 10 (166339).
Dynamic Workload Console installation fails on Windows 10 if JazzSm is installed in a virtual directory (i.e. C:\Program Files). A pop up appears asking for the credential, to circumvent the problem, insert the JazzSm credentials or install both Dynamic Workload Console and JazzSm in a non-virtual directory.

In a mixed network defining JS EVERY with ONOVERLAP DONOTSTART, fault-tolerant agents might unlink on a random basis.
In a mixed network, where, for example, agents are at version 9.2 and the master or domain manager is at version 9.4, defining JS EVERY with ONOVERLAP DONOTSTART, fault-tolerant agents might unlink on a random basis.

Workaround

The agents link back again automatically or you can enter the link command, as you prefer, however, it is recommended you upgrade the agents before the master is upgraded.

Unexpected duplication of keys in localopts file after agent restore (167236).

After an agent update with the command:
twsinst -restore -uname twsuser -acceptlicense yes
the localopts contains some unexpected duplicated keywords.

Workaround

Delete the duplicated entries from the localopts file.

Upgrading agent instances to V9.4, the old instance backup directory can be overwritten (168271).

During the upgrade, the installation process backups the old instance in the following directory:
<%Temp_Dir%>\TWA\tws9.4.0.00\backup\date\instance_bck\
where date has format ddmmyyyy.

If multiple agent instances are present on the same system, and more instances are upgraded the same day, the backup directory can be overwritten.


For agents V9.1 GA till FP2, V9.2 GA and FP1, and V9.3 GA, jobmanager crashes when connected to Master Domain Manager V9.4 (IV90922).

The installation of Master Domain Manager V9.4 prerequisites WebSphere® Application Server V8.5.5.9 and a level of Java V8.0.2.10 which is not compatible with the Java versions installed on Agents V9.1 GA till FP2, V9.2 GA and FP1, and V9.3 GA.

Workaround

Upgrade the agents as follows:
  • For agents V9.1, contact IBM support for ifix or install V9.1 FP3 when available.
  • For agents V9.2, install V9.2 FP2.
  • For agents V9.3, install V9.3 FP2.

Tivoli Common Reporting Installation fails on Linux for missing prerequisites (130480).

For Linux operating system, Tivoli Common Reporting installation fails for missing prerequisites. The error message is the following:
CRIMA1217E: A problem occurred during the execution of the /opt/IBM/JazzSM/install/reporting_services/tcrWrapperInstall.xml file.

Two defects have been opened to Jazz for Service Management development team (59346 and 59497).

Workaround

To circumvent the problem, install the following libraries:
  • libpng16-16-1.6.13-2.4.1.i586.rpm
  • openmotif-libs-32bit-2.3.4-25.3.x86_64.rpm
  • openmotif-libs-2.3.4-25.3.x86_64.rpm
  • openmotif22-libs-32bit-2.2.4-189.1.x86_64.rpm
  • openmotif22-libs-2.2.4-189.1.x86_64.rpm

Error while opening the TCR administrator panel after a successful installation of the Dynamic Workload Console (131760).

After a successful installation of the Dynamic Workload Console and its prerequisites, trying to open the TCR administrator panel, the following error message is displayed:
Error!
Refresh Edit Minimize Maximize
PF-VAL-6171 Error retrieving metadata for the target fragment.
Details | Retry | Hide this message.
Details
DashboardException
PF-VAL-6171 Error retrieving metadata for the target fragment.

A defect has been opened to Jazz for Service Management development team (59497).

Workaround

To circumvent the problem, rename or remove the following jar file:
BirtAdapterB.jar presente in questo path: /reporting/lib/birt-runtime-2_2_2/ReportEngine/lib

Upgrade from V9.x fails if ipc temporary files are present (111225).

For Unix operating system, during the upgrade from V9.x to V9.4, if there are files or directories in the path
Inst_Dir/TWS/ITA/cpa/temp/ipc, these files or directories are not copied into the backup directory and the upgrade fails.

Workaround

To circumvent the problem, before upgrading to V9.4, perform the following steps:
  • Stop all processes.
  • Check if there are files or directories in the path
    Inst_Dir/TWS/ITA/cpa/temp/ipc and, if any, remove them.
  • Perform the upgrade to V9.4.

Error upgrading from V9.x with an Oracle database. (156227).

When upgrading from V9.x to V9.4 with an Oracle database, 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.

Software limitations and problems, and their workarounds.

Top

The following are software limitations and problems that might affect IBM Workload Scheduler, and their workarounds (when available):

File monitor provider events: older event configurations might stay active on workstations after rule redeployment (34103).

If you deployed rules containing event types from the FileMonitor event provider, and then you redeploy rules that no longer include these file monitoring events, you might find that, despite the new configurations, the local monitoring agents still forward the file monitoring events to the event processor. The event processor correctly ignores these events, accordingly with the new configuration specifications deployed on the server; however, a certain amount of CPU time and bandwidth are needlessly misused.

The status of the local monitoring configuration on the agent is corrected when one of the following occurs:

  • The planman deploy -scratch command is issued
  • The event processing server is restarted
  • Another rule containing an event condition involving the FileMonitor provider is deployed to the agents.

Some data is not migrated when you migrate database from DB2® to Oracle, or to Informix® Dynamic Server, or vice versa. (38017)

Neither of the two migration procedures migrate the following information from the source database:

  • The pre-production plan.
  • The history of job runs and job statistics.
  • The state of running event rule instances. This means that any complex event rules, where part of the rule has been satisfied prior to the database migration, are generated after the migration as new rules. Even if the subsequent conditions of the event rule are satisfied, the record that the first part of the rule was satisfied is no longer available, so the rule will never be completely satisfied.
"Absolute" keyword required to resolve time zones correctly with enLegacyStartOfDayEvaluation set. (41192)

If the master domain manager of your network runs with the enLegacyStartOfDayEvaluation and enTimeZone options set to yes to convert the startOfDay time set on the master domain manager to the local time zone set on each workstation across the network, and you submit a job or job stream with the at keyword, you must also add the absolute keyword to make sure that the submission times are resolved correctly.

The absolute keyword specifies that the start date is based on the calendar day rather than on the production day.

File monitor provider events: if you specify a file path with forward slashes (/) in an event rule definition, on Windows workstations this results in the failed detection of the file. (53843)

This is due to the fact the SSM agent is not currently designed to automatically convert the slash sign to be Windows compatible when running the rule.

Workaround

Use backward slashes when you specify file paths in the definitions of rules that run on Windows systems.

Problems when International Date Line West time zone is used. (80881)

IBM Workload Scheduler is unable to manage the Date Line West time zone (UTC -12).


Batchman fails on V8.6, V9.1 fault-tolerant agents configured with the mailman server process. (96620)

The enAddWorkstation global option is set to "yes" on a V9.4 Master Domain Manager in a mixed version environment. After you successfully install a V9.4 dynamic agent, the batchman process fails on the V8.6, V9.1 fault-tolerant agents that have the mailman server process configured.

The cause is that the dynamic agent workstation is automatically added to the plan of each agent in the IBM Workload Scheduler mixed version network. The batchman process on the V8.6, V9.1 fault-tolerant agents that have the mailman server process configured is unable to manage the broadcast of the IBM Workload Scheduler event that communicates the addition of the dynamic agent to the plan.

To solve this problem, set enAddWorkstation to "no" on the master domain manager to prevent the automatic addition of the dynamic agent workstation in the plan.

On Windows 2012: all cli not supported on Windows power shell. (95772)

On Windows 2012, the IBM Workload Scheduler command lines are not supported in the Windows Power shell. They work only in the traditional shell.

File transfer job submitted on a Windows agent ends in error.

When endpoint protection software is active on a Windows agent workstation, the FTP connection is blocked by Java™. A Java technology bug reporting this issue can be accessed at http://bugs.java.com/bugdatabase/view_bug.do?bug_id=7077696.

The following are software limitations and problems that might affect the Plug-in for Informatica PowerCenter which is included in the IBM Workload Scheduler Version 9.4 installation:

Cannot submit Informatica PowerCenter jobs after a Web Services Hub restart

Following a restart of the Web Services Hub, the Plug-in for Informatica jobs launched from the command line end in FAIL state (Error state in the Dynamic Workload Console) and return the following exception in the job log:

AWKIPC005E Failed to run workflow.
---------------------------------------
Remote Exception
----------------------------------------

To enable the correct submission of plug-in jobs, after restarting the Hub, connect to the Informatica PowerCenter Web Services Hub URL and follow these steps:

  1. In the Navigator pane, expand Web Service -> Batch WebService, and then click Integration WebService.
  2. In the Operations pane, click Try-It from the toolbar.
  3. In the Web Service Operations Navigator pane, click login.
  4. Fill out the form in the right pane, specifying the required information in the UserName, RepositoryName, and Password text fields.
  5. Click Send.
  6. In the SOAP Response pane, copy the value for the SessionId tag.
  7. In the Web Service Operations Navigator pane, click getWorkflowLog.
  8. Paste the value copied previously in the SessionId text field and then enter the required information in the FolderName, WorkflowName, Timeout, and ServiceName text fields.
  9. Click Send.

    You can now submit jobs safely again.

The problem is due to an Informatica Powercenter defect, for which change request 296859 is outstanding. A formal solution to the problem should be provided by the Informatica HotFix that will address this change request.

The following are software limitations and problems that might affect IBM Workload Scheduler access methods and plug-ins included in the IBM Workload Scheduler Version 9.4 installation:

Intercepted jobs cannot be relaunched in a z/OS environment (60698).

The process of defining relaunch criteria and collecting and relaunching intercepted jobs is supported only in distributed environments and not in z/OS environments.

A request to rerun a process chain is made from the Dynamic Workload Console, but the operation is set to start (61976).

Rerunning a process chain from the Dynamic Workload Console where the operation in IBM Workload Scheduler for z/OS is linked to a special resource that is not available results in the operation being set to start.

On AIX 6.1, batchman process does not correctly recognize the time zone of the local workstation (IZ70267)
On AIX 6.1, the batchman process does not correctly recognize the time zone of the local machine that is set to GMT, even if, in the IBM Workload Scheduler CPU definition, it is correctly set to the correct timezone. You see the following message in the stdlist log : "10:29:39 24.11.2015|BATCHMAN:AWSBHT126I Time in CPU TZ (America/Chicago): 2015/11/24 04:29 10:29:39 24.11.2015|BATCHMAN:AWSBHT127I Time in system TZ (America/Chicago): 2015/11/24 10:29 10:29:39 24.11.2015|BATCHMAN:+ 10:29:39 24.11.2015|BATCHMAN:+ AWSBHT128I Local time zone time differs from workstation time zone time by 360 minutes."

Batchman does not recognize the correct time zone because AIX 6.1 uses (International Components for Unicode) ICU libraries to manage the timezone of the system, and these ICU libraries are in conflict with the IBM Workload Scheduler libraries.

Workaround:

Export the TZ environment variable before starting IBM Workload Scheduler to the old POSIX format, for example, CST6CDT . This is an example of a POSIX name convention instead of an Olson name convention (for example America/Chicago). It avoids the new default TimeZone management through the ICU libraries in AIX 6.1, by switching to the old POSIX one (as in AIX 5.x).

APARS Fixed in this release

Top
  • IV74715: AWSJCO016E ERROR IF USER RUNS "COMPOSER VALIDATE" BEFORE RUNNING "COMPOSER ADD" FOR A NEW DYNAMICE POOL DEFINITION.

  • IV89007: EWAS CRASHED DUE TO A SEGMENTATION ERROR.

  • IV89073: EVERY JOBSTREAM AT IS AFFECTED BY SOD TIME.

  • IV88310: TABLESPACE TWS_PLAN KEEP INCREASES.

  • IV83441: PROBLEM WITH TCL USED IN RMSTDLIST.CMD.

  • IV86478: IGNORE THE ALIAS FLAG IF AN ALIAS IS NOT PROVIDED BY THE UI/SBS.

  • IV85855: BATCHMAN IS FAILING WITH ERROR: AWSBCU011E RECORD FROM /OPT/WFA/TWS/TWS/SYMPHONY, RECORD 32768 (RM).

  • IV79081: COMPOSER VALIDATE ERRONEOUSLY GIVING WARNINGS.

  • IV87526: CAN NOT VIEW ANY ARGUMENTS FOR DYNAMIC JOBS BY DWC 9.3.

  • IV87558: TWS 9.3 FP1 AND FP2 UPDATESTATS TAKE A LOT OF TIME TO BE COMPLET ED AND INCREASE TIME EACH DAY IT RUNS.

  • IV87532: DEADLOCK USING FILE DEPENDENDENCIES + MIRRORING.

  • IV87386: SCHEDULE RECALL FORMATTING IN EVENT.LOG FILE (EVENT ID 203) FOR 9.2.0.

  • IV86692: UPDATESTATS JOB ABENDS ON IWS MDM 9.3 FP0001 WITH EXIT STATUS:8 AWSJCS011E JAVA.LANG.NULLPOINTEREXCEPTION.

  • IV86073: NOT POSSIBLE TO RETRIEVE THE JOBLOG OF THE JOBS RUN BY QSECONFR SINCE TWS USER CANNOT MANAGE THE NATIVEOUTNATIVEOUT FILES IN JOB.

  • IV85789: DWC QUERIES/GETS THAT ARE LOCKING ROWS.

  • IV85751: JOBSTATUSCHANGED EVENT RULES WITH A TBSMEVENTFORWARDER ACTION GIVE A STRING INDEX OUT OF RANGE: 128 ERROR WHEN JOBS FAIL.

  • IV85492: Unable to save RCG when using 2 run cycles in same subset with Logical AND.

  • IV85275: SAP JOBS FOR DYNAMIC AGENT REMAINS IN READY STATE CONSUME CPU LIMIT.

  • IV85010: CHANGEPASSWORD.SH DOES NOT UPDATE SOAP.CLIENT.PROPS IN IWS9.3 FP01.

  • IV84256: CONMAN SJ WHEN RUN AGAINST JS CONTAINING JOBS DEFINED ON MULTIPLE CPUS IS SLOW.

  • IV84268: UPDATESTATS POOR PERFORMANCE WITH 9.3/9.3FP1.

  • IV83557: MOVEHISTORYDATA DOES NOT RUN (MANUALLY NEITHER AUTOMATICALLY).

  • IV83084: ASSIGNMENT OF A NULL VALUE TO A NOT NULL COLUMN DURING UPDATE STATS.

  • IV82709: MIRRORING ISSUE. DEADLOCK CAUSED BY "RD" EVENT. ON TWS 9.2 WITH FP02 ON ORACLE DB.

  • IV81646: CANNOT CLOSE SIMULTANEOUSLY MULTIPLE TASKS.

  • IV68989: TDWC ERROR WHEN ACCESSING Z/OS VARIABLE TABLE.

  • IV79949: CAN NOT RETRIEVE /ETC/GROUP, IF GROUP CONTAINS A LOT OF MEMBERS.

  • IV83728: JOBlog archived zip file is readble only for tws user.

  • IV84911: REP11 SHOW INCORRECT SCHEDULE ON END OF MONTH.

  • IV82925: JOB ASSIGNED INCORRECT SECONDARY GROUP(S) WHEN RUNNING DYNAMIC /ZCENTRIC JOBS AS A USER OTHER THAN THE .

  • IV82925: JOB ASSIGNED INCORRECT SECONDARY GROUP(S) WHEN RUNNING DYNAMIC /ZCENTRIC JOBS AS A USER OTHER THAN THE .

  • IV89805: SWITCHPLAN RUNNING TOO LONG WHEN MULTIPLE CROSSDAY DEPENDENCIES ARE IN PLACE.

  • IV90180: PROBLEM WITH RUNCYCLE GROUPS.

  • IV84208: RANDOMLY ON Z-CENTRIC WE GET FOLLOWING MESSAGE: "NO JOBS STARTED UNDER THE SUBMITTED USER COMMAND.

  • IV89149: TWSINST PREREQUISITE CHECKER FAILS STATING SOLARIS 11 IS UNSUPPORTED.

  • IV85511: DWC SHOWS WRONG "ACTUAL START" AND "ACTUAL END" TIMES IN JOB HISTORY.

  • PI38246: TDWC DOES NOT DISPLAY TWSZ MANUALLY HELD JOBS WHEN THOSE JOBS ALSO HAVE PREDECSSORS OR IF WAITING FOR SUBMISSION TIME.

  • IV84891: MOVEHISTORYDATA.SH ENHANCEMENT ON ORACLE: DELETE ROWS IN SET.

  • IV84891: MOVEHISTORYDATA.SH ENHANCEMENT ON ORACLE: DELETE ROWS IN SET.

Documentation updates

Top

All updates to the IBM Workload Scheduler documentation that are required for version 9.4 are included in the editions of the publications in online IBM Knowledge Center.

Globalization notes
In the IBM Workload Scheduler product documentatation in IBM Knowledge Center, the PDF links in the table of contents only download contents in the English language, even if a language different from English is set.
Workaround
Either access the translated PDF content from the topic Product Library in PDF format after setting the language, or copy the PDF link and add the language suffix to the URL.
For example, to download the Application Lab User's Guide in the French language, modify the PDF link as follows: https://www.ibm.com/support/knowledgecenter/SSGSPN_9.4.0/com.ibm.tivoli.itws.doc_9.4/awsalmst.pdf?lang=fr.

Top

© Copyright International Business Machines Corporation 2006, 2016. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

© Copyright HCL Technologies Limited 2016, 2017.

Original publication date

2016/12/9

Document information

More support for: IBM Workload Scheduler

Software version: 9.4

Operating system(s): AIX, HP-UX, IBM i, Linux, Platform Independent, Solaris, Windows

Reference #: 7048863

Modified date: 27 April 2018


Translate this page: