NonStop SQL/MP Reference Manual

Table Of Contents
NonStop SQL/MP Reference Manual142115
P-21
Examples—PERUSE
jobs while they are in the spooler system. For a complete description of PERUSE, see
the Guardian Utilities Reference Manual.
run-options
are one or more standard run-options, separated by commas (as described in the
TACL Reference Manual).
supervisor
is the name of the spooler supervisor that PERUSE communicates with. If
supervisor is omitted, then PERUSE assumes $SPLS is the supervisor.
Examples—PERUSE
The following example shows how to start PERUSE from SQLCI:
>>PERUSE;
PERUSE - T9101D20 - (01JUN93) SYSTEM \SYS
Copyright Tandem Computers Incorporated 1978,1982,1983,1984,
1985,1986,1987,1988,1989,1990,1991
SPOOLER SUPERVISOR IS \SYS.$SPLS
JOB BATCH STATE PAGES COPIES PRI HOLD LOCATION REPORT
36 READY 2 1 4 #DEFAULT SALES
533 OPEN 1 4 B #DEFAULT BUDGET
1074 READY 1 1 4 A #DEFAULT MARCH
_
Plans
A plan (also called an execution plan or a query execution plan) is an execution method
for a single compiled SQL statement. A plan captures both the semantics and execution
characteristics of the statement. Compiled programs typically include many plans. Each
plan may be operable or inoperable, optimal or not optimal, and valid or invalid.
An operable plan is a plan that will give correct results for a given set of database tables.
An inoperable plan is one whose execution would result in an error, an incorrect query
result, or corruption of the database.
An optimal plan is an operable plan that is also the most efficient plan for processing the
statement against a given set of database tables. Not all operable plans are optimal plans.
An optimal plan for one set of tables might be operable, but not optimal, for a different,
but similar, set of tables.
PERUSE [ /run-options/ ] [supervisor] ;