IBM(R) Tivoli(R) Workload Scheduler for Applications Readme File for Fix Pack 02 - PTF (U812114) Version 8.3.0 +---- Note ------------------------------------------------------------+ Before using this information and the product it supports, read the information in 3.0, "Notices". +----------------------------------------------------------------------+ This edition applies to fix pack 2 (PTF U812114 ) for version 8, release 3, modification level 0 of IBM Tivoli Workload Scheduler for Applications program number (5698-WSE) Copyright International Business Machines Corporation 2006, 2007. All rights reserved. US Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents 1.0 IBM Tivoli Workload Scheduler for Applications Fix Pack 02 for Version 8.3.0 1.1 About this release 1.1.1 Fix pack installation CDs and tar files organized by operating system 1.1.2 New Features in IBM Tivoli Workload Scheduler for Applications version 8.3.0 Fix Pack 02 1.1.3 Features in IBM Tivoli Workload Scheduler for Applications version 8.3.0 Fix Pack 01 1.1.3.1 HP-UX 11i v2 for Integrity native support 1.1.3.1.1 Installing IBM Tivoli Workload Scheduler for Applications, version 8.3 on HP-UX for Integrity 1.1.4 APARs and Defects fixed in IBM Tivoli Workload Scheduler for Applications, Version 8.3.0 fix pack 2 1.1.4.1 Common APARs and Defects fixed 1.1.4.2 APARs and Defects fixed for SAP R/3 1.1.4.3 APARs and Defects fixed for z/OS 1.1.4.4 APARs and Defects for Peoplesoft 1.1.5 APARs and Defects fixed in IBM Tivoli Workload Scheduler for Applications, Version 8.3.0 fix pack 1 1.1.5.1 Common APARs and Defects fixed 1.1.5.2 APARs and Defects fixed for SAP R/3 1.1.5.3 APARs and Defects fixed for z/OS 1.1.6 Limitations 1.1.6.1 Common limitations 1.1.6.2 Limitation for Oracle E-business Suite 1.1.6.3 Limitations for SAP R/3 1.1.6.4 Limitation for z/OS 1.1.7 Installing the fix pack 1.1.7.1 Supported platforms 1.1.7.2 Hardware and software prerequisites 1.1.7.3 Fix pack installation methods 1.1.7.3.1 The InstallShield MultiPlatform (ISMP) wizard 1.1.7.3.2 Silent Installation 1.1.7.3.3 Compaq Tru64, SGI IRIX, IBM Sequent Dynix installation method 1.1.7.3.4 z/OS installation method 1.1.7.3.5 Software Distribution command line 1.1.7.3.6 Alternate install script on IBM AIX, HP-UX, Solaris, Linux 1.1.7.4 Interoperability tables 1.1.8 Documentation notes 2.0 Contacting IBM Software Support 3.0 Notices 3.1 Trademarks 1.0 IBM Tivoli Workload Scheduler for Applications Fix Pack 02 for Version 8.3.0 Date 29 June 2007 Fix Pack 8.3.0-TIV-TWSWSE-FP0002 PTF Number U812114 Product IBM(R) Tivoli(R) Workload Scheduler for Applications, Version 8.3.0 General Description IBM Tivoli Workload Scheduler for Applications, Version 8.3.0 Fix Pack 02 Review this section thoroughly before installing or using this fix pack. 1.1 About this release This section includes the following topics: * 1.1.1, "Fix pack installation CDs and tar files organized by operating system" * 1.1.2, "New Features in IBM Tivoli Workload Scheduler for Applications version 8.3.0 Fix Pack 02" * 1.1.3, "Features in IBM Tivoli Workload Scheduler for Applications version 8.3.0 Fix Pack 01" * 1.1.6, "Limitations" * 1.1.7, "Installing the fix pack" * 1.1.8, "Documentation notes" 1.1.1 Fix pack installation CDs and tar files organized by operating system This section shows the contents of the five CDs in this fix pack. * CD1 or the following tar files: * 8.3.0-TIV-TWSWSE-FP0002_I386NT.TAR * 8.3.0-TIV-TWSWSE-FP0002_AIX.TAR CD1 includes Fix Pack 02 images for Microsoft Windows and AIX. It has the following structure: +---CD1 | +---RESPONSE_FILE | | TWS4APPSSilent.txt | | | +---ZOS | | EEWSERVE.SAMPLE | | EEWSPACE.SAMPLE | | LOADLIB | | | +---LICENSE | +---I386NT | | +---INSTALLER | | | | setup.exe | | | | | | | \---SPB | | | TWS4APPS_OPTED_FP02.SPB | | | TWS4APPS_ZOSAGENT_I386NT_FP02.SPB | | | TWS4APPS_PSAGENT_I386NT_FP02.SPB | | | TWS4APPS_R3BATCH_I386NT_FP02.SPB | | | | | \---JVM_CM | | JRE142_I386NT.SPB | | | \---AIX | +---INSTALLER | | | setup.bin | | | | | \---SPB | | TWS4APPS_OPTED_FP02.SPB | | TWS4APPS_MCMAGENT_AIX_FP02.SPB | | TWS4APPS_ZOSAGENT_AIX_FP02.SPB | | TWS4APPS_PSAGENT_AIX_FP02.SPB | | TWS4APPS_R3BATCH_AIX_FP02.SPB | | TWS4APPS_R3BATCH_AIX64_FP02.SPB | | | +---JVM_CM | | JRE142_AIX.SPB | | | \---ALT_INST | | twsappsFPinst | | | +---SPB | | TWS4APPS_OPTED_FP02.SPB | | TWS4APPS_MCMAGENT_AIX_FP02.SPB | | TWS4APPS_ZOSAGENT_AIX_FP02.SPB | | TWS4APPS_PSAGENT_AIX_FP02.SPB | | TWS4APPS_R3BATCH_AIX_FP02.SPB | | TWS4APPS_R3BATCH_AIX64_FP02.SPB | | JRE142_AIX.SPB | | | +---_swdcli | ... * CD2, or the following tar files: * 8.3.0-TIV-TWSWSE-FP0002_LINUX.TAR * 8.3.0-TIV-TWSWSE-FP0002_LINUX390.TAR CD2 includes the Fix Pack 02 images for LINUX and LINUX390. It has the following structure: +---CD2 | +---RESPONSE_FILE | | TWS4APPSSilent.txt | | | +---ZOS | | EEWSERVE.SAMPLE | | EEWSPACE.SAMPLE | | LOADLIB | | | +---LICENSE | +---LINUX | | +---INSTALLER | | | | setup.bin | | | | | | | \---SPB | | | TWS4APPS_OPTED_FP02.SPB | | | TWS4APPS_MCMAGENT_LINUX_FP02.SPB | | | TWS4APPS_PSAGENT_LINUX_FP02.SPB | | | TWS4APPS_R3BATCH_LINUX_FP02.SPB | | | | | +---JVM_CM | | | JRE142_LINUX.SPB | | | | | \---ALT_INST | | | twsappsFPinst | | | | | +---SPB | | | TWS4APPS_OPTED_FP02.SPB | | | TWS4APPS_MCMAGENT_LINUX_FP02.SPB | | | TWS4APPS_PSAGENT_LINUX_FP02.SPB | | | TWS4APPS_R3BATCH_LINUX_FP02.SPB | | | JRE142_LINUX.SPB | | | | | +---_swdcli | | ... | \---LINUX390 | +---INSTALLER | | | setup.bin | | | | | \---SPB | | TWS4APPS_OPTED_FP02.SPB | | TWS4APPS_ZOSAGENT_LINUX390_FP02.SPB | | TWS4APPS_R3BATCH_LINUX390_FP02.SPB | | | +---JVM_CM | | JRE142_LINUX390.SPB | | | \---ALT_INST | | twsappsFPinst | | | +---SPB | | TWS4APPS_OPTED_FP02.SPB | | TWS4APPS_ZOSAGENT_LINUX390_FP02.SPB | | TWS4APPS_R3BATCH_LINUX390_FP02.SPB | | JRE142_LINUX390.SPB | | | +---_swdcli | ... * CD3, or the following tar file: * 8.3.0-TIV-TWSWSE-FP0002_HP.TAR CD3 includes the Fix Pack 02 images for HP-UX. It has the following structure: +---CD3 | +---RESPONSE_FILE | | TWS4APPSSilent.txt | | | +---ZOS | | EEWSERVE.SAMPLE | | EEWSPACE.SAMPLE | | LOADLIB | | | +---LICENSE | \---HP | +---INSTALLER | | | setup.bin | | | | | \---SPB | | TWS4APPS_OPTED_FP02.SPB | | TWS4APPS_MCMAGENT_HP_FP02.SPB | | TWS4APPS_ZOSAGENT_HP_FP02.SPB | | TWS4APPS_PSAGENT_HP_FP02.SPB | | TWS4APPS_R3BATCH_HP_FP02.SPB | | TWS4APPS_R3BATCH_HP64_FP02.SPB | | | +---JVM_CM | | JRE142_HP.SPB | | | \---ALT_INST | | twsappsFPinst | | | +---SPB | | TWS4APPS_OPTED_FP02.SPB | | TWS4APPS_MCMAGENT_HP_FP02.SPB | | TWS4APPS_ZOSAGENT_HP_FP02.SPB | | TWS4APPS_PSAGENT_HP_FP02.SPB | | TWS4APPS_R3BATCH_HP_FP02.SPB | | TWS4APPS_R3BATCH_HP64_FP02.SPB | | JRE142_HP.SPB | | | +---_swdcli | ... * CD4, or the following tar files: * TWS4APPS_ZOSAGENT_DYNIX.TAR * 8.3.0-TIV-TWSWSE-FP0002_DYNIX.TAR * TWS4APPS_ZOSAGENT_IRIX.TAR * 8.3.0-TIV-TWSWSE-FP0002_IRIX.TAR * TWS4APPS_R3BATCH_OSF.TAR * TWS4APPS_ZOSAGENT_OSF.TAR * 8.3.0-TIV-TWSWSE-FP0002_OSF.TAR * 8.3.0-TIV-TWSWSE-FP0002_SOLARIS.TAR CD4 includes the Fix Pack 02 images for DYNIX, IRIX, OSF, and SOLARIS. It has the following structure: +---CD4 | +---RESPONSE_FILE | | TWS4APPSSilent.txt | | | +---ZOS | | EEWSERVE.SAMPLE | | EEWSPACE.SAMPLE | | LOADLIB | | | +---LICENSE | +---SOLARIS | | +---INSTALLER | | | | setup.bin | | | | | | | \---SPB | | | TWS4APPS_OPTED_FP02.SPB | | | TWS4APPS_MCMAGENT_SOLARIS_FP02.SPB | | | TWS4APPS_ZOSAGENT_SOLARIS_FP02.SPB | | | TWS4APPS_PSAGENT_SOLARIS_FP02.SPB | | | TWS4APPS_R3BATCH_SOLARIS_FP02.SPB | | | TWS4APPS_R3BATCH_SOLARIS64_FP02.SPB | | | | | +---JVM_CM | | | JRE142_SOLARIS.SPB | | | | | \---ALT_INST | | | twsappsFPinst | | | | | +---SPB | | | TWS4APPS_OPTED_FP02.SPB | | | TWS4APPS_MCMAGENT_SOLARIS_FP02.SPB | | | TWS4APPS_ZOSAGENT_SOLARIS_FP02.SPB | | | TWS4APPS_PSAGENT_SOLARIS_FP02.SPB | | | TWS4APPS_R3BATCH_SOLARIS_FP02.SPB | | | TWS4APPS_R3BATCH_SOLARIS64_FP02.SPB | | | JRE142_SOLARIS.SPB | | | | | +---_swdcli | | ... | +---DYNIX | | TWS4APPS_ZOSAGENT_DYNIX.TAR | | | +---IRIX | | TWS4APPS_ZOSAGENT_IRIX.TAR | | | \---OSF | TWS4APPS_R3BATCH_OSF.TAR | TWS4APPS_ZOSAGENT_OSF.TAR * CD5, or the following tar file: * 8.3.0-TIV-TWSWSE-FP0002_HPIA64.TAR CD5 includes the Fix Pack 02 images for HP-UX for Integrity. It has the following structure: | \---CD5 +---RESPONSE_FILE | TWS4APPSSilent.txt | +---ZOS | EEWSERVE.SAMPLE | EEWSPACE.SAMPLE | LOADLIB | +---LICENSE \---HPIA64 +---INSTALLER | | setup.bin | | | \---SPB | TWS4APPS_OPTED_FP02.SPB | TWS4APPS_PSAGENT_HPIA64_FP02.SPB | TWS4APPS_R3BATCH_HPIA64_FP02.SPB | TWS4APPS_ZOSAGENT_HPIA64_FP02.SPB | TWS4APPS_MCMAGENT_HPIA64_FP02.SPB | +---JVM_CM | JRE142_HPIA64.SPB | \---ALT_INST | twsappsFPinst | +---SPB | TWS4APPS_OPTED_FP02.SPB | TWS4APPS_PSAGENT_HPIA64_FP02.SPB | TWS4APPS_MCMAGENT_HPIA64_FP02.SPB | TWS4APPS_R3BATCH_HPIA64_FP02.SPB | TWS4APPS_ZOSAGENT_HPIA64_FP02.SPB | JRE142_HPIA64.SPB | +---_swdcli ... 1.1.2 New Features in IBM Tivoli Workload Scheduler for Applications version 8.3.0 Fix Pack 02 This section describes the new features included in IBM Tivoli Workload Scheduler for Applications version 8.3.0 Fix Pack 02. SLES 10 support Tivoli Workload Scheduler for Applications 8.3 Fix Pack 2 has been successfully certified on Sles10. You can now install Tivoli Workload Scheduler for Applications 8.3 GA (July 2006) and then 8.3 Fix Pack 2. Using the following configuration you can run on SLES 10.0" SuSE SLES 10.0 32bit xSeries , TWS for Applications Peoplesoft Agent 8.3 FP02/TWS 8.3 FP02 SuSE SLES 10.0 64bit AMD64/EM64T , TWS for Applications Peoplesoft Agent 8.3 FP02/TWS 8.3 FP02 SuSE SLES 10.0 64bit zSeries , TWS for Applications R/3 Agent 8.3 FP02/TWS 8.3 FP02 SuSE SLES 10.0 32bit xSeries , TWS for Applications R/3 Agent 8.3 FP02/TWS 8.3 FP02 SuSE SLES 10.0 64bit AMD64/EM64T , TWS for Applications R/3 Agent 8.3 FP02/TWS 8.3 FP02 TIS support for Oracle The Tivoli Internationalization Function (TIS) feature has been introduced to provide additional functions to support MBCS character sets in the Oracle Job definition in Tivoli Workload Scheduler. TIS is a Tivoli library designed to provide a utility for character set conversions. The Oracle environments could be set in a different code set than Tivoli Workload Scheduler environments. For example, if your Oracle environments are in Japanese character set and the Tivoli Workload Scheduler is in English, you must translate the Tivoli Workload Scheduler task string from the original character set into the Japanese one. This is possible using the TIS library feature. Using the local and global configuration files, you can set up MCMAGENT to use different code pages and languages with a remote Oracle system. This feature allows you to install MCMAGENT on a localized Tivoli Workload Scheduler workstation and use localized characters for Tivoli Workload Scheduler job names, user name, and parameters. Listed below are the support options related to the NLS support: * National Language support options The following options control the code page and the national language used by Tivoli Workload Scheduler for Applications for Oracle version 8.3. * UTF8CMDLINE: This option enables (1) or disables (0) the encoding of extended parameters in UTF-8. * TWSXA_CP: This option affects the code page used to open the connection between MCMAGENT and the Oracle system. Set this option to the code page installed on the Oracle system. * TWSXA_LANG: This option affects the language that MCMAGENT uses to log in. * TWSMETH_CP: TWSMETH_CP is the code page that MCMAGENT uses for its output. The default is the code page used by the Tivoli Workload Scheduler workstation that hosts MCMAGENT. * TWSMETH_LANG: This option affects the catalog language used by MCMAGENT. The default is the language used by the Tivoli Workload Scheduler workstation that hosts MCMAGENT. 1.1.3 Features in IBM Tivoli Workload Scheduler for Applications version 8.3.0 Fix Pack 01 This section describes the features included in IBM Tivoli Workload Scheduler for Applications version 8.3.0 Fix Pack 01. Windows Vista IBM Tivoli Workload Scheduler for Applications runs on Windows Vista in compatibility mode on the access method listed in Table 1. Table 1. Supported operating systems +------------------+--------------------------------------------------+ | Operating System | Access Method | | |--------------------------------------------------| | | z/OS | z/OS | SAP | Peopl | Oracle | | | (Gateway | (Transact | R/3 | eSoft | E-busine | | | ) | ion | | | ss Suite | | | | Server) | | | | +---------------------------------------------------------------------+ | Microsoft Windows | +------------------+----------+-----------+--------+-------+----------+ | Windows Vista | | X | X | X | | +------------------+----------+-----------+--------+-------+----------+ HP-UX 11i v2 for Integrity IBM Tivoli Workload Scheduler for Applications runs on HP-UX 11i v2 for Integrity. To know what specific action you must take to properly install and use the product in this environment, see 1.1.3.1, "HP-UX 11i v2 for Integrity native support" 1.1.3.1 HP-UX 11i v2 for Integrity native support Table 2 shows which access methods run on HP-UX 11i v2 for Integrity: Table 2. Supported operating systems +------------------+--------------------------------------------------+ | Operating System | Access Method | | |--------------------------------------------------| | | z/OS | z/OS | SAP | Peopl | Oracle | | | (Gateway | (Transact | R/3 | eSoft | E-busine | | | ) | ion | | | ss Suite | | | | Server) | | | | +---------------------------------------------------------------------+ | HP-UX | +------------------+----------+-----------+--------+-------+----------+ | HP-UX version | | X | X | X | | | 11, 11i v1, 11i | | | | | | | v2 for Integrity | | | | | | +------------------+----------+-----------+--------+-------+----------+ 1.1.3.1.1 Installing IBM Tivoli Workload Scheduler for Applications, version 8.3 on HP-UX for Integrity To install IBM Tivoli Workload Scheduler for Applications, version 8.3 on HP-UX for Integrity, perform the following steps: 1. Install IBM Tivoli Workload Scheduler for Applications, version 8.3 on HP-UX as described in the IBM Tivoli Workload Scheduler for Applications version 8.3 User's Guide 2. Install IBM Tivoli Workload Scheduler for Applications, version 8.3 Fix Pack 02 on HP-UX as described in 1.1.7.3, "Fix pack installation methods". If you want to install it using IBM Tivoli Software Distribution version 4.1 or IBM Tivoli Configuration Manager version 4.2, use the software package blocks (SPBs) listed in Table 3 : The .SPB files are located in product media for operating system/HPIA64/INSTALLER/SPB Table 3. List of software package blocks to install IBM Tivoli Workload Scheduler for Applications and their location in the media. +-------------------------------------------------+-------------------+ | .SPB File | Software Package | | | Description | +-------------------------------------------------+-------------------+ | TWS4APPS_MCMAGENT_HPIA64_FP02.SPB | Installs the | | | HP-UX for | | | Integrity Oracle | | | E-business Suite | | | extended agent. | +-------------------------------------------------+-------------------+ | TWS4APPS_PSAGENT_HPIA64_FP02.SPB | Installs the | | | HP-UX for | | | Integrity | | | PeopleSoft | | | extended agent. | +-------------------------------------------------+-------------------+ | TWS4APPS_R3BATCH_HPIA64_FP02.SPB | Installs the | | | HP-UX for | | | Integrity SAP R/3 | | | extended agent. | +-------------------------------------------------+-------------------+ | TWS4APPS_ZOSAGENT_HPIA64_FP02.SPB | Installs the | | | HP-UX for | | | Integrity z/OS | | | extended agent. | +-------------------------------------------------+-------------------+ | JRE142_HPIA64_FP02.SPB | Installs the | | | HP-UX for | | | Integrity Java | | | Runtime | | | Environment (JRE) | | | version 1.4.2. | +-------------------------------------------------+-------------------+ 1.1.4 APARs and Defects fixed in IBM Tivoli Workload Scheduler for Applications, Version 8.3.0 fix pack 2 This section lists the APARs and Defects fixed in IBM Tivoli Workload Scheduler for Applications, Version 8.3 fix pack 2 by access methods. * 1.1.4.1, "Common APARs and Defects fixed" * 1.1.4.2, "APARs and Defects fixed for SAP R/3" * 1.1.4.3, "APARs and Defects fixed for z/OS" * 1.1.4.4, "APARs and Defects for Peoplesoft" 1.1.4.1 Common APARs and Defects fixed The following APARs and Defects were fixed for PeopleSoft: * Defect 29461 Symptoms: Support TIS libraries for internationalization 1.1.4.2 APARs and Defects fixed for SAP R/3 The following APARs and defects were fixed for R/3: * IY91484 Symptoms: SAP R3batch copy-overwrite function adding extra steps * IY96182 Symptoms: Program error in R/3 batch with lang. * Defect 29369 Symptoms: Wrong BDC status messages are written to the Tivoli Workload Scheduler joblog 1.1.4.3 APARs and Defects fixed for z/OS The following APARs and Defects were fixed for z/OS: * PK37747 Symptoms: The installation CDs for Tivoli Workload Scheduler for Applications did not contain the sample library 1.1.4.4 APARs and Defects for Peoplesoft The following APARs and Defects were fixed for Peoplesoft: * Defect 29490 Symptoms: Peoplesoft did not launch on Solaris 10 1.1.5 APARs and Defects fixed in IBM Tivoli Workload Scheduler for Applications, Version 8.3.0 fix pack 1 This section lists the APARs and Defects fixed in IBM Tivoli Workload Scheduler for Applications, Version 8.3 fix pack 1 by access methods. * 1.1.5.1, " Common APARs and Defects fixed" * 1.1.5.2, "APARs and Defects fixed for SAP R/3" * 1.1.5.3, "APARs and Defects fixed for z/OS" 1.1.5.1 Common APARs and Defects fixed The following APARs and Defects were fixed for PeopleSoft: * Defect 28870 Symptoms: FP1: repair fails after GA(R3,zos)->Fp1->GA(mcm)->commit->repair 1.1.5.2 APARs and Defects fixed for SAP R/3 The following APARs and defects were fixed for R/3: * APAR IY88000 Symptoms: Tivoli Workload Scheduler 8.3 SAP logon group does not allow white space and mixed case * APAR IY89134 Symptoms: Job runs successfully in SAP, but report abend in Tivoli Workload Scheduler * APAR IY91075 Symptoms: R3 batch cannot handle "select option" variant fields holding * Defect 26238 Symptoms: Enable r3batch to handle 40 char length passwords for SAP 7.00 * Defect 26240 Symptoms: Switch to SAP RFC 6.40 libraries to support mixed case password + Enigma long password * Defect 28367 Symptoms: FP2:Editing a previous created R/3 Job fails * Defect 28374 Symptoms: FP2:Succesfull delete of an R/3 Job shows erroneously an error * Defect 28838 Symptoms: FP1:r3event end in core dump if options & parms not well formed * Defect 28957 Symptoms: Delete from Table Criteria fails 1.1.5.3 APARs and Defects fixed for z/OS The following APARs and Defects were fixed for z/OS: * Defect 26911 Symptoms: z/OS methods do not create trace file on OSF 1.1.6 Limitations This section describes all limitations applying to IBM Tivoli Workload Scheduler for Applications, Version 8.3.0. It contains the following subsections: * 1.1.6.1, "Common limitations" * 1.1.6.2, "Limitation for Oracle E-business Suite" * 1.1.6.3, "Limitations for SAP R/3" * 1.1.6.4, "Limitation for z/OS" 1.1.6.1 Common limitations The following limitations apply to all the access methods: * Defect 12944: If you perform a rollback action of the fix pack when an access method is running, the rollback fails but a successful completion message appears. * Defect 25813: If you cancel the installation of an IBM Tivoli Workload Scheduler for Applications version 8.3 language pack, a Java exception is displayed: ServiceException: (error code = 315; message = "product bean R3BATCH_SOLARIS64_C OMPONENT_BEAN does not exist"; severity = 0) WORKAROUND: The IBM Tivoli Workload Scheduler for Applications version 8.3 language pack is installed. To uninstall it proceed as described in the IBM Tivoli Workload Scheduler for Applications version 8.3 User's Guide, Chapter 2. Installing, upgrading, and uninstalling IBM Tivoli Workload Scheduler for Applications, section "Uninstalling". * Defect 27711: The script twsappsFPinst does not support the REPAIR scenario. * Defect 28039: On UNIX operating systems, the installation of Fix Pack 01 fails if you did not log out from the UNIX shell used to install version 8.3. WORKAROUND: You need to log out and log in from the UNIX shell before installing the fix pack. * Defect 28089: On the HP-UX for Integrity operating system, due to an ISMP defect (SIOA-000063891) you cannot perform the following actions: * Launch the Option Editor either while installing the product using the ISMP installation wizard and at any other time. WORKAROUND: To launch the Option Editor, run the following command from the twshome/methods/opted directory: opted.sh * Uninstall the product. WORKAROUND: To uninstall the product, run the following command from the twshome/methods directory: ./_tools/_jvm/bin/java -jar ./_xauninst/uninstall.jar * Defect 28745: On Windows operating system, when you uninstall Fix Pack 01, the following files are left in the methods directory: * enigma.exe * icudt20.dll * icuin20.dll * icuuc20.dll * librfc32u.dll * libsapu16.dll * msvbvm60.dll * msvcp60.dll * TWSoslayer.dll WORKAROUND: Delete the files manually. * Defect 28850: Performing any actions on a fix pack using the ISMP silent installation, a memory dump of 64 byte might occur. WORKAROUND: The action is performed correctly. Delete the core file. * ISMP silent installation does not apply the fix pack when you specify the optional parameter LJUSER that contains double quotes or ends with an odd number of back-slashes. * The following scenario generates an inconsistent configuration. * Install some, but not all the access methods. * Apply the fix pack and optionally commit it. * Add the missing method(s). * Apply the fix pack. This generates an inconsistent state that the ISMP installer cannot handle properly. WORKAROUND: 1. Uninstall and reinstall all the access methods at the same time 2. Launch the InstallShield setup to upgrade/commit selectively the access methods that are at a lower level as follows: * On Windows: setup.exe -W METHODS_FILTER.value="" * On UNIX: setup.bin -W METHODS_FILTER.value="" where is one of the following: * R3BATCH - for R/3 access method * MCMAGENT - for Oracle access method * ZOSAGENT - for the z/OS access method * PSAGENT - for the PeopleSoft access method After realigning all the methods to the same level and state (for example to committed), you can use InstallShield. You can handle more than one method simultaneously by separating the method values with the '|' character. For example, to handle r3batch and MCMAGENT at the same time you can use: setup.exe -W METHODS_FILTER.value="R3BATCH|MCMAGENT" Note: This is a troubleshooting procedure specifically for this problem and not a standard procedure to apply to fix packs on single access methods selectively. * If you apply the fix pack and use Option Editor to create an option file with a password longer than 8 characters, you cannot open the option file with the Option Editor of Tivoli Workload Scheduler for Applications 8.3 at GA level. 1.1.6.2 Limitation for Oracle E-business Suite The following limitations apply to Oracle E-business Suite: * Defect 13171: In a three-tier connectivity configuration a coredump might kill a job when DBserver Oracle is stopped. * APAR IY97188: The submission of an Oracle job fails. The Tivoli Workload Scheduler job log shows the following information: * EEWP0017 Child MCMLJ exited normally. * Exit code: 1.EEWP0027 Error - Launch job failed WORKAROUND : Submitting an Oracle job might fail because there is a connection problem to the Oracle database. Verify that your Oracle naming methods are set correctly. For details about how to configure naming methods, refer to the Oracle Net Services Administrator's Guide. 1.1.6.3 Limitations for SAP R/3 The following limitations applies to SAP R/3: * Defect 12945: It is not possible to create a job with new variant without vpar. * On Linux on S390 32 bit, the following features are not supported: * Mixed case passwords for SAP Netweaver 2004s Systems. * Long passwords (above 8 characters) for SAP Netweaver 2004s. * Self.reduction mechanism for RFC trace file. 1.1.6.4 Limitation for z/OS The following limitation applies to z/OS: * On the IRIX platform under certain conditions the z/OS access methods hang and do not perform any submission. WORKAROUND: Add in the zos_access_method. properties file the following line: zos_access_method.multiproc=0 where zos_access_method can assume one of the following values: * mvsjes * mvsopc * mvsca7 1.1.7 Installing the fix pack This section describes how to install IBM Tivoli Workload Scheduler for Applications, Version 8.3.0 fix pack 2. Fix pack 2 upgrades all the extended agents associated to the selected Tivoli Workload Scheduler for Applications, Version 8.3 instances. Fix packs are cumulative, so you can apply them directly to the general availability version of the product without having to install previous fix packs. Remember, however, that you cannot install any fix packs unless you have the general availability version of the product installed on your computer. Before you install the fix pack, ensure that the following prerequisites are met: * Tivoli Workload Scheduler processes are stopped. * No extended agent method is running. * You must install the fix pack using the same installation method you used to install version 8.3. * Different access methods belonging to different Tivoli Workload Scheduler for Applications, version 8.2.1 or 8.1.1 cannot coexist within the same instance. For example r3batch 8.1.1 and mcmagent 8.2.1 cannot be installed on the same Tivoli Workload Scheduler agent. It is divided into the following sections: * 1.1.7.1, "Supported platforms" * 1.1.7.2, "Hardware and software prerequisites" * 1.1.7.3, "Fix pack installation methods" 1.1.7.1 Supported platforms Supported platforms at the time of the release are detailed in the User's Guide. For the most recent information, IBM maintains a matrix showing the supported operating systems for all its Tivoli products: http://www-306.ibm.com/software/sysmgmt/products/support/Tivoli_Supported_Platforms.html. Use the link to check the latest supported operating system information. 1.1.7.2 Hardware and software prerequisites Hardware and software prerequisites are detailed in the "Tivoli Workload Scheduler for Applications User's Guide" and in the download document. To locate the download document, see step 1 of the "IBM Tivoli Workload Scheduler for Applications Quick Start Guide", available with version 8.3 of the product. 1.1.7.3 Fix pack installation methods To install the fix pack, use the following methods: On Microsoft Windows, IBM AIX, HP-UX, Solaris operating environment, Linux on xSeries, Linux on zSeries, and Linux on eSeries * 1.1.7.3.1, "The InstallShield MultiPlatform (ISMP) wizard" * 1.1.7.3.2, "Silent Installation" * 1.1.7.3.5, "Software Distribution command line" * 1.1.7.3.6, "Alternate install script on IBM AIX, HP-UX, Solaris, Linux" On Compaq Tru64, SGI IRIX, IBM Sequent Dynix: 1.1.7.3.3, "Compaq Tru64, SGI IRIX, IBM Sequent Dynix installation method" On z/OS(R) access method 1.1.7.3.4, "z/OS installation method" Note: On UNIX platforms, if you want to install the language pack after having installed Tivoli Workload Scheduler 8.3.0, you need to log out and log in from the UNIX shell. 1.1.7.3.1 The InstallShield MultiPlatform (ISMP) wizard To install the fix pack using the InstallShield MultiPlatform (ISMP) wizard, perform the following steps: 1. Run the setup installation command appropriate for the operating system on which you are installing the fix pack. To see the setup installation commands, refer to 1.1.1, "Fix pack installation CDs and tar files organized by operating system" . The Welcome window is displayed. 2. Click Next to continue. The installation program detects and lists all the instances installed on your workstation. 3. From the list, select the instance on which you want to install the fix pack, and click Next to continue. 4. Choose one of the following actions and click Next to continue: APPLY Installs the fix pack. ROLLBACK Uninstall the fix pack. After you perform rollback you return to the previous committed version of the product. COMMIT Commits the fix pack. After you commit the fix pack you cannot rollback to the previous version. REPAIR Repairs the fix pack Note: The repair action repairs only the files specific to the Tivoli Workload Scheduler for Applications products that have been installed with the product (for example, access methods, option editor, ...). It does not repair files required by the installation process itself, for example, if you delete the _xauninst or _tools directories in the methods directory, the repair action does not recover them. 5. You are shown the location where the files are installed with the features you selected, click Next to continue. 6. The installation starts. 7. Click Finish to complete the installation. 1.1.7.3.2 Silent Installation This section describes how to install the fix pack using the setup installation command in silent mode. You can either specify the installation options directly on the command line or in a response file. To install the fix pack specifying the installation options directly on the command line, run one of the following commands: In a Windows environment: setup.exe -silent -P TWS4APPS.name -W DISPLAY_ACTION.selectedAction="action" -G overwriteJVM=yes In a UNIX environment: setup.bin -silent -P TWS4APPS.name -W DISPLAY_ACTION.selectedAction="action" -G overwriteJVM=yes where: name The Tivoli Workload Scheduler for Applications instance name. This is usually the Tivoli Workload Scheduler user that owns the Tivoli Workload Scheduler home directory where the method was installed. You have to specify the instance name assigning its value to this option. action The type of action you can perform. It can be one of the following values: APPLY Installs the fix pack. If the fix pack is already applied it will be interpreted as a repair action. UNDO Uninstall the fix pack. After you perform rollback you return to the previous committed version of the product. COMMIT Commits the fix pack. After you commit the fix pack you cannot rollback to the previous version. This is an example that performs the APPLY action to a fix pack on a UNIX workstation: setup.bin -silent -P TWS4APPS.twsuser -W DISPLAY_ACTION.selectedAction="APPLY" -G overwrite JVM=yes To install the fix pack using a response file, create your response file, or customize the silentfp.txt template response file contained in the RESPONSE_FILE directory of the fix pack. See the 1.1.1, "Fix pack installation CDs and tar files organized by operating system" Is the type for a detailed description of the fix pack CD structure. The response file must be accessible from the workstation where you want to perform the installation. Entries in the response file use the following format: option=value. Each entry must be written on a separate line. To install the fix pack using a response file, run one of the following commands: In a Windows environment setup.exe -silent -options responsefile In a UNIX(R) environment setup.bin -silent -options responsefile where responsefile is the fully qualified path to the response file you created. This is an example of a response file that performs the APPLY action on the fix pack: setup.bin -silent -options applyFPResponseFile" 1.1.7.3.3 Compaq Tru64, SGI IRIX, IBM Sequent Dynix installation method To install the fix pack, untar the files listed in 1.1.1, "Fix pack installation CDs and tar files organized by operating system" and follow the installation process described in the Tivoli Workload Scheduler for Applications User's Guide. Note: Before applying the fix pack, back up the methods directory. 1.1.7.3.4 z/OS installation method To install the fix pack, download the LOADLIB_830WSEFP01 and the SAMPLES_830WSEFP01 files contained in the ZOS directory of the fix pack to the z/OS system by following the instructions described in the User's Guide, Chapter 24 "Installing on z/OS", Section "Install and configure the z/OS gateway", Subsection "Unloading the Files from the CD". These files replace the files stored in the IBM Tivoli Workload Scheduler for Applications, Version 8.3.0. CD-ROM. See the 1.1.1, "Fix pack installation CDs and tar files organized by operating system" for a detailed description. 1.1.7.3.5 Software Distribution command line To install the fix pack using the Software Distribution command line perform the following steps: 1. Import the TWS4APPS_method_platform.SPB into the Profile Manager, using the wimpspo command as follows: wimpspo -c @ProfileManager -f source_path/TWS4APPS_method_platform_FP02.SPB -t build -p dest_path/TWS4APPS_method_platform_FP01.SPB [SoftwarePackageName.8.3.0.02] If you specify the SoftwarePackageName, this must be the same name you specified to install the IBM Tivoli Workload Scheduler for Applications, Version 8.3.0 software package. As default, if you do not specify the SoftwarePackageName, the software package profile TWS4APPS_method.8.3.0.01 is created in the profile manager. For a complete listing of the options required, see Chapter 2, "Installing, upgrading and uninstalling IBM Tivoli Workload Scheduler for Applications, section "Installing IBM Tivoli Workload Scheduler for Applications using Tivoli(R) Software Distribution version 4.1 or Tivoli Configuration Manager 4.2 or later" in the User's Guide. The following example shows how to install Fix Pack 2 of the r3batch access method on a Windows(R) endpoint, where the SoftwarePackageName is TWS4APPS_R3BATCH_I386NT.8.3.0. To install the fix pack 2 of the r3batch access method launch the following command: winstsp -uy -n TWS4APPS__R3BATCH.8.3.0.02 TWS4APPS_R3BATCH_I386NT_FP02.SPB Refer to the "IBM Tivoli Configuration Manager Reference Manual" for a detailed explanation of the wimpspo command. For a complete list of options required to install using Software Distribution, refer to the tables in Chapter 2 of "IBM Tivoli Workload Scheduler for Applications: User's Guide" Version 8.3.0. 2. Install the fix pack by running one of the following commands: To install the Fix Pack in undoable mode: winstsp -uy -D INSTALL_DIR=TWSHOME @SoftwarePackageName.8.3.0.02@Endpoint:endpointname To roll back to the previous code level: wundosp @SoftwarePackageName.8.3.0.02 @Endpoint:endpointname To commit the fix pack: waccptsp @SoftwarePackageName.8.3.0.02 @Endpoint:endpointname To remove the software package after performing the commit action: wremovsp @SoftwarePackageName.8.3.0.02 @Endpoint:endpointname To repair a fix pack installation: winstsp -mr @SoftwarePackageName.8.3.0.02 @Endpoint:endpointname 1.1.7.3.6 Alternate install script on IBM AIX, HP-UX, Solaris, Linux This section describes how to install and uninstall the fix pack using the twsappsFPinst script. The uninstall process uninstalls all access method simultaneously. Using the twsappsFPinst script you cannot: * Install the Option Editor * Have translated messages, because the installation script is not localized. All the messages are shown in English Because this installation script is included in the fix pack package, you can use it directly from the fix pack CD while applying a fix pack. Run installation actions using the twsappsFPinstcommand, use the following syntax: * If you want to know the syntax for the command, run: twsappsFPinst -u * If you want to know the version for the command, run: twsappsFPinst -v * If you want to apply the fix pack, run: twsappsFPinst -apply -twsuser []... [-inst_dir ] * If you want to commit the fix pack, run: twsappsFPinst -commit -twsuser []... [-inst_dir ] * If you want to rollback the fix pack, run: twsappsFPinst -rollback -twsuser user_name [access_method]... [-inst_dir TWS_install_directory] * If you want to uninstall the fix pack, run: twsappsFPinst -uninst -twsuser [-inst_dir ] Note: This will remove _tools and also_xauninst where: user_name Specifies the user under which Tivoli Workload Scheduler is installed. access_method Is one of the following: * SAP R/3 r3 * Oracle mcm * PeopleSoft ps * z/OS zos The following are examples of how to perform fix pack actions. In all the examples, the script is located in the /mnt/cdrom/AIX directory with the SPB directory and Tivoli Workload Scheduler is installed in the tws830 home directory (/home/tws830 Example 1 - Apply the fix pack to all the access methods belonging to the tws830 installation: [/mnt/cdrom/AIX]# ./twsappsFPinst -apply -twsuser tws830 Example 2 - The following example is equivalent to the previous (but it explicitly lists all the access methods): [/mnt/cdrom/AIX]# ./twsappsFPinst -apply -twsuser tws830 -r3 -zos -mcm Example 3 - Apply the fix pack to r3batch and zosagent only: [/mnt/cdrom/AIX]# ./twsappsFPinst -apply -twsuser tws830 -r3 -zos Example 4 - Apply the fix pack to r3batch only: [/mnt/cdrom/AIX]# ./twsappsFPinst -apply -twsuser tws830 -r3 The following are some usage examples to uninstall all the access methods or selected ones. Example 1- Uninstall the whole product (all the access methods) installed in the tws830 home directory; [/home/tws830/methods]# ./_xauninst/twsappsFPinst -uninst -twsuser tws830 Note: This command removes the _tools and _xauninst directories. Example 2- Uninstall the whole product (all the access methods) installed in the Tivoli Workload Scheduler instance in /opt/tws830 directory; [/home/tws830/methods]# ./_xauninst/twsappsFPinst -uninst -twsuser tws821 -twsdir /opt/tws830 Note: This command removes the _tools and _xauninst directories. 1.1.7.4 Interoperability tables The following tables show what associations are possible among component versions for: * Tivoli Workload Scheduler * Tivoli Workload Scheduler for Applications * Tivoli Workload Scheduler for z/OS * Distributed connector * z/OS connector * Job Scheduling Console * Dynamic Workload Console This table shows which versions of Tivoli Workload Scheduler and of the distributed connector, Job Scheduling Console, Dynamic Workload Console, and Tivoli Workload Scheduler for Applications can go together: Table 4. Interoperability table for Tivoli Workload Scheduler +-------------+---------+-----------+---------+-----------------------+ | Tivoli | Distrib | Tivoli | Tivoli | Tivoli Workload | | Workload | uted | Job | Dynamic | Scheduler for | | Scheduler | connect | Schedulin | Workloa | Applications | | | or | g Console | d | | | | | | Console | | +-------------+---------+-----------+---------+-----------------------+ | 8.3 | 8.3, | 8.3, | N/A | * 8.2, 8.2.0.01, | | | 8.3.0.0 | 8.3.0.01, | | 8.2.0.02, 8.2.0.03, | | | 1, | 8.3.0.02, | | 8.2.0.04, 8.2.0.05, | | | 8.3.0.0 | 8.3.0.03 | | 8.2.0.06, 8.2.0.07, | | | 2 | | | * 8.2.1, 8.2.1.0.01, | | | | | | 8.2.1.0.02 | | | | | | * 8.3, 8.3.0.01, | | | | | | 8.3.0.02 | +-------------+---------+-----------+---------+-----------------------+ | 8.3.0.01 | 8.3.0.0 | 8.3, | N/A | * 8.2, 8.2.0.01, | | | 1, | 8.3.0.01, | | 8.2.0.02, 8.2.0.03, | | | 8.3.0.0 | 8.3.0.02, | | 8.2.0.04, 8.2.0.05, | | | 2 | 8.3.0.03 | | 8.2.0.06, 8.2.0.07 | | | | | | * 8.2.1, 8.2.1.0.01, | | | | | | 8.2.1.0.02 | | | | | | * 8.3, 8.3.0.01, | | | | | | 8.3.0.02 | +-------------+---------+-----------+---------+-----------------------+ | 8.3.0.02 | 8.3.0.0 | 8.3, | 8.3 | * 8.2, 8.2.0.01, | | | 2, | 8.3.0.01, | | 8.2.0.02, 8.2.0.03, | | | 8.3.0.0 | 8.3.0.02, | | 8.2.0.04, 8.2.0.05, | | | 3 | 8.3.0.03 | | 8.2.0.06, 8.2.0.07 | | | | | | * 8.2.1, 8.2.1.0.01, | | | | | | 8.2.1.0.02 | | | | | | * 8.3, 8.3.0.01, | | | | | | 8.3.0.02 | +-------------+---------+-----------+---------+-----------------------+ | 8.3.0.03 | 8.3.0.0 | 8.3, | 8.3 | * 8.2, 8.2.0.01, | | | 3 | 8.3.0.01, | | 8.2.0.02, 8.2.0.03, | | | | 8.3.0.02, | | 8.2.0.04, 8.2.0.05, | | | | 8.3.0.03 | | 8.2.0.06, 8.2.0.07 | | | | | | * 8.2.1, 8.2.1.0.01, | | | | | | 8.2.1.0.02 | | | | | | * 8.3, 8.3.0.01, | | | | | | 8.3.0.02 | +-------------+---------+-----------+---------+-----------------------+ This table shows which versions of Tivoli Workload Scheduler for z/OS and of the z/OS connector, Job Scheduling Console, and Dynamic Workload Console can run together: Table 5. Interoperability table for Tivoli Workload Scheduler for z/OS +------------------+-------------+----------------+-------------------+ | Tivoli Workload | z/OS | Tivoli Job | Tivoli Dynamic | | Scheduler for | connector | Scheduling | Workload Console | | z/OS | | Console | | +------------------+-------------+----------------+-------------------+ | 8.1 | 8.3, | 8.3, 8.3.0.01, | N/A | | | 8.3.0.02 | 8.3.0.02, | | | | | 8.3.0.03 | | +------------------+-------------+----------------+-------------------+ | 8.2 | 8.3, | 8.3, 8.3.0.01, | N/A | | | 8.3.0.02 | 8.3.0.02, | | | | | 8.3.0.03 | | +------------------+-------------+----------------+-------------------+ | 8.2 + APAR | 8.3, | 8.3, 8.3.0.01, | 8.3 | | PK33565 | 8.3.0.02 | 8.3.0.02, | | | | | 8.3.0.03 | | +------------------+-------------+----------------+-------------------+ | 8.3 | 8.3.0.02 | 8.3, 8.3.0.01, | 8.3 | | | | 8.3.0.02, | Note: Version 8.3 | | | | 8.3.0.03 | of the scheduler | | | | Note: The new | is used in | | | | functions of | compatibility | | | | Tivoli | mode with 8.2. | | | | Workload | This means that | | | | Scheduler for | even though | | | | z/OS version | Tivoli Workload | | | | 8.3 are | Scheduler for | | | | supported only | z/OS version 8.3 | | | | on versions | is installed, | | | | 8.3.0.02 and | only the version | | | | later. | 8.2 functions can | | | | | be used. | +------------------+-------------+----------------+-------------------+ 1.1.8 Documentation notes This section contains new information and documentation corrections. Tivoli Workload Scheduler for Applications fix pack 2 now support TIS libraries for internationalization. To support this scenario add the following options to the option file: * UTF8CMDLINE = 1|0 to specify if chars will be sent between Tivoli Workload Scheduler for Applications and Oracle Business E-Suite in UTF8 or no. * UTF8CMDLINE = 1 to specify the channel communication in UTF8. * UTF8CMDLINE = O to use the Local Code Page set for Tivoli Workload Scheduler. * TWSXA_CP = CODEPAGE to specify the Local Code Page of DB of Oracle Business E-Suite remote server. Example 1: If DB of Oracle Business E-Suite is set in code page UTF8 open the WS_MCMAGENT.opts and add the following lines: UTF8CMDLINE = 1 TWSXA_CP = UTF8 Example 2: If DB of Oracle Business E-Suite is set in code page JA_jp open the WS_MCMAGENT.opts and add the following lines: UTF8CMDLINE = 1 TWSXA_CP = JA_JP 2.0 Contacting IBM Software Support Before contacting IBM(R) Software Support with a problem, refer to the IBM Software Support site by accessing the following Web address: http://www.ibm.com/software/support To access Tivoli support, click the Tivoli support link at the bottom right of the page. If you want to contact IBM Software Support, see the IBM Software Support Guide at the following Web site: http://techsupport.services.ibm.com/guides/handbook.html The guide provides information about how to contact IBM Software Support, depending on the severity of your problem, and the following information: * Registration and eligibility. * Telephone numbers, depending on the country in which you are located. * Information you must have before contacting IBM Software Support. 3.0 Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the users responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement might not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 2Z4A/101 11400 Burnet Road Austin, TX 78758 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. If you are viewing this information in softcopy form, the photographs and color illustrations might not display. 3.1 Trademarks IBM, the IBM logo, AIX(R), Tivoli, the Tivoli logo, and z/OS are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries | Java(TM) and all Java-based trademarks and logos are | trademarks or registered trademarks of Sun Microsystems, | Inc. in the United States, other countries, or both. Linux(TM) is a trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others.