Identity Resolution 
			
			- Identity Resolution 10.2
- All Products
 
           
      	
            
	
      | Field  | Description  | 
|---|---|
| NAME=  | This is 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=  | This is a text field that is used to describe the Logical File’s purpose.  | 
| 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_IDTor DEFINE_SOURCEclause of the User-Source-Table section. The name should be enclosed in double-quotes. This is a mandatory parameter. See the  Reading Flat File Input from a Named Pipe section for information on reading file input from a Named Pipe. | 
| FORMAT={SQL|Text|Binary|XML|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:  Textfiles contain records terminated by a newline. Binaryfiles do not contain line terminators. Records must be fixed in length and match the size (and layout) of the input View. XMLfiles contain XML messages. This format is used when loading a flat-file created by the Siebel Connector. Delimitedfiles 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 ("). You may change the defaults by defining 
 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:  
 These parameters are usually specified as sub-fields on the  FORMATdefinition. However, for convenience, they may be defined as separate fields. | 
| 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  IDT-NAME=parameter of the IDX-Definition). | 
| XSLT=  | In the case of an XML format input file, an XSLT stylesheet may be specified. The stylesheet will be used to transform an XML format input file into one that matches the IDT.  | 
| AUTO-ID-NAME=  | This parameter is used when IIR has been requested to generate a  Record Source IDfield (see the AUTO-ID-FIELD=and Auto-Idparameters). 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 generated by IIR. The resulting ID field is stored on the IDT in the field defined by the AUTO-ID-FIELDparameter. 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-Nameand 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-Nameprefix. |