tivoli workload scheduler for z/os: getting started ... › support › knowledgecenter ›...

IBM Tivoli Workload Scheduler for z/OS

Getting Started (Revised November 2014)Version 9 Release 2

SC32-1262-07

IBM

NoteBefore using this information and the product it supports, read the information in “Notices” on page 81.

This edition applies to version 9, release 2, modification level 0 SPE of Tivoli Workload Scheduler for z/OS(program number 5698-T08) and to all subsequent releases and modifications until otherwise indicated in neweditions.

© Copyright IBM Corporation 1999, 2014.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Figures . . . . . . . . . . . . . . . v

Tables . . . . . . . . . . . . . . . vii

About this publication . . . . . . . . ixWhat is new in this publication . . . . . . . . ixWho should read this publication . . . . . . . ixPublications . . . . . . . . . . . . . . ixUsing LookAt to look up message explanations . . ixAccessibility . . . . . . . . . . . . . . xTivoli technical training. . . . . . . . . . . xSupport information . . . . . . . . . . . . xConventions used in this publication . . . . . . xiHow to read syntax diagrams . . . . . . . . xi

Chapter 1. Introduction . . . . . . . . 1What is Tivoli Workload Scheduler for z/OS? . . . 1How your production workload is managed. . . . 1Concepts and terminology . . . . . . . . . . 1Setup tasks . . . . . . . . . . . . . . . 3About the examples in this manual . . . . . . . 3

Chapter 2. Communicating with thescheduler . . . . . . . . . . . . . . 5Setting options. . . . . . . . . . . . . . 5

Specifying the subsystem name . . . . . . . 6Setting date and time formats. . . . . . . . 7

Concatenating options and setting PF keys . . . . 7Concatenating options . . . . . . . . . . 8Setting PF keys . . . . . . . . . . . . 8

Using filter panels . . . . . . . . . . . . 9Using generic search arguments . . . . . . . 10Using the HELP command . . . . . . . . . 10Using the SORT and LOCATE commands . . . . 10

Sorting list output . . . . . . . . . . . 10Locating data strings in list output . . . . . 11

Chapter 3. Describing yourenvironment . . . . . . . . . . . . 13Creating workstations . . . . . . . . . . . 13

Creating a workstation . . . . . . . . . 13Creating a general job setup workstation . . . 17

Creating calendars . . . . . . . . . . . . 18Creating special resources . . . . . . . . . 19

Chapter 4. Creating applications. . . . 25Creating an application . . . . . . . . . . 26

Specifying general information . . . . . . . 26Creating a rule-based run cycle . . . . . . . 27Creating operations. . . . . . . . . . . 30

Creating a job description . . . . . . . . . 35

Chapter 5. Creating and using thelong-term plan . . . . . . . . . . . 37Creating a long-term plan . . . . . . . . . 37Adding an occurrence to the long-term plan . . . 39Using the long-term plan modify batch function . . 42Browsing occurrences in the long-term plan . . . 43

Chapter 6. Creating the current plan . . 45Creating the current plan . . . . . . . . . . 45Creating a batch job to extend the current plan . . 46Querying the current plan (QCP) . . . . . . . 47

Querying application occurrences . . . . . . 48Querying late and uncompleted occurrences . . 52

Chapter 7. Communicating withworkstations . . . . . . . . . . . . 55Using the Ready List panel . . . . . . . . . 55Selecting a ready list layout . . . . . . . . . 57Using the ready list. . . . . . . . . . . . 58

Viewing operator instructions . . . . . . . 59Preparing jobs at a setup workstation. . . . . 59

Chapter 8. Modifying the current plan(MCP) . . . . . . . . . . . . . . . 61Adding an occurrence to the current plan . . . . 61Changing details of an operation in the current plan 63Correcting and restarting failed operations . . . . 65

Correcting ended-in-error operations . . . . . 66Rerunning an occurrence from a specific operation 67

Chapter 9. Scheduling end-to-end . . . 69With fault tolerance capabilities. . . . . . . . 69

Defining a fault-tolerant workstation . . . . . 69Defining a job to be run on a fault-tolerantworkstation . . . . . . . . . . . . . 70

With z-centric capabilities . . . . . . . . . 72Defining Tivoli Workload Scheduler for z/OSAgent destinations with the ROUTOPTSstatement . . . . . . . . . . . . . . 72Defining a Tivoli Workload Scheduler for z/OSAgent workstation with ISPF . . . . . . . 73Defining a job in the JOBLIB data set . . . . . 74

Notices . . . . . . . . . . . . . . 81Trademarks . . . . . . . . . . . . . . 82

Index . . . . . . . . . . . . . . . 85

© Copyright IBM Corp. 1999, 2014 iii

iv Tivoli Workload Scheduler for z/OS: Getting Started (Revised November 2014)

Figures

1. EQQOPCAP - Main menu . . . . . . . . 52. Setting the subsystem name . . . . . . . 63. Setting the subsystem name for TCP/IP

connection . . . . . . . . . . . . . 64. Setting the date and time format . . . . . . 75. PF Key definitions and labels . . . . . . . 86. Selecting operations . . . . . . . . . . 97. Sorting a list . . . . . . . . . . . . 118. Maintaining the databases . . . . . . . 139. List of workstation descriptions . . . . . . 14

10. General information about a computerworkstation . . . . . . . . . . . . 14

11. Availability of a workstation . . . . . . . 1612. All open time intervals. . . . . . . . . 1613. General information about a job setup

workstation . . . . . . . . . . . . 1714. Modifying calendars . . . . . . . . . 1815. Creating a calendar . . . . . . . . . . 1916. List of special resources . . . . . . . . 2017. Creating a special resource . . . . . . . 2018. Modifying connected workstations for a

special resource . . . . . . . . . . . 2219. Modifying intervals for a special resource 2220. Modifying connected workstations for a

special resource . . . . . . . . . . . 2321. Maintaining application descriptions . . . . 2622. Creating an application . . . . . . . . 2623. Run cycles . . . . . . . . . . . . . 2824. Modifying a rule . . . . . . . . . . . 3025. Operations, text mode . . . . . . . . . 3126. Operations, predecessor mode . . . . . . 3227. Operation details. . . . . . . . . . . 3328. Job, WTO, and print options . . . . . . . 3429. Time specifications . . . . . . . . . . 3430. Predecessors . . . . . . . . . . . . 3531. Creating a job . . . . . . . . . . . . 3632. Selecting long-term plan batch job . . . . . 3733. Creating the long-term plan . . . . . . . 3834. Generating JCL for a batch job . . . . . . 3835. Long-term plan occurrences . . . . . . . 3936. Creating an occurrence . . . . . . . . . 4037. Specifying further occurrence data . . . . . 41

38. Creating a dependency. . . . . . . . . 4139. Modifying dependencies . . . . . . . . 4240. Long-term plan occurrences . . . . . . . 4341. Browsing an occurrence . . . . . . . . 4342. Browsing dependencies . . . . . . . . 4443. Browsing operation data . . . . . . . . 4444. Extending current plan period . . . . . . 4645. Creating a current plan extend job . . . . . 4746. Current plan and status inquiry . . . . . . 4847. Browsing application occurrences (left part) 4848. Selecting application occurrence information 4949. Browsing application occurrence details 5050. Selecting application occurrence and operation

information . . . . . . . . . . . . 5151. Selecting all dependencies. . . . . . . . 5152. All dependencies of an operation . . . . . 5253. Browsing most critical occurrences . . . . . 5254. Communicating with workstations . . . . . 5655. Specifying ready list criteria . . . . . . . 5656. Selecting a ready list layout . . . . . . . 5757. Ready list for job setup workstation . . . . 5858. Editing JCL for an operation . . . . . . . 5959. Modifying the current plan . . . . . . . 6160. Adding applications to the current plan 6261. Selecting applications to add to the current

plan . . . . . . . . . . . . . . . 6262. Adding an application to the current plan 6363. Modifying occurrences in the current plan 6464. Modifying an occurrence in the current plan 6465. Modifying operations in the current plan 6566. Specifying ended in error list criteria . . . . 6667. Handling operations ended in error . . . . 6668. Rerunning an occurrence in the current plan 6769. Rerunning an occurrence in the current plan 6870. Confirm rerun of an occurrence . . . . . . 6871. Defining a fault-tolerant workstation . . . . 7072. Defining a job for end-to-end scheduling with

fault tolerance capabilities. . . . . . . . 7173. Defining job options . . . . . . . . . 7174. EQQWCGEP - Creating general information

about a Tivoli Workload Scheduler for z/OSAgent workstation. . . . . . . . . . . 73

© Copyright IBM Corp. 1999, 2014 v

||

|||

vi Tivoli Workload Scheduler for z/OS: Getting Started (Revised November 2014)

Tables

1. Tasks and row commands on the Ready List 58 2. Jobs and their keywords . . . . . . . . 74

© Copyright IBM Corp. 1999, 2014 vii

viii Tivoli Workload Scheduler for z/OS: Getting Started (Revised November 2014)

About this publication

IBM® Tivoli® Workload Scheduler for z/OS® Getting Started describes how you defineyour installation data for IBM Tivoli Workload Scheduler for z/OS and how youcreate and modify plans.

The term scheduler, when used in this publication, refers to Tivoli WorkloadScheduler for z/OS.

What is new in this publicationExcept for editorial changes, updates to this edition are marked with a vertical barto the left of the change.

For information about the changes in this release of Tivoli Workload Scheduler forz/OS, see IBM Tivoli Workload Automation: Overview.

Who should read this publicationThis publication is intended for new users of Tivoli Workload Scheduler for z/OS.It introduces terms and shows you how to define installation data and createplans. This publication also introduces and describes the basic setup andmonitoring tasks for inexperienced users of Tivoli Workload Scheduler for z/OS.

Your workload can run on various platforms, but you control it from a centralz/OS system that runs Tivoli Workload Scheduler for z/OS controller.

Readers should know how to work with the following topics:v z/OS operating systemv Interactive System Productivity Facility (ISPF)v TSO

PublicationsThe Tivoli Workload Automation product is supported by a set of publications.

For a list of publications in the Tivoli Workload Automation product library, seePublications under Reference in the product documentation.

For a list of terms used in the Tivoli Workload Automation product, see Glossaryunder Reference in the product documentation.

Using LookAt to look up message explanationsLook up explanations for most of the IBM messages you encounter, as well as forsome system abends (an abnormal end of a task) and codes.

LookAt is an online facility that lets you look up explanations for most of the IBMmessages you encounter, as well as for some system abends (an abnormal end of atask) and codes. Using LookAt to find information is faster than a conventionalsearch because in most cases LookAt goes directly to the message explanation.

© Copyright IBM Corp. 1999, 2014 ix

You can use LookAt from the following locations to find IBM messageexplanations for z/OS elements and features, z/VM®, VSE/ESA, and Clusters forAIX® and Linux:v The Internet. You can access IBM message explanations directly from the LookAt

website at http://www.ibm.com/eserver/zseries/zos/bkserv/lookat/.v Your z/OS TSO/E host system. You can install code on your z/OS system to

access IBM message explanations, using LookAt from a TSO/E command line(for example, TSO/E prompt, ISPF, or z/OS UNIX System Services runningOMVS).

v Your Microsoft Windows workstation. You can install code to access IBMmessage explanations on the IBM Online Library z/OS Software Products CollectionKit (SK3T-4270), using LookAt from a Microsoft Windows DOS command line.

v Your wireless handheld device. You can use the LookAt Mobile Edition with ahandheld device that has wireless access and an Internet browser (for example,Internet Explorer for Pocket PCs, Blazer, or Eudora for Palm OS, or Opera forLinux handheld devices). Link to the LookAt Mobile Edition from the LookAtwebsite.

You can obtain code to install LookAt on your host system or Microsoft Windowsworkstation from a disk on your IBM Online Library z/OS Software ProductsCollection Kit (SK3T-4270), or from the LookAt website (click Download, and selectthe platform, release, collection, and location that suit your needs). Moreinformation is available in the LOOKAT.ME files available during the downloadprocess.

AccessibilityAccessibility features help users with a physical disability, such as restrictedmobility or limited vision, to use software products successfully.

With this product, you can use assistive technologies to hear and navigate theinterface. You can also use the keyboard instead of the mouse to operate allfeatures of the graphical user interface.

For full information with respect to the Dynamic Workload Console, see theAccessibility Appendix in the IBM Tivoli Workload Scheduler User’s Guide andReference.

Tivoli technical trainingTivoli provides technical training.

For Tivoli technical training information, refer to the following IBM TivoliEducation website:

http://www.ibm.com/software/tivoli/education

Support informationIBM provides several ways for you to obtain support when you encounter aproblem.

If you have a problem with your IBM software, you want to resolve it quickly. IBMprovides the following ways for you to obtain the support you need:

x Tivoli Workload Scheduler for z/OS: Getting Started (Revised November 2014)

http://www.ibm.com/eserver/zseries/zos/bkserv/lookat/

http://www.ibm.com/software/tivoli/education

v Searching knowledge bases: You can search across a large collection of knownproblems and workarounds, Technotes, and other information.

v Obtaining fixes: You can locate the latest fixes that are already available for yourproduct.

v Contacting IBM Software Support: If you still cannot solve your problem, andyou need to work with someone from IBM, you can use a variety of ways tocontact IBM Software Support.

For more information about these three ways of resolving problems, see theappendix on support information in Tivoli Workload Scheduler: Troubleshooting Guide.

Conventions used in this publicationConventions used in this publication.

The publication uses several typeface conventions for special terms and actions.Technical changes to the text are indicated by a vertical line to the left of thechange. These conventions have the following meanings:

Information type Style convention Example

Commands All capital letters CREATE

References in the text tofields on panels

All capital letters QUANTITY

File and directory names,input you should type inpanel fields

Monospace MYAPPLICATION

First time new termintroduced, publication titles

Italics Application

How to read syntax diagramsSyntax diagrams help to show syntax in a graphical way.

Throughout this publication, syntax is described in diagrams like the one shownhere, which describes the SRSTAT TSO command:

►► SRSTAT ' resource name 'OPCA

SUBSYS ( subsystem name )MSTR

►

►KEEP

AVAIL ( RESET )NOYES

KEEPDEVIATION ( amount )

RESET

►

►KEEP

QUANTITY ( amount )RESET

YESCREATE ( NO )

►

About this publication xi

►0

TRACE ( trace level )

►◄

The symbols have these meanings:

►►─────The statement begins here.

──────►The statement is continued on the next line.

►──────The statement is continued from a previous line.

─────►◄The statement ends here.

Read the syntax diagrams from left to right and from top to bottom, following thepath of the line.

These are the conventions used in the diagrams:v Required items appear on the horizontal line (main path):

►► STATEMENT required item ►◄

v Optional items appear below the main path:

►► STATEMENToptional item

►◄

v An arrow returning to the left above the item indicates an item that you canrepeat. If a separator is required between items, it is shown on the repeat arrow.

►► STATEMENT ▼

,

repeatable item ►◄

v If you can choose from two or more items, they appear vertically in a stack.– If you must choose one of the items, one item of the stack appears on the

main path:

►► STATEMENT required choice 1required choice 2

►◄

– If choosing one of the items is optional, the entire stack appears below themain path:

►► STATEMENToptional choice 1optional choice 2

►◄

– A repeat arrow above a stack indicates that you can make more than onechoice from the stacked items:

xii Tivoli Workload Scheduler for z/OS: Getting Started (Revised November 2014)


,

optional choice 1optional choice 2optional choice 3

►◄


,

required choice 1required choice 2required choice 3

►◄

v Parameters that are above the main line are default parameters:

►► STATEMENTdefault

alternative►◄

v Keywords appear in uppercase (for example, STATEMENT).v Parentheses and commas must be entered as part of the command syntax, as

shown.v For complex commands, the item attributes might not fit on one horizontal line.

If that line cannot be split, the attributes appear at the bottom of the syntaxdiagram:

►► STATEMENT required choice 1option 1 option 2

required choice 2required choice 3

►◄

option 1

defaultoptional choice 1 ( alternative )

option 2

defaultoptional choice 2 ( alternative )

About this publication xiii

xiv Tivoli Workload Scheduler for z/OS: Getting Started (Revised November 2014)

Chapter 1. Introduction

Introduction to Tivoli Workload Scheduler for z/OS

This chapter briefly describes Tivoli Workload Scheduler for z/OS and introducesbasic concepts and terminology. The term scheduler, when used in this publication,refers to Tivoli Workload Scheduler for z/OS.

What is Tivoli Workload Scheduler for z/OS?What is Tivoli Workload Scheduler for z/OS?

The Tivoli Workload Scheduler for z/OS licensed program is Tivoli’s foundationfor enterprise workload management. Tivoli Workload Scheduler for z/OSprovides a comprehensive set of services for managing and automating theworkload. Whether you manage a single-image z/OS system or multi-vendornetworks and systems from a single point of control, Tivoli Workload Scheduler forz/OS helps you manage and automate the production workload. If you are notfamiliar with IBM Tivoli Workload Scheduler for z/OS terminology or functions,read the Overview.

How your production workload is managedHow your production workload is managed

The scheduler builds operating plans from your descriptions of the productionworkload.

The scheduler consists of a base product, the tracker and a number of features. Allthe systems in your complex require the base product. The tracker is the linkbetween the system that it runs on and Tivoli Workload Scheduler for z/OScontroller.

One z/OS system in your complex is designated the controlling system and runsthe controller feature. From this system, you can automatically plan, control, andmonitor your production workload. Only one controller feature is required, evenwhen you want to start standby controllers on other z/OS systems in a sysplex.

The end-to-end scheduling lets you centrally manage the workload on supportedoperating systems from the controlling system, such as UNIX and Windows NT.For a list of the supported operating systems, see the Tivoli Workload SchedulerRelease Notes at http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27041032.

Concepts and terminologyConcepts and terminology

The scheduler uses these important concepts:

Applications

© Copyright IBM Corp. 1999, 2014 1

http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27041032

http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27041032

An application is a description of a unit of production work. It includes a list of theoperations (related tasks) associated with that unit of work. For example, a payrollapplication might include a manual task where an operator prepares a job, severalcomputer-processing tasks where programs are run to read a database, updateemployee records, and write payroll information to an output file, and a print taskthat prints pay checks.

Business processing cycles

The scheduler uses business processing cycles, or periods, to calculate when yourapplications should be run. When you create an application, you specify when itshould be planned using a run cycle. You can use rule-based run cycles to specifyrun days using rules such as “Third Thursday in July,” or “Every work day inweek 40,” where you select the words from a multiple-choice panel.

Calendars

The scheduler uses calendar information so that applications are not scheduled torun on days when processing resources are not available (for example, Sundaysand holidays). This information is stored in a calendar. The scheduler supportsmultiple calendars for enterprises where different departments have different workdays and free days or when multiple data centers in different states or regions arecontrolled from a single site.

Dependencies

Most data processing activities need to occur in a specific order. Activitiesperformed out of order can create invalid output or corrupt your corporate data.This results in costly reruns, missed deadlines, and dissatisfied customers.

In Tivoli Workload Scheduler for z/OS, you can specify dependencies for operationswhen a specific processing order is required.

Plans

The scheduler builds operating plans from your descriptions of the productionworkload. First a long-term plan (LTP) is created, which shows (for typically one ortwo months) the applications that should be run each day, and the dependenciesbetween applications. Then a more detailed current plan is created. The currentplan is used by Tivoli Workload Scheduler for z/OS to submit and controloperations.

You can simulate the effects of changes to your production workload, calendar, andinstallation, by generating trial plans.

Special resources

You can use special resources to represent any type of limited resource, such as tapedrives, communication lines, or a database. A special resource can be used toserialize access to a data set or to limit the number of file transfers on a networklink. The resource does not have to represent a physical object in yourconfiguration, although often it does.

Workstations

2 Tivoli Workload Scheduler for z/OS: Getting Started (Revised November 2014)

The scheduler supports a range of work process types, called workstations, that mapthe processing needs of any task in your production workload. Each workstationsupports one type of activity. This gives you the flexibility to schedule, monitor,and control any data processing activity, including:v Job setup, both manual and automaticv Jobsv Started tasksv NetView® communicationv Print operationsv Manual preprocessing or postprocessing activity.

Setup tasksSetup tasks in Tivoli Workload Scheduler for z/OS

If you are new to Tivoli Workload Scheduler for z/OS and it is your first timethrough this publication, ensure that all the following activities are complete:v You have a TSO user ID that is authorized to access Tivoli Workload Scheduler

for z/OS subsystem.v The scheduler subsystem is started.v You are authorized to update these scheduler databases:

– Workstation– Calendar– Application description– Job description

v You are authorized to use these scheduler functions:– Long-term planning– Daily planning– Workstation communication– Modify current plan– Query current plan

About the examples in this manualAbout the examples in this manual

Some examples show how to create and modify data elements in Tivoli WorkloadScheduler for z/OS databases. Before doing any modify or create tasks, you shouldget authorization from the Tivoli Workload Scheduler for z/OS administrator.

Examples of tasks that result in Tivoli Workload Scheduler for z/OS displaying thesame panel multiple times have been simplified to show the panel only once. Forthose examples with multiple input fields, such as Creating General Informationfor a Workstation (Figure 10 on page 14), you see a completed panel withhighlighted reference numbers next to applicable input fields.

Chapter 1. Introduction 3

Chapter 2. Communicating with the scheduler

Communication with the scheduler

To perform most tasks, you use Tivoli Workload Scheduler for z/OS panels, whichrun under Interactive System Productivity Facility (ISPF).

Like all ISPF applications, Tivoli Workload Scheduler for z/OS displays messagesin the upper-right corner of the panels. Use PF1 (HELP) to see the long messagetext. You can also use PF1 to get more information about input fields if you needhelp in the panels. To cancel a panel function, use the CANCEL command, whichyou can abbreviate to CAN. No data is saved when you enter the CANCELcommand.

You can reach all the controller panels from the main menu:

This chapter describes how to perform the following tasks:v Set options for your panel sessions.v Concatenate options.v Set program function (PF) keys and ISPF options.v Use filter panels to reduce the amount of data displayed in lists.v Use the CANCEL, SORT, and LOCATE commands.

Setting optionsSetting options

