This dialog box is dedicated to transaction files. Transaction files are validated and update permanent files or databases. For each data element called in the Segment, there is a presence, class and value validation.
Values | Comments |
---|---|
None | |
F: Optional | Default value. |
O: Required | Required. Generation of a level ’E’ (transaction refused) in standard error messages. |
P: Required (C error) | Required. Generation of a level ’C’ (data element refused) in standard error messages. |
I: Forbidden | Not allowed. For Relational Databases, it indicates the presence of a Column in a Table. |
Values | Comments |
---|---|
None (recommended) | Only the control automatically generated by the class is requested. |
A: Alphabetic | For an alphanumeric class, numeric and special characters will be rejected. This control is the same as that automatically generated if the "Pure alphabetic" box is checked. |
L: Lowercase Alphabetic | For an alphanumeric class, only lowercase letters will be accepted. |
U: Uppercase Alphabetic | For an alphanumeric class, only uppercase letters will be accepted. |
9: Numeric | Numeric only. For an alphanumeric class, alphabetic and special characters will be rejected. |
B: Numeric after replacing leading blanks with zeroes | For a numeric class, leading blanks will be replaced by zeroes. |
Z: Numeric after replacing all blanks with zeroes | For a numeric class, all blanks will be replaced by zeroes. |
Value | Comments |
---|---|
’ ’ | Must not appear on the first line for a data element. |
E | AND |
O | OR |
Header | Header |
---|---|
N | Negation (’NOT’ is generated). |
Blank | No negation. |
Type | Value | Comments |
---|---|---|
Contents Validation | = | Equal to the value entered in the Values/Sub-function field. |
> | Greater than the value entered (as above). | |
< | Less than the value entered (as above). | |
T | Must be in the table indicated in the Update target field. Content validations entered following a ’T’ type validation are not executed. | |
E | Must have one of the values defined on the Description screen (-D) for this data element. | |
Validation by PERFORM | P | Validation by PERFORM of a sub-function defined
by the user. There may be only one validation by PERFORM per data element
called in a segment. The following operations are executed:
|
Value | Comments |
---|---|
Blank | Direct update of the data element in the Update target field, contingent upon valid presence of the data element. This type of update can also be used with with ’contents Validations″ other than ’T’. |
+ | Update by addition, contingent upon valid presence. |
- | Update by subtraction, contingent upon valid presence. |
M | Update by unconditional substitution (MOVE). Updating is done regardless of the validation result. This type of update can be used with group data elements. |
Value | Comments |
---|---|
V | Initial value: generates a value using the literal entered in the Values/sub-function code field. It is the default value defined on the element description if the Values/sub-function code field is not used and if the element description has a D-type line The Record type field on the Call of Data Structures (-CD) tab must allow for the generation of VALUES clauses. |
W | Same as ’V’, but the literal can be continued into the UPDATE TARGET field. The two fields together would be considered as one. |
Context | Value | Comments |
---|---|---|
DL/1 GROUP KEY DATA ELEMENTS | M | To indicate a group key data element associated with the code entered (after ’A*’) in the Update target field. |
PACTABLES FUNCTIONS | S | This indicates that the data element belongs to one or or more sub-schemas. The sub-schemas are entered in the VALUES / SUB-FUNCTION CODE field. If the data element belongs to a group element, you must enter a sub-schema number on the group element line. |
SQL RELATIONAL DBD FUNCTION | The VALUE / SUBFUNCTION CODE field is used to indicate the sub-schema(s) a Column belongs to. |
In this example, the Data Element ’DELCO’ belongs to sub-schemas 1,3,4 and 5.
Header | Header |
---|---|
Data Structure code in the Program of a permanent file. | The filed Usage of Data Structure must be set to P on the Call of Data Structures to be updated, or of a table Data Structure with field Type (validation, update, values) set to T. |
Data Structure code | The data structure code for the target of an update. |
Working Data Structure code | Working Data Structure code for the Data Element communication area in a ’PERFORM’ (Type (validation, update, values) set to P). |
** | Associated with a repetitions number, in order to generate a variable number of OCCURs, using a counter contained in an element. This counter is referenced by the Segment and Data Element codes which are indicated in the Update target field / second and last parts. |
Generation of an OCCURS DEPENDING ONclause. Transfers of the counter between input, WORKING and output areas are carried out automatically by VA Pacbase if this counter belongs to the common part. | |
R* | To redefine a Data Element within a Segment. The Data
Element named in the Data Element code field will refine
the first Data Element that precedes it which is generated at the same COBOL
level. Example: ELEM. GR GRPFLD 2 ELEM1
ELEM2 R* <--- or NEWVAL R* <---
If R* is entered opposite ELEM2, ELEM2 will redefine ELEM1. If R* is entered opposite NEWVAL, NEWVAL will redefine GRPFLD. |
A* | To identify the external name of a DL/1 key or search field. The external name (8 characters) is entered in the Update target second and last parts and applies to the Data Element entered in the Data Element code field on this line. |
SQL Relational Databases | |
The relational label of a Column can be identified in this field; the value A must be left flushed and followed by the external name of the Column. | |
Header | Header |
---|---|
Segment code | Default value. |
continuation of a literal. | |
First two characters of the DL/1 external name. |