6 2 3 Field and File Defaults

6.2.3 Field and File Defaults

To display the Work with Field and File Defaults screen, select Administration from the Main System Menu (Advanced), choose Review system settings from the Administration Menu and then select Field and File defaults from the Review of System Settings menu.

The settings on the Work with Field and File Defaults screen are retrieved from these data areas:

Field default attributes

Positions 158 - 317 in data area DC@A01.

These specify the default attributes for fields. The values specified must be valid field attributes.  Refer to information on fields for a detailed list of valid attributes.

File default SIZE parameter

Positions 112 - 141 in data area DC@A01.

This default SIZE parameter is used when initially creating LANSA files. The initial number of records, the increment number of records and the maximum increments may be specified. The parameter must be a valid IBM i size parameter.

File default LVLCHK parameter

Positions 142 - 145 in data area DC@A01.

This default level check, LVLCHK, parameter is used when initially creating LANSA files.

File default commitment control

Position 391 in data area DC@A01.

This default commitment control value is used when initially creating LANSA files. It specifies whether or not the file is to be placed under commitment control. Refer to information on files for a detailed description of the commitment control parameter.

Always build using SQL

Set this option to Y to indicate that physical files and logical files on IBM i are to be built using SQL as much as possible when in an RDMLX partition. The physical file will be built as an SQL table. This keyword will have no effect on how logical files are built, and logical files sharing the access path of  a corresponding SQL index no longer occurs.

Note that there are some valid CRTPF /CHGPF parameters that will not be able to be applied to physical files created as tables using SQL, and similarly some valid CRTLF / CHGLF parameters that will not be able to be applied to logical files created as indexes. One such parameter for both is MAXMBRS with a value other than 1 or *SAME.

RDML files built when the *SQL_BUILD option is in effect can be imported to RDML partitions provided they do not have DB triggers set on, however if they are rebuilt in the RDML partition they lose the effects of the *SQL_BUILD option.