The options, and many of the parameters that you enter in the panels, are savedwhen you leave ISPF (unless the session terminates abnormally) and will be thedefault next time.

EQQOPCAP ------------ TIVOLI WORKLOAD SCHEDULER FOR z/OS ---------------------Option ===>

Welcome to Tivoli Workload Scheduler for z/OS V8R5M0 (TWSz)Connected to OPCC

Select one of the following options and press ENTER.

0 OPTIONS - Define TWSz dialog user parameters and options

1 DATABASE - Display or update TWSz data base information2 LTP - Long Term Plan query and update3 DAILY PLANNING - Produce daily plans, real and trial4 WORK STATIONS - Work station communication5 MCP - Modify the Current Plan6 QCP - Query the status of work in progress7 OLD OPERATIONS - Restart old operations from the DB2 repository

9 SERVICE FUNC - Perform TWSz service functions10 OPTIONAL FUNC - Optional functions

X EXIT - Exit from the TWSz dialog

Figure 1. EQQOPCAP - Main menu


The controller subsystem manages the panels, so you must communicate with thecorrect subsystem. This section describes how to set the controller subsystem nameand the date and time format for your panel sessions.

Specifying the subsystem nameSpecifying the subsystem name1. Select 0 on the main menu to display the DEFINING OPC PARAMETERS AND

OPTIONS menu.2. To display the panel in which you set the subsystem name, select option 1 in

the DEFINING OPC PARAMETERS AND OPTIONS menu. You see this panel:

3. Select a subsystem from the list by typing a slash in the S column of the listpanel.If the subsystem you want to connect to is not in the list, you can add newrows or change existing ones. If the subsystem is running on another z/OSsystem:v If it is connected through APPC link, enter the LU name of the server

associated to that controller in the Server LU name column. If the server ison another network, the fully-qualified LU name must be entered in the formNETWORKID.LUNAME.

v If it is connected through TCP/IP link, enter the TCPIP command. Thefollowing panel is displayed:

4. Enter host name and port number of the server associated to that controller inthe Remote host name and Remote port num columns. The Type (T) columnshows the dialog connection type: L=Local A=APPC T=TCP/IP.

EQQXLUSL ---------- TWSz CONTROLLERS AND SERVER LU NAMES -- Row 1 to 4 of 4Command ===>

Scroll ===> CSRChange data in the rows, and/or enter any of the following row commandsI(nn) - Insert, R(nn),RR(nn) - Repeat, D(nn),DD - DeleteEnter the TCPIP command above to include the TCP/IP information tocommunicate with the Server.

Row Con-cmd S troller T Server LU name Description’’’ _ OPCO A IS1MEOPV_________ On other________________’’’ _ OPCO A SEIBM200.IS1MEOPV ________________________’’’ _ OPCX L _________________ OPC on same MVS_________’’’ / TWSA T _________________ On other - TCP/IP link

Figure 2. Setting the subsystem name

EQQXTCPL ------------ TWSz CONTROLLERS AND SERVER LU NAMES ---- Row 1 to 4 of 4Command ===> Scroll ===> CSR

Change data in the rows, and/or enter any of the following row commandsI(nn) - Insert, R(nn),RR(nn) - Repeat, D(nn),DD - DeleteEnter the SNA command above to include the SNA LU information tocommunicate with the Server.

Row Con- Remote Remotecmd S troller T host name Port num’’’ _ OPCO A ____________________________________________________ _____’’’ _ OPCO A ____________________________________________________ _____’’’ _ OPCX L ____________________________________________________ _____’’’ / TWSA T 9.12.134.1__________________________________________ 425__

Figure 3. Setting the subsystem name for TCP/IP connection


5. Press PF4 (RETURN) to save the changes and return to the main menu.

Setting date and time formatsSetting date and time formats

To set the date and time formats, enter 0.2 in the main menu. You see this panel:

In the DATE-FORMAT field, you can combine the characters YY (year), MM (month),and DD (day) in any order. The Julian calendar format of YY (year) and DDD(day) is also supported. Any character except D, M, or Y can be used as adelimiter. YYMMDD is the format used in examples in this publication.

In the TIME-FORMAT field, you combine the characters HH (hour) and MM (minute).The delimiter character, shown as a period (.) in Figure 4, is optional and can beany character. HH.MM is the format used in examples in this publication.

In the DURATION-FORMAT field, you combine the characters HH (hour), MMMM(minute), and SS (second). The delimiter character, shown as a period (.) inFigure 4, is optional and can be any character. MMMM.SS is the format used inexamples in this publication.

The scheduler uses the calendar that you specify for panel functions, such as theLONG TERM PLAN panel and the GENDAYS command for checking run cycles.

You use the LOCAL TIME OFFSET field and the TIME OFFSET SIGN field when you areworking in a different time zone from the controller.

Save the changes and return to the main menu by pressing PF4 (RETURN).

Concatenating options and setting PF keysConcatenating options and setting PF keys

This section describes how to use common panel commands and facilities and howto set program function (PF) keys to move quickly through panels.

EQQXDATP-------------- SETTING TWSz DATE AND TIME FORMAT ----------------------Enter/change data below:DATE-FORMAT ===> YYMMDD__ Combine the characters for

year ( YY or CCYY ), and month ( MM ) andday ( DD ), or day number ( DDD ).You can use separation characters (suchas - or /) if space permits.

TIME-FORMAT ===> HH.MM Combine the characters forhours( HH ) and minutes( MM ).Optionally separated by any character.

DURATION-FORMAT ===> MMMM.SS_ Specify the characters for hours( HH )and minutes( MM ) and seconds( SS )or minutes( MMMM ) and seconds( SS ).Optionally separated by any character.

LOCAL TIME OFFSET ===> 0___ Specify local time offset in minutes.The value must be in the range 0 to 1439.

TIME OFFSET SIGN ===> + Specify - if local time is before TWSz.Specify + if local time is after TWSz.

CALENDAR ID ===> DEFAULT_________ Default calendar identification

Figure 4. Setting the date and time format

Chapter 2. Communicating with the scheduler 7

Concatenating optionsConcatenating options

Using the scheduler you enter concatenated options in the standard ISPF manneron the command line and in row command input fields. For example, you displaythe LIST OF APPLICATIONS panel without going through intermediate panels byentering 1.4.3.0 in the main menu.

You can also use the ISPF command delimiter (;) to concatenate options in thepanels. When you use the ISPF command delimiter, you pass through confirmationpanels without displaying them. This can make completing or deleting a long listof applications or occurrences much faster.

Quick return commandQuick return command

You can use the ISPF quick return command (=) as a fast path through the panels.For example, to return to the ready list from wherever you are in the panels, enter=4.1.0 on the command line.

Setting PF keysSetting PF keys

The panels maintain separate PF keys from your normal ISPF key assignments. Aswith all ISPF applications, the END command (PF3) returns you to the previouslydisplayed panel. The RETURN command (PF4) takes you directly to the mainmenu.

To display or change the key assignments, enter =0.4.3 at the command prompt.The scheduler displays this panel:

ISPOPT3B ------- PF KEY DEFINITIONS AND LABELS - PRIMARY KEYS ------------------COMMAND ===>

NUMBER OF PF KEYS ===> 24 TERMINAL TYPE ===> 3278

PF13 ===> ;=4.1.operPF14 ===> ;=4.1.cpu1PF15 ===> ;=5.4.0PF16 ===> ;=5.1PF17 ===> ;=5.2PF18 ===> ;=6.1PF19 ===> ;=6.3PF20 ===> ;=3.1PF21 ===> ;=3.2PF22 ===> ;=2.1PF23 ===> ;=2.2PF24 ===> ;=1.4.1

PF13 LABEL ===> rl_oper PF14 LABEL ===> rl_cpu1 PF15 LABEL ===> errorsPF16 LABEL ===> mcp_add PF17 LABEL ===> mcp_mod PF18 LABEL ===> qcp_applPF19 LABEL ===> qcp_job PF20 LABEL ===> dpreplan PF21 LABEL ===> dpextendPF22 LABEL ===> ltp_look PF23 LABEL ===> ltpbatch PF24 LABEL ===> ad_look

Press ENTER key to display alternate keys. Enter END command to exit.

F13=rl_oper F14=rl_cpu1 F15=errors F16=mcp_add F17=mcp_mod F18=qcp_applF19=qcp_oper F20=dpreplan F21=dpextend F22=ltp_look F23=ltpbatch F24=ad_look

Figure 5. PF Key definitions and labels


In this example, PF keys 13 to 24 are set, and a label is assigned to each PF key. Alabel is used for display in place of the corresponding PF key assignment whenyou issue the PFSHOW command. Assigning labels to PF key definitions isoptional.

The PF key settings in this example are valid for all panels except those panelswhere you override these settings. To override or change PF key settings for asingle panel, enter the KEYS command. The scheduler displays the panel shown inFigure 5 on page 8. Any PF key changes you make affect only the panel fromwhich you issued the KEYS command.

Note: Do not alter the key assignments for PF1 (HELP) or PF12 (RETRIEVE). PF12(RETRIEVE) returns the command last executed to the command prompt. A stackof approximately 25 commands is maintained.

Using filter panelsHow to use filter panels

Throughout the panels, options are provided to let you list data elements. Thissection describes how to use selection criteria to filter and limit the amount of datadisplayed in lists.

You use selection criteria to specify the contents of lists in the panels. Figure 6describes an example of a selection criteria panel. You can display this panel byentering 5.3 in the main menu.

On this and other selection criteria panels, you can use blanks, complete names,IDs, or generic search arguments in the input fields.

To reduce overhead during searches, use the fast-path option when it is availableon selection criteria panels (see ▌1▐ Figure 6).

EQQSOPFP ------------------- SELECTING OPERATIONS ---------------------------Command ===>

Specify selection criteria below and press ENTER to create an operation list.

JOBNAME => P*______ WORK STATION NAME => ____APPLICATION ID => ________________ OWNER ID => ________________AUTHORITY GROUP => ________ PRIORITY => _GROUP DEFINITION => ________________ STATUS => __________CLEAN UP TYPE => ________________ CLEAN UP RESULT => __OP.EXTENDED NAME =>_______________________________________________OP. SE NAME => ________________Input arrival in format YY/MM/DD HH.MMFROM => ________ _____TO => ________ _____Additional Options:FAST PATH => Y ▌1▐ Valid only along with jobnameSet Y, N, or leave blank to select all:MANUALLY HELD => _ WAITING FOR SE => _ STARTED ON WAIT WS => _CRITICAL PATH => _ COND RECOVERY JOB => _ RECOVERED BY COND => _UNEXPECTED RC => _ UNDEFINED COND => _ SHADOW JOB => _STARTED AT STARTUP => NSet P, M, B, E, or leave blank to select all:WAITING PEND.PRED. ==> _

Figure 6. Selecting operations


||||||||||||||||||||||||||||

Using generic search argumentsUsing generic search arguments

Many input fields in the panels accept generic search arguments. You specify ageneric search argument by entering either an asterisk (*) or a percent sign (%) inan input field. You can enter these characters by themselves or in combination withother characters.

Use an asterisk (*) to represent any character string or a null string. The percentsign (%) represents any single character.

If you want to select all applications whose first three letters are PAY, enter thesecharacters in the input field:

APPLICATION ID ===> PAY*________

If you want to select all applications where P is the first letter and Y is the thirdletter, you enter:

APPLICATION ID ===> P%Y*_________

The percent sign in this example results in a search for application identifierswhere there is any single character between P and Y.

Some selection panels contain the following field:TYPE OF MATCH ===>

Use this field to specify the type of match that should be applied for filters,allowing wild characters (* and %) to be treated as normal characters. If the field isleft blank, then standard generic matching is done.

Using the HELP commandUsing the HELP command

To get help for any panel, press the PF1 (HELP) key. In help panels, scroll forwardby pressing Enter. If you keep pressing Enter, you eventually get the first screen ofhelp again; it wraps round.

Using the SORT and LOCATE commandsHow to use the SORT and LOCATE commands

This section shows how to use the SORT and LOCATE commands to manipulatelists of data displayed by Tivoli Workload Scheduler for z/OS.

Sorting list outputSorting list output

In all list displays, you can enter the SORT command at the command prompt todisplay a panel where you can specify the order of the list items. The panel forsorting a list of applications is shown in Figure 7 on page 11.


There are different sort options for different types of lists. The sort order yourequest remains in effect for that specific list type until changed.

These steps show how to set sort options for lists. The example uses options for alist of applications.1. In the Sort order column, specify a number to tell Tivoli Workload Scheduler

for z/OS the order of precedence for the field you select.In this example, Application ID is the primary sort field.

2. In the Direction column of the same field, specify A or a D to set the sortsequence.In this example, Application ID is to be sorted in ascending order.

3. Press Enter to confirm your selections. The scheduler moves the selected fieldsto the top of the list.

4. You return to the list items panel by pressing PF3 (END).

The scheduler displays the list items in the new sequence.

Note: If you sort a list on date fields, use a date format that has the year first. Forinformation on specifying the date format, see “Setting date and time formats” onpage 7.

Locating data strings in list outputHow to locate data strings in list output

You can enter LOCATE (or LOC) at the command prompt on any list display panelto find a particular data string in the primary sort field. The command alsosupports generic search strings. For example, if you enter LOC ABC* to find anyitem in the list beginning with ABC, the list scrolls to the specified field. If the fieldis not found, the list is displayed starting with the entry before which the specifiedfield would have occurred.

If application name is the primary sort field, request LOCATE applname; similarly,if jobname is the primary sort field, request LOCATE jobname. If you need to issue

EQQXSRTL ---------------------- SORTING A LIST ----------- ROW 1 TO 14 OF 17Command ===> Scroll ===> PAGE

Enter/change data in rowsor enter DELETE in the command field to delete the active sort:Sort order = 1-9, where 1 is the first sort field.Direction = A for ascending (default) or D for descending.

Sort Directionorder Asc/Desc Title of field Description of field

1 A Application Application ID2 D Type Application type3 A Status Application status_ _ Application text Verbal description of the application_ _ Calendar Calendar name_ _ Group def Group definition_ _ Group id Authorization group ID_ _ Owner Application owner ID_ _ Owner text Verbal description of application owner_ _ Priority Application priority_ _ Tot oper Total number of operations_ _ Tot run Total number of run cycles_ _ Upd-Date Date in user format of last update_ _ Upd-Time Time in user format of last update

Figure 7. Sorting a list


a LOCATE command against a list of items that is not sorted by the item you wantto locate, you can change the sort order by entering the SORT command.


Chapter 3. Describing your environment

How to describe your data processing environment to Tivoli Workload Schedulerfor z/OS

This chapter describes how to describe your data processing environment to TivoliWorkload Scheduler for z/OS by performing the following tasks:v Creating workstationsv Creating a calendarv Creating special resources

To access your environment data that is stored in the scheduler databases, chooseOption 1 on the main menu. The following panel is displayed:

Creating workstationsCreating workstations

Each operation controlled by Tivoli Workload Scheduler for z/OS, whether a job,started task, or other activity, must be associated with a workstation. Theworkstation defines where in your installation the activity is performed. There arethree workstation types:v Computer workstationsv Printer workstationsv General workstations

Of these, the most commonly used are computer and general workstations.Computer workstations are used for batch job and started task operations. Youshould define at least one job computer workstation and one started taskworkstation, even though these may be the same physical processor.

General workstations let you control operations that are normally not automatic,such as manual job preparation.

Creating a workstationHow to create a workstation

Complete the following steps to create a workstation:

EQQODBSP ----- MAINTAINING TWSz DATA BASES --------------Option ===>

Select one of the following:

1 WS - Work station descriptions2 CALENDAR - Calendar descriptions3 PERIOD - Period descriptions4 AD - Application descriptions5 OI - Operator instructions6 SPECRES - Special resource descriptions7 ETT - Event triggered tracking criteria8 JD - Job descriptions9 JCLVAR - JCL variable tables

Figure 8. Maintaining the databases


1. Access the workstation panel by selecting option 1 (WS) on the MAINTAININGTWSz DATABASES menu. The scheduler displays the MAINTAININGWORKSTATION DESCRIPTION menu.

2. Select option 2 (LIST) to display the SPECIFYING WORK STATION LISTCRITERIA panel.

3. Enter your search criteria to see the workstations that you want to list. You seethis panel:

4. To create a workstation, either copy and modify an existing workstationdescription or use the CREATE command. In both cases, Tivoli WorkloadScheduler for z/OS displays the panel you see in Figure 10.

5. Specify the workstation details on the panel.

Figure 10 shows these values for a computer workstation:

WORK STATION NAMECPUA ▌1▐ The name of the workstation.

EQQWMLSL ------------- LIST OF WORKSTATION DESCRIPTIONS ---- ROW 1 TO 5 Of 5Command ===> SCROLL ===> PAGE

Enter the CREATE command above to create a workstation description or enterany of the following row commands:B - Browse, D - Delete, M - Modify, C - Copy.

Row Work station T R Last updatecmd name description user date’ CPU1 Main JES processor C A XRAYNER 940128’ PRT1 Printer pool C A XRAYNER 940128’ SETP Used to prepare JCL G A XRAYNER 940128’ STC1 Processor for started tasks C N XRAYNER 940128’ WTO1 Messages for NetView G N XRAYNER 940128******************************* BOTTOM OF DATA **************************

Figure 9. List of workstation descriptions

EQQWCGEP ----- CREATING GENERAL INFORMATION ABOUT A WORK STATION --------Command ===>

Enter the command R for resources, A for availability, or O for end-to-endoptions, D for Destinations above, or enter data below:

WORK STATION NAME ===> CPUA ▌1▐DESCRIPTION ===> System A-local processor________ ▌2▐WORK STATION TYPE ===> C ▌3▐ G General, C Computer, P Printer

R Remote EngineREPORTING ATTR ===> A ▌4▐ A Automatic, S Manual start and completion

C Completion only, N Non reportingPRINTOUT ROUTING ===> SYSPRINT The ddname of daily plan printout data setSERVER USAGE ===> B ▌5▐ Parallel server usage C, P, B or NDESTINATION ===> _________ Name of destinationOptions: allowed Y or NSPLITTABLE ===> N JOB SETUP ===> NSTARTED TASK, STC ===> N WTO ===> NAUTOMATION ===> N FAULT-TOLERANT AGENT ===> NWAIT ===> N Z-CENTRIC AGENT ===> NVIRTUAL ===> N DYNAMIC ===> N

REMOTE ENGINE TYPE ===> Z z/OS or D DistributedDefaults:TRANSPORT TIME ===> 00.00 Time from previous work station HH.MMDURATION ===> 0015.00 ▌6▐ Duration for a normal operation HH.MM.SS

Figure 10. General information about a computer workstation


DESCRIPTIONThe text in ▌2▐ is a brief description of the workstation.

WORK STATION TYPEC ▌3▐ describes the workstation as a computer workstation.

REPORTING ATTR (attribute)Every operation in the current plan is assigned a status, which describes itscurrent condition. When all processing for an operation is finished, theoperation is assigned status C (complete). Before it completes, the operationwill have many different statuses as it progresses through the system. Thesequence of statuses that an operation is assigned and the mechanism usedfor reporting status updates depends on the reporting attribute ▌4▐ of theworkstation. In this example, A means that the status of operations at thisworkstation is automatically updated as the operation progresses throughthe system.

SERVER USAGEThis is a resource that limits the number of operations that can run at thesame time. For workstations representing z/OS systems, a parallel server isusually a JES initiator. B (Both planning and control) in the SERVER USAGEfield ▌5▐ tells Tivoli Workload Scheduler for z/OS to:v Consider the number of servers when creating plansv Submit jobs in the current plan, only up to the limit of the number of

servers defined to the workstation.

This means that Tivoli Workload Scheduler for z/OS takes the number ofparallel servers into account when it develops plans for this workstationand submits work to be processed at this workstation. For example, ifTivoli Workload Scheduler for z/OS has 10 jobs to start and there are only5 servers available, Tivoli Workload Scheduler for z/OS starts 5 jobs first,then starts each of the remaining 5 as servers become available.

DURATION00.15.00 (15 minutes) ▌6▐ is the default estimated processing time foroperations on this workstation. When creating a current plan, TivoliWorkload Scheduler for z/OS uses the estimated duration to work out atimetable for the operations. It is not necessary to give an accurate figurefor duration because Tivoli Workload Scheduler for z/OS can adjust thisfigure automatically, using actual durations. Putting a value in this fieldcan save you time when creating operations that run at this workstation(see “Creating operations” on page 30). The minimum value of the plannedduration is 1 second, and the maximum value is 99 hours 59 minutes 00seconds. If you specify 99 hours 59 minutes 01 second, you do not receivean alert message if actual duration is greater than the planned duration.

DESTINATIONWhen this field is blank, as shown in Figure 10 on page 14, jobs andstarted tasks are submitted on the system where the controller subsystemis started. Trackers can connect to the controller using a variety ofcommunication methods. The destination can be an XCF member name, aVTAM® logical unit, the ddname of a shared data set, a name associated toa TCP/IP address, or an APPC partner logical unit.

REMOTE ENGINE TYPESpecify Z for z/OS remote engine, D for distributed remote engine.

Specifying workstation availabilitySpecifying workstation availability

Chapter 3. Describing your environment 15

The scheduler can schedule work on the workstation only when it is available(open for processing work). When you specify workstation availability, create openintervals for each day of the week and specify the number of servers andworkstation resources that are available during the open intervals. You can alsospecify an alternate workstation that Tivoli Workload Scheduler for z/OS useswhen the normal workstation is not available.

Complete the following steps to specify availability for a computer workstation:1. On the Creating General Information about a WORK STATION panel, type A on

the command line and press Enter. You see this panel:

Figure 11 shows one open interval definition, STANDARD, that is used for alldays of the week. The example on this panel is the default for any workstationyou create.

2. To display or modify the availability of this workstation, enter the ALLcommand. You see this panel:

On this panel, you specify when the workstation is open for processing, thenumber of parallel servers that are available during the intervals specified,resources, and alternate workstations to assume the workload if this

EQQWMAVL -------------- AVAILABILITY OF A WORK STATION ------ ROW 1 TO 8 OF 8Command ===> Scroll ===> PAGE

Work station : CPUA System A-local processor

