The following processes occur when you build an application that is configured for OLTP:
Each of your OLTP View class definitions is compared with the external definitions, and if different, the external definition is loaded and appropriate reedit flags are set.
If your application is to be an OLTP server, new data files are created in a format suitable to be loaded into the host OLTP software. These files contain the following:
View descriptions, including all your Direction Input and Direction Input-Output Ispecs that are either OLTP server-capable or OLTP reply-capable.
Service Definition, listing all unique Service names. There can be one Service name for the application, one for each subsystem (on MCP based hosts only), and one for each Ispec (although several Ispecs can have the same Service name.)
The Service definition is created and loaded during the generation process.
If your application is not an OLTP server, the View file (or files) are not produced. You must provide the required Views from any OLTP Services to be used by your application.
The OLTP configuration information, comprising both the View files and the Service definition files, can be loaded automatically to the runtime host OLTP software. This function is controlled by the Load OLTP Configuration Data Segment configuration property under the OLTP category for the relevant Configuration. Refer to Application-Level Options for more information.