HP Systems Insight Manager 5.3 Command Line Interface reference guide

The target list specified in the tool definition file is used as the target list.user-specified
The value of defTargets is ignored if a target list is specified on the command line. Authorization for each
target node is verified before a tool is executed.
Target execution environment
When a job is executing on a node, its environment contains information gathered on the CMS and sent to
the HP SIM agent on the target nodes. These variables are placed in the environment in which the tool
command runs:
• MX_USER. Contains the UNIX login name of the user running the job.
• MX_TASKID. The job ID assigned to the job.
• MX_TOOL. The toolname (this name might not be the same as the tool script name).
• MX_TARGETS. A space-separated list of target nodes for this job.
• MX_CMS. The CMS hostname.
• MX_REPOSITORY. The hostname of the system containing the SQL Server Service Repository.
• DISPLAY. The value copied from the user's environment so tools that use an X Window GUI can contact
the correct X server.
• HOME. The home directory of the execution user specified in the tool definition.
• SHELL. This is set to /usr/bin/sh.
These variables are set to the empty string:
• CLASSPATH
• ENV
• JAVA_HOME
• SHLIB_PATH
In addition to the previously listed variables, the following environment variables are inherited from the
init(1m) process that spawns the agent. These are default values.
• INIT_STATE
• PATH
A number of environment variables are set automatically by the POSIX shell (/usr/bin/sh). See the
sh-posix(1) manpage for more information.
Tool execution states
For every target node, a job goes through the following states that track the progress of the job on each
node:
• Pending. The job has not started on this node. This state is used when there are a large number of
target nodes and the CMS DTF is only able to run a job in parallel on a smaller number of nodes.
• Copying files. Any files that need to be copied are transmitted to the target, and the target writes the
files and sets their ownership and permissions. The maximum number of files that can be copied is 16.
• Running tool. If there is a command line to execute (the command line is optional for a tool), the job
enters the Running tool state. During this state, the target forks (starts) a process to run the command
and establishes a clean process environment (see Target Execution Environment). It then executes (see
execl(1) ) the POSIX shell with the command line as the argument (see sh-posix(1) ). The
command line is run from the HOME directory (as defined by getpwuid(3C) on the target) of the
execution user specified by the user keyword in the tool definition. If the user does not exist on the
target, / is used. The stdin for the process is set to /dev/null.
If the tool is a launch-only tool, as soon as the shell has successfully executed the command line, the
agent on the target moves to the next state. If not, the target agent waits while the command executes,
Target execution environment 31