Sections tab

This tab displays the Text content, which is structured in sections. The Text lines correspond to a word-wrap typing mode. From this tab, you can create reference links between the Text and instances of other entities.

Note: The first time you open the editor of a Text that was migrated from Pacbase in a version older than version 9.1.2, a message box is displayed:
  • If you click OK, the Text is transformed and saved in the new version of the model. The text is displayed in a read/write mode. An output change is present in the Pending Changes view.
  • If you click Cancel or the closing icon, the Text is transformed but is not saved in the new version of the model. The Text is then displayed in a read-only mode.
The Sections tab is constituted of the following elements:
  • The tree that shows the Text section codes. If you click a section code, the Sections area, which displays the section content, automatically opens. If you right-click a section code, a contextual menu contains items to add or remove a section, or to copy and paste a section with its content.
  • Buttons that you can use to add or remove a section, or to move a section in the tree.
  • The Sections area that opens when you click a section code in the tree or request the addition of a section. This area contains the constituting lines of the section.
The section content, which is displayed in the Sections area, contains three columns. You must use your cursor to move from one column to another:
  • The first column contains the line types, on one character.

    Using certain line types, you can specify entity calls to create reference links (super reference and subreference) between the Text and instances of other entities. You add these calls from a section or section part. An I or a B type line indicates the first line that refers to the entity instance. A J or E type line indicates the last line that refers to the entity instance. If it is not specified, all the following lines refer to the entity instance. You enter the referenced instance in the description column.

    The other line types (L, K, -, or 1 to 9 for example) are migrated from Pacbase but are not effective in Rational Programming Patterns. They are not used by the publishing or when the Text is used in a Volume.

  • The second column contains the section description.

    It contains the section code and content.

    The section code must be on 2 characters. It is recommended to use letters or digits only.

    You enter the description content in a word-wrap typing mode. You can add or remove characters inside the existing content. You can also copy and paste lines or characters.

    To create a reference link to another instance, you must enter @ENTINSTANCE, where ENT is the entity type and INSTANCE is the entity instance. The following entity types can be entered:
    • DBD for Database Blocks
    • DST for Data Structures
    • DEL for Data Elements
    • OST for Dialogs
    • OSV for Server Dialogs
    • SCR for Screens
    • SRV for Servers
    • PGM for Programs
    • MSP for Macros
    • RPT for Reports
    • SEG for Segments
    • TXT for Texts
    • IAD for Input Aids
    • LIB for Libraries
    • MET for Meta Entities
    • VOL for Volumes
    • USE for User Entities
      You must enter @USEUSER.META, where USER is the User Entity and META is the Meta Entity that the User Entity belongs to.
    Example: To create a link with a Macro that is named AASQUEL, you must enter @MSPAASQUEL.

    If the instance exists, it is displayed as a link that you can double-click to open the instance editor. If the instance does not exist, a message box indicates that the link is not resolved.

  • The third column can contain links to Data Elements because a Text that describes an application often refers to individual Data Elements.

    A subreference link is then automatically set from the Text to the Data Element.

    A Data Element cannot be referenced on the lines whose type is I, J, B, E, or Y.

    To create a subreference link to a Data Element, you must enter @DELINSTANCE, where DEL is the Data Element entity and INSTANCE is the Data Element instance.

    If the instance exists, it is displayed as a link that you can double-click to open the instance editor. If the instance does not exist, a message box indicates that the link is not resolved.


Feedback