Definition tab
This tab is available for the Dialog, Screen and Program entities. Its content varies according to the entity type.
- Dialog type
- In this field, you initialize the Dialog or Screen type as a standard online type or a TUI type.
- Type of COBOL to generate
- In this field, you specify the COBOL variant for the generated Screen.Note: Some variants are deprecated or not supported. Furthermore, the value 0 is forced to X upon the migration of Pacbase applications.
Table 1. Values of the COBOL to generate 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®.
- TP monitor variant
- In this field, you specify the variant of the TP monitor for
the generated Screen.
Table 2. Values of the TP monitor variant Value Meaning Default Retrieval of the 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.
COBOL target
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.
In a Library, the default values of the COBOL project, COBOL folder, and Map folder (for Screens only) are the values of the current project. If the project and folders are not indicated, the default values in a Dialog are the values of the Library or current project, as applicable. In a Screen or Server, the default values are the values of the Dialog, Library or current project, as applicable.
- A library. It then constitutes the default value for all the Dialogs and Screens or Servers of this Library.
- A Dialog. It then constitutes the default value for all the Screens or Servers of this Dialog.
- A Screen or Server. It then applies to the instance only.
- COBOL project
- The files that are generated from this instance are stored in the project that is indicated in
this field.
The project of the corresponding design file is the default project. If it is kept, Default is displayed between parentheses next to the project. However, if it is explicitly changed in the instance, only the project is displayed in this field, without any other indication. If it is explicitly changed in the Dialog, Inherited from Dialog is then displayed between parentheses next to the project. If it is 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 in the list.
If you change the project, the COBOL folder and map folder (for Screens) are automatically set to the default value (rpp). The new project then applies to the next generation.
- COBOL folder
- The files that are generated from this instance are stored in the folder that is displayed in
this field, inside the project displayed in the previous field.
The folder of the corresponding design file is the default folder. If it is kept, Default is displayed between parentheses next to the folder. However, if it is explicitly changed in the instance, only the folder is displayed in this field, without any other indication. If it is explicitly changed in the Dialog, Inherited from Dialog is then displayed between parentheses next to the folder. If it is 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 that is indicated in the Library.
If the default folder is kept, you can specify a root path for the generated files in the Properties wizard (accessed by clicking Change project properties). This path is then automatically inserted in this field, at the beginning of the folder.
You can select a new folder in the drop-down list. Creating a folder is impossible at this stage. Folders must have already been created in the project, for example from the Resource perspective.
If you change the folder, it applies to the next generation.
- Change project properties
- Click to open the Properties wizard, where you can complete the following actions:
- Change the default folder. This folder contains the design files and is the default target of the generated and metadata files.
- Indicate a root path for the generated files, provided the default generation folder is kept.
- Indicate a root path for the metadata files, which are stored by default in the same folder as the other generated files.
Note: A detailed help is available from the Properties wizard of the project.
- Program external name or COBOL program ID
- This code is the name of the file generated from this instance. The generated file name can then differ from the instance name.
- Map external name
- This field is unavailable on a Dialog.
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).