FATS/FATAR/FATSCOPY Installation – The install package is downloaded from the FTP site using instructions supplied in an order acknowledgment email.

Implementation instructions

With the electronic installation, instructions are sent in an e-mail for installing the libraries. The e-mail installation instructions supersede these example instructions and should be used if any differences are noted.

The order acknowledgment e-mail looks similar to:

This e-mail contains the product(s) and version(s) that are included in the install package, the expiration date (if the product has an expiration date), and a unique IDPREC password that is required for the install process.

Follow INSJVL.TXT instructions

Follow the instructions as directed in the INSJCL.TXT file included in the acknowledgment e-mail to retrieve the product package from the FTP site.

(Step “B” of the INSJCL.TXT file)

Expanding the product distribution file on your z/OS host is a two-step process. Login to your z/OS host and enter a TSO READY session (outside of ISPF). This TSO session must have access to an ISPF environment because the z/OS install process expects to employ ISPF panels to complete the installation. The steps described here assume TSO PROFILE NOPREFIX is NOT used.

If your site uses PDSFAST in place of IEBCOPY, ensure that you disable PDSFAST prior to this step so that you do not get a FATSCOPY error from PDSFAST. PDSFAST can be disabled by issuing the TSO ALLOC command:

1. Enter:

   RECEIVE INDATASET(FAT.BIN)

   where the INDATASET(…) value is the name that you created during the file transfer to z/OS.

   This creates a partitioned data set containing two load modules. After the RECEIVE is completed, the name of the PDS is “userid.IDPREC.LOAD”. If you want a different name, then at the prompt:

   Dataset FATSYS.IDPREC.LOAD from FATCFG on JESCPUA
   Enter restore parameters or 'DELETE' or 'END' +

   enter:

   DSN(desired.name)

   or take the default by pressing Enter.

2. Enter:

   CALL 'userid.IDPREC.LOAD(IDPREC)'

   or, if you gave the PDS a different name:

   CALL 'dsname(IDPREC)'

   A welcome message is displayed. Enter appropriate responses to data set name and SYSOUT class prompts.

   You are also prompted to enter the 16 digit IDPREC PASSWORD supplied in the Order Acknowledgment (first) e-mail.

   Follow the instructions on the ISPF panel to complete the installation of the distribution files.

IDP Product Install (Screen1)

This screen allows the specification of the data set names that are used for the data sets being loaded from the install package. These may be existing data sets to be updated, or they may be new data sets that are allocated and cataloged (new data sets are recommended).

IDP Product Install (Screen1)

The names shown above are the default names provided by the IDPREC Install program (when the default user IDP was used). You may change these names in one of two ways:

1. To change the High or 2nd Level qualifiers for all data sets, change the values in the corresponding field for the Output DSN section.
2. To change an individual Low Level qualifier, change the desired Low Level Qualifier for the data set(s) that you want to change.

The resulting data set names that are used are displayed at the bottom area of the panel.

You can also specify the SMS attributes (if they are to be SMS-managed) or VOLUME/UNIT information on this panel to allocate these data sets when creating them as NEW.

IDP product install (Screen2)

The following figure documents the process that is used to create the product libraries. When you press ENTER to continue, it also shows you the status of each of the data sets being created. Once the product libraries have been created, a completion message is displayed.

IDP Product Install (Screen2)

IDP product Install (Screen3)

The following figure documents that all the product libraries have been created and received and you can now go to the Primary Options Menu to continue the installation process and customize the product.

IDP Product Install (Screen3)

Once you have successfully transferred the FAT.BIN file to your z/OS mainframe, you can continue with Customizing FATS, FATAR, and FATSCOPY.

Activating the tape management interface

Please 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.

Customizing FATS, FATAR, and FATSCOPY

Displaying and modifying FATSCOPY defaults

The default values of many FATSCOPY’s COPY/SIM keywords are stored in the FATSCOPY Global Options Table. The original values of these defaults are shown as “delivered defaults” in the keyword descriptions in COPY/SIM Statement. Each FATSCOPY job reads this table to determine the current default values for each keyword.

The current default values can be displayed and changed using the FATZAPOP program that is provided with FATSCOPY. The keywords for which the default values can be changed are listed COPY/SIM Statement with asterisks (*), and are also listed below. FATZAPOP displays and/or modifies the FATSCOPY Global Options Table.

You must run FATZAPOP at least one time to define your tape management system to FATSCOPY, as described Activating the Tape Management Interface.

FATZAPOP JCL

To execute FATZAPOP as a batch job, use the following JCL:

FATZAPOP will write messages and a report to SYSPRINT.

