sh19-4484-02

Tivoli Operations Planning and Control IBM

Tracker Agents forAIX, UNIX**, VMS**, andOS/390 Open EditionVersion 2 Release 3

SH19-4484-02

Note

Before using this information and the product it supports, be sure to read the general information under “Notices” on page ix.

ISO 9001 Certification

This 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 qualitysystems in the field of information technology enterprises.

Third Edition (December 1999)

This is a major revision of, and obsoletes, SH19-4484-01.

This edition applies to Version 2 Release 3 Modification Level 0 of Tivoli Operations Planning and Control, Program Number5697-OPC, and to all subsequent releases and modifications until otherwise indicated in new editions or technical newsletters. Seethe “Summary of Tivoli OPC Version 2 Release 3 Enhancements” on page xv for the changes made to this manual. Technicalchanges or additions to the text to describe the Tivoli Job Scheduling Console Support are indicated by a vertical line to the left ofthe change. Make sure you are using the correct edition for the level of the product.

Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at theaddress below.

IBM welcomes your comments. A form for readers' comments appears at the back of this publication. If the form has beenremoved, address your comments to:

Tivoli OPC Information DevelopmentRome Tivoli LaboratoryIBM Italy S.p.A.Via Sciangai, 5300144 RomeItaly Fax Number (+39) 06 5966 2077 Internet ID: ROMERCF at VNET.IBM.COM

When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believesappropriate without incurring any obligation to you.

Copyright International Business Machines Corporation 1995, 1999. All rights reserved.Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject torestrictions set forth in GSA ADP Schedule Contract with IBM Corp.

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixTrademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiWho Should Read This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiHow This Book Is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiTivoli OPC Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Tivoli OPC Online Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiOnline Message Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Other Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Summary of Tivoli OPC Version 2 Release 3 Enhancements . . . . . . . . xvJob Scheduling Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvCatalog Management — Data Availability . . . . . . . . . . . . . . . . . . . . . . xvOS/390 Workload Manager Support . . . . . . . . . . . . . . . . . . . . . . . . . xvOS/390 Automatic Restart Manager Support . . . . . . . . . . . . . . . . . . . . xviProgram Interface (PIF) Enhancements . . . . . . . . . . . . . . . . . . . . . . . xviEnhancements for Non-OS/390 Tracker Agents . . . . . . . . . . . . . . . . . . xviUsability Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviNew and Changed Installation Exits . . . . . . . . . . . . . . . . . . . . . . . . . xviiNew and Changed Initialization Statements . . . . . . . . . . . . . . . . . . . . xviiVersion 2 Release 2 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiiVersion 2 Release 1 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii

Chapter 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Product Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Tracker Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

The Installation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Using the Latest Install Information . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 2. Things to Be Done with the Tivoli OPC Controller . . . . . . . . 5Loading the Tracker Agent Software to MVS . . . . . . . . . . . . . . . . . . . . . 5

Installing the Tracker Agent Software Using SMP/E . . . . . . . . . . . . . . . 6Applying Tracker Agent Maintenance . . . . . . . . . . . . . . . . . . . . . . . . 7

Loading Tracker Agent Enabler Software to MVS . . . . . . . . . . . . . . . . . . 7Installing the Enabler for the Tracker Agent Using SMP/E . . . . . . . . . . . 8Applying Maintenance for Tracker Agent Enabler . . . . . . . . . . . . . . . . . 8

Tivoli OPC Controller Initialization Statements . . . . . . . . . . . . . . . . . . . . 9ROUTOPTS Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10JTOPTS Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10OPCOPTS Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 3. Planning your Tracker Agent Installation . . . . . . . . . . . . . 11Creating a User Group and User IDs . . . . . . . . . . . . . . . . . . . . . . . . 12

Creating the User Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Creating the User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Adding New Users to the opc Group . . . . . . . . . . . . . . . . . . . . . . . 14

Kernel Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Planning Your Directory Layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Copyright IBM Corp. 1995, 1999 iii

Verifying Host and Service Names . . . . . . . . . . . . . . . . . . . . . . . . . . 17Verifying the TCP/IP Environment (AIX Only) . . . . . . . . . . . . . . . . . . . 19

Verifying that TCP/IP Is Operational . . . . . . . . . . . . . . . . . . . . . . . 21Verifying the Connection to the Controller Machine . . . . . . . . . . . . . . 22Verifying the Connection from the Controller Machine . . . . . . . . . . . . . 22Verifying the Network Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Verifying the TCP/IP Environment (HP-UX Only) . . . . . . . . . . . . . . . . . 23Verifying the Connection to the Controller Machine . . . . . . . . . . . . . . 24Verifying the Connection from the Controller Machine . . . . . . . . . . . . . 24

Verifying the TCP/IP Environment (Sun Solaris and SunOS only) . . . . . . . . 25Verifying the Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Verifying that TCP/IP Is Operational . . . . . . . . . . . . . . . . . . . . . . . 25Verifying the Connection to the Controller Machine . . . . . . . . . . . . . . 26Verifying the Connection from the Controller Machine . . . . . . . . . . . . . 26Verifying the Network Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Verifying the TCP/IP Environment (OS/390 only) . . . . . . . . . . . . . . . . . 27Verifying that TCP/IP Is Operational . . . . . . . . . . . . . . . . . . . . . . . 27Verifying the Connection to the Controller Machine . . . . . . . . . . . . . . 27Verifying the Connection from the Controller Machine . . . . . . . . . . . . . 27

Chapter 4. Installing and Customizing the Tracker Agent . . . . . . . . . . 29Download the Tracker Agent Files from the Controller System . . . . . . . . . 29

AIX Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29HP-UX Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Sun Solaris Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36SunOS Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

| SGI IRIX Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Digital UNIX Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Digital OpenVMS VAX/Alpha Only . . . . . . . . . . . . . . . . . . . . . . . . 44OS/390 Open Edition Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Creating Links between the Directories . . . . . . . . . . . . . . . . . . . . . . . 48Customizing the Configuration Parameter File . . . . . . . . . . . . . . . . . . . 48

Home Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Customizing the Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Customizing File Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Restrictions and Dependencies on System Software . . . . . . . . . . . . . . . 57NFS Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Number of Processes per User . . . . . . . . . . . . . . . . . . . . . . . . . . 57Coordinating Clock Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Chapter 5. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Running Scripts for Tivoli OPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Storing Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Writing Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Determining the Shell that Scripts Run Under . . . . . . . . . . . . . . . . . . 59Specifying a User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Getting Output from Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Testing for Errors from Commands . . . . . . . . . . . . . . . . . . . . . . . . . 61Specifying the Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Controlling the Tracker Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Starting the Tracker Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Checking Tracker Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Shutting Down the Tracker Agent . . . . . . . . . . . . . . . . . . . . . . . . . 65

Dealing with Temporary and Log Files . . . . . . . . . . . . . . . . . . . . . . . 65

iv Tivoli OPC Tracker Agents for AIX, UNIX, VMS, OS/390

Checking Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Restarting after an Abnormal Termination . . . . . . . . . . . . . . . . . . . . . 66

Chapter 6. Diagnosing Problems . . . . . . . . . . . . . . . . . . . . . . . . . 69Exit Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70General Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Dealing with a Hung Tracker Agent . . . . . . . . . . . . . . . . . . . . . . . . 71Checking Files in the Log and Temporary Directories . . . . . . . . . . . . . 72Trace Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Checking the Configuration Parameter File . . . . . . . . . . . . . . . . . . . 73Checking File Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Checking the Tracker User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Checking the NFS File System . . . . . . . . . . . . . . . . . . . . . . . . . . 75Checking the NIS Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Checking the name server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Checking Duplicate Port Definitions . . . . . . . . . . . . . . . . . . . . . . . . 75Defining local_ipaddr if Multiple Interfaces . . . . . . . . . . . . . . . . . . . . 75Fixing Problems with Symbolic Links . . . . . . . . . . . . . . . . . . . . . . . 75Resetting the Tracker Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Checking IPC Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Tuning and Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Appendix A. Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Appendix B. Utilities and Samples . . . . . . . . . . . . . . . . . . . . . . . . 93Utility Programs and Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

eqqstart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93eqqverify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94eqqstop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94eqqfm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95eqqdelete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96eqqview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96eqqinit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97eqqclean . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97eqqperm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97eqqcv80p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98eqqshow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Appendix C. Enabling the Pulse Functions . . . . . . . . . . . . . . . . . . 101| Setting Up the Controller Machine and OS/390 OE System . . . . . . . . . . 101

Setting Up an AIX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Setting Up an HP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Setting Up a SunOS System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Recompiling the Kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Setting Up a Sun Solaris System . . . . . . . . . . . . . . . . . . . . . . . . . 104Setting Up a MIPS ABI System . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Setting Up a Digital OpenVMS System . . . . . . . . . . . . . . . . . . . . . . 104Setting Up a Digital UNIX System . . . . . . . . . . . . . . . . . . . . . . . . . 105

Appendix D. Using LoadLeveler . . . . . . . . . . . . . . . . . . . . . . . . 107Sample LoadLeveler script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Contents v

Appendix E. EBCDIC and ASCII Codepage Tables . . . . . . . . . . . . . 109

Appendix F. Machine and Program Requirements for AIX Systems . . . 111Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Appendix G. Machine and Program Requirements for HP-UX Systems 113Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Appendix H. Machine and Program Requirements for Solaris Systems 115Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Appendix I. Machine and Program Requirements for SunOS Systems . 117Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Appendix J. Machine and Program Requirements for Digital OpenVMSSystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

| Appendix K. Machine and Program Requirements for Silicon Graphics| IRIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Appendix L. Machine and Program Requirements for Digital UNIX . . . 123Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Appendix M. Machine and Program Requirements for OS/390 . . . . . . 125Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Appendix N. Applying Tracker Maintenance on Non-AIX Machines . . . 127

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

vi Tivoli OPC Tracker Agents for AIX, UNIX, VMS, OS/390

Figures

1. An Extract from the /etc/hosts File . . . . . . . . . . . . . . . . . . . . . . . 172. Example Configuration Showing Port Numbers . . . . . . . . . . . . . . . 183. An Extract from the /etc/services File on UNIX Tracker 1 . . . . . . . . . 184. An Extract from the /etc/services File on UNIX Tracker 2 . . . . . . . . . 195. Ports in the UNIX Tracker 1 Configuration File . . . . . . . . . . . . . . . 196. Ports in the UNIX Tracker 2 Configuration File . . . . . . . . . . . . . . . 197. Checking the Tracker Files on Solaris . . . . . . . . . . . . . . . . . . . . 378. Checking the Tracker Files on SunOS . . . . . . . . . . . . . . . . . . . . 399. Checking the Tracker Files on SGI IRIX . . . . . . . . . . . . . . . . . . . 41

10. Checking the Tracker Files on Digital UNIX . . . . . . . . . . . . . . . . . 4311. Keyword Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5112. Example of a Configuration File . . . . . . . . . . . . . . . . . . . . . . . . 55

Tables

1. The INCLUDE Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii2. The INIT Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv3. Changes to Installation Exits . . . . . . . . . . . . . . . . . . . . . . . . . . xxv4. Stages in the Installation Process . . . . . . . . . . . . . . . . . . . . . . . . 25. Tracker Agent Libraries Loaded by SMP/E . . . . . . . . . . . . . . . . . . . 56. Enabler Libraries Loaded by SMP/E for the Tracker Agent . . . . . . . . . 77. Planning for Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118. Tracker Agent Directory Structure . . . . . . . . . . . . . . . . . . . . . . . 159. The Tracker Agent Installation Process . . . . . . . . . . . . . . . . . . . . 29

10. Symptoms and Required Actions for Common Problems . . . . . . . . . 6911. Values of Tracker Agent flags . . . . . . . . . . . . . . . . . . . . . . . . . 9412. Codepage Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Copyright IBM Corp. 1995, 1999 vii

viii Tivoli OPC Tracker Agents for AIX, UNIX, VMS, OS/390

Notices

References in this publication to IBM products, programs, or services do not implythat IBM intends to make these available in all countries in which IBM operates.Any reference to an IBM product, program, or service is not intended to state orimply that only IBM’s product, program, or service may be used. Subject to IBM'svalid intellectual property or other legally protectable rights, any functionallyequivalent product, program, or service may be used instead of the IBM product,program, or service. The evaluation and verification of operation in conjunction withother products, except those expressly designated by IBM, is the user’sresponsibility.

IBM may have patents or pending patent applications covering subject matter inthis document. The furnishing of this document does not give you any license tothese patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

Licensees of this program who wish to have information about it for the purpose ofenabling: (i) the exchange of information between independently created programsand other programs (including this one) and (ii) the mutual use of the informationwhich has been exchanged, should contact:

IBM CorporationP.O. Box 121953039 CornwallisResearch Triangle Park, NC 27709-2195U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

TrademarksThe following terms in this publication are trademarks of Tivoli Systems or IBMCorporation in the United States or other countries or both:

In Denmark, Tivoli is a trademark licensed from Kjøbenhavns Sommer - Tivoli A/S

AIX AIX/6000AS/400 BookManagerIBM LoadLevelerMVS/ESA OPCOS/2 OS/390OS/400 Scalable POWERparallel SystemsTivoli TMETME 10

Copyright IBM Corp. 1995, 1999 ix

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

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

C-bus is a trademark of Corollary, Inc.

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

PC Direct is a trademark of Ziff Communications Company and is used by IBMCorporation under license.

ActionMedia, LANDesk, MMX, Pentium, and ProShare are trademarks or registeredtrademarks of Intel Corporation in the United States and other countries.

Other company, product, and service names which may be denoted by a doubleasterisk (**), may be trademarks or service marks of others.

HP-UX Hewlett-Packard Corp.| IRIX Silicon Graphics, Inc.

Network File System Sun Microsystems Inc.Network Information System Sun Microsystems Inc.NFS Sun Microsystems Inc.NIS Sun Microsystems Inc.ORACLE Oracle Corp.Solaris Sun Microsystems Inc.SPARC SPARC International Inc.Sun Sun Microsystems Inc.SunOS Sun Microsystems Inc.

x Tivoli OPC Tracker Agents for AIX, UNIX, VMS, OS/390

Preface

This book covers installation tasks, component logic, operation, and problemdetermination for these features of Tivoli OPC.

� OPC Tracker Agent for AIX� OPC Tracker Agent for Digital OpenVMS**� OPC Tracker Agent for Digital UNIX**� OPC Tracker Agent for HP-UX**� OPC Tracker Agent for Silicon Graphics IRIX**� OPC Tracker Agent for Sun Solaris**� OPC Tracker Agent for SunOS**� OPC Tracker Agent for OS/390 Open Edition

These features differ only slightly in their installation and operation, and aretherefore described in the same book. Differences are clearly marked, like this:

OPC Tracker Agent for Sun Solaris only

Use the EQQTXSEN load module

OPC Tracker Agent for SunOS only

Use the EQQTXUEN load module

Installation is the task of making a program ready to do useful work. This taskincludes adding the materials on the IBM distribution tape to your system,preparing, and maintaining the program.

Who Should Read This BookThis book is intended for those who are responsible for Tracker Agent systemadministration. The role of the system administrator normally includes the followingtasks:

� Installing the Tracker Agent� Setting up the configuration files� Maintaining the Tracker Agent� Performing initial problem determination.

In order to perform the tasks described in this book, the Tracker Agent systemadministrator must be an experienced user of UNIX commands and be familiar withsystem management techniques used in the operating environment. Knowledge ofnetworking will also be helpful.

Copyright IBM Corp. 1995, 1999 xi

How This Book Is OrganizedRead Chapter 1, “Overview” to understand the relationship between the TrackerAgent and the controller products.Chapter 2, “Things to Be Done with the TivoliOPC Controller” describes the installation steps on the controllersystems.Chapter 3, “Planning your Tracker Agent Installation” and Chapter 4,“Installing and Customizing the Tracker Agent” describe the installation steps on theUNIX workstation. Chapter 5, “Operation” describes day-to-day tracker operation,and Chapter 6, “Diagnosing Problems” describes problem determination and datacollection information for diagnosing suspected problems. The appendixes describethe messages, utilities, samples, setup for enabling the pulse functionality (theKEEPALIVE option), and prerequisites for the Tracker Agent.

Tivoli OPC PublicationsThis book is part of an extensive Tivoli OPC library. These books can help you useTivoli OPC more effectively:

Task Publication Ordernumber

Evaluating Tivoli OPC General Fact Sheet GH19-4370

Evaluating Tracker Agents Tracker Agent Features Fact Sheet GH19-4371

Planning Tivoli OPC Licensed Program Specifications GH19-4373

Understanding Tivoli OPC General Information GH19-4372

Learning Tivoli OPC conceptsand terminology

Getting Started with Tivoli OPC SH19-4481

| Using the Java GUI| Tivoli Job Scheduling Console Guide for OPC Users| GC32-0402

| Using the Java GUI| Tivoli Job Scheduling Console Release Notes| GI10-9233

Interpreting messages andcodes

Messages and Codes SH19-4480

Installing Tivoli OPC Installation Guide SH19-4379

Customizing and tuning TivoliOPC

Customization and Tuning SH19-4380

Planning and scheduling theworkload

Planning and Scheduling the Workload SH19-4376

Controlling and monitoring thecurrent plan

Controlling and Monitoring the Workload SH19-4377

Using Workload Monitor/2 Workload Monitor/2 User’s Guide SH19-4482

Writing application programs Programming Interfaces SH19-4378

Quick reference Quick Reference GH19-4374

Diagnosing failures Diagnosis Guide and Reference LY19-6405

Controlling the AIX, UNIX**,VMS, OS/390 Open Editionworkload

Tracker Agents for AIX, UNIX, VMS, OS/390 Open EditionInstallation and Operation

SH19-4484

Controlling the OS/2 and NTworkload

Tracker Agents for OS/2 and Windows NTInstallation and Operation

SH19-4483

xii Tivoli OPC Tracker Agents for AIX, UNIX, VMS, OS/390

Task Publication Ordernumber

Controlling the OS/400workload

Tracker Agent for OS/400Installation and Operation

SH19-4485

A Master Index, SH19-4375, is published for the Tivoli OPC library.

Maximizing Your OPC Throughput, SG24-2130, contains useful information fortuning the OPC installation.

Tivoli OPC Online BooksAll the books in the Tivoli OPC library, except the licensed publications, areavailable in displayable softcopy form on CD-ROM in the following SoftcopyCollection Kit:

� OS/390, SK2T-6700

You can read the softcopy books on CD-ROMs using these IBM licensed programs:

� BookManager READ/2 (program number 5601-454)� BookManager READ/DOS (program number 5601-453)� BookManager READ/6000 (program number 5765-086)

All the BookManager programs need a personal computer equipped with aCD-ROM disk drive (capable of reading disks formatted in the ISO 9660 standard)and a matching adapter and cable. For additional hardware and softwareinformation, refer to the documentation for the specific BookManager product youare using.

Updates to books between releases are provided in softcopy only.

Online Message FacilityThe Online Message Facility (OMF) is an OS/2 program that provides onlineaccess to information from BookManager softcopy books. It helps you diagnoseproblems without interrupting your work. You can retrieve the description of amessage by clicking on a message number in a Communications Manageremulator window. Additional information about OMF is available on the Messagesand Codes CD-ROM.

Preface xiii

Other PublicationsYou might find these publications useful when you install the Tracker Agent:

Short title Publication Ordernumber

JCL Reference MVS JCL ReferenceMVS SP5 JCL Reference

GC28-1654GC28-1479

JCL User's Guide MVS JCL User's GuideMVS SP5 JCL User's Guide

GC28-1653GC28-1473

SMP/E Reference System Modification Program Extended Reference SC28-1107

SMP/E User's Guide System Modification Program Extended User's Guide SC28-1302

SMP/E Messages System Modification Program Extended Messages andCodes

GC28-1108

MVS TCP/IP User's Guide IBM Transmission Control Protocol/Internet Protocol forMVS: User's Guide

SC31-6088

AIX TCP/IP User's Guide AIX Operating System TCP/IP User's Guide SC23-2300

Quick Start Guide IBM RISC System/6000 Quick Start Guide SC23-2195

Task Index and Glossary Task Index and Glossary for IBM RISC System/6000 GC23-2201

AIX Communications AIX Communications Concepts and Procedures for IBMRISC System/6000

GC23-2203

AIX Commands AIX Commands Reference for IBM RISC System/6000 GC23-2367

Tivoli GEM Installation and User'sGuide

Tivoli Global Enterprise Manager: Installation and User'sGuide

GC31-8474

Tivoli GEM Application PolicyManager User's Guide

Tivoli Global Enterprise Manager: Application PolicyManager User's Guide

GC31-5108

Tivoli GEM Instrumentation Guide Tivoli Global Enterprise Manager: Instrumentation Guide GC31-5109

SAP R/3 User's Guide SAP R/3 User's Guide GC31-5147

Maestro SupplementalDocumentation Set

Unison Maestro Supplemental Documentation Set SK3T-3566

Before you install the Tracker Agent, you should be familiar with the procedures forinstalling software and system administration on the target operating environment.This information is provided by Hewlett-Packard Corporation, for HP-UX systems,by Sun Microsystems Inc., for Sun** systems, and by IBM, for AIX systems.

xiv Tivoli OPC Tracker Agents for AIX, UNIX, VMS, OS/390

Summary of Tivoli OPC Version 2 Release 3 Enhancements

Job Scheduling ConsoleThe new Tivoli Job Scheduling Console (JSC) is a Java-based, client/serverapplication. The key advantages of the JSC are the ability to performadministration and operation tasks in a graphical manner and the ability to accessmultiple OPC controllers from a single console.

The JSC can:

� Display lists of objects already defined to OPC, from the database and from thecurrent plan, by using flexible filtering criteria

� Work with application descriptions including jobs and their dependencies, timerestrictions (input arrival time, deadline, duration), and run cycles

� Work with special resource and workstation definitions

� Modify occurrences, workstation status, and special resource information fromthe current plan.

The JSC retains the OPC security model. Each data access request is validatedby the controller as it is done currently for ISPF users.

The JSC is a real-time interface with OPC and can be used concurrently with theISPF interface. It is available for various UNIX platforms, Windows NT, andWindows 98. The OPC Connector, which is a backend component supporting theJSC, is available for various UNIX platforms and Windows NT.

Catalog Management — Data AvailabilityThe new Catalog Management – Data Availability feature improves OPCperformance for job restart and job log retrieval functions. Job runtime information,for example, the sysout datasets, is maintained locally on the tracked system. Thecontroller retrieves this information only when needed for catalog managementactions, eliminating the network and processing overhead associated with thetransmission of superfluous data. The runtime information at the tracked system ismanaged by a new component, the OPC Data Store. Using the OPC Data Store,OPC Tracker processes are bypassed and are dedicated to the time-critical jobsubmission and tracking tasks. A new feature is provided to selectively determinehow long job runtime information is kept in the Data Store. This new feature isespecially useful when a joblog archiving product is used concurrently with OPC.

OS/390 Workload Manager SupportOS/390 Workload Manager, when used in goal mode, provides a new, policy-basedmanagement of deadlines for critical jobs. Some CPU-type operations can now bemarked as critical in OPC. When such a critical operation is late, according to thespecified policy, OPC interfaces with Workload Manager to move the associated jobto a higher performance service class. Thus the job receives appropriate additionalsystem resource to reduce or eliminate the delay. Several policies are available to

Copyright IBM Corp. 1995, 1999 xv

decide when a job is late, considering characteristics such as duration, deadlinetime, and latest start time.

OS/390 Automatic Restart Manager SupportOS/390 Automatic Restart Manager increases the availability of OPC components.In the event of program failure, OPC components, for example, the Controller, theOS/390 Tracker and the Server can now be restarted automatically by theAutomatic Restart Manager.

Program Interface (PIF) EnhancementsThe Program Interface (PIF) has been extended to increase the flexibility of OPC,allowing users to have extended access to OPC data from other applicationprograms. Tivoli OPC Version 2 Release 3 significantly enhances the ability toaccess current plan data from the PIF by providing:

� Full support for special resources data

� Read access to special resource usage information for operations

� The ability to modify the workstation open intervals

� The ability to modify the successor information for an operation.

New resource codes have been added to the Program Interface (PIF):

CPOPSRU Current plan operation segment with information for theoperation in relation to a special resource

CPSUC Current plan successor segment

CSR Current plan special resources

CSRCOM Current plan special resource common segment

IVL Current plan workstation interval segment

Enhancements for Non-OS/390 Tracker AgentsThe OPC Tracker Agents for non-OS/390 platforms have been enhanced:

� A new version of the OPC Tracker Agent for OpenVMS is available. This newversion runs in the native OpenVMS environment, thus removing therequirement to install the POSIX shell.

� The security features for the UNIX OPC Tracker Agents have been enhanced.Stricter file permissions are now used for temporary work files.

� The installation process of the OPC Tracker Agent for OS/390 UNIX SystemServices has been simplified.

Usability EnhancementsNew features increase the overall usability of the product, thus increasing userproductivity:

� OPC can perform variable substitution within inline procedures, thus increasingthe flexibility of the job setup feature. It is possible to customize OPC so that

xvi Tivoli OPC Tracker Agents for AIX, UNIX, VMS, OS/390

jobs are submitted also when variables are not defined in the OPC variabletables. This means that, when variables are substituted outside OPC, duplicatevariable definitions are avoided.

� During Catalog Management actions, OPC can delete datasets with anexpiration date.

� A new Modify command (JSUACT) has been provided to start or stop the jobsubmission function. This feature enables automation products, for example,Tivoli NetView to have control over the OPC job submission activity.

� The Mass Update utility has been enhanced with a new sample job Thisdownloads all the applications belonging to a group in a sequential file for useas input to the Batch Loader utility, thus easing the management of groupapplications from the batch administration.

� The sample library now contains the DSECT sections for the Program Interface(PIF) data areas. This eases the process of writing PIF applications and themigration of existing PIF applications to new OPC releases.

New and Changed Installation ExitsUser exit EQQUX001 has three new parameters:

NEWREC Number of JCL lines in new JCLAREA

NEWJCL New JCLAREA

USDREC Number of JCL lines used in new JCLAREA

User exit EQQUX007 has the new extended status (PEXSTAT) as part of itsparameters set.

The Job Submission exit (installation exit 1) now allows changes to the size of JCLbeing processed. This enhancement gives users more flexibility to customize theiroperating environment.

The Operation Status Change exit (installation exit 7) has been enhanced toreceive extended status information. This means that full status information isavailable within this exit to allow more detailed processing.

The samples set has two new samples: EQQCMX01 and EQQCMX05.

New and Changed Initialization StatementsTwo initialization statements have been added to enhance the JCL variablesubstitution:

VARFAIL If VARFAIL is specified, JCL variable substitution error isbypassed for the specified types and variables are leftunresolved in the submitted JCL.

VARPROC Specifies whether or not the variables must be resolved alsoin the inline procedures.

Three initialization statements have been added to handle the OPC Data Storeoptions:

Summary of Tivoli OPC Version 2 Release 3 Enhancements xvii

FLOPTS Defines the options for the FL (Fetch Job Log) task. AController uses this statement when OPCOPTS DSTTASK(YES) is specified.

DSTOPTS Specifies options for the OPC Data Store.

DSTUTIL Specifies options for the Data Store batch utilities and theclean up subtask.

Parameters have been added to, or changed in, the JOBOPTS statement so as tohandle the new Data Store options:

JOBLOGRETRIEVALA new value DELAYEDST has been added to this keywordfor specifying that the job log is to be retrieved by means ofthe OPC Data Store.

DSTCLASS A new parameter to define the reserved held class that is tobe used by the OPC Data Store associated with this tracker.

DSTFILTER A new parameter to specify if the job-completion checker(JCC) requeues to the reserved Data Store classes only thesysouts belonging to these classes.

Parameters have been added to, or changed in, the OPCOPTS statement so as tohandle the new catalog management functions:

DSTTASK Specifies whether or not the OPC Data Store is to be used.

JCCTASK A new DST value has been added to specify if the JCCfunction is not needed, but the Data Store is used.

A parameter has been added to the OPCOPTS and the SERVOPTS statements:

ARM Activates automatic restart (via the Automatic RestartManager) of a failed OPC component.

A parameter has been added to the OPCOPTS statement for the WorkloadManager (WLM) support:

WLM Defines the WLM options, that is, the generic profile for acritical job. The profile contains the WLM service class andpolicy.

Version 2 Release 2 SummaryInstrumentation for Tivoli Global Enterprise Manager

Tivoli Global Enterprise Manager (GEM) is the industry's first solution forunifying the management of cross-platform business applications that runbusinesses and make them competitive. Tivoli GEM helps you to managestrategic applications from a unique business systems perspective, focusingyour IT resources on keeping these systems working properly andproductively. Tivoli OPC has been enhanced to support the Job SchedulingBusiness System of the Tivoli GEM Systems Management Business System.From the Tivoli GEM console, which provides a single point of management,a Tivoli OPC user has complete control of all the Tivoli OPC components,regardless of the platform on which they run. In more detail, the Tivoli OPCinstrumentation for Tivoli GEM enables you to do the following:

xviii Tivoli OPC Tracker Agents for AIX, UNIX, VMS, OS/390

� Show all the Tivoli OPC components, including controllers, stand-bycontrollers, OS/390 trackers, AS/400 tracker agents, TCP/IP connectedtracker agents.

� Show the different links between the above components. This provides,at a glance, a check on the health of the connections. For example, anOS/390 tracker might be running but might have no connection to thecontroller.

� For each component, manage a set of status parameters (monitors)specific to that component. These monitors might report the status ofsome vital OPC controller data sets such as database, current plan, andlong-term plan)

� Manage this set of monitors graphically. You can:

– Ask for value of the monitor– Be notified when the value of the monitor changes– Associate a severity (such as normal, warning, severe, or critical)

with each monitor value

� Start or stop Tivoli OPC trackers without logging them on.

� Know at a glance, in a sysplex environment, which is the active controllerand which the stand-by.

� Execute commands on Tivoli OPC components, from a single point ofcontrol, regardless of the platform and operating system used for thatcomponent.

SAP R/3 supportTivoli OPC has been enhanced to exploit the Extended Agent technology ofthe Tivoli Workload Scheduler product. This technology enables Tivoli OPCto interface with a number of third party applications that can performscheduling. By using this technology, you can now start and track a SAPR/3 job from Tivoli OPC. You can also retrieve and display the job log at theTivoli OPC controller. This function requires the Tivoli OPC Tracker Agentfor one of the following platforms:

� AIX � Digital UNIX � Sun Solaris � Windows NT � HP–UX

TCP/IP communication improvementsThe TCP/IP communication component that enables the controller tocommunicate with the TCP/IP connected tracker agents has beenrestructured to use the standard TCP/IP C–Socket interface. This changeenables Tivoli OPC for the latest OS/390 releases and provides for the useof the standard TCP/IP features, such as the KEEPALIVE option.

Catalog management enhancementsThe logic that Tivoli OPC uses when determining which catalog managementactions to perform has been extended to manage the following situations:

� Some steps in a job are not executed, but are flushed. The datasetsreferred to in those steps are ignored by the catalog managementfunction.

Summary of Tivoli OPC Version 2 Release 3 Enhancements xix

� A dataset referred to with disposition NEW in one step is also referred toin other steps. Logic to determine the action to perform in these caseshas been added to the Catalog Management function.

Dataset Delete function (EQQDELDS) improvementsThe Dataset Delete function has been enhanced to determine the correctaction when a dataset referred to with disposition NEW in one step is alsoreferred to in other steps. Logic to determine the correct action to perform inthese cases has been added to the Dataset Delete function. The DatasetDelete function has also been improved to do the following:

� Delete datasets for which an expiration date was specified.

� Issue diagnostic information when the IDCAMS DELETE command orthe DFHSM ARCHDEL command fails to delete a dataset.

Current plan occurrence limit removalThe maximum number of occurrences in the current plan has been increasedfrom 32767 to 9999999. This enhancement enables you to manage thecurrent plan more flexibly when you have large workloads.

