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.

Overview of File-AID product configuration


File-AID element prefixes

BMC has registered the following element prefixes with IBM for the File-AID products:

  • XVJ for File-AID Common Components
  • XFD for File-AID for Db2
  • UDA for File-AID/Data Solutions
  • XFA for File-AID/MVS
  • XFR for File-AID/RDX
  • XIX for File-AID for IMS
  • XFE for File-AID/EX Enterprise Edition

File-AID PDSE libraries

Some of the File-AID libraries must be PDSE (Partitioned Data Set Extended) data sets. The following table lists the File-AID Target Libraries and identifies which libraries must be PDSEs. The default value column shows the initial default high level qualifier (SYS1.CPWR.MXVJ211) from the SMP/E installation. In the remainder of the documentation, the highlevel qualifier for File-AID libraries is represented with the hlq. variable.
File-AID Target Libraries

Description

Default Value

Your Value

Comments

Load Library

SMPE Target Dataset

SYS1.CPWR.MXVJ211.SXVJLOAD


SMP/E Target Load Library.

This PDSE stores the SXVJLOAD library members.

The SXVJLOAD load library needs only be APF Authorized in order for it to be ready to be referenced in the CSS TP Start-up procedure as mentioned in Installing ECC. This library MUST have universal read access. See also Task 6.6.1 Add File-AID Libraries to APF Authorized Library List for Topaz Workbench Integration in Task-5-Finalizing-the-configuration.

Configuration Module Dataset

SYS1.CPWR.MXVJ211.CXVJLOAD


Configuration Module Load Library.

Must be created manually after the SMP/E installation (see Task 3.1 Allocate Customized Libraries in Task-3-Preparing-for-configuration-after-installation).

This PDSE stores the CXVJLOAD library members. These library members contain customized load modules.

The CXVJLOAD load library needs only be APF Authorized in order for it to be ready to be referenced in the CSS TP Start-up procedure as mentioned in the Installing ECC. This library MUST have universal read access. See also Task 6.6.1 Add File-AID Libraries to APF Authorized Library List for Topaz Workbench Integration in Task-5-Finalizing-the-configuration.

Authorized Load Library

SMPE Target Dataset

SYS1.CPWR.MXVJ211.SXVJAUTH


SMP/E Target APF Authorized Load Library.

This PDSE stores the SXVJAUTH library members. These library members contain customized load modules.

The SXVJAUTH load library needs only be APF Authorized in order for it to be ready to be referenced in the CSS TP Start-up procedure as mentioned in the Installing ECC. This library MUST have universal read access. See also Task 6.6.1 Add File-AID Libraries to APF Authorized Library List for Topaz Workbench Integration in Task-5-Finalizing-the-configuration.

CLIST Library

SMPE Target Dataset

SYS1.CPWR.MXVJ211.SXVJCLIB


SMP/E Target CLIST library.

This PDS stores the SXVJCLIB library members. These library members contain CLISTs that are input to the product.

Configuration Module Dataset

SYS1.CPWR.MXVJ211.CXVJCLIB


Configuration Module CLIST library.

Must be created manually after the SMP/E installation (see Task 3.1 Allocate Customized Libraries in Task-3-Preparing-for-configuration-after-installation).

This PDS stores the CXVJCLIB library members. These library members contain configured CLISTs that are input to the product.

English Message Library

SMPE Target Dataset

SYS1.CPWR.MXVJ211.SXVJMENU


SMP/E Target Message library.

This PDS stores the SXVJMENU library members which contain product messages.

English Panel Library

SMPE Target Dataset

SYS1.CPWR.MXVJ211.SXVJPENU


SMP/E Target Panel library.

This PDS stores the SXVJPENU library members which contain product panels.

Sample Library

SMPE Target Dataset

SYS1.CPWR.MXVJ211.SXVJSAMP


SMP/E Target Sample library.

This PDS stores the SXVJSAMP library members which contain sample member.

English Skeleton Library

SMPE Target Dataset

SYS1.CPWR.MXVJ211.SXVJSENU


SMP/E Target Skeleton library.

This PDS stores the SXVJSENU library members which contain product skeletons.

Configuration Module Dataset

SYS1.CPWR.MXVJ211.CXVJSENU


Configuration Module Skeleton library.

Must be created manually after the SMP/E installation (see Task 3.1 Allocate Customized Libraries in Task-3-Preparing-for-configuration-after-installation).

This PDS is currently empty, but may be used in the future to store the CXVJSENU library members which contain customized product skeletons.

Table Library

SMPE Target Dataset

SYS1.CPWR.MXVJ211.SXVJTENU


SMP/E Target Table library.

This PDS stores the SXVJTENU library members which contain product tables.

DBRM Library

SMPE Target Dataset

SYS1.CPWR.MXVJ211.SXVJDBRM


SMP/E Target DBRM library.

This PDS stores the SXVJDBRM library members.

PSB Library

SMPE Target Dataset

SYS1.CPWR.MXVJ211.SXVJPPSB


SMP/E Target PSB library.

This PDS stores the SXVJPPSB library members.

