Retrieve Database File Description (QDBRTVFD) API

The Retrieve Database File Description (QDBRTVFD) API allows you to get complete and specific information about a file on a local or remote system. The information is returned to a receiver variable in either a file definition template or a format definition mapping. The file definition template provides more complete information about a database file than the Display File Description (DSPFD) command. The format definition provides complete information about the record formats of the file.

The format definition is used with the Query (QQQQRY) API to get data from a file. You can run the QDBRTVFD API to build a format definition that is later used to run a query. This format definition can be used several times to extract information from a database, making the Query API run faster. If the format definition is not created prior to running a query, the QQQQRY API must create one when it runs.

Authorities and Locks

Library Authority

*EXECUTE

File Authority

*OBJOPR

File Lock

*SHRNUP

Required Parameter Group

Receiver variable

OUTPUT; CHAR(*)

The receiver variable that is to receive the information requested. You can specify the size of the area smaller than the format requested as long as you specify the length of receiver variable parameter correctly. As a result, the API returns only the data the area can hold.

Length of receiver variable

INPUT; BINARY(4)

The length of the receiver variable provided. The length of receiver variable parameter may be specified up to the size of the receiver variable specified in the user program. If the length of receiver variable parameter specified is larger than the allocated size of the receiver variable specified in the user program, the results are not predictable. The minimum length is 8 bytes.

Qualified returned file name

OUTPUT; CHAR(20)

The actual qualified file name from which the file description has been extracted. If an override is active this file and library name may be different from the one entered with the API.

Format name

INPUT; CHAR(8)

The content and format of the information to be returned about the specified file, member, or format. You can use the following format names:

FILD0100	File definition template
FILD0200	Format definition template
FILD0300	Key field information template
FILD0400	Trigger information template

See Format of Generated Information for a description of these formats.

Qualified file name

INPUT; CHAR(20)

The name of the file about which the information is to be extracted and the library in which it is located. The first 10 characters contain the file name, and the second 10 characters contain the library name.

You can use the following special values for the library name:

*CURLIB	The job's current library
*LIBL	The library list

Record format name

INPUT; CHAR(10)

The name of the record format in the specified file that is to be used to generate the file description. (This parameter is used only with format FILD0200.)

You can use the following special value for the record format name

*FIRST

The first record format found

Override processing

INPUT; CHAR(1)

Whether overrides are to be processed. The following values are used:

0	No override processing
1	Override processing

System

INPUT; CHAR(10)

Whether the information that is returned is about a file on either a local or remote system, or both. The possible values are:

*LCL	The information returned is about local files only.
*RMT	The information returned is about remote files only.
*FILETYPE	The information returned is about files on both the local and remote systems. For DDM files, the information returned is about the remote file that was named on the RMTFILE parameter of the Create DDM File (CRTDDMF) command.

Format type

INPUT; CHAR(10)

Whether the logical formats returned are internal or external. (This parameter is used only with format FILD0200.) A description and examples of the internal (*INT) and external (*EXT) formats follow:

*EXT	The formats returned are external. If the specified file is a logical file, the format returns data for the logical fields defined in the logical record format. If the specified file is a physical file, the internal and external field names are the same.
*INT	The formats returned are internal. If the specified file is a logical file, the format returns data for the fields on which the logical fields are based. If the specified file is a physical file, the internal and external field names are the same.

The following are DDS, *EXT, and *INT format type examples: For a logical file definition of (1) that is based on a physical file definition of (2), a format type of *EXT would return (3) and a format type of *INT would return (4).

  Format Type Example DDS

  Logical file definition (1):

R	CONCAT1	PFILE(PF1)
	LFLD1	RENAME(FLD1)
	FLD2
	CATFLD	CONCAT(FLD1 FLD2 FLD3)
K	CATFLD

  Physical file definition (2):

	FLD1	5A
	FLD2	10A
	FLD3	5A
K	FLD1

  Format Type *EXT Example
  (3)

Record format name	CONCAT1
Record length	35
Number of fields	3
Internal field name 1	FLD1
External field name 1	LFLD1
Length of field 1	5
Internal field name 2	FLD2
External field name 2	FLD2
Length of field 2	10
Internal field name 3	FLD1
External field name 3	CATFLD
Length of field 3	20

  Format Type *INT Example
  (4)

Record format name	CONCAT1
Record length	35
Number of fields	5
Internal field name 1	FLD1
External field name 1	LFLD1
Length of field 1	5
Internal field name 2	FLD2
External field name 2	FLD2
Length of field 2	10
Internal field name 3	FLD1
External field name 3	CATFLD
Length of field 3	5
Internal field name 4	FLD2
External field name 4	CATFLD
Length of field 4	10
Internal field name 5	FLD3
External field name 5	CATFLD
Length of field 5	5

Error code

I/O; CHAR(*)

The structure in which to return error information. For the format of the structure, see Error code parameter.

Format of Generated Information

The QDBRTVFD API can be used to provide information in the following formats:

The following sections provide an overview of each of these formats. If an offset equals zero in the returned information, there is no corresponding structure associated with it.

The asterisk (*) in the Field column represents a reserved field. No variable is associated with these reserved fields.

FILD0100 Format (File Definition Template (FDT) header)

FILD0100 provides detailed information about how the file is built. FILD0100 Format shows how this information is organized. When more than one entry can appear, the figure indicates this as in (5).

Descriptions of the fields in this structure follow FILD0100 Format. The include source is supplied on the system, in source file H, member name QDBRTVFD, in the QSYSINC library. The field names in the following tables apply only to the ILE C include. See Include files and the QSYSINC library for the names of the OPM and ILE RPG and COBOL includes.

FILD0100 Format

File Definition Header (Qdb_Qdbfh)

Qdb_Qdbfh is the first structure and is located at offset zero of the returned data.