Operations in AD limit removalYou can now define up to 255 operations in each Application Description.This enhancement provides for more flexibility in the definition of theworkload.

AD and OI consistency checkThe consistency between the Application Description and the OperatorInstruction OPC databases is now enforced by OPC. For instance, wheneveran operation is deleted the associated operator instructions is also deleted.Some usability enhancements have also been implemented in the ApplicationDescription dialogs when defining operator instructions. For instance, youcan now also access temporary operator instructions.

JCL editing from Application Description dialogsYou can now customize the Tivoli OPC dialogs so that a library managementapplication used in the customer's environment to manage the productionjobs can be invoked from the Application Description OPC dialogs, thusincreasing user productivity. New row commands have been added toinvoke such an application from the Operation List panel while working withan Application Description.

OPC Control Language toolThe OPC Control Language (OCL) tool enables you to access andmanipulate Tivoli OPC data by using a REXX-like language. Severalmacro-functions are made available that perform, in a single action, whatwould require several invocations of the OPC Program Interface functions.The OCL tool acts as an extension to the REXX language processor.Therefore, normal REXX statements can be coded together with OCLstatements. This tool runs in a batch TSO session.

Tracker agentsNew Tracker Agents are provided to control the workload on:

� Digital UNIX� OS/390 Open Edition

xx Tivoli OPC Tracker Agents for AIX, UNIX, VMS, OS/390

SmartBatch coexistenceTivoli OPC has been extensively tested to make sure that all the featurescontinue to work correctly when the production workload is under SmartBatchcontrol.

Other enhancements to functions

� EQQZSUBX 16 MB limit removal: because it is no longer necessary tomove the JCL buffer below the 16 MB line before submitting it to JES2 orJES3, this processing has been removed from Tivoli OPC.

� To improve the robustness of Tivoli OPC, the STIMERM macro is nowinvoked, wherever the STIMER macro was previously invoked.

� Tivoli OPC Job-Submit user exit (EQQUX001) has been improved byadding two new parameters: WorkstationID and ErrorCode. WhenErrorCode is set, Tivoli OPC will not submit the job.

� Tivoli OPC Operation-Status-Change user exit (EQQUX007) has beenimproved by adding the procstep name to the JOBAREA parameter.This enhancement provides for fully automated problem management.

� Debugging aids for performance problems: new statistics are nowproduced by Tivoli OPC to trace all the activities performed during thejob submission process. These statistics are especially useful when youtune your systems to maximize job throughput in Tivoli OPC. You candynamically activate and deactivate these statistics by means of newMODIFY commands.

New and changed installation exitsUser exit EQQUX001 has two new parameters:

RETCO The error codeWSNAME The workstation name of submission process

User Exit EQQUX007 has a new field in the JobArea called procedure stepname.

Changes to commandsThe following modify commands have been added:

CPQSTA Activates or deactivates CP lock statistic messagingEVELIM Sets a new value for the EVELIM keyword of the JTOPTS

statementEVESTA Activates or deactivates EVENT statistic messagingGENSTA Activates or deactivates GS task statistic messagingHB Issues a heartbeat message for an OPC controller or for all

trackers connected to that controllerJCLDBG Activates or deactivates the JCL debugging traceQUELEN Sets a new value for the QUEUELEN keyword of the JTOPTS

statementSTATIM Sets a new value for the STATIM keyword of the JTOPTS

statementSTATUS Returns status information about the OPC controller and the

tracker agents connected to it.WSASTA Activates or deactivates WSA task statistic messaging

New and changed initialization statementsThe following values have been added to the STATMSG keyword of theJTOPTS statement:

Summary of Tivoli OPC Version 2 Release 3 Enhancements xxi

EVELIM Makes customizable the event number criterion for statisticmessaging.

STATIM Uses an interval time criterion to issue statistics messaging.WSATASK Activates new statistics for WSA task.

The following new values have been added to the SUBFAILACTION keywordof the JTOPTS statement:

XC, XE and XRTo specify how OPC must handle values returned by the JobSubmission Exit (EQQUX001) for the RETCO parameter.

A new keyword has been added to the BATCHOPT statement:

MAXOCCNUM Set the maximum number of occurrences in the currentplan for the daily planning function.

A new keyword has been added to the JTOPTS statement:

MAXOCCNUM Set the maximum number of occurrences in the CurrentPlan for the dialog, ETT, Automatic Recovery and PIFfunctions.

Changes to programming interfacesThe OPC Programming Interface (PIF) has been extended as follows:

� A new subsegment has been added to the Workstation record called theWorkstation Access Method Information (WSAM).

� A new keyword, ADOICHK, has been added to the OPTIONS request toactivate the consistency check between Application Description andOperator Instruction records.

Version 2 Release 1 SummaryTivoli OPC Version 2 Release 1 became generally available in March 1997. Majorenhancements compared to OPC/ESA Release 3.1 are described in the followingsections.

Tracker agentsNew Tracker Agents are provided to control the workload on:

� Digital OpenVMS� Pyramid MIPS ABI

Shared parm library in Sysplex environmentMVS controllers and trackers can share common controller and trackerinitialization statements and started task JCLs, making it easier to installmany OPC subsystems inside an MVS/ESA sysplex environment.

Controller configuration in Sysplex environmentTivoli OPC support of MVS/ESA sysplex (base and parallel) has beenextended to enable any one of many cloned controllers on different MVSimages to switch from standby to active status. An OPC controller is startedon each member of the XCF group. The first potential controller thatbecomes active is the active controller and the others are standby controllers.If the active controller fails, a standby controller running in another MVS/ESAimage of the sysplex environment takes over automatically as the activecontroller.

xxii Tivoli OPC Tracker Agents for AIX, UNIX, VMS, OS/390

Single system imageThis enhancement allows OPC TSO dialog users and PIF users to be on adifferent MVS/ESA image from the OPC controller. Dialog users and PIFapplications can also be on MVS systems outside the sysplex where thecontroller runs. Remote communication is based on APPC.

Extended dialog filterThe dialog filter has been extended to allow more specific search argumentsand to define the interpretation of wildcard characters.

Reparsing of NOERRORNew operator commands allow the operator to dynamically update theNOERROR table using the NOERROR initialization statements defined bythe OPC PARMLIB member, and to read the statements from a member ofthe EQQPARM DD concatenated libraries. In addition a new initializationstatement allows the inclusion of NOERROR statements from members ofthe EQQPARM DD concatenated libraries.

PIF extensionProgram Interface has been greatly extended to support almost all OPCdatabase record types.

Job tracking logThis enhancement provides to user exit 11 job tracking records on which aneffective disaster recovery procedure can be based. The customer throughexit 11 receives job tracking records, and can send this data to a remotecontroller that, in case of failure of the active controller, will take over ascontroller.

GMT clock support improvementThe GMTOFFSET keyword in the OPCOPTS statement lets the user definean offset between the GMT time set in the MVS system and the actual GMTtime. The OPC controller uses the GMT clock to validate an OPC TrackerAgent trying to connect; this improvement addresses the need of some usersto have the MVS GMT clock independent of the actual GMT time, whilekeeping the ability to use Tracker Agents.

Batch command interface toolA batch command interface tool is supplied to perform most of the actionssupported by the PIF interface by means of a batch command interface.

New and changed initialization statementsInitialization statements have been added and changed in Tivoli OPC Version2. The following sections summarize the differences.

The INCLUDE statementAdded in Tivoli OPC Version 2, the INCLUDE statement lets youreduce the size of the parameter library member that contains theOPCOPTS and JTOPTS statements and reduce the associatedmaintenance activities.

Table 1. The INCLUDE Statement

Keyword Short description

NOERROR Specifies to read NOERROR informationfrom other members of the EQQPARMlibrary.

Summary of Tivoli OPC Version 2 Release 3 Enhancements xxiii

The INIT statementAdded in OPC/ESA Release 3.1, the INIT statement lets you definerun-time options for processing requests from a PIF application. Thesesettings override the values set by the INTFOPTS statement inEQQPARM. The statement is defined in a second parameter file thatis identified by the EQQYPARM DD statement in the JCL procedure ofthe PIF application. In Tivoli OPC Version 2 the LUNAME keywordhas been added.

Changes to commandsThese modify commands have been added:

NEWNOERR Requests that the NOERROR statements be reprocessed.NOERRMEM

(member) Requests that the NOERROR information beread from the specified member.

The MODIFY command has been extended to accept stop and start of theserver started tasks:

F ssname, P=SERV

S ssname, P=SERV

Changes to programming interfacesThe Programming Interface is extended as follows:

UPDATE is supported for calendars, periods, workstations, and allworkstations closed.

BROWSE and UPDATE are supported for ETT and special resources.