Enter the ALL command above to get all open time intervals orchange data in the rows, and/or enter any of the following row commands:I(nn) - Insert, R(nn),RR(nn) - Repeat, D(nn),DD - DeleteC - Close a day/date, S - Define open intervals for a day/date

Row Day of week or Status Description of daycmd YYMMDD’’ STANDARD______ DEFINED ________________________’’ MONDAY________ STANDARD ________________________’’ TUESDAY_______ STANDARD ________________________’’ WEDNESDAY_____ STANDARD ________________________’’ THURSDAY______ STANDARD ________________________’’ FRIDAY________ STANDARD ________________________’’ SATURDAY______ STANDARD ________________________’’ SUNDAY________ STANDARD ________________________******************************* BOTTOM OF DATA **************************

Figure 11. Availability of a workstation

EQQWMATL ------------------ ALL OPEN TIME INTERVALS -------------- ROW 1 OF 7Command ===> Scroll ===> PAGE

Work station : CPUA System A-local processor

Change data in the rows, and/or enter any of the following row commands:I(nn) - Insert, R(nn),RR(nn) - Repeat, D(nn),DD - Delete

Row Day of week or Open time interval Parallel Resources Alt.cmd YYMMDD HH.MM - HH.MM servers R1 R2 WS’’ STANDARD______ 00.00 06.00▌1▐ 25 99 99 ____’’ STANDARD______ 06.00 22.00 10 99 99 ____’’ STANDARD______ 22.00 24.00 99 99 99 ____▌2▐******************************* BOTTOM OF DATA ********************************

Figure 12. All open time intervals


workstation fails or goes offline. The defaults for the open time interval,number of parallel servers, and resources are shown in the standard interval▌2▐.The example in Figure 12 on page 16 uses the default number of resources andno alternate workstation. As shown, you can specify multiple open timeintervals and vary the number of servers for each interval. The number ofparallel servers assigned to Tivoli Workload Scheduler for z/OS for the openinterval between midnight and 6 a.m. is 25 ▌1▐. The number of serversassigned to the 6 a.m. to midnight interval is 10.

Note: If you leave a gap in the intervals that you create for a workstation, theworkstation is closed for that time.

3. Save the workstation description by pressing PF3 (END) until you see themessage WS CREATED or pressing PF4 (RETURN) to return to the main menu.

Creating a general job setup workstationHow to create a general job setup workstation

This section shows how to create a new workstation description by copying anexisting one.

A job setup workstation lets you manually prepare the input stream for anoperation. Follow these steps to create a job setup workstation:1. Display the list of workstations by entering =1.1.2 on the command line.2. On the LIST OF WORKSTATION DESCRIPTIONS panel, type C next to one of

the workstations in the list, and press Enter. The scheduler displays generalinformation for the workstation you are copying.

3. Type the workstation name ▌1▐ and update the description ▌2▐.4. Type G ▌3▐ in the WORK STATION TYPE field.5. Change the reporting attribute ▌4▐ because at a manual job setup workstation,

you control the start and end of the operation. The S tells Tivoli Workload

EQQWCGEP ----- CREATING GENERAL INFORMATION ABOUT A WORK STATION --------Command ===>Enter the command R for resources or A for availability or O for end-to-endoptions, or D for Destinations above, or enter data below:

WORK STATION NAME ===> JCL1 ▌1▐DESCRIPTION ===> Job setup workstation___________ ▌2▐WORK STATION TYPE ===> G ▌3▐ G General, C Computer, P Printer

R Remote EngineREPORTING ATTR ===> S ▌4▐ A Automatic, S Manual start and completion

C Completion only, N Non reportingPRINTOUT ROUTING ===> SYSPRINT The ddname of daily plan printout data setSERVER USAGE ===> N ▌5▐ Parallel server usage C, P, B or NDESTINATION ===> _______ Name of destinationOptions: allowed Y or NSPLITTABLE ===> Y ▌6▐ JOB SETUP ===> Y ▌7▐STARTED TASK, STC ===> N WTO ===> NAUTOMATION ===> N FAULT-TOLERANT AGENT ===> NWAIT ===> N Z-CENTRIC AGENT ===> NVIRTUAL ===> N DYNAMIC ===> N

REMOTE ENGINE TYPE ===> Z z/OS or D DistributedDefaults:

TRANSPORT TIME ===> 00.00 Time from previous work station HH.MMDURATION ===> 00.05.00 ▌8▐ Duration for a normal operation HH.MM.SS

Figure 13. General information about a job setup workstation


Scheduler for z/OS that the status change of operations at this workstation isnormally reported manually by an operator from the READY LIST panel. Thescheduler lets you manually prepare JCL at a workstation with this attribute.

6. Server usage ▌5▐ is changed to N (neither planning nor control) to allowunlimited concurrent operations.

7. Specify Y in the SPLITTABLE field ▌6▐. Splittable means that you can interrupt thepreparation of an input stream by entering the TSAVE (temporary save)command. The scheduler sets the operation status to I (Interrupted). Anychanges made to the job are saved but the job is not submitted. You cancontinue job preparation later.

8. Because this workstation is for job setup, change the JOB SETUP field ▌7▐ to Y.The default for all workstations is N.

9. Change the duration ▌8▐ to the average job preparation time. In this example, itis 5 minutes.

Creating calendarsHow to create calendars

The scheduler uses calendars, periods, and run cycles to automatically includeapplications in the long-term plan on the dates that you specify.

A calendar specifies the status of each day and the work day end time. The statusof each day is set to either W, work day or F, free day. A work day is a normalbusiness day. Free days are non-business days, such as weekends and publicholidays. You can create several calendars, but name your primary calendarDEFAULT.

Complete the following steps to create or modify a calendar:1. Select option 1.2.2 on the main menu. You see this panel:

2. Type C next to an existing calendar, or type the CREATE command, and pressEnter. The scheduler displays this panel:

EQQTCAML -------------------- MODIFYING CALENDARS ----------- ROW 1 TO 1 OF 1Command ===> Scroll ===> PAGE

Enter the CREATE command above to create a new calendar orenter any of the following row commands:B - Browse, C - Copy, D - Delete, M - Modify,or G to display a calendar graphically

Row Calendar Description Last updatecmd id user date time’ COUNTRYX Different holidays calendar JOHNB 940130 11.10******************************* BOTTOM OF DATA ********************************

Figure 14. Modifying calendars


Figure 15 shows a calendar with 5 days of the week specified as work days, 2days of the week specified as free days, and 2 holidays specified as free days.

3. Specify the new calendar name in the CALENDAR ID field.4. Specify the default, 00.00, in the WORK DAY END TIME field.5. Specify the week days as work or free days. In the status column, W identifies

work days, and F identifies free days.6. Enter or change the dates of any holidays observed by your production

department. The status that you assign to a date overrides the status for thecorresponding day of the week. Identify each date with a comment.

Creating special resourcesHow to create special resources

You can use special resources to represent any resource in your environment. Forexample, you can create special resources to represent your tape drives or adatabase.

Complete the following steps to create a special resource called TAPES:1. Select option 1.6 from the main menu. You see the MAINTAINING SPECIAL

RESOURCES menu.2. Select option 3 (LIST) from the menu to display the SPECIFYING SPECIAL

RESOURCE LIST CRITERIA panel.3. From this panel, you can display a list of the resources that already exist in

the database. To do this, type * in the SPECIAL RESOURCE and SPECRES GROUPID fields, leave the TYPE OF MATCH field blank, and press Enter. You see thispanel:

EQQTCCAL -------------------- CREATING A CALENDAR ----------&hyphen ROW 1 TO 9 OF 9Command ===> Scroll ===> CSR

Enter/change data below and in the rows,and/or enter any of the following row commands:I(nn) - Insert, R(nn),RR(nn) - Repeat, D(nn),DD - Delete

CALENDAR ID ===> DEFAULT_________DESCRIPTION ===> OPC default calendar__________WORK DAY END TIME ===> 00.00

Row Weekday or Comments Statuscmd date YYMMDD’’ MONDAY________ ______________________________ W’’ TUESDAY_______ ______________________________ W’’ WEDNESDAY_____ ______________________________ W’’ THURSDAY______ ______________________________ W’’ FRIDAY________ ______________________________ W’’ SATURDAY______ ______________________________ F’’ SUNDAY________ ______________________________ F’’ 940126________ Australia Day_________________ F’’ 940204________ Chinese New Year______________ F

Figure 15. Creating a calendar


4. Enter the CREATE command. The scheduler displays this panel:

5. Use these fields to create a resource:

SPECIAL RESOURCEThe name of the resource (up to 44 characters) is translated touppercase. You can include national characters in the name, but donot use % and * because Tivoli Workload Scheduler for z/OS usesthese for filtering and searching in the panels.

TEXT A description of the resource, up to 54 characters.

SPECRES GROUP IDThe resource group up to 8 characters. The group ID is for selectingsubsets of resources in the panel (a list filter).

HIPERBATCHWhether the resource represents a data lookaside facility (DLF) object.Type N.

USED FORWhether the resource is used for:P Planning, when the current plan is builtC Control, when Tivoli Workload Scheduler for z/OS starts an

operation

EQQQDLSL ----------------- LIST OF SPECIAL RESOURCES -------- ROW 1 TO 4 OF 4Command ===> create Scroll ===> PAGE

Enter the CREATE command above to create a new resource, or,enter any of the row commands below:B - Browse, M - Modify, C - Copy, D - Delete

Row Special Specres A Qty Numcmd Resource group ID Ivl’’ HEIDE.ISPF.PROFILE Y 1 1’’ HEIDE.OPCESA.EQQDUMP Y 1 1’’ PAYROLL.DATABASE Y 1 1’’ RITZMAN.DSCLOSE.TEST Y 1 1******************************* BOTTOM OF DATA *******************************

Figure 16. List of special resources

EQQQDCRP ---------------- CREATING A SPECIAL RESOURCE -------------------Option ===>


1 INTERVALS - Specify intervals2 WS - Modify default connected work stations

SPECIAL RESOURCE ===> tapes_______________________________________TEXT ===> tape drives______________________________________SPECRES GROUP ID ===> sample__Hiperbatch ===> N DLF object Y or NUSED FOR ===> B Planning and control C , P , B or NON ERROR ===> f_ On error action F , FS , FX , K or blankON COMPLETE ===> _ On complete action Y , N , R , or blankMAX USAGE LIMIT ===> 3 Max number of allocations before usage resetMAX USAGE TYPE ===> N Status change type Y, N or R

DefaultsQUANTITY ===> 8_____ Number available 1-999999AVAILABLE ===> Y Available Y or N

Figure 17. Creating a special resource


B Both planning and controlN Neither

ON ERRORWhat happens if an operation that allocates this resource ends in error(and does not have an overriding keep-on-error specification in theoperation definition).

You may want critical jobs to keep their allocated resources evenwhen they fail (for example, so that there is no delay waiting forresources when they are restarted).

F Free any resource allocated

FS Free its full shared allocation of this resource

FX Free its full exclusive allocation of this resource

K Keep its full allocation of this resource

Blank Use the installation default

ON COMPLETEThe value to which the global availability is reset after the operationthat uses the resource completes. It can be one of the following:

Y Sets the global availability to Yes.

N Sets the global availability to No.

R Sets the global availability to blank.

Blank Uses the system default, according to the following order:a. The On Complete value set at operation definition level, if

not blank.b. The On Complete value set at special resource definition

level, if not blank.c. The ONCOMPLETE or DYNONCOMPLETE keyword

value, respectively set for the not dynamically addedresources or the dynamically added resources, in all theother cases.

MAX USAGE LIMITThe number of allocations of this resource after which the resourceglobal availability is changed to the value specified by Max UsageType.

MAX USAGE TYPEThe value to which the global availability of the resource is reset,when its maximum usage limit is reached:

Y Sets the global availability to Yes.

N Sets the global availability to No.

R Sets the global availability to blank.The two fields, QUANTITY and AVAILABLE, are default values. They apply tointervals where quantity or availability is not specified, and apply also to timeranges where there is no interval specified. You can save time by specifyingthe normal quantity and availability here and specifying only the exceptions inintervals.

QUANTITY1 to 999 999.


AVAILABLEAvailable (Y) or unavailable (N). If a resource is not available, anoperation that needs the resource cannot be started.

6. To specify the default-connected workstations, select option 2 (WS) on theCREATING A SPECIAL RESOURCE panel. You see this panel:

7. An asterisk (*) in the Ws column ▌1▐ means that the resource is connected bydefault to all workstations. If you want to restrict the resource to specificworkstations, specify them as shown in Figure 18.

8. Save the connected workstations by pressing PF3 (END).9. To create availability intervals, select option 1 (INTERVALS) from the

CREATING A SPECIAL RESOURCE panel. You see this panel:

10. Specify values for each interval where you do not want the default values:

Day of week or DateSpecify a day of the week, a specific date, or STANDARD (days ordates not specified).

From Time, To TimeSpecify a time range.

Qty The quantity in the time interval specified. The default quantity andavailability are those specified in the QUANTITY field.

A Available (Y) or unavailable (N).

EQQQDWML - MODIFYING CONNECTED WORK STATIONS FOR A SPECIAL RE ROW 1 TO 2 OF 2Command ===> Scroll ===> PAGE

Enter/Change data in the rows, and/or enter any of the followingrow commands:I(nn) - Insert, R(nn),RR(nn) - Repeat, D(nn),DD - Delete

Special resource : TAPESText : tape drives on CPU1 and STC1Interval : Default

Row Ws ▌1▐cmd’’ CPU1’’ STC1******************************* BOTTOM OF DATA *******************************

Figure 18. Modifying connected workstations for a special resource

EQQQDIML -------- MODIFYING INTERVALS FOR A SPECIAL RESOURCE ROW 1 TO 3 OF 3Command ===> Scroll ===> PAGE

Enter any of the row commands below:I(nn) - Insert, R(nn),RR(nn) - Repeat, D(nn),DD - Delete, or,S - Work stations

Special resource : TAPESText : tape drives on CPU1 and STC1

Row Day of From To Qty Acmd week or Date Time Time’’ STANDARD______ 08.00 22.00 6_____ _’’ SATURDAY______ 00.00 24.00 ______ _’’ SUNDAY________ 08.00 10.00 ______ N******************************* BOTTOM OF DATA *******************************

Figure 19. Modifying intervals for a special resource


11. If you want to modify the connected workstation for a certain interval, selectthe interval by typing the S row command. For example, to specify that onlyoperations on the CPU1 workstation can use the TAPES resource on Saturday,type S beside the SATURDAY interval row. You see this panel:

12. Specify the workstation that can use the resource in the Ws column. For thisexample, type CPU1.

13. Press PF3 (END) to return to the MODIFYING INTERVALS FOR A SPECIALRESOURCE panel. When you have specified all the intervals, press PF3 (END)to return to the CREATING A SPECIAL RESOURCE panel.

EQQQDWML - MODIFYING CONNECTED WORK STATIONS FOR A SPECIAL RE ROW 1 TO 1 OF 1Command ===> Scroll ===> PAGE

Enter/Change data in the rows, and/or enter any of the followingrow commands:I(nn) - Insert, R(nn),RR(nn) - Repeat, D(nn),DD - Delete

Special resource : TAPESText : tape drives on CPU1 and STC1Interval : SATURDAY 00.00 24.00

Row Wscmd’’ CPU1******************************* BOTTOM OF DATA *******************************

Figure 20. Modifying connected workstations for a special resource


Chapter 4. Creating applications

How to create and schedule applications and job descriptions

This chapter describes how to create and schedule applications and jobdescriptions.

An application in Tivoli Workload Scheduler for z/OS is a set of related jobs ortasks. The result of these may be an output listing, a set of invoices, consolidations,or updates which in turn are used by other applications. An application can rangefrom a single operation with no dependencies to a maximum of 99 operations atcomputer, general, and printer workstations. These operations can have complexlinks within the application and also to other applications. Most applications arerun regularly with the required frequency specified when the applications arecreated.

You can group applications that run together to form an application group. With anapplication group, you specify the run cycles in the group definition and not inindividual applications. By doing this, you avoid having to specify the samecalendar and run-policy information for each application. The use of applicationgroups can save you time in the initial specification of your work to TivoliWorkload Scheduler for z/OS and in ongoing maintenance to the applications. Youcan also use groups in the MODIFY CURRENT PLAN panel to add, delete, andcomplete all or part of an application group in the current plan.

A standard application can have up to three parts:

General informationSpecifying the application name and other general information thatdescribes the application.

Run cyclesSpecifying when the application is to run. This is optional.

OperationsSpecifying the work to be done.

When creating an application, you must specify general information andoperations.

Applications are kept in a database. In the main menu, display the applicationdatabase menu by typing 1.4 on the command line and pressing Enter. You seethis panel:


Use option 2 (CREATE) on this panel to create applications and application groups.Job descriptions are created from a different panel. Creating job descriptions isdescribed in “Creating a job description” on page 35.

Creating an applicationHow to create and schedule an application

This section shows you how to create and schedule an application. It covers thefollowing tasks:v Specifying general informationv Creating a rule-based run cyclev Creating operations

Specifying general informationSpecifying general information

When creating an application, you must specify general information before you cancreate the operations or run cycles.1. Enter 1.4.2 on the main menu. You see this panel:

Figure 22 shows general information for a standard application.

EQQASUBP ----------- MAINTAINING APPLICATION DESCRIPTIONS ---------------------Option ===>


1 BROWSE - Browse applications2 CREATE - Create an application3 LIST - List applications for further processing

(browse, modify, copy, delete, print,calculate and print run days, modify LTP)

4 PRINT - Perform printing of applications5 MASS UPDATE - Perform mass updating of applications

Figure 21. Maintaining application descriptions

EQQACGPP ------------------ CREATING AN APPLICATION ---------------------------Command ===>

Enter/Change data below:Enter the RUN command above to select run cycles or enter the OPER commandto select operations.

Application:ID ===> MYAPPLICATION___ ▌1▐TEXT ===> A sample application____▌2▐ Descriptive textTYPE ===> A ▌3▐ A - Application, G - Group definitionOwner:ID ===> SAMPLE_________ ▌4▐TEXT ===> Pay Office______________ ▌5▐

Descriptive text of application ownerPRIORITY ===> 5 ▌6▐ A digit 1 to 9 , 1=low, 8=high, 9=urgentVALID FROM ===> 940501__ ▌7▐Date in the format YY/MM/DDSTATUS ===> A ▌8▐ A - Active, P - PendingAUTHORITY GROUP ID ===> ________ Authorization group IDCALENDAR ID ===> ____________▌9▐For calculation of work and free daysGROUP DEFINITION ===> ________________ Group definition id▌10▐SMOOTHING FACTOR ===> ____ LIMIT ===> ____ Deadline Feedback options▌11▐

Figure 22. Creating an application


2. Specify the Application ID ▌1▐. This can be a name from 1 to 16 characters.The first character must be either an alphabetic or national character. All othercharacters must be alphanumeric. This is a required input field.

3. Enter up to 24 characters of descriptive text in the Application TEXT field ▌2▐.4. The same panel is used to create application groups. In the TYPE field ▌3▐, you

must specify whether this is an application or application group definition.5. In the Owner ID field ▌4▐, type the name of the owner of the application. It can

be a department name, such as PAYROLL. This field can be used to controlaccess to the application. It is a required input field.

6. In the Owner TEXT field ▌5▐, you can enter up to 24 characters of descriptivetext.

7. Type a value from 1 (low) to 9 (high) in the PRIORITY field ▌6▐. This is arequired input field for applications, but is blank for application groups.

8. VALID FROM ▌7▐ is the date from which your application is eligible to beincluded in the long-term and current plans. The default is the applicationcreation date. This field allows you to create several versions of the sameapplication with different valid-from dates. The scheduler picks the correctversion for the day it is planning. For example, on July 25 1994, you are askedto change the sequence of operations in an application that is run daily, and tomake the change effective from August 1 1994. To do this:a. Copy the application.b. Change the valid-from date of the copy to 940801.c. Make the requested changes.d. Change the in-effect and out-of-effect dates on the run cycles of the copied

and the original application. See “Creating a rule-based run cycle.”e. Update the long-term plan.

The scheduler will automatically use the new version from August 1.9. Type A in the STATUS field ▌8▐ if you want to include your application in the

long-term and current plans. Setting the status of an application to P(Pending) is a simple way to prevent Tivoli Workload Scheduler for z/OSfrom scheduling an application that you want to keep out of the plantemporarily. The scheduler disregards Pending applications when it is creatingplans. This is a required input field.

10. When calculating the run dates for an application, Tivoli Workload Schedulerfor z/OS uses the calendar that you specify in the CALENDAR ID field ▌9▐. Ifyou do not specify a calendar, Tivoli Workload Scheduler for z/OS uses thedefault calendar.

11. If the application is part of a group, specify the group name in the GROUPDEFINITION field ▌10▐.

12. Optionally, you can specify a deadline smoothing factor (from 0 to 999) andlimit for feedback (from 100 to 999) in the deadline feedback options field▌11▐.

13. After filling in the general information, verify your entries by pressing Enter.

Creating a rule-based run cycleCreating a rule-based run cycle

For an application to be automatically included in the long-term plan (LTP), itmust contain at least one run cycle specified either in the application itself or in a

Chapter 4. Creating applications 27

group definition. The run cycle must also be in effect for the duration of thelong-term plan (that is, the in-effect date of the run cycle must be within the rangeof time covered by the long-term plan).

When creating a rule-based run cycle you:1. Specify general information on the RUN CYCLES panel.2. Specify the run policy on the MODIFYING A RULE panel.

The example in this section shows how to use rules to create a run cycle forscheduling an application to run on the second Thursday of every month.1. Display the RUN CYCLES panel by entering RUN on the CREATING AN

APPLICATION panel. You see this panel:

2. In the Name of period/rule column, specify a name for the rule. In theexample, it is RULE01.

3. In the Input HH.MM column, specify the application input arrival time on theday it is scheduled to run. In the example, the input arrival time is 21.00.Each instance of an application in the long-term or current plan is called anoccurrence. Input arrival time forms part of the key that uniquely identifies eachoccurrence of the application in the plans; it is not the time that TivoliWorkload Scheduler for z/OS starts the application, unless the first operation istime-dependent (creating a time-dependent operation is described in“Specifying operation details” on page 33).When the daily planning process is selecting occurrences from the long-termplan, it selects only those occurrences with input arrival times that fall withinthe planning period.

