quick reference - ibmpublib.boulder.ibm.com/.../en_us/pdf/gh19-4374-02.pdf · quick reference...

TivoliOperations Planningand Control IBM

Quick ReferenceVersion 2 Release 3

GH19-4374-02

Note

Before using this information and the product itsupports, be sure to read the general informationunder “Notices” on page v.

ISO 9001 Certification

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

Certification has been awarded by the Italianquality system certification group, CSQ (Certif-ication No. CISQ/CSQ 9150.IBM7).

CSQ is a member of the mutually recognizedorganization of European assessors, ITQS, whichassesses and certifies quality systems in the fieldof information technology enterprises.

Third Edition (December 1999)

This major revision replaces GH19-4374-01.

This edition applies to Version 2 Release 3 Modifica-tion Level 0 of Tivoli Operations Planning and Control,Program Number 5697-OPC, and to all subsequentreleases and modifications until otherwise indicated innew editions or technical newsletters. Technicalchanges or additions to the text are indicated by avertical line to the left of the change. Make sure youare using the correct edition for the level of theproduct.

Order publications through your IBM representative orthe IBM branch office serving your locality. Publica-tions are not stocked at the address below.

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

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

When you send information to IBM, you grant IBM anonexclusive right to use or distribute the informationin any way it believes appropriate without incurringany obligation to you.

Copyright International Business Machines Cor-poration 1991, 1999. All rights reserved.Note to U.S. Government Users — Documentationrelated to restricted rights — Use, duplication or dis-closure is subject to restrictions set forth in GSA ADPSchedule Contract with IBM Corp.

Contents

Notices . . . . . . . . . . . . . . . . . . . vTrademarks . . . . . . . . . . . . . . . . . vi

Using the Tivoli OPC ISPF Dialogs . . . 1Specifying List Criteria . . . . . . . . . . . 2Using Generic Search Arguments . . . . . 2Sorting List Output . . . . . . . . . . . . . 3Locating Data Strings in List Output . . . . 3Graphically Displaying Lists . . . . . . . . 3PF Key Assignment . . . . . . . . . . . . . 4

TSO Commands . . . . . . . . . . . . . . 5BACKUP . . . . . . . . . . . . . . . . . . 5

| JSUACT . . . . . . . . . . . . . . . . . . 5OPINFO . . . . . . . . . . . . . . . . . . . 6OPSTAT . . . . . . . . . . . . . . . . . . 7SRSTAT . . . . . . . . . . . . . . . . . . 8WSSTAT . . . . . . . . . . . . . . . . . . 9

MVS Commands to Control Tivoli OPC 11Starting Tivoli OPC . . . . . . . . . . . . 11Stopping Tivoli OPC . . . . . . . . . . . 11Canceling Tivoli OPC . . . . . . . . . . . 12Modifying Tivoli OPC . . . . . . . . . . . 13

| Modifying Tivoli OPC Data Store . . . . . 20

Automatic Recovery . . . . . . . . . . . 23RECOVER statement . . . . . . . . . . . 23

JCL Directives . . . . . . . . . . . . . . 25SCAN directive . . . . . . . . . . . . . . 25SEARCH directive . . . . . . . . . . . . 25TABLE directive . . . . . . . . . . . . . 25SETFORM directive . . . . . . . . . . . 25SETVAR directive . . . . . . . . . . . . . 26BEGIN and END directives . . . . . . . . 26FETCH directive . . . . . . . . . . . . . 26COMP Keyword on BEGIN and FETCH

Directives . . . . . . . . . . . . . . . . 27

Tivoli OPC-Supplied JCL Variables . . 29Occurrence-Related JCL Variables . . . . 29Operation-Related JCL Variables . . . . 32Date-Related JCL Variables . . . . . . . 33Dynamic-Format Supplied Variables . . . 35

Codes . . . . . . . . . . . . . . . . . . 37

Copyright IBM Corp. 1991, 1999 iii

Operation Status and Extended StatusCodes . . . . . . . . . . . . . . . . . . 37

Operation Status Codes . . . . . . . . 37Extended Status Codes . . . . . . . . 38

Error Codes . . . . . . . . . . . . . . . . 39Catalog Management Status Codes . . . 41Job Log Retrieval Status Codes . . . . . 42Operation Reason Codes . . . . . . . . . 43Reason Codes . . . . . . . . . . . . . . 44

Free-Day Rule . . . . . . . . . . . . . . 59

iv Tivoli OPC Quick Reference

Notices

References in this publication to IBM products,programs, or services do not imply that IBMintends to make these available in all countriesin which IBM operates. Any reference to anIBM product, program, or service is notintended to state or imply that only IBM’sproduct, program, or service may be used.Subject to IBM’s valid intellectual property orother legally protectable rights, any functionallyequivalent product, program, or service may beused instead of the IBM product, program, orservice. The evaluation and verification ofoperation in conjunction with other products,except those expressly designated by IBM, isthe user’s responsibility.

IBM may have patents or pending patent appli-cations covering subject matter in this docu-ment. The furnishing of this document does notgive you any license to these patents. You cansend license inquiries, in writing, to:

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

Licensees of this program who wish to haveinformation about it for the purpose of enabling:(i) the exchange of information between inde-pendently created programs and other pro-grams (including this one) and (ii) the mutualuse of the information which has beenexchanged, should contact:

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

Such information may be available, subject toappropriate terms and conditions, including insome cases, payment of a fee.

Copyright IBM Corp. 1991, 1999 v

TrademarksThe following product names are trademarks ofTivoli Systems or IBM Corporation in the UnitedStates or other countries or both:

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

Microsoft, Windows, Windows NT, and theWindows logo are trademarks or registeredtrademarks of Microsoft Corporation.

UNIX is a registered trademark in the UnitedStates and other countries licensed exclusivelythrough X/Open Company Limited.

C-bus is a trademark of Corollary, Inc.

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

PC Direct is a trademark of Ziff Communi-cations Company and is used by IBM Corpo-ration under license.

ActionMedia, LANDesk, MMX, Pentium, andProShare are trademarks or registered trade-marks of Intel Corporation in the United Statesand other countries.

Other company, product, and service nameswhich may be denoted by a double asterisk (**),may be trademarks or service marks of others.

GDDM IBM IBMLinkMVS/ESA OPC OS/390SystemView Tivoli TMETivoli

vi Tivoli OPC Quick Reference

Using the Tivoli OPC ISPFDialogs

Table 1. Some Primary Commands for TivoliOPC Panels

Command Action

RETURN Return to main menu. Anend operation is executedfor each panel in thesequence leading back tothe main menu (all changeson the individual panels aresaved).

CANCEL Return to the previouspanel without making anychanges.

RIGHT Display the right part of thedata. This is available onlyfrom panels that have thetext LEFT PART in the paneltitle.

LEFT Display the left part of thedata. This is available onlyfrom panels that have thetext RIGHT PART in thepanel title.

HELP Display help information.

SORT Sort information in a list.

LOCATE lparm Scroll to the field specified.If the field is not found, thelist is displayed starting withthe entry before which thespecified field would haveoccurred. If the list issorted by application name,lparm is the name of theapplication; if sorted by jobname, lparm is a job name.

GRAPH Display a network ofdependencies.

GDDM Execute GDDM functionson a graphically displayednetwork.

ATTR Set graphic attributes.

Copyright IBM Corp. 1991, 1999 1

Specifying List CriteriaLimit the length of lists by using filter panels likethis:

à ð EQQSOPFP ------------------- SELECTING OPERATIONS ---------------------

Command ===>

Specify selection criteria below and press ENTER to create an operation

JOBNAME ===> ________

FAST PATH ===> Y Valid only along with jobname

Y Yes, N No

APPLICATION ID ===> ________________

OWNER ID ===> ________________

AUTHORITY GROUP ===> ________

WORK STATION NAME ===> ____

PRIORITY ===> _ Low priority limit

STATUS ===> __________ List of status codes:

A R \ S I C E W U and D

Input arrival in format YY/MM/DD HH.MM

FROM ===> ________ _____

