The type of values you enter in this tab depend on the
use context of the Segment. The tab contains fields which are specific
to '00' or other Segment you have defined.
Depending on the segment type, the information required
in the definition are different. For a non-'00' segment, you indicate
the action code value and presence check options. For
a '00' segment, you enter a value in the action code field
which is quite different and you need to indicate the data element
code which identifies the transaction type.
- Table size
- This field is common to the '00' and non-'00' Segments. This is
the amount of space reserved for a Segment in memory, the length is
4 numeric characters maximum :
- the Segment's Data Structure is used in a Program as a table.
By default, the default value at generation time is 100,
- the type of record description incorporates the number of OCCURS
indicated here.
Note: for both cases, see the Program editor's
online help.
non-'00' Segments
- Structure code value
Note: On non-'00' segment definition only.
Enter the value
of the structure code as a COBOL literal. This information is required
when a variable file is used in a Segment.
- Action code value
Note: On non'00' segment definition only.
Enter the data element code for the element used to identify the
transaction type. The System will generate validation logic appropriate
for creation, modification, deletion and implicit action codes, as
well as user-defined transaction types. Six values are associated
with this code. Validation and updates are automatic for the six values.
- Presence check
Note: On non '00' segment definition only.
Enter the presence
specifications for the individual segment. - Creation
- Enter the presence specifications for the individual segment.
You specify whether the presence of the specific Segment is required
when a 'create' action is carried out.
Table 1. CreationValues |
Meaning |
None |
No specification. |
F: optional |
Default value. The segment is optional on a
'create' action. |
O: Obligatory |
The segment must be present on a 'create' |
I: invalid |
The segment must not be present on a 'create' |
- Modification
- Enter the presence specifications for the individual segment.
You specify whether the presence of the specific Segment is required
when a 'modify' action is carried out.
Table 2. ModificationValues |
Meaning |
None |
No specification. |
F: optional |
Default value. The segment is optional on a
'modify' action. |
O: Obligatory |
The segment must be present on a 'modify' action. |
I: invalid |
The segment must not be present on a 'modify'
action. |
- Deletion
- Enter the presence specifications for the individual segment.
You specify whether the presence of the specific Segment is required
when a 'delete' action is carried out.
Table 3. Values |
Meaning |
None |
No specification. |
F: optional |
Default value. The segment is optional on a
'delete' action. |
O: Obligatory |
The segment must be present on a 'delete' action. |
I: invalid |
The segment must not be present on a 'delete'
action. |
- Type 4
- Type 5
- Type 6
- Enter the presence specifications for the individual segment.
You specify whether the presence of the specific Segment is required
when a type 4, 5 or 6 action is carried out.
Table 4. Type 4, type 5, type 6Values |
Meaning |
None |
No specification. |
F: optional |
Default value. The segment is optional on a
type 4, 5 or 6 action. |
O: Obligatory |
The segment must be present on a type 4, 5 or
6 action. |
I: invalid |
The segment must not be present on a type 4,
5 or 6 action. |
'00' Segments
- Structure code
Note: On '00' segments definition.
Enter the code of the
data element used to identify the type of record (six characters maximum).
- Action code
Note: On '00' segments definition. The action code and the values
must be entered on only one segment of the data structure.
Enter
the data element code for the element used to identify the transaction
type. The System will generate validation logic appropriate for creation,
modification, deletion and implicit action codes, as well as user-defined
transaction types. Six values are associated with this code. Validation
and updates are automatic for the six values. If there is no action
code, this field remains blank, and the transaction type is a modification.
In this case, presence specifications for the segment are entered
in the Type 4 field.- Creation
- Enter the value that stands for 'create' for this file: Example:
'ADD'.
Note: for alphabetic characters use quotes.
- Modification
- Enter the value that stands for 'modify' for this file. Example:
'CHG'.
Note: for alphabetic characters use quotes.
- Deletion
- Enter the value that stands for 'delete' for this file. Example:
'DEL'.
Note: for alphabetic characters use quotes.
- Type 4
- Enter the value that stands for implicit action codes - (creates
or modifications).
Note: for alphabetic characters use quotes.
- Type 5
- Enter the value that stands for this user-defined action. Note:
for alphabetic characters use quotes.
Note: for alphabetic characters
use quotes.
- Type 6
- Enter the value that stands for this user-defined action. Note:
for alphabetic characters use quotes.
Note: for alphabetic characters
use quotes.