4. In the Deadline day and Deadline HH.MM columns, specify the deadline day andtime for completion of the last operation in the application. In this example thedeadline day is 1, and the deadline time is 06.00. This means that relative tothe input arrival date for the occurrence, all operations in the application mustbe completed by 6 a.m. on the first work day after the occurrence is added tothe current plan.

5. Press Enter, and Tivoli Workload Scheduler for z/OS supplies the fields in theTYPE, F day rule, and In effect and Out of effect columns with defaultvalues. Figure 23 shows the default values.The fields can contain these values:

TYPE There are two types of rule-based run cycles:

EQQAMRPL ------------------------ RUN CYCLES --------------------- ROW 1 OF 1Command ===> Scroll ===> PAGE

Enter/Change data in the rows, and/or enter any of the followingrow commands:I(nn) - Insert, R(nn),RR(nn) - Repeat, D(nn),DD - DeleteS - Specify run days/Modify rule

Application : MYAPPLICATION___ A sample applicationName of In Out of

Row period/rule Input Deadline F day effect Effectcmd Text HH.MM day HH.MM Type rule YY

MMDD YYMMDD Variable table

s’’ RULE01__ 21.00 01 06.00 R 4 940129 991231 _____________

▌1▐Run ONLY on the second Thursday of every month.

Figure 23. Run cycles


R Regular rule, which specifies when to run the application.

E Exclusion rule, which specifies when not to run the application.Use this rule to suppress runs that are generated by regular runcycles. For example, if the regular rule specifies “EveryThursday in the Year,” you may want a rule that excludes the“Last Thursday in April.”

F day ruleFree-day rules provide the flexibility to schedule your applicationsprecisely when they are required. You use free-day rules to tell TivoliWorkload Scheduler for z/OS what to do if an application run datefalls on a free day. There are five free-day rule options:

E Count only work days, and exclude free days. If the rule is“Every tenth day in the month,” for example, Tivoli WorkloadScheduler for z/OS generates every tenth work day, whereasthe other options consider every tenth calendar day and thendecide what to do if it is free.

1 Reschedule the application on the closest work day before thefree day.

2 Reschedule the application on the closest work day after thefree day.

3 Schedule the application on the free day.

4 Do not schedule the application at all. This is the default forrule-based run cycles.

In effect, Out of effectThe in-effect and out-of-effect dates specify the period of time whenTivoli Workload Scheduler for z/OS uses this run cycle.

6. It is a good practice to document each run cycle with explanatory text. Thescheduler provides the space to do this on the line below the other fields (▌1▐in Figure 23 on page 28).

After filling in the fields, you specify the dates for the run cycle.

Specifying the run datesHow to specify the dates for the run cycle

The following steps show how to specify the dates for the run cycle:1. In the RUN CYCLES panel, enter the S row command next to the run cycle you

want. You see the MODIFYING A RULE panel:


2. Select or specify values for each of these columns:v Frequencyv Dayv Cycle Specifications

The panel shows the selections for scheduling this application on the secondThursday of each month.

3. Enter the E row command to specify the EVERY options for the run cycle. TheEVERY options define an interval of time, always starting from the IA time,within which an application is scheduled with a specified frequency. Forexample, you can set that an application is scheduled every 1 hour and 30minutes from the specified IA time 9:00 to the REPEAT END TIME 15.00. Fordetails about the EVERY options, refer to Managing the Workload.

4. Check your definition by displaying the dates that the rule generates. To dothis, enter the GENDAYS command on the command line, and return to theMODIFYING A RULE panel by pressing PF3 (END).

5. Press PF3 (END) to return to the RUN CYCLES panel.6. Press PF3 (END) once more to return to the CREATING AN APPLICATION

panel.

Now you create operations for the application.

Creating operationsHow to create operations

The operation that will be performed determines the type of workstation that youshould create. The following list provides some guidelines:v Batch jobs run on computer workstations.v Operations on distributed agents run on Tivoli Workload Scheduler for z/OS

Agents, dynamic domain managers, and fault-tolerant agents.v Started-tasks run on computer workstations that have the STC attribute.v Job setup operations for jobs and started tasks are created on general

workstations that have the SETUP attribute.

EQQRULEP -------------------- MODIFYING A RULE -----------------------------Command ===>

Enter the GENDAYS command to display the dates generated by this ruleEnter the E command to specify EVERY optionsEnter S and user data in the fields below to define a rule

Application : MYAPPLICATION ___Rule : RULE01

--- Frequency --- --- Day --- --- Cycle Specification -------------------------------------------------------------------------

S Only | _ Day | _ Week _ January _ July_ Every | _ Free day | S Month _ February _ August

| _ Work day | _ Year _ March _ September_ First _ Last | _ Monday | _ April _ OctoberS Second _ 2nd Last | _ Tuesday | _ May _ November_ Third _ 3rd Last | _ Wednesday | _ June _ December_ Fourth _ 4th Last | S Thursday | Week number __ __ __ __ __ ___ Fifth _ 5th Last | _ Friday | Period name ________ ________

___ ___ ___ ___ | _ Saturday | ________ ___________ ___ ___ ___ | _ Sunday |___ ___ ___ ___ | | Shift default origin by ___ days

Figure 24. Modifying a rule


v Print operations are created on printer workstations.v Write-to-operator (WTO) operations are created on a general workstation that

has the WTO attribute.v Dummy operations, which are used to simplify dependencies, are created on

non-reporting general workstations.v Other tasks that you want to be represented by operations are usually created on

general workstations.

Creating operations for an application includes these tasks:v Specifying values on the OPERATIONS panelv Specifying operation predecessorsv Specifying operation details

The following sections explain how to perform each task.

Specifying values on the operations panelHow to specify the values on the operation panel

In the CREATING AN APPLICATION panel, enter the OPER command to displayeither the OPERATIONS panel in which you enter operations with predecessors(Figure 26 on page 32) or the OPERATIONS panel in which you enter operationswith text (Figure 25). To switch between these two panels, enter TEXT to displaythe OPERATIONS panel for specifying text and PRED to display the OPERATIONSpanel for specifying predecessors.

Specify values for the fields on the OPERATIONS panel. Figure 25 shows valuesthat describe each operation in this example application.

Oper wsFor each operation, specify the name of the workstation where the taskwill be performed. In the example, the first operation is at a workstationcalled NONR.

Oper noEach operation number must be unique because these numbers specifyrequired links between operations in the application. The number of thefirst operation in the example is 001.

EQQAMOPL ------------------------ OPERATIONS ---------------- ROW 1 TO 4Command ===> Scroll ===>

Enter/Change data in the rows, and/or enter any of the followingrow commands:I(nn) - Insert, R(nn),RR(nn) - Repeat, D(nn),DD - DeleteS - Select operation details, J - Edit JCLEnter the PRED command above to include predecessors in this list, or,enter the GRAPH command to view the list graphically.

Application : MYAPPLICATION A sample application

Row Oper Duration Job name Operation textcmd ws no. HH.MM.SS’’ NONR 001 00.01.00 ________ Time dependent__________’’ CPUA 005 00.15.00 TESTJOB1 Depends on pred 001_____’’ CPUA 010 00.15.00 TESTJOB2 Depends on pred 001_____’’ WTO1 015 00.01.00 ________ Please setup TESTJOB3___’’ JCL1 020 00.05.00 TESTJOB3 Setup oper. for TESTJOB3’’ CPUA 025 00.15.00 TESTJOB3 Depends on preds 020,010******************************* BOTTOM OF DATA **************************

Figure 25. Operations, text mode


DurationSpecify either the estimated duration for each operation or leave blank touse the default specified in the workstation definition. The minimum valueof the planned duration is 1 second, and the maximum value is 99 hours59 minutes 00 seconds. If you specify 99 hours 59 minutes 01 second, youdo not receive an alert message if the actual duration is greater than theplanned duration.

Job nameSpecify the name of the job the operation represents. The scheduler usesthis name to find JCL for the job or started task.

Because operation 001 is at a non-reporting workstation, it does not need ajob name. However, for each job setup (JCL1 in this example), computer(CPUA in this example), and printer workstation operation, you must specifya job name. The job name for a setup or print operation must be the sameas the associated computer operation.

Operation 015 is a WTO operation. No job name is required for operationsat WTO or non-reporting workstations.

Operation textThe operation text forms part of a WTO message EQQW775I that is issuedon the system console.

Specifying operation predecessorsSpecifying operation predecessors

In applications with multiple operations, each operation must be linked to at leastone other operation within the application. If there are any unlinked operations,Tivoli Workload Scheduler for z/OS displays the error message APPLICATIONINCONSISTENT when you try to save the application.

Display the OPERATIONS panel for specifying dependencies by entering the PREDcommand on the OPERATIONS, text mode panel. The scheduler displays the panelin Figure 26.

You specify the links between operations to describe the flow of work to TivoliWorkload Scheduler for z/OS. In the application defined in Figure 26, operation 10

EQQAMOSL ------------------------ OPERATIONS ---------------- ROW 1 TO 3 OF 3Command ===> Scroll ===> PAGE

Enter/Change data in the rows, and/or enter any of the followingrow commands:I(nn) - Insert, R(nn),RR(nn) - Repeat, D(nn),DD - DeleteS - Select operation details, J - Edit JCLEnter the TEXT command above to include operation text in this list, or,enter the GRAPH command to view the list graphically.

Application : MYAPPLICATION A sample application

Row Oper Duration Job name Internal predecessors More predscmd ws no. HH.MM.SS -Int-Ext-’’ NONR 001 00.01.00 ________ ___ ___ ___ ___ ___ ___ ___ ___ 0 0’’ CPUA 005 00.05.00 TESTJOB1 1__ ___ ___ ___ ___ ___ ___ ___ 0 0’’ CPUA 010 00.01.00 TESTJOB2 1__ ___ ___ ___ ___ ___ ___ ___ 0 0’’ WTO1 015 00.01.00 ________ ___ ___ ___ ___ ___ ___ ___ ___ 0 0’’ JCL1 020 00.03.00 TESTJOB3 15_ ___ ___ ___ ___ ___ ___ ___ 0 0’’ CPUA 025 00.05.00 TESTJOB3 10_ 20_ ___ ___ ___ ___ ___ ___ 0 0******************************* BOTTOM OF DATA ******************************

Figure 26. Operations, predecessor mode


at workstation CPUA must be completed before operation 25 at the sameworkstation can be started. In addition, operation 20 at workstation JCL1 must becompleted before operation 25 can be started. Therefore, operation 25 in thisexample has two internal prerequisite operations or internal predecessors; internal,because the linked operations are all in the same application. This relationshipbetween operations is called a dependency.

You can specify up to eight internal predecessors on the panel in Figure 26 on page32. You can specify more predecessors on the OPERATION DETAILS panel.

The operations in Figure 26 on page 32 have the following dependencies:v Operation 1 has no predecessor.v Operations 5 and 10 both have operation 1 as their predecessor.v Operation 15 has no predecessor.v Operation 20 has operation 15 as a predecessor.v Operation 25 has two predecessors, operations 10 and 20. Operation 25 is

dependent on 20 because a job setup operation must be an immediatepredecessor of the related computer workstation operation. Also, both operationsmust have the same job name.

Specifying operation detailsSpecifying operation details

For each operation in an application, you can specify external predecessors,additional internal predecessors, and additional requirements such as timedependency. To do this, select the operation in the OPERATIONS panel by typing Snext to the operation and pressing Enter. You see this panel:

The steps in this example show how to use operation details to make an operationtime dependent, and also dependent on another application, ANOTHERAPPL.1. To make an operation time dependent, select option 4 (AUTOMATIC

OPTIONS). You see this panel:

EQQAMSDP --------------------- OPERATION DETAILS ------------------------------


1 PREDECESSORS - List of predecessors2 WS RES AND SERVERS - Work station resources and servers3 SPECIAL RESOURCES - List of special resources4 AUTOMATIC OPTIONS - Job, WTO, and print options5 FEEDBACK - Feedback options6 TIME - Time specifications7 OP INSTRUCTIONS - Operator instructions8 JCL EDIT - Edit JCL9 CLEANUP OPTIONS - Cleanup Options

10 EXTENDED INFO - Operation Extended Info11 AUTOMATION INFO - System Automation operation info12 USER FIELDS - User Fields operation info13 REMOTE JOB INFO - Remote job information

Application : MYAPPLICATION A sample applicationOperation : NONR 001Duration : 0001.00 Jobname :Number of int preds : 0 Number of ext preds : 0Number of conditions : 0Option ===>

Figure 27. Operation details


2. To tell Tivoli Workload Scheduler for z/OS to start this operation at or after aspecific time, change the value for TIME DEPENDENT to Y ▌1▐.

3. Save the change by pressing PF3 (END).4. Now select option 6 (TIME) on the OPERATION DETAILS menu. You see the

panel in Figure 29.

5. Specify the start day (Operation input arrival DAY) and time (Operationinput arrival TIME) for the operation.The fields DAY ▌2▐ and TIME ▌3▐ show the time specifications for this example.If no input arrival day or time is specified, Tivoli Workload Scheduler for z/OSuses the input arrival time on the Application time specifications ▌1▐(specified on the run cycle).

6. Save the job options and return by pressing PF3 (END).

EQQAMJBP ---------------- JOB, WTO, AND PRINT OPTIONS -------------------------Command ===>

Enter/Change data below:Application : MYAPPLICATION A sample applicationOperation : NONR 001JOB CLASS ===> _ Job class of corresponding jobERROR TRACKING ===> Y Y means error automatically trackedHIGHEST RETURNCODE ===> ____ Highest return code not in errorEXTERNAL MONITOR ===> N Job monitored by external product (Y/N)CENTRALIZED SCRIPT ===> N Centralized script Y/N (for FTW only)CRITICAL ===> N Critical job: N P WPOLICY ===> C CLASS ===> WLMCLASS WLM policy and serivce classJob release options: Answer Y or N for options below:SUBMIT ===> Y Automatically submittedHOLD/RELEASE ===> Y Automatically held and releasedTIME DEPENDENT ===> Y Run the job at specified time ▌1▐SUPPRESS IF LATE ===> N Suppress the job if not on timeDEADLINE WTO ===> N Deadline WTO, Y or N

WS fail options:RESTARTABLE ===> _ Operation is restartableREROUTEABLE ===> _ Operation is eligible for reroute

Print options:FORM NUMBER ===> ________ SYSOUT CLASS ===> _

Figure 28. Job, WTO, and print options

EQQAMTMP -------------------- TIME SPECIFICATIONS -----------------------------Command ===>

Enter/Change data below:

Application time specifications:Input arrival time : 21.00 ▌1▐Deadline day/time : 01 06.00

Operation : NONR 001

Operation input arrival:DAY ===> 00 ▌2▐ The day the input arrives for operation,

relative to application start day(0 means the start day).

TIME ===> 21.30 ▌3▐ Arrival time of the inputin the format HH.MM

Operation deadline:DAY ===> __ Deadline day for operation completion,

relative to application start day(0 means the start day).

TIME ===> _____ Deadline time of deadline dayin the format HH.MM

Figure 29. Time specifications


7. To make the application dependent on another one, select option 1(PREDECESSORS). You see this panel:

8. If you do not remember the full details of the external application, you can usethe asterisk (*) and percent (%) characters, as shown. The scheduler searchesthe database for operations that match and gives you a list to select from.

9. After all operation details are specified, save the application and return to themain menu by pressing PF4 (RETURN). You see the message APPLICATIONCREATED in the upper-right corner of the panel.

Creating a job descriptionHow to create a job description

A job description is an application consisting of a single job, started task, or WTOmain operation, and an internal predecessor job preparation, a manual preparationoperation, or both. The name of the job description is automatically set to the samename as the main operation.

If your application satisfies these restrictions, you can use the JOB DESCRIPTIONpanel, which compresses most of the function of the APPLICATIONDESCRIPTION panel into one panel by making some assumptions about theapplication you are creating.

You display the CREATING A JOB panel by entering 1.8.2 in the main menu. Thepanel is displayed with the settings from the previous job description that youcreated or modified.

The panel shown in Figure 31 on page 36 shows settings for an example jobdescription.

EQQAMPDL ----------------------- PREDECESSORS --------------- ROW 1 TO 3 OF 3Command ===> Scroll ===> PAGE

Enter the COND command to view the list of conditions, enter/changedata in the rows, and/or enter any of the following row commands:

I(nn) - Insert, R(nn),RR(nn) - Repeat, D(nn),DD - DeleteS - Description of external dependency

Application : APP0 test variable substOperation : CPU1 010 JOB0 textforjob0

Row Oper Transport time Application id Jobnamecmd ws no. HH.MM (for ext pred only)’’ cpu* 000 _____ another*________ *_______******************************* BOTTOM OF DATA **************************

Figure 30. Predecessors


You must specify values for these fields:v JOBNAMEv OWNER IDv WORK STATIONv VALID FROMv DURATIONv PRIORITY

From this panel, you have the option to specify more operation details andadditional run cycles. You must use the RUN command to add rule-based runcycles.

EQQJCGPP ---------------------- CREATING A JOB --------------------------Command ===>

Edit data below:Enter the RUN command above to select run cycles or enter the DETAILScommand to specify job details.

JOBNAME - TEXT ===> TESTJOB1 - ________________________OWNER: ID - TEXT ===> SAMPLE__________ - ________________________CALENDAR ID ===> ________________ AUTHORITY GROUP ID ===> ____VALID FROM - to ===> 940501 - 991231 DURATION ===> 0015.00RUN TIME FROM - TO ===> _____ - _____ TIME DEPENDENT ===> NWORK STATION ===> CPUA PRIORITY ===> 5JCL PREPARATION ===> N JCL WS ===> ____ HIGHEST RETURN CODE ===> 0000MANUAL INTERACTION ===> ________________________ MANUAL WS ===> ____RUN CYCLES ===> ________ - ____ ________ - ____ ________ - __

________ - ____ ________ - ____ ________ - __PREDECESSORS ===> ________ ________ ________ ________ ________SPECIAL ===> ____________________________________________ ______ _RESOURCES ===> ____________________________________________ ______ _

===> ____________________________________________ ______ _GROUP DEFINITION ===> ________________SMOOTHING FACTOR ===> ___ LIMIT ===> ___ Deadline Feedback Options

Figure 31. Creating a job


Chapter 5. Creating and using the long-term plan

How to Create and use the long-term plan

After you have described your installation to Tivoli Workload Scheduler for z/OSin the databases, you must build two plans to control your production workload.They are the long-term and current plans.

The long-term plan (LTP) contains a high-level description of work scheduled forthe coming weeks or months. The long-term plan typically spans 1 to 2 months.You create the long-term plan once, before a current plan has been created. Afterthe first creation, the long-term plan is continually extended. You cannot create along-term plan if a current plan already exists. If a current plan exists, you extendthe long-term plan.

You build the long-term plan using batch jobs in Tivoli Workload Scheduler forz/OS that use data from the application description database, the calendar andperiod definitions, and the old long-term plan, if one exists.

This chapter includes the following long-term-plan topics:v “Creating a long-term plan”v “Adding an occurrence to the long-term plan” on page 39v “Using the long-term plan modify batch function” on page 42v “Browsing occurrences in the long-term plan” on page 43

Creating a long-term planHow to create a long-term plan

The long-term plan batch jobs are usually submitted from the SELECTING LONGTERM PLAN BATCH JOB panel. The scheduler uses ISPF file-tailoring to generateJCL for these batch jobs. Skeleton JCL for these batch jobs is stored in a data setthat must be allocated to ddname ISPSLIB in your TSO logon procedure. If theskeleton JCL data set is not allocated, you see the message NO JCL AVAILABLE whenyou try to submit a batch job.

The steps in this section describe how to create a long-term plan using the panel.1. On the main menu, type 2.2 and press Enter to display the long-term plan

batch-job menu:

EQQLBATP ------------- SELECTING LONG TERM PLAN BATCH JOB --------------Option ===>


1 MODIFY - Modify the long-term plan for all applications2 MODIFY ONE - Modify the long-term plan for one application3 EXTEND - Extend the long-term plan4 TRIAL - Make a trial long-term plan5 PRINT - Print the long-term plan for all applications6 PRINT ONE - Print the long-term plan for one application7 CREATE - Create a new long-term plan

Figure 32. Selecting long-term plan batch job


2. Select option 7 (CREATE) to create a new plan. If a long-term plan or currentplan already exists for your subsystem, select option 3 (EXTEND). The panelsfor extending are similar to the ones for creating. However, when you extend,you do not specify a start date; specify just an end date, or the number of daysto extend the plan.

On this panel, you specify the duration of the long-term plan you are creating.3. Type a start date and end date, and press Enter. The scheduler displays this

panel:

On this panel, you supply data for Tivoli Workload Scheduler for z/OS toprepare the long-term plan create batch job.

4. If you want to send the report that Tivoli Workload Scheduler for z/OSgenerates from the long-term planning process to SYSOUT, specify a class ▌1▐.

5. If you want to send the report to a local printer, specify the local printer name▌2▐.If you do not specify a class or LOCAL PRINTER NAME, Tivoli Workload Schedulerfor z/OS creates a data set with your TSO user ID as the first qualifier of thedata set name ▌3▐.

6. To submit the batch job from this panel, type S in the SUBMIT/EDIT JOB field▌4▐.You can edit and save the generated JCL by placing E in the SUBMIT/EDIT JOBfield.

EQQLCREP ---------------- CREATING THE LONG TERM PLAN ------------------Command ===>


Long term plan:

START ===> 030513__ Date in format YYMMDD

END ===> 030518__ Date in format YYMMDD

Figure 33. Creating the long-term plan

EQQXSUBP -------------- GENERATING JCL FOR A BATCH JOB ------------------------Command ===>

Enter/change data below and press ENTER to submit/edit the JCL.

JCL to be generated for: CREATE A NEW LONG TERM PLAN

SYSOUT CLASS ===> _ ▌1▐ (Used only if output to system printer)LOCAL PRINTER NAME ===> ________ ▌2▐(Used only if output on local printer)