The LIST request has been extended to support a new keyword,MATCHTYP, to specify whether generic search arguments (* and % are tobe treated as normal characters.

A new keyword, ADVERS, has been added to the OPTIONS request, toactivate the support of AD versioning.

New and changed installation exitsTable 3 on page xxv summarizes the changes to installation exits in TivoliOPC Version 2.

Table 2. The INIT Statement

Keyword Short description

CWBASE Specifies the origin for the century windowused by the PIF application

HIGHDATE Specifies the high date presented to thePIF application in valid-to fields

LUNAME Specifies a server or controller LU namefor the PIF application

SUBSYS Identifies the Tivoli OPC subsystemcontroller

TRACE Specifies the level of trace information towrite to the diagnostic file.

xxiv Tivoli OPC Tracker Agents for AIX, UNIX, VMS, OS/390

MessagesMessages have been changed, deleted, and added in Tivoli OPC Version 2.Refer to Tivoli OPC Messages and Codes for the complete message text anddescriptions. Note that in Version 2 the message text and explanations referto the product as OPC/ESA.

Table 3. Changes to Installation Exits

Exit name Short description of change

EQQUX001 Tivoli OPC Version 2 now also supports the addressingmodes RMODE(24) and AMODE(31).

EQQUX011 Sample job tracking log write exit.

Summary of Tivoli OPC Version 2 Release 3 Enhancements xxv

xxvi Tivoli OPC Tracker Agents for AIX, UNIX, VMS, OS/390

Chapter 1. Overview

This chapter introduces the Tracker Agents and their relationship to Tivoli OPC.

If you are not familiar with the product terminology or functions, read Tivoli OPCGeneral Information.

Product FeaturesTivoli OPC is a workload management tool for:

� Managing your workload on a variety of platforms from a single point of control.

� Running jobs on the right day at the right time.

� Starting jobs in the correct order.

� Resolving complex dependencies between jobs.

� Taking into account business days and holidays across divisions, states, andcountries.

� Providing plans for the future workload to help you manage peak processing(year-end work, for example).

� Optimizing hardware resources by allocating work to specific machines.

� Initiating automatic recovery actions in the event of hardware or softwarefailure.

� Maintaining logs of work that has run—available for viewing or post-processing.

ControllersThe controller is the focal point of your configuration. It uses the information in thedatabase to determine which jobs to run, when they should run, and where theyshould run.

You need the Tivoli OPC controller if you want to run the controller on an MVSsystem. You must install at least one controller for your production systems.

You can use the controller to provide a single, consistent, control point forsubmitting and tracking your UNIX workload.

Copyright IBM Corp. 1995, 1999 1

Overview

Tracker AgentsMany installations run business applications on a variety of UNIX platforms. TivoliOPC provides Tracker Agents that can manage your workload in several operatingsystem environments.

At the time of publication, UNIX Tracker Agents for HP-UX, SunOS, Sun Solaris,| Silicon Graphics IRIX, Digital OpenVMS, Digital UNIX, AIX, and OS/390 operating

systems are available.

There is also a Tracker Agent for OS/400, and the base tracker for OS/390. OPCTracker Agents are functionally equivalent to the base OS/390 tracker, with theexception that automatic dataset cleanup and the job-completion checker (JCC)functions are not provided for non-MVS platforms. This means you can use TivoliOPC functions like automatic recovery, and automatic job tailoring for yournon-MVS workload. Refer to Tivoli OPC Planning and Scheduling the Workload fordetails about the functions provided by Tivoli OPC.

IBM is committed to provide a comprehensive workload management solution. Theavailability of Tracker Agents for other platforms will not necessarily coincide withthe availability of a new release or version of the product. Contact your IBMrepresentative to obtain a list of the operating environments that have a TrackerAgent, or send a note to one of the electronic addresses listed at the front of thisbook.

The Installation ProcessTo understand the flow of the installation process, read through this book beforeyou begin to install a Tracker Agent.

Table 4. Stages in the Installation Process

Stage Description For more information ...

1 Read the documentation that comes with thedistribution media.

See “Using the Latest Install Information” onpage 3.

2 Load the software for the Tracker Agent to thecontroller machine.

See “Loading the Tracker Agent Software toMVS” on page 5.

3 Modify the controller parameters to specify thenecessary Tracker Agents.

See “Tivoli OPC Controller InitializationStatements” on page 9.

4 Plan your installation and create user IDs. See Chapter 3, “Planning your Tracker AgentInstallation” on page 11.

5 Install and customize the Tracker Agent on eachUNIX machine.

See Chapter 4, “Installing and Customizing theTracker Agent” on page 29.

2 Tivoli OPC Tracker Agents for AIX, UNIX, VMS, OS/390

Overview

Using the Latest Install InformationThis book complements the Tivoli OPC Program Directory, which covers how toadd the materials on the IBM distribution tape to your system.

The Program Directory comes with the feature installation tape. It describes all ofthe installation materials and gives installation instructions specific to the featurenumber. If any differences exist between this book and the Program Directory, usethe information in the Program Directory.

Chapter 1. Overview 3

Chapter 2. Things to Be Done with the Tivoli OPC Controller

This chapter describes the installation tasks on MVS. These topics are included:

� Loading the Tracker Agent software to MVS� Loading the Tracker Agent enabler software to MVS� Tivoli OPC controller initialization statements.

The Tracker Agent software must be installed on an MVS system using the SystemModification Program Extended (SMP/E) program product before it can bedownloaded and installed on the UNIX machines that you want to connect to theTivoli OPC controller.

For more information on the installation procedure on MVS, refer to Tivoli OPCInstallation Guide. For more information on the Tivoli OPC initialization statements,refer to Tivoli OPC Customization and Tuning.

Loading the Tracker Agent Software to MVSTo load the Tracker Agent software to MVS, process the software distribution tapeusing SMP/E. This creates or updates the necessary disk-resident libraries on yoursystem.

Table 5 describes the datasets that are created or updated by SMP/E.

Table 5. Tracker Agent Libraries Loaded by SMP/E

DistributionSMP/Eddname

Target SMP/Eddname

Description

AEQQExxx(load)(see note)

SEQQExxx(load)(see note)

Compressed installp image (AIX), update image| (HP-UX), dstream file (Sun Solaris), tar file| (SunOS, Silicon Graphics IRIX, OS/390, Digital

UNIX), or vmsinstall file (Digital OpenVMS).

Note: Here xxx is the NLS enabling string. ENU is the English one.


Tivoli OPC Controllers

Installing the Tracker Agent Software Using SMP/EThe following example shows the JCL that transfers data sets from tape to diskusing SMP/E. If you need more information about how to use SMP/E, refer toSMP/E Reference.

SMP/E JCL example

//INSTALL JOB STATEMENT PARAMETERS

//RECEIVE EXEC SMPPROC

//SMPPTFIN DD DSN=SMPMCS,

// DISP=SHR,

// UNIT=unit,// VOL=SER=volser,// LABEL=(1,SL)

//SMPCNTL DD \

SET BOUNDARY(GLOBAL) OPTIONS(OPCOPT).

RECEIVE SYSMODS SELECT(fmid)./\

//APPLY EXEC SMPPROC

//\--------------------------------------------\

//\ TARGET LIBRARIES \

//\--------------------------------------------\

//SEQQEENU DD DSN=OPCESA.INST.SEQQEENU,DISP=SHR

//\

//\--------------------------------------------\

//\ SMP CONTROL FILE \

//\--------------------------------------------\

//SMPCNTL DD \

SET BOUNDARY(TZONOPC) OPTIONS(OPCOPT).

APPLY JCLINREPORT SELECT(fmid) RETRY(YES).

/\

//ACCEPT EXEC SMPPROC

//\

//\--------------------------------------------\

//\ DISTRIBUTION LIBRARIES \

//\--------------------------------------------\

| //AEQQEENU DD DSN=OPCESA.INST.AEQQEENU,DISP=SHR

//SMPCNTL DD \

SET BOUNDARY(DZONOPC) OPTIONS(OPCOPT).

ACCEPT JCLINREPORT SELECT(fmid) RETRY(YES).

/\

Refer to the Program Directory for information about unit type, volume serial, andTracker Agent FMID. You can use the names provided in the example or createyour own names that follow your naming conventions.



Applying Tracker Agent MaintenanceWhen you have loaded the Tracker Agent software, apply any recommendedmaintenance described in the PSP.

Loading Tracker Agent Enabler Software to MVSTo load Tivoli OPC enabler software for the Tracker Agent, process the softwaredistribution tape using SMP/E. This creates or updates the necessary disk-residentlibraries on your system. Table 6 describes the data sets that are created orupdated by SMP/E.

Table 6. Enabler Libraries Loaded by SMP/E for the Tracker Agent

DistributionSMP/Eddname

Target SMP/Eddname

Description

AEQQMOD0(object)

SEQQLMD0(load)

Load module (EQQTXTEN for AIX, EQQTXHENfor HP-UX, EQQTXSEN for Sun Solaris,EQQTXUEN for SunOS, EQQTXDEN for Digital

| OpenVMS or Digital UNIX, EQQTXPEN for Silicon| Graphics IRIX), EQQTXOED for OS/390

Chapter 2. Things to Be Done with the Tivoli OPC Controller 7


Installing the Enabler for the Tracker Agent Using SMP/EThe following example shows the JCL that transfers data sets from tape to diskusing SMP/E. You must install enabler software in a library that is accessible tothe controller. If you need more information about how to use SMP/E, refer toSMP/E Reference.

SMP/E JCL example

//INSTALL JOB STATEMENT PARAMETERS

//RECEIVE EXEC SMPPROC

//SMPPTFIN DD DSN=SMPMCS,

// DISP=SHR,

// UNIT=unit,// VOL=SER=volser,// LABEL=(1,SL)

//SMPCNTL DD \

SET BOUNDARY(GLOBAL) OPTIONS(OPCOPT).

RECEIVE SYSMODS SELECT(fmid)./\

//APPLY EXEC SMPPROC

//\

//\--------------------------------------------\

//\ TARGET LIBRARIES \

//\--------------------------------------------\

//SEQQLMDð DD DSN=OPCESA.INST.SEQQLMDð,DISP=SHR

//\

//\--------------------------------------------\

//\ SMP CONTROL FILE \

//\--------------------------------------------\

//SMPCNTL DD \

SET BOUNDARY(TZONOPC) OPTIONS(OPCOPT).

APPLY JCLINREPORT SELECT(fmid) RETRY(YES).

/\

//ACCEPT EXEC SMPPROC

//\--------------------------------------------\

//\ DISTRIBUTION LIBRARIES \

//\--------------------------------------------\

//AEQQMODð DD DSN=OPCESA.INST.AEQQMODð,DISP=SHR

//SMPCNTL DD \

SET BOUNDARY(DZONOPC) OPTIONS(OPCOPT).

ACCEPT JCLINREPORT SELECT(fmid) RETRY(YES).

/\

Refer to the Program Directory for information about unit type, volume serial, andenabler FMID information. You can use the names provided in the example orcreate your own names that follow your naming conventions.

Applying Maintenance for Tracker Agent EnablerWhen you have loaded the enabler software for the Tracker Agent, apply anyrecommended maintenance described in the PSP.



Tivoli OPC Controller Initialization StatementsThe Tivoli OPC controller ROUTOPTS initialization statement defines the TivoliOPC configuration. Update the statement to include the UNIX machines on whichyou will run work scheduled by Tivoli OPC. Review these parameters ofROUTOPTS and set values according to your configuration:

CODEPAGE(host system codepage|IBM-037)This keyword specifies the name of the host codepage. The value is used byTracker Agents running on operating environments that use the ASCIIcharacter set to convert submitted input data to ASCII. Up to 8 characters canbe defined. The default value, IBM-037, defines the EBCDIC codepage forU.S. English, Portuguese, and Canadian French.

TCP(destination,...,destination)This keyword specifies the network addresses of all TCP/IP-connected TrackerAgents able to communicate with the controller for job-tracking purposes. Eachdestination consists of a destination name and an IP address separated by acolon (name:nnn.nnn.nnn.nnn). The name is 1–8 alphanumeric characterswhere the first character is alphabetic. The IP address consists of 4 numericvalues separated by periods. Each value is in the range 1 to 255; leadingzeros are not required.

If the keyword is not defined, support for TCP/IP-connected Tracker Agents willnot be activated.

TCPIPID(TCP/IP ID|TCPIP)This keyword identifies the name of the TCP/IP address space on the MVSsystem where the controller is started. If you do not specify this keyword, thedefault value TCPIP is used.

TCPIPPORT(TCP/IP port|424)This keyword defines the TCP/IP port number used by the controller. See“Verifying Host and Service Names” on page 17 for details about port numbers.The number is 1–5 numeric characters. The controller reserved port number is424.

This keyword must be specified if the TCP keyword has been defined and thedefault port number is not used; for example, if you start more than onecontroller on the same MVS image that uses TCP/IP or if the port number isalready in use.

If you use a port number less than 1024, you must run the tracker as root.

TCPTIMEOUT(TCP/IP time-out interval|5)This keyword specifies the time interval within which the controller expects aTCP/IP-connected Tracker Agent to respond to a submit request. If theTracker Agent does not respond in two consecutive intervals, the session isterminated and workstations that reference the destination are set offline.When the tracker becomes active again, or if the time-out was caused by poornetwork response, the session will be reestablished automatically. The time-outprocessing comes into effect after the controller and the Tracker Agent havesynchronized at startup.

Specify a number of minutes from 1 to 60, or specify 0 if you do not requiretime-out processing. The default time-out interval is 5 minutes.

Chapter 2. Things to Be Done with the Tivoli OPC Controller 9


ROUTOPTS Example

ROUTOPTS TCP(MYAIX:9.52.5ð.16,YOURAIX:9.52.5ð.13) .1/ TCPIPID(TCP1) .2/ CODEPAGE(IBM-278) .3/

.1/ Tivoli OPC communicates with AIX machines running the Tracker Agent. Thecommunication method is TCP/IP. Operations that specify a computerworkstation with destination MYAIX are transmitted to IP address 9.52.50.16for execution. Operations that specify workstations with a destination ofYOURAIX are directed to IP address 9.52.50.13.

.2/ TCP1 is the name of the TCP/IP address space on the MVS system wherethe controller is started.

.3/ The codepage used on the MVS system where the controller is started isIBM-278, the codepage for Swedish and Finnish.

JTOPTS Example

JTOPTS WSFAILURE(LEAVE,REROUTE,IMMED) .1/ WSOFFLINE(LEAVE,REROUTE,IMMED) .2/ HIGHRC(ð) .3/

.1/ Actions to be taken when a workstation failure occurs.

.2/ Actions to be taken when a workstation offline situation occurs.

.3/ The highest return code generated in a job without causing the operation toabend is 0.

Note: The default is 4. For non-MVS tracker agents, specify 0. You canalso specify this return code for each operation in the AUTOMATIC OPTIONSsection of the Application Description dialog.

OPCOPTS Example

OPCOPTS CAT MGT(YES) .1/ STORELOG(ALL) .2/

.1/ Catalog management must be active.

.2/ All job logs that are retrieved immediately are stored.


Chapter 3. Planning your Tracker Agent Installation

This chapter gives you an overview of how to install, configure, and customize theTracker Agents.

The Tracker Agent is flexible and lets you define a configuration to suit your needs.If your enterprise has a large number of networked UNIX machines, you should runthe Tracker Agent on several machines. For availability, it is recommended thatyou start the tracker on at least two machines, and specify more than one host foreach job. When the first destination (workstation) is unavailable, the controller cansend the job to the next one available.

How you install the Tracker Agent depends on your configuration. If you haveNetwork File System** (NFS) or Network Information System** (NIS**) installed,you will be able to carry out most of the installation from one machine; otherwise,you will need to install the Tracker Agent on every machine where the controller willstart work.

To install you need superuser (root) authority. Depending on your network, youmay need root authority on the other servers.

If you use IBM LoadLeveler, you can run the Tracker Agent on one machine anduse LoadLeveler to distribute the workload among the networked machines. SeeAppendix D, “Using LoadLeveler” on page 107.

Certain programs for administration and operation of the Tracker Agent can only berun by the system administrator logged in with certain user IDs. Table 7 showsyou the user IDs that you need, and “Creating a User Group and User IDs” onpage 12 shows how to create them.

Even if you plan to run several instances of the Tracker Agent for the same type ofcontroller on the same machine, you should run them all under the same user ID.

Table 7. Planning for Users

Create user For ... Group Recommendedhome directory

tracker Running the tracker with Tivoli OPC opc /u/tracker


Planning

Creating a User Group and User IDsAs a security measure, the Tracker Agent requires that users belong to the opcuser group. The administrator does this by using the UNIX file-privilegemechanism, making the Tracker Agent programs executable only by users in thisgroup.

Creating the User GroupIf you are running the Network Information System (NIS), the user IDs and groupmust be created on the NIS master, and the maps rebuilt before you continue toinstall.

AIX only

To create a user group:

1. Start SMIT.2. Select Security and Users .

3. Select Groups .4. Select Add a Group .5. Fill in the relevant information. The group name must be opc.6. Press Do to create the user group.

HP-UX only

SAM can create it for you. The group name must be opc.

| Sun Solaris, SunOS, and Silicon Graphics IRIX

Create a user group with the name opc, and check that the group ID (GID) isthe same on all your platforms.

Digital UNIX

Create a user group with the name opc, by using the addgroup command.

Digital OpenVMS only

Refer to the corresponding section in the Chapter 4, “Installing and Customizingthe Tracker Agent” on page 29.

OS/390 only

Contact your system administrator to create the user group OPC and the userID TRACKER with root authority.


Planning

Creating the User ID AIX only

To create a new user ID:


3. Select Users .4. Select Add a User .5. Fill in the user name and group name as in Table 7 on page 11.6. Press Enter or select Do to create the user ID.

HP-UX only

To create a new user ID:

1. Login as root.

2. Enter the System Administration Manager with the sam command.

3. Select Users and Groups .

4. Select Users .

5. Select Actions and Add .

6. Fill in the relevant information:

Login Name As in Table 7 on page 11UID A spare ID (consistent across the network)Home Directory As in Table 7 on page 11Primary Group Name As in Table 7 on page 11Start-up Program /bin/shLogin Environment Shell (start-up program)

Sun Solaris only

You can create a user ID with admintool.

| SunOS and Silicon Graphics IRIX

You can create a user ID by editing the local /etc/passwd file if you are notusing NIS.

Digital UNIX

Create a user ID with the name tracker, by using the adduser command.



Chapter 3. Planning your Tracker Agent Installation 13

Planning

OS/390 only


Adding New Users to the opc GroupUsers who are going to work with the Tracker Agent must belong to the opc usergroup.

AIX only

To add a user ID to a group:


3. Select Users .4. Select Change / Show characteristics of a User .5. Type the user NAME.

6. Press Enter .7. Add opc to the values in the Group set field. (Values are separated by

commas.)8. Press Do to add the user to the group.

Repeat this for all users of the Tracker Agent.

HP-UX only

To add a user ID to a group:

1. Start SAM.2. Select Users and Groups .

3. Select Groups .4. Select the opc group and Actions and Modify .5. Add the users that are going to work with the Tracker Agent.

Sun Solaris only

Add a user ID to the opc group for each user of the Tracker Agent.

| SunOS, Silicon Graphics IRIX, and Digital UNIX

Add a user ID to the opc group for each user of the Tracker Agent.

The initial program will probably be /bin/sh or /bin/csh.




Planning

OS/390 only


Kernel Considerations SunOS only

Before installing the Tracker Agent, make sure that the selected kernel isgenerated with these options:

options IPCMESSAGE

options IPCSEMAPHORE

options IPCSHMEM

These options include System V IPC facilities.

Planning Your Directory LayoutsThis is the directory structure, omitting the log and temporary directories:

Table 8 (Page 1 of 2). Tracker Agent Directory Structure

Directory/File Description

/usr/lpp/tracker/EQQPARM Tracker configuration file

/usr/lpp/tracker/etc Configuration parameter files and samples

/usr/lpp/tracker/bin eqq_daemon Daemoneqqdr Data Routereqqew Event Writereqqgmeth Access method subtask (works in Digital

UNIX, HP–UX, Sun Solaris, and AIXenvironments for SAP R/3 support)

eqqgs Generic Submittoreqqgssub Generic Subtaskeqqls LoadLeveler Submittoreqqlsext LoadLeveler Tracker exiteqqclean Cleans up log files after the tracker has

terminated abnormallyeqqtr TCP Readereqqtw TCP Writereqqinit Script to initialize directorieseqqperm Script to set file permissionseqqstart Script to start the trackereqqstop Script to stop the trackereqqshow Script to show status of the trackereqqverify Utility to verify the configurationeqqcv80p Utility to convert scriptseqqfm File monitor utilityeqqview Checkpoint file view utilityeqqdelete Script to delete log fileseqqmon Tracker monitor utility


Planning

Table 8 (Page 2 of 2). Tracker Agent Directory Structure

Directory/File Description

/usr/lpp/tracker/methods Access method directory, in which youinstall R3 batch access method for SAPR/3 support

/usr/lpp/tracker/catalog Catalog message. Used by R3 batchaccess method

/usr/lpp/tracker/doc ASCII copy of this book

/usr/lpp/tracker/nls Message catalogs/msg

/prime Default (US English) message catalog/EN_US US English message catalog (not used)/loc

/iconvTable Code page converters

/usr/lpp/tracker/samples Sample directoryeop0 Sample configuration filetracker.cmd Sample LoadLeveler scriptecf Parameters used by eqqfm

Note: The naming conventions of the product and home directories are thosecommonly used in AIX systems. You may have other conventions, such as /homeor /users instead of /u, and /opt or /usr/packagename instead of /usr/lpp. Youmay need to alter the supplied sample scripts (such as eqqinit) accordingly.

If you have many systems, you can reduce your administration by planning thelayout of your directories carefully. You can run several instances of the TrackerAgent with a single copy of the binary files, and you can even use the same binaryfiles if you run the Tracker Agent with the Tivoli OPC controller.

Use the environment variable EQQHOME to point to the home directory on the localfile system. All the files in Table 8 on page 15 can be links to files on a commonfile system.

If you have many instances of the Tracker Agent, you will simplify youradministration if they all use the same binaries. For this reason, install the TrackerAgent image into the /usr/lpp/tracker directory, and then create links for thecommon files.

Besides the directories in Table 8 on page 15, the Tracker Agent uses log andtemporary directories. See “Customizing the Directories” on page 55 forrecommendations.

Notes:

1. The directory tree must be complete in order for the Tracker Agent to start.The base directory must contain all required subdirectories.

2. The iconvTable is empty for OS/390 and there is no sample LoadLeveler script.


Planning

Verifying Host and Service NamesSpecify the hostname to IP address in your /etc/hosts file.

| If NIS is running, (not for OS/390), update /etc/hosts on the NIS master. Tocheck whether NIS is running, use the ypwhich command: if it returns a hostname,you are using NIS. If ypwhich returns a message like “Domain name not bound,”you are not using NIS.

| For OS/390 only:

| Edit the /etc/rc.tcpip file. This file is processed at startup to initiate all TCP/IP| related processes. To add the Tracker Agent to the /etc/rc.tcpip file:

| 1. Login as superuser.

| 2. Edit /etc/rc.tcpip file, using as editor such as OEDIT.

| 3. At the end of the file add this section: /u/tarcker/bin/eqqstart

| 4. Also edit the .profile to set the environment variables:

| set EQQINSTANCE=muconfig

| set EQQHOME=/u/tracker

| export EQQINSTANCE

| export EQQHOME

If you have a name server (you can check its name with the nslookup command),update the host names on that machine.

à ð# The form for each entry is:

# <internet address> <official hostname> <aliases>

#

127.ð.ð.1 localhost loopback

9.52.53.254 troute taix

9.52.53.1ð thpðð testhp thp

9.52.51.34 sun4.ldg.se.ibm.com sun4

9.52.51.47 hp5.ldg.se.ibm.com hp5

9.52.52.3 m23wn12.ldg.se.ibm.com m23wn12...

á ñ

Figure 1. An Extract from the /etc/hosts File

Specify service names for the ports in your /etc/services file. Then you can use| these service names in the configuration parameter file in the directory on your| local machine where TCP/IP is installed. You can then use these service names in| the configuration parameter file instead of using port numbers. If you prefer to use| port numbers, you do not need to update the SERVICES file. If NIS is running,| (not for OS/390) update /etc/services on the NIS master. If you have a name

server, update the service names on that machine.

You must use port numbers above 1024 to avoid running the Tracker Agent withroot authority. You should use port numbers much higher than this (for example,above 5000) to avoid conflict with other programs.


Planning

| A Tivoli OPC controller needs one port, TCPIPPORT, which is also the tracker's| controller port. The default port number is 424. Each Tracker Agent needs two| ports:

| � The tracker's controller port, which is also the controller's tracker port| (TCPIPPORT).

| � The tracker's local port, which must be unique for each machine, but Tracker| Agents on different machines can have teh same local port number.

OPC Controller

UNIX Tracker 1

controller424

local5005

UNIX Tracker 2

controller424

local5006

TCPIPPORT424

Figure 2. Example Configuration Showing Port Numbers

The arrows in Figure 2 link the controllers' tracker ports with the correspondingtrackers' controller ports. Tracker Agents on the same machine must have differentlocal port numbers. Figure 3 shows suitable entries in the UNIX tracker 1 file/etc/services; Figure 4 on page 19 shows suitable entries in the UNIX tracker 2file /etc/services for this configuration.

à ð...

route 52ð/udp router routed

timed 525/udp timeserver

tempo 526/tcp newdate

courier 53ð/tcp rpc

conference 531/tcp chat

opctracker 424/tcp Tivoli OPC controller's tracker port TCPIPPORT

tracker1 5ðð5/tcp Local port for UNIX tracker 1

á ñ

Figure 3. An Extract from the /etc/services File on UNIX Tracker 1


Planning

à ð...

route 52ð/udp router routed

timed 525/udp timeserver

tempo 526/tcp newdate

courier 53ð/tcp rpc

conference 531/tcp chat

opctracker 424/tcp Tivoli OPC controller's tracker port TCPIPPORT

tracker2 5ðð6/tcp Local port for UNIX tracker 2

á ñ

Figure 4. An Extract from the /etc/services File on UNIX Tracker 2

Figure 5 shows the necessary entry in the configuration parameter file for UNIXtracker 1.

...

controller_portnr = opctracker # or controller_portnr = 424

local_portnr = tracker1 # or local_portnr = 5ðð5

Figure 5. Ports in the UNIX Tracker 1 Configuration File

Figure 6 shows the necessary entries in the configuration parameter file for UNIXtracker 2.

...

controller_portnr = opctracker # or controller_portnr = 424

local_portnr = tracker2 # or local_portnr = 5ðð6

Figure 6. Ports in the UNIX Tracker 2 Configuration File

The Tivoli OPC controller subsystem must be started with this parameter:

ROUTOPTS TCPIPPORT(424) ...

The TCP/IP /etc/services file on the controllers must also contain entries for theTracker Agent machines.

The next task is verifying the TCP/IP environment. This is described in thefollowing sections, depending on the type of operating system that you have:

1. “Verifying the TCP/IP Environment (AIX Only)”2. “Verifying the TCP/IP Environment (HP-UX Only)” on page 233. “Verifying the TCP/IP Environment (Sun Solaris and SunOS only)” on page 25

Verifying the TCP/IP Environment (AIX Only)Verify the TCP/IP setup on the Tracker Agent machine and communication with thecontroller machine before you start to install the Tracker Agent.

The bosnet.tcpip image must be installed on the Tracker Agent and controllermachines. Use the Systems Management Interface Tool (SMIT) to verify theimages installed:

1. Start SMIT.2. Select Software Maintenance and Installation .3. Select Install/Update Software .4. Select List the Installed Software .


Planning

Check for the TCP/IP install image:

à ð COMMAND STATUS

Command: OK stdout: yes stderr: no

Before command completion, additional instructions may appear below.

[MORE...153]

bosnet.tcpip.obj 3.2.

325ð bosnet Maintenance Level C U491ðð4

bsl.en_US.aix.loc 3.2.

325ð bsl Maintenance Level C U491ðð5

bsl.lat-1.fnt.loc 3.2.ð.ð

No Maintenance Level Applied.

bsl.sv_SE.aix.loc 3.2.

325ð bsl Maintenance Level C U491ðð5

bsl.sv_SE.pc.loc 3.2.

[MORE...235]

F1=Help F2=Refresh F3=Cancel F6=Command

F8=Image F9=Shell F1ð=Exit

á ñ

Note: The names may differ slightly depending on the version of the software thatyou have.

TCP/IP must be configured correctly and operational on the Tracker Agentmachine. To verify that TCP/IP is configured correctly:

1. Start SMIT.2. Select Communications Applications and Services .

3. Select TCP/IP.4. Select Minimum Configuration & Startup .

Verify these fields with your network administrator:

� Host IP Address� Network Subnet Mask

� Broadcast Address.


Planning

The panel should look similar to:

à ð

Minimum Configuration & Startup

To Delete existing configuration data, please use Further Configuration menus

Type or select values in entry fields.

Press Enter AFTER making all desired changes.

[Entry Fields]

\ HOSTNAME [m23wn12]

\ Internet ADDRESS (dotted decimal) [9.52.52.3]

Network MASK (dotted decimal) [255.255.255.ð]

\ Network INTERFACE trð

NAMESERVER

Internet ADDRESS (dotted decimal) [9.52.5ð.254]

DOMAIN Name [ldg.se.ibm.com.]

Default GATEWAY Address [9.52.52.254]

(dotted decimal or symbolic name)

RING Speed 16 +

START Now no +

F1=Help F2=Refresh F3=Cancel F4=List

F5=Undo F6=Command F7=Edit F8=Image

F9=Shell F1ð=Exit Enter=Do

á ñ

Verifying that TCP/IP Is OperationalTCP/IP must be operational on the Tracker Agent machine. To verify this, use theping command on the Tracker Agent machine, specifying the same machine as thedestination. For example, to test machine m23wn12, with IP address 9.52.52.3:

ping -c 5 9.52.52.3

OR

ping -c 5 m23wn12

Use -c 5 to specify the number of packets to be echoed.

The output should be similar to:

ldg2:/ldg/proj/opc/planit/AIX/src >> ping -c 5 m23wn12

PING m23wn12.ldg.se.ibm.com: (9.52.52.3): 56 data bytes

64 bytes from 9.52.52.3: icmp_seq=ð ttl=255 time=9 ms

64 bytes from 9.52.52.3: icmp_seq=1 ttl=255 time=6 ms





Planning

Verifying the Connection to the Controller MachineThe controller machine must be able to respond to the Tracker Agent machineacross the TCP/IP network. To test the connectivity, use ping from the TrackerAgent machine. For example,

ping -c 5 9.52.52.13

should generate output similar to:

$ ping -c 5 ldg4

PING ldg4.ldg.se.ibm.com: (9.52.52.13): 56 data bytes

64 bytes from 9.52.52.13: icmp_seq=ð ttl=59 time=79 ms





----ldg4.ldg.se.ibm.com PING Statistics----

5 packets transmitted, 5 packets received, ð% packet loss

round-trip min/avg/max = 67/7ð/79 ms

Verifying the Connection from the Controller MachineThe Tracker Agent machine must be able to respond to the controller machineacross the TCP/IP network. Check this as described in “Verifying the Connectionto the Controller Machine,” but from the controller machine. If you have problems,there might be a problem with your network setup. Consult your system or networkadministrator.

Verifying the Network RoutingVerify the route to the controller. From the Tracker Agent machine, entertraceroute controllermachine. The generated output should be similar to:

traceroute to ldg4.ldg.se.ibm.com (9.52.52.13), 3ð hops max, 4ð byte packets

1 ldgnames.ldg.se.ibm.com (9.52.5ð.254) 3 ms 28 ms 6 ms

2 ldg4.ldg.se.ibm.com (9.52.52.13) 64 ms 78 ms 134 ms

$

If the host is not found, there may be a problem with your network setup. Consultyour system or network administrator.

Continuing your installation ...

Continue reading from Chapter 4, “Installing and Customizing the Tracker Agent” on page 29.


Planning

Verifying the TCP/IP Environment (HP-UX Only)Check that you have a /system/NETINET directory.

Use these commands to check your connections:

$ hostname .1/hp5

$ /etc/ping hp5 8 1 .2/PING hp5.ldg.se.ibm.com: 8 byte packets

8 bytes from 9.52.51.47: icmp_seq=ð.

----hp5.ldg.se.ibm.com PING Statistics----


$ netstat -rn .3/Routing tables

Destination Gateway Flags Refs Use Interface

127.ð.ð.1 127.ð.ð.1 UH 4 348265 loð

default 9.52.51.3 UG 16 4185161 lanð

9.52.51 9.52.51.47 U 7 35227ð lanð

The hostname command .1/ gives you the name of your machine. Use this in theping command .2/ to give you the IP address of the machine (in this case,9.52.51.47). The netstat command .3/ should show at least one entry with anonlocal interface (where the data in the Interface column does not begin with lo).

The default gateway (9.52.51.3 in the above example) is used for destinations notlisted in the Destination column.

TCP/IP must be configured correctly and be operational on the HP-UX machine.Use the ifconfig lanð command to check the network status:

$ ifconfig lanð

lanð: flags=63<UP,BROADCAST,NOTRAILERS,RUNNING>

inet 9.52.51.47 netmask ffffffðð broadcast 9.52.51.255

The response should say that the network is UP.


Planning

Verifying the Connection to the Controller MachineThe controller machine must be able to respond to the Tracker Agent machineacross the TCP/IP network. To test the connectivity from the Tracker Agentmachine, use the ping command:

$ ping -v -o ldg2 64 2

PING ldg2.ldg.se.ibm.com: 64 byte packets

64 bytes from 9.52.5ð.2ð1: icmp_seq=ð. time=34. ms

64 bytes from 9.52.5ð.2ð1: icmp_seq=1. time=32. ms

----ldg2.ldg.se.ibm.com PING Statistics----


round-trip (ms) min/avg/max = 32/33/34

2 packets sent via:

9.52.52.3 - m23wn12.ldg.se.ibm.com

9.52.5ð.254 - ldgnames.ldg.se.ibm.com

9.52.6ð.3 - ldgkisrt.ldg.se.ibm.com

9.52.51.3 - [ name lookup failed ]

9.52.51.47 - hp5.ldg.se.ibm.com

Verifying the Connection from the Controller MachineThe Tracker Agent machine must be able to respond to the controller machineacross the TCP/IP network. Test this as described in “Verifying the Connection tothe Controller Machine,” but from the controller machine.

If you have problems, there might be a problem with your network setup. Consultyour system or network administrator.


Continue reading from Chapter 4, “Installing and Customizing the Tracker Agent” on page 29.


Planning

Verifying the TCP/IP Environment (Sun Solaris and SunOS only)

Verifying the GatewayTCP/IP must be configured correctly and operational on the Tracker Agentmachine. To verify that TCP/IP is configured correctly:

netstat -rn

The output should be similar to:

/u/tracker netstat -rn

Routing Table:

Destination Gateway Flags Ref Use Interface

-------------------- -------------------- ----- ----- ------ ---------

127.ð.ð.1 127.ð.ð.1 UH ð 976265 loð

9.52.51.ð 9.52.51.49 U 3 92477 leð

224.ð.ð.ð 9.52.51.49 U 3 ð leð

default 9.52.51.3 UG ð 771ð3

The default gateway (9.52.51.3 in the above example) is used for destinations notlisted in the Destination column. Verify this with your network administrator.

Verifying that TCP/IP Is Operational� To verify that TCP/IP is operational:

ifconfig leð

Where leð is the interface of the Tracker Agent machine. You can use thenetstat command to find the interface of your machine. If TCP/IP isoperational, your output will be similar to:

leð: flags=63<UP,BROADCAST,NOTRAILERS,RUNNING>inet 9.52.51.34 netmask ffffffðð broadcast 9.52.51.255

� To verify the IP address:

ping 9.52.51.34

Where 9.52.51.34 is the IP address of the Tracker Agent machine. If TCP/IPis operational, your output will be similar to:

9.52.51.34 is alive

� To verify that the local name server is operational:

ping sun4

Where sun4 is the local name of the Tracker Agent machine. You can use thehostname command to find the name of your machine.

If TCP/IP is operational, your output will be similar to:

sun4.ldg.se.ibm.com is alive


Planning

Verifying the Connection to the Controller MachineThe controller machine must be able to respond to the Tracker Agent machineacross the TCP/IP network. To test the connectivity from the Tracker Agentmachine, use the ping controllermachine command. For example, ping ldg2

should generate output similar to:

ldg2.ldg.se.ibm.com is alive

Verifying the Connection from the Controller MachineThe Tracker Agent machine must be able to respond to the controller machineacross the TCP/IP network. Test this as described in “Verifying the Connection tothe Controller Machine,” but from the controller machine.

Verifying the Network RoutingVerify the route to the controller machine. From the Tracker Agent machine, entertraceroute controllermachine. You must have root authority to use this command.The generated output should be similar to:

sun4# /usr/local/bin/traceroute ldg2

traceroute to ldg2ldg.se.ibm.com (9.52.5ð.2ð1), 3ð hops max, 4ð byte

1 ldgenet.ldg.se.ibm.com (9.52.51.3) 3 ms 2 ms 2 ms

2 ldgnames.ldg.se.ibm.com (9.52.5ð.254) 5 ms 5 ms 5 ms

3 ldgmvs1.ldg.se.ibm.com (9.52.5ð.2ð1) 76 ms 28 ms 28 ms

sun4#

If the controller is not found, there might be a problem with your network setup.Consult your system or network administrator.


Planning

Verifying the TCP/IP Environment (OS/390 only)Contact your system administrator to verify that TCP/IP is installed, then check thatit is running.

Verifying that TCP/IP Is OperationalVerify that the TCP/IP procedure is active. If the procedure has not started, contactyour system administrator.

Verifying the Connection to the Controller MachineTo test the connectivity, use the TSO ping command on the OS/390 Open EditionTracker Agent machine.

Verifying the Connection from the Controller MachineTo test the connectivity, use the TSO ping command on the OPC controllermachine.


Chapter 4. Installing and Customizing the Tracker Agent

Your next task is to download the binary install image to the Tracker Agentmachine. Otherwise, continue from “Creating Links between the Directories” onpage 48.

Unless otherwise specified, all steps must be performed as the superuser (root). Ifyou do not have the root password, contact your systems support area.

Table 9. The Tracker Agent Installation Process

Stage Description For moreinformation ...

1 Verify the TCP/IP connections. See page 19.

2 Check host and service names. See page 17.

3 Download the software if the Tracker Agent machinecannot access the software.

See page 29.

4 Create links between directories and files. See page 48.

5 Customize the configuration parameter file. See page 48.

6 Create the log and temporary directories. See page 55.

7 Customize file permissions, if required. See page 56.

Download the Tracker Agent Files from the Controller SystemSkip this step if the Tracker Agent machine shares a file system with the controllermachine.

The Tracker Agent files must be transferred from the controller host. Any filetransfer program can be used. It is recommended that you use the TCP/IP FTPprogram because this is a good way to test that the TCP/IP connection worksproperly (not applicable for OS/390).

Note: For details of the procedure for applying Tracker PTFs, see Appendix N,“Applying Tracker Maintenance on Non-AIX Machines” on page 127.

AIX OnlyYou can send the Tracker Agent files to the Tracker Agent machine, or you canreceive them from the controller machine.


Installation

To send files to the Tracker Agent machine, enter these commands on thecontroller machine (from the TSO command line if using MVS):

ftp aix1

user root

passwd xxxxx

binary

cd /usr/sys/inst.images

put 'OPCESA.INST.SEQQEENU(EQQTXAIX)' tracker.image.aix

quit

To receive files from the controller machine, enter these commands on the TrackerAgent machine:

cd /usr/sys/inst.images

ftp control

user opc

passwd xxxxx

binary

get 'OPCESA.INST.SEQQEENU(EQQTXAIX)' tracker.image.aix

quit

In these examples, the AIX machine is known as aix1, and the controller machineas control.

You can receive the image to any directory. /usr/sys/inst.images is therecommended and default directory. tracker.image is an installp image.

Using SMIT to Install the Required FeaturesThis section describes how to install the Tracker Agent using the SMIT installfacility. Consult your administrator for assistance if you have not previously usedthis function. There is more than one way to perform this task. For example, youcan install all the features from the installation media, or you can copy the softwareto a hard disk for future installation.

When installing the different features of the Tracker Agent, consider these points:

� The programs can be installed on one machine only, if:

– The file system is network mounted with NFS.– The installation directory is exported.– The remote clients NFS-mount the install directory.

� These network setups must be performed on every machine that uses theTracker Agent.


Installation

Updating .toc File for First Install: If this is the first time the Tracker Agent hasbeen installed on the machine, you must update the SMIT .toc file with the trackerinformation. To update your .toc file, enter:

inutoc /usr/sys/inst.images

If the Tracker Agent image is stored in another directory, use that directory insteadof /usr/sys/inst.images.

Reinstalling the Tracker Agent: If the Tracker Agent has previously beeninstalled, set these values on the Install Software Products at Latest AvailableLevel SMIT panel:

Install Prerequisite Software: no.

Overwrite existing version: yes.

Depending on the level of SMIT, you might have to remove all Tracker Agent filesfrom the system when re-installing. To remove the old files:

cd /usr/lpp

rm –rf tracker

Use SMIT to Install ImagesNote: The steps and panel names may vary slightly depending on the version ofSMIT that you have. The sequence below is for a Version 3 system.

To use SMIT to install the required features either from the installation media or thehard disk:

1. Start SMIT.

2. Select Software Installation & Maintenance .

3. Select Install / Update Software .

4. Select Install Software Products at Latest Available Level .

5. Enter the device or directory name where the installation media resides. Enterthe full path to the directory containing the file that was downloaded from thecontroller machine, for example,

/usr/sys/inst.images

If the installation is being performed from tape, enter the device name, forexample,

/dev/rmtð

Chapter 4. Installing and Customizing the Tracker Agent 31

Installation

6. Position the pointer on the line SOFTWARE to install , and press F4.

à ðInstall Software Products at Latest Available Level



[Entry Fields]

\ INPUT device / directory for software /usr/sys/inst.images

\ SOFTWARE to install [] +

Automatically install PREREQUISITE software? yes +

COMMIT software? yes +

SAVE replaced files? no +

VERIFY Software? no +

EXTEND file systems if space needed? yes +

REMOVE input file after installation? no +

OVERWRITE existing version? no +

ALTERNATE save directory []

F1=Help F2=Refresh F3=Cancel F4=List

F5=Reset F6=Command F7=Edit F8=Image

F9=Shell F1ð=Exit Enter=Do

á ñ

7. Select the required features from the list, position the pointer beside thepackage, and press F7.

à ðInstall Software at Latest Available Level



[Entry Fields]

\ INPUT device / directory for software /ldg/proj/opc/trackit/>

\ SOFTWARE to install [all] +

Automatically install PREREQUISITE software? yes +

COMMIT software? yes +

SAVE replaced files? no +

\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

\ SOFTWARE to install \

\ \

\ Move cursor to desired item and press F7. \

\ ONE OR MORE items can be selected. \

\ Press Enter AFTER making all selections. \

\ \

\ > 2.2.ð.ð tracker ALL \

\ 2.2.ð.ð tracker.obj \

\ \

\ F1=Help F2=Refresh F3=Cancel \

\ F7=Select F8=Image F1ð=Exit \

\ Enter=Do \

\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

á ñ

8. Press Enter or select OK.


Installation

9. Select Do to start the installation.

When the Tracker Agent install is complete you should see a panel similar to:

à ð COMMAND STATUS

Command: OK stdout: yes stderr: no

Before command completion, additional instructions may appear below.

[TOP]

installp -qacFNXd/ldg/proj/opc/trackit/images \

-f {File Containing Software} 2>&1

Contents of {File Containing Software}:

tracker 2.2.ð.ð.all

installp: Performing requisite checking.

(This may take several minutes.)

installp: The following software products will be applied:

tracker.obj at level 2.2.ð.ð

installp: Requisite checking complete.

[MORE...56]

F1=Help F2=Refresh F3=Cancel F6=Command

F8=Image F9=Shell F1ð=Exit

á ñ


Continue reading from “Creating Links between the Directories” on page 48.


Installation

HP-UX OnlyTo send files to the Tracker Agent machine, enter these commands on thecontroller machine (from the TSO command line if using MVS):

ftp hp5

user root

passwd xxxxx

binary

cd /usr/lpp

put 'OPCESA.INST.SEQQEENU(EQQTXHP1)' tracker.image.hp1.Z

quit

or to receive files from the controller machine, enter this series of commands on theHP-UX machine:

cd /usr/lpp

ftp control

user opc

passwd xxxxx

binary

get 'OPCESA.INST.SEQQEENU(EQQTXHP1)' tracker.image.hp1.Z

quit

In these examples, the HP-UX machine is known as hp5, and the controllermachine as control.

You can receive the image to any directory. /usr/lpp is the recommended anddefault directory. The file is packaged in compressed format. Uncompress itbefore you continue with the installation process. To uncompress the file, enter:

uncompress tracker.image.hp1.Z

The file name is changed to tracker.image.hp, which now contains anuncompressed update image.

Using Swinstall to Install the Required FeaturesThis section describes how to install the Tracker Agent on HP-UX V10 or HP-UXV11, using the swinstall tool. Consult your administrator for assistance if you havenot previously used this tool. When you have loaded and uncompressed the imagefile, use the swinstall to process it.

Note that the OPC member to be loaded, for the Tracker Agent for HP-UX V10 orHP-UX V11, is EQQTXHP1.

To run the swinstall tool:

1. If the system is not in single-user mode, enter:

$ /usr/sbin/shutdown

2. If the workstation is not already in graphical mode, restart VUE on aworkstation console, to run swinstall in graphical mode:

$ /usr/vuew/bin/vuerc

3. If the swagentd daemon if it is not already running, enter:

$ /usr/sbin/swagentd


Installation

4. Run swinstall:

$ /usr/sbin/swinstall

5. Specify, in the path field, the source of the software to be loaded:

$ /usr/lpp/tracker/tracker.image.hp1

When the tracker product name is shown in the window, you can double-clickon it to see its content.

6. On the Actions menu, choose Mark for Install .

7. Choose Install (analysis) .

8. When installation is complete, check that the correct tracker directories havebeen created with the correct owning users/group. To do this, enter thecommand:

ls -las

9. Make sure that the owning user (.1/) is tracker and that the group (.2/) is opc.This association of owning user entries and group entries should happenautomatically.

| Now from a root userid, set EQQHOME to /usr/lpp/tracker and run the| /usr/lpp/tracker/bin/eqqperm script to set file permissions.

After this, check the /usr/lpp/tracker directory again to ensure that the useridand groupid are correct. To do this:

ls -la

This is an extract from the output:

| $ cd tracker

| /usr/lpp/tracker

| $ ls -lg .1/ .2/| -rw-rw-r-- 1 tracker opc 446 Dec 8 1ð:46 EQQPARM

| drwxrwxr-x 2 tracker opc 512 Dec 1 ð6:38 bin/

| drwxrwxr-x 4 tracker opc 512 Dec 1 ð3:44 doc/

| drwxrwxrwx 2 tracker opc 512 Dec 8 12:ð1 log/

| drwxrwxrwx 2 tracker opc 512 Dec 8 12:ð1 etc/

| drwxrwxrwx 2 tracker opc 512 Dec 8 12:ð1 nls/

| drwxrwxrwx 2 tracker opc 512 Dec 8 12:ð1 samples/

| drwxrwxrwx 2 tracker opc 512 Dec 8 12:ð1 tmp/




Installation

Sun Solaris OnlyTo send files to the Tracker Agent machine, enter these commands on thecontroller machine (from the TSO command line if using MVS):

ftp sun2

user yourid

passwd xxxxx

binary

cd /usr/lpp

put 'OPCESA.INST.SEQQEENU(EQQTXSOL)' tracker.image.sol.Z

quit

Receiving the Files from the Controller MachineTo receive files from the controller machine, enter this series of commands on theTracker Agent machine:

cd /usr/lpp

ftp control (where control is the name of the controller machine

user yourid

passwd xxxxx

binary

get 'OPCESA.INST.SEQQEENU(EQQTXSOL)' tracker.image.sol.Z

quit

The file is packaged in compressed format. Uncompress it before you continuewith the installation process. To uncompress the file you should be in the/usr/lpp/ directory and enter:

uncompress tracker.image.sol.Z

When the file is uncompressed, a file called tracker.image.sol is placed in the/usr/lpp/ directory.

Installing the Required FeaturesThis section describes how to install the Tracker Agent. There is more than oneway to perform this task. For example, you can install all the features from theinstallation media, or you can copy the software to a hard disk for future installation.

When installing the features of the Tracker Agent, consider these points:





Installation

Installing the Tracker for the First Time: If this is the first time you haveinstalled the Tracker Agent, use this command to install the files:

pkgadd -d /usr/lpp/tracker.image.sol

After the files have been installed, check the usr/lpp/tracker directory to see thatthe files are there. To do this:

pkginfo -l tracker

An extract of the output is shown in Figure 7.

à ð/u/tracker$ pkginfo -l tracker

PKGINST: tracker

NAME: OPC Tracker Agent for Solaris

CATEGORY: application

ARCH: sparc

| VERSION: 2.3

BASEDIR: /usr/lpp

VENDOR: IBM Rome Tivoli Lab

DESC: OPC Tracker Agent for Solaris

INSTDATE: Jul ð2 1998 ð8:ð8

STATUS: completely installed

| FILES: 1ð9 installed pathnames

| 15 directories

| 25 executables

| 4 setuid/setgid executables

| 5ð52 blocks used (approx)

á ñ

Figure 7. Checking the Tracker Files on Solaris

Reinstalling the Tracker Agent: If the Tracker Agent has previously beeninstalled, you should remove Tracker Agent files from the system beforere-installing.

To check if the Tracker Agent has been installed:

pkginfo -l tracker

To remove the Tracker Agent package:

pkgrm tracker

Refer to Solaris documentation for more information about installing packages.




Installation

SunOS OnlyTo send files to the Tracker Agent machine, enter these commands on thecontroller machine (from the TSO command line if using MVS):

ftp sun4

user yourid

passwd xxxxx

binary

cd /usr/lpp

put 'OPCESA.INST.SEQQEENU(EQQTXSUN)' tracker.tar.sun.Z

quit

Receiving the Files from MVSTo receive files from the MVS machine, enter this series of commands on theTracker Agent machine:

cd /usr/lpp


user yourid

passwd xxxxx

binary

get 'OPCESA.INST.SEQQEENU(EQQTXSUN)' tracker.tar.sun.Z

quit

The file is packaged in compressed format. Uncompress it before you continuewith the installation process. To uncompress the file you should be in the /usr/lpp

directory and enter:

uncompress tracker.tar.sun.Z

When the file is uncompressed, a file called tracker.tar is placed in the /usr/lppdirectory. To verify the contents of the file:

tar tvf /usr/lpp/tracker.tar.sun







| tar xvof usr/lpp/tracker.tar.sun

After the files have been extracted from the tar file, check the usr/lpp/trackerdirectory to see that the files are there. To do this:

ls -lg


Installation


| After this, check the /usr/lpp/tracker directory again to ensure that the userid andgroupid are correct. To do this:

ls -la


à ð$ cd tracker

/usr/lpp/tracker

$ ls -lg .1/ .2/-rw-rw-r-- 1 tracker opc 446 Dec 8 1ð:46 EQQPARM

drwxr-xr-x 2 tracker opc 512 Dec 1 ð6:38 bin/

| -rw-r--r-- 1 tracker opc 512 Dec 1 ð6:38 copyright/

drwxr-xr-x 4 tracker opc 512 Dec 1 ð3:44 doc/

drwxr-xr-x 2 tracker opc 512 Dec 8 12:ð1 log/

drwxr-xr-x 2 tracker opc 512 Dec 8 12:ð1 etc/

drwxr-xr-x 2 tracker opc 512 Dec 8 12:ð1 nls/

drwxr-xr-x 2 tracker opc 512 Dec 8 12:ð1 samples/

drwxr-xr-x 2 tracker opc 512 Dec 8 12:ð1 tmp/

á ñ

Figure 8. Checking the Tracker Files on SunOS

Check that the owning user (.1/) is tracker, and that the group (.2/) is opc.

Reinstalling the Tracker Agent: If the Tracker Agent has previously beeninstalled, you might have to remove all Tracker Agent files from the system whenre-installing. To remove the old files:

cd /usr/lpp

rm –rf tracker


Installation

| SGI IRIX OnlyTo send files to the Tracker Agent machine, enter these commands on thecontroller machine (from the TSO command line if using MVS):

ftp mips4

user yourid

passwd xxxxx

binary

cd /usr/lpp

put 'OPCESA.INST.SEQQEENU(EQQTXPYR)' tracker.tar.mips.Z

quit


cd /usr/lpp


user yourid

passwd xxxxx

binary

get 'OPCESA.INST.SEQQEENU(EQQTXPYR)' tracker.tar.mips.Z

quit



uncompress tracker.tar.mips.Z


tar tvf /usr/lpp/tracker.tar.mips







| tar xvof usr/lpp/tracker.tar.mips



Installation

After this, check the /usr/lpp/tracker directory again to ensure that the userid andgroupid are correct. To do this:

ls -la


à ð$ cd tracker

/usr/lpp/tracker

$ ls -lg .1/ .2/-rw-rw-r-- 1 tracker opc 446 Dec 8 1ð:46 EQQPARM

drwxrwxr-x 2 tracker opc 512 Dec 1 ð6:38 bin/

| -rw-r--r-- 1 tracker opc 512 Dec 1 ð6:38 copyright/

drwxrwxr-x 4 tracker opc 512 Dec 1 ð3:44 doc/

drwxrwxrwx 2 tracker opc 512 Dec 8 12:ð1 log/

drwxrwxrwx 2 tracker opc 512 Dec 8 12:ð1 etc/

drwxrwxrwx 2 tracker opc 512 Dec 8 12:ð1 nls/

drwxrwxrwx 2 tracker opc 512 Dec 8 12:ð1 samples/

drwxrwxrwx 2 tracker opc 512 Dec 8 12:ð1 tmp/

á ñ

Figure 9. Checking the Tracker Files on SGI IRIX



cd /usr/lpp

rm –rf tracker

Note: In some environments it may be necessary to set the variable SYMBTEST| before starting the tracker. For example, in a Silicon Graphics IRIX system:

export SYMBTEST=-h


Installation

Digital UNIX OnlyTo send files to the Tracker Agent machine, enter these commands on thecontroller machine (from the TSO command line if using MVS):

ftp decunix4

user yourid

passwd xxxxx

binary

cd /usr/lpp

put 'OPCESA.INST.SEQQEENU(EQQTXDUX)' tracker.tar.decunix.Z

quit


cd /usr/lpp


user yourid

passwd xxxxx

binary

get 'OPCESA.INST.SEQQEENU(EQQTXDUX)' tracker.tar.decunix.Z

quit



uncompress tracker.tar.decunix.Z


tar tvf /usr/lpp/tracker.tar.decunix







| tar xvof usr/lpp/tracker.tar.decunix

After the files have been extracted from the tar file, check the usr/lpp/trackerdirectory to see that the files are there. To do this:

ls -la


Installation


After this, check the /usr/lpp/tracker directory again to ensure that the userid andgroupid are correct. To do this:

ls -la


à ð$ cd tracker

/usr/lpp/tracker

$ ls -lg .1/ .2/| -rw-rw-r-- 1 tracker opc 2ðð3 May 15 1998 EQQPARM

| drwxr-xr-x 2 tracker opc 512 Sep 13 11:ð1 bin

| drwxr-xr-x 2 tracker opc 512 Feb 24 1999 catalog

| -rw-rw-r-- 1 tracker opc 257 May 15 1998 copyright

| drwxr-xrwx 2 tracker opc 512 May 15 1998 doc

| drwxr-xrwx 2 tracker opc 512 Sep 22 14:2ð etc

| drwxr-xrwx 2 tracker opc 512 Sep 22 14:17 log

| drwxr-xrwx 2 tracker opc 512 Feb 24 1999 methods

| drwxr-xrwx 4 tracker opc 512 May 15 1998 nls

| drwxr-xrwx 2 tracker opc 512 Mar 15 1999 samples

| drwxr-xrwx 3 tracker opc 512 May 15 1998 tmp

á ñ

Figure 10. Checking the Tracker Files on Digital UNIX



cd /usr/lpp

rm –rf tracker


Installation

Digital OpenVMS VAX/Alpha Only| To install the Tracker Agent, create a temporary directory to put the zip file, for| example:

| create/dir dka3ðð:[ðððððð.u.kit_install]

| set def dka3ðð:[ðððððð.u.kit_install]

To send files to the Tracker Agent machine, enter these commands on thecontroller machine (from the TSO command line if using MVS):

ftp dec4

user yourid

passwd xxxxx

binary

| cd dka3ðð:[ðððððð.u.kit_install]

put 'OPCESA.INST.SEQQEENU(EQQTXDEC)' TRACKER_IMAGE_VMS.ZIP

quit


| set def dka3ðð:[ðððððð.u.kit_install]


user yourid

passwd xxxxx

binary

get 'OPCESA.INST.SEQQEENU(EQQTXDEC)' TRACKER_IMAGE_VMS.ZIP

quit

The file is packaged in compressed format. Uncompress it before you continue withthe installation process. To uncompress the file you should be in the /usr/lpp


unzip "–V" TRACKER_IMAGE_VMS.ZIP

by using unzip

When the file is uncompressed, a file called TRACKER_IMAGE_VMS is placed inthe /pub/archiving directory.


When installing the features of the Tracker Agent on DEC platforms (VAX andALPHA), consider this point:

� The package contains the following three backup files:

| – TRK020.A| – TRK020.B| – TRK020.C

| The file TRK020.A contains a script, which you can use to restore from TRK020.B| and TRK020.C. TRK020.B contains the DEC VAX files; TRK020.C contains the| DEC Alpha files. To proceed with the installation, you need a SYSTEM account.


Installation

Installing the Tracker for the First Time: If this is the first time you have| installed the Tracker Agent, after the login, using the ftp command, copy the three| TRK020.* files in a temporary directory.

1. Choose a unique UIC for the TRACKER to be created.

2. Verify the user UIC in the system; enter the following OpenVMS commands onthe DLC command line:

$ set def sys$system

$ run authorize

UAF> show /identifier/user=[\,\](check the UICs and choose a new one to be used in the installation procedure)UAF> exit

3. Now enter the following DCL commands:

$ set def sys$update

(to set the current directory)@vmsinstal

(to start the installation procedure)

4. Now follow these steps:

a. At the prompt:

* Where will the distribution volumes be mounted:

specify the file path (for example, dka3ðð:[ðððððð.u.kit_install])

b. At the prompt:

* Enter the product to be processed for first distribution volume set.

| specify the installing product: TRKð2ð

c. At the prompt:

* Enter installation options you wish to use (none)

press Enter .

The following message is displayed:

The following products will be processed:

| - TRK V2.ð

| Beginning installation of TRK V2.ð at 18:4ð

5. Create a UIC for the new TRACKER user:

a. At the prompt: * Enter unique UIC for the TRACKER USER [[450,350]]

do one of the following:

� Press Enter to accept the default UIC.

� Specify a UIC for the new TRACKER user you are creating, in theformat [[n.m]] and press Enter .

b. At the prompt:

* Enter device for TRACKER's user directory [OPCDEC$DKA300:]]:

specify the device on which to install the package.

The default is OPCDEC$DKA300:. Either press Enter to accept it, orspecify another device and press Enter .


Installation

EQQDISK The name of the disk that contains the Tracker Agent homedirectory

EQQINSTANCE The name of the Tracker Agent configuration fileEQQHOME The home directory, UNIX style

| EQQBIN

3. Create and customize the configuration file referred to by EQQINSTANCE in$EQQHOME/etc.

| 4. Execute the setpath file.

| 5. Run tracker commands, such as eqqverify, eqqstart, and eqqmon.


Installation

OS/390 Open Edition OnlyTo send Tracker Agent files from the Tivoli OPC controller to the OS/390 OpenEdition Tracker Agent, enter the following command from the TSO command line:

| OPUT 'OPCESA.INST.SEQQEENU(EQQTXOED)' /usr/lpp/tracker.oe.tar.Z' BINARY

This command copies the data set containing the archive file to the memberEQQTXOED in the specified directory in the file system.

From the TSO command line, proceed to the shell using the OMVS command andmove to the /usr/lpp directory.

The archive file tracker.oe.tar.Z is packaged in compressed format. Uncompress itby entering the shell command:

/usr/lpp:>uncompress tracker.oe.tar.Z

The file name is changed to tracker.oe.tar.

If this is the first installation, create the tracker directory under the /usr/lpp directorywith superuser authority.

If, instead, you are reinstalling the tracker agent, then remove the old files from thesystem with the command:

/usr/lpp:>rm -rf tracker

| Then extract into the /usr/lpp directory the tracker agent files from the package:

| usr/lpp:>tar -xvof tracker.oe.tar


Attention: The tracker for OS/390 Open Edition cannot reach the same level ofperformance as the tracker for AIX.

Creating Links between the DirectoriesThis step must be performed for all platforms except AIX and Digital OpenVMS.

If you have standard directory tree naming conventions, you can create the| required links using the sample script eqqinit. Ensure that EQQHOME is set to| your home directory; if not see “Home Directory” on page 49 for details.

/usr/lpp/tracker/bin/eqqinit -tracker

Run the script from the tracker user ID. See “eqqinit” on page 97 for further detailsof this sample script. Use the -tracker parameter to create the links.

Customizing the Configuration Parameter FileUse the configuration parameter file to specify the configuration parameters for theTracker Agent. Use a sample file in the samples directory to create your own

| configuration file. Edit the configuration file using an editor such as vi, ISHELL, or| OEDIT.


Installation

Home DirectoryYou normally start the Tracker Agent under the tracker user ID, and have/u/tracker as the home directory.

You are strongly recommended to set two environment variables that tell theTracker Agent binaries where the files are:

� EQQHOME variable � EQQINSTANCE variable.

Setting the EQQHOME VariableThis variable is the name of the home directory. To check the home directory,enter the following commands as the user ID under which the Tracker Agent runs:

cd

pwd

To set the environment variable EQQHOME in the Korn Shell (ksh):

export EQQHOME=/u/tracker

To set the environment variable EQQHOME in the C Shell (csh):

setenv EQQHOME /u/tracker

To set the environment variable EQQHOME in the Bourne Shell (sh):

EQQHOME=/u/tracker

export $EQQHOME

These examples assume that the home directory is /u/tracker.

$EQQHOME points to the base tree structure shown in Table 8 on page 15.

In the remainder of this book, the home directory is referred to as $EQQHOME. If/u/tracker is the home directory, for example, $EQQHOME/etc refers to/u/tracker/etc.

Setting the EQQINSTANCE VariableThis variable is the name of the configuration parameter file. Set it in the sameway as for the EQQHOME variable:

EQQINSTANCE=myconfig.file

export EQQINSTANCE

You can also specify the name of the configuration file using the -f flag on theeqqstart script or when you start the Tracker Agent directly. The -f flag takesprecedence over the EQQINSTANCE variable. See “Starting the Tracker Agent” onpage 62 for more information on starting the Tracker Agent.

Put the configuration parameter file in the $EQQHOME/etc directory. Copy theconfiguration file to each machine where a Tracker Agent is installed, ensuring thatthe values are consistent.


Installation

Updating the PATH VariableAdd $EQQHOME/bin to the PATH environment variable.

Sun Solaris only

Add /usr/ucb to the PATH environment variable.

Updating the Configuration Parameter FileThe general syntax rules for the statements are:

� All keywords must be lowercase.

� All user-specified values must be in the format shown.

� A # sign can be used for comments.

� Blank lines are treated as comments.

� Unknown or invalid keywords are ignored.

� Each keyword must begin on a separate line.

� If a keyword definition cannot fit on a single line, use a back slash (\) as acontinuation character.

� If you code a keyword more than once, the last value is used.

� Keyword values can include:

– Previously defined configuration or environment variables ($variable)– Home directories in the format ∼user– The logged-on-user home directory (∼ on its own).– Service names, for port numbers.– Host names, for IP addresses.


Installation

┌ ┐─,───────────────────────55─ ─controller_ipaddr──=─ ───

6┴─ ──controller_IP_Address─ ────────────────────────5%

55─ ──┬ ┬────────────────────────────────────────── ─────────────────────────────5%└ ┘──controller_portnr=controller_Port_Number

55─ ──┬ ┬───────────────────────── ──────────────────────────────────────────────5%└ ┘──local_ipaddr=IP_Address

55─ ──┬ ┬────────────────────────── ─────────────────────────────────────────────5%└ ┘──local_portnr=Port_Number

55─ ──┬ ┬──────────────────────── ───────────────────────────────────────────────5%└ ┘──eqqshell=default_shell

55─ ──┬ ┬─────────────────── ────────────────────────────────────────────────────5%└ ┘──eqqfilespace=nnnn

55─ ──┬ ┬────────────── ─────────────────────────────────────────────────────────5%└ ┘──eqqmsgq=nnnn

55─ ──┬ ┬──────────────── ───────────────────────────────────────────────────────5%└ ┘──eqqshmkey=nnnn

55─ ──┬ ┬──────────────────── ───────────────────────────────────────────────────5%└ ┘──event_logsize=nnnn

55─ ──┬ ┬───────────────────────────── ──────────────────────────────────────────5%└ ┘──ew_check_file=event_logfile

55─ ──┬ ┬─────────────────────────────── ────────────────────────────────────────5%└ ┘──local_codepage=local_codepage

55─ ──┬ ┬───────────── ──────────────────────────────────────────────────────────5%└ ┘──ipc_base=ID

55─ ──┬ ┬──────────────────────────────── ───────────────────────────────────────5% │ │┌ ┐─NO,DELETE────────

└ ┘──job_log= ──┼ ┼─NO,KEEP────────── ├ ┤─IMMEDIATE,KEEP─── ├ ┤─IMMEDIATE,DELETE─ ├ ┤─DELAYED,KEEP───── └ ┘─DELAYED,DELETE───

Figure 11 (Part 1 of 2). Keyword Syntax


Installation

55─ ──┬ ┬───────────────────── ──────────────────────────────────────────────────5%| └ ┘──controller_type=opc

55─ ──┬ ┬───────────────────── ──────────────────────────────────────────────────5% │ │┌ ┐─ð─

└ ┘──trace_level= ──┼ ┼─1─ ├ ┤─2─ ├ ┤─3─ └ ┘─4─

55─ ──┬ ┬─────────────────── ────────────────────────────────────────────────────5%└ ┘──num_submittors=nn

55─ ──┬ ┬─────────────────────────── ────────────────────────────────────────────5%└ ┘──subnn_workstation_id=wsID

55─ ──┬ ┬──────────────────────────── ───────────────────────────────────────────5%└ ┘──subnn_check_file=checkfile

55─ ──┬ ┬──────────────────────── ───────────────────────────────────────────────5% │ │┌ ┐─GS─

└ ┘──subnn_subtype= ──┴ ┴─LS─

55─ ──┬ ┬────────────────── ─────────────────────────────────────────────────────5%└ ┘──xxxxx_retry=nnnn

Figure 11 (Part 2 of 2). Keyword Syntax

Keywordscontroller_ipaddr= controller_IP_Address

Specifies the IP addresses for the systems where the controllers are running.There can be up to 10 addresses, each in the format nnn.nnn.nnn.nnn, wherennn is in the range 1-254, or a host name. It is a required keyword: there is nodefault value. Separate the addresses with commas.

The Tracker Agent tries the first address in the list at startup. If it is unable tomake a connection, it tries the next address in the list, and so on. Only onecontroller can be connected at any one time.

controller_portnr= controller_Port_NumberSpecifies the port number that the Tracker Agent TCP-Writer connects to, or aservices name. See “Verifying Host and Service Names” on page 17 for helpon defining ports.

local_ipaddr= IP_AddressSpecifies the IP address for the machine where the Tracker Agent is running.It must be in the format nnn.nnn.nnn.nnn, where nnn is in the range 1-254, oran environment variable such as $HOST, or a host name.

local_portnr= Port_NumberSpecifies the port number that the Tracker Agent TCP-Reader binds a socketto. See “Verifying Host and Service Names” on page 17 for help on definingports.

eqqshell= default_shellSpecifies the shell that noninterpreted scripts run under. The default is theKorn shell, if there is one, and otherwise the Bourne shell (/bin/sh).


Installation

eqqfilespace= nnnn | 1000Specifies the minimum number of blocks of temporary file space. The size of ablock depends on the Tracker Agent machine. If there is less space available,the Tracker Agent closes down in an orderly way with a message. The defaultis 1000 blocks.

eqqmsgq= nnnn | 16384Maximum size of a message transferred to the controller, in bytes. The defaultis 16384. If the kernel does not allow the size that you specify, the maximumallowable size is used, and a message is issued.

eqqshmkey= nnnn | 58871The key to the shared memory that the Tracker Agent will use. The default is58871.

event_logsize= nnnn | 1000Specifies the number of events to be logged in the Event Writer event logfile.The value defined is the number of events, not the event record size. Thedefault is 1000, and this value is also the minimum.

ew_check_file= event_logfileThe name of the file used for logging events. If a file does not exist, it will becreated. The default file name is ewriter_check. You can guarantee a uniquenetwork-wide name for the log file by specifying a name in this format:

$HOST.$local_portnr.ew.check

local_codepage = local_codepage | ISO8859-1Specifies the ASCII codepage used. The default is ISO8859-1.

ipc_base= ID | ASpecifies the unique ID character to be used for creating unique inter-processcommunication (IPC) numbers. The default value is A.

job_log= Log_OptionSpecifies how joblogs will be processed by the Tracker Agent. Thesecombinations are valid:

IMMEDIATE,DELETE IMMEDIATE,KEEP NO,DELETE NO,KEEP DELAYED,DELETE DELAYED,KEEP

The values have these meanings:

NO Joblogs will not be sent to the controller.

IMMEDIATE Joblogs are immediately sent to the controller when the jobends.

DELAYED Joblogs are returned to the controller only if a Tivoli OPCdialog user requests the joblog.

KEEP Joblogs are stored on disk for all jobs.

DELETE Joblogs are deleted when the job ends if NO or IMMEDIATE isalso specified. When DELAYED is specified, the joblog is kepton disk until a retrieval request is received from the controller.


Installation

When saving joblogs on disk, consider the disk space available on the system.The jobs will end in error if there is no space for the log. The default value isIMMEDIATE,DELETE. That is, joblogs are sent to the controller immediatelyand deleted. Joblogs are never sent to the controller if the submittor usesLoadLeveler.

| controller_type= opcSpecifies the type of controller for this Tracker Agent:

opc The controller is OPC/ESA.

There is no default value. opc must be specified.

trace_level=0 | 1 | 2 | 3 | 4Specifies the trace level for the component. The default is 0 (no trace). Youdo not need a trace for normal running.

num_submittors= nn | 1The number of submittors to initialize, from 1 to 56. By default, one submittoris started.

Each submittor will have a default subtype of GS, a default workstation ID ofAXnn, and a default check file of AXnn.check, but you can override thesedefaults with the following parameters.

sub nn_workstation_id= wsID | AXnnConnects submittor nn with a workstation. It is a character string. The lengthmust not exceed 4 (only the first 4 characters will be used). The default valueis AXnn.

sub nn_check_file= checkfile | wsID.checkConnects submittor nn with the file used for job checkpointing and eventlogging. If a file does not exist, it will be created. The default file name iswsID.check. You can guarantee a unique network-wide name for each file byspecifying a name in this format:

wsID.$HOST.$local_portnr.check

sub nn_subtype=GS | LSControls whether a submittor uses LoadLeveler (LS) or not (GS). GS, whichstands for generic submittor, is the default. A generic submittor is simply onethat does not use LoadLeveler.

xxxxx_retry= nnnn | 60These are retry intervals, in seconds, for various Tracker Agent components.xxxxx can be:

eqqtr The interval that Tracker Agent will wait before attempting tocommunicate with the controller if a TCP read attempt fails.

eqqtw The interval that Tracker Agent will wait before attempting tocommunicate with controller if a TCP write attempt fails.

eqqdr The interval that Tracker Agent will wait before attempting to connectand revalidate the connection to the controlling system.

sub nn The interval that the nn submittor will wait before retrying an operation(for example, because the number of processes had reached the limit).


Installation

An example of a configuration file is shown in Figure 12.

# Configuration parameter file ------------------------ Tracker for Tivoli OPC

controller_type = opc

trace_level = ð # global trace level ð-4 default is ð

# Configuration parameter file ------------------------ IP addresses

controller_ipaddr = 9.52.52.3 # REQUIRED

# controller_ipaddr = mvs1 # if using an entry in /etc/hosts

# could be up to 1ð IP addresses separated by ,

local_ipaddr = 9.52.51.49 # local SunOS ip address

# Configuration parameter file ------------------------ Tracker ports

controller_portnr = 2ð5ð # must match the Tivoli OPC TCPIPPORT parameter

# controller_portnr = agent1 # if using a service name from /etc/services

local_portnr = 2ð51

# local_portnr = sun1 # if using a services name

# Configuration parameter file ------------------------ General parameters

eqqfilespace = 5ðð # tracker checks that this space is available

local_codepage = ISO8859-1 # default is ISO8859-1

job_log = immediate,keep # default is immediate,delete

event_logsize = 1ððð # default is 1ððð

ew_check_file = $HOST.$local_portnr.ew.check # to be unique

ipc_base = A # default is A

# Configuration parameter file ------------------------ Tracker submittors

num_submittors = 1 # default is 1

subð1_subtype = gs # default is gs

subð1_check_file = SNð1.$HOST.$local_portnr.check # to be unique

subð1_workstation_id = SNð1 # must match workstation name in Tivoli OPC

# loadleveler submittor

# subð2_subtype = ls

# subð2_check_file = SNð2.check

# subð2_workstation_id = SNð2 # must match workstation name in Tivoli OPC

Figure 12. Example of a Configuration File

After editing the configuration parameter file, always check it using eqqverify, asdescribed in “Checking the Configuration Parameter File” on page 73. Makeespecially sure that the values using configuration or environment variables arecorrectly substituted—there is no error message if the variable is not set or wronglyset.

Customizing the DirectoriesBy default, the Tracker Agent creates the log, temporary, and trace files in the$EQQHOME/log and $EQQHOME/tmp directories. If the Tracker Agent home directory isNFS mounted, these directories will be the same for every Tracker Agent. This cancause performance problems. Also, if the network connection to the NFS server islost, the Tracker Agent cannot function fully. Put these directories on a local filesystem (or with a symbolic link to a local file system) to improve log performance.

If you run several instances of the Tracker Agent, and they share the samedirectory, use variables in the configuration parameter file to ensure that they donot use the same checkpoint and log files.


Installation

If the Tracker Agent is running from a NFS mounted file system, it is recommendedthat the log and temporary directories are configured on the local file system. Theeqqinit command (see Appendix B, “Utilities and Samples” on page 93) initializesa directory on the local machine:

eqqinit -v

This command must be run as root. This local file system must have writeprivileges for everyone, including a root user who is logged in across the network.

The recommended name of the local directory is /var/tracker. You might requireadministrator privileges to create the /var directory if it does not exist, and to createthe links.

Note: The /tmp directory is not suitable because this file system is frequentlycleaned when booting the system, and this would cause the Tracker Agent to beunable to recreate its internal status.

There can be a problem if a job writes too much output: this can fill up the allocatedspace. To protect the system, use a logical volume for the tmp and log directories,where this is supported, or set up a separate file system for them. If this fills up,the Tracker Agent will stop submitting jobs, but the operating system will continueto work. You can use SMIT to create a logical volume.

The log directory includes an event writer checkpoint file, a message log(eqqmsglog), and a trace log (EQQtrc.log) for each Tracker Agent instance, and asubmittor checkpoint file for each submittor instance. See “Checking Files in theLog and Temporary Directories” on page 72 for a description of the files in thesedirectories.

Customizing File PermissionsSome of the Tracker Agent components are designed to run with root authority.These components are:

� The TCP Reader� The Generic subtask� The LoadLeveler submittor.

If you use port numbers lower than 1025, the TCP Reader process must have rootauthority. If port numbers are defined with values greater than 1024, the TCPReader process does not need root authority.

Running without Root AuthorityTo update the TCP Reader to run without root authority, enter the followingcommand as root:

chown tracker $EQQHOME/bin/eqqtr

The generic and LoadLeveler submit processes must also run as root if the user IDunder which submitted jobs should be started is supplied by the controller. If theTracker Agent is not required to run jobs under other user IDs, the submittors canalso be updated to run with normal user authority.


Installation

To update the submittor processes to run without root authority, enter the followingcommands as root:

chown tracker $EQQHOME/bin/eqqls

chown tracker $EQQHOME/bin/eqqgssub

Restoring Root AuthorityTo update the TCP Reader and submittor processes to run with root authority,enter the following commands as root:

chown root $EQQHOME/bin/eqqtr

chmod u+s $EQQHOME/bin/eqqtr

chown root $EQQHOME/bin/eqqls

chmod u+s $EQQHOME/bin/eqqls

chown root $EQQHOME/bin/eqqgssub

chmod u+s $EQQHOME/bin/eqqgssub

chown root $EQQHOME/bin/eqqgmeth

chown u+s $EQQHOME/bin/eqqgmeth

Restrictions and Dependencies on System SoftwareThis section outlines restrictions and system dependencies that you need toconsider.

NFS RestrictionsWhen running the Tracker Agent on NFS mounted directories, the user ID runningthe Tracker Agent must have write access to the file system. If the Tracker Agentis running on an NFS mounted file system, the superuser must have write accessto the file system.

Number of Processes per UserIf the Tracker Agent is running under a user ID other than root, or many jobs arerun under one user ID, the number of processes per user ID should be increased.

AIX only

To set this parameter:

1. Start SMIT.2. Select System Environments .3. Select Change / Show characteristics of Operating System .4. Select Maximum number of PROCESSES allowed per user .

HP-UX only

Use this method:

1. Login as root.2. Enter the System Administration Manager with the sam command.3. Select Kernel Configuration .4. Select Configurable Parameters .5. Change the maxuprc value.


Installation

Sun Solaris and SunOS only

The system administrator should update this value in the Kernel.

Coordinating Clock ValuesThe value of Greenwich Mean Time (GMT) must be approximately the same for theTracker Agent machine and the controlling system. If you set GMT as local time,both the Tracker Agent and controller environments must set GMT as local time.The Tracker Agent will not be able to connect to the controller if the GMT value forthe Tracker Agent machine is not within 60 minutes (plus or minus) of GMT on thecontrolling system.

If machines are in different time zones, these times must be set correctly on thedifferent machines, or coordinated through a network time service.


Chapter 5. Operation

This chapter contains general information to help you control the operation andbehavior of the Tracker Agent.

To run scripts under the Tracker Agent, you do not have to change them, but youshould read these sections first.

Running Scripts for Tivoli OPC

Storing ScriptsThe controller schedules scripts to be executed by the Tracker Agent in the normalTivoli OPC way—a script is an operation, which is part of an application. Refer toPlanning and Scheduling the Workload for details of creating applicationdescriptions. You can store the scripts in the controller EQQJBLIB dataset, orretrieve them with the controller EQQUX002 exit, which is described inCustomization and Tuning. If you edit the member using ISPF, make sure that youhave numbers set off (UNNUM), or the editor will add sequence numbers incolumns 73–80, which will cause errors.

Note: The scripts residing in the MVS host dataset EQQJBLIB must have a logicalrecord length of 80 (LRECL=80). The tool eqqcv80p is provided to facilitate the80-bytes formatting. For details of the eqqcv80p utility, see “eqqcv80p” onpage 98.

Writing ScriptsScripts can contain Tivoli OPC variable substitution and automatic recoverydirectives, which are described in Planning and Scheduling the Workload, but theycannot use MVS-specific functions such as catalog management and step-levelrestart.

Determining the Shell that Scripts Run UnderThere are two ways to determine the shell that scripts run under.

The value of the eqqshell keyword in the EQQPARM file determines wherenoninterpreted scripts run. If you do not give this keyword a value, it takes thedefault, which is /bin/ksh (the Korn shell) for AIX systems, and /bin/sh (the Bourneshell) for other UNIX systems.

Interpreted script files, that is files that begin with the line:

#! pathname

run under the shell indicated in the pathname.


Operation

Specifying a User IDIf the controller supplies user IDs for submitted jobs, the user ID must exist on theTracker Agent machine. Ensure the user ID is supplied in the correct format, withlowercase and uppercase characters as defined on the Tracker Agent machine.

You cannot specify a user ID if the script will run under LoadLeveler: theLoadLeveler runs all scripts under its own user ID.

Getting Output from ScriptsIf an empty script is sent to the Tracker Agent, or a script that is too long, theoperation completes with error code JCLI. If there is an environment error duringexecution of the script, the operation completes with error code JCL.

If you use the generic submittor, you can browse the standard out and error filesfrom the script (the job log) using the controller dialogs. You cannot browse the joblog of scripts submitted using LoadLeveler.

If you have very large script output, check the event_logsize configurationparameter. Every 512 bytes of output (approximately) causes an event, so theparameter must be set large enough for the largest expected output. If the outputis too big, the Tracker Agent writes an error message to the message log. Theevent log wraps round, and the Tracker Agent must scan the whole file for events,so do not make the file unnecessarily large, or this will impact performance.

There is a limit of approximately 64 KB on the job log output that can be retrievedby the Tivoli OPC controller.


Operation

Testing for Errors from CommandsThe generic submittor monitors the return code from the script, and the return codesent to the controller is the return code from the execution of the script. If you havea multiline script like:

date

touch /tmp/file

date

and the touch command fails, the return code in the shell is set. On the nextcommand, date, the return code is reset to 0, so the return code from the touch isgone and the script will return 0 (job successful).

If you want to verify each step in the script, add tests after each call in the script toverify the shell return code:

date

(test rc) - if rc nonzero exit with rc

touch /tmp/file


date


The test depends on the shell used to run the job—the syntax for /bin/sh is differentto /bin/csh, for example.

If you want to monitor a single command directly, specify the command as asingle-line script. In the case of scripts that are only one line long, the submittormonitors the actual command and the return code sent to the controller is thereturn code from the execution of the command. In this case, the command is runusing a standard UNIX exec, so you can not use shell syntax.

Testing return codes will only work, of course, if the command returns a bad codewhen it fails, and a zero code when it works. If you are not sure, try the commandfrom the UNIX command line, and echo the return code from the shell.

If the script is more than one line, the generic submittor submits the script andmonitors the shell for a return code. This means that in very rare cases, the scriptcan have run without error, but an error in the shell can result in an error returncode.

| It is important to note that, if more than 256 error codes are produced from the| execution of a command or a program, then they are processed modulus 256. This| means that return code multiples of 256 are treated as return code zero, for| example, return code 769 (256*3 + 1) is treated as return code 0001, and so on.

Note: Make sure that the correct code page is set for your terminal emulator. Ifthe code page is incorrect, such characters as £, $, and # in scripts sent from theTivoli OPC controller might be mistranslated, causing jobs not to run correctly.

Chapter 5. Operation 61

Operation

Specifying the PathThe default path, and the sequence in which the libraries are searched forcommands to be executed, depends on the user ID that the tracker is started with.To be sure that a program or script is loaded from the correct library, it is advisableto specify the full path in the script or command.

Controlling the Tracker AgentThese topics are presented:

� Starting the Tracker Agent� Checking the Tracker Agent status� Stopping the Tracker Agent.

Starting the Tracker AgentA sample script has been provided to start the Tracker Agent. Login as the TrackerAgent user ID (normally tracker), and enter:

eqqstart [-f filename]

| For Digital OpenVMS only

| @eqqstart

You can use the -f flag to specify the configuration file. This overrides theEQQINSTANCE environment variable. You must also set the EQQHOMEenvironment variable to point to the home directory. See “Customizing theConfiguration Parameter File” on page 48.

The method for automatically starting the Tracker Agent depends on your operatingsystem:

For AIX only

Edit the /etc/rc.tcpip file. This file is processed at startup to initiate all TCP/IPrelated processes. To add the Tracker Agent to the /etc/rc.tcpip file:

1. Login as root.

2. Edit /etc/rc.tcpip, using an editor such as vi.

3. At the bottom of the file add this section:

set EQQINSTANCE=myconfig

set EQQHOME=/u/tracker

export EQQINSTANCE

export EQQHOME

/u/tracker/bin/eqqstart

Attention: Daemons cannot control TTY consoles. Therefore, if you arerunning applications that access TTY consoles, either start AIX Tracker byissuing the eqqstart command, or use local applications to avoid the need forconsole access.


Operation

For Sun Solaris only

Create a file called S99ibm.tracker in the /etc/rc2d directory. This file isprocessed at startup to initiate all TCP/IP related processes. To create theS99ibm.tracker file:

1. Login as root.2. Create the /etc/rc2d/ directory.3. Create the S99ibm.tracker file in this directory and add this:

#!/bin/sh

# start/stop IBM Tracker during system startup/shutdown

# Copyright International Business Machines, Corp. 1995

EQQINSTANCE=myconfig

EQQHOME=/u/tracker

export EQQINSTANCE

export EQQHOME

case $1 in

start)

$EQQHOME/bin/eqqstart

;;

stop)

