The usermod is shipped as file ibm.hhop700.tpfa001
Steps required to install the usermod:
A sequential data set must be allocated on the z/OS system to receive the usermod that you will upload from your workstation. You can do this by submitting the job below. Add a job card and modify the parameters to meet your site's requirements before submitting.
//ALLOC EXEC PGM=IEFBR14 //* //FTPALLOC DD DSN=hlq.IBM.HHOP700.TPFA001, // DISP=(NEW,CATLG,DELETE), // DSORG=PS, // RECFM=FB, // LRECL=80, // UNIT=SYSALLDA, //* VOL=SER=volser, //* BLKSIZE=6160, // SPACE=(TRK,(1,1)) //*
Upload the file in binary format from your workstation to the z/OS data set. On a Windows system, you can use FTP from a command prompt to upload the file. In the sample dialog shown below, commands or other information entered by the user are in bold, and the following values are assumed:
| User enters: | Values |
|---|---|
| mvsaddr | TCP/IP address of the z/OS system |
| tsouid | Your TSO user ID |
| tsopw | Your TSO password |
| d: | Your drive containing the usermod files |
| hlq | High-level qualifier that you used for the data set that you allocated in the job above |
C:\>ftp mvsaddr Connected to mvsaddr. 220-FTPD1 IBM FTP CS V2R8 at mvsaddr, 04:43:52 on 2002-03-15. 220 Connection will close if idle for more than 60 minutes. User (mvsaddr:(none)): tsouid 331 Send password please. Password: tsopw 230 tsouid is logged on. Working directory is "tsouid.". ftp> cd .. 250 "" is the working directory name prefix. ftp> cd hlq 250 "hlq." is the working directory name prefix. ftp> binary 200 Representation type is Image ftp> put c:\ibm.hhop700.tpfa001 ibm.hhop700.tpfa001 200 Port request OK. 125 Storing data set hlq.ibm.hhop700.tpfa001 250 Transfer completed successfully 51520 bytes sent in .32 seconds ftp> quit 221 Quit command received. Goodbye.
SMP/E RECEIVE and APPLY the usermod.
The WebSphere Developers Fault Analyzer tech preview usermod requires 2 modifications to the WebSphere Developer host setup.
Steps required to activate the usermod:
rsed.envvars must include FAMiner.jar in its CLASSPATH configuration. This can be done by adding the following lines to the END of rsed.envvars:
#============================================================= # Fault Analyzer tech preview (usermod TPFA001) #============================================================= CLASSPATH=$CLASSPATH:$RSE_LIB/FAMiner.jar
Note: rsed.envvars resides by default in the RSE install path (default: /usr/lpp/wd4z/rse/lib), but could have been copied to a different location to avoid overwriting customizations when applying maintenance.
minerFile.dat must be updated to include FAMiner. A rexx program, TPFA001.active, is installed by this usermod to check if FAMiner is enabled, and to enable (-e) or disable (-d) the change to minerFile.dat
Give the following commands in the RSE install path (default: /usr/lpp/wd4z/rse/lib) to display the current status, to enable Fault Analyzer or to disable it:
$ ./TPFA001.active Fault Analyzer is NOT enabled in minerFile.dat $ ./TPFA001.active -e Enabling Fault Analyzer in minerFile.dat Fault Analyzer is enabled in minerFile.dat $ ./TPFA001.active -d Disabling Fault Analyzer in minerFile.dat Fault Analyzer is NOT enabled in minerFile.dat