(Used only if CLASS is blank)DATASET NAME ===> JOHNB.OPIC.LTCRE.LIST ▌3▐____________________

(Used only if CLASS and LOCAL PRINTERare both blank). If blank default nameused is JOHNB.OPIC.LTCRE.LIST

SUBMIT/EDIT JOB ===> S ▌4▐ S to submit JOB, E to edit

Job statement :===>▌5▐//OPCDPCR JOB (ACCTCDE),’LTP CREATE’,___________________________________===>▌6▐// CLASS=A,MSGCLASS=Q,MSGLEVEL=(1,1),NOTIFY=JOHNB______________________===>▌7▐________________________________________________________________________===>▌8▐________________________________________________________________________

Figure 34. Generating JCL for a batch job


7. If this is the first time that you are using the batch job functions with yourcurrent TSO user ID, Job statement lines ▌5▐, ▌6▐, ▌7▐, and ▌8▐ are blank. Onthe Job statement lines, type valid job card information.

8. After filling in the applicable fields, press Enter. If you selected the SUBMIToption, Tivoli Workload Scheduler for z/OS submits the job, then redisplays thepanel from which you started your long-term plan create action. If you selectedthe EDIT option, you see the JCL. Use the TSO SUBMIT command to submitthe job.

The scheduler saves the information you supply for items ▌1▐, ▌2▐,▌4▐, ▌5▐, ▌6▐,▌7▐, and ▌8▐. The next time you invoke a batch function, it retrieves theinformation.

Adding an occurrence to the long-term planHow to add an occurrence to the long-term plan

The scheduler lets you manually add and remove occurrences and externaldependencies in the long-term plan. In this section, the examples show how to addan occurrence and modify a dependency in the long-term plan. An occurrence ofMYAPPLICATION is added, and an existing occurrence of TESTJOB1 is made anexternal predecessor to the new occurrence.

To make the steps easier to follow, the names of intermediate panels are mentionedbut the panels are not shown.1. On the main menu, type 2.1 (LTP.ONLINE) and press Enter to display the

SPECIFYING LTP OCCURRENCE LIST CRITERIA panel.2. On the criteria panel, press Enter to display this panel:

3. You can add extra occurrences to the long-term plan by entering the CREATEcommand to display this panel:

EQQLSTOL ---------------- LONG TERM PLAN OCCURRENCES ------ ROW 1 TO 6 OF 6Command ===> Scroll ====> PAGE

Enter the CREATE command above to create a new occurrence orenter the GRAPH command above to view occurrences graphically, or,enter any of the commands below:B - Browse, D - Delete, J - Job setup, M - Modify, RG - Remove from Group

Row Application id Owner id Input arrival Deadline P C Pre Succmd date time date time’’ TESTJOB1 SAMPLE 03/05/13 08.00 03/05/13 08.30 5 N 0 0’’ TESTJOB1 SAMPLE 03/05/14 08.00 03/05/14 08.30 5 N 0 0’’ TESTJOB1 SAMPLE 03/05/15 08.00 03/05/15 08.30 5 N 0 0’’ TESTJOB1 SAMPLE 03/05/16 08.00 03/05/16 08.30 5 N 0 0’’ TESTJOB1 SAMPLE 03/05/26 08.00 03/05/26 08.30 5 N 0 0******************************* BOTTOM OF DATA ********************************

Figure 35. Long-term plan occurrences

Chapter 5. Creating and using the long-term plan 39

4. Now you specify the new occurrence. In this example, these fields arespecified:

APPLICATION ID ▌1▐The name of the application you are adding.

Input arrival DATE, TIME ▌2▐The input arrival date and time for the new occurrence. In thisexample, a new occurrence of MYAPPLICATION is added as asuccessor to an existing occurrence (TESTJOB1 03/0513 08.30); so theinput arrival date and time of the new occurrence must be on or afterthe input arrival date and time of its predecessor.

Deadline DATE, TIME ▌3▐The deadline date and time for the new occurrence.

MORE DETAIL ▌4▐Because a dependency is being created for the new occurrence, theMORE DETAIL field has Y.

5. After specifying more detail, press Enter to display this panel:

EQQLADDP ------------------- CREATING AN OCCURRENCE --------------------------Command ===>

Enter/Change data below and press ENTER to create an occurrence.

APPLICATION ID ===> MYAPPLICATION ▌1▐

Input arrival:DATE ===> 030513__▌2▐ Date in format YYMMDDTIME ===> 11.00 Time in format HH.MM

Deadline:DATE ===> 030514__▌3▐ Date in format YYMMDDTIME ===> 06.00 Time in format HH.MM

PRIORITY ===> 5 1-9 where 1=low, 8=high and 9=urgentERROR CODE ===> ____ Comment on daily plan reportVARIABLE TABLE ===> ________________ JCL variable table idGROUP DEFINITION ===> ________________ Group definition id

MORE DETAIL ===> Y▌4▐ Enter Y to specify further data beforecreating this occurrence.

Figure 36. Creating an occurrence


6. Select option 2 (DEPENDENCIES) to display the MODIFYING DEPENDENCIESpanel, where Tivoli Workload Scheduler for z/OS displays any existingexternal dependencies.

7. On the MODIFYING DEPENDENCIES panel, enter the CREATE command todisplay this panel:

In this example, the application TESTJOB1 is made a predecessor toMYAPPLICATION.

8. To create a dependency, specify these fields on the panel:

DEPENDENCY TYPEType P or S to specify the type of dependency.

APPLICATION IDType the name of the predecessor application (or use * if you do notremember the exact name), and press Enter. You see a list ofoccurrences for the application on the SELECTING ANOCCURRENCE TO CREATE A DEPENDENCY panel. Select a

EQQLSELP ------------- SPECIFYING FURTHER OCCURRENCE DATA ---------------------Option ===>


1 OPERATIONS - Modify operation data2 DEPENDENCIES - Modify dependencies3 OCCURRENCE - Modify general data4 JOB SETUP - Edit JCL5 BROWSE - Browse the occurrence

Application : MYAPPLICATION A test applicationInput arrival : 030513 11.00Deadline : 030514 06.00Owner : SAMPLE Pay OfficePriority : 5Error code :

Variable table :Successors : 0Predecessors : 0

Figure 37. Specifying further occurrence data

EQQLCADP ------------------- CREATING A DEPENDENCY ----------------------------Command ===>


Application : MYAPPLICATION A test applicationInput arrival : 030513 11.00

DEPENDENCY TYPE ===> P P - PredecessorS - Successor

If more than one occurrence meet the following criteriadata will be selected from the long term plan.

APPLICATION ID ===> TESTJOB*________Input arrival:DATE ===> ________ Date in format YYMMDDTIME ===> _____ Time in format HH.MM

Figure 38. Creating a dependency


predecessor occurrence from the list. The scheduler redisplays theMODIFYING DEPENDENCIES panel with the dependencyinformation that you specified.

Input arrival date, timeIf the input arrival date and time of the predecessor application areknown, you can skip a step by filling in the date and time fields onthis panel.

9. After filling in the fields on the CREATING A DEPENDENCY panel, pressEnter. The scheduler redisplays this panel:

Although this panel shows that the new predecessor was manually created▌1▐, the modification is not yet saved. If the predecessor occurrence displayedis not the one you want, you can enter the CANCEL command to exit fromthis panel.

10. You save the newly added predecessor by pressing PF3 (END). The schedulerredisplays the LONG TERM PLAN OCCURRENCES panel with the messageCREATED in the upper-right corner of the panel.

Using the long-term plan modify batch functionUsing the long-term plan modify batch function

After the long-term plan is created, you use either the long-term plan modify one orthe long-term plan modify all function to update the long-term plan. The long-termplan modify all automatically resolves external dependencies but the long-termplan modify one does not.

In the previous section, an external predecessor dependency was manually createdfor an occurrence. To make the relationship between the two occurrences complete,the predecessor must have a matching successor dependency link. In this section,the long-term plan modify all option is used to create a successor dependency.

To update the long-term plan and resolve external dependencies:1. Enter 2.2.1 from the main menu to display the GENERATING JCL FOR A

BATCH JOB panel.On this panel, you see that Tivoli Workload Scheduler for z/OS retained the jobstatement information that you typed when you created the long-term plan.You also see a different output data set name. The third qualifier in the data setname has been changed to reflect the long-term plan modify all function.

EQQLCDPL ------------------- MODIFYING DEPENDENCIES ---------------------------Command ===>

Enter the CREATE command above to create a new dependency orenter any of the commands below:B - Browse, D - Delete

Application : MYAPPLICATION A test applicationInput arrival : 030513 11.00Deadline : 030514 06.00

Row Dep Application id Input arrival Complete Manually Deletedcmd Type date time Created’ P TESTJOB1 030513 08.00 N Y ▌1▐ N******************************* BOTTOM OF DATA ********************************

Figure 39. Modifying dependencies


2. Type S in the SUBMIT/EDIT JOB field, and press Enter to submit the batch job.The scheduler redisplays the main menu.

Browsing occurrences in the long-term planBrowsing occurrences in the long-term plan

You use the option 2.1 (LTP.ONLINE) to browse occurrences in the long-term plan.1. On the main menu, type 2.1 and press Enter to display the SPECIFYING LTP

OCCURRENCE LIST CRITERIA panel.2. Enter your search criteria to see the occurrences that you want to list. You see

this panel:

This panel shows the occurrences. In the Suc (external successor) column ofTESTJOB1, you see the number 1. This means that this occurrence has oneexternal successor. The long-term plan modify all batch function updated thisoccurrence.

3. To browse an occurrence, type B (BROWSE) next to the occurrence, and pressEnter. You see this panel:

EQQLSTOL ---------------- LONG TERM PLAN OCCURRENCES ------ ROW 1 TO 6 OF 6Command ===> Scroll ==

Enter the CREATE command above to create a new occurrence orenter the GRAPH command above to view occurrences graphically, or,enter any of the commands below:B - Browse, D - Delete, J - Job setup, M - Modify, RG - Remove from Group

Row Application id Owner id Input arrival Deadline P C Pre Succmd date time date time’’ TESTJOB1 SAMPLE 03/05/13 08.00 03/05/13 08.30 5 N 0 1’’ MYAPPLICATION SAMPLE 03/05/13 11.00 03/05/14 06.00 5 N 1 0******************************* BOTTOM OF DATA ********************************

Figure 40. Long-term plan occurrences

EQQLBOCP ------------------- BROWSING AN OCCURRENCE ---------------------------Option ===>


1 OPERATIONS - Browse operations2 APPLICATION DEP - Browse dependencies (application level)3 OPERATION DEP - Browse dependencies (operation level)

Application : MYAPPLICATION A test applicationInput arrival : 030513 11.00Deadline : 030514 06.00Owner : SAMPLE Pay OfficePriority : 5Error code :

Variable table :Successors : 0Predecessors : 1Manually created : YesGroup Definition :

Figure 41. Browsing an occurrence


4. You can display external dependencies for the occurrence by selecting option 2(APPLICATION DEP) on this menu. You see this panel:

In Figure 42, you see that MYAPPLICATION has an external predecessor that wascreated manually.

5. To browse the operations in an occurrence, select option 1 on the BROWSINGAN OCCURRENCE menu. You see this panel:

In the example in Figure 43, you see that although the input arrival time for theoccurrence is 11.00, Tivoli Workload Scheduler for z/OS will not start operation001 until 21.30 because the operation is time-dependent.

The input arrival time of 11.00 for operation 015 is taken from the input arrivaltime of the application.

EQQLBBDL ------------------- BROWSING DEPENDENCIES ---------- ROW 1 TO 1 OF 1Command ===> Scroll ===> PAGE

View data below:

Application : MYAPPLICATION A test applicationInput arrival : 030513 11.00Deadline : 030514 06.00

Dep Application id Input arrival Complete Manually DeletedType date time createdP TESTJOB1 030513 08.00 N Y N******************************* BOTTOM OF DATA ********************************

Figure 42. Browsing dependencies

EQQLBOPL ------------------ BROWSING OPERATION DATA --------- ROW 1 TO 6 OF 6Command ===> Scroll ===> PAGE

Enter the row command S to select operation details.

Application : MYAPPLICATION A test applicationInput arrival : 03/09/29 12.00Deadline : 03/09/29 12.50

Row Operation Jobname Input arrival Durationcmd ws no. text date time’ NONR 001 Time dependent 03/05/13 21.30 0001.00’ CPUA 005 Depends on pred 001 TESTJOB1 0005.00’ CPUA 010 Depends on pred 001 TESTJOB2 0010.00’ WTO1 015 Setup req. for TESTJOB3 03/05/13 11.00 0001.00’ JCL1 020 Setup oper. for TESTJOB3 TESTJOB3 0003.00’ CPUA 025 Depends on preds 020,010 TESTJOB3 0005.00******************************* BOTTOM OF DATA ********************************

Figure 43. Browsing operation data


Chapter 6. Creating the current plan

How to create the current plan

Before Tivoli Workload Scheduler for z/OS can schedule work, you must producea detailed plan called the current plan. The current plan (CP) is the heart of TivoliWorkload Scheduler for z/OS processing. It drives your production workload andprovides feedback about the current status of the workload. The current plan isderived from a section of the long-term plan and contains the work that TivoliWorkload Scheduler for z/OS will run. It typically covers a period of 24 hours.

This chapter includes the following topics:v “Creating the current plan”v “Creating a batch job to extend the current plan” on page 46v “Querying the current plan (QCP)” on page 47

Creating the current planHow to create the current plan

The process of producing the CP is called daily planning. The task of creating theCP is normally done once. After creation, the plan is continually extended usingbatch functions.

When the CP is created or extended, Tivoli Workload Scheduler for z/OS brings infrom the long-term plan all occurrences with an input arrival time that is withinthe interval you specify. The scheduler creates a detailed schedule for theoperations that are contained in these occurrences. When you extend the currentplan, the planning process carries forward any uncompleted occurrences into thenew plan and updates the long-term plan with completed occurrence information.Completed occurrences are not carried forward into the new plan.

These steps show how to create the current plan using the panels.1. Select option 3 (DAILY PLANNING) on the main menu to display the

PRODUCING TWSz DAILY PLANS menu.2. To create or extend the current plan, select option 2 (EXTEND) from the

PRODUCING TWSz DAILY PLANS menu. The scheduler displays this panel:


3. Specify the length of the current plan and the reports that you want.▌1▐, ▌2▐, and ▌3▐ in Figure 44 show input for creating a 24-hour current planwhich starts at 7 a.m. on May 13, 2003. This is the most commonly used formatfor specifying the length of the CP. If no current plan exists, Tivoli WorkloadScheduler for z/OS uses the current date and time as the default for ▌1▐ and▌2▐. You can change both fields to suit your needs if no CP exists. Whenextending the CP, change only the extension length ▌3▐, if necessary.The EXTENSION TYPE field ▌4▐ specifies whether both work days and free days(A) or work days only (W) are included when calculating the extension. Forexample, assume that Saturdays and Sundays are free days in your calendarand you extend the CP by 24 hours at 7 a.m. on Friday. If you include all daysby specifying A, the CP extension ends at 7 a.m. on Saturday. If, however, youspecify W, the CP is extended to 7 a.m. on Monday. Extension type A is used inthe example in Figure 44.When extending the CP, you have the option of producing reports about thecontents of the plan (see ▌5▐ in Figure 44). The scheduler puts the generatedreports into a data set with your user ID as the first qualifier if you do notspecify SYSOUT or a local printer on the GENERATING JCL FOR A BATCHJOB panel (see Figure 34 on page 38).

4. After specifying the CP length and selecting the reports that you want, pressEnter to display the GENERATING JCL FOR A BATCH JOB panel (seeFigure 34 on page 38).

5. Press Enter to submit the current plan batch job. The scheduler redisplays thedaily planning menu with the message JOB SUBMITTED.

Creating a batch job to extend the current planHow to create a batch job to extend the current plan

When you extend the current plan you can duplicate the steps in “Creating thecurrent plan” on page 45 or you can automate the process by following these steps:

EQQDPEXP --------------- EXTENDING CURRENT PLAN PERIOD ------------------------Command ===>

Enter/change data below and press ENTER

Current plan end date :

START DATE ===> 030513 ▌1▐ YYMMDD If no current plan existsTIME ===> 07.00 ▌2▐ HH.MM

END DATE ===> ________ YYMMDD Specific END dateTIME ===> _____ HH.MM Specific END time

EXTENSION LENGTH ===> 02400 ▌3▐ HHHMM Extend plan byTYPE ===> A ▌4▐ A - includes all days

W - includes only work days in theextension length above

Report selection :▌5▐ Y if report wanted, otherwise NWS SUMMARY ===> Y Summary for all work stationsOPERATING PLAN ===> Y Daily operation planWS PLANS ===> Y Plans for all work stationsINPUT ARRIVAL ===> Y List of input arrival operationsNON REPORTING ===> Y Plans for non reporting work stationCURRENT PERIOD ===> Y Print current period resultsPLANNED RESOURCE ===> Y Planned resource utilizationACTUAL RESOURCE ===> Y Actual resource utilization

Figure 44. Extending current plan period


1. Display the EXTENDING CURRENT PLAN PERIOD panel and specify thelength of the extension.

2. Press Enter to display the GENERATING JCL FOR A BATCH JOB panel.3. Type E in the SUBMIT/EDIT Batch Job field, then press Enter. The scheduler

displays the JCL for the current plan batch job.4. Type the copy command C9999 next to the first line of JCL.5. Create a new member in the job library of Tivoli Workload Scheduler for z/OS

by entering the CREATE command on the command line of the GENERATINGJCL FOR A BATCH JOB panel. You see this ISPF panel:

6. In the DATA SET NAME field ▌1▐, type the name of your job library data set andthe name of the member you are creating, and press Enter.

7. After creating the batch job, create a job or application description forextending the current plan.

Querying the current plan (QCP)Querying the current plan (QCP)

The QUERY CURRENT PLAN (QCP) panel provides answers to your productionstatus queries. You can request detailed or summary information on individualapplications, operations, or workstations, and summary information concerning allthe operations. The QCP panel looks at the current plan, which is continuouslyupdated as the operations are processed.

You can invoke QCP functions from many places in the panel. For example, if youenter row command I (Information) next to an operation in the ready list (coveredin Chapter 7, “Communicating with workstations,” on page 55), the SELECTINGAPPLICATION OCCURRENCE AND OPERATION INFORMATION panel(Figure 50 on page 51) is displayed. This can save time because you do not need toleave an area of the panel to get information.

To display the CURRENT PLAN AND STATUS INQUIRY menu (Figure 46 on page48), select option 6 (QCP) on the main menu or enter =6 from anywhere in thepanels.

---------------------------- EDIT - CREATE ----------------------------------COMMAND ===>"CURRENT" DATA SET: SYS94163.T100711.RA000.JOHNB.R0000002

TO ISPF LIBRARY:PROJECT ===>GROUP ===>TYPE ===>MEMBER ===>

TO OTHER PARTITIONED DATA SET MEMBER:DATA SET NAME ===> ’dataset(member)’ ▌1▐VOLUME SERIAL ===> (If not cataloged)

DATA SET PASSWORD ===> (If password protected)

SPECIFY PACK OPTION FOR "CREATE" DATA SET ===> NO (YES or NO)

Press ENTER key to create.Enter END command to cancel create.

Figure 45. Creating a current plan extend job

Chapter 6. Creating the current plan 47

Querying application occurrencesHow to use the QCP panel to check information about occurrences in the currentplan

This section shows how to use the QCP panel to check information aboutoccurrences in the current plan. The topics include:v Browsing application occurrences in the current planv Displaying detailed information about an occurrencev Displaying detailed operation information

Browsing application occurrences in the CPBrowsing application occurrences in the CP

To see details about occurrences:1. Start by displaying the CURRENT PLAN AND STATUS INQUIRY panel

(Figure 46).2. Select option 1 (APPLICATIONS) to display the SELECTING APPLICATION

OCCURRENCES filtering panel, where you specify the selection criteria.On this panel, if the STATUS field is left blank, all occurrences that have a statusof W (Waiting), S (Started), C (Complete), E (Ended-in-error), or U (Undecided)are displayed. Deleted applications are displayed only when you specificallyrequest applications in D status. You can also filter on the occurrence token.

3. After specifying selection criteria, press Enter to display the list of occurrences.You see this panel:

EQQSTOPP -------------- CURRENT PLAN AND STATUS INQUIRY --------------------Option ===>


1 APPLICATIONS - Query application occurrences2 MOST CRITICAL - Query most critical uncompleted application occurrences

3 OPERATIONS - Query operations (jobs)4 ENDED IN ERROR - Query operations ended in error

5 WORK STATIONS - Query work station activities

6 GENERAL - Query general information about current plan

7 CRITICAL JOBS - Query critical jobs and their critical paths

Figure 46. Current plan and status inquiry

EQQSAO1L ------- BROWSING APPLICATION OCCURRENCES (left part) ROW 1 TO 2 OF 2Command ===> Scroll ===> PAGE

Enter the GRAPH command above to view occurrences graphically orscroll right or enter the row command S to select an occurrence for details.

Row Application Input Started Status P Addcmd id text arrival at func’’ TESTJOB1 A job description 13 08.00 W 5’’ MYAPPLICATION A test application 13 11.00 13 13.02 S 5******************************* BOTTOM OF DATA ********************************

Figure 47. Browsing application occurrences (left part)


You can tell from the title line that this panel has a left part and a right part. To seethe right part, press PF11 (SCROLL RIGHT).

This example shows that:v TESTJOB1 has a status W (Waiting).v MYAPPLICATION was started at 13:02 on day 13 of the current month (Started

at column).v Both applications have an input arrival time on day 13 of the current month.v Both occurrences were added by a CP batch job function; the Add func (Add

function) column is blank.

To find out more about an occurrence, type S next to the occurrence, and pressEnter to display this panel:

From this panel, you can request detailed information about the occurrence, theoperations defined in the occurrence, or the external dependencies established withthe occurrence.

Requesting detailed information about an occurrenceRequesting detailed information about an occurrence

To display detailed information about an occurrence, select option 1 (APPLICATION)on the SELECTING APPLICATION OCCURRENCE INFORMATION menu. Yousee the panel shown in Figure 49 on page 50.

