IBM

Tivoli

Workload

Scheduler

for

z/OS

Controlling

and

Monitoring

the

Workload

Version

8.1

(Maintenance

Release

October

2003)

SH19-4547-01

IBM

Tivoli

Workload

Scheduler

for

z/OS

Controlling

and

Monitoring

the

Workload

Version

8.1

(Maintenance

Release

October

2003)

SH19-4547-01

Note

Before

using

this

information

and

the

product

it

supports,

read

the

information

in

Notices

on

page

113.

Refreshed

Edition

(October

2003)

This

refreshed

edition

applies

to

version

8,

release

1,

modification

0

of

IBM

Tivoli

Workload

Scheduler

for

z/OS

(program

number

5697-WSZ)

and

to

all

subsequent

releases

and

modifications

until

otherwise

indicated

in

new

editions.

Contents

Figures

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. v

Tables

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. vii

Preface

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. ix

Maintenance

Release

.

.

.

.

.

.

.

.

.

.

. ix

Who

Should

Read

This

Guide

.

.

.

.

.

.

.

. ix

What

This

Guide

Contains

.

.

.

.

.

.

.

.

. ix

Publications

.

.

.

.

.

.

.

.

.

.

.

.

.

. x

Tivoli

Workload

Scheduler

for

z/OS

Library

.

.

. x

Using

LookAt

to

Look

Up

Message

Explanations

xi

Accessing

Publications

Online

.

.

.

.

.

.

. xi

Softcopy

Collection

Kit

.

.

.

.

.

.

.

.

.

. xi

Ordering

Publications

.

.

.

.

.

.

.

.

.

. xii

Providing

Feedback

about

Publications

.

.

.

. xii

Contacting

IBM

Software

Support

.

.

.

.

.

.

. xii

Required

Product

Knowledge

.

.

.

.

.

.

.

. xii

Conventions

Used

in

This

Guide

.

.

.

.

.

.

. xii

Chapter

1.

What

Is

the

Scheduler?

.

.

. 1

How

the

Scheduler

Works

.

.

.

.

.

.

.

.

.

. 1

How

Does

the

Scheduler

Keep

Track

of

Jobs?

.

. 3

How

Does

the

Scheduler

Help

with

Job

Preparation?

.

.

.

.

.

.

.

.

.

.

.

.

. 3

How

Can

the

Scheduler

Help

You

Recover

Jobs?

. 3

Can

the

Scheduler

Help

with

Online

Systems?

.

. 3

Can

You

Run

Jobs

outside

the

Scheduler?

.

.

.

. 4

Finding

Out

about

the

Scheduler

.

.

.

.

.

.

. 4

Chapter

2.

Using

the

Scheduler

Panels

7

The

Scheduler

ISPF

Panels

.

.

.

.

.

.

.

.

.

. 7

Setting

Options

.

.

.

.

.

.

.

.

.

.

.

. 8

Common

Panel

Commands

and

Facilities

.

.

. 13

Concatenating

Options

.

.

.

.

.

.

.

. 13

Quick

Return

Command

.

.

.

.

.

.

.

. 14

Primary

Commands

.

.

.

.

.

.

.

.

. 14

Specifying

List

Criteria

.

.

.

.

.

.

.

. 15

Using

Generic

Search

Arguments

.

.

.

.

. 16

Sorting

List

Output

.

.

.

.

.

.

.

.

.

. 16

Locating

Data

Strings

in

List

Output

.

.

.

. 17

Graphically

Displaying

Lists

.

.

.

.

.

.

. 17

PF

Key

Assignment

.

.

.

.

.

.

.

.

.

. 18

Tivoli

Job

Scheduling

Console

.

.

.

.

.

.

.

. 19

Utilities

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 19

Chapter

3.

Monitoring

the

Workload

.

. 21

Using

the

Ready

List

Panel

.

.

.

.

.

.

.

.

. 21

Selecting

a

Ready

List

Layout

.

.

.

.

.

.

. 21

Creating

Your

Own

Ready

List

Layout

.

.

.

. 22

Ready

List

Layout

User

Exit

.

.

.

.

.

.

.

. 24

Invoking

the

User

Exit

from

the

Panels

.

.

. 24

Defining

and

Setting

Up

the

User

Exit

.

.

. 24

Communicating

with

the

User

Interface

Routine

.

.

.

.

.

.

.

.

.

.

.

.

.

. 24

Using

the

Ready

List

.

.

.

.

.

.

.

.

.

.

. 26

Setting

the

Status

of

an

Operation

.

.

.

.

.

. 27

Letting

the

Scheduler

Assign

the

Next

Status

27

Setting

the

Status

Explicitly

.

.

.

.

.

.

. 27

Resetting

an

Operation

to

Its

Previous

State

27

Interrupting

an

Operation

.

.

.

.

.

.

. 28

Reporting

an

Operation

As

Ended-in-error

.

. 28

Viewing

Operator

Instructions

.

.

.

.

.

.

. 28

Preparing

Jobs

at

a

Setup

Workstation

.

.

.

. 28

Preparing

Jobs

without

Unresolved

Promptable

Variables

.

.

.

.

.

.

.

.

. 29

Preparing

Jobs

with

Unresolved

Promptable

Variables

.

.

.

.

.

.

.

.

.

.

.

.

. 30

Other

Ways

of

Editing

a

Job

.

.

.

.

.

.

. 31

Delaying

an

Operation,

and

Releasing

It

.

.

.

. 32

Removing

an

Operation

from

the

Current

Plan

and

Restoring

It

.

.

.

.

.

.

.

.

.

.

.

. 32

Running

an

Operation

Immediately

with

EXECUTE

.

.

.

.

.

.

.

.

.

.

.

.

.

. 33

Diagnosing

Delays

.

.

.

.

.

.

.

.

.

.

. 34

The

QCP

Panel

.

.

.

.

.

.

.

.

.

.

.

.

. 35

Querying

Application

Occurrences

.

.

.

.

.

. 35

Querying

Operation

Information

.

.

.

.

.

. 37

Checking

the

Status

of

a

Workstation

.

.

.

.

. 38

Checking

the

Status

of

the

Current

Plan

.

.

.

. 39

Chapter

4.

Updating

the

Current

Plan

41

Using

Fast

Paths

.

.

.

.

.

.

.

.

.

.

.

.

. 42

Accessing

the

Modify

Current

Plan

Panel

.

.

.

. 43

Specifying

Selection

Criteria

.

.

.

.

.

.

.

.

. 43

Running

Work

on

Request

.

.

.

.

.

.

.

.

. 43

Adding

Occurrences

to

the

Current

Plan

.

.

. 44

Selecting

Occurrences

.

.

.

.

.

.

.

.

. 44

Adding

Occurrences

.

.

.

.

.

.

.

.

. 45

Specifying

an

Error

Code

.

.

.

.

.

.

.

. 47

Including

Dependencies

Defined

in

the

Database

.

.

.

.

.

.

.

.

.

.

.

.

. 47

Changing

and

Adding

Dependencies

.

.

.

. 48

Grouping

Occurrences

.

