A project represents the physical distribution of your instances in your workspace. It groups directories and files. It is used to organize resources that can be built, shared, or versioned.
A Pacbase project contains a subset of file that correspond to the models and the generated sources that constitute an application.
If you are maintaining a Pacbase application, selecting a package is not advised. The instance override mechanism is then made easier because the overriding instance is always in the same package as the overridden instance. You do not need to manage the presence of both the instances in the same package, which is the requirement of an override.
You select the Library by clicking Browse.
The internal format is used when the Data Element is called in one of the following components:
You must ensure the compatibility between the input and internal formats.
Symbolic value | Meaning |
---|---|
D | Without century (DDMMYY or MMDDYY) |
I | Without century (YYMMDD) |
E | Without century (DD/MM/YY or MM/DD/YY) |
S | With century (CCYYMMDD) |
C | With century (DDMMCCYY or MMDDCCYY) |
M | With century (DD/MM/CCYY or MM/DD/CCYY) |
G | Gregorian format (CCYY-MM-DD) |
T | Time format (HH:MM:SS) |
TS | Timestamp format |
For details on the use of the formats with the various types of Database Blocks, see the summary tables in chapter Columns: Data Elements of the Relational SQL Database Description manual at this URL:
http://www-01.ibm.com/support/docview.wss?rs=37&uid=swg27005477
Symbolic value | Meaning |
---|---|
D | Without century (DDMMYY or MMDDYY) |
I | Without century (YYMMDD) |
E | Without century (DD/MM/YY or MM/DD/YY) |
S | With century (CCYYMMDD) |
C | With century (DDMMCCYY or MMDDCCYY) |
M | With century (DD/MM/CCYY or MM/DD/CCYY) |
G | Gregorian format (CCYY-MM-DD) |
T | Time format (HH:MM:SS) |
TS | Timestamp format |
All the other sections provide links to the corresponding editor tabs.
If no information is displayed in the section, click the symbol in front of the section name. It gives you access to the More button. Click it to access the corresponding tab.
If you click Hierarchy, you can see a partial view of the design build path. In this view, the project that constitutes the work context is the lowest project of the hierarchy.
More information can be found in the following links: The work context and The design build path.
So the current instance is associated with the generation parameters indicated in the Library that is displayed here. You can click Change to select another Library.
The value that you can enter here changes according to whether it is a COBOL position for a Program or a Screen.
Value | Meaning |
---|---|
AA to ZZ and 0A to 0Z | These values cause the lines entered in this
tab to be generated at the beginning of the WORKING-STORAGE
SECTION. These lines are generated:
|
00 to 09, 1A to 19... 9A to 99 | The lines entered in this tab will be generated in the WORKING-STORAGE SECTION, after all the Data Structures whose COBOL position is lower than this prefix |
Value | Meaning |
---|---|
AA to 0Z | The description is generated in the WORKING-STORAGE SECTION. |
00 to 99 | The description is generated in the LINKAGE SECTION. |
AA and 00 | These values are used for automatically generated data. |
99 | With a Line number = 999, this value is used for the PROCEDURE DIVISION statement. Therefore, you can use it to create a line with a sequencing number 99999, which replaces the PROCEDURE DIVISION line automatically generated. |
$n | This value represents a parameterized value in a Macro. |
In a Macro, you can parameterize it by assigning it a $n value.
It sets the sequence in which the Data Structure or Report is processed in the program.
When the Data Structure or Report is used only once in a program, it is advised to indicate the code that is entered as the Data Structure or Report name. This name is entered upon creation. However, if it is called more than once in a program, you can differentiate these calls.
You can parameterize this code in a Macro with $n.
Value | Comment |
---|---|
E : Input | Default value for Data Structures with a usage set to M: Transaction to be validated, N: Transaction not to be validated, or E: Transaction with error checking |
I: Internal | Default value for Data Structures whose usage is not set to: M: Transaction to be validated, N: Transaction not to be validated, or E: Transaction with error checking |
S: Output |
Value | Meaning |
---|---|
Redefined records | No VALUE clause is generated |
1: Records without initial values | Records without initial values or occurs. These
records contain the Segment common part, followed by the different
specific parts. If the Data Structure description is included in the COBOL FILE SECTION, the COBOL record level field must be set to 2: COBOL 01 level for DS area and Segments at 02 level. With this value, the specific Segments are described without redefines, at the COBOL level 02. Several Segment descriptions are grouped under the same I/O area. |
2: Records with initial values | Records with the specific initial values indicated in the Segment -CE Lines tab. These values can also default to blank or zero depending on the format. Initial values are also generated for the multiple occurrence fields if the Generated language of the Library is set to D: COBOL II, 85, LE. |
3: Records with occurs (used with level 2) | Records that incorporate the number of occurrences
that are indicated in the Table size field
of the Segment Definition tab. No VALUE clause is generated. If the Data Structure description is included in the COBOL FILE SECTION, the COBOL record level field must be set to 2: COBOL 01 level for DS area and Segments at 02 level. You cannot use this description type if the common part Segment of this Data Structure is assigned a value in the Table size field of the Segment Definition. In that case, set the Organization to W: File description in Working and the Usage to T: Table stored in memory. |
4: Records with occurs (used with level 3) | Records that incorporate the number of occurrences
that are indicated in the Table size field
of the Segment Definition tab. The associated Level field
must be set to 3. The associated COBOL record level must be set to 3: COBOL level varying with records description type Comment specific to the OnLine Systems Development function: The index is not generated if the Generated description type set to 4: Records with occurs (used with level 3), and the COBOL record level is set to 3: COBOL level varying with records description type, A COBOL level 02 is used to access the table made up of occurs of the same record (ddssT). A COBOL level 01 is used to group the whole Data Structure (common or specific parts, whether occurred or not). A group level field that incorporates all instances is generated. You cannot use this description type if the common part Segment of this Data Structure is assigned a value in the Table size field of the Segment Definition tab. In that case, set the Organization to W: File description in Working, and the Usage to T: Table stored in memory. |
Value | Meaning |
---|---|
1: COBOL 01 level for DS area and Segments | If the Data Structure description is included
in the COBOL FILE SECTION, the Segments must be redefined. If a Data Structure has no common part with a non-redefined description, the D.S. area is only included when the Generated description type is set to Redefined records. |
2: COBOL 01 level for DS area and Segments at 02 level | If the Generated description type is set to Redefined records, the D.S. area and Segments are described at level 02. Preferably set the Organization to L: Working with placement and define the higher levels through work areas. |
3: COBOL level varying with records description type | Level 02 for D.S. area and level 03 for Segments
if the Generated description type is set to 1:
Records without initial values, 2: Records
with initial values or 3: Records with occurs
(used with level 2). Level 01 for D.S. area and level 03 for Segments if the Generated description type is set to 4: Records with occurs (used with level 3). Level 03 for both the D.S. and Segments if the Generated description type is set to Redefined records. |
4: COBOL 02 level for Data Elements, DS areas and Segment levels disappear | Reserved for the D.S. with an Organization set
to L: Working with placement and a Usage set
to D: Output file. Level 02 for the group Data Elements or elementary Data Elements that are not part of a group. The elementary Data Elements that are part of a group are displayed but the D.S. area and Segment levels are not included. Level 01 is to be defined in the work areas. |
5: COBOL 01 level for Data Elements, DS areas and Segment levels disappear | Organization set to L:
Working with placement or W: File description
in Working and a Usage set to D:
Output file. Level 01 for the group Data Elements or elementary Data Elements that are not part of a group. The elementary Data Elements that are part of a group are displayed but the D.S. area and Segment levels are not included. |
You can select whether the Data Structure must be generated in the WORKING-STORAGE SECTION, or as the description of a Pactables Table.
You can also use this field to specify database descriptions when the Database Description function is not used. These values are taken into account by application Programs.
Value | Comment |
---|---|
S: Sequential | Only authorized value for a Report, a sequential file or a sort file Data Structure. |
V: VSAM, UFAS | One of the two possible values for an indexed
file Data Structure This value generates the STATUS KEY IS clause. The corresponding field is declared in the File Status field of the -CD Line Definition of the -CD Lines tab (the part that can be viewed by clicking More). |
I: Indexed | The other possible value for an indexed file
Data Structure. This value corresponds to an indexed sequential organization (ISP for GCOS8 BCD). An ISP file coded LE is
generated in 3 work areas:
|
G: Table description | This value generates the communication area with the Pactables function. |
L: Working with placement | File descriptions are generated in the WORKING-STORAGE SECTION, in the location you indicate in the COBOL position field. |
W: File description in Working | File descriptions are generated in the WORKING-STORAGE SECTION, before the WSS-BEGIN constant. |
Y: Pacbench C/S | Call of the COPY clause that corresponds to the communication area between the client and the server (Pacbench C/S Business Components only). |
X: Comment | Data Structure that is used as a comment, not used for generation. |
2: DB2 Segments or VAX/SQL | Generation and description of a DB2 or VAX/SQL Segment. Only the physical accesses are not generated. The structure of the variable indicators corresponding to the columns of the DB2 or VAX/SQL table is always generated. |
Q: DB2 or ALLBASE/SQL | Reserved for the description of SQL/DS, DB2/2 or DB2/6000 databases (IBM), or ALLBASE/SQL databases (HP3000), or DB2/2 or DB2/600 databases (MICRO FOCUS). |
D: DL/1, IDS I and II | Reserved for the description of Segments or records of the IMS (DL/1), IDS I or IDS II databases, in the generation of DBD, SYSGEN, schemas, or application programs |
B: IDMS | IDMS |
A: ADABAS | ADABAS |
T: TOTAL files | TOTAL files |
O: ORACLE (< V6) | ORACLE (< V6) |
C: INTEREL RDBC or RFM | INTEREL RDBC or RFM |
R: RDMS | RDMS |
4: DB2/400 | DB2/400 |
M: DATACOM DB | DATACOM DB |
N: NONSTOP SQL | NONSTOP SQL |
P: ORACLE V6 and V7 | ORACLE V6 and V7 |
9: INFORMIX, SYBASE, INGRES/SQL, or SQL SERVER | INFORMIX, SYBASE, INGRES/SQL, or SQL SERVER |
Z: Data Structure for SOCRATE/CLIO | Data Structure for SOCRATE/CLIO |
F: Formal for SOCRATE/CLIO | Formal for SOCRATE/CLIO |
This field is used with the Pactables function, to indicate which subschema is to be described. It is numeric, from 0 to 9 (0 corresponds to subschema 10).
The Segment level is nested in the Data Structure level. The first two characters of the Segment are constituted by the Data Structure and the last two characters are the Segment code in program.
The Segment level displays the Segment name in the first column and the Segment label in the second column.
If you expand this level, you see the Segment code in program, which is editable.
The composition of each Segment (equivalent to the -CE Lines tab) is displayed in the nested level, with one line for each called Data Element. If you expand the first line of a called Data Element, you can see and modify its name and label. Its Attributes level contains the same information as the Definition tab, except the inheritance, which can be specified in the tab only.
This name consists of alphabetic or numeric characters only. The following table lists the Data Element names that cannot be created:
Name | Reserved for |
---|---|
FILLER | Field alignment |
ENPR GRPR ERUT |
Error check fields on transaction files (options
of the Batch Applications function) Data Element error check Segment error check User-defined errors |
With the USAGE clause of a COBOL numeric variable, you indicate the internal representation of its value. Different usages are available depending on the COBOL variants adapted to the material in use.
Value | Meaning |
---|---|
B | COMPUTATIONAL-1 ICL 1900 BINARY-1 UNISYS 1100 |
C | COMPUTATIONAL (binary), IBM
or equivalent; BINARY, IBM and COBOL II variant. |
D | DISPLAY (default option). Required for date Data Elements. |
F | COMPUTATIONAL-1 IBM or equivalent. COMPUTATIONAL-9 BULL GCOS7. COMPUTATIONAL-11 GCOS8. Relational DBD: floating point, simple precision. |
G | COMPUTATIONAL SYNCHRONIZED RIGHT ICL
2900 COMPUTATIONAL-5 MICRO FOCUS. |
H | COMPUTATIONAL UNISYS 2200. BINARY UNISYS 2200 (COBOL 85) |
I | DISPLAY-1 UNISYS 2200 |
J | COMPUTATIONAL-6 GCOS8. REAL UNISYS-A. |
N | COMPUTATIONAL-4 aligned on
a half-byte. You must add the complement if the length is uneven. NATIONAL (default usage) for Unicode-type Data Elements (U type). |
O | COMPUTATIONAL-4 UNISYS 2200 |
P | COMPUTATIONAL-1 GCOS8. |
Q | COMPUTATIONAL GCOS8. |
R | COMPUTATIONAL SYNCHRONIZED RIGHT, IBM or equivalent; This value is preferable to C when binary data is aligned on even addresses, because the corresponding COBOL statements are more efficient. |
T | COMPUTATIONAL-3 PACKED SYNC. GCOS8. |
U | COMPUTATIONAL-1 UNISYS 2200. |
W | COMPUTATIONAL-2 UNISYS 2200. COMPUTATIONAL-12 GCOS8. Relational database: floating point, double precision. |
X | DISPLAY SIGN IS TRAILING SEPARATE CHARACTER. or NATIONAL SIGN IS TRAILING SEPARATE CHARACTER for Unicode-type Data Elements (U type). |
Y | DB-KEY GCOS8. POINTER IBM and MICRO FOCUS |
Z | In batch mode only: this option, which is only used with an output format, generates a BLANK WHEN ZERO clause with the Batch Applications function. |
0 | COMPUTATIONAL-7 GCOS8 |
1 | DISPLAY SIGN LEADING SEPARATE -
UNISYS 2200, GCOS8, IBM, TANDEM, GCOS7. or NATIONAL SIGN IS LEADING SEPARATE CHARACTER for Unicode-type Data Elements (U type). |
2 | DISPLAY-2 GCOS8 = DISPLAY. Fields are compared in accordance with the commercial collating sequence and not in accordance with the standard BULL sequence. |
3 | COMPUTATIONAL-3 IBM or equivalent. COMPUTATIONAL GCOS7 PACKED-DECIMAL UNISYS 2200 (COBOL 85) |
5 | COMPUTATIONAL-1 GCOS7 GCOS8 |
6 | COMPUTATIONAL-2 GCOS7 GCOS8 |
7 | COMPUTATIONAL-5 ICL 2900. |
8 | COMPUTATIONAL BULL 66 GCOS8. |
9 | COMPUTATIONAL-3 GCOS7 and GCOS8. |
Value | Comments |
---|---|
U | References the access key for a Table. This value must be indicated on the group Data Element if it is a group key. |
S | Indicates that the Data Element belongs to at least one subsystem. |
Values | Comments |
---|---|
U | References a unique key for a DL/1 database. |
M | References a multiple key for a DL/1 database. |
1 - 9 | Secondary index All other values designate a search field. |
Values | Comments |
---|---|
0 - 9 | AS400 physical file key. relational databases |
V | Variable length column |
Blank | Fixed-length column |
W | For DB2 SQL, SQL/DS and ORACLE, generation of a variable length column (VARCHAR). |
L | For DB2 SQL, SQL/DS and ORACLE, generation of a LONG VARCHAR. |
Moreover, if this line is not correct, this column also displays an error or warning symbol, depending on the severity of the error. A hover help indicates the source of the error.
These lines are used for documentation purposes. You can write or edit text in relation to the selected instance. You can write, modify, move, or delete text lines by using the standard word-processing functions.
The variable labels and the symbolic values that are indicated in the selected Input Aid -D Lines tab are then displayed in the Description column, in a read-only mode. The Input Aid name is displayed in the Input Aid column.
Moreover, if this line is not correct, this column also displays an error or warning symbol, depending on the severity of the error. A hover help indicates the source of the error.
This column displays a value I on all the Input Aid insertions. This value cannot be selected directly.
The selected instance is then automatically displayed in the Description field.
The Description field can be modified for a Text call, in order to indicate generic codes.
The Text calls for the documentation are aligned according to a standard print layout.
All the Text calls are aligned (except if the non-alignment $$ parameter was used). The $n print windows that are indicated in the Text are respected. If they are not specified, the default print window ($0) is used.
All the text processing options are functional (underlining, negative indentation...).
Line skips are specified in the Text, but limited to a three-line skip (line skips greater than three become three-line skips); page skips become three-line skips. By default, the skips are one line, except for print windows $0 and $1, where they are two lines.
If the list is large, you can reduce it by entering a string that is used as a filter. You can filter on the code or on the label of the instance.
Select an instance and click OK to insert it.For the Y: Pacbench C/S organization, this field must contain the code of the COBOL COPY clause that represents the communication area of the Pacbench C/S application component that accesses the Logical View.
For an SQL database Data Structure, this field must contain the code of the SQL Block.
For any other Data Structure, the contents of this field depend on the value of the Type of COBOL code in the Program Definition tab.
Type of COBOL code | Field value |
---|---|
1: IBM DOS/VSE | This field can take 3 forms:
|
X: IBM MVS/ESA OS/390 | The ASSIGN clause (for sequential
files, S: sequential organization), with SYSnnn as
external name, is generated in the following form: SYSnnn-UT-....-S-SYSnnn For OS/390: DDNAME |
4: BULL GCOS7 | INTERNAL-FILE-NAME |
5: BULL GCOS8 | File-code (2 characters) |
F: TANDEM | External name |
I: DEC/VAX VMS | External name |
This field is used to obtain a Data Structure description in a particular area (communication area with DBMS or LINKAGE SECTION) or at the beginning of the WORKING-STORAGE SECTION.
This field is reserved for Data Structures whose organization is W: File description in Working or L: Working with placement.
To obtain the description of a Data Structure in the WORKING-STORAGE SECTION, you are advised to indicate it in the work area lines of the COBOL code, using micropatterns.
Value | Meaning |
---|---|
00 | The description of the Data Structure is inserted after all the work areas. |
Alphabetic characters | The description of the Data Structure is inserted
after all the work areas whose COBOL position corresponds
to this value. The description and work areas are found at the beginning of the WORKING-STORAGE SECTION of the generated program. These lines are displayed before the Data Structures whose organization is W: File description in Working and before the Data Structures whose code in the Program is greater than this alphabetic code. Note: Do not select a COBOL
position identical to the Data Structure code
in the program for a Data Structure with a W:
File description in Working organization.
|
Alphanumeric characters | The description of the Data Structure is inserted
after all the work areas whose COBOL position corresponds
to this value. The work area lines and the description can be found in the generated program, at the end of the WORKING-STORAGE SECTION among the user areas. |
Value | Comment |
---|---|
S: Sequential | Sequential access |
R: Direct / Random | The read function is not generated automatically |
D: Dynamic | This value is reserved for VSAM files. |
Value | Comment |
---|---|
F: Fixed | At generation time, the lengths of the different records are aligned with the length of the longest record. |
V: Variable | |
U: Undefined | |
S: Spanned | This value is reserved for IBM MVS and DOS variants. |
Value | Comment |
---|---|
I: Input | Can be selected with a usage set to C: Consultation, T: Table stored in memory, X: Table partially stored in memory, M: Transaction to be validated, N: Transaction not to be validated, and P: Principal. |
O: Output | Can be selected with a usage set to D: Output file, S: Selected, R: Result, E: Transaction with error checking, I: Direct printing, and J: Indirect printing. |
E: Output plus OPEN EXTEND clause | Can be selected with a Types of Code to generate set to 4: BULL GCOS7, 5: BULL GCOS8, 0: IBM MVS/ESA OS/390, U: UNYSIS 2200 Series, F: TANDEM, I: DEC/VAX VMS, and K: ICL 2900 |
R: Input / Output | Direct-access Data Structures only |
T: Sort | In input or output, depending on the usage |
O is the default value.
1 to 9 levels, according to the number of Data Elements to be used for control break processing. These Data Elements are identified as the Sort key composition field for this Data Structure.
O is the default value.
1 to 9 levels. Enter the number of Data Elements (elementary or group) on which a file matching is to be synchronized for this Data Structure. This number identifies the number of the key fields (identified in the Sort key composition field) that are involved in the synchronization.
For an automatic synchronization, the following conditions must be met:Value | Comment |
---|---|
C: Consultation | Any input file |
D: Output file | Any output file |
P: Principal | Input file, likely to be updated by a transaction file (whose usage is M: Transaction to be validated or N: Transaction not to be validated) |
R: Result | Updated principal file in sequential access mode. (When the Data Structure contains an OCCURS DEPENDING ON clause, the output/result Data Structure must be declared as an D: Output file). |
S: Selected | Output file that is extracted from another file. It differs from the D: Output file usage because the generated description in the output area is not detailed. For Data Elements with an OCCURS DEPENDING ON clause, the usage must be D: Output file. |
T: Table stored in memory | A file to be fully stored in memory. The table is generated according to the number of occurrences that is indicated on each Segment Definition. The maximum number of selected Segments for each Data Structure is 50. |
X: Table partially stored in memory | A file to be partially stored in memory. Fillers included in the Segment composition are not stored. Elementary Data Elements other than fillers are limited to 10 (in addition to the Record type Element) for the 00 Segment and to 29 for each specific non-00 Segment. |
M: Transaction to be validated | Input file to be validated which can update
other files. The generated functions range from 30 to 76. Note: Only
one M: Transaction to be validated or N:
Transaction not to be validated Data Structure is authorized
in a Program.
|
N: Transaction not to be validated | Input file that can update other files. The
generated functions are: 30, 33, 39, 70 - 76. Note: Only one M:
Transaction to be validated or N: Transaction
not to be validated Data Structure is authorized in a
Program.
|
E: Transaction with error checking | Output transaction file that contains a field
that identifyies records with errors. Generation of the fields to track the erroneous Data Elements and Segments, and the user-defined errors by using the reserved Data Elements ENPR, GRPR, and ERUT. Selected or not, the descriptions of these Data Elements are generated (using the DE-ERR and ER-PRR Data Elements). |
I: Direct printing | Direct printing (or by SYSOUT in
IBM MVS). Upon generation, the lines whose structure identifier is 00 in the Report are ignored. |
J: Indirect printing | Indirect printing to be processed by a spool
program. The fields that are required to identify the lines, line skips... are indicated in the structure identifier 00 in the Report. |
Y: Internal codification table |
They are identified by the value that is entered in the Sort key field on the Segment -CE Lines tab.
The order for sorting these key Data Elements can be entered here. To do so, you use the values that are assigned on the -CE Lines tab in the appropriate order, from major to minor.
If you do enter anything here, the Data Elements that are coded with value 1 - 9 are taken as the default.
It must contain a numeric value. It corresponds to the block size (the size of the physical record). Spaces and zeros are equivalent.
If the Data Structure has a Usage set to P: Principal, you must enter the Code in program of the result output Data Structure (2 characters).
If the Data Structure has a Usage set to R: Result or D: Output file, you must enter the Code in program of the principal input Data Structure (two characters).
Value | Type of COBOL code |
---|---|
R: reader | 1: IBM DOS/VSE |
P: punch | 1: IBM DOS/VSE |
S: EBCDIC set code | 5: BULL GCOS8 and U: UNYSIS 2200 Series |
C: ASCII set code | 5: BULL GCOS8 |
O: OPTIONAL option not to be generated | 4: BULL GCOS7 and 5: BULL GCOS8 |
A: ALLOWING ALL file optioning option & REGARDLESS sequential reading | I: DEC VAX VMS |
If you specify it, you are advised to specify a character string, on 10 characters maximum, in the following format:
This code, on six characters, is required for indexed files.
Enter the code (6 characters) of the Data Element whose values identify the different record types of a Data Structure.
This Data Element must belong to the common part Segment (00 Segment).
This name can also be specified in the Structure code field of the Segment Definition tab.
The values of the field correspond to the association between the Data Element and the presentation characteristics for these labels.
Value | Comment |
---|---|
Default value | Defaults to the value specified in the Dialog. |
F: Data Element only | The Data Element is displayed without any label. |
L: Data Element with long label, left-aligned | The Data Element is preceded by the Data Element label, left-aligned, on 36 positions. |
M: Data Element with long label, right-aligned | The Data Element is preceded by the Data Element label, right-aligned, on 36 positions. |
N: Data Element with long label, left-aligned, trimmed right | The Data Element is preceded by the Data Element label, left-aligned with the deletion of blanks on the right. |
R: Data Element with long relational label, left-aligned | The Data Element is preceded by the relational label, left-aligned on 18 positions. |
S: Data Element with short label, left-aligned | The Data Element is preceded by the short label, left-aligned, on 18 positions. |
T: Data Element with short label, right-aligned | The Data Element is preceded by the short label, right-aligned, on 18 positions. |
U: Data Element with short label, left-aligned, trimmed right | The Data Element is preceded by the short label, left-aligned, with the deletion of blanks at the end of the string. |
1: Data Element topped by a single line column label | The Data Element is topped by the column label on one line. |
2: Data Element topped by a 2–line column label | The Data Element is topped by the column label on two lines. |
3: Data Element topped by a 3–line column label | The Data Element is topped by the column label on three lines. |
Line overflow is automatically controlled.
If both the line and column numbers equal zero, the element is automatically moved to the next tabulation point available.
Any line length overflow and field overlapping are automatically detected. However, the presence of a space in front of each field is not verified.
If both the line and column numbers equal zero, the element is automatically moved to the next tabulation point available.
Segment belonging to the Screen top.
Segment belonging to the repetitive category (as many times as there are repetitions),
Segment belonging to the Screen bottom.
The logical access is generated automatically, according to the use of the Segment
User-defined Segment access in structure code. (organization different from X)
No description of Segment. (organization different from X)
The logical access is generated automatically, according to the use of the Segment.
User-defined Segment access (organization different from S)
Segment accesses not described (organization different from S)
Options | Description |
---|---|
No control break. | No control break for organizations different
from X. Indicates that a Data Element, which belongs to a key in the repetitive category of a Screen, must remain constant during display. |
C: display break | Display break for organizations different from X. Indicates that a Data Element, which belongs to a key in the repetitive category of a Screen, must remain constant during display. |
E: display break (SQL) | For an SQL organization: Display control break. It causes the generation of an equal condition in the WHERE clause of the SQL DECLARE CURSOR statement (and not >=, which is generated otherwise). The use of CURSOR is optimized in the repetitive category. |
Options | Description |
---|---|
No control break. | No control break for organizations different
from S. It indicates that a Data Element, belonging to a key in the repetitive part, must remain constant during the selection. |
C: display break | Display break for organizations different from S. It indicates that a Data Element, belonging to a key in the repetitive part, must remain constant during the selection. |
E: Selection for control break (SQL) | For an SQL organization: it causes the generation of an equal condition in the WHERE clause of the SQL DECLARE CURSOR statement. |
Options | Description |
---|---|
No value or N: | For an organization different from X:
No access statement is generated for this Segment in the validation
and update processing (default). For an X organization: No Server call is generated. |
L: | For an organization different from X:
A simple read command is generated for the Segment. For an X organization: Server call for selection. |
E: | For an organization different from X:
Existence validation to run. A read command with the setting of an
error code is generated (if it is not found). For an X organization: Server call for validation. |
M: | For an organization different from X:
Updated Segment (modification only). For an X organization: Server call for validation and update. |
X: | For an organization different from X:
Updated Segment (creation and modification only). For an X organization: Server call for validation and selection |
S: | For an organization different from X only: Updated Segment (deletion only). |
C: | For an organization different from X only: Segment (deletion only) |
T: | For an organization different from X:
Updated Segment (creation, modification, and deletion). In these
cases, the existence validations and the update statements corresponding
to the selected options are generated. If the Segment is related to a previous Segment, regardless of the indicated use, only the update commands for modification and creation are generated. For an X organization: Server call for validation, update, and selection. |
U: | For an X organization only: User-defined logical accesses |
Options | Description |
---|---|
No value or N | For an organization different from X, S,
and 2: No access statement is generated for
this Segment in the validation and update processing (default).
For an X or 2 organization: No Server call is generated. |
L: | For an organization different from X, S,
and 2: A simple read command is generated for
the Segment. For an X or 2 organization: Server call for selection. |
E: | For an organization different from X and 2:
Existence validation to run. A read command with the setting of an
error code is generated (if it is not found). For an X or 2 organization: Server call for validation. |
M: | For an organization different from X, S,
and 2: Updated Segment (modification only).
For an X or 2organization: Server call for validation and update. |
X: | For an organization different from X, S,
and 2: Updated Segment (creation and modification
only). For an X or 2 organization: Server call for validation and selection |
S: | For an organization different from X, S, and 2 only: Updated Segment (deletion only). |
C: | For an organization different from X, S, and 2 only: Segment (deletion only) |
T: | For an organization different from X, S,
and 2: Updated Segment (creation, modification,
and deletion). In these cases, the existence validations and the
update statements corresponding to the selected options are generated. If the Segment is related to a previous Segment, regardless of the indicated use, only the update commands for modification and creation are generated. For an X or 2 organization: Server call for validation, update, and selection. |
U: | For an X or 2 organization only: User defined logical accesses |
Options | Description |
---|---|
No value or N: | For organizations different from X:
No order is generated for this Segment in the selection processing
(default option). No Server call is generated. |
A: | For organizations different from X:
Used in selection. The access order is generated for the selection
according to the type of logical access processing. If the previous
Segment code is blank and the Segment is used, the key is saved in
the conversation area. X organization: Server call for selection (not compatible with the L value in reception). |
U: | X organization only: Call of a user service |
Options | Description |
---|---|
No value or N | For organizations different from X, S,
and 2: No order is generated for this Segment
in the selection processing (default option). For an X or 2 organization: No Server call is generated. |
A: | For organizations different from X or 2:
Used in selection. The access order is generated for the selection
according to the type of logical access processing. If the previous
Segment code is blank and the Segment is used, the key is saved in
the conversation area. For an X or 2 organization: Server call for selection (not compatible with the L value in reception). |
U: | For an X or 2 organization only: Call of a User service |
In this pane, you select a Data Element or you enter the name of a new Data Element (not defined in the repository) that is to be used as the primary access key to the Segment. For a VSAM file (V organization), it must be entered on the Segment 00 line. The Data Element that is specified here is considered as a group Data Element, except for SQL organizations where it is considered as an elementary Data Element.
For a Table (G organization), you select a subsystem by indicating the value NUSSY in this field. The associated key (G-ddss-NUSSY) is generated.
For SQL database Segments, a key element must be entered on each line where the value of the Use in display field is not N.
In generated accesses, the Segments are selected when the keys are equal for an update or a direct read. For a sequential read in the repetitive category, the Segments are selected when their keys are equal or greater.
A Segment cannot contain more than 10 key Data Elements.
For an error message file or a Table, if the error message Segment is an SQL/DS Segment or if it has a V or W organization, the Data Element key must be ERKEY.
Values | Meaning |
---|---|
ATTRE | UNISYS 2200: Definition of the 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. CICS: The dynamic modification of the presentation attributes is taken into account. This option applies to F7020. |
BREAKDATE | Breakdown of date Data Elements. The date Data Elements is broken down into elementary Data Elements upon generation. You can also inhibit this option by entering BREAKDATE=NO if it was set to YES at the Library level. This
breakdown is effective:
Notes:
A date is broken down only if the generated COBOL level of the date field is lower than or equal to 47. 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 on 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:
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. |
CSSA | Memorizes all the SSAs during a generated access
to a database. This option is valid for 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: Downloads 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 PROCEDURE DIVISION, 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 PF key table. |
DYNAM | Pactables Tables with a DYNAM 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 any category (top, bottom, repetitive), if it contains at least one variable field or access to a Segment. |
FOR | Formatting of the generated COBOL: Left-aligned DATA
DIVISION, no alignment for the PROCEDURE DIVISION but
one COBOL command per line. This option can 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: Generates fields with an HEXADECIMAL value in PIC XX. |
HLPI | Generates the 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. It is true even if this check has been removed from the Screen in which 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 and the associated
Texts and comments in the Screen -GC Lines section 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 tab). |
IMSME | Generates the multiscreen variant for IMS. |
INDEXS | DL/1: Generates the Segment accesses through
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 multiterminal and MICRO FOCUS
variants, this option generates a logical message. This message manages
both the screen display and the sending of messages to the communication
monitor. This monitor is 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 internet. |
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 tab). The LPAGE option is available with a monitor, a submonitor, or with MONITOFF. With the MONITOFF option, paging can be performed on the same Screen only. With a monitor or submonitor, paging
is possible on several Screens by entering the Screen codes on the
Dialog work areas.
Note: If submonitors are used, all the Screens
that make up 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 | 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, only the MONITOFF option is recognized. |
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: Reads the Segments without update. It
adds the WITH NO LOCK clause in 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. |
NOMAP | Generation or no generation of the map, according
to the value of the option in the Dialog and the Screen. The value NOMAP is equivalent to NOMAP=YES. It inhibits the generation of the map. The value NOMAP=NO generates the map. The value of the option in the Dialog is automatically taken into account in the Screen. To keep this value in all the Screens of the Dialog, there is no need to enter this option in all the Screens. However,
to modify the value of the option that is indicated in the Dialog
in some Screens, you must indicate it. The two following cases are
possible:
|
NOOCF | The OCF variable is not set to value 1 upon the first program run (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. |
NOOPENB | HP3000, TURBOIMAGE: 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 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 | No automatic processing of repeated Data Elements. |
NOSAV | With DEC/VAX, GCOS7, MICRO FOCUS, ICL, IBM 36 and 38, and BOS/TP: 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: The transaction code is not generated 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 programs and maps of the Dialog are generated with option MDT-OFF (default value for GCOS7 FORMS). |
ON | Default value (except for GCOS7 FORMS). The programs and maps of the Dialog are generated with the MDT-ON option. |
PACSQL | Takes into account 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 used in a Dialog. This list is found in the WORKING-STORAGE
SECTION for documentation purposes. It includes the following
Data Elements:
|
REPET or RPT | Validation, transfer, and positioning of 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 Segment call of the Screen. |
SQLALL or SQA | SQL: All the table columns are listed in the
Segment access commands:
|
SQLCA or SQC | SQL: The INCLUDE SQLCA is generated in the WORKING-STORAGE SECTION if one or more DB2 or NONSTOP SQL Segments are 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 | The indicators are generated for the new V-FFnn-DELCO structure. Cross-references are then automatically managed. |
SSMON | You can indicate one PSB 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 code of 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 using deferred branching, or setting OPER with the PF key, the external name is that of 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 selected, the SWAP option is not taken into
account.
|
TMF | TANDEM: With this option, the transactional mode is recognized by the generation of BEGIN-TRANSACTION and END-TRANSACTION in the requesters and of BEGIN-WORK and COMMIT-WORK orders in the Pacweb communication monitor. |
TS | CICS: The communication area is managed 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 to the message (F8145) is conditioned by the fact that no error was encountered (SCR-ER = 0). |
Values | Meaning |
---|---|
ACCESERR | Maximum number of errors on Segment access that
can be returned to the Client. Three-character value (default value = 001) This option must be entered in the Business Component or, for single-view developments, in the Server Dialog. |
CALLTYPE | Call type between the client and the server. For CICS, there are 2 possible values: LINK (default) and CALL. For IMS, there are 2 possible values: CALL (default) and CHNG (equivalent to a CALL CHANGE). For GCOS8, there are 3 possible values: CALL, LINK (equivalent to a CALL .ILINK) and NTPR (equivalent to a NEXT TPR). For TANDEM PATHWAY, the value is PATHSEND. |
CHANGE | Only with TUXEDO: CHANGE=NO (default value): the Business Component is called with the TPNOCHANGE parameter CHANGE=NO (default value): the Business Component is called with the TPCHANGE parameter |
CHECKSER | The Business Component checks the data of the
Logical View. CHECKSER=NO (default): the Business Component does not check the Logical View data CHECKSER=YES: the Business Component checks the Logical View data |
CONNECT | Management of the connections to and the disconnections
from SQL databases Default value: CONNECT=YES: the connections and disconnections are generated in the communication monitor For TUXEDO, the connections and disconnections are generated in the initialization and termination Business Components (SI or ST type). In this case, you must call one of the Table Segments from the database you want to be connected to or disconnected from. |
CURSUFF | Default value: CURSUFF=NO:
the cursor names are not suffixed CURSUFF=YES: the SQL cursor names are suffixed with the corresponding Screen name. |
DATAERR | Maximum number of errors on the Logical View
data that can be detected by a Server. This option must be entered in the Business Component or, for single-view developments, in the Server Dialog. |
ERRLAB | For single-view development: This option specifies
how the errors must be returned. By default, ERRLAB=YES: the communication monitor retrieves the key, severity, and error messages that are returned by the Business Component before sending back the answer to the client component. But if the option value is set to NO, only the error key is returned. In that case, the error message is locally read by the client application. This option must be entered in the Folder or, for single-view developments, in the Server Dialog. |
ERRSERV | For single-view development: name of the error
server. This option is required and must be indicated in the Server Dialog. |
LGCOMM | Length of the communication area of Business
Components, I/T servers, error message servers. Numeric value on 5 characters |
LOCATION | For single-view development: This option is
required. It represents the name of the communication monitor (on
6 characters) followed by the environment name (on 20 characters maximum).
Example: LOCATION=FMCODE-ENVIRNAME
|
LOCKMODE | For single-view development: This option is
used to specify the type of lock. The lock process prevents the update of a set of data to avoid inconsistency. If the value is NO (default) no lock is specified. The PESSIMIST value creates an exclusive appropriation of the instance that is locked to all other users during updating. The OPTIMIST value performs the lock only when the update is requested and compares the initially loaded image with its current image in the database. If they are identical, the update is accepted. |
MONSER | Name of the server monitor (default: no server monitor), for the TUI mode. |
NULLMNGT | NULLMNGT=NO (default
value): No management of the presence of the Data Elements of the
Logical Views at the Proxy level. NULLMNGT=YES:
Management of the presence of the Data Elements of the Logical Views.
Note: If NULLMNGT=YES,
then VECTPRES=YES is systematically implemented.
|
NUVERS | Version management of the Business Component
and TUI client. The versions of the TUI client and of the Business Component are transferred to the server through the technological buffer, Default value for TUI clients only: generation session |
PACTABLE | Name of the Pactables access program to the
CICS Business Component. Default value: PACTABLE |
PAGEMODE | For single-view development: paging mode. The NOEXTEND value (by default) pages forward and backward through a predefined population. Each paging operation (forward or backward) runs a read request and its result replaces that of the previous read. The EXTEND value pages forwards through a predefined population, and the result of each paging adds to the preceding read. The reading of the previous pages is then handled by the graphic client. |
PROCESS | Available for TANDEM PATHWAY only. Name of the process when the Business Component is called 15 characters maximum without space. No lowercase/uppercase conversion |
SEGMBUFF= s1s2s3s4… | Available only with the specification of a Folder.
This option must be entered in the Business Component. Option that is used for the server buffer. It selects Segments of the Data Structure that defines the server buffer. s1, s2, s3.... represent the first 2 characters of the Segments. 10 Segments can be selected by this option. A maximum of 10 SEGMBUFF options can be called in each Business Component. Selecting the 00 Segment is not necessary; it is systematically generated if it is present in the Data Structure. By default, all the Segments of the Data Structure are selected. |
SERVBUFF | Available only with the specification of a Folder.
This option must be entered in the Server Dialog or in the Business
Component. This option identifies the Data Structure that defines the server buffer: SERVBUFF=xx (where xx is the Data Structure on 2 characters). Various Segments of this Data Structure can be selected in each Business Component with the SEGMBUFF= s1s2s3s4… option. |
TRAN | Only with TUXEDO TRAN=YES (default value): use of the transactional mode for the TUXEDO variant TRAN=NO: no use of the transactional mode. |
VECTPRES | Management of the presence of the Logical View
Data Elements. VECTPRES=NO: No management of the presence of the Logical View Data Elements VECTPRES=YES:
Management of the presence of the Logical View Data Elements
Note: If CHECKSER=YES,
the VECTPRES=YES option is systematically implemented.
|
Values | Meaning |
---|---|
FORMAT | Format of the Logical View Data Elements. With the INTERNAL value, the Data Elements that are called in the Logical View are generated with their internal format; their usage is taken into account. With the EXTENDED option, the format of the Data Elements is computed. Their usage is ignored and replaced by the DISPLAY usage. For signed numeric Data Elements, it is replaced by the SIGN IS LEADING usage. |
INICHECK | Check of the Data Element presence. Option that is reserved to a TUI 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 the display are also conditioned by the Data Element presence (N). |
INITSERV | Call of an initialization server. |
LTHENATT | Length of the backup area of the DE-ATT table (default: 2000). |
LTHREPET | Length of the backup area of the repetitive category (default: 1000). |
LTHSCREEN | Length of the backup area of the screen message (default: 6000). |
NUVERS | Version management of the Business Component
and TUI client. The versions of the TUI client and of the Business Component are transferred to the server through the technological buffer. Default value for TUI clients only: generation session |
TERMSERV | Call of a termination server |
Values | Meaning |
---|---|
BASE | The relational Database Block name is required
when all the application components access the same database. In this case, the connection orders are automatically generated in the communication monitors of the application. |
BASELOC | Location type of the relational database to
access. This information is mandatory especially when the connection Database Block name is specified. The possible values are: LOCAL (default) or REMOTE. |
CALLSPG | Call type of the components that are associated
with the monitor. If there is no client monitor, it is the call type of the server component by the client component. For GCOS8, this option must have the same value as the CALLTYPE option. |
CALLTYPE | Call type between the client and the server. For CICS, there are 2 possible values: LINK (default) and CALL. For IMS, there are 2 possible values: CALL (default) and CHNG (equivalent to a CALL CHANGE). For GCOS8, there are 3 possible values: CALL, LINK (equivalent to a CALL .ILINK), and NTPR (equivalent to a NEXT TPR). For TANDEM PATHWAY, the value is PATHSEND. |
LGCOMZS | Length of the communication area between the
client and server monitors. Its value must be 5 characters long (default: 32000). |
WAITINT | Option specific to WebSphere MQ and TCP/IP Socket
on MVS/CICS Waiting time, in seconds, between two queries. Default value for WebSphere MQ = 0001 Default value for TCP/IP Socket on MVS/CICS = 1800 |
WAITINT1 | Option specific to WebSphere MQ Waiting time, in seconds, before the first request starts (default value = unlimited). This default value can be modified by entering a four-character number |
WORKFILB | Required option for a graphical client Database Block for a work file with an H organization or external name for a work file with a V organization. |
WORKFILS | Required option for a graphical client Segment that is associated with the work file. |
WORKFILO | Required option for a graphical client Organization of the work file that is used by the associated monitor and Services Manager:
|
In the -GG Lines tab, you can modify the generation lines that are associated with the Database Block description lines.
Depending on the type of description line, lines are automatically displayed to guide you when you enter the physical information of the Block.
These lines are identified by VIRT or GUID in the last field of the table of the -GG Lines tab. Collectively, these lines are called virtual lines. The lines that are identified by VIRT are generated. To modify these lines, you must override them and create new lines between beginning and end insertion lines. When you select a virtual line and click Override, the VIRT or GUID line is changed into a FromVIRT or FromGUID line. Then, it can be modified. You can also edit the FromGUID and FromVIRT lines by selecting them and pressing the F2 key. You can create lines anywhere in the table. However, if you want them to be taken into account at generation time, you must identify them with a G Type.
Moreover, if this line is not correct, this column also displays an error or warning symbol, depending on the severity of the error. A hover help indicates the source of the error.
G CREATE TABLE (EXTERNAL NAME) IN DATABASE-NAME
G ---> COLUMN INSERTION BEGINNING <---
G LIBFO
G DO10LIBFO FLOAT
G ---> COLUMN INSERTION END <---
G IN DATABASE-TABLE SPACE
FFNNDELCO
FFNNDELCO
is the code that is entered in the SOURCE COLUMN field. G CREATE VIEW (VIEW NAME)
G ---> COLUMN INSERTION BEGINNING <---
G <LIBFO>
G DO10LIBFO FLOAT
G ---> COLUMN INSERTION END <---
G AS SELECT ALL
G ---> SOURCE COLUMN INSERTION BEGINNING <---
G <FFNN-DELCO>
G 'X'
G ---> SOURCE COLUMN INSERTION END <---
G FROM (SOURCE TABLES NAME)
You
must manage the Source table (after the FROM clause).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 |
Value | Meaning |
---|---|
Default | Retrieval of 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. |
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).
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 |
FM: communication monitor | For graphic applications |
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 |
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).
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.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.
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 describe it in a Segment called in a hierarchical Database Block.
Segments are declared in FD and accesses are generated in function F80.
The extraction method is sent to the Business Component through the technical part of the message. Parameters must be described in the application part of the message, that is in the Logical View.
In the Data type field, you specify the parameters by value for all the extraction methods that can be used by the Logical View. To do so, you call defined Data Elements. For each parameter, you enter the E type, which indicates that it is a parameter. Each identifier Data Element (U type) is an implicit parameter. The other Data Elements that describe the contents of the Logical View cannot be used as parameters. The E-type Data Element does not belong to the description of a Logical View. If necessary, you can define and call a child Data Element.Options | Description |
---|---|
None | Data Element not used as a parameter. For Data Elements that describe the Logical View. |
U: identifier for paging | Data Elements that are to be used as selection criteria or start key for the reading of data occurrences in the database. Identifier for the paging of a list for the client. As output from the server, it contains the selection criteria values of the next page. |
R: repeated structure | There is only one repeated structure for one Logical View. A repeated structure is specified in the group Data Elements. This Data Element indicates the beginning of the repeated Data Elements. The end of the repeated Data Elements is deduced from the number of Data Elements in a group. The number of occurrences must be indicated in the Number of occurrences field in the Logical View definition. |
E: extraction parameter | The Data Element is used as a parameter for an extraction method. The E type Data Elements must be entered in the -CE lines before the Data Elements that describe the Logical View contents. Each identifier Data Element (U type) is an implicit extraction parameter. The other Data Elements describing the Logical View cannot be used as parameters. If necessary, you can define and call a child Data Element. |
Options | Description |
---|---|
O: required | Required Data Element. The check for its presence
is generated in the client, and in the Business Component if CHECKSER=YES. Note: It
includes checks in relation to the Data Element description.
|
P: required | Required Data Element. The check for its presence
is generated only in the Business Component, if CHECKSER=YES. Note: It
includes checks in relation to the Data Element description.
|
Blank | The checks that are specified in the Data Element description are generated in the client, and in the Business Component, if CHECKSER=YES. |
F: optional | The checks that are specified in the Data Element description are only generated in the Business Components if CHECKSER=YES. |
Options | Comments |
---|---|
Both directions | Default value for an update service or a selection service. It is the required value for graphic applications. |
C: Client to Server | Client to Business Component: From Logical View to Segment for an update service. |
S: Server to Client | Business Component to client: From Segment to Logical View for a selection service. |
The direction of the transfer must also be indicated in the group Data Elements. The repeated Data Elements must have the same transfer direction. This direction can be indicated on the Data Elements bordering the repeated data (Data Element with an R indicator). You enter the C or S value in this Data Element only if the Direction of transfer field in the Logical View Definition tab is both directions.
PDPPacbaseavailable from Rational Programming Patterns V9.0.1Rational Programming Patterns
The beginning of this file reminds the parameters that were entered to run the Pacbase migration procedures.
It is the default option. It provides the general structure of an iterative structure: beginning of loop (F05), end of run (F20), end of loop (F9099. GO TO F05).
This option does not provide an iterative structure: no beginning of loop (F05), no end of run (F20), no end of loop (F9099. GO TO F05).
It is the default value. The Data Element is present if its value is not blank.
The Data Element is present if its value is not zero.
The Data Element is present if it does not contain low values. This option is available for alphabetic and numeric Data Elements.
If you select this option, the SQL indicators will be generated as: V-XXNN-DELCO.
If you do not select this option, the SQL indicators will be generated as: VXXNNDELCO.
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.
The project of the corresponding design file is the default project. If it has been kept, Default is displayed between parentheses next to the project. However, if it has been explicitly changed in the instance, only the project is displayed here, without any other indication. If it has been 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 by clicking the symbol or the Change COBOL project and folder button.
If you change the project, it will be taken into account upon the next generation.
The folder of the corresponding design file is the default folder. If it has been kept, Default is displayed between parentheses next to the folder. However, if it has been explicitly changed in the instance, only the folder is displayed here, without any other indication. If it has been 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 indicated in the Library.
If the default folder has been kept, you can specify a root path for the generated files in the Properties wizard (accessed by clicking the Change project properties button). This path will be automatically inserted in this field, at the beginning of the folder.
You can select a new folder by clicking the symbol or the Change COBOL project and folder button.
If you change the folder, it will be taken into account upon the next generation.
Expand the appropriate project and select a folder or create a folder. Click OK. The selected folder and project are then automatically displayed in the corresponding fields here.
A called Segment can call another one. A maximum of 4 levels of nesting are possible.