tivoli workload scheduler release notes -...

Tivoli Workload SchedulerRelease Notes

Version 7.0

June 30, 2000

Tivoli Workload Scheduler Version 7.0 Release Notes (June 2000)

Copyright Notice

ISO 9001 CertificationThis product was developed using an ISO 9001 certified quality system.

Certification has been awarded by the Italian quality system certification group, CSQ (Certification No. CISQ/CSQ 9150.IBM7).

CSQ is a member of the mutually recognized organization of European assessors, ITQS, which assesses and certifies quality systems in the field of information technology enterprises.Copyright NoticeCopyright © 1999 by Tivoli Systems Inc., an IBM Company, including this documentation and all software. All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of Tivoli Systems. Tivoli Systems grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the Tivoli Systems copyright notice. No other rights under copyright are granted without prior written permission of Tivoli Systems. The document is not intended for production and is furnished “as is” without warranty of any kind. All warranties on this document are hereby disclaimed including the warranties of merchantability and fitness for a particular purpose.Note to U.S. Government Users—Documentation related to restricted rights—Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation.

NoticesReferences in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to Tivoli System’s or IBM’s valid intellectual property or other legally protectable right, any functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of the user.Tivoli Systems or IBM may have patents or pending patent applications covering subject matter 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 the IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, New York 10504-1785, U.S.A.

TrademarksThe following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, IBM, RS/6000, Tivoli, Tivoli Management Environment, and TME 10.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation.

UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited.

HP-UX is a registered trademark of Hewlett Packard Company.

Pentium is a registered trademark of Intel Corporation in the United States and other countries.

Java and all Java-based trademarks or logos are trademarks of Sun Microsystems, Inc.

Solaris is a registered trademark of Sun Microsystems, Inc.

Tivoli and OPC are registered trademarks or trademarks of Tivoli Systems Inc. in the United States, other countries or both. In Denmark, Tivoli is a trademark licensed from Kjøbenhavns Sommer - Tivoli A/S.

IBM is a registered trademark or trademark of International Business Machines Corporation in the United States and other countries.

Other company, product, and service names mentioned in this document may be trademarks or service marks of others.

Tivoli Workload Scheduler Release Notes 1

1.Tivoli Workload Scheduler Version 7.0 Release Notes

These release notes provide important information about the Tivoli Workload Scheduler (TWS) Version 7.0. These notes are the most current information for the product and take precedence over all other documentation.

Please review these notes thoroughly before installing or using this product.

Both Tivoli and TME 10 are used in our sales, marketing, and product information materials. These terms are interchangeable. We will remove references to TME 10 in future product releases.

Please note the following changes to these release notes:

These release notes include the following topics:

� “Additional Information” on page 2

� “New Features” on page 3

� “System Requirements” on page 4

� “Installation Notes” on page 7

� “Migrating to the Tivoli Workload Scheduler Version 7.0” on page 11

Revised on Section and Page Content Change

June 30, 2000 Installation Notes, page 9

Added page reference for customize arguments

June 30, 2000 Installation Notes, page 10

Added page reference for customize arguments

2 Version 7.0

� “Existing Problems Corrected in this Version” on page 13

� “Known Product Defects, Limitations, and Workarounds” on page 15

� “Internationalization Considerations” on page 21

� “Documentation Changes” on page 23

� “Product Notes” on page 29

Additional InformationVisit the Tivoli Customer Support site for information on customer services. These URLs require a password and ID. If you do not have access privileges or are unsure of your ID or password, send e-mail to:

[email protected]

Include your name and your company name in this correspondence.

You can find frequently updated information about configuring and using Tivoli products from the Tivoli Customer Support home page at:

http://www.tivoli.com/support/

This site includes the following links:

� Updated versions of these release notes: http://www.tivoli.com/support/Prodman/html/RN.html

� Updated versions of Tivoli documentation: http://www.tivoli.com/support/documents/

� Searchable support databases: http://www.tivoli.com/tivoli.ww.reg/rform?lang=english

� Access to product patches: http://www.tivoli.com/support/patches/

� Access to training schedules: http://www.tivoli.com/services/education/

� Access to Tivoli documentation survey: http://www.tivoli.com/support/survey/

You can order additional copies of product documentation by sending e-mail or calling one of the following locations:


� U.S. Customer E-mail: [email protected]

� U.S. Telephone: 1-800-879-2755

� Canada Telephone: 1-800-426-4968

� International Telephone: 404-238-1234

Please provide the title and version number of the document that you are ordering.

Note: Online files of the product manuals are available in PDF and postscript format on the TWS 7.0 CD-ROM. The following table shows where you can find these files:

New FeaturesTWS 7.0 includes the following new features:

Job Scheduling Console (JSC)A Java™-based GUI that you can install on Windows 95, Windows 98, Windows 2000, Windows NT, HP-UX, AIX, or Solaris. From any of these clients, you can connect to any master domain manager (MDM) or fault-tolerant agent (FTA) in a TWS network with TWS

Manual Path

Tivoli Workload Scheduler Planning and Installation Guide Version 7.0

� /TWS/DOC/tws-inst.pdf

� /TWS/DOC/tws-inst.ps

Tivoli Workload Scheduler User’s Guide Version 7.0

� /TWS/DOC/tws-ug.pdf

� /TWS/DOC/tws-ug.ps

Tivoli Workload Scheduler Reference Guide Version 7.0

