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.

IMS system definition

File-AID for IMS/DC runs like any other IMS application and, therefore, must be initially defined to the IMS system. Because system definition can be performed only at specific times at your installation, it will speed the installation process if you do the following before starting the detailed installation steps:

  1. Code an APPLCTN and TRANSACT macro for each transaction/PSB combination to be used in your installation configuration. These macros are input to the IMS Stage 1 system definition job.The PSB= operand must be the same as the main program name or an alias’ program name and correspond to the PSBNAME= operand of the PSB used as the transaction.

    APPLCTN PSB=IXDMAIN,PGMTYPE=(TP,,,)

    For full-featured databases code the following:

    TRANSACT CODE=FILEAID,MSGTYPE=(SNGLSEG,RESPONSE),MODE=SNGL,
    PROCLIM=(10,2),EDIT=ULC,SCHD=1

    For Fast Path databases code the following:

    TRANSACT CODE=FILEAID,MSGTYPE=(SNGLSEG,RESPONSE),MODE=SNGL,
    PROCLIM=(10,2),EDIT=ULC,SCHD=1,FPATH=YES

    The CODE= operand in the TRANSACT macro corresponds to the NAME= operand in the first PCB in the transaction’s PSB. Refer to Modify PSBs in Customizing-File-AID-for-IMS-DC.

    Warning

    The TRANSACT macro must be coded with the RESPONSE keyword, and the TERMINAL macro CANNOT be coded with NORESP. Failure to do this will yield unpredictable results.

    To browse/edit Fast Path databases with File-AID for IMS/DC you need to define the transaction as an IMS Fast Path potential transaction. File-AID for IMS/DC does not run as a Fast Path exclusive transaction. An IMS Fast Path potential transaction is identified by a TRANSACT macro statement that specifies FPATH=YES following an APPLCTN statement that does not specify FPATH=YES.

  2. Code a DATABASE macro to define the required CLT and LTM control database DBDs, the three sample database DBDs, and, optionally, the AUD DBD. These macros are input to the IMS Stage 1 system definition job.

    DATABASE DBD=IXDCLT,ACCESS=EX
    DATABASE DBD=IXDLTM,ACCESS=EX
    DATABASE DBD=IXDAUD,ACCESS=EX
    DATABASE DBD=PCUST,ACCESS=EX
    DATABASE DBD=PORDR,ACCESS=EX
    DATABASE DBD=PPART,ACCESS=EX

    If you want the Data Management Block (DMB) created by the database statement to be made resident in storage during system initialization, include the resident option on the database statement.

  3. Code a DFSMDA macro for each of the control databases and the sample databases, if desired. Use the procedures in place at your installation to make them available to IMS.

    DFSMDA TYPE=DATABASE,DBDNAME=IXDCLT
    DFSMDA TYPE=DATASET,DSNAME=XXXXXXX.IXDCLT,
                DDNAME=IXDCLTDD
    DFSMDA TYPE=DATABASE,DBDNAME=IXDLTM
    DFSMDA TYPE=DATASET,DSNAME=XXXXXXX.IXDLTM,
                DDNAME=IXDLTMDD
    DFSMDA TYPE=DATABASE,DBDNAME=IXDAUD
    DFSMDA TYPE=DATASET,DSNAME=XXXXXXX.IXDAUD,
                DDNAME=IXDAUDDD
    DFSMDA TYPE=DATABASE,DBDNAME=PCUST
    DFSMDA TYPE=DATASET,DSNAME=XXXXXXX.FIDSAMP.CUSTOMER,
                DDNAME=PCUSTDD
    DFSMDA TYPE=DATABASE,DBDNAME=PORDR
    DFSMDA TYPE=DATASET,DSNAME=XXXXXXX.FIDSAMP.ORDER,
                DDNAME=PORDRDD
    DFSMDA TYPE=DATABASE,DBDNAME=PPART
    DFSMDA TYPE=DATASET,DSNAME=XXXXXXX.FIDSAMP.PART,
                DDNAME=PPARTDD

  4. If you want the control databases and sample databases to be under the control of DBRC, code an INIT.DB and INIT.DBDS command for each. These commands are input to the Recovery Control Utility of DBRC.

    INIT.DB DBD(IXDCLT) SHARELVL(0) TYPEIMS
    INIT.DBDS DBD(IXDCLT) DDN(IXDCLTDD)
              DSN(XXXXXXX.IXDCLT) GENMAX(2)
    INIT.DB DBD(IXDLTM) SHARELVL(0) TYPEIMS
    INIT.DBDS DBD(IXDLTM) DDN(IXDLTMDD)
              DSN(XXXXXXX.IXDLTM) GENMAX(2)
    INIT.DB DBD(IXDAUD) SHARELVL(0) TYPEIMS
    INIT.DBDS DBD(IXDAUD) DDN(IXDAUDDD)
              DSN(XXXXXXX.IXDAUD) GENMAX(2)
    INIT.DB DBD(PCUST) SHARELVL(0) TYPEIMS
    INIT.DBDS DBD(PCUST) DDN(PCUSTDD)
              DSN(XXXXXXX.FIDSAMP.CUSTOMER) GENMAX(2)
    INIT.DB DBD(PORDR) SHARELVL(0) TYPEIMS
    INIT.DBDS DBD(PORDR) DDN(PORDRDD)
              DSN(XXXXXXX.FIDSAMP.ORDER) GENMAX(2)
    INIT.DB DBD(PPART) SHARELVL(0) TYPEIMS
    INIT.DBDS DBD(PPART) DDN(PPARTDD)
              DSN(XXXXXXX.FIDSAMP.PART) GENMAX(2)

 

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