Report Generator

Information Exchange Group, Inc.

Generating Unload/LOAD reports is a billable service. Generating a single report for an assessment is permitted. Generating all reports is subject to being invoiced by IEG.

IEG's Report Generation process generates LINC report programs, specifically for the user's application, to unload data from the existing repositories -- one report per structure -- in a platform independent format. Existing file transfer utilities can safely move this data format between platforms. Once resident on the new platform, the same reports load the data into the LINC application database.

All I-O or Output structures are list in either the left or right list box. The right list box contains reports, which are to be generated. In the left list box are reports that have been generated or excluded. Individual report names can be selected and moved between the list boxes as desired. Pressing the PROCESS button will create new Load/Unload reports for all names in the right list box.

Before generating the new reports two check boxes should be marked. One is Re-examine the Model. If a new version of your model is available and you wish to re-load that version to get updated file characteristics , then this box should have a check mark. The other is Create New Report Model. Multiple requests to generate reports can be made. If a new report model is desired, this box should have a check mark. If it does not have a check mark then any reports generated will be appended to the current report model.

Generated Case Models:

Specific features of the LINC reports produced by IEG's Report Generation process are:

· Parameter file control
The user is prompted with a request for desired functions in the absence of a parameter file. The presence of the parameter file allows the migration routine to run in batch mode without operator intervention.

· Option to "LOAD" or "UNLOAD"
The user is prompted with a request for the desired function.

· Common data record layout
The extracted data is in a generic character format that allows file transfer utilities to move data between architectures without losing numeric signs and decimal points.

· Ordinate validation
Whenever an ordinate is a data item in a related record, generated logic performs a validation against the parent record. It is important that data is loaded in an order establishing static information first, followed by dynamic transaction information.

· Date field validation
Fields defined as edit date are verified using the LINC DATE.CONVERT construct to ensure dates are valid.

· Required Field validation
Data items defined as required fields are tested for zeros and spaces.

· Numeric field validation
Data items defined as numeric are tested for correct numeric values.

· Area for user modifications
Each report contains a section for user logic. It is often helpful to the developer to select specific business information. User logic can be added to the UNLOAD or LOAD procedures to narrow the data to selected department numbers, product numbers, or customers. Using LDA to modify the report, the developer can easily and quickly add this logic giving immediate results.

· Documentation for each report
Each report contains documentation explaining the features and operations of the report including the names of the flat data files and error logs from validation logic.

Report Parameter File:

The options when running this report are 'LOAD' or 'UNLOAD'. When LOADing, you may also choose to skip the edits below. If a file called "<system>/IMPORT/ACCEPT" is visible, it will be used to set the options; LOAD or UNLOAD must be in the first record, EDIT or NOEDIT in the second. If this parameter file does not exist, the parameters will be entered through ACCEPTs. You will also be prompted with a request to store this information so other reports will be able to read this parameter file.

Report Generator Generated Models:

The case model containing the Load/Unload reports is called: <model>R.MDL and is found under the WORK directory.

A second model is present under the WORK directory called: <model>X.MDL. It contains a Global Logic routine for standardizing the name and directories of external files. This Global Logic is used by each of the Load/Unload reports generated by this process. The reason this is a separate model is for the convenience of loading. This <model>X.MDL model should be loaded once. It can be user modified and used where you wish to standardize the names and directories of the external files.

Both case models are partial case model files.

ã Copyrighted 1995-2009 Information Exchange Group, Inc.