$EQQHOME/bin/eqqstop

;;

\)

echo "Unknown tracker start/stop command: $1"

;;

esac

For SunOS only

Edit the /etc/rc.local file. This file is processed at startup to initiate allTCP/IP related processes. To add the Tracker Agent to the /etc/rc.local file:

1. Login as root.

2. Edit /etc/rc.local, using an editor such as vi.

3. At the bottom of the file add this section:

EQQINSTANCE=myconfig

EQQHOME=/u/tracker

export EQQINSTANCE

export EQQHOME

$EQQHOME/bin/eqqstart

These methods start the tracker as root, using the configuration parameter filemyconfig.

You can also start the Tracker Agent under a userid other than root when you startthe workstation. The following example applies to the AIX, HP-UX, and Sun Solarisplatforms:

1. Add to the file /etc/inittab the line:

tracker:2:once:/home/tracker/bin/start.tracker

2. Add to the script file /home/tracker/bin/start.tracker the line:

su - tracker -c /home/tracker/bin/eqqstart


Operation

When you reboot the workstation, the Tracker Agent processes start under theuserid tracker.

Checking Tracker StatusUse the eqqshow command to determine the current state of the Tracker Agent.

Shutting Down the Tracker AgentThe Tracker Agent can be orderly shut down by using the eqqstop command on acommand line.

