Use the mqsicvp command to perform verification tests on an integration node, to verify ODBC connections, and perform CPU benchmark processing.
When you start an integration node by using the mqsistart command, this command is run automatically to verify the component.
On z/OS®, the same verification procedures
are run automatically when you start an integration node.
You can run this command against an integration node that is running, or is not running. If the integration node is not running, the verification tests are performed, but the integration node is not started.
The mqsicvp command completes the following actions:
The data sources that are described are those that you defined when you set up the ODBC database. See Enabling ODBC connections to the databases.
Extra invocations of the mqsicvp command provide ODBC test tool function. This function provides useful information about a user data source, or compares two user data sources for equivalence. These invocations of the command are discrete from the basic invocation of the mqsicvp command, and are not run at integration node startup.
When you use the mqsicvp command as an ODBC test tool, the command issues an informational message for a successful connection, providing the name of the data source, database type, and version. If a secondary data source is supplied, the mqsicvp command issues a second informational message for a successful connection to that data source, with the same information about the secondary data source, and stating that a comparison will be made.
When the tool is run against one data source, it completes several checks against the ODBC interface to determine which data types and functions are supported, together with information about the names and sizes of those data types. If any data types or functions are not supported, they are summarized in a final informational message.
When these tests are run against two data sources, they are run against both data sources, and both sets of results are shown. A final informational message states whether the two data sources are equivalent and eligible to be used in the same message processing node; for further information, see Accessing databases from ESQL.
When you run the mqsicvp command with parameters shown in the following syntax diagram, the command provides ODBC test tool function. You can use the command to display useful information about a user data source, or compare two user data sources. On Linux and UNIX systems only, invocations of the command that use these parameters also verify that the ODBC environment (if specified) is configured correctly. In these cases, the command checks that the ODBCINI, ODBCSYSINI, and IE02_PATH variables are set.
Each data source name (DSN) is fully specified with a user name and password.
This invocation does not rely on an association between the integration node and the data source, and returns information about the data source even when there is no association with an integration node.
>>-mqsicvp-- -n--primaryDatasource------------------------------> >-- -u--primaryDatasourceUserId---------------------------------> >-- -p--primaryDatasourcePassword-------------------------------> >--+--------------------------------------------------------------------------------------------+--> '- -c--secondaryDatasource-- -i--secondaryDatasourceUserId-- -a--secondaryDatasourcePassword-' >--+-----+----------------------------------------------------->< '- -v-'
This invocation requires an association between the integration node and the data source name (DSN). To successfully use this invocation, you must first run the mqsisetdbparms command to identify a specific user ID and password for the integration node to use when connecting to the data source. The output from this invocation is the same as the output from the invocation where data source names have not been associated with the integration node.
When using the mqsisetdbparms command, you can either specify the data source name directly, or add the prefix odbc::.
mqsisetdbparms IBNODE -n odbc::myDsn -u username -p password
mqsicvp IBNODE -n myDsn
If
you use mqsisetdbparms to
set an integration server level identity for a data source, the identity
cannot be used in mqsicvp. On Linux and UNIX systems only, invocations of
the command that use the parameters in the following syntax diagram
also verify that the ODBC environment (if specified) is configured
correctly. In these cases, the command checks that the ODBCINI, ODBCSYSINI,
and IE02_PATH variables are set.
All names are case-sensitive on Linux and UNIX systems.
mqsicvp IBNODE
mqsicvp IBNODE -n MyDB
mqsicvp IBNODE -n MyDB -c MyDB2
mqsicvp -n MyDB -u username -p password -c MyDB2 -i username2 -a password2
The mqsicvp command can be used to perform a benchmark on the system. The benchmark tests the CPU performance by calculating a recursive, arithmetic sequence on one or more threads. For the duration of the benchmarking process, each thread that is used typically consumes an entire logical CPU on the system. Consequently, the optimal time to run the command is during a period of scheduled downtime so that the CPU usage does not impact running production workloads.
All names are case-sensitive on Linux and UNIX systems.
mqsicvp IBNODE -b benchmark -o javarecursion,threads=2,iterations=5,sequence=40
The output from the command is similar in format to the following example:mqsicvp IBNODE -b benchmark -o javarecursion,threads=2,iterations=5,sequence=40
Running 2 threads
ThreadId:23 - Calculating sequence to number 40 5 times
ThreadId:24 - Calculating sequence to number 40 5 times
Took 3 seconds to run
Total CPU time: 7014ms, for 10 calculations
Rating Value:285714
Average Core Value:142857
BIP8071I: Successful command completion.