� /TWS/DOC/tws-ref.pdf

� /TWS/DOC/tws-ref.ps

Tivoli Workload Scheduler User’s Guide Version 7.0

� /TWS/DOC/tws-plus.pdf

� /TWS/DOC/tws-plus.ps

Tivoli GEM Instrumentation for Workload Scheduler User’s Guide Version 7.0

� /TWS/DOC/tws-gem.pdf

� /TWS/DOC/tws-gem.ps

4 Version 7.0

connectors installed. You can manage both TWS and the Operations Planning and Control (OPC) scheduler from the JSC.

TWS connectorsA set of application programming interfaces (APIs) that you install on a system running the Tivoli Managed Framework (TMF). TWS connectors allow communication ween the JSC and the TWS engine.

AuditingA tracking feature that allows you to record user modifications to your TWS databases and production-control files.

InternationalizationA feature that adds TWS support for the following languages: Brazilian Portuguese, French, German, Italian, Japanese, Korean, Simplified Chinese (P.R.), Spanish, and Traditional Chinese (Taiwan).

Time Zone SupportA feature that allows you to define time zones on workstations and job stream definitions. Time zone support allows you to schedule jobs in relative time across multiple time zones in the TWS network.

See the TWS documentation included in your product package for more information about these features.

System RequirementsTWS consists of the following components:

� TWS engine

� TWS connector

� JSC

For information on JSC requirements, see the Tivoli Job Scheduling Console Release Notes for TWS and OPC Users.

Tivoli Workload Scheduler Engine RequirementsThe following table summarizes the supported platforms, recommended hardware, and operating system requirements for TWS. Tivoli supports


TWS for these vendor-supported operating systems at the time of release of TWS.

Additional Requirements for Windows NT and Windows 2000

To install the TWS engine on a system running Windows NT or Windows 2000, you must have the following:

� CD-ROM drive

� Space for log files and temporary files that TWS places on the local hard drive. The space for these files depends on the number of jobs TWS manages and the amount of time you retain log files.

Platform Operating System Disk Space RAM Swap

Space

Pentium 300 system

� Microsoft Windows NT Version 4.0 with Service Pack 4 or higher

� Microsoft Windows 2000

100 MB 128 MB 128 MB

RS/6000 AIX 4.2.1 or 4.3 200 MB 128 MB 128 MB

HP9000 700/800 series

HP-UX 10.20 and 11.00 200 MB 128 MB 128 MB

SPARC system Sun Solaris 2.6 or 2.7 200 MB 128 MB 128 MB

MIPS ABI � SINIX Pyramid V5.4.x

� Siemens Reliant - UNIX 5.44

� IRIX 6.5.2–6.5.9

100 MB 128 MB 128 MB

Intel ABI � NCR SVR4 MP-RAS V3.02 UNIX, NCR UNIX SVR4

� SCO Unixware 7.1 and 7.1.1

� DYNIX/ptx 4.4.4–4.5.1

� DG-UX 4.2

100 MB 128 MB 128 MB

DECUX OSF 4.0D–5.0 200 MB 128 MB 128 MB

6 Version 7.0

� TCP/IP network communications

� TWS user account

� NTFS partition for TWS

Additional Requirements for UNIX

To install the TWS engine on a system running UNIX, you must have the following:

� CD-ROM drive

� Space for log files and temporary files that TWS places on the local hard drive. The space for these files depends on the number of jobs TWS manages and the amount of time you retain log files.

� TCP/IP network communications

� TWS user account

� Network File System (NFS) if TWS FTAs mount directories from the MDM. See your system and network administrators and the Tivoli Workload Scheduler User’s Guide Version 7.0 for more information.

Tivoli Workload Scheduler Connector RequirementsThe following table summarizes the supported platforms, recommended hardware, and operating system requirements for the TWS connector.

Platform Operating System Disk Space RAM Swap

Space

Pentium 300 system

Microsoft Windows NT Version 4.0 with Service Pack 4 or higher

10 MB 128 MB 128 MB

RS/6000 AIX 4.2.1 or 4.3 20 MB 128 MB 128 MB

HP9000 700/800 series

HP-UX 10.20 and 11.00 20 MB 128 MB 128 MB

SPARC system Sun Solaris 2.6 or 2.7 20 MB 128 MB 128 MB


Additional Requirements

To install the TWS connector, you must have the following:

� Tivoli Management Framework (TMF) Version 3.6.1 or later

� TWS engine

Installation NotesThis section contains important information about installing TWS. Read this information carefully before installation.

For additional installation issues, see “Documentation Changes” on page 23.

PrerequisitesMake sure you address the following items before installing TWS:

� If you use AIX Version 4.2, you may need to install AIX fileset xlC.rte.3.6.6.0 to use gconman or gcomposer. To determine whether to install this fileset, run the following command:

lslpp -l xlC.rte

If the command displays a level value below 3.6.6.0, you must install the fileset.

� If you use AIX Version 4.3, you must install AIX fileset bos.rte.commands.4.3.1.1.bff. To determine whether this fileset is already installed on your system, run the following command:

lslpp -l box.rte.commands

If the command displays a level value below 4.3.1.1, you must install the fileset.

� If you use AIX 4.3, you must install the X11.compat.lib.X11R3 fileset from the AIX 4.3 Install Media. This compatibility library is necessary if you use gconman or gcomposer. To determine if this fileset is installed, run the following command:

lslpp -l X11.compat.lib.X11R3

� When you install on Unixware, use tar -oxvf instead of tar-xvf to untar the MAESTRO.TAR file.

8 Version 7.0

� Before you install on DG-UX, make sure the environment variable LD_NO_LIBSTREAMSOCKET is set to 0 and exported. This variable must be set when you run any TWS 7.0 application.

Changes in Installation and Uninstallation ProcedureThe following items describe changes to the installation procedure:

� In the Tivoli Workload Scheduler Planning and Installation Guide Version 7.0, page 26, replace the pathname in step 4 with the following:

d:\TWS\i386\maestro\setup.exe

� In the Tivoli Workload Scheduler Planning and Installation Guide Version 7.0, page 26, replace the pathname in step 2 part b with the following:

tar -xvf cd/TWS/platform/MAESTRO.TAR

� In the Tivoli Workload Scheduler Planning and Installation Guide Version 7.0, page 38, replace JOBMON Service with Tivoli Workload Scheduler Service.

� In the Tivoli Workload Scheduler Planning and Installation Guide Version 7.0,.The following command is incorrect:

./etc/Tivoli/setup_env.sh

Change it to the following for ksh:

. /etc/Tivoli/setup_env.sh

Change it to the following for csh:

source /etc/Tivoli/setup_env.csh

This error occurs on the following pages:

80 Installing JSS Using the Tivoli Desktop

84 Installing JSS Using the Command Line

85 Installing the TWS Connector Using the Tivoli Desktop

91 Installing the TWS Connector Using the Command Line

93 Installing JSS and TWS Connector Patches

95 Uninstalling the TWS Connector


95 Uninstalling the JSS Server

133 Running WMAEUTIL

� In the Tivoli Workload Scheduler Planning and Installation Guide Version 7.0, page 91, replace the bullets in step 3 with the following:

• To install on all managed nodes:

winstall -c install-dir -i TWS_CONNtwsdir=/users/maestro iname=Maestro

• To install on only one managed node:

winstall -c installdir -I TWS_CONN nodetwsdir=/users/maestro iname=Maestrocreateinst=1

where installdir is the pathname containing the installation images files and node is the name of the managed node on which to perform the installation.

� In the Tivoli Workload Scheduler Planning and Installation Guide Version 7.0, page 51, replace steps 4–7 with the following:

4. Create the FINAL job stream definition. This job stream contains the Jnextday job that automates creation of the Symphony file.

composer "add Sfinal"

5. Run the Jnextday job:

Jnextday

6. When the Jnextday job completes, check the status of TWS:

conman status

If TWS started correctly, the status is batchman LIVES.

� In the Tivoli Workload Scheduler Planning and Installation Guide Version 7.0, page 49, replace the last sentence in step 3 with the following:

For more information on the customize arguments and more examples, refer to page 57, “The Customize Script”.

10 Version 7.0

� In the Tivoli Workload Scheduler Planning and Installation Guide Version 7.0, page 55, replace the last sentence in step 2 with the following:

For more information on the customize arguments and more examples, refer to page 57, “The Customize Script”.

� After uninstalling the Tivoli GEM, you must delete all files in the following directories:

• $BINDIR/../generic_unix/TME/GEM/images/Tivoli/

Maestro_Control/V7_0_/Tivoli/Maestro_xxx

• $BINDIR/../generic_unix/TME/GEM/Tivoli/

Maestro_Control/V7_0_/Tivoli/Maestro_xxx

where Maestro_xxx can be Maestro_Fta, Maestro_Master, Maestro_StdAgent, or Maestro_Xagent.

In addition, you must delete the following files from the .installed directories in $BINDIR and $DBDIR:

• $BINDIR/.installed/Tivoli_Maestro_Control_V7_0__

Tivoli_Maestro_Fta_V7_0__BIN

• $BINDIR/.installed/Tivoli_Maestro_Control_V 7_0__Tivoli_Maestro_Master_V7_0__BIN

• $BINDIR/.installed/TTivoli_Maestro_Control_ V7_0__Tivoli_Maestro_StdAgent_V7_0__BIN

• $BINDIR/.installed/TTivoli_Maestro_Control_ V7_0__Tivoli_Maestro_Xagent_V7_0__BIN

• $DBDIR/.installed/Tivoli_Maestro_Control_V7 _0__Tivoli_Maestro_Master_V7_0__ALIDB

• $DBDIR/.installed/Tivoli_Maestro_Control_V7 _0__Tivoli_Maestro_Master_V7_0__ALIDB

• $DBDIR/.installed/Tivoli_Maestro_Control_V7 _0__Tivoli_Maestro_StdAgent_V7_0__ALIDB

• $DBDIR/.installed/Tivoli_Maestro_Control_V7 _0__Tivoli_Maestro_Xagent_V7_0__ALIDB

� If you uninstall JSS and you have multiple interconnected TMRs, you must specify the following:

wuninst TMF_JSS#TMRregion <node> -rmfiles


If you uninstall TWS connectors and have multiple interconnected TMRs, you must specify the following:

wuninst TWSConnector#TMRname <node> -rmfiles

Use the following command to find the correct syntax for removing an item:

wuninst TWSConnector

� Remcon (Remote Console) files are not removed by uninstall.exe. You must remove these files manually. (defect 93648)

� The following files are not removed by wuninst command. You must remove these files manually: (defect 94397)

$BINDIR/TAS/UNINST/twsclean

