Installation Checklist

Use the following checklist as you proceed through the installation.

  1. Configure the FDRTCT User and Define Security Definitions (New Install ONLY)
  2. Prepare for Product Installation
  3. Download the Installer to USS
  4. Product Installation via OMVS
  5. Change to Working Directory
  6. Product Installation

Configure the FDRTCT user and define security definitions

New install ONLY - upgrade should skip this section.

FDRTCT runs as a started task with it’s program on USS; thus the FDRTCT userid requires an OMVS segment with appropriate information and started task authority. This is the basic information needed by the FDRTCT user profile:

1.Since FDRTCT runs as a started task under USS, you need to define a CA ACF2, IBM RACF, or CA TOP SECRET userid/acid with an OMVS segment. Specify the OMVS attributes of UID, HOME, and PROGRAM for FDRTCT. A TSO segment is also needed.

ADDUSER fdrtct OMVS(AUTOUID HOME(‘/usr/lpp/fdrtct’) PROGRAM(‘/bin/sh’)) TSO

Important

  • This ID requires an OMVS segment.
  • It is suggested that the ID not have a password, but that is a customer decision.
  • This ID requires read/write access to the FDRTCT installation directory.
  • Associate the RACF userid to be used at FDRTCT Server PROC Start.

The HOME directory should be the directory you intend to install FDRTCT. This directory is referred to as the installation directory from this point on. This path is important in Download the Installer to USS section.

2.Create an IBM RACF STARTED class entry for a Started Task PROCs named FDRCTSRV and FDRCTUTL. Here is an example of a RACF RDEFINE commands to do this. Please consult with your system security personnel for alterations to this or for CA ACF2 or CA TOP SECRET instructions and procedures.

RDEFINE STARTED FDRCTSRV.* UACC(NONE) STDATA(USER(fdrtct) GROUP(stcgrp) TRUSTED(YES) PRIVLEDGED(NO) TRACE(NO))

RDEFINE STARTED FDRCTUTL.* UACC(NONE) STDATA(USER(fdrtct) GROUP(stcgrp) TRUSTED(YES) PRIVLEDGED(NO) TRACE(NO))

Important

The TRUSTED attribute can be assigned to started tasks and address spaces. Doing so allows the started procedure or address space to bypass RACF authorization checking and to successfully access or create any resources it needs.
A trusted started procedure or address space is treated as a z/OS UNIX superuser if a z/OS UNIX user identifier (UID) is assigned to it in the OMVS segment, even when the assigned UID is not 0.

3.Refresh the RACF Started Class Profiles via the SETROPTS command, again consult your system security personnel for CA ACF2 or CA TOP SECRET command syntax:

SETROPTS RACLIST(STARTED) REFRESH

4.Define the following RACF resource classes:

  • STGADMIN.ADR.CREATE.CLOUD – For the CREATE command.
  • STGADMIN.ADR.DELETE.CLOUD – For the DELETE command.
  • STGADMIN.ADR.INFO.CLOUD – For the INFO command.
  • STGADMIN.ADR.LIST.CLOUD – For the LIST and FIND commands.

Prepare for product installation

The installation package (fdrct.tar.gz) must be moved to a USS file system on the mainframe where FDRTCT is to be installed. Installation is done via OMVS running on the mainframe.

  • Download the distribution package (fdrct.tar.gz) from Compuware. The installation package is located in the BMC Support Center for product FDR in the Additional Resources section of the Product Home tab.
  • Ensure Java 1.8+ is installed

Use TSO OMVS for access to the z/OS shell to install FDRTCT.

  • ISPF Option 6: OMVS or
  • TSO READY prompt: OMVS

In the OMVS environment, verify the installed version of Java with the command:

java -version

The first 3 lines of the response looks similar to the following. The Java version shown in the first line needs to be higher than “1.8.0”.

1 java version "1.8.0_211"

2 Java(TM) SE Runtime Environment (build 8.0.5.37 - pmz6480sr5fp37-20190618_01(SR5 FP37))

