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.

File-AID for IMS/DC

A short test that uses the File-AID for IMS training files (see Installing-Training-Files) completes the installation process. Running the test verifies that all components of File-AID for IMS/DC are loaded properly and that executing File-AID for IMS/DC produces the expected results.

This section provides step-by-step procedures along with screen illustrations and explanations of common variances to assist you with the verification of the installation of File-AID for IMS/DC. If you encounter any problems during the verification procedure, refer to Potential Problems. If you are still unable to solve the problem, contact BMC customer support at BMC Support.

Task 13.38 Verify Primary Options

  1. Log on to IMS to invoke File-AID for IMS/DC.
  2. If you installed the MFS formats into the test format library, enter /TEST MFS to allocate the correct format library.
  3. Enter one of the transaction codes installed, preferably one that can access the sample databases shipped with File-AID. The File-AID for IMS/DC Primary Option Menu is displayed (see the following figure).

Primary Option Menu

image2021-7-19_22-56-37.png

Task 13.39 Edit DBD

  1. Type 2 in the Option field.

  2. Press Enter. The DBD Member List screen is displayed (see the following figure). The DBDs listed are the same as those in the PSB associated with the transaction entered in IMS System Definition.

    DBD Member List Screen

    image2021-7-19_22-57-22.png

Task 13.40 Edit Data Base Location

  1. Type S next to the PORDR database name that you want to select.

  2. Press Enter. The Data Base Location screen is displayed (see the following figure).

    Data Base Location Screen

    image2021-7-19_22-58-24.png

Task 13.41 Select Segment and Format

  1. Select the first segment on the Data Base Location screen to retrieve the first segment in the database, and press Enter. The Formatted screen is displayed (see the following figure).

    Formatted Screen

    image2021-7-19_22-59-12.png

  2. Type UNFMT to display the segment in the unformatted mode, and press Enter. The Unformatted screen is displayed (see the following figure).

    Unformatted Screen

    image2021-7-19_22-59-50.png

  3. Type KEY, and press Enter. The Key Specification screen is displayed (see the following figure).

    Key Specification Screen

    image2021-7-19_23-0-30.png

  4. Type CANCEL, and press Enter. The Unformatted screen is displayed again.

  5. Type HEX OFF, and press Enter. The Unformatted/HEX Off screen is displayed (see the following figure).

    Unformatted/HEX OFF Screen

    image2021-7-19_23-1-11.png

  6. Type INDEX, and press Enter. The Index screen is displayed (see the following figure).

    Index Screen

    image2021-7-19_23-1-50.png

Task 13.42 Exit

Type =X in the Command field and press Enter to exit File-AID. A blank screen is displayed.

Potential Problems

  • If, after Verify Primary Options, the message NO SUCH TRANSACTION CODE appears:
    • Verify that the Stage 1 system definition was done for the transaction code entered.
    • Verify that a space was entered after the transaction code.
  • If, after any task, the message REQUESTED BLOCK NOT AVAILABLE appears:
    • Verify that /TEST MFS was entered prior to the transaction code if the MFS modules were linked into the test format libraries.
    • Verify that the block name displayed in the message is the same as the MOD name of the corresponding MFS source member.
    • Verify that the logical terminal type is one of those supported by File-AID (Refer to MFS Tailoring).
  • If, after Verify Primary Options, there is no response from the terminal:
    • Verify that the IMS transaction queue is not backed up.
    • Verify that all the databases within the PSB are online to IMS and not stopped.
    • Verify that the class specified on the APPLCTN or TRANSACT macros is proper for your installation.
    • Verify that the PSB size shown on the ACB generation report is within your installation’s PSB pool size limits.
    • Verify that the VSAM buffer subpool has buffers large enough to contain the control intervals of the control database datasets.
  • If File-AID abends with an AI status code:
    • Verify that the control databases are correctly allocated.
    • Verify that the control databases were properly initialized with job JCLALOC.
    • Verify that the control databases’ dataset names are not restricted from read/write access by an existing security package.
  • If File-AID abends with message "D204":
    • Verify that job JCLCLTUP was run correctly.
    • The control segment may have been deleted by an external job. Run program XIXREBLD to reestablish this segment. Refer to Control Segment Missing or Invalid.
  • If, upon entering the Edit Formatted mode, no segment layout is displayed:
    • Verify that job JCLCLTUP was correctly run.
    • If the database selected was not one of the sample databases, verify that job XIXOXUPD or XIXOXUPB was correctly run for that database.
  • If, after any task, the message TRAN/LTERM STOPPED appears:
    • Verify that File-AID did not previously abend.
    • Verify that the transaction was not stopped by the MTO.

  • If, after entering the KEY or INDEX command, data is missing or truncated or there is no response from the terminal:

    Verify that the IMS large message queue is long enough. For the required size, see IMS Message Queues.

 

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