Release Notes for Tivoli Workload Scheduler, version 9.1

Release notes


Abstract

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

Content

The Release Notes for Tivoli Workload Scheduler, version 9.1 contain the following topics:

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

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

To access the Tivoli Workload Scheduler documentation, see the online Information Center.

A complete list of new or changed functions in this release are documented in the "Overview->Summary of enhancements" section of the information center at the following link: Summary of enhancements.


Interoperability tables

Top

Support at level of older product or component: For all products and components described in this section, the level of support is at that of the older product or component.

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

DA Dynamic agent
DDM Tivoli Workload Scheduler dynamic domain manager or backup dynamic domain manager
DM Tivoli Workload Scheduler domain manager
DWC Dynamic Workload Console
FTA Tivoli Workload Scheduler fault-tolerant agent
MDM Tivoli Workload Scheduler master domain manager or backup master domain manager
TWS Tivoli Workload Scheduler
TWS for Apps Tivoli Workload Scheduler for Applications
TWS for z/OS agent Tivoli Workload Scheduler for z/OS agent

Tivoli Workload Scheduler: compatibility

 

MDM

DDM

DM

FTA

DA
TWS for Apps
TWS for z/OS agent
MDM 9.1
 
9.1, 8.6
9.1, 8.6, 8.5.1, 8.5
9.1, 8.6, 8.5.1, 8.5
9.1, 8.6
8.6, 8.5
9.1, 8.6
DM 9.1
9.1, 8.6, 8.5.1, 8.5
 
 
9.1, 8.6, 8.5.1, 8.5
 
8.6, 8.5
 
FTA 9.1
9.1, 8.6, 8.5.1, 8.5
9.1, 8.6
9.1, 8.6, 8.5.1, 8.5
 
 
8.6, 8.5
 
DA 9.1
9.1, 8.6, 8.5.1
9.1, 8.6
9.1, 8.6, 8.5.1, 8.5
 
 
8.6, 8.5
 
DDM 9.1
9.1, 8.6
 
 
9.1, 8.6, 8.5.1, 8.5
9.1, 8.6
8.6, 8.5
9.1, 8.6
TWS for z/OS agent 9.1
9.1, 8.6
9.1, 8.6
 
 
 
 
 
Note:
You are strongly recommended to maintain all Tivoli Workload Scheduler components at the latest fix pack level.
For versions earlier than 9.1, be aware of Flash alert: Tivoli Workload Scheduler default certificates need to be renewed before December 10 2013, that will require your intervention for some configurations of Tivoli Workload Scheduler.

Dynamic Workload Console: compatibility

 
MDM/DDM/DM 9.1
MDM/DDM
DM/FTA 8.6
MDM/DM/FTA 8.5.1
MDM/DM/FTA 8.5
DWC 9.1
9.1
8.6
8.5.1
8.5
DWC 8.6

8.6
8.5.1
8.5
DWC 8.5.1


8.5.1
8.5
DWC 8.5



8.5
Notes:
  • You are strongly recommended to maintain all Tivoli Workload Scheduler components at the latest fix pack level.
  • With Dynamic Workload Console V9.1 you also install the latest default security certificates, which expire one year after their installation. These certificates are automatically renewed 60 days before their expiration.
  • For versions earlier than 9.1, be aware of Flash alert: Tivoli Workload Scheduler default certificates need to be renewed before December 10 2013, that will require your intervention for some configurations of Tivoli Workload Scheduler.

Tivoli Workload Scheduler Command-line client: compatibility

 

MDM

Command-line client, version 9.1
9.1 *
Command-line client, version 8.6
8.6
Command-line client, version 8.5.1
8.5.1
Command-line client, version 8.5
8.5

* The V9.1 command-line client is installed when you install a fault-tolerant agent and not as a standalone component.

Tivoli Workload Scheduler for Applications: compatibility

 
MDM/DM/FTA
DWC
TWS for Apps
8.6, 8.5, 8.4
9.1, 8.6, 8.5.1, 8.5
9.1, 8.6, 8.5.1, 8.5
Note:
It is recommended that you upgrade Tivoli Workload Scheduler for Applications to the latest fix pack version before upgrading the Tivoli Workload Scheduler engine to version 9.1 and later. This applies to all Tivoli Workload Scheduler for Applications versions up to version 8.5. If you have already upgraded the Tivoli Workload Scheduler engine to version 9.1 and now need to upgrade any version of Tivoli Workload Scheduler for Applications up to version 8.4, refer to Technote 1384969.