Offset		Bit	Type	Field	Description
Dec	Hex
0	0		BINARY(4)	Qdbfyret	Length of the data returned in bytes.
4	4		BINARY(4)	Qdbfyavl	Number of bytes provided for the file definition data.
8	8		BIT(16)	Qdbfhflg	Attributes bytes.
8	8	0	BIT(2)	Reserved_1	Reserved.
8	8	2	BIT(1)	Qdbfhfpl	Type of file. If on, the file is a logical database file. If off, a physical database file.
8	8	3	BIT(1)	Reserved_2	Reserved.
8	8	4	BIT(1)	Qdbfhfsu	File type (FILETYPE). If on, the file is a source file (*SRC). If off, a data file (*DATA).
8	8	5	BIT(1)	Reserved_3	Reserved.
8	8	6	BIT(1)	Qdbfhfky	Access path. If on, the file has a keyed sequence access path. If off, an arrival sequence access path.
8	8	7	BIT(1)	Reserved_4	Reserved.
9	9	0	BIT(1)	Qdbfhflc	Record format level check (LVLCHK). If on, the record format level identifiers are checked when the file is opened (*YES) if off, they are not checked when the file is opened (*NO).
9	9	1	BIT(1)	Qdbfkfso	Select/omit. If on, the file is a select/omit logical file.
9	9	2	BIT(4)	Reserved_5	Reserved.
9	9	6	BIT(1)	Qdbfigcd	Double-byte character set (DBCS) or Graphic data. If on, the file's record format(s) contains DBCS or Graphic data fields.
9	9	7	BIT(1)	Qdbfigcl	Double-byte character set (DBCS) or Graphic literals. If on, the file's record format(s) contains DBCS or Graphic literals.
10	A		CHAR(4)	Reserved_7	Reserved.
14	E		BINARY(2)	Qdbflbnum	Number of data members. 0 indicates an externally described physical file or a program described physical file that is not linked to a data dictionary. 1 through 32 indicates the number of data dictionary record formats for a program described physical file that is linked to a data dictionary or the number of based-on physical records for a logical file.
16	10		CHAR(14)	Qdbfkdat	Keyed sequence access path description. If this file has an arrival sequence access path, these fields are not applicable.
16	10		BINARY(2)	Qdbfknum	Number of key fields for the file. 1 through 120.
18	12		BINARY(2)	Qdbfkmxl	Maximum key length for the file. 1 through 2000.
20	14		CHAR(1)	Qdbfkflg	Keyed sequence access path attributes.
20	14	0	BIT(1)	Reserved_8	Reserved
20	14	1	BIT(1)	Qdbfkfcs	Alternate collating sequence (ALTSEQ). If on, an alternate collating sequence table is specified for the file.
20	14	2	BIT(4)	Reserved_9	Reserved.
20	14	6	BIT(1)	Qdbfkfrc	Force keyed access path (FRCACCPTH). If on, the access path and changed records are forced to auxiliary storage when the access path is changed (*YES).
20	14	7	BIT(1)	Qdbfkflt	Floating point key indicator. If on, the access path for the file contains floating point keys.
21	15		CHAR(1)	Qdbfkfdm	Access path maintenance (MAINT). I Immediate maintenance (*IMMED) D Delayed maintenance (*DLY) R Rebuild maintenance (*REBLD)
22	16		CHAR(8)	Reserved_10	Reserved.
30	1E		CHAR(10)	Qdbfhaut	Public authority (AUT). *CHANGE Public change authority *ALL Public all authority *USE Public use authority *EXCLUDE Public exclude authority authorization-list-name The name of the authorization list whose authority is used for the file. This is the original public authority that the file was created with, not the current public authority for the file.
40	28		CHAR(1)	Qdbfhupl	Preferred storage unit (UNIT). X'00' through X'FE' The file members can be allocated on any available auxiliary storage (*ANY). X'FF' The file members may be allocated on Solid State Disk media, if available (*SSD).
41	29		BINARY(2)	Qdbfhmxm	Maximum members (MAXMBRS). 0 No maximum is specified; 32,767 is used (*NOMAX). 1 through 32,767 The maximum number of members the file can have.
43	2B		BINARY(2)	Qdbfwtfi	Maximum file wait time (WAITFILE). -1 The default wait time specified in the class description is used (*CLS). 0 The program does not wait for the file; an immediate allocation is required (*IMMED). 1 through 32,767 The number of seconds a program waits for the file.
45	2D		BINARY(2)	Qdbfhfrt	Records to force a write (FRCRATIO). 0 There is force write ratio. 1 through 32,767 The number of inserted, updated, or deleted records that are explicitly forced to storage.
47	2F		BINARY(2)	Qdbfhmnum	Number of members, 0 through 32,767.
49	31		BINARY(2)	Qdbfapsize	Access path page size; -1 is not valid because access path is a 4 gigabyte access path; 0 is system determines page size from the key length of the access path; 8K,16K,32K,64K,128K,256K,512K bytes.
51	33		CHAR(7)	Reserved_11	Reserved.
58	3A		BINARY(2)	Qdbfbrwt	Maximum record wait time (WAITRCD). -2 The default wait time allowed by the system is used (*NOMAX). -1 The program does not wait for the record, an immediate allocation is required (*IMMED). 1 through 32,767 The number of seconds a program waits for the record.
60	3C		CHAR(1)	Qaaf	Additional attribute flags.
60	3C	0	BIT(7)	Reserved_12	Reserved
60	3C	7	BIT(1)	Qdbfpgmd	Program described file indicator. If on, the file is program described.
61	3D		BINARY(2)	Qdbffmtnum	Total number of record formats, 1 through 32.
63	3F		CHAR(2)	Qdbfhfl2	Additional attribute flags
63	3F	0	BIT(1)	Qdbfjnap	Access path journaled.
63	3F	1	BIT(1)	Reserved_13	Reserved.
63	3F	2	BIT(4)		File capability/operation flags.
63	3F	2	BIT(1)	Qdbfrdcp	Allow read operation. If on, records are not allowed to be read from the file.
63	3F	3	BIT(1)	Qdbfwtcp	Allow write operation. If on, records are not allowed to be written to the file.
63	3F	4	BIT(1)	Qdbfupcp	Allow update operation (ALWUPD). If on, records are not allowed to be updated in the file (*NO).
63	3F	5	BIT(1)	Qdbfdlcp	Allow delete operation (ALWDLT). If on, records are not allowed to be deleted from the file (*NO).
63	3F	6	BIT(9)	Reserved_14	Reserved.
64	40	7	BIT(1)	Qdbfkfnd	Null values cause duplicates indicator (UNIQUE). Only valid if Qdbfpact is equal to 'KU'. If on, null values do not cause duplicate keys in the file access path(s) (*EXCNULL).
65	41		BINARY(2)	Qdbfvrm	First supported version release modification level. New database support is used in the file that will prevent it from being saved and restored to a prior version, release, and modification level. X'0000' Pre-Version 2 Release 1 Modification 0 file. X'1500' Version 2 Release 1 Modification 0 V2R1M0 file. X'1501' Version 2 Release 1 Modification 1 V2R1M1 file. X'1600' Version 2 Release 2 Modification 0 V2R2M0 file. X'1700' Version 2 Release 3 Modification 0 V2R3M0 file. X'1F00' Version 3 Release 1 Modification 0 V3R1M0 file. X'2000' Version 3 Release 2 Modification 0 V3R2M0 file.
					X'2400' Version 3 Release 6 Modification 0 V3R6M0 file. X'2500' Version 3 Release 7 Modification 0 V3R7M0 file. X'2900' Version 4 Release 1 Modification 0 V4R1M0 file. X'2A00' Version 4 Release 2 Modification 0 V4R2M0 file. X'2B00' Version 4 Release 3 Modification 0 V4R3M0 file. X'2C00' Version 4 Release 4 Modification 0 V4R4M0 file. X'2D00' Version 4 Release 5 Modification 0 V4R5M0 file. X'3300' Version 5 Release 1 Modification 0 V5R1M0 file. X'3400' Version 5 Release 2 Modification 0 V5R2M0 file. X'3500' Version 5 Release 3 Modification 0 V5R3M0 file. X'3600' Version 5 Release 4 Modification 0 V5R4M0 file. X'3D00' Version 6 Release 1 Modification 0 V6R1M0 file. X'4700' Version 7 Release 1 Modification 0 V7R1M0 file.
