The design entities and their editors in the Software Development Kit
Each entity covers a specific aspect of the application design. If you double-click an entity instance in the Design Explorer view, you view this instance in its dedicated editor.
- The Skeleton entity
A Skeleton must be defined to manage COBOL code or other types of source codes. - The COBOL Program and COBOL Copybook entities
These entities are dedicated to the management of the COBOL code. When their instances are created, they must reference a Skeleton that has a COBOL type. This skeleton contains the basic structure of their COBOL code. After you generate the instances, you can modify their generated code. If you generate again, your modifications are kept. - The Source Code entity
With this entity, you can generate a source code different from the COBOL code. Its instances must reference a generic Skeleton (ALL type) that contains the basic structure of their code. You can generate a Source Code. After the generation, you can modify the generated code. - The Static Micropattern entity
With this entity, you insert code lines by calling the Software Development Kit dedicated micropattern in the code of a COBOL Program, COBOL Copybook, or Source Code. This particular micropattern is the RPPMPF Static Micropattern. When the calling instance is generated again, the Static Micropattern call is replaced with the corresponding code lines. - The Data entity
The purpose of this entity is to identify and describe the information that is used in the COBOL code of the applications. A Data can be viewed in the Pacbase facet as a Data Element. However, the formats that are indicated in the Pacbase facet are not recognized in the COBOL facet. - The Data Aggregate entity
This entity groups internal descriptions and Data or Data Aggregates that are already defined. A Data Aggregate can be seen in the Pacbase as a Segment. - The Data Structure entity
This entity is displayed in a read-only mode to give access to the Pacbase Data Structures when a Pacbase repository is used. It corresponds to groups of Data Aggregates. - Meta Entities
Meta Entities and Meta Entity Types can be used to create customized concepts that the metamodel does not manage in a standard manner. Meta Entity Types extend all the model entities that are managed by Rational® Programming Patterns. When a Meta Entity instance is defined and described, it is managed as any other instance. User Entities are instances of a Meta Entity.
Feedback