The Target Host Name, Platform, And Version Information Is Not Displayed For The Deployment Status In The Cli Or The Workspace; Agent Upgrade And Restart Using Non-Root - IBM E027SLL-H - Tivoli Monitoring - PC Troubleshooting Manual

The target host name, platform, and version information is not
displayed for the deployment status in the CLI or the workspace
Target host name, platform, and version information is not displayed for the
deployment status in the CLI or the workspace. For group commands, the target
host name, platform, and version information are not displayed. However, the
transaction ID for the grouping command can be used to query all the transactions
started by this group command.
Here is an example of a group with one member:
@echo "Creating DEPLOY Group Window"
tacmd creategroup -g Window -t DEPLOY -d "Windows Deploy Group"
@echo "Adding ACHAN1 to Window DEPLOY group"
tacmd addgroupmember -g Window -t DEPLOY -m achan1.raleigh.ibm.com
KDYRXA.installDir=C:\data
@echo "Issuing group DEPLOY of Windows OS agent"
tacmd createNode -g Window
Transaction ID : 1222782542297000000015724
Command
Status
Retries
TEMS Name
Target Hostname:
Platform
Product
Version
Error Message : KDY0028I: Request completed successfully.
Deployment request was processed successfully and is now completed.
Transaction ID : 1222782542297000000015724
Command
Status
Retries
TEMS Name
Target Hostname: achan1.raleigh.ibm.com
Platform
Product
Version
Error Message : KDY2065I: The node creation operation was a success.
Old Component: deploy
New Component: itm_scn_ID

Agent upgrade and restart using non-root

About this task
The monitoring agent can run using a non-root user ID on UNIX and Linux
systems. This can be done by running the itmcmd agent start command while
logged in as a non-root user, and this can be done remotely by deploying the agent
using the Run As option on the GUI or using the _UNIX_STARTUP_.Username
option on the tacmd addSystem command line. If the agent is running using a
non-root user ID, and then the agent is upgraded, restarted remotely, restarted as a
result of a system reboot, or the itmcmd agent start is run using the root user ID,
then the monitoring agent subsequently runs as the root user. To confirm the user
ID that the monitoring agent is using, run the following command:
itm_install/bin/cinfo -r
If the installation is not permissioned properly, then you might be unable to restart
the agent as a non-root user ID after it has been run as the root user ID. To prevent
184
IBM Tivoli Monitoring: Troubleshooting Guide
-p KDYRXA.RXAusername=achan KDYRXA.RXApassword=xxxxx
: CREATENODE
: SUCCESS
: 0
: HUB_ACHAN2
:
: ITM
:
: CREATENODE
: SUCCESS
: 0
: HUB_ACHAN2
: WINNT
: NT
: 062100000