MUPEX: Set Maximum Count for MU and PE Fields

#### Search Results

Search

# MUPEX: Set Maximum Count for MU and PE Fields

The MUPEX function is used to specify MU field or PE group limits for a file. This function cannot be run on files that use a PE field in a descriptor nor can it be run on system files. In addition, the maximum number of occurrences is also limited by the maximum size of a compressed record in data storage.

To increase the MU/PE count for a file that contains a PE group in a descriptor, any descriptors having to do with the PE group must first be released (using the ADADBS RELEASE function). After they have been released, the MUPECOUNT parameter can be set to "2" using the MUPEX function and the descriptors then reinverted (using the ADADBS INVERT function).

This document covers the following topics:

- Syntax

- Essential Parameters

- Optional Parameters

- Example

## Syntax

## Essential Parameters

> FILE: File Number

>   FILE specifies the file for which the maximum number of occurrences are to be set. Specify the valid file number of the file in the database for which you want MU and PE limits set.

>   System files cannot be changed.

> MUPECOUNT: Size of the count field

>   MUPECOUNT sets the maximum number of MU and PE occurrences allowed in the file. Valid values are "1" or "2".

>   A specification of "1" indicates that no more than 191 MU fields and PE groups will occur in the file; a specification of "2" indicates that the file may contain as many as 65534 MU fields and PE groups.

>   To set the MUPECOUNT parameter to "1", the file must either be empty or have no MU or PE fields. To set the MUPECOUNT to "2", the file cannot contain a PE field that is part of a DE field unless the file is empty.

## Optional Parameters

> 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

>   The password of the file for which MU and PE field counts are to be limited. This parameter is required if the file is password-protected. Specify the password between apostrophes ('). In addition, the password must provide update authority for this function to work correctly.

> 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

In the following example, the maximum number of MU and PE field elements that can be stored in file 17 is 65534:

    ADADBS MUPEX FILE=17,MUPECOUNT=2

### On this page

- Syntax
- Essential Parameters
- Optional Parameters
- Example