Copy Options from a Previous Version (4.9.26 Or Later)

When you upgrade to a new release of FATSCOPY you will usually want to copy all FATSCOPY default options from the version that you are currently using. FATZAPOP’s COPY command statement will copy all defaults from the library whose DD statement is the operand of the FROMDD= keyword:

You can copy default options from releases 4.9.26 or later. Earlier versions of FATSCOPY  did not have an Option Table from which to copy values.

FATZAPOP Command Statements

The following command statements can be used with the FATZAPOP program:

• COPY ALL,FROMDD=oldlibrarydd – Copy default values from another version of FATSCOPY. This is described in detail above.
• ZAP keyword1=value1,keyword2=value2,… – Changes the default value of each option to the new value. Multiple ZAP command statements may be specified. In most cases, except at noted below, the allowed keywords and values for ZAP are the same as the corresponding keywords and values for the FATSCOPY  COPY/SIM statement.
• PRINT – Display the current values of all options in the FATSCOPY Global Options Table. Values that have been changed from their delivered defaults (the values shown COPY/SIM Statement section) will be marked with asterisks.
• AUDIT – Display the current values of the options in the FATSCOPY Global Options Table that have been changed from their delivered defaults. Options that have not had their values changed will not be displayed.
• RESET – Resets the values of all options in the FATSCOPY Global Options Table to their delivered default values. The resulting defaults will all match the values shown in this space unless RESET is followed by ZAP statements.

Setting Defaults with the ZAP Statement

The following FATZAPOP keywords are used with the ZAP command statement to save FATSCOPY defaults in the Global Options Table:

• To set “ABEND” as the FATSCOPY default, use ZAP ABEND=U0888. Or, to set “RETCODE” as the FATSCOPY default, use ZAP ABEND=RETCODE. (You cannot use ZAP RETCODE.)
• To set “SUPULAB” as the FATSCOPY default, use ZAP SUPULAB=YES. Or, to set “NOSUPULAB” as the FATSCOPY default, use ZAP SUPULAB=NO. (You cannot use ZAP NOSUPULAB.)
• ZAP EXCLUDE=dsn is used to save a DSN/mask into the Option Table that will prevent FATSCOPY from selecting a data set matching that name or mask. Up to 15 EXCLUDE defaults may be specified. ZAP UNEXCLUDE= is used to remove an existing EXCLUDE entry from the Option Table.
  
  To exclude or un-exclude multiple DSNs or masks, you may specify multiple ZAP statements, or you may specify a list of DSNs/masks on a single ZAP statement, enclosed in parentheses and separated by commas.
  
  Example:
  ZAP EXCLUDE=(NOT.THESE.**,NOT.THOSE.**)
• If you are using Control-M/Tape tape management, you must specify several data sets from your Control-M/Tape configuration:
  • CTTIOAPARM= Control-M/Tape IOA.PARM library name
  • CTTIOAENV= Control-M/Tape IOA.IOAENV library name
  • CTTMDB= Control-M/Tape Media Database Data File name
  • CTTMDI= Control-M/Tape Media Database Index File name
  • CTTSTKD= Control-M/Tape Stacking Statistics Data File name
  • CTTSTKI= Control-M/Tape Stacking Statistics Index File name
  • CTTTRC= Control-M/Tape Trace File name

To set value to a blank, code ‘ ‘ (single quote, blank, single quote) after the equals sign.

Example: ZAP HSMMIGMASK= ‘ ‘

Use ZAP VMFDSN=tlms.vmf.name only when you have TLMS tape management, as described Activating the Tape Management Interface.

You should carefully consider the implications of changing the defaults for CAT, TMSINPUT, and SORT. It is recommended to not changing the defaults for these three parameters. Changing these defaults may result in unexpected results for the cataloging (CAT) and retention (TMSINPUT) of data sets, and in the number of tape mounts required (SORT).

FATZAPOP Example

The following example sets the tape management interface to RMM, and then changes the default values for MULTIFILE, ECHO, and ABRARC. It also uses PRINT to display the new default values for all the options in the Global Options Table.

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

ICL (Installation Control Library) 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 panel 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.

Changing the Dialog Library Names

During the installation with the FATLOAD program, the names of the FATS/FATAR dialog libraries are automatically changed in the CLIST library to the names you specified on the installation screens. If you later change those names, or if you manually loaded the dialog libraries, you can correct the dialog to use the proper names by editing member FATALLOC in the FATS/FATAR CLIST library. Change the appropriate CLIST lines to specify the new data set name(s):

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 FATSFATR CLIST for this purpose. The table library must be allocated before FATSFATR 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.