RELEASE: Release Descriptor

#### Search Results

Search

# RELEASE: Release Descriptor

The RELEASE function releases a descriptor from the descriptor space.

This function results in the release of all space currently occupied in the Associator inverted list for this descriptor. This space can then be reused for this file by reordering or ADALOD UPDATE. No changes are made to Data Storage.

When releasing descriptor space for an Adabas expanded file, perform the RELEASE function for each individual component file of the expanded file. Each RELEASE operation on a component file causes a message that confirms the change, and returns condition code 4.

This utility function does not need to lock the database file for its use; this function can perform its processing in parallel with active users. This means that you do not need to set the file to read-only status to run this utility function.

It is not possible to release a descriptor which has Security By Value set on it; you must first remove this security option on the descriptor before releasing it. For complete information about Adabas Security, contact your Software AG representative.

This document covers the following topics:

- Essential Parameters

- Optional Parameters

- Example

## Essential Parameters

> FILE: File Number

>   FILE specifies the file that contains the descriptor to be released. The file cannot be an Adabas system file.

> DESCRIPTOR: Descriptor to Be Released

>   DESCRIPTOR specifies the descriptor to be released. Any descriptor type can be specified. A descriptor currently being used as the basis for file coupling cannot be specified. If the descriptor being released is an ADAM descriptor, the file is no longer processed as an ADAM file.

## Optional Parameters

> INPARALLEL: Execute function in parallel

>   When INPARALLEL=YES (the default) is specified, the function may be executed even if other users are active on the file. Adabas performs the function while all application commands against the file are temporarily quiesced and suspended. The integrity of the file targeted by the ADADBS function is maintained.

>   With INPARALLEL=NO, the function requires exclusive file control – that is, no applications can be executing against the file. Adabas refuses to execute the function (with response code 48) if other users are active on the file.

> NOUSERABEND: Termination without Abend

>   When a parameter error or a functional error occurs while this utility function is running, the utility ordinarily prints an error message and terminates with user abend 34 (with a dump) or user abend 35 (without a dump). If NOUSERABEND is specified, the utility will not abend after printing the error message. Instead, the message "utility TERMINATED DUE TO ERROR CONDITION" is displayed and the utility terminates with condition code 20.

>   Note
>   When NOUSERABEND is specified, we recommend that it be specified as the first parameter of the utility function (before all other parameters). This is necessary to ensure that its parameter error processing occurs properly.

> PASSWORD: File Password

>   This parameter is required if the file is password-protected. Specify the password between apostrophes (').

> TEST: Test Syntax

>   The TEST parameter tests the operation syntax without actually performing the operation. Only the syntax of the specified parameters can be tested; not the validity of values and variables. See Syntax Checking with the TEST Parameter for more information on using the TEST parameter in ADADBS functions.

## Example

    ADADBS RELEASE FILE=31,DESCRIPTOR='AA'

Descriptor AA in file 31 is released from descriptor status.

### On this page

- Essential Parameters
- Optional Parameters
- Example