Object Administration Pattern Library

SMPE Target Dataset

SYS1.CPWR.MXVJ211.SXVJPATT


Object Administration SMP/E Target Pattern library.

This PDSE stores the SXVJPATT library members. These library members contain encrypted patterns.

Optional data sets

Japanese Message Library

SMPE Target Dataset

SYS1.CPWR.MXVJ211.SXVJMJPN


SMP/E Target Japanese Language Message library.

This PDS stores the SXVJMJPN library members which contain product messages in Japanese.

Japanese Panel Library

SMPE Target Dataset

SYS1.CPWR.MXVJ211.SXVJPJPN


SMP/E Target Japanese Language Panel library.

This PDS stores the SXVJPJPN library members which contain product panels in Japanese.

Japanese Skeleton Library

SMPE Target Dataset

SYS1.CPWR.MXVJ211.SXVJSJPN


SMP/E Target Japanese Language Skeleton library.

This PDS stores the SXVJSJPN library members which contain product skeletons in Japanese.

Task 1.1 Update CLIST Members for hlq.CXVJCLIB

Members XVJRUN and XVJALLOC in hlq.SXVJCLIB use the default DDSNnnnn member as specified in your site’s CMSC start-up. Always point to the CMSC PARMLIB DDSNnnnn member that includes the File-AID run-time libraries you are currently configuring.

Important

We recommend to add the FMID to each File-AID runtime data set in the DDSN member so that the Release 17.02 and Release 21.01 can both be in the DDSNnnnn member together if needed during the upgrade. Example:

DD_INFO
DDNAME=SXVJCLIB
DSNAME=hlq.V210100.SXVJCLIB
FMID=MXVJ211
END
Warning
  • When converting from a non-Simple Deploy installation to a Simple Deploy installation, remove any and all previous CXVJCLIB modifications.
  • There should never be modifications to SXVJCLIB.

If your File-AID run-time libraries you are currently configuring are included in the default DDSNnnnn member as specified in your site’s CMSC start-up, you may skip this task.

Important

This task is only required if your File-AID run-time libraries you are currently configuring are in a different DDSNnnnn member than the default member as specified in your site’s CMSC start-up or you are not using the CMSC “Simple Deploy” facility.

Member XVJRUN

XVJRUN launches File-AID products using the ALTLIB facility to allocate the CLIST library or libraries, which in turn calls XVJALLOC to allocate the remaining libraries.

  1. Copy CLIST member XVJRUN from hlq.SXVJCLIB into your customized CLIST library hlq.CXVJCLIB.
  2. Modify XVJRUN to your site’s requirements by following the instructions in the member.

Member XVJALLOC

XVJALLOC allocates libraries used by File-AID products.

  1. Copy CLIST member XVJALLOC from hlq.SXVJCLIB into your customized CLIST library hlq.CXVJCLIB.
  2. Modify XVJALLOC to your site’s requirements by following the instructions in the member.
    Always allocate CXVJLOAD and CXVJSENU in XVJALLOC.

Task 1.2 Update XVJDSN with File-AID Run-Time Libraries

XVJDSN makes the File-AID run-time library names available for File-AID skeletons.

Important

This task is only required if your File-AID run-time libraries you are currently configuring are in a different DDSNnnnn member than the default member as specified in your site’s CMSC start-up or your site uses other than the default IBM names for ISPFxLIB (only required for File-AID for Db2, File-AID/RDX and File-AID for IMS) and SORTLIB (only required for File-AID for IMS).

Important

If your File-AID run-time libraries you are currently configuring are included in the default DDSNnnnn member as specified in your site’s CMSC start-up, you may skip this task.

  1. Copy member XVJDSN from hlq.SXVJSENU into your customized skeleton library hlq.CXVJSENU.
  2. Modify the copied member XVJDSN to your site’s requirements by following the instructions in the member.

Db2 system requirements

If you are using DDF (Distributed Data Facility), define the SYSIBM.LOCATIONS table in the Db2 catalog for each subsystem on which you plan to access a File-AID product. If it is not present and the subsystem parameter DDF_INSTALLED is set to YES, a bind SQL error occurs when you bind the File-AID plan. For more information, see DDF_INSTALLED.

File-AID/MVS SMF record mapping

The SMF Record Mapping facility is shipped with the File-AID/MVS product as libraries hlq.SXVJSMFL and hlq.SXVJSMFX.

The mapping facility consists of PL/I record layouts (hlq.SXVJSMFL) for most of the common IBM SMF record types and a File-AID XREF library (hlq.SXVJSMFX), containing XREF and selection criteria members that automate the process of layout selection when browsing SMF data records. A complete File-AID/MVS system is required to use the SMF record mapping facility.

File-AID users may employ the SMF Record Mapping facility to browse raw SMF data intelligently using the BMC-supplied PL/I layouts, automatic layout cross reference (XREF) members, and File-AID’s selection logic.

The Getting started with File-AID/MVS SMF record mapping JES 4 provides instructions for using BMC’s File-AID SMF Record Mapping facility to map IBM MVS JES Version 4 or 5 SMF records.

 

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