IBM

Tivoli

Workload

Scheduler

Reference

Guide

Version

8.1

(Maintenance

Release

October

2003)

SH19-4556-01

IBM

Tivoli

Workload

Scheduler

Reference

Guide

Version

8.1

(Maintenance

Release

October

2003)

SH19-4556-01

Tivoli

Workload

Scheduler

Reference

Guide,

Version

8.1

Copyright

Notice

Copyright

IBM

Corporation

1993,

2001.

All

rights

reserved.

May

only

be

used

pursuant

to

a

Tivoli

Systems

Software

License

Agreement,

an

IBM

Software

License

Agreement,

or

Addendum

for

Tivoli

Products

to

IBM

Customer

or

License

Agreement.

No

part

of

this

publication

may

be

reproduced,

transmitted,

transcribed,

stored

in

a

retrieval

system,

or

translated

into

any

computer

language,

in

any

form

or

by

any

means,

electronic,

mechanical,

magnetic,

optical,

chemical,

manual,

or

otherwise,

without

prior

written

permission

of

IBM

Corporation.

IBM

Corporation

grants

you

limited

permission

to

make

hardcopy

or

other

reproductions

of

any

machine-readable

documentation

for

your

own

use,

provided

that

each

such

reproduction

shall

carry

the

IBM

Corporation

copyright

notice.

No

other

rights

under

copyright

are

granted

without

prior

written

permission

of

IBM

Corporation.

The

document

is

not

intended

for

production

and

is

furnished

as

is

without

warranty

of

any

kind.

All

warranties

on

this

document

are

hereby

disclaimed,

including

the

warranties

of

merchantability

and

fitness

for

a

particular

purpose.

U.S.

Government

Users

Restricted

RightsUse,

duplication

or

disclosure

restricted

by

GSA

ADP

Schedule

Contract

with

IBM

Corporation.

Trademarks

IBM,

Tivoli,

the

Tivoli

logo,

AIX,

AS/400,

and

NetView

are

trademarks

or

registered

trademarks

of

International

Business

Machines

Corporation

or

Tivoli

Systems

Inc.

in

the

United

States,

other

countries,

or

both.

Microsoft,

Windows,

and

Windows

NT

are

trademarks

of

Microsoft

Corporation

in

the

United

States,

other

countries,

or

both.

UNIX

is

a

registered

trademark

of

The

Open

Group

in

the

United

States

and

other

countries.

Java

and

all

Java-based

trademarks

and

logos

are

trademarks

or

registered

trademarks

of

Sun

Microsystems,

Inc.

in

the

United

States

and

other

countries.

Other

company,

product,

and

service

names

may

be

trademarks

or

service

marks

of

others.

Notices

References

in

this

publication

to

Tivoli

Systems

or

IBM

products,

programs,

or

services

do

not

imply

that

they

will

be

available

in

all

countries

in

which

Tivoli

Systems

or

IBM

operates.

Any

reference

to

these

products,

programs,

or

services

is

not

intended

to

imply

that

only

Tivoli

Systems

or

IBM

products,

programs,

or

services

can

be

used.

Subject

to

valid

intellectual

property

or

other

legally

protectable

right

of

Tivoli

Systems

or

IBM,

any

functionally

equivalent

product,

program,

or

service

can

be

used

instead

of

the

referenced

product,

program,

or

service.

The

evaluation

and

verification

of

operation

in

conjunction

with

other

products,

except

those

expressly

designated

by

Tivoli

Systems

or

IBM,

are

the

responsibility

of

the

user.

Tivoli

Systems

or

IBM

may

have

patents

or

pending

patent

applications

covering

subject

matter

in

this

document.

The

furnishing

of

this

document

does

not

give

you

any

license

to

these

patents.

You

can

send

license

inquiries,

in

writing,

to

the

IBM

Director

of

Licensing,

IBM

Corporation,

North

Castle

Drive,

Armonk,

New

York

10504-1785,

U.S.A.

ISO

9001

Certification

This

product

was

developed

using

an

ISO

9001

certified

quality

system.

Certification

has

been

awarded

by

Bureau

Veritas

Quality

International

(BVQI)

(Certification

No.

BVQI

-

92086

/

A).

BVQI

is

a

world

leader

in

quality

certification

and

is

currently

recognized

by

more

than

20

accreditation

bodies.

iii

iv

Tivoli

Workload

Scheduler

Reference

Guide

Contents

Preface

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. ix

Maintenance

Release

.

.

.

.

.

.

.

.

.

.

. ix

Who

Should

Read

This

Guide

.

.

.

.

.

.

.

. ix

What

This

Guide

Contains

.

.

.

.

.

.

.

.

. ix

Publications

.

.

.

.

.

.

.

.

.

.

.

.

.

. x

Tivoli

Workload

Scheduler

Library

.

.

.

.

.

. x

Accessing

Publications

Online

.

.

.

.

.

.

. x

Ordering

Publications

.

.

.

.

.

.

.

.

.

. xi

Providing

Feedback

about

Publications

.

.

.

. xi

Contacting

IBM

Software

Support

.

.

.

.

.

.

. xi

Conventions

Used

in

This

Guide

.

.

.

.

.

.

. xi

Typeface

Conventions

.

.

.

.

.

.

.

.

.

. xi

Operating

System-dependent

Variables

and

Paths

xii

Chapter

1.

The

Production

Cycle

.

.

.

. 1

Automating

the

Production

Cycle

.

.

.

.

.

.

. 1

Customizing

the

Final

Job

Stream

.

.

.

.

.

. 1

Adding

the

final

Job

Stream

.

.

.

.

.

.

.

. 2

Starting

a

Production

Cycle

.

.

.

.

.

.

.

. 2

Managing

the

Production

Environment

.

.

.

.

. 2

Choosing

the

Start

of

Day

.

.

.

.

.

.

.

.

. 2

Changing

the

Start

of

Day

.

.

.

.

.

.

.

.

. 3

Creating

a

Plan

for

Future

or

Past

Dates

.

.

.

. 3

Launching

Jobs

.

.

.

.

.

.

.

.

.

.

.

.

. 4

Jobman

Environment

Variables

.

.

.

.

.

.

. 4

Standard

Configuration

Script

-

jobmanrc

.

.

.

. 5

Local

Configuration

Script

-

$HOME/.jobmanrc

. 6

Production

Processing

Commands

.

.

.

.

.

.

. 7

The