3 IBM J9 VM (build 2.9, JRE 1.8.0 z/OS s390x-64-Bit Compressed References 20190617_419755 (JIT enabled, AOT enabled)

  • Ensure you have update access to the PROCLIB library where you wish to install the FDRTCT started task JCL procedures.

Download the installer to USS

Important

  • The userid performing this configuration needs SUPERUSER authority.
  • The root file system must be R/W to add the /usr/lpp/fdrtct directory.
  • If not already created, create the FDRTCT installation directory.

mkdir /usr/lpp/fdrtct mode(7,5,5)

chmod -R 755 /usr/lpp/fdrtct

1.Open a command prompt (Windows Command Prompt or Windows PowerShell) on your workstation.

2.Navigate to the location of the installer file (fdrct.tar.gz) that was saved in Step 1.

3.Initiate a FTP session to the mainframe where FDRTCT is being installed.

FTP <host_name or IP addr of the LPAR you wish to FTP the file to>

4.Provide your user id and password when prompted.

5.Ensure you are in binary mode before transferring the installation file).

bin

6.FTP the downloaded installation file into the directory you wish to install FDRTCT. Using the installation directory of /usr/lpp/fdrtct, an example of the FTP command is:

put "C:\Downloads\fdrct.tar.gz" "/usr/lpp/fdrtct/fdrct.tar.gz"

7.Terminate your FTP session..

FTP installer from PC to USS file system

C:\> ftp cpu.idp.com
Connected to cpu.idp.com.
220-ENFTP001 IBM FTP CS V2R3 at CPU.IDPNJ.COM, 21:47:13 on 2018-11-09.
220 Connection will close if idle for more than 240 minutes.
501 command OPTS aborted -- no options supported for UTF8
User (cpu.idp.com:(none)): user
331 Send password please.
Password:
230 USER is logged on. Working directory is "USER.".
ftp> binary
200 Representation type is Image
ftp> put "C:\Downloads\fdrct.tar.gz" "/usr/lpp/fdrtct/fdrct.tar.gz"
200 Port request OK.
125 Storing data set /usr/lpp/fdrtct/fdrct.tar.gz
250 Transfer completed successfully.
ftp: nnnnnnnn bytes sent in n.nn Seconds nnnnn.nnKbytes/sec.
ftp> quit

Product installation via OMVS

Important

se TSO OMVS for access to the z/OS shell to install FDRTCT.

  • ISPF Option 6: OMVS or
  • TSO READY prompt: OMVS.

Sample OMVS Command Initiation

IBM
Licensed Material - Property of IBM
5650-ZOS Copyright IBM Corp. 1993, 2017
(C) Copyright Mortice Kern Systems, Inc., 1985, 1996.
(C) Copyright Software Development Group, University of Waterloo, 1989.


U.S. Government Users Restricted Rights -
Use,duplication or disclosure restricted by
GSA ADP Schedule Contract with IBM Corp.


IBM is a registered trademark of the IBM Corp.


USER:/usr/user: >



===>
INPUT
ESC=¢ 1=Help 2=SubCmd 3=HlpRetrn 4=Top 5=Bottom 6=TSO 7=BackScr 8=Scroll
9=NextSess 10=Refresh 11=FwdRetr 12=Retrieve

Change to working directory

Return to the OMVS session and change the working directory so you are in the installation directory. Assuming the installation directory is /usr/lpp/fdrtct, an example of the command:

cd /usr/lpp/fdrtct

Continue to Product Installation.

Product installation

1.Untar the installation tar file with the following commands:

cd /usr/lpp/fdrtct

tar -xcf fdrct.tar.gz