Tivoli Workload Scheduler database, version 9.1: compatibility

 
Engine V9.1
Engine V8.6
Engine V8.5, V8.5.1
Database version V9.1 freshly installed
Y
 
 
Database version migrated from V8.6 to V9.1
Y
Y
 
Database version migrated from version V8.5 to V9.1
Y
Y
Y
Note:
A database at any given level can be used only with a freshly-installed engine, if that engine is at the same level as the database. This means, for example, that a version 8.6 database, that you migrated yesterday from version 8.5, cannot be used with a version 8.5 engine that you installed today, but only with a version 8.5 engine that had already been installed prior to the migration. The database can also be used with any version 8.6 engine, whenever installed.

Fix packs released for this version of the product

To find the fix packs released for Tivoli Workload Scheduler, and the Dynamic Workload Console including links to the related readmes files, see the Fixes by version.


Installation limitations and problems, and their workarounds

Top

 

Installation limitations and workarounds

The following are software limitations that affect the installation of Tivoli Workload Scheduler on all platforms:

Unexpected behavior for warning message displayed because of missing software prerequisite package files. (80833)

When running the setup installation for Tivoli Workload Scheduler, the prerequisite software is already selected in the list of installation packages and a message informs you that some of the files related to the prerequisite software cannot be found. If you clear the selection for Tivoli Workload Scheduler while maintaining the prerequisite software selected, the message disappears.

Script file, imLauncherUnix.sh, used only on Linux operating systems, although the file name suggests otherwise.

This internal script is run by the installation process and is not required to be run manually by the user. Although it is run only on Linux operating systems, its name erroneously suggests that it is used for all UNIX platforms.

Parentheses () are not permitted in the Tivoli Workload Scheduler installation path

When installing Tivoli Workload Scheduler, you cannot specify parentheses in the installation path field.

Multiple installations on the same workstation with the same TWSuser cannot exist (52946)

Two installations cannot coexist on the same workstation if they have the same TWSuser name, where one is a local user account and the other is a domain user account.

Workaround:

Install two instances of a Tivoli Workload Scheduler with different TWSuser names.