schedulr

Command

.

.

.

.

.

.

.

.

. 8

The

compiler

Command

.

.

.

.

.

.

.

.

. 9

The

stageman

Command

.

.

.

.

.

.

.

.

. 11

The

logman

Command

.

.

.

.

.

.

.

.

. 14

The

wmaeutil

Command

.

.

.

.

.

.

.

.

. 16

Managing

the

Production

Environment

.

.

.

.

. 18

Choosing

the

Workload

Scheduler

Start

of

Day

18

Changing

the

Start

of

Day

.

.

.

.

.

.

.

. 18

Creating

a

Plan

for

Future

or

Past

Dates

.

.

.

. 18

Using

Reports

.

.

.

.

.

.

.

.

.

.

.

. 19

Chapter

2.

Composer

Reference

.

.

.

. 21

Managing

Scheduling

Objects

.

.

.

.

.

.

.

. 21

Workstation

Definitions

.

.

.

.

.

.

.

.

. 22

Workstation

Class

Definitions

.

.

.

.

.

.

. 26

Domain

Definitions

.

.

.

.

.

.

.

.

.

.

. 27

Job

Definitions

.

.

.

.

.

.

.

.

.

.

.

. 28

User

Definitions

.

.

.

.

.

.

.

.

.

.

.

. 32

Calendar

Definitions

.

.

.

.

.

.

.

.

.

. 34

Parameter

Definitions

.

.

.

.

.

.

.

.

.

. 35

Prompt

Definitions

.

.

.

.

.

.

.

.

.

.

. 36

Resource

Definitions

.

.

.

.

.

.

.

.

.

. 37

The

Composer

Program

.

.

.

.

.

.

.

.

.

. 38

Running

Composer

.

.

.

.

.

.

.

.

.

.

. 38

Command

Syntax

.

.

.

.

.

.

.

.

.

.

. 40

Command

Descriptions

.

.

.

.

.

.

.

.

.

. 41

add

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 43

build

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 44

continue

.

.

.

.

.

.

.

.

.

.

.

.

.

. 45

create

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 46

delete

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 48

display,

list,

print

.

.

.

.

.

.

.

.

.

.

. 50

edit

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 53

exit

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 54

modify

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 55

new

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 57

redo

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 58

replace

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 59

validate

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 60

version

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 61

System

Command

.

.

.

.

.

.

.

.

.

.

. 62

Chapter

3.

Scheduling

Language

.

.

. 63

Syntax

for

Job

Streams

.

.

.

.

.

.

.

.

.

.

. 63

Keywords

.

.

.

.

.

.

.

.

.

.

.

.

.

. 63

Dependencies

.

.

.

.

.

.

.

.

.

.

.

.

. 64

Case

Sensitivity

.

.

.

.

.

.

.

.

.

.

.

. 65

Keyword

Descriptions

.

.

.

.

.

.

.

.

.

.

. 65

at

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 66

carryforward

.

.

.

.

.

.

.

.

.

.

.

.

. 67

comments

.

.

.

.

.

.

.

.

.

.

.

.

.

. 68

confirmed

.

.

.

.

.

.

.

.

.

.

.

.

.

. 69

end

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 70

every

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 71

except

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 72

follows

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 74

freedays

.

.

.

.

.

.

.

.

.

.

.

.

.

. 75

job

statement

.

.

.

.

.

.

.

.

.

.

.

.

. 77

limit

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 80

needs

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 81

on

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 82

opens

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 85

priority

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 87

prompt

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 88

schedule

.

.

.

.

.

.

.

.

.

.

.

.

.

. 89

until

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 90

Chapter

4.

Conman

Reference

.

.

.

.

. 91

Running

Conman

.

.

.

.

.

.

.

.

.

.

.

. 91

Examples

.

.

.

.

.

.

.

.

.

.

.

.

.

. 91

Control

Characters

.

.

.

.

.

.

.

.

.

.

. 91

Executing

System

Commands

.

.

.

.

.

.

. 91

User

Prompting

.

.

.

.

.

.

.

.

.

.

.

. 92

Terminal

Output

.

.

.

.

.

.

.

.

.

.

.

. 92

Offline

Output

.

.

.

.

.

.

.

.

.

.

.

. 92

Selecting

the

Conman

Command

Prompt

.

.

. 93

Command

Syntax

.

.

.

.

.

.

.

.

.

.

.

. 93

Wildcard

Characters

.

.

.

.

.

.

.

.

.

. 93

Delimiters

and

Special

Characters

.

.

.

.

.

. 94

List

of

Commands

.

.

.

.

.

.

.

.

.

.

. 95

Selecting

Jobs

in

Commands

.

.

.

.

.

.

.

.

. 96

Synopsis

.

.

.

.

.

.

.

.

.

.

.

.

.

. 96

v

||

||||||||

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

Arguments

.

.

.

.

.

.

.

.

.

.

.

.

. 97

Selecting

Job

Streams

in

Commands

.

.

.

.

.

. 103

Synopsis

.

.

.

.

.

.

.

.

.

.

.

.

.

. 103

Arguments

.

.

.

.

.

.

.

.

.

.

.

.

. 103

Command

Descriptions

.

.

.

.

.

.

.

.

.

. 107

Conman

Command

Processing

.

.

.

.

.

. 107

adddep

job

.

.

.

.

.

.

.

.

.

.

.

.

. 109

adddep

sched

.

.

.

.

.

.

.

.

.

.

.

. 110

altpass

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 111

altpri

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 112

cancel

job

.

.

.

.

.

.

.

.

.

.

.

.

.

. 113

cancel

sched

.

.

.

.

.

.

.

.

.

.

.

.

. 115

confirm

.

.

.

.

.

.

.

.

.

.

.

.

.

. 117

console

.

.

.

.

.

.

.

.

.

.

.

.

.

. 118

continue

.

.

.

.

.

.

.

.

.

.

.

.

.

. 119

deldep

job

.

.

.

.

.

.

.

.

.

.

.

.

. 120

deldep

sched

.

.

.

.

.

.

.

.

.

.

.

. 121

display

.

.

.

.

.

.

.

.

.

.

.

.

.

. 122

exit

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 123

fence

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 124

help

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 125

kill

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 126

limit

cpu

.

.

.

.

.

.

.

.

.

.

.

.

.

. 127

limit

sched

.

.

.

.

.

.

.

.

.

.

.

.

. 128

link

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 129

