Release Notes for Dynamic Workload Console, version 9.2

Content

The Release Notes for IBM Dynamic Workload Console version 9.2 contain the following topics:

• Interoperability tables
• Fix packs
• Software limitations and their workarounds
• Installation and upgrade limitations and their workarounds
• Graphical views limitations and their workarounds
• Event management limitations and their workarounds
• Reporting limitations and their workarounds
• Globalization Notes
• Documentation Updates
• APAR fixed in this release

Product publications

To download the appropriate package for your operating system, see the Dynamic Workload Console 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.

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:

The following tables are available:

• Tivoli Workload Scheduler: compatibility
• Dynamic Workload Console: compatibility
• Tivoli Workload Scheduler for z/OS: compatibility
• Tivoli Workload Scheduler Command-line client: compatibility
• Tivoli Workload Scheduler for Applications: compatibility
• Tivoli Workload Scheduler database, version 9.2: compatibility

Tivoli Workload Scheduler: compatibility

Dynamic Workload Console: compatibility

Tivoli Workload Scheduler for z/OS: compatibility

Notes:

1. The z/OS connector version must be the same as the Dynamic Workload Console version. When you install Dynamic Workload Console V9.2, the z/OS connector is also automatically installed.
2. The Tivoli Workload Scheduler for z/OS version must be equal to or earlier than the Dynamic Workload Console version.

Dynamic Workload Console	z/OS connector	TWS for z/OS
DWC 9.2	9.2	9.2 9.1 8.6
DWC 9.1	9.1	9.1 8.6 8.5.1 8.5
DWC 8.6	8.6	8.6 8.5.1 8.5
TDWC 8.5.1	8.5.1	8.5.1 8.5
TDWC 8.5	8.5	8.5

Tivoli Workload Scheduler Command-line client: compatibility

	MDM/BKM
Command-line client, version 9.2	9.2*
Command-line client, version 8.6	8.6
Command-line client, version 8.5	8.5
* The V9.2 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.2, 9.1, 8.6, 8.5.1, 8.5	9.2, 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.2. 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.2 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 9.2: compatibility

	Engine V9.2	Engine V9.1	Engine V8.6
Database version V9.2 freshly installed	Y
Database version migrated from version V9.1 to V9.2	Y	Y
Database version migrated from version V8.6 to V9.2	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.1, cannot be used with a version 8.5.1 engine that you installed today, but only with a version 8.5.1 engine that had already been installed prior to the migration. It 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 Fixes by version.

---

Software limitations and their workarounds

Top

 

Software limitations and problems, and their workarounds

This section contains product limitations not resolved with this release of Dynamic Workload Console, and their workarounds (where applicable):

Accessibility issue with the navigation bar (80436)

When using a screen reader to work with the navigation bar, use up and down arrow keys to move among folders and space to open a folder. To open a menu entry, use the right-arrow, as if the navigation bar was a menu with submenus.

 

File duplicated in the Symphony (79383)

You can find a duplicated file in the Symphony when the following behavior takes place: you use conman to define a file dependency from a non existent file, therefore a new file is created. Then, you use the Dynamic Workload Console to define another dependency from the same file. In this case, during the second dependency creation, the file is not recognized as already existent and it is newly created, causing a file duplication in the Symphony.

 

Connection problems with a stopped engine (45685)

Connecting the Dynamic Workload Console to an engine that is not running, you can have some connection problems, even after restarting the engine.
Workaround: Log out from the console and then log in again to solve the problem.

 

SAP queries problem

If you create a new SAP job definition in the Workload Designer, and in the Task tab on the right pane you select BW Infopackage subtype, and you click on the Pick SAP InfoPackage icon to search for a job name, the filters that you can add in the search panel do not work correctly. All the information contained in the R/3 database is displayed if the information you specified does not exist or if you use the wildcard * (asterisk). (43512)

 

Slow performance using Internet Explorer (44158)

Several known problems of memory leaks affecting Internet Explorer might cause decreasing performance while using the Dynamic Workload Console. For this reason the browser can become unstable.
Workaround: To solve the problem, stop and restart the browser. However, this problem is mitigated by using Internet Explorer V9.

 

Run Cycle low performance (43998)

If you have Dynamic Workload Console traces activated on your server, the performance of the Run Cycle Preview is very low.

 