EQQSAOSP ------- SELECTING APPLICATION OCCURRENCE INFORMATION -----------------Option ===>


1 APPLICATION - Detailed information2 OPERATION LIST - Operations of the application occurrence3 EXTERNAL DEPS - External dependencies of the occurrence

Application : MYAPPLICATION A sample applicationOwner : SAMPLE Pay OfficeStatus : StartedPriority : 5Variable table :Calendar name : DEFAULTOccurence token : B4B2BE368D856102

Input arrival time:Planned : 030513 11.00Actual : 030513 13.02

Group Definition :

Figure 48. Selecting application occurrence information


On this panel, you see:v The Status of the application ▌1▐v Planned and actual start and end times for the occurrence ▌2▐v The number of uncompleted critical operations ▌3▐v The estimated duration for the uncompleted operations in the occurrence ▌4▐v The method used to add the occurrence to the current plan ▌5▐v If the occurrence is a rerun ▌6▐v Other application information

Getting detailed operation informationGetting detailed operation information

Sometimes you need to know why a certain operation is not started. Here aresome reasons why a computer workstation operation may not be started:v The workstation is not open.v Predecessors are not complete.v No parallel server is available.v The workstation is offline or has failed and no rerouting is in effect.v Not enough workstation resources are available.v Not all the required special resources are available.v The operation is waiting for a specific time of day.v The operation has been manually held.v The automatic-job-submission option is set to NO for the operation.v There was an error during job submission.

Complete the following steps to get detailed information to determine why anoperation is not started:1. Select option 2 (OPERATION LIST) from the SELECTING APPLICATION

OCCURRENCE INFORMATION menu (Figure 48 on page 49). The schedulerdisplays the BROWSING OPERATIONS panel, which lists all operations in theoccurrence.

EQQSAODP ---------- BROWSING APPLICATION OCCURRENCE DETAILS -------------------Command ===>

Application : MYAPPLICATION A sample applicationOwner : SAMPLE Pay OfficeAuthority group :Status ▌1▐: Started Occurence token : B4B2BE368D856102Priority : 5Group Definition :Calendar name : DEFAULT

Date and time for: ▌2▐ Planned ActualInput arrival : 03/09/28 12.00 03/09/25 15.17Deadline : 03/09/28 12.50

Remaining on critical path:No. of operations ▌3▐: 3Duration ▌4▐: 0000.01First critical oper : NONR 1 Time dependentLatest start : 03/09/28 12.49

Occurrence added by▌5▐: Daily Plan batch runRerun ▌6▐: No

Figure 49. Browsing application occurrence details


2. On the BROWSING OPERATIONS panel, type S next to the operation youwant to check, and press Enter. The scheduler displays this panel:

You can reach this menu from almost anywhere in the modify current plan (MCP),QCP, or workstation communication panels. The example in Figure 50 shows whya selected operation is not started. It is Ready ▌1▐ but Waiting for time ▌2▐. Referto Managing the Workload for a complete list of status codes.

Option 9 (ALL DEPS) can be helpful when you want to know why an operationhas not started. You can use this option to find out what outstanding predecessorsremain before an operation will start and to see the impact of its being late orfailing.

To list all dependencies:1. Select option 9 (ALL DEPS). You see this panel:

EQQSOPSP--SELECTING APPLICATION OCCURRENCE AND OPERATION INFORMATION ----------Option ===>

Select one of the following:1 APPLICATION - Detailed application occurrence information2 OPERATION - Detailed operation information3 OPERATION LIST - Operations of the application occurrence4 DEPENDENCIES - Immediate predecessor and successor information5 RESOURCES - List of resources used by the operation6 JCL - Browse the JCL7 OPERATOR INSTR - Operator instructions8 EXTERNAL DEPS - Immediate external dependencies of the occurrence9 ALL DEPS - All dependencies of this operation

10 CLEANUP OPTIONS - Cleanup options11 EXTENDED INFO - Operation extended info12 AUTOMATION INFO - System Automation operation info13 USER FIELDS - User fields operation info14 REMOTE JOB INFO - Detailed information about remote job15 STEP LIST - List of job steps

Application : MYAPPLICATION A test applicationOperation : CPUA 025 Depends on preds 020,010Jobname and jobid : TESTJOB3Status of operation : Ready▌1▐ Waiting for time▌2▐on Work Station :Priority of operation : 5Planned input arrival: 030513 11.00 Actual input arrival:

Figure 50. Selecting application occurrence and operation information

EQQSOPGD ---------------- SELECTING ALL DEPENDENCIES --------------------------Command ===>

Specify selection criteria below and press ENTER to create a dependency list

TYPE OF SELECTION ===> AP AP - All predecessor operationsNP - Non-completed predecessors onlyAS - All successor operationsNS - Non-waiting successors only

NUMBER OF NESTINGS ===> 999 A digit 1 to 999NESTING DETAIL ===> ALL_ ALL or NONE

Figure 51. Selecting all dependencies


|||||||||||||||||||||||||||||||

2. Specify the type of dependencies you want to see, then press Enter. In theexample, AP is selected, which lists all predecessors for the selected operation(Figure 52).

On this panel, the operation dependencies are shown by type (Ty) and level (Lev).A P in the type column indicates that the operation in the list is a predecessor tothe operation you are checking ▌1▐; S indicates that it is a successor.

If the listed operation is linked directly to the operation you are checking, its levelis 1. A direct link from the level 1 operation to another operation is a level 2dependency. This example shows 3 levels with the highest level being an operationin a different application ▌2▐.

From this panel, you can investigate further by selecting details for any of theoperations in the list.

Querying late and uncompleted occurrencesQuerying late and uncompleted occurrences

You can display the applications that are most critical and those that have missed,or are close to missing, the defined deadline.

From the main menu, you enter 6.2.0 to display a list of critical, uncompletedoccurrences. You see the panel shown in Figure 53:

EQQSPG1L ------- ALL DEPENDENCIES OF AN OPERATION (left part) ROW 1 TO 5 OF 5Command ===> Scroll ===> PAGE

Enter the GRAPH command above to view operations graphically orscroll right or enter the row command S to select an operation for details.

Application : MYAPPLICATION A sample applicationOperation : CPUA 25▌1▐ Depends on preds 020,010Jobname : TESTJOB3

Row Lev Ty Operation Jobname Application id Statuscmd ws no. text’’ 1 P CPUA 010 Depends on pred 001 TESTJOB2 MYAPPLICATION W’’ 1 P JCL1 020 Setup oper. for TESTJOB3 TESTJOB3 MYAPPLICATION W’’ 2 P NONR 001 Time dependent MYAPPLICATION W’’ 2 P WTO1 015 Setup req. for TESTJOB3 MYAPPLICATION S’’ 3 P CPUA 015 TESTJOB1 TESTJOB1▌2▐ A******************************* BOTTOM OF DATA ********************************

Figure 52. All dependencies of an operation