TO ===> ________ _____

GROUP DEFINITION ===> ________________

á

ñ

You can use blanks, complete names, IDs, orsearch arguments in the input fields.

On some selection panels you can choose theFASTPATH option, so that Tivoli OPC searchesfor matching job names on automatic work-stations. If there is a matching job name, TivoliOPC includes all operations with that job name,whether on an automatic workstation or not.

Using Generic Search ArgumentsMany of the input fields in the Tivoli OPC dialogaccept generic search arguments. Use anasterisk (*) to represent any character string ora null string. Use a percent sign (%) for anysingle character.

To select all application identifiers whose firstthree letters are PAY, enter this in the inputfield:

APPLICATION ID ===> PAY\________

To select all applications where P is the firstletter and Y is the third letter, enter this:

APPLICATION ID ===> P%Y\________

2 Tivoli OPC Quick Reference

Sorting List OutputIn all list displays, enter the SORT command todisplay a panel where you can specify the orderof the list items. The sort order you requestremains in effect for that specific list type untilchanged.

If you sort on date fields, take into account thedate format that has been specified, becausethis can affect the order.

Locating Data Strings in List OutputEnter LOCATE on any list display panel to find adata string in the list. The command also sup-ports generic search strings. For example, youcan enter LOCATE ABC\ to find any item in thelist beginning with ABC. Locate scrolls to thefield specified.

If the list is sorted by application name, requestLOCATE applname; similarly, if sorted by jobname, request LOCATE jobname. If you need toissue a locate command on a list that is notsorted by the item you want to locate, changethe order with the SORT command.

Graphically Displaying ListsIf you have GDDM installed and have a ter-minal capable of displaying graphics, you canalso display lists of applications, occurrences,and operations graphically. Graphic displayscontain the same information as edit orselection lists, but the format is different—youcan see dependency connections that might behard to see from a conventional list.

To see a graphically displayed list, enter GRAPHat the command prompt of a panel on whichgraph is an option.

Using the Tivoli OPC ISPF Dialogs 3

PF Key AssignmentThe Tivoli OPC dialog maintains separateprogram function (PF) keys from your normalISPF key assignments. Enter KEYS at thecommand prompt to display or change thecurrent assignment.

You can define PF keys to execute a TivoliOPC command that you use regularly, forexample, to display the ready list. To ensurethat the command will be executed correctlyregardless of the Tivoli OPC panel it is enteredfrom, define the PF key like this:

PF5 ===> ;=4.1.cpu1

Where ; is your ISPF command delimiter.

You can define unique PF key assignments fordifferent Tivoli OPC panels. For example, ifyou regularly use the application descriptiondialog, you can define PF keys for the OPERand RUN commands.

It is recommended that you do not alter the keyassignments for PF1 (HELP), or PF12(RETRIEVE). The retrieve PF key returns thecommand you last executed to the commandprompt. A stack of approximately 25 com-mands is maintained.

The PF KEY DEFINITIONS AND LABELS panel letsyou assign labels to the PF key definitions.When you enter the PFSHOW command from apanel, the PF key labels are displayed. Toremove the display, enter PFSHOW OFF.


TSO Commands

This chapter describes the syntax for the Tivoli| OPC TSO commands, BACKUP, JSUACT,

OPINFO, OPSTAT, SRSTAT and WSSTAT.

You can abbreviate keywords to their shortestunambiguous form. For example, you canshorten the AVAIL keyword to an ‘A’. Beforeyou invoke a Tivoli OPC TSO command, youmust allocate the EQQMLIB dataset to the TSOaddress space, either by adding DD statementsto the logon procedure, or by using the ALLOCcommand after TSO logon. Error messagesare sent directly to the terminal.

The TSO commands can be directed to a spe-cific Tivoli OPC subsystem (tracker). Thetracker does not have to be active when youissue the command. An event is generated andqueued in ECSA along with other job-trackingevents.

BACKUP

55──BACKUP──RESDS──(─ ──┬ ┬─CP─ ─)────────────────5 └ ┘─JS─

5─ ──┬ ┬────────────────────────── ───────────────5 │ │┌ ┐─ð───────────

└ ┘──TRACE( ──┴ ┴─trace level─ )

5─ ──┬ ┬────────────────────────────── ──────────5% │ │┌ ┐─OPCA───────────

└ ┘──SUBSYS( ──┼ ┼─MSTR─────────── ) └ ┘─subsystem name─

| JSUACT|

| 55─| ─JSUACT──ACT──(─ ──┬ ┬─yes─ ─)─────────────────5| └ ┘─no──

| 5─ ──┬ ┬────────────────────────────── ───────────5| │ │┌ ┐─OPCA───────────| └ ┘──SUBSYS( ──┼ ┼─MSTR─────────── )| └ ┘─subsystem name─

| 5─ ──┬ ┬────────────────────────── ──────────────5%| │ │┌ ┐─ð───────────| └ ┘──TRACE( ──┴ ┴─trace level─ )


OPINFO

55──OPINFO─────────────────────────────────────5

5─ ──┬ ┬────────────────────────────────── ───────5└ ┘──ADID( ─── ──appl. description ID─ )

5─ ──┬ ┬─────────────────────────────────── ──────5└ ┘──CLASS( ─── ──printer sysout class─ )

5─ ──┬ ┬─────────────────────────────── ──────────5└ ┘──FORM( ─── ──printer form name─ )

5─ ──┬ ┬────────────────────── ───────────────────5└ ┘──IA( ─── ──yymmddhhmm─ )

5─ ──┬ ┬───────────────────────── ────────────────5└ ┘──JOBNAME( ─── ──job name─ )

5─ ──┬ ┬─────────────────────────────── ──────────5└ ┘──OPNUM( ─── ──operation number─ )

5─ ──┬ ┬────────────────────────────── ───────────5 │ │┌ ┐─OPCA───────────


5─ ──┬ ┬────────────────────────── ───────────────5 │ │┌ ┐─ð───────────


5─ ──┬ ┬────────────────────────── ───────────────5└ ┘──USERDATA( ─── ──any data─ )

5─ ──┬ ┬──────────────────────────────── ────────5%└ ┘──WSNAME( ─── ──workstation name─ )


OPSTAT

55──OPSTAT─────────────────────────────────────5

5─ ──┬ ┬────────────────────────────────── ───────5└ ┘──ADID( ─── ──appl. description ID─ )

5─ ──┬ ┬─────────────────────────────────── ──────5└ ┘──CLASS( ─── ──printer sysout class─ )

5─ ──┬ ┬────────────────────── ───────────────────5└ ┘──DURATION( ─── ──hhmm─ )

5─ ──┬ ┬───────────────────────────────── ────────5└ ┘──ERRORCODE( ─── ──op. error code─ )

5─ ──┬ ┬────────────────────── ───────────────────5└ ┘──EVDATE( ─── ──yymmdd─ )

5─ ──┬ ┬──────────────────── ─────────────────────5└ ┘──EVTIME( ─── ──hhmm─ )

5─ ──┬ ┬─────────────────────────────── ──────────5└ ┘──FORM( ─── ──printer form name─ )

5─ ──┬ ┬────────────────────── ───────────────────5└ ┘──IA( ─── ──yymmddhhmm─ )

5─ ──┬ ┬───────────────────────── ────────────────5└ ┘──JOBNAME( ─── ──job name─ )

5─ ──┬ ┬───────────────────── ────────────────────5└ ┘──NUMJOB( ─── ──nnnnn─ )

5─ ──┬ ┬─────────────────────────────── ──────────5└ ┘──OPNUM( ─── ──operation number─ )

5─ ──┬ ┬────────────────────────── ───────────────5└ ┘──TOKEN( ─── ──token value─ )

5─ ──┬ ┬───────────────── ────────────────────────5 │ │┌ ┐─C─

└ ┘──STATUS( ──┼ ┼─E─ ) ├ ┤─I─ ├ ┤─Q─ ├ ┤─T─ ├ ┤─S─ └ ┘─X─

5─ ──┬ ┬────────────────────────────── ───────────5 │ │┌ ┐─OPCA───────────