.

.

.

.

.

.

.

. 51

Adding

an

Application

Group

to

the

Current

Plan

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 51

Excluding

Some

Applications

.

.

.

.

.

. 51

Specifying

Dependency

Resolution

.

.

.

. 52

Restarting

an

Occurrence

from

the

Beginning

.

. 53

Rerunning

an

Occurrence

in

the

Current

Plan

from

a

Specific

Operation

.

.

.

.

.

.

.

.

. 54

Completing

an

Application

Occurrence

.

.

.

. 57

Deleting

an

Application

Occurrence

.

.

.

.

. 57

Modifying

an

Application

Occurrence

.

.

.

. 57

Changing

External

Dependencies

to

an

Occurrence

.

.

.

.

.

.

.

.

.

.

.

. 58

Changing

Dependencies

to

an

Operation

.

. 58

Changing

the

Details

of

an

Operation

.

.

. 58

Adding

and

Deleting

Operations

.

.

.

.

. 59

Modifying

an

Operation

.

.

.

.

.

.

.

.

.

. 59

iii

||

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

Rerunning

Operations

in

the

History

Database

.

. 60

Updating

the

History

Database

.

.

.

.

.

.

. 60

Processing

History

Operations

.

.

.

.

.

.

. 60

Selecting

a

History

Operation

.

.

.

.

.

. 61

Informing

the

Scheduler

of

Unplanned

Changes

in

Resources

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 62

Keeping

Plans

Up-to-date

.

.

.

.

.

.

.

.

. 63

Fault-tolerant

Workstations

and

Replanning

.

. 63

Changing

Workstation

Availability

.

.

.

.

.

.

. 65

Active

and

Inactive

Computer

Workstations

.

. 65

Redirecting

Work

to

Alternate

Workstations

.

. 66

Browsing

System

Information

.

.

.

.

.

.

. 68

Chapter

5.

Handling

Operations

that

End

in

Error

.

.

.

.

.

.

.

.

.

.

.

. 69

Displaying

the

Ended-in-error

List

for

Action

.

.

. 69

Selecting

an

Ended-in-error

List

Layout

.

.

.

. 70

Creating

Your

Own

Ended-in-error

List

Layout

70

Getting

Rerun

or

Recovery

Instructions

.

.

.

.

. 72

Completing

an

Ended-in-error

Operation

.

.

.

. 72

Modifying

a

Job

That

Has

Failed

.

.

.

.

.

.

. 72

Restarting

Ended-in-error

Operations

.

.

.

.

.

. 72

Restarting

Ended-in-error

Operations

Managing

Cleanup

Action

.

.

.

.

.

.

.

.

.

.

.

.

. 73

Taking

Action

at

the

Occurrence

Level

.

.

.

. 74

Handling

Operations

with

the

OSEQ

Error

Code

74

Restarting

an

Operation

from

a

Certain

Step

.

.

. 75

Using

Cleanup

Options

.

.

.

.

.

.

.

.

. 76

Specifying

Automatic

Restart

for

Operations

That

Fail

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 77

Chapter

6.

Monitoring

Special

Resources

.

.

.

.

.

.

.

.

.

.

.

.

. 79

Understanding

Special

Resources

.

.

.

.

.

.

. 79

Example

Using

Data

Sets

.

.

.

.

.

.

.

.

. 80

Example

Using

Tape

Drives

.

.

.

.

.

.

.

. 81

Example

Using

Communication

Lines

.

.

.

. 82

How

Does

the

Scheduler

Use

Special

Resources?

82

Using

the

Special

Resource

Monitor

.

.

.

.

.

. 83

Understanding

Availability

Intervals

.

.

.

.

. 83

Accessing

the

Special

Resource

Monitor

.

.

.

. 84

Looking

at

the

Operations

Waiting

for

a

Resource

86

Modifying

a

Special

Resource

.

.

.

.

.

.

. 88

Chapter

7.

Using

Tivoli

Business

Systems

Manager

.

.

.

.

.

.

.

.

.

. 91

Enabling

Monitoring

by

Tivoli

Business

Systems

Manager

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 91

Scheduler

Start

Options

.

.

.

.

.

.

.

.

. 91

Identifying

Jobs

for

Monitoring

.

.

.

.

.

.

. 92

Setting

Monitors

from

the

ISPF

Panels

.

.

.

. 92

Setting

Monitors

from

the

Programming

Interface

93

Setting

Monitors

from

the

Job

Scheduling

Console

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 93

How

Monitoring

Works

.

.

.

.

.

.

.

.

.

. 94

Discovery

of

the

Scheduler

.

.

.

.

.

.

.

.

. 94

Appendix

A.

Supported

z/OS

Commands

.

.

.

.

.

.

.

.

.

.

.

.

. 95

Starting

the

Scheduler

.

.

.

.

.

.

.

.

.

.

. 95

Stopping

the

Scheduler

.

.

.

.

.

.

.

.

.

. 95

Canceling

the

Scheduler

.

.

.

.

.

.

.

.

.

. 96

Modifying

the

Scheduler

.

.

.

.

.

.

.

.

.

. 96

Modifying

the

Data

Store

.

.

.

.

.

.

.

.

. 101

Appendix

B.

Status,

Error,

and

Reason

Codes

.

.

.

.

.

.

.

.

.

.

. 103

Occurrence

Status

Codes

.

.

.

.

.

.

.

.

. 103

Operation

Status

and

Extended

Status

Codes

103

Operation

Status

Codes

.

.

.

.

.

.

.

. 103

Extended

Status

Codes

.

.

.

.

.

.

.

. 103

Error

Codes

.

.

.

.

.

.

.

.

.

.

.

.

.

. 104

Job

Log

Retrieval

Status

Codes

.

.

.

.

.

.

. 106

Operation

Reason

Codes

.

.

.

.

.

.

.

. 106

Appendix

C.

Fields

Displayed

in

Ready

and

Error

Lists

.

.

.

.

.

.

.

. 109

Notices

.

.

.

.

.

.

.

.

.

.

.

.

.

. 113

Trademarks

.

.

.

.

.

.

.

.

.

.

.

.

.

. 114

Glossary

.

.

.

.

.

.

.

.

.

.

.

.

. 115

Index

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 123

iv

Controlling

and

Monitoring

the

Workload

||||

Figures

1.

A

Rolling

Long-term

Plan

.

.

.

.

.

.

.

. 2

2.

Extending

the

Current

Plan

.

.

.

.

.

.

. 2

3.

EQQOPCAPMain

Menu

.

.

.

.

.

.

.

. 7

4.

EQQXOPTPDefining

Parameters

and

Options

8

5.

EQQXDATPSetting

Date

and

Time

Format

9

6.

EQQXCOLPSetting

Color

and

Highlight

Attributes

.

.

.

.

.

.

.

.

.

.

.

.

. 10

7.

EQQXAOIPSetting

AD/OI

Consistency

Check

.

.

.

.

.

.

.

.

.

.

.

.

.

. 12

8.

EQQXJCLPSetting

JCL

Edit

Tool

Information

13

9.

