Readme File for Fix Pack 1

Transcription

1 IBM Tioli Workload Scheduler Readme File for Fix Pack 1 Version 8.6.0

2

3 IBM Tioli Workload Scheduler Readme File for Fix Pack 1 Version 8.6.0

4 Note Before using this information and the product it supports, read the information in Notices on page 35. This edition applies to Fix Pack 1 for ersion 8, release 6, modification leel 0 of IBM Tioli Workload Scheduler (program number 5698-WSH) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 2011, US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents IBM Tioli Workload Scheduler Readme File for Fix Pack 1 for ersion About this fix pack Features introduced with Fix Pack Problems fixed APARs and defects fixed in Tioli Workload Scheduler Fix Pack 1 for ersion Known limitations and workarounds Globalization notes Fix pack structure Fix pack files aailable for Tioli Workload Scheduler using Fix Central Fix pack files aailable for batch reports using Fix Central Installing the fix pack Creating a fix pack installation package for a specific Tioli Workload Scheduler component Downloading and replacing files from GAFixes directory Installation notes Disk space requirements Performing a safe fix pack installation Customizing the safe fix pack installation using the wizard Customizing the safe fix pack installation using the silent method Customizing the safe fix pack installation using twspatch Installation actions Product actions when applying the fix pack Before Installing Untar the eimages for the Tioli Workload Scheduler for z/os Agent and Dynamic Agent on IBM i operating systems Installing using the ISMP wizard Installing using the ISMP silent installation Installing using the twspatch script Installing using Software Distribution Installing the fix pack on fault-tolerant agents when there are corrupt registry files Re-creating the registry files using the installation wizard Re-creating registry files using silent fix pack installation Re-creating registry files using twspatch Installing the batch reports Configuring properties for the dynamic workload broker command line Rolling back the fix pack installation Uninstalling the entire Tioli Workload Scheduler instance Installation log files Documentation updates Contacting IBM Software Support Notices Trademarks Copyright IBM Corp. 2011, 2012 iii

6 i IBM Tioli Workload Scheduler: Readme File for Fix Pack 1

7 IBM Tioli Workload Scheduler Readme File for Fix Pack 1 for ersion About this fix pack Date 8 June 2012 Fix Pack TIV-TWS-FP0001 Product IBM Tioli Workload Scheduler ersion General Description IBM Tioli Workload Scheduler Fix Pack 1 for ersion This readme file proides important information about Fix Pack 1 for IBM Tioli Workload Scheduler ersion This readme file is the most current information for the fix pack and takes precedence oer all other documentation for Tioli Workload Scheduler ersion Fix Pack 1. It is diided into the following sections: About this fix pack Fix pack structure on page 9 Installing the fix pack on page 10 Documentation updates on page 32 Reiew this section thoroughly before installing or using this Fix Pack. This section contains information specific for this fix pack including what has been modified or introduced, what has been fixed, product ersions or components to which the fix pack applies, and compatibility issues, if any. Product ersions and components to which the fix pack applies This fix pack can be applied only on top of Tioli Workload Scheduler V This section includes the following subsections: Features introduced with Fix Pack 1 on page 2 Problems fixed on page 3 Known limitations and workarounds on page 7 Globalization notes on page 9 Copyright IBM Corp. 2011,

8 Features introduced with Fix Pack 1 All the features introduced with Fix Pack 1 are described in the updated manuals in the information center: com.ibm.tioli.itws.doc_ /welcome_twa.html The following list contains details about some of these features: Authorizing the user to sae the credentials for a job type with adanced options in a centralized location In Tioli Workload Scheduler ersion 8.6, when defining a job with adanced options, you specify and sae the username and password in the credentials section of the job definition. If the password for a specific user changes, you must update all the job definitions for that user. In Tioli Workload Scheduler ersion Fix Pack 1, the database administrator can sae the password, proided in a job definition, in a centralized location. Regardless of the operating system of the dynamic agent running the job, the username and password alues, proided in the credentials section of the job, are saed in a user definition on the database. The password alue for the job credentials is resoled at run time with the alue stored in the database. For more information about this feature, see Tioli Workload Scheduler: User's Guide and Reference. To use this feature, you must hae the authorization set in the Security file to perform USE actions on USEROBJ objects. For further information,.see the Tioli Workload Scheduler: Administration Guide. The fix pack installation does not update the Security file installed on the master domain manager. If you want to include a new security statement, or add a new access keyword to a statement, you must do it manually. After the fix pack installation, if you need to update the Security file with a new authorization, follow these steps: 1. Log in as TWSUser on your master domain manager and set the Tioli Workload Scheduler enironment. 2. Extract the Security file using the command: dumpsec > sec_file where sec_file is the text file created by the dumpsec command. 3. Edit the file sec_file to insert the access keyword USE in the USEROBJ statement: userobj access=display,modify, altpass, use 4. Sae your changes in the file sec_file. 5. Build you security file for your master domain manager using the makesec command. makesec sec_file 6. If you hae centralized security feature enabled, distribute the Security file to the entire network. Manually setting the enironment in a dynamic agent to run the param and twstrace commands Tioli Workload Scheduler ersion Fix Pack 1 installs two new command lines to manage a dynamic agent: 2 IBM Tioli Workload Scheduler: Readme File for Fix Pack 1

9 The param command line, which creates and manages ariables and user passwords locally. For more information about this feature, see Tioli Workload Scheduler: User's Guide and Reference. The twstrace command line, which modifies the settings for tracing at run time. For more information about this feature, see Tioli Workload Scheduler: User's Guide and Reference. The existing file in your agent instance: <tws_install_dir>\tws\tws_en.bat for Windows operating systems <tws_install_dir>/tws/tws_en.sh for UNIX operating systems that are used to set the Tioli Workload Scheduler enironment, must be updated to support these commands. The fix pack installation program copies a new ersion of the existing file, that contains the alid settings to run the commands, into the <tws_install_dir>/tws/config directory. Manually, you either add the new settings to your existing file or merge the old and new ersions of the file. Profiler implemented to monitor connector APIs and EDWA rule builder time consumption A profiler has been implemented to monitor connector APIs and the rule builder time consumption related to eent-drien workload automation (EDWA). This profiler can be enabled or modified by setting the following properties located in the <tws_install_dir>/ewas/profiles/tipprofile/ properties/twsconfig.properties file: com.ibm.tws.util.profiling={truefalse} com.ibm.tws.util.profiling.erbose={truefalse} com.ibm.tws.util.profiling.interal=xx where xx is a alue expressed in minutes in the range from 1 to If the property com.ibm.tws.util.profiling.erbose is set to true, the profiler writes erbose information in the file <tws_install_dir>/tws/ profiling.txt. As a default, after the fix pack is installed, the profiler is disabled and no property is added to the <tws_install_dir>/ewas/profiles/tipprofile/ properties/twsconfig.properties file. Problems fixed This section lists all APARs and internal defects soled by this fix pack. For additional information about documentation APARs and internal defects, see Documentation updates on page 32. This section also proides information about the procedure for downloading and replacing GA fixes before starting the Tioli Workload Scheduler ersion installation. See Downloading and replacing files from GAFixes directory on page 12. This section includes the following topic: APARs and defects fixed in Tioli Workload Scheduler Fix Pack 1 for ersion on page 4 IBM Tioli Workload Scheduler Readme File for Fix Pack 1 for ersion

10 APARs and defects fixed in Tioli Workload Scheduler Fix Pack 1 for ersion This section lists APARs and internal defects soled by Fix Pack 1. Some APARs and internal defects need for resolution the GA fixed files, located under \CD_number\GAFixes directory. For more details, see the Downloading and replacing files from GAFixes directory on page 12. List of APARs fixed: IV00371: ERROR AWSBCZ111E ENCOUNTERED WHEN CREATING A VARIABLE TABLE USING COMPOSER ADD. IV00639: ISSUE WITH RERUN OF JOBS, AFTER LATEST START TIME, WHICH INCLUDEAN EVERY" FREQUENCY, AND SUPPRESS AFTER LATEST START TIME. IV00662: "CONMAN SC;GETMON" FAILS WITH NO MSG: /USR/LOCAL/TWS851/MAE851/TWS/SYMPHONY,,,0,. IV00921: FP2 OPENS HAS DOUBLE QUOTES AROUND THE FILE NAME. IV01408: AFTER APPLYING 8.5 FP02 JOB STREAMS ARE NOT REMOVED FROM PLAN AFTER UNTIL TIME REACHED. IV01550: AFTER SWITCHMGR, SEVERAL DM'S FAIL TO LINK AUTOMATICALLY, AND REQUIRE A MANUAL RELINK. IV01873:JOB SUBMITTED WITH ALIAS VIA TDWC DOES NOT SHOW THE ORIGINAL JOBNAME IN THE PLAN AUDIT LOG OR TWSMERGE. IV01885:TDWB AGENT GIVES AWSITA082E ERROR WHEN TWO HARDWARE SCAN HAPPENS WITHIN SECONDS OF EACH OTHER. IV02089: EWAS UPGRADE FAILS DUE TO NOT ENOUGH FREE DISK SPACE. IV02340: Time of predecessor jobs and dependency prompts on JSC and TDWC are in GMT IV02406: INTERNETWORK DEPS DONT WORK USING SCHEDTIME WITH MULTIPLE JS. IV02414: MDM THREADS HANG WHEN AN ERROR READING FROM SYMPHONY FILE OCCURS WHILE JOB LOGS ARE RETRIEVED. IV02797: IN E2E ENVIRONMENT, CENTRALIZED SCRIPTS RUN ON UNIXLOCL EXTENDEDAGENTS (XAS), ONLY COMPLETE THE FIRST LINE. IV03447: MAKEPLAN AND SWITCHPLAN SUCCEED WHEN PLANMAN WAILS WITH AWSBEH021E ERROR. IV03559: SSMAGENT DOESN'T WORK IF TWS INSTALL PATH IS TOO LONG IV03894: DOES_NOT_MATCH IS IGNORED WHEN MULTIPLES ARE USED. IV06620: FIX THE MECHANISM USAGE TO CREATE THE JOB ALIAS DURING ADHOC SUBMISSION. IV06734: CONNECTION ERROR LOGGED EVERY FIVE MINUTES IF DATABASE IS NOT AVAILABLE. IV06847: AWSJCO111E HAPPENS ON SAVING EVENT RULE THROUGH TDWC. IV07182: STAGEMAN FAILED WITH AWSBHV021E. 4 IBM Tioli Workload Scheduler: Readme File for Fix Pack 1

