This article details the process of installing the Assure client on the mainframe ( z/OS ) platform.
Documentation on installing the Assure client on other platforms are located within the Assure documentation section of our support site : Assure Documentation
Assure Client Install
Please note, steps may differ depending on the Assure client version being installed. At the time of this articles publication, the latest version available is Assure client v9.3. Additionally, this article assumes the utilization of OMVS shell ( =6, OMVS ) and your TSO login has a minimum of 192 MB of RAM available.
To complete the Assure client installation on z/OS please complete the following steps :
1 ) Download product binaries and patches
Leave both product and patch files in a compressed state once downloaded. Product binaries and patches are located on our support site at the following location :
2 ) Ensure JAVA is available to the shell
If JAVA is available to the shell, version information will be displayed with the following command :
Additionally, the following command will determine the location of the JAVA_HOME directory :
Please make note of this location, as it will be referenced in an upcoming step
3 ) Create a new directory for Assure client ( when upgrading do not install over the old version ). This directory will be referenced as <install_home> throughout the rest of this article.
4 ) Move downloaded files to mainframe's UNIX shell
Perform a binary transfer of the Assure client .zip utilizing commands similar to the following :
ftp cd <install_home>
5 ) Unpack Assure client binaries
The client binaries may be unpacked by utilizing "unzip" from the IBM z/OS website :
Perform an unzip command against the Assure client binaries :
6 ) Configure Assure client
- Navigate to <install_home>/InfogixClient/etc and edit "setupzos.sh" to point to the JAVA_HOME directory
- Navigate to <install_home>/InfogixClient/bin and run "fixfileszos.sh". This command should only be run a single time after unzipping the client.
- From the /bin directory, run the following command to create your Assure client property file
Please note, the above command will utilize the "default" configuration. Similar to the Assure server installation, the "-c" argument may be utilized to create separate configurations, as needed.
- Edit the client.properties ( created in the prior step ). This file will be located within the <install_home>/InfogixClient/config/default/IA directory.
This client.properties file must be defined with the appropriate values to connect to your Assure server installation. Included in this file is the JAVA_HOME location as reviewed in step 2 above.
7 ) Optionally, run the following command from the /bin directory to encrypt your clear-text passwords within the client.properties file :
8 ) From the /bin directory, run the following command to deploy the Assure client :
Please note, this "deploy-client" script both validates and deploys the default configuration defined we defined above. If the script detects a configuration issue, correct the problem and run this script again.
9 ) From the /bin directory, run the following command to verify the license and ensure correct permissions are applied, allowing log files to be made :
Logs will be located within the <install_home>/InfogixClient/logs/default/IA directory.
10 ) Install any client patches downloaded in step 1 above. Follow the client installation instructions included in the release notes for each patch ( client instructions will be detailed after the server installation section of the patch instructions ).
Assure Client JCL
Assure client may be installed, though JCL will be required to execute the Assure client from batch jobs. The supported z/OS JAVA environments allow use of JCL to run JAVA applications from batch jobs. Custom versions of sample JCL suitable for use with Assure is included with the product binaries. To install this JCL library, complete the following steps within ISPF :
1 ) Within the Assure client binaries downloaded at the beginning of this article, a file titled "SAMPJCL.XMIT" is located with a /ZOS directory.
Unpack the file by entering the following TSO command
RECEIVE INDS (HLQ.SAMPJCL.XMIT)
2 ) When prompted to enter restore paramters or 'DELETE' or 'END', enter the following command :
The expected response is :
Restore successful to dataset 'HLQ.ASSURE.JCL'
3 ) Customize each member of the dataset by following instructions in the member.
If additional troubleshooting assistance is needed to run the client with JCL, please contact Infogix customer support.