During generation and installation, the Construction Client creates directories subordinate to the directories you named in the Construction Paths window. (The path directories you entered included source path, install control path, and remote install path for source and RI triggers.) This allows proper identification of the source code by operating system and source code language. The user ID is the name used to log on to the Construction Client.
When load modules containing non-default dialects are selected for generation, a specific directory subordinate to the language subdirectory is created for each dialect source code. The default dialect source code is stored in the language subdirectory.
These path definitions appear in the table that follows:
If you are using MFS devices, the following separate path entry exists:
Various files listed in the following table are created during generation and installation:
|
Path |
File Name |
Description |
|---|---|---|
|
Source |
*.c *.cbl |
Generated COBOL or C source code without embedded SQL. The extension indicates the language used to generate the source code. The file names can be:
|
|
MFS Source |
*.cbl |
IMS-specific source for MID, MOD, and FMT members. This file is only present if you generate the screen. |
|
Source |
*.sqb |
Generated COBOL source code with embedded SQL. |
|
Source |
*.sqc |
Generated C source code with embedded SQL. |
|
Source |
*.err |
Messages resulting from a failed generation. |
|
Source |
*.gml |
General Markup Language source file used with online help created for GUI applications. |
|
Source |
*.h |
Header file created for GUI applications. |
|
Source |
*.java |
Java source file |
|
Source |
*.html |
Hypertext markup language file |
|
Source |
*.css |
Cascade style sheet file |
|
Source |
*.jsp |
Java Server Page |
|
Source |
*.js |
Java Script |
|
Source |
*.rme |
Read Me file |
|
Source |
*.lst |
List file |
|
Source |
*.xml |
Extend Markup Language file |
|
Installation Control |
*.icm |
Install control information. The install control file is a set of instructions on how to install all procedure steps, screens, and action blocks for the load module. The install control file is in Standard Generalized Markup Language (SGML) format. |
|
Remote Installation |
*.rc |
Resource control file created for GUI applications. |
|
Remote Installation |
*.rmt |
A remote file which contains a concatenation of the .icm and source files. A separate .rmt file exists for each load module. The RI triggers are placed in a file called cascade.rmt. |
|
%%% |
.asp |
|
|
|
.bas |
|
|
|
.cpp |
|
|
|
.def |
|
|
|
.idl |
|
|
|
Rgs |
|
If you generate a complete application, the result is one remote file for the RI triggers, named cascade.rmt, and one remote file for each load module. A complete application also has a database remote file, which is created separately.
Note: For more information, see the chapter “Generating DDL.”
The files in the following table are temporary and may or may not be present after generation:
|
Path |
File Name |
Description |
|---|---|---|
|
Source |
*.ctl |
Information used by the Construction Client when creating a remote file. |
|
|
genstat.ctl |
Generation status log file that contains messages about the last action initiated. |
|
remote install path + user ID |
rfg.txt rfgcdr.txt |
Status messages issued during the generation of remote files. |
|
Copyright © 2013 CA.
All rights reserved.
|
|