Planning

This section provides information to consider before you attempt to install or update File-AID products to Release 23.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:

• Task-1-Ensuring-installation-and-configuration-of-companion-products
• Task-2-Installing-File-AID-products-using-SMP-E
• Task-3-Preparing-for-configuration-after-installation
• Task-4-Configuring-the-File-AID-products
• Task-5-Finalizing-the-configuration
• Task-6-Preparing-File-AID-products-to-integrate-with-BMC-AMI-DevX-Workbench-for-Eclipse-and-BMC-AMI-DevX-Workbench-for-VS-Code
• Task-7-Verifying-the-File-AID-products-installation
• Task-8-Deploying-the-File-AID-products

Upgrade

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

• Task-1-Ensuring-installation-and-configuration-of-companion-products
• Task-2-Installing-File-AID-products-using-SMP-E
• Task-3-Preparing-for-configuration-after-installation
• Task-4-Configuring-the-File-AID-products
• Task-5-Finalizing-the-configuration
• Task-6-Preparing-File-AID-products-to-integrate-with-BMC-AMI-DevX-Workbench-for-Eclipse-and-BMC-AMI-DevX-Workbench-for-VS-Code
• Task-7-Verifying-the-File-AID-products-installation
• Task-8-Deploying-the-File-AID-products

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.

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. The Parameter-descriptions also lists all parameters with their descriptions.

• 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 BMC AMI Common 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 PARMLIB-members.
   

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 BMC AMI Common 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 AMI products, such as File-AID, BMC AMI DevX Code Debug for TSO, BMC AMI DevX 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.

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

   Warning

   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.

   Error

   Warning

   The MODIFY command requires proper OPERATOR authority.

   Warning

   Important

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

   Refresh a single PARMLIB member for a BMC AMI 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 AMI products:

      F cmscname,PARMLIB REFRESH

   Warning

   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

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.

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 AMI DevX File-AID/MVS

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 AMI DevX File-AID/Data Solutions

UDASPF

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 AMI DevX File-AID/RDX

BMC AMI DevX File-AID for Db2

BMC AMI DevX File-AID for IMS

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:

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: