Re: remote admin of queue managers not working / not using MMC ro explorer.......
It
should be done via MQ Services. If you don't have MQ Services, then the only
thing I know is to edit the registry (but I have never done that before on
Window MQ). There should be a key call 'DefaultQueueManager" under
hkey_local_machine\software\ibm\MQSeries\ConfigureationIf you haven't set
that up, probably it's not there.
You
can either create such key or to make it simple, just create another qmgr
with "crtmqm -q" to make it as default. Then change the registry to
source.queue.manager to aviod typo of the key name.
Once
you have done this, you should be able to start "runmqsc -w
30 target.queue.manager". Of course, it may follow up with security
problem when you type command in.
Regards,
Ian
-Original Message-From: MQSeries List
[mailto:[EMAIL PROTECTED]On Behalf Of Shantanu
UpadhyayaSent: Wednesday, 9 June 2004 7:30 PMTo:
[EMAIL PROTECTED]Subject: Re: remote admin of queue managers
not working / not using MMC ro explorer...Nope. How do I do that. Which pdf / page ? Here I go do
some more searching..
Sent by:
MQSeries List
<[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc:
Our Ref:
Your Ref:
Subject: Re: remote admin of queue managers not working / not
using MMC ro explorer... Have
you set your local queue manager as default queue manager? -Original Message-From: MQSeries List
[mailto:[EMAIL PROTECTED]On Behalf Of Shantanu
UpadhyayaSent: Wednesday, 9 June 2004 3:50 PMTo:
[EMAIL PROTECTED]Subject: remote admin of queue managers not
working / not using MMC ro explorer...Hi ! Thanks for the listserver, I have found out ways to
connect to a remote queue manager if you don't have MMC / MW Explorer. But
these don't seem to work.
Ways are : 1.
Websphere MQ support pac ...has a simple GUI...not tried yet 2.
MQ Web administration : need a support pack / installation for
this 3.
MQJExplorer
(http://www.kolban.com/mqjexplorer/download.htm)
This needs the following to be done on the remote queue
manager (a) A channel definition
for a SVRCONN channel called SYSTEM.ADMIN.SVRCONN
eg define
channel(SYSTEM.ADMIN.SVRCONN) chltype(SVRCONN) mcauser('mqm')
(b) strmqcsv
Not working. I suspect that the problem is the mqm
group. I think my user id should be a member of that group. But I
don't rights to do that on my NT !
4. Page 87 admin guide :
'Administering Remote MQSeries Objects' I did all the steps mentioned here. I changed the order or
steps as per remote queue definition example on another pdf.
Local QMGR : source.queue.manager
Remote QMGR : target.queue.manager local machine (1) runmqslr
-m source.queue.manager -t TCP -p 6002 (2) define
qlocal(target.queue.manager) usage(XMITQ) (3) define
channel(source.to.target) CHLTYPE(SDR) conname('')
XMITQ(target.queue.manager) TRPTYPE(TCP)
(4) define channel(target.to.source) CHLTYPE(RCVR) TRPTYPE(TCP)
Now...on the remote machine, lemme...just run a few
cubicles away ! (5) runmqlsr -m
target.queue.manager -t TCP -p 6001
(6) define
qlocal(source.queue.manager) usage(XMITQ) (7) define
channel(target.to.source) CHLTYPE(SDR) CONNAME('') XMITQ(source.queue.manager)
TRPTYPE(TCP) (8) define channel(source.to.target)
CHLTYPE(RCVR) TRPTYPE(TCP) (9) strmqcsv
target.queue.manager local
machine (10) runmqchl -c source.to.target -m
source.queue.manager
remote
machine (11) runmqchl -c target.to.source -m
target.queue.manager Now as per the pdf, I run the following command on my
machine : runmqsc -w 30 target.queue.manager and
get this message : 5724-B41 (C) Copyright
IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
Starting MQSC for queue manager
target.queue.manager.
AMQ8146: WebSphere MQ queue manager not available. No MQSC commands read.
0 command responses received.
Someone please explain what I could be doing wrong. Why does
a simple task in MQ Series take a lot of time ? Muchos gracias !
Dark
WarriorHSBC
Software Development (India) Pvt Ltd HSBC Center, Riverside, West
Avenue,25-B Raheja Woods, Kalyani Nagar, Pune 411006.Telephone:
+91 20 26683000Fax: +91 20
26681030**This
E-mail is confidential. It may also be legally privileged.If you are not
the addressee you may not copy, forward, discloseor use any part of it. If
you have received this message in error,please delete it and all copies
from your system and notify thesender immediately by return
E-mail.Internet communicatio
CCSID 437 can't convert in HP-Unix
Title: CCSID 437 can't convert in HP-Unix We currently upgrade our HP-Unix system to V11.11 and MQSeries to V5.3 CSD05. It no longer supports messages sending from the Window/NT environment. I received the following messages: AMQ6047: Conversion not supported. EXPLANATION: WebSphere MQ is unable to convert string data tagged in CCSID 437 to data in CCSID 1051. Before our Unix system upgrade, application can receive messages from NT (CCSID 437) or Z/OS (CCSID 500) with no problem. After upgrade, it can only receive messages from Z/OS. We specify NO convert for all our channels. The CCSID for the queue manager on Unix is 1051. Since I don't know much about the Unix system, neither does our Unix System Administrator, can anyone tell me what went wrong and how to fix it? Thank you very much for any suggestions. Linda Kinnard Sr. Systems Programmer Technical Services (714) 850-2852
Re: Can you write an app that is both client and server code?
Yes for windows at least. However you can only do one at a time. You do it by building a dll hook, basically you put your own library between the application and MQ with your library loading the client or server dll as required. HOWEVER you will be building something with custom code you are may have to modify every time you upgrade MQ. A risky business. But techincally challenging and fun to do. Regards Tim A -Original Message- From: Larry Hendersen [mailto:[EMAIL PROTECTED] Sent: Thursday, 10 June 2004 8:26 AM To: [EMAIL PROTECTED] Subject: Can you write an app that is both client and server code? Is it possible to write an MQ app that is an MQ client and it also it connects to servers locally? How can you make the program determine which DLL or library to open/use? dlopen()? For Solaris, or Windows or other Unix. _ MSN 9 Dial-up Internet Access fights spam and pop-ups now 3 months FREE! http://join.msn.click-url.com/go/onm00200361ave/direct/01/ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material.
Can you write an app that is both client and server code?
Is it possible to write an MQ app that is an MQ client and it also it connects to servers locally? How can you make the program determine which DLL or library to open/use? dlopen()? For Solaris, or Windows or other Unix. _ MSN 9 Dial-up Internet Access fights spam and pop-ups now 3 months FREE! http://join.msn.click-url.com/go/onm00200361ave/direct/01/ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: WBIMB SNMP
Here's some info on it: - the command requires environment variables be set first; these are in another script. I copy that env script into a new, temporary script, append the wpostemsg command on the end, and then execute the whole thing. If you can get the environment set first, then you can just issue the wpostemsg command - the command has required parameters and optional parameters; some of these optional parameters can only be used if your installation has genned certain 'slots' to be active on the alert message. (An alert message has about 30 or 40 attributes called slots; not all are used. We use the slot or attribute called 'sub_origin' to put our extra detail info into. The message field is not big enough to contain all the detail and actually, we would rather keep the message field content at a high level and put the detail in the sub_origin field/slot). - here is an example of a wpostemsg command: /script/directory/name/wpostemsg -r "put severity level here" -m "put message here" hostname="put server name here" sub_origin="put detail here" tivoliclassname MQSERIES That last item (MQSERIES) equates to something defined to Tivoli, but it escapes me now. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Robert Broderick Sent: Wednesday, June 09, 2004 4:25 PM To: [EMAIL PROTECTED] Subject: Re: WBIMB SNMP Thanks Peter, I would assume it has parameters that allow you to refine the alert up to the console. I will locate the books and look into it. bobbee >From: "Heggie, Peter" <[EMAIL PROTECTED]> >Reply-To: MQSeries List <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Re: WBIMB SNMP >Date: Tue, 8 Jun 2004 13:41:51 -0400 > >Tivoli has a command line API called wpostemsg, which sends alerts to >the Tivoli console. I use it on Windows and AIX. It is nicer than the >delivered Tivoli Distributed Monitoring product which can issue cryptic >messages. > >-Original Message- >From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of >Robert Broderick >Sent: Tuesday, June 08, 2004 1:25 PM >To: [EMAIL PROTECTED] >Subject: WBIMB SNMP > > >I want to design an SNMP interface to (possibly TIVOLI) escalate >Message FLow processing errors to a monitoring console. Has anybody >done this type of thing through the Broker. Any guidelines? Any info? > >I know you can have QPASA and other monitoring packages in place. I >believe we will eventually go to TIVOLI. How do you interface the >Broker with TIVOLI to escalate error situations??? > > bobbee > >_ >Stop worrying about overloading your inbox - get MSN Hotmail Extra >Storage! http://join.msn.click-url.com/go/onm00200362ave/direct/01/ > >Instructions for managing your mailing list subscription are provided >in the Listserv General Users Guide available at http://www.lsoft.com >Archive: http://vm.akh-wien.ac.at/MQSeries.archive > > >This e-mail and any files transmitted with it, are confidential to >National Grid and are intended solely for the use of the individual or >entity to whom they are addressed. If you have received this e-mail in >error, please reply to this message and let the sender know. > >Instructions for managing your mailing list subscription are provided >in the Listserv General Users Guide available at http://www.lsoft.com >Archive: http://vm.akh-wien.ac.at/MQSeries.archive _ MSN 9 Dial-up Internet Access fights spam and pop-ups now 3 months FREE! http://join.msn.click-url.com/go/onm00200361ave/direct/01/ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive This e-mail and any files transmitted with it, are confidential to National Grid and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please reply to this message and let the sender know. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: WBIMB SNMP
Thanks Peter, I would assume it has parameters that allow you to refine the alert up to the console. I will locate the books and look into it. bobbee From: "Heggie, Peter" <[EMAIL PROTECTED]> Reply-To: MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: WBIMB SNMP Date: Tue, 8 Jun 2004 13:41:51 -0400 Tivoli has a command line API called wpostemsg, which sends alerts to the Tivoli console. I use it on Windows and AIX. It is nicer than the delivered Tivoli Distributed Monitoring product which can issue cryptic messages. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Robert Broderick Sent: Tuesday, June 08, 2004 1:25 PM To: [EMAIL PROTECTED] Subject: WBIMB SNMP I want to design an SNMP interface to (possibly TIVOLI) escalate Message FLow processing errors to a monitoring console. Has anybody done this type of thing through the Broker. Any guidelines? Any info? I know you can have QPASA and other monitoring packages in place. I believe we will eventually go to TIVOLI. How do you interface the Broker with TIVOLI to escalate error situations??? bobbee _ Stop worrying about overloading your inbox - get MSN Hotmail Extra Storage! http://join.msn.click-url.com/go/onm00200362ave/direct/01/ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive This e-mail and any files transmitted with it, are confidential to National Grid and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please reply to this message and let the sender know. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive _ MSN 9 Dial-up Internet Access fights spam and pop-ups now 3 months FREE! http://join.msn.click-url.com/go/onm00200361ave/direct/01/ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: remote admin of queue managers not working / not using MMC ro explorer.......
Anthony, "1. You have set the MCAUSER to "MQM" therefore you must connect with the user MQM if you however leave the MCAUSER blank you can connect with any user name but the user must be defined on the system for which you are connecting and be part of the MQM group. " Not true. The value in the MCAUSER in no way filters the UserID that connects to the QMgr. The effect is that ANY UserID that connects will be overridden by the MCAUSER value, if set. That is true whether the client asserts any arbitrary UserID or asserts no UserID at all. I believe the problem that was encountered was that an MCAUSER of "mqm" was used on a Windows system where it is not defined. Probably would have worked if the MUSR_MQADMIN ID had been used instead. -- T.Rob -Original Message-From: MQSeries List [mailto:[EMAIL PROTECTED]On Behalf Of Anthony G AllisonSent: Wednesday, June 09, 2004 12:08 PMTo: [EMAIL PROTECTED]Subject: Re: remote admin of queue managers not working / not using MMC ro explorer...Good afternoon, Regarding remote access to queue managers: 1. The RUNMQSC command does work in remote mode with the -w flag. You do however need to have standard sender/receiver channels setup and your transmit queue must be the name of the remote queue manager. Second, the command server does need to be running on the remote machine. Third, This only works with a default queue manager. 2. The problem you may be having with the MQJExplorer is as follows. 1. You have set the MCAUSER to "MQM" therefore you must connect with the user MQM if you however leave the MCAUSER blank you can connect with any user name but the user must be defined on the system for which you are connecting and be part of the MQM group. There are many packages out there for accessing a queue manager remotely and each have there own instructions. Anthony AllisonMiddleware Architect CSC 1001 G StreetSuite 800WDC, 20001(202) 824-7938[EMAIL PROTECTED] IBM Certified MQ Specialist IBM Certified MQ Application Developer IBM Certified MQ Solutions ProviderThis is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.
Re: Channel send/receive exit
>Does anyone have a channel send/receive exit that does compression that they >might want to share? I'd rather not re-invent the wheel if possible. >Thanks, >Mark Bond Mark, You could take a look at SupportPac MO02 (http://www-1.ibm.com/support/docview.wss?rs=203&uid=swg24000828&loc=en_US&cs=utf-8&lang=en). This essentially does a Run Length Encoding compression of the messages. Clearly for good compression rates the compression algorithm will depend on the type of messages you're sending. Cheers, P. Paul G Clarke WebSphere MQ Development IBM Hursley Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Channel send/receive exit
Hi Mark, try take a look on the supportpack MO02: http://www-306.ibm.com/software/integration/support/supportpacs/category.html#cat2 It works on: z/OS, windows and AIX. Kind regards Jxrgen www.mrmq.dk the author of BlockIP Mark wrote: Does anyone have a channel send/receive exit that does compression that they might want to share? I'd rather not re-invent the wheel if possible. Thanks, Mark Bond E-mail: [EMAIL PROTECTED] Phone: (440) 264-6140 FAX:(440) 379-6524 Cell Phone: (440) 478-3856 Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive _ Fe alle de nye og sjove ikoner med MSN Messenger http://www.msn.dk/messenger Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Channel send/receive exit
Does anyone have a channel send/receive exit that does compression that they might want to share? I'd rather not re-invent the wheel if possible. Thanks, Mark Bond E-mail: [EMAIL PROTECTED] Phone: (440) 264-6140 FAX:(440) 379-6524 Cell Phone: (440) 478-3856 Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: how to restrict users from accessing XMITQ
Title: Message Unrestricted XMITQ's are a security exposure. If you can use QREMOTEs instead of QM Alias, then you protect the XMITQ at the sending end and grant selective access to the QREMOTE. If not, then you may want to consider using PUTAUT on the channel and grant/restrict access on the receiving end. -Original Message-From: Firoz K [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 08, 2004 2:44 PMTo: [EMAIL PROTECTED]Subject: how to restrict users from accessing XMITQ We have a third-party software using MQ as the transport layer.The Software performs a request for a user and writes to a Remote Queue using Queue Manager Alias resolution.This resolves the XMITQ to the receiving queue manager.Does any one allow access to any third party software write directly to the XMITQ ?What RACF do you provide for the XMITQs on MVS. Thanks, -Firoz Kotta. Check out the coupons and bargains on MSN Offers! Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: remote admin of queue managers not working / not using MMC ro explorer.......
Good afternoon,
Regarding remote access to queue managers:
1. The RUNMQSC command does work in remote mode with the -w flag. You do however need to have standard sender/receiver channels setup and your transmit queue must be the name of the remote queue manager. Second, the command server does need to be running on the remote machine. Third, This only works with a default queue manager.
2. The problem you may be having with the MQJExplorer is as follows.
1. You have set the MCAUSER to "MQM" therefore you must connect with the user MQM if you however leave the MCAUSER blank you can connect with any user name but the user must be defined on the system for which you are connecting and be part of the MQM group.
There are many packages out there for accessing a queue manager remotely and each have there own instructions.
Anthony Allison
Middleware Architect
CSC
1001 G Street
Suite 800
WDC, 20001
(202) 824-7938
[EMAIL PROTECTED]
IBM Certified MQ Specialist
IBM Certified MQ Application Developer
IBM Certified MQ Solutions Provider
This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.
Ruzi R
@PERSOLS.COM>
Sent by: MQSeries List
06/09/2004 11:43 AM
Please respond to MQSeries List
To: [EMAIL PROTECTED]
cc:
Subject: Re: remote admin of queue managers not working / not using MMC ro explorer...
Hi Dark Worrior, >Now as per the pdf, I run the following command on my >machine : > runmqsc -w 30 target.queue.manager and get this > >message : Since, the target.queuemanager is not defined on your machine, you cannot issue runmqsc against it. In other words, RUNMQSC works only on the local machine (where the qmgr is defined). So, you have to logon to the target machine and issue the same RUNMQSC. Regards, Ruzi --- Shantanu Upadhyaya wrote: > Hi ! > > Thanks for the listserver, I have found out ways to > connect to a remote > queue manager if you don't have MMC / MW Explorer. > But these don't seem to > work. > > Ways are : > 1. Websphere MQ support pac ...has a simple > GUI...not tried yet > 2. MQ Web administration : need a support pack / > installation for this > > 3. MQJExplorer > (http://www.kolban.com/mqjexplorer/download.htm) > This needs the following to be don!
e on the > remote queue manager > > (a) A channel definition for a SVRCONN > channel called > SYSTEM.ADMIN.SVRCONN > eg define > channel(SYSTEM.ADMIN.SVRCONN) > chltype(SVRCONN) mcauser('mqm') > > (b) strmqcsv > > Not working. I suspect that the problem is > the mqm group. I think my user id should be a > member of that group. But I don't > rights to do that on my NT ! > > 4. Page 87 admin guide : 'Administering Remote > MQSeries Objects' > > I did all the steps mentioned here. I changed the > order or steps as per > remote queue definition example on another pdf. > > Local QMGR : source.queue.manager > Remote QMGR : target.queue.manager > > local machine > > (1) runmqslr -m source.queue.manager -t TCP -p > 6002 > (2) define qlocal(target.queue.manager) > usage(XMITQ) > (3) define channel(source.to.target) CHLTYPE(SDR) > conname(' !
here(6001)>') > XMITQ(target.queue.manager) TRPTYPE(TCP) > (4
) define channel(target.to.source) > CHLTYPE(RCVR) TRPTYPE(TCP) > > Now...on the remote machine, lemme...just run a > few cubicles away ! > > (5) runmqlsr -m target.queue.manager -t TCP -p > 6001 > (6) define qlocal(source.queue.manager) > usage(XMITQ) > (7) define channel(target.to.source) CHLTYPE(SDR) > CONNAME(' ip(6002)>') > XMITQ(source.queue.manager) TRPTYPE(TCP) > (8) define channel(source.to.target) > CHLTYPE(RCVR) TRPTYPE(TCP) > (9) strmqcsv target.queue.manager > > local machine > (10) runmqchl -c source.to.target -m > source.queue.manager > > remote machine > (11) runmqchl -c target.to.source -m > target.queue.manager > > > Now as per the pdf, I run the following command > on my machine : > runmqsc -w 30 target.queue.manager and get this > message : > > 5724-B41 (C) Copyright IBM Corp. 1994, 2002. > ALL RIGHTS RESERVED. > Starting MQSC for queue!
manager > target.queue.manager. > > > AMQ8146: WebSphere MQ queue manager not > available. > > No MQSC commands read. > 0 command responses received. > > Someone please explain what I could be doing wrong. > Why does a simple task > in MQ Series take a lot of time ? > > Muchos gracias ! > > Dark Warrior > > > HSBC Software Development (Indi
Re: remote admin of queue managers not working / not using MMC ro explorer.......
Sorry, I take back what I said about runmqsc working
only on the local machine... What was I thinking?!!
Ruzi
--- Shantanu Upadhyaya <[EMAIL PROTECTED]>
wrote:
> Hi !
>
> Thanks for the listserver, I have found out ways
to
> connect to a remote
> queue manager if you don't have MMC / MW
Explorer.
> But these don't seem to
> work.
>
> Ways are :
> 1. Websphere MQ support pac ...has a simple
> GUI...not tried yet
> 2. MQ Web administration : need a support pack /
> installation for this
>
> 3. MQJExplorer
> (http://www.kolban.com/mqjexplorer/download.htm)
> This needs the following to be done on
the
> remote queue manager
>
> (a) A channel definition for a SVRCONN
> channel called
> SYSTEM.ADMIN.SVRCONN
> eg define
> channel(SYSTEM.ADMIN.SVRCONN)
> chltype(SVRCONN) mcauser('mqm')
>
> (b) strmqcsv
>
> Not working. I suspect that the problem
is
> the mqm group. I think my user id should be a
> member of that group. But I don't
> rights to do that on my NT !
>
> 4. Page 87 admin guide : 'Administering Remote
> MQSeries Objects'
>
>I did all the steps mentioned here. I changed
the
> order or steps as per
> remote queue definition example on another pdf.
>
>Local QMGR : source.queue.manager
>Remote QMGR : target.queue.manager
>
>local machine
>
>(1) runmqslr -m source.queue.manager -t TCP -p
> 6002
>(2) define qlocal(target.queue.manager)
> usage(XMITQ)
>(3) define channel(source.to.target)
CHLTYPE(SDR)
> conname(' here(6001)>')
>XMITQ(target.queue.manager) TRPTYPE(TCP)
>(4) define channel(target.to.source)
> CHLTYPE(RCVR) TRPTYPE(TCP)
>
>Now...on the remote machine, lemme...just run
a
> few cubicles away !
>
>(5) runmqlsr -m target.queue.manager -t TCP -p
> 6001
>(6) define qlocal(source.queue.manager)
> usage(XMITQ)
>(7) define channel(target.to.source)
CHLTYPE(SDR)
> CONNAME(' ip(6002)>')
>XMITQ(source.queue.manager) TRPTYPE(TCP)
>(8) define channel(source.to.target)
> CHLTYPE(RCVR) TRPTYPE(TCP)
>(9) strmqcsv target.queue.manager
>
>local machine
>(10) runmqchl -c source.to.target -m
> source.queue.manager
>
>remote machine
>(11) runmqchl -c target.to.source -m
> target.queue.manager
>
>
>Now as per the pdf, I run the following
command
> on my machine :
>runmqsc -w 30 target.queue.manager and get
this
> message :
>
> 5724-B41 (C) Copyright IBM Corp. 1994,
2002.
> ALL RIGHTS RESERVED.
> Starting MQSC for queue manager
> target.queue.manager.
>
>
> AMQ8146: WebSphere MQ queue manager not
> available.
>
> No MQSC commands read.
> 0 command responses received.
>
> Someone please explain what I could be doing
wrong.
> Why does a simple task
> in MQ Series take a lot of time ?
>
> Muchos gracias !
>
> Dark Warrior
>
>
> HSBC Software Development (India) Pvt Ltd
> HSBC Center, Riverside, West Avenue,
> 25-B Raheja Woods, Kalyani Nagar, Pune 411006.
>
> Telephone: +91 20 26683000
> Fax: +91 20 26681030
>
>
>
>
**
> This E-mail is confidential. It may also be
legally
> privileged.
> If you are not the addressee you may not copy,
> forward, disclose
> or use any part of it. If you have received this
> message in error,
> please delete it and all copies from your system
and
> notify the
> sender immediately by return E-mail.
>
> Internet communications cannot be guaranteed to
be
> timely,
> secure, error or virus-free. The sender does not
> accept liability
> for any errors or omissions.
>
**
>
>
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: remote admin of queue managers not working / not using MMC ro explorer.......
Hi Dark Worrior,
>Now as per the pdf, I run the following command on my >machine :
> runmqsc -w 30 target.queue.manager and get this >
>message :
Since, the target.queuemanager is not defined on your machine, you cannot issue runmqsc against it. In other words, RUNMQSC works only on the local machine (where the qmgr is defined). So, you have to logon to the target machine and issue the same RUNMQSC.
Regards,
Ruzi
--- Shantanu Upadhyaya <[EMAIL PROTECTED]> wrote:
> Hi !
>
> Thanks for the listserver, I have found out ways to
> connect to a remote
> queue manager if you don't have MMC / MW Explorer.
> But these don't seem to
> work.
>
> Ways are :
> 1. Websphere MQ support pac ...has a simple
> GUI...not tried yet
> 2. MQ Web administration : need a support pack /
> installation for this
>
> 3. MQJExplorer
> (http://www.kolban.com/mqjexplorer/download.htm)
> This needs the following to be done on the
> remote queue manager
>
> (a) A channel definition for a SVRCONN
> channel called
> SYSTEM.ADMIN.SVRCONN
> eg define
> channel(SYSTEM.ADMIN.SVRCONN)
> chltype(SVRCONN) mcauser('mqm')
>
> (b) strmqcsv
>
> Not working. I suspect that the problem is
> the mqm group. I think my user id should be a
> member of that group. But I don't
> rights to do that on my NT !
>
> 4. Page 87 admin guide : 'Administering Remote
> MQSeries Objects'
>
>I did all the steps mentioned here. I changed the
> order or steps as per
> remote queue definition example on another pdf.
>
>Local QMGR : source.queue.manager
>Remote QMGR : target.queue.manager
>
>local machine
>
>(1) runmqslr -m source.queue.manager -t TCP -p
> 6002
>(2) define qlocal(target.queue.manager)
> usage(XMITQ)
>(3) define channel(source.to.target) CHLTYPE(SDR)
> conname(' here(6001)>')
>XMITQ(target.queue.manager) TRPTYPE(TCP)
>(4) define channel(target.to.source)
> CHLTYPE(RCVR) TRPTYPE(TCP)
>
>Now...on the remote machine, lemme...just run a
> few cubicles away !
>
>(5) runmqlsr -m target.queue.manager -t TCP -p
> 6001
>(6) define qlocal(source.queue.manager)
> usage(XMITQ)
>(7) define channel(target.to.source) CHLTYPE(SDR)
> CONNAME(' ip(6002)>')
>XMITQ(source.queue.manager) TRPTYPE(TCP)
>(8) define channel(source.to.target)
> CHLTYPE(RCVR) TRPTYPE(TCP)
>(9) strmqcsv target.queue.manager
>
>local machine
>(10) runmqchl -c source.to.target -m
> source.queue.manager
>
>remote machine
>(11) runmqchl -c target.to.source -m
> target.queue.manager
>
>
>Now as per the pdf, I run the following command
> on my machine :
>runmqsc -w 30 target.queue.manager and get this
> message :
>
> 5724-B41 (C) Copyright IBM Corp. 1994, 2002.
> ALL RIGHTS RESERVED.
> Starting MQSC for queue manager
> target.queue.manager.
>
>
> AMQ8146: WebSphere MQ queue manager not
> available.
>
> No MQSC commands read.
> 0 command responses received.
>
> Someone please explain what I could be doing wrong.
> Why does a simple task
> in MQ Series take a lot of time ?
>
> Muchos gracias !
>
> Dark Warrior
>
>
> HSBC Software Development (India) Pvt Ltd
> HSBC Center, Riverside, West Avenue,
> 25-B Raheja Woods, Kalyani Nagar, Pune 411006.
>
> Telephone: +91 20 26683000
> Fax: +91 20 26681030
>
>
>
> **
> This E-mail is confidential. It may also be legally
> privileged.
> If you are not the addressee you may not copy,
> forward, disclose
> or use any part of it. If you have received this
> message in error,
> please delete it and all copies from your system and
> notify the
> sender immediately by return E-mail.
>
> Internet communications cannot be guaranteed to be
> timely,
> secure, error or virus-free. The sender does not
> accept liability
> for any errors or omissions.
> **
>
>
Vladimir Veytsel is out of the Office.
I will be out of the office from 06/09/2004 until 06/10/2004. I will respond to your message when I return. For production emergencies please contact me at: 201-251-3892 - Home 347-563-1085 - Cell For questions other than production emergencies contact my manager Rommel Belen at: 212-270-1037 Intranet MQSeries Reference Site: http://unix-dris.ny.global.chase.com/documentation/MQ Regards, Vlad. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: remote admin of queue managers not working / not using MMC ro explorer.......
Nope. How do I do that. Which pdf / page ? Here I go do some more searching..
Sent by: MQSeries List <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Our Ref:
Your Ref:
Subject: Re: remote admin of queue managers not working / not using MMC ro explorer...
Have you set your local queue manager as default queue manager?
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED]On Behalf Of Shantanu Upadhyaya
Sent: Wednesday, 9 June 2004 3:50 PM
To: [EMAIL PROTECTED]
Subject: remote admin of queue managers not working / not using MMC ro explorer...
Hi !
Thanks for the listserver, I have found out ways to connect to a remote queue manager if you don't have MMC / MW Explorer. But these don't seem to work.
Ways are :
1. Websphere MQ support pac ...has a simple GUI...not tried yet
2. MQ Web administration : need a support pack / installation for this
3. MQJExplorer (http://www.kolban.com/mqjexplorer/download.htm)
This needs the following to be done on the remote queue manager
(a) A channel definition for a SVRCONN channel called SYSTEM.ADMIN.SVRCONN
eg define channel(SYSTEM.ADMIN.SVRCONN) chltype(SVRCONN) mcauser('mqm')
(b) strmqcsv
Not working. I suspect that the problem is the mqm group. I think my user id should be a member of that group. But I don't rights to do that on my NT !
4. Page 87 admin guide : 'Administering Remote MQSeries Objects'
I did all the steps mentioned here. I changed the order or steps as per remote queue definition example on another pdf.
Local QMGR : source.queue.manager
Remote QMGR : target.queue.manager
local machine
(1) runmqslr -m source.queue.manager -t TCP -p 6002
(2) define qlocal(target.queue.manager) usage(XMITQ)
(3) define channel(source.to.target) CHLTYPE(SDR) conname('')
XMITQ(target.queue.manager) TRPTYPE(TCP)
(4) define channel(target.to.source) CHLTYPE(RCVR) TRPTYPE(TCP)
Now...on the remote machine, lemme...just run a few cubicles away !
(5) runmqlsr -m target.queue.manager -t TCP -p 6001
(6) define qlocal(source.queue.manager) usage(XMITQ)
(7) define channel(target.to.source) CHLTYPE(SDR) CONNAME('')
XMITQ(source.queue.manager) TRPTYPE(TCP)
(8) define channel(source.to.target) CHLTYPE(RCVR) TRPTYPE(TCP)
(9) strmqcsv target.queue.manager
local machine
(10) runmqchl -c source.to.target -m source.queue.manager
remote machine
(11) runmqchl -c target.to.source -m target.queue.manager
Now as per the pdf, I run the following command on my machine :
runmqsc -w 30 target.queue.manager and get this message :
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
Starting MQSC for queue manager target.queue.manager.
AMQ8146: WebSphere MQ queue manager not available.
No MQSC commands read.
0 command responses received.
Someone please explain what I could be doing wrong. Why does a simple task in MQ Series take a lot of time ?
Muchos gracias !
Dark Warrior
HSBC Software Development (India) Pvt Ltd
HSBC Center, Riverside, West Avenue,
25-B Raheja Woods, Kalyani Nagar, Pune 411006.
Telephone: +91 20 26683000
Fax: +91 20 26681030
**
This E-mail is confidential. It may also be legally privileged.
If you are not the addressee you may not copy, forward, disclose
or use any part of it. If you have received this message in error,
please delete it and all copies from your system and notify the
sender immediately by return E-mail.
Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability
for any errors or omissions.
**
**
This message originated from the Internet. Its originator may or may not
be who they claim to be and the information contained in the message
and any attachments may or may not be accurate.
**
HSBC Software Development (India) Pvt Ltd
HSBC Center, Riverside, West Avenue,
25-B Raheja Woods, Kalyani Nagar, Pune 411006.
Telephone: +91 20 26683000
Fax: +91 20 26681030
**
This E-mail is confidential. It may also be legally privileged.
If you are not the addressee you may not copy, forward, disclose
or use any part
