Additional information pertaining to Clocking may be found in the Clocking page.
The LTCE will look for an IDIF interface code “LTCE” for the file structure.
The extract directory is defined using the EXTRCT DATA FLDR preference. The load directory is defined using the LOAD DATA FLDR preference. The ATTACHMENTS FLDR must be specified so the load functions know where to write the report exceptions log to.
If the full path is not specified here, then the path used by the HL Application Directory will apply. The user who is running the LTCE must have Read/Write/Create access to this directory on the server.
There are 2 tiers of exceptions that can be generated during the load process. The first tier involves extracting and building data from the source file and the second involves processing the extracted data. However, there will only be ONE exception for each failed load. Basically, if the record fails to build data correctly, the program will not bother loading it so you will never see 2 exceptions for a single failed record load.
Exceptions generated while extracting and building data from the source file will indicate that the exception occurred while "reading data from file". Exceptions generated while processing the extracted data will indicate that the exception occurred while "loading data into the DB".
When a Null Pointer Exception (NPE) occurs during the load process, the entire stack trace to the NPE is captured and displayed as part of the exception message in the load report.
The report text file will be located in the directory which was specified in the IMST preference LOAD DATA FLDR.
Report Parameters | |
---|---|
File Name | This field holds the name of the file that has been placed on the server in the directory specified in the IMST record LOAD DATA FLDR. Mandatory |
Delimiter | This file indicates the delimiter in the file if it is not a Fixed Format. |
Directory Path | This field indicates the location of the source file on the server. |
Interface Code | The Interface Code 'LTCE' that was created in step 1 must be specified. |
Exception Level | Lexicon value of 0 to 9. Allows you to specify the level of trace they wish to see in the report. |
Screen captures are meant to be indicative of the concept being presented and may not reflect the current screen design.
If you have any comments or questions please email the Wiki Editor
All content © High Line Corporation