Job definition shows not compatible workstations if connecting to a Tivoli Workload Scheduler master domain manager V8.4 (43222)

If you have the Dynamic Workload Console V8.6 connected to a Tivoli Workload Scheduler master domain manager V8.4 and you manage object definitions, all available workstation lookups do not allow filtering workstations by operating system.

 

You perform a submit from the Dynamic Workload Console and the Tivoli Workload Scheduler Websphere Application Server ends abnormally (40567)

When you perform a submit from the Dynamic Workload Console, the Tivoli Workload Scheduler Websphere Application Server ends abnormally and the following message appears:
AWSUI0796E The specified action cannot be performed.
Reason: AWSJCS011E An internal error has occurred. The error is the following:
"javax.naming.ServiceUnavailableException: A communication failure occurred while attempting to obtain an initial context with the provider URL: "corbaloc:iiop:nc123456.it.ibm.com:31117". Make sure that any bootstrap address information in the URL is correct and that the target name server is running. A bootstrap address with no port specification defaults to port 2809. Possible causes other than an incorrect bootstrap address or unavailable name server include the network environment and workstation network configuration. [Root exception is org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=nc123456.it.ibm.com,port=31117 vmcid: IBM minor code: E02 completed: No]".

Workaround: Specify the value -Xmso512k for the attribute genericJvmArguments in the file /opt/ibm/TWA/eWAS/profiles/jazzsm_profile/config/cells/jazzsm_cell_name/nodes/ jazzsm_node_name/servers/server1/server.xml,
to obtain the following property:

jvmEntries xmi:id="JavaVirtualMachine_1311759672130" verboseModeClass="false" verboseModeGarbageCollection="false" verboseModeJNI="false" initialHeapSize="256" maximumHeapSize="1024" runHProf="false" hprofArguments="" debugMode="false" debugArgs="-Djava.compiler=NONE -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=7777" genericJvmArguments="-Xmso512k" disableJIT="false"

Additional step required for Single Sign-On enablement (37140)

When enabling the Single Sign-On method between Dynamic Workload Console and an engine, before exporting the LTPA token_keys using the manage_ltpa script, create the file in which to export the LTPA token_keys (for example, using the command touch if you are using UNIX operating systems).

 

Authentication problems with LDAP without Single Sign-On configured (37109)

If Dynamic Workload Console version 8.6 and the Tivoli Workload Scheduler engine version 8.5 have been configured with the same LDAP user registry without using the Single Sign-On (SSO) configuration, you might receive an authentication failure when testing the connection to the engine, even if in the scheduler connection panel you provided a valid user and password. If this happens, configure the WebSphere Application Server security on both the servers, specifying two different values for the LDAP server hostnames. For example, in Dynamic Workload Console, specify the short hostname or the IP address of the LDAP server. On the Tivoli Workload Scheduler engine, specify the fully qualified hostname.

 

Slow search in the help on first-time use (35489)

The first time you use the search function in Dynamic Workload Console help, it can take some time to index the whole help content before the search starts.

 

Disabled browser BACK button (32905)

You cannot use the browser back button to go back to a previous panel in the Dynamic Workload Console, this operation closes all the panels of the console.
Workaround: To go back to a previous panel, use the back button or the cancel button of the Dynamic Workload Console.

 

Monitor jobs task: filtering action on Internal status BOUND on old TWS engine retrieves jobs in internal FENCE status (21749)

If you connect to an engine with version earlier than 8.6 and you filter for jobs with internal state set to BOUND, a list of all the jobs with internal state set to FENCE is returned.

 

Communication problems with the engine when using IPv6

If you are using Dynamic Workload Console in environments where you are using the IPv6 protocol or in mixed environments where both the IPv4 and IPv6 protocols are in use, you might experience connection problems.

Workaround: To fix this problem set a configuration parameter in the application server, as follows:

1. Open the following file for editing: $TWA_HOME/eWAS/profiles/jazzsm_profile/config/cells/jazzsm_cell_name/ nodes/jazzsm_node_name/servers/server1/server.xml
2. Locate the variables: java.net.preferIPv4Addresses and java.net.preferIPv6Addresses
3. Set the variables as follows:

   Pure IPv6 environment

   java.net.preferIPv4Addresses=false
java.net.preferIPv6Addresses=true

   Pure IPv4 environment

   java.net.preferIPv4Addresses=true