5─ ──┬ ┬────────────────────────── ───────────────5 │ │┌ ┐─ð───────────


5──WSNAME──(─ ─── ──workstation name─ ─)─────────5%

TSO Commands 7

SRSTAT

55─ ─── ──SRSTAT─ ─'──resource name──'────────────5

5─ ──┬ ┬────────────────────────────── ───────────5 │ │┌ ┐─OPCA───────────

└ ┘──SUBSYS( ──┼ ┼─subsystem name─ ) └ ┘─MSTR───────────

5─ ──┬ ┬──────────────────── ─────────────────────5 │ │┌ ┐─KEEP──

└ ┘──AVAIL( ──┼ ┼─RESET─ ) ├ ┤─NO──── └ ┘─YES───

5─ ──┬ ┬───────────────────────── ────────────────5 │ │┌ ┐─KEEP───

└ ┘──DEVIATION( ──┼ ┼─amount─ ) └ ┘─RESET──

5─ ──┬ ┬──────────────────────── ─────────────────5 │ │┌ ┐─KEEP───

└ ┘──QUANTITY( ──┼ ┼─amount─ ) └ ┘─RESET──

5─ ──┬ ┬─────────────────── ──────────────────────5 │ │┌ ┐─YES─

└ ┘──CREATE( ──┴ ┴─NO── )

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



WSSTAT

55─ ─── ──WSSTAT─ ────────────────────────────────5

5─ ──┬ ┬─────────────────────────────── ──────────5└ ┘──ALTWS( ─── ──alternate wsname─ )

5─ ──┬ ┬────────────────── ───────────────────────5 │ │┌ ┐─L─

└ ┘──REROUTE( ──┴ ┴─R─ )

5─ ──┬ ┬─────────────────── ──────────────────────5 │ │┌ ┐─L─

└ ┘──STARTOPS( ──┼ ┼─R─ ) └ ┘─E─

5──STATUS──(─ ──┬ ┬─A─ ─)─────────────────────────5 ├ ┤─O─ └ ┘─F─

5─ ──┬ ┬────────────────────────────── ───────────5 │ │┌ ┐─OPCA───────────

└ ┘──SUBSYS( ──┼ ┼─subsystem name─ ) └ ┘─MSTR───────────

5─ ──┬ ┬────────────────────────── ───────────────5 │ │┌ ┐─ð───────────


5──WSNAME──(─ ─── ──workstation name─ ─)─────────5%

TSO Commands 9

MVS Commands to Control TivoliOPC

You can start, stop, cancel, or modify TivoliOPC using the following MVS operatorcommands:

S STARTP STOPC CANCELF MODIFY

In addition, you can use the MODIFY (F)command to start and stop individual subtasks.

You can enter these commands from a multipleconsole support (MCS) console or from aprogram such as the spool display and searchfacility (SDSF). In both cases, the terminal orconsole operator must have the requiredauthority to enter operator commands.

Starting Tivoli OPCTo start Tivoli OPC, enter this MVS operatorcommand:

START Tivoli OPC

S procname (procname = Tivoli OPCJCL procedure name)

If a Tivoli OPC started task with this name isalready active, the second attempt to invoke itends with an error message. If this happens,the started task in error cannot write an errormessage to the Tivoli OPC message log(ddname EQQMLOG) because the messagelog is already being used by the active startedtask. If Tivoli OPC is to run as a batch job, donot start it with an operator command. Instead,submit a batch job with the same name as theTivoli OPC subsystem. JES starts this job inthe same manner as any ordinary job.

Note: Because Tivoli OPC uses JES exits,among other things, to track the progress ofMVS jobs, it does not start before JES is active.

Stopping Tivoli OPCTo stop Tivoli OPC, enter the following MVSoperator command:


STOP Tivoli OPC

P procname (procname = Tivoli OPC JCLprocedure name)

If you are stopping a controller, the controllercreates a backup copy of the current plandataset (if required) and ends all active func-tions.

When Tivoli OPC ends, it writes this messageto the message log:

STOP message log

EQQZð86I NO ACTIVE Tivoli OPC SUBTASKS.

Tivoli OPC IS ENDING

Canceling Tivoli OPCIf Tivoli OPC is still active 5 minutes after youenter the STOP operator command, you mustcancel Tivoli OPC.

You may also need to cancel Tivoli OPC if thecurrent plan is corrupt, because a normal shut-down causes a backup to the alternate file(refer to Customization and Tuning for details ofcurrent plan recovery). There are two ways todo this. The first is to enter:

(1) CANCEL Tivoli OPC

C procname,DUMP (procname = TivoliOPC JCL procedure name)

This causes Tivoli OPC to end with a dump onthe SYSMDUMP file (if the ddname is in thestarted-task JCL). The second way is to enter:

(2) CANCEL Tivoli OPC

C procname (procname = Tivoli OPCJCL procedure name)

This causes Tivoli OPC to end without a dump.


If the STOP command is ineffective and youhave no earlier documentation of the problem,cancel Tivoli OPC with a dump so that the errorcan be located.

Modifying Tivoli OPCUsing the MODIFY command, you can supplyinformation to Tivoli OPC after it has started.The syntax of the MODIFY command is:

MODIFY Tivoli OPC

F procname,modifyoption

where:

procname Is the Tivoli OPC JCL procedurename

modifyoption Is one of the following:

S=taskname Start the specified Tivoli OPCsubtask.

P=taskname Stop the specified Tivoli OPCsubtask.

taskname can be one of thefollowing:

APPC APPC subtask.

AR Automatic recoverysubtask.

A4 APPC tracker routersubtask.

DC Catalog managementsubtask.

DRT Data router subtask.

EMGR Event managersubtask.

ERDR All active event-readersubtasks.

EWTR Event writer subtask.

EXA External routersubtask.

| FL Fetch joblog task.

GEN General servicesubtask.

JCC Job-completion-checkersubtask.

MVS Commands to Control Tivoli OPC 13

NMM Normal-mode-managersubtask. The normalmode manager mustbe restarted as soonas possible after it hasstopped. Many TivoliOPC functions requirean active NMM task toexecute successfully.

RODM RODM subtask.

SUB Submit subtask.

TA TCP/IP router subtask.

VTAM Network communi-cation function (NCF)subtask.

WSA Workstation analyzersubtask.

Only the tasks in the Tivoli OPCsubtask table can be activatedby a MODIFY command. Thesubtask table is built when TivoliOPC is started. This means thatyou can only start a task thathas stopped earlier in the currentsession. If you attempt to start astarted subtask or stop astopped subtask, error messageEQQZ049W is issued, and noaction is taken.

CPQSTA=ONActivates theSTATMSG(CPLOCK) message.

CPQSTA=OFFDeactivates theSTATMSG(CPLOCK) message.

DSPSTA Displays, in message EQQZ095,the status of statistics mes-saging. The message indicateswhether messaging is active forEVENTS, CPLOCKS,GENSERV, and WSATASK. Italso gives the values currentlyset for EVELIM and STATIM.For details, refer to Tivoli OPCMessages and Codes.

EVELIM=nnnnSets the new value of theEVELIM keyword of the JTOPTS


statement. Allowed values are 0to 9999.

EVESTA=ON Activates theSTATMSG(EVENTS) message.

EVESTA=OFFDeactivates theSTATMSG(EVENTS) message.

GENSTA=ONActivates theSTATMSG(GENSERV)message.

GENSTA=OFFDeactivates theSTATMSG(GENSERV)message.

HB(, TRK) Sends a heartbeat message onthe MVS system log for the OPCsubsystem or for all trackersconnected to that subsystem if itis an OPC controller. IfGEM/OPC instrumentation isactive, a heartbeat event is sentto the Tivoli GEM console andan icon is shown for the sub-system and for each activetracker agent connected to thatsubsystem.

JCLDBG=ONActivates the single JCL trace.For each job handled by WSAtask information, such as theelapsed time in millisecondsneeded to handle the job,retrieve the JCL, access the JSVSAM, or whatever else, will beshown.

This is a powerful trace andshould be activated only for shortperiods of time to identify pos-sible performance problems.

JCLDBG=OFFDeactivate the single JCL trace.

NEWDSLST Order a Tivoli OPC tracker torebuild the dataset triggeringfilter table EQQDSLST. Thenew table is read from memberEQQDSLST of the dataset refer-enced to by the EQQJCLIB


ddname in the started task JCLfor the tracker. The new tablereplaces the table in ECSA.

NEWNOERR Order a Tivoli OPC tracker torebuild the NOERROR table, inthe case NOERROR statementshave been modified in theparameter library member thatcontains the JTOPTS statement.

NOERRMEM(member)Order a Tivoli OPC tracker torebuild the NOERROR table, inthe case NOERROR statementshave been modified in a param-eter library member that wasspecified in an INCLUDE state-ment.

NOERRMEM(M1)Order a Tivoli OPC tracker todelete all NOERROR codesdefined by member M1, onceyou have previously changed M1to contain only comments. Themodified member can contain adifferent number of NOERRORcodes than the original member.

Note: Tivoli OPC opens theEQQPARM library when TivoliOPC is started and parameterlibrary members (residing inlibrary extents), that have beencreated, cannot be accessed,after have been opened. Toavoid this problem, the datasetsthat define the EQQPARM libraryshould be allocated without anysecondary extents.

QUELEN=nnnnSets the new value of theQUEUELEN keyword of theJTOPTS statement. Allowedvalues are 0 to 9999, but aminimum value of 5 is forced.

STATIM=nn Sets the new value of theSTATIM keyword of the JTOPTSstatement. Allowed values are 0to 99.


STATUS Returns a message on thesystem log with the status of theOPC subsystem. The status canbe one of the following:

FULLY_OPERATIONALEverything is activeand is working prop-erly.

PARTIALLY_OPERATIONALThe OPC subsystemhas limitedfunctionality. Forexample, if a con-troller ER isstopped, the con-troller can stillschedule jobs butcannot receive theirstatuses.

NOT_OPERATIONALThe major sub-system functionalityis not available. Forexample, a controlleris not able toexecute a plan or tosubmit a job.

STATUS, DD=ddnameChecks for the status of theTivoli OPC dataset associatedwith the specified ddname.ddname can be a specific DDname, such as EQQWSDS,EQQCP1DS, or EQQLTDS, or itcan assume the value ALL, CP,DB, LTP, or JTL. It returns thereturn code of the last I/O opera-tion performed on that ddname.The status of the dataset can beone of the following:

NORMAL WARNING SEVERE CRITICAL UNKNOWN

STATUS, {OP_COMP | OP_ERR}, "destinationname"Returns the number of com-pleted operations (OP_COMP) or


the number of ended-in-erroroperations (OP_ERR) for thespecified tracker (destinationname).

Notes:

1. If more than one workstationis defined for tracker trackername, the number of com-pleted or in-error operationsis the sum of the operationson all the workstationsdefined on that tracker.

2. destination name is the des-tination name of a TivoliOPC tracker, as specified inthe ROUTOPTS keyword inthe initialization statements.

STATUS, SUBTASKLists all Tivoli OPC subtasks withtheir statuses. The status canbe ACTIVE or INACTIVE.

STATUS, TRK={ trkname | trktype}Returns the status of a TivoliOPC tracker agent defined forthat controller. The status canbe ACTIVE or INACTIVE, indi-cating whether an active sessionexists for that tracker agent.

trkname The tracker agent des-tination name definedin the Tivoli OPCPARM member, or theTCP/IP or SNAaddress of the trackeragent

trktype The type of trackeragent. It can be TCP,SNA, APPC or ALL .If you specify one ofthese values, you willget the status for eachdefined tracker agentof that type. Forexample, if you specifyTCP, you will get thestatus of all TCP/IPtracker agents youhave defined for thatcontroller; if you


specify ALL, you willget the status of alltrackers defined tothat controller.

TAKEOVER Order a standby controller totake over the functions of thecontroller. This command isvalid only when both systemsare part of the same XCF group,and no controller is active. Youcan use this command only forTivoli OPC address spaceswhere OPCHOST(STANDBY) isspecified on the OPCOPTSinitialization statement.

Note: Takeover can occur auto-matically if you have specifiedthe TAKEOVER keyword on theXCFOPTS initialization statementof a standby system. Refer toCustomization and Tuning formore information.

VSTRC=STARTStart a trace on the message logof all VSAM I/O requests. In abusy Tivoli OPC system, you willneed a large message-logdataset, and the trace will affectthe performance of the TivoliOPC system.

VSTRC=STOPStop a VSAM I/O request traceon the message log.

WSASTA=ONActivates theSTATMSG(WSATASK)message.

WSASTA=OFFDeactivates theSTATMSG(WSATASK)message.

After the STOP command is entered, theMODIFY command no longer functions, andgives this message on SYSLOG:

IEE324I MODIFY REJECTED - TASK BUSY


Automatic Recovery

RECOVER statement

55──//\%OPC RECOVER───────────────────────────────────5

┌ ┐─,───────────────────────────────────── │ │┌ ┐─,───────────────────5─ ───

6┴┬ ┬──ERRSTEP=( ───

6┴┬ ┬─stepname────────── ) ────────5%

│ │├ ┤─stepname.procstep─ │ │└ ┘─stepname–stepname─ │ │┌ ┐─,─────────────────

├ ┤──JOBCODE=( ───6

┴┬ ┬─abendcode─────── ) ── │ │├ ┤─casecode──────── │ │├ ┤─retcode───────── │ │└ ┘─retcode–retcode─ │ │┌ ┐─,─────────────────

├ ┤──STEPCODE=( ───6

┴┬ ┬─abendcode─────── ) ─ │ │├ ┤─casecode──────── │ │├ ┤─retcode───────── │ │└ ┘─retcode–retcode─

├ ┤──TIME=( ─── ──hhmm-hhmm─ ) ───────────── │ │┌ ┐─,───────────────────

├ ┤──DELSTEP=( ───6

┴┬ ┬─stepname────────── ) │ │└ ┘─stepname–stepname─ │ │┌ ┐─,────────────────

├ ┤──ADDPROC=( ───6

┴─ ──procedure name─ ) ─── │ │┌ ┐─,───────────────────

├ ┤──RESSTEP=( ───6

┴┬ ┬─stepname────────── ) │ │├ ┤─stepname.procstep─ │ │├ ┤─\───────────────── │ │├ ┤─%───────────────── │ │└ ┘─checkid───────────

├ ┤──CALLEXIT=( ─── ──program name─ ) ────── │ │┌ ┐─Y───

├ ┤──RESTART=( ──┼ ┼─YES─ ) ──────────────── │ │├ ┤─N─── │ │└ ┘─NO──

├ ┤──RESJOB=( ─── ──job name─ ) ──────────── │ │┌ ┐─,──────────────────

├ ┤──ADDAPPL=( ───6

┴─ ──application name─ ) ─ │ │┌ ┐─,──────────────────

├ ┤──RELSUCC=( ───6

┴─ ──application name─ ) ─├ ┤──ALTWS=( ─── ──workstation name─ ) ─────└ ┘──ALTJOB=( ─── ──job name─ ) ────────────

You cannot have JCL variables on theRECOVER statement.


JCL Directives

SCAN directive

SCAN Directive

55──//\%OPC SCAN─────────────────────────────5%

SEARCH directive

SEARCH Directive

55──//\%OPC SEARCH────────────────────────────5

┌ ┐─,────────────────── │ │┌ ┐─,────────────5─ ──NAME=( ───

6┴┬ ┬───

6┴┬ ┬──────────── ) ──────────5%

│ │└ ┘─table name─ │ │┌ ┐─APPL─── ├ ┤──┼ ┼──────── ────── │ │└ ┘─NOAPPL─ │ │┌ ┐─GLOBAL─── └ ┘──┼ ┼────────── ──── └ ┘─NOGLOBAL─

TABLE directive

TABLE Directive

55──//\%OPC TABLE─ ──NAME=( ─table name─) ──────5%

