Previous Topic: Application Components, VLS, and the DatadictionaryNext Topic: Compilation and VLS Object Modules

Problem Determination › CA Ideal Internals › CA Ideal Modules › Storing Application Components

Storing Application Components

Entries in the Datadictionary and VLS members for CA Ideal components are created at various times during the application development process.

The first CA Ideal entity‑occurrences are stored in the Datadictionary when CA Ideal is installed. At that time, the first CA Ideal system and user are created, the appropriate entity‑occurrences are added to the Datadictionary, the VLS source library, object library, and panel libraries are specified, and the appropriate relationships are created on the Datadictionary.

When additional users and systems are defined, CA Ideal adds other entries to the Datadictionary.

The Database Administrator defines modeled dataviews in the dictionary. In CA Ideal, the CATALOG DVW command reads the dictionary tables and creates an object module in the IDDVW VLS library.

Unmodeled Dataviews

Defines in CA Ideal and added to the dataview source library and the Datadictionary. The CATALOG DVW command accesses the source library and the dictionary tables and creates an object module in the IDDVW VLS library. You can create unmodeled dataviews for sequential files and VSAM files.

CA Ideal data members are stored in the VLS library IDDAT. They are not modeled in the Datadictionary.

Panels and Reports

Are modeled in the Datadictionary and stored as VLS members. A dictionary entity‑occurrence is created when the panel or report identification is entered. A single VLS member is added to the source library when the report parameter, header, detail, and column sections are created. This member contains all of these report components. A VLS member is added to the panel library for the panel layout, summary data, extended field definitions, input edit and validation rules, output edit rules, and facsimile. This member contains all of these panel components.

Programs

Are modeled in the Datadictionary and an entity‑occurrence is created in the dictionary when the program identification is entered. Relationship occurrences are added when the program resource table is entered. Separate VLS members are added to the source library for each program component. That is, members are added for the program parameter data, working data, and procedure. Each member is added when the corresponding component is first edited.