Rational Developer for System z, Version 7.5

Dialog Complement tab

This tab must contain all the information common to all the Screens of the Dialog.

The information common to all the Screens are:
  • The characteristics of the communication common area which conveys the information needed between the Screens of the Dialog,
  • The code of the first Screen. This is the Screen which is displayed when the transaction is launched.
  • The characteristics of the Error Message file of the Dialog.
The physical characteristics of the Error Message file, the common area, etc., can be entered regardless of the type of TP monitor in use.

Other options are selected according to the hardware and TP monitor in use at the site.

When the Screen is generated, a WARNING type message points 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
In this field, you enter the code of the common area: it is a Data Structure which stores the information common to all of the Screens of a Dialog and the Segment access keys.

As a Data Structure, it may consist of more than one Segment. When this occurs, the Segments will be redefined in the LINKAGE SECTION (WORKING-STORAGE SECTION if appropriate).

Complementary length
You must specify a number in this field 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 Screen code (6 char.), a common area Data Structure, a field which stores the access keys of the Segments in display, and technical information (transparent).

When you calculate this length, you must take into account the fact that:
  • The length which corresponds to the access keys of each Segment in display is calculated by category.
    Example: if a Segment is used in the Screen-top category, the repetitive category and the Screen-bottom category, the length of the keys may be calculated as follows:
    • the length of the key for the screen-top category,
    • + 2 times the length of the key for the repetitive category,
    • + the length of the key for the screen-bottom category.
  • When the MDT-OFF or, for the BULL Multi-Screen variant and UNISYS A series, the DYNPRT (to automatically convert variable fields to protected fields) options are 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 Sub-schema 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 reference
By default, no Screen is selected and this field is titled 'No first screen selected yet'.
According to the type of code to generate, the specifications of this field are different:
  • In CICS:

    If no first Screen is selected, the Common Area of each Screen of the Dialog is generated in the WORKING-STORAGE SECTION.

    If a first Screen is selected, the Common Area of each Screen of the Dialog is generated in the LINKAGE SECTION, except for the first Screen, where it is generated in the WORKING-STORAGE SECTION.

  • In 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 displayed and of its corresponding program must have been previously defined at the Screen Definition level).

    The code is required, even when the MONITOFF option has been indicated.

  • In GCOS7 and GCOS8:

    This field is only used with Multi-terminal type transactions.

  • DEC/VAX, MICROFOCUS and HP3000:

    A branching Monitor is generated. This Monitor branches to the indicated Screen at the beginning of the conversation.

  • UNISYS-A:

    This field is used for the multi-terminal type transactions.

  • UNISYS-2200:

    This field is not used.

Options
Enter here the options, separating them with blanks. All these options can also be entered in the -GO Lines section of the -G Lines tab.
Note: A synonym is sometimes associated with some options to allow the input of all the necessary options.
Values Meaning
ATTRE UNISYS 2200: Definition of default attributes at the Screen level.
ATTRIB UNISYS 2200: The display of the attributes dynamically specified (REVERSE VIDEO and BLINK) is kept. This option applies to F7020.
CSSA Memorizes all SSA’s during a generated access to Databases. This option is valid with all the Screens of a Dialog.

When this option is specified, all the Screens in the Dialog must be recompiled because the length of the COMMUNICATION AREA is increased.

CVISION GCOS6: This option allows to download the standard validations (presence validation, numeric validation, formatting of the initialization character) onto the CVISION screen manager, thus improving performances.
DCPROC Generates the DECLARE CURSOR of DB2, NONSTOP SQL and DATACOM tables in the DIVISION PROCEDURE, FOC function.

If this option is not specified, the DECLARE CURSOR is generated in the WORKING STORAGE SECTION.

DFHAID IBM CICS: its content initializes the PFKEYS Table.
DYNAM Pactables table DYNAM-called.
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 given Data Element. The Data Element is then protected and received by the program (nature F).

This option is not available with the IBM 36, UNISYS A series variant (SDF format).