listsym

.

.

.

.

.

.

.

.

.

.

.

.

.

. 131

recall

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 132

redo

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 133

release

job

.

.

.

.

.

.

.

.

.

.

.

.

. 134

release

sched

.

.

.

.

.

.

.

.

.

.

.

. 136

reply

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 138

rerun

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 139

resource

.

.

.

.

.

.

.

.

.

.

.

.

.

. 142

setsym

.

.

.

.

.

.

.

.

.

.

.

.

.

. 143

showcpus

.

.

.

.

.

.

.

.

.

.

.

.

. 144

showdomain

.

.

.

.

.

.

.

.

.

.

.

. 147

showfiles

.

.

.

.

.

.

.

.

.

.

.

.

.

. 148

showjobs

.

.

.

.

.

.

.

.

.

.

.

.

.

. 150

showprompts

.

.

.

.

.

.

.

.

.

.

.

. 155

showresources

.

.

.

.

.

.

.

.

.

.

.

. 157

showschedules

.

.

.

.

.

.

.

.

.

.

.

. 159

shutdown

.

.

.

.

.

.

.

.

.

.

.

.

. 162

start

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 163

status

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 165

stop

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 166

submit

docommand

.

.

.

.

.

.

.

.

.

. 168

submit

file

.

.

.

.

.

.

.

.

.

.

.

.

. 170

submit

job

.

.

.

.

.

.

.

.

.

.

.

.

. 172

submit

sched

.

.

.

.

.

.

.

.

.

.

.

. 174

switchmgr

.

.

.

.

.

.

.

.

.

.

.

.

. 177

System

Command

.

.

.

.

.

.

.

.

.

.

. 178

tellop

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 179

unlink

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 180

version

.

.

.

.

.

.

.

.

.

.

.

.

.

. 182

Chapter

5.

Utility

Commands

.

.

.

.

. 183

Command

Descriptions

.

.

.

.

.

.

.

.

.

. 183

at

|

batch

Commands

.

.

.

.

.

.

.

.

. 184

caxtract

Command

.

.

.

.

.

.

.

.

.

. 187

cpuinfo

Command

.

.

.

.

.

.

.

.

.

. 188

datecalc

Command

.

.

.

.

.

.

.

.

.

. 190

dbexpand

Command

.

.

.

.

.

.

.

.

.

. 194

delete

Command

.

.

.

.

.

.

.

.

.

.

. 195

evtsize

Command

.

.

.

.

.

.

.

.

.

.

. 196

jbxtract

Command

.

.

.

.

.

.

.

.

.

.

. 197

jobinfo

Command

.

.

.

.

.

.

.

.

.

.

. 199

jobstdl

Command

.

.

.

.

.

.

.

.

.

.

. 201

maestro

Command

.

.

.

.

.

.

.

.

.

. 203

makecal

Command

.

.

.

.

.

.

.

.

.

. 204

morestdl

Command

.

.

.

.

.

.

.

.

.

. 206

parms

Command

.

.

.

.

.

.

.

.

.

.

. 208

paxtract

Command

.

.

.

.

.

.

.

.

.

. 209

prxtract

Command

.

.

.

.

.

.

.

.

.

. 210

r11xtr

Command

.

.

.

.

.

.

.

.

.

.

. 211

release

Command

.

.

.

.

.

.

.

.

.

.

. 212

rextract

Command

.

.

.

.

.

.

.

.

.

.

. 214

rmstdlist

Command

.

.

.

.

.

.

.

.

.

. 215

showexec

Command

.

.

.

.

.

.

.

.

.

. 216

StartUp

Command

.

.

.

.

.

.

.

.

.

. 217

version

Command

.

.

.

.

.

.

.

.

.

.

. 218

wmaeutil

Command

.

.

.

.

.

.

.

.

.

. 220

xrxtrct

Command

.

.

.

.

.

.

.

.

.

.

. 222

Unsupported

Commands

.

.

.

.

.

.

.

. 227

Chapter

6.

Report

Commands

.

.

.

. 229

Report

Commands

.

.

.

.

.

.

.

.

.

.

. 229

Command

Output

.

.

.

.

.

.

.

.

.

.

. 229

rep1

-

rep4b

Commands

.

.

.

.

.

.

.

.

. 231

rep7

Command

.

.

.

.

.

.

.

.

.

.

.

. 232

rep8

Command

.

.

.

.

.

.

.

.

.

.

.

. 233

rep11

Command

.

.

.

.

.

.

.

.

.

.

. 234

reptr

Command

.

.

.

.

.

.

.

.

.

.

. 235

xref

Command

.

.

.

.

.

.

.

.

.

.

.

. 236

Chapter

7.

Extended

Agent

Reference

237

What

are

Extended

Agents?

.

.

.

.

.

.

.

. 237

Workstation

Definition

.

.

.

.

.

.

.

.

. 237

Access

Method

Interface

.

.

.

.

.

.

.

.

.

. 237

Method

Command

Line

Syntax

.

.

.

.

.

. 237

Method

Response

Messages

.

.

.

.

.

.

. 239

Method

Options

File

.

.

.

.

.

.

.

.

.

. 240

Method

Execution

.

.

.

.

.

.

.

.

.

.

.

. 241

Launch

Job

(LJ)

Task

.

.

.

.

.

.

.

.

.

. 241

Manage

Job

(MJ)

Task

.

.

.

.

.

.

.

.

. 242

Check

File

(CF)

Task

.

.

.

.

.

.

.

.

.

. 242

Get

Status

(GS)

Task

.

.

.

.

.

.

.

.

.

. 243

The

cpuinfo

Command

.

.

.

.

.

.

.

.

. 243

Troubleshooting

.

.

.

.

.

.

.

.

.

.

.

. 243

Job

Standard

List

Error

Messages

.

.

.

.

.

. 244

Method

Not

Executable

.

.

.

.

.

.

.

.

. 244

Console

Manager

Messages

.

.

.

.

.

.

. 244

Composer

and

Compiler

Messages

.

.

.

.

. 244

Jobman

Messages

.

.

.

.

.

.

.

.

.

.

. 244

Chapter

8.

Network

Agent

Reference

247

Overview

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 247

Configuring

a

Network

Agent

Workstation

.

.

. 247

Network

Agent

Command

Line

Example

.

.

. 248

Options

File

.

.

.

.

.

.

.

.

.

.

.

.

. 248

Internetwork

Dependencies