11 IV07279: TEMPORARY FILE IS CREATED AND NOT REMOVED BY "COMPOSER REPLACE" OF JOBS. IV07336: ZCENTRIC AGENT INSTALLATION IMAGE FOR WINDOWS 64 BIT VERSION. IV07340: MAILMAN CORE DUMP AFTER FAILED LINK ATTEMPT TO FTA CHECKHEALTHSTATUS FAILURE ON MDM MAILMAN LEADS TO COREDUMP. IV07655: Memory leak in netman process when starting a serice. IV07688: AWSJMR003E A TRANSPORT PROBLEM WAS FOUND - GSKIT LIBRARIES. IV07874: ERROR 500 WHEN ADDING JOB VIA COMPOSER. IV07888: WINDOWS 'CPCH' COMMAND DOES NOT WORK AT ZCENTRIC WORKSTATIONS. IV08543: TSM INTEGRATION: TSM JOBS ABENDING WHEN PASSING THE MIDNIGHT. IV08700: TWS WEBSERVICE API RETURNS EPOCH DATE FOR START AND END TIMES. IV08995: CONMAN ALTPRI IS LOST WHILE SYMPHONY SWITCH. IV09145: TWA_ENV SCRIPT FAILS TO SET PATH. IV09379: AFTER SETTING A NEW UNTIL TIME, UNTIL DOES NOT OCCUR AT A NEW UNTIL TIME. IV09453: LATEST START TIME NOT WORKING CORRECTLY. IV09908: PARAMETERS FILE DOES NOT GET IMPORTED IN TWS UPGRADE USING TWSINST.SH. IV10349: CONMAN RERUN FROM BEHAVES DIFFERENTLY THAN JSC/TDWC RERUN FROM. IV10400: DELAY IN VIEWING JOBLOG IN JSC ON HPUX. IV10403: JOBMON HANG AFTER THE CLUSTER FAILOVER. IV10438: FILEMODIFICATIONCOMPLETE EVENT RULES NOT TRIGGER ON FTA. IV10460: CONMAN CAN NOT LOAD ICU LIBRARIES. IV11228: JOBMAN CRASHES WITH ERROR AWSBIK007E. IV12331: MISSING JAR FILE WHEN USING JAVA API WITH TWS 8.6. IV12413: IN THE CURRENT PLAN, "RELEASE JOB" COMMANDS ARE DISCARDED FROM THE PREVIOUS DAY'S PRODUCTION PLAN IN TIVOLI WORKLOAD SCHEDULER. IV12500: RUNCYCLES WITH RULE BYWORKDAY OR BYFREEDAY, IN SOME CIRCUMSTANCES CAN SLOW-DOWN THE PLAN CREATION. IV12548: COMPOSER VALIDATE ON SCHEDULE'S FLAT FILE GENERATES AN ICALENDARERROR SYNTAX ERROR WHEN THE RUN CYCLE IS LONGER THAN 128 BYTES. IV12564: EWAS IS NOT ABLE TO AUTHENTICATE LDAP GROUP MEMBERS FOR TWS. IV13189: INSTALLTEB.CMD FAILS ON WINDOWS WHILE INSTALL TWS 8.6 GA. IV13294: ZCENTRIC AGENT JOBS WITH STDERROR- AND STDOUTPUT-CARD EXECUTING POWERSHELL SCRIPTS HANG AND HAVE TO BE KILLED. IV13825: CONMAN TELLOP ADDS LINE BREAK. IBM Tioli Workload Scheduler Readme File for Fix Pack 1 for ersion

12 6 IBM Tioli Workload Scheduler: Readme File for Fix Pack 1 IV13950: INLINE SCRIPTS WITH CURLY BRACKETS CAUSE JOB FAILURE. IV14569: INTERNETWORK DEPENDENCIES ARE NOT BEING CLEARED WHEN CANCELED. IV15366: TDWC 8.6 RUNNING A REPORT ON A CURRENT PLAN WITH A LARGE SYMPHONY FILE RETURNS NO RESULTS. IV15451: AWSBCV012E ON CHILD DM FOLLOWING SWITCHMGR. IV15710: MVS OPENS DEPENDENCY IS NOT RECOGNIZED. IV15887: JOBMANGER CRASH DUE SIGPIPE IF THE COMMUNICATIONS WITH THE BROKER IS BROKEN, FOR EXAMPLE NO TRUSTED CERTIFICATE. IV16134: AFTER CONMAN SUBMIT INPUTS BAD RECORD INTO SYMPHONY FILE. IV16852: REMOVE ICON ABOUT MULTIPLE FILE NAME IN THE EVENT RULE FILE NAMEFILECREATED,FILEDELETE,FILEMODIFICATIONCOMPLETED ETC. IV17252: LOGMAN CORE DUMPS DURING UPDATESTATS. IV17638: TWS 8.6:JOBS WITH AT BETWEEN 0000 AND SOD GET START TIME ONE DAY LATE. IV17907: MAKEPLAN RETURN 0 EVEN IF THE PLAN WAS NOT CREATED AT ALL. IV19237: WEBSPHERE (JAVA) CRASHES INTERMITTENTL. IZ95386: TDWC SHOULD SHOW DEPENDENCIES AS THEY APPEAR ON CONMAN. IZ95391: WINDOWS OS ENVIRONMENT VARIABLE ARE DUPLICATED SINCE KB ARTICLE SUPPORT.MICROSOFT.COM/KB/ IZ96555: TIMEOUT CONDITIONS RELATED TO ROUTER PROCESS USED TO DOWNLOAD CENTRALIZED SCRIPTS. SIMILAR TO Z/OS APAR PM IZ97073: ZCENTRIC JOBS WITH '$ IN THE NAME GO IN ERROR. IZ97356: ROUTER STUCK AFTER A PROBLEM CONNECTING THE AGENT. IZ98358: RMSTDLIST FAILS ON TWS FP1 WINDOWS 2003 CLUSTER. IZ98964: TWS JOBNUMBER INVALID IN EVENT.LOG ON LINUX 64BIT. IZ99233: EVENT RULE ALLOWS JOB SUBMIT WHEN JOBSTREAM SPECIFIED DOES NOT EXIST. IZ99333: DELAY IN JOB STARTING EVEN THOUGH CANCEL PENDING DEPENDENCY HAS BEEN PROCESSED. IZ99697: THE NUMBER OF FILE DEPENDENCIES UNRESOLVED IS SET TO 1, ALTHOUGH ALL OF THEM ARE RESOLVED. IZ99755: NEW OPTION TO SKIP JOB EVERY INSTANCE IN LATE. IZ99893: LOG MESSAGE WRITTEN EVENT TRIGGERS 1 TRAP FOR N MESSAGES INSTEAD OF 1 TRAP PER MESSAGE. PM53893: TWS 8.6 and DWC 8.6: shared ewas hung. The Tioli Workload Scheduler and Dynamic Workload Console instances sharing the same Websphere Application Serer, might become

