NetBatch Manual

NetBatch Introduction

NetBatch Manual—522460-004

1-3

ASSIGNs, DEFINEs, and PARAMs

The NetBatch scheduler propagates ASSIGNs, DEFINEs, and PARAMs to executor-

program processes through user-defined entities called attachment sets. A single set

can supply ASSIGNs, DEFINEs, and PARAMs to many jobs, thus simplifying job setup.

Operator Interface

The NetBatch operator interface (BATCHCOM) lets you inquire about and manipulate

the scheduler, the scheduler’s executors and classes, and attachment sets and jobs.

The interface comes with a comprehensive online help facility that contains information

about topics such as command syntax.

Scheduling Options

The NetBatch scheduler offers a variety of scheduling options that let you specify when

jobs are to start. The scheduler can run a job at or after a specified date and time, or

delay execution for a specified period after submission. Jobs can run automatically at

regular, specified intervals or at times specified by a run calendar. Execution of a job

also can depend on the completion of up to 50 other jobs.

Scheduler Logging

The NetBatch scheduler records in a log file details of events that occur while the

scheduler is running. You can see the log file, for example, when troubleshooting the

scheduler. In addition to maintaining this log file, the scheduler creates log files for the

jobs it starts. The scheduler uses these log files to record details of events that occur

during job execution.

Programmatic Interfaces

The NetBatch subsystem has programmatic interfaces (commands, responses, and

event messages in Subsystem Programmatic Interface [SPI] format) that let your

applications:

•

Send commands to and receive responses from the subsystem in the form of

tokenized messages

•

Retrieve Event Management Service (EMS) events sent by the subsystem in the

form of tokenized messages

For details of the interfaces, see the NetBatch Management Programming Manual.

Spooler Jobs

The spooler subsystems support the NetBatch product through their ability to link

output of NetBatch jobs into batches of spooler jobs. This lets you manipulate the

batched jobs in the spoolers as single entities instead of as individual jobs.