67	43		CHAR(2)	Qaaf2	Additional attribute flags.
67	43	0	BIT(1)	Qdbfhmcs	Multiple coded character set identifier indicator (CCSID). If on, the file has more than one CCSID for its input and output character type fields. If the file has no character type fields, this bit is off.
67	43	1	BIT(1)	Reserved_15	Reserved.
67	43	2	BIT(1)	Qdbfknll	Allow null value key indicator (ALWNULL). If on, null value keys are allowed.
67	43	3	BIT(1)	Qdbf_nfld	Allow null value data (ALWNULL). If on, the file record format(s) allow null value fields.
67	43	4	BIT(1)	Qdbfvfld	Variable length data (VARLEN). If on, the file record format(s) contain variable length fields.
67	43	5	BIT(1)	Qdbftfld	Date/time/timestamp data. If on, the file record format(s) contain date, time, or timestamp fields.
67	43	6	BIT(1)	Qdbfgrph	Graphic data. If on, the file record formats contain graphic fields.
67	43	7	BIT(1)	Qdbfpkey	Primary key (*PRIKEY). If on, the access path for the file is a primary key.
68	44	0	BIT(1)	Qdbfunqc	Unique constraint (*UNQCST). If on, the access path for the file is a unique constraint.
68	44	1	BIT(2)	Reserved_118	Reserved.
68	44	3	BIT(1)	Qdbfapsz	Access path size (ACCPTHSIZ). If on (*MAX1TB), all access paths associated with this file will be allowed to occupy a maximum of 1 terabyte (1 099 511 627 776 bytes) of auxiliary storage. If off (*MAX4GB), all access paths associated with this file will be allowed to occupy a maximum of 4 gigabytes (4 294 966 272 bytes) of auxiliary storage.
68	44	4	BIT(1)	Qdbfdisf	Distributed file. If on, the file is a distributed file.
68	44	5	BIT(1)	Reserved_68	Reserved.
68	44	6	BIT(1)	Reserved_69	Reserved.
68	44	7	BIT(1)	Reserved_70	Reserved.
69	45		CHAR(13)	Qdbfhcrt	File level identifier. The date of the file in internal standard format (ISF), CYYMMDDHHMMSS.
82	52		CHAR(52)	Qdbfhtx	File text description.
82	52		CHAR(2)	Reserved_18	Reserved.
84	54		CHAR(50)	Qdbfhtxt	Text description (TEXT)
134	86		CHAR(13)	Reserved_19	Reserved.
147	93		CHAR(30)	Qdbfsrc	Source file fields. Must be hexadecimal zeros if there is no source file information.
147	93		CHAR(10)	Qdbfsrcf	Source file name.
157	9D		CHAR(10)	Qdbfsrcm	Source file member name.
167	A7		CHAR(10)	Qdbfsrcl	Source file library name.
177	B1		CHAR(1)	Qdbfkrcv	Access path recovery (RECOVER). A The file access path is built after the IPL is completed (*AFTIPL). N The file access path is built when the file is next opened (*NO). S The file access path is built during the IPL (*IPL).
178	B2		CHAR(1)	Qdbfh_dfp_round	Rounding mode to be used for decimal floating point (DECFLOAT) calculations. 0 *HALFEVEN 1 *HALFUP 2 *DOWN 3 *CEILING 4 *FLOOR 5 *HALFDOWN 6 *UP blank No decimal floating point fields or not an SQL view, SQL index with a derived key expression, SQL materialized query table or logical file.
179	B3		CHAR(1)	Qdbfh_dfp_warnings	Indicates whether warnings should be returned from decimal floating point (DECFLOAT) calculations. 0 Warnings are not returned. 1 Warnings are returned. blank No decimal floating point fields or not an SQL index with a derived key expression, SQL materialized query table or logical file.
180	B4		CHAR(21)	Reserved_20	Reserved.
201	C9		BINARY(2)	Qdbftcid	Coded character set identifier (CCSID) for text description. 0 There is no file text description. 1 through 65,535 The file text description CCSID.
203	CB		CHAR(2)	Qdbfasp	Auxiliary storage pool (ASP). X'0000' The file is located on the system auxiliary storage pool. X'0002' through X'0010' On which user auxiliary storage pool the file resides.
205	CD		CHAR(1)	Qdbfnbit	Complex objects flags.
205	CD	0	BIT(1)	Qdbfhudt	If on, the file record format has a user-defined type field.
205	CD	1	BIT(1)	Qdbfhlob	If on, the file record format has a large object field.
205	CD	2	BIT(1)	Qdbfhdtl	If on, the file record format has a datalink field. A datalink is a field data type that is used to point to another object that contains the data for that field.
205	CD	3	BIT(1)	Qdbfhudf	If on, the file uses a user-defined function.
205	CD	4	BIT(1)	Qdbfhlon	If on, the file has a datalink field with FILE LINK CONTROL.
205	CD	5	BIT(1)	Qdbfhlop	If on, the file is a logical file without any large object fields, but the based-on physical file has a large object field.
205	CD	6	BIT(1)	Qdbfhdll	If on, the file is a logical file without any datalink fields, but the based-on physical file has a datalink field.
205	CD	7	BIT(1)	Qdbfsqlvol	If on, the file is an SQL Volatile Table.
206	CE		BINARY(2)	Qdbfmxfnum	Maximum number of fields, 1 through 8000. Indicates the number of fields in the file's record format that contains the largest number of fields.
208	D0		CHAR(74)	Reserved_22	Reserved.
282	11A		CHAR(2)	Qdb_Qdbfidfl	Additional attribute flags.
282	11A	0	BIT(5)	Reserved_121	Reserved.
282	11A	5	BIT(1)	Qdbf_File_Has_Identity_Column	If on, the file record format has an identity column.
282	11A	6	BIT(1)	Qdbf_File_Has_Rowid	If on, the file record format has a row ID column.
282	11A	7	BIT(1)	Qdbfh_Row_Change_Timestamp	If on, the file record format has a Row Change Timestamp column.
283	11B	0	BIT(6)	Reserved_122	Reserved.
283	11B	6	BIT(1)	Qdbf_Keep_In_Memory	If on, the keep in memory attribute of the file has been changed to *YES.
283	11B	7	BIT(1)	Reserved_124	Reserved.
284	11C		BINARY(4)	Qdbfodic	Offset from the start of the FDT header, Qdb_Qdbfh, to the IDDU/SQL Data Dictionary area, Qdbfdic.
288	120		CHAR(14)	Reserved_23	Reserved.
302	12E		BINARY(2)	Qdbffigl	File generic key length, 0 through 2000. The length of the key before the first *NONE key field for the file. If this file has an arrival sequence access path, this field is not applicable.
304	130		BINARY(2)	Qdbfmxrl	Maximum record length, 1 through 32,766. The length of the record in the file's record format that contains the largest number of bytes.
306	132		CHAR(8)	Reserved_24	Reserved.
314	13A		BINARY(2)	Qdbfgkct	File generic key field count, 0 through 120. The count of the number of key fields before the first *NONE key field for the file. If this file has an arrival sequence access path, this field is not applicable.
316	13C		BINARY(4)	Qdbfos	Offset from the start of the FDT header, Qdb_Qdbfh, to the file scope array, Qdbfb.
320	140		CHAR(8)	Reserved_25	Reserved.
328	146		BINARY(4)	Qdbfocs	Offset from the start of the FDT header, Qdb_Qdbfh, to the alternative collating sequence table section, Qdb_Qdbfacs.
332	14C		CHAR(4)	Reserved_26	Reserved.
336	150		CHAR(2)	Qdbfpact	Access path type. AR Arrival sequence access path. KC Keyed sequence access path with duplicate keys allowed. Duplicate keys are accessed in first-changed-first-out (FCFO) order. KF Keyed sequence access path with duplicate keys allowed. Duplicate keys are accessed in first-in-first-out (FIFO) order. KL Keyed sequence access path with duplicate keys allowed. Duplicate keys are accessed in last-in-first-out (LIFO) order. KN Keyed sequence access path with duplicate keys allowed. No order is guaranteed when accessing duplicate keys. KU Keyed sequence access path with no duplicate keys allowed (UNIQUE). EV Encoded vector with a 1-, 2-, or 4-byte vector.
338	152		CHAR(6)	Qdbfhrls	File version, release, and modification level. VxRyMz, where x is the version, y the release, and z the modification level.
344	158		CHAR(20)	Reserved_27	Reserved.
364	16C		BINARY(4)	Qdbpfof	Offset from the start of the FDT header, Qdb_Qdbfh, to the physical file specific attributes section, Qdb_Qdbfphys.
368	170		BINARY(4)	Qdblfof	Offset from the start of the FDT header, Qdb_Qdbfh, to the logical file specific attributes section, Qdb_Qdbflogl.
372	174		CHAR(6)	Qdbfssfp	Sort sequence table.
372	174		CHAR(1)	Qdbfnlsb	Flags.
372	174	0	BIT(3)	Qdbfsscs	Sort sequence table (SRTSEQ) indicators. B'000' No sort sequence table for the file; however, an alternate collating sequence table was specified. B'010' No sort sequence table is used for the file, and the hexadecimal value of the characters will be used to determine the sort sequence (*HEX). B'100' A sort sequence table was specified for the file.
372	174	3	BIT(5)	Reserved_103	Reserved.
373	175		CHAR(3)	Qdbflang	Language identifier (LANGID).
376	178		CHAR(2)	Qdbfcnty	Country or region identifier (CNTRYID).
378	17A		BINARY(4)	Qdbfjorn	Offset from the start of the FDT header, Qdb_Qdbfh, to the journal section, Qdb_Qdbfjoal.
382	17E		BINARY(4)	Qdbfevid	Initial number of distinct values an encoded vector access path was allowed at creation.
386	182		CHAR(14)	Reserved_28	Reserved.

