Author |
Message
|
nithinkumar1519 |
Posted: Fri Dec 09, 2011 4:45 am Post subject: MQ |
|
|
Novice
Joined: 07 Dec 2011 Posts: 14
|
guyz i know i have asked a silly question asking everything how to do??
Thanks & Regards
A NithinKumar
EDIT by exerk: duplicate of this post removed |
|
Back to top |
|
 |
nithinkumar1519 |
Posted: Fri Dec 09, 2011 5:20 am Post subject: error |
|
|
Novice
Joined: 07 Dec 2011 Posts: 14
|
AFTER DOING THIS
1:
Run SET MQSERVER=CLIENT.PORT.ONE/TCP/hostname(1414)on the command propmt, don't close the command prompt windows. Ensure that the QMGR and LSTR are running. On the same command prompt window, run amqscnxc(with no options) to confrim connectivity from client to server.If you get positive results, then try amqsputc.
You can also set MQSERVER as the System environment variable.
2:
Alternatively set the below in mqclient.ini and run amqscnxc and amqsputc.
Channels:
ServerConnectionParms=CLIENT.PORT.ONE/TCP/hostname(1414)
I AM GETTING AN ERROR
**The procedure entry point @xtr_FNC_entry@12 could not be located in the dynamic link library AMQXCS2.dll.** |
|
Back to top |
|
 |
Vitor |
Posted: Fri Dec 09, 2011 5:25 am Post subject: Re: error |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
nithinkumar1519 wrote: |
AFTER DOING THIS |
Stop shouting.
nithinkumar1519 wrote: |
I AM GETTING AN ERROR
**The procedure entry point @xtr_FNC_entry@12 could not be located in the dynamic link library AMQXCS2.dll.** |
From what? Which of the 2 application named in the documentation you've quoted?
We're not a training resource for good & sufficient reason; we're a technical forum. We're not going to step you through the process, especially if you keep shouting. We're doubly not going to do it if you post "I did this, this happened, what now?" without any indication of the circumstances or what you have tried to fix this yourself.
If you're new to WMQ that's fine, we all were once (some of us a long while ago admitedly) but WMQ is not the easiest thing to pick up. Formal training, or at least mentoring by an experienced person is a good idea.
Push back on your management. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
nithinkumar1519 |
Posted: Sun Dec 11, 2011 11:01 pm Post subject: error |
|
|
Novice
Joined: 07 Dec 2011 Posts: 14
|
dude my mgmt is co-operating in every way.......i mena they are trying to help me in every way....
we are trying MQ in db2 for the first time.....so having problems |
|
Back to top |
|
 |
Vitor |
Posted: Mon Dec 12, 2011 5:39 am Post subject: Re: error |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
nithinkumar1519 wrote: |
dude my mgmt is co-operating in every way.......i mena they are trying to help me in every way.... |
Except training and mentoring it seems.
nithinkumar1519 wrote: |
we are trying MQ in db2 for the first time.....so having problems |
What has DB2 got to do with this? You've posted an utterly basic WMQ client question and expecting answers even though you're giving us nothing (unless the answer to my previous question is cleverly coded in your response somehow). You're certainly showing no evidence of what you're doing to resolve this and if this is the first time for WMQ in DB2 is it not your first time with WMQ? If not, how does this differ from other set ups?
And what do you mean "WMQ in DB2"? From inside a stored procedure? A DB2 enabled application? You're drip feeding information. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
nithinkumar1519 |
Posted: Mon Dec 12, 2011 9:01 pm Post subject: dude |
|
|
Novice
Joined: 07 Dec 2011 Posts: 14
|
I am working with WMQ for the first time and i work with db2 almost daily....
This is the error i am getting
*** Please wait: creating queue manager (DB2MQ_DEFAULT_MQM) ......
*** Please wait: starting the queue manager (DB2MQ_DEFAULT_MQM) ......
*** Error -- while connecting to DB2MQ_DEFAULT_MQM failed (reason code -- 2058)
crtmqm/strmqm has been issued
*** Problem -- while checking MQ
Please ensure that the user has permission to create/start start queue manager
Please ensure that the user has permission to create a queue
*** enable_MQFunctions Failed .....
Please ensure that MQSeries is installed properly
I have installed WEBSPHEREMQ CLIENT,AMI in the client side....
is this information enough?? |
|
Back to top |
|
 |