13 unresponsie after some days. This issue has been soled by this fix pack that embeds the new Tioli Integrated Portal leel. List of defects fixed: This list contains the defects that fixed some of the limitations reported in the Tioli Workload Scheduler Version Release Notes: 52510: AWKRAA207E The EMF framework is not initialized properly while starting Jaa Job for each job submitted on a zcentric 52782: Was loop performing multiple EDWA actions 54123: Timeout during Symphony download : eent.log after JnexPlan,stop/start was, doesn't work 55478: SCHEDULED TIME OF THE PREDECESSOR JOB IN GMT ON TDWC : _TWSMERGE.log hae wrong group and onwer : Composer tmp files should not be world-writable : 851FP3 with Oracle fails to migrate to 86 (ORA-02443) : JobManager on DDM WIN bit dump continously 58295: Solaris x86 JobManager dies after a while : TWS trace folder increases size indefinitely 59723: master ewas HANG: requesting a JOBLOG output of a database job on 86FP1 agent and old master : Base: GVT: Unable to submit jobs on a workstation more than one time CMVC(56476) 59680: JnextPlan doesn't work after upgrade from TWS 851fp1 to 8.6GA : SSO doesn't work (from TDWC 86 FP1) after master upgrade to 86 GA. See Downloading and replacing files from GAFixes directory on page : ssmagent dies to manage 50K eents (1000 rules, 50 files) 60190: Jaa Runtime Exception performing a pick list and executing jaa jobs on HPIA64 machine 60585: JobManager hang after submission of multiple jaa jobs 60834: CIT step fails if you install TWS 86 GA after a TWS 86 fp1 installation on the same machine : The apply FP1 operation fails on a Windows 64 bit machine. Known limitations and workarounds The following are software limitations and workarounds that affect Tioli Workload Scheduler ersion Fix Pack 1: During installation: Installation at step 0 doesn't stop with TWS command lines opened (60595) On AIX operating systems, the IBM Tioli Workload Scheduler fix pack installation might fail: apply action at step 0 rollback action at step 12 IBM Tioli Workload Scheduler Readme File for Fix Pack 1 for ersion

14 One possible cause is that the process is unable to recognize whether a file is locked, and is therefore unable to erify if the IBM Tioli Workload Scheduler command lines are open or if IBM Tioli Workload Scheduler jobs are running. Before installing running the fix pack, update the AIX operating system to a later ersion. twspatch output completely corrupted on some Windows platforms (59219) On platforms running Windows Vista, Windows 2008, or Windows 2007, the output of the twspatch command is corrupt. Workaround 1: Open the generated file with an editor supporting the UTF-8 character set. Workaround 2: Redirect the output of the twspatch command to a file Open a command prompt window and type chcp Open the generated file with no errors Missing config.ini settings after fix pack apply and undo (60221) If you apply the fix pack and then undo it, the original <tws_install_dir>\tws\jaaext\eclipse\configuration\ config.ini file is restored. If, after the fix pack is applied and before it is undone, you installed any plug-in, the settings related to this plug-in are lost. You can recoer these settings from the <tws_install_dir>\tws\ JaaExt\eclipse\configuration\config.ini.tomerge file and manually merge its content with the tws\jaaext\eclipse\ configuration\config.ini file. Fault-Tolerant Agent not working with distributor connector (61632) If you install this fix pack on a fault-tolerant agent and then install the distributed connector, the fault-tolerant agent might hae an unexpected behaiour. Workaround: To aoid this, first install the distributed connector and later apply this fix pack. At run time: EDWA: With high load, sometimes some eents are lost (60056) With high load, sometimes some eents can be lost, and consequently related actions are not run. If you enable the SSL for Tioli Eent integration facility, the problem does not occur. EDWA: ssmagent memory consumption with SSL enabled might occur (62010) If you are monitoring a high number of files using the FileMonitorPlugIn, you might see a high memory consumption for the ssmagent process. To reduce the memory used by the ssmagent process, if you are monitoring FileCreated eents, delete the files created, otherwise, stop and restart the ssmagent process. During uninstallation: Graphical rollback might get stuck at times (RTC 61813) If you perform a graphical rollback of this fix pack, the process might get stopped at the step Start the Tioli Workload 8 IBM Tioli Workload Scheduler: Readme File for Fix Pack 1

15 Globalization notes None. Fix pack structure Scheduler instance but the startup completes successfully. The reason is that the machine has exhausted its resources. Workaround: Kill the installation process, resume it, and run the other remaining steps. This section describes the structure of the images contained in this fix pack. Fix pack files aailable for Tioli Workload Scheduler using Fix Central This is the structure of the fix pack for the engine on Fix Central: TIV-TWS-FP0001.README (this file in text format) TIV-TWS-FP0001.pdf (this file in pdf format) TIV-TWS-FP0001.VSR TIV-TWS-AIX-FP0001.zip TIV-TWS-HPUX-FP0001.zip TIV-TWS-HPIA64-FP0001.zip TIV-TWS-LINUX_I386-FP0001.zip TIV-TWS-LINUX_PPC-FP0001.zip TIV-TWS-LINUX_S390-FP0001.zip TIV-TWS-LINUX_X86_64-FP0001.zip TIV-TWS-SOLARIS-FP0001.zip TIV-TWS-SOLARIS_I386-FP0001.zip TIV-TWS-WINDOWS-FP0001.zip TIV-TWS-WINDOWS_X86_64-FP0001.zip TIV-TWS-IBM_I-FP0001.tar TIV-WSSDK-WINDOWS-FP001.zip TIV-WSSDK-WINDOWS_X86_64-FP001.zip TIV-WSSDK-LINUX_X86_64-FP001.zip TIV-WSSDK-LINUX_I386-FP001.zip Fix pack files aailable for batch reports using Fix Central This is the structure of the fix pack for batch reports on Fix Central: TIV-REPCLI-SOLARIS_I386-FP0001.tar TIV-REPCLI-AIX-FP0001.tar TIV-REPCLI-WINDOWS-FP0001.zip IBM Tioli Workload Scheduler Readme File for Fix Pack 1 for ersion

16 Installing the fix pack TIV-REPCLI-LINUX_PPC-FP0001.tar TIV-REPCLI-HPUX-FP0001.tar TIV-REPCLI-SOLARIS-FP0001.tar TIV-REPCLI-LINUX_X86_64-FP0001.tar TIV-REPCLI-HPIA64-FP0001.tar TIV-REPCLI-WINDOWS_X86_64-FP0001.zip TIV-REPCLI-LINUX_I386-FP0001.tar TIV-REPCLI-LINUX_S390-FP0001.tar This section describes how to apply Fix Pack 1 to Tioli Workload Scheduler ersion The section is diided into the following subsections: Creating a fix pack installation package for a specific Tioli Workload Scheduler component Downloading and replacing files from GAFixes directory on page 12 Installation notes on page 12 Disk space requirements on page 15 Performing a safe fix pack installation on page 16 Product actions when applying the fix pack on page 20 Installation actions on page 18 Installing using the ISMP wizard on page 23 Installing using the ISMP silent installation on page 24 Installing using the twspatch script on page 25 Installing using Software Distribution on page 27 Installing the fix pack on fault-tolerant agents when there are corrupt registry files on page 28 Configuring properties for the dynamic workload broker command line on page 31 Rolling back the fix pack installation on page 31 Uninstalling the entire Tioli Workload Scheduler instance on page 31 Installation log files on page 31 Creating a fix pack installation package for a specific Tioli Workload Scheduler component In Tioli Workload Scheduler ersion 8.6, you could choose to download either the eimage for the platform, which contains the installation package for all the components for that platform, or just the specific eimage for the component you require. In Tioli Workload Scheduler ersion 8.6 Fix Pack 1, you must download the eimages for the platform and you can use this package to install Fix Pack 1 for all the components or you can create the specific installation package for the component you need, by running a script located in the Fix Pack 1 eimages. 10 IBM Tioli Workload Scheduler: Readme File for Fix Pack 1

17 The Tioli Workload Scheduler ersion 8.6 Fix Pack 1 eimages contain a script for each platform, which creates the specific package for the component from the original fix pack eimages. Before installing Tioli Workload Scheduler ersion 8.6, if you want to create a specific component image to install, perform the following procedure: 1. Download locally Tioli Workload Scheduler ersion 8.6 Fix Pack 1 images. 2. From the <platform>\tws_tools\ directory, run: Windows operating system createtwsfpimage.bat -type ftaagent [-destination <NEW_IMAGE_DIR>] [-remoesetup truefalse] UNIX and Linux operating systems createtwsfpimage.sh -type ftaagent [-destination <NEW_IMAGE_DIR>] [-remoesetup truefalse] where type This parameter is required. Specify fta for fault-tolerant agent image or agent for Tioli Workload Scheduler agent (agent, dynamic agent, or agent for z/os). destination This parameter is optional. Specify the absolute path for the folder that contains the new image. The default is the folder where the current image is located and the script runs. If the destination is not specified, the script remoes locally the files not needed for the image type chosen. remoesetup This parameter is optional. Specify that the new image does not contain the ISMP file SETUP.exe for Windows operating systems or SETUP.bin for UNIX operating systems. The default is false and the new image created contains the ISMP file. Example 1 On a Windows machine, if you want to create the image to install Fix Pack 1 on a fault-tolerant agent installed on an AIX operating system, using twspatch script, perform the following actions: 1. Download the Fix Pack 1 eimage for the AIX platform on the Windows machine. 2. To create the Fault-Tolerant Agent component image on the directory C:\Documents and Settings\Administrator, from the directory AIX\tws_tools\, run: createtwsfpimage.bat -type fta -destination "C:\Documents and Settings\Administrator" -remoesetup true Note: In this example you set remoesetup to true because, to install with twspatch, you do not need the file SETUP.bin. Example 2 On a Windows machine, if you want to create, the image to install Fix Pack 1 for an Agent for z/os installed on a Windows operating system, using the wizard, perform the following actions: IBM Tioli Workload Scheduler Readme File for Fix Pack 1 for ersion

