installing capki, is "env=all" needed?

Products

• CA Harvest Software Change Manager
• CA Harvest Software Change Manager - OpenMake Meister

Issue/Introduction

Is this an issue? Ths sysadmin did not use "env=all"

./setup install caller=SCMSERVER verbose instdir=/opt/CA/SharedComponents
[CAPKI] Parameters: mode=install, caller=SCMSERVER, instdir=/opt/CA/SharedComponents, env=none, verbose=true
[CAPKI] This installer contains CAPKI Version 5.2.11
grep: warning: stray \ before #
grep: warning: stray \ before #
[CAPKI] Using install directory as specified by CASHCOMP
[CAPKI] Installation directory: /opt/CA/SharedComponents/CAPKI
[CAPKI] Checking for Permissions
[CAPKI] Proper permissions are set for installation directory
[CAPKI] Disk space is available
[CAPKI] Existing Version RV=1
[CAPKI] Updated installed files log: /opt/CA/SharedComponents/CAPKI/CAPKI5/Linux/s390x/64/files.dat
[CAPKI] CAPKI Installed Successful, return Value is 0

Environment

Harvest Software Change Manager v14.x and higher
Linux/Unix/zLinux platforms

Resolution

Inside the same folder where you find capki's "setup" executable for installation, you'll find a file named "readme.txt".  This file contains all the information about how to run "setup", all the options available, and how they will be used to install capki.

The "readme.txt" file explains:

env=<none|user|all>   - It enables setting environment variables for the specified user(s) as shown below:
  none: do not set environment variables (default)
  user: current user only ($HOME/.profile)
  all : all users (for using this, login must be root).
  
NB: env=none option acts same as env=all except that it does not set any environment variables. So, when env=none is passed, it may require root priveleges depending on the installation directory.

When "env=all" is included on the "setup" command line, the installer will add some environment variables to the system's .profile.  This is why only the root user can use this option.