The default release specification defines the data management software release to be used for any usercodes not specifically named in the user specification. You can include only one default release specification in your Query Processor configuration file. If a default release specification is not declared, the first release specified in the file becomes the default release specification.
The following diagrams illustrate the syntax of the default release specification:
<default release specification>
── DEFAULT ─┬────────────────┬─┬───────────┬─┬─────┬───────────────────►
└─<limit clause>─┘ └─ RELEASE ─┘ └─ = ─┘
►─<release identifier>─────────────────────────────────────────────────┤ <limit clause>
── LIMIT ─┬─────┬─┬─<limit value>─┬────────────────────────────────────┤
└─ = ─┘ └─ UNLIMITED ───┘The following table explains the elements of the syntax diagrams.
|
Element |
Definition |
|---|---|
|
<limit clause> |
Enables the system administrator to impose an upper limit on the number of database operations performed by a single SQL query. Refer to Using the Limit Clause later in this section for limit clause information. |
|
<limit value> |
Identifies the maximum number of database operations allowed in one SQL query. The limit value must be an integer between 1 and 1000000. |
|
UNLIMITED |
Indicates that no limit is applied to the specified usercodes. UNLIMITED is the default if no limit clause is specified. |
|
<release identifier> |
Names the software that is to be used by anyone accessing the data management software from a usercode that is not explicitly mentioned in the Query Processor configuration file. The designated release identifier must appear in a release specification before it can be used in the default release specification. |