EQQSOPFPSelecting

Operations

.

.

.

.

. 15

10.

EQQXSRTLSorting

a

List

.

.

.

.

.

.

. 17

11.

ISPOPT3BPF

Key

Definitions

and

Labels

19

12.

EQQXSUBPGenerating

JCL

for

a

Batch

Job

20

13.

EQQRTOPPCommunicating

with

Workstations

.

.

.

.

.

.

.

.

.

.

.

. 21

14.

EQQRSRLPSpecifying

Ready

List

Criteria

22

15.

EQQRLYLLReady

List

Layouts

.

.

.

.

. 23

16.

EQQRLYCLCreating

a

Ready

List

Layout

23

17.

EQQRLRLMReady

List

.

.

.

.

.

.

.

. 26

18.

EQQRJCLEEditing

JCL

for

an

Operation

29

19.

EQQRLVALList

of

JCL

Preparation

Variables

to

Be

Set

.

.

.

.

.

.

.

.

.

.

.

.

. 30

20.

EQQRJCLEEditing

JCL

for

an

Operation

31

21.

EQQSOPSPSelecting

Application

Occurrence

and

Operation

Information

.

.

.

.

.

.

. 34

22.

EQQSTOPPCurrent

Plan

and

Status

Inquiry

35

23.

EQQSAOSPSelecting

Application

Occurrence

Information

.

.

.

.

.

.

.

.

.

.

.

. 36

24.

EQQSMC1LBrowsing

Most

Critical

Occurrences

.

.

.

.

.

.

.

.

.

.

.

. 37

25.

EQQSOPSPSelecting

Application

Occurrence

and

Operation

Information

.

.

.

.

.

.

. 38

26.

EQQSPG1LAll

Dependencies

of

an

Operation

(Left

Part)

.

.

.

.

.

.

.

.

. 38

27.

EQQSWSSPBrowsing

Summary

of

Activities

at

a

Workstation

.

.

.

.

.

.

.

.

.

.

. 39

28.

EQQSGCPPBrowsing

General

Current

Plan

Information

.

.

.

.

.

.

.

.

.

.

.

. 40

29.

EQQMTOPPModifying

the

Current

Plan

43

30.

EQQMADDPAdding

Applications

to

the

Current

Plan

.

.

.

.

.

.

.

.

.

.

.

. 44

31.

EQQMAADLSelecting

Applications

to

Add

to

the

CP

.

.

.

.

.

.

.

.

.

.

.

.

. 45

32.

EQQMAOCPAdding

an

Application

to

the

Current

Plan

.

.

.

.

.

.

.

.

.

.

.

. 46

33.

EQQMMOPLModifying

Operations

in

the

Current

Plan

.

.

.

.

.

.

.

.

.

.

.

. 49

34.

EQQMMODPModifying

an

Operation

in

the

Current

Plan

.

.

.

.

.

.

.

.

.

.

.

. 49

35.

EQQMMADPCreating

a

Dependency

in

the

Current

Plan

.

.

.

.

.

.

.

.

.

.

.

. 50

36.

EQQMMDLLDefining

Dependencies

in

the

Current

Plan

.

.

.

.

.

.

.

.

.

.

.

. 50

37.

EQQMAAGLAdding

an

Occurrence

Group

to

the

CP

.

.

.

.

.

.

.

.

.

.

.

.

. 51

38.

EQQMAMOLModifying

Occurrences

Added

to

the

Current

Plan

.

.

.

.

.

.

.

.

.

. 53

39.

EQQMOCLLModifying

Occurrences

in

the

Current

Plan

.

.

.

.

.

.

.

.

.

.

.

. 53

40.

EQQMROCLRerunning

an

Occurrence

in

the

Current

Plan

.

.

.

.

.

.

.

.

.

.

.

. 55

41.

EQQRCLSEOperation

Restart

and

Cleanup

55

42.

EQQMOSTLList

Dependency

Status

Change

56

43.

EQQMOPRLModifying

Operations

in

the

Current

Plan

.

.

.

.

.

.

.

.

.

.

.

. 59

44.

EQQHISTLOperations

History

List

.

.

.

. 61

45.

EQQHIPUPSpecifying

Occurrence

Input

Arrival

.

.

.

.

.

.

.

.

.

.

.

.

.

. 62

46.

EQQMWSLLModifying

Work

Stations

in

the

Current

Plan

.

.

.

.

.

.

.

.

.

.

.

. 64

47.

EQQMWSRPModifying

a

Workstation

in

the

Current

Plan

.

.

.

.

.

.

.

.

.

.

.

. 67

48.

EQQMWSVPModifying

Workstation

Status

in

the

Current

Plan

.

.

.

.

.

.

.

.

.

. 67

49.

EQQMWSOLModifying

Open

Time

Intervals

in

the

CP

.

.

.

.

.

.

.

.

.

.

.

.

. 68

50.

EQQMEP1LHandling

Operations

Ended

in

Error

(Left

Part)

.

.

.

.

.

.

.

.

.

.

. 69

51.

EQQMERRPSpecifying

Ended

In

Error

List

Criteria

.

.

.

.

.

.

.

.

.

.

.

.

.

. 70

52.

EQQELYLLSelecting

an

Error

List

Layout

71

53.

EQQELYCLCreating

an

Error

List

Layout

71

54.

EQQRCLSEOperation

Restart

and

Cleanup

73

55.

EQQMERTPConfirm

Restart

.

.

.

.

.

. 74

56.

EQQMERSLStep

Restart

Selection

List

75

57.

EQQMCMDLModifying

Cleanup

Actions

77

58.

An

example

of

RECOVER

statements

.

.

.

. 78

59.

EQQQMSEPSpecifying

Resource

Monitor

List

Criteria

.

.

.

.

.

.

.

.

.

.

.

. 84

60.

EQQQMLSLSpecial

Resource

Monitor

85

61.

EQQQMIMLSpecial

Resource

Monitor

-

In

Use

List

.

.

.

.

.

.

.

.

.

.

.

.

.

. 86

62.

EQQQMWMLSpecial

Resource

Monitor

-

Waiting

Queue

.

.

.

.

.

.

.

.

.

.

. 87

63.

EQQQMMOPModifying

a

Special

Resource

88

64.

EQQQDIMLModifying

Intervals

for

a

Special

Resource

.

.

.

.

.

.

.

.

.

.

. 89

65.

EQQQDWMLModifying

Connected

Workstations

for

a

Special

Resource

.

.

.

. 90

66.

EQQAMJBPJob,

WTO,

and

Print

Options

panel

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 92

67.

EQQSOPDPBrowsing

Detailed

Operation

Information

.

.

.

.

.

.

.

.

.

.

.

. 93

v

|

|

|

|

|

|

vi

Controlling

and

Monitoring

the

Workload

Tables

1.

List

of

Publications

.

.

.

.

.

.

.

.

.

. x

2.

Primary

Commands

for

the

Panels

.

.

.

.

. 14

3.

Using

the

Modify

Current

Plan

panel

.

.

.

. 41

4.

Codes

for

the

Ability

to

Restart

a

Step

