IBM 51 Troubleshooting Manual page 40

28
Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide
Table 1. Tivoli Intelligent Orchestrator command line tools (continued)
Name Location
dcmExport.cmd
v On
dcmExport.sh
v On UNIX:
dcmQueryCommand.cmd
v On
dcmQueryCommand.sh
v On UNIX:
engineStatus.cmd
v On
engineStatus.sh
v On UNIX:
init.cmd
v On
init.sh
v On UNIX:
packageLogs.cmd
v On
packageLogs.sh
v On UNIX:
reinit.cmd
v On
reinit.sh
v On UNIX:
Description
Example:
dcmExport.cmd
Windows:
c:/myDirectory/
%TIO_HOME%\
myOutput.xml If
tools
outputFilename is not
specified, the default
$TIO_HOME/
output file name is
tools
dcmExport.xml in the
current directory).
Use of option [-d]
outputs protected
data in clear text
(default is encrypted).
Expects full path
name of the input
Windows:
file.
%TIO_HOME%\
tools
$TIO_HOME/
tools
Verifies the status of
the deployment
Windows:
engine, policy engine,
and AgentShell
$TIO_HOME/
Server.
tools
Initializes the
database and installs
Windows:
the automation
%TIO_HOME%\
packages with the
tools
installDriver option.
$TIO_HOME/
tools
Packages the Tivoli
Intelligent
Windows:
Orchestrator logs. The
%TIO_HOME%\
resulting zip file is
tools
saved by default in
your current
$TIO_HOME/
directory.
tools
Initializes the
database and installs
Windows:
the automation
%TIO_HOME%\
packages with the
tools
forceInstallDriver
option.
$TIO_HOME/
tools
Syntax
dcmExport.cmd [-d]
[outputFilename]
dcmExport.sh [-d]
[outputFilename]
dcmQueryCommandt.cmd
[input_file]
dcmQueryCommandt.sh
[input_file]
init.cmd [dcmcfg_file]
init.sh [dcmcfg_file]
packageLogs.cmd
packageLogs.sh
[dcmcfg_file]
reinit.cmd reinit.sh