A project represents the physical distribution of your instances in your workspace. It groups directories and files. It is used to organize resources which will be built, shared or versioned.
A Pacbase project contains a sub-set of files which correspond to the models and/or generated sources making up a Pacbase application.
There can be various projects for each location (a location is the equivalent of a database).
A package corresponds to a logical group of information.
The logical resources contained in a package can be distributed into various projects.
In the 'Navigator' view of the 'Design' perspective, you will see that the packages represent the branches of your projects. Each package contains its own instances.
For the resources transferred from Pacbase, the naming convention of a package will be {Repository Name}.{Library Path}.{Library Name} So respecting this naming when you create a package is a good idea. To reflect the library hierarchy, you can enter the library names (starting from the highest-level library), and separate each with a period (ex: 'COM.CIF'). This way, the 'Navigator' view will display a first-level branch, COM, with its instances, and a second-level branch, CIF, with its own instances.
You select the library by clicking the Browse... button.
The internal format is used when the Data Element is called in:
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, just click on the arrows located in front of the section name. This gives you access to the More... button. Click on it to access the corresponding tab.
The Documentation section does not directly display the assigned documentation. You must access the Documentation tab to see it.
So the current instance is associated with the generation parameters indicated in the library displayed here. You can click the Change... button to select another library.
Value | Meaning |
---|---|
For a batch program | |
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.
Relatively to the Data Structures called in the -CD Lines tab,
these lines will be generated as follows:
|
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 |
For a transactional program | |
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 by the system for data generated automatically. |
99 | With a Line number = 999, this value is used by the system for the PROCEDURE DIVISION statement. Therefore, you may use it to create a line with a sequencing number 99999, which will replace the PROCEDURE DIVISION line which is automatically generated. |
$n | This represents a parameterized value in a Macro-Structure |
In a Macro, it can be parameterized by assigning it a $n value
It sets the sequence in which the Data Structure or Report will be processed in the program.
When the Data Structure or Report is used only once in a program, it is recommended to indicate the same code as the one entered as the Data Structure/Report name (chosen upon creation). However if it is called more than once in a program, you may 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 t:, M: Transaction to be validatedN: Transaction notto be validated, E: Transaction with error checking |
I: Internal | Default value for Data Structures whose usage is NOT set to: M: Transaction to be validatedN: Transaction notto be validated, 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
are presented with the Segment common part followed by the different specific
parts. If the Data Structure description appears 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 together 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 may also default to blank or zero depending on the format. Initial values are also generated for the occursed 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 which incorporate the occurs number indicated
in the 'Table size' field of the Segment Definition tab. No VALUE clause will be generated. If the Data Structure description appears 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. This type of description cannot be used 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 ). |
4: Records with occurs (used with level 3) | Records which incorporate the occurs number 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 On LIne System 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 D.S. together - common or specific parts, whether occurred or not. A group level field that incorporates all instances is generated. This type of description cannot be used 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 appears 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 will only appear 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 will be 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 & 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 & level 03 for Segments if the Generated description type is set to 4: Records with occurs (used with level 3). Level 03 for both 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 D.S. with an Organization set
to L: Working with placement and a Usage set
to D: Output file. Level 02 for group Data Elements or elementary Elements that are not part of a group. Elementary Elements that are part of a group appear but the D.S. Area and Segment levels disappear. Level 01 is to be defined in the -W Lines tab. |
5: COBOL 01 level for Data Elements, DS Areas and Segment levels disappear | Organization set to L:
Working with placementor W: File description in Working
and a Usage set to D: Output file. Level 01 for group Data Elements or elementary Elements that are not part of a group. Elementary elements that are part of a group appear but the D.S. Area and Segment levels disappear. |
You can choose 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 | This is the only authorized value for a Report, a Sequential file or a Sort file Data Structure. |
V: VSAM, UFAS | This is one of the two possible values for an Indexed
file Data Structure This value generates the STATUS KEY IS clause and the corresponding field is declared in the File Status field of the -CD Line Definition section of the '-CD Lines' tab (the part which can be viewed by clicking the More... button). |
I: Indexed | This is 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'
will be generated in three work areas:
|
G: Table description | This value generates the communication area with the Pactables access 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 which corresponds to the communication area between the client and the server (Pacbench C/S Business Components only). |
X: Comment | Data Structure used as a comment, not used for generation. |
2: DB2 segments or VAX/SQL | Generation-Description of a DB2 or VAX/SQL Segment. Only 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 (MICROFOCUS). |
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 | |
A: ADABAS | |
T: 'TOTAL' files | |
O: ORACLE (< V6) | |
C: INTEREL RDBC or RFM | |
R: RDMS | |
4: DB2/400 | |
M: DATACOM DB | |
N: NONSTOP SQL | |
P: ORACLE V6 and V7 | |
9: INFORMIX, SYBASE, INGRES/SQL, or SQL SERVER | |
Z: Data Structure for Socrate/Clio | |
F: Formal for Socrate/Clio |
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 Function) Data Element error check Segment error check User-defined errors |
The USAGE clause of a COBOL numeric variable allows you to indicate the internal representation of its value. Different USAGEs are available depending on the COBOL variants adapted to the material in use.
Value | Meaning |
---|---|
D | DISPLAY (default option). Required for date Data Elements. |
C | COMPUTATIONAL (binary), IBM or equivalent; BINARY, IBM and COBOL II variant. |
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 MICROFOCUS. |
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, since 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 DBD : 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 MICROFOCUS |
Z | In batch mode only: this option, which is only used with an output format, allows for the generation of a BLANK WHEN ZERO clause with the Batch D.S. 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-3IBM 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 VisualAge Pacbase 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 sub-system. |
Values | Comments |
---|---|
U | References a unique key for an DL/1 database. |
M | References a multiple key for an DL/1 database. |
1 to 9 | Secondary index All other values designate a search field. |
Values | Comments |
---|---|
0 to 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. |
These lines are used for documentation purposes. Comments are available with all entities and allow you to write, edit text in relation to the selected instance. This tab allows you to write, modify, move or delete text lines using basic word processing functions.
Value | Comments |
---|---|
* or blank | Standard documentation line. |
A | Alias for the Segment name. |
On a blank-type line, you enter a free comment.
On an A-type line, enter the COBOL Segment name.
Values | Comments |
---|---|
T | Call of a text section. |
* | Line which will not be generated. It is used to insert a comment or an override. |
S | Replacement of an automatic error message. Automatic messages can be replaced by specific messages such as: ’THE ORDER NUMBER IS REQUIRED These messages are indicated on ’S’ type lines assigned to data element call lines (-CE lines tab) in the Segments. |
F | Data Element call |
U | Error message |
C | Comment |
D | Documentary messages. |
Type | Description |
---|---|
D | Column 1:
Column 2: blank Column 3:
Column 4: blank Column 5: Begin the documentary message or Enter the text and paragraph code being called. Two asterisks (**) for the paragraph code is a permitted value, it will call all the paragraphs of the text. |
S | Column 1: ERROR TYPE (2, 3, 4 or 5) Column 2: blank Column 3: ERROR GRAVITY (E, C or W) Column 4: blank Column 5: enter the message beginning here. |
For the Y: Pacbench C/S organization, this field must contain the code of the COBOL COPY clause which represents the communication area of the Pacbench C/S Application Component which 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 may take three 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 | Nom externe |
This field is used to obtain a Data Structure description in a particular area (communication area with DBMS's or LINKAGE SECTION that you must define in the -W Lines tab) or at the beginning of the WORKING-STORAGE SECTION.
This field is reserved for Data Structures whose organization is W: File description in Working, L: Working with placement or D: DL1, IDS and II. It places the I/O area in the WORKING-STORAGE SECTION.
To obtain the description of a Data Structure in the WORKING STORAGE SECTION, you should preferably use the -W Lines tab.
Value | Meaning |
---|---|
00 | The description of the Data Structure is inserted after all the -W lines |
Alphabetic characters | The description of the Data Structure is inserted after
all the -W lines whose COBOL position corresponds to
this value. The description and -W lines are found at the beginning of the WORKING-STORAGE SECTION of the generated Program. These lines are displayed before Data Structures whose organization is W: File description in Working and before those whose DS code in the Program is greater than this alphabetic code. Note: Do
not choose a COBOL position identical to the DS 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 -W lines 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 the following usages: 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 the following usages: 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 the following Types of Code to generate: 4: BULL GCOS7, 5: BULL GCOS8, 0: IBM MVS/ESA OS/390, U: UNYSIS 2200 Series, F: TANDEM, I: DEC/VAX VMS, 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 Elements to be used for control break processing. These Elements are identified as the Sort key composition field for this Data Structure.
When there is a control break processing on one or more Data Structures, two indicators keep track of the status of the records being processed
O is the default value.
1 to 9 levels. Enter the number of Elements (Elementary or Group) on which 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/resultData Structure must be declared as an D: Output file). |
S: Selected | Output file extracted from another file. It differs from the D: Output file usage since 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 occurs indicated on each Segment Definition. The maximum number of selected Segments per 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 file(s).
The generated functions range from 30 to 76. Note: Only
one M: Transaction to be validated or N:
Transaction not to be validatedData Structure is allowed per Program.
|
N: Transaction not to be validated | Input file which can update other files. The generated
functions are: 30, 33, 39, 70 to 76. Note: Only one M: Transaction
to be validated or N: Transaction not to be validatedData
Structure is allowed per Program.
|
E: Transaction with error checking | Output transaction file containing a field identifying
records with errors. The system will generate the field(s) to track the erroneous Elements, erroneous Segments and user-defined errors using the reserved Data Elements ENPR, GRPR and ERUT. . Selected or not, the descriptions of these Elements are generated (using the Data Elements DE-ERR and ER-PRR). |
I: Direct printing | Direct printing (or by SYSOUT in IBM MVS). Upon generation, the lines whose 'Structure Identifier' is 00 in the Report will be ignored. |
J: Indirect printing | Indirect printing to be processed by a spool Program. The fields 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 entered in the Sort key field on the Segment -CE Lines tab.
The order for sorting these key Data Elements may be entered here using the values assigned on the -CE Lines tab in the desired order from major to minor - left to right.
If no explicit entry is made here, Elements coded with value 1 to 9 will be taken as the default.
It must contain a numeric value, which corresponds to the block size, i.e. the size of the physical record. Spaces and zeroes 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 (2 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 fill it in, it is recommended to specify a character string, on 10 characters maximum, in the following format:
You enter here 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.
You must specify the replacement values of the parameters in the form of character strings. Each occurrence of the parameter in the Macro is then replaced by the value entered for this particular Program.
The number of characters used for each parameter value must correspond to the appropriate field length for the element being parameterized. For example, if $1 is being used as a Function code, the value must be two characters long.
The values for the label type correspond to the association between the Data Element and the presentation characteristics for these labels (left-justified...).
Values | Comments |
---|---|
Default value | Defaults to the value specified in the Dialog. |
F: Data Element only | |
L: Data Element with long label, left-justified | The Data Element is preceded by the Data Element label, left-justified, on 36 positions. |
M: Data Element with long label, right-justified | The Data Element is preceded by the Data Element label, right-justified, on 36 positions. |
N: Data Element with long label, left-justified, trimmed right | The Data Element is preceded by the Data Element label, left-justified with suppression of blanks on the right. |
R: Data Element with long relational label, left-justified | The Data Element is preceded by the relational label, left-justified on 18 positions. |
S: Data Element with short label, left-justified | The Data Element is preceded by the short label, left-justified, on 18 position |
T: Data Element with short label, right-justified | The Data Element is preceded by the short label, right-justified, on 18 position |
U: Data Element with short label, left-justified, trimmed right | The Data Element is preceded by the short label, left-justified, with suppression of blanks on the right. |
1: Data Element topped by a single line column label | |
2: Data Element topped by 2–line column label | |
3: Data Element topped by 3–line column label |
If the line and column numbers are both equal to zero, the Data Element is automatically positioned on 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 the line and column numbers are both equal to zero, the Data Element is automatically positioned on the next tabulation point available.
Segment belonging to the screen-top.
Segment belonging to the repetitive section.
Segment belonging to the screen-bottom.
the logical access is generated automatically, according to the use of the Segment.
Logical accesses to be written in Structured Code.
Segment accesses not described.
Header | Header |
---|---|
Blank: no control break. | |
C: display break | This provides an indication of the logical end-of-file
for control break processing in the repetitive section . Control break processing
will take place under either of these conditions:
|
E: display break (SQL) | Display control break, causes the generation of an equal condition in the 'WHERE' clause of the SQL 'DECLARE CURSOR' statement (and not >=, which is generated otherwise). Allows optimization of the use of 'CURSORs' in the repetitive category. |
Options | Description |
---|---|
N | Not used. No access statement will be generated for this Segment in the validation and update processing. |
L | Read. A simple read command is generated for the Segment. |
E | Existence validation to execute. A read command with the setting of an error code is generated (if it is not found). |
M | Updated Segment (modification only). |
X | Updated Segment (creation and modification only). |
T | Updated Segment (creation, modification and deletion). In the last three cases, the existence validations and the update statements corresponding to the chosen 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 Segments accesses conditioned by a previous Segment access, update commands for deletions will not be generated. |
U | User-defined logical accesses. |
Entered on the '00' line, the '*SSA' value inhibits the generation of the qualified SSA corresponding to the Segment in the PCB. The Access key source field must be entered with the code of the Data Element used as the display key. The K-.... field is generated with the access key indicated in the Primary access key field (Data element). The key will be filled in automatically in functions F25, F40, and F60.
The SSA of the processed Segment is filled in from the '-CS' lines whose key code has not been found in the hierarchical path
This specification is not available with the HLPI option (the key is directly coded in the 'WHERE' parameter).
In this pane, you select a Data element or you enter the name of a new Data Element (not defined in the Dictionary) that will be used as the primary access key to the Segment. It is used to generate the 'RECORD KEY' clause. The Data Element specified here is considered as a Group Data Element except for SQL organizations where it is considered as an Elementary Data Element.
If a group Data Element is used, and different values are given to the individual members of that group, the codes of those elementary Data Elements are named here. Key Data Elements are not updated in a 'SQL UPDATE' order.
For a Table (’G’ organization), selection of a sub-system is executed by indicating the value ’NUSSY’ in this field. The system generates the associated key (G-ddss-NUSSY).
In DL/1, the Data Element can belong to all SSA’s that permit access to the Segment in the PCB indicated in the external name (code of the PCB).
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 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 can not contain more than 10 key Data Elements.
Key Data Elements are not updated in a 'SQL UPDATE' order.