To access this process:
See this process in the Command Table.
This process is used to check the legend definition file prior to running ATTSET.
ATTCHK copies values from previous records into blank fields, and reports any inconsistencies in the file.
A hierarchy is verified in each legend specification found in the file :-
Each LEGEND can contain one or more DATFLD entries
Each DATFLD can contain one or more ranges and/or patterns
Each range/pattern can have one or more ATTRIB entries.
The values of fields at each key change are propagated down until the next non-blank value in a column. One of the combinations below is expected for each DATFIELD/ATTRIB entry :-
DATMIN (discrete value)
DATMIN, DATMAX (data range)
DATEXP (data pattern)
The validation of the file reports :-
Missing values on a record
Overlapping, missing or over-specified ranges
Alphanumeric range fields for which a blank is intentionally to be specified should have blanks included within single or double quotes within the legend file. A blank field will be output.
Name |
Description |
I/O Status |
Required |
Type |
IN |
Overwritten |
Yes |
Undefined |
Input legend file. The following standard field names are recognized but not all need be present in the file :- LEGEND A8 Legend key. DATFIELD A8 Data field in the input file. DATMIN A12 Minimum value. DATMAX A12 Maximum value. DATEXP A40 Match (regular) expression. ATTFIELD A8 Attribute field. ATTVALUE A12 Attribute field value. Alternate field names can be supplied to the process by specification through the symbolic field names eg DATMIN(MIN). |
Name |
I/O Status |
Required |
Type |
Description |
OUT |
Output |
No |
Undefined |
Output legend file. Can be the same as the input file. |
ERROR |
Output |
No |
Undefined |
Optional output error file for invalid records. |
Related topics and activities