18 1. Download the Fix Pack 1 eimage for the Windows platform on the Windows machine. 2. To create the Agent for z/os component image on the directory C:\Documents and Settings\Administrator, from the directory Windows\tws_tools\ run: createtwsfpimage.bat -type agent -destination "C:\Documents and Settings\Administrator" Downloading and replacing files from GAFixes directory The Tioli Workload Scheduler ersion 8.6 Fix Pack 1 images contain the directory GAFixes, which includes the fixed files for General Aailability installation. Before restarting the Tioli Workload Scheduler ersion 8.6 installation, perform the following procedure: 1. Download locally Tioli Workload Scheduler ersion 8.6 images. 2. Download locally Tioli Workload Scheduler ersion 8.6 Fix Pack 1 images. 3. Go to the GAFixes directory and perform the actions described below: If you hae an earlier ersion of Dynamic Workload Console and Tioli Workload Scheduler installed that share the same LDAP user Registry and they are configured to use SSO (Single Sign-On) and you upgrade the Dynamic Workload Console, the Tioli Workload Scheduler or both to ersion 8.6.0, the SSO configuration is lost. Fix Pack 1 images proide the files to fix the problem. Replace the following file: GAFixes\tws_tools\ChangeSecurityProperties.jacl in the directory <platform>\tws\<platform> of Tioli Workload Scheduler ersion 8.6 images On Windows operating systems, Tioli Workload Scheduler ersion 8.6 installation fails if you use the SYSTEM user. Fix Pack 1 images proide the files to fix the problem. Replace the following file: GAFixes\twsinst.bs in the directory <platform>\tws\<platform> of Tioli Workload Scheduler ersion 8.6 images The installation of a Dynamic agent on an Iseries machine, using the twsinst method on a QP2TERM fails, because the installation process is unable to start the agent. Fix Pack 1 images proide the files to fix the problem. Replace the following file: GAFixes\\twsinst in the directory <platform>\tws\<platform> of Tioli Workload Scheduler ersion 8.6 images. 4. If step 3 completed successfully, start the installation from Tioli Workload Scheduler ersion 8.6 images. 5. If step 4 completed successfully, start the fix pack installation from Tioli Workload Scheduler ersion 8.6 Fix Pack 1 images. Installation notes When installing the Tioli Workload Scheduler, follow these recommendations: 12 IBM Tioli Workload Scheduler: Readme File for Fix Pack 1

19 On UNIX only: Before installing the Tioli Workload Scheduler fix pack ersion 8.6.0, ensure that your umask is set to 022. To erify that umask is set to the correct alue, from a command prompt run the umask command. If the alue is different from 022, modify it by running: umask 022 On UNIX operating systems, the data base administrator must hae read and run priileges for the Tioli Workload Scheduler installation path; otherwise the installation fails. (54367) On UNIX operating systems, the installation might fail with a message indicating that there is a problem when alidating the Jaa Virtual Machine (JVM). This might be caused by a timeout problem. The InstallShield wizard uses a default timeout of 5 seconds during its operations to alidate the ersion of Jaa Virtual Machine that you hae installed, which might be insufficient. Before launching the installation wizard again, increase the timeout alue by running the following command: -is:jmtimer 100 This extends the timeout to 100 seconds, and if you still get the same error message, increase it to 200 seconds. On workstations running Linux Red Hat 64-bit, if the problem persists, set the ariable setenforce to 0 using the following command: /usr/sbin/setenforce 0 and then launch the installation again. To install, undo, and commit the fix pack, use the same installation method (ISMP, twspatch) that you used to install the General Aailability ersion. Note: If you install the fix pack with the action APPLY using the installation method twspatch, to roll back to the preious leel, use the command twspatch -undo. To uninstall the entire Tioli Workload Scheduler instance, use the command twspatch remoe, but note that this action is not intended to remoe the applied fix pack without also uninstalling the instance (51112). On Windows operating systems, do not install from a Samba disk On HP-UX, systems, the default alue for the kernel parameter max_thread_proc is 64. Set this alue to at least 128 otherwise the installation can fail and cause Jaa to generate a core dump. If you get an error message indicating insufficient space for the installation wizard temporary data in the default /tmp directory, you can launch the installation wizard with the is flag and set an alternatie temporary directory. For example, SETUP.sh [-is:tempdir <temporary_directory>]. For additional information about disk and space requirements for the installation, see Detailed system requirements. If you get an error message indicating permission denied for the installation process, to run a script in the tws_tools directory as a user, different from the root user because this user does not hae write, read, and execute rights in this directory, you must: 1. Unzip the eimages in a directory where all users hae write, read, and execute rights. 2. Restart the installation process from this directory. Before updating the Tioli Workload Scheduler serices and DLL, it is strongly adised to put the Tioli Workload Scheduler resources offline and the nodes in pause. (IV09792) IBM Tioli Workload Scheduler Readme File for Fix Pack 1 for ersion

20 When installing the batch reports, follow these recommendations: On Solaris Opteron operating systems, the extraction of the file TIV-REPCLI-SOLARIS_I386-FP0001.TAR might fail with the error: átar:reportengine/configuration/ org.eclipse.core.runtime/.contributions.6: HELP - extract write error To preent this error, upgrade to a release of the operating system that includes a newer ersion of the tar command, or to a more recent maintenance leel that includes a newer ersion of tar. After the fix pack installation completes, erify the following information: On IBM i operating systems, if you want to install the fix pack on the Tioli Workload Scheduler for z/os Agent and Tioli Workload Scheduler Dynamic Agent, erify that the User profile used as TWSUser is not a member of a group profile. Set the group profile associated with the TWSUser to *NONE. Ifthe TWSUser is a member of a group, the fix pack installation fails. After installing the fix pack, the last line of the TWS_home/ersion/patch.info file contains: TIV-TWS-FP0001. During the fix pack installation the following file is remoed and a new one is created when the WebSphere Application Serer is restarted: TWA_home/eWAS/profiles/TIPPprofile/temp/TWS/EIFListener/eif.templ If you preiously modified the property BuffEtmaxSize, after installing the fix pack you must set it again in the new file, as described in the IBM Tioli Workload Scheduler Administration Guide, Chapter 9, Administratie tasks, section Managing the eent processor. (38192) On Windows systems, jobs that belong to Final jobstream, go into abend state if the master domain manager is installed in a directory other than the C: drie. Workaround: To sole this problem, merge the content of these files: <tws_homw>\resetplan.cmd <tws_homw>\jnextplan.cmd <tws_homw>\makeplan.cmd <tws_homw>\switchplan.cmd <tws_homw>\createpostreports.cmd <tws_homw>\updatestats.cmd with those under <tws_home>\config. They are not replaced by fix pack installation because they can be customized. (53435) There is a mismatch for some Tioli Workload Scheduler enironment ariables. UNISONHOME On Windows operating systems, it does not exist or is blank. On UNIX operating systems, it is the alue of the UNISONHOME ariable, set in the user enironment. If not specified, its alue is set to the user home directory. This ariable must hae, on all operating systems, the alue of the path where the Tioli Workload Scheduler instance is installed. HOME This ariable is not documented for Windows operating systems, but is the path where the Tioli Workload Scheduler instance is installed. On UNIX operating systems it is the user home directory. (53442) 14 IBM Tioli Workload Scheduler: Readme File for Fix Pack 1

21 To grant permissions to users on the updated database iews, run the dbgrant script again after the fix pack installation, only if the following conditions are both satisfied: The database used by Tioli Workload Scheduler is DB2. The dbgrant script was already run before installing this fix pack. (38487) Only on Windows platforms, after the fix pack installation, a new ersion of file twa_en.bat is created in the following directory: <tws_home>\tws\config. If you customized the original file <tws_home>\twa_en.bat, you must merge the content of these files to keep your customization. (55999) After the fix pack installation, if you run the command conman sc;info, it shows the old product ersion. To get the updated ersion, wait for the next plan to be created and distributed. Howeer, the updated ersion is in the file <tws_home>\ersion\patch.info immediately after the fix pack installation. (RTC 59988) After installing the fix pack on a fault tolerant agent with all configured cluster nodes, the output shows the old product ersion for the DLLs installed on each node. In any case, the nodes are updated and if you run again the command to show the ersion, you get the current product ersion. (RTC 59999) When connecting to the Dynamic Workload Console V8.6 Fix Pack 1, using the same browser preiously used to connect before the fix pack installation, the browser might still display page elements related to the Dynamic Workload Console V8.6. This behaiour is not expected to cause any product malfunctions; howeer, to preent it, clear the browser cache. (RTC 61420) When installing Tioli Workload Scheduler V8.6 General Aailability (GA) on a fault tolerant agent using the twsinst installation script, the licence directory is not created and the licence files are not copied on the fault tolerant agent. If you want to access these files, you can find a copy on the installation CDs in the directory TWS/License. (RTC 61947) Disk space requirements Before starting the fix pack installation, ensure that you hae the following space aailable in the file system: Table 1. Disk space requirements for installing a master domain manager or a backup master fix pack Operating System Installation directory Software distribution installation directory Temporary directory AIX 2 GB 400 MB 500 MB HP-UX 2.5 GB 400 MB 720 MB Solaris 2 GB 400 MB 720 MB Microsoft 2 GB 400 MB 500 MB Windows Linux 2 GB 400 MB 500 MB IBM Tioli Workload Scheduler Readme File for Fix Pack 1 for ersion