Note: No confirmation is requested when using this command.

Only the Tracker Agent administrator or root user can shutdown the Tracker Agent.If the Tracker Agent has been started as root, only the root user can requestshutdown.


| Stop the tracker by running eqqmon: $run [.bin]eqqmon and selecting option| 5.

Modify CommandsThere is no support for interactive commands to communicate with the TrackerAgent or the individual components. The only command that can be used is theUNIX kill command, which is used to terminate a process. This command canalso be used to stop the Tracker Agent. The command syntax is kill -1 <pid>where <pid> is the process ID of eqq_daemon.

For AIX, HP-UX, and Sun Solaris

This can be determined with the ps –def | grep eqq_daemon command.

For SunOS only

This can be determined with the ps –aucx | grep eqq_daemon command.

The signals passed for termination should be -HUP (-1) or -TERM (-15). This shutsdown the entire Tracker Agent system, because the daemon process sends a -HUPto each process, and then waits five seconds before the same procedure isrepeated with -KILL.

You are recommended to use the eqqstop command to shut down the TrackerAgent.

Dealing with Temporary and Log Files| Temporary file names include the token number assigned for the operation, the| jobname, and the submission date and time. The submittor creates these

temporary files, and removes them only if the job ends with a zero final return code,and if you do not specify KEEP in the job_log configuration parameter. The KEEPoption can be useful for debugging.


Operation

To keep enough space in the log directory, periodically run the eqqdelete script toremove files, or remove all the files using the rm –rf \ command.

Note: Be careful if you have several Tracker Agents using the same temporaryspace.

Checking Disk SpaceMake sure there is sufficient disk space on the partition.

