Release Notes for Dynamic Workload Console, version 8.6

Content

After December 10th 2013, the Dynamic Workload Console 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 IBM Dynamic Workload Console version 8.6 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 8.6: compatibility

Tivoli Workload Scheduler: compatibility

Dynamic Workload Console: compatibility

Tivoli Workload Scheduler for z/OS: compatibility

Notes:

• The z/OS connector version must be the same as the Dynamic Workload Console version.
• The TWS for z/OS version must be equal to or lower than the Dynamic Workload Console version.

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 higher. 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 higher 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 only be used 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. It 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

This section contains product limitations that could not be resolved with this release of IBM Dynamic Workload Console:

 

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

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/TIPProfile/config/cells/TIPCell/nodes/TIPNode/
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" (40567)

 

Wrong DWC link provided in the log files

When you install the WebSphere Application Server with the Tivoli Integrated Portal, the Dynamic Workload Console does not work if the context root is different from the default ibm/console.
Workaround: Define ibm/console as context root. (33030)

 

Disabled browser BACK button

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: o go back to a previous panel, use the back button or the cancel button of the Dynamic Workload Console. (32905)

 

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

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

 

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)

 

Connection problems with a stopped engine

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

Slow performance using Internet Explorer

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

 

Videos do not start or play correctly

Occasionally, due to low bandwidth or network performance, demos do not start or work as expected.
Workaround: Ensure that you use Internet Explorer as you preferred browser and that you have the latest version of Adobe Flash Player installed.

 

SAP queries problems

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)

If you create a new SAP job definition in the Workload Designer, and in the Task tab on the right pane you select any subtype, and you click on the job name lookup icon, all the jobs with the special character " (double quote) in their name are not displayed in the search panel results. (44228)

Internet Explorer V7 and 8: Certificate Error: Navigation Blocked page at Tivoli Integrated Portal login

If you open the Integrated Solutions Console login page with the Internet Explorer V7 and 8 browser, a Certificate Error: Navigation Blocked page is displayed stating that the security certificate presented by the Web site was not issued by a trusted certificate authority , and that it was issued for a different Web site's address.
Workaround: Although Internet Explorer V7 and 8 explicitly recommend closing the Web page and not continuing to the Web site, you must click the Continue to this Web site (not recommended) link to go to the Integrated Solutions Console login page. (40681)

 

Some transparency effects might not work properly on Internet Explorer V7 and 8

If you use the Internet Explorer V7 and 8 browser, some transparency effects might not work correctly. For example, this might happen while sorting objects resulting from plan or database queries, or while using lookup panels within the Workload Designer window. In both cases, you might see a blank background. This only happens if you changed the Internet Explorer V7 and 8 default settings.
Workaround: Open an Internet Explorer V7 and 8 browser page and go to Tools--> Internet Options --> Security, then select the zone that the Dynamic Workload Console Web site belongs to, go to Custom Level, and change the ActiveX controls and plug-ins --> Binary and script behaviors to ENABLE. (44748)

 

Run Cycle low performance

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

 

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

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

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/TIPProfile/config/cells/TIPCell/ nodes/TIPNode/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
   
   

Slow search in the help on first-time use

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

 

Authentication problems with LDAP without Single Sign-On configured

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

Additional step required for Single Sign-On enablement

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

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/TIPProfile/logs/ffdc/tdwc_server_name.pid

After exporting user settings from file to database repository some task data is missing

With current version of Dynamic Workload Console, the task "refreshTime" data is not exported when exporting your user settings repository form local file to database.
Workaround: To solve the problem, install Dynamic Workload Console 8.6 Fix Pack 1 before exporting user settings (60712).

The following are software limitations that affect the installation of Dynamic Workload Console on all platforms:

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

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

• On AIX operating systems if the launchpad fails to start, install the Dynamic Workload Console in graphical mode using the wizard.
• 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)
• When installing Tivoli Workload Scheduler, you cannot specify parentheses in the installation path field.
• 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.
• When upgrading from Tivoli Dynamic Workload Console 8.5 Fix Pack 1 to Dynamic Workload Console version 8.6, the process stops on step 2.
  Workaround: To avoid the problem, before launching the upgrade, change the file: /etc/TWA/twainstance0.TWA.properties, replacing the value TDWC_version=8.5.0.1 with TDWC_version=8.5.0.0.
  If you have not done it before upgrading and you receive the following error: /opt/tws/tmptdwc851/TDWC/WEBUI/LINUX390/xml/upgradeMacros.xml:77: The