22 Table 2. Disk space requirements for installing Tioli Workload Scheduler agents and the Jaa Extension fix pack Operating System Installation directory Software distribution installation directory Temporary directory AIX 1500 MB 300 MB 40 MB HP-UX 1700 MB 300 MB 40 MB Solaris 1500 MB 300 MB 40 MB Microsoft 1500 MB 300 MB 40 MB Windows Linux 1500 MB 300 MB 40 MB Table 3. Disk space requirements for installing Tioli Workload Scheduler agents fix pack Operating System Installation directory Software distribution installation directory Temporary directory AIX 20 MB 80 MB 40 MB HP-UX 20 MB 80 MB 40 MB Solaris 20 MB 80 MB 40 MB Microsoft 20 MB 80 MB 40 MB Windows Linux 20 MB 80 MB 40 MB Table 4. Disk space requirements for installing the Tioli Workload Scheduler for z/os agent fix pack Operating System Installation directory Software distribution installation directory Temporary directory AIX 20 MB 20 MB 40 MB HP-UX 500 MB 20 MB 40 MB Solaris 20 MB 20 MB 40 MB Microsoft 20 MB 20 MB 40 MB Windows Linux 20 MB 20 MB 40 MB Note: Only on HP and Solaris operating systems, the fix pack installation requires also 300 MB free disk space in the temporary directory /ar/tmp. Performing a safe fix pack installation Tioli Workload Scheduler installs fix packs in safe mode, to ensure integrity of the running processes. Before starting the installation, the product performs the following actions: Checks if there are command lines currently running. 16 IBM Tioli Workload Scheduler: Readme File for Fix Pack 1

23 Preents other jobs from starting by setting the job fence on the workstation to the go (101) alue. Checks if there are jobs running. If there are, it waits 60 minutes and checks again. If all the jobs do not complete during this interal, the fix pack installation does not proceed and an error message is displayed. If you want to change this alue, specify the number of minutes when you run the setup, perform a silent installation, or using twpatch script. This alue can be an integer or you can specify the alue -1 for the product to wait indefinitely. The default is 60. To customize the number of minutes the installer waits for running jobs to complete, see: Customizing the safe fix pack installation using the wizard. Customizing the safe fix pack installation using the silent method on page 18. Customizing the safe fix pack installation using twspatch on page 18. Note: The safe fix pack installation is aailable with all the installation methods except using Software Distribution. Checks if there are processes running. If there are, it stops them. If all these checks are passed, Tioli Workload Scheduler starts the fix pack installation. If the fix pack installation completes successfully, after the Batchman process restarts, the job fence on the workstation is set to its original alue because there is a synchronization between the Batchman message queues and Symphony file for the job fence alue. The installation process does not start the Batchman process and to set the original job fence on your workstation, run: conman "start" If the fix pack installation does not complete successfully, either because the checks are not passed or an error occurs, the job fence is not set to the original alue and you must: Set the job fence manually to its original alue. Perform the steps to correct the errors and resume the fix pack installation. Note: If the fix pack installation is successful and you do not restart the Batchman process, there is no a synchronization between the Batchman message queues and the Symphony file for the job fence alue, which is set to GO. If you perform an undo fix pack action, without restarting the Batchman process, for the installation process the original job fence alue is GO and, after the undo action, when Batchman restarts the workstation fence is wrongly set to GO and the jobs do not start. Customizing the safe fix pack installation using the wizard To modify the number of minutes the installer waits for running jobs to complete, when you run the installation wizard, perform the following steps: From the installation DVD or from the downloaded images, run one of the following commands: Windows operating system From the WINDOWS directory, run: SETUP.exe -W checkjobsloop.wait=alue IBM Tioli Workload Scheduler Readme File for Fix Pack 1 for ersion

24 UNIX and Linux operating systems From the operating_system directory, run: SETUP.bin -W checkjobsloop.wait=alue Customizing the safe fix pack installation using the silent method To modify the number of minutes the installer waits for running jobs, when you run a silent fix pack installation method, perform the following steps: 1. Copy the response file to a local directory, according to your operating system: patchinstall.txt 2. Edit the response file by specifying the parameter: -W checkjobsloop.wait=alue. 3. Sae the file with your changes. 4. Enter the following command: Windows operating systems SETUP.exe -options local_dir\patchinstall.txt -silent where patchinstall.txt is the name of the response file to use for fix pack installation. The SETUP.exe file is located in TWS\operating_system. UNIX and Linux operating systems./setup.bin -options local_dir/patchinstall.txt -silent where patchinstall.txt is the name of the response file to use for fix pack installation. The SETUP.bin file is located in the TWS/operating_system directory. Customizing the safe fix pack installation using twspatch To modify the number of minutes the installer waits for running jobs to complete, when you run the twspatch script, perform the following steps: From the installation DVD or from the downloaded images, run one of the following commands: Windows operating system From the WINDOWS directory, run: twspatch.bs -install -uname TWS_user -wait minutes UNIX and Linux operating systems From the operating_system directory, run:./twspatch -install -uname TWS_user -wait minutes Installation actions When you install the fix pack, you can perform one of the following actions: APPLY Use this action to install the fix pack without making it permanent. Product actions when applying the fix pack on page 20 lists the actions the product performs when you apply the fix pack. ROLLBACK Use this action to roll back to the preious leel if you did not committed it. COMMIT Use this action to make the fix pack permanent. A rollback operation is no longer possible. 18 IBM Tioli Workload Scheduler: Readme File for Fix Pack 1

25 REPAIR Use this action (only after the Commit action) to restore an existing Tioli Workload Scheduler instance to the current committed leel when a problem arises with the binary files. It forces an APPLY operation een if the current fix pack is already applied. It is used to repair the currently installed product. Depending on the fix pack installation state, you can perform the actions shown in the table below. Table 5. Fix pack installation state Initial state Action Final State Final State General Aailability Pack - apply ICU ICH ICU commit IC - ICU undo - IC IC repair IC - where: ICU IC ICH Installed undoable Installed and committed Installed, committed, and hidden If you hae a Tioli Workload Scheduler fix pack installed in "undoable mode" (ICU state) on your machine and you are applying a more recent Tioli Workload Scheduler fix pack on it, all the changes that you made when installing the preious Tioli Workload Scheduler fix pack are committed before applying the newer ones. Therefore, if you undo the fix pack you last installed, you restore the preious fix pack changes. These changes are permanent. The fix pack installation is recorded in the TWSRegistry.dat file by adding the following lines: /Tioli/Workload_Scheduler/tws_user_DN_FixpackName= FP_TWS_$(SWD-OS-NAME)_$(tws_user) $(patch_id) where: $(SWD-OS-NAME) Specifies the operating system where you are installing. $(tws_user) Specifies the Tioli Workload Scheduler instance owner. $(patch_id) Specifies the Tioli Workload Scheduler fix pack number. Before repairing a fix pack installation, ensure that: The processes listed in Table 6 are inactie: Table 6. Inactie processes Windows netman monman UNIX netman monman IBM Tioli Workload Scheduler Readme File for Fix Pack 1 for ersion

26 Table 6. Inactie processes (continued) Windows ssmagent writer batchman batchup JOBMAN JOBMON scribner agent JobManager UNIX ssmagent writer batchman batchup JOBMAN tokensr scribner agent JobManager The files listed in Table 7 are aailable under TWS_home/bin and are not corrupt (40042): Table 7. Files aailable under TWS_home/bin Windows conman composer (on the master) setown.cmd setown.exe oslayer.dll icudt*.dll HTTPChannel.dll HTTPSSLChannel.dll HTTPTransport.dll libatrc.dll ms*.dll agent JobManager UNIX conman composer (on the master) libatrc.so libicu*.so libhttp*.soinstmecho mecho composer agent JobManager Product actions when applying the fix pack The installer performs the following actions when you APPLY the fix pack: 1. Checks if there are any command lines running for the selected Tioli Workload Scheduler instance. 2. Retriees the alue of the job fence on the workstation for the selected Tioli Workload Scheduler instance. 3. Sets the alue of the job fence on the workstation to the GO alue for the selected Tioli Workload Scheduler instance. 4. Checks if there are any jobs running for the selected Tioli Workload Scheduler instance. 5. Stops the embedded ersion of WebSphere Application Serer. 6. Stops the Tioli Workload Scheduler agent. 20 IBM Tioli Workload Scheduler: Readme File for Fix Pack 1