java.net.preferIPv6Addresses=false

   Mixed IPv4 and IPv6 environments

   java.net.preferIPv4Addresses=false
java.net.preferIPv6Addresses=false

4. Stop and restart the application server, using the commands stopappserver and startappserver
   
   

Job stream editing limitations with Tivoli Workload Scheduler for z/OS

In Dynamic Workload Console for z/OS there is no job stream editor available to manage jobs within the job stream in a plan. As a consequence, on z/OS, there is no Submit and Edit option available within the Predefined Job Stream action.

Incorrect selection of jobs in manage browsed workstations panel

In the panel to manage browsed workstations, when you select Jobs from the More Actions menu, the displayed list shows all the jobs belonging to job streams defined on the selected workstation, and not just the jobs running on it.

Special character validation problems with Tivoli Workload Scheduler for z/OS

In z/OS environments, during task creation or editing, a few special characters might not be validated by Dynamic Workload Console. As a consequence, an error might occur on the z/OS connector causing the result table of the task to be empty. This happens when the code page of the z/OS engine is not the same as the code page of the z/OS connector client. Invalid characters are those that map the hexadecimal values 0x7B, 0x5B, 0x7C in all supported EBCDIC code pages (for example #, $, @ for IBM-37 EBCDIC codepage).

Stop of application server hangs

The command that stops the embedded WebSphere Application Server hosting Dynamic Workload Console might hang or end due to a timeout. This can occur randomly after several days of activity. It might be necessary to stop the server manually. The server process ID to stop is stored in the following file: $TWA_HOME/eWAS/profiles/jazzsm_profile/logs/ffdc/dwc_server_name.pid

 

---

Installation and upgrade limitations and their workarounds

Top

 

Installation limitations and problems, and their workarounds

The following are installation limitations that affect the installation of Dynamic Workload Console:

• On Windows operating systems, where the Dynamic Workload Console is installed on the same computer as the master domain manager, initially after installing, you can log in successfully, but after logging off or after a system reboot, attempts to log in fail.

  You can solve this problem temporarily by starting the WebSphere Application server instance, but you will need to repeat this operation each time the problem occurs, or you can solve the problem definitively by creating a Windows service for Jazz for Service Management.

  To start the Dynamic Workload Console related to the Jazz for Service Management extension for the WebSphere profile, start the WebSphere Application server instance on a Windows operating system as follows:

  TWA_home\TWAUI\wastools\startWas.bat

  where TWA_home is the Dynamic Workload Console installation directory.

  Note: When you start or stop the Dynamic Workload Console, related to a Jazz for Service Management extension for WebSphere profile, you are prompted to insert the credentials for the profile. To avoid this, run the command with the -direct option.

  To definitively solve this problem, you must manually create a Windows service for Jazz for Service Management. However, if you have other products or solutions in addition to Tivoli Workload Scheduler that use Jazz for Service Management as an integration service, then ensure that the creation of the Windows service does not interfere with your other products or solutions. On Windows systems, create a service for Jazz for Service Management using the smsetApplicationServer command, as follows:

  1. Open a command prompt and browse to the JazzSM_install_directory\bin directory.
  2. Submit the following command:

     smsetApplicationServer.bat --property autostart=true --property admin.name=JazzSM_username --property admin.password=JazzSM_password

     where:

     JazzSM_username

     Is the user name that is used to log on to the Jazz for Service Management WebSphere profile.

     JazzSM_password

     Is the password for the Jazz for Service Management user name.

     autostart

     When the property is set to true, the command can complete some or all of the following actions:

     • Creates the service if it does not exist.
     • Starts the service if it is not started.

     When the property is set to false, the command can complete some or all of the following actions:

     • Checks the status of the service.
     • Stops the sesrvice if it is not stopped..
     • Deletes the service if it exists.

     admin.name

     Is the user name with administrative privileges who can change the configuration settings of the Jazz for Service Management application server.

     admin.password

     Is the password that is associated with the administrator user name as set by the admin.name property.

  3. If you are installing only the software prerequisites for Tivoli Workload Scheduler or Dynamic Workload Console, the installation process starts without warning you that Installation Manager cannot find the files for the packages. You will be later prompted to insert the required disks or specify the required images. (80833)
  4. When installing the Dynamic Workload Console V9.1 by launching either setupALL or setupDWC script, the installation procedure incorrectly refers to Registry Services 1.1 and asks to specify the path to it, instead of referring to Jazz for Service Management.
     Workaround: When asked for Registry Services 1.1 path, specify the path to Jazz for Service Management. (80292)
  5. During the installation of Dynamic Workload Console version 9.1 on Windows Server 2008 R2 64-bit and SUSE Linux Enterprise Server 11 SP2 (x86_64) operating systems, if errors like the following are logged, you can sefaely ignore them:
SystemErr R Exception in thread "ActiveMQ ShutdownHook" java.lang.NoClassDefFoundError: rg.apache.activemq.transport.vm.VMTransportFactory
SystemErr R Failed to shut down: java.lang.NullPointerException (79000)
  6. You cannot install Dynamic Workload Console into an instance of Tivoli Workload Automation if Tivoli Workload Scheduler was previously installed in a path that contains characters that are not US-ASCII. (42876)
  7. In the tdwcinstall.log file it is mistakenly said that TIPInstaller-00.log file is located under /root. Instead, this file is in the /tmp/TWA/tdwc86 directory, like all the other log files relating to Tivoli Integrated Portal installation.
  8. On Solaris operating systems, after uninstalling Dynamic Workload Console, you might see the following exception in the installation log file: java.lang.NullPointerException at com.installshield.product.service.registry.VPDDef.pack(Unknown Source)

     If so, delete the /root_dir/InstallShield/Universal/TDWC directory before you reinstall Dynamic Workload Console. (38106)

  9. On Windows operating systems, after uninstalling Dynamic Workload Console version 8.6 with its embedded version of WebSphere Application Server, verify that the Windows service used to start the application server has been removed too. If that Windows service still exists, either remove it manually or make sure that you use a different service ID when you reinstall Dynamic Workload Console. (37410)
  10. On Windows operating systems, when you uninstall Dynamic Workload Console version 8.6 after having run one or more reports from the Web console, a warning message might be displayed saying that some files could not be deleted. These files are harmless and are replaced with a new installation. (37107)
  11. During installation of Dynamic Workload Console version 8.6 on HP-UX operating systems, when you browse to a directory, click or double-click Open, and return to the installation panel, the directory name appears duplicated. To proceed with the installation, delete the duplicated directory instance. (33165)
  12. When using the launchpad on Linux and Solaris operating systems, warning messages might appear in the standard output. These messages can be ignored because they do not indicate any malfunctioning.
  13. Some characters, which are not supported in the installation directory field, are not listed in the error message AWSUI0009E. The complete list of unsupported characters for that field are:

      On UNIX: space character and { } [ ] < > $ | ? ! # * + " - \ : = ~ ' ( ) ; , & % ^ `
      (37552)

  On Windows: { } [ ] < > $ | ? ! # * + " / % ' ( ) ^ : ; , = & `
  (37429)

  14. On AIX operating systems if the launchpad fails to start, install the Dynamic Workload Console in graphical mode using the wizard.
  15. When installing Tivoli Workload Scheduler, you cannot specify parentheses in the installation path field.
  16. No password validation is performed on UNIX and Linux platforms at data input. If you have made an error in the password, it will only be discovered when the installation process attempts to use the password during the performance of an installation step.
      Workaround: To resume the installation, locate every step that includes the indicated password (an appendix of Tivoli Workload Scheduler: Administration Guide and Troubleshooting Guide help you do this) and change it to the correct value. Then, resume the installation at the first step that failed. Otherwise, rerun the installation, using the correct value for the password.

 

---

Graphical views limitations and their workarounds

Top

The following are software limitations that affect the graphical views of Dynamic Workload Console on all operating systems:

Workload Designer does not open

The Workload Designer cannot be opened from a monitoring graphical view if the monitor task has been run against an engine whose definition has not been saved, that is if engine connection properties have been provided at task run time.

 

Job Stream View and Impact View limitations with older z/OS engine versions

• Tivoli Workload Scheduler for z/OS version 8.5 and z/OS Connector version 8.5.0
  -status information about dependency links and condition nodes is not available. As a consequence, the "Show/Hide Dependency Status" button is not available.
  -dependency links originating from the same predecessor job and pointing to the same condition node are collapsed into a single dependency link.
  -"Delete" action is not available on dependency links poining to a condition node.
  -rule information is not available on condition nodes.
• Tivoli Workload Scheduler for z/OS version 8.5 and z/OS Connector version 8.5.1
  -status information about dependency links, other than condition dependencies, is not available. As a consequence, the "Show/Hide Dependency Status" button is not available.

Job Stream View limitations with older engine versions

• When using the graphical views with older version of Tivoli Workload Scheduler distributed engines, the rerun-chain table of the job properties is incomplete when the chain contains rerun-instances with job names different from the original job. In particular, if the last job of the rerun-chain has a name different from the original job, possible links originating from it are not shown.
• The following properties of jobs and workstations contain incorrect values in the Job Stream View with engine connections version 8.4 and must be ignored:
  
• Jobs
  if the engine is version 8.4 the following properties are not applicable:

  • Critical Job
  • Promoted
  • Critical Latest Start
   

Event management limitations and their workarounds

Top

The following software limitation affects the event management feature of Dynamic Workload Console on all operating systems:

Using the event management function from Dynamic Workload Console, it is not possible to retrieve the internal names of the event types. If you need to find an event internal name, use the command line interface from the master where the event processor is installed. For more information about the command to use, and how to use it, refer to the utility commands chapter of the Tivoli Workload Scheduler User's Guide and Reference.

---

Reporting limitations and their workarounds

Top

This section describes the software limitations that affect the reporting feature of Dynamic Workload Console on all operating systems:

• When you run a production plan report and, in the Filter Criteria panel, you select Plans in the last days or Plans in the following days the following message appears:

  "AWSUI0831E The plan "" does not exist."

  when there is no Symphony file that matches the filter criteria.

• When you are creating a production details report, the panel displays Current Plan as a default value in the Select plans list, even though a current plan does not exist.
• If you use a version of Microsoft Excel that does not support UTF 8 character set to open CSV reports the content of the file looks corrupted. You can bypass this problem by using a more recent version of Excel, such as that contained in Micosoft Office 2007, and by following these steps to open the file:
  1. Save the extracted CSV report
  2. Open Microsoft Excel
  3. In the Data menu entry, select Import External Data and then Import Data
  4. Select the saved CSV file and click Open
  5. In the field File Origin, select UTF8. (37965)

 

---

Globalization notes

Top

This section describes software limitations, problems, and workarounds for international versions of Dynamic Workload Console.

• Some simplified Chinese characters are missing or corrupted when using Google Chrome or Apple iPad Safari browser
  When you access the Self-Service Catalog or Self-Service Dashboard form a mobile device that uses the Google Chrome or Apple iPad Safari borwser, if you use the GB18030 Simplified Chinese character set, the characters that you type might be missing or corrupted.
  Cause: Google Chrome and Apple iPad Safari do not fully support GB18030 Simplified Chinese.
  Solution: Ensure that you are using a browser that supports GB18030 Simplified Chinese character set.
• The Dynamic Workload Console installation fails if you specify a user name for the WebSphere Application Server that contains Arabic characters. (43052)
  

---

Documentation Updates

Top

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

---

APARs fixed in this release

Top

Dynamic Workload Console V9.2 includes APARs fixed in V9.1, plus the following:

• IV36472: CLASSCASTEXCEPTION WTEXTCOMPONENT INCOMPATIBLE WITH WCHECKBOXLIST
• IV38108: TDWC SAP JOB LISTING SORTED BY DATE DISCOUNTING YEAR
• IV43461: REMOTE SERVER NAME IS AVAILABLE FOR DISTRIBUTED SYSTEMS
• Porting of IV43882
• Porting of IV43883
• IV44824: JOBS RUN AT WRONG TIME ON DAY DST SHIFT BACK IN SYDNEY
• IV45156: TDWC EWAS SYSTEMOUT. LOG GETS SERIES OF [DASHBOARD] MESSAGES REPEATING EVERY FEW SECONDS
• Porting of IV46431
• IV49674: CUSTOM SQL REPORT ERRORS IN DWC 9.1
• IV49985: AFTER UPGRADE TO FP2 - CAN NO LONGER ACCESS "JOB RUN HISTORY"
• IV51978: SCREEN COVERS ALL THE MONITOR
• IV51982: PAGEMGR THREADS IN TDWC WAIT WITHOUT TIMEOUT
• IV52907: TDWC INTERPRETS DEFAULT CALENDAR HOLIDAYS AS WORKDAYS

 

Top

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