SETFORM directive

SETFORM Directive

55──//\%OPC SETFORM───────────────────────────5

5─ ──dynamic-variable-name=( ─format─) ─────────5%

� Choose the variable from Table 4 onpage 35.

� Compose the format from one or more ofthese keywords and any other charactersexcept &, %, ?, =, (, and ):CC Century (2 digits)YY Year (2 digits)MM MonthDDD Day in year (Julian)DD Day in monthHH Hour (time variables only)MM Minutes (time variables only)


SETVAR directive

SETVAR Directive

55──//\%OPC SETVAR────────────────────────────5

┌ ┐─,───────────────────────────────────5─ ───

6┴┬ ┬──Tname=(─date variable +/– nnnTT─) ──5%

└ ┘──┬ ┬──────────────────── ─────────── │ │┌ ┐─SUBMIT─ └ ┘ ─PHASE=─ ──┴ ┴─SETUP──

� Use parentheses around the expression forthe temporary variable Tname.

� Begin the variable Tname with the letter T.� TT is the type and can be one of:

WD Work daysCD Calendar daysWK WeeksMO MonthsYR Years

BEGIN and END directives

BEGIN Directive

55──//\%OPC BEGIN─────────────────────────────5

┌ ┐─,─────────────────────────────────5─ ───

6┴┬ ┬──ACTION= ──┬ ┬─EXCLUDE─ ─────────── ────5%

│ │├ ┤─INCLUDE─ │ │└ ┘─NOSCAN── ├ ┤──┬ ┬──────────────────── ───────── │ ││ │┌ ┐─SUBMIT─ │ │└ ┘ ─PHASE=─ ──┴ ┴─SETUP── └ ┘──┬ ┬───────────────────────────── │ │┌ ┐─,────────── └ ┘─COMP=──(─ ───

6┴(expression) ─)─

END Directive

55──//\%OPC END─ ──ACTION= ──┬ ┬─EXCLUDE─ ───────5% ├ ┤─INCLUDE─ └ ┘─NOSCAN──

FETCH directive

FETCH Directive

55──//\%OPC FETCH─────────────────────────────5

┌ ┐─,─────────────────────────────5─ ───

6┴┬ ┬──┬ ┬──MEMBER=member ────────── ────────5%

│ │└ ┘──EXIT=exit ──── ├ ┤──┬ ┬──────────────────── ───── │ ││ │┌ ┐─SUBMIT─ │ │└ ┘──PHASE= ──┴ ┴─SETUP── └ ┘──┬ ┬───────────────────────── │ │┌ ┐─,──────────

└ ┘──COMP=( ───6

┴(expression) )


COMP Keyword on BEGIN andFETCH Directives

COMP keyword

┌ ┐─,──────────────────────── │ │┌ ┐─,──55─ ──COMP=( ───

6┴( exp1 ──┬ ┬─.EQ.─ ( ───

6┴exp2 )) ) ───5%

├ ┤─.NE.─ ├ ┤─.GE.─ ├ ┤─.GT.─ ├ ┤─.LE.─ └ ┘─.LT.─

Only & (ampersand) variables are valid in theCOMP expressions, and embedded blanks arenot allowed.

JCL Directives 27

Tivoli OPC-Supplied JCLVariables

Note: IA = input arrival

Occurrence-Related JCL Variables

Table 2 (Page 1 of 3). Occurrence-relatedTivoli OPC-supplied JCL variables

Variablename

Length(bytes)

Description

OADID 16 Application ID

OADOWNER 16 Occurrence owner

OAUGROUP 8 Authority group

OCALID 16 Calendar name

ODAY 1 Occurrence IA day ofthe week (1–7); 1represents Monday

ODD 2 Occurrence IA day ofmonth, in DD format

ODDD 3 Occurrence IA day ofthe year, in DDD format

ODMY1 6 Occurrence IA date inDDMMYY format

ODMY2 8 Occurrence IA date inDD/MM/YY format

OFREEDAY 1 Denotes whether theoccurrence IA date is afree day (F), or aworkday (W)

OHH 2 Occurrence IA hour inHH format

OHHMM 4 Occurrence IA hour andminute in HHMM format

OMM 2 Occurrence IA month inMM format

OMMYY 4 Occurrence IA monthand year in MMYYformat

OWW 2 Occurrence IA week ofthe year in WW format



Variablename

Length(bytes)

Description

OWWD 3 Occurrence IA week,and day within week, inWWD format, whereWW is the weeknumber within the year,and D is the day withinthe week

OWWLAST 1 A value, Y (yes) or N(no), that indicateswhether the occurrenceIA date is in the lastweek of the month

OWWMONTH 1 A value between 1 and6 that indicates theoccurrence IAweek-in-month, whereeach new week beginson a Monday. Forexample, considerthese occurrence IAdates for the month ofJanuary in 1996:

Date ValueMonday 1st 1Monday 8th 2Wednesday 31st 5

OYMD 8 Occurrence IA date inYYYYMMDD format

OYM 6 Occurrence IA monthwithin year in YYYYMMformat

OYMD1 6 Occurrence IA date inYYMMDD format

OYMD2 8 Occurrence IA date inYY/MM/DD format

OYMD3 10 Occurrence IA date inYYYY/MM/DD format

OYY 2 Occurrence IA year inYY format

OYYDDD 5 Occurrence IA date asa Julian date in YYDDDformat

OYYMM 4 Occurrence IA monthwithin year in YYMMformat



Variablename

Length(bytes)

Description

OYYYY 4 Occurrence IA year inYYYY format, forexample, 1996

Tivoli OPC-Supplied JCL Variables 31

Operation-Related JCL Variables

Variablename

Length(bytes)

Description

OJOBNAME 8 Operation job name

OLDAY 1 Operation latest startday (1–7); 1 representsMonday, 7 representsSunday

OLDD 2 Operation latest startday (day in the month)

OLHH 2 Operation latest starthour

OLHHMM 4 Operation latest start inhours and minutes

OLMD 4 Operation latest starttime (month and day),in MMDD format

OLMM 2 Operation latest starttime in minutes, in MMformat

OLWK 2 Operation latest startweek (week in theyear), WW format

OLYMD 6 Operation latest startdate in YYMMDDformat

OLYYDDD 5 Operation latest start inJulian date format(YYDDD)

OOPNO 3 Operation numberwithin the occurrence,right-justified andpadded with zeros

OWSID 4 Workstation ID forcurrent operation


Date-Related JCL Variables

Table 3 (Page 1 of 2). Date-related JCL vari-ables

Variablename

Length(bytes)

Description

CDAY 1 Current day of theweek; 1 representsMonday, 7 representsSunday

CDD 2 Current day of monthin DD format

CDDD 3 Day number in thecurrent year

CDDMMYY 6 Current date inDDMMYY format

CHH 2 Current time in HHformat

CHHMM 4 Current hour andminute in HHMMformat

CHHMMSSX 8 Current hour, minute,second, and hun-dredths of seconds inHHMMSSXX format

CMM 2 Current month in MMformat

CMMYY 4 Current month withinyear in MMYY format

CWW 2 Week number in thecurrent year

CWWD 3 Current day withinweek in WWD format,where WW is the weeknumber within the yearand D is the day withinthe week

CYMD 8 Current date inYYYYMMDD format

CYY 2 Current year in YYformat

CYYDDD 5 Current Julian date inYYDDD format

CYYMM 4 Current month withinyear in YYMM format

CYYMMDD 6 Current date inYYMMDD format


Table 3 (Page 2 of 2). Date-related JCL vari-ables

Variablename

Length(bytes)

Description

CYYYY 4 Current year in YYYYformat, for example,1990

CYYYYMM 6 Current month withinyear in YYYYMMformat


Dynamic-Format Supplied Variables

Table 4. Dynamic-format date-related TivoliOPC-supplied variables

Variablename

Description

CDATE Current date

CTIME Current time

OCDATE Occurrence IA date

OCFRSTC First calendar day in month of theoccurrence IA date

OCFRSTW First work day in the month of theoccurrence IA date