EQQSMC1L ------ BROWSING MOST CRITICAL OCCURRENCES (left part ROW 1 TO 2 OF 2Command ===> Scroll ===> PAGE

Enter the GRAPH command above to view occurrences graphically orscroll right or enter the row command S to select an occurrence for details.

Row L Application S P First critical opercmd ▌1▐ id text ws no. stat latest start’’ Y TESTJOB1 A job description W 5 CPUA 015 A 13 08.25’’ MYAPPLICATION A sample application S 5 NONR 001 W 14 05.44******************************* BOTTOM OF DATA ********************************

Figure 53. Browsing most critical occurrences


On this panel, Tivoli Workload Scheduler for z/OS displays occurrences sorted bythe latest start time. For any occurrence that contains operations that are not yetstarted and their latest start times have passed, Tivoli Workload Scheduler forz/OS puts Y in the L (Late) column (see ▌1▐ in Figure 53 on page 52). Lateoperations are at the top of the list.


Chapter 7. Communicating with workstations

Communicating with workstations

A workstation in Tivoli Workload Scheduler for z/OS is the place where work isdone. All operations in the current plan are associated with a workstation. For anoverall view of operations, you use the QUERY CURRENT PLAN panel. However,if you want to find out which operations are due to start or are already started at aworkstation, use the workstation ready list.

This chapter includes the following topics:v “Using the Ready List panel”v “Selecting a ready list layout” on page 57v “Using the ready list” on page 58

Using the Ready List panelUsing the Ready List panel

The ready list contains operations that have no outstanding predecessors,operations that are defined to the workstation that are waiting for a particular timeor resource, operations that have already started, and operations that have endedin error. The status of operations in the ready list is specified by the followingcodes:A Arriving—ready for processing; no predecessors were defined.I Interrupted.R Ready for processing; all predecessors are complete.* Ready—at least one predecessor is defined on a non-reporting workstation;

all predecessors are complete.S Started.E Ended-in-error.

The ready list can also include one operation in C (Complete) status; the lastoperation that you manually set to complete. This operation is maintained on theready list to give you an opportunity to reset the operation if you change yourmind.

Select option 4 (WORK STATIONS) from the main menu to display this menu:


To use ready list functions, select option 1 (READY LIST). The scheduler displaysthis panel:

On this panel, you specify the name of a workstation. You can display the readylist for only one workstation at a time. You also specify criteria to select whichoperations are included in the ready list.

The ready list displays information about the selected operations. There are up to90 fields of information that you can select for display. You use ready list layouts toidentify the fields of information you want to see. Ready list layouts contain thetitles of selected fields of information in the order that they are displayed. Severalready list layouts are supplied with Tivoli Workload Scheduler for z/OS, each for adifferent workstation type. You can also create your own ready list layouts.

EQQRTOPP ------------- COMMUNICATING WITH WORK STATIONS-----------------------Option ===>


1 READY LIST - Using the ready list

2 WAITING LIST - Review submitted jobs that have a waiting status

3 JOB SETUP - Setup the JCL for jobs

4 WORK STATIONS - Review the status of work stations

9 DEFINE RL - Define alternative ready list layouts

Figure 54. Communicating with workstations

EQQRSRLP -------------- SPECIFYING READY LIST CRITERIA ------------------------Command ===>

Enter/Change data below and press ENTER to create a ready list.

WORK STATION NAME ===> JCL1▌1▐ (Blank presents a list.)LAYOUT ID ===> *_______▌2▐ An id, blank for default, * for a list

Selection criteria:APPLICATION ID ===> _________________________OWNER ID ===> _________________________JOB NAME ===> ________LOWEST PRIORITY ===> _ Lowest priority to be selected.OPERATION STATUS ===> ______ List of status codes, A R * S I E or blank

Latest input arrival: Select only operations with inputDATE ===> ________ arrival before this date and time.TIME ===> _____ (Format YYMMDD and HH.MM )

Status sort order ===> CES List of status codes, A R * S I E or C(Any three must be selected, or all blank)

Clean Up Type ===> ____ Types list: A M I N or blankClean Up Result ===> _______ Status list: C E or blank

OP. EXTENDED NAME ===> ______________________________________________OP. SE NAME ===> _________________WAITING FOR SE ===> _ Y or N, leave blank to select all

Figure 55. Specifying ready list criteria


Selecting a ready list layoutHow to Select a ready list layout

To display the ready list layout for a workstation, follow these steps:1. On the panel shown in Figure 55 on page 56, specify the workstation name in

the WORK STATION NAME field▌1▐.When you select the ready list for a workstation for the first time, you mustspecify the layout to use for the list. If you have not specified a layout for theworkstation that you have selected, Tivoli Workload Scheduler for z/OSdisplays the list of layouts that are available. The scheduler stores yourpreferred layout for each workstation in your ISPF profile.

2. To display all the ready list layouts, type * in the LAYOUT ID field ▌2▐ on theSPECIFYING READY LIST CRITERIA panel, and press Enter. You see the paneldisplayed in Figure 56.

This figure shows the layouts that are supplied. Each layout occupies 2 lines.The first line ▌1▐ contains the name of the layout (Layout id), a description(Description), the ID of the person who created the layout (Owner), and thedate and time it was last updated (Last update). The second line ▌2▐ containsthe titles (Header) of the fields that have been selected for the layout. Refer toManaging the Workload for a complete list of the fields.

3. To select a layout for the workstation, type S next to the layout, and pressEnter. The scheduler displays the workstation ready list with the layoutselected.

EQQRLYSL --------------- SELECTING A READY LIST LAYOUT ------ ROW 1 TO 6 OF 6Command ===> Scroll ====> PAGE

Enter the CREATE command to create a new layout orenter any of the row commands below:S - select a layout, C - create a copy of a layout

Row Layout id Description Owner Last updatecmd Header’ C1 Layout 1 for CPU work station LEIFTO2 860915 08.21

St no. Jobname Operation text Job id Application Oi U’ C2 Layout 2 for CPU - times LEIFTO2 860913 13.12

St no. Jobname Last out time Pl start time E dur Plan end time Oi U’ C3 Layout 3 for CPU - options LEIFTO2 860913 13.19

St no. Jobname Job id Rdr date Rdr t R1# R2# SR# SU# A C H T P Oi U’ ID1 Identification layout1 - texts LEIFTO2 860913 13.24

St Application Application text no. Ia date Ia time Oi U’ ID2 Identification layout2 - texts LEIFTO2 860913 13.29

St Application Ia date Ia time no. Operation text Oi U▌1▐ S1 Layout for setup work station LEIFTO2 860913 13.37▌2▐ St no. Operation text Ia day Ia time Jobname Lo time Oi U******************************* BOTTOM OF DATA *************************

Figure 56. Selecting a ready list layout

Chapter 7. Communicating with workstations 57

Using the ready listHow to use the ready list

You use the row commands that are displayed on the READY LIST panel to dovarious tasks. The items in Table 1 show some of the tasks and the applicable rowcommands that you can use.

Table 1. Tasks and row commands on the Ready List

Task Row command

Diagnose delays. I (Information about an operation)

Set the status of an operation. N–x (Set specific status x) and N (Set next logicalstatus)

Reset an operation to its previousstate.

R (Reset status)

Interrupt an operation. N–I (Set specific status)

Set an operation to ended-in-error. N–E (Set specific status)

Read operator instructions. O (Operator Instructions)

Prepare JCL at a setup workstation. N (Set next logical status)

Delay an operation, then release it. MH (manual hold) and MR (manual release)

Make the operation anon-operation, which means thatTivoli Workload Scheduler forz/OS passes over it withoutrunning it, and continues with itssuccessors. Reverse this by makingthe operation executable again.

NP (NOP operation) and UN (un-NOP operation)

Run an operation immediately withEXECUTE.

EX (execute operation)Note: The scheduler takes account of predecessors,but otherwise ignores other reasons for waiting (NOP,Held, job submission inactive, time not reached,resources unavailable, job not automaticallysubmittable, workstation is being shut down).

Reset the bind information collectedfor a shadow job.

BND

EQQRLRLM ------------------------ READY LIST ---------------- ROW 1 TO 1 OF 1Command ===> Scroll ===> PAGE

Enter the HIST primary command orenter any of the following row commands:N - Set next logical status, N-x - Set specific status( x ),R - Reset status, O - Operator Instructions, I - Information about operation,MH Manual hold operation, MR Manual release operation, NP Nop operation,UN Un-nop operation, EX Execute operation, BND Reset bind information.

WORK STATION ===> JCL1 Change to switch work stationLAYOUT ID ===> S1______ Change to switch layout id

▌1▐Cmd St no. Operation text Ia day Ia time Jobname Lo time Oi U’’ R 20 Setup oper. for TESTJOB3 06 21.00 TESTJOB3 07 05.53 +******************************* BOTTOM OF DATA ********************************

Figure 57. Ready list for job setup workstation


The next sections in this chapter show examples of how to use the O and N rowcommands on the ready list.

Viewing operator instructionsViewing operator instructions

Some operations might require specific instructions about how they are to behandled. These instructions are called operator instructions. You can tell whetherinstructions exist for an operation by looking at the code in the Oi ready-list field(see ▌1▐ in Figure 57 on page 58). The three operator instruction codes displayed inthe Oi ready-list field are:N There are no operator instructions.Y There are operator instructions.+ Some operator instructions have been changed recently. The default is 30

days, but the definition of “recent” depends on installation parameters.1. To browse operator instructions for an operation, type the letter O next to the

operation on the READY LIST panel, and press Enter. The scheduler displaysthe instructions using the ISPF/PDF browse function.

2. To return to the READY LIST panel, press PF3 (END).

Preparing jobs at a setup workstationPreparing jobs at a setup workstation

A setup workstation is a general workstation used for preparing jobs manually,when this is necessary. The operation that runs the job on the computerworkstation can be started as soon as job setup is complete, if it is not waiting forother conditions to be met.1. To display the JCL for editing, type N (set next logical status) next to the

operation, and press Enter. When you set the next logical status for anoperation at a job setup workstation, Tivoli Workload Scheduler for z/OS setsthe status of the setup operation to S (Started). The action that Tivoli WorkloadScheduler for z/OS takes depends on whether it finds unresolved promptablevariables in the job. A promptable variable is a variable that must be suppliedby the operator.The scheduler displays the input stream on this panel:

EQQRJCLE --------------- EDITING JCL FOR AN OPERATION -------------------------Command ===> Scroll ===> HALF

Edit JCL below and press END to complete, CANCEL to reject and reset,or TSAVE to save changes and interrupt the operation.

Application : MY#APPLICATION#2 A test applicationOperation : CPUA 025 Depends on preds 020,010Jobname : TESTJOB3 JCL last updated by: JOHNB

****** ***************************** TOP OF DATA ******************************000001 //TESTJOB3 JOB (account_field),’JOB3’,000002 // MSGLEVEL=(1,1),NOTIFY=notify_field,000003 // MSGCLASS=Q,CLASS=init_class,REGION=4094K000004 //*000005 //BR14 EXEC PGM=IEFBR14000006 //****** **************************** BOTTOM OF DATA ****************************

Figure 58. Editing JCL for an operation

Chapter 7. Communicating with workstations 59

When you edit the job using the READY LIST or MCP panels, you edit thelatest job from the JCL repository (JS file), which is where Tivoli WorkloadScheduler for z/OS places modified jobs. The original job is always leftunaltered in the partitioned data set allocated to the ddname EQQJBLIB(JBLIB). This ensures that the master JCL is protected from temporary changesand that reruns of the job use the same JCL as in the original run. To forceTivoli Workload Scheduler for z/OS to read a fresh copy of the job from JBLIB,delete all the lines, and end the edit.To temporarily save changes you make to the job, enter the TSAVE (temporarysave) command. The scheduler sets the operation status to I (Interrupted) andsaves the JCL but does not submit the job. You redisplay the job by typing Nnext to the operation and pressing Enter.

2. To save the edited JCL, press PF3 (END). The scheduler sets the status of theoperation to C (Complete) and redisplays the READY LIST panel.


Chapter 8. Modifying the current plan (MCP)

How to modify the current plan (MCP)

After the current plan is built, you might need to make changes to it if, forexample, a processor becomes unavailable, or you need an extra run of anapplication. To perform these tasks, you use the MODIFY CURRENT PLAN (MCP)panel.

This chapter describes how you use the MCP panel to:v “Adding an occurrence to the current plan”v “Changing details of an operation in the current plan” on page 63v “Correcting and restarting failed operations” on page 65v “Rerunning an occurrence from a specific operation” on page 67

To access the MCP panel, select option 5 from the main menu. You see this menu:

Adding an occurrence to the current planHow to add an occurrence to the current plan

You can add on-request work to the current plan using the MCP panel. Before youcan add an application occurrence to the plan, however, a description of theapplication must exist in the application description database.

If your installation frequently adds work to the plan that does not have anapplication description defined for it, consider creating dummy model applicationsthat match the work most commonly added. The simplest model applicationconsists of one computer workstation operation. The job names in these modelapplications should be dummy names indicating that they are only models.

Note: To stop the planning programs adding occurrences for these applications,create them without run cycles, or with run cycles that never generate occurrences.

These steps show how to add an occurrence to the CP. In the example, theapplication MYAPPLICATION is added to the CP.

EQQMTOPP ---------------- MODIFYING THE CURRENT PLAN --------------------------Option ===>


1 ADD - Add a new occurrence to the current plan2 LIST - List existing occurrences for further processing

3 OPERATIONS - List existing operations for further processing4 ERROR HANDLING - Handle operations in error5 WORK STATIONS - Change status and open interval of work stations

6 JOB SETUP - Prepare JCL for jobs in the current plan

7 SPECRES - Special resource monitor

9 DEFINE EL - Define alternative error list layouts

Figure 59. Modifying the current plan


1. Select option 1 from the MODIFYING CURRENT PLAN panel, or enter =5.1from the command prompt in any other part of the panel.

The AUTOMATIC DEP and RESOLVE REQUIRED fields on this panel affecthow Tivoli Workload Scheduler for z/OS adds the occurrence. These fields andthe APPLICATION ID field retain the values from the last occurrence youadded. The scheduler always puts the current date in the Input arrival DATEfield.

2. In this example, a generic application ID is entered so that Tivoli WorkloadScheduler for z/OS displays a selection list on the SELECTINGAPPLICATIONS TO ADD TO THE CP panel (Figure 61).You can save time by entering the full application name on the criteria panel.The scheduler then displays the ADDING AN APPLICATION TO THECURRENT PLAN panel (Figure 62 on page 63).

3. Type A next to the application you are adding, and press Enter. The schedulerdisplays this panel:

EQQMADDP ---------- ADDING APPLICATIONS TO THE CURRENT PLAN -------------------Command ===>

Specify the information below and press ENTER to add the occurrence,or specify selection criteria to create a list of applications.

APPLICATION ID ===> MY*_____________

Input arrival:DATE ===> 030513 Date in format YYMMDDTIME ===> _____ Time in format HH.MM

Deadline:DATE ===> ________ Date in format YYMMDDTIME ===> _____ Time in format HH.MM

PRIORITY ===> _ 1-9ERROR CODE ===> ____ If rerun of occurrence

AUTOMATIC DEP ===> Y Automatic dependency add, Y P S or NRESOLVE REQUIRED ===> Y Auto deps must be resolved, Y or NGROUP DEFINITION ===> ________________ Group Definition filter

Figure 60. Adding applications to the current plan

EQQMAADL ---------- SELECTING APPLICATIONS TO ADD TO THE CP - ROW 1 TO 1 OF 1Command ===> Scroll ===> PAGE

Enter the row command A to add an applicationor G to add an application group to the Current Plan,

Row Application Group Ownercmd id description id Identity’ MYAPPLICATION A sample application SAMPLE******************************* BOTTOM OF DATA ********************************

Figure 61. Selecting applications to add to the current plan


4. If you are adding an occurrence for an application with no run cycle, you mustfill in the input arrival TIME, and deadline DATE and TIME.The input arrival and deadline DATE and TIME fields are filled in by TivoliWorkload Scheduler for z/OS if the application has a run cycle. You canmodify these fields to:v Suit the on-request run timesv Change the input arrival TIME if you are adding another occurrence of the

application.5. When you press PF3 (END) to create the new occurrence, Tivoli Workload

Scheduler for z/OS displays the SELECTING APPLICATIONS TO ADD TOTHE CP panel, with the message OCCURRENCE ADDED in the upper-rightcorner of the panel.

Changing details of an operation in the current planHow to change details of an operation in the current plan

Use the MCP panel to change the details of operations in the current plan. Thesesteps show how to activate automatic submission, and how to remove the timedependency from an operation:1. Select 2 (LIST) on the MODIFYING THE CURRENT PLAN menu (Figure 59 on

page 61) to display the SPECIFYING MCP OCCURRENCE LIST CRITERIApanel.

2. Specify selection criteria and press Enter. You see this panel:

EQQMAOCP --------- ADDING AN APPLICATION TO THE CURRENT PLAN -----------------Command ===>

Enter the DEP command above to verify automatic dependency resolution, or,enter the OPER command to modify operations.

Application : MYAPPLICATION A sample applicationOwner : SAMPLE Pay OfficeOperations : 6External predecessors : 0

AUTOMATIC DEP ===> N Automatic resolution of external andconditional dependencies, Y P S or N

Input arrival:DATE ===> 030513 Date in format YYMMDDTIME ===> 21.00 Time in format HH.MMDeadline:DATE ===> 030514 Date in format YYMMDDTIME ===> 06.00 Time in format HH.MMVARIABLE TABLE ===> ________________ JCL variable table to be usedGROUP DEFINITION ===> ________________PRIORITY ===> 5 1-9ERROR CODE ===> ____ If this is a rerun

Figure 62. Adding an application to the current plan

Chapter 8. Modifying the current plan (MCP) 63

3. Type M (Modify) next to the occurrence, and press Enter. The schedulerdisplays this panel:

4. On this panel, enter OPER to display this panel:

EQQMOCLL --------- MODIFYING OCCURRENCES IN THE CURRENT PLAN ROW 1 TO 3 OF 3Command ===> Scroll ===> PAGE

Enter the CREATE command to add a new occurrence orenter the GRAPH command to display occurrence list graphically orenter any of the row commands below:B - Browse, D - Delete, M - Modify, RG - Remove from group, DG - Delete Group,C - Complete, W -Set to Waiting, R - Rerun, CG - Complete Group

Row Application Input arrival S P G Addcmd id text date time func’’ MYAPPLICATION A sample application 030513 11.00 S 5 N’’ MYAPPLICATION A sample application 030513 21.00 S 5 N D’’ TESTJOB1 A job description 030513 08.00 W 5 N******************************* BOTTOM OF DATA ********************************

Figure 63. Modifying occurrences in the current plan

EQQMMOCP -------- MODIFYING AN OCCURRENCE IN THE CURRENT PLAN -----------------Command ===>

Enter/change data below:Enter the DEP command above to verify external dependencies, or,enter the OPER command to modify operations.

Application : TESTJOB1 A job descriptionOwner : SAMPLE Pay OfficeStatus : WaitingOperations : 1External predecessors : 0Calendar name :

Input arrival:DATE ===> 030513 Date in format YY/MM/DDTIME ===> 08.00 Time in format HH.MMDeadline:DATE ===> 030513 Date in format YY/MM/DDTIME ===> 08.30 Time in format HH.MM

VARIABLE TABLE ===> ________________ JCL variable table idPRIORITY ===> 5 1-9GROUP DEFINITION ===> ________________ Group definition id

Figure 64. Modifying an occurrence in the current plan


In this example, occurrence TESTJOB1 is being modified. In the Opt S (SUBMIT)column, you see N. This means that automatic job submission is deactivated forthe operation in TESTJOB1.

5. To activate automatic job submission for this operation, change the N to Y andpress PF3 (END). The scheduler redisplays the panel in Figure 64 on page 64.

6. Press PF3 (END) once more to return to the panel in Figure 63 on page 64. Thescheduler displays the message OCCURRENCE MODIFIED.Time-dependent operations have Y in the Opt T (Time Dependent) column onthis panel.

7. To remove time-dependency from an operation, change the Y to N and save thechange. If there are no other dependencies, Tivoli Workload Scheduler for z/OSstarts the operation immediately.

Correcting and restarting failed operationsCorrecting and restarting failed operations

When an operation under the control of Tivoli Workload Scheduler for z/OS doesnot complete successfully, it is reported as having ended in error. The schedulerautomatically reports failures of jobs or started tasks, and you can manually reportfailures of other operations using the panel.

The scheduler keeps an error list, which is a list of all operations that have endedin error. You can display this list using either the MCP panel, which lets you takesome action on the operation, or the QCP panel, where you can only browse theoperation.

When you use the HANDLING OPERATIONS ENDED IN ERROR panel(Figure 67 on page 66) in the MCP panel, you have access to these options:v Restarting the operationv Completing or deleting the operation or the occurrencev Requesting automatic recovery for the operationv Completing or deleting an occurrence groupv Initiating, discarding, or displaying catalog-management actionsv Browsing the job log

The steps in this section show how to display the error list:

EQQMMOPL --------- MODIFYING OPERATIONS IN THE CURRENT PLAN - ROW 1 TO 1 OF 1Command ===> Scroll ===> PAGE

Enter the GRAPH command above to view operations graphically orchange data in the rows, and/or enter any of the following row commands:I(nn) - Insert, R(nn),RR(nn) - Repeat, D(nn),DD - DeleteJ - Edit JCL, O - Browse operator instructions, S - Modify operation detailsL - Browse joblog

Application : TESTJOB1 A job descriptionOwner : SAMPLE Pay OfficeInput arrival : 030513 08.00Status : Waiting

Row Operation Jobname PS Duration Opt Ext Res Statcmd ws no. text HH.MM.SS S T S/P S R1 R2 N Cu’’’ CPUA 015 ________________________ TESTJOB1 1 00.00.01 N N Y 0 0 _ S******************************* Bottom of data ********************************

Figure 65. Modifying operations in the current plan


1. Select option 4 (ERROR HANDLING) from the MCP menu. You see this panel:

2. On this panel, you specify selection criteria to display only the list items youwant to examine. The scheduler uses an error list layout to display selectedfields of information about the operation that ended in error. You can createyour own error list layout or use the supplied layout OPCESA ▌1▐.

3. Press Enter to display this panel:

You use the row commands on this panel to act on operations in the error list.Figure 67 shows extended explanatory text for the row commands. The schedulerdisplays this text when you enter the EXTEND command on this panel. You cansuppress the text using the SUPPRESS command.

Correcting ended-in-error operationsCorrecting ended-in-error operations

Figure 67 shows job TESTJOB2 ended with a JCL interpreter error; the error code(Errc) is JCLI. Follow these steps to correct the JCL:1. To display the JCL for an ended-in-error operation, type J (JCL edit) next to the

operation, and press Enter. The scheduler displays the JCL on the EDITING JCLFOR A COMPUTER OPERATION panel.The scheduler keeps a separate copy of the job for each run. The job you editusing the J row command is always the job that was used during the failingrun of the job (unless you have edited it since the failure).

EQQMERRP ---------- SPECIFYING ENDED IN ERROR LIST CRITERIA -------------------Command ===>

Specify selection criteria below and press ENTER to create a listof operations that have ended in error.

LAYOUT ID ===> OPCESA___ ▌1▐ Id of layout, * for a list

JOBNAME ===> ________APPLICATION ID ===> ________________OWNER ID ===> ________________AUTHORITY GROUP ID ===> ________WORK STATION NAME ===> ____ERROR CODE ===> ____GROUP DEFINITION ===> ________________CLEAN UP TYPE ===> ____ Types list: A M I N or blankCLEAN UP RESULT ===> _______ Status list: C E or blankOP. EXTENDED NAME ===> ______________________________________________OP. SE NAME ===> _________________

Figure 66. Specifying ended in error list criteria

EQQMEP1L ------ HANDLING OPERATIONS ENDED IN ERROR (left part Row 1 to 1 of 1Command ===> Scroll ===> PAGE

Scroll right, enter the EXTEND command to get extended row commandinformation, enter the HIST command to select operation history list orenter any of the row commands below:I,O,J,L,RC,RI,C,MH,MR,SJR or RER,ARC,WOC,CMP,MOD,DEL,RG,DG or CG

LAYOUT ID ===> OPCESA__ Change to switch layout id

Cmd Ended time Application ws no. Jobname Errc’’ 030513 14.14 MYAPPLICATION CPUA 10 TESTJOB2 JCLI

Figure 67. Handling operations ended in error


2. To save the edited JCL, press PF3 (END). The scheduler saves the modified jobin the JCL repository and redisplays the error list.

Editing and saving the JCL does not cause the operation to be restarted; restart theoperation using the RC row command.

Rerunning an occurrence from a specific operationHow to Rerun an occurrence from a specific operation

Sometimes you need to rerun an occurrence either from the first operation or froma specific operation in the sequence. In this section, a sample application calledMYAPPLICATION is used to demonstrate how to set up and rerun an application.1. Type R (Rerun) next to an occurrence on the MODIFYING OCCURRENCES IN

THE CURRENT PLAN panel (Figure 63 on page 64) to display the panel shownin Figure 68.

2. On this panel, you set the restart point in the application by entering the S rowcommand next to the operation where you want to start the rerun.If there are external dependencies defined to the operation, they are includedon the LIST DEPENDENCY STATUS CHANGE panel, which Tivoli WorkloadScheduler for z/OS displays automatically; if not, the RERUNNING ANOCCURRENCE panel is updated to show the changes in operation status (seeFigure 69 on page 68).

EQQMROCL -------- RERUNNING AN OCCURRENCE IN THE CURRENT PLAN ROW 1 TO 6 OF 6Command ===> Scroll ===> PAGE

Enter/change data below and/or enter any of the following row commands:

S - Set restart point, RC - Restart and Cleanup, L - Browse joblog,J - Edit JCL, O - Browse operator instructions, MH - Manual HOLD oper,MR - Manual RELEASE oper, NP - NOP oper, or UN - Undo NOP oper

Application : MYAPPLICATION A sample applicationInput arrival : 030513 11.00Calendar name : DEFAULT

DEADLINE DATE ===> 030514 Date in format YY/MM/DDDEADLINE TIME ===> 06.00 Time in format HH.MMPRIORITY ===> 5 1-9 where 1=low, 8=high and 9=urgentERROR CODE ===> ____ For reporting purposes

Row Operation Jobname Status Error Man Nop Cln Logcmd ws no. text code Hld T S Stat’ NONR 001 Time dependent C N N N’ CPUA 005 Depends on pred 001 TESTJOB1 C N N Ns CPUA 010 Depends on pred 001 TESTJOB2 C N N N’ WTO1 015 Setup req. for TESTJOB3 C N N N’ JCL1 020 Setup oper. for TESTJOB3 TESTJOB3 C N N N’ CPUA 025 Depends on preds 020,010 TESTJOB3 C N N N

Figure 68. Rerunning an occurrence in the current plan


Figure 69 shows that Tivoli Workload Scheduler for z/OS set the status of therestart point operation to R ▌1▐ and the status of its successor dependency to W▌2▐. The completed operations at the general workstations and all predecessoroperations are set to status C (Complete).

3. After setting the restart point, confirm the rerun request. Press PF3 (END) todisplay this panel:

4. On this panel, you confirm or reject the rerun request. You must enter a reasonfor the restart. The scheduler redisplays the MODIFYING OCCURRENCES INTHE CURRENT PLAN panel with the message STATUS SET TO RERUN.

If you use the MCP panel to browse details of the occurrence, you see Yes in theRerun field of the BROWSING APPLICATION OCCURRENCE DETAILS panel (seeFigure 49 on page 50).

EQQMROCL -------- RERUNNING AN OCCURRENCE IN THE CURRENT PLAN ROW 1 TO 6 OF 6Command ===> Scroll ===> PAGE

Enter/change data below and/or enter any of the following row commands:

S - Set restart point, R - Restart and Cleanup, L - Browse joblog,J - Edit JCL, O - Browse operator instructions, MH - Manual HOLD oper,MR - Manual RELEASE oper, NP - NOP oper, or UN - Undo NOP oper

Application : MYAPPLICATION A sample applicationInput arrival : 030513 11.00

DEADLINE DATE ===> 030514 Date in format YY/MM/DDDEADLINE TIME ===> 06.00 Time in format HH.MMPRIORITY ===> 5 1-9 where 1=low, 8=high and 9=urgentERROR CODE ===> ____ For reporting purposes

Row Operation Jobname Status Error Man Nop Cln Logcmd ws no. text code Hld T S Stat’ NONR 001 Time dependent C N N N’ CPUA 005 Depends on pred 001 TESTJOB1 C N N N’ CPUA 010 Depends on pred 001 TESTJOB2 R ▌1▐ N N N’ WTO1 015 Setup req. for TESTJOB3 C N N N’ JCL1 020 Setup oper. for TESTJOB3 TESTJOB3 C N N N’ CPUA 025 Depends on preds 020,010 TESTJOB3 W ▌2▐ N N N

Figure 69. Rerunning an occurrence in the current plan

EQQMCSTL --------------- CONFIRM RERUN OF AN OCCURRENCE -----------------------Command ===> Scroll ===> PAGE

Enter Y in the command field to confirm rerun orenter N to reject rerun.

Application : MYAPPLICATION A sample applicationInput arrival : 030513 11.00Owner : SAMPLEStatus : C

Error code :Reason for restart ===> _____________________________________________

_________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Figure 70. Confirm rerun of an occurrence


Chapter 9. Scheduling end-to-end

Scheduling end-to-end

After the end-to-end environment has been set up, you can run any workload onthe distributed network. According to the type of end-to-end environment you set,you can schedule:v “With fault tolerance capabilities”v “With z-centric capabilities” on page 72

With fault tolerance capabilitiesWith fault tolerance capabilities

You must define the following objects in the Tivoli Workload Scheduler for z/OSdatabase:v The fault-tolerant workstations.v The jobs that will be scheduled to run on the fault-tolerant workstations.

For detailed information about the fault-tolerant end-to-end environment, see theEnd-to-end Scheduling with Fault Tolerance Capabilities manual.

Defining a fault-tolerant workstationDefining a fault-tolerant workstation

A fault-tolerant workstation is the definition of an existing Tivoli WorkloadScheduler for z/OS standard or fault-tolerant agent in the distributed network. Theagent is where the job associated with the fault-tolerant workstation will beactually run in the distributed network. To Tivoli Workload Scheduler for z/OS,the fault-tolerant workstation is configured as a computer workstation.

To define the fault-tolerant workstation, you must:1. Define the workstation in a CPUREC initialization statement.2. Add the definition to the database using ISPF.

Creating the CPUREC statementHow to create the CPUREC statement for the workstation.

Create the CPUREC statement for the workstation. This CPUREC statement,together with others, is included in a PARMLIB member that is pointed to in theTOPOLOGY initialization statement. The TOPOLOGY initialization statement isused to define parameters related to the topology of the connected Tivoli WorkloadScheduler for z/OS network. Such network topology statement is made up of asmany DOMREC statements as the domains in the distributed network, and by asmany CPUREC statements as there are fault-tolerant workstations.

The distributed agents of an end-to-end with fault tolerance capabilitiesenvironment do not need to be organized in domains. You may also attachfault-tolerant workstations (corresponding to fault-tolerant and to standard agents)directly to the end-to-end server (OPCMASTER) without the need of anintermediate domain manager.


In the example below, note that only the domain manager FTW1 of the TivoliWorkload Scheduler for z/OS domain DOMAIN1 is defined as a fault-tolerantworkstation and that Tivoli Workload Scheduler for z/OS is the master domainmanager (with the hard-coded MASTERDM name) for the distributed domain.****************TPLGINFO MEMBER ***************************

/*********************************************************************//* DOMREC: Domain definitions *//*********************************************************************/DOMREC DOMAIN(DOMAIN1)

DOMMNGR(FTW1)DOMPARENT(MASTERDM)

/*********************************************************************//* CPUREC: Fault Tolerant Workstation definitions *//*********************************************************************/CPUREC CPUNAME(FTW1)

CPUOS(WNT)CPUNODE(’146.84.179.86’)CPUDOMAIN(DOMAIN1)CPUTYPE(FTA)CPUAUTOLNK(ON)CPUTZ(’Europe/Rome’)CPUUSER(maestro)

Defining the workstation with ISPFHow to define the workstation with ISPF

Figure 71 shows the ISPF definition for FTW1. You must define fault-tolerantworkstations as computer automatic and then set the FT Workstation field to Y.Make sure you create the CPUREC statement before doing the ISPF definition. TheISPF definition alone has no effect without the CPUREC statement.

Defining a job to be run on a fault-tolerant workstationDefining a job to be run on a fault-tolerant workstation

EQQWCGEP---------- CREATING GENERAL INFORMATION ABOUT A W0RK STATION ----------Command ===>

Enter the command R for resources A for availability or O for end-to-endoptions, or D for Destinations above, or enter data below:

WORK STATION NAME ===> FTW1DESCRIPTION ===> FTA on my PC____________________WORK STATION TYPE ===> C G General, C Computer, P Printer

R Remote EngineREPORTING ATTR ===> A A Automatic, S Manual start and completion

C Completion only, N Non reportingPRINTOUT ROUTING ===> SYSPRINT The ddname of daily plan printout data setSERVER USAGE ===> B Parallel server usage C , P , B or NDESTINATION ===> ________ Name of destination

Options: allowed Y or NSPLITTABLE ===> N JOB SETUP ===> NSTARTED TASK, STC ===> N WTO ===> NWAIT ===> N FAULT-TOLERANT AGENT ===> YAUTOMATION ===> N Z-CENTRIC AGENT ===> NVIRTUAL ===> N DYNAMIC ===> N

REMOTE ENGINE TYPE ===> Z z/OS or D DistributedDefaults:TRANSPORT TIME ===> 00.00 Time from previous work station HH.MMDURATION ===> 00.05.00 Duration for a normal operation HH.MM.SS

Figure 71. Defining a fault-tolerant workstation


Fault-tolerant end-to-end jobs and applications are defined just like any other inTivoli Workload Scheduler for z/OS. Just specify the fault-tolerant workstations onwhich they will be running. In Figure 72, RECOV becomes a job used forend-to-end scheduling only because the associated workstation is FTW1.

You also have the option for specifying if the job is to use centralized scripts ornot. You do this by specifying Y or N in the CENTRALIZED SCRIPT field of thepanel shown in Figure 73.

If you use centralized scripts, the scripts are stored in the JOBLIB on the host. Ifyou use non-centralized scripts, the definition of a job is stored in the SCRIPTLIBon the fault-tolerant agent where the job runs. If you choose to use centralizedscripts when the job is run, then the statements in the script are sent through thenetwork to the fault-tolerant agent. This causes a limitation on the fault-toleranceof the workstation and, if selected for a large number of end-to-end schedulingjobs, can increase network traffic.

The following is an example of a non-centralized job definition:

--------------------------------- OPERATIONS -----------------Row 1 to 1 of 1Command ===> Scroll ===> PAGE

Enter/Change data in the rows, and/or enter any of the followingrow commands:I(nn) - Insert, R(nn),RR(nn) - Repeat, D(nn),DD - DeleteS - Select operation details, J - Edit JCLEnter the TEXT command above to include operation text in this list, or,enter the GRAPH command to view the list graphically.

Application : APLL1 FTW appl

Row Oper Duration Job name Internal predecessors Morepredscmd ws no. HH.MM.SS -IntExt-’’’’ FTW1 001 00.00.01 RECOV___ ___ ___ ___ ___ ___ ___ ___ ___ 0 0******************************* Bottom of data ********************************

Figure 72. Defining a job for end-to-end scheduling with fault tolerance capabilities

EQQMMJOP ------ MODIFYING JOB, WTO, AND PRINT OPTIONS IN THE CP ---------------Command ===>

Enter/change data below:Application : APPL1 appl1 twsInput arrival : 03/03/18 00.01Operation : FTW1 001JOB NAME ===> RECOV___ Name of the job or taskJOB/SYSOUT CLASS ===> - Job/sysout class depending on workstationERROR TRACKING ===> Y Automatically track errors, Y or NHIGHEST RETURN CODE ===> ____ Highest return code not treated as errorEXTERNAL MONITOR ===> N Job monitored by external product (Y/N)CENTRALIZED SCRIPT ===> N Centralized script Y/N (for FTW only)CRITICAL ===> N Critical job N P WPOLICY ===> _ CLASS ===> ________ WLM Policy and Service ClassJob options : Specify Y or N for the following options:SUBMIT ===> Y Will be submitted by OPC/ESAHOLD/RELEASE ===> Y Will be released if held by OPC/ESATIME DEPENDENT ===> N Above actions at a specific timeSUPPRESS IF LATE ===> N Suppress if time dependent action is lateDEADLINE WTO ===> N Deadline WTO should be issuedRESTARTABLE ===> - Operation is restartableREROUTEABLE ===> - Operation is eligible for reroute

Print options : Specify for a printer operation:FORM NUMBER ===> ________ Sysout forms name

Figure 73. Defining job options

Chapter 9. Scheduling end-to-end 71

VARSUBTABLES(APPL1)PREFIX(’&’)BACKPREF(’%’)VARFAIL(YES)

JOBRECJOBSCR(’D:\win32app\maestro\valerr.bat’)JOBUSR(’&OWNER’)

RECOVERYOPTION(RERUN)MESSAGE(’Continue: YES or NO?’)JOBSCR(’D:\win32app\maestro\valeok.bat’)JOBUSR(’maestro’)JOBWS(FTW1)

With z-centric capabilitiesWith z-centric capabilities

You must define the following objects in the Tivoli Workload Scheduler for z/OSdatabase:v The Tivoli Workload Scheduler for z/OS Agent destinations.v The Tivoli Workload Scheduler for z/OS Agent workstations.v The jobs that will be scheduled to run on the Tivoli Workload Scheduler for

z/OS Agent workstations.

If you did not change the default configuration of the Tivoli Workload Schedulerfor z/OS Agent, you must also configure the SSL connection protocol andcustomize the connection parameters. For detailed information, see the End-to-endScheduling with z-centric Capabilities manual.

Defining Tivoli Workload Scheduler for z/OS Agentdestinations with the ROUTOPTS statement

Defining Tivoli Workload Scheduler for z/OS Agent destinations with theROUTOPTS statement

Tivoli Workload Scheduler for z/OS Agents are directly connected to the controller.This means that you use the ROUTOPTS statement to define the connection detailsof a Tivoli Workload Scheduler for z/OS Agent to the controller or standbycontroller.

Set the HTTP or HTTPS keyword to define all your Tivoli Workload Scheduler forz/OS Agent destinations. For a Tivoli Workload Scheduler for z/OS Agent, adestination is the combination of a name (up to 8 characters) and the fullyqualified host name, or IP address, and port number of the agent.

HTTP and HTTPS have the same syntax. The difference is that HTTPS defines theconnection as SSL-secure.

ROUTOPTS is defined in the member of the EQQPARM library specified by thePARM parameter in the JCL EXEC statement of the controller. The syntax fordefining Tivoli Workload Scheduler for z/OS Agent destinations is the following:ROUTOPTS HTTP|HTTPS(destination,...,destination)

where destination is indicated as follows:destName:’fully qualified hostname or IP address of agent’/port num of agent


You can include as many destinations as you want within the parentheses. Theymust be separated by commas. Because you cannot specify more than 455 lines foreach ROUTOPTS statement, you can add further destinations by specifying morethan one ROUTOPTS statement.

The destination name is any alphanumeric sequence of up to 8 characters. You willneed the destination names again when you define the Tivoli Workload Schedulerfor z/OS Agent workstations with ISPF or the Dynamic Workload Console.

For example:ROUTOPTS HTTPS(ITAAC1:’192.27.144.12’/44112, ITAAC2:’192.14.55.231’/61424)

Specifies the destinations to two Tivoli Workload Scheduler for z/OS Agentworkstations. ITAAC1 and ITAAC2 are the destination names that define theconnection parameters of the two agents. These names must also be specified asthe destination names in the workstation definitions of the Tivoli WorkloadScheduler for z/OS Agents.

Defining a Tivoli Workload Scheduler for z/OS Agentworkstation with ISPF

Defining a Tivoli Workload Scheduler for z/OS Agent workstation with ISPF

After defining the destinations of your Tivoli Workload Scheduler for z/OS Agents,you need to define the Tivoli Workload Scheduler for z/OS Agents as TivoliWorkload Scheduler for z/OS computer automatic workstations. Figure 74 showsthe EQQWCGEP panel used to create general information about a Tivoli WorkloadScheduler for z/OS Agent workstation named LWE1.

Define a Tivoli Workload Scheduler for z/OS Agent as a computer automaticworkstation and enter the destination name previously defined in the ROUTOPTSstatement. The Z-CENTRIC AGENT option excludes all other options.

EQQWCGEP ----- CREATING GENERAL INFORMATION ABOUT A WORK STATION --------Command ===>

Enter the command R for resources or A for availability or O for end-to-endoptions, or D for Destinations above, or enter data below:

WORK STATION NAME ===> LWE1DESCRIPTION ===> Accts ReceivableWORK STATION TYPE ===> C G General, C Computer, P Printer

R Remote EngineREPORTING ATTR ===> A A Automatic, S Manual start and completion

C Completion only, N Non reportingPRINTOUT ROUTING ===> SYSPRINT The ddname of daily plan printout data setSERVER USAGE ===> B Parallel server usage, B, N, P, or CDESTINATION ===> ITAAC1 Name of destinationOptions: allowed Y or NSPLITTABLE ===> N JOB SETUP ===> NSTARTED TASK, STC ===> N WTO ===> NAUTOMATION ===> N FAULT-TOLERANT AGENT ===> NWAIT ===> N Z-CENTRIC AGENT ===> YVIRTUAL ===> N DYNAMIC ===> N

REMOTE ENGINE TYPE ===> Z z/OS or D DistributedDefaults:TRANSPORT TIME ===> 00.00 Time from previous work station HH.MMDURATION ===> 00.05.00 Duration for a normal operation HH.MM.SS

Figure 74. EQQWCGEP - Creating general information about a Tivoli Workload Scheduler forz/OS Agent workstation.


Defining a job in the JOBLIB data setHow to define a job in the JOBLIB data set

You define the jobs to be run on Tivoli Workload Scheduler for z/OS Agentworkstations in a job definition member of the JOBLIB data set. In the JOBLIBmember, you can either define the job contents or invoke a script or an executablethat is stored locally on the Tivoli Workload Scheduler for z/OS Agentworkstation. If you do not specify any content in the job definition member, theerror code JCLI is issued.

To define the job contents, the following syntax rules apply:v The lines that start with //* OPC, //*%OPC, or //*>OPC are used for variable

substitution and automatic recovery. They are removed before the script isdownloaded onto the Tivoli Workload Scheduler for z/OS Agent.

v Each line starts between column 1 and column 80.v The last backslash (\) in a line is considered the character of continuation.v Blanks at the end of the line are automatically removed.

Optionally, you can define the job properties by setting the “JOBREC” on page 75statement.

According to the job that you are defining, refer to Table 2 for a list of the requiredand optional keywords that apply.

Table 2. Jobs and their keywords

Job to be run Keywords

executable or scriptENVVAR (optional)INTRACTV (optional)JOBCMD (required for executable, optional for script)JOBPWD (optional)JOBUSR (optional)PARM (optional)STDERROR (optional)STDINPUT (optional)STDOUTPUT (optional)WRKDIR (optional)

xajobENVVAR (optional)JOBPWD (optional)JOBTYPE (required)JOBUSR (optional)PARM (optional)

j2ee jmsAUTHALIAS (optional)CONNFACTORY (required)DESTINATION (required)INVOKEYTYPE (optional)JOBPWD (optional)JOBTYPE (required)JOBUSR (optional)MESSAGE (optional)


Table 2. Jobs and their keywords (continued)

Job to be run Keywords

j2ee ejbAUTHALIAS (optional)INVOKEYTYPE (optional)JNDIHOME (required)JOBTYPE (required)JOBUSR (optional)

The following is an example of a JOBREC statement to invoke the scriptALLOCATE.BAT stored locally on the Tivoli Workload Scheduler for z/OS Agentworkstation.//JOBRECWRKDIR(C:\)STDERROR(D:\MYDIR\ERROR.TXT)STDINPUT(D:\MYDIR\INPUT.TXT)STDOUTPUT(D:\MYDIR\OUTPUT.TXT)STDOUTPUT(D:\MYDIR\NEWT.TXT)JOBCMD(EXECUTABLE)PARM(300)PARM2(ELEMENT)//END JOBRECD:\MYDIR\ALLOCATE.BAT

The following is an example of a JOBREC statement to run the command DIR onthe directory C:\PROGRAM on the Tivoli Workload Scheduler for z/OS Agentworkstation.//JOBRECWRKDIR(C:\PROGRAM)JOBCMD(SCRIPT)//END JOBRECDIR

The following is an example of a JOBREC statement to submit a JMS job.//JOBRECJOBTYPE(/j2ee/jms)INVOKEYTYPE(DIRECT)CONNFACTORY(jms/MyCF)DESTINATION(jms/MyQueue)MESSAGE(This is my message)JOBUSR(administrator)JOBPWD(YES)//END JOBREC

The following is an example of a JOBREC statement to submit an EJB job.//JOBRECJOBTYPE(/j2ee/ejb)INVOKEYTYPE(INDIRECT)JNDIHOME(ejb/test/scheduler/MyTest30BeanHome)AUTHALIAS(JAASauthenticationAlias)//END JOBREC

JOBRECJOBREC

Purpose

To define the properties of a job that must run on Tivoli Workload Scheduler forz/OS Agent workstations, you can use the JOBREC statement. This statement is


optional. If you omit it, Tivoli Workload Scheduler for z/OS runs the script on theTivoli Workload Scheduler for z/OS Agent working directory.

Use the following format://JOBRECkeyword(value)keyword(value)//END JOBREC

The following syntax rules apply:v The value of each keyword can continue over two or more lines.v The value of each keyword must be enclosed within parentheses. Therefore, any

character enclosed within parentheses is considered part of the keyword value,including blanks and single quotes.

v The script or executable must follow the //END JOBREC line.v If you specify the same keyword twice or more, only the last keyword specified

is considered valid.v You can insert any comment text by using //* as the starting characters.

Format

►► JOBRECAUTHALIAS ( authentication alias )

►

►CONNFACTORY ( connection factory )

►

►DESTINATION ( message destination )

►

► ▼

ENVVAR ( EnvVarName=value )ENVVARn ( EnvVarName=value )...

NOINTRACTV ( YES )

►

►DIRECT

INVOKEYTYPE ( INDIRECT )JNDIHOME ( JNDI home dir )

►

►SCRIPT

JOBCMD ( EXECUTABLE )NO

JOBPWD ( YES )

►


►JOBTYPE ( /xajob/<name of access method> )

/j2ee/jms/j2ee/ejb

►

►JOBUSR ( user name ) MESSAGE ( message )

►

► ▼

PARM ( parameter )PARMn ( parameter )...

STDERROR ( standard error file path )►

►STDINPUT ( standard input file path )

►

►STDOUTPUT ( standard output file path )

►

►WRKDIR ( working dir path )

►◄

Parameters

AUTHALIAS(authentication alias)The Java™ Authentication and Authorization Service (JAAS) authenticationalias. This keyword is meaningful only if you set INVOKEYTYPE(DIRECT).

CONNFACTORY(connection factory)The administered object that a client uses to create a connection to the JavaMessage Service (JMS) provider. This keyword is valid only if you setJOBTYPE(/j2ee/jms).

DESTINATION(message destination)The administered object that encapsulates the identity of a messagedestination, which is where messages are delivered and consumed. Thiskeyword is valid only if you set JOBTYPE(/j2ee/jms).

ENVVAR(EnvVarName=value)The environment variable that the task launcher must set before submitting thejob. Use the following format:ENVVARn(EnvVarName=value)

Where EnvVarName is the name of the environment variable and value is thevalue associated with it. It is case sensitive.

You can set more than one ENVVAR keyword by specifying ENVVARn.


INTRACTV(YES|NO)Specifies if a Windows job runs interactively on the Windows desktop. Thiskeyword is used only for jobs running on Windows Tivoli Workload Schedulerfor z/OS Agent workstations.

INVOKEYTYPE(INDIRECT|DIRECT)The type of scheduling. This keyword is valid only if you setJOBTYPE(/j2ee/ejb) or JOBTYPE(/j2ee/jms). Allowed values are:

INDIRECTTivoli Workload Scheduler for z/OS uses an existing WebSphere®

Application Server scheduling infrastructure already configured on anexternal WebSphere Application Server. Specify indirect scheduling toinvoke an EJB that does not contain roles. If the EJB contains roles, usedirect scheduling.

DIRECTTivoli Workload Scheduler for z/OS immediately forwards the job tothe components (EJB or JMS) of the external WebSphere ApplicationServer instance.

JNDIHOME(JNDI home dir)The complete path to the home directory of the Java Naming and DirectoryInterface (JNDI) application programming interface. Using JNDI, you canaccess different kinds of naming and directory services. J2EE componentslocate objects by invoking the JNDI lookup method.

This keyword is valid only if you set JOBTYPE(/j2ee/ejb).

JOBCMD(EXECUTABLE|SCRIPT)The content of the job definition member. Valid values are:

SCRIPTThe job definition member contains the command or script to be run.

EXECUTABLEThe job definition member invokes the job that is to be run, which isstored locally on the Tivoli Workload Scheduler for z/OS Agentworkstation. If you did not set any value for the WRKDIR keyword,you must specify the fully qualified path to the job.

JOBPWD(YES|NO)Specifies that the user name set in JOBUSR or by using the job-submit exitEQQUX001 is associated with a password. If you set JOBPWD to YES, TivoliWorkload Scheduler for z/OS searches for the user password in the USRPSWkeyword of the USRREC statement (for details, see Scheduling End-to-end withz-centric Capabilities).

Typically, the password is required for users who schedule jobs to run onWindows workstations. Set JOBPWD to NO if the user works with UNIXworkstations.

JOBTYPE(/xajob/name of access method|/j2ee/ejb|/j2ee/jms)According to the job that you want to run, one of the following values:

/xajob/name of access methodThe name of the access method hosted by the extended agent on whichyou want to submit the job. For example, for a job to be submitted ona SAP extended agent, this value could be /xajob/r3batch. If you setthis keyword, the JOBCMD keyword value is ignored.


/j2ee/ejbSet this value to submit an Enterprise Java Bean (EJB) job.

/j2ee/jmsSet this value to submit a Java Message Service (JMS) job.

JOBUSR(user name)For J2EE jobs, the WAS administrator. For all the other jobs, the name of theuser submitting the job.

If the user schedules jobs to run on Windows workstations, ensure that a userpassword is also defined (see the JOBPWD keyword). If you are defining aWindows domain user, use the following format:JOBUSR(domainName\user1)

To specify the user name, you can also use the job-submit exit EQQUX001.This user name overrides the value specified for JOBUSR. In turn, the valuespecified for JOBUSR overrides that specified for USRNAM in the USRRECstatement.

MESSAGE(message)The object that is sent from one application to another. This keyword is validonly if you set JOBTYPE(/j2ee/jms).

PARM(parameter)The parameter to be used when running the script or command. You can setmore than one PARM keyword by specifying PARMn.

STDERROR(standard error file path)The fully qualified name of the file where the standard error must beredirected.

STDINPUT(standard input file path)The fully qualified name of the file to be used as standard input.

STDOUTPUT(standard output file path)The fully qualified name of the file to be used as standard output.

WRKDIR(working dir path)The fully qualified path to the directory where the script or command is to berun.


Notices

This information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

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

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM websites are provided forconvenience only and do not in any manner serve as an endorsement of thosewebsites. The materials at those websites are not part of the materials for this IBMproduct and use of those websites is at your own risk.


IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

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

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

TrademarksIBM, the IBM logo, and ibm.com® are trademarks or registered trademarks ofInternational Business Machines Corporation in the United States, other countries,or both. If these and other IBM trademarked terms are marked on their firstoccurrence in this information with a trademark symbol (® or ™), these symbolsindicate U.S. registered or common law trademarks owned by IBM at the time thisinformation was published. Such trademarks may also be registered or commonlaw trademarks in other countries. A current list of IBM trademarks is available onthe Web at "Copyright and trademark information" at http://www.ibm.com/legal/copytrade.shtml.

Intel is a trademark of Intel Corporation in the United States, other countries, orboth.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.

Microsoft and Windows are registered trademarks of Microsoft Corporation in theUnited States, other countries, or both.


http://www.ibm.com/legal/copytrade.shtml

http://www.ibm.com/legal/copytrade.shtml

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Notices 83

Index

Special characters*, use in generic search arguments 10%, use in generic search arguments 10=, ISPF quick return command 8

Aaccessibility xadding

applications 61occurrences 61

adding applications to the current planpanel 62

all dependencies of an operation 52allocation status of special resources 21APARs

PK40969 6, 15PK48574 7

applicationsadding to the current plan 61application description 25

defining 26priority, specifying 27

creating 26group definition 25job description 25operations 30run cycles 28status 27types 25valid-from date 27

arrival time, specifying 34AUTHALIAS, keyword of JOBREC 77

Bbrowsing

application occurrences 48dependencies 43, 44most critical occurrences 52operation data 44

browsing most critical occurrences 52

Ccalendar

creating 18default in dialog 7free days 18general description 18work days 18work-day end time 19

CANCEL command 5changing operations in the current

plan 63checking

dependencies 51occurrences 48operations 50

commandsCANCEL 5concatenating 7LOCATE 11SORT 10TSAVE 18

confirming rerun of an occurrence 68CONNFACTORY, keyword of

JOBREC 77conventions used in publications ixcreating

current plan 45dependencies 41long-term plan 38occurrences 39

criteria for lists 9current plan

changing 61checking occurrences 48general description 45status inquiry 47

cycle specification for rules 30

Ddate, specifying format 7day specification for rules 30deadline, specifying 28defining

destinations 72dependencies, checking 51destinations 72dialog

introduction 5modify current plan 61options, setting 5overview 5parameters, setting 5query current plan 47

duration 18Dynamic Workload Console

accessibility x

Eediting JCL for an operation 59education xended-in-error operations 65ENVVAR, keyword of JOBREC 77error list 65EVERY options, specifying 30external predecessors 35

Ffast path 8, 9filter characters 10finding data in a list 11free days 18free-day rule 28

frequency specification for rules 30

GGENDAYS command 30generic search arguments 10glossary ix

Hhandling operations ended in error 66HELP command 9

IInteractive System Productivity Facility

(ISPF) 5internal predecessors 32interrupting workstation activity 18intervals for special resources 23INTRACTV, keyword of JOBREC 78INVOKEYTYPE, keyword of JOBREC 78ISPF (Interactive System Productivity

Facility)=, quick return command 8command delimiter 8concatenating options 8dialog manager 5setting options 5table services 5

JJ row command 66JCL

correcting 66preparing 59

JNDIHOME, keyword of JOBREC 78job description

creating 35DETAILS command 35RUN command 35

job, WTO and print options 33JOBCMD, keyword of JOBREC 78JOBLIB statements

JOBRECAUTHALIAS keyword 77CONNFACTORY keyword 77definition 75ENVVAR keyword 77INTRACTV keyword 78INVOKEYTYPE keyword 78JNDIHOME keyword 78JOBCMD keyword 78JOBPWD keyword 78JOBTYPE keyword 78JOBUSR keyword 79MESSAGE keyword 79PARM keyword 79


JOBLIB statements (continued)JOBREC (continued)

STDERROR keyword 79STDINPUT keyword 79STDOUTPUT keyword 79WRKDIR keyword 79

JOBPWD, keyword of JOBREC 78JOBREC statement of JOBLIB

AUTHALIAS keyword 77CONNFACTORY keyword 77definition 75ENVVAR keyword 77INTRACTV keyword 78INVOKEYTYPE keyword 78JNDIHOME keyword 78JOBCMD keyword 78JOBPWD keyword 78JOBTYPE keyword 78JOBUSR keyword 79MESSAGE keyword 79PARM keyword 79STDERROR keyword 79STDINPUT keyword 79STDOUTPUT keyword 79WRKDIR keyword 79

JOBTYPE, keyword of JOBREC 78JOBUSR, keyword of JOBREC 79

KKEYS command 9

Llists

criteria, specifying 9locating data 11sorting 10

LOCATE command 11locating data in a list 11long-term plan

batch updating 42browsing 43creating 37modify all 42modifying 39occurrences 37

LookAt message retrieval tool ix

Mmain menu 5maintaining databases 13MCP dialog 61message area 5message retrieval tool, LookAt ixMESSAGE, keyword of JOBREC 79modify current plan (MCP) dialog 61modifying

current plan 61dependencies 42occurrences in the current plan 63operations in the current plan 64

Ooccurrences

adding to the current plan 61adding to the long-term plan 39querying 48rerunning 67

on completespecial resources 21

OPER command 63operations

changing 63checking 50defining 30defining details 33in error 65input arrival time 34options 33predecessors, specifying 32querying 50rerunning 67time-dependent 34

operator instructions 59options and parameters, defining 5owner ID for applications 26

Ppanels

EQQLBATP 37EQQLBBDL 44EQQLBOCP 43EQQLBOPL 44EQQMAADL 62EQQMADDP 62EQQSAO1L 48EQQSAOSP 49EQQSMC1L 52EQQSOPGD 51EQQSOPSP 51fast path 9filter panels 9generic search arguments 10selection criteria 9

parallel servers 15, 16parameters and options, defining 5PARM, keyword of JOBREC 79PF keys 7, 8PFSHOW command 8PRED command 32predecessors, checking 51primary commands 63priority 27producing OPC daily plans 45publications ix

QQuery Current Plan (QCP) dialog 47

RR row command 67ready list 55

operator instructions 59row commands 58

recalling the last command 9rerunning an occurrence in the current

plan 67resources, allocation status 21RETRIEVE command 9ROUTOPTS 72row commands 58, 66, 67rules, modifying 29run cycle

creating, rule-based 27defining 28

run dates 29

Ssearching

*, use in generic search arguments 10%, use in generic search

arguments 10selecting all dependencies panel 51selecting application occurrence and

operation information panel 51Selecting Application Occurrence

Information panel 49selecting applications to add to the CP

panel 62Selecting Long Term Plan Batch Job

panel 37setting up JCL 59SORT command 10sorting items in a list 10special resources

allocation status 21connecting to workstations 23intervals 21max usage limit 21max usage type 21on complete 21

specifyingended-in-error list criteria 66further occurrence data 40list criteria 9

splittable workstation 18status

applications 27operation 51

STDERROR, keyword of JOBREC 79STDINPUT, keyword of JOBREC 79STDOUTPUT, keyword of JOBREC 79subsystem name, setting or changing 6successors, checking 51syntax diagrams, how to read xi

Ttechnical training xTEXT command 30time

input arrival 34specifications 34specifying format 7

Tivoli technical training xtraining

technical xTSAVE command 18


Vvalid-from date 27

Wwildcard characters 10work days 18, 19workstation

availability 16connecting to special resources 23creating 13, 17general description 13general information, computer 14general information, job setup 17job setup 17, 59open time intervals 16parallel servers 15, 16reporting attribute 14splittable 18types 13

WRKDIR, keyword of JOBREC 79

Index 87

IBM®

Product Number: 5698-T08

Printed in USA

SC32-1262-07

tivoli workload scheduler for z/os: getting started ... › support › knowledgecenter ›...

Documents