FDRWEB Installation

Overview

FDRWEB is an interactive, browser based, web application that provides users with insight into their z/OS DASD and TAPE storage configuration and usage through an intuitive, easy to use graphic interface. FDRWEB allows users to gather data from a variety of sources, and generate detail as well as summary reports relating to their z/OS DASD and TAPE storage. FDRWEB can, optionally, provide its output as CSV files that can be downloaded, allowing easy import by other programs for analysis or charting, such as Microsoft Excel.

FDRWEB runs as a standalone task, using the Java virtual machine under Unix System Services (USS). It requires a dedicated FDRWEBuser to be created with an MVS segment in order to run properly.

System requirements

Minimum software requirements (z/OS):

• ABR or FDREPORT—FDRWEB requires ABR or FDREPORT version 5.4/87 or higher.
• zFS File System—For the code and the database.

• JAVA—

  FDRWEB

   requires JAVA 8.0 or higher.

Web application requirements:

Browser Support—FDRWEB supports most browsers (Chrome, Edge, Firefox) that support the current features of HTML5 and CSS.

Installation

Installation Checklist

Use the following checklist as you proceed through the installation:

Step 1: [ ] Configure the FDRWEB User (New Install ONLY)

Step 2: [ ] Configure the FDRWEB File System (New Install ONLY)

Step 3: [ ] Prepare for Product Installation

Step 4: [ ] Download the Installer Script to USS

Step 5: [ ] Change to Working Directory

Step 6: [ ] Continue to Product Installation

Step 7: [ ] FDRWEB is installed. Proceed to Starting and Stopping FDRWEB

Configure the FDRWEB User

New Install ONLY – Upgrade should skip this section.

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

1. Since FDRWEB 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, PROGRAM, and ASSIZEMAX for FDRWEB. A TSO segment is also needed. 
   ADDUSER fdrweb OMVS(AUTOUID HOME(‘/usr/lpp/fdrweb’) PROGRAM(‘/bin/sh’) ASSIZEMAX(2147483647)) TSO

   Warning

   Important

   • The HOME directory should be the directory you intend to install FDRWEB. This directory is referred to as the installation directory from this point on. This path is important in Download the Installer Script to USS section.
   • The JVM will fail to start if the MAXASSIZE for the FDRWEBuser ID is too small. The recommended minimum for Java is 2,147,483,647. The MAXASSIZE parameter in the BPXPRMxx parmlib member sets the system-wide default and can be overridden by the ASSIZEMAX variable in the OMVS security profile segment on a per application basis.
     However, the IEFUSI and IEALIMIT installation exits can control region size and memory above the bar. These exits may override this value and prevent Java from initializing.

2. Create an IBM RACF STARTED class entry for a Started Task PROC named FDRWEB. Here is an example of a RACF RDEFINE command 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 FDRWEB.* UACC(NONE) STDATA(USER(fdrweb) GROUP(stcgrp) TRUSTED(YES) PRIVLEDGED(NO) TRACE(NO))

   Warning

   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

Configure the FDRWEB file system

New install only – upgrade should skip this section.

Allocate and initialize a zFS file system, create the mount point to be used for the FDRWEBcode and database, and create the directory FDRWEB in the root file system.

Update the BPXPRMxx member with the same operands specified in the MOUNT step above to MOUNT the FDRWEBFile System across system IPLs.

Prepare for product installation

The installation file (fdrweb-installer<ver>.tar) must be moved to a USS file system on the mainframe where FDRWEB is to be installed. Installation is done via OMVS running on the mainframe.

• Download the installation package from the BMC Support as directed by the BMC Order email.

• Ensure that there is sufficient available memory to have JVM start up properly. Issue the following commands to set the hard and soft limits for the address space.
  
• ulimit -HA 500000
  
• ulimit -SA 500000
  
• Ensure Java 8+ is installed
• Use TSO OMVS for access to the z/OS shell to install FDRWEB.
  
  • 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 FDRWEBstarted task JCL procedure.
  

Download the installer script to USS

1. Open a command prompt (Windows Command Prompt or Windows PowerShell) on your workstation.
   
2. Navigate to the location that the fdrweb-installer<ver>.tar file is located.
   
3. Initiate a FTP session to the mainframe where FDRWEB 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 package (fdrweb-installer<ver>.tar) into the USS directory you wish to install FDRWEB. Using the installation directory of /usr/lpp/fdrweb, an example of the FTP command is:
   put "C:\Downloads\fdrweb-installer<ver>.tar" "/usr/lpp/fdrweb/fdrweb-installer<ver>.tar"
7. Terminate your FTP session.

If you are unable to directly FTP this file onto your system, please contact BMC Support for assistance.

Product installation via OMVS

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

• 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/fdrweb, an example of the command:

cd /usr/lpp/fdrwebContinue to Product Installation.

Product Installation

Unpack the tar file using the command:

tar -xvf fdrweb-installer<ver>.tarThis unpacks the FDRWEBinstaller (im.sh).

The installation manager is used install the main FDRWEBHub and the auxiliary FDRWEBNodes. The FDRWEBHub should be installed on only one LPAR in your system. The FDRWEBHub can submit jobs to the LPAR it is running on without an FDRWEBNode. Jobs can be submitted to other LPARS by installing an FDRWEBNode on the target LPAR and connecting it to the Hub via the Administrator Panel (see “Configuration – LPARS” subsection of Section 3).

To install an FDRWEB Hub, run the distributed im.sh file, select option 1 in the installation manager, and follow the on-screen prompts. At any prompt, enter quit to stop the installation process.

