IBM Tivoli Workload Scheduler

Readme File for Fix Pack 1 Version 9.2.0




IBM Tivoli Workload Scheduler

Readme File for Fix Pack 1 Version 9.2.0




Note Before using this information and the product it supports, read the information in “Notices” on page 31.

This edition applies to Fix Pack 1 for version 9, release 2, modification level 0 of IBM Tivoli Workload Scheduler (program number 5698-WSH) and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright IBM Corporation 2014. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents IBM Tivoli Workload Scheduler Readme File for Fix Pack 1 for version 9.2.0 . . . . . . 1 About this fix pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Features introduced with Fix Pack 1 . . . . . . . . . . . . . . . . . . . . . . . Problems fixed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . APARs and defects fixed in Tivoli Workload Scheduler Fix Pack 1 for version 9.2.0 . . . . . . . Known limitations and workarounds . . . . . . . . . . . . . . . . . . . . . . . Fix pack structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fix pack files available for Tivoli Workload Scheduler using Fix Central . . . . . . . . . . . Installing the fix pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disk space requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Untar the eImages for the Tivoli Workload Scheduler for z/OS Agent and Dynamic Agent on IBM i operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Tivoli Workload Scheduler for the first time using the IBM Installation Manager wizard . . Installing the fix pack on the Tivoli Workload Scheduler General Availability version 9.2 using the IBM Installation Manager wizard . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the fix pack on a Tivoli Workload Scheduler version earlier than 9.2 using the IBM Installation Manager wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the fix pack using IBM Installation Manager silent installation . . . . . . . . . . . Installing the fix pack on agents using the twsinst script . . . . . . . . . . . . . . . . Uninstalling the entire Tivoli Workload Scheduler instance . . . . . . . . . . . . . . . Installation log files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documentation updates . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . .

. . . . .

. . . . . . .

. . . . . . .

. 1 . 2 . 3 . 3 . 9 . 10 . 10 . 11 . 11 . 12 . 13 . 14

. .

. .

. 15 . 15

.

.

. 16

. . . . . .

. . . . . .

. . . . . .

18 20 21 22 22 23

Contacting IBM Software Support . . . . . . . . . . . . . . . . . . . . . . . . 29 Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Trademarks .

.

.

.

.

© Copyright IBM Corp. 2014

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 32

iii

iv

IBM Tivoli Workload Scheduler: Readme File for Fix Pack 1

IBM Tivoli Workload Scheduler Readme File for Fix Pack 1 for version 9.2.0 Date

12 December 2014

Fix Pack 9.2.0-TIV-TWS-FP0001 Product IBM® Tivoli® Workload Scheduler version 9.2.0 General Description IBM Tivoli Workload Scheduler Fix Pack 1 for version 9.2.0 This readme file provides important information about Fix Pack 1 for IBM Tivoli Workload Scheduler version 9.2.0. This readme file is the most current information for the fix pack and takes precedence over all other documentation for Tivoli Workload Scheduler version 9.2.0 Fix Pack 1. It is divided into the following sections: v v v v

“About this fix pack” “Fix pack structure” on page 10 “Installing the fix pack” on page 11 “Documentation updates” on page 23

Review this section thoroughly before installing or using this Fix Pack.

About this fix pack This section contains information specific for this fix pack including what has been modified or introduced, what has been fixed, product versions or components to which the fix pack applies, and compatibility issues, if any. Product versions and components to which the fix pack applies This fix pack can be applied only on top of Tivoli Workload Scheduler V9.2.0. This section includes the following subsections: v “Features introduced with Fix Pack 1” on page 2 v “Problems fixed” on page 3 v “Known limitations and workarounds” on page 9

© Copyright IBM Corp. 2014

1

Features introduced with Fix Pack 1 Serviceability improvement in planman unlock (IV54973) With this feature, if a planman -unlock command is issued when MakePlan is running, MakePlan is stopped to avoid having multiple MakePlan running. Updating of GSKit version (112592, IV56650, IV60577, IV60580) The version of GSKit is updated to version 8.0.50.20. Updating of System Service Monitor (SSM) version (112592, IV60620) The version of System Service Monitor is updated to version 4.0.1.78. Including the latest daylight saving time Olson table to include Egypt timezone announced on May 2014 (IV61426) Updated timezone table that includes Egypt change announced on May 2014. Enhancements in the makeplan performance when CPUCLASSes are used (IV61734) When creating the currentPlan file, Tivoli Workload Scheduler is not optimized for CPUCLASSes. A cache has been added to increase performances. Solved vulnerability for SetGID and SetUID (112592, IV62010) Solved a potential vulnerability in SetGID and SetUID programs on UNIX operating systems, that a malicious code might exploit to be executed with elevated rights giving an attacker the possibility to run programs with root authority. Enhance the check on lifecycle of ssmagent.bin to prevent multiple spawning of the file (IV63524) It might happen that multiple ssmagent.bin processes are started. To prevent this issue, additional checks have been added to the scripts starting ssmagent.bin. Updating of OpenSSL version (112592, IV66398) The version of OpenSSL is updated to version openssl-0.9.8zc. New property in file PamUnixRegistryImpl.properties On AIX operating systems, when the PAM authentication method is active, it might happen that WebSphere Application Server ends abnormally generating a core file. This happens when a Tivoli Workload Scheduler user authentication to WebSphere Application Server fails because of a wrong or expired password, or a wrong PAM system configuration, and the password encryption algorithm used by the operating system is different from the Crypt algorithm. To avoid this event, a new property, com.ibm.tws.pam.security.registry.nolocalos, must be added to file PamUnixRegistryImpl.properties. Usage: com.ibm.tws.pam.security.registry.nolocalos=yes

When this property is set, WebSphere Application Server does not end abnormally after a failed WebSphere authentication. To have it working, it is necessary that PAM is properly configured in your system. (RTC 102214) New property file for RemoteCommand plug-in (112368) On Windows systems, the RemoteCommand plug-in has a hardcoded timeout

2

IBM Tivoli Workload Scheduler: Readme File for Fix Pack 1

set to 5 minutes (300 seconds). It might happen that this timeout is reached when a job is still running, causing its abnormal ending. To prevent this, a new property file, RemoteCommandExecutor.properties, has been added to the plug-in having the attribute timeout that can be set to a different amount of seconds to give more time to run to the job. Usage: timeout=sec

where sec is the amount of time in seconds. SUSE Linux Enterprise Server V12 supported (113424) Starting with this fix pack, the operating system SUSE Linux Enterprise Server V12 is supported only on fault-tolerant agents with silent installation. Linux Red Hat V7 supported (115521) Starting with this fix pack, the operating system Linux Red Hat V7 is supported. Capability to enable a mailman process profiling (116812) Mailman now adds more information in the TWSMERGE.log file, to trace usage percentage and time elapsed to contact fault-tolerant agents managed by mailman. Information are added every 12 hours or every time mailman stops. The 12 hours time interval can be varied by setting a different amount of time in minutes, with parameter mm mail profiler located in the \TWS\config\localopts file, where is the Tivoli Workload Scheduler installation directory. Credentials for domain users (117572) With this feature, domain users are supported in the form DOMAIN\USER. Windows 2012 R2 supported (120812) Starting with this fix pack, the operating system Windows 2012 R2 is supported.

