CIM Interface
This chapter describes how to use database utilities to manage the movement and storage of data in a database.
Introduction to CIMExplains how CIM is used.
Using the CIM InterfaceExplains the CIM data load and format, and describes the input file formatting rules, input data types, and data for the input file. Gives a CIM data input file example, and discusses creating a CIM input file and error handling.
Deleting Records through CIMExplains how to create input files to delete records and gives an example of CIM delete.
Running Multiple CIM SessionsExplains how to run multiple sessions.
Killing CIM SessionsExplains the best way to stop a CIM session.
Introduction to CIM
Transferring data can save disk space, increase disk access speeds by compacting fragmented data, and integrate legacy or otherwise noncompatible data with QAD data. There are three basic ways to transfer data into and out of your QAD database:
• Dump or load data files.
• Archive and delete or reload data files.
• CIM load data files.
The first two options are discussed in . This chapter discusses CIM data load, which lets you load data into your QAD database from any source, as long as the data is formatted to match the QAD database schema. See
here.
CIM is typically used to add or modify records in a database. In certain cases, it can also be used to delete records. Only some functions support this feature. See
Deleting Records through CIM.
Unlike direct data loads, CIM checks load data for errors and saves unloaded records in an error file for correction and reloading. CIM loads can be run in either batch or continuous mode.
Note: CIM must be executed against character-based programs; it is not supported in the QAD .NET UI. Additionally, component-based functions in the .NET UI offer different integration approaches, such as Excel integration, along with the XML and Event daemons.