Once you have successfully installed FATS on your z/OS mainframe, you can continue configuring FATS, FATAR, and FATSCOPY.

This section contains the following topics:

Managing the FDR service address space

This section describes the process of managing the FDR service address space.

Manage the FDR service address space (FDRMAIN)

The FDR service address space (FDRMAIN) runs as a started task and is used by most of the BMC AMI Storage FDR products. This address space provides services and facilitates communication with other FDR service address spaces on other local and remote systems.

Start FDRMAIN

To start FDRMAIN.

1. Verify that the JCL for the FDRMAIN started task procedure exists. Creating the FDRMAIN startup procedure describes the JCL for creating the FDRMAIN started task procedure. By default, the FDRMAIN started task procedure that is created during the installation configuration is called FDRMAIN. Your site might have defined a different FDRMAIN procedure name and library.
2. From the operator console, enter the START command.
   • S procname[.id][,REUSASID=YES]
3. The following console message confirms that FDRMAIN was started successfully:

Create the FDRMAIN startup procedure

To create an FDRMAIN startup procedure:

1. Copy the FDRSAMP member FDRMAIN to PROCLIB or another system procedure library and rename this to an appropriate started task procedure name.

2. Follow the instructions at the top of the member to modify the procedure to your site requirements.

   Warning

   Important

   The default started task name for the FDR main task is FDRMAIN, you can rename this name as per your installation standards.

3. (Optional) Define the FDRMAIN started task procedure to your IPL procedure so that it starts at system initialization. 

FDRMAIN started task procedure statements

The following table describes the list of procedure statements for FDRMAIN started tasks.

Activating the tape management interface

Note: This procedure replaces the tape management installation procedure used by FATAR and FATSCOPY in version 4.9.25 and previous versions. You no longer run an assembly job using member ASMCA1, ASMTLMS, or ASMRMM. Those members are no longer provided.

• For 

  FATSCOPY

   , installation of the tape management interface is REQUIRED.

• The tape management interface is optional for FATAR, and is used by the FATAR ISPF dialogs to query tapes to be processed. Details on this interface are in Tape Management System Support.
• If you are licensed for only FATS, you will not use a tape management interface and can skip this section.

IBM’s DFSMSrmm (RMM), BMC’s Control-M/Tape, CA Technologies’ CA 1 (TMS) and TLMS, and ASG’s Zara are supported by FATAR and FATSCOPY.

Activating the interface

There are two ways to activate the tape management interface: using the ISPF Dialog, or with a batch job.

If you are going to install the ISPF dialog, you may proceed to Installing the ISPF Dialog to install it.

Otherwise, to activate the tape management interface with a batch job, run the FATZAPOP program that is provided with FATAR and FATSCOPY. FATZAPOP (fully described Displaying and Modifying FATSCOPY Defaults) is a program that can optionally be used to set many FATSCOPY defaults. However, to define your tape management system to FATAR or FATSCOPY, it must be run it at least once with the ZAP TMSIN= statement to define your tape management system to FATAR or FATSCOPY. For FATSCOPY , this is a required step.

Run the following job to activate the tape management interface. Substitute the name of your tape management system for "tapemgt". Use the ZAP VMFDSN= statement only if you are using TLMS tape management, using the name of your TLMS Volume Master File. Use the CTT* parameters only if you are using Control-M/Tape tape management. Additional FATZAPOP command statements, described in Section 90.4.1, may be added to this job but are not required. (This job can be found in the EX900301 member of the JCL library.)

Testing the interface

You can quickly test the tape management interface using a test program, FATTMTST. The JCL is simple:

The parameter (PARM=volser) is a tape volume serial. FATTMTST will use the tape management interface to query that volume and will print out the data set name on the volume. If the tape has multiple files on it, all tape files are listed. If the tape is part of a multi-volume tape set, all volumes in the set (and all data sets on the set) are listed. If the volume serial is not recorded in your tape management database, you will get a return code of 12. If you get other return codes, abends, or unexpected results, please contact BMC support for assistance.

Proceed to the next section for product customization.

Security

By default, FATAR and FATSCOPY will do security checks on input data sets. It will verify that users have READ authority to each input data set in the DATASET class. This prevents users from using FATAR to access data to which they are not authorized, especially on multi-file tapes, and prevents FATSCOPY from selecting tapes for which the user does not have at least READ authority. More details are found in FATAR Security and FATSCOPY Security. If you do not want to do this data set security check, you have two options:

1. You can apply FATAR/FATSCOPY custom zap C-49.0002 to disable the security check (contact BMC support for assistance); or
2. You can define security resource FATAR.DATASET.SECBYPAS (for FATAR) or FATSCOPY.DATASET.SECBYPAS (for FATSCOPY) in class FACILITY and give all users READ authority to it.

By default, all users can use all functions and options of FATS, FATAR, and FATSCOPY. If you want to restrict certain users from using certain functions, you must apply the FATS/FATAR/FATSCOPY custom zap C-49.0001 and define FACILITY class resources in your security system to control each function, as described in FATS Security, FATAR Security, and FATSCOPY Security.

Optional modules and tables

FDR Installation FDRSAMP contains three source modules that you may wish to modify and assemble.

Member OPENEXIT is a sample FATAR Open exit. Use of the Open exit is documented in Output Tape Processing and is controlled by operand EXIT= documented in Miscellaneous Operands.

Member FATCHTAB is a sample FATAR printer translate table. Use of the translate table is documented under the CHARTAB= operand in Print Control Operands.

Member ASCIITRS is a sample FATAR ASCII translate table, containing a table for translation of ASCII to EBCDIC and another for EBCDIC to ASCII. Use of the translate table is documented under the ASCII= operand in Print Control Operands.

At this point, installation of the batch function of FATS, FATAR, and FATSCOPY is complete. If you wish to install the ISPF panels, continue to the next section.

Installing the ISPF dialog

The FATS/FATAR ISPF dialog can be invoked at any time, from any TSO userid that is authorized to read the FATS/FATAR dialog libraries, by going to ISPF option 6 (TSO COMMAND) and entering:

Since this can be awkward, two convenient alternatives are available:

Adding FATS/FATAR to a menu

You may add FATS/FATAR as an option on the ISPF main menu or any menu of your choice. In the FATS/FATAR FDRSAMP data set, there are two example panels showing how to add FATS/FATAR to the ISPF main menu:

You can make similar modifications to your ISPF main menu (panel ISR@PRIM) or to any other ISPF menu.

Adding FATS/FATAR as a command

You can add a FATS/FATAR command to the ISPF command table (ISPCMDS) by going to ISPF option 6 (TSO COMMAND) and entering:

The modified command table will be stored in the first library in the ISPTLIB concatenation for this TSO userid. If the user has a private table library, it will normally be the first one in that concatenation, so the updated command table will be available only to this user. If the user does not have a private library, but has update authority to the first public library in ISPTLIB, it will be updated, and will be available to any userid using that library. However, you will have an option to specify a different table library before it is actually stored. If you do choose a different table library, that library will have to be in the ISPTLIB concatenation, prior to any other library containing a table called ISPCMDS. The FATS/FATAR dialog can now be entered from almost any ISPF panel by entering FATS on the command line.

Adding or changing the Dialog Library Names

During installation, by default the name of FATS/FATAR dialog libraries are not automatically set in the CLIST library member FATALLOC to the names you specified during the installation process. If you need to add or change those names, or if you manually loaded the dialog libraries, you can update library names by editing the member FATALLOC in the FATS/FATAR CLIST library. Update the appropriate CLIST lines to specify the new data set names:

• CLIST FATS/FATAR ISPF Dialog CLIST Library
• LLIB FATS/FATAR Load Module Library
• PLIB FATS/FATAR ISPF Dialog Panel Library
• MLIB FATS/FATAR ISPF Dialog Message Library
• SLIB FATS/FATAR ISPF Dialog Skeleton Library
• TLIB FATS/FATAR ISPF Dialog Table Library

Do not modify the FATSF@TR CLIST for this purpose. The table library must be allocated before FATSF@TR is invoked.

Authorizing programs under TSO

If you want to use the FATSCOPY panels to do foreground simulations, you need to modify member IKJTSOxx in SYS1.PARMLIB. An entry needs to be added to the AUTHTSF, AUTHCMD, and AUTHPGM tables for program FATSCOPY.

Define JCL parameters

Each ISPF panel user must define the JCL parameters to be used for FATSCOPY jobs in their ISPF profile. From the Main Menu, select Option “J – JCL PARMS”. Enter any JOB statement parameters required by your installation for running FATSCOPY batch jobs. If FATSCOPY  is in the system link list, no Load Library is required; if not, provide the name of the FATS/FATAR/FATSCOPY load library. You can also change the parameter for SYSOUT= statements. Enter END to save these values to the ISPF profile for your userid.

If you are using FATAR or FATSCOPY, the interface for the tape management system you are using must be activated (usually, by the system administrator or system programmer) before any FATAR or FATSCOPY  jobs are run. If a FATZAPOP batch job has already been run to activate it, you can skip this step.

Select Option “S - SETOPT” from the Main Menu, then select “2 – Miscellaneous Options” on the following panel (Set FATSCOPYGlobal Options Primary Menu), and enter the name of your tape management system (RMM, CA1, CTLT, ZARA, or TLMS) in the TMSIN section of the panel.

Using the dialog to activate the tape management interface

If you are using TLMS tape management, enter F3 to return to the Set FATSCOPY Global Options Primary Menu, then “4 – Data Set Names and Masks”, and then enter the name of your TLMS Volume Master File in the VMFDSN field.

Enter F3 to return to the Set FATSCOPY Global Options Primary Menu. Be sure the correct library is entered in the FATSCOPY LIBRARY field, and enter SAVE on the command line to save your tape management values.

At this point, installation of the ISPF panels is complete.