AcuBench File Types

A number of different file types are created and used by AcuBench . Some of these files are COBOL COPY files, produced by AcuBench's code generation facility, as discussed in the previous section. Others, however, are non-COBOL files used to define AcuBench workspaces and projects, store workspace state information, determine basic workspace settings, define template information, transfer compiler and runtime settings between projects, generate programs and data handling code, and so on.

Especially when you are using a version (source) control system, as discussed in Version Control, it can be vital to know what each file contains and how it is used by AcuBench. Because this information is particularly useful in a version control context, the reference includes two tables: one listing files generally tracked by version control, and one listing files that do not need to be tracked (either because the information they contain is relevant only to a single user, or because the files are completely recreated on generation from another file). Note that projects developed in the workbench may contain additional file types that are not AcuBench-specific (such as MIcro Focus .def or .acu files, user-defined COPY files, and resource files).

Commonly tracked files are:

Extension Description
.pjt    The workspace project file includes information about the projects within a workspace and the location of programs within each project.
.pjf The individual project file contains the location of all programs within a single project. By default, project information is stored in and read from the workspace project file (.pjt).
.psf The program structure file contains the information AcuBench needs to generate a program.
.cbl Default extension for COBOL source code. Note that source generated by AcuBench is recreated from the .psf file when you generate.
.dlt Data layout files contain the definitions that AcuBench uses to create FD, SL, and SD COPY files, as well as user-defined file handling code.
.ini AcuBench .ini files contain information about default program and control properties and code templates, as well as information about the overall appearance of the workspace and its editors.
.pof Project option files contain project settings, including compiler and run-time flags, AcuBench environment settings, and library options.
.stf Screen template files can be used to create a consistent look and feel for a user interface.
.prf Program option files store the default properties assigned to new AcuBench programs, including key status values and code generation options (shown in the Program Properties interface).
.wtf Report template files can be used to create a consistent look and feel for reports across an application or set of programs.

Files that are not usually tracked:

Extension Description
.wif The workspace information file contains the current state of the AcuBench workspace, including such things as which windows are open and which breakpoints are set.
.evt Event paragraph COPY file, generated from the .psf file and accessed through the Event Editor.
.lks Linkage section COPY file, generated from the .psf file and accessed through the Linkage Editor.
.mnu    Menu COPY file, generated from the .psf file and accessed through the Menu Designer dialog box in the Screen Designer.
.prd Procedure Division COPY file, generated from the .psf file. The code that is generated into this file comes from a number of the AcuBench editors and designers, including the Screen Designer and File Designer.
.rpt Report COPY file, generated from the .psf file and accessed through the Report Composer
.scr Screen Section COPY file, generated from the .psf file and accessed through the Screen Designer.
.wrk Working-Storage COPY file, generated from the .psf file and accessed through the Working-Storage Designer.
.fd File description COPY file, generated from the .dlt file and accessed through the File Designer.
.sl SELECT statement COPY file, generated from the .dlt file and accessed through the File Designer.
.sd Sort COPY file, generated from the .dlt and accessed through the File Designer.