.

.

.

.

.

.

.

.

. 249

Creating

an

Internetwork

Dependency

.

.

.

. 249

vi

Tivoli

Workload

Scheduler

Reference

Guide

Internetwork

Dependencies

and

Conman

.

.

. 250

Chapter

9.

Integration

with

Other

Products

.

.

.

.

.

.

.

.

.

.

.

.

. 253

Integration

with

NetView

.

.

.

.

.

.

.

.

. 253

General

Information

.

.

.

.

.

.

.

.

.

. 253

Installing

the

Integration

Software

.

.

.

.

. 254

Setting

Up

.

.

.

.

.

.

.

.

.

.

.

.

. 257

Objects,

Symbols,

and

Submaps

.

.

.

.

.

. 258

Menu

Actions

.

.

.

.

.

.

.

.

.

.

.

. 260

Tivoli

Workload

Scheduler/NetView

Events

.

. 262

Tivoli

Workload

Scheduler/NetView

Configuration

Files

.

.

.

.

.

.

.

.

.

. 264

Tivoli

Workload

Scheduler/NetView

Configuration

Options

.

.

.

.

.

.

.

.

. 267

Unison

Software

MIB

.

.

.

.

.

.

.

.

.

. 268

Tivoli

Workload

Scheduler/NetView

Program

Reference

.

.

.

.

.

.

.

.

.

.

.

.

.

. 272

Integration

with

Tivoli

Business

Systems

Manager

274

General

Information

.

.

.

.

.

.

.

.

.

. 274

Using

the

Key

Flag

Mechanism

.

.

.

.

.

. 275

Installing

the

Common

Listener

Agent

.

.

.

. 276

Customizing

the

Configuration

Files

.

.

.

.

. 276

Starting

and

Stopping

the

Common

Listener

Agent

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 278

Workload

Scheduler/Tivoli

Business

Systems

Manager

Events

.

.

.

.

.

.

.

.

.

.

. 279

Appendix

A.

Maintaining

Tivoli

Workload

Scheduler

.

.

.

.

.

.

.

. 281

Databases

.

.

.

.

.

.

.

.

.

.

.

.

.

. 281

Defragmenting

Build

.

.

.

.

.

.

.

.

.

. 281

Backing

Up

.

.

.

.

.

.

.

.

.

.

.

.

. 282

Reporting

.

.

.

.

.

.

.

.

.

.

.

.

.

. 283

Maintaining

the

File

System

.

.

.

.

.

.

.

. 283

File

Sets

.

.

.

.

.

.

.

.

.

.

.

.

.

. 283

Temporary

Files

.

.

.

.

.

.

.

.

.

.

. 283

Appendix

B.

Time

Zone

Names

and

Descriptions

.

.

.

.

.

.

.

.

.

.

.

. 285

Notices

.

.

.

.

.

.

.

.

.

.

.

.

.

. 287

Trademarks

.

.

.

.

.

.

.

.

.

.

.

.

.

. 288

Glossary

.

.

.

.

.

.

.

.

.

.

.

.

. 289

Index

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 293

Contents

vii

|

|

|

|

viii

Tivoli

Workload

Scheduler

Reference

Guide

Preface

Tivoli

Workload

Scheduler

simplifies

systems

management

across

distributed

environments

by

integrating

systems

management

functions.

Workload

Scheduler

plans,

automates,

and

controls

the

processing

of

your

enterprises

entire

production

workload.

The

Tivoli

Workload

Scheduler

Reference

Guide

provides

detailed

information

about

the

command

line

interface,

scheduling

language,

and

utility

commands

for

Tivoli

Workload

Scheduler.

Maintenance

Release

This

is

a

maintenance

refresh

of

the

corresponding

IBM

Tivoli

Workload

Scheduler

Version

8.1

manual,

form

number

SH19-4556-00.

It

contains

updates

for

the

APARS

fixed

with

the

Tivoli

Workload

Scheduler

fix

packs

up

to

fix

pack

8.

Throughout

the

book,

the

changed

or

new

sections

are

marked

by

revision

bars.

The

name

of

the

fix

pack

or

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

guide

is

intended

for

administrators

and

advanced

users

of

Tivoli

Workload

Scheduler.

What

This

Guide

Contains

This

guide

contains

the

following

sections:

v

Chapter

1,

The

Production

Cycle,

on

page

1

Describes

the

procedures

and

commands

used

in

the

Workload

Scheduler

production

cycle.

v

Chapter

2,

Composer

Reference,

on

page

21

Describes

the

composer

command

line

interface.

This

is

used

to

create

scheduling

objects

in

the

Workload

Scheduler

database.

v

Chapter

3,

Scheduling

Language,

on

page

63

Describes

the

scheduling

language

used

to

define

jobs

and

job

streams

in

the

Workload

Scheduler

database.

v

Chapter

4,

Conman

Reference,

on

page

91

Describes

the

conman

command

line

interface.

This

is

used

to

monitor

and

manage

job

execution

during

the

production

day.

v

Chapter

5,

Utility

Commands,

on

page

183

Describes

the

Tivoli

Workload

Scheduler

utility

commands.

These

commands

are

used

to

manage

the

Workload

Scheduler

environment.

v

Chapter

6,

Report

Commands,

on

page

229

Describes

how

to

print

different

types

of

report

in

Workload

Scheduler.

v

Chapter

7,

Extended

Agent

Reference,

on

page

237

Provides

a

programmers

reference

for

creating

extended

agents.

v

Chapter

8,

Network

Agent

Reference,

on

page

247

ix

|

|||

|||||

Describes

how

to

create

and

use

a

network

agent

workstation.

v

Chapter

9,

Integration

with

Other

Products,

on

page

253

Describes

how

Workload

Scheduler

works

with

NetView

and

Tivoli

Business

Systems

Manager.

v

Appendix

A,

Maintaining

Tivoli

Workload

Scheduler,

on

page

281

Discusses

how

to

keep

Workload

Scheduler

running

with

optimal

performance.

v

Appendix

B,

Time

Zone

Names

and

Descriptions,

on

page

285

Lists

the

time

zones

supported

by

Workload

Scheduler.

Publications

This

section

lists

publications

in

the

Tivoli

Workload

Scheduler

library

and

any

other

related

documents.

It

also

describes

how

to

access

Tivoli

publications

online,

how

to

order

Tivoli

publications,

and

how

to

make

comments

on

Tivoli

