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.

Planning

This section provides information to consider before you attempt to install or update File-AID products to Release 21.01.

Process outline

The process for a new installation or an upgrade is achieved by performing tasks associated with milestones. 

New installation

The following milestones guide you through a new installation of File-AID products:

Upgrade

The following milestones guide you through an upgrade of File-AID products:

Important

To keep track of your progress, you may want to print the Checklist of Milestones and Tasks at the end of this space, then check off each milestone and task as it gets completed.


Milestones and roles

Installation, configuration, verification, and deployment are done in 9 milestones. The following table identifies the role or skill set required to perform each milestone. This makes it easier to know which people need to be involved at each milestone and can allow certain tasks to be performed at the same time.


 People Required for Each Milestone

Milestone

Compuware Product
Installer/Administrator

DBA

z/OS UNIX System Administrator

ECC



File-AID



File-AID



File-AID

Db2 l
IMS l

Data Privacy

File-AID

Db2 l
IMS l

Data Privacy

File-AID



File-AID

Db2 l

Data Privacy

File-AID



File-AID



Pre-installation considerations

Understanding PARMLIB members

File-AID uses parameter libraries, or PARMLIBs, to configure each File-AID product and common components. File-AID Product PARMLIB Members lists the sample PARMLIB members for all File-AID products and common components. Each sample PARMLIB member includes comments describing the parameters. Configuration-parameters also lists all parameters with their descriptions.

Important

