qoperation capture

Description

This command captures information from a single client or multiple clients and stores the information in the form of a database on the CommServe. An answer file is also created which can be edited by a user during the merge operation. This answer file can be created either on the CommServe or on the local client machine. If the database file path is a UNC path, then the command line operation will prompt the user for impersonation details. When completed successfully, the qoperation capture command displays the message "Capture Successful" in the command prompt.

In case of an error, an error code and description are displayed as: "capture: Error errorcode: errordescription"

Usage

qoperation capture -c <client> -dfn <dumpfile> [-dbn <databasename>] [-afn <answerfile]> [-st <starttime>] [-et <endtime>] [-u <username>] [-p <password>] [-rp <alternate database path>][-af <argsfile>] [-tf <tokenfile>] [-tk <token>] [-h]

Options

-c	Name of the client to capture
-dfn	Full path and the dump file name on the CommServe
-dbn	Name of the database from which you wish to capture data. (This is useful when you want to capture data from a database other than the current CommServe.)
-afn	Full path and the answer file name on the local Client
-st	Start date and time from which data will be captured. The time must be entered in the following format: mm/dd/yyyy hh:mm[:ss] or yyyy/mm/dd hh:mm[:ss].
-et	End date and time until which data must be captured. The time must be entered in the following format: mm/dd/yyyy hh:mm[:ss] or yyyy/mm/dd hh:mm[:ss].
-u	User name, if database location is an UNC path
-p	Password, if database location is an UNC path
-rp	Alternative database restore path. This option is useful when migrating clients in the clustered environment. In a cluster, the CommServe binaries are installed on the physical server and the database is located on the shared disk resource. As the capture and merge operations are executed on the physical server that hosts the binaries, the -rp option provides a way to specify the path to the shared disk resource in which the database resides. (If this option is not specified, the command will by default look for the database in the same drive in which the binaries reside and the operation will fail.)
-af	Reads arguments from a file
-tf	Reads token from a file
-tk	Token string
-h	Displays help

Argument File

For information on creating an argument file, see Command Line - FAQ - How do I use argument files in commands.

clients	[list] List of clients to capture
dumpfilename	[string] Full path and the dump file name on the CommServe
databasename	[string] Name of the database from which you wish to capture data. (This is useful when you want to capture data from a database other than the current CommServe)
answerfile	[string] Full path and the answer file name on the local Client
starttime	[time] Start date and time from which data will be captured The time must be entered in the following format: mm/dd/yyyy hh:mm[:ss] or yyyy/mm/dd hh:mm[:ss].
endtime	[time] End date and time until which data must be captured. The time must be entered in the following format: mm/dd/yyyy hh:mm[:ss] or yyyy/mm/dd hh:mm[:ss].
user	[string] User name, if database location is an UNC path
password	[string] Password, if database location is an UNC path

Diagnostics

Possible exit status values are:

0 - Successful completion.

1 - CLI usage failures, due to the use of an unsupported option or missing argument.

2 - Any other failure.

Example

In windows, capture a client with the name client1, store the information in a dump file at c:\capturedb on the CommServe computer, and save the answer file at C:\afile on the local client.

qoperation capture -c client1 -dfn c:\capturedb -dbn db -afn c:\afile