Problems fixed This section lists all APARs and internal defects solved by this fix pack. For additional information about documentation APARs and internal defects, see “Documentation updates” on page 23. This section includes the following topic: v “APARs and defects fixed in Tivoli Workload Scheduler Fix Pack 1 for version 9.2.0”

APARs and defects fixed in Tivoli Workload Scheduler Fix Pack 1 for version 9.2.0 This section lists APARs and internal defects solved by Fix Pack 1. List of APARs fixed: v IV40269: SLOW SSH TRANSFER OF FILE DUE TO PROCESSING LOCAL FILE. v IV41568: PATCH LEVEL AND MEMORY ERROR WHEN INSTALLING 86 FTA ON HPIA SYSTEM. v IV47992: FILE IS NOT CLOSED BY APPSERVMAN UNTIL APPSERVMAN IS STOPPED.

IBM Tivoli Workload Scheduler Readme File for Fix Pack 1 for version 9.2.0

3

v IV47998: JOB FAILED WHEN JOBNAME CONSISTS OF SPECIAL CHARACTERS. v IV51390: PAM AUTHENTICATION SWITCH LOCAL OS MODE. v IV51987: TIME STAMP IS OFF BY (-) 5 HOURS IN EVENT RULE EMAIL BODY. v IV52046: INCLUDE NEW TIMEZONE TABLE IN NEXT TWS RELEASE(S). v IV54764: WINDOWS REMOTE COMMAND JOB ENDS WITH EXIT CODE 259 AFTER 5 MINUTES. v IV54821: CAN NOT SAVE ER, IF A MBCS CHARACTER IS AT A TRUNCATION POINT OF THE "SCOPE". v IV54879: COMPANY NAME IN OUTPUT BANNER FROM CONMAN WITH OFFLINE OPTION IS GARBLED. v IV55052: ERROR "EQQA637E THE NAME OF THE DATASET IS INVALID"IN TDWC TWSZINTERFACE. v IV55234: INCORRECT SATISFIED DEPENDENCY COUNT FOR JOB ON TDWC. v IV55237: JOB RERUN SUCC HOWEVER ITS STREAM STAYS IN READY. v IV56113: SUBMITTING 2ND JOBSTREAM FROM SAME DISPLAY AFTER SUBMITTING THE 1ST JOBSTREAM WILL CAUSE RESUBMISSION OF THE 1ST JOBSTREAM NAME. v IV56125: EVENT RULE FOR RECOVERY PROMPT DOES NOT WORK. v IV56180: CONFIRM SUCC DOESN'T WORK ON EVERY JOB. v IV56186: TWSUSERACTION.EXE CRASH WHEN TRYING TO CREATE A USER. v IV56439: REPORT 10B OUTPUT TRUNCATES JOBSTREAMID AT 15 BYTES. v IV56870: JBXTRACT RETURNS USAGE WHEN THE SECOND CHARACTER OF THE JOB NAME IS U. v IV57342: MAKEPLAN SERVICEABILITY ENHANCEMENT. v IV58430: DST FEATURE CAUSING JOB FLAGS TO BE OVERWRITTEN IN SOME RARE SCENARIOS. v IV59053: REPTR CONSUMES 100% CPU. v IV59126: TWS SERVICE GOES IMMEDIATELY DOWN AFTER RESTART ON WINDOWS 2012. v IV60236: MBCS CHARACTERS ARE GARBLED BROWSING JOBLOG USING TDWC AND CONMAN SJ;STDLIST ON AIX. v IV60377: JOBS RUNNING ONE HOUR LATER AFTER DST CHANGE. v IV60621: IMPROVE IV41929, SWITCHING TO OLD INTERACTIVE JOBS BEHAVIOR ONLY IF THERE AREN'T VALID ACTIVE SESSIONS. v IV60715: JOB CONFIRM SUCC STILL DISPLAYED IN ABEND FROM TDWC. v IV60962: JOBSTREAM STATUS READY FROM TDWC AND SUCC IN CONMAN AFTER CANCEL PENDING. v IV60964: DURING PLANMAN RESYNC, RESOURCES ARE SEEN TWICE FROM TDWC. v IV60965: RESOURCE STATUS UNKNOWN IN TDWC.

4

IBM Tivoli Workload Scheduler: Readme File for Fix Pack 1

v IV60988: UNABLE TO RUN AGENT CLI COMMAND ON A WINDOWS SERVER 2012 MACHINE. v IV61275: GARBLED CHARACTER AT ZCENTRIC SIDE WHEN USING FRENCH CODEPAGE. v IV61731: GOT THE WRONG JOB NAME THROUGH TWS JAVA API AND WEB SERVICES. v IV62252: "?" IN PASSWORD IS WRONGLY INTERPRETED AS A SPECIAL CHAR OF A REGULAR EXPRESSION. v IV62658: MISSING CHECKS IN JOB STATISTICS UPDATES BY LOGMAN. v IV62662: COMPLEX VARIANT ARE NOT DISPLAYED BY TDWC. v IV62676: PLANMAN CHECKSYNC FAIL WITH AWSJCL075E. v IV62797: THE JOBMANAGER.INI PARAMETER DELAYBEFORECOMPRESSINGSECONDS DOES NOT WORK AS EXPECTED IF THE VALUE IS SET FOR MORE THAN ONE HOUR. v IV62800: VARIABLES DEFINED BY 'PARAM' COMMAND ARE NOT RESOLVED LOCALLY. v IV62943: TIMING OF RELEASING A RESOURCE DIFFERS IN JOB STREAM. v IV63096: TWSPROFILER.LOG NEVER WRAPS AND GROWS CONSTANTLY IN SIZE. v IV63159: EVENT SEND FROM FTA IS NOT RECOGNIZED BY EVENT SERVER. v IV63216: OPENS FILE TAKES ABOUT 1 SECS PER FILE. v IV63324: CONMAN ALLOWS TO EXECUTE SOME COMMANDS IF A CONFIGURATION FILE IS MISSING. v IV63448: GETGOBOUTPUT CAUSES WAS CRASH. v IV63524: ENHANCE THE CHECK ON LIFECYCLE OF SSMAGENT, TO PREVENT MULTIPLE SPAWNING OF THE FILE. v IV63672: EXECUTION OF JNEXTPLAN HANGS BECAUSE OF DEFINITION OF RUNCYCLE GROUPS. v IV63764: TWS DB LOCK AND LOCK/WAIT CREATED WHEN TDWC QUERIES AND SUBMISSIONS WHEN LOCK ESCALATION. v IV64151: CROSS_DEP PERFORMANCE ISSUES. v IV64313: "WAPPMAN -DISPLAY" OUTPUT IS DISPLAYED AS UNICODE CODE NUMBERS FOR MBCS CHARACTERS. v IV64500: UPDATESTATS JOB ABEND IF USETCL=NO IS USED. v IV64661: AN EXTRA SLASH IS ADDED TO THE TWSREGISTRY.DAT v IV64796: ZCENTRIC AGENT AT V9.1 LEVEL ON WINDOWS IS FILLING THE DIRECTORY JMJOBTABLEDIR WITH TEMPORARY FILES. v IV65213: II IS IMPOSSIBLE TO MIGRATE A WIN32 IMAGE ON WIN64 TO 9.X. v IV65235: JOB STREAM VIEW DOES NOT SHOW CORRECT STATUS IF A JOB RERUNED v IV65450: /WASTOOLS/BACKUPCONFIG.SH REQUIRES A SPECIFIC VERSION OF BASH. v IV65671: JSTREAMS SCHEDULED TO RUN FROM 20 TO 21 (UTC) THE DAY BEFORE DST. IBM Tivoli Workload Scheduler Readme File for Fix Pack 1 for version 9.2.0