Running the automatic installer

Continue to HTTPS Setup for FDRWEBas described in the following section.

HTTPS Setup for FDRWEB

This step is Optional.

To enable HTTPS, select the Enable HTTPS option from the FDRWEB Installation Manager.

Sample HTTPS Setup for FDRWEB

• The user will not be able to use a commercial CA unless FDRWEBis available on a domain that the customer publicly owns.
  

• The user will need to add https:// in front of the FDRWEBURL.
  

Continue to Install on Other LPARs (Nodes).

Install on other LPARs (Nodes)

The main FDRWEB installation detailed in Product Installation installs the FDRWEBHub, which acts as the host or “master” installation. The FDRWEBHub allows users to submit and retrieve jobs on the LPAR the Hub is installed on. In order to submit and retrieve jobs on other LPARs, an FDRWEBNode must be installed on the desired remote LPARs.

An FDRWEBNode is meant to be installed on an LPAR which does not have an FDRWEBHub. Nodes cannot be used to run an instance of FDRWEB and are instead meant to be connected to an FDRWEBHub. Once a Node is installed on an LPAR and connected to the Hub, the Hub can submit jobs and retrieve output from the LPAR.

To install an FDRWEB Node, run the distributed im.sh file, select option 2 in the installation manager, and follow the on-screen prompts. At any prompt, enter quit to stop the installation process.

Running the automatic installer

Once the node is installed, and the started task has been started on the LPAR, proceed to “Configuration - LPARs” on page 3-22 to connect Nodes to the FDRWEB Hub.

Starting and stopping FDRWEB

• Start the FDRWEB Started Task: S FDRWEB

• Stop the FDRWEB Started Task: P FDRWEB

FDRWEBwill be available at the port specified in the PORT=nnnn parameter of the FDRWEBPROC. If, for example, the IP address of the system FDRWEB is installed on is 192.168.1.1 and FDRWEB is running on port 4444, then FDRWEBis accessible from a web browser at the following address:

http://192.168.1.1:4444/FDRWEBmay be slow for the first few minutes of use after installation, as it takes time for FDRWEBto build the necessary indexes in the database for fast response times.

If any errors occur, they are displayed in log files present in the $FDR_HOME/logs directory. Contact BMC Support  in such a case with these log files, as well as the installer.log file that was produced by the automatic installer.

The default procs installed by the FDRWEBInstallation Manager (fdrweb_ver_im.sh) on the LPAR that hosts FDRWEBare:

• FDRWEB

  //*
  //FDRWEB PROC
  //*
  //* PROC FDRWEB STARTED TASK
  //*
  //START EXEC FDRWEBP,VERSION=’86’,PORT='4444'
  //*
  //STDENV DD PATH='/usr/lpp/fdrweb/env/FDRWENV'

• FDRWEBP

  //*
  //* JVM PROC CALLED BY THE FDRWEB STARTED TASK
  //*
  //FDRWEBP PROC LEPARM='',
  // JAVACLS='com.idp.fdrweb.FDRWebServer',
  // PORT='4444',
  // LEPARM='TERMTHDACT(UADUMP)',
  // VERSION='86',
  // LOGLVL='+I',
  // OUT=X
  //*
  //FDRWEBP EXEC PGM=JVMLDM&VERSION,REGION=0M,
  // PARM='&LEPARM/&LOGLVL &JAVACLS &PORT'
  //SYSPRINT DD SYSOUT=&OUT
  //SYSOUT DD SYSOUT=&OUT
  //STDMSG DD SYSOUT=&OUT
  //STDOUT DD SYSOUT=&OUT
  //STDERR DD SYSOUT=&OUT
  //CEEDUMP DD SYSOUT=&OUT
  //SYSUDUMP DD SYSOUT=&OUT
  //ABNLIGNR DD DUMMY
  //*
  //FDRWEBP PEND

  The default procs installed by running the FDRWEB Node Installation Manager (fdrweb_node_im.sh) on the LPARs that communicate with the FDRWEB host LPAR are:

• FDRWEB

  //*
  //FDRWEB PROC
  //*
  //* PROC FDRWEB STARTED TASK
  //*
  //START EXEC FDRWEBP,VERSION=’86’,PORT='4444'
  // JAVACLS='com.idp.fdrwebnode.NodeServer'
  //*
  //STDENV DD PATH='/usr/lpp/fdrweb/env/FDRWENV'

• FDRWEBP

  //*
  //* JVM PROC CALLED BY THE FDRWEB STARTED TASK
  //*
  //FDRWEBP PROC LEPARM='',
  // JAVACLS='com.idp.fdrwebnode.NodeServer',
  // PORT='4444',
  // LEPARM='TERMTHDACT(UADUMP)',
  // VERSION='86',
  // LOGLVL='+I',
  // OUT=X
  //*
  //FDRWEBP EXEC PGM=JVMLDM&VERSION,REGION=0M,
  // PARM='&LEPARM/&LOGLVL &JAVACLS &PORT'
  //SYSPRINT DD SYSOUT=&OUT
  //SYSOUT DD SYSOUT=&OUT
  //STDMSG DD SYSOUT=&OUT
  //STDOUT DD SYSOUT=&OUT
  //STDERR DD SYSOUT=&OUT
  //CEEDUMP DD SYSOUT=&OUT
  //SYSUDUMP DD SYSOUT=&OUT
  //ABNLIGNR DD DUMMY
  //*
  //FDRWEBP PEND