Examples of file names for your built application are shown in the following table. Some of these files are created optionally. Descriptions of the variable values used are given following this table.
File Type | File Name | Resident Pack |
|---|---|---|
Database data/Files | database/comp/DATA | comp |
database/event ispec/DATA | event | |
database/ ispec/ profile | profile | |
database/AUDIT nnnn | audit | |
database/event ispec/ profile | profile | |
database/comp comp/DATA | comp | |
Database Description | DESCRIPTION/database | dict |
Database DMSUPPORT | DMSUPPORT/database | object |
Database RECONSTRUCT | RECONSTRUCT/database | object |
Database control | database/CONTROL | dict |
Generated System control file | system/LINCCNTL | dict |
Offline Input format file | system/LINCOFF | dict |
GLI format files | system/LINCGLI | dict |
system/LINCGLIS | dict | |
Forms files | system/LINCFORM | dict |
system/LINCFORM/LoadED | dict | |
COMS Configuration file | system/COMS/CONFIG/= | dict |
COMS TTRAIL file | COMS/TTRAIL/coms-db/nnnn | log |
DASDL source file | system/SOURCE/DMS | dict |
Database files | database/ispec/DATA | |
database/ispec/profile | ||
database/ispecispec/DATA | MyMemoData | |
database/ispec/DATA/nnnn | newplateau | |
database/CONTROL | ||
Report names | system/report | object |
system/WORK/report Resident pack when generated from Builder is dictionary pack. | object | |
system/OLDREPORT/report | object | |
system/WORK/report/SAVED Resident pack when generated from Builder is dictionary pack. | object | |
system/WORK/ASERIES/report/LIST Resident pack when generated from Builder is dictionary pack. | object | |
system/WORK/report/BUILD_DATA | dict | |
system/WORK/report/STUB Resident pack when generated from Builder is dictionary pack. | object | |
system/GEN_CODE/report/STUB | object | |
system/GEN_CODE/report | object | |
System | system/GEN_SOURCE/ispec | dict |
system/GEN_SOURCE/ispec/STUB | dict | |
system/SOURCE_FILE/ispec | dict | |
system/SOURCE_FILE/ispec/STUB | dict | |
system/GEN_CODE/ispec | object | |
system/GEN_CODE/ispec/STUB | object | |
system/CODE_FILE/ispec | object | |
system/CODE_FILE/ispec/STUB | object | |
Global logics – COBOL | system/GEN_SOURCE/glg | object |
system/SOURCE_FILE/glg | object | |
system/GEN_CODE/glg | object | |
system/CODE_FILE/glg | object | |
Global logic stubs | system/GEN_SOURCE/GLG_LIB/STUBn | |
system/SOURCE_FILE/GLG_LIB/STUBn | ||
system/GEN_CODE/GLG_LIB/STUBn | ||
system/CODE_FILE/GLG_LIB/STUBn | ||
User library stubs | system/GEN_SOURCE/USR_LIB/STUBn | |
system/SOURCE_FILE/USR_LIB/STUBn | ||
system/GEN_CODE/USR_LIB/STUBn | ||
system/CODE_FILE/USR_LIB/STUBn | ||
Bound code | system/GEN_CODE/nnn | |
system/CODE_FILE/nnn | ||
Segment attribute programs | system/GEN_SOURCE/GSD/PROGRAM | |
system/GEN_CODE/GSD/PROGRAM | ||
system/SOURCE_FILE/GSD/PROGRAM | ||
system/CODE_FILE/GSD/PROGRAM | ||
system/GEN_SOURCE/GSD/PROGRAM/STUB | ||
system/GEN_CODE/GSD/PROGRAM/STUB | ||
system/SOURCE_FILE/GSD/PROGRAM/STUB | ||
system/CODE_FILE/GSD/PROGRAM/STUB | ||
system/GEN_SOURCE/GSD/INCLUDES | ||
system/GEN_CODE/GSD/INCLUDES | ||
Build files | system/SOURCE_FILE/BUILD/MEMDB | |
system/SOURCE_FILE/BUILD/BIND_DECK | ||
system/SOURCE_FILE/BUILD/KNOWN_GLGS | ||
system/SOURCE_FILE/BUILD/CARD_FILE/ C85nnn | ||
system/SOURCE_FILE/BUILD/CARD_FILE/ALGnnn | ||
system/GEN_SOURCE/BUILD/MEMDB | ||
system/GEN_SOURCE/BUILD/BIND_DECK | ||
system/GEN_SOURCE/BUILD/KNOWN_GLGS | ||
system/GEN_SOURCE/BUILD/CARD_FILEnnn | ||
system/COMS_LINC_TP | ||
system/ENVIRONMENT | ||
system/DBINTERFACE | ||
Log information | system/LINCLOG/nnn | log |
system/OLD/LINCLOG/nnn | log | |
system/LOGBACKUP | log | |
Unique file (created at runtime) | system/UNIQUE/SAVE | dict and audit |
Note: To assist in the recovery of a failed reorganization, the old Report object code file is saved as system/OLDREPORT/report. It is your responsibility to delete any copies of these old object code files that you do not require. These files are not automatically removed after successful generates, as you might want to use them for your own backup or recovery procedures.
The variables used for file names and packs are explained in the following table.
Parameter | Description |
|---|---|
database | Database name |
coms-db | Database name as declared to COMS |
system | Your generated System name |
file | Name of the particular file or program created during the generate |
ispec | Name of the particular Ispec created during the generate |
comp | Name of the particular Component created during the generate |
profile | Name of the particular Profile created during the generate |
report | Name of the particular Report created during the generate |
nnn | A three-digit number from 001 through 998 |
nnnn | A four-digit number from 0001 through 9999. |
audit | Audit pack name, as entered on the Pack Allocation Business Segment Options for ClearPath MCP page. (If blank, Log pack is used). |
dbpack | Pack name for database structures, if specified on the Pack Allocation Business Segment Options for ClearPath MCP page. (If blank, Default or Dictionary pack name is used.) |
comp | Pack name for Component record storage, as entered on each Component Environment Component Options for ClearPath MCP page. (If blank, Database pack is used.) |
event | Pack name for Event record storage, as entered on the Pack Allocation Business Segment Options for ClearPath MCP page. (If blank, Database pack is used.) |
dict | Dictionary pack name, as entered on the Pack Allocation Business Segment Options for ClearPath MCP page. (If blank, Default pack is used.) |
object | Object pack name, as entered on the Pack Allocation Business Segment Options for ClearPath MCP page. (If blank, Dictionary pack is used.) |
log | Pack name for storage of the optional log for your System. (If blank, Default pack is used.) |