27 7. Stops the Tioli Workload Scheduler instance. 8. Checks if there are any processes running for the selected Tioli Workload Scheduler instance. 9. Backs up the profile for the embedded WebSphere Application Serer. 10. Updates the embedded ersion of IBM WebSphere Application Serer UPDI V Updatse the embedded ersion of IBM WebSphere Application Serer FP Updates the embedded ersion of IBM WebSphere Application Serer IFPM Updates the embedded ersion of IBM WebSphere Application Serer IFPM Updates the embedded ersion of IBM WebSphere Application Serer SDK FP Installs the Tioli Workload Scheduler modeling and planning serer, ersion Installs with Rollback FP_LWA_<platform>.SPB. 17. Installs CIT scanners. 18. Installs with Rollback FP_Eclipse_<platform>.SPB. 19. Installs with Rollback the IBM Tioli Workload Scheduler scheduling engine. 20. Installs with Rollback IBM Tioli Workload Scheduler scheduling engine National Language Support. 21. Installs with Rollback FP_TDWB_<platform>.SPB. 22. Customizes the SQL scripts used to configure the Tioli Workload Scheduler database. 23. Customizes the SQL scripts used to configure the Tioli Workload Scheduler broker database. 24. Configures the Tioli Workload Scheduler database. 25. Configures the Tioli Workload Scheduler broker database. 26. Propagates the security policies of the applications to the JACC proider in the embedded WebSphere Application Serer. 27. Starts the embedded WebSphere Application Serer. 28. Creates uninstaller. 29. Configures the Tioli Workload Scheduler instance. 30. Starts the Tioli Workload Scheduler instance. 31. Starts the Tioli Workload Scheduler agent. 32. Completes and clean the Tioli Workload Scheduler instance. 33. Updates the Tioli Workload Automation registry. 34. Resets the alue of the job fence on the workstation to the original alue for the selected Tioli Workload Scheduler instance. 35. Updates the patch.info file. The installer performs the following actions when you UNDO the fix pack: 1. Checks if there are any command lines running for the selected Tioli Workload Scheduler instance. 2. Retriees the alue of the job fence on the workstation for the selected Tioli Workload Scheduler instance. IBM Tioli Workload Scheduler Readme File for Fix Pack 1 for ersion

28 3. Sets the alue of the job fence on the workstation to the GO alue for the selected Tioli Workload Scheduler instance. 4. Checks if there are any jobs running for the selected Tioli Workload Scheduler instance. 5. Stops the embedded ersion of WebSphere Application Serer. 6. Stops the Tioli Workload Scheduler agent. 7. Stops the Tioli Workload Scheduler instance. 8. Checks if there are any jobs running for the selected Tioli Workload Scheduler instance. 9. Rolls back FP_LWA_<platform>.SPB. 10. Updates the patch.info file. 11. Installs CIT scanners. 12. Rolls back FP_Eclipse_<platform>.SPB. 13. Rolls back the IBM Tioli Workload Scheduler scheduling engine. 14. Updates the patch.info file. 15. Rolls back IBM Tioli Workload Scheduler scheduling engine National Language Support. 16. Rolls back FP_TDWB_<platform>.SPB. 17. Restores the profile for the embedded WebSphere Application Serer. 18. Starts the embedded ersion of WebSphere Application Serer. 19. Starts the Tioli Workload Scheduler instance. 20. Starts the Tioli Workload Scheduler agent. 21. Completes and cleans the Tioli Workload Scheduler instance. 22. Updates the Tioli Workload Automation registry. 23. Resets the alue of the job fence on the workstation to the original alue for the selected Tioli Workload Scheduler instance. 24. Updates the patch.info file. Before Installing Before installing the fix pack using all the methods described in the following sections, perform the following actions: 1. Unlink the host on which you are installing the fix pack from the Tioli Workload Scheduler network 2. Shut down Tioli Workload Scheduler. Run the following commands, depending on your configuration: If you installed only the Tioli Workload Scheduler for z/os Agent or the Tioli Workload Scheduler Dynamic agent, run the following command: On Windows operating systems: ShutdownLwa.cmd On UNIX and Linux operating systems: ShutDownLwa If you hae any other configuration, run the following command: On Windows operating systems: conman noask" conman "stop; wait" conman "stopmon;wait" ShutdownLwa.cmd 22 IBM Tioli Workload Scheduler: Readme File for Fix Pack 1

29 On UNIX and Linux operating systems: conman noask" conman "stop; wait" conman "stopmon;wait" conman "shut;wait" ShutDownLwa If you hae jobs scheduled to run on the instance you are upgrading, make sure that they hae completed otherwise some processes, such as jobmon or joblnch, might still be actie. 3. Download the ZIP file specific for the operating system. 4. Extract the content of the ZIP files into a directory, using one of the unzip tools aailable on your system or downloadable from the Internet. The tool you use must be able to keep the file permissions on the extracted files, for example, infozip. You can find the unzip tool also on the DVD and the eimages of Tioli Workload Scheduler V8.6 in the directory TWS\<operating_system>\tws_tools, where <operating_system> is the operating system for which you want to install the product. Note: If you want to install the fix pack on IBM i, to untar the eimages, see Untar the eimages for the Tioli Workload Scheduler for z/os Agent and Dynamic Agent on IBM i operating systems. 5. If you are installing on a UNIX operating system, run the following command: chmod -R 755 <imagesdir> Untar the eimages for the Tioli Workload Scheduler for z/os Agent and Dynamic Agent on IBM i operating systems To untar the TWS86_IBM_I.tar fix pack eimage, you can use the PASE shell or the AIXterm. Using PASE shell: 1. Open the PASE shell. 2. Run the command: "CALL QP2TERM" 3. Locate the folder where you downloaded the file TWS86_IBM_I.tar and run the command: "tar xf TWS86_IBM_I.tar" 4. Exit from the PASE shell. Using AIXterm: 1. Start the Xserer on your desktop. 2. On the iseries machine, open a QSH shell and export the display. 3. In QSH shell, go to the directory /QopenSys and run the command: "aixterm -sb" 4. A pop-up window is displayed on your desktop. Using this pop-up window, untar the TWS86_IBM_I.tar file. Installing using the ISMP wizard After you hae completed the actions described in the section Before Installing on page 22, if you want to install the fix pack using the interactie wizard, perform the following steps: 1. Unlink the host on which you are installing the fix pack from the Tioli Workload Scheduler network IBM Tioli Workload Scheduler Readme File for Fix Pack 1 for ersion

30 2. Shut down Tioli Workload Scheduler. Run the following commands, depending on your configuration: If you installed only the Tioli Workload Scheduler for z/os agent, run the following command: On Windows operating systems: ShutdownLwa.cmd On UNIX and Linux operating systems: ShutDownLwa If you hae any other configuration, run the following command: On Windows operating systems: conman noask" conman "stop; wait" conman "stopmon;wait" ShutdownLwa.cmd On UNIX and Linux operating systems: conman noask" conman "stop; wait" conman "stopmon;wait" conman "shut;wait" ShutDownLwa If you hae jobs scheduled to run on the instance you are upgrading, make sure that they hae completed otherwise some processes, such as jobmon or joblnch, might still be actie. 3. Download the TAR or ZIP file specific for the operating system and unpack it. To extract the.tar file, ensure that you use the GNU ersion of the TAR command. Otherwise, if you unpack the file using a ersion other than GNU, your fix pack installation fails. If you are installing on a UNIX operating system, run the following command: chmod -R 755 <imagesdir> 4. Depending on the type of operating system, to launch the wizard, run the following command: On Windows operating systems: SETUP.exe On UNIX and Linux operating systems:./setup.bin The installation starts. 5. Follow the instructions proided on the panel. 6. Click Finish to complete the installation. Installing using the ISMP silent installation After you hae completed the actions described in the section Before Installing on page 22, if you want to want to install the fix pack in silent mode use silent installation. Silent installation requires the customization of a response file. The response file includes all the information required to run the installation without user interention. You are proided with the patchinstall.txt sample response file located under the RESPONSEFILES directory. Create your response file or customize the response file to include the options required to complete the installation. 24 IBM Tioli Workload Scheduler: Readme File for Fix Pack 1

