FastSort Manual

ManualsBrandsHP ManualsServerHP NonStop G-Series

211

212

213

214

215

216

217

218

219

220

Optimizing Sort Performance

FastSort Manual—429834-003

9-13

Managing Sort Failures

For information about TAL compiler directives, see the TAL Reference Manual. For

information about the Binder SET command, see the Binder Manual.

Other Data Stack Space Considerations

In addition to the requirements listed above, if you specify either the SCRATCHON or

NOSCRATCHON attributes in a SORT DEFINE, FastSort requires up to 138 additional

words (276 bytes) of stack space. To learn how FastSort uses this space to build a

pool of scratch volumes, see Table 5-1 on page 5-5.

If your application process starts a new process, FastSort also requires 30 to 35

additional words of stack space to support the PROCESS_CREATE_ procedure.

Managing Sort Failures

If a sort operation fails, the cause of the failure is usually stated in the error message

FastSort returns. Most sort failures are caused by insufficient workspace. For more

information on how to set up scratch and swap files, see Managing Sort Workspace on

page 9-1. This subsection recommends strategies for managing failures that are not

caused by insufficient sort workspace.

Verifying Version Compatibility

A sort operation might fail if you run versions of FastSort and other NonStop software

that are incompatible. Incompatible versions are likely cause of failure, for example, if

SORTPROG runs on one node, and a software component that affects FastSort runs

on a second node.

For SQL/MP sort operations, you might receive error 121 (INCOMPATIBLE SQL

VERSION) when the sort fails due to incompatible versions. In other cases, the error

message you receive might not directly refer to a version problem.

If you suspect a version problem, check versions of the operating system,

SORTPROG, SORT, SQL/MP, and other NonStop software products for compatibility.

Run the VPROC utility to determine software versions. The syntax for the VPROC

utility is:

VPROC object-file

In VPROC syntax, object-file is the volume, subvolume, and file name of the

program object file. For example, to determine the version of SORTPROG on your

local node, type:

VPROC $SYSTEM.SYSnn.SORTPROG

at a TACL prompt. The operating system returns version information in the following

format:

VPROC-T9617D30-(31 OCT 94) SYSTEM \TSII Date 17 JUL 1995,

14:54:38