5

v IV65770: BATCHMAN FAILS SIGSEGV ABNORMAL END PROCESSING DEPENDENCY LIST. v IV66165: MISSING AGENT PLUGIN DELETION AFTER AGENT MIGRATION. v IV66440: FIX CURL/LIBCURL FOR CVE-2014-0139 AND CVE-2014-0138. v IV67340: PLANMAN RESYNC FAIL IN RARE SITUATION. v IV67745: SENDEVENT CRASH ON WINDOWS USED BY DYNAMIC AGENT JOBS. List of defects fixed: v 102013: EDWA: WorkstationStatusChanged for a dynamic agent. Hostname field of the event is not populated with the agent hostname but with dynamic broker name. v v v v v v

108097: Zcentric IBM i - jobs definition from ISPF enabled. 109432: Procedure to change user mdm 92. 110727: TWS Internetwork dependencies conman submission. 112498: Wrong version on maestro.info. 112499: Add compiler cache. 112501: Patch.info, version and version.info don't exist.

v 112571: Wrong conman version. v 112572: Wrong version in Registry folder. v 112688: NullPointerException and no jobs displayed in MonitorJobs view. v 112689: Incorrect job status after confirm action. v 112699: Enhancement bug. v 112702: Wrong predecessor job after a rerun in a follows chain. v 112704: Wrong Job Stream status (READY) after canceling a job in a rerun chain with abend jobs. v 112706: Setting pri=0 or HOLD a job in WAIT, its internal status doesn't become HELD. v 112707: JS in ready instead of succ when canceling job before rerunning abend job. v 112708: All the rerun chain is in held status instead of the specific instance. v 113389: Missing Sterling jar file after MDM installation. v 113390: Unable to stop the WAS from the Windows services after updateWasService.bat. v 113393: Missing standard output and usage running updateWas command. v 113395: RPATH Security issue. v 113422: zcentric IBM i - jobs definition from ISPF enabled. v 113429: "Optman show sccdUserPassword" wrongly shows not encrypted password. v 113430: Planman resync fails when maxdur is set to a value greater than 999 minutes. v 113784: TWSActionPlugIn wrong schedTime when submitting a jobstream without the schedDate. v 113808: Installation using Software distribution can fail.

6

IBM Tivoli Workload Scheduler: Readme File for Fix Pack 1

v 113853: Incorrect change status after rerun and cancel operation. v 113854: Internal error occurred trying to remove a job stream predecessor dependency. v 113912: Incorrect number of Not satisfied Dependency after job cancel. v 113913: NullPointerException and no jobs displayed in MonitorJobs view. v 113914: Incorrect behavior adding a runtime dependency to an already completed job. v 113915: After rerun a failed job, the job stream doesn't change the status. v 113916: After rerun a failed job, the job stream doesn't change the status. v 113917: After rerun a failed job, the job stream doesn't change the status. v 113918: The dependencies status is incorrect if associated with a failed job. v 113919: Incorrect job status performing a job rerun. v 113920: The job stream status is incorrect after cancel pending status. v 113922: Incorrect prompt number performing multiple job rerun. v 113931: Incorrect unresolved dependency number performing a job rerun. v 113934: Incorrect prompt status performing a job rerun. v 113935: Wrong NumberOfNotRunningJobs when canceling job before rerunning abend job. v 113937: Incorrect number of Not satisfied Dependency after job cancel. v 113952: Incorrect job status after confirm action. v 113955: Incorrect predecessor dependency status after dynamic dependency kill. v 113959: Unexpected prompt dependencies status after release. v 113963: Incorrect number of unsatisfied predecessors dependencies after removal of multiple dependencies instances. v 114322: Wrong patch version on TWSRegistry. v 114683: Installation Manager old version. v 114783: Cannot delete wat after unlock operation. v 114786: Event rules actions are not triggered for dynamic agents without gateway enabled and security enabled. v 115084: Replace procedure to reset repository of IM in documentation for the silent installation. v 115513: Failure in migrating/fixpack installing on Oracle partitioned DB. 115549: Wrong version of IM in the AIX package. 115632: createdb_root.sh should not require root. 115768: r11xtr AWSJCS011E. 116238: Installation completed with warning on starting Dynamic Agent. 116457: After switch the backup controller the job on DDM fo z/OS remain in start status. v 116480: After uninstall TWS 9.2 unable to reinstall due WAS profiles not properly deleted. v 117072: Installation failed because TSAMP does not exist. v v v v v

v 117110: Deadlock during JnextPlan affecting RJR_REMOTE_JOB_REQUESTS. IBM Tivoli Workload Scheduler Readme File for Fix Pack 1 for version 9.2.0

7

v 117128: Two logman running simultaneously or two UPDATESTATS can cause duplicate JS in LTP. v 117236: TWS 9.2 GA becomes unusable after the FP1 has crashed. v 117785: Broker jobs always end with status code 0. v 118185: Cscript twsinst.vbs on win32 does not work. v 118238: Dynamic agent 'partially linked' and writer down performing a planman resync. v 118257: Wrong number -1 of dependencies after release dependencies. v 118494: Wrong number of dep in final js. v 118497: Incorrect job number and dep. v 118996: ING changes. v 118997: FINALPOSTREPORTS doesn't respect dependencies. v 119016: Wrong prompt number after job rerun. v 119039: Answering twice (or more) to a prompt updates the wrong job record. v 119050: Installations fails during installation of zCentric on AS400. v 119372: Broker query "update" never updates any row impacting broker schedule throughput. v 119387: Broker query "update" never updates any row impacting broker schedule throughput (50%). v 119394: Self-Service Catalog Cross-Site Scripting: Issue 1 of 1. v 119397: Cross-Site Scripting: Issue 2 of 8. v 119408: Cross-Site Scripting: Issue 3 of 8. v 119411: Cross-Site Scripting: Issue 5 of 8. v 119412: Cross-Site Scripting: Issue 6 of 8. v 119546: Cross-Site Request Forgery: AjaxServiceDispatcherServlet/ ServiceDispatcherServlet. v 119604: Modify the upgrade scripts to enable the plan follows deps index creation. v 119606: To install is need to delete the files in TWS_HOME/ TWAMDM92/TWS/ITA/cpa/temp/ipc /. v 119646: Installation failed during TEB installation. v 119676: MIssing rerun chain displayed after run of a job with recovery and rerun option. v 119764: Monitoring portlet enhancement. 119807: "_" validation on java jobs. 120171: Installation on DB2 can erroneously check the services. 120262: Unexpected prompt dependency shown after job rerun. 120309: TWS garbage on browse joblog Linux eucJP: joblog garbled on DWC/conman. v 120326: Change tws_env.sh to set TISDIR=$UNISONHOME. v 120354: Java null Pointer Exception running a database job.

v v v v