publications.

Tivoli

Workload

Scheduler

Library

The

following

documents

are

available

in

the

Tivoli

Workload

Scheduler

library:

Table

1.

List

of

Publications

for

Tivoli

Workload

Scheduler

Task

Publication

Order

number

Installing

a

Workload

Scheduler

network

Tivoli

Workload

Scheduler

Planning

and

Installation

SH19-4555

Using

the

command

line

interface,

scheduling

language,

and

utility

commands

Tivoli

Workload

Scheduler

Reference

Guide

SH19-4556

Installing

and

configuring

limited

fault-tolerant

agents

on

AS/400

Tivoli

Workload

Scheduler

Limited

Fault-Tolerant

Agent

for

AS/400

Users

Guide

SH19-4558

Setting

up

and

using

the

Plus

module

Tivoli

Workload

Scheduler

Plus

Module

Users

Guide

SH19-4562

Interpreting

messages

Tivoli

Workload

Scheduler

Error

Messages

SH19-4557

Using

the

Java-based

graphical

user

interface

Tivoli

Workload

Scheduler

Job

Scheduling

Console

Users

Guide

SH19-4552

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

Tivoli

Workload

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.

x

Tivoli

Workload

Scheduler

Reference

Guide

|

||||

|

|

||||

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

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

Conventions

Used

in

This

Guide

This

book

uses

several

conventions

for

special

terms

and

actions,

operating

system-dependent

commands

and

paths,

and

margin

graphics.

Typeface

Conventions

The

following

typeface

conventions

are

used

in

this

book:

Bold

Lowercase

and

mixed-case

commands,

command

options,

and

flags

that

appear

within

text

appear

like

this,

in

bold

type.

Graphical

user

interface

elements

(except

for

titles

of

windows

and

dialogs)

and

names

of

keys

also

appear

like

this,

in

bold

type.

Italic

Variables,

values

you

must

provide,

new

terms,

and

words

and

phrases

that

are

emphasized

appear

like

this,

in

italic

type.

Monospace

Commands,

command

options,

and

flags

that

appear

on

a

separate

line,

code

examples,

output,

and

message

text

appear

like

this,

in

monospace

type.

Preface

xi

|

|

|||

|

|

|

|

|

|

||

|

|

||

|

||

|

||

|

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

Names

of

files

and

directories,

text

strings

you

must

type,

when

they

appear

within

text,

names

of

Java

methods

and

classes,

and

HTML

and

XML

tags

also

appear

like

this,

in

monospace

type.

Operating

System-dependent

Variables

and

Paths

This

book

uses

the

UNIX

convention

for

specifying

environment

variables

and

for

directory

notation.

When

using

the

Microsoft

Windows

command

line,

replace

$variable

with

%variable%

for

environment

variables

and

replace

each

forward

slash

(/)

with

a

backslash

(\)

in

directory

paths.

Note:

If

you

are

using

the

bash

shell

on

a

Windows

system,

you

can

use

the

UNIX

conventions.

xii

Tivoli

Workload

Scheduler

Reference

Guide

Chapter

1.

The

Production

Cycle

The

Tivoli

Workload

Scheduler

processing

day

begins

at

the

time

defined

by

the

start

global

option,

which

is

set,

by

default.

to

6:00

a.m.

To

turn

over

a

new

day,

pre-production

set

up

is

performed

for

the

upcoming

day,

and

post-production

logging

and

reporting

is

performed

for

the

day

just

ended.

This

chapter

describes

the

procedures

and

commands

you

use

to

perform

these

tasks.

For

information

about

the

start

options,

refer

to

the

Tivoli

Workload

Scheduler

Planning

and

Installation

Guide.

Automating

the

Production

Cycle

Pre-production

and

post-production

processing

can

be

automated

fully

by

adding

the

Tivoli-supplied

final

job

stream,

or

a

user-supplied

equivalent,

to

the

scheduler

database,

together

with

other

job

streams.

A

copy

of

the

Tivoli-supplied

job

stream

is

in

the

TWShome/config/Sfinal

directory.

A

copy

of

the

job

script

is

in

the

TWShome/Jnextday

directory.

You

might

find

it

useful

to

print

copies

to

help

you

understand

the

turnover

process.

The

final

job

stream

is

placed

in

production

every

day,

and

results

in

running

a

job

named

Jnextday

prior

to

the

start

of

a

new

day.

The

job

performs

the

following

tasks:

1.

Executes

the

schedulr

command

to

select

job

streams

for

the

new

days

production

plan.

For

more

information,

see

8.

2.

Executes

the

compiler

command

to

compile

the

production

plan.

For

more

information,

see

The

compiler

Command

on

page

9.

3.

Executes

the

reptr

command

to

print

pre-production

reports.

For

more

information,

see

reptr

Command

on

page

235.

4.

Stops

the

scheduler.

5.

Executes

the

stageman

command

to

carry

forward

uncompleted

job

streams,

log

the

old

production

plan,

and

install

the

new

plan.

For

more

information,

see

The

stageman

Command

on

page

11.

6.

Runs

the

wmaeutil

command

to

stop

all

mapper

servers

so

that

they

all

open

a

new

symphony.

For

more

information,

see

The

wmaeutil

Command

on

page

16.

7.

Starts

the

scheduler

for

the

new

day.

8.

Executes

the

reptr

and

the

rep8

commands

to

print

post-production

reports

for

the

previous

day.

For

more

information,

see

reptr

Command

on

page

235.

9.

Executes

the

logman

command

to

log

job

statistics

for

the

previous

day.

For

more

information,

see

The

logman

Command

on

page

14.

In

the

Tivoli

Workload

Scheduler

manual

set,

the

terms

final

and

Jnextday

are

used

when

referring

to

both

the

Tivoli-supplied

versions,

and

any

user-supplied

equivalents.

Customizing

the

Final

Job

Stream

Before

using

the

final

job

stream,

it

can

be

modified

to

meet

your

needs,

or

you

can

create

a

different

job

stream

to

use

in

its

place.

1

When

creating

your

own

job

stream,

model

it

after

the

one

supplied

by

Tivoli.

If

you

choose

to

do

so,

consider

the

following:

v

If

you

choose

to

change

the

way

stageman

generates

log

file

names,

remember

that

reptr

and

logman

must

use

the

same

names.

v

If

you

would

like

to

print

the

pre-production

reports

in

advance

of

a

new

day,

you

can