.

.

. 75

5.

How

Attributes

Are

Preserved

across

Intervals

83

6.

Keyword

and

Owner

Combinations

.

.

.

. 101

7.

Fields

Available

for

Display

in

Ready

and

Error

Lists

.

.

.

.

.

.

.

.

.

.

.

. 109

vii

||

viii

Controlling

and

Monitoring

the

Workload

Preface

This

book

shows

you

how

to

use

the

Interactive

System

Productivity

Facility

(ISPF)

panels

of

Tivoli

Workload

Scheduler

for

z/OS

to

run

and

control

planned

and

ad

hoc

jobs.

Your

workload

can

run

on

various

platforms,

but

you

control

it

from

a

central

z/OS

system

that

runs

the

controller

feature.

The

term

the

scheduler

when

used

in

this

book,

refers

to

Tivoli

Workload

Scheduler

for

z/OS.

The

term

DB2,

when

used

in

this

book,

also

includes

reference

to

DATABASE2

and

DB2

Universal

Database.

Maintenance

Release

This

is

a

maintenance

refresh

of

the

corresponding

IBM

Tivoli

Workload

Scheduler

for

z/OS

Version

8.1

manual,

form

number

SH19-4547-00.

It

contains

updates

for

the

following

APARS:

v

60113

v

68608

v

68665

v

70914

Throughout

the

book,

the

changed

or

new

sections

are

marked

by

revision

bars.

The

name

of

the

APAR

causing

the

information

change

is

also

featured

within

the

changed

chapter,

section,

or

paragraph.

If

your

version

of

the

product

has

not

been

fixed

for

a

particular

APAR,

refer

to

the

original

version

of

the

manual

for

the

corresponding

information.

Who

Should

Read

This

Guide

This

book

is

intended

for

those

involved

in

controlling

and

monitoring

the

workload

in

the

production

department

of

a

computer

installation.

It

explains

how

to

use

the

scheduler

for

these

tasks.

What

This

Guide

Contains

The

information

in

this

book

is

organized

as

follows:

v

Chapter

1,

What

Is

the

Scheduler?,

on

page

1

Introduces

you

to

the

scheduler.

This

chapter

explains

what

the

scheduler

is

and

how

it

works.

v

Chapter

2,

Using

the

Scheduler

Panels,

on

page

7

Explains

how

to

use

the

scheduler

ISPF

panels.

This

chapter

also

introduces

the

scheduler

utilities.

v

Chapter

3,

Monitoring

the

Workload,

on

page

21

Explains

how

to

use

the

Ready

List

panel

to

process

operations

that

are

ready

to

run

and

to

prepare

JCL

where

this

is

necessary.

It

also

explains

how

to

use

the

Query

Current

Plan

panel

to

display

operations

in

the

plan.

v

Chapter

4,

Updating

the

Current

Plan,

on

page

41

Explains

how

to

use

the

Modify

Current

Plan

panel

to

change,

add,

and

delete

operations

and

occurrences.

You

can

also

change

dependencies

and

rerun

jobs

in

the

current

plan

and

jobs

in

the

history

database.

ix

|

|||

|

|

|

|

|||||

v

Chapter

5,

Handling

Operations

that

End

in

Error,

on

page

69

Explains

what

to

do

when

an

operation

fails.

v

Chapter

6,

Monitoring

Special

Resources,

on

page

79

Explains

how

to

use

the

Special

Resource

Monitor

panel

to

change

resource

allocation

and

status.

v

Chapter

7,

Using

Tivoli

Business

Systems

Manager,

on

page

91

Explains

how

to

use

the

Tivoli

Business

Systems

Manager

to

monitor

and

manage

the

scheduler

installation.

v

Appendix

A,

Supported

z/OS

Commands,

on

page

95

Describes

the

supported

z/OS

commands.

v

Appendix

B,

Status,

Error,

and

Reason

Codes,

on

page

103

Explains

what

the

status,

error,

and

reason

codes

mean.

v

Appendix

C,

Fields

Displayed

in

Ready

and

Error

Lists,

on

page

109

Describes

the

fields

you

can

display

in

the

ready

list

and

in

the

error-handling

list.

Publications

This

book

is

part

of

an

extensive

Tivoli

Workload

Scheduler

for

z/OS

library.

The

books

in

this

library

can

help

you

use

the

product

more

effectively.

Tivoli

Workload

Scheduler

for

z/OS

Library

The

following

table

lists

the

publications

in

the

Tivoli

Workload

Scheduler

for

z/OS

library.

Table

1.

List

of

Publications

Task

Publication

Order

number

Planning

Tivoli

Workload

Scheduler

for

z/OS

Licensed

Program

Specifications

GH19-4540

Understanding

the

Tivoli

Workload

Scheduling

Suite

General

Information

GH19-4539

Using

the

Java

GUI

Tivoli

Job

Scheduling

Console

Users

Guide

SH19-4552

Using

the

Java

GUI

Tivoli

Job

Scheduling

Console

Release

Notes

GI10-5781

Interpreting

messages

and

codes

Messages

and

Codes

SH19-4548

Installing

Tivoli

Workload

Scheduler

for

z/OS

Installation

Guide

SH19-4543

Customizing

and

tuning

Tivoli

Workload

Scheduler

for

z/OS

Customization

and

Tuning

SH19-4544

Planning

and

scheduling

the

workload

Planning

and

Scheduling

the

Workload

SH19-4546

Learning

concepts

and

terminology

Getting

Started

SH19-4542

Writing

application

programs

Programming

Interfaces

SH19-4545

Quick

reference

Quick

Reference

GH19-4541

Diagnosing

failures

Diagnosis

Guide

and

Reference

LY19-6410

x

Controlling

and

Monitoring

the

Workload

Using

LookAt

to

Look

Up

Message

Explanations

LookAt

is

an

online

facility

that

lets

you

look

up

explanations

for

most

messages

you

encounter,

as

well

as

for

some

system

abends

and

codes.

Using

LookAt

to

find

information

is

faster

than

a

conventional

search

because

in

most

cases

LookAt

goes

directly

to

the

message

explanation.

You

can

access

LookAt

from

the

Internet

at:

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

or

from

anywhere

in

z/OS

or

z/OS.e

where

you

can

access

a

TSO/E

command

line

(for

example,

TSO/E

prompt,

ISPF,

z/OS

UNIX

System

Services

running

OMVS).

The

LookAt

Web

site

also

features

a

mobile

edition

of

LookAt

for

devices

such

as

Pocket

PCs,

Palm

OS,

or

Linux-based

handhelds.

So,

if

you

have

a

handheld

device

with

wireless

access

and

an

Internet

browser,

you

can

now

access

LookAt

message

information

from

almost

anywhere.

To

use

LookAt

as

a

TSO/E

command,

you

must

have

LookAt

installed

on

your

host

system.

You

can

obtain

the

LookAt

code

for

TSO/E

from

a

disk

on

your

(SK3T-4270)

or

from

the

LookAt

Web

sites

Download

link.

Accessing

Publications

Online

IBM

posts

publications

for

this

and

all

