11.11.2012 Views

HP Systems Insight Manager 7.0 Command Line Guide

HP Systems Insight Manager 7.0 Command Line Guide

HP Systems Insight Manager 7.0 Command Line Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Description<br />

The mxexec command executes an <strong>Systems</strong> <strong>Insight</strong> <strong>Manager</strong> tool with associated arguments on<br />

specific managed nodes and node groups. A tool and its arguments, specified to run on one or<br />

more nodes, is called a task. An instance of the task running at a particular time is called a job.<br />

• mxexec -t toolname [-A argvalue... ] [-h|-O filename|-o directory<br />

] [-n target...|-q queryname... ]<br />

This command enables you to run <strong>Systems</strong> <strong>Insight</strong> <strong>Manager</strong> tools. The toolname is required,<br />

and depending on the tool being run, the argument values and targets might be required.<br />

The results returned by the tool can be saved in a file or a series of files, one per managed<br />

node.<br />

You can specify the option to suppress the job header information and send the job's standard<br />

output to stdout and the job's standard error to stderr. The option to suppress the job<br />

header information is mutually exclusive with the options to send the job output to a file or<br />

directory.<br />

• mxexec -c [-k] -j job_ID<br />

This command enables you to cancel a specific job, and gives you the option to kill the<br />

command execution. Only an administrative rights user or the user who initiated the job can<br />

cancel or kill a job.<br />

• mxexec [-l n|t] [-i task_name...|-j job_ID... ] [-d date ]<br />

mxexec -l d [-h] -j job_ID...<br />

These commands allow you to list information about one or more running jobs. All jobs can<br />

be listed, specific jobs can be listed by job_ID, and all the jobs for a specific task_name<br />

can be listed. Use the -d option to list all jobs completed after a specific date. The date is<br />

specified in the format month/day/year hour:minute AM|PM, and must be enclosed in<br />

quotation marks to ensure that the date specification string is interpreted as a single argument,<br />

including the embedded spaces.<br />

When mxexec is run with no options, it displays a list of the current user's jobs which have<br />

not completed. The capability to display several levels of detail for a specific job is supported.<br />

Any user can view the details for any job.<br />

When viewing job details, you can specify the option to suppress job headers and send the<br />

job output to stdout or stderr.<br />

Tool execution authorization<br />

<strong>Systems</strong> <strong>Insight</strong> <strong>Manager</strong> verifies that the user invoking mxexec is authorized to execute the tool<br />

on the specified managed nodes. If the user is not authorized, the command terminates with an<br />

error message that is logged to the <strong>Systems</strong> <strong>Insight</strong> <strong>Manager</strong> log file, and the job is aborted.<br />

NOTE: The default location of the log file is /var/opt/mx/logs/mx.log.<br />

A user is authorized to run a tool on a node if all the following are true:<br />

• The user is a valid <strong>Systems</strong> <strong>Insight</strong> <strong>Manager</strong> user (see mxuser(1M)).<br />

• The tool is assigned to a toolbox (see mxtool(1M)).<br />

• The user is authorized to have that toolbox on that node (see mxauth(1M)).<br />

Tool authorization is all or none, meaning that it will fail if the user is not authorized to run the tool<br />

on all nodes in the target list.<br />

36 <strong>Command</strong> descriptions

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!