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.

Specify MVS field subscripts


The Specify MVS Field Subscripts pop-up window shown in the following figure is displayed when you attempt to map two fields where one or both fields contain an occurrence of subscript. You then specify the bounds of the array for each subscript. File-AID/RDX supports a maximum occurrence of a three dimensional array.

Specify MVS Field Subscripts for Parent Field

image2021-10-22_15-36-2.png

This window appears only if the selected parent field contains subscripts. Use it to specify the desired value for up to three subscripts, where applicable.

Parent

Displays the name of the parent file.

Field Name

Displays the name of the parent field to be mapped.

Data Type

Displays the type of data contained in the field. The length, in parentheses, follows the data type.

Subscript 1

Specify the starting position of substring 1 in the parent field that will comprise the column/field relationship.

Subscript 2

Specify the starting position of substring 2 in the parent field that will comprise the column/field relationship.

Subscript 3

Specify the starting position of substring 3 in the parent field that will comprise the column/field relationship.

After you press Enter, you continue either with the Dependent Field Subscripts window (see the following figure), if the dependent field contains subscripts, or the Extended Field Relationship Definition window (Extended Field Relationship Definition with Field Subscripts Defined), if the parent and dependent field types qualify for Extended Field Relationship Definition, or return directly to the Field/Column Relationship screen (Extended Field Relationship with Defined Subscripted Relationship) when the relationship definition is completed.

Specify MVS Field Subscripts for Dependent Field

image2021-10-22_15-36-25.png

Use this window to specify the desired value for up to three subscripts, if applicable, for the dependent field.

Dependent

Displays the name of the dependent file.

Field Name

Displays the name of the dependent field to be mapped.

Data Type

Displays the type of data contained in the field. The length, in parentheses, follows the data type.

Subscript 1

Specify the starting position of substring 1 in the parent or dependent field that will comprise the column/field relationship.

Subscript 2

Specify the starting position of substring 2 in the parent or dependent field that will comprise the column/field relationship.

Subscript 3

Specify the starting position of substring 3 in the parent or dependent field that will comprise the column/field relationship.

After you press Enter, you continue either with the Extended Field Relationship Definition window (see the following figure), if the parent and dependent field types qualify for Extended Field Relationship Definition, or return directly to the Field/Column Relationship screen (Extended Field Relationship with Defined Subscripted Relationship) when the relationship definition is completed.

Extended Field Relationship Definition with Field Subscripts Defined

image2021-10-22_15-37-7.png

See Extended Column Relationship Definition for a description of the fields. Note that the Type(Length) field now also includes the array size and maximum length of the related elements.

Upon completion, File-AID/RDX displays the defined relationship in the Field Relationships screen as shown in the following figure.

Extended Field Relationship with Defined Subscripted Relationship

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

 Parent:     MVS-TSOID01.FASAMP.INVFILE
 Dependent:  MVS-TSOID01.FASAMP.INVFILE
 CMD  Parent fields                   Type(Length) Mapped fields
 ---- ------------------------------- ------------ -----------------------------
 ____ 5/INV-WAREHOUSE(1)              CHAR(3)      6(1,3,1)/INV-STATUS(1)
      - - - - - - - - - End of Related Columns - - - - - - - - -         
 ____ INV-PART-NO                     CHAR(15)                           
 ____ INV-DESCRIPTION                 CHAR(40)                           
 ____ INV-UNIT-OF-MEASURE             CHAR(2)                           
 ____ INV-UNIT-PRICE                  DEC(7,2)                           
 ____ INV-WAREHOUSE(2)                CHAR(3)                            
 NMBR Dependent fields                Type(Length)                       
 ---- ------------------------------- ------------                       
    1 INV-PART-NO                     CHAR(15)                           
    2 INV-DESCRIPTION                 CHAR(40)                           
    3 INV-UNIT-OF-MEASURE             CHAR(2)                            
    4 INV-UNIT-PRICE                  DEC(7,2)                          
    5 INV-WAREHOUSE(2)                CHAR(3)

See Relationships for a description of the fields. Note that the element notation for the parent is enclosed in parentheses following the parent field name, while the element notation for the dependent is enclosed in parentheses following the dependent name in the Mapped Fields area.

 

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