This document provides information on the parameters that can be set in the global and local configuration files.
+------------------------------------------------------------------------------+
¦File Edit Configuration Search ¦
+----------------------------------+---------------------------+---------------+
¦ Global Configuration File ¦
¦ Local Configuration File ¦
+---------------------------+
|
The configuration files can only be modified by an administrator. They should only be changed with the Configuration Utility.
After a new Natural installation, the default administrator name is DBA. For this administrator, the menu is available. The administrator DBA can then add further administrators to the local configuration file as defined in the section Administrator Assignments.
The following topics are covered below:
This parameter group contains the following categories:
The parameters which apply to the database management system assignments are grouped under the following headings:
A table is shown which is used to define the database ID with which the database is mapped in the DDM.
When DBMS assignments have already been defined, they are shown in the table.
The database ID.
Note:
If you are using DDMs where the database ID is set to
"0", a separate entry where the database ID is also
set to "0" must exist, with the corresponding
database type specified. This entry is used at compilation time in order to
generate the corresponding database statements into the generated program (GP).
Since the types of all databases which are to be accessed by Natural must be defined in the global configuration file, specify one of the following values for each database ID:
| Value | Description |
|---|---|
| ADA | Adabas database server (this is the default). |
| ADA2 | Adabas database server. This database type
is provided for use with Adabas as of version 6 on Open Systems and Adabas as
of version 8 on mainframes. In particular, it supports Adabas LA fields, Adabas
large object fields and Natural view sizes greater than 64 KB.
See also Adabas Database Management Interfaces ADA and ADA2 in the Programming Guide. |
Important:
You must not define a database type for a DBID which has
already been assigned to a system file in the global configuration file (see
System
Files). If you do so, an error message will be issued at
Natural startup, indicating an inconsistency in the system file setting and an
error when reading the database assignments.
At compilation time, the profile parameter
UDB is not
used to determine the database type. UDB is only used at
runtime to determine the database type. The database types must be the same at
compilation time and at runtime.
Exception: For compatibility reasons, it is possible to use database type ADA at compilation time and ADA2 at runtime.
The settings for Adabas Trace are for error diagnostics reasons. They should only be filled out when requested by Software AG support. Software AG support will provide valid values in this case.
With dictionary servers, you can access free rules and automatic rules maintained in Predict once you have access to Predict on a mainframe or UNIX host.
You can assign so-called dictionary servers (a free rule server and an automatic rule server) to one common logical server name. It is possible to define more than one logical server name where each name represents a different pair of free rule server and automatic rule server. The servers to be assigned can be located on different nodes.
In the global configuration file, you define all dictionary servers that are available for selection in the parameter file. The name of the logical server that is to be used must then be defined in the parameter file. See Remote Dictionary Access in the Overview of Profile Parameters.
You can specify the following information:
Specify the name for a logical dictionary server.
Specify the server name and node name for the server that is to be used for remote access to Predict free rules.
Specify the server name and node name for the server that is to be used for remote access to Predict automatic rules.
The following parameters are used to define the name and port number for the HTTP server.
| Option | See the Parameter Reference for a description of this profile parameter |
|---|---|
| HTTP proxy address to use | PROX
|
| HTTP proxy port number | PROXPORT |
| Do not use proxy for addresses | NOPROX |
| HTTPS proxy address to use | SSLPRX |
| HTTPS proxy port number | SSLPRXPT |
| Do not use SSL proxy for addresses | NOSSLPRX |
You can specify a directory common to all installed Natural versions, which is to contain operating system-specific work files and temporary files used by all these Natural versions. These files are required for synchronization purposes and must not be deleted or modified by a Natural Administrator.
Note:
If you use the system directory for temporary files, ensure that no
automatic procedures regularly delete the contents.
When you choose this function, the currently defined ports are shown in a window. When you edit a port number (by entering "E" next to the port number and pressing ENTER), the environment assignments are shown. You can also choose , which is shown at the top of the window, to add environment assignments for further ports.
You can assign user-specific environments for any Natural development server (NDV). To do so, use the following syntax in the Environment column:
VARIABLE=VALUE[;VARIABLE=VALUE]...
Example:
+----------------- Environment settings for NDV port <1234> ------------------+ ¦ C User Environment ¦ ¦ USER1 MYWRKFILE=/natural/prog/user1;NDVSESSION=naturalins ¦ ¦ USER2 MYWRKFILE=/natural/prog/user2;NDVSESSION=naturaltr;NAT_TRACE=1 ¦ ¦ USER3 MYWRKFILE=/natural/prog/user3;NDVSESSION=naturalsql ¦ ¦ ¦ |
In the above example, 3 user environments for the server started on
port 1234 are defined. The environment variable
MYWRKFILE defines the path of a Natural work file.
This environment variable can then be used in the
Work
Files section of a parameter file to define the location
of the work file, depending on the defined user.
The variable NDVSESSION specifies the
Natural image to be loaded when a mapping to the server takes place. It is only
known by the Natural development server.
Suppose Natural Studio is mapping to a Natural development server with
port 1234 and user ID USER2: the server loads naturaltr as the
Natural session and any Adabas call of a started application will be traced.
Work files defined with MYWRKFILE will be written
to the location /natural/prog/user2.
For information on how to configure a Natural development server under OpenVMS, see the Natural Development Server for OpenVMS documentation.
Printer profiles are used for printing additional reports, for hardcopies and for batch output generation. They recognize particular Natural field attributes and insert the appropriate control sequences (see below) as defined in the profile.
With the ability to translate Natural field attributes into escape sequences, you can control your printer in various ways by using the right profile name, and you can use the print features of a given device by using simple attributes in Natural programs.
Each profile that you define can be assigned to a Natural report number
either statically by using the Configuration Utility (see
Device/Report
Assignments), or dynamically by using the
DEFINE PRINTER
statement within a Natural program.
You can specify the following information:
Specify the name of a new printer profile. Or press PF2 to select a defined printer profile from a list.
Optional. An external character set must be defined, for example, if a printer's character set is different from the system character set, or if you wish to preserve Unicode data by outputting the data in UTF-8 format.
You can specify the name of the external character set. If the name is "UTF-8", the data are converted into UTF-8 format. Otherwise, any name can be used, but it must agree with the name used in the character translation table definition in the file NATCONV.INI. For example, if the internal character set name (as defined near the top of the NATCONV.INI file) is "ISO8859_1" and you define "FRED" as the name of the external character set in the printer profile, a section with the following name must be defined in the file NATCONV.INI, otherwise no character translation is performed:
[ISO8859_1 -> FRED]
Note that, in the non-UTF-8 case, the data are first converted from the in-memory format (UTF-16) into the system code page, prior to any NATCONV.INI-based translation being applied.
For further information on the NATCONV.INI file, see Support of Different Character Sets with NATCONV.INI in the Operations documentation.
You can specify whether commands to be triggered at job, page or field level.
| Option | Description | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Trigger |
|
||||||||||||
| Leading command | The leading control sequence is inserted immediately before the triggering event (for example, to define a job header or to set attributes for field representation). | ||||||||||||
| Trailing command | The trailing control sequence is inserted immediately after the triggering event (for example, to define a job trailer or to reset attributes previously set). | ||||||||||||
For each control sequence, you can specify the control characters in either alphanumeric or hexadecimal format.
Notes:
This example shows the PCL command for setting a proportional character spacing in both alphanumeric and hexadecimal format. The escape character "^1b", which must always be specified in hexadecimal format, corresponds to the decimal value 27.
Alphanumeric format:
^1b(s1P
Hexadecimal format:
^1b^28^73^31^50
Mark this field with "Y" if you want to delete the currently displayed profile.
A list of existing Natural system file assignments is shown.
The paths for all possible system files (that is: for all possible DBID/FNR combinations) are defined in the global configuration file. These must be valid paths which indicate the physical location of the system files on the disk.
You can specify the following information:
The database ID.
The file number.
This feature applies when working in a remote development environment (SPoD) with Natural for Windows.
When you specify an alias name for a system file, this name is shown in Natural Studio's library workspace.
The path to the system file.
The DBID/FNR combination for each defined system file can then be defined in the parameter file. See System Files in the Overview of Profile Parameters.
This parameter group contains the following categories:
You can specify whether a user is to be a Natural administrator or a configuration administrator. The following combinations are possible:
+----- Administrator Assignments -----+ ¦ C User Name Administrator ¦ ¦ NATURAL CONFIGURATION ¦ ¦ NAT1 Y Y ¦ ¦ NAT2 Y N ¦ ¦ NAT3 N Y ¦ ¦ NAT4 N N ¦ |
When a user is defined as both Natural administrator and configuration administrator (Y/Y), the user can modify all parameter files as well as the global and local configuration files. When such a user invokes the Configuration Utility, "(Config)" is shown in the right-hand corner of the screen (instead of the user ID).
Note:
Only Natural administrators can be defined as configuration
administrators. However, when a user is defined only as a configuration
administrator (N/Y), the above information applies. This is handled as if the
user has been defined as both Natural administrator and configuration
administrator (Y/Y).
When a user is defined only as a Natural administrator (Y/N), the user can modify all parameter files. The menu is not shown; thus, modification of the configuration files is not possible. When such a user invokes the Configuration Utility, "(Admin)" is shown in the right-hand corner of the screen (instead of the user ID).
When a user is neither defined as a Natural administrator nor as a configuration administrator (N/N), the user can only modify his own parameter file. When such a user invokes the Configuration Utility, the user ID is shown in the right-hand corner of the screen.
A table is shown which is used to define buffer pools. See also Natural Buffer Pool in the Operations documentation.
You can specify the following information:
The name of the Natural buffer pool. The name can be up to 8
characters long. The name of the default buffer pool is NATBP. See
also BPID
in the Parameter Reference.
Caution:
Do not delete the default buffer pool NATBP, as
it is possible that Natural may not function properly anymore.
The size of the Natural local buffer pool. This setting is used
during startup of the Natural buffer pool by the
NATBPSRV
server to create a global shared memory segment of the specified size.
Possible settings: 1 - 512 MB.
Default setting: 1.
The maximum number of users that can have simultaneous access to the buffer pool. This number determines the sizes of some internal tables stored inside the shared memory during startup.
Possible settings: 1 - 5000.
Default setting: 20.
The number of directory entries. This value is used by the
NATBPSRV
server during the start of the buffer pool. If the maximum value has been
reached, this value is automatically increased.
Possible settings: 10 - 9999.
Default setting: 10.
Specifies whether the system resources of a buffer pool, such as locks and the global section, are created system-wide or group-wide.
It is recommended to set this value before starting the buffer pool and to keep the chosen value until the buffer pool has been terminated.
Possible settings: 0 (group-wide) or 1 (system-wide).
Default setting: 1.
Specifies whether the section file is to be deleted when the buffer pool is shut down.
Possible settings: 0 (do not delete section file) or 1 (delete section file).
Default setting: 0.
Press ENTER to edit/display the following information:
Lock Resource Name
The name of the lock resource needed by the buffer pool.
Global Section Descriptor Name
The name of the global section to be used by the buffer pool.
Section File Name
The file that contains the global section. The default value
"NATBPDEV" is a logical name which is defined when
the buffer pool is started by the command procedure
NATETC:NATBPENV_<node>.COM.
This command procedure is created during installation.
You can specify the following:
The location of the Natural parameter files.
The location of the Natural user profiles.
The name and location of the global configuration file (default name is NATCONF.CFG).
The location of the Natural error files.
The name of the file which contains the character translation tables used with the internal character set ISO-8859-1. By default, this file is called NATCONV.INI. See Support of Different Character Sets with NATCONV.INI in the Operations documentation for further information.
The location of Natural temporary output.
Instead of defining a specific path, you can use a logical name or concealed device to define the path (for example: NATDIR:[tmp]). At runtime, the path will be used with the currently valid setting of the logical name or concealed device.
The name of the database which contains the descriptions of the terminal capabilities for each terminal type supported by Natural. See Natural Termcap (NATTERMCAP) Utility in the Utilities documentation for further information.
The location of messages, choices and help texts used by the editors and by the Natural Termcap utility.
Note:
When specifying a path, you can use logical names or
concealed devices. When you press TAB after having
specified a valid path, the path is automatically expanded.