other

Tivoli

products,

as

they

become

available

and

whenever

they

are

updated,

to

the

Tivoli

Software

Information

Center

Web

site.

The

Tivoli

Software

Information

Center

is

located

at

the

following

Web

address:

http://publib.boulder.ibm.com/tividd/td/tdprodlist.html

Click

the

the

scheduler

link

to

access

the

product

library.

Note:

If

you

print

PDF

documents

on

other

than

letter-sized

paper,

select

the

Fit

to

page

check

box

in

the

Adobe

Acrobat

Print

dialog.

This

option

is

available

when

you

click

File

Print.

Fit

to

page

ensures

that

the

full

dimensions

of

a

letter-sized

page

print

on

the

paper

that

you

are

using.

Softcopy

Collection

Kit

All

the

books

in

the

Tivoli

Workload

Scheduler

for

z/OS

library,

except

the

licensed

publications,

are

available

in

displayable

softcopy

form

on

CD-ROM

in

the

following

Softcopy

Collection

Kit:

v

OS/390,

SK2T-6951

You

can

read

the

softcopy

books

on

CD-ROMs

using

these

IBM

licensed

programs:

v

Softcopy

Reader

v

BookManager

READ/2

v

BookManager

READ/DOS

v

BookManager

READ/6000

All

the

BookManager

programs

need

a

personal

computer

equipped

with

a

CD-ROM

disk

drive

(capable

of

reading

disks

formatted

in

the

ISO

9660

standard)

and

a

matching

adapter

and

cable.

For

additional

hardware

and

software

information,

refer

to

the

documentation

for

the

specific

BookManager

product

you

are

using.

Preface

xi

|

||||

||||

||||

|||

|

||||

|

|

||||

|

||||

||||||

|||||

http://www.ibm.com/eserver/zseries/zos/bkserv/lookat/http://publib.boulder.ibm.com/tividd/td/tdprodlist.html

Updates

to

books

between

releases

are

provided

in

softcopy

only.

Ordering

Publications

You

can

order

many

Tivoli

publications

online

at

the

following

Web

site:

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

You

can

also

order

by

telephone

by

calling

one

of

these

numbers:

v

In

the

United

States:

800-879-2755

v

In

Canada:

800-426-4968

In

other

countries,

see

the

following

Web

site

for

a

list

of

telephone

numbers:

http://www.ibm.com/software/tivoli/order-lit/

Providing

Feedback

about

Publications

If

you

have

comments

or

suggestions

about

Tivoli

products

and

documentation,

complete

the

customer

feedback

survey

at

the

following

Web

site:

http://www.ibm.com/software/sysmgmt/products/support

Contacting

IBM

Software

Support

If

you

have

a

problem

with

any

Tivoli

product,

you

can

contact

IBM

Software

Support.

See

the

IBM

Software

Support

Guide

at

the

following

Web

site:

http://techsupport.services.ibm.com/guides/handbook.html

The

guide

provides

information

about

how

to

contact

IBM

Software

Support,

depending

on

the

severity

of

your

problem,

and

the

following

information:

v

Registration

and

eligibility

v

Telephone

numbers

and

e-mail

addresses,

depending

on

the

country

in

which

you

are

located

v

Information

you

must

have

before

contacting

IBM

Software

Support

Required

Product

Knowledge

You

must

know

how

to

use

ISPF

and

TSO.

Conventions

Used

in

This

Guide

The

guide

uses

several

typeface

conventions

for

special

terms

and

actions.

These

conventions

have

the

following

meanings:

Information

type

Style

convention

Example

Commands

All

capital

letters

CREATE

References

in

the

text

to

fields

on

panels

All

capital

letters

QUANTITY

Input

you

should

type

in

panel

fields

Monospace

MYAPPLICATION

First

time

new

term

introduced

Italics

Application

xii

Controlling

and

Monitoring

the

Workload

|

|

|

|||

|

|

|

|

|

|

||

|

|

||

|

||

|

||

|

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgihttp://www.ibm.com/software/tivoli/order-lit/http://www.ibm.com/software/sysmgmt/products/supporthttp://techsupport.services.ibm.com/guides/handbook.html

Preface

xiii

xiv

Controlling

and

Monitoring

the

Workload

Chapter

1.

What

Is

the

Scheduler?

This

chapter

gives

a

description

of

the

scheduler

and

introduces

its

terminology.

Read

this

chapter

if

you

are

new

to

the

scheduler.

One

system

in

your

complex

is

designated

as

the

controlling

system:

it

runs

the

controller.

From

this

system,

you

can

automatically

plan,

control,

and

monitor

your

entire

production

workload.

All

the

systems

in

your

complex

must

run

the

tracker.

The

tracker

acts

as

the

communication

link

between

the

system

that

it

runs

on

and

the

controller.

How

the

Scheduler

Works

If

you

do

not

have

an

automated

planning

system

such

as

the

scheduler,

you

submit

jobs

on

request,

or

according

to

run

sheets.

If

they

fail,

you

correct

the

error

and

resubmit

them,

perhaps

after

running

recovery

jobs.

The

jobs

depend

on

many

conditions,

such

as:

v

Hardware,

such

as

tape

drives.

v

Online

systems,

such

as

Customer

Information

Control

System

(CICS).

Often

a

system

must

be

shut

down

before

a

batch

job

can

run.

v

Operating

system

resources,

such

as

job

entry

subsystem

(JES)

initiators,

that

you

need

to

run

a

job

of

the

correct

class.

v

Other

jobs.

You

cannot

run

the

job

to

print

pay

slips

until

the

payroll

tax

deduction

program

has

completed

successfully.

v

Job

parameters

that

you

must

change

each

run.

v

The

time

of

day.

v

The

day

of

the

week

or

year.

Some

jobs

must

be

run

on

Friday.

There

are

sometimes

complex

rules

that

specify

what

you

do

when

the

normal

day

is

a

holiday.

When

you

run

jobs

and

started

tasks

under

the

scheduler,

these

dependencies

are

defined

in

the

scheduler

databases

by

someone

in

your

enterprise

who

is

the

scheduler

administrator.

The

administrator

defines

your

workload

to

the

scheduler

like

this:

1.

Create

one

or

more

calendars

with

the

holidays

that

you

take.

2.

Define

applications,

which

are

sets

of

jobs

and

other

steps

such

as

job

preparation

and

print

processing.

Applications

can

themselves

be

grouped

into

application

groups.

3.

Create

a

long-term

plan

(LTP).

This

lists

all

occurrences

of

the

applications

that

will

run

in

a

long

period

of

typically

a

few

months

and

the

dependencies

among

them.

4.

Create

a

current

plan

(CP).

This

is

a

detailed

plan,

typically

for

one

day,

that

lists

the

applications

that

will

run

and

the

operations

in

each

application.

An

operation

can

be

a

computer

job,

but

it

can

also

be

any

other

operation

that

you

want

to

control

with

the

scheduler,

such

as

printing

and

job

preparation.

The

administrators

tasks

are

described

in

Planning

and

Scheduling

the

Workload.

You

work

mostly

with