OCFRSTWY First work day in the year of theoccurrence IA date

OCLASTC Last calendar day in the month ofthe occurrence IA date

OCLASTW Last work day in the month of theoccurrence IA date

OCLASTWY Last work day in the year of theoccurrence IA date

OCTIME Occurrence IA time (hours andminutes)

OPIADATE Operation IA date (if blank, thistakes the value of the occurrenceIA date)

OPIATIME Operation IA time (if blank, thistakes the value of the occurrenceIA time)

OPLSDATE Operation latest start date

OPLSTIME Operation latest start time


Codes

The occurrence status codes are:

C CompleteD DeletedE An operation in the occurrence has

ended-in-errorP A pending predecessor exists for the

occurrenceS StartedU Undecided (the status is not known)W No operations in the occurrence have

started.

Operation Status and ExtendedStatus CodesWhen Tivoli OPC displays the status of anoperation, it uses the format xy, where x is thestatus code and y, if present, is the extendedstatus code.

Operation Status CodesThe operation status codes are:

A Arriving—the operation is ready for proc-essing; no predecessors were defined

R Ready for processing; all predecessors arecomplete

S Started

C Complete

D Deleted

I The operation is interrupted

* Ready—at least one predecessor isdefined on a nonreporting workstation; allpredecessors are complete

E The operation has ended-in-error

W The operation is waiting for a predecessorto complete

U Undecided—the operation status is notknown.


Extended Status CodesTogether with the normal status codes, TivoliOPC maintains extended status codes thatprovide additional information about the statusof operations. The extended status code is notalways present.

The following extended status codes are valid,depending on the type and status of theoperation:

� Valid for all operations that have a status ofarriving (A) or ready (* or R):

X Waiting for resourceH A dialog user has used the HOLD

command on the operationN A dialog user has used the NOP

command on the operation

� Valid for all operations that have a status ofarriving (A), ready (* or R), started (S), orerror (E):

M The status of the operation has beenmanually set by a dialog user fromthe ready list.

� Valid only for computer workstation oper-ations that have a status of arrived (A) orready (* or R):

T Waiting until a particular time

L The operation is a latetime-dependent operation with thesuppress-if-late attribute

R The operation has ended in errorbut was automatically reset (thecompletion code is defined in theinstallation options to be automat-ically reset)

E An error occurred during job sub-mission or release

D Closedown in progress.

Blank OPC is in the process of submit-ting this job. OPC is waiting forthe availability of a parallel serveror a critical resource, or the opera-tion is not to be submitted auto-matically.

� Valid only for computer workstation oper-ations that have a status of started (S):


Q The job has been added to theJES job queue

S The job or started task is exe-cuting

M The status of the job or startedtask has been manually set to S

U Submit in progress

Blank The job has been successfullysubmitted but has not yet beenreported as added to the JES jobqueue.

� Valid only for computer workstation oper-ations that have a status of ready (R) orerror (E):

A The job is waiting for a deferredcatalog management action to beinitiated or discarded by a dialoguser

C The job is waiting for the catalogmanagement action to be com-pleted.

Error CodesTivoli OPC assigns error codes to certain oper-ations and to job and started task steps. Thesecodes are used by the automatic job recoveryfunction to decide a recovery action.

CAN The job or started task was canceledby the operator or by a TSO userbefore execution. This code is alsopossible if the job-termination event(type 3P) is missing.

CCUN The completion code is unknown.The job or started task has ended,but no completion code is available.This code is also possible if thejob-end event (type 3J) is missing.

Check the job log and SYSLOG.

JCCE An error during JCC (job completionchecker) processing prevented theJCC from determining an error codefor the operation.

JCL A JCL error was recognized after thejob or started task began to execute,or a JCL error was recognized aftersyntax checking in the internalreader.

Codes 39

JCLI A JCL error occurred immediately;that is, the error was detected beforethe job or started task began. Thiscode is also possible when both thejob-start event (type 2) and thejob-end event (type 3J) are missing.

MCP The operation was manually set toerror in the MCP dialog.

OFxx The system that the operation isdefined on has gone offline. TheWSOFFLINE parameter on theJTOPTS initialization statementspecifies that started operationsshould be marked as ended-in-error.xx is the status and extended statusof the failing operation. Operationsthat were running (status SS) have astep-code error status of OFFL.

OJCV An error occurred duringJCL-variable substitution when thejob or started task was submitted, orTivoli OPC detected an error in theRECOVER statement during auto-matic recovery. Browse the JCL forthe operation or the EQQMLOGdataset to find more informationabout the failure.

OSEQ A job or started task began toexecute before all its predecessorshad completed. This can occur onlyif the job was not submitted by TivoliOPC and if either HOLDJOB(NO) orHOLDJOB(USER) is specified forthe Tivoli OPC event writer options.Refer to Customization and Tuning.

OSUB A failure occurred when Tivoli OPCattempted to submit a job or start astarted task. In the case of a startedtask, it could be that the started taskis a subsystem that is not started byJES, or the Tivoli OPC subsystemEQQSTC ddname is not allocated toa JES-defined procedure library.The operation should be marked asended-in-error.

OSUF A failure occurred when Tivoli OPCattempted to retrieve the JCL for ajob or started task. This code is setif the SUBFAILACTION keyword of


the JTOPTS initialization statementspecifies that the operation shouldbe marked as ended-in-error. Thiscode is also caused if you haveJOBCHECK(SAME) and the jobname in the application descriptiondoes not match the one on the jobcard.

OSUP A time operation is late, and theSUPPRESSACTION parameter ofthe JTOPTS initialization statementspecified that the operation shouldbe marked as ended-in-error.

OSxx The system on which the operationis defined has failed. TheWSFAILURE parameter on theJTOPTS initialization statementspecifies that started operationsshould be marked as ended-in-error.xx is the status and extended statusof the failing operation. Operationsthat were running (status SS) have astep-code error of OSYS.

PCAN A print operation was canceled bythe operator.

nnnn Step return code.

Sxxx System abend code.

Uxxx User abend code in hexadecimalnotation. For example user abend2750 is represented in Tivoli OPC asUABE.

xxxx User-defined error code.

Catalog Management Status CodesWhen the catalog management function isused, Tivoli OPC maintains status informationto report on the progress of the catalog man-agement action. The following CM statuscodes are possible:

Z Cancelled—catalog management status isnot available. Examine the Tivoli OPCmessage log for CM errors; one possibilityis that the dataset collection at the trackerhas failed.

E Catalog management action has failed.

I Catalog management has been initiatedbut has not yet started.

Codes 41

S The catalog management action hasstarted.

M The catalog management action is inprogress but is delayed waiting for aresponse from DFHSM.

R A catalog management action has beenrestarted. This status is possible if eitherthe controller or tracker stopped while aCM action was in progress.

C Actions completed normally.

D The catalog management action has beendiscarded by a dialog user or thepre-catalog management exit, EQQUX008.

X Excluded—Tivoli OPC has determined thatthere are no datasets defined by DD state-ments in the JCL that require catalog man-agement actions. This status has thesame meaning as complete.

Job Log Retrieval Status CodesWhen the job log retrieval function is used,Tivoli OPC maintains status information toreport on the retrieval of the log. The followingstatus codes are possible:

C Completed—the controller hasreceived the log.

E Error. There was an error retrievingthe log.

I Initiated. The controller has sent aretrieval request to the tracker, butthe tracker has not yet processed therequest.

S Started. The controller has sent aretrieval request to the tracker, andthe tracker has started to retrieve thelog.

blank The controller has not sent anyretrieval request to the tracker.


Operation Reason CodesIf you include the RSNC field in the ready list,you get these operation reason codes. Thecodes are listed in hierarchical order. Forexample, if job submission failed, and job sub-mission is deactivated, code D is obtained—notcode F.

D Job submission deactivated.C Workstation is closed.P All parallel servers in use.S Special resource is unavailable.A Automatic reset error condition.F Job submission failed.J No automatic job submission.L Job is late.T Start time not reached.1 Not enough free WS resource 1.2 Not enough free WS resource 2.H Closedown in progress.