v 120453: Files with an extension other than "opts" in / TWS/EDWA/monitors are also handled by JobManager and throws errors. v 120456: When starting the Monman service on Windows, an error is thrown in JobManager_trace.log.

8

IBM Tivoli Workload Scheduler: Readme File for Fix Pack 1

v 120473: Delete DWC unused wastools. v 120549: Mailman profiler wrong value. v 120575: Agent Self patching failing on SOLARIS and HPI. selfpatching script fails. v 120677: Wrong version in TSAMP script.

Known limitations and workarounds The following are software limitations and workarounds that affect Tivoli Workload Scheduler version 9.2.0 Fix Pack 1: Logs displayed with corrupted MBCS characters (117891) It might happen that, after starting a job on a fault-tolerant agent, some job logs displayed using the console or the command conman sj stdlist are showed with corrupted multibyte character set (MBCS) characters even if the log files content is not corrupted. This happens because some libraries do not retrieve the local codepage information. Workaround: To solve this issue, perform the following actions: 1. Log in as TWS_user and run the command locale -a to get the preferred language settings. For example: v LANG=zh_CN v LC_MESSAGES=zh_CN v LC_CTYPE=zh_CN.IBM-eucCN Note: For Linux operating systems, showing the locale settings does not imply that you have installed the language pack and font. To check that you have installed them, run the command rpm-qa|grep -i , check its output and that all the language variable are set correctly in /etc/sysconfig/i18n. 2. Stop the fault-tolerant agent and check that no process is running (including netman). 3. Depending on your operative system, at the end of each of the following files: v TWS_user.profile v TWS_home/tws_env.sh or TWS_home\tws_env.cmd v TWA_home/twa_env.sh or TWA_home\twa_env.cmd v TWS_home/jobmanrc or TWS_home\jobmanrc.cmd and at the beginning of TWS_home/StartUp or TWS_home\StartUp.cmd script, add these commands to export the following variables, set accordingly with the value for the local language: v LANG=; export LANG v LC_MESSAGES=; export LC_MESSAGES v LC_CTYPE=; export LC_CTYPE For example: v LANG=Ja_JP; export LANG v LC_MESSAGES=Ja_JP; export LC_MESSAGES v LC_CTYPE=Ja_JP.IBM-943; export LC_CTYPE 4. Log out and then log in again as TWS_user 5. Start again the fault-tolerant agent.

IBM Tivoli Workload Scheduler Readme File for Fix Pack 1 for version 9.2.0

9

IBM Installation Manager V1.8 not supported IBM Installation Manager V1.8 is not supported. You must use a previous version. Wrong version number on fault-tolerant agents After installing this fix pack, if you run the command conman "sc;info" on a fault-tolerant agent, you get a wrong version number: 9.2.0.00 instead of 9.2.0.01.

Fix pack structure This section describes the structure of the images contained in this fix pack.

Fix pack files available for Tivoli Workload Scheduler using Fix Central This is the structure of the fix pack for the engine on Fix Central: +---9.2.0-TIV-TWS-FP0001.README.zip | +---9.2.0-TIV-TWS_FP0001_AIX_AGENT.tar | +---9.2.0-TIV-TWS_FP0001_AIX_AGENT_FOR_ZOS.tar | +---9.2.0-TIV-TWS_FP0001_AIX.zip | +---9.2.0-TIV-TWS_FP0001_HPIA64.zip | +---9.2.0-TIV-TWS_FP0001_LINUX390.zip | +---9.2.0-TIV-TWS_FP0001_LINUXPPC.zip | +---9.2.0-TIV-TWS_FP0001_LINUX_X86_64.zip | +---9.2.0-TIV-TWS_FP0001_SOLARIS.zip | +---9.2.0-TIV-TWS_FP0001_SOLARIS_I386.zip | +---9.2.0-TIV-TWS_FP0001_WINDOWS_X86_64.zip | +---9.2.0-TIV-TWS_FP0001_HPIA64_AGENT.tar | +---9.2.0-TIV-TWS_FP0001_HPIA64_AGENT_FOR_ZOS.tar | +---9.2.0-TIV-TWS_FP0001_IBM_I_AGENT.tar | +---9.2.0-TIV-TWS_FP0001_IBM_I_AGENT_FOR_ZOS.tar | +---9.2.0-TIV-TWS_FP0001_LINUX_I386_AGENT.tar | +---9.2.0-TIV-TWS_FP0001_LINUX_I386_AGENT_FOR_ZOS.tar | +---9.2.0-TIV-TWS_FP0001_LINUX_PPC_AGENT.tar | +---9.2.0-TIV-TWS_FP0001_LINUX_PPC_AGENT_FOR_ZOS.tar | +---9.2.0-TIV-TWS_FP0001_LINUX_S390_AGENT.tar | +---9.2.0-TIV-TWS_FP0001_LINUX_S390_AGENT_FOR_ZOS.tar | +---9.2.0-TIV-TWS_FP0001_LINUX_X86_64_AGENT.tar | +---9.2.0-TIV-TWS_FP0001_LINUX_X86_64_AGENT_FOR_ZOS.tar | +---9.2.0-TIV-TWS_FP0001_SOLARIS_AGENT.tar

10

IBM Tivoli Workload Scheduler: Readme File for Fix Pack 1

| +---9.2.0-TIV-TWS_FP0001_SOLARIS_AGENT_FOR_ZOS.tar | +---9.2.0-TIV-TWS_FP0001_SOLARIS_I386_AGENT.tar | +---9.2.0-TIV-TWS_FP0001_SOLARIS_I386_AGENT_FOR_ZOS.tar | +---9.2.0-TIV-TWS_FP0001_WINDOWS_AGENT.zip | +---9.2.0-TIV-TWS_FP0001_WINDOWS_AGENT_FOR_ZOS.zip | +---9.2.0-TIV-TWS_FP0001_WINDOWS_X86_64_AGENT.zip | +---9.2.0-TIV-TWS_FP0001_WINDOWS_X86_64_AGENT_FOR_ZOS.zip

Installing the fix pack This section describes how to apply Fix Pack 1 to Tivoli Workload Scheduler version 9.2.0. The section is divided into the following subsections: v “Installation notes” v “Disk space requirements” on page 12 v “Installation methods” on page 13 v “Installing Tivoli Workload Scheduler for the first time using the IBM Installation Manager wizard” on page 15 v “Installing the fix pack on the Tivoli Workload Scheduler General Availability version 9.2 using the IBM Installation Manager wizard” on page 16 v “Installing the fix pack on a Tivoli Workload Scheduler version earlier than 9.2 using the IBM Installation Manager wizard” on page 18 v “Installing the fix pack using IBM Installation Manager silent installation” on page 20 v “Installing the fix pack on agents using the twsinst script” on page 21 v “Uninstalling the entire Tivoli Workload Scheduler instance” on page 22 v “Installation log files” on page 22

Installation notes When installing the Tivoli Workload Scheduler, follow these recommendations: v Before installing this fix pack on AIX V7.1 operating systems, you must apply the patch for APAR IZ99634. For more information, see: http://www01.ibm.com/support/docview.wss?uid=isg1IZ99634. v On UNIX operating systems, before installing the Tivoli Workload Scheduler fix pack, ensure that your umask is set to 022. To verify that umask is set to the correct value, from a command prompt, run the umask command. If the value is different from 022, modify it by running the command: umask 022

