CA Ideal™ for CA Datacom® imposes certain rules on dataviews used for sequential files. The CA Ideal™ for CA Datacom® CATALOG command enforces the rules.
A dataview can be successfully cataloged in TEST or PROD status. A dataview that is cataloged in TEST status has all elements in TEST status and all version numbers of the elements are the same as the dataview version. A dataview that is cataloged in PROD status has all elements in PROD status. The elements in PROD status do not have to have the same version number as the dataview. The dataview must be related to one element. The element must be related to a single record, and the record to a file.
For a dataview that CA Ideal™ for CA Datacom® accesses, the only DATAVIEW attribute whose specified value is used is UPDATE-INTENT. You can specify Y for updateable or N for non-updateable. (U for updateable is also supported for compatibility with earlier releases.) CA Ideal™ for CA Datacom® interprets any other value as N, non-updateable. If the DATABASE entity-occurrence name is DATA-DICT or UNIVERSAL, CA Ideal™ for CA Datacom® assumes a value of N, non-updateable.
The attributes DBMS-USED and ACCESS-METHOD for the dataview attribute are updated with values CA Ideal™ for CA Datacom® supplies when the dataview is cataloged.
For CA Ideal™ for CA Datacom® to access a sequential dataview, FILE attributes must be defined as follows:
This information is summarized in the following table.
|MAX-RECORD-SIZE||Actual rec size||Actual rec size|
|MAX-BLOCK-SIZE||See Creating Dataviews for Sequential Files||See Creating Dataviews for Sequential Files|
|DEVICE||See Creating Dataviews for Sequential Files||TAPE|PRT|READER, PUNCH|2314|3330, 3330II|3340|3350, |3375|
DISK - DLBL Name
SLTAPE - TLBL Name
Other - any identifier
|LABEL||See Creating Dataviews for Sequential Files||Y|N (DEVICE=TAPE only)|
For a sequential file dataview, the MONITOR-NAME attribute of the FILE entity-occurrence must contain a logical data set identifier. (The term MONITOR-NAME indicates that this is the logical name by which the file is known to the host monitor.) In batch, the host monitor is actually the host operating system. In a given run, each dataview can have a unique MONITOR-NAME relating each dataview to a separate physical data set. Or two (or more) dataviews can have the same MONITOR-NAME value, which causes the two dataviews to share the same physical dataset (for output files, these results in interleaved output).
All runs in a CICS partition that use the same sequential dataview for output write interleaved records to the same physical file. In addition, MONITOR-NAME connects the dataview to the host environment in the following ways:
For a sequential dataview, there can be only one element. It must explicitly include all the fields in the record. It is possible to accidentally violate this rule by inserting a field through DEFINE FILE, but forgetting to include the field in the appropriate DEFINE or MODIFY element.
The maximum number of nested levels of groups and fields in a dataview is 15. Since the dataview itself is the outermost level (level 1), the highest level number allowed is 16. Since the dictionary assigns level 1 to all columns with a PARENT of START, the level numbers that CA Ideal™ for CA Datacom® assigns is always at least one greater than the level numbers assigned by the dictionary.
CA Ideal™ for CA Datacom® supports a maximum of three nested levels of occurring fields (that is, tables of up to three dimensions are supported).
Compound fields (group fields) should not have initial values. If they do, the value is ignored and a warning message issued.
CA Ideal™ for CA Datacom® supports the following data types:
CA Ideal™ for CA Datacom® converts all other unknown data types to alphanumeric and issues a warning message.
CA Ideal™ for CA Datacom® supports numeric fields up to the equivalent of 31 decimal (base 10) digits (for zoned or packed decimal) and up to the equivalent of 9 decimal (base 10) digits (full word or half word binary) for binary fields. CA Ideal™ for CA Datacom® supports only half word (2 bytes) and full word (4 bytes) binary fields. You can define binary fields of other than 2 or 4 bytes (including data types 2, 4, and 8), but CA Ideal™ for CA Datacom® treats them as alphanumeric fields (with a warning message) and the user must call a non-CA Ideal™ for CA Datacom® subprogram to handle them. CA Ideal™ for CA Datacom® does not support floating point items of any precision.
CA Ideal™ for CA Datacom® ignores FIELD occurrences with class="I" (INDEXED BY). The BLANK-WHEN-ZERO attribute is also ignored. If either the LOW-RANGE or HIGH-RANGE attribute is used with a class="V" FIELD, a warning message occurs.
The REDEFINES attribute has the following values:
You can specify any valid COBOL edit pattern (except Sterling currency symbols) for a field in the dictionary (attribute EDIT-PATTERN). It is used in CA Ideal™ for CA Datacom® reports unless overridden by RDF; see Generating Reports. PDF also uses the edit pattern specified in the dictionary for dynamically generated panel fields.
You can specify field column headings for fields in the dictionary (attributes HEADING-1 and HEADING-2). However, headings longer than 20 characters are truncated to 20 characters in the CA Ideal™ for CA Datacom® cataloged dataview. PDF uses the field column headings specified in the dictionary for dynamically generated panel fields. They are also used in CA Ideal™ for CA Datacom® reports unless overridden by RDF.
You cannot use a PDL-reserved word as the name of a dataview (see PDL Reserved Words). You can use reserved words for field names; however, qualification of such field names with the dataview name is required. For example, assume there is a dataview called SHIPMENT with elements containing fields called TO and FROM. It is valid for a PDL procedure to have statements:
MOVE SHIPMENT.TO TO LOCATION
SUBTRACT SHIPMENT.FROM FROM AMOUNT
However, the following command is ambiguous and causes a program compilation error.
MOVE TO TO LOCATION
For names of fields, CA Ideal™ for CA Datacom® uses the 32-character field entity-occurrence name, not the 30-character compiler name. Field names in CA Ideal™ for CA Datacom® must be unique in the dataview. This occurs automatically since all elements must belong to one record and the dictionary requires field names to be unique in the record name.
CA Ideal™ for CA Datacom® supports one unique value for each condition name (class V field in the dictionary). Lists or ranges of values are not supported.
CA Ideal™ for CA Datacom® supports the following figurative constants as values in the dictionary:
The VALUE attribute for a condition-name (class V field in the dictionary) cannot be blank. A value of all spaces can only be represented by the figurative constants SPACE or SPACES.
CA Ideal™ for CA Datacom® recognizes the following considerations for optional FIELD attributes:
HEADING-1 and HEADING-2 One or two literals (without quotes) used as the default column headings for the CA Ideal™ for CA Datacom® Report Definition Facility and for dynamic field definition using the CA Ideal™ for CA Datacom® Panel Definition Facility. For example, if ACCOUNT is specified as the value for HEADING-1 and NUMBER is specified as the value for HEADING-2, the column header appears as follows: