Dialog Complement tab
In this tab, you enter the information common to all of the Screens of the Dialog, and data related to the physical environment of the transaction.
- The characteristics of the communication common area that conveys the information between the Screens of the Dialog.
- The code of the first Screen. This Screen is displayed when the transaction is started.
- The characteristics of the error message file of the Dialog.
Other options are selected according to the environment and TP monitor in use at the site.
More than one value can be entered in the Options field. They must be separated by a space. When the Screen is generated, warnings point out erroneous parameters, if any.Common area
The communication common area constitutes the area of exchange between the various Screens of the Dialog.
- Data Structure
- By default, no common area is indicated and this field is titled No
common area selected yet.
To specify the Data Structure that constitutes the common area, click Modify and select a Data Structure in the selection box.
This Data Structure stores the information that is common to all of the Screens of a Dialog and the necessary Segment access keys.
If the selected Data Structure consists of more than one Segment, the Segments are redefined in the LINKAGE SECTION (WORKING-STORAGE SECTION if appropriate).
- Complementary length
- You must specify a number if the length of the common area exceeds
100 characters. The length of the common area (5-xxnn-LENGTH in the generated programs) is determined by the combined lengths of the following elements:
- The Screen code (6 characters)
- A common area Data Structure
- A field that stores the access keys of the Segments in display
- Technical information (not apparent)
When you calculate this length, you must take into account the following facts:- The length that corresponds to the access keys of each Segment in display is calculated by
category. Example: If a Segment is used in the screen-top, repetitive, and screen-bottom categories, the length of the keys is calculated as follows:
- The length of the key for the screen-top category
- + twice the length of the key for the repetitive category
- + the length of the key for the screen-bottom category
- If the MDT-OFF option or, for the BULL multiscreen variant and UNISYS A series, the DYNPRT option is specified in this tab, you must take into account the length of the longest Screen Segment of the Dialog to calculate the key length.
- PSB or Subschema code
- This field is reserved for DL/1 database Segments.
The PCB name of the error message file (external name) must belong to the PSB.
For HP3000, you must specify the ALLBASE/SQL Database Block code for a monitor generation with a database connection.
- First Screen of the Dialog
- Here you indicate the code of the first Screen of the transaction. According to the type of code to generate, the specifications of this field vary:
- For CICS®, if no first Screen is specified, the common area of each Screen of the Dialog is generated in the WORKING-STORAGE SECTION.
If a first Screen is specified, the common area of each Screen of the Dialog is generated in the LINKAGE SECTION. However, for the first Screen, it is generated in the WORKING-STORAGE SECTION.
- For IMS™, a monitor program is generated. It calls the selected Screen at the beginning of a Dialog and calls it again at the end of the Dialog. The external names of the first Screen and of its corresponding program must have been previously defined in the Screen Definition.
The code is required, even when the MONITOFF option is indicated.
- For GCOS7 and GCOS8, this field is only used with multiterminal type transactions.
- For DEC/VAX, MICRO FOCUS, and HP3000, a branching monitor is generated. This monitor branches to the Screen at the beginning of the conversation.
- For UNISYS-A, this field is used for the multiterminal type transactions.
- For UNISYS-2200, this field is not used.
- For CICS®, if no first Screen is specified, the common area of each Screen of the Dialog is generated in the WORKING-STORAGE SECTION.
- Options
- Enter the options and separate them with blanks. The options are not checked for
validation.
The options vary according to the Dialog and Screen type and to the COBOL type.
See Table 1 for the options on a standard Dialog or Screen. The options can also be entered in the -GO Lines.
See Table 2 for the options on a Client Dialog or Screen. Other options can be entered in the -GO Lines.
Note: A synonym is sometimes associated with some options. This way, you can enter all the necessary options.Table 1. Options on a standard Dialog or Screen. This table presents the options that can be indicated in the Complement tab of a standard Dialog or in the -GO Lines of a standard Dialog or Screen. If the options are entered in the Dialog, they become the default options of the Screens.
Values Meaning ATTRE UNISYS 2200: Defines the default attributes at the Screen level. ATTRIB UNISYS 2200: Keeps the display of the attributes that are dynamically specified (Reverse video and Blink). This option applies to F7020. CICS: Recognizes the dynamic modification of the presentation attributes. This option applies to F7020.
BREAKDATE Breaks down date Data Elements. The date Data Elements is broken down into elementary Data Elements upon generation.
In the -GO Lines, you can also inhibit this option by entering BREAKDATE=NO if it was set to YES in the Library.
This breakdown is effective in the following entities:- In Programs, on the elementary Data Elements of the Segments that are called in the -CD Lines and in the work areas.
- In Dialogs and Screens, on the elementary Data Elements of the Segments that are called in the Dialog Complement tab, in the -CS Lines tab, and in the work areas.
- On the Data Elements that are called in the work areas.
If you activate the BREAKDATE option, the Data Elements that are defined with a date format are generated as elementary fields that correspond to the year, month, and day. It also contains a separator if a separator is included in the date format
Example of a date defined with an M-type format (MM/DD/YYYY):
10 ffnn-date. 11 ffnn-date-MMX. 12 ffnn-date-MM PICTURE 99. 11 ffnn-date-S1 PICTURE X. 11 ffnn-date-DDX. 12 ffnn-date-DD PICTURE 99. 11 ffnn-date-S2 PICTURE X. 11 ffnn-date-YYX. 12 ffnn-date-YY PICTURE 9(4).
Notes:A date is broken down only if the generated COBOL level of the date field is lower than or equal to 47.
If a VALUE has been entered, it is generated in the group field.
Any additional information (such as a VALUE) must be entered on the same line as the Data Element call on I, E, or S-type lines in the work areas. If a continuation line has been specified, the date is not broken down.
The Data Elements that are called in SQL Segments cannot be broken down, except if these SQL Segments are DB2® Segments and if the DESCR=ALL option is entered in the -GO Lines of the DB2 Database Block.
Since host variables cannot be group fields, the elementary fields are generated under a redefined group field in the following way: ffnn-date-BRK REDEFINES ffnn-date.
CSSA On standard Dialog only: Memorizes all the SSAs that are used upon a generated access to a database. This option is valid for all the Screens of the Dialog. When this option is specified, all the Screens in the Dialog must be recompiled because the length of the communication area is increased.
DCPROC Generates the DECLARE CURSOR of DB2, NONSTOP SQL, and DATACOM tables in the PROCEDURE DIVISION, FOC function. If this option is not specified, the DECLARE CURSOR is generated in the WORKING-STORAGE SECTION.
DFHAID IBM® CICS: Initializes the PF key table with the content of DFHAID. DYNAM Calls Pactables Tables with a dynamic call. DYNPRT Specifies the recognition of the variable field protection in the DE-AT table (position 5) and the automatic processing of the protection in F7020. Enter an F in position 5 of the DE-AT table for the Data Element. The Data Element then becomes protected and is received by the program (nature F).
This option is unavailable with the IBM 36, UNISYS A series variant (SDF format).
F10 Processes each category (top, bottom, repetitive) if the category contains at least one variable field or access to a Segment. FOR Formats the generated COBOL lines. The DATA DIVISION lines are left-aligned, the PROCEDURE DIVISION lines are not aligned and there is one COBOL command per line. With this option, up to 150 lines are possible in a COBOL paragraph (between two periods).Warning: This option still exists but is no longer maintainedHEXVAL UNISYS A: Generates fields with an HEXADECIMAL value as PIC XX. HLPI Generates the file access with the HLPI interface. HLPVAL Sends the values to be checked (indicated in the -D Lines of a Data Element) to the error messages file. It is true even if this check has been removed from the Screen where the Data Element is called. HPRT Calls the documentation that is associated with the protected fields (P or F type). It includes the documentation of the Data Element (Data Element -D Lines) and the associated Texts and comments (C or T line after an F line) in the Screen -GE Lines. In the help program, the screen flow is as follows: first the help on the variable Data Elements, then the help on the protected Data Elements (in the order of the -CE Lines).
IMSME IMS: Generates the multiscreen variant. INDEXS DL/1: Generates the Segment access through secondary indexes. This option is not compatible with the NOP58 option if the target Segment is different from the source Segment and if the source Segment is not generated in the PSB field.
LOGMES CICS multiterminal and MICRO FOCUS: Generates a logical message. This message manages both the screen display and the sending of messages to the communication monitor, which is selected with the MONIT option (if it is not a default value in the COBOL type). AS/400® and IMS: This option is used for the internet only.
LPAGE or LPA Manages the LOGICAL PAGING in implicit mode (with PA1 function key) or in explicit mode (with a logical paging operator on the Screen -CE Lines). The LPAGE option is available with a monitor, a submonitor, or with MONITOFF.
With the MONITOFF option, paging applies to the same Screen only.
With a monitor or submonitor, paging applies to several Screens if the Screen codes are entered on the Dialog work areas.Note: If submonitors are used, all the Screens that constitute a paging group must be in the same submonitor.The LPAGE and SWAP options are not compatible. If they are both indicated, only the LPAGE option is recognized.
MONIT IBM CICS and UNISYS A Series: Generates with a monitor. MONITOFF or MOFF IMS: Gets one transaction code per Dialog Screen and does not generate a monitor. MONITOFF and NOTRAC are incompatible. If they are both entered, only the MONITOFF option is recognized.
NOATTR IMS: Generates the protected fields in the MOD without their attributes (ATTR=YES). This option is valid for all the Screens of a Dialog. NOLOCK AS/400: Reads the Segments without update. It adds the WITH NO LOCK clause to the read function when the file is open in OPEN I-O. This option does not work if several Segments of a same file are accessed, some with update, some without, because READ WITH NO LOCK removes the preceding lock.
NOOCF Does not set value 1 to the OCF variable upon the first program input (no F0160 function). NOOPEN MICRO FOCUS and DEC: Optimizes the opening of the HE file (help file backup), the LE, OU, EM (error messages) files, and the CONNECT to ORACLE. NOPSB Limits the Segment generation. In each Screen, only the Segments in use and their hierarchical parents are generated. In the monitor and submonitors, the PSB field is no longer generated and is not sent to the Screens.
NORPT Does not automatically process the repeated Data Elements. NOSAV DEC/VAX, GCOS7, MICRO FOCUS, ICL, and IBM 38: Avoids generating the description of, and the physical access to the HE help file. NOSDERR UNISYS 2200: Recognizes the ERMSG Data Element in the message, which therefore is not sent by the SEND ERROR clause. NOTRAC IMS: Does not generate the transaction code in the MID of the first Screen of the Dialog. OCF Sets value 1 to the OCF variable upon the first program input (current default value). OFF Generates the programs and maps of the Dialog with the MDT-OFF option (default value for GCOS7 FORMS). ON Generates the programs and maps of the Dialog with the MDT-ON option (default value, except for GCOS7 FORMS). PACSQL Recognizes the data that is entered in the Segment -GG Lines for the SQL statements. PSBINIT CICS-DL/1 Screen with monitor option: Used for the connection to the PSB and its termination (SCHEDULE PSB and TERMINATE) on the submonitor and not on each Screen. REFER or REF Generates the list of all the Data Elements that are referenced in the Dialog program. This list is formatted as comments in the WORKING-STORAGE SECTION. It includes the following Data Elements: - Data Elements from the Segments that are called in the -CS Lines,
- Data Elements from the Segments that are called in the work areas, on F-type lines,
- Data Elements that are directly called in the work areas on I-, E-, or S- type lines,
- Data Elements that are directly called in the -CE Lines.
REPET or RPT Validates, transfers, and sets the attributes for the variable fields that are repeated horizontally or vertically. When a repeated field is used in a Segment access, you must indicate the number of repeated uses in the Screen -CS Lines.
SQLALL or SQA SQL: Lists all the table columns in the Segment access commands: (SELECT ALL COLDELCOn, ... INTO :FFNN-DELCOn)SQLCA or SQC SQL: Generates the INCLUDE SQLCA statement in the WORKING-STORAGE SECTION if one or more DB2 or NONSTOP SQL Segments are called in the Screen (-CS Lines tab, Organization = S, Q, or N). SQLIND or SQI Generates the presence indicators for the Data Element before it is updated or displayed. SQLREF or SQR Generates the indicators for the new V-FFnn-DELCO structure. Cross-references are then automatically managed. SSMON Recognizes the PSB of the submonitor that each Screen belongs to. One PSB is then generated for each submonitor instead of one PSB for all the Screens in the Dialog (see the -GG Lines). SWAP IMS: Option to be used with a monitor or submonitor. The Screen to branch to through a function key is indicated in the MFS map. In each map, a 10-character FUNC field is generated and includes the PF key value and the external name of the next Screen to branch to.
For End-Of-Conversation, the external name of the Screen must not be entered.
When a deferred branching is used, or when OPER is set with the PF key, the external name is the name that corresponds to the generated map.
The FUNC field is processed in the monitor or submonitor.
The SWAP option improves performance as it avoids loading the program which processes the branching.
Note: If the MONITOFF or LPAGE option is specified, the SWAP option is not recognized.TMF TANDEM: Recognizes the transactional mode by generating BEGIN-TRANSACTION and END-TRANSACTION in the requesters and BEGIN-WORK and COMMIT-WORK orders in the Pacweb communication monitor. TS CICS: Manages the communication area outside the LINKAGE SECTION. This area is described in the WORKING-STORAGE SECTION and saved in TEMPORARY STORAGE by default. In addition, with MDTOFF and a call to the help function, the Screen is saved in only one area. TZVAR BULL: Uses the reception and display areas in case of an error. ZNUM GCOS7 (except GCOS7 FORMS) and GCOS8: Conditions the transfer of the numeric fields to the message (F8145) by the fact that no error was encountered (SCR-ER = 0). Table 2. Options on a Client Dialog. This table presents the options that can be indicated in the Complement tab of a Client Dialog. These options become the default options for all the Screens of this Dialog.
Other options can be entered in the -GO Lines.
Values Meaning HPRT Calls the documentation that is associated with the protected fields (P or F type). It includes the documentation of the Data Element (Data Element -D Lines) and the associated Texts and comments (C or T line after an F line) in the Screen -GE Lines. In the help program, the screen flow is as follows: first the help on the variable Data Elements, then the help on the protected Data Elements (in the order of the -CE Lines).
INICHECK Checks the Data Element presence. Option for a Client Dialog.
A buffer for the Data Element presence is generated and initialized to P (absent Data Element). When Data Elements are transferred (F30 function), the host variable indicator of each Data Element actually transferred is set to N. The transfers for display are also conditioned by the Data Element presence.
MONIT Indicates the use of a client monitor or submonitor. The monitor handles the transfer of one client to another and the server calls. For the types of COBOL codes that require a monitor (MICRO FOCUS), this option makes it possible to manage the server calls in the monitor.
NOATTR IMS: Generates the protected fields in the MOD without their attributes (ATTR=YES). This option is valid for all the Screens of a Dialog. NOOCF Does not set value 1 to the OCF variable upon the first program input (no F0160 function). NORPT Does not automatically process the repeated Data Elements. NOSAV DEC/VAX, GCOS7, MICRO FOCUS, ICL, and IBM 38: Avoids generating the description of, and the physical access to the HE help file. NOTRAC IMS: Does not generate the transaction code in the MID of the first Screen of the Dialog. OFF Generates the programs and maps of the Dialog with the MDT-OFF option (default value for GCOS7 FORMS). ON Generates the programs and maps of the Dialog with the MDT-ON option (default value, except for GCOS7 FORMS). SERVER MICRO FOCUS WINDOWS/NT: The multi-applications server handles the display. TMF TANDEM: Recognizes the transactional mode by generating BEGIN-TRANSACTION and END-TRANSACTION in the requesters and BEGIN-WORK and COMMIT-WORK orders in the Pacweb communication monitor. TS CICS: Manages the communication area outside the LINKAGE SECTION. This area is described in the WORKING-STORAGE SECTION and saved in TEMPORARY STORAGE by default. In addition, with MDTOFF and a call to the help function, the Screen is saved in only one area.
Error file
Enter the physical characteristics of the error message file. They must be specified to generate the file description and access.
The physical access levels are generated in function F8098. If you want to rewrite these access levels, you must overwrite this function.
- Organization
- Select the organization of the error message file:
- blank: None
- D: DL/1 database Segment
The description of the error message file and the access to it are automatically generated. In IMS, the description of the error message file is not automatically generated. You must describe it in a Segment called in a hierarchical Database Block.
- S: DB2 database
- U: Access by specific code
- V: Indexed organization
- Y : UNYSIS 2200 SFS indexed organization
Segments are declared in FD and the access levels are generated in function F80.
- External name
- Enter the external name of the error message file. Its value varies
according to the type of COBOL code to generate:
- For IBM CICS - VSAM, enter a DDNAME on 8 characters.
- For GCOS7 - UFAS, enter a file code on 2 characters.
- For GCOS8-TP8, enter an external name on the first 4 characters (generated in the SELECT clause) and a blocking factor on the last 4 characters (generated in the FD clause).
- For any other type of COBOL code, enter a logical name, which is generated in the SELECT clause.