Writer instructions

Purpose

Use this page to display a banner announcement on each page of the space. Create the Space announcements page in the master space, outside of the Home branch.

You can version the Space announcements page to enable different banners to be published into different target spaces, however, the banner that is displayed in the versioned (master) space itself only displays the most recently-published banner.  If you find errors in the banner area of your versioned space and you are sure the Space announcements page is set up correctly, try publishing the page to the same space.

For more information, see Space-announcements-banners.

Removing

When an announcement is no longer needed, remove the BMC Space Banner macro.

Translation

Localized spaces using the L10n Viewport theme must change the name of this page to Space announcements l10n.  See Configuring-the-Scroll-ViewPort-theme-for-translated-spaces.

Usage

Choose one or none of the following BMC Space Banner macros.

If your space requires another kind of announcement, you can use this page in coordination with your team lead and editors.

When should I use a space announcement banner?

Use the space organization announcement after you change the content from a book-like organization (such as User Manual, Configuration Manual, and Administration Guide) to the product model.

Use the latest version announcement to push traffic to later versions. You do not need to add this to every previous version, but if you have a specific reason that you want users to be aware—for example, Google searches show content for an obsolete version—use the banner to help users find a relevant version.

When an announcement is no longer needed, remove the BMC Space Banner macro.

Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Building column/field relationships

File-AID/RDX enables you to modify the relationship file by modifying existing application relationships or creating new ones. To modify or create application relationships, you modify or create column/field relationships on the Relationships screen. An application relationship can consist of one or more column/field mappings.

The parent and dependent portions of the Relationships screen comprise two lists. These lists contain names, data types, and lengths of columns or fields from the parent and dependent objects specified in the preceding screen. Use these lists to build the relationships at the column/field level.

Important

To build application relationships to be used with existing Db2 relationships, you must be connected to the subsystem for which the existing relationships are defined. You can specify a subsystem in the SSID field on the Add Relationships Screen — Db2 to Db2 screen.

To build column/field relationships:

  1. Decide which parent and dependent columns or fields you want to be related. It is likely that these will be columns or fields that your application recognizes as containing data values that are used as an index into the corresponding object in the relationship.

  2. Enter the number from the dependent NMBR column that corresponds to the dependent column/field you chose in step 1 in the parent CMD column next to the name of the parent column/field you chose in step 1. See the following figure.
    See Column/Field Types Mapping to ensure which data types can be paired to establish an application relation. For other pairings File-AID/RDX displays an error message and will not establish the relationship.Relationships Screen — Creating a DB2 to MVS Relationship

    image2021-10-22_15-15-10.png

  3. Press Enter.
    If one or both parent and dependent fields in an MVS file contain subscripts, File-AID/RDX will need to know which occurrence of subscript to use for the relationship. In that case, File-AID/RDX continues with Specify MVS Field Subscripts.

    When partial column mapping is allowed between the parent and dependent columns/fields, the Extended Column Relationship Definition pop-up window is displayed as shown in the following figure. For more information about extended column relationships, see Extended Column Relationship Definition.

    Extended Column Relationship Definition Window

    image2021-10-22_15-15-34.png

    If partial column mapping is not applicable for the selected parent to dependent pairing the relationship is established immediately. File-AID/RDX positions the name of the parent column/field of the relationship you just created to the end of the list of established column relationships as shown in the following figure. Note that the new column relationship is located above the dashed “End of Related Columns” line. In addition, the Mapped Fields value is filled with the dependent column/field number that appeared in the NMBR column next to the dependent column/field as well as any applicable extended column information in parentheses, followed by the dependent column/field name.

    Relationships Screen — New DB2 Column to MVS Field Relationship Established

     File-AID/RDX  -------  Column/Field Relationships  --------------------------
     Command ===>                                                  SCROLL ===> CSR
     Primary Command: CONDitional relationships, SUGgest Relationships
     Line Commands:   Field Number  to Define Relationship  D = Delete Relationship

     Parent:     DB2-LOCATION.TSOID01.CUSTOMER_TABLE
     Dependent:  MVS-TSOID01.FARDX2.SAMP.SALEHIST
     CMD  Parent Columns                  Type(Length) Mapped Fields
     ---- ------------------------------- ------------ -----------------------------
     ____ CUSTOMER_NUMBER                 CHAR(6)      1/SH-CUST-NO
          - - - - - - - - - End of Related Columns - - - - - - - - -
     ____ CUSTOMER_NUMBER                 CHAR(6)
     ____ COMPANY_NAME                    CHAR(30)
     ____ ADDRESS                         CHAR(30)
     ____ CITY                            CHAR(25)
     ____ STATE                           CHAR(2)
     ____ ZIP_CODE                        CHAR(9)
     NMBR Dependent fields                Type(Length)
     ---- ------------------------------- ------------
        1 SH-CUST-NO                      CHAR(6)
        2 SH-ORD-NO                       CHAR(6)
        3 SH-ORD_TYPE                     CHAR(8)
        4 SH-DATE-SHIP                    CHAR(8)
        5 SH-SHIP-CUST-NO                 CHAR(6)
  4. Repeat steps 1-3 for all columns/fields that you want to include in the application relationship for the pair of objects. 

When you exit from this screen, File-AID/RDX writes a new or modified application relationship to the relationship file. File-AID/RDX redisplays the Application Relationship Detail screen, where the completed action is indicated in the Status column with the “Added” or “Modified” message.

Related topics

Relationships-screen

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*