Error message displayed when you run setupDWC.sh.
The following error is displayed when you run setupDWC.sh:
./setupDWC.sh: line 39: [: =: unary operator expected ./setupDWC.sh: line 39: [: =: unary operator expected ./setupDWC.sh: line 39: [: =: unary operator expected ./setupDWC.sh: line 39: [: =: unary operator expected ./setupDWC.sh: line 39: [: =: unary operator expected ./setupDWC.sh: line 39: [: =: unary operator expected ./setupDWC.sh: line 39: [: =: unary operator expected ./setupDWC.sh: line 39: [: =: unary operator expected ./setupDWC.sh: line 39: [: =: unary operator expected ./setupDWC.sh: line 39: [: =: unary operator expected

Workaround:

The error can be ignored, the installation starts normally.

Dynamic agent fails to start if the path for TWA_HOME is greater than or equal to 53 bytes.
If you try to install a dynamic agent version 9.1 for a user where the value of $HOME is equal to or greater than 53 bytes in length, the agent does not start.
Netcool/OMNIbus System Service Monitor (SSM) agents not supported on IBM ® i systems. (77154)
The Netcool/OMNIbus SSM agent does not start when installed on an IBM i system.
Two instances of the same master domain manager appear to be installed after installing Tivoli Workload Scheduler for Applications version 8.6.
If you install a master domain manager version 9.1 and then install Tivoli Workload Scheduler for Applications version 8.6, then two instances of the master domain manager appear to be installed in Tivoli Workload Scheduler for Applications.

Workaround:

The installation uses the correct instance and ignores the incorrect one.


Installation and upgrade notes

Top
Structure of Sfinal file modified

The structure of the Sfinal file containing the FINAL job stream has been modified to include a new job and a new job stream. In addition to the FINAL job stream, a second sample job stream, FINALPOSTREPORTS, responsible for printing postproduction reports, has been added to the Sfinal file. The FINALPOSTREPORTS job stream includes a job named, CHECKSYNC, that monitors the progress and outcome of the planman resync command. The planman resync command loads the plan data from the Symphony file to the database.

When performing an upgrade from version 8.6 to version 9.1, the FINAL job stream is not replaced, however, the upgrade procedure does place the new FINAL job stream defintion in the file TWA_home/TWS/Sfinal. After performing the upgrade, import the updated Sfinal file into your database. If you customized your old Sfinal file and want to merge the two versions, perform the following steps:

  1. From the composer command line, extract your old Sfinal file to a new Sfinal_definition_file by issuing the command: composer extract Sfinal_definition_file from js=final
  2. Import the new Sfinal file by issuing the command: composer replace Sfinal
  3. Merge the content of the old Sfinal file with the new Sfinal file

Changes to object access in the security file

With version 9.1 of the product, the LIST access keyword has been added to the objects: CALENDAR, USEROBJ, and, PARAMETER in the security file. When the global option "enListSecChk" is set to YES, the LIST permission on these objects must be specified to be able to run queries on these objects.

When performing an upgrade from version 8.6 to version 9.1, if the global option "enListSecChk" is set to YES, then you mjust also modify the security file, adding the LIST permission to the objects: CALENDAR, USEROBJ, and, PARAMETER.

Tivoli Workload Scheduler default certificates expire on February 10, 2014 but must be renewed before December 10, 2013

The default certificates released with Tivoli Workload Scheduler V8.3.0, V8.4.0, V8.5.0, V8.5.1, and V8.6.0 general availability expire on February 10, 2014 but must be renewed before December 10, 2013.

By default, Tivoli Workload Scheduler uses default certificates for secure connections that must be renewed to avoid connection interruption between Tivoli Workload Scheduler components. If you use customized certificates, then check their expiration date periodically.

The following are situations that are affected and action must be taken to renew the certificates before December 10, 2013:

  • A connection between a master domain manager and a dynamic agent, or between a master domain manager and a dynamic domain manager for the following product versions: 8.6, 8.5.1.
  • Connection between a master domain manager and a fault-tolerant agent where SSL is enabled for the following product versions: 8.6, 8.5.1, 8.5, 8.4
  • Dynamic Workload Console and Job Scheduler Console installations.
  • Dynamic feature is used.
  • Tivoli Workload Scheduler API integration is used.
  • SSL on the Tivoli Workload Scheduler network with sample certificates used.
    "nm SSL port" or "nm SSL full port" different from 0 in localopts

Renewing the certificates involves following a procedure in the correct order and completing the entire procedure before the certificate expiration date. The procedure is designed to minimize disruption to your environment. You can choose to use one of the following approaches to renew the certificates:

  • Apply the latest fix pack available for your product version, and run the manual step labelled "Step 2" in the manual procedure that follows.

    OR

  • Perform a manual procedure. The manual procedure is a two-step process:
    Step 1
    Enable components to communicate with those components that already have or will have the new private key by adding the public key to the trustore (running the script, updTurstStoresCerts).
    Step 2
    Replaces the component's private key in the keystore (running the script, updKeyStoresCerts).

Note: See the following flash alert for information about how your end-to-end environment might be affected: Flash alert: Tivoli Workload Scheduler for z/OS default certificates need to be renewed before 10 December 2013.

If you want to upgrade your environment to version 9.1, and your environment contains dynamic agents or fault-tolerant agents with SSL enabled, then follow this procedure to ensure you maintain communication between the components in your environment:

  1. Apply the latest fix pack available for each product version on the master domain manager.
  2. Upgrade the agents to version 9.1.
  3. Before December 10, 2013, either upgrade the master domain manager to version 9.1 or run "Step 2" of the manual procedure.

Upgrading a component to version 9.1 automatically replaces the default certificate with the renewed one for previous releases. The installation of the fix pack plus step 2 of the manual procedure, or the renewal package enables you to maintain the current product version of your components without having to obligatorily upgrade all of them to version 9.1.

Refer to the following table for information about the procedures available for renewing the default certificates:

Procedures for renewing default certificates

 
Procedure
Details
Install fix pack
The following alert contains instructions about accessing the relative fix packs on IBM Fix Central. The readme files that accompany the fix packs contain the necessary information to complete the procedure:
Flash alert: Tivoli Workload Scheduler default certificates expire on 10 February 2014 but must be renewed before 10 December 2013

Dynamic agents/Dynamic domain managers:
V8.6 Fix pack 2
V8.5.1 Fix pack 5

Fault-tolerant agents with SSL enabled:
V8.6 Fix pack 2
V8.5.1 Fix pack 5
V8.5 Fix pack 4
V8.4 Fix pack 7

Download and install package
Renewal packages can be downloaded from IBM Fix Central at the following link: Fix Central

To access the packages:

  1. In Product Group, select Tivoli.
  2. In Select from Tivoli, select Tivoli Workload Scheduler.
  3. In Installed Version, select the appropriate product version.
  4. In Platform>, select the appropriate platform
  5. Click Continue.
  6. Type Certificates in the Text field and click Continue to browse for fixes containing this text.

    The fixes matching your criteria are displayed.

  7. Download the appropriate compressed file, Product_version-TIV-TWA-CERTIFICATES.zip. The zip file contains a document, awscertsmst.pdf, containing the necessary instructions.

Packages are available for all components according to product version.

Upgrade procedure for platforms out of support

To upgrade master domain managers or backup master domain managers running on platforms that are not supported by version 9.1 (such as AIX® 32 bit kernel), run the parallel upgrade procedure on a supported system. Upgrade procedures are described in the IBM Tivoli Workload Scheduler: Planning and Installation Guide (44363).

Direct backup master upgrade modifies the security file

The upgrade of the backup master modifies the security file when centralized security is enabled. In this scenario, the backup master does not work after the upgrade.

Workaround:

Before beginning the backup master upgrade, complete the following steps:

  1. Set the attribute AUTOLINK to OFF for the backup master workstation.
  2. Run JnextPlan -for 0000 to include the backup master workstation changes.
  3. Make a backup of the security file ( /TWS/Security) into a temporary directory.

Run the upgrade and perform the following steps after the upgrade:

  1. Substitute the upgraded security file ( /TWS/Security) with the copy previously backed up in the temporary directory.
  2. Set the attribute AUTOLINK to ON for the backup master workstation.
  3. Make a backup of the security file ( /TWS/Security) into a temporary directory.
  4. Run JnextPlan -for 0000 to include the backup master workstation changes.
(52390)

Software limitations and workarounds

Top
The following are software limitations that affect Tivoli Workload Scheduler, and their workarounds (where available):
FileMonitor events do not work for dynamic agents with multilingual display name

If you create a FileMonitor type event to monitor the creation of a specific file on a dynamic agent workstation specifying a multilingual name, then this event is not monitored. (80372)

Problems when International Date Line West time zone is used.

Tivoli Workload Scheduler is unable to manage the Date Line West time zone. (80881)

Jobs scheduled to run on the day that Daylight Saving Time is switched on, runs at the wrong time.

When working with an Oracle database server, Oracle passes an incorrect timestamp to Tivoli Workload Scheduler resulting in an incorrect run time for a job. (80371)

TWSObjectsMonitor events

TWSObjectsMonitor events are not applicable to the Dynamic Domain Manager type of workstation. (37786)

Incorrect character coding in log files

If you are using Tivoli Workload Scheduler in a locale other than English and want to produce the Tivoli Workload Scheduler logs in your locale, perform the following steps:

  1. Set the TWS_TISDIR and TISDIR enviroment variables to the Tivoli Workload Scheduler installation directory. For example:
    • On Windows operating systems, if Tivoli Workload Scheduler is installed in the %ProgramFiles%\IBM\TWA\TWS directory, set the variables as follows:
      c:\Program Files\IBM\TWA\TWS
    • On UNIX and Linux operating systems, if Tivoli Workload Scheduler is installed in the default directory /opt/IBM/TWA/TWS, set the variables as follows:
      /opt/IBM/TWA/TWS
  2. Set the TWS_TISDIR and TISDIR enviroment variables as a global environment variables.
(36154)
Incorrect behavior of database auditing after renaming a job stream that has more than one job stream instance

If you rename a job stream that has more than one job stream instance with different valid from interval values from the composer command line and if database auditing is enabled, all the instances of the job stream are renamed, but only one instance is recorded in the audit report. (32001)

Backward compatibility problems with job types with advanced options

Some job types with advanced options defined in Tivoli Workload Scheduler V9.1 are not supported on agents at version 8.5.1, Fix Pack 1, even though these job types were introduced with version 8.5.1, Fix Pack 1. This limitation applies to the following job types:

  • j2ee jobs
  • File transfer jobs
  • MSSQL jobs

The remaining job types include additional operations, which vary depending on the job type, to help you define and schedule the job correctly. For example, you can use these job-specific operations to check for the connection to the database when defining a database job or to retrieve a list of the available operations for a web service when defining a web service job. If you try to perform job-specific operations on a dynamic agent, version 8.5.1, Fix Pack 1, an error message is returned because the operations are not supported, but the job can be scheduled correctly. (22663, 35503, 35505, 35507)

Job definitions are displayed truncated in USERJOBS

This problem affects only the display of the job and does not affect the job itself. (27754)

Deploying large numbers of event rules

The rule deployment process (run either automatically or with the planman deploy command) performs slowly when you deploy high numbers of new and changed rules (2000 and more).

Workaround

If you need to deploy large numbers of event rules, there are two actions you can take to improve performance:

Use planman deploy with the -scratch option

To deploy large numbers of rules collectively in an acceptable time limit, use planman deploy with the -scratch option (37011).

Increase the Java heap size of the application server

Increase the Java heap size of the application server, as described in the Scalability section of the Performance chapter in the Administration Guide. The critical point at which you should increase your heap size is difficult to calculate, but consider a deployment of several thousands of rules as being at risk from an out of memory failure.

"Absolute" keyword required to resolve time zones correctly with enLegacyStartOfDayEvaluation set

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. (41192)

Deploy (D) flag not set after ResetPlan command used

The deploy (D) flag is not set on workstations after the ResetPlan command is used.

This is not a problem that affects the processing of events but just the visualization of the flag that indicates that the event configuration file has been received at the workstation.

Workaround

You can choose to do nothing, because the situation will be normalized the next time that the event processor sends an event configuration file to the workstation. (36924)

Alternatively, if you want to take a positive action to resolve the problem, do the following:

  1. Create a dummy event rule that applies only to the affected workstations
  2. Perform a planman deploy to send the configuration file
  3. Monitor the receipt of the file on the agent
  4. When the file is received, delete the dummy rule at the event processor. (36924 / 37851)

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

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. (38017)
Event LogMessageWritten is not triggered correctly

You are monitoring a log file for a specific log message, using the LogMessageWritten event. The message is written to the file but the event is not triggered.

Cause

The SSM agent monitors the log file and sends an event when a new message is written to the log file that matches the string in the event rule. However, there is a limitation. It cannot detect the very latest message to be written to the file, but only messages prior to the latest. Thus, when message line "n" is written containing the string that the event rule is configured to search for, the agent does not detect that a message has been written, because the message is the last one in the file. When any other message line is written, whether or not it contains the monitored string, the agent is now able to read the message line containing the string it is monitoring, and sends an event for it.

Workaround

There is no workaround to resolve this problem. However, note that in a typical log file, messages are being written by one or other processes frequently, perhaps every few seconds, and the writing of a subsequent message line will trigger the event in question. If you have log files where few messages are written, you might want to attempt to write a dummy blank message after every "real" message, to ensure that the "real" message is never the last in the file for any length of time. (33723)

Microsoft® Remote Desktop Connection must be used with "/console" option

If you use the Microsoft Remote Desktop Connection to operate Tivoli Workload Scheduler, you must use it always with the "/console" parameter, otherwise Tivoli Workload Scheduler gives inconsistent results.

The planman showinfo command displays inconsistent times

The plan time displayed by the planman showinfo command might be different from the time set in the operating system of the workstation. For example, the time zone set for the workstation is GMT+2 but planman showinfo displays plan times according to the GMT+1 time zone.

This situation arises when the WebSphere® Application Server Java Virtual Machine does not recognize the time zone set on the operating system.

Workaround:

Set the time zone defined in the server.xml file equal to the time zone defined for the workstation in the Tivoli Workload Scheduler database. Proceed as follows:

  1. Create a backup copy of this file:
    WAS_profile_path/config/cells/
    TWSNodeCell/nodes/TWSNode/servers/server1

    where the default value for WAS_profile_path is TWA_home/WAS/TWSprofile.
  2. Open server1. xml with an editor.
  3. Find the genericJvmArguments string and add:
    genericJvmArguments="-Duser.timezone=time zone"
    where time zone is the time zone defined for the workstation in the Tivoli Workload Scheduler database.
  4. Stop WebSphere Application Server.
  5. Restart WebSphere Application Server.
(IZ05400)
WebSphere Application Server limitations in a pure IPV6 environment when using the Dynamic Workload Console

When you install Tivoli Workload Scheduler, the following WebSphere Application Server variables are initialized as follows to allow communication in a mixed IPV4 and IPV6 environment:

java.net.preferIPV6Addresses=false
java.net.preferIPv4Stack=false
If your configuration requires the use of a pure IPV6 environment, or you have specific firewall configuration settings that block IPV4 packets, the connection between the Tivoli Workload Scheduler master domain manager and the Dynamic Workload console fails.

Workaround:

To establish a connection in this specific environment, you must initialize the variable as follows:

java.net.preferIPV6Addresses=true

by editing the server.xml file in the following path:

WAS_profile_path/config/cells/
TWSNodeCell/nodes/TWSNode/servers/server1/server.xml

where the default value for WAS_profile_path is TWA_home/WAS/TWSprofile.

If, instead, you want to use IPV4 communication exclusively, set:

java.net.preferIPv4Stack=true
(35681)
Different behavior of UNIX and Windows® operating systems at springtime daylight savings

During the springtime daylight savings time change (01:59:59-03:00:00), different operating systems behave differently.

For example,

    Windows

    The command: conman submit job at=02xx is set to 01xx

    HP-UX

    The command: conman submit job at=02xx is set to 03xx

Workaround

Avoid creating jobs that have a start time in the "lost" hour and are due to run on the night of the daylight savings change (a Saturday night in spring).

(94279)
The writer process on a fault-tolerant agent does not download the Symphony® file

If you delete the Symphony file on a fault-tolerant agent, writer should automatically download it when it next links to the master domain manager. However, this does not happen if you launch conman before the file has downloaded.

Workaround

Delete the mailbox.msg file and writer downloads the Symphony file. (22485)

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

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.
(34103)
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.

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.

(53843)
Messages in the TWSMERGE.log file in English are corrupt

Messages in the TWSMERGE.log file in English are corrupt.

Workaround:

On windows, you must set the TWS_TISDIR environment variable at system level and then restart the workstation. (51518)

Certificates for SSL communication defined at Job Brokering Definition Console startup cannot be modified

In the Job Brokering Definition Console, the certificates for SSL communication defined at the Job Brokering Definition Console startup are used during the entire session and cannot be modified until the Job Brokering Definition Console is restarted.

If you want to set the SSL parameters on the dynamic workload broker component connection, you must include your own certificates in the keystore and truststore that are shown in the SSL section. Alternatively, you can change the keystore and truststore that appear on the SSL section with your own certificates and restart the Job Brokering Definition Console to save the updates.

(52753 / 51957)
WebSphere Application Server cannot be stopped

Because the appserverman is down, WebSphere Application Server cannot be stopped using the conman stopappserver command.

Workaround:

Use wastools with the -direct parameter to stop the WebSphere Application Server or, if you want to stop the WebSphere Application Server using conman stopappserver, you must do it BEFORE you run the conman shut command.

(53173)
SSL V3 Renegotiation vulnerability exposure

There is a vulnerability exposure if you are using an SSL/TLS client that connects to a server whose certificate contains a DSA or ECDSA key. This does not affect users with an SSL/TLS client that connects to a server whose certificate uses an RSA key. Verification of client certificates of servers for any key type is not affected.

(53251)
The return code mapping for Tivoli Workload Scheduler jobs that are migrated to broker is ignored

Return code mapping for Tivoli Workload Scheduler jobs that are migrated to broker using the JSDL template is ignored. Any script or command issued with a nonzero return code is considered abended.

Workaround:

Do not use return code mapping for static jobs that are migrated to dynamic job using the JSDL template.

(51582)
On AIX 6.1, batchman process does not correctly recognize the time zone of the local workstation
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 Tivoli Workload Scheduler CPU definition, it is correctly set to the correct timezone. You see in the stdlist log the following message: "10:29:39 24.11.2008|BATCHMAN:AWSBHT126I Time in CPU TZ (America/Chicago): 2008/11/24 04:29 10:29:39 24.11.2008|BATCHMAN:AWSBHT127I Time in system TZ (America/Chicago): 2008/11/24 10:29 10:29:39 24.11.2008|BATCHMAN:+ 10:29:39 24.11.2008|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 Tivoli Workload Scheduler libraries.

Workaround

Export the TZ environment variable before starting Tivoli 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).

(IZ70267)

Globalization notes

Top
This section describes software limitations, problems, and workarounds for globalized versions of Tivoli Workload Scheduler.
Arabic characters are not correctly displayed using composer and conman (CLI) commands

If you are working on a Windows machine and you launch composer and conman commands, the objects defined with Arabic characters are not displayed correctly.

Workaround:

Configure the machine and code pages to display Arabic characters. (35394)

The job output log retrieved from an agent is displayed in the language of the agent and is not translated into the language of the master.

By default, the job output log is displayed in the language of the workstation where it was generated, instead of the language of the workstation where it is displayed. The job output log for remote engines is always in English, because the log is generated on a remote workstation that might use a different language from the language of the master. (34169)

Cannot add dynamic agents with names containing national characters to z/OS pools and dynamic pools

National characters are not supported when adding dynamic agents to a z/OS® pool or dynamic pool. To work around this problem, modify the dynamic agent names using the Dynamic Workload Console, as follows:

  • Log in to the Dynamic Workload Console.
  • Expand Tivoli Workload Scheduler.
  • Select Scheduling Environment -> Design -> List Workstations.
  • Select the agent you want to modify and click Edit.
  • Modify the agent name as necessary.
  • (34446)
UTF-8 support required when transferring files to and from workstations in non-English locales

When transferring files with the FTP job type to and from workstations in locales other than English, ensure that the FTP server supports the UTF-8 command encoding. This is required for supporting any special characters that are present in the commands. (34845)

In the output of the composer list and display commands, the list and report headers are in English

This has been done to avoid a misalignment of the column headers in DBCS versions, which was making it difficult to understand the information. (22301, 22621, 22654)

In the output of the product reports, the report headers are in English

This has been done to avoid a misalignment of the column headers in DBCS versions, which was making it difficult to understand the information.

Data input is shorter in DBCS languages

All information is stored and passed between modules as UTF-8, and some characters occupy more than one byte in UTF-8. For DBCS languages, each character is three bytes long. Western European national characters are two bytes long. Other Western European characters are one byte long. (IY82553, 93843)

On Windows operating systems, you cannot create a calendar with a name containing Japanese characters using the "makecal" command .

Workaround:

Enclose the calendar name in double quotes.

(123653)
On Windows operating systems, the Tivoli Workload Scheduler joblog is created with incorrect characters

You are working in a non-English language environment and you have correctly set the LANG and TWS_TISDIR environment variables. However, the Tivoli Workload Scheduler joblog is created with incorrect characters in the body of the log (the headers and footers of the log are correct).

Workaround

The problem is caused by the code page in use. Windows editors and applications use code page 1252, which is correct for writing text files. However, the DOS shell uses the default code page 850. This can cause some problems when displaying particular characters.

To resolve this problem for Tivoli Workload Scheduler jobs, add the following line to the beginning of the file jobmanrc.cmd on the workstation:

chcp 1252

For further details about the jobmanrc.cmd file, see the section on customizing job processing on a workstation in Tivoli Workload Scheduler: User's Guide and Reference.

It is possible to resolve this problem for all applications on the workstation by using regedit to set the DOS code page globally in the following registry keyword:

HKEY_LOCAL_MACHINE/system/current Control set/
Control/Nls/Code page/OEMCP =1252

You must reboot the workstation to implement the change.

Note:
Microsoft warns you to take particular precautions when changing registry entries. Ensure that you follow all instructions in Microsoft documentation when performing this activity.
(IY81171)
The output of the twsinst command is corrupted
The output for the twsinst command might contain some incorrect characters for Japanese (ja), Traditional Chinese (zh_TW), Korean (ko), and Simplified Chinese environments(zh_CN). (82684)

APARS Fixed in this release


Top
  • 67329: DEVELOP INTERACTIVE JOBS ON WINDOWS 7

  • 67868: SQL OPTIMIZATION

  • 69949:ADD SECURITY LEVEL TO AN FTA: WARNING MESSAGE ABOUT XA

  • 76873: PORTING OF RESOURCECLI: ADDING FAILOVER MANAGEMENT

  • 76874: Porting SQL Optimization Feature

  • 78015: ALIGN REGISTRY BETWEEN AGENT AND MASTER DOMAIN MANAGER

  • 78597: RECREATE REGISTRY FILE recovInstReg for -modify option

  • 79284: CHECK FILE DOES NOT WORK AFTER IV25338

  • IV19053: CONMAN CRASHES WHEN PIPED WITH "MORE" AND LINES=-1

  • IV20855: JOB IS REMOVED FROM JOBSTREAM THAT RUNS ON IGNORED FTA

  • IV20902: OPENS DEPENDENCY TREATING AN ENVIRONMENT VARIABLE INCORRECTLY

  • IV23995: TWS FAILED TO RUN DB2 STORAGE PROCEDURE WHICH INCLUDE OUTPUT PARAMETER

  • IV24925: FILE DETECTION EVENT TRIGGER DOES NOT WORK PROPERLY

  • IV24995: MONITOR OF "RUNNING" STATUS EVENT RULE SEND 2 EMAILS NOT 1

  • IV25204: TIVOLI STORAGE MANAGER JOBS FAIL IF THE TSM OBJECT CONTAINS "\" CHAR

  • IV25338: FILE CHECK FUNCTION HANGS WHEN THE FILE IS ON AN NFS MOUNTED FILE SYSTEM THAT HAS BECOME UNMOUNTED

  • IV26764: "AWSBII005E UNDEFINED PARAMETER" CAUSES NATIVE_STERR.LOG GROWTH

  • IV28167: WINDOWS COMMAND JOB WITH BRACKET "(" GOES IN ABEND

  • IV28639: USERS ARE UNABLE TO RERUN, SUBMIT OR CONFIRM JOBS

  • IV29255: MDM RANDOMLY CRASHES PERFORMING CONCURRENT OPERATION LIKE QUERIES AND SUBMISSIONS

  • IV29269: USERS ARE NOT ABLE TO AUTHENICATE WHEN THE USER IS IN A GROUP WITH MORE THAN 1024 CHARACTERS

  • IV29992: MIGRATE OF TWS INSTALLED OVERr ORACLE PARTITION DOES NOT WORK IF NOT DEFAULT TABLESPACE ( USERS ) IS USED DURING THE GA

  • IV31427: ON SOLARIS THE ITA FAILS TO OBTAIN IP ADDRESS WHEN MULTIPLE IPS ARE USED ON AN INTERFACE

  • IV31916: NET_IF, NET_IF_IPV6 DOES NOT WORK WELL IN CASE OF HOST NAME WITH MORE IPS ADDRESSES

  • IV31950: CANNOT VIEW BROKER JOB LOGS

  • IV32349: Z-CENTRIC AGENT ON UNIX DOES NOT RESPECT THE UMASK

  • IV33046: UNABLE TO CREATE JOBS WITH ADVANCED OPTIONS IN BROKER

  • IV33168: REPORTS SPECIFY INCORRECT START TIMES FOR UNRUN JOBS USING TIMEZONE OF MDM INSTEAD OF FTA

  • IV33256: CHECK REVOCATION PARAMETER NEEDS TO BE SET TO FALSE

  • IV33462: ON LINUX UNISON_JOB ENVIRONMENT VARIABLE INCORRECTLY SET

  • IV33732: PARAMETERS WITH AMPERSAND -&- AND QUOTES -"- ARE NOT RESOLVED

  • IV35337: UNHANDLED EXCEPTION FROM EVTSIZE.EXE

  • IV35486: JOB STREAM ELAPSE TIME IS NOT CORRECT

  • IV35722: TWS HAS SEVERAL WORLD-WRITEABLE (777 PERMISSIONS) THAT ARE NOT ALLOWABLE FOR CUSTOMER'S ENVIRONMENT

  • IV36517: DATABASE JOB EXECUTOR JOBS GO IN FAIL IF THEY EXECUTE A STORED PROCEDURE WITHOUT PARAMETERS WITH ERROR AWKDBE006E

  • IV36727: TWS JOB CANNOT BE CREATED WHEN SAP JOB ID IS ALPHANUMERIC

  • IV37071: "GLOBAL PROMPT" DOES NOT WORK AS EXPECTED

  • IV37443: AWSBHT228W MESSAGES IN TWSMERGE ALTHOUGH THE JOB STREAM ALREADY RAN

  • iv37647: SAMPLE PLUGIN READMAIL DOES NOT WORK WITH POP3 PROTOCOL

  • IV37648: TWS PROCESSES ABEND IF BMEVENTS.CONF EVENTS PARAMETER CONTAINS MORE THAT 50 EVENTS

  • IV37859: DURING DST CHANGE, TWS DOES NOT SWITCH FROM EPOCH SCHEDULING

  • IV76319: DATECALC DOES NOT WORK ON AIX


Documentation updates

Top
All updates to the Tivoli Workload Scheduler documentation that are required for version 9.1 are included in the editions of the publications in the Information Center.

Top

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

Original publication date

2013/6/14

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Workload Scheduler

Software version:

9.1

Operating system(s):

AIX, HP-UX, IBM i, Linux, Linux/390, Solaris, UNIX, Windows, Windows 2003, Windows 2003 server, Windows 2008 server, Windows 64bit, Windows 7, Windows Vista

Reference #:

7038323

Modified date:

2014-02-25

Translate my page

Machine Translation

Content navigation