the

current

plan.

It

is

created

by

a

batch

job,

usually

at

a

fixed

time

each

day.

The

current

plan

is

really

a

data

set

of

the

scheduler,

which

is

1

continually

updated

by

events

on

the

processors,

but

you

can

have

a

printed

plan,

which

is

a

report

that

is

produced

when

the

current

plan

is

created.

Strictly

speaking,

the

current

plan

is

created

only

once

and

the

daily

planning

process

is

called

extending

the

plan.

Extension

is

a

better

term

than

creation,

because

the

old

current

plan

is

also

part

of

the

new

current

plan.

Look

at

the

long-term

plan

in

Figure

1.

The

current

plan

should

always

stretch

for

some

hours

or

days

into

the

future.

Extend

the

current

plan

at

regular

intervals,

using

the

EXTEND

option

of

the

DAILY

PLANNING

menu.

You

can

extend

the

current

plan

to

a

fixed

date

and

time,

or

you

can

extend

it

by

a

period

of

hours

and

minutes.

Figure

2

shows

a

48-hour

current

plan.

The

initial

current

plan

lasts

48

hours:

every

morning,

the

current

plan

is

extended

by

a

further

24

hours.

Input

is

taken

from

both

the

long-term

plan

and

from

the

present

current

plan.

The

planning

performed

on

Tuesday

for

Tuesdays

work

considers

the

actual

situation

(both

completed

and

outstanding

work)

as

reflected

in

the

current

plan.

Jul Aug Sep Oct Nov

2001

Create the long-term plan

Extend the plan 28 days

Extend the plan another 28 days

Figure

1.

A

Rolling

Long-term

Plan

Figure

2.

Extending

the

Current

Plan

2

Controlling

and

Monitoring

the

Workload

The

extended

current

plan

always

keeps

uncompleted

application

occurrences,

but

the

current

plan

will

usually

be

about

48

hours

long,

extended

by

24

hours

every

24

hours.

How

Does

the

Scheduler

Keep

Track

of

Jobs?

The

scheduler

submits

jobs

to

the

operating

system.

The

scheduler-supplied

code

in

the

operating

system

(in

the

case

of

a

z/OS

tracker,

this

code

is

in

JES

and

System

Management

Facilities

[SMF]

exits)

tells

the

scheduler

when

the

jobs

have

finished

and

also

how

they

have

finished

(the

scheduler

looks

at

abend

and

return

codes

and

can

also

look

for

certain

error

messages

in

the

job

log

that

do

not

always

give

rise

to

nonzero

return

codes).

The

scheduler

calculates

the

latest

time

that

a

job

can

be

started

before

it

is

in

danger

of

missing

its

deadline.

The

scheduler

continually

adjusts

its

estimate

of

how

long

a

job

takes,

taking

the

actual

run

times

into

account.

When

a

job

or

other

operation

is

running

late,

the

scheduler

can

issue

alerts.

An

alert

can

be

a

message

to

the

operator

console,

but

it

can

also

trigger

other

events.

How

Does

the

Scheduler

Help

with

Job

Preparation?

The

scheduler

helps

in

two

ways:

v

Run-time

variables

can

often

be

automatically

substituted,

even

if

they

vary

from

run

to

run.

Many

such

variables

are

related

to

the

date,

and

the

scheduler

can

build

a

string

in

the

format

required

by

a

program.

v

When

jobs

need

manual

job

preparation,

the

administrator

specifies

a

job

setup

operation

as

a

predecessor

for

the

job

operation.

The

scheduler

does

not

submit

the

job

until

you

have

finished

preparing

the

job

statements.

Do

not

edit

and

submit

the

job

outside

the

scheduler.

Instead,

use

the

Ready

List

panel

to

edit

the

job:

the

scheduler

submits

the

job

for

you

when

you

have

prepared

the

job

(and

when

other

dependencies

have

been

met).

How

Can

the

Scheduler

Help

You

Recover

Jobs?

The

scheduler

supports

automatic

recovery

by

having

its

own

job

statements

that

take

effect

when

a

job

fails:

these

job

statements

look

like

comments

to

z/OS

and

JES.

For

jobs

tracked

on

a

z/OS

system,

the

scheduler

also

notices

when

the

catalog

has

been

updated

by

a

job

and

is

able

to

undo

the

catalog

updates

(step

by

step,

if

required)

to

the

point

before

the

job

ran,

for

all

data

sets

allocated

with

job

control

language

(JCL)

DD

statements.

This

facility

is

called

restart

and

cleanup.

For

example,

when

a

job

creates

a

data

set,

a

rerun

often

fails

because

the

data

set

already

exists.

With

cleanup

active

for

the

job,

the

scheduler

un-catalogs

and

deletes

the

data

set

before

resubmitting

the

job.

Can

the

Scheduler

Help

with

Online

Systems?

An

online

system,

such

as

a

CICS

system,

is

a

job

or

started

task,

so

it

can

be

started

like

any

other

operation

defined

to

the

scheduler.

Many

batch

applications

cannot

start

until

the

online

system

shuts

down.

One

advantage

of

defining

an

online

system

to

the

scheduler

is

that

a

batch

application

can

be

made

dependent

on

the

online

system

and

the

scheduler

can

start

the

batch

application

automatically

(assuming

other

dependencies

are

met)

when

the

online

system

ends.

Chapter

1.

What

Is

the

Scheduler?

3

The

scheduler

administrator

can

specify

that

the

scheduler

issues

a

message

when

an

operation

deadline

passes

before

the

operation

is

complete.

This

is

called

a

DEADLINE

WTO.

If

a

DEADLINE

WTO

is

specified

for

the

operation

representing

an

online

system

on

a

z/OS

system,

the

scheduler

sends

a

write-to-operator

(WTO)

message

to

the

operator

console

when

the

online

system

must

shut

down.

This

message

can

trigger

events

in

NetView,

such

as

the

broadcasting

of

a

Closing

in

5

minutes

message

to

online

users

and

the

initiation

of

the

shutdown

transaction

5

minutes

later.

Can

You

Run

Jobs

outside

the

Scheduler?

Jobs

fall

into

four

categories:

1.

Jobs

that

are

in

the

current

plan

and

are

submitted

by

the

scheduler.

These

are

scheduled

jobs,

or

jobs

that

you

have

added

to

the

current

plan

using

the

Modify

Current

Plan

(MCP)

panel.

2.

Jobs

that

are

in

the

current

plan,

but

are

not

submitted

by

the

scheduler.

These

are

usually

jobs

that

are

generated

and

submitted

by

some

other

subsystem,

such

as

CICS.

The

scheduler

can

track

these

jobs

and

take

account

of

the

resources

that

they

use.

It

is

also

possible

for

other

subsystems

to

submit

held

jobs

and

for

the

scheduler

to

release

them

when

all

dependencies

are

met.

3.

Jobs

that

are

not

submitted

by

the

scheduler,

but

trigger

events

in

the

scheduler.

These

jobs

are

specified

with

event-triggered

tracking

(ETT).

Refer

to

Planning

and

Scheduling

the

Workload