v On UNIX operating systems, the data base administrator must have read and run privileges for the Tivoli Workload Scheduler installation path; otherwise the installation fails. (54367) v 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 have write, read, and execute rights in this directory, you must:

IBM Tivoli Workload Scheduler Readme File for Fix Pack 1 for version 9.2.0

11

1. Unzip the eImages in a directory where all users have write, read, and execute rights. 2. Restart the installation process from this directory. After the fix pack installation completes, verify the following information: v This fix pack installs a new version of file tws_env.sh in the directory /TWS/config, where is the Tivoli Workload Scheduler installation directory, without overwriting the original version. You must merge the content of this new version with the content of the original version in /TWS to carry your customized content in the new version. (119928 IV64313) v On IBM i operating systems, if you want to install the fix pack on the Tivoli Workload Scheduler for z/OS Agent and Tivoli Workload Scheduler Dynamic Agent, verify 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. If the TWSUser is a member of a group, the fix pack installation fails. v Only on Windows operating systems, to correctly display double-byte character set (DBCS) characters, you must perform the following actions: – Set the LANG environment variable to the DBCS language code you want to use, for example, set LANG=zh_CN. – Set the TWS_TISDIR environment variable to the Tivoli Workload Scheduler home directory, for example, set TWS_TISDIR=C:\FTA\TWS. – Open the Control Panel window and click Clock, Language, and Region. – Click Region and Language. – In the Format tab, choose from the Format drop-down list the language you want to use. – In the Keyboards and Languages tab, under Display Language, click install and follow the steps to install the DBCS language pack you want to use. – In the Administrative tab, click Change system locale and, from the drop-down list, choose the language (system locale) you want to use. Note that all the settings must be coherent, that is they must refer to the same DBCS language setting. After you have completed these changes, reboot your workstation to have the changes take effect.

Disk space requirements Before starting the fix pack installation, ensure that you have the following space available 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

Temporary directory

1 GB

1750 MB

HP-UX

1,1 GB

1000 MB

Solaris

1 GB

1800 MB

Microsoft Windows

1 GB

1000 MB

Linux

1,1 GB

800 MB

AIX

12

®

IBM Tivoli Workload Scheduler: Readme File for Fix Pack 1

Table 2. Disk space requirements for installing Tivoli Workload Scheduler agents and the Java Extension fix pack Operating System

Installation directory

Temporary directory

AIX

2 GB

40 MB

HP-UX

2 GB

40 MB

Solaris

2 GB

40 MB

Microsoft Windows

2 GB

40 MB

Linux

2 GB

40 MB

Table 3. Disk space requirements for installing Tivoli Workload Scheduler agents fix pack Operating System

Installation directory

Temporary directory

AIX

450 MB

40 MB

HP-UX

560 MB

40 MB

Solaris

450 MB

40 MB

Microsoft Windows

370 MB

40 MB

Linux

410 MB

40 MB

Table 4. Disk space requirements for installing the Tivoli Workload Scheduler for z/OS agent fix pack Operating System

Installation directory

Temporary directory

AIX

340 MB

40 MB

HP-UX

420 MB

40 MB

Solaris

290 MB

40 MB

Microsoft Windows

275 MB

40 MB

Linux

275 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 /var/tmp.

Installation methods You can install the fix pack using one of the following methods: For Master domain manager or dynamic domain manger or their backups: v “Installing Tivoli Workload Scheduler for the first time using the IBM Installation Manager wizard” on page 15 v “Installing the fix pack on the Tivoli Workload Scheduler General Availability version 9.2 using the IBM Installation Manager wizard” on page 16 v “Installing the fix pack on a Tivoli Workload Scheduler version earlier than 9.2 using the IBM Installation Manager wizard” on page 18 v “Installing the fix pack using IBM Installation Manager silent installation” on page 20. IBM Tivoli Workload Scheduler Readme File for Fix Pack 1 for version 9.2.0

13

For fault-tolerant agent or domain manager: v “Installing the fix pack on agents using the twsinst script” on page 21.

Before Installing Before installing the fix pack using any of 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 Tivoli Workload Scheduler network. 2. Shut down Tivoli Workload Scheduler. 3. Run the following commands, depending on your configuration: Master domain manager or dynamic domain manger or their backups: On Windows operating systems: conman "unlink @; noask" conman "stop; wait" conman "stopmon;wait" ShutdownLwa.cmd .\stopServer.bat

On UNIX and Linux operating systems: conman "unlink @; noask" conman "stop; wait" conman "stopmon;wait" conman "shut;wait" ShutDownLwa ./stopServer.sh

Fault-tolerant agent or domain manager: On Windows operating systems: conman "unlink @; noask" conman "stop; wait" conman "stopmon;wait" ShutdownLwa.cmd

On UNIX and Linux operating systems: conman "unlink @; noask" conman "stop; wait" conman "stopmon;wait" conman "shut;wait" ShutDownLwa

Tivoli Workload Scheduler for z/OS agent or Tivoli Workload Scheduler dynamic agent: On Windows operating systems: ShutdownLwa.cmd

On UNIX and Linux operating systems: ShutDownLwa

If you have jobs scheduled to run on the instance you are upgrading, make sure that they have completed otherwise some processes, such as jobmon or joblnch, might still be active. 4. Download the ZIP file specific for the operating system. 5. Delete the content of the following directory: /TWS/ITA/cpa/temp/ ipc, where is the Tivoli Workload Scheduler installation directory. 6. Extract the content of the ZIP files into a directory, using one of the unzip tools available 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.

14

IBM Tivoli Workload Scheduler: Readme File for Fix Pack 1

Note: If you want to install the fix pack on IBM i, to untar the eImages, see “Untar the eImages for the Tivoli Workload Scheduler for z/OS Agent and Dynamic Agent on IBM i operating systems.”

Untar the eImages for the Tivoli Workload Scheduler for z/OS Agent and Dynamic Agent on IBM i operating systems To untar the TWS92_IBM_I_AGENT.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 TWS92_IBM_I_AGENT.tar and run the command: "tar xvf TWS92_IBM_I_AGENT.tar"

4. Exit from the PASE shell. Using AIXterm: 1. Start the Xserver 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 TWS92_IBM_I_AGENT.tar file.

Installing Tivoli Workload Scheduler for the first time using the IBM Installation Manager wizard To install Tivoli Workload Scheduler for the first time using the interactive wizard, complete the following steps: 1. Perform the actions described in section “Before Installing” on page 14. 2. Download the TAR or ZIP file specific for the operating system and extract it. To extract the .tar file, ensure that you use the GNU version of the TAR command. Otherwise, if you extract the file using a version other than GNU, your fix pack installation fails. If you are installing on a UNIX operating system, run the following command: chmod -R 755

3. Depending on the type of operating system, run the following command: On Windows operating systems: From the directory where you extracted the files, run setupTWS.cmd -gapath . On UNIX and Linux operating systems: From the directory where you extracted the files, run setupTWS.sh -gapath . where is the path where you extracted the TAR or ZIP file specific for your operating system. The IBM Installation Manager window opens. 4. Select the packages you want to install and the click Next to continue. 5. In the Validating Results page, check that all the prerequisites are fulfilled and then click Next to continue. IBM Tivoli Workload Scheduler Readme File for Fix Pack 1 for version 9.2.0