$BINDIR/TAS/UNINST/jssclean

usr/local/Tivoli/msg_cat/TMF_JSS_msgs

Migrating to the Tivoli Workload Scheduler Version 7.0

This section contains important information about migrating to TWS. Read this information carefully if you are migrating from previous versions of the product.

For additional migration issues, see “Documentation Changes” on page 23.

Migrating from Version 5.2Make sure you address the following before migrating to TWS from Version 5.2:

� Make sure that the following programs have the indicated revision levels:

mailman 3.34.1.17.1.1

writer 3.31.1.11.1.1

To get this information, run the programs with the -v option as follows:

12 Version 7.0

mailman -v

writer -v

If the revision levels are less than these values, you must apply patch 5.2-MAE-0054 (byte-order fix) before you migrate to TWS. This patch prevents batchman from encountering stopping errors when used after migration. (defect 88584)

� If you upgrade the MDM before the FTAs, problems occur due to differences in the way a version 5.2 and a 7.0 mailman modify the CPU records with domain pointers. The following error messages are displayed when you issue the stop or start commands on the local FTA, the FTA has been updated to 7.0, and Jnextday has not run:

• AWS11240012IAttempt to insert a null pointer into list.

• AWS11240026IList to search for visited nodes is empty.

• AWS11240031INull pointer supplied for delete.

• AWS11240012IAttempt to insert a null pointer into list.

• AWS11240026IList to search for visited nodes is empty.

• AWS22020072No qualified entries.

To avoid this problem, you can issue the start and stop commands from the MDM.

If you upgrade the MDM first, run Jnextday on the MDM after you upgrade the FTAs. The TWS mailman process modifies the CPU records to handle the domain pointers correctly.

� You must remove .tar and .tar.z files from the Maestro home directory for UNIX systems before upgrading to TWS.


Migrating from Version 6.xMake sure you address the following before migrating to TWS from Version 6.x:

� You must remove .tar and .tar.z files from the Maestro home directory for UNIX systems before upgrading to TWS.

Existing Problems Corrected in this VersionThe following APARs are addressed in TWS 7.0:

� IY09030 Job names longer than 22 chars get corrupted in stdlist header

� IY09171 Remote console cannot connect to CPU in trusted host environment

� IY00227 * character not allowed in the r3username field on gcomposer

� IY01702 The state fence does not work when selected from the GUI or CLI

� IY03683 UNIX master with MPE FTA, giving negative run times

� IY04175 Incorrect char support for r3 job def fields

� IY03890 Only the first line of remote cnf being referenced

� IY05049 Spurious jt causing succ job to be marked abend

� 85983 Need an environment variable to reflect job launch date

� IX82466 Change path in makecalc.tcl so that it is not relative

� IX85009 A 64-character job description exported using composer and then imported is truncated

� IY00235 Maestro ’at’ and ’mat’ commands do not work.

� IY01186 showexec displays a wrong date

� IY02496 conman changes on CPUs with serverid and in a subdomain are not being reflected in conman

� IY03388 Cannot kill jobs when job + schedname is greater than 28 characters

14 Version 7.0

� IY04837 Deleting until=nil dependencies causes jobman to die

� IY05047 showjobs at GUI and command line does not give correct state

� IY07096 datecalc with -12 month offset gives incorrect info

� IY07200 No dates are showing past 12/31/99 for report 7

� 87090 RD records filling mailbox.msg during Jnextday

� IY00308 catgets failed 0 error message when replying to local prompts

� IY02591 close_wait sessions are not closed after remote connection is closed

� IY02574 Jobs submitted at midnight do not have a start date in conman output

� 80935 rep11 doesn’t show dates with calendar offset

� IY04439 netman dies on master after connecting from agent using remote console

� IY06329 Jnextday hangs indefinitely at conman stop command

� 90764 Increasing maximum number of threads in tokensrv.exe

� IX85166 Jobs with an until time set after midnight still run

� IY08875 rep7 causes segmentation fault

� IX88466 Uninstall on NT does not remove all files/directories/registry entries

� IY02023 Performance fix (events file changes)

� IY05584 Cannot stop German NT FTA

� IY02307 Maestro does not work properly with large userids on HP-UX

� IX88357 Temp files left in root partition on NT

� IY05468 xrxtrct xjob report does not output CPU name


Known Product Defects, Limitations, and Workarounds

General defects, limitations, and workarounds for TWS Version 7.0 include:

� The default DOS editor for Windows NT is unable to handle a large number of job and job stream definitions. To correct this, set the editor variable to notepad. (defect 90681)

� During the spring daylight savings time change (01:59:59–03:00:00), UNIX and Windows NT behave differently. (defect 94279) For example:

• Windows NT: conman submit job at=02xx is set to 01xx

• HP-UX: conman submit job at=02xx is set to 03xx

� If you try to start a workstation with the JSC, an error message is displayed due to a missing or incorrect components file entry. This is because either the location for the components file is not the default and the variable $UNISON_COMPONENT_FILE is not set, or the entry in the /usr/unison/component file is incorrect (location incorrect).

To fix the problem, create a copy of the components file in the /usr/unison/components directory. If one already exists, modify the contents to match what is installed. Make sure you specify the path name of the home directory of the installed user. If your home directory is linked to another file system, make sure both references are listed in the file. (defect 93362)

� If you use text that is more than 71 characters long, the parameters are not expanded when scripts or commands are launched. (defect 76667)