This tar file contains the following product files:

  • FDRCTSRV_PROC – sample z/OS Started Task PROC for the FDRTCT server.

    //FDRCTSRV PROC OUT=X
    //*
    //CTSRV EXEC PGM=BPXBATSL,REGION=0M,DYNAMNBR=100
    //STDOUT DD SYSOUT=&OUT
    //STDERR DD SYSOUT=&OUT
    //SYSPRINT DD SYSOUT=&OUT
    //STDPARM DD PATH='/var/fdrct/stdparmsrv'
    //STDENV DD PATH='/var/fdrct/stdenvsrv'

  • FDRCTUTL_PROC – sample PROC for the FDRTCT management/reporting utility executed in batch.

    //FDRCTUTL PROC OUT=X
    //*
    //CTUTL EXEC PGM=BPXBATSL,REGION=0M,DYNAMNBR=100
    //STDOUT DD SYSOUT=&OUT
    //STDERR DD SYSOUT=&OUT
    //SYSPRINT DD SYSOUT=&OUT
    //STDPARM DD PATH='/var/fdrct/stdparmutl'
    //STDENV DD PATH='/var/fdrct/stdenvutl'
  • fdrctsrv.jar – Server Started Task code.
  • fdrctutl.jar – Management/Reporting Utility code.
  • genkeystore – Script to generate a certificate keystore.
  • libASCBJNI64.so – Required assembly subroutines used by both the Server started task and the Utility.
  • stdenvsrv – Environment variables for the Server Started Task.
  • stdenvutl – Environment variables for the batch Management/Reporting Utility.
  • stdparmsrv – BPXBATCH invocation command for the Server Started Task.
  • stdparmutl – BPXBATCH invocation command for the batch Management/Reporting Utility.
  • template_config.txt – Configuration file for the Server Started Task and Batch Utility.

2.During the following installation procedure, these two files are created:

  • ds800.cer – example name of the input file to hold the certificate.
  • fdrctkeystore – fixed name generated by genkeystore script.

3.Obtain the connection certificate from the DS8800 (Instructions are in the IBM manual IBM DS8000 and Transparent Cloud Tiering (SG24-8381.02) – Chapter 5. The installation instructions will refer to this file as ds800.cer.

4.Generate – get prompt of “Y”.

5.Customize the FDRCTSRV PROC.

  • The fully-qualified install path to the stdparmsrv file should be specified on the STDPARM DD statement. The filename portion should remain unchanged.
  • The fully-qualified install path to the stdenvsrv1 file should be specified on the STDENV DD statement. The filename portion should remain unchanged.

6.Place the FDRCTSRV and FDRCTUTL PROCs into an appropriate z/OS PROCLIB.

7.Customize the PGM command line containted within the stdparmsrv and stdparmutl files as follows:

PGM /usr/lpp/java/J8.0_64/bin/java -Xms256m -Xmx1096m -jar /var/fdrtct/fdrctsrv.jar

vChange the path to the Java program to the correct fully-qualified path.

vChange the path to the fdrctsrv.jar file to the correct fully-qualified path.

Make the same changes to stdenvutl.

8.Customize the stdenvsrv and stdenvutl file contents LIBPATH to point to the installation path.

9.Start the FDRCTSRV Started Task. It will quickly start and then end. The following should appear in the JESLOG output.

+FDR/CTSrv - Starts +FDR/CTSrv - Configuration file ‘/var/fdrtct/Compuware/FDRTCT/config.txt’ does not exist +FDR/CTSrv - Please configure/edit your settings and Save As filename ‘config.txt’ +FDR/CTSrv - in that directory before re-starting FDRCTSrv +FDR/CTSrv - Ends

Important

The /var directory structure that was created and perform the steps as outlined in the messages

10.Customize the /var version of the template_config.txt created in the previous step:

  • LISTENING_IP – This parameter can be ignored.
  • LISTENING_PORT=1900 – This parameter can be ignored.
  • STORAGE_ARRAY_IP=COMPANY8886.company.com – Set this parameter to the DNS name or IP address of the DS8800 Storage Array.
  • STORAGE_ARRAY_PORT=8452 – This parameter is the PORT number of the Cloud Tiering services on the DS8800 Storage Array. This sample value is IBM’s default value. Consult your storage array administrator for the proper value.
  • CLOUD_NAME=MyCloudName – This value should be customized after consulting with your DS8800 storage administrator.
  • CLOUD_USER=MyCloudUser – This value should be customized after consulting with your DS8800 storage administrator.
  • CLOUD_PASS=MyCloudPassword – This value should be customized after consulting with your DS8800 storage administrator.
  • SSL=Y/N – Method to use to connect to the storage array.

SSL=Y – for IBM DS8nnn arrays

SSL=N – for EMC arrays

11.You may now start your FDRCTSRV Started Task. It should stay running. Typical output on JESLOG DD should be similar to:

Starts... Running as jobname: FDRCTSRV - Use this name for STOP/MODIFY

 

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