15

6. In the Licenses page, read the license agreement for the selected package. If you agree to the terms of all the license agreements, click I accept the terms in the license agreements and then click Next. 7. In the Install Packages page, type the directory where you want to install the product and then click Next to continue. 8. In the Features page, select the Tivoli Workload Scheduler features: v master domain manager v dynamic domain manager Click Next to continue. 9. Complete the not greyed fields in the following panels: For master domain manager v User information v Master configuration v v v v

Database configuration WebSphere profile configuration WebSphere ports configuration Disk space check

For dynamic domain manager v User information v v v v v

Dynamic domain manager configuration Database configuration WebSphere profile configuration WebSphere ports configuration Disk space check

For each panel, click Validate to validate that the information you entered is correct and then click Next to continue. 10. In the Summary page, review your choices before upgrading the product package. To change any choices that you made on previous pages, click Back and make the changes. When you are satisfied with your installation choices, click Install to install the packages. 11. Ignore any request to create the WebSphere Application Server administrator user. 12. Click Finish to complete the installation.

Installing the fix pack on the Tivoli Workload Scheduler General Availability version 9.2 using the IBM Installation Manager wizard To install the fix pack using the interactive wizard, complete the following steps: 1. Perform the actions described in section “Before Installing” on page 14. 2. Download the TAR or ZIP file specific for the operating system and extract it. To extract the .tar file, ensure that you use the GNU version of the TAR command. Otherwise, if you extract the file using a version other than GNU, your fix pack installation fails. If you are installing on a UNIX operating system, run the following command: chmod -R 755

3. You can start the installation process by using one of the following methods:

16

IBM Tivoli Workload Scheduler: Readme File for Fix Pack 1

IBM Installation Manager program v Start the Installation Manager. v In the menu bar, click File > Preferences. v The Repositories window opens. Click Add Repository. v In the Select a Repository window, in the Filter pane, type the path to the directory where the fix pack files are located. v In the Directories pane, select the directory containing the fix pack files and click OK. v Verify that the checkbox Search service repositories during installation and updates is not selected, then click OK in the Repositories window. update.bat or update.sh script Depending on the type of operating system, run the following command: On Windows operating systems: On Windows platforms, you must use only the 32-bit version of IBM Installation Manager. From the root directory of the installation DVD or of the eImages, run update.bat. On UNIX and Linux operating systems: From the root directory of the installation DVD or of the eImages, run update.sh. The IBM Installation Manager window opens. 4. Click Update. 5. In the Installation Packages page, select the "Tivoli Workload Scheduler" > "Version 9.2.0.1" product package. Click Next to continue. 6. In the Licenses page, read the license agreement for the selected package. If you agree to the terms of all the license agreements, click I accept the terms in the license agreements and then click Next. 7. In the Features page, select the Tivoli Workload Scheduler features: v master domain manager v dynamic domain manager Click Next to continue. 8. Complete the not greyed fields in the following panels: For master domain manager v Upgrade configuration v v v v v v

User information Master configuration Database configuration WebSphere profile configuration WebSphere ports configuration Disk space check

For dynamic domain manager v Upgrade configuration v User information v Dynamic domain manager configuration IBM Tivoli Workload Scheduler Readme File for Fix Pack 1 for version 9.2.0

17

v v v v

Database configuration WebSphere profile configuration WebSphere ports configuration Disk space check

For each panel, click Validate to validate that the information you entered is correct. 9. In the Summary page, review your choices before upgrading the product package. To change any choices that you made on previous pages, click Back and make the changes. When you are satisfied with your installation choices, click Update to install the update packages 10. Click Finish to complete the installation. Note: If the fix pack installation fails, the Tivoli Workload Scheduler General Availability version 9.2 instance might not work properly and the following error is shown in the installation logs: An error occurred while restoring the Tivoli Workload Scheduler instance from the backup, located in the folder

where is the folder where the Tivoli Workload Scheduler backup files are located. To recover from this issue, complete the following steps: 1. Check that you have right permissions for the Tivoli Workload Scheduler installation path, that there is enough disk space, and that no process is locking the files located in the Tivoli Workload Scheduler installation path. 2. Access the and remove the folders with the same names as those located in the Tivoli Workload Scheduler installation folder. 3. Copy all the folders from the to the Tivoli Workload Scheduler installation folder. 4. Rerun the fix pack installation steps.

Installing the fix pack on a Tivoli Workload Scheduler version earlier than 9.2 using the IBM Installation Manager wizard To install the fix pack on a Tivoli Workload Scheduler version earlier than 9.2 using the interactive wizard, complete the following steps: 1. Perform the actions described in section “Before Installing” on page 14. 2. Download the TAR or ZIP file specific for the operating system and extract it. To extract the .tar file, ensure that you use the GNU version of the TAR command. Otherwise, if you extract the file using a version other than GNU, your fix pack installation fails. If you are installing on a UNIX operating system, run the following command: chmod -R 755

3. Depending on the type of operating system, run the following command: On Windows operating systems: From the directory where you extracted the files, run setupTWS.cmd -gapath . On UNIX and Linux operating systems: From the directory where you extracted the files, run setupTWS.sh -gapath .

18

IBM Tivoli Workload Scheduler: Readme File for Fix Pack 1

4. 5. 6.

7. 8.

where is the path where you extracted the TAR or ZIP file specific for your operating system. The IBM Installation Manager window opens. Select the packages you want to install and the click Next to continue. In the Validating Results page, check that all the prerequisites are fulfilled and then click Next to continue. In the Licenses page, read the license agreement for the selected package. If you agree to the terms of all the license agreements, click I accept the terms in the license agreements and then click Next. In the Install Packages page, type the directory where the earlier Tivoli Workload Scheduler version is installed and then click Next to continue. A warning window opens with the message: The location already contains a Tivoli Workload Scheduler instance of version that will be upgraded.

where is the directory where the earlier Tivoli Workload Scheduler version is installed and is the installed version. Click OK to continue. 9. In the Features page, select the Tivoli Workload Scheduler features: v master domain manager v dynamic domain manager Click Next to continue. 10. Complete the not greyed fields in the following panels: For master domain manager v v v v v v

Upgrade configuration User information Master configuration Database configuration WebSphere profile configuration WebSphere ports configuration

v Disk space check For dynamic domain manager v Upgrade configuration v User information v Dynamic domain manager configuration v Database configuration v WebSphere profile configuration v WebSphere ports configuration v Disk space check For each panel, click Validate to validate that the information you entered is correct and then click Next to continue. 11. In the Summary page, review your choices before upgrading the product package. To change any choices that you made on previous pages, click Back and make the changes. When you are satisfied with your installation choices, click Install to install the packages. 12. In the Install packages page, in the Which program do you want to start? pane, select None and the click Finish to complete the installation. IBM Tivoli Workload Scheduler Readme File for Fix Pack 1 for version 9.2.0

19