� If you use quotes around the streamlogon, composer issues an error message when trying to document an MPE job. To avoid this message, avoid using quotes or use the JSC (defect 91819)

� The JSC hangs if you use the switch manager more than once in rapid succession. To avoid this, stop both the original MDM and the new one from conman before you issue the switchmgr command. (defect 92699)

16 Version 7.0

� If you use the CLI for composer, the MPE userjob documentation drops account and group names and adds necessary or out-of-place quotation marks. Use the JSC to avoid this problem. (defect 92708)

� wmaeutil performs a core dump when you use a wrong syntax on Solaris. (defect 93143)

� If you uninstall Tivoli Framework on Windows NT, you may get the following error message when you run Jnextday: libtas.dll is not found in the path. However, Jnextday still runs successfully. (defect 93859)

� If an undefined calendar is named in a job stream EXCEPT clause, scheduler fails. (defect 94490)

� The TWS engine allows duplicate job names in same schedule for HP-UX 10.20. (defect 94625)

� Logman during Jnextday, gives negative runtime errors on jobs. Jnextday still executes successfully. (defect 94699)

� If composer is unable to retrieve the maestro user password entry information from UNIX, it performs a core dump instead of issuing an error message. This is due to DNS/NIS configuration problems. (defect 94701)

� If you are logged on as root rather than maestro user, you will see the following message while performing untar during installation:

UX:tar: WARNING: Cannot get group information for users

Use tar -oxvf to avoid this message. (defect 95454)

� rmstdlist returns an exit code of 2, instead of 0, when there are no files to delete. (defect 78454)

� Jnextday shows errors when no instances of the connector are installed but the Tivoli Framework is installed. Jnextday still runs successfully. (defect 89937)

� If you use the conman kill command, Windows NT leaves the job running. To avoid this, you can use the Windows NT task manager to end the task or the TWS killproc utility from the unsupported directory. (defect 90111)


� You will receive the following message when you use the conman display job if the database is not present on the FTA: (defect 91096)

WS22020072 No qualified entries.

� Batchman performs a core dump when you use large Symphony files (with more than 65537 records). The Symphony size is 32 MB for expanded mode and 16 MB for unexpanded mode. (defect 93650)

� Recovery jobs that run on a workstation other than that of the original job are not launched if the recovery job workstation is a not a full-status FTA. (defect 94789)

� You may receive incorrect status information when you issue the stop command for all FTAs in a domain instance. The MDM is stopped before the FTAs. Therefore, the MDM displays the available information at the time it stops, regardless of changes in the FTA status. (defect 93759)

� If the directory you use for TWS is a symbolic link to another location, the actual, hard link is recorded in the components file. You will get an error if you use an absolute path. To avoid this, invoke the TWS programs with $PATH. (defect 90634)

� You may receive the following misleading message if you perform a MAKESEC command while another user uses CLI COMPOSER: (defect 90218)

MAKESEC:AWS11140308I Error renaming

MAKESEC:c:\win32app\maestro/../unison/Security.temp to

MAKESEC:c:\win32app\maestro/../unison/Security: File exists

AuditingThe following contains important information about the TWS auditing feature:

� Audit-level information, defined in the globalopts file, is stored into the Symphony file and distributed to the FTAs. As a result,

18 Version 7.0

you cannot toggle auditing on and off in the Plan or change the audit level during the production day. Changes to the Symphony file take effect when you run Jnextday.

� The audit-level information displayed in the JSC with engine information is unreliable and may be incorrect or misleading. Use the command-line interface (CLI) to confirm the audit levels. The JSC performs auditing correctly.

Time Zone The following contains important information if you are using TWS across multiple time zones

� If you enter a start time before the TWS start of day or a deadline time before the TWS start of day, the dates calculated by submitting a job stream from the database in the CLI are not consistent with those calculated by performing the same operation in the JSC (defect 6615).

For example, suppose the schedule date (displayed in the Properties-Scheduler window) is 5/25/2000 and the TWS start of day is 6 AM. Create the following three job streams in the database:

The resulting start times are calculated differently in the JSC and in the CLI, as shown in the following table:

Job Stream Start Time

JSA 4 AM

JSB 4 AM + 1 day

JSC 4 AM + 1 day

Job Stream Database CLI JS Console

JSA 4 AM 5/26/2000 4 AM 5/26/2000 4 AM


The start time calculated in the CLI is consistent with the start times calculated in the JSC and in Version 6.1.

Note: Using “until” time instead of start time gives similar results.

� You can specify time zones with the conman rerun command when the globalopts time-zone-enabled flag is set to NO, which causes the time and date to be calculated incorrectly. (defect 93407)

� The MDM can show an incorrect status for jobs on workstations in other time zones in an unexpanded database. The master workstation local time is used to determine the HOLD or READY state instead of the time on the workstation that hosts the job.

This has no operational effect since the job/job streams still launch at the correct time on their parent workstation. (defect 94283)

� TWS uses the local workstation time to calculate run dates for any conman command that has an AT= option when time zones are enabled but no date and time zone are specified. This can cause discrepancies if the job/job stream of the conman workstation is hosted by a workstation that uses a different date because of time zone differences.

Use the TZ= option with these commands to be sure that the date and time are calculated correctly. (defect 95785)

Tivoli Plus ModuleThe following contains important information about the Tivoli Plus Module:

� Enter the following commands to uninstall the Plus module: (defect 91093)