File-AID Release 21.01 requires PARMLIB Version 2. Version 2 members include the line "$$$ V2 END $$$ -- DO NOT MODIFY OR REMOVE" and do not have PARSELIB specified.
If you are upgrading from a previous release and have not yet migrated your File-AID PARMLIB members to PARMLIB Version 2, do so before updating and processing your PARMLIB members. Follow the instructions in Migration utility for release 17.02.

  • Sample PARMLIB members with suffix 00 (FACM00, FADE00, etc.) in hlq.SXVJSAMP provide the core parameters required for File-AID and should be used as a skeleton for parameters for your particular installation.
  • The sample default PARMLIB members represent the initial defaults in the Compuware Mainframe Services Controller (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.
  • Sample PARMLIB members with suffix ALL (FACMALL, FADEALL, etc.) include all available parameters. If your site requires non-core parameters, you only need to copy those individual parameters to the CMSC PARMLIB members that require non-default parameter values.
  • If you have a requirement to use a PARMLIB suffix other than the default, you must create an XVJSFX Load Module for each unique set of suffixes. For more information, see Configuration-parameters.

File-AID Product PARMLIB Members

Component

Component PARMLIB Name Prefix

Sample Core PARMLIB Member

Sample ALL PARMLIB Member

Shared configuration data

File-AID Common Components (required for all products)

FACM

FACM00

FACMALL

Db2 subsystem environment

FADE

FADE00

FADEALL

IMS environment

FAIE

FAIE00

FAIEALL

Data Privacy environment

FADP

FADP00

FADPALL

Individual product configuration data

File-AID/MVS

FAMV

FAMV00

FAMVALL

File-AID/Data Solutions

FADA

FADA00

FADAALL

File-AID for Db2

FAFD

FAFD00

FAFDALL

File-AID for IMS

FAIX

FAIX00

FAIXALL

File-AID/RDX

FAFR

FAFR00

FAFRALL

Gather CMSC PARMLIB information

Gather the following information from your ECC Installer/Administrator as you will need it to configure File-AID parameters:

  • The name of the CMSC task running on your system (‘cmscname’ value) when updating the CMSC PARMLIB values using the z/OS MODIFY (F) command in Task-5-Finalizing-the-configuration.
  • The file name of the Compuware Mainframe Services Controller (CMSC) PARMLIB data set. You will need this name for configuring the File-AID products.
  • The name of CMSC “Simple Deploy” PARMLIB member(s) DDSNnnnn (initial default is DDSN00, or the specified default in your site’s CMSC start-up) with the DDNAMEs and DATASET NAMEs of all BMC products, such as File-AID, Xpediter/TSO, Abend-AID, etc. A sample is located in hlq.SLCXCNTL(DDSN00).
    DDSNnnnn provides the names of BMC run-time libraries installed at your site. You will need the DDSNnnnn name(s) for configuring your File-AID products.

Important

We recommend to add the FMID (see also FMIDs in section Task-2-Installing-File-AID-products-using-SMP-E) 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


Update CMSC with File-AID PARMLIB information

  1. Make your File-AID PARMLIB libraries available in the //CWPARM concatenation of the Compuware Mainframe Services Controller (CMSC) which is located in hlq.SLCXCNTL(CMSC). For further information on CMSC, see Installing ECC for Release 17.02.

    Important

    • Ensure there is an entry for each File-AID product being used in the CMSC PARMLIB member.
    • Jobs and TSO sessions using File-AID should be restarted to reflect the change.

  2. After making changes to your PARMLIB members, use a JES viewer (such as SDSF, IOF, EJES) to issue a z/OS MODIFY command (abbreviated as F) to update the CMSC with the changes you made to the PARMLIB members.

    Warning

    The MODIFY command requires proper OPERATOR authority.

    Important

    cmscname is the name of the CMSC started task or procname.

    Refresh a single PARMLIB member for a BMC product:

       F cmscname,PARMLIB REFRESH member_name

    For example, you updated the parameters in member FACM00:

       F cmscname,PARMLIB REFRESH FACM00

    Refreshing all parameter members for all BMC products:

       F cmscname,PARMLIB REFRESH

    Important

    Before refreshing all members in the CMSC started task, make sure that it doesn’t include members that aren’t ready to be updated, yet.

  3. Verify that the parameters were updated by using a JES viewer and checking the CMSC address space’s FDBDLOG (see the following figure).

CMSC Address Space FDBDLOG

image2021-3-19_12-46-20.png

Add the File-AID load libraries to your system

We recommend placing the programs listed in File-AID Programs for Link Pack Area (LPA) in the Link Pack Area (LPA). This method saves the system from loading a copy of these modules into each user’s address space which reduces region size required to run these File-AID products by approximately one-half. The rest of the File-AID modules must be made available to your system as described in this section.

Important

File-AID Programs for Link Pack Area (LPA)

Product

Programs

File-AID/MVS

XFASPF, XVJSPFMN, XVJSPFXE, XVJCOMMN, XVJCATLG, XVJUTLTY, XVJIDCMS

File-AID/Data Solutions

UDASPF, XVJSPFMN, XVJSPFXE, XVJCOMMN, XVJCATLG, XVJUTLTY, XVJIDCMS

File-AID for Db2

F2FADB2

Security access to File-AID programs

If your site uses an external security product that restricts programs from being executed as TSO commands (for example, CA ACF2), ensure that File-AID commands are available to your users and do not fall under this restriction. If the commands are restricted, the message “command NOT FOUND” is received.

The security commands and considerations for each File-AID product are:

BMC Compuware File-AID/MVS

XFASPF

XFARLVAR 

Link Pack Area Method Considerations for File-AID/MVS

If you place XFASPF in LPALIB (see also Add the File-AID Load Libraries to Your System) you may need to update your ISPTCM table with an entry for XFASPF. Without this update you may get the error message “COMMAND XFASPF NOT FOUND”. The entry for XFASPF should specify FLAG=42,ENTNAME=XFASPF to indicate that XFASPF is invoked as a command. For more details on the ISPTCM table, consult the IBM reference manuals on the ISPF TSO Command Table.

BMC Compuware File-AID/Data Solutions

UDASPF

UDARLVAR 
Link Pack Area Method Considerations for File-AID/Data Solutions  

If you place UDASPF in LPALIB (see also Add the File-AID Load Libraries to Your System) you may need to update your ISPTCM table with an entry for UDASPF. Without this update you may get the error message “COMMAND UDASPF NOT FOUND”. The entry for UDASPF should specify FLAG=42,ENTNAME=UDASPF to indicate that UDASPF is invoked as a command. For more details on the ISPTCM table, consult the IBM reference manuals on the ISPF TSO Command Table.

BMC Compuware File-AID/RDX

XFRINIT  XFRSWCH   XFRCMDS  XFREXEC
XFREXED  XFRTATUS  F2FAD    FRSPZ

BMC Compuware File-AID for Db2

F2EDIT   F2EDITL   F2PRCMD   F2SQLIDC
F2EDITP  F2FADB2   F2TORDX   F2EDCNTL
F2ENTRY  F2LFANAP  F2XCMD    F2EDREQ
F2FAD    F2MENU    F2XXK50   XFRTATUS
XFDBLDFI XFDICHK   XVJPRMT

DBUSB00  DBUIB00   DBUZB00   DBIDINT2
DBADMNC  DBIDLIB

BMC Compuware File-AID for IMS

XIXMAIN

Required Db2 privileges

We recommend that the installer of File-AID products for Db2 have the SYSADM privilege in order to configure the Db2 environment module (see also Configure Db2 Environment in section Configuring-a-new-installation-of-File-AID-products  or Update Db2 Environment in section Configuring-File-AID-products-to-upgrade).

The installer must have the authority to execute the following Db2 commands:

BIND PACKAGE             BIND PLAN           GRANT EXECUTE ON PACKAGE
GRANT EXECUTE ON PLAN    SET CURRENT SQLID   GRANT CREATE ON COLLECTION

The person who creates the training data (see also Install Training Data in section Task-7-Verifying-the-File-AID-products-installation) must have the authority to execute the following Db2 commands:

ALTER TABLE   CHECK DATA      CREATE DATABASE
CREATE INDEX  CREATE TABLE    CREATE TABLESPACE
GRANT SELECT  LOAD DATA

Prerequisites

Software and Hardware Requirements

Important

Day one support for IBM hardware and software is for toleration-only. For more information on day one support, see support.bmc.com.


Hardware Platforms

  • Mainframe Systems:
    • z16
    • z15, z15 T02
    • z14, z14 ZR1
    • z13, z13s
    • zEC12, zBC12
    • z196, z114

Operating Systems

  • IBM z/OS V2.3, 2.4, and 2.5
  • IBM ISPF for the supported z/OS releases
  • LE libraries for the supported z/OS releases
  • TSO/E for the supported z/OS releases

Notes:

    • Recommended TSO region sizes for processing:

      • File-AID/MVS

        : Minimum region size of 8 MB. If 

        File-AID/MVS

         is installed in the LPA, it requires a minimum region size of approximately 6 MB.

      • File-AID/Data Solutions

        : Minimum region size of 8 MB. If 

        File-AID/Data Solutions

         is installed in the LPA, it requires a minimum region size of approximately 6 MB.

      • File-AID/RDX

        : Minimum region size of 8 MB. In the supplied profiles for batch defaults, the region size is set to 8192K.

      • File-AID for Db2

        : Minimum region size of 16M.

      • File-AID for IMS

        : Minimum region size of 4 MB

    • If using a smaller region size, use caution when entering wildcards or working with large amounts of data. Increase region size accordingly when processing a large amount of data.
    • IBM's fast data access service of the program management binder uses 64-bit storage rather than a dataspace. Therefore, we recommend changing your system default SMF MEMLIMIT Parameter to NOLIMIT through SMFPRMxx in PARMLIB: MEMLIMIT(NOLIMIT).
    • IBM z/OS Conversion Services need to be activated with the appropriate conversion tables in your system. File-AID uses the conversion services to convert Unicode data. See the z/OS Conversion Services documentation for more information.
    • For File-AID Data Privacy jobs using Dynamic Privacy Rules (DPR):

      • specify a region size large enough to run Java (REGION=0M is suggested, 200M is the minimum, 300M minimum for

        File-AID for Db2

        ) in your jobcard.

      • setting the memory values in the LE STACK option to values lower than the IBM default values can cause a performance degradation. The IBM default is: STACK=((128K,128K,ANYWHERE,KEEP,512K,128K),OVR)

Major Subsystems


    • IBM CICS Transaction Server for z/OS V5.4, 5.5, 5.6, and 6.1 (for File-AID products that provide CICS Transactions Server for z/OS support)
    • IBM Db2 for z/OS V11.1, 12.1, and 13.1 (for File-AID products that provide IBM Db2 support)
    • IBM IMS Transaction and Database Servers V15.1, 15.2, and 15.3 (for File-AID products that provide IBM IMS support)

Languages


    • IBM Enterprise COBOL for z/OS V4.2, 6.1, 6.2, 6.3, and 6.4.
    • IBM Enterprise PL/I for z/OS 5.3 and 6.1.

Corequisites


    • BMC Products and Components:
      • To use Compuware Mainframe Services Controller (CMSC) with:
        • Enterprise Common Components (ECC) 17.2, with current maintenance. 
      • To use File-AID with Xpediter/TSO
        • 17.2
      • To use File-AID with Abend-AID:
        • 17.2

Important

When configuring File-AID support for the Topaz Workbench and you want to maintain access to multiple releases of File-AID, each release level must have its unique host and port configuration (different releases of File-AID cannot share the same host and port).


    • Innovation Access Method (IAM) 9.4, 10.0.
    • CA Librarian 4.4

Known issues

There are no known issues at this time.

 

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