This tab is available for Dialog, Screen and Program entities. Its content depends on the entity type and the derivation type selected upon the instance creation.
Value | Meaning |
---|---|
Default | Value of the Generated language field in the Library Definition tab. |
N | No generation |
X | IBM MVS COBOL II, IBM VSE COBOL II |
0 | IBM MVS/ESA OS/390 |
1 | IBM DOS/VSE |
3 | UNIX, WINDOWS |
4 | BULL GCOS7 COBOL |
5 | BULL GCOS8 COBOL |
6 | BULL GCOS8 COBOL, TP8 Screens |
8 | UNISYS A-SERIES COBOL |
F | TANDEM COBOL |
I | DEC/VAX VMS COBOL |
K | ICL 2900 COBOL |
O | IBM AS/400 COBOL |
Q | ACUCOBOL |
R | TUXEDO COBOL |
U | UNISYS 2200–SERIES COBOL |
Z | IBM AIX |
Value | Meaning |
---|---|
Default | Retrieval of default value |
N | No generation |
0 | Variants 0, 1, X for
CICS (IBM) (programs and BMS maps). Variant 3 for PC/MICRO FOCUS (MS/DOS). Variants 4, 5, 6 for QUESTAR. Variant 8 for UNISYS A-Series SDF format. Variant I for DEC/VAX. Variant Q for UNIX, Windows (ACUCOBOL). Variant U for UNISYS 2200 (programs and FLDP maps). Variant O for AS 400. Variant Z for AIX (IBM). |
1 | Variants 0, X for
IMS (IBM) (programs and MFS maps). Variant 3 for PC/MICRO FOCUS (OS2). Variants 4, 5, 6 for VIP TYPE. |
2 | Variants 0, 1, X for
CICS (IBM), BMS color map Variant 3 for MICRO FOCUS (UNIX). |
3 | Variants 0, X for IMS (IBM), MFS map in color. |
4 | Variants 0, X for
IMS (IBM) monitor. Variant 3 for IBM COBOL program. |
5 | Variants 0, X for CICS (IBM) monitor. |
C | Variants 4, 5, 6, U for
multiterminal. Variants 0, 1, X for CICS multiterminal. Variant K for ICL. Variant 8 for UNISYS A-Series logical screen. |
F | Variant 4 for TDS FORMS
(BULL GCOS7). Variant R for a TPSVRINIT or TPSVRDONE service-type program. |
R | Variant F for a REQUESTER-type program or variant R for a CLIENT-type program. |
S | Variant F for a SERVER-type program or variant R for a SERVICE-type program. |
By default, the generated COBOL files are stored with the design files in a root folder whose default name you can change. You can separate them from the design files or even change the generation project and folder.
The project of the corresponding design file is the default project. If it has been kept, Default is displayed between parentheses next to the project. However, if it has been explicitly changed in the instance, only the project is displayed here, without any other indication. If it has been explicitly changed in the generation Library, Inherited from Library is then displayed between parentheses next to the project. In the instance, you can overwrite the value that is inherited from the Library.
You can select a new project by clicking the symbol or the Change COBOL project and folder button.
If you change the project, it will be taken into account upon the next generation.
The folder of the corresponding design file is the default folder. If it has been kept, Default is displayed between parentheses next to the folder. However, if it has been explicitly changed in the instance, only the folder is displayed here, without any other indication. If it has been explicitly changed in the generation Library, Inherited from Library is then displayed between parentheses next to the folder. In the instance, you can overwrite the value indicated in the Library.
If the default folder has been kept, you can specify a root path for the generated files in the Properties wizard (accessed by clicking the Change project properties button). This path will be automatically inserted in this field, at the beginning of the folder.
You can select a new folder by clicking the symbol or the Change COBOL project and folder button.
If you change the folder, it will be taken into account upon the next generation.
Expand the appropriate project and select a folder or create a folder. Click OK. The selected folder and project are then automatically displayed in the corresponding fields here.
It is the name of the map file (.bms, .mfs, or .map) generated from this instance. The generated file name of the map can then differ from the instance name. If this field is not entered, the map name is the instance name.
For CICS, you indicate the map set name.
For IMS, you indicate the format name.
For TANDEM, you indicate the name of the associated server for an R-type Screen (REQUESTER).