• Windows NT:

JSB 4 AM + 1 day 5/26/2000 4 AM 5/27/2000 4 AM

JSC 4 AM + 2 days 5/27/2000 4 AM 5/28/2000 4 AM

Job Stream Database CLI JS Console

20 Version 7.0

1. C:\>%SystemRoot%\system32\drivers\etc\

Tivoli\setup_env.cmd

2. C:\> bash

3. bash$ $BINDIR/../generic_unix/TME/PLUS/LINK/PLUSuninstall.sh $BINDIR/../generic_unix/TME/PLUS/TWS/

PLUSproduct-info.sh

• UNIX:

1. % . /etc/Tivoli/setup_env.sh

2. % $BINDIR/../generic_unix/TME/PLUS/LINK/PLUSuninstall.sh $BINDIR/../generic_unix/TME/PLUS/TWS/

PLUSproduct-info.sh

� You must manually remove the TWSPLUS_CAT file in the message catalog directory when uninstalling the PLUS module. (defect 93828)

� When you install the Link Bin and the Plus Module, do not reinstall the database portion of these components. Doing so can overwrite existing customized files. (defect 91101)

� When you use the TWS_Planned_Production_Schedule_reptr dialog, select only one level of detail: summary or detail. You will see the following error message if you select both:

###################################################

Task Name:TWS_Planned_Production_Schedule__reptr_

Task Endpoint:tisldev1 (ManagedNode)

Return Code:0

------Standard Output------

MAESTRO for UNIX/REPTR 7.0 (C) Tivoli Systems Inc. 1998

MAESTRO for UNIX (SOLARIS)/SYXTRACT 7.0 (1.4) (C) Tivoli Systems Inc. 1998

Installed for group ’DEFAULT’.

Locale LANG set to "C"

------Standard Error Output------

1: No such file or directory


####################

Internationalization ConsiderationsThe following items describe important information if you are using a translated version of TWS 7.0:

� On UNIX, you must set the LANG variable in the .profile (for ksh) or applicable file for other shells.

� You must set the LANG variable in jobmanrc for batchman to use the configuration in the language catalogs. By default, if the date format is changed and LANG is not set, the catalog is C and reports default to mm/dd/yy format.

� For double-byte languages using Microsoft Windows NT, you must use Notepad as the editor. Specify editor in the Variable field of the System Properties dialog box and specify notepad in the Value field.

� For western European languages, you must set the code page and change the font to Lucida before executing the TWS CLI. The command is chcp=1252. This is documented in the Tivoli Framework release notes as a known Microsoft problem.

� To view extended characters in any editor or DOS window, you must set the TISDIR environment variable. You can use the following paths:

• c:\tivoli\desktop

• c:\win32app\maestro

• c:\WINNT\system32\drivers\etc\Tivoli

� You must set MAESTRO_OUTPUT_STYLE=LONG to see all of the extended character set in the CLI. For example, if the schedule name is three Chinese characters, the total is nine bytes.The schedule field in the conman showjob command is eight characters, and the third character appears corrupted.

� All information is stored and passed as UTF8. For Asian languages, each character is three bytes long. The e accent, a accent, etc. characters in the European languages are two bytes long. Keep this in mind when planning object names.

22 Version 7.0

� The following are the English and double-byte character set (DBCS) length limitations for names:

� Setting the TISDIR environment variable during Windows NT installation could cause the following: (defect 93246)

• If you install maestro after you install netman, TISDIR overwrites the previous value and is reset to the maestro home. Currently, TISDIR is set during both netman and maestro installation. The codeset directory is bundled with both the maestro and netman products. If you install only netman, for example, under c:\win32app\unison\netman, TISDIR is set to

c:\win32app\unison\netman.

Scheduling ObjectEnglish limit

(ascii characters)

DBCS limit

(DBCS characters)

cpu name 16 5

domain name 16 5

cpuclass name 16 5

schedule name 16 5

job name 40 13

parm name 8 2

prompt name 8 2

prompt size 200 66

resource name 8 2

calendar name 8 2

JCL file name 4095 1365

file basename 28 9

file equation 120 40


• You must reboot the system after installation for the netman and maestro services to pick up the value of TISDIR.

• For multiple installations, TISDIR always points to the codeset bundled with the last netman/maestro installation. This is because the TISDIR variables overwrite each other when you install one netman/maestro over the other. If you want TISDIR to point to a specific directory, you must reset it.

• When netman/maestro is uninstalled, TISDIR is removed from the system. You must reset it to point to any existing codeset directory.

For UNIX, you must set TISDIR manually before you run a command.

� You must reboot your system to set the TISDIR environment variable for National Language Support (NLS) systems. TISDIR sets the path for the code pages, which display extended characters. (defect 96303)

Documentation ChangesPlease note the following changes to TWS 7.0 documentation:

� In the Tivoli Workload Scheduler User’s Guide Version 7.0, pages 375–376, “JS Console Job Status”, replace job stream with job.

� In the Tivoli Workload Scheduler Plus Module User’s Guide Version 7.0, page 11, replace the second paragraph with the following. Changes are shown in boldface text:

This task should be run on TWS agents where the Plus module has not been installed and whose TWS directory is different than the one specified when the Plus module was installed on the TME Server. This task must be executed on all TMAs. It must be run on managed nodes only if the TWS agent installation directory differs from the one specified when the Plus module was installed on the TME server. If this task is not executed, many of the tasks for this module will fail, as well as some of the distributed monitors.

