Search

User Guide

User Guide

10.5 HotFix 2
- 10.5 HotFix 1
- 10.5
- 10.2 HotFix 1
- 10.2
- 10.1
- 10.0 HotFix 1
- 10.0

Back Next

Logical File Definition

Logical File Definition

This begins with the

Logical-File-Definition

keyword. The fields are as follows:

Field	Description
NAME=	A character string that identifies the Logical-File. A Job object refers to a logical-file with its FILE= parameter. This is a mandatory parameter.
COMMENT=	A character string for documentation purposes only.
PHYSICAL-FILE=	A character string that specifies the file name containing the input data. When reading input from a flat file, this will specify the full filename including the path. When reading input from User Source Tables it specifies the name of the IDT defined in the CREATE_IDT clause of the User Source Table section. The name should be enclosed in double-quotes. This is a mandatory parameter. DCE does not support spaces in file or PATH names.
VIEW=View	The name of the Database View Definition to be used when reading the flat input file. It must not be specified if data will be read from User Source Tables. The View is used to translate the contents of the input file into the layout to be stored in the IDT (specified by the KEY-INDEX= parameter of the IDX-Definition ).
[INPUT-]FORMAT={SQL\|Text\|Binary\|Delimited}	Describes the format of the input file. When reading from a User Source Table, specify a format of SQL . Otherwise, when reading from a flat-file, the following options may be used: Text files contain records terminated by a newline. Binary files do not contain line terminators. Records must be fixed in length and match the size of the input View. Delimited files contain variable length records and fields which are delimited. By default, records are separated by a newline, fields are separated by a comma (,) and the field delimiter is a double-quote ("). However, you may change this behaviour by defining FORMAT=Delimited, Record-Separator(<char>), Field-Separator(<char>), Field-Delimiter(<char>) All three values are always used when the Delimited format is processed. There is no way of specifying that a particular delimiter should not be used. However, you may specify a value that does not appear in your data such as a non-ASCII value. For example, if a field delimiter is not used, the following could be specified: Field-Delimiter(Numeric(255))
Record-Separator=(<char>)Field-Separator=(<char>)	These parameters are usually specified as sub-fields on the FORMAT definition. However, for convenience, they may be defined as separate fields. For a delimited file using the default delimiters, there is no need to specify any of the delimiters in either the Project ( *.sdf ) file or in the Relate dialog. The delimiter definition should only be used when re-defining the default delimiters.
AUTO-ID-NAME=	This parameter is used when DCE has been requested to generate a Record Source ID field by defining the AUTO-ID clustering option (see the OPTIONS= section for description of this option). The generated ID is composed of a text string concatenated to a base 36 sequence number. The value for the text string portion is specified by using the AUTO-ID-NAME= parameter. It is limited to 32 bytes. The sequence number is supplied by DCE. The resulting ID field is stored on the IDT in the field defined by the AUTO-ID-FIELD parameter. This field must be defined in the Files section. We recommend defining an ID field with attributes F,10 . This leaves ample room for an Auto-Id-Name and several characters for the sequence number. Since the latter is a base 36 number, it allows for 1.6 million records in 4 characters, 60 million using 5 characters, or up to 3.6 Gig with a 6 character sequence number. The length attribute of the ID field is not limited to 10 bytes. It may be increased when you have a large number of records and/or a long Auto-Id-Name prefix. Refer to the IDX Definition / AUTO-ID-FIELD= section.

Watch

Comments

0 COMMENTS

We’d like to hear from you! Log in to comment.