Use the mqsicvp command to perform verification tests on a broker, or to verify ODBC connections.
When you start a broker 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 a broker.
You can run this command against a broker that is running, or is not running. If the broker is not running, the verification tests are performed, but the broker is not started.
The mqsicvp command completes the following actions:
On Linux and UNIX systems, the command verifies
that the ODBC environment (if specified) is configured correctly.On Linux and UNIX systems, if the ODBC environment
check is successful, the command connects to all data sources that
are listed in the odbc.ini files, and that were
associated with the broker by using the mqsisetdbparms command.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 broker 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.
On Linux and UNIX systems only, the command
verifies that the ODBC environment (if specified) is configured
correctly. If the ODBCINI environment variable is not set, ODBC
environment verification is skipped. If the ODBC environment check is
completed successfully, the command then tries to connect to all data
sources that are listed in the odbc.ini files where
the mqsisetdbparms command was
used to associate the data source with the broker. To check what credentials are set by mqsisetdbparms, use mqsireportdbparmsWhen 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 broker and the data source, and returns information about the data source even when there is no association with a broker.
>>-mqsicvp-- -n--primaryDatasource------------------------------> >-- -u--primaryDatasourceUserId---------------------------------> >-- -p--primaryDatasourcePassword-------------------------------> >--+--------------------------------------------------------------------------------------------+--> '- -c--secondaryDatasource-- -i--secondaryDatasourceUserId-- -a--secondaryDatasourcePassword-' >--+-----+----------------------------------------------------->< '- -v-'
This invocation requires an association between the broker 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 broker 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 broker.
When using the mqsisetdbparms command, you can either specify the data source name directly, or add the prefix odbc::.
mqsisetdbparms IB9NODE -n odbc::myDsn -u username -p passwordmqsicvp IB9NODE -n myDsnOn 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 IB9NODEmqsicvp IB9NODE -n MyDBmqsicvp IB9NODE -n MyDB -c MyDB2mqsicvp –n MyDB –u username –p password –c MyDB2 –i username2 –a password2
Last updated Friday, 21 July 2017