31 Run the following command from the path were the SETUP file is located to start the installation in silent mode: On Windows operating systems: setup.exe -options response_file -silent where response_file is the full path name of the response file that you customized with your enironment settings. On UNIX and Linux operating systems:./setup.bin -options response_file -silent where response_file is the full path name of the response file that you customized with your enironment settings. Table 8 lists the keywords that you can set in the -W displayactions.selectedaction="apply" parameter to customize the response file for your needs: Table 8. Parameters KEYWORD APPLY UNDO COMMIT APPLY_AND_COMMIT SCENARIO Install an undoable fix pack Roll back to the preious leel if you did not commit it. Make the fix pack permanent. An UNDO operation is no longer possible. Repair an installed and committed fix pack. Note: This action is aailable only when you install a fix pack. It is not aailable on General Aailability (GA) ersions. Installing using the twspatch script You can use the twspatch script file to install the agents. To show command usage: On Windows operating systems: twspatch.bs -u On UNIX and Linux operating systems:./twspatch -u To install a fix pack: On Windows operating systems: twspatch.bs -install -uname TWS_user [-inst_dir installation_dir [-recoinstreg {true false}]] [-wait <minutes>] [-lang <lang_id>] twspatch.bs -{undo commit remoe repair} -uname TWS_user [-lang <lang_id>] On UNIX and Linux operating systems:./twspatch -install -uname TWS_user [-inst_dir installation_dir [-recoinstreg {true false}]] [-wait <minutes>][-lang <lang_id>]./twspatch -{undo commit remoe repair} -uname TWS_user [-lang <lang_id>] Where: install Install an undoable fix pack IBM Tioli Workload Scheduler Readme File for Fix Pack 1 for ersion

32 undo Roll back an undoable image of the fix pack. commit Make the fix pack permanent. An UNDO operation is no longer possible. remoe Uninstall the Tioli Workload Scheduler instance. repair Repair an installed and committed fix pack when a problem occurs with the binary files. Forces an APPLY operation een if the current fix pack is already applied. It is used to repair the currently-installed product. -uname TWS_user The name of the user you used to install the Tioli Workload Scheduler instance. -inst_dir installation_dir [-recoinstreg true false ] The name of the directory where you installed Tioli Workload Scheduler. When installing the fix pack the inst_dir is used: If the installation process cannot retriee the product install location from the registries. If you need to re-create the Tioli Workload Scheduler registries again before the fix pack installation. Set the alue of the recoinstreg to true if you want to re-create the registry files while performing a fix pack installation on a fault-tolerant agent. See Re-creating registry files using twspatch on page 29. -wait minutes The number of minutes that the product waits for jobs that are running to complete before starting the fix pack installation. If the jobs do not complete during this interal the installation process does not proceed and an error message is displayed. Valid alues are integers or -1 for the product to wait indefinitely. The default is 60. -lang lang_id The language used for the twspatch messages displayed. The default is the alue of the system ariable LANG. If the language catalog for the alue you specified is missing, the default C language catalog is used. twspatch for Windows is a Visual Basic Script (VBS) that you can run in CScript and WScript mode. After you hae completed the actions described in the section Before Installing on page 22, perform the following action: Run twspatch with the options you need for your fix pack installation scenario. Note: On IBM i operating systems, if you are installing the fix pack on a Tioli Workload Scheduler for z/os Agent or a Tioli Workload Scheduler Dynamic Agent, after you hae completed the actions described in the section Untar the eimages for the Tioli Workload Scheduler for z/os Agent and Dynamic Agent on IBM i operating systems on page 23, run the twspatch from the QSH shell. 26 IBM Tioli Workload Scheduler: Readme File for Fix Pack 1

33 Installing using Software Distribution After you hae completed the actions described in the section Before Installing on page 22, to install the fix pack using Software Distribution, run the following commands depending on your configuration: If you installed only the Tioli Workload Scheduler for z/os agent: wdinstsp -f -uy -D execactiontools=false -D tws_user=<tws_user> -D install_dir=<tws_home> -n <INST_PKG_NAME_LWA> <SPB_FILE_NAME_LWA> If you installed the Tioli Workload Scheduler for z/os agent or the Tioli Workload Scheduler Dynamic agent and the Jaa Extension: wdinstsp -f -uy -D execactiontools=false -D tws_user=<tws_user> -D install_dir=<tws_home> -n <INST_PKG_NAME_LWA> <SPB_FILE_NAME_LWA> followed by this command: wdinstsp -f -uy -D tws_user=<tws_user> -D install_dir=<tws_home> -n <INST_PKG_NAME_JAVA> <SPB_FILE_NAME_JAVA> If you installed only the fault-tolerant agent: wdinstsp -f -uy -D execactiontools=false -D tws_user=<tws_user> -D install_dir=<tws_home> <CPU_TYPE_DEF> -n <INST_PKG_NAME> <SPB_FILE_NAME> If you installed the fault-tolerant agent and the Jaa Extension: wdinstsp -f -uy -D execactiontools=false -D tws_user=<tws_user> -D install_dir=<tws_home> -n <INST_PKG_NAME_LWA> <SPB_FILE_NAME_LWA> followed by this command: wdinstsp -f -uy -D execactiontools=false -D tws_user=<tws_user> -D install_dir=<tws_home> <CPU_TYPE_DEF> -n <INST_PKG_NAME> <SPB_FILE_NAME> and followed by this command: wdinstsp -f -uy -D tws_user=<tws_user> -D install_dir=<tws_home> -n <INST_PKG_NAME_JAVA> <SPB_FILE_NAME_JAVA> where: <CPU_TYPE_DEF> -D st_agent=<true or false> -D ft_agent=<true or false> -D master=<true or false> -D bkm_agent=<true or false> <INST_PKG_NAME> FP_TWS_<INST_INTERP>_<TWS_USER> <PATCH_NUMBER> <INST_PKG_NAME_LWA> FP_LWA_<INST_INTERP>_<TWS_USER> <PATCH_NUMBER> <INST_PKG_NAME_JAVA> FP_Eclipse_<INST_INTERP>_<TWS_USER> <PATCH_NUMBER> IBM Tioli Workload Scheduler Readme File for Fix Pack 1 for ersion

34 <INST_INTERP> AIX HPIA64 HPUX LINUX_I386 LINUX_S390 LINUX_PPC LINUX_X86_64 SOLARIS_I386 SOLARIS WINDOW_X86_64 WINDOWS <PATCH_NUMBER> fixpack leel (e.g. 01) <SPB_FILE_NAME> <spb file path>fp_tws_<inst_interp>.spb <SPB_FILE_NAME_LWA> <spb file path>fp_lwa_<inst_interp>.spb <SPB_FILE_NAME_JAVA> <spb file path>fp_eclipse_<inst_interp>.spb Installing the fix pack on fault-tolerant agents when there are corrupt registry files If you tried to install the fix pack on a stand-alone, fault-tolerant agent (an agent that is not shared with other components or does not hae the connector feature) and receied an error message that states that an instance of Tioli Workload Scheduler cannot be found, this might be caused by a corrupt registry file. It is possible to install the fix pack on a stand-alone, fault-tolerant agent that has corrupt registry files without haing to re-install the product. Tioli Workload Scheduler has a recoery option that you can run to re-create the necessary files. You can also use this option when installing the fix pack on nodes in cluster enironments, where the node on which you want to perform the fix pack installation is unaailable or is in an inconsistent state. The recoery option re-creates the registry files and the Software Distribution information without haing to reinstall the product. You can run the recoery option when using any of the following fix pack installation methods: Installing using the ISMP wizard on page 23 Installing using the ISMP silent installation on page 24 Installing using the twspatch script on page 25 Re-creating the registry files using the installation wizard If you want to re-create the registry files while performing a fix pack installation on a fault-tolerant agent using the installation wizard, perform the following steps: 1. From the installation DVD or from the downloaded images, run one of the following commands: Windows operating systems TWS\operating_system\SETUP.exe -W displaylactions.installationdirh=twa_home -W recoinstreg.run=true TWS\SETUP.cmd -W displaylactions.installationdir=twa_home -W recoinstreg.run=true where operating_system is the operating system where you want to install the fix pack and TWA_home is the directory where Tioli Workload Scheduler is installed. UNIX and Linux operating systems 28 IBM Tioli Workload Scheduler: Readme File for Fix Pack 1

35 TWS/operating_system/SETUP.bin -W displaylactions.installationdir=twa_home -W recoinstreg.run=true TWS/SETUP.sh -W displaylactions.installationdir=twa_home -W recoinstreg.run=true where operating_system is the operating system where you want to install the fix pack and TWA_home is the directory where Tioli Workload Scheduler is installed. Re-creating registry files using silent fix pack installation To re-create the registry files while performing a fix pack installation on a fault-tolerant agent using the silent fix pack installation method, perform the following steps: 1. Copy the response file to a local directory, according to your operating system: patchinstall.txt 2. Edit the response file by specifying the parameter: -W recoinstreg.run=true 3. Sae the file with your changes. 4. Enter the following command: Windows operating systems SETUP.exe -options local_dir\patchinstall.txt -silent where patchinstall.txt is the name of the response file to use for fix pack installation. The SETUP.exe file is located in TWS\operating_system. UNIX and Linux operating systems./setup.bin -options local_dir/patchinstall.txt -silent where patchinstall.txt is the name of the response file to use for fix pack installation. The SETUP.bin file is located in TWS/operating_system. 5. Reiew the installation messages in the summary.log file to check that fix pack installation was successful. Re-creating registry files using twspatch To re-create the registry files while performing a fix pack installation on a fault-tolerant agent using the twspatch script, perform the following steps: On Windows operating systems 1. Log in as administrator on the workstation where you want to upgrade the product. 2. From the TWS/operating_system directory of the installation DVD or from the downloaded images, run one of the following commands, where operating_system is the operating system where you want to install the fix pack, run twspatch using the synopsis described below. On UNIX and Linux 1. From the TWS/operating_system directory of the installation DVD or from the downloaded images, where operating_system is the operating system where you want to install Tioli Workload Scheduler fix pack, run the twspatch script using the synopsis described below. Synopsis: On Windows operating systems: IBM Tioli Workload Scheduler Readme File for Fix Pack 1 for ersion

