Definition tab

The values that are specified in the Dialog become the default values of the Folders that are attached to the Dialog. They are marked as Inherited in the Folder Definition tab. You can overwrite these default values in each Folder. In this tab, you can indicate the generation information for the COBOL code and the Folder proxy, the error Server, and some options. Moreover, in the Definition tab of the Folder Dialog only, you can specify a user buffer.

Parent Dialog
This field is displayed in the Folder editor. It contains the name of the parent Folder Dialog that was selected in the Folder creation wizard. You can click Change to select another parent Dialog.
Type of COBOL and map to generate
Only the COBOL type X : IBM MVS/ESA OS390 and the transactional monitor variant 0 (IBM®/CICS®) are available.

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.

Note: More information on the Generation target of a Program or a Screen is available.

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 COBOL folder or map (for Screen) can be indicated in various entities:
  • 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.
Proxy
The explanations of the COBOL target are relevant but they apply to the proxy that is generated from the Folder. This proxy has a .txt extension. It is used in a Client that was created in a graphical development tool. In this case, it contains the information that is required to interface the Client with the Server. You specify the generation project and folder of the Folder proxy. They default to the project and folder of the Folder design file.
Error Server
If you do not specify it in the Dialog, you must specify it in the Folder. It is required. It must correspond to a Server with a type E: Error Message Server and must be defined.

It is used to access the error message file.

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.
Lock option
The upload and download mechanisms used in the management of Folders increase the time lapse between the reading of the initial image of a Folder and the return of its updated image. In this context, a lock process can adequately prevent simultaneous updates on the same Folder occurrence. In this manner, the coherence of accumulated updates is ensured. The following values are available:
  • N: No lock option: This option is selected by default.
  • P: Lock option - Before update: This option creates an exclusive ownership of the Folder, which is locked to all other users during the update.
  • O: Lock option - After update: This option is active only when the update is requested. It compares the Folder image that is initially loaded with the current image. If they are identical, the update is accepted.

If you select a lock option, you must write the lock and unlock processing in the Business Component that is associated with the Folder root node. You must then create a subfunction that depends on a function 05*C. To do so, open the function and subfunction creation wizard from the COBOL code editor. Select the Business Component model with an Insertion relative to the Logical View processing, then select the service LOCK or UNLOCK.

Paging mode
Two paging modes are available:
  • N: Non-extend paging mode: This option makes it possible to page forward and backward through a predefined population. Each paging operation (forward or backward) runs a reading request and its result replaces the result of the previous reading.
  • E: Extend paging mode: This option makes it possible to page forward through a predefined population. The result of each paging adds to the result of the previous reading. The reading of the previous pages is then handled by the graphic client.
Buffer
The message between the Client and the Server can convey contextual data that is related to the execution of the called service. You must manage this data in a structure that is named a user buffer. You specify this buffer in the Definition tab of the Folder Dialog.

With the buffer, you can set fields that complement the technical buffer (for the data compression or the identification of the end user for example). This buffer is included in each message that is exchanged between all the Business Components of the Dialog and the Client. If your application is to use a user buffer, you must declare the corresponding Segment in the -CS Lines of the Business Component Dialog and select the value W as its organization.

The Business Components of a Folder (root and dependent nodes) must use the same Segment to define the user buffer. This rule is automatically respected if these Business Components belong to the same Dialog.

The user buffer of a Business Component that is called or associated with a reference node must have the same length as the buffer that is used for the root or dependent nodes.

A user buffer must not contain repeated or FILLER Data Elements.

In the Definition tab of the Folder Dialog, you must select the Segment that constitutes the user buffer. You can assign it a Code in the Folder that is different from the Segment name.

The Description type field contains values that generate, from the Segment description in the repository, different descriptions in the generated COBOL code. The following values can be selected:
  • Conventional (fixed) (default value) for a Segment that might have a specific part. For example, it can be a Data Structure with a Segment.
  • 1: Database Segments for a Segment without any common part. For example, it can be, for a database, various Segments that are defined in the same Data Structure.
  • E: Table type for Table-type Segments. The input format of the Data Elements that are called in the Segment is taken into account.
  • 2 : Conventional (variable) for a complete Segment with a variable length for an indexed organization (V). The generated description can vary according to the generation variant.

The default value of the External name field corresponds to the first two characters of the Segment Code in the Folder.


Feedback