Physical File Specific Attributes (Qdb_Qdbfphys)

You can locate the Qdb_Qdbfphys section with the offset Qdbpfof, in the FDT header section.

Trigger Description Area (Qdb_Qdbftrg)

You can locate the Qdb_Qdbftrg section with the offset Qdbfotrg in the Physical File Specific Attributes section, or with the offset Qdbflotrg in the Logical File Specific Attributes section. This section is repeated by the number of triggers, Qdbftrgn or Qdbfltrgn.

Constraint Definition Header (Qdb_Qdbf_Constraint)

You can locate the Qdb_Qdbf_Constraint section with the offset Qdbfofcs located in the physical file specific attributes section, Qdb_Qdbfphys.

Offset		Bit	Type	Field	Description
Dec	Hex
0	0		BINARY(4)	Qdbf_csto	Offset from Qdbf_Constraint to the next section for this constraint.
4	4		BINARY(4)	Qdbf_hlen	Constraint entry header length in bytes.
8	8		CHAR(1)	Qdbf_type	Constraint type (TYPE) F Referential constraint P Primary unique constraint U Unique constraint. C Check constraint.
9	9		CHAR(1)	Qdbf_chkpd	Check pending attribute. N The constraint is not in check pending. Y The constraint is in check pending.
10	A		CHAR(1)	Qdbf_state	Constraint state. D The constraint is defined. E The constraint is established.
11	B		CHAR(1)	Qdbf_abled	Constraint enablement. D The constraint is disabled. E The constraint is enabled.
12	C		CHAR(13)	Qdbf_add_ts	Constraint date. The date is in the internal standard format (ISF), CYYMMDDHHMMSS.
25	19		CHAR(10)	Qdbf_cst_lin	Constraint library name.
35	23		BINARY(4)	Qdbf_cst_lp2	Constraint name (delimited) length
39	27		CHAR(1)	Qdbf_cst_checked	Enable Constraint Type. U The constraint is enabled without checking. Blank The constraint is enabled with checking or is desabled.
40	28		CHAR(24)	Reserved_54	Reserved.
64	40		CHAR(258)	Qdbf_cst_name	Constraint name (CST).

Constraint Definition Entries

The number of constraint definition entries depends on the type of constraint.

• A referential constraint, type F, has three structures in this sequence:
  
  
  1. Qdbf_Keyn for parent file
  2. Qdbf_Keyn for dependent file
  3. Qdbf_Riafk_Afkd
• A unique constraint, type U, has one Qdbf_Keyn structure.
• A primary unique constraint, type P, has one Qdbf_Keyn structure.
• A check constraint, type C, has one Qdbf_Chk_Cst structure.

Constraint Keys (Qdb_Qdbf_Keyn)

The Qdb_Qdbf_Keyn section is located with the offset Qdbf_Hlen in the constraint definition header, Qdbf_Constraint. When the constraint is referential constraint, the offset to the next section is located with the offset Qdbf_Kslen in this structure.

Key Name Array (Qdb_Qdbf_Narray)

This array follows the constraint keys structure, Qdbf_Keyn. The number of constraint key name array entries is in field Qdbf_nokys in the constraint keys structure.

Referential Constraint Definition (Qdb_Qdbf_Riafk_Afkd)