36 Show command usage and ersion twspatch.bs -u - Install fix pack twspatch.bs -install -uname user_name [-domain user_domain] [-inst_dir install_dir [-recoinstreg true]] Example twspatch.bs -install -uname twsuser -password qaz12qaz -inst_dir "C:\Program Files\IBM\TWA" -recoinstreg true On UNIX and Linux Show command usage and ersion./twspatch -u - Install fix pack./twspatch -install -uname user_name [-inst_dir install_dir [-recoinstreg true]] Example./twspatch -install -uname twsuser -inst_dir /opt/ibm/twa -recoinstreg true For information about the twspatch parameters, see Installing using the twspatch script on page 25. Installing the batch reports To install the batch reports eimage ersion Fix Pack 1 images, perform the following actions: You installed the batch reports ersion Rename the directory TWSBatchReportCli, where you installed the batch reports ersion to TWSBatchReportCli_old. 2. In the directory TWSBatchReportCli, download the file TIV-REPCLI-<operating system>-fp0001.tar ersion 8.6 Fix Pack 1 images where operating system is the platform you want to install batch reports. 3. To extract the package in the directory TWSBatchReportCli, see Tioli Workload Scheduler: User's guide and Reference > Getting reports and statistics > Running reports and batch reports > Running batch reports from the command line interface 4. Back up the TWSBatchReportCli\config\common.properties file and all the templates stored in the TWSBatchReportCli\reports\templates. 5. Merge the TWSBatchReportCli\config\common.properties file with the TWSBatchReportCli_old\config\common.properties file. 6. Copy the customized files from TWSBatchReportCli_old\reports\ templates to TWSBatchReportCli\reports\templates. You do not hae the batch reports ersion installed 1. In the directory TWSBatchReportCli, download the file 8.6-TIV-REPCLI-<operating system>-fp0001.tar ersion 8.6 Fix Pack 1 images, where operating system is the operating system on which you want to install batch reports. 2. To install batch reports, see Tioli Workload Scheduler: User's Guide and Reference > Getting reports and statistics > Running reports and batch reports > Running batch reports from the command line interface. 30 IBM Tioli Workload Scheduler: Readme File for Fix Pack 1

37 Configuring properties for the dynamic workload broker command line This step is required only if you run the dynamic workload broker command line on a Windows system. The ersion of the CLIConfig.properties file installed with ersion on Windows workstations omits the following keywords: tdwb_user tdwb_pwd These keywords are required to run commands on the dynamic workload broker command line (not if you use the Tioli Dynamic Workload Console). This fix pack installs an additional, non-running, instance of CLIConfig.properties with the correct keywords in: TWA_home\TDWB\config\config Copy the tdwb_user and tdwb_pwd keywords from the CLIConfig.properties located in TWA_home\TDWB\config\config into the CLIConfig.properties located in TWA_home\TDWB\config, which is the running instance. Rolling back the fix pack installation You can roll back the installation only if you installed it in undoable mode. To roll back the installation using ISMP, perform the following steps: 1. Launch the installation setup for your operating system. 2. Select the instance that you want to remoe. 3. Select the UNDO option. 4. Click Finish. To roll back the installation using the twspatch command from the TWS_home directory, use the undo option. For more information about the rolling back action, see also Installation notes on page 12. Uninstalling the entire Tioli Workload Scheduler instance If you installed using the twspatch command, to uninstall the entire Tioli Workload Scheduler instance, use the twspatch remoe command from the TWS_home directory. If you installed using ISMP, to uninstall, see Planning and Installation. Installation log files The following installation log files gie you details about the status of the fix pack installation for the master domain manager, backup master domain manager, the agents, and the connector: Trace file for ISMP installer On Windows operating systems: %TEMP%\TWA\tws86fixpack\twsismp.log IBM Tioli Workload Scheduler Readme File for Fix Pack 1 for ersion

38 On UNIX and Linux operating systems: $TMPDIR/TWA/tws86fixpack/twsismp.log Log file for ISMP installer On Windows operating systems: %TEMP%\TWA\tws86fixpack\twsstatus.log %TEMP%\TWA\tws86fixpack\summary.log On UNIX and Linux operating systems: $TMPDIR/TWA/tws86fixpack/twsstatus.log $TMPDIR/TWA/tws86fixpack/summary.log Log file for Tioli Workload Scheduler twspatch installer. On Windows operating systems: %TEMP%\TWA\tws86fixpack\ twspatch_<inst_interp>_<twsuser>^8.6.0.n.log On UNIX and Linux operating systems: $TMPDIR/TWA/tws86fixpack/ twspatch_<inst_interp>_<twsuser>^8.6.0.n.log where n is the fix pack number. For this fix pack the number is 1. Log file for Configuration Manager installation. Documentation updates On Windows operating systems: %TEMP%\FP_TWS_<INST_INTERP>_<TWSuser>^8.6.0.n.log On UNIX and Linux operating systems: $TMPDIR/FP_TWS_<INST_INTERP>_<TWSuser>^8.6.0.n.log where n is the fix pack number. For this fix pack the number is 1. For information about INST_INTERP, see Installing using Software Distribution on page 27. If you do not set the ariable $TMPDIR on the UNIX system then the default /tmp is assumed. The manuals were updated with all the features introduced with Fix Pack 1 in the information center: com.ibm.tioli.itws.doc_ /welcome_twa.html The following APARs were fixed: IV16524: DOCC UPDATE IS REQUIRED THAT "ACTIVEAUTHMECHANISM" SHOULD BE "LTPA" INSTEAD OF "SWAM". IV16952: TDWC INSTALL USER REQUIREMENTS DOCUMENTATION CONSIDERING TWAPAM. 32 IBM Tioli Workload Scheduler: Readme File for Fix Pack 1

39 Contacting IBM Software Support Before contacting IBM Software Support with a problem, refer to the IBM Software Support site by accessing the following Web address: To access Tioli support, click the Tioli support link at the bottom right of the page. If you want to contact IBM Software Support, see the IBM Software Support Handbook at the following Web site: The guide proides information about how to contact IBM Software Support, depending on the seerity of your problem, and the following information: Registration and eligibility. Telephone numbers, depending on the country in which you are located. Information you must hae before contacting IBM Software Support. Copyright IBM Corp. 2011,

40 34 IBM Tioli Workload Scheduler: Readme File for Fix Pack 1

41 Notices This information was deeloped for products and serices offered in the U.S.A. IBM may not offer the products, serices, or features discussed in this document in other countries. Consult your local IBM representatie for information on the products and serices currently aailable in your area. Any reference to an IBM product, program, or serice is not intended to state or imply that only that IBM product, program, or serice may be used. Any functionally equialent product, program, or serice that does not infringe any IBM intellectual property right may be used instead. Howeer, it is the user's responsibility to ealuate and erify the operation of any non-ibm product, program, or serice. IBM may hae patents or pending patent applications coering subject matter described in this document. The furnishing of this document does not gie you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drie Armonk, NY 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: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan, Ltd , Shimotsuruma, Yamato-shi Kanagawa Japan The following paragraph does not apply to the United Kingdom or any other country where such proisions 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 improements 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 proided for conenience only and do not in any manner sere 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. Copyright IBM Corp. 2011,

42 IBM may use or distribute any of the information you supply in any way it beliees appropriate without incurring any obligation to you. Licensees of this program who wish to hae 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/ Burnet Road Austin, TX U.S.A. Such information may be aailable, 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 aailable for it are proided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equialent agreement between us. Any performance data contained herein was determined in a controlled enironment. Therefore, the results obtained in other operating enironments may ary significantly. Some measurements may hae been made on deelopment-leel systems and there is no guarantee that these measurements will be the same on generally aailable systems. Furthermore, some measurement may hae been estimated through extrapolation. Actual results may ary. Users of this document should erify the applicable data for their specific enironment. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly aailable 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 indiiduals, 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 iewing this information in softcopy form, the photographs and color illustrations might not display. Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol ( or ), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is aailable on the Web at Copyright and trademark information at 36 IBM Tioli Workload Scheduler: Readme File for Fix Pack 1

43 Adobe, the Adobe logo, PostScript and the Postscript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc., in the United States, other countries, or both and is used under license therefrom. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Goernment Commerce. ITIL is a registered trademark, and a registered community trademark of the Office of Goernment Commerce, and is registered in the U.S. Patent and Trademark Office. Jaa and all Jaa-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Linux is a trademark of Linus Toralds in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are 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. Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries. Notices 37