Release Specification

You must include at least one release specification in your Query Processor configuration file. Each release specification identifies the location of some set of Query Processor software that can be accessed by a system user. You can tailor the release specifications to suit individual users or groups of users.

You can also build release specifications from other release specifications contained in your Query Processor configuration file.

A release specification can be used multiple times for the same release identifier; however, only the last set of specifications is recognized. If the same release identifier is defined multiple times, a warning message appears.

The following diagrams illustrate the syntax of a release specification:

<release specification>

── RELEASE ──<release identifier>─┬────────────────────────────────┬───►
                                  └─ = ──<base release identifier>─┘
►─┬────────────────────────────────────────────────┬───────────────────►
  │     ┌►──────────────── , ────────────────┐     │
  └─ ( ─┴───/1\─ PACK ── = ──<family name>───┴─ ) ─┘
►─┬────────────────────────────────────────┬───────────────────────────┤
  │ ┌►───────────────────────────────────┐ │
  └─┴─ SL ──<SL name>── = ──<file title>─┴─┘

<file title>

                           ┌►──────── / ───────┐
──┬──────────────────────┬─┴─/12\─<identifier>─┴───────────────────────►
  ├─ ( ──<usercode>── ) ─┤
  └─ * ──────────────────┘
►─┬─────────────────────┬──────────────────────────────────────────────┤
  └─ ON ──<family name>─┘

The following table explains the elements of the syntax diagrams.

Element

Definition

<release identifier>

Identifies the software to be used for a particular release. The release identifier is a contiguous group of no more than 17 characters. The release identifier cannot contain a space, colon (:), semicolon (;), equal sign (=), comma (,), left parenthesis ( ( ), or right parenthesis ( ) ). Examples of valid release identifiers include

  • PRODRELEASE

  • BETARELEASE

  • MYRELEASE

<base release identifier>

Names a release identifier declared earlier in a release specification in the same file. The software named in the earlier release specification becomes associated with the release identifier you are using in this release specification.

This ability to associate the information in one release specification with one or more other release specifications enables you to tailor your environment to the needs of individual users as well as to groups of users.

PACK = <family name>

Designates the pack location for the software identified in this release specification. If an individual piece of software resides on a pack other than the designated pack, you must use the SL statement to identify the name and location of the file.

If you do not include a PACK statement in the release specification, the software is located using standard enterprise server file-search conventions.

SL

Identifies the command used to map a function name to a library file. Use the SL statement if a piece of the data management software resides in a location different from the default location identified in the PACK statement, or if the software does not follow the default naming convention.

<SL name>

Identifies one of the system library configuration functions.

<file title>

Identifies the name of the file containing the code for the data management software.

<usercode>

Identifies the usercode under which the data management code file is contained. The usercode can contain from 1 to 17 alphanumeric characters. The first character must be either a letter or a number. The remainder of the characters can be letters, numbers, underscores (_), or hyphens (-).

<identifier>

Specifies a node in the name of the data management code file. The identifier can contain from 1 to 17 alphanumeric characters. The first character must be either a letter or a number. The remainder of the characters can be letters, numbers, underscores (_), or hyphens (-).

<family name>

Identifies the pack on which the data management code file resides. The family name can contain from 1 to 17 alphanumeric characters.

Usually it is necessary only to identify the level of software you want to use and the pack on which the software resides. However, in a release specification you can designate different locations for any of the Query Processor configuration specifications. The following table lists each specification and the name of the code file that the specification is associated with by default.

Note: The following table lists Query Processor configuration specifications, not Query Processor settings.

Query Processor Configuration Specification

Default Name

MCPSQLADMIN

*SYSTEM/MCPSQL/ADMIN

MCPSQLDRIVER

*SYSTEM/MCPSQL/DRIVER

MCPSQLDMSIIMAPPER

*SYSTEM/MCPSQL/DMSIIMAPPER

MCPSQLPARSER

*SYSTEM/MCPSQL/PARSER

MCPSQLSCODESUPPORT

*SYSTEM/MCPSQL/SCODESUPPORT

MCPSQLSUPPORT

*SYSTEM/MCPSQL/SUPPORT

MCPSQLCATALOG

*DESCRIPTION/SQLDIR/MCPSQL-CATALOG

MCPSQLSCODE

MCPSQLSCODE

Prev  Up  Next
Creating the Query Processor Configuration File  Home  User Specification