Installing the fix pack using IBM Installation Manager silent installation After you complete the actions described in the section “Before Installing” on page 14, if you want to install the fix pack in silent mode use silent installation. When you run a silent installation, the Installation Manager is already installed and you use an XML response file that contains parameters required to install the product package. The response file includes all the information required to run the installation without user intervention. You are provided with several sample response files located under the \response_files\ directory. Create your own response file or customize a sample response file to include the options required to complete the installation. Perform the following steps: 1. Copy the relevant response file to a local directory. 2. Edit the Tivoli Workload Scheduler section. For details about the response file properties, see Planning and Installation. 3. Save the file with your changes. 4. Open a command-line prompt. 5. Go to the Installation Manager tools directory. The default tools directory is: v On Windows operating systems: C:\Program Files\IBM\Installation Manager\eclipse\tools

v On UNIX and Linux operating systems: /opt/IBM/InstallationManager/eclipse/tools

6. Run the following command: v On Windows operating systems: imcl.exe -c

v On UNIX and Linux operating systems: ./imcl -c

7. Type P and press the Enter key to access the Preferences menu. 8. Type 1 and press the Enter key to access the Repositories menu. 9. Remove all the listed repositories by typing the number beside each repository to edit it and then type 2 to remove the repository. Perform these actions for each of the listed repositories. 10. If there is an X beside the S menu item related to Search service repositories, type S and press the Enter key to deselect it. 11. 12. 13. 14.

Type A and press the Enter key to apply the changes. Type R and press the Enter key to return to the main menu. Type X and press the Enter key to exit. Go to the Installation Manager tools directory. The default tools directory is: v On Windows operating systems: C:\Program Files\IBM\Installation Manager\eclipse\tools

v On UNIX and Linux operating systems: /opt/IBM/InstallationManager/eclipse/tools

20

IBM Tivoli Workload Scheduler: Readme File for Fix Pack 1

15. Run the following command: v On Windows operating systems: imcl.exe input \response_file.xml -log \log_file.xml -acceptLicense -sP

v On UNIX and Linux operating systems: ./imcl input //response_file.xml -log //log_file.xml -acceptLicense -sP

where response_file is the name of the response file to be used for the installation, and log_file is the name of the log file that records the result of the silent installation.

Installing the fix pack on agents using the twsinst script You can use the twsinst script to install the fix pack on agents. To show command usage: On Windows operating systems: cscript twsinst.vbs -u | -v

On UNIX and Linux operating systems: ./twsinst -u | -v

To install a fix pack: On Windows operating systems: twsinst -update -uname TWS_user -password user_password [-domain user_domain] [-inst_dir installation_dir [-recovInstReg {true | false}]] [-wait ] [-lang ]

On UNIX and Linux operating systems: ./twsinst -update -uname TWS_user [-inst_dir installation_dir [-recovInstReg {true | false}]] [-wait ][-lang ]

Where: -update Upgrades an existing agent that was installed using the twsinst script. -uname TWS_user The name of the user for which Tivoli Workload Scheduler is upgraded. -password user_password Windows operating systems only. The password of the user for which you are upgrading Tivoli Workload Scheduler. -domain user_domain Windows operating systems only. The domain name of the Tivoli Workload Scheduler user. The default is the name of the workstation on which you are upgrading the product. -inst_dir installation_dir [-recovInstReg true | false ] The name of the directory where you installed Tivoli Workload Scheduler. When installing the fix pack the inst_dir parameter is used: v If the installation process cannot retrieve the product installation location from the registries. IBM Tivoli Workload Scheduler Readme File for Fix Pack 1 for version 9.2.0

21

v If you need to re-create the Tivoli Workload Scheduler registries again before the fix pack installation. Set the value of recovInstReg to true if you want to re-create the registry files while performing a fix pack installation on a fault-tolerant agent. -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 interval the installation process does not proceed and an error message is displayed. Valid values are integers or -1 for the product to wait indefinitely. The default is 60. -lang lang_id The language used for the twinst messages displayed. The default is the value of the system variable LANG. If the language catalog for the value you specified is missing, the default C language catalog is used. twsinst for Windows is a Visual Basic Script (VBS) that you can run in CScript and WScript mode. The Tivoli Workload Scheduler user is automatically created. The software is installed by default in the Tivoli Workload Scheduler installation directory. The default value is %ProgramFiles%\IBM\TWA. If you enabled the Security Warning, a dialog box is displayed during the installation. In this case answer Run to continue. After you complete the actions described in the section “Before Installing” on page 14, perform the following action: v Run twsinst 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 Tivoli Workload Scheduler for z/OS Agent or a Tivoli Workload Scheduler Dynamic Agent, after you complete the actions described in the section “Untar the eImages for the Tivoli Workload Scheduler for z/OS Agent and Dynamic Agent on IBM i operating systems” on page 15, run the twsinst script from the QSH shell.

Uninstalling the entire Tivoli Workload Scheduler instance Master domain manager or dynamic domain manger or their backups: To uninstall using the IBM Installation Manager, see Planning and Installation. Fault-tolerant agent or domain manager: To uninstall the entire Tivoli Workload Scheduler instance, use the twsinst -uninst -uname username command from the TWS_home directory, where username is the name of the user for which the Tivoli Workload Scheduler agent is uninstalled.

Installation log files The following installation log files give you details about the status of the fix pack installation for the master domain manager, backup master domain manager, the agents, and the connector: v Log file for master domain managers, dynamic domain managers, and their backups:

22

IBM Tivoli Workload Scheduler: Readme File for Fix Pack 1

On Windows operating systems: C:\ProgramData\IBM\InstallationManager\logs\.xml

Note: The folder ProgramData is a hidden folder. On UNIX and Linux operating systems: /var/ibm/InstallationManager/logs/.xml

where is the date and is the time when the log file is created. v Log file for fault-tolerant agents and dynamic agents: On Windows operating systems: %Temp%\TWA\tws9201\ twsinst__^9.2.0.0n.log

On UNIX and Linux operating systems: /tmp/TWA/tws9201/ twsinst__^9.2.0.0n.log

where is the operating system running on the workstation where you are applying the fix pack. is the name of the user for which Tivoli Workload Scheduler was installed (the name you supplied during installation). n

is the fix pack number. For this fix pack the number is 1.

Documentation updates This section contains new information and documentation corrections contained in this fix pack. It is organized by manual: Tivoli Workload Scheduler Version 9.2.0 Administration Guide, SC23-9113-07 Authentication method configuration In Chapter "Configuring the Dynamic Workload Console", section "Configuring access to the Dynamic Workload Console", subsection "Configuring the Dynamic Workload Console to use the local OS or PAM authentication method", do the following changes: v In section "About this task", change the description to: To modify the Dynamic Workload Console authentication method to use the local OS or PAM authentication method, perform the following steps: v In bullet number 4, change "operative" to "operating". v After bullet number 4, insert the following: – 5. Switch back to the Dynamic Workload Console. – 6. From the navigation toolbar on the left side, click the search glass icon, on top of the toolbar. In the search field, enter User Roles to open the User Roles page. – 7. Enter the new user account in the User ID field and click Search. – 8. Click on the user name in the results table.

IBM Tivoli Workload Scheduler Readme File for Fix Pack 1 for version 9.2.0

23

– 9. Select the roles the for primary administrative user. Usually all roles are assigned. – 10. Press the Save button. Reorganizing the DB2 database In Chapter "Data maintenance", section "Administrative tasks DB2", subsection "Reorganizing the DB2 database", in the procedure list do the following changes: v Change item number 2 to: 2. Stop WebSphere Application Server and appservman by running the following command: conman "stopappserver;wait"

