| Author |
Message
|
| x22ips |
 Posted: Wed Apr 30, 2014 3:47 am Post subject: mqsicvp no verification test on datasource |
 |
|
Novice
Joined: 02 Dec 2013
Posts: 22
|
Hello,
mqsicvp brokername does not check the datasources automatic.
mqsicvp brokername <primaryDatasource> run successfully.
Any idea?
Thanks  |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Wed Apr 30, 2014 4:52 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Any ideas about what?
It is very simple to code mqsicvp BROKER -n <DS_NAME>
in order to do a specific tests against a known datasource.
If you are asking for the default option for mqsicvp to be enhanced to include these DSN tests then there is nothing from stopping you from submitting an enhancement request.
If this is not the case then please let us know what you want to achieve in a bit more detail.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| iShakir |
| Posted: Thu May 01, 2014 2:00 am Post subject: |
|
|
Apprentice
Joined: 07 Mar 2013
Posts: 47
|
| Is ODBCINI set? If you set ODBCINI in the broker, then all datasources should be verified by mqsicvp <broker_name>. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu May 01, 2014 2:37 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| iShakir wrote: |
| Is ODBCINI set? If you set ODBCINI in the broker, then all datasources should be verified by mqsicvp <broker_name>. |
citation please?
for example, on a WINDOWS system with IIB 9.0.0.1.
| Code: |
d:\Data\MY Broker Build\wbiscripts\MYBROKER>mqsicvp MYBROKER
BIP8873I: Starting the component verification for component 'MYBROKER'.
BIP8876I: Starting the environment verification for component 'MYBROKER'.
BIP8894I: Verification passed for 'Registry'.
BIP8894I: Verification passed for 'MQSI_REGISTRY'.
BIP8894I: Verification passed for 'Java Version - 1.7.0 IBM Windows AMD 64 build
pwa6470sr5-20130619_01(SR5)
BIP8894I: Verification passed for 'MQSI_FILEPATH'.
BIP8878I: The environment verification for component 'MYBROKER' has finished successfully.
BIP8882I: Starting the WebSphere MQ verification for component 'MYBROKER'.
BIP8886I: Verification passed for queue 'SYSTEM.BROKER.ADMIN.QUEUE' on queue manager 'MYBROKER'.
BIP8886I: Verification passed for queue 'SYSTEM.BROKER.EXECUTIONGROUP.QUEUE' on queue manager 'MYBROKER'.
BIP8886I: Verification passed for queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on queue manager 'MYBROKER'.
BIP8884I: The WebSphere MQ verification for component 'MYBROKER' has finished successfully.
BIP8874I: The component verification for 'MYBROKER' has finished successfully.
BIP8071I: Successful command completion.
d:\Data\MY Broker Build\wbiscripts\MYBROKER>
|
No mention of and ODBC testing there.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| iShakir |
| Posted: Thu May 01, 2014 3:00 am Post subject: |
|
|
Apprentice
Joined: 07 Mar 2013
Posts: 47
|
|
| Back to top |
|
|
| x22ips |
| Posted: Sat May 03, 2014 4:13 am Post subject: |
|
|
Novice
Joined: 02 Dec 2013
Posts: 22
|
Thanks for your answers.
I have set ODBCINI, but the datasource is not verified, only when i set mqsicvp <broker_name> -n <DS_NAME> .
We have another customer environment, when i start the command there mqsicvp <broker_name> --> the datasource is verified without setting of -n DS_Name.
My question is : setting of odbc.ini is correct, mqsisetdbparms for a specific database as well -> BUT no verification of datasource with mqsicvp <broker_name> |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat May 03, 2014 4:25 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
| iShakir wrote: |
I always struggle to get links out of product infocentres:
|
It is relatively easy. Most pages have the link at the bottom of the page.
Alternatively, synchronize right pane and left pane, go to the left pane, right click and copy the link from there... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| x22ips |
| Posted: Sun May 04, 2014 10:19 pm Post subject: |
|
|
Novice
Joined: 02 Dec 2013
Posts: 22
|
 sorry, i´m on linux command line. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun May 04, 2014 10:26 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
| x22ips wrote: |
| sorry, i´m on linux command line. |
So where do you access the infocenter from? You do use a browser don't you?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| x22ips |
| Posted: Mon May 05, 2014 1:04 am Post subject: |
|
|
Novice
Joined: 02 Dec 2013
Posts: 22
|
IBM Infocenter:
When you run the mqsicvp command with only the broker name, and no other parameters, the command completes the following checks:
•Checks that the broker environment is set up correctly (for example, the installed level of Java is supported).
•Verifies that the WebSphere MQ queues are defined and accessible.
• 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.
In my case the ODBCINI environment is specified, but the command (mqsicvp brokername) did not connect and verifies data sources |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon May 05, 2014 4:07 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
| x22ips wrote: |
| If the ODBC environment check is completed successfully, ... |
Note that it does not specify if the ODBCINI variable is set...
I suggest you verify all your ODBC setup. It looks like your ODBC environment check did not complete successfully.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| vamsisparky |
| Posted: Mon May 05, 2014 6:24 am Post subject: Just check the same command by starting your Message Queue |
|
|
Newbie
Joined: 05 May 2014
Posts: 1
|
Its check for the default configurations for your broker which is associated with.
I restarted my system and started it again its working fine...
check your MQ is running or not
with WMQ running
its verify and displays the components like this..
C:\Program Files\IBM\MQSI\9.0.0.0>mqsicvp IB9NODE
BIP8873I: Starting the component verification for component 'IB9NODE'.
BIP8876I: Starting the environment verification for component 'IB9NODE'.
BIP8894I: Verification passed for 'Registry'.
BIP8894I: Verification passed for 'MQSI_REGISTRY'.
BIP8894I: Verification passed for 'Java Version - 1.7.0 IBM Windows AMD 64 build
pwa6470sr4fp2-20130426_01(SR4 FP2)
BIP8894I: Verification passed for 'MQSI_FILEPATH'.
BIP8878I: The environment verification for component 'IB9NODE' has finished succ
essfully.
BIP8882I: Starting the WebSphere MQ verification for component 'IB9NODE'.
BIP8886I: Verification passed for queue 'SYSTEM.BROKER.ADMIN.QUEUE' on queue man
ager 'IB9QMGR'.
BIP8886I: Verification passed for queue 'SYSTEM.BROKER.EXECUTIONGROUP.QUEUE' on
queue manager 'IB9QMGR'.
BIP8886I: Verification passed for queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on
queue manager 'IB9QMGR'.
BIP8884I: The WebSphere MQ verification for component 'IB9NODE' has finished suc
cessfully.
BIP8874I: The component verification for 'IB9NODE' has finished successfully.
BIP8071I: Successful command completion. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon May 05, 2014 6:35 am Post subject: Re: Just check the same command by starting your Message Que |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| vamsisparky wrote: |
Its check for the default configurations for your broker which is associated with.
|
You excerprt is the same as the example I posted above. The problem is that the original quesyio relates to a Unix/Linux system and not to a broker environment running on Windows. The 'mqsicvp' command can do additional tests when running on an *ix system.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| x22ips |
| Posted: Tue May 27, 2014 3:28 am Post subject: |
|
|
Novice
Joined: 02 Dec 2013
Posts: 22
|
Hello,
we have found workaround for our connection problem.
We have added in odbc64.ini:
LoginTimeout=0
ConnectionRetryCount=3
ConnectionRetryDelay=3
So if timeout to database has occured, number of times the driver retries connection.
In our case, it helps, the odbc error didn't occured again. |
|
| Back to top |
|
|
|
|