You can locate this section with the offset Qdbf_kslen in the constraint keys structure, Qdbf_Keyn, that precedes this structure. This structure exists only if the constraint is a referential constraint.

Check Constraint (Qdb_Qdbf_Chk_Cst)

This section is located with the offset Qdbf_Hlen in the constraint definition header, Qdbf_Constraint. This structure exists only if the constraint is a check constraint.

Datalink Header (Qdb_Qdbfdtalnk)

The Qdb_Qdbfdtalnk section is the header for the datalink columns that have linked servers. There will be one header and one or more datalink column entries defined by the Qdb_Qdbfdlcole structure. You can locate this structure with the offset Qdbfodl in the Physical File Specific Attributes structure, Qdb_Qdbfphys.

Datalink Column Entry (Qdb_Qdbfdlcole)

The Qdb_Qdbfdlcole section repeats for the number of columns (Qdbfdlcoln) defined in structure Qdb_Qdbfdtalnk. You can locate the first column entry using offset Qdbfdlocole in structure Qdb_Qdbfdtalnk. Since Qdb_Qdbfdlcole is a varying length structure, use length Qdbfdlcelen to get to the next column entry.

Record ID Codes (Qdb_Qdbfdrtb)

The Qdb_Qdbfdrtb section describes the record ID codes for program described physical files. The record ID code information is an array with variable length entries. You can locate this section with the offset Qdbforid located in the physical file specific attributes section, Qdb_Qdbfphys.

Record ID Codes Array (Qdb_Qdbfdrae)

This array follows the record ID codes structure, (Qdb_Qdbfdrtb). The number of record ID code array entries is in Qdbfdrnum.

Logical File Specific Attributes (Qdb_Qdbflogl)

You can locate the Qdb_Qdbflogl section with the offset Qdbflfof located in the FDT header section, Qdb_Qdbfh.

Join Specifications (Qdb_Qdbfj)

The join specifications, Qdb_Qdbfj, are a linked list. There is an entry in the linked list for each join to-file. Each entry defines the join logical file's based on physical files and the fields in the from-file and the to-file used to join the based on physical file.

You can locate this section with the offset Qdbfoj located in the FDT header section, Qdb_Qdbfh.

Join Specification Array (Qdb_Qdbfjfld)

You can locate the Qdb_Qdbfjfld section with the offset Qdbfjsao located in the join header section, Qdb_Qdbfj. The number of join specification array entries may be up to one less than the number of data members, Qdbflbnum , located in the FDT header section, Qdb_Qdbfh.

Join Duplicate Sequence Specification Array (Qdb_Qdbfjdup)

You can locate the Qdb_Qdbfjdup section with the offset Qdbfjdao in the join section, Qdb_Qdbfj. The number of join specification array entries may be up to one less than the number of data members, Qdbflbnum, located in the FDT header section, Qdb_Qdbfh.

SQL Area (Qdb_Qdbfv)

The SQL area, Qdb_Qdbfv, contains the SQL select statement, or the SQL create index statement for new SQL indexes created for V6R1M0. For logical files, you can locate this section with the offset Qdbfovw located in the logical file specific attributes section, (Qdb_Qdbflogl). For SQL materialized query tables, you can locate this section with the offset Qdbfovw_mqt located in the physical file specific attributes section, (Qdb_Qdbfphys).

SQL Materialized Query Table Dependency Header (Qdb_Qdbfmqtd_Head)

The Qdb_Qdbfmqtd_Head section is located with the offset Qdbfmqtd_o in the SQL area, Qdb_Qdbfv. This structure exists only if the file is a SQL materialized query table.

SQL Materialized Query Table Dependency Entry (Qdb_Qdbfmqtd)