split

the

Jnextday

job

into

two

jobs.

The

first

job

will

execute

schedulr,

compiler

and

reptr.

The

second

job

will

stop

the

scheduler,

execute

stageman,

start

the

scheduler,

and

execute

reptr

and

logman.

The

first

job

can

then

be

scheduled

to

run

at

any

time

prior

to

the

end

of

day,

while

the

second

job

is

scheduled

to

run

just

prior

to

the

end

of

day.

Adding

the

final

Job

Stream

If

you

performed

the

quick

start

procedure

in

the

Tivoli

Workload

Scheduler

Installation

Guide,

the

final

job

stream

is

already

added

to

the

database.

If

not,

follow

these

steps

to

add

the

final

job

stream,

or

a

user-supplied

equivalent.

1.

Log

in

as

the

maestro

user

on

the

master

domain

manager.

2.

At

a

command

prompt,

execute

the

following

command

on

UNIX:

composer

add

Sfinal

or

the

following

command

on

Windows

NT:

composer

add

Sfinal

To

add

your

own

job

stream,

use

its

name

in

place

of

Sfinal.

Starting

a

Production

Cycle

If

it

has

not

been

started

before

follow

these

steps:

1.

Log

in

as

the

maestro

user

on

the

master

domain

manager.

2.

At

a

command

prompt,

execute

the

Jnextday

job

by

entering

the

following

command:

Jnextday

This

will

perform

pre-production

processing

and

start

the

scheduler

production

processes.

Managing

the

Production

Environment

This

section

provides

information

on

changing

the

start

of

day

for

Workload

Scheduler

and

creating

a

plan

to

process

future

or

past

days

processing.

Choosing

the

Start

of

Day

There

are

three

common

choices

for

the

start

of

the

production

day.

v

early

morning

v

late

afternoon

v

midnight

These

are

a

few

of

the

scheduling

implications:

Start

and

Deadline

Times

Start

times

(AT

keyword)

specified

are

always

in

relationship

to

the

Workload

Scheduler

production

day

start

time.

You

may

need

to

add

+

1

day

to

job

2

Tivoli

Workload

Scheduler

Reference

Guide

|

||

|

|

|

|

|

|

|

||

streams

whose

jobs

process

across

production

days.

Also

be

certain

that

the

deadline

(UNTIL

keyword)

time

comes

after

the

m

start

time.

On

keyword

Production

and

calendar

days

do

not

have

to

be

the

same.

If

your

production

day

starts

at

06:00

a.m.

(the

default

setting),

05:59

a.m.

will

be

the

last

minute

of

the

production

day.

A

Job

Stream

defined

to

run

ON

MONDAY

at

05:30

will

be

selected

on

Monday

and

will

run

on

the

calendar

day

Tuesday

at

5:30

a.m.

Carryforward

keyword

Placing

the

start

of

day

near

midnight

to

correspond

with

the

calendar

day

will

tend

to

produce

a

large

number

of

carried

forward

job

streams.

This

may

increase

the

complexity

of

managing

the

data

center.

Changing

the

Start

of

Day

The

start

of

day

for

Workload

Scheduler

is

when

the

final

Job

Stream

is

run

and

the

Workload

Scheduler

processes

are

stopped

and

restarted.

To

specify

the

start

of

day

for

Workload

Scheduler:

1.

Modify

the

start

option

in

the

Globalopts

file.

This

is

the

start

time

of

Workload

Schedulers

processing

day

in

24

hour

format:

hhmm

(0000-2359).

The

default

start

time

is

6:00

A.M.

2.

Modify

the

start

time

(AT

keyword)

of

the

final

job

stream

to

run

one

minute

before

the

end

of

day.

If

you

want

to

set

the

start

of

the

production

day

to

midnight:

1.

Set

the

start

time

of

the

final

job

stream

to

midnight.

2.

Set

the

start

option

in

the

Globalopts

file

to

0001.

Otherwise,

by

having

the

start

option

set

to

0000

and

Jnextday

set

to

2359,

you

risk

selecting

schedules

or

job

streams

for

the

day

that

just

ended,

since

the

schedulr

command

uses

the

system

date

and

small

networks

can

sometimes

get

to

the

schedulr

run

before

midnight.

Creating

a

Plan

for

Future

or

Past

Dates

You

can

create

a

plan

that

executes

processing

normally

scheduled

for

a

future

or

past

day

of

processing.

This

procedure

effectively

recreates

any

specified

day

of

processing.

You

may

need

to

use

this

procedure

if

you

lost

a

day

of

processing

due

to

an

emergency.

1.

Unlink

and

stop

all

workstations

in

your

Workload

Scheduler

network

with

the

following

commands:

conman

unlink

@!@;noask

conman

stop

@!@;wait

This

stops

all

processing

in

the

network.

2.

Run

the

schedulr

command

with

the

date

option

to

create

a

prodsked

file:

schedulr

-date

MM/DD/YY

With

the

date

option

you

can

specify

to

create

a

plan

based

on

a

future

or

past

day

of

processing.

3.

Run

the

compiler

command

to

create

a

symnew

file:

compiler

(-date

MM/DD/YY)

Chapter

1.

The

Production

Cycle

3

||

|

||||

|

|||

|

|||

|||

||

|

|

|

||||

|

||||

||

|

|

|

|

|

||

|

|

You

can

use

the

date

option

with

the

compiler

to

specify

todays

date

or

the

date

of

the

day

you

are

trying

to

recreate.

This

option

may

be

necessary

if

you

have

job

streams

that

contain

date

sensitive

input

parameters.

The

scheddate

parameter

is

keyed

off

the

date

specified

with

the

compiler

command.

If

you

do

not

specify

a

date,

it

defaults

to

the

date

entered

with

the

schedulr

command.

4.

Run

console

manager

to

stop

Workload

Scheduler

processes:

conman

stop

@!@

5.

Run

stageman

to

create

the

new

symphony

file:

stageman

6.

Run

console

manager

to

start

Workload

Scheduler

processes:

conman

start

Launching

Jobs

Jobs

are

launched

under

the

direction

of

the

Production

Control

process

Batchman.

Batchman

resolves

all

job

dependencies

to

ensure

the

correct

order

of

execution,

and

then

issues

a

job

launch

message

to

the

Jobman

process.

Jobman

spawns

a

job

monitor

process

that

begins

by

setting

a

group

of

environment

variables,

and

then

it

executes