for

more

details

of

ETT.

4.

Jobs

that

are

completely

ignored

by

the

scheduler

controller.

One

disadvantage

of

having

jobs

outside

the

scheduler

(categories

3

and

4)

is

that

the

scheduler

cannot

take

account

of

the

resources

that

they

use.

The

scheduler

can

schedule

and

control

its

jobs

to

avoid

contention

for

resources

(such

as

tapes,

data

sets,

and

JES

initiators),

but

if

other

jobs

use

these

resources,

the

scheduler

may

submit

its

jobs

when

a

resource

is

unavailable.

Finding

Out

about

the

Scheduler

If

you

are

new

to

the

scheduler,

the

number

of

pages

in

its

library

can

be

daunting,

but

you

do

not

need

to

read

it

all.

Start

with

this

book,

using

the

index

and

the

table

of

contents

to

find

help

for

the

task

that

you

have

to

do.

Do

v

Read

the

reports

that

are

produced

when

the

current

plan

is

extended.

v

Use

the

panels,

especially

the

panels

mentioned

in

this

book

(Ready

List,

Query

Current

Plan,

and

Modify

Current

Plan),

to

find

out

more

about

the

scheduler

and

your

application

and

workstation

definitions.

v

Press

PF1

for

help

in

the

panels

when

you

need

additional

information.

v

Suggest

improvements

to

your

administrator

if

jobs

do

not

run

smoothly

or

if

you

very

often

have

to

make

changes

through

the

panels.

v

Tell

the

administrator

about

any

tasks

that

you

often

do

and

you

think

could

be

automated

by

the

scheduler.

v

Use

Getting

Started

for

a

quick

introduction

to

the

scheduler.

Do

not

v

Run

the

scheduler-controlled

jobs

(or

their

associated

job

preparation

tasks)

outside

the

scheduler,

except

where

this

is

planned.

4

Controlling

and

Monitoring

the

Workload

v

Attempt

to

get

work

going

by

changing

the

status

of

jobs

or

by

using

the

EXECUTE

command.

If

a

job

is

not

being

submitted,

there

must

be

a

reason:

use

the

scheduler

panels

to

find

the

reason

and

resolve

the

dependency.

Changing

the

status

of

an

operation

and

using

the

EXECUTE

command

are

for

exceptional

occasions.

Chapter

1.

What

Is

the

Scheduler?

5

6

Controlling

and

Monitoring

the

Workload

Chapter

2.

Using

the

Scheduler

Panels

To

perform

most

operator

tasks,

you

use

the

scheduler

panels,

which

run

under

Interactive

System

Productivity

Facility

(ISPF).

This

chapter

shows

you

how

to

get

help,

how

to

tailor

the

program

function

(PF)

keys

and

ISPF

options,

and

how

to

use

the

scheduler

filter

panels

to

reduce

the

amount

of

data

displayed

in

lists.

The

Scheduler

ISPF

Panels

How

you

invoke

the

panels

on

your

system

depends

on

your

installation

standards.

The

department

that

installed

the

scheduler

can

tell

you

how

to

invoke

the

scheduler

at

your

installation.

Usually,

you

select

the

scheduler

option

from

the

ISPF

main

menu.

The

scheduler

administration

is

performed

on

the

controlling

system

in

a

multisystem

complex,

so

you

must

use

the

panels

on

the

system

in

your

configuration

that

is

running

the

controller.

You

can

reach

all

the

controller

panels

from

the

scheduler

main

menu.

See

Figure

3.

Before

you

can

use

any

panel

in

the

scheduler,

you

must

have

the

authority

to

access

it.

See

your

security

administrator

or

system

programmer

if

you

do

not

have

the

access

that

you

need.

EQQOPCAP

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

OPERATIONS

PLANNING

AND

CONTROL

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

Option

===>

Welcome

to

OPC.

You

are

communicating

with

the

OPCC

subsystem.

Select

one

of

the

following

options

and

press

ENTER.

0

OPTIONS

-

Define

OPC

dialog

user

parameters

and

options

1

DATABASE

-

Display

or

update

OPC

data

base

information

2

LTP

-

Long

Term

Plan

query

and

update

3

DAILY

PLANNING

-

Produce

daily

plans,

real

and

trial

4

WORK

STATIONS

-

Work

station

communication

5

MCP

-

Modify

the

Current

Plan

6

QCP

-

Query

the

status

of

work

in

progress

7

OLD

OPERATIONS

-

Restart

old

operations

from

the

DB2

repository

9

SERVICE

FUNC

-

Perform

OPC

service

functions

10

OPTIONAL

FUNC

-

Optional

functions

X

EXIT

-

Exit

from

the

OPC

dialog

Figure

3.

EQQOPCAPMain

Menu

7

Setting

Options

You

do

not

have

to

set

options

every

time

you

use

the

panels.

The

options,

and

many

of

the

parameters

that

you

enter

in

the

panels,

are

saved

when

you

leave

ISPF

(though

not

if

the

session

is

not

terminated

normally)

and

will

be

the

default

next

time.

Select

option

0

on

the

main

menu

to

display

this

panel:

After

you

specify

the

options

you

prefer,

they

are

used

throughout

the

scheduler.

The

options

are

stored

in

your

ISPF

profile

data

set.

When

you

use

the

panels,

the

options

are

retrieved

from

your

profile.

REINIT

Use

this

option

to

set

the

scheduler

profile

to

the

default

values

defined

at

installation

time.

This

is

done

automatically

the

first

time

that

you

use

the

scheduler.

If

you

start

to

use

the

scheduler

for

a

new

language

feature,

perform

a

REINIT.

SUBSYSTEM

NAME

Select

this

option

to

specify

the

name

of

the

controller

subsystem

with

which

the

panels

are

to

communicate.

The

name

must

be

an

alphanumeric

string

of

not

more

than

4

characters.

If

the

controller

is

on

a

different

z/OS,

the

SERVER

LU

NAME

must

be

given.

The

logical

unit

(LU)

name

can

be

a

fully

qualified

LU

name

networkid.luname,

317

characters.

The

LU

name

is

sufficient

if

the

Server

is

on

the

same

net

as

the

panels.

DATE

Use

this

option

to

specify

the

format

of

dates

and

times

in

the

scheduler

and,

if

required,

to

set

a

local

time

offset.

The

following

panel

is

displayed:

EQQXOPTP

---------

DEFINING

OPC

PARAMETERS

AND

OPTIONS

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

Option

===>

Select

one

of

the

following:

0

REINIT

-

Re-initialize

the

application

profile

values

1

SUBSYSTEM

NAME

-

Set

or

change

name

of

Subsystem

and

Server

LU

2

DATE

-

Specify

date/time

formats

and

default

calendar

3

COLOR

-

Specify

panel

color

and

highlight

attributes

4

ISPF

OPTIONS

-

Specify

ISPF/PDF

options

5

AD/OI

CHECKS

-

Specify

AD/OI

consistency

checks

6

JCL

EDIT

-

Specify

JCL

edit

tool

7

CLEANUP

CHECK

-

Specify

check

option

for