The Qdb_Qdbfmqtd section repeats in the dependency array for the number of depended-on files (Qdbfmqtd_#_deps) defined in structure Qdb_Qdbfmqtd_Head. The first dependency entry follows the dependency header Qdb_Qdbfmqtd_Head. Use length Qdbfmqtd_len to get to the next dependency entry.

Partitioned Table Header (Qdb_Qdbfsqpt_Head)

The Qdb_Qdbfsqpt_Head section is located with the offset Qdbfoff_sqpt. This structure exists only if the file is a partitioned table.

Partitioned Area (Qdb_Qdbfsqpt_Part)

The Qdb_Qdbfsqpt_Part section is located with the offset Qdbfsqpt_Part_Offset. This structure exists only if the file is a partitioned table.The repeating structure(Qdb_Qdbfsqpt_Part) can be located with the Qdb_Qdbfsqpt_Part_Len value.

Partition Range Key Area (Qdb_Qdbfsqpt_Range)

The Qdb_Qdbfsqpt_Range section is located with the offset Qdbfsqpt_Ran_Offset. This structure exists only if the file is a partitioned table that has range partitioning. Use Qdbfsqpt_Range_Len to get to the next entry.

Partition Header Hash Key Area (Qdb_Qdbfsqpt_Head_Hash)

The Qdb_Qdbfsqpt_Head_Hash is the header area for the hash keys. It is located with the offset Qdbfsqpt_Hk_Offset. This structure exists only if the file is a partitioned table that has hash partitioning.

Partition Hash Key Area (Qdb_Qdbfsqpt_Hash)

The Qdb_Qdbfsqpt_Hash section repeats for the number of partition hash keys,Qdbfsqpt_Head_Num_Keys. It follows Qdb_Qdbfsqpt_Head_Hash.

Alternative Collating Sequence Table (Qdb_Qdbfacs)

You can locate this section with the offset Qdbfocs in the FDT header section, Qdb_Qdbfh. This section is also referred to as the Sort Sequence Table. A sort sequence table can be either single-byte or UCS-2. If the UCS-2 table length, Qdbf_UCS2_Srtseq_Len, is non-zero, then it is a UCS-2 sort sequence table and the single-byte table, Qdbfacst, will be cleared.

Qdbf_UCS2
_Srtseq_Len

Qdbf_UCS2
_Srtseq

IDDU/SQL Data Dictionary Area (Qdb_Qdbfdic)

You can locate the Qdb_Qdbfdic section with offset Qdbfodic in the FDT header section, Qdb_Qdbfh.

SQL Long/Alias File Name Area (Qdb_Qdbflngn)

The SQL long/alias file name area contains the files alternate names that can be used to access the file when using the system's SQL interfaces. You can locate the Qdb_Qdbflngn section with the offset Qdbfolng in the IDDU/SQL data dictionary section.

File Scope Array (Qdb_Qdbfb)

A file scope array, Qdb_Qdbfb, is present for all database files. The number of data members, Qdbflbnum, contains the number of file scope array entries. Each entry contains a based on physical file name and, optionally, a record format name.

Externally described physical files have one entry that names the physical file record format. The entry's file name portion is not used.

Program described physical files have one entry for each data dictionary record format. The entry names the data dictionary record format. The entry's file name portion is not used.

Non-join logical files have one entry for each based on physical file. The entry names the based on physical file and describes the logical file record format to use with that file.

Join logical files have one entry for each based on physical file. The entry names the based on physical file. Only the first entry describes the logical file record format.

SQL view logical files have one entry for each based on physical file. The entry names the based on physical file that will be either an externally described physical file or another view logical file. Only the first entry describes the logical file record format.

You can locate this section with the offset Qdbfos in the FDT header section, Qdb_Qdbfh.

Select/Omit Specification Array (Qdb_Qdbfss)

The select/omit specification array ( Qdb_Qdbfss) entries describe the record format fields to which the select/omit statement refer.

Non-join logical files can have one select/omit specification array for each file scope array entry.

Join logical files can have only one select/omit specification array. The first scope array entry for the join logical file contains the offset to the select/omit specification array.

You can locate this section with the offset Qdbfsoof in the scope array entry section.

Select/Omit Parameters (Qdb_Qdbfsp)

The Qdb_Qdbfsp section is a linked list of parameter descriptions. It describes the parameter values for this particular select/omit statement. The parameters are either a compare value or another record format field.

You can locate this section with the offset Qdbfsoso in the select/omit array section, Qdb_Qdbfss.

Key Specification Array (Qdb_Qdbfk)

The key specification array (Qdb_Qdbfk) entries describe the record format fields used in defining the file access path.

Non-join logical files can have one key specification array for each file scope array entry.

Join logical files can have only one key specification array. The first scope array entry for the join logical file contains the offset to the file's key specification array.

You can locate this section with the offset (Qdbfksof) in the scope array entry section, Qdb_Qdbfb.

Distributed File Definition Section and Partition Key Array (Qdb_Qdbf_dis_pkeyarr)

The distributed file definition section and partition key array (Qdb_Qdbf_dis_pkeyarr) contains the node group name and library name for the distributed file and the record format fields used in defining the partition key for each scope entry.

You can locate this section with the offset Qdbfodis in the scope array entry section, Qdb_Qdbfb.

Journal Information (Qdb_Qdbfjoal)

The section Qdb_Qdbfjoal contains the journal information for the physical file. You can locate this section with offset Qdbfjorn in the FDT header section, Qdb_Qdbfh.

FILD0200 Format (Qdb_Qddfmt Structure)

FILD0200 provides the format used by the records of the specified file. This structure is also used by the QQQQRY API to get data from the named file. FILD0200 Format shows how this information is organized. When more than one entry can appear, the figure indicates this as in (6). Descriptions and offsets of the fields in this structure are in the tables immediately following FILD0200 Format.

The descriptions and offsets are available in the include source supplied on the system. You can see this source in source file H, member name QDBRTVFD, in the QSYSINC library.

FILD0200 Format

Format Definition Header (Qdb_Qddfmt)

The Qdb_Qddfmt section is always located at the beginning of the returned data area.

Field Header (Qdb_Qddffld)

This section is located immediately after the Qdb_Qddfmt header. The number of entries in this structure is defined by variable Qddffldnum in the Qdb_Qddfmt header. This structure is to be defined at variable Qddffldx in the Qdb_Qddfmt header.

Offset		Bit	Type	Field	Description
Dec	Hex
0	0		BINARY(4)	Qddfdefl	Length of field header structure. The length of each occurrence of the field header structure, including all subsections.
4	4		CHAR(30)	Qddffldi	Internal field name. The name of the physical format field. If this is a logical format, the name of the physical field on which the logical field is based.
34	22		CHAR(30)	Qddfflde	External field name. If this is a logical format, the logical format field name. If this is a physical format, the internal name is a duplicate of Qddfflde.
64	40		CHAR(2)	Qddfftyp	Data type. X'0000' BINARY X'0001' FLOAT X'0002' ZONED DECIMAL X'0003' PACKED DECIMAL X'0004' CHARACTER X'8004' VAR CHARACTER X'0005' GRAPHIC X'8005' VAR GRAPHIC X'0006' DBCS-CAPABLE X'8006' VAR DBCS-CAPABLE X'000B' DATE X'000C' TIME X'000D' TIMESTAMP X'000F' DECIMAL FLOATING POINT X'4004' BLOB/CLOB X'4005' DBCLOB X'4006' CLOB-OPEN X'8044' DATALINK-CHAR X'8046' DATALINK-OPEN X'FFFF' NULL
66	42		CHAR(1)	Qddffiob	Usage X'01' The field can be used for input only. X'02' Output only. X'03' Both input and output. X'04' Neither input nor output. X'FF' The usage is unknown.
67	43		BINARY(4)	Qddffobo	Output buffer offset. The offset of this field from the start of the output buffer.
71	47		BINARY(4)	Qddffibo	Input buffer offset. The offset of this field from the start of the input buffer.
75	4B		BINARY(2)	Qddffldb	Length. The length of the field. For character fields: the number of characters. For binary float fields: 4 for single, 8 for double. For decimal floating point fields: 8 for DECFLOAT(16), 16 for DECFLOAT(34). For variable length fields: the maximum the field can be plus 2. For date, time, or timestamp fields: the length of the formatted data. For graphic data fields: the number of bytes. For LOB fields: the number of bytes in the buffer.
77	4D		BINARY(2)	Qddffldd	Number of digits. The number of digits in the field. For numeric fields: the number of digits. For graphic data fields: the number of DBCS characters the field can contain.
79	4F		BINARY(2)	Qddffldp	Decimal positions. The number of position to the right of the decimal point.
81	51		CHAR(1)	Qddffkbs	Keyboard shift (RESHIFT) The keyboard shift attribute of the field. X Alphabetic only. A Alphameric shift. N Numeric shift. S Signed numeric. Y Numeric only. D Digits only. M Numeric only character. W Katakana. H Hexadecimal. I Inhibit keyboard entry. J DBCS only. E DBCS either. O DBCS open. B Binary character. X'00' No shift expected.
82	52		CHAR(1)	Qddffldst	Field status byte 1
82	52	0	BIT(1)	Qddffiat	Double-byte character set (DBCS) alternate type field. If on, indicates the alternate type for this field contains DBCS data.
82	52	1	BIT(1)	Qddffitx	Double-byte character set (DBCS) field text description. If on, indicates the text description contains DBCS data.
82	52	2	BIT(1)	Qddffich	Double-byte character set (DBCS) column headings. If on, indicates the column headings contains DBCS data.
82	52	3	BIT(1)	Qddffivc	Double-byte character set (DBCS) validity checking literals. If on, indicates the compare, range, or values literals contain DBCS data.
82	52	4	BIT(1)	Qddffrnd	Rounding. Rounding method for the field. If on, indicates round insignificant decimal digits. If off, indicates truncate insignificant decimal digits.
82	52	5	BIT(1)	Qddffcid	Character identifier flag. If on, indicates a character identifier was specified.
82	52	6	BIT(2)	Reserved_62	Reserved.
83	53		BINARY(2)	Qddfjref	Join reference (JREF) (logical files only). For fields whose names are specified in more than one physical file, this values identifies which physical file contains the field.
85	55		CHAR(1)	Qddffldst2	Field status byte 2.
85	55	0	BIT(1)	Qddffnul	Allow null value (ALWNULL). If on, indicates the null value is allowed for this field.
85	55	1	BIT(1)	Qddffdft	Column default value. If on, indicates the column does not have a default value.
85	55	2	BIT(1)	Qddffvar	If on, indicates the column is a variable field for a query format; Qddfvarx has meaning.
85	55	3	BIT(1)	Reserved_70	Reserved.
85	55	4	BIT(1)	Qddffvln	If on, indicates the column is a variable length field.
85	55	5	BIT(3)	Reserved_70a	Reserved.
86	56		CHAR(1)	Qddflgs2	Flags.
86	56	0	BIT(1)	Qddfcorr	Correlated field. If on, indicates this is a correlated field.
86	56	1	BIT(1)	Qddffrrn	File relative record number. If on, indicates this is a relative record number field.
86	56	2	BIT(5)	Reserved_71	Reserved.
86	56	7	BIT(1)	Qddffmep	Mapping errors possible. If on, indicates the field may return data mapping errors.
87	57		BINARY(2)	Qddfvarx	Variable field index. Index into the list of all variable field values for the query.
89	59		CHAR(2)	Reserved_72	Reserved.
91	5B		BINARY(2)	Qddflalc	Allocated length. The number of bytes allocated for the field in the fixed portion of the file. Or: Date/time/timestamp length. The number of bytes the based on field occupies.
93	5D		CHAR(1)	Qddfdttf	Date format (DATFMT) or time format (TIMFMT), depending on the use of the field. This field is not valid unless Qddfftyp is X'000B', X'000C', or X'000D' except for the following cases. DATFMT and TIMFMT are valid on '0002'X type logical file fields having based-on physical file fields that are '000B'X and '000C'X. DATFMT is valid on '0003'X and '0004'X type logical file fields having based-on physical file fields that are '000B'X. Some DATFMTs are valid only for the the '0002'X, '0003'X, and '0004'X fields having based-on physical file '000B'X fields and are identified (by pseudo date) below. X'FE' The format associated with the job. X'FF' The format associated with the QDT. X'01' The *USA format. X'03' The *ISO format. X'05' The *EUR format. X'07' The *JIS format (date only). X'09' The SAA® timestamp. X'17' The *MDY format (date only). X'18' The *DMY format (date only). X'19' The *YMD format (date only). X'1A' The *JUL format (date only). X'1B' The *HMS format (time only). X'25' The *CMDY format (pseudo date). X'26' The *CDMY format (pseudo date). X'27' The *CYMD format (pseudo date). X'28' The *MDYY format (pseudo date). X'29' The *DMYY format (pseudo date).
					X'2A' The *YYMD format (pseudo date). X'2B' The *YM format (pseudo date). X'2C' The *MY format (pseudo date). X'2D' The *YYM format (pseudo date). X'2E' The *MYY format (pseudo date). X'30' The *LONGJUL format (pseudo date).
94	5E		CHAR(1)	Qddfdtts	Date separator (DATSEP) or Time separator (TIMSEP) This field is not valid unless Qddfftyp is X'000B', X'000C', or X'000D'. X'00' The separator associated with the job. X'EE' The implied separator is used. '/' The slash is used. '-' The dash is used. '.' The period is used. ' ' The blank is used. ':' The colon is used.
95	5F		BINARY(2)	Qddfcsid	Common coded character set identifier (CCSID). 00000 The CCSID associated with the job is used. 65535 No data translation is done. nnnnn The CCSID.
97	61		BINARY(2)	Qddftsid	Text description common coded character set identifier. 00000 The CCSID associated with the job is used. 65535 No data translation is done. nnnnn The CCSID.
99	63		BINARY(2)	Qddfhsid	Column heading common coded character set identifier. 00000 The CCSID associated with the job is used. 65535 No data translation is done. nnnnn The CCSID.
101	65		BINARY(2)	Qddflsid	Long comment common coded character set identifier. 00000 The CCSID associated with the job is used. 65535 No data translation is done. nnnnn The CCSID.
103	67		CHAR(1)	Qddfldur	Labeled duration. The type of labeled duration this field defines. X'00' The field not a labeled duration. X'0D' Year/years. X'0E' Month/months. X'0F' Day/days. X'10' Hour/hours. X'11' Minute/minutes. X'12' Second/seconds. X'13' Microsecond/microseconds.
104	68		CHAR(1)	Qddfflgs	Flags. These flags indicate the user-specified value for the field at the time the format was created. These flags only apply to date, time, and timestamp fields. If the format was ever shared, these flags may not be applicable to the file for which the API was called.
104	68	0	BIT(1)	Qdddatfmt_dft	If on, indicates DATFMT was defaulted.
104	68	1	BIT(1)	Qdddatfmt_job	If on, indicates DATFMT(*JOB) was specified.
104	68	2	BIT(1)	Qdddatsep_dft	If on, indicates DATSEP was defaulted.
104	68	3	BIT(1)	Qdddatsep_job	If on, indicates DATSEP(*JOB) was specified.
104	68	4	BIT(1)	Qddtimfmt_dft	If on, indicates TIMFMT was defaulted.
104	68	5	BIT(1)	Qddtimsep_dft	If on, indicates TIMSEP was defaulted.
104	68	6	BIT(1)	Qddtimsep_job	If on, indicates TIMSEP(*JOB) was specified.
104	68	7	BIT(1)	QddSAAfmt	SAA format was specified.
105	69		BINARY(2)	Qddfwsid	Edit word common coded character set identifier. 00000 The CCSID associated with the job is used. 65535 No data translation is done. nnnnn The CCSID.
107	6B		CHAR(1)	Reserved_61	Reserved.
108	6C		CHAR(1)	Reserved_62	Reserved.
109	6D		BIN(2)	Reserved_63	Reserved.
111	6F		CHAR(1)	Qddflagco	Flags.
111	6F	0	BIT(3)	Reserved_64	Reserved.
111	6F	3	BIT(1)	Qddffucs	If on, indicates the column is a UCS-2 field.
111	6F	4	BIT(1)	Qddfudt	If on, indicates the column is a user-defined type field.
111	6F	5	BIT(1)	Qddf_Identity_ Col	If on, indicates the column is an identity column.
111	6F	6	BIT(1)	Qddf_Rowid_ Col	If on, indicates the column is a row ID column.
111	6F	7	BIT(1)	Qddfutf	If on, indicates the field is a UTF-8 or UTF-16 field.
112	70		CHAR(5)	Qdducs2co	UCS-2 Field Information
112	70		BINARY(2)	Qddfdspl	Used with a UCS-2 field when the CCSID keyword modifies the display length.
114	72	0	BIT(1)	Qddfucsp	When referenced by a printer file, indicates whether UCS-2 characters are to be converted before printing. If on, do not convert.
114	72	1	BIT(1)	Qddfucsm	Minimum-display-length-flag, when referenced by a display file. If on, Qddfdspl contains the number of display positions allowed equal to the field length defined in the DDS.
114	72	2	BIT(1)	Qddfucsl	Length-of-display-field_flag, when referenced by a display file. If on, the DDS for the field provided the allowed number of display positions. This number is in Qddfdspl.
114	72	3	BIT(1)	Qddf_Row_Change_Timestamp	If on, indicates the column is a Row Change Timestamp column.
114	72	4	BIT(1)	Qddf_Hidden_Column	If on, indicates the column is a Hidden Column.
114	72	5	BIT(1)	Qddf_Secure_Data	If on, indicates the column contains data of a secure nature (for example, a credit card number).
114	72	6	BIT(1)	Qddf_XML_Column	If on, indicates this LOB column is an XML Column.
114	72	7	BIT(1)	Reserved_130	Reserved.
115	73		CHAR(2)	Qddfencode	Encoding scheme for field's CCSID. '0000'X means no encoding scheme.
117	75		CHAR(1)	Qddf_Row_Change_Tmstmp_Generat	Row Change Timestamp GENERATE indicator. 1 = GENERATE BY DEFAULT. 0 = GENERATE ALWAYS.
118	76		CHAR(10)	Qddf_Fld_Proc_Program	Field Procedure program name.
128	80		CHAR(10)	Qddf_Fld_Proc_Library	Field Procedure library name.
138	8A		CHAR(42)	Reserved_74	Reserved.
180	B4		BINARY(4)	Qddfcplx	Offset from the start of the field header to the field information if the field was a user-defined type, datalink, or large object. See structure Qdb_Qddfcpli.
184	B8		BINARY(4)	Qddfbmaxl	Maximum length of the large object field.
188	BC		BINARY(2)	Qddfbpadl	Pad length of the large object field.
190	BE		BINARY(4)	Qddfdicd	Offset from the start of the field header to the IDDU/SQL dictionary field information, Qddfdicf.
194	C2		BINARY(4)	Qddfdftd	Offset from the start of the field header to the default value description, Qddfdft.
198	C6		BINARY(4)	Qddfderd	Offset from the start of the field header to the derived field description (or to the concatenated field description if its file is externally described), Qddfderv.
202	CA		CHAR(6)	Reserved_75	Reserved.
208	D0		BINARY(4)	Qddftxtd	Offset from the start of the field header to the field text description, Qddfftxt.
212	D4		CHAR(2)	Reserved_102	Reserved.
214	D6		BINARY(4)	Qddfrefd	Offset from the start of the field header to the field reference information, Qddfrefi.
218	DA		BINARY(2)	Qddfedtl	Length of the edit code/edit word for the field.
220	DC		BINARY(4)	Qddfedtd	Offset from the start of the field header to the edit code/edit word information, Qddfedcw.
224	E0		BINARY(2)	Reserved_76	Reserved.
226	E2		BINARY(4)	Qddfchd	Offset from the start of the field header to the column heading information, Qddfcolh.
230	E6		BINARY(2)	Qddfvckl	Length of validity checking data present for the field.
232	E8		BINARY(4)	Qddfvckd	Offset from the start of the field header to the validity checking data, Qddfvchk.
236	EC		BINARY(4)	Qddfxals	Offset from the start of the field header to the alias name entry.
240	F0		BINARY(4)	Qddffpnd	Offset from the start of the field header to the field prompted numeric editing information, Qddfdfne.
244	F4		CHAR(8)	Reserved_77	Reserved.
252	FC		CHAR(*)	Qddfvpx	Start of the variable portion of the field description.

Reference Information (Qdb_Qddfrefi)

You can locate the Qdb_Qddfrefi section with the offset Qddfrefd in the field header section, Qdb_Qddffld.

Field Prompted Numeric Editing Information (Qdb_Qddfdfne)

You can locate the Qdb_Qddfdfne section with the offset Qddffpnd in the field header section, Qdb_Qddffld.

Edit Code/Edit Word Information (Qdb_Qddfedcw)

You can locate the Qdb_Qddfedcw section with the offset Qddfedtd in the field header section, Qdb_Qddffld.

Validity Checking Information (Qdb_Qddfvchk)

You can locate the Qdb_Qddfvchk section with the offset Qddfvckd in the field header section, Qdb_Qddffld.

Validity Checking Entry (Qdb_Qddfvcst)

The first validity checking entry starts at Qddfvcen in the validity checking information section, Qdb_Qddfvchk.

Validity Checking Parameter (Qdb_Qddfvcpr)

The first validity checking parameter starts at Qddfvcpm in the validity checking entry section, Qdb_Qddfvcst.

Complex Object Field Type Information (Qdb_Qddfcpli)

You can locate the Qdb_Qddfcpli section with the offset Qddfcplx in the field header section, Qdb_Qddffld.

Field Text (Qdb_Qddfftxt)

You can locate the Qdb_Qddfftxt section with the offset Qddftxtd in the field header section, Qdb_Qddffld.

Alias Name Structure (Qdb_Qddfalis)

You can locate this section with the offset Qddfxals located in the field header section, Qdb_Qddffld.

Default Value Description Information (Qdb_Qddfdft)

You can locate the Qdb_Qddfdft section with the offset Qddfdftd in the field header section, Qdb_Qddffld.

Identity Column Information (Qdb_Qddfidcl)

You can locate the Qdb_Qddfidcl section with the offset Qddf_Identity_Off in the field header section, Qdb_Qddffld.

Derived Field Description Information

The derived field structure is a stack of operators and operands in postfix notation. Postfix notation is a method of forming mathematical expressions in which each operator is preceded by its operands and indicates the operation to be performed on the operands or the intermediate results that precede it. For example:

A + B
would be:
A B +

Numeric operands and character operands cannot be mixed in one derived field description. If numeric operands are specified, the resulting field attributes must be numeric. If character operands are specified, the resulting field attributes must be character or DBCS. Character and DBCS only fields cannot be mixed in one derived field description.

Substringing DBCS fields is allowed, although the data is treated as character data, that is, there is no true double-byte substring support. This applies to query formats only.

Derived Field Header (Qdb_Qddfderv)

You can locate this section, Qdb_Qddfderv, with the offset Qddfderd in the field header section, Qdb_Qddffld.

Derived Field Entry (Qdb_Qddfdvst)

Field Operand Entry (Qdb_Qddfdvof)

Constant Operand Entry (Qdb_Qddfdvoc)