Codes 43

Reason CodesThe following table lists the Tivoli OPC reasoncodes generated when data validation fails fordatabase fields. The 'related message' numbercan be used to search in the Tivoli OPC Mes-sages if you need more information.

Reasoncode

Meaning (reasonfor failure)

Relatedmessage

000 The record sizeexceeds themaximum recordsize for the appli-cation descriptiondatabase.

EQQX300

002 The record versionis invalid.

EQQX301

003 The application IDis invalid.

EQQX302

004 The applicationstatus is invalid.Valid applicationstatuses are: A foractive, P forpending, or blankfor both active andpending.

EQQX303

005 The valid-to date isinvalid.

EQQX304

006 The valid-to time isinvalid.

EQQX328

007 The record identi-fier is invalid.

EQQX321

010 The run cyclepointer is invalid.

EQQX305

011 The record sizedoes not includethe run cycle.

EQQX306

012 The offset to thenext run cycle inthe record isinvalid. It must be0 if it is last.

EQQX307

013 The JCL variabletable name isinvalid.

EQQX417

014 A valid rule namemust be specified.

EQQA521


Reasoncode


Relatedmessage

020 The operationpointer is invalid.

EQQX308

021 The record sizedoes not includeoperation data.

EQQX309

022 The offset to thenext operation inthe record isinvalid. It must be0 if it is last.

EQQX310

023 The record sizedoes not includedependencies andspecial resources.

EQQX311

100 The valid-from dateis invalid ormissing.

EQQX312

101 The valid-from dateis later than thevalid-to date; itmust be earlier.

EQQX313

102 The authorizationgroup is invalid.

EQQX314

103 The owner ID ismissing.

EQQX315

104 The date for thelast update isinvalid or missing.

EQQX316

105 The time for thelast update isinvalid or missing.

EQQX317

106 The priority isinvalid or missing.A valid priority is anumber from 1–9.

EQQX318

107 The value specifiedin the number ofoperations field isinvalid. A validvalue is a numberfrom 1–99.

EQQX319

108 The number of runcycles is invalid. Itdoes not match theactual number ofrun cycles in therecord.

EQQX320

Codes 45

Reasoncode


Relatedmessage

109 The offset to thefirst run cycle isincompatible withthe number of runcycles.

EQQX322

110 The offset to thefirst operation isinvalid.

EQQX323

111 The common partof the applicationdescription recordhas invalid charac-ters.

EQQX324

112 The calendardescription identi-fier in the applica-tion descriptionrecord is invalid.

EQQX325

113 The calendardescription identi-fier referred to bythe applicationdescription recorddoes not exist inthe database.

EQQX326

114 The owner ID con-tains lower casecharacters.

EQQX397

115 No run cycles areallowed for anapplication in agroup.

EQQA516

116 Priority cannot bespecified for agroup definition.

EQQA510

117 Group definitionscannot containoperations.

EQQA500

118 Calendar cannotbe specified for anapplication in agroup.

EQQA511

119 Group definitioncannot belong toanother group.

EQQA503

120 The valid-from timeis invalid.

EQQX327


Reasoncode


Relatedmessage

122 Validity periods oftemporary OI'smust not overlap.

EQQK002

200 The run cycleperiod cannot befound.

EQQX329

201 The positive runday offset is notblank or numeric.It must be blank or1 to 999.

EQQX330

202 The negative runday offset is notblank or numeric.It must be blank or1 to 999.

EQQX376

203 The free day rulespecification isinvalid. A validspecification is Efor free daysexcluded; 1 for runon the closest workday before the freeday; 2 for run onthe closest workday after the freeday; 3 for run onthe free day; or 4for do not run atall.

EQQX331

204 The run cyclevalid-from date isinvalid or missing.

EQQX381

205 The run cyclevalid-to date isinvalid or missing.

EQQX375

206 The negative runcycle indicator isincorrect. It mustbe either blank orN.

EQQX332

207 The input arrivaltime is invalid.

EQQX333

208 The relative dead-line day is notnumeric. It mustbe a number from0–99.

EQQX334

Codes 47

Reasoncode


Relatedmessage

209 The deadline timeis invalid.

EQQX335

210 The run cyclesection containsinvalid characters.

EQQX336

211 Duplicate positiverun day offsetsfound in a runcycle.

EQQX398

212 The variable tableis not defined toTivoli OPC.

EQQX418

213 No run cycleoffsets have beendefined for theperiod.

EQQX436

214 A negative run dayspecification con-tains errors.

EQQX437

215 The rule namemust be uniquewithin an applica-tion definition.

EQQA522

216 The rule on whichthe run cycle isbased must bedefined.

EQQA520

301 The workstationdescription doesnot exist in theworkstationdescription data-base.

EQQX337

302 The operationnumber is invalid.It must be anumber from 1–99.

EQQX338

303 The duration timeof the operation isinvalid. It must befrom 00.00 to99.59.

EQQX339

304 The smoothingfactor is invalid. Itmust be a numberfrom 0–999.

EQQX340


Reasoncode


Relatedmessage

305 The feedback limitis invalid. A validfeedback limit is anumber from100–999.

EQQX341

306 The automaticerror completioncode is invalid.

EQQX342

307 The job name isinvalid.

EQQX343

308 The operation inputarrival relative dayis invalid.

EQQX344

309 The operation inputarrival time isinvalid.

EQQX345

310 The operationdeadline relativeday is invalid.

EQQX346

311 The operationdeadline time isinvalid.

EQQX347

312 The workstationresource 1 usageis invalid.

EQQX348

313 The workstationresource 2 usageis invalid.

EQQX348

314 The parallel proc-essing count isinvalid.

EQQX349

315 The number ofinternal predeces-sors is invalid; it isnot compatible withthe actual numberof predecessors inthe record.

EQQX350

316 The number ofexternal predeces-sors is invalid; it isnot compatible withthe actual numberof predecessors inthe record.

EQQX351

Codes 49

Reasoncode


Relatedmessage

317 The number ofspecial resourcesis invalid; it is notcompatible with theactual number ofspecial resourcesin the record.

EQQX352

318 The operation partof the applicationdescription recordcontains invalidcharacters.

EQQX353

319 Cancel if late spec-ified for the nontime-dependentjob.

EQQX412

320 Relative start daymissing for thetime-dependentjob.

EQQX413

321 Start time missingfor thetime-dependentjob.

EQQX414

322 Job name ismissing for thecomputer, printer,or job setup opera-tion.

EQQX415

323 Number of parallelservers must be 1for an operation ona computer work-station.

EQQX419

400 The workstationname for theinternal prede-cessor is invalid.

EQQX354

401 The operationnumber for theinternal prede-cessor is invalid.

EQQX355

402 The transport timefor the internalpredecessor isinvalid.

EQQX356


Reasoncode


Relatedmessage

403 The internal prede-cessor block con-tains invalidcharacters.

EQQX357

404 All internalprocessors in anoperation must beunique.

EQQX395

450 The required appli-cation descriptiondoes not exist.

EQQX377

455 The required appli-cation descriptiondoes not containan operator withthe specified oper-ation number andworkstation name.

EQQX378

456 The required appli-cation does notcontain an opera-tion with the speci-fied operationnumber.

EQQX379

457 The required appli-cation does notcontain an opera-tion on the speci-fied workstation.

EQQX380

500 The application IDfor the externalpredecessor isinvalid.

EQQX358

501 The workstationname for theexternal prede-cessor is invalid.

EQQX359

502 The operationnumber for theexternal prede-cessor is invalid.

EQQX360

503 The transport timefor the externalpredecessor isinvalid.

EQQX356

Codes 51

Reasoncode


Relatedmessage

504 The long-term planprint option for theexternal prede-cessor is invalid.Valid print optionsare A for always,and C for condi-tionally.

EQQX361

505 The external pred-ecessor block con-tains invalidcharacters.

EQQX357

506 All externalprocessors in anoperation must beunique.

EQQX396

507 More than 100external predeces-sors were speci-fied.

EQQX433

600 The specialresource name isblank.

