Summary of runtime considerations for processing database files

 

These tables show whether you can specify a particular file processing option on a CL command and in a high-level language. For parameters that can be specified in more than one place, the system merges the values. The Override with Database File (OVRDBF) command parameters take precedence over program parameters, and Open Database File (OPNDBF) or Open Query File (OPNQRYF) command parameters take precedence over create or change file parameters.

Any override parameters other than TOFILE, MBR, LVLCHK, SEQONLY, SHARE, WAITRCD, and INHWRT are ignored by the OPNQRYF command.

The parameters in the following tables are arranged in the order of importance. If a new parameter is related to an existing parameter, it is added next to the existing parameter.

Table 1. Database processing options specified on CL commands
Description Parameter Command
CRTPF, CRTLF CHGPF, CHGLF OPNDBF OPNQRYF OVRDBF
File name FILE Yes Yes1 Yes Yes Yes
Library name LIB Yes Yes2 Yes Yes Yes
Member name MBR Yes No Yes Yes Yes
Member processing options OPTION No No Yes Yes No
Record format lock state RCDFMTLCK No No No No Yes
Starting file position after open POSITION No No No No Yes
Program performs only sequential processing SEQONLY No No Yes Yes Yes
Ignore keyed sequence access path ACCPTH No No Yes No No
Time to wait for file locks WAITFILE Yes Yes No No Yes
Time to wait for record locks WAITRCD Yes Yes No No Yes
Prevent overrides SECURE No No No No Yes
Number of records to be transferred from auxiliary to main storage NBRRCDS No No No No Yes
Share open data path with other programs SHARE Yes3 Yes4 No No Yes
Format selector FMTSLR Yes5 Yes5 No No Yes
Force ratio FRCRATIO Yes Yes No No Yes
Inhibit write INHWRT No No No No Yes
Level check record formats LVLCHK Yes Yes No No Yes
Expiration date checking EXPCHK No No No No Yes
Expiration date EXPDATE Yes6 Yes6 No No Yes
Force access path FRCACCPTH Yes Yes No No No
Commitment control COMMIT No No Yes Yes No
End-of-file delay EOFDLY No No No No Yes
Duplicate key check DUPKEYCHK No No Yes Yes No
Reuse deleted record space REUSEDLT Yes6 Yes6 No No No
Coded character set identifier CCSID Yes6 Yes6 No No No
Sort sequence SRTSEQ Yes Yes7 No Yes No
Language identifier LANGID Yes Yes7 No Yes No

1 File name: The CHGPF and CHGLF commands use the file name for identification only. You cannot change the file name.

2 Library name: The CHGPF and CHGLF commands use the library name for identification only. You cannot change the library name.

3 Share open data path with other programs: It applies only to members that are added on the create file request.

4 Share open data path with other programs: It applies only to the current members of the file on the change file request.

5 Format selector: It is used on the CRTLF and CHGLF commands only.

6 Expiration date, reuse deleted records, and coded character set identifier: They are used on the CRTPF and CHGPF commands only.

7 Sort sequence and language identifier: They cannot be specified on the CHGLF command. They can be specified on the CHGPF command only when they are used in conjunction with the source file.

Table 2. Database processing options specified in high-level language programs
Description RPG/400® ILE RPG COBOL/400® ILE COBOL PL/I
File name Yes Yes Yes Yes Yes
Library name No Yes No No Yes
Member name No Yes No No Yes
Record length Yes Yes Yes Yes Yes
Member processing options Yes Yes Yes Yes Yes
Record format lock state No No No No Yes
Record formats the program will use Yes Yes No No No
Clear physical file member of records No No Yes Yes No
Program performs only sequential processing Yes Yes Yes Yes Yes
Ignore keyed sequence access path Yes Yes Yes Yes Yes
Share open data path with other programs No No No No Yes
Level check record formats Yes Yes Yes Yes Yes
Commitment control Yes Yes Yes Yes Yes
Duplicate key check No No Yes Yes No

Control language (CL) programs can also specify many of these parameters. See Table 1 for more information about the database processing options that can be specified on CL commands.

 

Parent topic:

Database file processing: Runtime considerations