Vitor |
Posted: Tue Dec 13, 2011 5:47 am Post subject: Re: dude |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
nithinkumar1519 wrote: |
This is the error i am getting |
From what? The only application you've mentioned in this thread is amqsputc and that doesn't seem to be what you're using. This looks like some kind of install script:
nithinkumar1519 wrote: |
*** Please wait: creating queue manager (DB2MQ_DEFAULT_MQM) ......
*** Please wait: starting the queue manager (DB2MQ_DEFAULT_MQM) ......
*** Error -- while connecting to DB2MQ_DEFAULT_MQM failed (reason code -- 2058)
crtmqm/strmqm has been issued
*** Problem -- while checking MQ
Please ensure that the user has permission to create/start start queue manager
Please ensure that the user has permission to create a queue
*** enable_MQFunctions Failed .....
Please ensure that MQSeries is installed properly
I have installed WEBSPHEREMQ CLIENT,AMI in the client side....
is this information enough?? |
It's enough to indicate that you're in a serious mess. You started out trying to establish a client connection and are now running a script that's attempting to create (or at least start) a local queue manager. These things do not mesh together at all as a single problem. And still you fail to explain anything about context.
You've also totally failed to provide any information on what DB2 has to do with this. If you're not going to answer questions we pose & provide additional information how do you expect to get any assistance? Your random guesses are as good as ours (though given your track record that's perhaps charitable). _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
bruce2359 |
Posted: Tue Dec 13, 2011 6:14 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9472 Location: US: west coast, almost. Otherwise, enroute.
|
I've long suspected that there is a Pseudo-random OP Reply Generator (POPG) out there. This may confirm it. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
Vitor |
Posted: Tue Dec 13, 2011 6:15 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
bruce2359 wrote: |
I've long suspected that there is a Pseudo-random OP Reply Generator (POPG) out there. This may confirm it. |
Alarmingly I can believe that. It's more plausible than some of the other potential explainations... _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
nithinkumar1519 |
Posted: Tue Dec 13, 2011 8:54 pm Post subject: error |
|
|
Novice
Joined: 07 Dec 2011 Posts: 14
|
when i try to give this command i have encountered with this error
**enable_MQFunctions -n database -u user -p pwd!**
-------------
error
-------------
*** Please wait: creating queue manager (DB2MQ_DEFAULT_MQM) ......
*** Please wait: starting the queue manager (DB2MQ_DEFAULT_MQM) ......
*** Error -- while connecting to DB2MQ_DEFAULT_MQM failed (reason code -- 2058)
crtmqm/strmqm has been issued
*** Problem -- while checking MQ
Please ensure that the user has permission to create/start start queue manager
Please ensure that the user has permission to create a queue
*** enable_MQFunctions Failed .....
Please ensure that MQSeries is installed properly |
|
Back to top |
|
 |
nithinkumar1519 |
Posted: Tue Dec 13, 2011 9:02 pm Post subject: leave everything |
|
|
Novice
Joined: 07 Dec 2011 Posts: 14
|
This is what i have in the client/server side
client
------------
1) websphereMQ client
2) AMI
server
---------
1)websphere MQSERVER
2)configured queue managers
(a queuemgr with port number 1414)
Then in the client side
i have encountered with this error when i was trying to enable functions
**enable_MQFunctions -n database -u user -p pwd!**
-------------
error
-------------
*** Please wait: creating queue manager (DB2MQ_DEFAULT_MQM) ......
*** Please wait: starting the queue manager (DB2MQ_DEFAULT_MQM) ......
*** Error -- while connecting to DB2MQ_DEFAULT_MQM failed (reason code -- 2058)
crtmqm/strmqm has been issued
*** Problem -- while checking MQ
Please ensure that the user has permission to create/start start queue manager
Please ensure that the user has permission to create a queue
*** enable_MQFunctions Failed .....
Please ensure that MQSeries is installed properly
Last edited by nithinkumar1519 on Tue Dec 13, 2011 9:20 pm; edited 1 time in total |
|
Back to top |
|
 |
bruce2359 |
Posted: Tue Dec 13, 2011 9:17 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9472 Location: US: west coast, almost. Otherwise, enroute.
|
From the output you see, it seems the command you issue attempts to create a brand new qmgr, then start the brand new qmgr, then...
These are administrative tasks that are labor-intensive, time-consuming, and it requires mqm-group authority. It makes no sense whatsoever that a transaction-based application expects to create a qmgr instance, start it, AND update a DB.
Since state that you know nothing about MQ or AMI, I'd suggest that you ask someone at your organization for help with the procedure you are executing.
I'd also strongly suggest that you get formal WMQ training. Look for WM10 and WM20 courses at www.ibm.com/training/us.
Last, please use some less-juvenile, more formal salutation, rather than 'dude.' My paying clients don't call me 'dude.' _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
|