EQQX362

601 The specialresource heldoption type isinvalid. Validspecial resourceheld options are Sfor shared, and Xfor exclusive.

EQQX363

602 The specialresource blockcontains invalidcharacters.

EQQX364

603 Duplicate specialresources exist inthe operation.

EQQX394

604 The resourcequantity is not inthe range 1 to999 999.

EQQX438

605 The predecessorinput arrival time isrequired but notavailable.

EQQX429


Reasoncode


Relatedmessage

700 Duplicate oper-ations exist in theapplicationdescription record.

EQQX365

701 A predecessordoes not exist.

EQQX366

702 There is a loop inthe applicationnetwork.

EQQX367

703 All operations inthe application donot belong to thesame network.

EQQX368

704 A job setup,processor, or printoperation lacks ajob name.

EQQX369

705 A job setup opera-tion has noprocessor opera-tion as successor.

EQQX370

706 A print operationhas no predeces-sors.

EQQX371

707 A print operationhas more than onepredecessor.

EQQX372

708 A print operationdoes not have aprocessor opera-tion as prede-cessor.

EQQX373

709 A print operationhas a predecessorwith a different jobname.

EQQX374

710 A job setup opera-tion has noprocessor suc-cessor with thesame job name.

EQQX416

800 The calendarrecord exceeds themaximum recordsize for the cal-endar descriptionrecord, or has ashorter thanminimum size.

EQQX400

Codes 53

Reasoncode


Relatedmessage

801 The calendardescription recordidentifier wasinvalid.

EQQX321

802 The calendardescription recordversion wasinvalid.

EQQX301

803 The calendardescription ID isinvalid.

EQQX401

804 The date for thelast update isinvalid or missingin the calendardescription record.

EQQX316

805 The time for thelast update isinvalid or missingin the calendardescription record.

EQQX317

806 The time for WorkDay End Time isinvalid or missingin the calendardescription record.

EQQX402

807 The number ofweekday/date dayshas an invalidvalue in calendardescription record.

EQQX403

808 The commonsection of the cal-endar descriptionrecord containsinvalid characters.

EQQX404

809 The size of the cal-endar descriptionis too short to holdthe number ofweekday/date daysindicated in thecommon section ofthe record.

EQQX405

810 The weekday inthe calendardescription recordis invalid.

EQQX406


Reasoncode


Relatedmessage

811 The weekday daysare not inascending order inthe calendardescription record.

EQQX407

812 The status of theweekday/date fieldis not Work orFree.

EQQX408

813 The date in thecalendardescription recordis invalid.

EQQX409

814 The date days arenot in ascendingorder in the cal-endar descriptionrecord.

EQQX410

815 The variablesection of the cal-endar descriptionrecord containsinvalid characters.

EQQX411

850 The application IDwas not specified.

EQQX390

851 The application IDis not bracketed byshift-in or shift-outcharacters.

EQQX382

852 The DBCS part ofthe field applicationID is blank.

EQQX384

853 Check if theroutine hasencountered asuperfluousshift-out or shift-incharacter withinthe DBCS part ofthe field applicationID.

EQQX385

Codes 55

Reasoncode


Relatedmessage

854 The Field applica-tion ID containseither invalidDBCS characters,that is, out of therange X'41' - X'FE',or an odd numberof blanks (x'40'), inthe trailing part ofthe DBCS part ofthe field.

EQQX387

855 The DBCS-fieldapplication ID con-tains an oddnumber of bytes.

EQQX392

860 Group definition IDis invalid.

EQQX500

861 Group definition IDnot in bracketedDBCS format.

EQQX501

862 No ID specified forDBCS group defi-nition.

EQQX505

863 Unpaired shift-outor shift-in charac-ters in group defi-nition.

EQQX502

864 Invalid DBCS char-acters in groupdefinition.

EQQX503

865 Odd number ofbytes in group defi-nition.

EQQX504

870 The field owner IDwas not specified.

EQQX391

871 The field owner IDis not bracketed byshift-in or shift-outcharacters.

EQQX383

872 The DBCS part offield owner ID isblank.

EQQX389

873 The check routinehas encountered asuperfluousshift-out or shift-incharacter in theDBCS part of thefield owner ID.

EQQX386


Reasoncode


Relatedmessage

874 The Field owner IDcontains eitherinvalid DBCS char-acters, that is, outof the range X'41' -X'FE', or an oddnumber of blanks(x'40'), in thetrailing part of theDBCS part of thefield.

EQQX388

875 The DBCS-fieldowner ID containsan odd number ofbytes.

EQQX393

1001 The control blockis invalid.

EQQX321

1002 The block versionis invalid.

EQQX301

1003 The request type isinvalid.

EQQX420

1004 The length isinvalid.

EQQX421

1011 The input arrivaldate is missing.

EQQX422

1012 The input arrivaldate is invalid.

EQQX423

1013 The input arrivaltime is missing.

EQQX424

1014 The input arrivaltime is invalid.

EQQX333

1015 The application IDsare different.

EQQX425

1016 The application IDis missing.

EQQX390

1017 The DBCS applica-tion ID is invalid.

EQQX387

1018 The application IDis invalid.

EQQX302

1021 The deadline dateor time is given(but not both).

EQQX426

1022 The deadline dateis invalid.

EQQX427

1023 The deadline timeis invalid.

EQQX335

Codes 57

Reasoncode


Relatedmessage

1024 The priority isinvalid.

EQQX318

1031 The predecessorinput arrival date ismissing.

EQQX428

1032 The predecessorinput arrival date isinvalid.

EQQX423

1033 The predecessorinput arrival time ismissing.

EQQX429

1034 The predecessorinput arrival time isinvalid.

EQQX333

1035 The predecessorapplication ID ismissing.

EQQX430

1036 The DBCS prede-cessor applicationID is invalid.

EQQX382

1037 The predecessorapplication ID isinvalid.

EQQX302

1038 An occurrence isdependent onitself.

EQQX434

1039 The input arrivaldate is later thanthe deadline.

EQQL510

1040 The input arrivaltime is later thanthe deadline.

EQQL510

2001 The status code isinvalid.

EQQX431

2002 The function codeis invalid.

EQQX432


Free-Day Rule

The possible values of the free-day rule are:

E Count only work days when using the ruleor offset. That is, free days are excluded.This option ensures that the scheduled daywill always be a work day. This is thedefault for offset-based run cycles.

1 Count work days and free days whenusing the rule or offset. If this gives a freeday, schedule the application on theclosest work day before the free day.

2 Count work days and free days whenusing the rule or offset. If this gives a freeday, schedule the application on theclosest work day after the free day.

3 Count work days and free days whenusing the rule or offset. If this gives a freeday, schedule the application on the freeday. This is the default for rule-based runcycles.

4 Count work days and free days whenusing the rule or offset. If this gives a freeday, do not schedule the application at all.

The free-day rule provides the flexibility toschedule your applications precisely when theyare required. Sometimes you will find that youmust work out on paper which free-day rule youshould select. When you do this, consider whatwould happen if a normal work day is declareda holiday and, therefore, is defined in the cal-endar as a free day.

When an application is normally due to run butthe calendar definition identifies the day as free,the free-day rule in the run cycle for that appli-cation determines the effect.

Figure 1 on page 60 shows what happens foreach free-day rule if you specify January withoffsets 1,6,11,16, and so on, or the equivalentrule “Every fifth day in January.”


Jan 1996

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

Shaded areas above are free days in the calendar.

Shaded areas below are the days that Tivoli OPC selects.Rule

E

1

2

3

4

60T

ivoli OP

C Q

uick Reference

Figure 1. The Effect of the Free-Day Rule

Every fifth day inJanuary

Free days in calendar

Free days excluded

Closest work day before

Closest work day after

Schedule on the freeday

Do not schedule at all

IBM

Program Number: 5697-OPC

Printed in Denmark by IBM Danmark A/S

GH19-4374-ð2

quick reference - ibmpublib.boulder.ibm.com/.../en_us/pdf/gh19-4374-02.pdf · quick reference...

Documents