Server Dialog or Server Definition tab
This tab is common to the Server Dialog and its constituting Servers, except the COBOL target, which is specific to the Servers. The values selected at the Dialog level become the default values of the Servers and are marked as Inherited on the Servers Definition tab. Inappropriate default values can be overridden at the Server level.
- Dialog type
- In this field, you initialize the Server Dialog/Server type.
Table 1. Values of the Server Dialog or Server type Values Comments MS: server monitor For TUI applications S: Business Component For TUI and graphic applications IT: initialization/termination Business Component For graphic applications with the development of a Folder MV: communication monitor, simple mode No comment E: error message server For TUI and graphic applications SI: initialization server No comment ST: termination server No comment
- Type of COBOL to generate
- The generation variants of Screens and Servers are the combination of the type of COBOL to
generate and of the TP monitor variant. The type of COBOL to generate constitutes the first
character in the table of the generation variants that is presented in the TP monitor
variant field. Note: Some variants are deprecated. Furthermore, the value 0 is forced to X upon the migration of Pacbase applications.
- TP monitor variant
- The generation variants of Server are the combination of the type of COBOL to generate and of
the TP monitor variant. The TP monitor variant constitutes the second character in the table of the
Server generation variants.
The variants that start with N do not trigger any generation.
The following table presents all the available generation variant types. The deprecated variant types cannot be used to generate.
Table 2. Server generation variants Variant types Generatable variants Deprecated variants X0: IBM CICS - BMS maps X X1: IBM IMS - MFS maps X 0 : IBM DOS/VSE X 30: MICROFOCUS MS-DOS X 31: MICROFOCUS OS2 X 32: MICROFOCUS UNIX X 33: MICROFOCUS X 34: MICROFOCUS VisualAge COBOL X 40: BULL GCOS7 COBOL X 50: BULL GCOS8 et 6: BULL GCOS8 TP8 X 80 and 81 for UNISYS A X F0 and F1 for TANDEM X I0: DEC/VAX IMS X K: ICL X O0: AS/400 X Q0: ACUCOBOL X R0: TUXEDO X RC: TUXEDO Carray X U0: UNISYS 2200 X Z0: IBM AIX X
COBOL target
By default, the generated COBOL files are stored with the design files in a root folder whose default name you can change. However, 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 displayed 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 another 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 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 another 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, only if 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: See the help on Modifying the generation target in the project properties wizard.
Proxies generation
From a Server (except IT: Initialization/Termination Business Component and E: Error Message Server), selecting generates the proxy that can be used to manage the services of the Business Component on the Logical View in a graphic environment.
The proxy is generated as a .txt file in the project and folder that are indicated. By default, the generation project is different from the generation project of the COBOL files but is identical to the project generation of the service managers.
The explanations on the COBOL target apply to the proxies generation.
The proxy must then be integrated into the graphic applications so that the Client can activate the services on the Server.
Service management generation
- The type of the Server (or Server Dialog if the value is inherited) is S: Business Component.
- The LOCATION=FMCODE-ENVIRNAME option is present in the -GO Lines of the Business Component or of its Dialog. In this option, FMCODE is the Communication Monitor name and ENVIRNAME the environment name. The presence of LOCATION triggers the default recognition of the implicit SRVMGR=YES option (this option is not visible). The service manager is then generated by default.
- The SRVMGR=NO option is not present in the -GO Lines of the Business Component or of its Dialog. The SRVMGR=NO option overrides the implicit SRVMGR=YES option.
The service manager is generated as a .cbl file in the project and folder that are indicated. By default, the generation project is different from the generation project of the COBOL files but is identical to the project generation of the proxies.
The content of the .cbl file that corresponds to the service manager must not be modified. If it is, the modifications are automatically removed upon the next generation.
The explanations on the COBOL target apply to the service management generation.
- Program external name
- It is the name of the file that is generated from this instance. The generated file name can then differ from the instance name.
- Service manager external name
- This field is used for a Business Component-type Server. It contains the name of the service
manager that is generated from the Business Component. The COBOL code of this manager complements
the COBOL code of the Business Component if the Business Component is not included in a Folder.
If the external name is not entered whereas a service manager must be generated, the Business Component name is recognized. If the generation project and folder of the service manager are identical to the generation project and folder of the Business Component, then the service manager name must be different from the Business Component name.
- Transaction code
- Enter the transaction code in the following way:
- For a CICS® variant, enter the four-character transaction code (Dialog default code).
- For an IMS™ variant, enter the transaction code that is associated with the Dialog. This field is displayed on all the Dialog Screens except if the MONITOFF option (one transaction code for each Screen, no generated monitor) is specified.