the

standard

configuration

script

(maestrohome/jobmanrc).

If

the

user

is

allowed

to

use

a

local

configuration

script,

and

the

script

$HOME/.jobmanrc

exists,

the

local

configuration

script

is

also

executed.

The

job

is

then

executed

either

by

the

standard

configuration

script,

or

by

the

local

one.

Each

of

the

processes

launched

by

Jobman,

including

the

configuration

scripts

and

the

jobs,

retain

the

user

name

recorded

with

the

Logon

of

the

job.

In

case

of

submitted

jobs,

they

retain

the

submitting

users

name.

To

have

the

jobs

execute

with

the

users

environment,

be

sure

to

add

the

users

.profile

environment

to

the

local

configuration

script.

Jobman

Environment

Variables

The

variables

listed

in

the

table

below

are

set

and

exported

by

Jobman.

Table

2.

Variable

Name

Value

HOME

The

login

users

name

directory.

LOGNAME

The

login

users

name.

PATH

For

MS-Windows:

%SYSTEMROOT\SYSTEM32.

For

UNIX:

/bin:/usr/bin

TZ

The

timezone.

UNISON_SHELL

The

users

login

shell.

UNISON_CPU

The

name

of

this

CPU.

UNISON_HOST

The

name

of

the

master/host

CPU.

UNISON_JOB

The

fully

qualified

job

name:

cpu#sched.job

UNISON_JOBNUM

The

job

number

(ppid).

UNISON_MASTER

The

name

of

the

master

CPU.

4

Tivoli

Workload

Scheduler

Reference

Guide

||||||

|

|

|

|

|

|

|

|||

||||||

|||||

|

|

||

||

||

||

||||

||

||

||

||

||

||

||

Table

2.

(continued)

UNISON_RUN

Tivoli

Workload

Schedulers

current

production

run

number.

UNISON_SCHED

The

schedule

name.

UNISON_SCHED_DATE

Tivoli

Workload

Schedulers

production

date

(yymmdd).

UNISON_SCHED_EPOCH

Tivoli

Workload

Schedulers

production

date,

expressed

in

epoch

form.

Standard

Configuration

Script

-

jobmanrc

A

standard

configuration

script

template

named

maestrohome/config/jobmanrc

is

supplied

with

Workload

Scheduler.

It

is

installed

automatically

as

maestrohome/jobmanrc.

This

script

can

be

used

by

the

system

administrator

to

establish

a

desired

environment

before

each

job

is

executed.

If

you

wish

to

alter

the

script,

make

your

modifications

in

the

working

copy

(maestrohome/jobmanrc),

leaving

the

template

file

intact.

The

file

contains

variables

which

can

be

configured,

and

comments

to

help

you

understand

the

methodology.

Table

3

describes

the

jobmanrc

variables.

Table

3.

Variables

of

jobmanrc

Variable

Name

Value

UNISON_JCL

The

path

name

of

the

jobs

script

file.

UNISON_STDLIST

The

path

name

of

the

jobs

standard

list

file.

UNISON_EXIT

(Settable)

If

set

to

yes,

the

job

is

terminated

immediately

if

any

command

returns

a

non-zero

exit

code.

If

set

to

no,

the

job

continues

to

execute

if

a

command

returns

a

non-zero

exit

code.

Any

other

setting

is

interpreted

as

no.

LOCAL_RC_OK

(Settable)

If

set

to

yes,

the

users

local

configuration

script

is

executed

(if

it

exists),

passing

$UNISON_JCL

as

the

first

argument.

The

user

may

be

allowed

or

denied

this

option.

See

Local

Configuration

Script

-

$HOME/.jobmanrc

on

page

6

for

more

information.

If

set

to

no,

the

presence

of

a

local

configuration

script

is

ignored,

and

$UNISON_JCL

is

executed.

Any

other

setting

is

interpreted

as

no.

MAIL_ON_ABEND

(Settable)

If

set

to

yes,

a

message

is

mailed

to

the

login

users

mailbox

if

the

job

terminates

with

a

non-zero

exit

code.

This

can

also

be

set

to

one

or

more

user

names,

separated

by

spaces,

and

a

message

is

mailed

to

each

user.

For

example,

root

mis

sam

mary.

If

set

to

no,

no

messages

are

mailed

if

the

job

abends.

Abend

messages

have

the

following

format:

cpu#sched.job

jcl-file

failed

with

exit-code

Please

review

standard-list-filename

Chapter

1.

The

Production

Cycle

5

|

|||

||

|||

||||

|

||||||||

||

||

||

||

|||||||

|||||||||||

||||||||||

|

|

|

Table

3.

Variables

of

jobmanrc

(continued)

Variable

Name

Value

SHELL_TYPE

(Configurable)

If

set

to

standard,

the

first

line

of

the

jcl

file

is

read

to

determine

which

shell

to

use

to

execute

the

job.

If

the

first

line

does

not

start

with

#!,

then

/bin/sh

is

used

to

execute

the

local

configuration

script

or

$UNISON_JCL.

Commands

are

echoed

to

the

jobs

standard

list

file.

If

set

to

user,

the

local

configuration

script

or

$UNISON_JCL

is

executed

by

the

users

login

shell

($UNISON_SHELL).

Commands

are

echoed

to

the

jobs

standard

list

file.

If

set

to

script,

the

local

configuration

script

or

$UNISON_JCL

is

executed

directly,

and

commands

are

not

echoed

unless

the

local

configuration

script

or

$UNISON_JCL

contains

a

set

-x

command.

Any

other

setting

is

interpreted

as

standard.

USE_EXEC

(Settable)

If

set

to

yes,

the

job,

or

the

users

local

configuration

script

is

executed

using

the

exec

command,

thus

eliminating

an

extra

process.

This

option

is

overridden

if

MAIL_ON_ABEND

is

also

set

to

yes.

Any

other

setting

is

interpreted

as

no,

in

which

case

the

job

or

local

configuration

script

is

executed

by

another

shell

process.

Local

Configuration

Script

-

$HOME/.jobmanrc

The

local

configuration

script

permits

users

to

establish

a

desired

environment

for

the

execution

of

their

own

jobs.

The

script

will

be

executed

only

under

the

following

conditions:

1.

The

standard

configuration

script,

jobmanrc,

must

be

installed,

and

the

environment

variable

LOCAL_RC_OK

must

be

set

to

yes

(see

Table

3).

2.

