|
|
|
The CA-Datamacs/II generated fields are illustrated below.
M A P 01 table-name. nnn00010
LEV #* VERSION=status/version nnn00020
04 DATACOM-NAME-xxx PIC X(4). nnn00030
04 DATACOM-DATA-OFFSET-xxx PIC 9(7) COMP-3. nnn00040
04 DATACOM-DM-FILLER-xxx PIC 9(4). nnn00050
04 first-user-field nnn00060
The xxx's after each of the CA-Datamacs/II generated fields are replaced by the table DATACOM-NAME. In the sequence number, nnn is replaced by the tables DATACOM-ID. Fields composing any attached epilog are never shown.
CA-Datamacs/II defines a path to the desired information within Datadictionary. The path for table retrieval would start with the DATABASE occurrence and retrieve only those table occurrences defined to the database name and status/version specified on the CA -Datamacs/IICA-Datamacs/II DATACOM statement. The same is applicable to keys, elements, and fields.
If the desired element is in a different status/version, the status/version on the DATACOM statement would have to be changed. This technique helps to insure that the proper copybook is generated for the database version being accessed.
When a DATAVIEW is specified, the status/version on the CA-Datamacs/II COPY TABLE statement would also be used. A test is done to insure that the DATAVIEW chosen is related to the database specified on the DATACOM statement.
The success of retrieving various entity occurrences depends upon the presence or absence of a LOC2 on the occurrence. The system override code would have to be provided to allow access to locked occurrences.
If certain information in a particular locked entity occurrence is required, but the system override code is not provided, CA-Datamacs/II will issue an error message and terminate after phase I processing, even though the other entity occurrences are not locked. The error message will not give an indication that a locked entity was encountered, because Datadictionary is designed not to reveal the presence of a lock.
For example, one of the tasks CA-Datamacs/II performs is to retrieve all of the element names related to the database status/version so that, if the user chooses to enter the individual element names on the COPY TABLE statement, they can be checked for accuracy. CA -Datamacs/IICA-Datamacs/II will define a path, using the Datadictionary Service Facility, of database to area, to table/file, to record, to element entities. In this element processing, we skip the area and record entities. At this time there is nothing in those entities we need. However, in this example, if the table/file occurrence was locked, but not the element occurrences, CA-Datamacs/II would still not retrieve the element occurrences until the override code was provided, as certain attributes from the table/file occurrence are needed at the same time.
| Copyright © 2009 CA. All rights reserved. | Tell Technical Publications how we can improve this information |