Release Notes for Tivoli Workload Scheduler, version 8.6

Content

After December 10th 2013, the Tivoli Workload Scheduler installation might fail because the embedded WebSphere Application Server automatically renews the default Tivoli Workload Scheduler certificates. For more information about the steps to perform before installing to avoid the failure, see the following technote: TWS 8.5. 8.5.1 and 8.6 GA release installation failure after December 10th. If you already had the failure, perform the steps described in the technote and restart the installation process. For the 8.6 version, you can avoid performing these steps by downloading from Passport Advantage the 8.6 version available starting from the end of January 2014.

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

• Interoperability tables
• Installation limitations and problems, and their workarounds
• Upgrade notes
• Fix packs
• Software limitations and workarounds
• Globalization notes
• APARS Fixed in this release
• Documentation updates

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

If you are installing a Limited Fault-tolerance agent on IBM i systems, to download the package, see the Tivoli Workload Scheduler download page for the Limited Fault-tolerance agent on IBM i systems.

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.

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:

Tivoli Workload Scheduler: compatibility

Dynamic Workload Console: compatibility

Tivoli Workload Scheduler Command-line client: compatibility

Tivoli Workload Scheduler for Applications: compatibility

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 8.6 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 8.6 and later and now need to upgrade any version of Tivoli Workload Scheduler for Applications up to version 8.4, refer to Tech Note 1384969.

Tivoli Workload Scheduler database, version 8.6: compatibility

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.5.1 database, that you migrated yesterday from version 8.4, cannot be used with a version 8.4 engine that you installed today, but only with a version 8.4 engine that had already been installed prior to the migration. The database can also be used with any version 8.5.1 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.

Software limitations and workarounds

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

On the installation window some buttons seem to disappear if you press next and then back

In the installation window, if you choose Install a new instance, click Next, and then Back, in the previous window you can no longer see the buttons Install a new instance or Use an existing instance.

Workaround:

When you click Back, the two buttons mentioned do not disappear; they are just moved a little further down in the window. You must scroll down to see the buttons again.

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.

Possible heap size problem during installation

If the installation hangs, one possible cause is not enough heap memory. Before running the installation again, you must provide information related to the Java heap memory size. Do the following:

1. Create a file called SETUP.jar in the same directory where the file SETUP.bin is located
2. Open it and write the following lines:
   
   For Window and UNIX operating systems:
   %IF_EXISTS%("INIT_JAVA_HEAP", "@INIT_JAVA_HEAP@1024m")
%IF_EXISTS%("MAX_JAVA_HEAP", "@MAX_JAVA_HEAP@1024m")
   
   For Linux operating systems:
   %IF_EXISTS%("INITIAL_HEAP_SIZE", "@INITIAL_HEAP_SIZE@1024m")
%IF_EXISTS%("MAXIMUM_HEAP_SIZE", "@MAXIMUM_HEAP_SIZE@1024m")


3. Run the installation

(IV12212)

 

In the interactive InstallShield wizard on UNIX® and Linux® platforms, any passwords you enter are not validated at data input

No password validation is performed in the interactive InstallShield wizard on UNIX and Linux platforms at data input. If you make an error in the password, it is only discovered when the installation wizard attempts to use the password during the performance of an installation step.

Workaround:

Rerun the installation, using the correct value for the password.

On Red Hat Enterprise Linux V5.0 the automount feature does not work

On Red Hat Enterprise Linux V5.0, after inserting the DVD and double-clicking the desktop icon, the following message is displayed:

./setup.sh: /bin/sh: bad interpreter: Permission denied

This is because the automount feature that mounts the DVD uses the option -noexec, which is not compatible with how Tivoli Workload Scheduler uses the DVD.

Workaround:

To solve the issue, umount the DVD, and manually remount it, using the following command:

mount /dev/scd0 /media

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.

In a remote silent installation on Windows 64, the installation fails (52485)