See Starting and stopping the application server and appservman for full details. v Change item number 9 to: 9. Restart WebSphere Application Server and appservman by running the following command: conman "startappserver;wait"

See Starting and stopping the application server and appservman for full details. Tivoli Workload Scheduler Version 9.2.0 User's Guide and Reference, SC32-1274-15 117572 In Chapter "Defining objects in the database", section "Defining scheduling objects", subsection "Job definition", in table 35 "Required and optional attributes for the definition of a database job", and in table 36 "Required and optional attributes for the definition of an MSSQL job", in the description of attribute credentials, change the sentence in parenthesis from: domain users are not supported to: domain users are supported in the form DOMAIN\USER and add the following bullet: v When integrated security is used for Microsoft SQL server, the sqljdbc_auth.dll library (that is part of the Microsoft JDBC Driver 4.0 for SQL Server package) must be placed in the same directory where the JDBC driver is located, and this path must be added to the PATH system environment variable. 110727 In Chapter "Managing objects in the plan - conman", section "Conman commands", in the description of argument joboption of commands submit file and submit job, change the syntax of parameter follows to: follows=[netagent::][workstation#]{jobstreamname[hhmm [mm/dd[/yy]]] [.job | @] | jobstream_id.job;schedid}| job[;nocheck][;wait=time][,...] 100488 In Chapter "Managing objects in the plan - conman", section "Conman commands", in the description of argument domain of command deployconf, change this description to: Specifies the name of the destination domain for the operation. Wildcard characters are not permitted.

24

IBM Tivoli Workload Scheduler: Readme File for Fix Pack 1

If you do not include domain, the default domain is the one in which conman is running. Tivoli Workload Scheduler Version 9.2.0 Planning and Installation, SC32-1273-14 117236 In Part 2 "Tivoli Workload Scheduler", Chapter "Troubleshooting installation, migration, and uninstallation", section "Problem scenarios: install, reinstall, upgrade, migrate, and uninstall", subsection "Fix pack installation problems", add the following paragraph: Master domain manager unavailable after fix pack installation fails You have tried to apply a fix pack, but the installation fails and the master domain manager becomes unavailable. Cause and solution It might happen that the master domain manager becomes unavailable after a fix pack installation fails. To solve this issue, you must delete the content of the following directories: Windows operating sytems v \properties v \TDWB v \TWS v \wastools UNIX and Linux operating systems: v /properties v /TDWB v /TWS v /wastools where is the Tivoli Workload Scheduler installation directory, and replace it with the content of the same directories saved in the backup directory chosen when installing the fix pack. An example of backup directory on Windows operating systems is: C:\Users\ADMINI~1\AppData\Local\Temp\2\tws92UpgradeBackup\ 16102014\instance_bck. 116578 In Part 2 "Tivoli Workload Scheduler", Chapter "Creating or upgrading the Tivoli Workload Scheduler database tables before installing or upgrading", every reference to the login user as root on UNIX and Linux operating systems, must be changed to root or database administrator. 116480 In Part 2 "Tivoli Workload Scheduler", Chapter "Troubleshooting installation, migration, and uninstallation", section "Problem scenarios: install, reinstall, upgrade, migrate, and uninstall", subsection "Reinstallation problems", add the following paragraph: Reinstalling a master domain manager or dynamic domain manager with a corrupted WebSphere Application Server registry file

IBM Tivoli Workload Scheduler Readme File for Fix Pack 1 for version 9.2.0

25

You are reinstalling a master domain manager or dynamic domain manager and the reinstallation fails because of a corrupted WebSphere Application Server registry file. Cause and solution It might happen that the reinstallation fails because the previous uninstallation left a corrupted WebSphere Application Server registry file. To solve this issue, before reinstalling, you must clean the corrupted WebSphere Application Server registry file by running the following command: v On Windows operating systems: \manageprofiles.bat -validateAndUpdateRegistry

v On UNIX and Linux operating systems: /manageprofiles.sh -validateAndUpdateRegistry

where is the full path to the directory where WebSphere is installed. 115273 In Part 2 "Tivoli Workload Scheduler", Chapter "Troubleshooting installation, migration, and uninstallation", section "Problem scenarios: install, reinstall, upgrade, migrate, and uninstall", subsection "Other installation problems", add the following paragraph: On UNIX operating systems master domain manager or dynamic domain manager installation fails with error AWSFAB035E While you are installing a master domain manager or a dynamic domain manager on a UNIX operating system, you receive the error AWSFAB035E. On UNIX operating systems, during the installation of a master domain manager or a dynamic domain manager, you receive the following error: AWSFAB035E The installation has failed. For more details see the log file: .

In the file you find a reference to a missing parameter from the Tivoli Workload Scheduler configuration. Cause and solution This error might occur because some operating system libraries required by the Common Installation Technology (CIT) component are missing. To solve the problem, check the prerequisite libraries. For a complete list of the correct versions to install, see the System Requirements Document at http://www-01.ibm.com/support/ docview.wss?rs=672&uid=swg27041009. 110861 In Part 2 "Tivoli Workload Scheduler", Chapter "Installing", section "Installing main components", subsection "Installing agents", subsection "Agent installation parameters", change the description of parameter -lang lang_id as follows: The language in which the twsinst messages are displayed. If not specified, the system LANG is used. If the related catalog is

26

IBM Tivoli Workload Scheduler: Readme File for Fix Pack 1

missing, the default C language catalog is used. If neither -lang nor LANG are used, the default codepage is set to SBCS. For a list of valid values for these variables see the following table: Table 5. Valid values for -lang and LANG parameter Language

Value

Brazilian portuguese

pt_BR

Chinese (traditional and simplified)

zh_CN, zh_TW

English

en

French

fr

German

de

Italian

it

Japanese

ja

Korean

ko

Russian

ru

Spanish

es

Note: This is the language in which the installation log is recorded and not the language of the installed engine instance. twsinst installs all languages as default. Tivoli Workload Scheduler Version 9.2.0 Integrating with Other Products, SC23-8904-07 IZ42313 In Chapter "Integrating with Tivoli Enterprise Console", section "Job Scheduling events format", in table "Event formats", delete the following event: Table 6. Event formats Event Number

Event Class

115

TWS_Job_Stuck

IBM Tivoli Workload Scheduler Readme File for Fix Pack 1 for version 9.2.0

27

28

IBM Tivoli Workload Scheduler: Readme File for Fix Pack 1

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: 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 Handbook 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: v Registration and eligibility. v Telephone numbers, depending on the country in which you are located. v Information you must have before contacting IBM Software Support.

© Copyright IBM Corp. 2014

29

30

IBM Tivoli Workload Scheduler: Readme File for Fix Pack 1

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 user's 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: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan, Ltd. 1623-14, Shimotsuruma, Yamato-shi Kanagawa 242-8502 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.

© Copyright IBM Corp. 2014

31

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.

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 available on the Web at “http://www.ibm.com/legal/copytrade.shtml." Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml.

32

IBM Tivoli Workload Scheduler: Readme File for Fix Pack 1

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 Government Commerce. ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office. Java™ and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.

Linux is a trademark of Linus Torvalds 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

33

34

IBM Tivoli Workload Scheduler: Readme File for Fix Pack 1




Product Number: 5698-WSH

Printed in USA