Automatic

Cleanup

type

Figure

4.

EQQXOPTPDefining

Parameters

and

Options

8

Controlling

and

Monitoring

the

Workload

DATE-FORMAT

You

can

specify

dates

with

these

formats:

v

CCYYMMDD

or

YY/MM/DD,

where

CC

is

the

century.

CC,

YY,

MM,

and

DD

can

be

in

any

order.

v

YY/DDD

or

CCYY/DDD,

where

DDD

is

the

day

number

in

the

Julian

calendar.

CC,

YY,

and

DDD

can

be

in

any

order.

The

delimiter

character,

shown

as

a

slash

(/),

is

optional

and

can

be

any

character

other

than

C,

Y,

M,

or

D.

If

you

specify

CCYYMMDD,

you

cannot

use

delimiters.

The

date

format

can

be

no

more

than

8

characters.

Example

panels

in

this

book

use

the

format

YY/MM/DD.

TIME-FORMAT

Similarly,

you

can

specify

the

time

format

as

HH.MM

or

MM.HH.

The

delimiter

character,

shown

as

a

period

(.),

is

optional

and

can

be

any

character

other

than

H

or

M.

Example

panels

in

this

book

use

the

format

HH.MM.

DURATION-FORMAT

You

can

specify

hours

(HH),

minutes

(MM),

and

seconds

(SS)

or

minutes

(MMMM)

and

seconds

(SS).

Any

character

can

be

specified

as

a

separation

character.

LOCAL

TIME

OFFSET

If

you

are

in

a

different

time

zone

from

the

controller,

you

can

specify

a

local

time

offset.

This

means

that

actual

start

and

end

times

are

adjusted

to

take

your

local

time

into

consideration.

The

local

time

offset

is

the

number

of

minutes

your

local

time

is

ahead

of

or

behind

controller

subsystem

time;

that

is,

the

scheduler

controlling

processor

clock

time.

The

local

time

offset

specified

on

this

panel

applies

only

to

the

ISPF

profile

that

you

are

using.

EQQXDATP

-----------

SETTING

OPC

DATE

AND

TIME

FORMAT

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

Command

===>

Enter/change

data

below:

DATE-FORMAT

===>

YY/MM/DD

Combine

the

characters

for

year

(

YY

or

CCYY

),

and

month

(

MM

)

and

day

(

DD

),

or

day

number

(

DDD

).

You

can

use

separation

characters

(such

as

-

or

/)

if

space

permits.

TIME-FORMAT

===>

HH.MM

Combine

the

characters

for

hours(

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

OPC/ESA.

Specify

+

if

local

time

is

after

OPC/ESA

.

CALENDAR

ID

===>

________________

Default

calendar

identification

Figure

5.

EQQXDATPSetting

Date

and

Time

Format

Chapter

2.

Using

the

Scheduler

Panels

9

Note:

All

time

values

stored

in

controller

data

sets

are

specified

in

controller

subsystem

time

so

that

you

cannot,

for

example,

use

the

local-time

offset

option

to

specify

or

display

workstation

open

intervals,

input

arrival

times,

or

run-cycle

start

times,

in

your

local

time.

Reports

created

by

the

scheduler

batch

jobs

always

have

time

values

expressed

in

controller

subsystem

time

and

not

your

local

time.

TIME

OFFSET

SIGN

This

option

is

used

with

LOCAL

TIME

OFFSET

to

specify

whether

your

local

time

is

ahead

of

or

behind

the

scheduler

controller

subsystem

time.

For

example,

you

specify

+

if

your

local

time

is

ahead

of

controller

subsystem

time.

CALENDAR

ID

Specify

the

default

calendar

that

the

scheduler

uses

for

panel

functions

such

as

the

Long

Term

Plan

panel,

the

GENDAYS

command

for

checking

run

cycles,

and

substituting

job

control

language

(JCL)

variables

at

job

setup.

For

batch

functions,

the

scheduler

uses

the

calendar

specified

in

the

BATCHOPT

initialization

statement.

In

both

cases,

the

scheduler

looks

for

a

calendar

called

DEFAULT

if

no

other

calendar

is

specified.

For

some

functions

(ETT

and

the

EQQUSIN

subroutine),

the

scheduler

has

no

access

to

BATCHOPT

or

the

panel

default,

so

the

scheduler

always

looks

for

the

calendar

DEFAULT

if

no

calendar

is

specified.

If

no

calendar

is

specified

and

there

is

no

calendar

called

DEFAULT,

the

scheduler

treats

all

days

as

work

days.

COLOR

Select

this

option

to

display

this

panel,

where

you

specify

color

and

highlighting

attributes

for

different

panel

elements:

EQQXCOLP

------

SETTING

OPC/ESA

COLOR

AND

HIGHLIGHT

ATTRIBUTES

---------

Command

===>

Enter/change

data

below:

COLOR

HILITE

PANEL

ELEMENT

CATEGORY

WHITE__

_______

Panel

titles

and

data

items

BLUE___

_______

Directional

lines

and

explanatory

text

BLUE___

REVERSE

Header

text

WHITE__

_______

Option

numbers

and

command

text

BLUE___

_______

Normal

status

(for

instance

output

text)

WHITE__

_______

Important

status

(for

instance

output

data)

RED____

_______

Command

input

GREEN__

_______

Optional

input

RED____

_______

Required

input

RED____

BLINK__

Error

flagged

input

Valid

color

specifications

are:

WHITE,

RED,

BLUE,

GREEN,

PINK,

YELLOW,

and

TURQ

Valid

highlight

specifications

are:

USCORE,

REVERSE,

BLINK,

and

blank

for

no

highlighting

Figure

6.

EQQXCOLPSetting

Color

and

Highlight

Attributes

10

Controlling

and

Monitoring

the

Workload

The

panels

have

different

panel

elements;

for

example,

the

title

of

the

panel

and

the

command

input

field.

For

each

of

these

elements,

you

can

specify

color

and

highlighting.

If

you

set

a

color

to

blank,

the

installation

default

is

used.

To

test

the

effect

of

the

color

and

highlighting

attributes,

press

Enter

to

re-display

the

panel

with

the

specified

attributes.

All

panel

elements

in

the

scheduler

are

subsequently

displayed

with

the

attributes

specified

on

this

panel.

You

can

also

use

the

COLOR

command

at

any

time.

ISPF

OPTIONS

Select

this

option

on

the

Defining

OPC

Parameters

and

Options

panel

to

change

the

following:

TERMINAL

Specify

these

terminal

characteristics:

v

Terminal

type

v

Number

of

PF

keys

v

Input

field

pad

characters:

nulls

or

blanks

v

Command

delimiter

for

stacking

commands

v

Screen

format.

LOG/LIST

Specify

the

log

data

set

and

list

data

set

options,

print

process

options,

and

job

statement

information

for

the

system

printer.

PF

KEYS

Specify

the

number

of

PF

keys

and

the

operations

they

will

perform.

DISPLAY

Specify

whether

the

command

line

is

to

be

placed

at:

v

The

top

(ASIS)

of

the

panel

(as

shown