During a remote silent installation on Windows 64, the installation fails due to a defect in the InstallShield. On Windows 64, it is not possible to perform a remote Tivoli Workload Scheduler silent installation using a scheduling product.

Workaround:

Use the graphic desktop to install Tivoli Workload Scheduler in silent mode.

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 8.6 (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 (52390)

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.

Upgrade fails on integrated installation of Tivoli Workload Scheduler components on Windows (51013)

On Windows systems, the upgrade fails on an integrated installation of two Tivoli Workload Scheduler components sharing an instance of WebSphere Application Server. In this scenario, two instances of a Tivoli Workload Scheduler component are installed with a different user and one of them is configured in LDAP. The upgrade fails because the WebSphere Application Server service is running.

Workaround:

Stop the WebSphere Application Server service and retry the upgrade.

API: External dependency not added if you specify only JobInPlanKey or JobStreamInPlanKey, and you have enListSecChk=YES (40139)

When performing addJobInstance or addJobStreamInstance on the Tivoli Workload Scheduler Application Programming Interface, the external dependency is not added if the optman parameter enListSecChk is set to YES, and if you specify only the JobInPlanKey or the JobStreamInPlanKey, without specifying the identifier.

Workaround

Specify also the Identifier.

TWSObjectsMonitor events (37786)

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

Loss of information for job types with advanced options (37157)

Job types with advanced options might lose some information when moved to the USERJOBS job stream. As a consequence:

• The job type might be missing or different from the original one.
• The Extra Information section in the job properties is not displayed.
• In the graphical views of Dynamic Workload Console, shadow jobs are not displayed with the typical dots.

When you browse for the joblog of a job, the system might return two or more joblogs (36900)

When you browse for the joblog of a job on:

• Master domain manager and its backup.
• Domain manager and its backup.
• Fault-tolerant agent.
• Standard agent.
• Dynamic domain manager and its backup.

the system might return two or more joblogs. This happens because the operating system assigned the same process identifier for two or more jobs in the same minute (in the same machine).

Incorrect character coding in log files (36154)

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.

Incorrect behavior of database auditing after renaming a job stream that has more than one job stream instance (32001)

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.

Backward compatibility problems with job types with advanced options (defects 22663, 35503, 35505, 35507)

Some job types with advanced options defined in Tivoli Workload Scheduler V8.6 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.

Job definitions are displayed truncated in USERJOBS (27754 )

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

Interoperability problem on Linux platforms

On Linux platforms there are connectivity problems between Tivoli Dynamic Workload Console version 8.6 and earlier Tivoli Workload Scheduler versions configured with the Custom user registry.

The connection does not work because of a missing variable in the configuration of the embedded WebSphere Application Server on Tivoli Workload Scheduler.

If you run Tivoli Workload scheduler version 8.4 (where Custom user registry is the default configuration value on Linux), or if you use PAM authentication, you must expect to experience such connectivity problems with Tivoli Dynamic Workload Console version 8.6.

To check if the Tivoli Workload Scheduler version 8.4 engine on the Linux system is configured based on the Custom user registry, do the following on the master domain manager of the Tivoli Workload Scheduler version 8.4 engine:

1. Run the showSecurityProperties.sh script from <TWS_home>/wastools and check if the value of the activeUserRegistry property is Custom. Also, take note of the value of LocalOSServerREALM.
2. If the value of activeUserRegistry is not Custom, there are no connectivity problems and you need do nothing. If the value is Custom, then you must apply the following workaround on Tivoli Workload Scheduler:
   1. Edit the <TWS_home>/appserver/profiles/twsprofile/config/cells/
      DefaultNode/security.xml file as follows:
      1. Find the activeUserRegistry key. The value is similar to:

         CustomUserRegistry_<series of numbers>
         

      2. Search the userRegistries section of the file, where the value of xmi:id is the same as the value of the activeUserRegistry key.
      3. In the same section, after the LocalOSSserverPassword variable declaration, add the following string:

         realm=LocalOSServerREALM value
         

         where LocalOSServerREALM value is the value you took note of in step 1.

   2. Save the file.
   3. Run stopWas.sh and then startWas.sh from <TWS_home>/wastools to restart the embedded WebSphere Application Server (44551).

File eif.templ is re-created when migrating from version 8.4 GA to version 8.6

When Tivoli Workload Scheduler version 8.4.0 (the General Availability version without the addition of any Fix Pack) is migrated to version 8.6, before the embedded WebSphere Application Server is restarted, the file <TWS_home>/appserver/profiles/twsprofile/temp/TWS/EIFListener/eif.templ is removed and replaced with a new one.

This means that, if you had changed the value of property BuffEvtmaxSize in this file, your changes are lost.

If this happens, you must set the value of this property again in the new version of the file. For details about how to do this, see the section Managing the event processor in the IBM Tivoli Workload Scheduler: Administration Guide . (38971)

Note that the new copy of the file is created in the new path, which is: <TWA_home>/eWas/profiles/TIPProfile/temp/TWS/EIFListener/eif.templ

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.

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 (IZ05400)

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:

   eWAS/profiles/TIPProfile/config/cells/TIPCell
        /nodes/TIPNode/servers/server1

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.

WebSphere Application Server limitations in a pure IPV6 environment when using the Dynamic Workload Console (35681)

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:

$TWS_home/eWAS/profiles/TIPProfile/config/cells/TIPCell
    /nodes/TIPNode/servers/server

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

java.net.preferIPv4Stack=true

Different behavior of UNIX and Windows operating systems at springtime daylight savings (94279)

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

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

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.

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.

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.

Event rule management: Deploy flag is not maintained in renewed symphony (36924)

The deploy flag (D) indicates that a workstation is using an up-to-date package monitoring configuration and can be displayed by running the conman showcpus command. Testing shows that the flag is lost from the symphony file when the file is renewed after a JnextPlan or ResetPlan command. Although the event monitoring configuration deployed to the agents is the latest one, and event management works correctly, an incorrect monitoring agent status is shown on the workstations.

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

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.

Certificates for SSL communication defined at Job Brokering Definition Console startup cannot be modified (52753 / 51957)

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.

WebSphere Application Server cannot be stopped (53173)

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.

SSL V3 Renegotiation vulnerability exposure (53251)

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.

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

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.

 

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

Arabic characters are not correctly displayed using composer and conman (CLI) commands (35394)

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.

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 (34169 )

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.

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

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.

The InstallShield wizard installation fails if DBCS characters are used in the -is:tempdir path or in the TEMP environment variable (36979)

If you are installing using the -is:tempdir option or the TEMP environment variable and you specify DBCS characters in the path, the installation fails.

Workaround:

Do not specify DBCS characters when using this option.

UTF-8 support required when transferring files to and from workstations in non-English locales (34845)

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.

In the output of the composer list and display commands, the list and report headers are in English (22301, 22621, 22654)

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

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 (IY82553, 93843)

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.

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

Workaround:

Enclose the calendar name in double quotes.

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

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.

• IZ82940: CREATE-TRIAL SHOULD NOT BE ALLOWED FROM TWS COMMAND LINE WHEN
  
  
• IZ80500: MAKESEC CORRUPTS SECURITY FILE.
  
  
• IZ81502: SCRIPTS TWS_INST_PULL_INFO.CMD EXITS
  
  
• IZ82455: CONMAN FILTERING ISSUES FOR SS AND SJ COMMANDS WITH DEADLINE AN
  
  
• IZ77651: JOB STREAM STAYS IN READY, AFTER JOBS ARE CANCELLED WITH "PEND"
  
  
• IZ81893: No FIX (change history) available COMPOSER USER SECURITY CONSISTENCY CHECKS NOT BEHAVING THE SAME
  
  
• IZ83265: REP11 DOES NOT SHOW ALL RUNS OF SCHEDULE USING LAST DAY OF
  
  
• IZ82772:MONMAN ISN'T SWITCHING WRITING TO A DIFFERENT FILE EVERY DAY.
  
  
• IZ84698: REPTR -POST VARIES WITH DIFFERENT MAESTRO_OUTPUT_STYLE VALUES
  
  
• IZ86162: NETMAN PROCESS CONSUMING MEMORY ON W2K3 64BIT
  
  
• IZ74359: EVENT IS TRIGGERED BY MONMAN WITH DELAY.
  
  
• IZ84757: Doc change - JBXTRACT DOESN'T EXTRACT FOR THE CORRECT DATES
  
  
• IZ86769: KILL JOB DOES NOT WORK ON 64BIT WINDOWS
  
  
• IZ85790: "XREF -F" COMMAND DOESN'T SHOW FILENAME OF QUALIFIER
  
  
• IZ88122: COMPOSER VALIDATE ERROR AWSBIB043E DUE TO THE WRONG PARSING
  
  
• IZ88104: 9 BYTES OF MEMORY LEAK WITH GETENGINEINFO CALLS
  
  
• IZ89053: WHEN THE NETWORK DEPENDENCY IS CHECKED ON AN HP-UX IA64 SYSTEM
  
  
• IZ86831: JS AT 00:00 IS NOT INCLUDED IN CONMAN SS +STARTED=,HIGHTIME
  
  
• IZ89553:UPDATESTATS JOB ENDS WITH WARNING MESSAGE AWSJPL804W
  
  
• IZ86885: SCHEDULE WITH AT TIME IS LOST WITH JNEXTPLAN -FOR 0000
  
  
• IZ87368: RECOVERY JOB IS LOST BY CONMAN SBS FROM LINUX/WINDOWS, IF THE
  
  
• IZ87209: PATHS CONTAINING THE AMPERSAND "&" ARE NOT BE RECOGNIZED IN TWS
  
  
• IZ73772: AFTER TWS 8.5 FP1 MESSAGE CCGBC0071W WARNING APPEARS WHEN
  
  
• IZ85790:XREF -F" COMMAND DOESN'T SHOW FILENAME OF QUALIFIER
  
  
• IZ90231: COMPOSER REPLACE XML SYNTAX ERROR AWSJCL306E FWK005 PARSE
  
  
• IZ91175: DEPENDENCIES ARE NOT CORRECTLY PROPAGATED IF AT/SCHEDTIME
  
  
• IZ91384: "CONMAN SETSYM" TERMINATES BY SEGMENTATION FAULT.
  
  
• IZ89674: REP11 OUTPUT IS NOT CORRECT, IF TZ="-11", CPU
  
  
• IZ90045: CONFIRM ON CANCELLED JOB BREAKS SUCCESSOR DEPENDENCY
  
  
• IZ89582: FP01 REMOVES ICU**34.DLL LIBRARY FILES CAUSING ICU I18N MESSAGE
  
  
• IZ91629: TWS SWITCHEVENTPROCESSOR ONLY USES 1ST 10 CHARS OF CPUNAME
  
  
• IZ91918: TIMEINTERVAL UNIT ERRORS IN EVENTRULE EXAMPLE IN USER'S GUIDE.
  
  
• IZ92535: AWSBEH021E ERROR WHEN ATTEMPTING TO GENERATE A FORECAST
  
  
• IZ92747: BATCHMAN TERMINATES WITH EXIT CODE 255 WHILE READING SYMPHONY
  
  
• IZ85919: SCHEDULED TIME OF THE PREDECESSOR JOB STREAM IN GMT ON JSC AND
  
  
• IZ92617: WINDOWS CONMAN SBS WITH TZ VARIABLE SET HAS GMT SCHEDTIME
  
  
• IZ91526: IF A JOB HAS "RECOVERY STOP", SUBMITTING A JOB STREAM LOGS
  
  
• IZ93348: CONMAN DOES NOT SELECT A JOB WITH RCCONDSUCC, IF "SCRIPTNAME="
  
  
• IZ93843: TWS 8.4 JOBS ABENDING ON WIN2K3 SERVERS AFTER APPLYING TWS
  
  
• IZ86983: SHOW/CHANGEBROKERSECURITYPROPERTIES NOT WORK IN NON-ENG ENV.
  
  
• IZ94088: SYMPHONY FILE CORRUPTION INTO DEPENDENCY OF A JOB RECORD
  
  
• IZ95290: AFTER A SWITCHMGR ON A DM, A LINK OR OTHER DIRECT EVENT FROM TH
  
  
• IZ92818: JSC WILL NOT SAVE A TASK OF A UNIX COMMAND JOB TO THE DATABASE
  
  
• IZ95353: COMPOSER SHOWS ONLY HOURS WHEN CREATING EVENT RULE
  
  
• IZ86029: PROMPT TEXT BEGIN WITH A COLON (:), REQUIRES INTERVENTION
  
  
• IZ84302: MAKESEC FAILS WITH NTDLL.DLL DURING 8.5.1 INSTALLATION
  
  
• IZ83683: WEBSPHERE CRASH IF BROWSE JOBLOG IN ALTERNATE PLAN
  
  
• IZ81457: E2E LINK PROBLEM FOR FTA WITH DISTRIBUTED CONNECTOR
  
  
• IZ78475: ON APPSERVMAN STOP, IT WRITES INCORRECT MESSAGE TO MERGE LOG
  
  
• IZ77122: TRIAL/FORECAST PLAN WITH MBCS NAME CAN NOT BE ACCESSED FROM
  
  
• IZ84993: "TWSPATCH" FAILS TO CREATE /TMP/TWA/TWS851FIXPACK DIRECTORY
  
  
• IZ85720: TWS 8.5.1 FP1 DID NOT CONTAINS WIN64 FOR FILEWATCH.EXE AND FILE
  
  
• IZ88174: FORECAST PLAN IS CREATED WITH GMT TIME, IF TZ=NO AND CREATED BY
  
  
• IZ88241: CLUSTERINSTANCENAME IS ADDED BY TWSCLUSTERADM.EXE INCORRECTLY
  
  
• IZ95946: TDWB WRONG RESOURCE ALLOCATION CAUSES AWKRAE104E
  
  
• IZ96576: MAKESEC ERROR IF SECURITY FILE HAS CPU ENTRY WITH GROUP KEYWORD
  
  
• IZ87365: TWS 8.5.1 ON AIX DWB JOB FAILS WITH 0403-015 CANNOT ACCESS A
  
  
• IZ94802: THE Z-CENTRIC AGENTS DON'T HANDLE THE RC OF ENDED-IN-ERROR SAP
  
  
• IZ95497: FILE CREATED EVENT RULE DOES NOT TRIGGER OR TRIGGERS MULTIPLE (BLOCKED)
  
  
• IZ96527: IF "ENEVENTPROCESSORHTTPSPROTOCOL=NO", DEPLOYMENT OF EVENTS DO
  
  
• IZ97076: MONMAN PROCESS MEMORY LEAKS
  
  
• IZ96510: FTAs LINK/UNLINK CONTINOUSLY
  
  
• IZ95727: JOBMAN FAILS TO START ON SOLARIS 10U9 X86 (AWSDFF001I)
  
  
• IZ95647: COMPOSER CORE DUMP WITH MAESTROCOLUMNS GREATER THAN 511
  
  
• IZ92887: WAS DOESN'T START UNTIL CRITICAL PATH IS CALCULATED
  
  
• IZ94316: CONMAN SC SHOWS "FTI J" W/O W ON MDM, ALTHOUGH WRITER IS RUNNIN
  
  
• IZ94516: COMPOSER ADD JOBS WITH LARGE INPUT FILE TERMINATES WITH CORE
  
  
• IZ96613: E2E ENVIRONMENT ON HP-UX IA64 DWNLDR FAILS WITH BUS ERROR
  
  
• IZ81897: DWC DOES NOT UPDATE EVENT WHEN A RELATED JOBSTREAM GETS A NAME
  
  
• IZ91819: UNABLE TO CHANGE PRIORITY IN CRITICAL PATH
  
  
• IZ95722: CPU LIMIT ON BROKER CPU IS NOT OBSERVE
  
  
• IZ97908: EVENT RULE IS NOT PROCESSED IF WAS IS BEING RECYCLED
  
  
• IZ99233: EVENT RULE ALLOWS JOB SUBMIT WHEN JOBSTREAM SPECIFIED DOES NOT EXIST
  
  
• IV00401: NETWORK EXTENDED AGENT GIVES ERROR WHEN THE CPU_XA_NAME_NETMTH.OPTS
  
  
• IV00406: BROKER JOB EXECUTED MULTIPLE TIMES
  
  
• IZ70730: BATCHMAN CORE OR STAGEMAN ERROR IF ACCESSING BAD FOLLOWS RECORD
  
  
• IZ63856: ENLISTSECCK NOT ENFORCED ON ALTERNATE PLANS THROUGH DWC OR JSC
  
  
• IZ64003: CENTRALIZED SCRIPTS IN END TO END ENVIRONMENT START AND FAIL
  
  
• IZ65453: TWSMERGE LOG & /STDLIST/ OWNED BY ROOT INSTEAD
  
  
• IZ69965: R11XTR WITH -M OPTION SHOWS THE INCORRECT DATE
  
  
• IZ67385: DWC FILE MONITORING EVENT IS INCORRECTLY SHOWING FILE AS BEING
  
  
• IZ70640: SSM AGENT LOGS ARE CREATED WITH WRITE PERMISSIONS FOR "OTHERS"
  
  
• IZ70630: AT THE END OF DAILY PLAN MANY FTAS DO NOT LINK
  
  
• IZ70415: ADHOC SUBMISSIONS WITH PROMPTS HAVE THE SAME PROMPT NUMBER
  
  
• IZ74028: EVENTS BEING TRIGGERED MULTIPLE TIMES
  
  
• IZ73256: JOB STREAM ID IS DISPLAYED AS JOBSTREAMNAME IN MESSAGE TEXT ON
  
  
• IZ72911: JOBINFO RSTRT_RETCODE COMMAND IN A RECOVERY JOB DOES NOT RETURN
  
  
• IZ72810: TWS spawn incorrectly a new ssmagent each 5 minutes
  
  
• IZ72156: STAGEMAN COMPLETE SYMPHONY CREATION ALSO IF WRONG RECORD INTO
  
  
• IZ72154: UNIXLOCL METHOD DOESN'T PERFORM CHECK OF FILE EXISTENCE IF
  
  
• IZ71230: JOB STREAM CANCEL NOT LOGGED IN PLAN AUDIT
  
  
• IZ69984: DB2 Database locked while making schedule changes
  
  
• IZ74400: DURIG FORECAST PLANERROR AWSJDB803E WITH REASON CODE "68"WHEN
  
  
• IZ71924: JNEXTPLAN NOT DELETING OBSOLETE/COMPLETED JSI FROM PREPRODUCTIO
  
  
• IZ77122: TRIAL/FORECAST PLAN WITH MBCS NAME CAN NOT BE ACCESSED FROM
  
  
• IZ56270: CHANGE THE MIN VALUE OF MAXLEN FROM 14 DAYS TO 8 DAYS
  
  
• IZ76676: DASHBOARD SHOWS JOB IN ABEND ALSO IF IT HAS BEEN RERUN
  
  
• IZ67125: Unable to create the plan with monthly run cycles
  
  
• IZ76066: WAS/EWAS CORES RUNNING PLANMAN/REPTR -POST WHEN CERTAIN
  
  
• IZ68546: ALLOW SCHEDULE IN ADDING STATE TO CARRY FORWARD
  
  
• IZ25976: REPTR TRUNCATES FOLLOWS JOB STREAM NAME
  
  
• IZ71924: JNEXTPLAN NOT DELETING OBSOLETE/COMPLETED JSI FROM PREPRODUCTIO
  
  
• IZ90719: TWS EWAS FAILS AUTHENTICATION WITH LDAP USER IN GROUP WITH
  
  
• IZ91194: TIMESTAMP VALUE OF JOBSTATCHGEVT IS EARLIER THAN ACTUAL TIME
  
  
• IZ86292: JOBLOG RETRIEVAL FOR A Z CENTRIC AGENT NOT POSSIBLE
  
  
• IZ92256: CCLOG WRITES AN ERROR MESSAGE TO STDOUT WHEN THE CURRENT WORKIN
  
  
• IZ80144: FOLLOWS DEPENDENCY NOT HONORED WHEN SCHEDULE WITH "MATCHING
  
  
• IZ94087: JOBMON PROCESS MEMORY LEAKS
  
  
• IZ73578: ONE PREDECESSOR IF SBS WITH FOLLOWS PREVIOUS SELF AND SAME
  
  
• IZ78481: THE SUBMISSION OF DATABASE JOBS WITH THE CMDTYPE SET TO JOB
  
  
• IZ80975: SET 305 (WS LINKED) IN THE BMEVENTS.CONF
  
  
• IZ75038: WHEN USING A MAILMAN SERVER FOLLOWING A CONMAN STOP ON AGENT
  
  
• IZ77386: CONMAN STOP GENERATES SEGFAULT ERROR ON LINUX /VAR/LOG/MESSAGES
  
  
• IZ81173: TWSHOST.SH RETURNS STATUS "DOWN" IF SYMPHONY FILE IS NOT
  
  
• IZ83745: MAILMAN OR BATCHMAN TERMINATES WITH CORE IF OPTIONS=OFF IN
  
  
• IZ83199: TIVOLI_JOB_DATE HOLDS -0032768, IF DELDEP AT ON JOB IS
  
  
• IZ84212: FORMAT OF EVENT 163, 164, 165 IS NOT CORRECT IN FORMAT FILE
  
  
• IZ80015: ABILITY TO SELECT A DIFFERENT VARIABLE TABLE
  
  
• IZ77650: AWSGTW113I IS GARBLED WHEN LANG=JA_JP ON AIX
  
  
• IZ84990: MULTIPLE SENDEVENT FAILS WITH AWSGTW112E ERROR
  
  
• IZ83267: MONTHLY JOB STREAM IS NOT SCHEDULED CORRECTLY
  
  
• IZ81898: SOCKET ERROR INFORMATION IS NO COMPLETE ON JAPANESE ENVIRONMENT
  
  
• IZ80775: TWSCLUSTERADM.EXE ABENDING ON 2008 WINDOWS CLUSTER
  
  
• IZ74400: DURIG FORECAST PLANERROR AWSJDB803E WITH REASON CODE "68"WHEN
  
  
• IZ62551: """AT"" TIME NOT HONORED WHEN ADHOC IS FOR EARLIER TZ THAN MASTER"
  
  
• IZ64931: EDWA: JOBSTATUSCHANGED EVENT RULE IS NOT TRIGGERED FOR FAILED J
  
  
• IZ65928: TWS DB2 INSTALL FAILS IF USER HAS ) SIGN IN PASSWORD
  
  
• IZ66322: JOBMON.EXE START FAIL MSG IF TWSUSER CANNOT OPEN FILE IN TEMP
  
  

Top

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