Troubleshooting
Problem
tacmd command fails for some users and returns to command window prompt without any message
Cause
lack of permission on env.config file
Environment
AIX
Diagnosing The Problem
To diagnose the problem set 'set -x' on top of the tacmd script file before executing the login command. The below result shows that the tacmd command is unable to get the working JavaHome due to lack of permission
+ export CANDLEHOME
+ CurRegPath=/opt/IBM/ITM/registry
+ ArchTbl=/opt/IBM/ITM/registry/archdsc.tbl
+ DynShl=/opt/IBM/ITM/bin/dynarch.shl
+ + /opt/IBM/ITM/bin/CandleGetJavaHome
JavaHome=
+ [ ! -d /opt/IBM/ITM/registry ]
+ . /opt/IBM/ITM/bin/dynarch.shl /opt/IBM/ITM/registry/archdsc.tbl
+ 2> /dev/null
$
Resolving The Problem
The reason for the failure due to a lack of permissions for the file $candlehome/config/env.config.
This control file contains, among other things, the Java home directory. The underpinnings of CandleGetJavaHome read/update this file as part of normal operations. Consequently, when you use "secureMain -g <group> lock", all userids requiring access to ITM functions need to be in <group>.
It looks like someone had changed the permission of the $candlehome/config/env.config file after executing the "secureMain -g <group> lock"
After changing the permission of the $candlehome/config/env.config the problem is resolved.
The difference is explained by permission for the file $candlehome/config/env.config.
xxxx470: (not working user)
-rw-rw---- 1 root tivadmin 1174 Feb 28 19:59 env.config
xxxx471: (working user)
-rwxrwxrwx 1 root tivadmin 1174 Feb 28 18:55 env.config
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21591399