24 Version 7.0

� In the Tivoli Workload Scheduler Plus Module User’s Guide Version 7.0, replace the table beginning on page 45 with the following:

TWS Log File Event Messages

"TWS process %s has been reset on host %s" (program_name, host_name)

Event Description: UNIX Event Class: Windows NT Event Class: Event Severity:

TWS daemon process reset. TWS_Process_Reset. TWS_NT_Process_ResetHARMLESS.

"TWS process %s is gone on host %s" (program_name, host_name)

Event Description: UNIX Event Class: Windows NT Event ClassEvent Severity:

TWS process gone. TWS_Process_Gone. TWS_NT_Process_GoneSeverity: CRITICAL.

"TWS process %s has abended on host %s" (program_name, host_name)

Event Description: UNIX Event Class: Windows NT Event Class:Event Severity:

TWS process abends. TWS_Process_Abend. TWS_NT_Process_AbendSeverity: CRITICAL.

"Job %s.%s failed, no recovery specified" (schedule_name, job_name)

Event Description: UNIX Event Class: Windows NT Event ClassEvent Severity: Automated Action: Correlation Activity:

Job abends, no recovery specified. TWS_Job_Abend.TWS_NT_Job_AbendCRITICAL. Mail job stdlist to user TWS (UNIX only). If this job had abended more than once within a 24 hour window, send a "TWS_Job_Repeated_Failure" event.

"Job %s.%s failed, recovery job will be run then schedule %s will be stopped" (schedule_name, job_name, schedule_name)

Event Description:

UNIX Event Class: Windows NT Event ClassEvent Severity: Automated Action: Correlation Activity:

Job abends, recovery step is run recovery job then stop schedule. TWS_Job_Abend. TWS_NT_Job_AbendCRITICAL. Mail job stdlist to user TWS (UNIX only).If this job had abended more than one time within a 24 hour window, send a "TWS_Job_Repeated_Failure" event.


"Job %s.%s failed, this job will be rerun" (schedule_name, job_name)

Event Description: UNIX Event Class: Windows NT Event ClassEvent Severity: Automated Action: Correlation Activity:

Job abends, recovery step is rerun job. TWS_Job_Abend. TWS_NT_Job_AbendCRITICAL. Mail job stdlist to user TWS (UNIX only). If this job had abended more than one time within a 24 hour window, send a TWS_Job_Repeated_Failure" event.

"Job %s.%s failed, this job will be rerun after the recovery job" (schedule_name, job_name)

Event Description: UNIX Event Class: Window NT Event Class:Event Severity: Automated Action: Correlation Activity:

Job abends, recovery step is rerun after recovery job. TWS_Job_Abend. TWS_NT_Job_AbendCRITICAL. Mail job stdlist to user TWS (UNIX only). If this job had abended more than one time within a 24 hour window, send a "TWS_Job_Repeated_Failure" event.

"Job %s.%s failed, continuing with schedule %s" (schedule_name, job_name, schedule_name)

Event Description: UNIX Event Class:Windows NT Event ClassEvent Severity: Automated Action: Correlation Activity:

Job abends, recovery step is continue with schedule. TWS_Job_Abend. TWS_NT_Job_AbendCRITICAL.Mail job stdlist to user TWS (UNIX only).If this job had abended more than one time within a 24 hour window, send a "TWS_Job_Repeated_Failure" event.

"Job %s.%s failed, running recovery job then continuing with schedule %s" (schedule_name, job_name, schedule_name)

Event Description:

UNIX Event Class: Windows NT Event Class:Event Severity: Automated Action: Correlation Activity:

Job abends, recovery step is run recovery job and continue with schedule. TWS_Job_Abend.TWS_NT_Job_AbendCRITICAL. Mail job stdlist to user TWS (UNIX only). If this job had abended more than one time within a 24 hour window, send a "TWS_Job_Repeated_Failure" event.

"Failure while rerunning failed job %s.%s" (schedule_name, job_name)

Event Description: UNIX Event Class: Windows NT Event Class:Event Severity: Automated Action: Correlation Activity:

Rerun of abended job abends. TWS_Job_Abend. TWS_NT_Job_AbendCRITICAL. Mail job stdlist to user TWS (UNIX only). If this job had abended more than one time within a 24 hour window, send a "TWS_Job_Repeated_Failure" event.


26 Version 7.0

"Failure while recovering job %s.%s" (schedule_name, job_name)

Event Description: UNIX Event Class: Windows NT Event Class:Event Severity: Automated Action: Correlation Activity:

Recovery job abends. TWS_Job_Abend. TWS_NT_Job_AbendCRITICAL. Mail job stdlist to user TWS (UNIX only). If this job had abended more than one time within a 24 hour window, send a "TWS_Job_Repeated_Failure" event.

"Multiple failures of Job %s#%s in 24 hour period" (schedule_name, job_name)


Same job fails more than once in 24 hours. TWS_Job_Repeated_Failure. TWS_NT_Job_Repeated_FailureCRITICAL.

"Job %s.%s did not start" (schedule_name, job_name)


Job failed to start. TWS_Job_Failed. TWS_NT_Job_FailedCRITICAL.

"Job %s.%s has started on CPU %s" (schedule_name, job_name, cpu_name)

Event Description: UNIX Event Class: Windows NT Event Class:Event Severity: Correlation Activity:

Job started. TWS_Job_Launched. TWS_NT_Job_LaunchedHARMLESS. Close open job prompt events related to this job.

"Job %s.%s has successfully completed on CPU %s" (schedule_name, job_name, cpu_name)


Job completed successfully. TWS_Job_Done. TWS_NT_Job_DoneHARMLESS. Close open job started events for this job and autoacknowledge this event.

"Job %s.%s suspended on CPU %s" (schedule_name, job_name, cpu_name)


Job suspended. TWS_Job_Suspended. TWS_NT_Job_SuspendedWARNING.



(TWS Prompt Message)


Job recovery prompt issued. TWS_Job_Recovery_Prompt. TWS_NT_Job_Recovery_PromptWARNING.

"Schedule %s has failed" (schedule_name)


Schedule abends. TWS_Schedule_Abend. TWS_NT_Schedule_AbendCRITICAL. If event is not acknowledged within 15 minutes, send mail to "TWS" user (UNIX only).

"Schedule %s is stuck" (schedule_name)


Schedule stuck. TWS_Schedule_Stuck. TWS_NT_Schedule_StuckCRITICAL. If event is not acknowledged within 15 minutes, send mail to "TWS" user (UNIX only).

"Schedule %s has started" (schedule_name)


Schedule started. TWS_Schedule_Started. TWS_NT_Schedule_StartedHARMLESS. Close all related schedule stuck or schedule abend events related to this schedule.

"Schedule %s has completed" (schedule_name)


Scheduled completed successfully. TWS_Schedule_Done. TWS_NT_ Schedule_DoneHARMLESS. Close all related schedule started events and auto-acknowledge this event.

(Global Prompt Message)


Global prompt issued. TWS_Global_Prompt. TWS_NT_Global_PromptWARNING.


28 Version 7.0

(Schedule Prompt’s Message)


Schedule prompt issued. TWS_Schedule_Prompt. TWS_NT_Schedule_PromptWARNING.

(Job Recovery Prompt’s Message)


Job recovery prompt issued. TWS_Job_Prompt. TWS_NT_Job_PromptWARNING.

"Comm link from %s to %s unlinked for unknown reason" (hostname, to_cpu)


TWS link to cpu dropped for unknown reason. TWS_Link_Dropped. TWS_NT_Link_DroppedWARNING.

"Comm link from %s to %s unlinked via unlink command" (hostname, to_cpu)


TWS link to cpu dropped by unlink command. TWS_Link_Dropped. TWS_NT_ Link_DroppedHARMLESS.

"Comm link from %s to %s dropped due to error" (hostname, to_cpu)


TWS link to cpu dropped due to error. TWS_Link_Dropped. TWS_NT_Link_DroppedCRITICAL.

"Comm link from %s to %s established" (hostname, to_cpu)


TWS cpu link to cpu established. TWS_Link_Dropped. TWS_NT_Link_DroppedHARMLESS. Close related Link_Dropped or Link_Failed events and auto-acknowledge this event.

"Comm link from %s to %s down for unknown reason" (hostname, to_cpu)

Event Description:UNIX Event Class: Windows NT Event Class:Event Severity:

TWS link to cpu failed for unknown reason. TWS_Link_Failed. TWS_NT_Link_FailedCRITICAL.



Product NotesThe following items describe important information for using TWS 7.0:

� TWS 7.0 is compatible with the Tivoli Scheduler Agent for SAP R/3 4.0. Previous versions of the agent are not fully compatible with TWS 7.0. Contact Tivoli for more information.

� gconman or gcomposer are no longer available for MIPS ABI and INTEL ABI platforms.

� gconman and gcomposer do not support TWS users that use a UID and GID greater than 65500 for HP-UX 10.2 or later.

� Contact Tivoli for information on the following extended agents:

• 5698-WKB-4805 - Tivoli Workload Scheduler MVS Integration 1.4.4

"Comm link from %s to %s down due to unlink" (hostname, to_cpu)


TWS link to cpu failed due to unlink.TWS_Link_Failed.TWS_NT_Link_FailedHARMLESS.

"Comm link from %s to %s down due to error" (hostname, to_cpu)


TWS cpu link to cpu failed due to error.TWS_Link_Failed.TWS_NT_Link_FailedCRITICAL.

"Comm link from %s to %s established" (hostname, to_cpu)


TWS link to cpu established.TWS_Link_Established.TWS_NT_Link_EstablishedHARMLESS. Close related Link_Dropped or Link_Failed events and auto-acknowledge this event.

"Active manager % for domain %" (cpu_name, domain_name)


TWS domain manager switch has occurred.TWS_Domain_Manager_SwitchTWS_NT_Domain_Manager_SwitchHARMLESS.


30 Version 7.0

• 5698-WKB-4807 - Tivoli Workload Scheduler SAP R/3 Integration 4.0

• 5698-WKB-4811 - Tivoli Workload Scheduler Oracle Financial Integration 1.3.0

• 5698-WKB-4813 - Tivoli Workload Scheduler Baan IV Integration v1.1

• 5698-WKB-5879 - Tivoli Workload Scheduler PeopleSoft Integration v1.1

� You must install patch 1.1-WXP-0003 if you are currently using PeopleSoft Xagent Version 1.1 and plan to upgrade to TWS 7.0.

� gcomposer and gconman (and visualm) do not support time zones.

tivoli workload scheduler release notes -...

Documents