SORT Subsystem

The sorting function for an HP NonStop server is called FastSort. FastSort is the sort- merge utility and can sort or merge records from one or more input sources:

A sort operation arranges and combines one or more sets of input records into a single set of output records. During a sort operation, FastSort arranges the records in either ascending or descending order, or in a combination of both based on a sequence of key-field values.

A merge operation combines two or more sets of sorted input records into a single set of output records. The records for merging are already sorted in an ascending or descending sequence of key-field values.

FastSort accepts records to sort or merge from these input sources:

1 to 32 disk files

A terminal

An application process

Tape files

RISK FastSort requires read access from the input sources. If an input source is a disk or tape file containing sensitive data, the output of FastSort could allow unauthorized access to the data.

The components of FastSort are:

RECGEN

SORT

SORTPROG

RECGEN

RECGEN is the record generator process for the parallel creation and loading of partitioned indexes, if NonStop SQL/MP database is installed on the system.

The RECGEN processes read the rows of the base NonStop SQL/MP table. SORTPROG processes the generated rows and writes them to the partitions of the index. RECGEN is invoked implicitly by NonStop SQL/MP database as required.

SORT

SORT is the interactive conversational interface to SORTPROG. SORT can only be used by a user with READ access to an input source. The following describes the source and target specifications for SORT:

FROM Specifies the name of an input source for a sort or merge run and the exclusion mode to use to open the file, the maximum number of records in the file, the maximum length of records in the file, and whether the records in the file are already sorted.

TO Specifies an output file for a sort run and parameters for the file including the percentage of data and index slack , whether FastSort should purge and recreate an existing output file, and the type of sort run (record, permutation, or key sort).

RISK SORT does not have inherent risks. The user must have read access to the input source. More risk may be placed upon input tapes that may contain sensitive data not accessible via disk files.

RISK SORT has a performance risk if not controlled.

AP-ADVICE-SORT-01 It may be desirable to limit interactive sorts, allowing sorts of application data files to be controlled via application processes.

SORTPROG

The SORTPROG process performs all sort or merge operations. It is initiated interactively from the SORT process or via application requests , however, it runs separately from the application process or the interactive SORT process. To configure and start a SORTPROG process, either:

Issue FastSort interactive commands

Call FastSort system procedures

Products that invoke FastSort systematically:

Application languages invoke sorts via system procedures calls

CROSSREF program sorts a cross-reference listing

ENFORM Database Manager sorts records for a report

File Utility Program (FUP) sorts to loads data into a file

NonStop SQL/MP database sorts entries in a query

NonStop SQL/MP database sorts data to load into a table or index

Peripheral Utility Program (PUP) sorts entries in the free-space table

NonStop TMF software sorts audit trail information

RISK Although SORTPROG performs the actual sort, no risk is attached to the actual sorting process. SORTPROG must be available to the general users and application for requested sort functions. Any risk associated with sorting is associated with the interactive SORT interface.

AP-ADVICE-SORT-02 Since FastSort is invoked from many subsystems, it is not recommended that a Safeguard protection Record be created that does not include everyone.

Securing SORT Components

BP-FILE-SORT-01 RECGEN should be secured "UUNU".

BP-OPSYS-OWNER-01 RECGEN should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-01 RECGEN must reside in $SYSTEM.SYSnn.

BP-FILE-SORT-02 SORT should be secured "UUNU".

BP-OPSYS-OWNER-01 SORT should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-01 SORT must reside in $SYSTEM.SYSnn.

BP-FILE-SORT-03 SORTPROG should be secured "UUNU".

BP-OPSYS-LICENSE-01 SORTPROG must be LICENSED.

BP-OPSYS-OWNER-01 SORTPROG should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-01 SORTPROG must reside in $SYSTEM.SYSnn.

	Discovery Questions	Look here:
OPSYS-OWNER-01	Who owns the RECGEN object file?	Fileinfo
OPSYS-OWNER-01	Who owns the SORT object file?	Fileinfo
OPSYS-OWNER-01	Who owns the SORTPROG object file?	Fileinfo
OPSYS-LICENSE-01	Is SORTPROG object file licensed?	Fileinfo
FILE-SORT-01	Is the RECGEN object file secured correctly?	Fileinfo
FILE-SORT-02	Is the SORT object file secured correctly?	Fileinfo
FILE-SORT-03	Is the SORTPROG object file secured correctly?	Fileinfo

Related Topics

Securing Applications