F10 Processes any category (top, bottom, repetitive), provided that it contains at least one variable field or access to a Segment.
FOR Formatting of the generated COBOL: left-justified DATA DIVISION, no justification for the PROCEDURE DIVISION but one COBOL command per line.

This option may be entered on the Library Definition tab. In this case, the Dialog is generated in formatted COBOL even if the FOR option is not explicitly entered in this field.

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 maintained
HEXVAL UNISYS A: Generation of fields with HEXADECIMAL value in PIC XX.
HLPI Generation of file access with the HLPI interface.
HLPVAL The values to be checked (indicated in the -D Lines of a Data Element) are sent to the error messages file even though this check has been removed from the Screen in which the Data Element is called.
HPRT Calls the documentation associated with the protected fields (P or F type). This includes the documentation associated with the Data Element as well as the Texts and comments associated in the Screen’s -GC Lines section (-G Lines tab), F-type lines)

In the Help program, the screen flow will be: first the help on the variable Data Elements, then the help on the protected Data Elements (in the order of the -CE Lines tab).

IMSME Generation of the ’Multi-Screens’ variant for IMS.
INDEXS DL/1: Automatic generation of the Segment Accesses via secondary indexes.

This option is not compatible with the NOP58 option if the target Segment code is different from the source Segment code and if the source Segment is not generated in the PSB field.

LOGMES With the CICS multi-terminal and Microfocus variants, this option generates a logical message which manages both the screen display and the sending of messages to the communications monitor selected with the MONIT option (if it is not a default value in the variant).

AS400 and IMS: This option is used only for the Web.

LPAGE or LPA LOGICAL PAGING management in implicit mode (with PA1 Function Key) or in explicit mode (with a Logical Paging Operator on the Screen -CE Lines tab).

The LPAGE option is available with a monitor, a sub-monitor, or with MONITOFF.

With the MONITOFF option, pagination can only be done on the same Screen.

With a (sub-)monitor, pagination is possible on several Screens by entering the Screen codes on the Dialog -W Lines tab. For more information, please refer to the IMS-DB/DC ’On-Line Systems’ manual, chapter ’The Generated Program’, subchapter ’Additional Screens’.
Note: If sub-monitors are used, all the Screens that make up a paging group must be in the same sub-monitor.

The LPAGE and SWAP options are not compatible. If they are both coded, only the LPAGE option is recognized.

MONIT UNISYS A Series: generation with a monitor.

IBM CICS: generation with a monitor.

MONITOFF or MOFF IMS: One transaction code per Dialog Screen and no monitor generation.

MONITOFF and NOTRAC are incompatible. If both are entered, MONITOFF overrides NOTRAC.

NOATTR IMS: Generates the protected fields in the MOD without their attributes (ATTR=YES). This option is valid with all the Screens of a Dialog.
NOLOCK AS400: reading of the Segments without update and with the addition of the WITH NO LOCK clause in the reading 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, since READ WITH NO LOCK removes the preceding lock.

NOOPEN MICROFOCUS and DEC: optimization of the opens of the HE files (Help file backup) and of the LE OU EM files (error messages) and of the CONNECT to ORACLE.
NOOPENB HP3000, TurboImage: this option stops the opening of the TurboImage database. The OPEN is not generated in the program.
NOPSB Segment generation limitation:

In each Screen, only the Segments used and their hierarchical parents are generated. In the monitor and sub-monitors, the PSB field is no longer generated and is not transmitted to the Screens.

