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.

Performing resource definition

File-AID for IMS/CICS runs like any other CICS application and, therefore, must be initially defined to the CICS system. Because resource 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 tasks.

  • If using Resource Definition Online (RDO), perform the following steps:

    1. Code CEDA transactions to define the File-AID for IMS/CICS GROUP and PROFILE to CICS.
    2. Code a CEDA transaction for each transaction/PSB to be used in your installation configuration. These transactions create entries in the Program Control Table (PCT).
    3. Code CEDA transactions for the ten programs and four mapsets that comprise File-AID for IMS. These transactions create entries in the Processing Program Table (PPT).

Important

The first three characters of the module names are customizable based on the “Program name prefix” (CICS_PROGRAM_PREFIX) and “Mapset name prefix” (BMS_MAPSET_PREFIX) which can be set as described under File-AID for IMS Additional Parameters (FAIXALL).

  • Perform the following steps to complete the resource definition:

    1. 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 (see DFSMDA Macros: ). These macros are input to the IMSDALOC procedure during CICS system definition.DFSMDA Macros:

      DFSMDA TYPE=DATABASE,DBDNAME=IXCCLT
      DFSMDA TYPE=DATASET,DSNAME=XXXXXXX.IXCCLT,DDNAME=IXCCLTDD
      DFSMDA TYPE=DATABASE,DBDNAME=IXCLTM
      DFSMDA TYPE=DATASET,DSNAME=XXXXXXX.IXCLTM,DDNAME=IXCLTMDD
      DFSMDA TYPE=DATABASE,DBDNAME=IXCAUD
      DFSMDA TYPE=DATASET,DSNAME=XXXXXXX.IXCAUD,DDNAME=IXCAUDDD
      DFSMDA TYPE=DATABASE,DBDNAME=PCUST
      DFSMDA TYPE=DATASET,DSNAME=XXXXXXX.FICSAMP.CUSTOMER,DDNAME=PCUSTDD
      DFSMDA TYPE=DATABASE,DBDNAME=PORDR
      DFSMDA TYPE=DATASET,DSNAME=XXXXXXX.FICSAMP.ORDER,DDNAME=PORDRDD
      DFSMDA TYPE=DATABASE,DBDNAME=PPART
      DFSMDA TYPE=DATASET,DSNAME=XXXXXXX.FICSAMP.PART,DDNAME=PPARTDD

    2. 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(IXCCLT) SHARELVL(0) TYPEIMS

      INIT.DB DBD(IXCCLT) SHARELVL(0) TYPEIMS
      INIT.DBDS DBD(IXCCLT) DDN(IXCCLTDD) DSN(XXXXXXX.IXCCLT) GENMAX(2)
      INIT.DB DBD(IXCLTM) SHARELVL(0) TYPEIMS
      INIT.DBDS DBD(IXCLTM) DDN(IXCLTMDD) DSN(XXXXXXX.IXCLTM) GENMAX(2)
      INIT.DB DBD(IXCAUD) SHARELVL(0) TYPEIMS
      INIT.DBDS DBD(IXCAUD) DDN(IXCAUDDD) DSN(XXXXXXX.IXCAUD) GENMAX(2)
      INIT.DB DBD(PCUST) SHARELVL(0) TYPEIMS
      INIT.DBDS DBD(PCUST) DDN(PCUSTDD) DSN(XXXXXXX.FICSAMP.CUSTOMER) GENMAX(2)
      INIT.DB DBD(PORDR) SHARELVL(0) TYPEIMS
      INIT.DBDS DBD(PORDR) DDN(PORDRDD) DSN(XXXXXXX.FICSAMP.ORDER) GENMAX(2)
      INIT.DB DBD(PPART) SHARELVL(0) TYPEIMS
      INIT.DBDS DBD(PPART) DDN(PPARTDD) DSN(XXXXXXX.FICSAMP.PART) GENMAX(2)

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

      DATABASE DBD=IXCCLT,ACCESS=EX
      DATABASE DBD=IXCLTM,ACCESS=EX
      DATABASE DBD=IXCAUD,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.

    4. Code an APPLCTN macro for each PSB to be used in your installation configuration. These macros are input to the IMS Stage 1 system definition job.
        APPLCTN PSB=IXCIXC

Online

Important

For unspecified options, use the defaults or installation requirements.

CEDA ADD GROUP(IXCCICS) LIST(user-list)
CEDA DEFINE PROFILE(IXCPROF) GROUP(IXCCICS)

PCT

CEDA DEFINE TRANS(IXC) GROUP(IXCCICS) PROG(IXCMAIN) TWA(4)1
PROF(IXCPROF) TASKDATALOC(ANY)

Important

1: the main program name (default IXCMAIN) is replaced with the value you specified with the value you specified for it in the linkedit JCL XIXCLINK. For more information, see Linkedit File-AID for IMS/CICS (XIXCLINK) (Optional) in the Customizing-File-AID-for-IMS-CICS.

PPT

CEDA DEFINE PROGRAM(XVJPARM) GROUP(IXCCICS) LANGUAGE(PLI) EXECKEY(CICS) DATALOC(ANY)
CEDA DEFINE PROGRAM(IXCMAIN) GROUP(IXCCICS) LANGUAGE(PLI) EXECKEY(CICS) DATALOC(ANY)Step 1
CEDA DEFINE PROGRAM(IXCEDTF) GROUP(IXCCICS) LANGUAGE(PLI) EXECKEY(CICS) DATALOC(ANY)
CEDA DEFINE PROGRAM(IXCEDTI) GROUP(IXCCICS) LANGUAGE(PLI) EXECKEY(CICS) DATALOC(ANY)
CEDA DEFINE PROGRAM(IXCEDTL) GROUP(IXCCICS) LANGUAGE(PLI) EXECKEY(CICS) DATALOC(ANY)
CEDA DEFINE PROGRAM(IXCEDTS) GROUP(IXCCICS) LANGUAGE(PLI) EXECKEY(CICS) DATALOC(ANY)
CEDA DEFINE PROGRAM(IXCEDTU) GROUP(IXCCICS) LANGUAGE(PLI) EXECKEY(CICS) DATALOC(ANY)
CEDA DEFINE PROGRAM(IXCKEY)  GROUP(IXCCICS) LANGUAGE(PLI) EXECKEY(CICS) DATALOC(ANY)
(OPTIONAL) CEDA DEFINE PROGRAM(IXCSCXT) GROUP(IXCCICS) LANGUAGE(PLI) EXECKEY(CICS) DATALOC(ANY)

CEDA DEFINE PROGRAM(IXCEND)  GROUP(IXCCICS) LANGUAGE(COBOL) EXECKEY(CICS) DATALOC(ANY)

CEDA DEFINE MAPSET(IXCMP1)   GROUP(IXCCICS)
CEDA DEFINE MAPSET(IXCMP2)   GROUP(IXCCICS)
CEDA DEFINE MAPSET(IXCMP3)   GROUP(IXCCICS)
CEDA DEFINE MAPSET(IXCMP4)   GROUP(IXCCICS)

Important

Step 1: The main program name (default IXCMAIN) is replaced with the value you specified with the value you specified for it in the linkedit JCL XIXCLINK. For more information, see Linkedit File-AID for IMS/CICS (XIXCLINK) (Optional) in the Customizing-File-AID-for-IMS-CICS.

Related topics

BMC Compuware File-AID for IMS

 

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