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.

Configuring File-AID products to upgrade


This milestone will guide you through the configuration of an upgrade to File-AID 21.01 from a File-AID Release 10.01, 10.02, or 16.03, or 17.02.

Warning

If you are upgrading from a File-AID Release prior to 10.01 or performing an initial installation of File-AID, perform Configuring-a-new-installation-of-File-AID-products instead.


Important

Detailed information on parameter options for all File-AID products can be found in the sample PARMLIB members as well as in the Configuration-parameters and PARMLIB-members.

The following persons are required for this milestone:

  • File-AID Installer
  • Db2 DBA
  • IMS DBA
  • z/OS UNIX System Administrator

Tasks

Perform the following tasks to upgrade your File-AID product(s).


Important

Environment parameters and File-AID product parameters can be converted at the same time.

Task 5.1 Convert PARMLIB Load Modules to PARMLIB Members

Important

The following person is required for this task:

  • File-AID Installer

File-AID provides sample JCL (XVJCNV) in the sample library hlq.SXVJSAMP that converts PARMLIB Load Modules created with File-AID Release 10.01 through 16.03 into PARMLIB Members for File-AID Release 21.01. The following table lists the PARMLIB Load Modules and their corresponding Release 21.01 PARMLIB Members.

  1. Modify the sample member XVJCNV by following the instructions in the job.
  2. Submit the job.
  3. Verify the output PARMLIB members to make sure the parameter values match your site requirements, especially for parameters added since your PARMLIB Load Modules were created.
  4. If you are setting up File-AID to work with Topaz Workbench, for parameter TOPAZ_WORKBENCH_MESSAGE_LIBRARY= in PARMLIB member FACMnnnn, specify the name of the Target Message Library (for example, hlq.SXVJMENU) that is required for the Topaz Workbench File-AID Data Editor.

PARM modules

Component

Pre-Release 17.02 Module Name

Release 17.02 and 21.01 PARMLIB Member Prefix

Shared configuration data

File-AID Common Components (required for all products)

XVJOPUNV

FACM

Db2 subsystem environment

XVJOPDB2

FADE

IMS environment

XVJOPIMS

FAIE

Data Privacy environment

XVJOPDPR

FADP

Individual product configuration data

File-AID/MVS

XVJOPXFA

FAMV

File-AID/Data Solutions

XVJOPUDA

FADA

File-AID for Db2

XVJOPXFD

FAFD

File-AID for IMS

XVJOPXIX
XVJOPNIX
XVJOPOIX

FAIX

File-AID/RDX

XVJOPXFR

FAFR

PARMLIB member naming convention

PPPPnnnn

PPPP is the product prefix (see PARM modules).

nnnn is the 1 to 4-character PARMLIB suffix, for example 00.

The PARMLIB member name for each product or product component must start with the product prefix, for example FACM for File-AID Common Components. The 1- to 4-character suffixes can be used to replace the default name (FACM00). If the parameter for a given product is omitted, the default suffix will be 00.

Important

default name : The listed defaults represent the initial defaults in the CMSC. However, the default suffix for each PARMLIB member could have been changed for your site’s CMSC start-up and supersede these listed values. For more information, see Installing ECC.

Task 5.2 Update Db2 Environment

Important

If you have purchased File-AID for Db2 or File-AID/RDX with Db2 option, perform this task to configure your Db2 environment (Db2 subsystems), otherwise skip this task.

The following person is required for this task:

  • Db2 DBA

This also includes the tasks that would need to be executed after upgrading Db2. These tasks should be performed anytime a change is made to any Db2 subsystem.


Task 5.2.1 Review/Update Your Converted Db2 Environment Parameters (FADEnnnn)

The converted Db2 Environment PARMLIB member(s) include all parameters for the Db2 subsystems you defined previously. You may modify, delete, or add Db2 subsystem definitions:

  1. Review and update the converted PARMLIB member FADEnnnn for your site specific parameters. Do this during the initial upgrade and anytime thereafter when you want to modify your Db2 subsystem definitions for File-AID.
  2. If you are setting up File-AID to work with Topaz Workbench, setting the SUBSYSTEM_ENABLED indicator to Y will mark this subsystem as active and available to be used with File-AID/RDX, File-AID for Db2, and File-AID Data Editor of the Topaz Workbench.

Task 5.2.2 Create and Run Bind JCL

Each Db2 subsystem you defined and marked as an active Db2 subsystem with the SUBSYSTEM_ENABLED indicator must be bound before they can be used within the new File-AID release.

Sample library hlq.SXVJSAMP includes sample Bind JCL member XVJBIND.

  1. Follow the instructions in the member and define the BIND job for the first Db2 subsystem.
  2. Review the JCL and submit the job to bind the selected Db2 Subsystem. Verify that the job completed before continuing.
  3. Copy the member and modify the JCL for the next Db2 subsystem(s).
  4. Review the JCL and submit the job to bind the selected Db2 Subsystem. Verify that the job completed before continuing.
  5. Repeat steps 3 and 4 as needed for additional Db2 subsystems.
  6. Save your Bind JCL members in case you need to re-bind your Db2 subsystems.

Important

As an alternative to using sample Bind JCL member XVJBIND, BMC provides File-AID BIND dialog service XVJ$BIND in hlq.SXVJSAMP. Instead of completing Task 5.2.2, you can execute XVJ$BIND, but only after completing Task 6.1 Update CMSC with PARMLIB Information as described in Task-5-Finalizing-the-configuration as XVJ$BIND collects its information to build the Bind JCL from CMSC. For more information, see Db2 Bind JCL Dialog.

Task 5.3 Update IMS Environment

Important

If you have purchased a File-AID for IMS license, perform this task to configure your IMS environment(s), otherwise skip this task.

The following person is required for this task:

  • IMS DBA

Task 5.3.1 Review/Update Your Converted IMS Environment Parameters (FAIEnnnn)

The converted IMS Environment PARMLIB member(s) include all parameters for the IMS environments you defined previously. You may modify, delete, or add IMS Environment definitions:

  1. Review and update the converted PARMLIB member FAIEnnnn to create your site specific parameters. Do this during the initial installation and anytime thereafter when you want to modify your IMS Environment definitions for File-AID.
  2. If you are setting up File-AID to work with Topaz Workbench, for the MAX_GN_CALLS_FOR_FIND_AND_CHANGE_CMDS parameter, specify how many GET NEXT calls should be allowed when processing a maximum page down request using the File-AID Data Editor before processing is interrupted.

Task 5.4 Update File-AID Data Privacy Environment

Important

If you have purchased a license for one or more of the following products and intend to use Topaz Workbench File-AID Data Privacy, perform this task to configure your File-AID Data Privacy environment, otherwise skip this task.

  • File-AID/Data Solutions with Topaz Workbench File-AID Data Privacy option
  • File-AID for IMS/ISPF with Topaz Workbench File-AID Data Privacy option
  • File-AID/RDX with Topaz Workbench File-AID Data Privacy option
  • File-AID for Db2 with Topaz Workbench File-AID Data Privacy option

The following person is required for this task:

  • z/OS UNIX System Administrator

Task 5.4.1 Review/Update Your Converted File-AID Data Privacy Environment Parameters (FADPnnnn)

The converted File-AID Data Privacy Environment PARMLIB member(s) include all parameters for the File-AID Data Privacy environments you defined previously. You may modify File-AID Data Privacy Environment definitions:

Important

File-AID Data Privacy must have been installed per the instructions in Topaz for Enterprise Data Installation and Configuration Guide before proceeding with this task.

Review and update the converted PARMLIB member FADPnnnn to create your site specific parameters. Do this during the initial installation and anytime thereafter when you want to modify your File-AID Data Privacy Environment definitions for File-AID.

What’s Next?

At this point you are done with setting your File-AID parameters. Go to Task-5-Finalizing-the-configuration to continue your configuration.

 

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