directory you specified does not exist,
perform the following steps:
  1. Close the installation setup program.
  2. Change the value TDWC_version=8.5.0.1 with TDWC_version=8.5.0.0 in the TWA instance registry. For example, follow these steps:
     1. Open the TWA registry %WINDIR%/TWA/twainstance0.TWA.properties (WINDOWS)
        /etc/TWA/twainstance0.TWA.properties (UNIX)
        The file property to edit depends on installed TWA instance number, which can be 0,1,2, etc.
     2. Change the value: TDWC_version=8.5.0.1 to TDWC_version=8.5.0.0.
  3. Open the InstallShield registry (file vpd.scripts) located under:
     %CommonProgramFiles%\InstallShield\Universal\TDWC\Gen2\_vpddb (WINDOWS)
     /usr/lib/objrepos/InstallShield/Universal\TDWC\Gen2\_vpddb (AIX)
     /root/InstallShield/Universal/TDWC/Gen2/_vpddb (LINUX, HP)
     /InstallShield/Universal/TDWC/Gen2/_vpddb (SOLARIS)
  4. Edit the file and change the string 8.6 in the section below to 8.5.0:
     INSERT INTO INSTALLED_SOFTWARE_OBJECT VALUES(1,'e625666383dedb70850864e2a6feaa2e','/opt/IBM/TWA1',1,'8.5.1',3,'true',NULL,'false','IBM','http://www.ibm.com','TWS','$L(com.ibm.scheduling.msg.WebUIInstallationMsg, PRODUCT_NAME)',NULL,'"TDWC\\_tdwcuninst" "uninstall.jar" "uninstall.dat" "assembly.dat" "run.inf" "/root/InstallShield/Universal/TDWC/Gen2/engine/1.0/engine.jar" "/root/InstallShield/Universal/TDWC/Gen2/engine/1.0/ext" "" ""','true','true','1.0.29')
  5. Restart the installation setup program to upgrade to TDWC 8.6.

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

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

• 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
   

The following is a software limitation that affects the event management feature of Dynamic Workload Console on all platforms:

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.

The following are software limitations that affect the reporting feature of Dynamic Workload Console on all platforms:

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

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

• The Dynamic Workload Console installation fails if you specify a user name for the WebSphere Application Server that contains Arabic characters. (43052)
  

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

Dynamic Workload Console version 8.6 includes APARs fixed in V8.5.1 Fix Pack 1, plus the following:

• IZ85335: FIELD 'EXPAND JCL' ARE SET TO 'N' WHEN CHANGE 'RESTART AND CLEANUP ACTION. 'USER FIELDS' ARE CLEARED WHEN UPDATE APPL.(Z)
• IZ89635: AMPERSAND (&) IS ILLEGAL IN TDWC SAP R/3 VARIANT FIELD
• IZ72050: DATE IN SCHEDULED DATE COLUMN IS WRONG
• IZ69676: 12:00 PM TIMES SAVED AS 12:00 AM IN 8.5 TDWC EVENTS.
• IZ90605: WHEN GENERATING HISTORICAL REPORTS, THE TIME ON THE REPORT IS ININ GMT AND NOT LOCAL TIME.
• IZ83736: "RELEASE DEPENDENCIES" OF JOB STEAM FROM TDWC IS NOT LOGGED TO AUDIT
• IZ79820: DEFINING A JOB STEAM FAILS BY AWSUI6007E, TIMEZONE ERROR, USING TDWC WITH JAPANESE BROWSER.
• IZ86318: LAUNCHING TDWC IN CONTEXT FAILS FOR A JOB FILTER '&JOB'
• IZ81404: THE VIEW FOR "MONITOR CRITICAL JOBS" FOR Z/OS MAY SHOW A BLANK VALUE FOR THE COLUMN "CRITICAL PATH REMAINING DURATION"
• IZ79113: "SPECIFY DATE AND TIME" BOX NEVER CHECKED OUT FROM TIME RESTRICTIONS.
• IZ84314: TDWC MISSES 'STANDARD' INVERVAL WHEN CREATING SPECIAL RESOURCE
• IZ87157: TDWC JCL EDITOR CHANGE '>' CHARACTER TO '&GT' CAUSING JCL ERROR
• IZ95436: JAVA PROCESS HIGH CONSUMPTION OF RAM
• IZ92526: UNABLE TO CREATE EXTERNAL DEPENDENCY WITH 0000 TIME IN
• IZ96495: DISPLAYING A GRAPHICAL VIEW OF JOB STREAM TAKES TOO LONG

Top

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