$ cd ∼tracker (if this is the home directory

$ cd log

Command for AIX, showing 4MB free

$ df .

Filesystem Total KB free %used iused %iused Mounted on

/dev/hd9var 8192 3856 52% 231 11% /var

Command for HP-UX, showing about 66MB free

$ bdf .

Filesystem kbytes used avail capacity Mounted on

/dev/dsk/c2ð1d6tð 1818624 175ð924 677ðð 96% /nfs/home/m

Command for Sun Solaris and SunOS, showing about 120MB free

$ df .

Filesystem kbytes used avail capacity Mounted on

/dev/sdðh 457926 29ð5ðð 121634 7ð% /opt

About 20MB should be enough for the log files. If there are many scripts, thepartition size should be increased.

Restarting after an Abnormal TerminationUse the eqqclean command to tidy the temporary files.

Sometimes, depending on how the Tracker Agent terminates, the shared memorykey might not be deleted, preventing a subsequent restart of the Tracker Agent.When this happens and the Tracker Agent is restarted, the security mechanismprevents the Tracker Agent from starting. A warning message informs you that aTracker Agent might already be active, and a message describing a sharedmemory allocation failure is issued to the message log.

If the problem is not due to a tracker with the same key already running, you mustremove the shared memory segment before the Tracker Agent can restart. To dothis:

1. Enter the command ipcs –mob

2. In the generated output, find the identifier of the segment with:

Owner trackerGroup opcSize 6048


Operation

3. Remove the segment using the ipcrm –m <identifier> command.

4. Perform the first step again to ensure that the segment is no longer listed.


Operation


Chapter 6. Diagnosing Problems

This chapter contains information to help you diagnose problems with the TrackerAgent. See Appendix B, “Utilities and Samples” on page 93 for a full syntax of anycommands mentioned. See Appendix A, “Messages” on page 77 for moreinformation about messages.

Problems will usually be one of these kinds:

� Communication between the Tracker Agent and the controller.

Follow the procedures in “Verifying that TCP/IP Is Operational” on page 25,and see “Checking the Configuration Parameter File” on page 73.

� Failure to start the Tracker Agent.

Check the parameter file (“Checking the Configuration Parameter File” onpage 73) and reset the Tracker Agent (“Resetting the Tracker Agent” onpage 76).

� Failure of submitted jobs.

Check the log files (“Checking Files in the Log and Temporary Directories” onpage 72).

� Abnormal termination of the Tracker Agent. See “Exit Codes” on page 70.

� Nothing is happening. See “Dealing with a Hung Tracker Agent” on page 71.

� Performance problems. See “Tuning and Performance” on page 76.

Table 10 (Page 1 of 2). Symptoms and Required Actions for Common Problems

Symptom Required action

A number of jobs ends in error. The Tracker Agent probably terminated while the jobs were executing.The status of jobs cannot be determined if the Tracker Agent is notstarted. Rather than leaving the operations in Started status forever, theoperations are set to Error status to highlight the problem. Manually checkthe status of the jobs, and change the status in the controller to thecurrent status. Ensure the Tracker Agent is restarted.

A controller never becomes active. Check that TCP/IP is active on the controller. Check that the TCPIPPORTparameter value is valid on the controller. Check that there is free diskspace in the Tracker Agent tmp and log directories. Check the TrackerAgent status from the controller machine, and run eqqverify on theTracker Agent machine.

A process continually terminates. Check the message log for error messages describing the problem. Ifthere are none, run eqqverify. If the problem cannot be identified, set thetrace level to 4, restart the Tracker Agent to gather trace information, andcontact your IBM representative.

Cannot connect with Errno=78. The Tracker Agent cannot locate the controller. There might be a problemwith the network setup of the machine. Contact your system or networkadministrator.

Cannot connect with Errno=79. The controller is not responding to the Tracker Agent. Check that:

� The controller is active.� The tracker machine is defined in the controller database.� controller_ipaddr and controller_portnr are correct.


Fixing Problems

Table 10 (Page 2 of 2). Symptoms and Required Actions for Common Problems

Symptom Required action

Tracker machine (workstation) notactive in the controller.

If the TCP/IP conversation is active, this normally means that the TrackerAgent and the controller have not completed synchronization processing.

� Check the Tracker Agent status from the controller machine.

� Check that the controller parameter (TCPIPPORT) matches thecontroller_portnr parameter in the Tracker Agent configurationparameter file.

� Check the status of the tracker using the eqqshow command.

Exit CodesThe Tracker Agent sets exit codes according to the reason for termination. Youcan see the exit return code:

� In the Korn shell (ksh), using $?� In the Bourne shell (sh), using $?� In the C shell (csh) variable status.

These exit codes are possible:

Code Reason

1 The environment could not be initialized. This includes configuration errors.

2 Error in the parameters specified at invocation.

3 Trace mode could not be set.

4 A needed shared memory segment already exists. This could indicate analready running Tracker Agent that is using the same configuration parameterfile and shared memory key. See “Restarting after an Abnormal Termination”on page 66.

5 The Tracker Agent could not attach to its shared memory segment.

6 Memory needed for restart information could not be allocated.

7 Main loop has terminated for a reason other than that a process time quotahas been exceeded or a Tracker Agent component has exited.

The reason for this condition is entered into the message log—both in textand as a numeric code. See “Return Codes” on page 71 for details about thereturn codes.

8 A restartable condition has occurred. Restarts are performed according to thesetting of the –v flag. A message describing the error is written to themessage log.

9 Semaphore ID needed for component signalling can not be retrieved.

10 Semaphore initialization can not be performed.


Fixing Problems

Return CodesThe following codes are placed in the message log when the Tracker Agentexperiences a fatal condition after it has started main processing. The exit codeconnected to the return codes is 7. If a restart is to be attempted, the exit code is8.

Code Reason

1 A Tracker Agent component time quota has been exceeded. A restartattempt will be performed.

2 There is no place in shared memory to place a new process. A restartattempt will not be performed.

4 A Tracker Agent component could not be started. A restart attempt will notbe performed.

8 Parsing of configuration failed. The name of the Tracker Agent componentscould not be accessed. A restart attempt will not be performed.

16 There are no executables to manage. A restart attempt will not be performed.

32 A Tracker Agent component has exited. A restart attempt will be performed.

64 A message queue could not be deleted. A restart attempt will not beperformed.

128 A message queue could not be created. A restart attempt will not beperformed.

General TroubleshootingThis section contains general troubleshooting hints. If you suspect you have aproblem with the Tracker Agent, check the conditions that apply to your installationbefore calling your IBM representative. You can use the eqqapars command tocollect diagnostic information for IBM.

Dealing with a Hung Tracker AgentIf the Tracker Agent is hung and needs to be terminated:

1. Find out the process ID of the daemon by using the UNIX command:

ps –def | grep eqq

2. Use the kill command to kill the process.

kill –HUP <pid>

You must be running under root or the user ID that owns the daemon process to dothis.

Investigate the reason for the failure before attempting to restart the daemon. If theproblem continues, restart the Tracker Agent with trace level 4 to collect diagnosticinformation, and contact your IBM representative.

Chapter 6. Diagnosing Problems 71

Fixing Problems


| Check the eqqout.dat file to see any errors resulting from the tracker execution.| If you find an exceeded quota error, contact your systems administrator to tune| the system quotas. The Tracker Agent uses the PQL_ quotas.

Checking Files in the Log and Temporary DirectoriesThese files can be very useful in diagnosing a problem.

Checking the Log DirectoryIf nothing is in the log directory, check the file permissions. If it is a link, changedirectory (cd) to the link and check the directory.

| The file permissions for the log and tmp directories should be 644. If not, use 644

to set the permissions:

| chmod 644 /u/tracker/log (if this is your directory name

Checking the Message Log FileCheck the file $EQQHOME/log directory for information. The message log eqqmsglogcontains information, warning, and error messages. See Appendix A, “Messages”on page 77 for a description of the messages generated by the Tracker Agent.

Event LogfileThis file (its real name is specified in the ew_check_file configuration parameter,but is typically called ewriter.check) contains all events logged by the TrackerAgent. The log file contains either a complete tracker internal message structure ora joblog data record. Its function is the same as the Tivoli OPC event dataset.

The file contains binary data. Use the eqqview command to browse it.

Trace FilesTrace information is generated when the trace level in the configuration parameterfile is greater than 0. The file names are EQQenv.log, EQQpgm.log, and EQQtrc.log.You do not need to set any trace level unless you suspect there is a problem withthe Tracker Agent.

The EQQxxxx.ENV, EQQxxxx.PGM, and EQQxxxx.TRC files contain trace data for theindividual components when the trace level is greater than 0, or when there is asevere error. You only see these files when a process is running, or if a processends without cleaning up. The data is normally appended to the EQQenv.log,EQQpgm.log, and EQQtrc.log files when the process ends normally.

Checking the Other FilesEQQenv.log This file contains environment-related trace data for the Tracker

Agent if the trace level is greater than 0.

EQQpgm.log This file contains the program log for the Tracker Agent.Program errors are reported in the program log.

EQQtrc.log This file contains the trace log for the Tracker Agent if the tracelevel is greater than 0.


Fixing Problems

EQQxxxx.ENV These files contain environment-related trace data for theindividual components when the trace level is greater than 0, orwhen there is a severe error. You only see these files when aprocess is running, or if a process ends without cleaning up.This data is normally appended to EQQenv.log when a processends, and the file is deleted.

EQQxxxx.PGM These files contain program trace data for the individualcomponents when the trace level is greater than 0, or whenthere is a severe error. You only see these files when a processis running, or if a process ends without cleaning up. This data isnormally appended to EQQpgm.log when a process ends, and thefile is deleted.

EQQxxxx.TRC These files contain trace data for the individual componentswhen the trace level is greater than 0, or when there is a severeerror. You only see these files when a process is running, or ifa process ends without cleaning up. This data is normallyappended to EQQtrc.log when a process ends, and the file isdeleted.

eqqmsglog This file contains error messages and other auditing information.

You can choose different names for the following files when you code theconfiguration parameter file.

ewriter.check This file (its real name is specified in the ew_check_fileconfiguration parameter) contains event records for the eventwriter.

wsID.check This file (its real name is specified in the subnn_check_fileconfiguration parameter) contains checkpoint records for thesubmittor wsID, number nn.

You can run the eqqdelete command, for example once a day, to delete log files.You can do this manually or by scheduling a batch job that runs regularly.

Job Output FilesStandard out and standard error lists of submitted jobs are saved and storedtemporarily in the tmp directory according to the job_log keyword in theconfiguration parameter file.

| The temporary file names include the jobname, the submission date and time, and| an 8-character hexadecimal token that is unique for every job. The file name is| built from this information, concatenated with a string of .OUT for stdout. A job with| jobname "UNIXDIR" submitted at 10:00 on July 01, 1999 with token number 10 will| therefore build a stdout file name of UNIXDIR__99ð7ð1_1ððððð_ðððððððA.OUT.

Checking the Configuration Parameter FileSpecify the configuration parameter file using the EQQINSTANCE variable, or usingthe -f flag when you start the Tracker Agent. It is in the $EQQHOME/etc directory.

Use the eqqverify command to check the configuration parameter file for syntaxand consistency. It writes messages to the message log and displays the currentsettings at your terminal. Always rerun eqqverify after:

� Editing the configuration parameter file.


Fixing Problems

� Deleting log files.� Changing the user ID.� Re-installing the Tracker Agent.� Changing the Tracker Agent directory links.

To run eqqverify, enter:

$EQQHOME/bin/eqqverify [-f filename]

You can omit -f filename if the file is $EQQHOME/etc/EQQPARM, or the EQQINSTANCEvariable is set.

Messages will be written to the screen and the $EQQHOME/log/eqqmsglog file. If youget error messages, check:

� File permissions on $EQQHOME/etc

� File permissions on $EQQHOME/tmp

� File permissions on $EQQHOME/log

� File permissions on $EQQHOME/log/eqqmsglog

� File permissions on $EQQHOME/nls

Also check the parameters, and especially:

� That the Tracker Agent parameter controller_portnr matches the controllerparameter (TCPIPPORT).

� The IP address parameters.

� The workstation name parameter subnn_workstation_id.

Checking File PermissionsEnsure the files in $EQQHOME have the correct file permissions.

The home directory should be similar to:

$ ls –la /u/tracker

lrwxrwxrwx 1 tracker opc 2ð Aug 4 12:ð9 bin@ –> /usr/lpp/tracker/bin/

lrwxrwxrwx 1 tracker opc 2ð Aug 4 12:ð9 doc@ –> /usr/lpp/tracker/doc/

drwxrwxr–x 5 tracker opc 512 Jul 18 19:13 info/

lrwxrwxrwx 1 tracker opc 16 Aug 4 12:11 log@ –> /var/tracker/log

lrwxrwxrwx 1 tracker opc 2ð Aug 4 12:ð9 nls@ –> /usr/lpp/tracker/nls/

lrwxrwxrwx 1 tracker opc 24 Aug 4 12:ð9 samples@ –> /usr/lpp/tracker/samples/

lrwxrwxrwx 1 tracker opc 16 Aug 4 12:11 tmp@ –> /var/tracker/tmp

The arrow (–>) shows that the files are linked.

$ ls –la /usr/lpp/tracker/bin

lrwxrwxrwx 1 tracker opc 43 Mar 9 11:48 eqq_daemon@ –> /usr/lpp/tracker/bin/eqq_daemon\

lrwxrwxrwx 1 tracker opc 41 Mar 9 11:48 eqqapars@ –> /usr/lpp/tracker/bin/eqqapars\

lrwxrwxrwx 1 tracker opc 41 Mar 9 11:48 eqqclean@ –> /usr/lpp/tracker/bin/eqqclean\

lrwxrwxrwx 1 tracker opc 41 Mar 9 11:48 eqqcv8ðp@ –> /usr/lpp/tracker/bin/eqqcv8ðp\

lrwxrwxrwx 1 tracker opc 42 Mar 9 11:48 eqqdelete@ –> /usr/lpp/tracker/bin/eqqdelete\

lrwxrwxrwx 1 tracker opc 38 Mar 9 11:48 eqqdr@ –> /usr/lpp/tracker/bin/eqqdr\

lrwxrwxrwx 1 tracker opc 38 Mar 9 11:48 eqqew@ –> /usr/lpp/tracker/bin/eqqew\

lrwxrwxrwx 1 tracker opc 38 Mar 9 11:48 eqqfm@ –> /usr/lpp/tracker/bin/eqqfm\

lrwxrwxrwx 1 tracker opc ...


Fixing Problems

Checking the Tracker User IDCheck that the user ID tracker is defined, and that the group ID opc is definedcorrectly. See “Creating a User Group and User IDs” on page 12 for moreinformation.

Checking the NFS File SystemIf you run the Tracker Agent on an NFS mounted drive, ensure the tmp and logdirectories are allocated locally on each machine. Also ensure that the root userhas write access to the NFS mounted file system.

Checking the NIS MasterIf you are running NIS, ensure the tracker user ID and group are defined on theNIS master host, and that the NIS maps are updated.

Checking the name serverIf you run a name server, ensure the name server has been updated with entriesfor both the Tracker Agent machine and the controller machine.

Checking Duplicate Port DefinitionsCheck the /etc/services file on the Tracker Agent machine for duplicate portnumbers. Check that controller_portnr and local_portnr in the configurationparameter file are set to unused ports. On the controller machine, check that thesame port numbers are defined.

Tracker Agent ports are unavailable if they are specified in the /etc/inetd.conf

file.

Defining local_ipaddr if Multiple InterfacesIf the Tracker Agent machine has multiple network cards, the address used for theconnection is unpredictable. Set the parameter local_ipaddr in the configurationparameter file.

Fixing Problems with Symbolic LinksWhen the Tracker Agent was installed, you probably used the eqqinit script to setup the symbolic links for the Tracker Agent. Normally, you only need to do thisonly once, but if the links are deleted, run eqqinit again. If you use the ls -las

command on the $EQQHOME/bin directory for the Tracker Agent, the output shouldbe similar to:

lrwxrwxrwx 1 tracker opc 2ð Jul 15 19:18 bin –> /usr/lpp/tracker/bin

If there is a problem with the links (if they already exist, or you need to update thedestination file system), you can reset them manually. To do this, login as thetracker user and enter:

rm –rf log

rm –rf tmp

ln –s /usr/lpp/tracker/tmp

ln –s /usr/lpp/tracker/log


Fixing Problems

Resetting the Tracker AgentSometimes you may need to tidy the log files before the Tracker Agent will startproperly:

1. Run eqqstop to stop the Tracker Agent.

2. Run eqqclean to tidy up the log files. If you use nonstandard log file names,change the eqqclean script to use your file names. Check that it really hasremoved the event history file with the name specified in the eqq_check_fileconfiguration parameter file parameter. If you specified a name beginning withan environment variable such as $HOST.checkfile and this variable is not set,the file is called .checkfile, which is a file invisible to the ls command butvisible to the ls -las command, so use this command for extra security, anduse the eqqverify utility to check the resolution of variables.

3. Run eqqstart.

To completely reset the tracker:

1. Set EQQHOME.2. Change to the log directory and remove everything.3. Change to the tmp directory and remove everything.

4. Run eqqverify.5. Check the message log in $EQQHOME/log/eqqmsglog.

6. Run eqqstart.

If the Tracker Agent is terminated without being restarted, run eqqclean andmanually remove any file not related to the tracker, which is stored in the /log,/tmp, /tmp/save. Then restart the Tracker Agent.

Checking IPC QueuesIf you run the tracker under root, and then under another user, you might need tocheck that old queues are not left undeleted:

1. Run the ipcs -a command.

2. Check for queue keys owned by the tracker, and that have a qbytes size equalto that specified by the eqqmsgq configuration parameter.

Tuning and PerformanceData is sent to the controller in blocks whose size is set by the eqqmsgq keyword.You can find the value of eqqmsgq by running the eqqverify command. Shouldoutput exceed the maximum size, the Tracker Agent splits it into two or morechunks and sends these in sequence.


EQQTX10I � EQQTX19I

Appendix A. Messages

EQQTX10I Process: READY event from componentcomponent number1 of number2

Explanation: The component with ID component hascompleted its initial set-up and is ready for events.

System action: Processing continues.

System administrator response: None.

EQQTX11I Process: is ending

Explanation: The process Process has beenrequested to stop by the tracker daemon.

System action: The process terminates.


EQQTX12I Process: Completed Initialization.

Explanation: The process Process has received andsuccessfully processed configuration data.

System action: The process is operational and waitsfor work.


EQQTX13I Process: Initialized tracker object.

Explanation: The process Process has initialized thetracker.

System action: The process is operational and waitsfor work.


EQQTX14I Process: Setting field keyword value tovalue

Explanation: During initialization of the processProcess, the keyword identified in the message is notdefined in the configuration parameter file, or the valuedefined for the keyword is not valid. The default valuefor the keyword will be used.

System action: Initialization processing continues.


EQQTX15I Process: Verified configuration file

Explanation: The configuration parameters for theprocess process have been successfully verified.

System action: The Tracker Agent will create theprocess.


EQQTX16I Process: IP address for controller Numberis ip_addr

Explanation: Up to 10 IP addresses can be definedfor the controller. When the Tracker Agent starts itattempts to connect to the first controller address in thelist. If the connection can not be made, the TrackerAgent will retry 5 times (at intervals specified in theeqqdr_retry parameter) before trying to connect to thenext controller address in the list. If there is only onecontroller, the Tracker Agent will continue to attemptconnection until the Tracker Agent is stopped or theconnection is successful.



EQQTX17I Process: IP address for local machine isip_addr

Explanation: The IP address for the local machinecan either be specified in the configuration parameterfile or the Tracker Agent can determine the addressautomatically. When there is more than one IP addressdefined for the machine, the address determined by theTracker Agent is not predictable. The preferred addressshould be defined in the configuration parameter file.


System administrator response: Verify that the IPaddress is correct. If your machine has more than oneaddress defined, specify the preferred address in theconfiguration parameter file.

EQQTX18I Process: Port number for the controller isport_nr

Explanation: The TCP/IP port number defined for thecontroller is port_nr. The Tracker Agent will attempt toconnect to this port.



EQQTX19I Process: Port number for the tracker isport_nr

Explanation: The TCP/IP port number defined for theTracker Agent is port_nr. The controller will attempt toconnect to this port.




EQQTX20I � EQQTX31I

EQQTX20I Process: Local codepage is codepage

Explanation: The local codepage is defined ascodepage, default is ISO8859-1.



EQQTX21I Process: Host codepage is codepage

Explanation: The host codepage is defined ascodepage, default is IBM-037.



EQQTX22I Process: Job jobname submitted to LL,job_id is job_id

Explanation: The LoadLeveler submittor hassuccessfully submitted the job jobname to LoadLeveler.



EQQTX23I Process: TCP/IP connection to controllercccccccc value dddddddddddddestablished

Explanation: The Tracker Agent has established aTCP/IP connection to the cccccccc controllersuccessfully. Communication is handled by theTCP-Reader and the TCP-Writer.



EQQTX24I Process: Trying to establish a connectionto controller cccccccc

Explanation: All processes are started and theTracker Agent will attempt to connect to the cccccccccontroller.



EQQTX25I Process: Event logfile has been formatted

Explanation: The Event Writer has successfullyformatted the event logfile.



EQQTX26I Process: Event logfile will be formatted

Explanation: The Event Writer has detected thateither a new event logfile has been allocated, or theevent_logsize has changed since the previous start ofthe Tracker Agent. The event logfile will bere-formatted, old data is erased.



EQQTX27I Process: Controller type is type

Explanation: The message informs you that thecontroller is OPC/ESA.



EQQTX28I Process: Sending submit checkpointstatus for workstation ws to controller

Explanation: The Tracker Agent has received arequest for synchronization for the workstation ws. Thismessage is issued after the Tracker Agent and thecontroller have established a connection and theTracker Agent is ready to receive job submit requests.

System action: Processing continues waiting for jobsubmit requests.


EQQTX29I Process: Killed process processerrno= error

Explanation: The tracker has processed a kill requestfrom the controller.



EQQTX30I Process: Trace level is set to trace_level

Explanation: The trace level determines how muchtrace information is printed for servicing the code. Thedefault is 0, no trace information.

System action: Processing continues. If thetrace_level is greater than 0, the Tracker Agent willgenerate trace information. This can impact theperformance of the Tracker Agent.


EQQTX31I Process: Log filename is filename

Explanation: Process will use this file to log internalevents




EQQTX32I � EQQTX3BI

EQQTX32I Process: Size for the event logfile islogsize

Explanation: The Tracker Agent will log this numberof events in the event logfile for internal use by EventWriter. If the event logfile already exists and the valuehas changed since the previous start of the TrackerAgent, the logfile will be re-formatted, erasing old data.The default value is 1000.



EQQTX33I Process: Directory to store temporaryfiles is directory

Explanation: The Tracker Agent will use this directoryto create, store, and remove temporary files. Job logsand script data are written to this directory.



EQQTX34I Process: Tracker message catalog ismsgcat

Explanation: The Tracker Agent will use the messagecatalog msgcat for messages. The full path to themessage catalog is displayed. The default value for themessage catalog file is$EQQHOME/nls/msg/$LANG/eqqmsgcat.cat.

System action: The Tracker Agent will open messagecatalog.


EQQTX35I Process: Parameter file is parmfile

Explanation: The Tracker Agent will use the fileparmfile for configuration parameter information. Thefull path to the configuration parameter file is displayed.The default value for the configuration parameter file isthe variable $EQQHOME/EQQPARM. If theenvironment variable $EQQHOME is not set, theTracker Agent uses the home directory of the user IDrunning the Tracker Agent. If the environment variable$EQQINSTANCE is set, the Tracker Agent will use thisvalue for the configuration parameter file.

System action: The Tracker Agent will start to verifythe configuration parameters.


EQQTX36I Process: Job Log is job_log

Explanation: The Tracker Agent will use this optionwhen processing stdout and stderr for jobs submitted bythe generic submittor.



EQQTX37I Process: Workstation ID is workstation forthis submittor

Explanation: This submittor is processing operationson the work submittor workstation in the controller.



EQQTX38I Process: All components active sendingID event.

Explanation: The data router has verified that alltracker components are active, and will attempt toconnect to the controller.



EQQTX39I Process: Shutting down active trackerprocesses

Explanation: The Tracker Agent has either beenrequested to shutdown by a kill command, or hasdetected an error in a process and will restart thedaemon and all processes.

System action: Termination continues.


EQQTX3AI Process: Restart of tracker will not beperformed. Exiting

Explanation: The Tracker Agent has been requestedto terminate. The exit code and return code do notallow the Tracker Agent to automatically restart.

System action: The Tracker Agent will terminate.

System administrator response: See Chapter 6,“Diagnosing Problems” on page 69 for a description ofreasons for Tracker Agent exit codes.

EQQTX3BI Process: Submitting tracker componentcomp

Explanation: During initialization, the Tracker Agenthas determined that the component started is comp.There should be at least 5 components started.



Appendix A. Messages 79

EQQTX3CI � EQQTX3NI

EQQTX3CI Process: Waiting num seconds beforerestarting tracker

Explanation: The Tracker Agent process process hasbeen terminated. It will be automatically restarted innum seconds.



EQQTX3DI Process: Initializing num Objects withnumsub submittors

Explanation: Process has initialized the requirednumber of objects. Each Tracker Agent process has aninternal object to store information. The total number ofobjects is the number of Tracker Agent processes plusone for each submittor defined.



EQQTX3EI Process: Directory to store log files isdirectory

Explanation: The Tracker Agent will create and storelogfiles in this directory. The event logfile, submitcheckpoint file, message log file, and trace files arestored in this directory.



EQQTX3FI Process: Found component comp

Explanation: Process has verified that the componentexists in the current configuration. There is a messageissued for each Tracker Agent process plus one foreach submittor defined.



EQQTX3GI Process: Shared memory operation -optype - successful

Explanation: Process has completed a sharedmemory operation. The operation could be create,attach, or drop.


System administrator response: None

EQQTX3HI Process: Attempting to allocate sharedmemory size num

Explanation: Process will attempt to allocate a sharedmemory segment to store configuration parameterinformation.



EQQTX3JI Process: Allocated shared memory keykey

Explanation: Process has allocated a shared memorysegment with the key key. This key is used to identifythe configuration information for each machine.



EQQTX3KI Process: Attached data segment key

Explanation: Process has attached to the sharedmemory segment with key key to obtain configurationinformation.



EQQTX3LI Process: Initialized component

Explanation: Process has successfully initializedcomponent.



EQQTX3MI Process: Current system level levelversion version

Explanation: This message displays the softwarelevel.



EQQTX3NI Process: Closing component component

Explanation: Process has received a shutdownrequest. A terminating message will be issued for eachcomponent.




EQQTX3OI � EQQTX44W

EQQTX3OI Process: RFW for submittor submittor.Current Agent Limit= limit

Explanation: The controller has connected to thetracker and is requesting information about activeworkstations.



EQQTX3PI Process: SYNCH for submittor. CurrentAgent Status status

Explanation: The controller has verified allworkstations and now resets the submittor to handlenew work.



EQQTX3QI Process: Set initial READY timeout to ttttseconds

Explanation: The data router sets an initial timeout forall components to become active. All components mustrespond within tttt seconds or the tracker will end.



EQQTX3RI Process: ID event status reader readerwriter writer

Explanation: The data router has processed an IDevent. Both the TCP-Reader and the TCP-Writer mustsignal ID events to the data router.



EQQTX3SI Process: setting Workstation workstationstatus to status

Explanation: This shows the new status of thesubmittor.



EQQTX3TI Process: bound socket to controller oncontroller on port port

Explanation: This shows which port has been used toconnect to the controller.



EQQTX41W Process: environ error setting UID rootgroup= group user= user jobname= jobname

Explanation: This message shows an environmenterror with user IDs. The subtask usually runs with rootauthority.

System action: If the process cannot switch to therequired user ID, the job will not run.

System administrator response: Check the user ID.Check that the submittor can run with root authority.

EQQTX42W Process: Connection closed bycontroller

Explanation: The controller has closed theconnection. It might be down.

System action: The Tracker Agent attempts toreconnect at intervals specified in the eqqdr_retryparameter.

System administrator response: Check the status ofthe controller, and restart it if necessary.

EQQTX43W Process: environ errorinitgroups= igroups user= userjobname= jobname errno= errno

Explanation: The submittor could not initializesecondary groups.

System action: This could cause a problem runningjobs that need these groups.

System administrator response: Check that thesubtask has root authority. Check that the secondarygroups in /etc/groups match groups on separatemachines. Check the error code (listed in/usr/include/sys/errno.h).

EQQTX44W Process: Connect to controller onip_addr failed, errno = error.

Explanation: During startup, the Tracker Agent failedto connect to the controller. It might be down, or the IPaddress defined in the configuration file may not becorrect.

System action: The Tracker Agent attempts toreconnect according to the retry parameters.

System administrator response: Check that the IPaddress defined for the controller is correct. Check theerror code (listed in /usr/include/sys/errno.h).


EQQTX45W � EQQTX53W

EQQTX45W Process: Job jobname has beenprocessed to status status

Explanation: Process was unable to post the EventWriter with the status of the job jobname. This canhappen if the Tracker Agent daemon is killed whilethere are jobs executing.

System action: Status for this job is not reportedaccurately.

System administrator response: The Tracker Agentis probably no longer active. Restart it. Check the jobstatus in the controller. It should have been set toEnded status. Manually set the status for the operation.

EQQTX46W Process: Job Log is currently disabledbut received a Job Log Request

Explanation: Job log handling for the Tracker Agent iscurrently disabled but the controller has sent a requestfor the Tracker Agent to retrieve a job log.

System action: The request is ignored and processingcontinues.

System administrator response: If job logs shouldbe sent to the controller, set the Job_log keyword todelayed or immediate in the configuration file andrestart the Tracker Agent. The user requesting the joblog for this operation will be informed that is notavailable.

EQQTX47W Process: System call fork failed, will tryagain in tttt seconds

Explanation: The submittor tried to create a childprocess but failed. This can happen if too manyprocesses are currently executing for the user runningthe Tracker Agent.

System action: The submittor will try again after ttttseconds.

System administrator response: If this message isissued regularly, check for the limit of active processesdefined for the user running the Tracker Agent, increasethe limit if it is too low.

EQQTX48W Process: Could not change to homedirectory for user user, jobname isjobname

Explanation: The home directory could not be foundin the system for the user user. The job will beexecuted using the directory where the Tracker Agent isrunning.


System administrator response: Check the homedirectory for the user, and create one if necessary.

EQQTX49W Process: Diskspace available infilesystem filesystem might not beenough

Explanation: The Tracker Agent has determined thatthere might be too little disk space for the TrackerAgent functions to run correctly. The amount of spaceis reviewed by the Tracker Agent at startup, and alsoafter every 100 job submits.


System administrator response: Check for diskspace available for the file system by using thedf filesystem command.

EQQTX50W Process: Number number of events havebeen lost

Explanation: The Tracker Agent has detected thatevents have been lost. This can happen ifcommunication to the controller is inactive while manyjobs are executing, and the event logfile is too small.


System administrator response: Check the status ofall jobs on the submittors handled by this TrackerAgent. Review the size of the event logfile. It must belarge enough to allow network outages without losingthe status of jobs running on the system.

EQQTX51W Process: Invalid controller type type

Explanation: The controller type must be OPC.


System administrator response: Check theconfiguration parameter file.

EQQTX52W Process: Tracker will now try to connectto the controller on ip_addr

Explanation: More than one IP address has beendefined for the controller. The Tracker Agent has notbeen able to connect to a controller, and will switch tothe next IP address defined.


System administrator response: Check the definedIP addresses in the configuration file. Ensure one ofthe controllers in the list is started.

EQQTX53W Process: Tracker exiting with reasoncode code - msg

Explanation: The Tracker Agent is exiting with thecode defined in the message.




EQQTX54W � EQQTX5CW

EQQTX54W Process: Tracker restarting with reasoncode code - msg

Explanation: The Tracker Agent is restarting with thereason code defined in the message.

System action: Restart processing continues.


EQQTX55W Process: Process group could not bechanged, reason rsnc

Explanation: The process group could not bechanged.


System administrator response: Correct the errorand restart the Tracker Agent. See Chapter 6,“Diagnosing Problems” on page 69 for a description ofreasons for Tracker Agent exit codes.

EQQTX56W Process: The number of componentsrunning exceeds maximum limit.Unpredictable events might occur,reason code

Explanation: The number of Tracker Agentcomponents, specifically the number of submittor tasks,exceeds the maximum number of components allowedfor the system.


System administrator response: When convenient,stop the Tracker Agent, decrease the number ofsubmittor tasks and restart the Tracker Agent.

EQQTX57W Process: The tracker submit processreported error submitting jobname

Explanation: An error was encountered when theTracker Agent attempted to submit the job using thefork system call.

System action: The job is not submitted. Processingcontinues.

System administrator response: The job will bereported back to the controller in Error status.Determine the reason for the failure and restart theoperation.

EQQTX58W Process: Received signal sig

Explanation: Process has received the signalidentified in the message.

System action: Depends on the signal received.

System administrator response: Take theappropriate action depending on the signal received.

EQQTX59W Process: Restart time value assignmentfailed. This might cause unpredictablerestart behavior

Explanation: The Tracker Agent was unable todetermine the restart interval required. It might bedefined incorrectly.


System administrator response: When convenient,restart the Tracker Agent with a valid restart interval.

EQQTX5AW Process: Message catalog could not beopened

Explanation: Process could not open the messagecatalog. The Tracker Agent will continue to run, butmessages will not be written to the message log.


System administrator response: Check the defaultmessage catalog defined for$EQQHOME/nls/msg/$LANG/eqqmgcat.cat. Ensure thefile exists and is accessible to the Tracker Agent.Restart the Tracker Agent when the problem isresolved.

EQQTX5BW Process: Job jobname with LL Jobidjob_id has been removed

Explanation: The LoadLeveler submittor tasksubmitted the job jobname to LoadLeveler successfully.LoadLeveler has removed the job from its queue.

System action: The job is reported in Error status tothe controller. Processing continues.

System administrator response: Determine whyLoadLeveler removed the job.

EQQTX5CW Process: Initializing field field withdefault value value

Explanation: Field field was not specified, or aninvalid value was specified. The field is initialized withthe default value. This information is displayed so thatyou can verify that the Tracker Agent is running with thecorrect parameters.

System action: Verification of the parameter filecontinues.

System administrator response: If required,shutdown the Tracker Agent, set the correct value andrestart the Tracker Agent.


EQQTX5DW � EQQTX64E

EQQTX5DW Process: Field field Size size less thanminimum min

Explanation: A field in the parameter file has beendetected with a value less than the required minimumvalue.

System action: The default value for the field will beused. Processing continues.

System administrator response: Update theparameter file with a value greater than the minimummin and restart the Tracker Agent when it is convenientto do so.

EQQTX5EW Process: Field field Size size greaterthan maximum max

Explanation: A field in the parameter file has beendetected with a value greater than the requiredmaximum value.

System action: The default value for the field will beused. Processing continues.

System administrator response: Update theparameter file with a value less than the maximum maxand restart the Tracker Agent when it is convenient todo so.

EQQTX5FW Process: Tracker will be reinitialized intttt seconds

Explanation: The connection to the controller hasbeen lost. The Tracker Agent will attempt to reconnectto the controller in tttt seconds.

System action: The Tracker Agent is reinitialized.

System administrator response: Ensure TCP/IP isactive on both Tracker Agent and controller systems.

EQQTX5GW Process: Resetting controller connecttimeout to tttt seconds

Explanation: The data router will wait tttt secondsbefore retrying the connection to the controller.

System action: The data router will try to reconnect.

System administrator response: If the controller isnot available, restart it.

EQQTX5HW Process: Received job request forunknown WS workstation

Explanation: A job needs a submittor associated withthe workstation workstation, but this workstation is notdefined in the configuration parameter file.

System action: The job is reported in Error status tothe controller.

System administrator response: Check that theworkstation is defined in the configuration parameterfile.

EQQTX61E Process: Job jobname could not beexecuted, exec system call failed, errno =error

Explanation: The exec system call has failed with theerror code supplied.

System action: Process terminates. If the process isthe generic submittor, the Tracker Agent will be shutdown. The job jobname is not submitted.

System administrator response: Check the errorcode (listed in /usr/include/sys/errno.h).

EQQTX62E Process: Job jobname terminated due tothe signal sig

Explanation: The job submitted by the Tracker Agenthas been terminated by the signal sig.


System administrator response: Check the status ofthe operation in the controller. If required, set thecorrect status.

EQQTX63E Process: Job jobname could not besubmitted to LL

Explanation: Job jobname could not be submitted toLoadLeveler because the argument list containing jobinformation became too long. This can happen if theTracker Agent log and tmp directories have long pathnames.

System action: The job is report in Error status.Processing continues.

System administrator response: Check the pathlength for the Tracker Agent directories. Use a shorterpath name if possible and restart the tracker.

EQQTX64E Process: Directory directory cannot beaccessed

Explanation: The directory directory is not accessibleto the process. The directory must exist and have therequired file permissions.

System action: Processing will terminate after theconfiguration parameter file is processed.

System administrator response: Verify that thedirectory exists and that the file permissions are correct.Restart the Tracker Agent.


EQQTX65E � EQQTX74E

EQQTX65E Process: Cannot determine local IPaddress, check system configuration

Explanation: Process could not determine the IPaddress for the local machine.

System action: Process terminates.

System administrator response: Ensure the localmachine is defined in the network. When the problemis resolved restart the Tracker Agent.

EQQTX66E Process: Connect request refused,unknown controller IP address ip_addr

Explanation: An unknown client has attempted toconnect to the Tracker Agent.


System administrator response: Ensure the IPaddress defined for the controller in the configurationparameter file is correct.

EQQTX67E Process: Unknown type found with valuevalue

Explanation: An unknown value was detected in theconfiguration parameter file.


System administrator response: Update theconfiguration parameter file with the correct value andrestart the Tracker Agent.

EQQTX68E Process: Required field field notspecified

Explanation: The required field field was not specifiedin the configuration parameter file.


System administrator response: Update theconfiguration parameter file with the required field.

EQQTX69E Process: Internal IPC message queueopen/read/write error, rc = rc

Explanation: Process failed to initialize a messagequeue.

System action: The Tracker Agent is terminated andrestarted.

System administrator response: Ensure there is notanother Tracker Agent already started. Check the errorcode (listed in /usr/include/sys/errno.h).

EQQTX70E Process: File file can not be accessed

Explanation: File file is not accessible to the process.The file must exist and have the correct filepermissions.


System administrator response: Verify that the fileexists and that the file permissions are correct. Restartthe Tracker Agent when the problem is resolved.

EQQTX71E Process: I/O error on file file, errno =error

Explanation: File I/O operation on the file file failed.


System administrator response: Check the errorcode (listed in /usr/include/sys/errno.h).

EQQTX72E Process: Workstation workstation is notdefined

Explanation: The workstation is not defined in theconfiguration parameter file.

System action: Process: terminates.

System administrator response: Check that there isa submittor associated with this workstation.

EQQTX73E Process: ID verification timed out

Explanation: During Tracker Agent initialization, the IDevent was not received back from the controller withinthe specified timeout period. The controller might havebeen shut down.


System administrator response: Ensure thecontroller is active.

EQQTX74E Process: Conversion table for codepagescodepage and codepage could not becreated

Explanation: The codepages defined in theconfiguration parameter file for either the Tracker Agentor the controller are not known on your system, or thecodepage conversion table required could not be found.


System administrator response: Verify thecodepages defined are valid and installed on yoursystem. Restart the Tracker Agent when the problem isresolved.



EQQTX75E Process: Job jobname will not beexecuted, script data is too large

Explanation: The Tracker Agent was unable toforward script data received for job jobname to asubmittor task because the script received from thecontroller is too large. The maximum size of script datahandled by the Tracker Agent is 15 800 bytes,excluding trailing blanks.

System action: The job is not started. It will bereported in Error status to the controller.

System administrator response: Split the script forthe job into two or more scripts and resubmit the job.

EQQTX76E Process: Could not get hostname for thecalling controller, errno = error

Explanation: The hostname for the calling host wherethe controller is started could not be determined. Anunknown client might have tried to connect to theTracker Agent.

System action: The Tracker Agent terminates.

System administrator response: Ensure the IPaddress defined in the configuration file is correct.Check the error code (listed in/usr/include/sys/errno.h).

EQQTX77E Process: Connection broken with thecontroller on ip_addr

Explanation: The connection to the controller hasbeen broken, The controller might have been shutdown.


System administrator response: Ensure thecontroller is started. Also verify that TCP/IP is startedon Tracker Agent and on controller systems.

EQQTX78E Process: ID time values mismatch

Explanation: The Tracker Agent has been unable toauthenticate the ID event returned from the controller.This could happen in an unauthorized client attempt toconnect to the Tracker Agent.


System administrator response: Verify theconfiguration parameters for both the Tracker Agent andthe controller. Ensure IP addresses and port numbersare correct.

EQQTX79E Process: Field field value value is notunique

Explanation: Field field value values must be unique.For example, two submittors cannot use the samecheckpoint file.


System administrator response: Update theconfiguration parameter file with a unique value for thefield.

EQQTX80E Process: Could not run setuid, jobjobname, user user, uid uid, errno = error

Explanation: A request to set the user ID for jobjobname to uid failed.


System administrator response: Check the errorcode (listed in /usr/include/sys/errno.h). Verify thatthe user ID supplied by the controller is defined on theTracker Agent system.

EQQTX81E Process: Could not run setgid, jobjobname, user user, gid gid, errno = error

Explanation: A request to set the user ID for jobjobname failed because the group ID (GID) could not beset for the supplied user ID.


System administrator response: Verify that the userID supplied by the controller is defined on the TrackerAgent system. Check the error code (listed in/usr/include/sys/errno.h).

EQQTX82E Process: Could not run chown to uid uid,gid gid, job jobname, user user

Explanation: A request to set the user ID for jobjobname to uid failed.


System administrator response: Verify that the userID specified has a primary group defined. The processProcess must be owned by root. The SUID bit must beon if the user ID supplied by the controller is not thesame user ID as is currently being used by the TrackerAgent.



EQQTX83E Process: Errors found while sendingdata to the controller on ip_addr

Explanation: An error was encountered while sendingdata to the controller.


System administrator response: Ensure TCP/IP isfunctioning correctly on Tracker Agent and controllersystems.

EQQTX84E Process: Failed to bind a socket to theport port_nr, errno = error

Explanation: Binding a socket to the local portnumber failed.

System action: Process will try again.

System administrator response: If you are using thedefault port number, or any other port number under1025, ensure the Process is owned by root and that theSUID bit is on. Check the error code (listed in/usr/include/sys/errno.h).

EQQTX85E Process: Could not open/create file file,errno = error

Explanation: File file could not be opened or created.

System action: The tracker is terminated.

System administrator response: Check that there issufficient disk space available for the file system wheretemporary and log files are stored. Look up the errorcode in the /user/include/sys/errno.h file.

EQQTX86E Process: Configuration file not verified

Explanation: Errors were detected in the configurationfile. One or more fields could not be validated.

System action: The Tracker Agent is terminated.

System administrator response: Update the requiredfields in the configuration parameter file, and restart theTracker Agent.

EQQTX87E Process: Component component notspecified

Explanation: Component component could not befound while processing the configuration parameter file.


System administrator response: Update the requiredfields in the configuration parameter file, and restart theTracker Agent.

EQQTX88E Process: Errors from LL llsubmit,jobname jobname, rc = rc

Explanation: Submit to LoadLeveler failed,LoadLeveler might not be active.

System action: Job jobname is not executed and isreported in Error status to the controller.

System administrator response: Ensure LoadLeveleris started.

EQQTX89E Process: User user does not exist, jobjobname is not submitted

Explanation: Username user does not exist in thesystem.

System action: The job jobname is reported in Errorstatus to the controller.

System administrator response: Define the user ID ifnecessary.

EQQTX90E Process: file is not a regular file

Explanation: The file must be a regular file. It cannotbe a directory, FIFO, or block device.

System action: Processing will be terminated after theconfiguration parameter file has been processed.

System administrator response: Ensure that file fileis a regular file.

EQQTX91E Process: Error Reading file file

Explanation: The file cannot be read. The file mightnot exist, or could not be read with the current filepermissions.

System action: Processing will be terminated after theconfiguration parameter file is processed.

System administrator response: Create the file orupdate the environment variable EQQHOME and restartthe Tracker Agent.

EQQTX92E Process: Error loading the parameter filefile

Explanation: A syntax error was detected whenloading the parameter file file.

System action: Processing terminates.

System administrator response: Check theparameter file for variables without associated values.Update the configuration parameter file and restart theTracker Agent.


EQQTX93E � EQQTX9AE

EQQTX93E Process: Error can not kill processprocess errno= error

Explanation: The tracker was requested to kill theprocess, but could not.


System administrator response: Check that theprocess is inactive. Check the error code (listed in/usr/include/sys/errno.h). Check that the subtaskhas authority.

EQQTX94E Process: Cannot find IPC queue queue

Explanation: The Tracker Agent verifies the IPCqueues when the parameter file is read. During thisverification the Tracker Agent could not find a requiredIPC queue.

System action: Processing terminates after theconfiguration parameter file is processed.

System administrator response: Contact your IBMrepresentative.

EQQTX95E Process: Workstation ID workstation mustbe nnnn characters long

Explanation: The ID must be more than 1 and lessthan 5 characters long. The first character must bealphabetic.

System action: Processing will terminate.

System administrator response: Rename theworkstation and restart the tracker.

EQQTX96E Process: proc failed. Reason code iscode and the tokens are tokens

Explanation: This message is normally associatedwith an I/O error.

System action: Depending on the severity of thereason, processing might be terminated. If themessage is received after the Tracker Agent hasexecuted for some time the message usually indicates aless severe error, and the Tracker Agent will continue toexecute. If the error occurs during Tracker Agentstartup, processing is terminated.

System administrator response: See Chapter 6,“Diagnosing Problems” on page 69 for a description ofreasons for Tracker Agent exit codes. Correct the errorand restart the Tracker Agent.

EQQTX97E Process: Program instance number numcan not be invoked, reason rsnc

Explanation: The program instance reported in themessage could not be invoked. The fork system callfailed.

System action: Processing is terminated.

System administrator response: Ensure themaximum number of processes defined for the systemand the user has not been exceeded. Also check thatthere is sufficient virtual memory on the machine tosatisfy the request. Correct the error and restart theTracker Agent. Chapter 6, “Diagnosing Problems” onpage 69 for a description of reasons for Tracker Agentcodes.

EQQTX98E Process: Environment variable var notset

Explanation: Environment variable var is not specifiedand the user ID tracker does not exist. The processcannot find the directory tree structure.


System administrator response: Set the environmentvariable EQQHOME or define the correct user ID, andrestart the tracker.

EQQTX99E Process: Loading of parsed data failed,reason rsnc, tokens token

Explanation: Process could not load the parsed data.


System administrator response: Examine themessage log for previous messages which describe theproblem. Correct the error and restart the TrackerAgent. See Chapter 6, “Diagnosing Problems” onpage 69 for a description of reasons for Tracker Agentcodes.

EQQTX9AE Process: Set environment host typefailed, reason rsnc, tokens token

Explanation: Process could not set the environmenthost type.




EQQTX9BE � EQQTX9KE

EQQTX9BE Process: Dropping of parsed data failed,reason rsnc

Explanation: Process was unable to drop the parseddata.



EQQTX9CE Process: Environment termination failed,reason rsnc, tokens token

Explanation: During daemon shutdown, the tracingenvironment could not be released.

System action: Termination processing continues.

System administrator response: Examine themessage and trace logs for previous messages whichdescribe the problem. See Chapter 6, “DiagnosingProblems” on page 69 for a description of reasons forTracker Agent codes.

EQQTX9DE Process: Process not created. Toomany processes active. Tokens fromtok -totok

Explanation: An Tracker Agent component could notbe started because the maximum number of concurrentprocesses has been reached.

System action: The Tracker Agent terminates.

System administrator response: Either decrease thenumber of submittor tasks defined for the TrackerAgent, or increase the maximum number of concurrentprocesses.

EQQTX9EE Process: Process could not be added toprocess control table

Explanation: There was insufficient space available incontrol blocks to add the process.


System administrator response: Decrease thenumber of submittor tasks defined and restart theTracker Agent.

EQQTX9FE Process: Executable name could not besubmitted, reason reason

Explanation: The executable subroutine identified inthe message text could not be started.


System administrator response: Check the name,path, and file permissions for the executable.

EQQTX9GE Process: Process proc is not activatedand will be discarded. Tokens token1 -token2 - token3 - token4

Explanation: The process could not be registeredwithin the timeout value.

System action: Processing continues. Thecomponent will be killed.

System administrator response: Check the messagelog for previous messages that describe the problem. Ifpossible, increase the value of –I specified when thedaemon is started.

EQQTX9HE Process: Shared memory operation -operation - could not be performed

Explanation: The shared memory operation create,attach, or drop could not be completed. View themessage log or other messages which describe theproblem.


System administrator response: Check if anotherdaemon process is already running.

EQQTX9IE Process: The parm parameter can only bespecified once

Explanation: A flag has been specified multiple timeson the start command.


System administrator response: Restart the TrackerAgent with the correct flags.

EQQTX9JE Process: An invalid parameter has beenpassed as parm

Explanation: An invalid flag was specified on the startcommand.



EQQTX9KE Process: The minimum number passedas flag is num

Explanation: An invalid value was specified for a flagon the start command. The value specified is below theminimum value.




EQQTX9LE � EQQTX9UE

EQQTX9LE Process: The maximum number passedas flag is num

Explanation: An invalid value was specified for a flagon the start command. The value specified is greaterthan the maximum value.



EQQTX9ME Process: directory is not a directory

Explanation: The file name directory is not a directory.The file name must be a directory and have therequired permissions.


System administrator response: Verify that thedirectory exists and that the file permissions are correct.

EQQTX9NE Process: Module module variable pointer= NULL

Explanation: Internal processing error detected inmodule. A variable pointer was detected as NULLwhen it should have a value.


System administrator response: Contact your IBMrepresentative.

EQQTX9OE Process: Cannot read the parameter filefile

Explanation: The configuration parameter file couldnot be read. The file must exist and have readpermission from the current process.


System administrator response: Verify that the fileexists, and that the user ID running the Tracker Agenthas read access.

EQQTX9PE Process: Error Initializing component rc =int

Explanation: The component could not be initialized.


System administrator response: Check previousmessages in the message log for messages describingthe reason for this error. Update files, or permissions,and restart the Tracker Agent.

EQQTX9QE Process: Unable to find error messages.Contact system administrator

Explanation: The process could not initialize themessage system.


System administrator response: Check the directorystructure, the environment variable, and the TrackerAgent user ID. Restart the Tracker Agent when theproblem is corrected.

EQQTX9RE Process: The passwd file for user IDuser could not be opened. Checkinstallation or set EQQHOME

Explanation: The environment variable EQQHOMEwas not set. The Tracker Agent defaults to the homedirectory of the Tracker Agent user ID. If this user IDdoes not exist or the home directory is inaccessible, theTracker Agent cannot find the required files.


System administrator response: Set the environmentvariable EQQHOME to point to an alternative tree ordefine the tracker user ID. Restart the Tracker Agentwhen the problem is corrected.

EQQTX9SE Process: Cannot export the environmentvariable var

Explanation: The tracker could not initialize theinternal environment variable.


System administrator response: Check theparameters in the configuration parameter file and runeqqverify.

EQQTX9TE Process: Could not initialize messagesystem: catalog cat log log

Explanation: Files required for writing messages couldnot be found, or the access permissions on the fileswere incorrect.

System action: Processing will terminate after theconfiguration parameter file is processed,

System administrator response: Check that the filesand the access permissions are correct. Restart theTracker Agent when the problem is corrected.

EQQTX9UE Process: Required field Host IP Addressnot specified in parameter file: file

Explanation: The IP address for the controller hostwas not found in the parameter file. The IP address forthe controller is required.



EQQTX9VE � EQQTXA5E

System administrator response: Update the fieldcontroller_ipaddr in the parameter file. The value of thisfield is the IP address of the controller. Restart theTracker Agent when the problem is corrected.

EQQTX9VE Process: Did not receive ID fromcomponents in tttt seconds

Explanation: The timeout period tttt expired withoutthe data router receiving the ID event.


System administrator response: Check theconfiguration parameter file and the message log.

EQQTX9XE Process: Log file logfile size nnnn toolarge for Event logfile

Explanation: A job log was found that is greater thanthe size of the event file.

System action: Processing continues, but the job logis not available.

System administrator response: Increase the eventwriter dataset size, and check the job output is notexcessive.

EQQTX9YE Process: Diskspace available indirectory directory less than minimumminimum

Explanation: There is too little filespace.

System action: An Offline event is sent to thecontroller. The job fails with code OSPC.

System administrator response: Increase the spaceavailable in the directory. Stop and restart the tracker.

EQQTX9ZE Process: Job job could not be executed,environment error, error = error

Explanation: The environment could not be initializedfor the job.

System action: The job does not run.

System administrator response: Check the user(UID), the group (GID), and the file permissions.

EQQTXA0E Process: Job job not executed. Trackerending due to lack of filespace.

Explanation: There is too little filespace.


System administrator response: Stop the tracker,increase the log space, and restart the tracker.

EQQTXA1E Process: I/O error sending data tocontroller size= size nbytes= nbyteserror= error

Explanation: The connection between the tracker andthe controller has been lost.

System action: The tracker tries to reconnect.

System administrator response: Check if thecontroller has gone down.

EQQTXA2E Process: creating socket to controllercontroller failed errno= error

Explanation: The Tracker Agent could not connect tothe controller.


System administrator response: Check the portnumbers and address in the controller and TrackerAgent configuration parameter files.

EQQTXA3E Process: Invalid data data read fromcontroller

Explanation: The tracker does not recognize incomingdata.

System action: The connection is closed.

System administrator response: Check the controllerand the TCP/IP connection.

EQQTXA4E Process: Error validating ID event datadata

Explanation: There is invalid data from the controller.


System administrator response: Check thesynchronization of clocks, restart the tracker, andrefresh the controller.

EQQTXA5E Process: Socket operation operationfailed sockfd= socket errno= error

Explanation: The tracker found an error whencommunicating with the controller.


System administrator response: Check the socketoperation (bind/listen). Check the error code (listed in/usr/include/sys/errno.h) to determine the cause.Stop and restart the tracker.


Appendix B. Utilities and Samples

The bin and samples directories supplied with the Tracker Agent contain utilitiesand samples to help you operate and maintain the Tracker Agent.

Utility Programs and ScriptsThese utility programs and scripts are located in the bin directory. If you need tomodify a script, save a copy of the original in the samples directory.

Note: Some parameters take a -f parameter, which you can use to specify theconfiguration parameter file name, if you do not use the EQQINSTANCE environmentvariable.

eqqstartThis script starts the Tracker Agent. If the environment variable EQQHOME is set, theTracker Agent starts from $EQQHOME/bin. Otherwise, the Tracker Agent starts from∼tracker.

The flags for start-up are:

Flag Description

-d|D Engine timeout, in minutes.

When a process signals that it is active, this value specifies the maximumtime allowed before it must send another active or idle signal. If the defaultvalue is used, a process cannot be active for more than five minutes withoutsending another active or idle signal, or the Tracker Agent will automaticallyshutdown and restart.

-i|I Maximum inactivity time for server.

This is the time allowed for a process to become active. Change it only inspecial cases.

-f|F The configuration parameter file name.

You need not specify this if you have set the EQQINSTANCE variable, or if theconfiguration parameter file is $EQQHOME/EQQPARM.

-r|R Time between automatic restart, in minutes.

At these intervals (for example, once a day), the daemon will refresh eachprocess.

-s|S Sleep between restart, in seconds.

It takes about five seconds to complete a clean shutdown of the TrackerAgent processes. Sometimes it can be useful to delay the time betweenautomatic restart attempts.

-v|V The number of times, within a number of minutes, a process is allowed torestart before the Tracker Agent terminates abnormally. For example, thevalue -v4:1ð specifies that the Tracker Agent will restart up to 4 times in a10-minute period.

There are two reasons for restart:

� A process has been active more than 5 minutes without a signal.


Utilities

� A process has abnormally terminated.

The eqqstart sample script passes these flags unaltered to the Tracker Agentdaemon. You can change the eqqstart sample script if you want to change thedefaults.

The flags can be entered either as uppercase or lowercase characters. There is nodifference in how they are treated.

Syntax

55──eqqstart─ ──┬ ┬───────────── ──┬ ┬─────────────────── ───────────────5 └ ┘─-f filename─ └ ┘─-i inactive-limit─

5─ ──┬ ┬────────────────── ──┬ ┬────────────────── ──────────────────────5 └ ┘─-v restart-limit─ └ ┘─-d timeout-limit─

5─ ──┬ ┬───────────────────── ──┬ ┬────────────────── ──────────────────5% └ ┘─-r refresh-interval─ └ ┘─-s restart-delay─

You can specify these values for the flags:

Table 11. Values of Tracker Agent flags

Flag Min Max Default

d|D 1 600 5

f|F - - -

i|I 1 600 30

r|R 1 65535 0

s|S 0 60 0

v|V 1:1 200:2880 1:1

eqqverifyThis utility shows the Tracker Agent settings. The Tracker Agent configurationparameters are written to the $EQQHOME/log/eqqmsglog. The verified values arealso written to the terminal. If a parameter cannot be verified, a message isgenerated describing the problem.

Syntax

55──eqqverify─ ──┬ ┬───────────── ────────────────────────────────────5% └ ┘─-f filename─

eqqstopThis script stops the Tracker Agent. The current tracker processes are searchedfor the daemon. The daemon is sent a SIGHUP, (1) and exits normally.

Syntax

55──eqqstop─ ──┬ ┬───────────── ──────────────────────────────────────5% └ ┘─-f filename─


Utilities

eqqfmYou can run this utility program to check for file arrivals. The program checks forthe existence and size of files you define in an event-control file (ECF), which ispassed to the program as a parameter. There is a sample ECF in the samplesdirectory. The program supports two types of files, flag files, where the size is notverified, and data files, where the size is checked.

The checking is performed using a time interval of 60 seconds. If the size is thesame as when last checked, the file is considered stable and will be checkedagainst the ECF values to verify if the file is larger than the value specified.

Syntax

55──eqqfm──ECF_file────────────────────────────────────────────────5%

Parameter :

ECF_fileSpecifies the name of an ECF file.

The format of the file is:

% <time_trigger><type> <filename> <size>

| <time_trigger> has a format of yyyy:mm:dd:hour:min

where:

| 'yyyy' must be within ðððð - 9999,

'mm' must be within ð1 - 12,

'dd' must be in the range allowed for the month and year,

'hour' must be within ðð - 24,

'min' must be within ðð - 59.

<type> can be ð (flag file) or 1 (data file)

<filename> filename including path.

<size> expected size for data files, any number for flag files.

For example:

| % 1994:ð4:13:1ð:ðð

ð /u/tracker/fileð1 ð

1 /u/tracker/fileð2 1ð

This example tells eqqfm to check for the existence of fileð1 and fileð2. Thesize of fileð2 must be greater than 10 bytes.

The program returns:

0 The file exists and matches the criteria specified.1 The time expired before the file arrived.2 The file has arrived, but is smaller than expected.5 The format of time_trigger is incorrect.

You can include the utility as the first program in a script, and continue processingbased on the return code.

Appendix B. Utilities and Samples 95

Utilities

eqqdeleteThis script can be used to delete old log files according to the age of the files. Thiscan be run periodically to clean up the disk. There is one parameter—the age indays. All Tracker Agent log files older than the value specified are deleted. Theutility looks in the $EQQHOME/log directory.

Syntax

55──eqqdelete─ ──┬ ┬───── ────────────────────────────────────────────5% └ ┘─age─

Parameter :

age | 0All Tracker Agent log files older than the value specified are deleted. If novalue is given, the eqqdelete script deletes all the files in the log directory.

Sample output:

$ eqqdelete 1ð

Cleaning from EQQHOME /u/tracker

Cleaning files from /u/tracker older than 1ð days

Cleaning /u/tracker/log

eqqviewUse this utility to browse the event logfile and the submit checkpoint file.

Syntax

55──eqqview─ ──┬ ┬─-e eventlog─ ──────────────────────────────────────5% └ ┘─-s ckptfile─

Parameters :

-e eventlogEnter this parameter to browse the event logfile. A command line will beprompted to enter the record number you want to view. The default is 1. Thenext record is displayed when you press Enter. Enter q to quit at any time.

-s ckptfileEnter this parameter to to view the last checkpointed submit sequence number.

The environment variable EQQHOME must point to the current tracker environment.eqqview tries to open the named file in $EQQHOME/log (replace eventlog and ckptfilewith the names specified in the configuration parameter file).


Utilities

eqqinitAttention: Do not run eqqinit for the Digital OpenVMS Tracker Agent.

Use this script to create a local directory, or to create symbolic links to the directorywhere the software is installed.

If you do not use a conventional directory file structure, you can edit this script file.

Syntax

55──eqqinit─ ──┬ ┬─-v─ ───────────────────────────────────────────────5% └ ┘─-t─

Parameters :

-v Enter this parameter to configure the local (log and tmp) directories. Run thisas root.

-t Enter this parameter to make symbolic links to the directories where thesoftware is installed. Run this under the tracker user ID.

eqqcleanThis script tidies the log files after the tracker has terminated abnormally.

Syntax

55──eqqclean───────────────────────────────────────────────────────5%

eqqpermThis script sets file permissions. It is necessary when you install the SunOSTracker Agent, but optional for the others.

Syntax

55──eqqperm────────────────────────────────────────────────────────5%


Utilities

eqqcv80pThis utility converts scripts so that they can be submitted using the Tivoli OPCcontroller. You can store your scripts on the Tracker Agent machine, or on MVS inthe Tivoli OPC EQQJBLIB concatenation. If you store the scripts in the EQQJBLIBdatasets, the data must be in a PDS with a fixed record length of 80 bytes. If youhave scripts with longer data lines you can still store the data on MVS, if you usethis utility to convert the script data to 80-byte records. Alternatively, you can editthe script manually.

The eqqcv8ðp utility reads data from a file and breaks down lines exceeding 80bytes into 80-byte records. Changed records are marked with a / in column 80. Ifcolumn 80 already has a /, column 1 of the next line will be marked with a /. Linesshorter than 80 bytes are padded with blanks.

Syntax

┌ ┐─<──infile──55──eqqcv8ðp─ ──┬ ┬──────────── ──┬ ┬──── ──┼ ┼──────────── ───────────────5 └ ┘ ─-l──length─ └ ┘─-n─ └ ┘ ─-f──infile─

5─ ──┬ ┬──────────── ─────────────────────────────────────────────────5% └ ┘ ─>──outfile─

Parameters :

-l length | 80The number of columns in a row. If not specified, a value of 80 is used.

-n If specified, no newline character will be inserted at the end of the rows in theoutput file. The default is to insert newline characters.

-f infile | < infileThe name of the input file. If you do not specify -f, the utility expects inputfrom stdin.

> outfileSpecify this to redirect the stdout output to a file.

eqqshowThis script shows the status of the Tracker Agent. The daemon process, theTracker Agent processes, shared memory, and message queues are displayed.

Syntax

55──eqqshow─ ──┬ ┬───────────── ──────────────────────────────────────5% └ ┘─-f filename─


Utilities

SamplesThe samples directory contains these files:

File name Description

ecf Sample event control file used by the eqqfm utility.

tracker.cmd Sample LoadLeveler script. See “Sample LoadLeveler script”on page 108 for a listing.

The etc directory contains these files:

File name Description

EOP0 This is a sample configuration parameter file for a Tivoli OPCcontroller.


Appendix C. Enabling the Pulse Functions

This appendix explains how to enable the Pulse functions. To do this, you set upthe KEEPALIVE parameters on the controller image and on the tracker agentmachines for the AIX, UNIX, VMS, and OS/390 Open Edition platforms.

To activate the SO_KEEPALIVE option on the tracker agent machine, you mustconfigure the KEEPALIVE parameters. These parameters differ for each operatingsystem. When you specify the SO_KEEPALIVE option, TCP/IP periodically sendspackets to check that the other end of the connection is still available. If the otherend of the connection is not available, it terminates the channel.

Note: To enable automatic recovery of communication between the controller anda tracker that is using the KEEPALIVE functionality, perform any corrective actionfor network problems after the expiration of the specified KEEPALIVE timeout time.By that time, the controller and tracker will have registered the loss of the remotepartner. Only then can the controller and tracker recover communication after thenetwork problem has been fixed.

You can define time intervals to control the behavior of the SO_KEEPALIVE option.When you change the time interval, only those TCP/IP channels started after thechange are affected. The value that you choose for the time interval should be lessthan the value of the disconnect interval for the channel. Make sure you choose anappropriate value for the time interval: too high a value may not be useful, whereastoo low a value may create a lot of traffic in the network.

| Setting Up the Controller Machine and OS/390 OE SystemAdd the following statement to the TCP/IP profile:

KEEPALIVEOPTIONS INTERVAL mmm SENDGARBAGE TRUE ENDKEEPALIVEOPTIONS

where mm is the idle connection. It defaults to 120 minutes.

Setting Up an AIX SystemTo implement the KEEPALIVE functionality, use the no command to configure thefollowing TCP/IP parameters in the kernel:

tcp_keepidle Specifies the length of time to keep the connection active,measured in half seconds. The default is 14400 halfseconds (7200 seconds or 2 hours).

tcp_keepinit Sets the initial timeout value for a tcp connection. Thisvalue is defined in 0.5-second increments, and defaults to150, which is 75 seconds.

tcp_keepintvl Specifies the interval, measured in half-seconds, betweenpackets sent to validate the connection. The default is 150half seconds (75 seconds).

The no command operates only on the currently running kernel; it must be runagain after each startup or after the network has been configured.


Pulse Functions

Attention: The no command performs no range checking. Because it thereforeaccepts all the values for the variables, if it is used incorrectly, it can cause thesystem to become inoperable.

Syntax

no -o Option [ =NewValue]

The -o flag both sets and displays an option value.

Example:

no -o tcp_keepidle=24ð

Sets the keepalive time to 2 minutes.

Setting Up an HP SystemThe following TCP/IP parameters should be configured to implement theKEEPALIVE functionality:

tcp_keepstart Valid range: 5–12000 secondsDefault: 7200 secondsDescription: Specifies the number of seconds that a TCPconnection can be idle (that is, no packets are received)before keepalive packets will be sent in an attempt to elicit aresponse. After a packet is received, further keepalivepackets are sent only if the connection is again idle for thisperiod of time.

tcp_keepfreq Valid range: 5-2000 secondsDefault: 75 secondsDescription: Specifies the interval in seconds at whichkeepalive packets will be sent on a TCP connection oncethey have been started. The receipt of a packet will stop thesending of keepalive packets.

If you are increasing both tcp_keepfreq and tcp_keepstop,increase tcp_keepstop first. If you are decreasing both,decrease tcp_keepfreq first.

tcp_keepstop Valid range: 10–4000 secondsDefault: 600 secondsDescription: Specifies the number of seconds keepalivepackets will be sent on a TCP connection without the receiptof a packet after which the connection will be dropped.

If you are increasing both tcp_keepfreq and tcp_keepstop,increase tcp_keepstop first. If you are decreasing both,decrease tcp_keepfreq first.

From HP–UX Version 10.01, the nettune command, located in /usr/contrib/bin, isavailable to set these TCP/IP parameters.

Syntax

nettune -s Object Value


Pulse Functions

Example:

nettune -s tcp_keepfreq 24ð

Setting Up a SunOS SystemAttention: The kernel must be recompiled and replaced when you configure theKEEPALIVE parameter. It is therefore recommended that you do not use theKEEPALIVE implementation on a SunOS system.

To implement the KEEPALIVE functionality on this system, configure the followingTCP/IP parameters in the kernel:

tcp_keepidle Determines how frequently to test whether an idleconnection is still alive. The default value is 7200 seconds(2 hours).

tcp_keepintvl Determines how frequently to check an idle connection if thefirst check has failed. The default value is 75 seconds.

These parameters are set as standard C declarations in the file/sys/netinet/in_proto.c. After you modify them, you must rebuild the kernel.

Recompiling the KernelTo recompile the kernel:

1. # more /etc/motd

Show the current kernel.2. # arch -k

Show the architecture.3. # cd /usr/kvm/sys/sun4m/conf4. # cp GENERIC GENERIC_NEW

Copy the kernel and use the new version.5. # config GENERIC_NEW

Allocate the directory ../GENERIC_NEW.6. # cd ../GENERIC_NEW

7. # make

Create the file vmunix.8. # mv /vmunix /vmunix.orig

Save the original vmunix file.9. # cp vmunix /vmunix

Copy the new kernel file to the root directory.10. Reboot the machine to verify that everything is correct. If you experience any

problems, reboot with the old vmunix, using the command:

> b vmunix.orig -s

Appendix C. Enabling the Pulse Functions 103

Pulse Functions

Setting Up a Sun Solaris SystemTo implement the KEEPALIVE functionality on a Sun Solaris system, configure thefollowing TCP/IP parameter:

tcp_keepalive_interval Determines how frequently to test whether an idleconnection is still alive. The default value is 7200000 ms (2hours).

Use the ndd command to tune this TCP/IP parameter.

To list all the appropriate variables, supply the ndd command with the driver nameand a ?. For example:

% ndd /dev/tcp \?

Note: Under Solaris 2.5 or higher, you will need to be user root to display thesevariables.

You can change ndd variables by supplying the -set option, the variable name, andthe value. For example:

% ndd -set /dev/tcp tcp_keepalive_interval 1ðððððð

To set an ndd variable each time you boot the system, add a line for it in the file/etc/rc2.d/S69inet, as follows:

% cat /etc/rc2.d/S69inet...

#

# Set configurable parameters.

#

ndd -set /dev/tcp tcp_keepalive_interval 1ðððððð

Setting Up a MIPS ABI SystemAttention: Changes to tcp_keepidle directly affect the system kernel. It istherefore not recommended that you use the KEEPALIVE implementation on aMIPS ABI system.

The only parameter to set is the tcp_keepidle parameter. To set it, edit followingfile:

/var/sysgen/master.d/bsd

You will need to have at least one of the older network patches to findtcp_keepidle. The IRIX 5.3 Recommended Patch Set is recommended.

Setting Up a Digital OpenVMS SystemThe KEEPALIVE function is not available on Digital OpenVMS systems.


Pulse Functions

Setting Up a Digital UNIX SystemModify the Internet Subsystem (inet) KEEPALIVE attributes defined in the/etc/sysconfigtab file, using the dxkerneltuner or sysconfig command.

tcp_keepalive_default When set to 1, the tcp_keepalive_default attribute EnablesTCP keepalive for all sockets. Use this attribute to overrideprograms that do not set keepalive on their own or for whichyou do not have access to the application sources.

Default value: 0 (disabled)tcp_keepcnt The maximum number of keepalive probes that can be sent

before a connection is dropped.

Default value: 8 probestcp_keepidle Idle time before the first keepalive probe.

Default value: 2 hours (in increments of 0.5 seconds)tcp_keepinit Initial connect timeout.

Default value: 75 seconds (in units of 0.5 seconds)tcp_keepintvl The time between keepalive probes.

Default value: 75 seconds (in increments of 0.5 seconds)

Appendix C. Enabling the Pulse Functions 105

Appendix D. Using LoadLeveler

The Tracker Agent is supplied already linked with LoadLeveler modules at theVersion 1 Release 2 base level. Before applying service to LoadLeveler, check thedocumentation to see if you must also apply service updates to the LoadLevelersubmittor.

Ensure the user loadl has permissions to execute the Tracker Agent exit program(eqqlsext). loadl should also have read and write permissions to the directory fortemporary and log files. You must also set the SUID bit on. To do this, login asroot and enter:

chown root: eqqls

chmod u+s eqqls

If you use the Tivoli OPC job-submit exit (EQQUXðð1) to supply the user ID of jobs tobe submitted by the Tracker Agent, the LoadLeveler submittor must run as root.This can be done by changing the owner of the LoadLeveler submittor to root.

For AIX only

If the LoadLeveler submittor is used, you must set the environment variableLIBPATH for the Tracker Agent to include the LoadLeveler shared library. TheTracker Agent cannot start the LoadLeveler submittor if this is not set. SetLIBPATH using this command:

export LIBPATH=$LIBPATH:/usr/lpp/LoadL/nfs/lib

If LoadLeveler is not installed in the standard directory, adjust the path to theLoadLeveler directory.

Ensure the user loadl has permissions to execute the Tracker Agent exitprogram (eqqlsext). loadl should also have read and write permissions to thedirectory for temporary and log files.

If you use the Tivoli OPC job-submit exit (EQQUXðð1) to supply the user ID ofjobs to be submitted by the Tracker Agent, the LoadLeveler submittor must runas root. This can be done by changing the owner of the LoadLeveler submittorto root. You must also set the SUID bit on. To do this, login as root andenter:

chown root: eqqls

chmod u+s eqqls

Then create (still as root) a link for the LoadLeveler shared library, such as:

/usr/lib/libllapi.a -> /usr/lpp/LoadL/lib/libllapi.a


LoadLeveler

This submittor is based on LoadLeveler and takes advantage of load balancing in alarge network of UNIX machines. The LoadLeveler submittor passes every job(LoadLeveler script) to LoadLeveler using the LoadLeveler application programinterface (API), llsubmit. The LoadLeveler API submits the job and calls theTracker Agent exit program to report job status to the Event Writer.

Job logs from LoadLeveler submittor-submitted jobs can not be captured andreturned to the controller, because LoadLeveler does not support this.

This submittor uses only one fork system call. Child processes do setuid/setgid ifthe user ID is supplied by the controller. When the submit is successful, amessage is written to the message log file with the returned LoadLeveler job ID.The parent process continues doing fork without waiting for child processes tofinish.

Sample LoadLeveler scriptThis is the file tracker.cmd in the samples directory:

#!/bin/ksh

# @ job_name = tracker

# @ input = /dev/null

# @ output = $(Executable).OUT

# @ error = $(Executable).OUT

# @ notification = never

# @ checkpoint = no

# @ restart = no

# @ queue

echo "Start LL tracker"

date

uname -a

echo "End LL tracker"

RestrictionsYou cannot browse the job log of scripts submitted using LoadLeveler.

When the Tracker Agent is started as root, the LoadLeveler submittor uses thetracker user ID. LoadLeveler does not support the submission of jobs using theroot user ID.

The controller cannot specify a user ID if the script will run under LoadLeveler: theLoadLeveler runs all scripts under its own user ID.


Appendix E. EBCDIC and ASCII Codepage Tables

These tables convert between ISO (ASCII) and EBCDIC single-byte stateless codesets. The following types of conversions are supported: PC to/from ISO, PCto/from EBCDIC, and ISO to/from EBCDIC. Conversion is provided betweencompatible Latin-1 code sets: double-byte character set conversion is notsupported. Conversion tables in the iconvTable directory are created by the genxltcommand.

A character that exists in the source code set but does not exist in the target codeset is converted to a converter-defined substitute character by the iconvTableconverters found in the $EQQHOME/nls/loc/iconvTable directory.

Table 12. Codepage Compatibility

Languages ISO (ASCII) EBCDIC

U.S. English, Portuguese,Canadian French

ISO8859-1 IBM-037

Danish, Norwegian ISO8859-1 IBM-277

Finnish, Swedish ISO8859-1 IBM-278

Italian ISO8859-1 IBM-280

Japanese ISO8859-1 IBM-281

Spanish ISO8859-1 IBM-284

U.K. English ISO8859-1 IBM-285

German ISO8859-1 IBM-273

French ISO8859-1 IBM-297

Belgian, Swiss German ISO8859-1 IBM-500


Appendix F. Machine and Program Requirements for AIXSystems

This appendix describes the hardware and software needed to operate the TrackerAgent under AIX.

Attention: This does not include the hardware and software necessary to runTivoli OPC or the OPC Tracker Agent enabler.

Hardware RequirementsThe Tracker Agent for AIX/6000 requires a RISC Systems/6000 computer, with a

| minimum of 3 MB of RAM, capable of running AIX/6000 Version 4.2.1 or later. 8MB of RAM is recommended for performance reasons.

The Tracker Agent also requires:

� Approximately 20 MB of disk space for the components

� Additional space on the local hard disk for the log files and other temporarydata it generates. The volume of data is highly dependent on the volume andoutput of jobs managed by the Tracker Agent.

Software Requirements| The Tracker Agent requires AIX Version 4.2.1 or later.


Appendix G. Machine and Program Requirements for HP-UXSystems

This appendix describes the hardware and software needed to operate the TrackerAgent under HP-UX.


Hardware RequirementsThe Tracker Agent for HP–UX requires a 700-series computer, capable of running

| HP–UX Version 10 or Version 11. It uses between 500 KB and 1 MB of memory.




Software Requirements| The Tracker Agent requires the Hewlett-Packard HP–UX Operating System Version| 10 or Version 11.


Appendix H. Machine and Program Requirements for SolarisSystems

This appendix describes the hardware and software needed to operate the TrackerAgent under Solaris.


Hardware RequirementsThe Tracker Agent for Sun Solaris requires a SPARC** computer capable ofrunning Solaris Version 2 Release 3. It uses between 500 KB and 1 MB ofmemory.




Software RequirementsThe Tracker Agent requires the following software:

� Sun Solaris Version 2 Release 3 or later.


Appendix I. Machine and Program Requirements for SunOSSystems

This appendix describes the hardware and software needed to operate the TrackerAgent under SunOS.


Hardware RequirementsThe Tracker Agent for Sun OS requires a SPARC computer capable of runningSunOS Version 4 Release 1 Modification Level 3 (Sun Solaris Version 1 Release 1Modification Level 1). It uses between 500 KB and 1 MB of memory.





| � SunOS Version 4 Release 1 Modification 3_v1 (Sun Solaris Version 1 Release1 Modification Level 1)


Appendix J. Machine and Program Requirements for DigitalOpenVMS Systems

This appendix describes the hardware and software needed to operate the TrackerAgent under Digital OpenVMS.


Hardware RequirementsThe Tracker Agent for Digital OpenVMS requires one of the following:

� A DEC VAX computer, with at least 16 MB of disk space, capable of runningOpenVMS Version 7.0 or 7.1

� A DEC Alpha computer, with at least 32 MB of disk space, capable of runningOpenVMS Version 7.0 or 7.1


� Approximately 1 MB of memory



� OpenVMS Version 7.0 or 7.1


| Appendix K. Machine and Program Requirements for Silicon| Graphics IRIX Systems

This appendix describes the hardware and software needed to operate the TrackerAgent under Silicon Graphics IRIX.


Hardware Requirements| The Tracker Agent for Silicon Graphics IRIX requires:

| an SGI Indigo2 Family computer capable of running Silicon Graphics IRIX| Version 5.3.





� DC/OSx Version 1.1.


Appendix L. Machine and Program Requirements for DigitalUNIX

This appendix describes the hardware and software needed to operate the TrackerAgent under Digital UNIX.


Hardware RequirementsThe Tracker Agent for Digital UNIX requires:

| � A DEC Alpha computer, with at least 32 MB of disk space, capable of running| UNIX 4.0D or later.





| � Digital UNIX Version 4.0D or later


Appendix M. Machine and Program Requirements for OS/390

This appendix describes the hardware and software needed to operate the TrackerAgent under OS/390.


Hardware RequirementsThe Tracker Agent for OS/390 Open Edition runs on any IBM hardwareconfiguration supported by OS/390 Version 1 Release 3.

The Tracker Agent requires:

� Approximately 20 MB of file system space

� A display terminal supported by ISPF Version 4 or later, to invoke and run OPChost dialogs


� OS/390 Version 1 Release 3 or later with Open Edition services � TCP/IP 3.2


Appendix N. Applying Tracker Maintenance on Non-AIXMachines

The tracker PTFs (or fixes) are shipped as compressed tar files. The namingconvention for non-AIX PTFs is:

/usr/lpp/tracker/images/tracker.ptf.<platform>.Z

where <platform> is a shortform name for the remote tracker, that is:

hp For the HP-UX tracker agentsun For the SunOS tracker agentsol For the Sun Solaris tracker agentdux For the Digital UNIX tracker agent

| mips For the Silicon Graphics IRIX tracker agentomvs For the OS/390 Open Edition tracker agent

To install the PTFs on a non-AIX tracker machine, follow this procedure:

cd /usr/lpp (directory above the tracker sub-directory tree)

ftp controller

binary

get OPCDATASET(OPCMEMBER) tracker.ptf.<platform>.Z

For OPC, replace OPCDATASET and OPCMEMBER with the correct informationfor the remote non-AIX tracker you are installing.

To extract the compressed tar file on the non-AIX remote tracker machine:

uncompress tracker.ptf.<platform>.Z| tar xvof tracker.ptf.<platform>

The tracker subdirectories will be updated with the binaries from the PTF.


Glossary

AABARS . See Aggregate Backup and RecoverySupport.

active application description . An applicationdescription that is complete and ready for use inplanning or scheduling.

actual duration . At a workstation, the actual time inhours and minutes it takes to process an operation fromstart to finish.

adjusted quantity . The current quantity of a specialresource, taking the deviation into account.

AD. See application description.

Aggregate Backup and Recovery Support(ABARS) . A DFHSM facility that manages backup andrecovery of user-defined data set groups (aggregates).Aggregate backup copies and related controlinformation are written as portable data and control fileson 3480 or 3420 volumes.

Advanced Program-to-Program Communications(APPC). An implementation of the Systems NetworkArchitecture (SNA), logical unit (LU) 6.2 protocol thatallows interconnected systems to communicate andshare the processing of programs.

all-days cyclic period . A cyclic period where all daysare counted when calculating the interval.

alert . Two Workload Monitor/2 objects, Operations Listand Workstations List, can be used to monitor a TivoliOPC subsystem and notify you if alert conditions aremet. The alert can be a sound (Beep), or a message ina window (Message). The Details view of the Planobject must be open to monitor for plan alerts. The Listor Icons views of the Operations List object must beopen to monitor for operation alerts.

APAR . Authorized program analysis report. A reportof a problem that is suspected to be caused by a defectin a current, unaltered release of a program.

API. See application programming interface.

APPC. See Advanced Program-to-ProgramCommunications.

application . A measurable and controllable unit ofwork that completes a specific user task, such as therunning of payroll or financial statements. The smallest

entity that an application can be broken down into is anoperation. Generally, several related operations makeup an application.

application description (AD) . A database descriptionof an application.

application group . Type of application descriptionwhich holds run cycle and calendar information forstandard applications or job descriptions which havebeen defined as a member of the group.

application ID . The name of an application. (Forexample, PAYROLL or DAILYJOBS.)

application programming interface (API) . Aformally-defined programming language interfacebetween an IBM system control program or a licensedprogram and the user of a program.

application transaction program (ATP) . A programthat uses the Advanced Program-to-ProgramCommunications (APPC) application programminginterface (API) to communicate with a partner programat a remote node.

application version . See versions.

ATP. See application transaction program.

authority . The ability to access a protected resource.

authority group . A name used to generate a RACFresource name for authority checking.

automatic events . Events recognized by or triggeredby an executing program. Automatic events are usuallygenerated by Tivoli OPC tracking programs but can alsobe created by a user-defined program.

automatic hold/release . Function used to control jobsthat are submitted outside Tivoli OPC. It allows you todefine whether such jobs should be automaticallyreleased at the appropriate time if placed in HOLDstatus when submitted.

automatic job and started-task recovery . A TivoliOPC function that lets you specify, in advance,alternative recovery strategies for operations that end inerror.

automatic-reporting workstation . A workstation (forexample, a processor or printer) that reports events (thestarting and stopping of operations) in real time to TivoliOPC.


availability . The degree to which a system (and inTivoli OPC, an application) or resource is ready whenneeded to process data.

Bbatch loader . A Tivoli OPC batch program that youcan use to create and update information in theapplication-description and operator-instructiondatabases.

buffer . A memory area reserved for performinginput/output (I/O) operations.

BMP. Batch message processing.

Ccalendar . The data that defines the operationdepartment's work time in terms of work days and freedays.

capacity . The actual number of parallel servers andworkstation resources available during a specified openinterval.

capacity ceiling . The maximum number of operationsthat a workstation can handle simultaneously.

catalog . A directory of files and libraries, withreference to their locations. A catalog may containother information such as the types of devices in whichthe files are stored, passwords, blocking factors.

catalog management . Catalog management is arecovery function of Tivoli OPC, which handles thedeleting or uncataloging of datasets created in a joboperation that ends in error.

CICS. Customer Information Control System.

closed workstation . A workstation that is unavailableto process work for a specific time, day, or period.

Common Programming Interface (CPI) . A consistentset of specifications for languages, commands, andcalls to enable applications to be developed across allSystems Application Architecture (SAA) environments.

complete (C) . The status of an operation indicatingthat it has finished processing.

completion code . A Tivoli OPC system code thatindicates how the processing of an operation ended at aworkstation. See error code.

complex of processors . A JES2 Multi-Access Spoolsystem or a JES3 system with more than oneprocessor.

computer workstation . (1) A workstation thatperforms MVS processing of jobs and started-taskoperations, and that usually reports status to Tivoli OPCautomatically. (2) A processor used as a workstation.It can refer to single processors or multiprocessorcomplexes serving a single job queue (for example,JES2 or JES3 systems).

contingency plan . A plan for emergency response,backup procedures, and post-disaster recovery.Synonymous with disaster recovery plan, emergencyplan.

controller . The Tivoli OPC component that runs onthe controlling system, and that contains the Tivoli OPCtasks that manage the Tivoli OPC plans and databases.

controlling system . The system that the controllerruns on.

control on servers . If a workstation is defined withcontrol on servers, OPC/ESA will not start moreoperations at the workstation than there are availableservers.

conversation . In Advanced Program-to-ProgramCommunications (APPC), a connection between twotransaction programs over a logical unit-logical unit(LU-LU) session that allows them to communicate witheach other while processing a transaction.

conversation verb . In Advanced Program-to-ProgramCommunications (APPC), one of the verbs a transactionprogram issues to perform transactions with a remoteprogram.

CP. See current plan.

CPI. See Common Programming Interface.

CPI-C. Common Programming Interface forCommunications. See also Common ProgrammingInterface.

cross-system coupling facility (XCF) . MVScomponents and licensed programs use the XCFservices to provide additional functions in a SYSPLEX.

critical path . The route, within a network, with theleast slack time.

current plan (CP) . A detailed plan of system activitythat covers a period of at least 1 minute, and not morethan 21 days. A current plan typically covers 1 or 2days.

cyclic interval . The number of days in a cyclic period.

cyclic period . A period that represents a constantnumber of days. There are two types of cyclic periods:


� Work-days-only cyclic period, where only the workdays are counted when calculating the number ofdays in the period.

� All-days cyclic period, where all days are counted.

Ddaily planning . The process of creating a currentplan.

DASD. Direct access storage device.

database . A collection of data that is fundamental to asystem. Tivoli OPC uses six databases: calendar,period, workstation description, JCL variable table,application description, and operator instruction.

Data Facility Hierarchical Storage Manager(DFHSM). A licensed MVS program which providesautomatic and command functions that manage userstorage space and data recovery.

Data Facility Systems Management Subsystem/MVS(DFSMS/MVS). A group of licensed MVS programswhich transform system environments fromuser-managed DASD volumes toadministrator-controlled, system-managed data sets.

Data Lookaside Facility (DLF) . The MVS/ESAcomponent that manages Hiperbatch objects.

data processing center (DP center) . A center ordepartment, including computer systems and associatedpersonnel, that performs input, processing, storage,output, and control functions to accomplish a sequenceof operations on data.

| Data Store . The Tivoli OPC component managing the| job runtime information at the tracked system. It is| dedicated to the storing and possible retrieval of sysout| datasets belonging to OPC-submitted jobs, to optimize| the sysout availability.

DB2. DATABASE 2.

DBCS. Double-byte character set.

ddname . Data definition name.

deadline . See deadline date and deadline time.

deadline date . The latest date by which an occurrencemust be complete.

deadline time . The latest time by which an occurrencemust be complete.

deadline WTO message . You can specify that TivoliOPC issue an operator message (EQQW776I) when astarted operation has not been marked as completedbefore the deadline time. In addition to the standardmessage, the user-defined text that describes theoperation is issued as part of the WTO.

default calendar . (1) A calendar that you havedefined for Tivoli OPC to use when you do not specify acalendar in an application description. (2) A calendarthat Tivoli OPC uses if you have neither specified acalendar in an application description, nor defined yourown default calendar.

dependency . A relationship between two operations inwhich the first operation must successfully finish beforethe second operation can begin.

descriptive text . User-written text describing theoperation. This text is also issued as part of thewrite-to-operator message if the operation has beenstarted, exceeds its deadline, and has the deadlinewrite-to-operator (WTO) option specified.

Details notebook . See Details view.

Details view . A view of a Workload Monitor/2 objectshowing details about the object. The Details view ofthe Plan object shows information about the currentplan. The Details view of the Operation object showsinformation about the selected operation. The Detailsview of the Workstation object shows information aboutthe selected workstation.

deviation . A temporary variation in the quantity of aspecial resource.

DFHSM. See Data Facility Hierarchical StorageManager.

DFSMS/MVS. See Data Facility Storage ManagementSubsystem.

dialog . The user's online interface with Tivoli OPC.

Disaster Recovery Plan (DRP) . A plan for emergencyresponse, backup procedures, and post-disasterrecovery. Synonymous with contingency plan,emergency plan.

DLF. See Data Lookaside Facility.

DP center . See data processing center.

DRP. See Disaster Recovery Plan.

duration . The length of time an operation is active at aworkstation.

Glossary 131

Eend user . A person who uses the services of the dataprocessing center.

ended-in-error (E) . The Tivoli OPC reporting status foran operation that has ended in error at a workstation.

error code . A code set by Tivoli OPC to describe howthe processing of an operation ended at a computerworkstation.

ETT. See event-triggered tracking.

estimated duration . The estimated length of time anoperation will use a workstation. This is initially basedon a value that is provided when the operation isdefined, but can be adjusted automatically by TivoliOPC's feedback mechanism to reflect actual durations.

event . An action that changes an operation's statusand changes the current plan.

event manager . The Tivoli OPC function thatprocesses all tracking events and determines which ofthese are Tivoli OPC-related.

event reader . A Tivoli OPC task that reads eventrecords from an event dataset.

event tracking . A function of Tivoli OPC that followsevents in the operations department in real time andrecords status changes in the current plan.

event-triggered tracking (ETT) . A component of TivoliOPC that waits for specific events to occur, and thenadds a predefined application to the current plan. ETTrecognizes two types of events: the reader event, whichoccurs when a job enters the JES reader, and theresource event, which occurs when the availabilitystatus of a special resource is set to “yes”.

event writer . A Tivoli OPC task that writes eventrecords in an event dataset.

exclusive resource . A resource that can be used byonly one operation at a time.

expected arrival time . The time when an operation isexpected to arrive at a workstation. It can be calculatedby daily planning or specified in the long-term plan.

extended status code . Together with the normalstatus codes, Tivoli OPC maintains extended statuscodes that provide additional information about thestatus of operations. The extended status code is notalways present.

external dependency . A relationship between twooccurrences, in which an operation in the first

occurrence (the predecessor) must successfully finishbefore an operation in the second occurrence (thesuccessor) can begin processing.

Ffeedback limit . A numeric value in the range 100–999that defines the limits within which actual data that iscollected in tracking is fed back and used by TivoliOPC.

filter criteria . Input values that are used to limit themass update of applications to only those specified.This term is used in the Tivoli OPC ISPF dialogs.

first critical operation . An operation of an occurrencethat has the earliest latest-start-time. The first criticaloperation of an occurrence determines the critical path.

first operation . (1) An operation in an occurrence thathas no internal predecessor. (2) The start node in anetwork.

fixed resources . A set of resource names used tocheck the authority of users to access the Tivoli OPCdialogs.

form number . A user-defined code that identifies thetype of paper to be used for an operation on a printerworkstation. Tivoli OPC can use the form number toidentify the different print operations belonging to onejob.

free day . Any day that is not a work day.

free-day rule . A rule that determines how Tivoli OPCwill treat free days when the application run day falls ona free day.

Ggeneral workstation . A workstation where activitiesother than printing and processing are carried out. Ageneral workstation reporting to Tivoli OPC is usuallymanual, but it can also be automatic. Manual activitiescan include data entry and job setup.

generic alert . An alert that is broadcast by Tivoli OPC,and collected by NetView, when an operation ends inerror. You can specify this as an option when definingapplication descriptions.

global search character . In Tivoli OPC, a percentsign (%), which represents any single character, or anasterisk (*), which represents any character string ofany length.

global variable table . The JCL variable table thatTivoli OPC checks for a variable substitution value if no


value is found in the specific JCL variable table that isassociated with the operation.

Graph view . (1) A view of the Workload Monitor/2Workstation object. Shows the total number ofoperations with different statuses for a singleworkstation. (2) In the Graphical User Interface forApplication Description, a view of the operations thatmake up an application. It shows the workstation whereeach operation is run, and dependencies between theoperations.

Graphs view . A view of the Workload Monitor/2Workstations List object. Shows the total number ofoperations with different statuses for each of theworkstations that are included in the object.

group definition . The application group to which theapplication description or job description is a member.

Hhighest return code . A numeric value in the range0–4095. If this return code is exceeded during jobprocessing, the job will be reported as ended-in-error.

Hiperbatch . The MVS/ESA facility that stores VSAMand QSAM data in Hiperspace for access by multiplejobs. The facility can significantly reduce the executiontime of certain batch streams that access VSAM andQSAM data sets.

Hot standby . Using the MVS/ESA cross-systemcoupling facility (XCF), you can include one or morestandby controllers in your configuration. A standbysystem can take over the functions of a controller if thecontroller fails or if the MVS/ESA system that it wasactive on fails.

IIcons view . The Workload Monitor/2 objects,Workstations List and Operations List, contain otherobjects. The Icons view shows an icon for eachcontained object.

IMS. Information Management System.

incident log . An optional function available under thejob completion checker.

initiator/terminator . The job scheduler function thatselects jobs and job steps to be executed, allocatesinput/output devices for them, places them under taskcontrol, and at completion of the job, supplies controlinformation for writing job output on a system outputunit.

in-progress operation . An operation with a status ofA, R, *, I, E, or S.

input arrival time (IAT) . The user-defined date andtime when an operation or an application is planned tobe ready for processing.

intermediate start . The date and time an operationstarted after processing was interrupted.

internal date . Internally, Tivoli OPC uses a two-digityear format when handling dates. In order to handledates before and after 31 December 1999 correctly,Tivoli OPC uses an origin year of 72 for the internalcentury window. This means that internally the year1972 is represented as 00 and 2071 is represented as99.

internal dependency . A relationship between twooperations within an occurrence, in which the firstoperation (the predecessor) must successfully finishbefore the second operation (the successor) can begin.

interrupted (I) . A Tivoli OPC reporting status for anoperation that indicates that the operation has beeninterrupted while processing.

ISPF. Interactive System Productivity Facility.

JJCC. See job completion checker.

JCL . Job control language. A problem-orientedlanguage designed to express statements in a job thatare used to identify the job or describe its requirementsto an operating system.

JCL tailoring . Tivoli OPC provides automatic JCLtailoring facilities, which enable jobs to be automaticallyedited using information that is provided at job setup orsubmit.

JCL variable table . A group of related JCL variables.See variable table.

JES. Job entry subsystem. A system facility forspooling, job queuing, and managing I/O.

job . (1) A set of data that completely defines a unit ofwork for a computer. A job usually includes allnecessary computer programs, linkages, files, andinstructions to the operating system. (2) In Tivoli OPC,an operation performed at a computer workstation.

job class . Any one of a number of job categories thatcan be defined. By classifying jobs and directinginitiators to initiate specific classes of jobs, it is possibleto control a mixture of jobs that can be run concurrently.

Glossary 133

job-completion checker (JCC) . An optional functionof Tivoli OPC that allows extended checking of theresults from CPU operations.

job description . A single processor (job orstarted-task) operation and its dependencies.

Job Description dialog . The ISPF dialog used tocreate job descriptions.

job ID . The JES job ID of the job associated with theoperation.

job name . The name of the job associated with anoperation. The job name is assigned in the JOBstatement of a job. It identifies the job to the system.

job preparation . Job preparation involves modifyingjobs in preparation for processing. This can beperformed manually, by a job preparer, or automaticallyby Tivoli OPC JCL tailoring functions.

job setup . The preparation of a set of JCL statementsfor a job at a job setup workstation. Job setup can beperformed manually by an operator, or automatically byTivoli OPC.

job setup workstation . A general workstation definedwith the job setup option. A job setup workstation letsyou modify your job or STC JCL before execution.

job submission . A Tivoli OPC process that presentsjobs to MVS for running on a Tivoli OPC-definedworkstation once the scheduling criteria for theoperation is met.

job tracking . A Tivoli OPC process that communicateswith operating systems that control computerworkstations.

JS. The JCL repository dataset.

Kkanji . A character set for the Japanese language.

Llast operation . (1) An operation in an occurrence thathas no internal successor. (2) The terminating node ina network.

latest out time . See latest start.

latest start . The latest day and time (calculated byTivoli OPC) that an operation can start and still meetthe deadline specified for the operation and anysuccessor operations. The latest out time for anoperation is identical to the latest start time.

layout . In the Graphical User Interface for ApplicationDescription, a user-created file that determines whichinformation about each application is displayed whenyou view a list of application descriptions. Anapplication description contains many details about theapplication, such as application ID, valid to date,application status, and last user. A layout specifieswhich details the user wishes to view.

layout ID . A unique name that identifies a specificready or error list layout.

limit for feedback . See feedback limit.

list, application . In the Graphical User Interface forApplication Description, a list of application definitionsfrom which the user can select one to work with. Itconsists of application definitions selected according touser-specified criteria.

List view . The Workload Monitor/2 objectsWorkstations List and Operations List contain otherobjects. The List view shows a list of the containedobject and displays data about each contained object.

local . Synonym for channel-attached.

local processor . (1) In a complex of processorsunder JES3, a processor that executes users' jobs andthat can assume global functions if the global processorfails. (2) In Tivoli OPC, a processor in the sameinstallation that communicates with the controlling TivoliOPC processor through shared DASD or XCFcommunication links.

logical unit (LU) . In Systems Network Architecture(SNA), a port through which an end user accesses theSNA network in order to communicate with another enduser and through which the end user accesses thefunctions provided by system services control points(SSCPs).

logical unit 6.2 (LU 6.2) . A type of Systems NetworkArchitecture (SNA) logical unit (LU) for communicationbetween peer systems. Synonymous with APPCprotocol, see Advanced Program-to-ProgramCommunications (APPC).

long-term plan (LTP) . A high-level plan of systemactivity that covers a period of at least 1 day, and notmore than 4 years. It serves as the basis for a servicelevel agreement with your users, and as input to dailyplanning.

LU. See logical unit.

LU-LU session type 6.2 . See logical unit 6.2.

LTP. See long-term plan.


Mmanipulation button . One of the two mouse buttons.With default mouse settings, the manipulation button ismouse button 2, the button on the right. You press andhold this button to move an object, for example, to dragan object to a printer. Pressing the manipulation buttononce when the pointer is on an object, opens theobject's pop-menu.

manual reporting . A type of workstation reporting inwhich events, once they have taken place, are manuallyreported to Tivoli OPC. This type of reporting requiresthat some action be taken by a workstation operator.Manual reporting is usually performed from a list ofready operations.

mass updating . A function of the ApplicationDescription dialog in which a large update to theapplication database can be requested.

MCU. Multiple Console Support.

Merged Graph view . A view of the WorkloadMonitor/2 Workstations List object. Shows the totalnumber of operations with different statuses for all theworkstations that are included in the object. Theinformation is shown in a single graph.

modify current plan (MCP) . A Tivoli OPC dialogfunction used to dynamically change the contents of thecurrent plan to respond to changes in the operationenvironment. Examples of special events that wouldcause alteration of the current plan are: a rerun, adeadline change, or the arrival of an unplannedapplication.

most critical application occurrences . Thoseunfinished applications whose latest start time is lessthan or equal to the current time.

NNCF. See Network Communication Function.

NCP. Network Control Program.

NetView operations . Operations that consist of anoperator instruction that Tivoli OPC passes to NetView.These operations are run at a general workstation withthe WTO option specified.

Network Communication Function (NCF) . A VTAMapplication that submits work to remote systems andpasses events back to the Tivoli OPC trackersubsystem on the Tivoli OPC controlling system.

noncyclic period . A period that does not represent aconstant number of days or work days. Examples:quarter, academic semester.

nonreporting . A reporting attribute of a workstation,which means that information is not fed back to TivoliOPC.

Ooccurrence . An instance of an application in thelong-term plan or current plan.

An application occurrence is one attempt to processthat application. Occurrences are distinguished fromone another by run date, input arrival time, andapplication ID. For example, an application that runsfour times a day is said to have four occurrences perday.

occurrence group . Consists of one or moreapplication occurrences added to the long-term plan orcurrent plan, where such occurrences are defined asbelonging to a particular application group specified inthe group definition field of the application description orjob description.

offset . Values, in the ranges 1 to 999 and −1 to −999,that indicate which days of a calendar period anapplication runs on. This is sometimes calleddisplacement.

OI. See operator instruction.

OPC/ESA. Operations Planning and Control/ESA

OPC host . The processor where Tivoli OPC updatesthe current plan database.

OPC local processor . A processor that connects tothe Tivoli OPC host or remote processor through sharedevent datasets or XCF communication links.

OPC remote processor . A processor connected tothe Tivoli OPC host processor via an SNA network. ATivoli OPC event writer and an event transmitter (TivoliOPC Network Communication Function) are installed onthe remote processor and transmit events to the TivoliOPC host processor via VTAM.

open interval . The time interval during which aworkstation is active and can process work.

operation . A unit of work that is part of an applicationand that is processed at a workstation.

operation deadline . The latest time when theoperation must be complete.

operation latest out . For an operation that haspredecessors, the latest out date and time are the latest

Glossary 135

start time for the first critical operation in the applicationoccurrence. If the first critical operation has not startedby this date and time, then the operation is flagged aslate, because it will be impossible for it to start on timebased on the sum of the planned durations of all theoperations on its critical path.

operation number . The number of the operation.This uniquely identifies each operation in an application.

Operation object . An object contained in theWorkload Monitor/2 Operations List object. Itrepresents one operation in the current plan.

operation status . The status of an operation at aworkstation.

operation waiting for arrival . The status of anoperation that cannot begin processing because thenecessary input has not arrived at a workstation. Thisstatus is applicable only for operations withoutpredecessors.

Operations List object . A Workload Monitor/2 objectthat can be used to display information about operationsin the current plan. It contains Operation objects.

operator instruction (OI) . An instruction that anoperator can view when the operator must manuallyintervene in Tivoli OPC operations.

origin date . The date that a period (cyclic ornoncyclic) starts on.

owner ID . Owner ID is an identifier that represents theapplication owner.

Pparallel operations . Operations that are notdependent on one another and that can, therefore, runat the same time.

parallel servers . These represent the number ofoperations that can be processed concurrently by thatworkstation.

partner transaction program . An AdvancedProgram-to-Program Communications (APPC)transaction program located at the remote partner.

PDF. Program Development Facility.

pending application description . An applicationdescription that is incomplete and not ready for use inplanning or scheduling. See active applicationdescription.

pending occurrence . The dummy occurrence createdby the daily planning process to honor a dependencythat has been resolved in the long-term plan but cannotbe resolved in the current plan because thepredecessor's input arrival time is not within the currentplan end time.

pending predecessor . A predecessor dependency toan occurrence which is defined in the long-term plan butnot yet included in the current plan. See also pendingoccurrence.

period . A time period defined in the Tivoli OPCcalendar.

personal workstation . In Tivoli OPC documentationthis term is used to refer to a computer that runs IBMOperating System/2.

PIF. See program interface (PIF).

plan . See current plan.

Plan object . A Workload Monitor/2 object that can beused to get information about the status of the currentplan. When the Details view of the Plan object is open,the object monitors for current plan alerts if alertconditions have been specified.

predecessor . An operation in an internal or externaldependency that must finish successfully before itssuccessor operation can begin.

print workstation . A workstation that prints output andusually reports status to Tivoli OPC automatically.

printout routing . The ddname of the daily planningprintout dataset.

priority . The priority of an operation is a value from 1to 9 (where 1=low, 8=high, and 9=urgent). It is one ofthe factors that determines how Tivoli OPC schedulesapplications.

program interface (PIF) . A Tivoli OPC interface thatlets user-written programs issue various requests toTivoli OPC.

Qquery current plan (QCP) dialog . An ISPF dialog thatdisplays information taken directly from the current plan.The information includes information on operations,workstations, and application occurrences.

QSAM. Queued Sequential Access Method.


RRACF. Resource Access Control Facility.

read authority . Access authority that lets a user readthe contents of a dataset, file, or storage area, but notchange it.

ready (R) . The status of an operation indicating thatpredecessor operations are complete and that theoperation is ready for processing.

ready list . An ISPF display list of all the operationsready to be processed at a workstation. Ready lists arethe means by which workstation operators manuallyreport on the progress of work.

receive . (1) To obtain a message or file from anothercomputer. Contrast with send. (2) In CommunicationsManager, the command used to transfer a file from ahost.

record format . The definition of how data is structuredin the records contained within a file. The definitionincludes record names, field names, and field attributes,such as length and data type.

recovery . See automatic job and started-taskrecovery.

remote job tracking . The function of tracking jobs onremote processors connected by VTAM links to a TivoliOPC controlling processor. This function enables acentral site to control the submitting, scheduling, andtracking of jobs at remote sites.

remote processor . A processor connected to theTivoli OPC host processor via a VTAM network.

replan current period . A Tivoli OPC function thatrecalculates planned start times for all occurrences toreflect the actual situation.

reporting attribute . A code that specifies how aworkstation will report events to Tivoli OPC. Aworkstation can have one of four reporting attributes:

A AutomaticC Completion onlyN NonreportingS Manual start and completion.

reroutable . Tivoli OPC can reroute operations if theworkstation that they are scheduled to run on isinactive. An example of this can be if communicationlinks to the system where the workstation is located fail.This option applies to operations only when they havestatus R (ready) or W (waiting). When you define anoperation, you can specify one of the followingreroutable options:

Y The operation is eligible to bererouted if the workstationbecomes inactive.

N The operation will not bererouted, even though theworkstation has an alternatedestination.

blank The operation will be reroutedaccording to the WSFAILUREparameter on the JTOPTSinitialization statement. This isthe default.

rerun . A Tivoli OPC function that lets an application orpart of an application that ended in error be run again.

Resource Object Data Manager . A licensed programthat monitors resources and informs subscribingapplications of their availability.

restartable . If an operation is defined as restartable,Tivoli OPC can automatically restart that operation if theworkstation that it is using becomes inactive. Thisoption applies only to the operation while it has status S(started). The operation will be reset to status R(ready).

return code . An error code that is issued by TivoliOPC for automatic-reporting workstations.

RODM. See Resource Object Data Manager.

row command . An ISPF dialog command used tomanipulate data in a table.

rule . A named definition of a run cycle that determineswhen an application will run.

run cycle . A specification of when an application is torun. The specification may be in the form of a rule oras a combination of period and offset.

SSAA . See Systems Application Architecture.

SAF. System Authorization Facility.

schedule . (1) The current or long-term plan. (2) Todetermine the input arrival date and time of anoccurrence or operation.

selection button . One of the two mouse buttons.With default mouse settings, the selection button ismouse button 1, the button on the left. You use thisbutton to select windows, menu choices, pages in anotebook, and buttons. Pressing the selection buttontwice when the pointer is on an object opens the objectto the default view.

Glossary 137

send . (1) To send a message or file to anothercomputer. Contrast with receive. (2) InCommunications Manager, the command used totransfer a file to the host.

server . The optional Tivoli OPC component that runson the controlling system and handles requests fromremote ISPF dialogs, remote PIF applications, and theGraphical User Interface for Application Description.

service functions . Functions of Tivoli OPC that let theuser deal with exceptional conditions, such asinvestigating problems, preparing APAR tapes, andtesting Tivoli OPC during implementation.

service level agreement . An agreement madebetween the data processing center and its user groupsindicating the service hours and levels, as well as thekind of service the DP center will provide.

Settings notebook . See Settings view

Settings view . A view of an object that is used tospecify properties of the object itself.

shared DASD . Direct access storage devices that canbe accessed from more than one processor.

shared resource . A special resource or workstationresource that can be used simultaneously by more thanone operation.

slack . Refers to ‘spare’ time. This extra time can becalculated for the critical path by taking 'Deadline lessthe Input Arrival less the sum of Operation Durations'.

SMF. System Management Facilities. An MVScomponent that collects and records system andjob-related information.

smoothing factor . A value in the range 0-100 thatcontrols the extent to which actual durations are fedback into the application description database.

SMP. System Modification Program.

SNA. See Systems Network Architecture.

special resource . A resource that is not associatedwith a particular workstation, such as a dataset.

splittable . Refers to a workstation where operationscan be interrupted while being processed.

standard . User-specified open intervals for a typicalday at a workstation.

started (S) . A Tivoli OPC reporting status, for anoperation or an application, indicating that an operationor an occurrence is started.

started-task computer workstation . You can specifythat a computer workstation will support started tasks bygiving the workstation the STC option. Operationsdefined to this workstation will be treated as startedtasks, not as jobs.

started-task operations . Operations that start or stopstarted tasks. These operations are run at a computerworkstation with the STC option specified.

status . The current state of an operation oroccurrence.

status code . Codes that represent the current state ofan operation. The status code is often associated withan extended status code.

The status of an operation can be one of the following:

A The operation is waiting for input to arrive.

R The operation is ready for processing (allpredecessors have been reported as complete).

S Operation processing has started.

C Operation processing has completed.

D The operation has been deleted from the currentplan.

I Operation processing has been interrupted.

* The operation is ready for processing. There is apredecessor at a nonreporting workstation, but allother predecessors are reported as complete.

E The operation has ended in error.

W The operation is waiting for a predecessor tocomplete.

U The operation status is not known.

submit/release dataset . A dataset shared betweenthe Tivoli OPC host and a local Tivoli OPC processorthat is used to send job-stream data and job-releasecommands from the host to the local processor.

subresources . A set of resource names and rules forthe construction of resource names. Tivoli OPC usesthese names when checking a user's authority toaccess individual Tivoli OPC data records.

subsystem . A secondary or subordinate system,usually capable of operating independently of, orasynchronously with, a controlling system.

successor . An operation in an internal or externaldependency that cannot begin until its predecessorcompletes processing.

SYSOUT. A system output stream, also an indicatorused in data definition statements to signify that adataset is to be written on a system output unit.


SYSOUT class . An indicator used in data definitionstatements to signify that a dataset is to be written on asystem output unit. It applies only to print workstations.

SYSPLEX. An MVS/ESA systems complex providessystems management enhancements for coordinatingand controlling the data processing facility acrossmultiple systems, while minimizing complexity.Implemented using the 9037 Sysplex Timer and thecross-system coupling facility (XCF) component ofMVS/ESA.

Systems Application Architecture (SAA) . A formalset of rules that enable applications to be run withoutmodification, in different computer environments.

Systems Network Architecture (SNA) . Thedescription of the logical structure, formats, protocols,and operational sequences for transmitting informationunits through the networks and also operationsequences for controlling the configuration andoperations of networks.

Ttail plan . Created during the daily planning process,includes only tail work; that is, work that started duringor before the current planning period and that extendsbeyond its end.

TCP/IP. Transmission Control Protocol/InternetProtocol. A set of communication protocols that supportpeer-to-peer connectivity functions for both local andwide-area networks.

temporary operator instructions . Operatorinstructions that have a specific time limit during whichthey are valid. They will be displayed to the workstationoperator only during that time period.

time dependent . Tivoli OPC attempts to startoperations as soon as possible, when all dependencieshave been resolved and processing resources areavailable. However, you can specify that an operationis time-dependent, so Tivoli OPC will not start it until aspecific time.

time zone support . A feature of Tivoli OPC that letsapplications be planned and run with respect to thelocal time of the processor that runs the application.Some networks might have processors in different timezones. The controlling processor will make allowancesfor differences in time during planning activities toensure that interacting activities are correctlycoordinated.

TP. See application transaction program.

tracker . The Tivoli OPC component that runs on everysystem in your complex. It acts as the communication

link between the MVS system that it runs on and thecontroller.

tracking event log . A log of job-tracking events andupdates to the current schedule.

transport time . The time allotted for transportingmaterials from the workstation where the precedingoperation took place to the workstation where thecurrent operation is to occur. The transport time isused only for planning purposes. Operations will bestarted irrespective of the transport time specified.

TSO. Time Sharing Option.

turnover . A subfunction of Tivoli OPC that is activatedwhen Tivoli OPC creates an updated version of thecurrent plan.

Uundecided (U) . A Tivoli OPC reporting status, for anoperation or an application, indicating that the status isnot known.

update authority . (1) Access authority to use theISPF/PDF edit functions of the Tivoli OPC dialog. Theauthority is given to the user via RACF. (2) Accessauthority to modify a master file or dataset with thecurrent information.

Vvalidity period . The time interval defined by an origindate and an end date within which a run cycle or anapplication description is valid.

variable table . A group of related JCL variables.Tivoli OPC can check these variable tables forsubstitution values for variables that occur in JCL. Thissubstitution can occur during job setup or at job submit.

versions . Applications with the same ID but differentvalidity dates.

VSAM. Virtual Storage Access Method.

VTAM. Virtual Telecommunications Access Method.

Wwaiting (W) . A status indicating that an application iswaiting for a predecessor operation to complete.

waiting list . A list of jobs that have been submittedbut still have uncompleted predecessors. Operationswill be included in the waiting list if the JCL is not

Glossary 139

submitted by the Tivoli OPC controller and the TivoliOPC tracker has been started with HOLDJOB(YES).

work day . A day on which applications can normallybe scheduled to start.

work-days-only cyclic period . A cyclic period whereonly work days are counted when calculating theinterval.

work-day end time . The time when one Tivoli OPCwork day ends and the next day begins. By default,this time is midnight.

For example, if the work-day end time is 02:00, work forFriday can continue until 02:00 on Saturday morning,even if Saturday is a free day. If Saturday and Sundayare free days, no new work will be started until 02:00 onMonday.

Workload Monitor/2 . A part of Tivoli OPC. It runs onOS/2 Version 2 (or later) and communicates with aTivoli OPC controller subsystem. It carries data aboutthe subsystem's current plan from the host to aworkstation, and can update operation status.

workstation . (1) A unit, place, or group that performsa specific data processing function. (2) A logical placewhere work occurs in an operations department.

Tivoli OPC requires that you define the followingcharacteristics for each workstation: the type of work itdoes, the quantity of work it can handle at any particulartime, and the times it is active. The activity that occursat each workstation is called an operation. (3) See alsopersonal workstation.

workstation description database . A Tivoli OPCdatabase containing descriptions of the Tivoli OPCworkstations in the operations department.

workstation resource . A physical resource, such as atape drive, that must be allocated among jobs. Whenyou define a workstation, you can specify the quantity ofeach of two resources (R1 and R2) that are available tooperations. When defining operations to thatworkstation, you can specify the number of theseresources that must be available for the operation tostart on that workstation.

workstation type . Each workstation can be one ofthree types: computer, printer, or general.

write-to-operator workstation . A general workstationthat lets you use Tivoli OPC scheduling facilities toissue a write-to-operator (WTO) message at a specificoperator console defined by the workstation destination.NetView can intercept the WTO message and takenecessary action.

WTO message . Write-to-operator message.

WTO operations . Operations that consist of anoperator instruction that Tivoli OPC passes to NetView.These operations are run at a general workstation withthe WTO option specified.

XXCF. MVS/ESA cross-system coupling facility.

XRF. Extended recovery facility.


Index

Aadding users to a group 12administrator user ID 12AIX requirements, hardware and software 111automatic startup 62

Bboot startup 62

Cchecking the configuration parameter file 73checkpoint file 54, 72, 96CODEPAGE keyword of ROUTOPTS 9codepage tables 109communications

checking 19configuration file

creating 48configuration parameters

controller 9controller

description 1parameters 9

controller IP address parameter 52controller port number parameter 52controller_ipaddr 52controller_portnr 52controller_type 52creating

administrator user ID 12directory 15group ID (GID) 12user ID 12

Ddiagnosing problems 69Digital OpenVMS requirements, hardware and

software 119Digital UNIX requirements, hardware and software 123directories 15directory structure 15, 55distribution media 3

Eenabler support

loading for the Tracker Agent 7environment variable

EQQHOME 48

environment variable (continued)EQQINSTANCE 48PATH 48

eqqclean script 66eqqdelete script 65eqqdr_retry 52eqqfilespace 52EQQHOME variable 48eqqinit 97EQQINSTANCE variable 48eqqmsgq 52eqqshell 52eqqshmkey 52eqqtr_retry 52eqqtw_retry 52eqqverify 73errors from jobs 61errors, debugging 69event logfile 52, 53, 72, 96event_logsize 52ew_check_file 52exit codes 70

Ffailures and problems 69files

planning 15fixing problems 69

Ggroup ID (GID) 12

Hhardware requirements

Digital OpenVMS 119for AIX 111for Digital UNIX 123for HP-UX 113for OS/390 Open Edition 125for Silicon Graphics IRIX 121for Solaris 115for SunOS 117

home directory 15setting 48

host names 17how to install fixes on a non-AIX tracker machine 127HP-UX requirements, hardware and software 113


Iinitialization statements

JTOPTSexample of 10

OPCOPTSexample of 10

ROUTOPTSCODEPAGE keyword 9example of 10TCP keyword 9TCPIPID keyword 9TCPIPPORT keyword 9TCPTIMEOUT keyword 9

installation 11—57installation tasks 11installation tasks for the Tivoli OPC controller 5installing

loading Tracker Agent enabler software 7loading Tracker Agent software 5overview 2

installing required features 36, 38, 40, 42, 44IP address parameter 52ipc_base 52

Jjob output log actions parameter 52Job Scheduler

introduction 2job_log 52JTOPTS initialization statement

example of 10

KKEEPALIVE parameters

on a Digital UNIX system 105on a MIPS ABI system 104on a Sun Solaris system 104on a SunOS system 103

recompile the kernel 103on an AIX system 101on an HP system 102on the controller machine 101unavailable on a Digital OpenVMS system 104

kernel considerations 15key generator for IPC queues parameter 52

Llinks to package directory

creating 97LoadLeveler 107LoadLeveler, specifying 54local code page parameter 52

local directoryinitializing 97

local_codepage 52local_ipaddr 52local_portnr 52log directories, creating 48log files

cleaning 65event logfile 53, 72, 96submit checkpoint file 54, 72, 96

Mmachine requirements

for AIX 111for Digital OpenVMS 119for Digital UNIX 123for HP-UX 113for OS/390 Open Edition 125for Silicon Graphics IRIX 121for Solaris 115for SunOS 117

messages 77

Nnaming convention for non-AIX fixes 127national language support 109NFS considerations 57NIS 17NIS considerations 17, 57num_submittors 52number of submittors parameter 52

Oopc group 12OPCOPTS initialization statement

example of 10operation 59OS/390 Open Edition requirements, hardware and

software 125overview 1

PPATH variable 48port number 52port numbers 17prerequisites

for AIX 111for Digital OpenVMS 119for Digital UNIX 123for HP-UX 113for OS/390 Open Edition 125for Silicon Graphics IRIX 121for Solaris 115


prerequisites (continued)for SunOS 117

problems, solving 69program requirements

for AIX 111for Digital OpenVMS 119for Digital UNIX 123for HP-UX 113for OS/390 Open Edition 125for Silicon Graphics IRIX 121for Solaris 115for SunOS 117

pulse functionsenabling 101on a Digital UNIX system 105on a MIPS ABI system 104on a Sun Solaris system 104on a SunOS system 103on an AIX system 101on an HP system 102on the controller machine 101unavailable on a Digital OpenVMS system 104

RREADME file 3restarting the Tracker Agent 66return codes 71return codes from jobs 61ROUTOPTS initialization statement

CODEPAGE keyword 9example of 10TCP keyword 9TCPIPID keyword 9TCPIPPORT keyword 9TCPTIMEOUT keyword 9

SSAM

creating a user group 12creating a user ID 13

scripts 98storing 59utility 93

service names 17shell parameter 52Silicon Graphics IRIX requirements, hardware and

software 121size of event log history parameter 52SMIT

creating a user group 12installing required features 30reading product installation media 31

software requirementsDigital OpenVMS 119

software requirements (continued)for AIX 111for HP-UX 113for OS/390 Open Edition 125for Silicon Graphics IRIX 121for Solaris 115for SunOS 117

Solaris requirements, hardware and software 115solving problems 69starting the Tracker Agent 48storing scripts 59submit checkpoint file 54, 72, 96submittor parameters 52subnn_check_file 52subnn_retry 52subnn_subtype 52subnn_workstation_id 52SunOS requirements, hardware and software 117swinstall tool

installing required features 34symbolic links

creating 97symptoms of problems 69

TTCP keyword of ROUTOPTS 9TCP/IP

checking 19port number 9, 52

TCP/IP environmentverifying

OS/390 27Sun Solaris and SunOS 25

TCP/IP KEEPALIVE parameters 101TCP/IP SO_KEEPALIVE option 101TCPIPID keyword of ROUTOPTS 9TCPIPPORT keyword of ROUTOPTS 9TCPTIMEOUT keyword of ROUTOPTS 9temporary files

cleaning 65Tivoli OPC

introduction 2Tivoli OPC controller 5tools 93trace level parameter 52trace_level 52Tracker Agent

loading enabler software 7loading software 5

Tracker Agent description 2tracker fixes for OPC (non-AIX) 127tracker user ID 12translation, ASCII to EBCDIC 109troubleshooting 71

Index 143

Uuser group

creating 12user ID (UID) 12utility programs 93

Vvariable

EQQHOME 48EQQINSTANCE 48PATH 48

verifying the configuration parameter file 73

Wworkstation ID 54

Yypwhich command 17


Communicating Your Comments to IBM

Tivoli Operations Planning and ControlTracker Agents forAIX, UNIX**, VMS**, andOS/390 Open EditionInstallation and OperationVersion 2 Release 3

Publication No. SH19-4484-02

If you especially like or dislike anything about this book, please use one of the methodslisted below to send your comments to IBM. Whichever method you choose, make sure yousend your name, address, and telephone number if you would like a reply.

Feel free to comment on specific errors or omissions, accuracy, organization, subject matter,or completeness of this book. However, the comments you send should pertain to only theinformation in this manual and the way in which the information is presented. To requestadditional publications, or to ask questions or make comments about the functions of IBMproducts or systems, you should talk to your IBM representative or to your IBM authorizedremarketer.

When you send comments to IBM, you grant IBM a nonexclusive right to use or distributeyour comments in any way it believes appropriate without incurring any obligation to you.

If you prefer to send comments by mail, use the reader's comment form (RCF) at the back ofthis book. If you wish, you can give the RCF to the local branch office or IBM representativefor postage-paid mailing.

If you prefer to send comments by fax, use this number, which is in Italy:

39+06+596+62077

If you prefer to send comments electronically, use this network ID:

ROMERCF at VNET.IBM.COM

Make sure to include the following in your note:

� Title and publication number of this book� Page number or topic to which your comment applies

Help us help you!

Tivoli Operations Planning and ControlTracker Agents forAIX, UNIX**, VMS**, andOS/390 Open EditionInstallation and OperationVersion 2 Release 3

Publication No. SH19-4484-02

We hope you find this publication useful, readable and technically accurate, but only you can tell us! Yourcomments and suggestions will help us improve our technical publications. Please take a few minutes tolet us know what you think by completing this form.

Specific Comments or Problems:

Please tell us how we can improve this book:

Thank you for your response. When you send information to IBM, you grant IBM the right to use ordistribute the information without incurring any obligation to you. You of course retain the right to use theinformation in any way you choose.

Name Address

Company or Organization

Phone No.

Overall, how satisfied are you with the information in this book? Satisfied Dissatisfied

Ø Ø

How satisfied are you that the information in this book is: Satisfied Dissatisfied

Accurate Ø ØComplete Ø ØEasy to find Ø ØEasy to understand Ø ØWell organized Ø ØApplicable to your task Ø Ø

Cut or FoldAlong Line

Cut or FoldAlong Line

Help us help you !SH19-4484-02 IBM

Fold and Tape Please do not staple Fold and Tape

PLACEPOSTAGESTAMPHERE

Tivoli OPC Information DevelopmentRome Tivoli LaboratoryIBM Italia S.p.A.Via Sciangai, 5300144 RomeItaly

Fold and Tape Please do not staple Fold and Tape

SH19-4484-02

IBM

Program Number: 5697-OPC

Printed in Denmark by IBM Danmark A/S

SH19-4484-ð2

sh19-4484-02

Documents