If

the

file

maestrohome/localrc.allow

exists,

the

users

name

must

appear

in

the

file.

If

the

allow

file

does

not

exist,

the

users

name

must

not

appear

in

the

file,

maestrohome/localrc.deny.

If

neither

of

these

files

exists,

the

user

is

permitted

to

use

a

local

configuration

script.

3.

The

local

configuration

script

must

be

installed

in

the

users

home

directory

($HOME/.jobmanrc),

and

it

must

have

execute

permission.

If

you

intend

to

use

a

local

configuration

script,

it

must,

at

a

minimum,

execute

the

jobs

script

file

($UNISON_JCL).

The

Tivoli-supplied

standard

configuration

script,

jobmanrc,

executes

your

local

configuration

script

as

follows:

$EXECIT

$USE_SHELL

$HOME/.jobmanrc

"$UNISON_JCL"

$IS_COMMAND

The

value

of

USE_SHELL

is

set

to

the

value

of

the

jobmanrc

SHELL_TYPE

variable

(see

Table

3

on

page

5).

IS_COMMAND

is

set

to

yes

if

the

job

was

scheduled

or

submitted

using

the

docommand

construct.

EXECIT

is

set

to

exec

if

the

variable

USE_EXEC

is

set

to

yes

(see

Table

3

on

page

5),

otherwise

it

is

null.

The

following

example

shows

how

to

execute

a

jobs

script

file,

or

command,

in

your

local

configuration

script:

#!/bin/ksh

6

Tivoli

Workload

Scheduler

Reference

Guide

|

||

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

||||||||||

|

|||

||

||||

||

|||

|

||||

||

|

PATH=maestrohome:maestrohome/bin:$PATH

export

PATH

/bin/sh

-c

"$UNISON_JCL"

The

following

is

an

example

of

a

.jobmanrc

that

does

processing

based

on

the

exit

code

of

the

users

job:

#!/bin/sh

#

PATH=maestrohome:maestrohome/bin:$PATH

export

PATH

/bin/sh

-c

"$UNISON_JCL"

#or

use

eval

"$UNISON_JCL"

and

the

quotes

are

required

RETVAL=$?

if

[

$RETVAL

-eq

1

]

then

echo

"Exit

code

1

-

Non

Fatal

Error"

exit

0

elif

[

$RETVAL

-gt

1

-a

$RETVAL

-lt

100

]

then

conman

"tellop

This

is

a

database

error

-

page

the

dba"

elif

[

$RETVAL

-ge

100

]

then

conman

"tellop

Job

aborted.

Please

page

the

admin"

fi

Production

Processing

Commands

The

pre

and

post-production

processing

commands

executed

by

the

Jnextday

job

are

described

on

the

pages

that

follow.

Chapter

1.

The

Production

Cycle

7

|

|

|

||

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

The

schedulr

Command

The

schedulr

command

selects

job

streams

for

a

specific

date

from

the

database

file

mastsked,

and

copies

them

to

a

new

production

schedule

file

named

prodsked.

You

must

have

build

access

to

the

scheduler

database

files.

Synopsis

schedulr

-v|-u

schedulr

[-date

date|-autodate]

[-scheds

{in-file|-}]

[-prodsked

{out-file|-}]

Arguments

-u

Displays

the

command

version

and

exits.

-v

Displays

command

usage

information

and

exits.

-date

Selects

job

streams

for

a

specific

date.

The

date

is

entered

as

mm/dd/[yy]yy.

-autodate

Selects

job

streams

for

the

current

system

date.

-scheds

In

addition

to

those

selected

by

-date

or

-autodate,

if

any,

selects

the

job

streams

named

in

in-file.

The

names

must

appear

in

the

file

as

[workstation#]jobstream,

with

one

name

per

line.

If

a

dash

is

entered

instead

of

a

file

name,

schedulr

prompts

for

job

stream

names

at

stdin.

-prodsked

Directs

schedulr

output

to

out-file.

If

a

dash

is

entered

instead

of

a

file

name,

the

output

is

directed

to

stdout.

If

the

argument

is

omitted,

the

output

is

written

to

a

file

named

prodsked.

Description

If

-autodate,

and

-date

are

omitted,

schedulr

prompts

for

a

date.

If

you

respond

to

the

prompt

by

pressing

Return,

job

streams

are

selected

only

from

the

in-file.

Examples

Select

job

streams

for

todays

date,

plus

the

job

streams

named

in

the

file

myskeds:

schedulr

-autodate

-scheds

myskeds

Select

job

streams

for

February

15,

1999,

do

not

prompt

for

extra

job

stream

names,

and

write

the

output

to

the

file

myprodsked:

schedulr

-date

2/15/90

-prodsked

myprodsked

Select

job

streams

for

February

15,

1999,

and

prompt

for

extra

job

streams:

schedulr

-date

2/15/1999

-scheds

-

Prompt

for

the

production

date,

and

extra

job

streams

(note

that

schedule

is

the

same

as

job

stream):

schedulr

Enter

schedule

date:

4/14/99

Enter

a

list

of

extra

schedules

Schedule

name:

site1#sked2

Schedule

name:

End

of

Program

8

Tivoli

Workload

Scheduler

Reference

Guide

The

compiler

Command

The

compiler

command

compiles

the

production

schedule

file,

and

creates

an

interim

production

plan

file.

Synopsis

compiler

-v|-u

compiler

[-date

date]

[-input

in-file]

[-output

out-file]

Arguments

-u

Displays

the

command

version

and

exits.

-v

Displays

command

usage

information

and

exits.

-date

The

production

date

to

be

recorded

in

the

interim

production

plan

file.

The

date

is

entered

as

mm/dd/[yy]yy.

-input

The

name

of

the

file

containing

the

production

schedule.

If

this

option

is

omitted,

the

default

name

is

prodsked.

-output

Directs

compiler

output

to

out-file.

If

the

argument

is

omitted,

the

output

is

written

to

a

file

named

Symnew.

Description

If

you

omit

the

-date

argument,

Symnew

is

given

the

same

date

as

that

recorded

in

the

production

schedule

file

created

by

schedulr.

If

there

is

no

date

in

production

schedule

file,

the

current

system

date

is

used.

The

date

in

Symnew

is

the

date

that

the

scheduler

will

begin

executing

the

production

plan.

The

ability

to

enter

a

different

date

can

be

used

to

set

up

processing

for

past

or

future

dates.