PROFILE - Apply Parameter Profile

#### Search Results

Search

# PROFILE - Apply Parameter Profile

This Natural profile parameter can be used to apply a parameter profile.

Instead of having to specify a whole string of individual parameters each time you invoke Natural, you can specify the string of parameters once, store this string under a profile name and then invoke Natural with this parameter profile. The parameters defined with this profile are then passed to Natural as dynamic profile parameters.

You create and maintain these profiles with the SYSPARM utility (described in the Utilities documentation).

You can use the profile parameter `FPROF` to specify a system file for parameter profiles (`FPROF`).

Possible settings | See PROFILE Parameter Syntax.
Default setting | none |
Dynamic specification | yes |
Specification within session | no |

Notes:

1. If the `PROFILE` parameter is specified in the Natural parameter module, it is evaluated after the other parameters in the parameter module, but before any dynamically specified profile parameters are evaluated; this means that parameters specified within the profile can be overridden by individually specified dynamic parameters.
2. To restrict the use of a profile, you can use the profile parameter `USER`.
3. Unlike other parameters, a `PROFILE` parameter specification cannot be overwritten by another `PROFILE`. So you can have multiple parameter profiles which are evaluated all in a sequence.
4. The `PROFILE` parameter cannot be used with `ADARUN MODE=SINGLE`.

This document covers the following topics:

- PROFILE Parameter Syntax

## PROFILE Parameter Syntax

The `PROFILE` parameter is specified using either of the following syntax options:

Syntax 1 - Default Database/File:

PROFILE= |  | profile-name AUTO PROGRAM TERMINAL |

Syntax 2 - Specified Database/File:

PROFILE=( |  | profile-name AUTO PROGRAM TERMINAL |  | ,dbid,fnr,password,cipher-key)

The elements of the syntax diagrams are described in the following section.

For explanations of the symbols used in the syntax diagrams, see Syntax Symbols (Statements documentation).

### Storage Location of Parameter Profiles

Storage of parameter profiles depends on whether the database ID and file number are specified with the `PROFILE` parameter. The following applies:

- If the database ID and file number are not specified with `PROFILE` (Syntax 1), default settings are used:

  1. If the `FPROF` profile parameter is set, the parameter profile is read from the current `FPROF` system file.

  2. If the `FPROF` profile parameter is not set, the parameter profile is read from the current `FNAT` system file.

- If the database ID and file number are specified with `PROFILE` (Syntax 2), the specified values are used.

### Syntax Element Description

Syntax Element | Value | Explanation
--- | --- | ---
`profile-name` | 1 - 8 characters | The name of the profile to be used. If you want that all profiles used during a session are read from a database and system file other than the default, specify the following before you use the first profile:
    PROFILE=(,dbid,fnr)
`AUTO` | n/a | Natural takes the current TP user ID (as contained in the system variable `*INIT-USER`) as profile name, which means that the profile defined under the name corresponding to that ID is used. If no such profile is found, a profile named `AUTO` is used instead (if available). You can define such an `AUTO` profile as default profile for users without individual profiles.
`PROGRAM` | n/a | Natural takes the name of the program currently executing as Natural (as contained in the system variable `*INIT-PROGRAM`) as profile name, which means that the profile defined under this name is used. If no such profile is found, a profile named `PROGRAM` is used instead (if available). You can define such a `PROGRAM` profile as default profile for users without individual profiles.
`TERMINAL` | n/a | Natural takes the current terminal ID (as contained in the system variable `*INIT-ID`) as profile name, which means that the profile defined under the name corresponding to that ID is used. If no such profile is found, a profile named `TERMINAL` is used instead (if available). You can define such a `TERMINAL` profile as default profile for users without individual profiles.
`dbid` | `1 - 65535`, except `255` | The ID of the database (DBID) in which the Natural system file for parameter profiles is located. If `dbid` is not specified, the corresponding value of the profile parameter `DBID` is used.
`fnr` | `1 - 65535` | The file number (FNR) of the database in which the Natural system file for parameter profiles is located. If `fnr` is not specified, the corresponding value of the profile parameter `FNR` is used.
`password` | 1 - 8 characters | The Adabas password if required for a password-protected Natural system file. If `password` is not specified, the corresponding value of the profile parameter `SYSPSW` is used.
`cipher-key` | 8 characters | The Adabas cipher key if required for a password-protected Natural system file. If `cipher-key` is not specified, the corresponding value of the profile parameter `SYSCIP` is used.