NOSAV With DEC/VAX, GCOS7, MICROFOCUS, ICL, IBM 36 and 38, and BOS/TP: Avoids the generation of the description of, and the physical access to, the HELP file (HE).
NOSDERR UNISYS 2200: recognition of the ERMSG Data Element in the message, which therefore is not sent by the SEND ERROR clause.
NOTRAC IMS: No generation of the transaction code in the MID of the first Screen of the Dialog.
OCF The OCF variable is set to value ’1’ upon the first program run (Current default value).
OFF The Dialog’s programs and maps are generated with option MDT-OFF (default value for Gcos7 FORMS).
ON Default value (except for Gcos7 FORMS). The Dialog’s programs and maps are generated with option MDT-ON.
PACSQL Validation of the data entered in the -GG section (-G Lines tab) of the Segment for the SQL statements.
PSBINIT CICS-DL1 Screen with monitor option: this option allows to perform the connection to the PSB and its closing (SCHEDULE PSB and TERMINATE) on the sub-monitor and not on each Screen.
REFER or REF Generates the list of all the Data Elements used in a Dialog. This list is found in the WORKING-STORAGE SECTION and has a documentary value. It includes the:
  • Data Elements from the Segments called in the -CS Lines tab,
  • Data Elements from the Segments called in the WORKING-STORAGE SECTION on F-type Work Areas lines (-W Lines tab),
  • Data Elements directly called in the WORKING-STORAGE SECTION on I-, E-, or S- type Work Areas lines (-W Lines tab),
  • Data Elements directly called in the -CE Lines tab,.
REPET or RPT Validation, transfer and positioning of the attributes for the variable fields which are repeated horizontally and/or vertically.

When a repeated field is used in a Segment access, you must indicate the number of repeated uses at the Segment call level of the related Screen.

SQLALL or SQA SQL: All the table columns are listed in the Segment access commands:
(SELECT ALL COLDELCOn, ...  
        INTO   :FFNN-DELCOn)
SQLCA or SQC SQL: Generation of the SQL command INCLUDE SQLCA in WORKING-STORAGE if there is a least one DB2 or Non-Stop SQL Segment called in the Screen: (-CE Lines tab, Organization = S, Q or N).
SQLIND or SQI Presence indicators are generated for the Data Element before it is updated or displayed.
SQLREF or SQR Generation of indicators with the new V-FFnn-DELCO structure, allowing the automatic management of the cross-references.
SSMON This option allows the coding of one PSB for each sub-monitor instead of one PSB for all the Screens in the Dialog. (Refer to the -GG Lines section of the -G Lines tab).
SWAP IMS: Option to be used with a (sub-)monitor.

This option allows the code of the Screen to branch to via a Function Key to be indicated in the MFS map. In each map, a 10-character FUNC field is generated and includes the PFKEY value and the external name of the next Screen to branch to

For End-Of-Conversation, the external name of the Screen must be left blank.

When using deferred branching, or setting OPER with the PFKEY, the external name is that of the generated map.

The FUNC field is processed in the (sub-)monitor.

The SWAP option improves performance as it avoids loading the program which processes the branching.

Note: If the MONITOFF or LPAGE option is selected, the SWAP option is not taken into account.
TMF TANDEM: With this option, the transactional mode can be taken into account through the generation of BEGIN-TRANSACTION and END-TRANSACTION orders in the requesters and through the generation of BEGIN-WORK and COMMIT-WORK orders in the PacWeb Communications Monitor.
TS CICS: Management of the Communication Area outside the LINKAGE SECTION. This area is described in WORKING and saved in TEMPORARY STORAGE by default. In addition, if MDTOFF and call of the HELP function, the Screen is saved in only one area.
TZVAR BULL: With this option, the reception and display areas are used in case of error.
ZNUM The transfer of the numeric fields in the message (F8145) is conditioned by the fact that no error was encountered (SCR-ER = 0).

Error file

Here you specify the physical characteristics of the error message file, which are used to generate the file description and accesses.

The physical accesses are generated in function F8098. If you want to rewrite these accesses, you must overwrite this function.

Organization
Select the organization of the error message file in the dropdown list.
  • : None
  • D: DL/1 Database segment

    The description of the error message file and the accesses to it are automatically generated. In IMS, the description of the error message file is not automatically generated. You must generate 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 the FILE DESCRIPTION and accesses are generated in function F80.

External name
Enter the external name of the error message file. Its value varies according to the type of code to generated:
  • For IBM CICS - VSAM, it is the DDNAME on 8 characters,
  • For GCOS7 - UFAS, it is the file code on 2 characters,
  • For any other variant, except for the GCOS8 TP8 variant, it is the logical name, generated in the SELECT clause.
For DL/1, you must enter the mnemonic code of the PCB. This code must be in the list of PCB’s for the PSB of this transaction.

Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)