(R)Tivoli Workload Scheduler and Connector Fix Pack 0012 for Version 8.1.0 +---- Note ------------------------------------------------------------+ Before using this information and the product it supports, read the information in 3, "Notices". +----------------------------------------------------------------------+ i) Second Edition (November 2004) This edition applies to fix pack 12 (PTF U800231) Tivoli Workload Scheduler and Connector for Version 8.1.0 Copyright International Business Machines Corporation 2003, 2004. All rights reserved. Contents i) Second Edition (November 2004) 1) Tivoli Workload Scheduler and Connector Fix Pack 0012 for Version 8.1.0 1a) About this release 1a.i) Problems Fixed in 8.1.0-TIV-Tivoli Workload Scheduler-Fix Pack 0012 New APARs for Version 8.1.0 New Internal Defects for Version 8.1.0 1a.ii) Problems Fixed in 8.1.0-TIV-Tivoli Workload Scheduler-Fix Pack 0011 New APARs for Version 8.1.0 New APARs for Version 8.2 New Internal Defects 1a.iii) Problems Fixed in 8.1.0-Tivoli Workload Scheduler-Fix Pack 10 New APARs for Version 8.1.0 New APARs for Version 8.2 New Internal Defects APARs in 8.1-Tivoli Workload Scheduler-Fix Pack 09 Version 8.1 APARs in Tivoli Workload Scheduler-FP09 for Version 8.1 Internal Defects in 8.1-Tivoli Workload Scheduler-FP09 for Version 8.1 APARs in 8.1-Tivoli Workload Scheduler-FP08 for Version 8.1 Internal Defects in 8.1-Tivoli Workload Scheduler-FP08 for Version 8.1 APARs in 8.1-Tivoli Workload Scheduler-FP07 for Version 8.1 Internal Defects in 8.1-Tivoli Workload Scheduler-FP07 for Version 8.1 APARs in 8.1-Tivoli Workload Scheduler-U487473 for Version 8.1 Internal Defects in 8.1-Tivoli Workload Scheduler-U487473 for Version 8.1 APARs in 8.1-Tivoli Workload Scheduler-U485968 for Version 8.1 APARs in 8.1-Tivoli Workload Scheduler-U485968 for Version 6.1 or 7.0 Internal Defects in 8.1-Tivoli Workload Scheduler-U485968 APARs in 8.1-Tivoli Workload Scheduler-0006 for Version 8.1 APARs in 8.1-Tivoli Workload Scheduler-0006 for Version 6.1 or 7.0 Internal Defects in 8.1-Tivoli Workload Scheduler-0006 APARs in 8.1-Tivoli Workload Scheduler-0004 for Version 8.1 APARs in 8.1-Tivoli Workload Scheduler-0004 for Version 6.1 or 7.0 Internal Defects in 8.1-Tivoli Workload Scheduler-0004 APARs in 8.1-Tivoli Workload Scheduler-0001 1a.iv) Architecture(s) 1a.v) Dependencies 1a.vi) Files Replaced by this Patch 1a.vii) Patches Superseded by this Patch 1a.viii) Patch Contents 1a.ix) Applying the Fix Pack UNIX Windows Tivoli Workload Scheduler Plus Module Tivoli Workload Scheduler Connector Additional Installation Instructions Fix Pack Installation Policy and Changes in the Opens Dependency Mechanism 1a.x) Notes for the User Changed Syntax for evtsize Command Autotrace level 3.1.5 IY35486 - Windows Users Information 165022 Documentation Error in Tivoli Workload Scheduler Reference Guide IY41955 - Windows Silent Installation IY45797 - Cannot apply a Tivoli Workload Scheduler fix pack on W2K if installation directory is different from the twsuser home directory Feature 153685: Implementation of nocheck and wait Options for submit Command Feature 153621: Implementation of at/until time and absolute Keywords 168083 End- to- end: Re-use of deleted dependencies position APAR IY52476 Documentation APAR Installation Considerations Special Considerations 1a.xi) Known Defects and Limitations for the Scheduler 1a.xii) Known Defects and Limitations for Tivoli Workload Scheduler Connector 2) Contacting IBM(R) Software Support 3) Notices 3a) Trademarks 1) Tivoli Workload Scheduler and Connector Fix Pack 0012 for Version 8.1.0 Date December 17, 2004 Fix Pack 8.1.0-TIV-TWS-FP0012 PTF Number U800231 Product Tivoli Workload Scheduler Version 8.1.0 General Description Tivoli Workload Scheduler fix pack 0012 for Version 8.1.0 and Tivoli Workload Scheduler Connector fix pack 0012 for Version 8.1.0 Please review this section thoroughly before installing or using this fix pack. 1a) About this release This section includes the following topics: * 1a.i, "Problems Fixed in 8.1.0-TIV-Tivoli Workload Scheduler-Fix Pack 0012" * "New Internal Defects for Version 8.1.0" * 1a.ii, "Problems Fixed in 8.1.0-TIV-Tivoli Workload Scheduler-Fix Pack 0011" * "New APARs for Version 8.1.0" * "New APARs for Version 8.2" * "New Internal Defects" * 1a.iii, "Problems Fixed in 8.1.0-Tivoli Workload Scheduler-Fix Pack 10" * "New APARs for Version 8.2" * "New Internal Defects" * "APARs in 8.1-Tivoli Workload Scheduler-Fix Pack 09 Version 8.1" * "APARs in Tivoli Workload Scheduler-FP09 for Version 8.1" * "Internal Defects in 8.1-Tivoli Workload Scheduler-FP09 for Version 8.1" * "APARs in 8.1-Tivoli Workload Scheduler-FP08 for Version 8.1" * "Internal Defects in 8.1-Tivoli Workload Scheduler-FP08 for Version 8.1" * "APARs in 8.1-Tivoli Workload Scheduler-FP07 for Version 8.1" * "Internal Defects in 8.1-Tivoli Workload Scheduler-FP07 for Version 8.1" * "APARs in 8.1-Tivoli Workload Scheduler-U487473 for Version 8.1" * "Internal Defects in 8.1-Tivoli Workload Scheduler-U487473 for Version 8.1" * "APARs in 8.1-Tivoli Workload Scheduler-U485968 for Version 8.1" * "APARs in 8.1-Tivoli Workload Scheduler-U485968 for Version 6.1 or 7.0" * "Internal Defects in 8.1-Tivoli Workload Scheduler-U485968" * "APARs in 8.1-Tivoli Workload Scheduler-0006 for Version 8.1" * "APARs in 8.1-Tivoli Workload Scheduler-0006 for Version 6.1 or 7.0" * "Internal Defects in 8.1-Tivoli Workload Scheduler-0006" * "APARs in 8.1-Tivoli Workload Scheduler-0004 for Version 8.1" * "APARs in 8.1-Tivoli Workload Scheduler-0004 for Version 6.1 or 7.0" * "Internal Defects in 8.1-Tivoli Workload Scheduler-0004" * "APARs in 8.1-Tivoli Workload Scheduler-0001" 1a.i) Problems Fixed in 8.1.0-TIV-Tivoli Workload Scheduler-Fix Pack 0012 Fix pack 12 supersedes all the preceding Fix packs. Therefore, Fix pack 12 fixes also all the APAR's and internal defects fixed by fix pack 1 to fix pack 11. New APARs for Version 8.1.0 * APAR IY58104 Symptoms: There are orphaned TWS job objects when running TBSM discovery. * APAR IY58243 Symptoms: The "Dependencies Status" is "not released" ,although it is canceled. * APAR IY58973 Symptoms: AWS1130005 error is received when entering a "composer validate" is issued by any other user than maestro. * APAR IY59057 Symptoms: stdlist message is not correct when communication between mailman and a writer was interrupted. * APAR IY59058 Symptoms: Event 252 sent when actually the link was not dropped. * APAR IY61530 Symptoms: Fta cannot be stopped ,after switchmgr has been performed while FTA is down.This is a sysroute of IY60567, IY61233. * APAR IY61734 Symptoms: Stageman memory fault reading symnew with missing dependencies. * APAR IY62198 Symptoms: Jobman and Batchman abended when a running job that has a long jcl file name is killed. * APAR IY63093 Symptoms: A JOB With a Recovery option of "continue after recovery" does not launch. New Internal Defects for Version 8.1.0 * Internal CMVC Defect 154368: Symptoms: MSG AWSDEC100E issued instead of AWSDEC101i. * Internal CMVC Defect 173210: Symptoms: E2E Heap memory corruption. 1a.ii) Problems Fixed in 8.1.0-TIV-Tivoli Workload Scheduler-Fix Pack 0011 New APARs for Version 8.1.0 * APAR IY58174 Symptoms: JOBMON fails to create tmp file at start up time if multiple TWS instances are installed on a single Windows machine. * APAR IY58584 Symptoms: Abended rerun jobs status shows as exec indefinitely on Master. This apar required IY50278 on TWS 8.2.0-TIV-TWS-FP0005. * APAR IY58834 Symptoms: composer create says 'unable to open' file despite the file being create. * APAR IY53992 Symptoms: TWS events are not sent to TEC server after applying TEC fix pack. * APAR IY55007 Symptoms: reptr displays AWS21060458 message, if the total character length of "Dependencies" data exceeds 32 bytes. * APAR IY55835 Symptoms: Dependency prompt is created after JNEXTDAY for a follows dependency that was resolved prior to JNEXTDAY. * APAR IY57199 Symptoms: Reporter dies with SIGSEGV due to memory corruption * APAR IY58454 Symptoms: Internetwork dependencies prompt for a CF schedule gets truncated. * APAR IY58968 Symptoms: After applying TWS 8.1 Fix Pack 10 LINUX FTAS FAIL to link following subsequent jnextdays New APARs for Version 8.2 * APAR IY55606 Symptoms: TWS 8.2 Plus Module will not install on TMR after MN has been created. * APAR IY56317 Symptoms: Showexec does not list running jobs howexec does not list running jobs * APAR IY58655 Symptoms: launching jobs from JSC 1.3 (fp03) with bad security settings New Internal Defects * Internal CMVC Defect 171478 Symptoms: TECAD_START fails if EndPoint is installed in C:\Program Files. * Internal CMVC Defect 171972 Symptoms: Reasoning out of bound array access. * Internal CMVC Defect 171973 Symptoms: Reasoning: initialized variables * Internal CMVC Defect 172140 Symptoms: Composer replace resources fails on LINUX 1a.iii) Problems Fixed in 8.1.0-Tivoli Workload Scheduler-Fix Pack 10 New APARs for Version 8.1.0 * APAR IY47219 Symptoms: Engine hangs when listing or setting alternate plan with many entries in SCHEDLOG DIR * APAR IY49435 Symptoms: Partial wild cards in security file are not working correctly * APAR IY49695 Symptoms: Tivoli Workload Scheduler connector programs abend with SIGSEGV if no security file is present when a list is loaded in JSC * APAR IY50186 Symptoms: The job description of JOB1 is moved to JOB2'S within the job stream after modifying the JOB * APAR IY50927 Symptoms: Parms cannot used from Conman with TWS 8.1 and 8.2 * APAR IY51314 Symptoms: Cancelled Job still EXEC allows rerun action from JSC and CLI - JOB is on incorrect state for rerun * APAR IY51363 Symptoms: Calendar DB corrupts when multiple "composer replace" are run simultaneously * APAR IY51658 Symptoms: Domain names greater than eight (8) characters cause problems with linking and unlinking subordinate FTAs * APAR IY51701 Symptoms: COMPOSER AWS22080148 WARNING: UNTIL time occurs before AT time Incorrect Warning for Time zones * APAR IY51712 Symptoms: Conman 'show schedules' command not properly sorting output * APAR IY51927 Symptoms: JSC hangs when trying to obtain 'Status of All Files' * APAR IY52222 Symptoms: High CPU usage by CONMAN when doing show JOBS @#@ * APAR IY52241 Symptoms: Getting "AWS22020072 no qualified entries" error message when trying to display jobs using +STATE=ABEND orSTATE=HOLD * APAR IY52253 Symptoms: JSC Filter on login fails to retrieve more than 250 records * APAR IY52337 Symptoms: Standard Agent (SA) Job Abend and PID J0 when executed during Jnextday (timing issue) * APAR IY52339 Symptoms: Composer and Conman creates TMP files * APAR IY52476 Symptoms: EVERY jobs with AT times behavior should be changed back to the way it historically worked * APAR IY53201 Symptoms: After applying connector patch 8.1-TWS-FP09, JSC does not show jobstream/schedule descriptions even though composer does * APAR IY53443 Symptoms: User Info Field contains garbage with TWS 8.2 FP-02 StreamLogon fix in place * APAR IY53520 Symptoms: Schedule with JOB that has +1 days scheduled to launch on day when time changes shows the incorrect launch time. * APAR IY53831 Symptoms: Use of symbolic link or mounted filesystem for the SCHEDLOG directory produces SCHEDLOG file that is 512 Bytes * APAR IY54456 Symptoms: Intermittent AWS11130001 Invalid COMAREA Messages When Using JSC * APAR IY55455 Symptoms: FDOPEN Fails in JOBMON because reached FOPEN_MAX # of streams * APAR IY55456 Symptoms: Jobmon.exe has handle leaks with TWS 8.1 * APAR IY56810 Symptoms: Datecalc 11-MAY-2004 PIC "dd-mm-yyyy" no longer works with '-' DATECALC:AWS11070008I bad date specification * APAR IY56877 Symptoms: Conman sbd [command] stays in ADD state. Schedule stays in ready state New APARs for Version 8.2 * APAR IY54578 Symptoms: JSC 1.2 GJS1052 & AWS22230003 Unable to create an ID/handle message is unclear * APAR IY55175 Symptoms: Mailman server memory corruption on W2K TWS Master New Internal Defects * Internal CMVC Defect 164016 Symptoms: From JSC, you are not allowed to define an NT user with numbers as first characters. You should be allowed to do so, instead. * Internal CMVC Defect 167318 Symptoms: Remove Copyright String from JOBMANRC * Internal CMVC Defect 167454 Symptoms: To complete APAR IY48076 * Internal CMVC Defect 168364 Symptoms: Installation TWS81 fix pack9 fails in a particular case. * Internal CMVC Defect 168574 Symptoms: performance problem running Jnextday * Internal CMVC Defect 169004 Symptoms: sbd does not work * Internal CMVC Defect 169242 Symptoms: kill of a job defined on fta win32 does not work * Internal CMVC Defect 170048 Symptoms: Jobstream with external DEP not correctly submitted * Internal CMVC Defect 170663 Symptoms: conman sbj coredump on Solaris and job stays on ADD * Internal CMVC Defect 171018 Symptoms: Database corruption after running the build tws utility * Internal CMVC Defect 171019 Symptoms: Batchman.exe abend after running two switchmgr commands. * Internal CMVC Defect 171021 Symptoms: Wrong start time when "conman sbd" and timezone used APARs in 8.1-Tivoli Workload Scheduler-Fix Pack 09 Version 8.1 * APAR IY44883 Symptoms: Tivoli Workload Scheduler patch Readme needs further NT patch requirements. * APAR IY45797 Symptoms: Cannot apply a Tivoli Workload Scheduler Fix Pack if installation directory is different from TWSUSER home directory. * APAR IY45818 Symptoms: Standard agent uses the CPU limit of its host. * APAR IY45913 Symptoms: Schedule on master stays ready even if it's jobs on FTA go SUCC. * APAR IY46139 Symptoms: Bogus opens dependency opens FTA#"" causes JOBMAN to abend on AIX. * APAR IY46140 Symptoms: BATCHMAN goes down when two users delete resources at the same time when two CLI or JSC. * APAR IY46358 Symptoms: Large numbers of "Description for Event ID 10006" * APAR IY46414 Symptoms: Cannot define a NT_USER beginning with a numeric char from composer * APAR IY46787 Symptoms: If opens dep is placed on a Jobstream when it is on EXEC and if after the Jobstream is cancelled, resources are not released. * APAR IY46792 Symptoms: WMAEUTIL core dump when framework roles are insufficient. * APAR IY46970 Symptoms: Composer create CMD does not use the UMASK setting. * APAR IY47381 Symptoms: After applying Fix Pack 7 - Conman SJ (SHOWJOBS) error if CPU is ignored. * APAR IY47866 Symptoms: When alternate plan is set, job dependencies are not shown. * APAR IY47889 Symptoms: JSC Cannot save Jobstream for an X-agent using a resource on the host CPU. * APAR IY48072 Symptoms: Schedules with RUNCYCLES containing workdays offsets and free days features do not run on the right day. * APAR IY48076 Symptoms: TWS 8.1 with FP06 on WIN-PLATFORM does not execute all the possible jobs against an X-agent. * APAR IY48308 Symptoms: Customize script creates STDLIST/TRACES directory for no reason. * APAR IY48325 Symptoms: Jobs with opens dependencies are launched even thought Batchman shows a "FN" for the file. * APAR IY48409 Symptoms: TWS 8.1 Directory permission fails security compliance. * APAR IY49003 Symptoms: X-agent hosted by $MASTER is shown as unlinked from JSC. * APAR IY49100 Symptoms: Validate and compiler allows jobs to be submitted for ignored FTA. * APAR IY49150 Symptoms: DBCS users GECOS field gets garbled in Tivoli Workload Scheduler job output. * APAR IY49379 Symptoms: R11XTR core dump when run REP11 with incorrect parameters. * APAR IY49420 Symptoms: Tivoli Workload Scheduler Plus Module 8.1 - DM Monitor - STDLIST space used does not work. * APAR IY49577 Symptoms: Stageman does not correctly carry forward resources for large symphony. * APAR IY49599 Symptoms: Job Streams containing an external dependency are not correctly submitted. * APAR IY49672 Symptoms: Failed Tivoli Workload Scheduler job create JOBLOG. * APAR IY49876 Symptoms: JOBINFO not working correct in 8.1- RSTRT_FLAG, JOB_NAME, RE_TYPE. * APAR IY50126 Symptoms: Plus Module fails to install on Solaris 2.9. * APAR IY50193 Symptoms: Jobs are randomly kept in ready state when submitted. * APAR IY50614 Symptoms: XRXTRCT hangs when schedule contains 127 characters comment. * APAR IY50678 Symptoms: Tivoli Workload Scheduler 8.1 receiving DR Watson error when LOOKUPACCOUNTNAME fails. * APAR IY50680 Symptoms: Tivoli Workload Scheduler Jobs remain in INTRO+ STATE on an X-agent. * APAR IY50725 Symptoms: Unable to submit jobs ADHOC when user has tight security access. * APAR IY50814 Symptoms: INVALIDE handle in JOBMON code. * APAR IY51097 Symptoms: Schedulr command does not select schedules due to the order. APARs in Tivoli Workload Scheduler-FP09 for Version 8.1 * APAR IY48660 Symptoms: The Tivoli Workload Scheduler "TRAPJOBABEND" trap has a carriage return coded. * APAR IY50123 Symptoms: Unable to submit JOBSTREAM defined for a CPU class in 8.2. * APAR IY50833 Symptoms: Tivoli Workload Scheduler Module FP1 fails to install on managed node. Internal Defects in 8.1-Tivoli Workload Scheduler-FP09 for Version 8.1 * Internal CMVC Defect 165241 Symptoms: TWS PLUS: Job cancel event not sent to TEC. * Internal CMVC Defect 165444 Symptoms: TWS PLUS 8.2: event 111: wrong mapping with maestro.fmt file. * Internal CMVC Defect 166079 Symptoms: TWS PLUS: end of TWSPLUSinstallafter script after download of dependent files to managed nodes. * Internal CMVC Defect 166110 Symptoms: TWS PLUS 8.2: event 111 causes a parsing error on TEC server. * Internal CMVC Defect 168024 Symptoms: TWS PLUS: DM Monitor Disk Space used for stdlist fails against endpoints because du.exe is not downloaded to them. * Internal CMVC Defect 168083 Symptoms: E2E: Re-use of deleted dependencies position. APARs in 8.1-Tivoli Workload Scheduler-FP08 for Version 8.1 * APAR IY40910 Symptoms: Cannot run ant Tivoli tasks on some TMR EPS after installing TWSPLUS 8.1. * APAR IY41774 Symptoms: Conman shut can cause bad mailbox record to be written. * APAR IY43302 Symptoms: JOBDSTDL script returned error 0403-027 the parameter list is too long. * APAR IY44845 Symptoms: AWS2201003E too many jobs for BATCHMAN since APAR IY38717. * APAR IY46202 Symptoms: The variable $UNISON_HOST is set every time to the MASTER WKS. * APAR IY46982 Symptoms: Japanese characters get garbles in STDLIST JOBLOG. * APAR IY46724 Symptoms: Confirm SUCC for Job via JSC not working for FTA's * APAR IY45955 Symptoms: Parent of switched domain manager makes error in computing routing tables. * APAR IY47140 Symptoms: Jobs stays on ready when submitting from master in TZ on different date. * APAR IY46411 Symptoms: REP11 reports incorrect planned date. * APAR IY47563 Symptoms: Symphony Decompression problem - follow to IY36118 * APAR IY46100 Symptoms: Cannot define non local resources dependencies on JSC 1.2. * APAR IY44864 Symptoms: Filed in return code structure for ACK to a NETMAN request are not filled with correct values. * APAR IY42607 Symptoms: NETMAN (and other processes) handle leak. * APAR IY41863 Symptoms: Composer verify does not catch hard return codes in dependencies. * APAR IY47897 Symptoms: TWS JOB is reported as Suspended when Until time is crossed even if it gets completed Internal Defects in 8.1-Tivoli Workload Scheduler-FP08 for Version 8.1 * Internal CMVC Defect 159232 Symptoms: Unable to Launch JSConsole from Plus Job * Internal CMVC Defect 159341 Symptoms: TME Logfile adapter configuration fails on Win2k * Internal CMVC Defect 155991 Symptoms: datecalc on AIX reject names that includes underscore APARs in 8.1-Tivoli Workload Scheduler-FP07 for Version 8.1 * APAR IY34233 Symptoms: EVTSIZE on INTERCOM.MSG is reset to default at JNEXTDAY. * APAR IY35020 Symptoms: JSC ADHOC submission of jobstreams containing opens and ends with "unable to submit". * APAR IY38156 Symptoms: JOBSTDL and MORESTDL commands do not produce any output for any user other than the Maestro user. * APAR IY38322 Symptoms: Partial entry in workstation option on the JSC saves * APAR IY38884 Symptoms: TWS 8.1 - Event 107 not generated. * APAR IY39073 Symptoms: Conman SC does not show the L Flag for XA hosted by $MASTER. * APAR IY40719 Symptoms: 'VERSION -A' Command does not return correct patch information. * APAR IY40825 Symptoms: Recovery Job inheriting "interactive" job definition from parent * APAR IY41035 Symptoms: SCHED with name of 16 characters and JOBNAME of 12 characters in a CPUCLASS does not work. * APAR IY41341 Symptoms: Performance issues for TWS with the autotrace features. * APAR IY41433 Symptoms: Tivoli Workload Scheduler cannot create calendars past year 2038. * APAR IY41449 Symptoms: /TWSHOME/CATALOG/POSIX use a link with ABSOLUT path to /TWSHOME/CATALOG/C * APAR IY41485 Symptoms: WS distributed is to send different instance IDS for all the jobs except for jobs rerun. * APAR IY41586 Symptoms: Conman SS (Show schedules) does not show correct status. * APAR IY41868 Symptoms: Every job w/file dependency can run too quickly * APAR IY42465 Symptoms: Jobtable is created with wrong run number after recovery * APAR IY42468 Symptoms: Some characters are garbled when view job STDLIST, due to corrupted packets sent by SCRIBNER, related to IY38683 * APAR IY42731 Symptoms: Kill corrupting JOBTABLE. * APAR IY42797 Symptoms: Batchman abended with AWS1000301E experienced error 3.0 reading courier in ../../SRC/JOBMAN/COURIER.C:READ_COURIER * APAR IY42981 Symptoms: Validate error on opens dependency. * APAR IY43246 Symptoms: Composer create jobs-format incorrect in output file. * APAR IY43352 Symptoms: Optimization needed for locking mechanism on Jobtable. * APAR IY43608 Symptoms: Conman "SJ +STATE=FENCE" Does not properly select the jobs in fence state * APAR IY43491 Symptoms: JSC LINK/UNLINK status wrong for FTA when host is unlinked. * APAR IY44102 Symptoms: Stageman tries to use a record number (32768) in Symphony file * APAR IY44297 Symptoms: EVTSIZE -show command output * APAR IY44471 Symptoms: JSConsole does not update Job status correctly if the job status is changed from CLI Internal Defects in 8.1-Tivoli Workload Scheduler-FP07 for Version 8.1 * Internal CMVC Defect 156824.1 Symptoms: Mailman stops to work if cache set to yes APARs in 8.1-Tivoli Workload Scheduler-U487473 for Version 8.1 * APAR IY32174 Symptoms: Composer stops with error if a recovery job is missing. * APAR IY32257 Symptoms: Number of successful jobs field is incorrect for carried forward JOBSTREAM. * APAR IY32436 Symptoms: The state for jobs running at JNEXTDAY is not updated correctly. This results in loss of jobs at JNEXTDAY. * APAR IY32693 Symptoms: TWS/NETVIEW: The positional variables $12 for the trap 101 UTTRAJOBABEND is displayed in HEX instead of in DECIMAL. * APAR IY35131 Symptoms: Maestro setup program does not handle null user and traps. * APAR IY35151 Symptoms: Numerous directory permissions are word-writable, which is a security flow. * APAR IY35182 Symptoms: Follows on a schedule at schedule level does not hold after JNEXTDAY. * APAR IY35486 Symptoms: Improve error reporting of NT/W2K domain errors. * APAR IY36118 Symptoms: FTAS do not link to master after JNEXTDAY, because of corruption in the compressed sinfonia file from master. * APAR IY36608 Symptoms: JOBMON stops responding on TWS 8.1 * APAR IY36997 Symptoms: Via command line is impossible to create schedules that contain jobs with different workstation classes - this break JNEXTDAY. * APAR IY37705 Symptoms: CPU LIMIT=0 not honored on XA * APAR IY37706 Symptoms: TWS DB/PLAN audit files are writable by every user. * APAR IY37999 Symptoms: Complier fails to add a dummy job in fail state during JNEXTDAY. * APAR IY38037 Symptoms: Unable to create a Job that logs on as a user that has greater than 8 characters. * APAR IY38040 Symptoms: Incorrect error message **ERROR**(23) AWS22080023 JOB XXXXXX not found in job master instead of access denied error. * APAR IY38216 Symptoms: When confirming a job, the wrong job is being confirmed "SUCC" in JSC 1.2 * APAR IY38717 Symptoms: Batchman abends on master due to JOBTABLE exceeds 32000 * APAR IY38726 Symptoms: Cannot browse JOBLOG on DYNIX FTA via JSC or command line after applying 8-1-TWS-0006 * APAR IY38732 Symptoms: On Linux TWS connector error to submit job with PARMS * APAR IY38795 Symptoms: Batchman crashes when crossing the barrier of 65535 records * APAR IY38683 Symptoms: Some characters are garbled when viewing job STDLIST files * APAR IY38798 Symptoms: FILEAID does not display correctly records with RECNUM > 65535 * APAR IY39396 Symptoms: Conman SJ gives bad output after EFIX for IY38795 * APAR IY39399 Symptoms: Conman SWITCHMGR does not work on WIN2K when mailman server is used * APAR IY40463 Symptoms: The "DATACALC SCHEDDATE" command is no longer reporting the original production date on carryforward schedules * APAR IY40838 Symptoms: Better error reporting needed when FPS since 8.1-TWS-0006 installation fail (PSAPI.LL MISSING) * APAR IY41442 Symptoms: Event 101-119 missing parameter * APAR IY41632 Symptoms: New parameter needed into TEC events * APAR IY41650 Symptoms: Fix Pack 5 does not set the LIBPATH variable for the new location of LIBATRC.A * APAR IY41955 Symptoms: silent install of Tivoli Workload Scheduler patches causes problems with dialog. * APAR IY41986 Symptoms: Tivoli Workload Scheduler performance is adversely affected when more than 65535 jobs. * APAR IY42018 Symptoms: Kill command can corrupt a message queue Internal Defects in 8.1-Tivoli Workload Scheduler-U487473 for Version 8.1 * Internal CMVC Defect 153621 Symptoms: Enhancement request for the at/until time * Internal CMVC Defect 153685 Symptoms: Enhancement request for no check and wait options for submit command * Internal CMVC Defect 155876 Symptoms: Output of "add Sfinal" is invalid APARs in 8.1-Tivoli Workload Scheduler-U485968 for Version 8.1 * APAR IY37113 Symptoms: Tivoli Workload Scheduler 8.1 autotrace fills 64-BIT HP-UX SYSLOG * APAR IY36781 Symptoms: TIVOLI_JOB_DATE variable is returning incorrect output * APAR IY36336 Symptoms: Unexpanded database issues W/TWS 8.1 including X-agent job numbers in CONMAN and DELDEP command * APAR IY36192 Symptoms: JOBMON.EXE intermittent applications error popup * APAR IY36120 Symptoms: Cannot submit JOBSTREAM with an opens dependency when the filename contains a parameter and is bigger than 28 characters * APAR IY35986 Symptoms: CONMAN ALTPASS CMD does not work for WINNT SA * APAR IY35978 Symptoms: NETMAN.EXE intermittent application error popup * APAR IY35866 Symptoms: Tivoli Workload Scheduler cannot handle long path in UNIX ($PATH VARIABLE) Tivoli Workload Scheduler commands core dump * APAR IY34857 Symptoms: Cancelled schedule carried forward if using non expanded databases and FLAGGD as carryforward * APAR IY34732 Symptoms: Event 106 in the EVENT.LOG returns a date of 1970 * APAR IY34278 Symptoms: FIXPACK 3 Overwrite /delete additional group and user settings APARs in 8.1-Tivoli Workload Scheduler-U485968 for Version 6.1 or 7.0 * APAR IY36966 Symptoms: Report 10B lacks start time for a job stream which runs at 0:00 * APAR IY35967 Symptoms: "no time zone stamp in STDLIST on TWS 7.0 and 8.1 when LANGVARIABLES is set to ""C.""" * APAR IY35874 Symptoms: JSLFILE string gets corrupted when submitting a SAP job from JSC * APAR IY35485 Symptoms: If a schedule has only 1 job which is then canceled pending before job launches then the schedule status is always ready * APAR IY35425 Symptoms: 25+ character schedule name make GCONMAN abend * APAR IY34920 Symptoms: MAKESEC fails to compile security file * APAR IY32240 Symptoms: Continuation character not correctly placed on except line of Tivoli Workload Scheduler schedule/job stream causing JNEXTDAY abend * APAR IY31896 Symptoms: It is possible to cancel jobs in the USERJOBS by JSC Internal Defects in 8.1-Tivoli Workload Scheduler-U485968 * Internal CMVC Defect 151506 Symptoms: Variable TIVOLI_JOB_DATE doesn't report the origianl value anymore. * Internal CMVC Defect 150249 Symptoms: Reasoning - Uninitialized variable - TBSM (360-361) APARs in 8.1-Tivoli Workload Scheduler-0006 for Version 8.1 * APAR IY32993 Symptoms: Cannot set alternate plan from JSC when Tivoli Workload Scheduler engine is installed on NFS file system * APAR IY30687 Symptoms: Cannot perform a kill CMD on child-process by Tivoli Workload Scheduler (W2K) * APAR IY31441 Symptoms: Limit 0 not honored on Tivoli Workload Scheduler 8.1 UNIX CPUS after MSG, SYMPHONY, SINFONIA, JOBTABLE removed. * APAR IY31717 Symptoms: AWS22080105 Error received with validate, add or replace of job * APAR IY32464 Symptoms: After Tivoli Workload Scheduler 8.1, patch 0001, C:\WIN32APP\MAESTRO\SETUP\SETUP.EXE no longer works * APAR IY32928 Symptoms: Jobs fail on WIN2K W/V8.1 when run by active directory users * APAR IY33025 Symptoms: Tivoli Workload Scheduler 8.1 composer replace prompting for confirmation * APAR IY33568 Symptoms: Jobs received logon error on Windows NT * APAR IY33801 Symptoms: Tivoli Workload Scheduler process hangs when "MM CACHE MAILBOX=YES" and MAILBOX.MSG reaches it's maximum size * APAR IY34126 Symptoms: Job Stream SUCC when job abend - job stream should abend. * APAR IY34282 Symptoms: Tivoli Workload Scheduler jobs status is incorrect in TBSM console * APAR IY34445 Symptoms: Mailman hangs * Defect 149741 Switchmgr did not work properly when Cache option is Yes. * APAR IY35086 Symptoms: Composer display calendars core dump on calendar that has more than 34 days and MAESTROCOLUMNS=346 or greater set * APAR IY32919: Symptoms: Prompt events garbled for JAP LANG APARs in 8.1-Tivoli Workload Scheduler-0006 for Version 6.1 or 7.0 * APAR IY29435 Symptoms: On SOLARIS platforms USERNAMES > 8 characters in length are truncated * APAR IY29801 Symptoms: Follow DEP is not resolved for a FTA job which is a SUCCESSOR of a job stream containing jobs defined on different CPUS * APAR IY31085 Symptoms: Days offset is not logged in STD list when adding a dependency * APAR IY31373 Symptoms: Report 10B lacks start time for reruns at 00:00 * APAR IY31726 Symptoms: Report 09D displays repeat range where none exists * APAR IY31732 Symptoms: Recovery job inherits the original dependencies of original job * APAR IY31898 Symptoms: The writer create defunct process after JNEXTDAY * APAR IY32176 Symptoms: CRMFP1 is not in CPUTABLE received multiple time in IN MAESTRO STDLIST * APAR IY32595 Symptoms: After 7.0-TWS-0140 opens file DEPS are sometimes solved on the MASTER for FY get lost from the FTA to the master * APAR IY35149 Symptoms: JOBLNCH.EXE cannot find PSAPI.DLL after installing 7.0-TWS-0150 Internal Defects in 8.1-Tivoli Workload Scheduler-0006 * Internal CMVC Defect 116911 Symptoms: evtsize to report the current size of any .msg file * Internal CMVC Defect 139745 Symptoms: UserĘs ulimit not respected with >2GB files * Internal CMVC Defect 141626 Symptoms: Class::PopulateTZtable abends if no Symphony is found * Internal CMVC Defect 142351 Symptoms: Abend during VAfill_errhandle * Internal CMVC Defect 143262 Symptoms: Composer "add/modify cpu" problems * Internal CMVC Defect 149340 Symptoms: oserv failure when trying to display AllJobDefinition on Linux * Internal CMVC Defect 149137 Symptoms: Uninitialised memory or empty msg written into msg box * Internal CMVC Defect 148956 Symptoms: TWS for z/OS APAR PQ65794 * Internal CMVC Defect 148971 Symptoms: TWS for z/OS APAR PQ65556 * Internal CMVC Defect 149008 Symptoms: TWS for z/OS APAR PQ65694 APARs in 8.1-Tivoli Workload Scheduler-0004 for Version 8.1 * APAR IY31645 Symptoms: Cancel job command from JSC must be allowed in an ENDTOEND * APAR IY31184 Symptoms: Composer comments greater then 127 characters cause the error of SCHEDULR parser error and corrupts the DB * APAR IY31181 Symptoms: BM check file entries in LOCALOPTS are being doubled when the checking for file is done * APAR IY31137 Symptoms: SCHEDULR abends when 127TH characters in schedule dependency is the # SYMBOL * APAR IY30857 Symptoms: AWS11250006I Unable to open output file received when using the composer create command as a user who is not the MAESTRO user * APAR IY29572 Symptoms: Error when invoking the MORESTDL and JOBSTDL SCRIPTS-AWS2234000 * APAR IY29459 Symptoms: DATECALC show the system-date when it is launched by Tivoli Workload Scheduler * APAR IY29284 Symptoms: Composer errors follows dependencies when the job used for follows is prefix of another job. * APAR IY29117 Symptoms: JSC - ADHOC prompt generates OSERV message on answer APARs in 8.1-Tivoli Workload Scheduler-0004 for Version 6.1 or 7.0 * APAR IY31594 Symptoms: JOBMON abending on WINNT FTA's * APAR IY31528 Symptoms: JSC - "CALL UNISON" message appears when view dependencies for job in plan when you click OK. * APAR IY31434 Symptoms: Full status FTA jobs do not get RD records properly if opens is checked on MASTER on MASTER CPU in the same domain * APAR IY30162 Symptoms: DR. WATSON error during high job causes system crash and requires reboot on . * APAR IY29877 Symptoms: Tivoli Workload Scheduler processes creating NT handle leaks while running scripts utilizing mapped drives in a NOVELL user administrator environment * APAR IY29842 Symptoms: Submitted job info lost during STAGEMAN step of JNEXTDAY on MDM. * APAR IY29249 Symptoms: Job events may get lost when switching the backup master * APAR IY28374 Symptoms: MAGENT dies when CONMAN kill used on job in USERJOBS SCHED on FTA * APAR IY27514 Symptoms: Incorrect "SWITCHED" message at the end of startup command output * APAR IY27512 Symptoms: X-agent jobs stuck in ABEND+ OR SUCC+ state if carryforward * APAR IY20201 Symptoms: Cannot change password within JSC SCHEDULAR controller information do not show up in STDLIST * APAR IY16098 Symptoms: LOGMAN writes negative numbers for jobs running on XAS Internal Defects in 8.1-Tivoli Workload Scheduler-0004 * Internal CMVC Defect 140909 Symptoms: TWSPlus: TWSPlus fix pack 2 fails on Solaris and Win2000 * Internal CMVC Defect 140818 Symptoms: TBSM Integration: used cp command instead of copy command into * Internal CMVC Defect 140684 Symptoms: TBSM Integration: modified the design so that the number of objects sent into each packet during the build discovery is customizable. * Internal CMVC Defect 140575 Symptoms: TBSM Integration: memory leaks problems * Internal CMVC Defect 140350 Symptoms: E2E limitation not performed in TWS Connector * Internal CMVC Defect 138479 Symptoms: Dependency on full status WS from job different domain higher in domain hierarchy is not resolved. Job stays in ready. * Internal CMVC Defect 137651 Symptoms: EBCDIC Euro code pages does not work * Internal CMVC Defect 137569 Symptoms: Tivoli Workload Scheduler for z/OS APAR PQ60253 * Internal CMVC Defect 136036 Symptoms: Opens dependency mechanism redesign * Internal CMVC Defect 135344 Symptoms: It's not possible carry forwarding two jobs in USERJOBS with same name * Internal CMVC Defect 135188 Symptoms: TWS Connector fails submit jobstreams on Linux * Internal CMVC Defect 134434 Symptoms: 8.1-TWS-0002 (build 20020305) composer error on NT Problems Fixed in 8.1-TWS-0002: * APAR IY26157 Symptoms: Schedules with executing jobs are not carry forwarded even if "CARRYFORWARD=ALL" is set into the GLOBALOPTS. * APAR IY27157 Symptoms: Jobs follows dependency modified by JSC when Jobstreams properties window is opened * APAR IY27812 Symptoms: TWSPLUS Module 8.1 - SETUP TEC event server task errors * APAR IY27814 Symptoms: TWSPLUS Module 8.1 - SETUP TEC event server task errors (PERL) * APAR IY28002 Symptoms: Follows and opens dependency causes AWS22010005E * APAR IY28084 Symptoms: "AWS20760015 Cannot open database when trying to create PARM on a FTA * APAR IY28096 Symptoms: Installation failure of TWS8.1 Plus Module on AIX4.3.3 platform * APAR IY28803 Symptoms: Tivoli Workload Scheduler 8.1, patch 0001, job with recovery option of continue crashes BATCHMAN * APAR IY14748 Symptoms: CPU'S sharing server ID are affected by one problem CPU * APAR IY17613 Symptoms: Composer add report a wrong job indication in case of error * APAR IY21145 Symptoms: Resources get reset at JNEXTDAY for USERJOBS * APAR IY21459 Symptoms: 2 SCHEDS with same job with same file DEP. File DEP not being reset to no after 1st DEP is answered * APAR IY22146 Symptoms: CONMAN SHOWJOB with qualifier prefix '~' (TILDE) does not return proper information * APAR IY24661 Symptoms: CONMAN SETSYM reverts back to current symphony file after a few minutes of idle time * APAR IY24831 Symptoms: Tivoli Workload Scheduler is logging everything to SYSLOGD at the LOG_ERR level * APAR IY25303 Symptoms: X-agent jobstream gets modified as MPE JOBSTREAM. * APAR IY25417 Symptoms: Cannot create PARM using double quote (") character from COMMAN * APAR IY25421 Symptoms: After submitting a ADHOC schedule, it stays on hold until next CONMAN command us issued * APAR IY25875 Symptoms: FD_OPEN receives null file DESSCRIPTOR return from NT OS API * APAR IY26115 Symptoms: The JCL attribute of job object in security file does not work * APAR IY26464 Symptoms: MAESTROLPLINES has no effect to the output of report7 * APAR IY26544 Symptoms: ADHOC submit and rerun cause error "ATTEMPTING TO WRITE NIL" on RECNUM 32768 * APAR IY26704 Symptoms: The database and plan audit logs are being created using the UMAASK of user that first writes to audit files rather than Tivoli Workload Scheduler use * APAR IY26853 Symptoms: Error 6 reported in application log when shutting down TOKENSRV * APAR IY27438 Symptoms: Maestro service reports an invalid state * APAR IY27477 Symptoms: BATCHMAN abends when writing to EVENT.LOG * APAR IY27487 Symptoms: Temporary files SXX.XX created in the root DIR not removed * APAR IY27494 Symptoms: 'Composer validate' requires read/write access by Tivoli Workload Scheduler user * APAR IY27578 Symptoms: Ready job problem, domain manager is not aware of partial resolution of dependencies and does not release jobs * APAR IY27579 Symptoms: JOBMAN:+ ERROR receiving data MONITOR.C:323 ERROR = NO ERROR * APAR IY27772 Symptoms: RMSTDLIST script sometimes removes UNWANTED(NEW) STDLIST * APAR IY28254 Symptoms: Jobs DB gets corrupted on SOLARIS after composer build when LC_ALL locale variable is UNSET * APAR IY28291 Symptoms: JNEXTDAY and reports 7, 8, 9, 10, and AND XREF COREDUMP ON 64-BIT AIX running TWS 7.0 * Internal CMVC Defect 126497 Symptoms: Interwork DEP not working for ADHOC schedules connector * Internal CMVC Defect 128161 Symptoms: Sched does not start with OPENS file for a standard agent * Internal CMVC Defect 131173 Symptoms: APAR IY27174 : cannot browse job log from alternate plan view * Internal CMVC Defect 131174 Symptoms: IY27157 jobs follow DEP. Changed by JSC when JS PROPERT.IS OPEN * Internal CMVC Defect 131547 Symptoms: Error message during Jnextday on NT platform * Internal CMVC Defect 131753 Symptoms: TWSPlus: common-tec-install.sh contains "let" command that is not supported by bourne shell * Internal CMVC Defect 132433 Symptoms: TWSPlus: wrong variable name into config_nontme_logfile.sh * Internal CMVC Defect 134159 Symptoms: 8.1-TWS-0002 (build 20020305) Composer modify cpu problem * Internal CMVC Defect 134659 Symptoms: 8.1-TWSPLUS-0002: provide script for unistalling of fixpack * Internal CMVC Defect 134665 Symptoms: 8.1-TWSPLUS-0002: event 11 is copyied into BmEvents.conf instead of number 111 * Internal CMVC Defect 134667 Symptoms: 8.1-TWSPLUS-0002: EventGroup TWSPlus filters all TWS events; * Internal CMVC Defect 134694 Symptoms: 8.1-TWSPLUS-0002: Event 119 is mapped by TEC in a wrong manner * Internal CMVC Defect 134788 Symptoms: Configuration Adapter 31 TME on Manage Node failed. APARs in 8.1-Tivoli Workload Scheduler-0001 * APAR IY04058 Symptoms: When using parameters, if the number of characters in a DOCOMMAND exceeds 256 characters, get error 2210.16 upon PARM expand * APAR IY05018 Symptoms: If two users access the database at the same time, the database is corrupted * APAR IY09979 Symptoms: An XA hosted by $MASTER is not switched to the new master * APAR IY10837 Symptoms: Test qualifiers in open statement on UNIX REMOTE XA does not work * APAR IY11079 Symptoms: Master not receiving a SUCC when jobs run near the JNEXTDAY * APAR IY14997 Symptoms: Script utilizing visual basic/C++ encounter runtime errors * APAR IY15224 Symptoms: CONMAN SJ returns "NO QUALIFIED ENTRIES 2202.72 "on a SOLARIS * APAR IY15577 Symptoms: SCHEDULES/JOBNAMES of 8 characters truncated in MAESTROHOME/ATJOBS * APAR IY16682 Symptoms: $THISCPU in security file is ignored for schedules * APAR IY17029 Symptoms: Composer replace reports warning AWS11250006I and AWS11040004I * APAR IY17189 Symptoms: Compiler reports a warning message "NO HOST SPECIFIED" for SA * APAR IY17288 Symptoms: On job completion a defunct process is spawned on UNIX * APAR IY17667 Symptoms: CONSLOG file cannot be automatically deleted on FTAS * APAR IY17798 Symptoms: Warning message get truncated for Composer command * APAR IY18185 Symptoms: Japanese message of TWS becomes garbled * APAR IY18517 Symptoms: Error on component when using symbolic LINKS(DEFECT 90634) * APAR IY18552 Symptoms: CONMAN "SUBMIT J=#" submits all defined jobs for specified CPU * APAR IY19805 Symptoms: Job number with 5 digits gets truncated to 4 digits in the REPTR -POST -DETAIL. Last digit of job 3 gets truncated * APAR IY20215 Symptoms: CONMAN confirm command does not allow confirmation of repeating jobs. * APAR IY20296 Symptoms: Reports XREF does only work with the owner of script. * APAR IY20778 Symptoms: A timing issue during JNEXTDAY cause MAILMAN on DM to not close * APAR IY20847 Symptoms: CONMAN SR @#@:DEPS does not list jobs in status exec * APAR IY20954 Symptoms: BATCHMAN ABENDS when an until (DEADLINE) time on job is reached * APAR IY20990 Symptoms: The CMD PARMS does not work when the security-file use $THISCPU and the CPU-NAME is larger than 8 characters * APAR IY21441 Symptoms: File check messages for a FTA get sent to all 7.0 FTA'S thru master causes MAILBOX.MSG file to get very large * APAR IY21668 Symptoms: Follows and files dependency not correct. * APAR IY21729 Symptoms: Schedule not releasing resource upon completion * APAR IY21988 Symptoms: JCL keyword in job object DEF of security file prevents the reading & applying of any other job OBJECTDEF for the same user * APAR IY22565 Symptoms: BATCHMAN abends with SIGSEGV when deleting a needs dependency * APAR IY22566 Symptoms: The Conman stop CMD return no ERR-OUTPUT in the JNEXTDAY script * APAR IY23180 Symptoms: Jobs abend with BATCHMAN reporting J0 as job number * APAR IY23198 Symptoms: NT-JOB create some 102 event entries in the EVENT.LOG (FAIL) * APAR IY24317 Symptoms: Composer 1.22 is core dumping when exporting job definitions * APAR IY26227 Symptoms: TWS 8.1 SWITCHMGR does not complete successfully * APAR IY26392 Symptoms: Running customize with -UPDATE option does not update NETMAN * APAR IY26396 Symptoms: COMAN output Japanese character garbled * APAR IY19916 Symptoms: NT USER password not being changes correctly. See closed APAR IY17119 * APAR IY20621 Symptoms: Composer build corrupts databases causing 1/1/1970 date to appear in "last update" field of JSCONSOLE. * APAR IY22295 Symptoms: Job stream W/2 JOBS..INTER DEP and another job W/REQ for inter DEP,1ST job wait, , 2ND INTER DEP INTRODUCED..CREATES ADD'TL RECS * APAR IY22827 Symptoms: JSC is using ADDDEP command to change priority * APAR IY25833 Symptoms: AIX JSS/CONN/ENG does not allow job streams to be saved correctly * Internal CMVC Defect 124617 Symptoms: Error msg for adding job is not correct and confusing * Internal CMVC Defect 125426 Symptoms: Incorrect TWS instructions allowed on fault tolerant agents * Internal CMVC Defect 125634.1 Symptoms: Composer: problem with "add Sfinal" in Japanese locale * Internal CMVC Defect 127601 Symptoms: Japanese security messages become garbage * Internal CMVC Defect 128160 Symptoms: Installation of Plus Module fails if TEC on a different MN * Internal CMVC Defect 128228 Symptoms: Configure adapter fails on endpoint * Internal CMVC Defect 128256 Symptoms: After patch , RMSTDLIST command does not work * Internal CMVC Defect 128424 Symptoms: Configure adapter fails searching for the Format File Pathname This section includes the following topics: * 1a.iv, "Architecture(s)" * 1a.v, "Dependencies" * 1a.vi, "Files Replaced by this Patch" * 1a.vii, "Patches Superseded by this Patch" * 1a.viii, "Patch Contents" * 1a.ix, "Applying the Fix Pack" * "UNIX" * "Windows" * "Tivoli Workload Scheduler Plus Module" * "Tivoli Workload Scheduler Connector" 1a.iv) Architecture(s) AIX, HPUX, SOLARIS, WIN32 (Intel), LINUX (Intel, S390), IRIX, OSF, DYNIX 1a.v) Dependencies IBM Tivoli Workload Scheduler Version 8.1 1a.vi) Files Replaced by this Patch All Tivoli Workload Scheduler files (complete update) 1a.vii) Patches Superseded by this Patch * Patch: 8.1 - Fix Pack 1 PTF Number: U481302 Component: Tivoli Workload Scheduler Version 8.1 * PTF Number: U481303 Component: TWS Connector Version 8.1 * Patch: 8.1 - Fix Pack 2 PTF Number: U482258 Component: Tivoli Workload Scheduler Version 8.1 and Tivoli Workload Scheduler Connector Version 8.1 * Patch: 8.1 - Fix Pack 3 PTF Number: U483828 Component: Tivoli Workload Scheduler Version 8.1 and Tivoli Workload Scheduler Connector Version 8.1 * Patch: 8.1 - Fix Pack 4 PTF Number: U484623 Component: Tivoli Workload Scheduler Version 8.1 and Tivoli Workload Scheduler Connector Version 8.1 * Patch: 8.1 - Fix Pack 5 PTF Number: U485968 Component: Tivoli Workload Scheduler Version 8.1 and Tivoli Workload Scheduler Connector Version 8.1 * Patch: 8.1 - Fix Pack 6 PTF Number: U487473 Component: Tivoli Workload Scheduler Version 8.1 and Tivoli Workload Scheduler Connector Version 8.1 * Patch: 8.1 - Fix Pack 7 PTF Number: U489588 Component: Tivoli Workload Scheduler Version 8.1 and Tivoli Workload Scheduler Connector Version 8.1 * Patch: 8.1 - Fix Pack 8 PTF Number: U495889 Component: Tivoli Workload Scheduler Version 8.1 and Tivoli Workload Scheduler Connector Version 8.1 * Patch: 8.1 - Fix Pack 9 PTF Number: U496402 Component: Tivoli Workload Scheduler Version 8.1 and Tivoli Workload Scheduler Connector Version 8.1 * Patch: 8.1 - Fix pack 10 PTF Number: U400019 Component: Tivoli Workload Scheduler Version 8.1 and Tivoli Workload Scheduler Connector Version 8.1 * Patch: 8.1 - Fix pack 11 PTF Number: U498734 Component: Tivoli Workload Scheduler Version 8.1 and Tivoli Workload Scheduler Connector Version 8.1 1a.viii) Patch Contents Patch Contents in CD * README.U800231 (this file) * 8.1.0-TIV-TWS-FP0012.VSR * AIX * MAESTRO.TAR * HPUX * MAESTRO.TAR * SOLARIS * MAESTRO.TAR * LINUX * I386 * MAESTRO.TAR * S390 * MAESTRO.TAR * IRIX * MAESTRO.TAR * OSF * MAESTRO.TAR * DYNIX: * MAESTRO.TAR * I386NT: * MAESTRO * Setup.exe * Other installation files * TWSPLUS * MAESTRO.TAR Note: If you download the patch from FTP, there is no MAESTRO.TAR but a number of unpacked installation files. * U1_TWS.image 1a.ix) Applying the Fix Pack Notes: 1. Always verify that you have a viable backup before installing any software. 2. Also read "Additional Installation Instructions". 3. Make sure to back up the TWSHOME/Tbsm/TbsmAdapter/adapter.config configuration file. It will be replaced during the installation of this Fix Pack. 4. You should start the installation of this Fix Pack when no high workload of running Tivoli Workload Scheduler jobs is present on your system. You will have to wait for all jobs to complete in order to have all the Tivoli Workload Scheduler processes down (see below). UNIX The CD contains a directory for each platform with a TAR file that is specific for each operating system. Follow these steps to apply the fix pack: 1. Unlink the host on which you are installing the fix pack from the Tivoli Workload Scheduler network and shutdown Tivoli Workload Scheduler. Use the following command: conman "unlink @; noask" conman "shut; wait" 2. Wait until all jobman processes are down. 3. Log on as root user. 4. Make sure ALL the Tivoli Workload Scheduler processes are stopped: a. Run ps -ef to obtain a list of running processes. b. Run kill term pid for every running Tivoli Workload Scheduler process. c. If this does not work, run kill -9 pid. If you have difficulties or doubts about which processes are started by Tivoli Workload Scheduler, look for the process names in the TWSHOME/version/version.info file. 5. Download the operating system-specific MAESTRO.TAR file to the Tivoli Workload Scheduler home directory and untar it with the following command: tar xvf MAESTRO.TAR This will create the following two files: * maestro.tar.Z * customize 6. You may have to set the execute bit on the customize script as follows: chmod 755 customize 7. Run the customize script with the -update option as follows: customize -update -uname Windows While installing the fix pack on Windows 2000, you are recommended to keep Services snap-in and all other handles to the Tivoli Workload Scheduler services closed (see Microsoft(R) Windows bug Q287516 for more information). To apply the fix pack on Windows NT(R) and on Windows 2000 follow these steps: 1. Unlink the host on which you are installing the patch from the Tivoli Workload Scheduler network and shutdown Tivoli Workload Scheduler. Use the following commands: conman "unlink@; noask" conman "stop; wait" shutdown 2. Wait until the jobmon and joblnch processes are down. 3. Log on as Administrator. 4. Download the I386NT directory from the fix pack CD onto your system. 5. Make sure ALL the Tivoli Workload Scheduler processes are stopped: a. Run TWSHOME\unsupported\listproc to obtain a list of running processes. b. Run TWSHOME\unsupported\killproc pid for every running Tivoli Workload Scheduler process. If you have difficulties or doubts about which processes are started by Tivoli Workload Scheduler, look for the process names in the TWSHOME\version\maestro.info file. 6. Run setup.exe to install the fix pack and follow the instructions on the screen. When the prompt for the user name appears, type the name of the TWS user for which you are installing the fix pack. Tivoli Workload Scheduler Plus Module To successfully apply the fix pack to the Plus Module, you must have the install_product and super authorization roles. Follow these steps: * Using the Tivoli desktop, select the Install -> Install Patch... option from the Desktop menu to display the Install Patch dialog. * Press the Select Media... button to display the File Browser dialog. * Enter the path to the directory containing the patch in the Path Name: field. * Press the Set Media & Close button to return to the Install Patch dialog. The patch install list now contains the name of the patch. Select the patch by clicking on it. * Select the clients where you want to install this patch. * Press the Install button to install the patch. Tivoli Workload Scheduler Connector It is required that both the Tivoli Workload Scheduler master workstation and the connector be at the same level. Therefore, when you install this fix pack on the connector, make sure that you also install the fix pack for the Tivoli Workload Scheduler engine on the master workstation. To install this fix pack, you must have the General Availability version of the connector for IBM Tivoli Workload Scheduler 8.1, with or without the previous fix pack. You must also have Job Scheduling Services Version 1.2. To install the fix pack, follow these steps on the workstation that runs the connector: 1. Insert the CD of the fix pack. 2. Open the Tivoli desktop and click on Desktop -> Install->Install Patch.... 3. Select the installation path in the file browser of Select Media. 4. Follow the instructions listed in the Tivoli Job Scheduling Console User's Guide to complete installation. Additional Installation Instructions This section includes the following topics: * "Fix Pack Installation Policy and Changes in the Opens Dependency Mechanism" * 1a.x, "Notes for the User" * "Changed Syntax for evtsize Command" * "Autotrace level 3.1.5" * "IY35486 - Windows Users Information" * "165022 Documentation Error in Tivoli Workload Scheduler Reference Guide" * "IY41955 - Windows Silent Installation" * "IY45797 - Cannot apply a Tivoli Workload Scheduler fix pack on W2K if installation directory is different from the twsuser home directory" * "Feature 153685: Implementation of nocheck and wait Options for submit Command" * "Feature 153621: Implementation of at/until time and absolute Keywords" * "168083 End- to- end: Re-use of deleted dependencies position" * "APAR IY52476 Documentation APAR" * 1a.xi, "Known Defects and Limitations for the Scheduler" * 1a.xii, "Known Defects and Limitations for Tivoli Workload Scheduler Connector" Fix Pack Installation Policy and Changes in the Opens Dependency Mechanism From fix pack 4 or later, the best way to install the patch should be to do it at the same time on all agents. In case of transitory resolution problems, these can be resolved by applying the patch on the agents that do not follow the latest version of the resolution algorithms. A complete simultaneous upgrade is a difficult condition to ask for; for this reason, a more progressive upgrading procedure is described below. Not all the upgrade schemes are compatible with the correct operation of Tivoli Workload Scheduler. This section describes the best choices to move to the latest patch. Due to changes in the Opens dependency polling, the patch is to be installed preferably bottom-up. The change in addressing of the Fy record implies that agents bearing files or hosting other agents with files (included XAs) have to be updated after any non-full status FTA that depends on those files, and before any domain manager with such non-full status FTAs that depends on those files in its domain. During transition, some errors may appear about unknown 'Id' messages. These messages do not bear any operational content; they circulate for informational purposes. Be aware that these messages could fill the stdlists more quickly than expected. A safe path for migration is outlined below: 1. Patch the FTAs that are non- domain managers, non-full status, and that depend on files stored on other FTAs. 2. Patch the FTAs that are non-domain managers that have the files other jobs depend from, or that host the XAs that have the files that other jobs depend on. 3. Patch the domain managers. 1a.x) Notes for the User This section describes important information affecting the use of Tivoli workload Scheduler. Changed Syntax for evtsize Command The syntax for the evtsize command has a new option. Instead of: * evtsize {-V | -U | } it becomes: * evtsize {-V | -U | -show |} You can use the -show option to query information about the maximum size of the current file and current queue length. Autotrace level 3.1.5 This fix pack uses Autotrace level 3.1.5. The new level is used in order to fix APAR IY37113. As a consequence, before you run any of the Autotrace commands (the ones contained in the TWSHOME/trace directory), you must set the environment variables as follows: ATTRACELIB=/usr/Tivoli/TWS/TKG/3.1.5/lib * For AIX: LIBPATH=$ATTRACELIB:$LIBPATH; export LIBPATH * For HP-UX: LIBPATH=$ATTRACELIB:$LIBPATH; export LIBPATH (32bit) SHLIB_PATH=$ATTRACELIB:$SHLIB_PATH; export SHLIB_PATH (64 bit) * For Solaris: LD_LIBRARY_PATH=$ATTRACELIB:$LD_LIBRARY_PATH;export LD_LIBRARY_PATH IY35486 - Windows Users Information APAR IY35486 has been opened to improve error messages reporting NT/W2K domain account authentication problems that affect Tivoli Workload Scheduler. To verify the security information Tivoli Workload Scheduler needs to resolve the Windows user name account. Two types of users exist in Windows: * Domain users. They are defined in the Domain Controller. * Local users. They are defined in the network workstations. For a domain user, Tivoli Workload Scheduler makes a request to the Primary Domain Controller (or to any Domain Controller for Windows 2000 Active Directory) to obtain any available Domain Controller. Tivoli Workload Scheduler uses the Domain Controller provided by the Primary Domain Controller to fill out the users structure. For a local user Tivoli Workload Scheduler makes a request that is processed by the local workstation. Tivoli Workload Scheduler specifies two types of user: * The maestro user. * The streamlogon user. These are the steps that Tivoli Workload Scheduler performs for Windows authentication: 1. Tivoli Workload Scheduler searches the Reference Domain for the user. The Reference Domain is either the name of the Windows network for the domain user or the name of the local workstation for the local user. Involved API: LookupAccountName. 2. If the user is a domain user, Tivoli Workload Scheduler asks the Primary Domain Controller for any available Domain Controller that can resolve the account for the user into the Reference Domain. Involved API: NetGetAnyDCName for Windows NT or DsGetDcName for Windows 2000. 3. Tivoli Workload Scheduler asks the Domain Controller (or the local workstation if the user is local) for the user information. API involved: NetUserGetInfo. On Windows 2000 the permissions for this API are contained in the group: BUILTIN\"Pre-Windows 2000 compatible access". For more details, see the MSDN Microsoft Web Site. You may see error messages concerning the above APIs for the following processes: jobmon, jobman, batchman, mailman, netman, writer, batchup, and joblnch. 165022 Documentation Error in Tivoli Workload Scheduler Reference Guide In the Tivoli Workload Scheduler Reference Guide correct the following example of makecal command: makecal -e -i24 makecal -r 3 -s "30 MAY 1999"-i30 as follows: makecal -e -i 24 makecal -r 3 -s "30 MAY 1999" -i 30 A blank space is required between the -i option and the digits. IY41955 - Windows Silent Installation On Windows, to install the product in silent mode, you must perform the following steps: 1. Copy the Setup.iss file available in the CD fix pack to your work directory. 2. Customize the Setup.iss file by specifying the Tivoli Workload Scheduler user, the Tivoli Workload Scheduler home directory and other settings. 3. From the CD directory run the setup.exe program with the following options: Setup.exe -f1 -f2 4. At the end of the installation, check in the log file to see if the installation ended successfully. IY45797 - Cannot apply a Tivoli Workload Scheduler fix pack on W2K if installation directory is different from the twsuser home directory Starting with Fix Pack 09, the Windows Silent Installation process completes successfully only if the Setup.iss configuration file contained in the fix pack is used. Versions of Setup.iss in previous fix packs do not work. You must therefore customize the new Setup.iss of fix pack 09. Feature 153685: Implementation of nocheck and wait Options for submit Command This feature implements two options, "nocheck" and "wait" to use together with the follows keyword in a conman submit command. The submit command can be issued against a schedule, a job, or an adhoc job. The follows dependency can be either a pre-sched dep or pre-job dep. The "nocheck" option inhibits conman from checking if the dependency exists in Symphony. It is related to the follows keyword that precedes it and is valid for every dependent object specified in the operands list of the follows keyword. In the following example: conman sbd dir follows=paperino,topolino;nocheck follows=DonaldDuck,MickeyMouse conman does not check for the dependency existence of paperino and topolino in Symphony, but it does check for the dependency existence of DonaldDuck and MickeyMouse. As a consequence of a nocheck option after a follows keyword, conman prints a warning message for each operand to which the option applies. Batchman adds the argument of the submit command (job/sched) and discards all the dependency records not found in the Symphony file. For each discarded dependency, batchman prints a warning message in the stdlist file. The "wait" option checks for the dependency in Symphony every second, until it finds it or until the specified time interval has expired. This option requires a parameter that represents a time interval in seconds (maximum value is 1200 sec). Like "nocheck", the "wait" option applies to all the operands list of the follows dependency that precedes it. The functionality of conman does not change. When the timeout expires, it means that the dependency was not found in the Symphony and conman prints an error message. When the timeout does not expire, it means that the dependency was found and conman prints a message stating that the submit command completed successfully. The combined use of "wait" and "nocheck" is allowed. In this case, the "wait" option takes effect first; then if the dependency is not found in the Symphony, conman forwards it to batchman. Feature 153621: Implementation of at/until time and absolute Keywords The time value in the AT/UNTIL options is considered as follows: if the time value is less than the current time, it is considered for the next day. If the time value is greater than the current time, it is considered for the current day. If you specify a time value greater than 2400, this value is divided by 2400 to obtain the number of days. If you specify days, these are added to the previously obtained value. This is the syntax for the sbj, sbd, sbf, sbs, and adddep commands: sbj ;at=time [Time Zone] [absolute | abs] Examples: sbj dir ;at=2700 absolute sbj dir ;at=2700 TZ JST abs sbj dir ;at=1200 TZ JST absolute If you specify the absolute keyword with at/until time, the scheduling date is the current date time with respect to the specified Time Zone. If the current time is greater than the at/until time, the is submitted immediately. If you specify a time value greater than 2400, this value is divided by 2400 to obtain the number of days. The absolute keyword cannot be used together with "+ n days" or "date". 168083 End- to- end: Re-use of deleted dependencies position The code fix for internal defect 168083 applies only to Tivoli Workload Scheduler networks working in end-to-end environments (that is, where the master domain manager is a z/OS host). A dependency is a condition that must be satisfied before a job (or operation) is launched. When Tivoli Workload Scheduler works in end-to-end configurations, only follows (successor/predecessor) and time dependencies are allowed. The maximum number of follows dependencies allowed for an operation (job) is 40. Using either ISPF or the Job Scheduling Console, users can add or remove predecessors/successors of a particular operation running on a fault-tolerant workstation. The problem fixed by this patch arises when the operation (job) already has 40 dependencies. If a user first deletes a number of dependencies to make room for new ones (keeping the number within the allowed limit) and then tries to add the new dependencies, Tivoli Workload Scheduler will log on stdlist that the limit of 40 dependencies has been reached and that new ones cannot be inserted. APAR IY52476 Documentation APAR Symptoms: Every job with AT times behavior should be changed back to the way it worked before. IY52475 is a DOC APAR raised to explain how Tivoli Workload Scheduler works with the EVERY option. If the every option is used with the AT dependency the product is designed to launch jobs at specific points in time. The following example launches the job testjob1 every 15 minutes, "testjob1 at 1800 every 15". The job is launched at 1800, 1815, 1830 and so on. If one rerun is delayed (for a dependency or for any other reason) the product realigns to the AT time so in this case it is possible that one or two iterations do not respect the EVERY rate. For example, if the above job is submitted adhoc at 1833 the reruns occur at 1833, 1834, 1845 and so on. In the example above, the job started at 1833, the start time is set to 1800 and it starts at 1833 the next rerun will have the start time set to 1830 (the start time of the previous job + three every rate) and it starts at 1834, the next rerun will have the start time set to 1845, it will start at 1845. To calculate the number of iterations that do not respect the every rate in a job, you have to consider two time values. * The start time: this is the expected start time of the job, it is displayed by conman when the job has not started to run. It is set to the AT time specified for the job or to the time when the rerun should be launched. * The time started: this is the actual start time of the job, it is displayed by conman when the job has run. To calculate the number of iterations that do not respect the every rate you have to consider the last run of the job. When Tivoli Workload Scheduler creates a new "rerun job" it sets the "expected" start time of the job, this value is calculated by adding to the start_time of the previous job as many "every rate" as possible but without exceeding the current value. If the EVERY option is used without the AT dependency the rerun jobs are scheduled always respecting the EVERY rate specified, starting from the time when the job actually started. If the EVERY option is used with the AT dependency there could be some interactions that do not respect the EVERY rate. For all other cases the every rate is always respected. 167318 Remove Copyright String from JOBMANRC. To remove Copyright String, it needs to customize own jobmanrc command as jobmanrc command into directory config. Installation Considerations None Special Considerations None 1a.xi) Known Defects and Limitations for the Scheduler * 155874 Error message of modify calendar is corrupted when LANG=ja_JP.eucJP. * 156386 On Solaris 5.8 command "build" on composer gets error for big file. * 156532 Two error messages when defining a job you are not allowed. * 162763 Recovery job inherits "interactive" from parent in a schedule. * 165685 DBCS-On Windows only the apar IY46982 (TWS-8.1-FP08) is not fixed. * 165700 composer cannot handle DBCS parms. * 165701 conman dj does not show job except Jnextday. * 165702 conman cannot handle DBCS parameters. * 165703 conman tellop cannot handle DBCS parms. * 165704 rep8 -b cannot run on D: (or E:, F: ...) drive. * 165705 rep7 -v command was issue on Windows prompt error message displayed. * 166676 info of jobs in userjobs lost if Task type is a long string. * 168111 the script version fails on linux because of nawk is not present. * 168364 Installation TWS81 Fix Pack 9 fails if some files with restricted permission are installed on the directory "/usr/Tivoli" (read the section Additional installation instructions). * 170598 Symptoms: DIVT:Makecal command displays error when issued w/o argument. * 170618 Symptoms: DIVT:Job names with Jap.char will not display job info using jbxtract * 170655 Symptoms: DIVT:DBCS filenames created thru create command can not be edited. * 170657 Symptoms: DIVT:Garbled msg when replacing files w/ duplicate definition. * 170760 Symptoms: DIVT:Rep commands display garbage characters on JP FTA machines * 170761 Symptoms: DIVT: Wmaetuil command gives garbled msgs * 170762 Symptoms: DIVT: Disp command display garbage char on WinJP FTA machines * 170765 Symptoms: DIVT: Caxtract command display garbage characters on WinJP FTA 1a.xii) Known Defects and Limitations for Tivoli Workload Scheduler Connector Defect 134562: Configuration: * TMR Server where Connector 8.1 and patch 1 are installed * Managed Node without Tivoli Workload Scheduler Connector In this scenario of a TMR Server that has already installed the Tivoli Workload Scheduler Connector 8.10 GA + fix pack 1 or later, when you try to install the Tivoli Workload Scheduler Connector 8.1.0 GA on a Managed Node that is connected to this TMR an error occurs. This was due to an incorrect revision level of Tivoli Workload Scheduler 8.1.0 Connector GA, there is a workaround to by-pass this problem and to be able to install on the Managed Node. * Copy on your local Machine all the images of the Tivoli Workload Scheduler Connector 8.1.0 GA. (where the Managed Node is installed) * Edit the TWS_CONN.ind file, to change the revision level from 0.03.00 to 8.01.11. * If you have installed on the TMR Server the Tivoli Workload Scheduler Connector 8.1.0 GA and fix pack 2, the revision level must be 8.01.02. Otherwise, if you had on the TMR Server the Tivoli Workload Scheduler 8.1.0 Connector fix pack 1, the revision level to set is 8.01.01. * In this way the installation of the Tivoli Workload Scheduler Connector 8.1.0 GA will be allowed. 2) Contacting IBM(R) 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(R) support, click the Tivoli support link at the bottom right of the page. If you want to contact IBM Software Support, see the IBM Software Support Guide at the following Web site: http://techsupport.services.ibm.com/guides/handbook.html The guide provides information about how to contact IBM Software Support, depending on the severity of your problem, and the following information: * Registration and eligibility. * Telephone numbers, depending on the country in which you are located. * Information you must have before contacting IBM Software Support. 3) NoticesThis 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: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement might not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 2Z4A/101 11400 Burnet Road Austin, TX 78758 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. If you are viewing this information in softcopy form, the photographs and color illustrations might not display. 3a) TrademarksIBM, the IBM logo, AIX(R), Tivoli, the Tivoli logo, and z/OS are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries | Java(TM) and all Java-based trademarks and logos are | trademarks or registered trademarks of Sun Microsystems, | Inc. in the United States, other countries, or both. Linux(TM) is a trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others.