Re: Remote Admin Win - AIX
Title: Message
Hi,
MQExplorer doesn't work with sender and receiver channels, it uses a
server connection channel. You will need to do the
following:
-
Create a server connection channel SYSTEM.ADMIN.SVRCONNon the HP-UX queue manager, and either set the
MCAUSER attribute of the channel to 'mqm' or add your user id to the mqm
group on HP-UX.
-
Start the command server by running the following command:
strmqcsv Queue Manager
Name
- Make
sure when you select show remote queue manager, that you specify the IP address
or hostname and the port number, e.g. hostname(1414), and also make sure that
there is a listener listening on the port you have
specified.
Cheers
Ahmed
-Original Message-From:
damien.m.o'[EMAIL PROTECTED] [mailto:damien.m.o'[EMAIL PROTECTED] Sent: 16
September 2004 17:16To: [EMAIL PROTECTED]Subject:
Remote Admin Win - AIXHi I am trying to remotley
administer a Queue manager hosted on a HP-UX machine through my windows based
MQ Explorer. I have followed the Admin Guide and set up a Sender
Receiver channel on both ends with transmission Queues reflectiong the names
of the remote quque managers as so: On
the Local Windows Machine - Queue Manager (YHAM_XPX_001) * Transmit queue to SAP def ql (YHAM_HPX_001) replace + usage(xmitq) + descr('Used to send commands to YHAM_HPX_001') * Outbound channel to SAP define channel(ADMIN.YHAMHPX001) chltype(SDR)
replace + conname(hpks01v3.germany.glaxo) + xmitq (YHAM_HPX_001) + trptype(TCP) * Inbound
channel from SAP define
channel(ADMIN.YHAMXPX001) chltype(RCVR) replace + trptype(TCP) On the Remote HP-UX Machine - Queue Manager (YHAM_HPX_001)
* Transmit queue to GAA Server
def ql (YHAM_XPX_001) replace +
usage(xmitq) + descr('Used to send command responses to
YHAM_XPX_001') * Outbound
channel to GAA Server define
channel(ADMIN.YHAMXPX001) chltype(SDR) replace + conname(194.45.50.153) + xmitq (YHAM_XPX_001) + trptype(TCP) * Inbound channel from GAA Server define channel(ADMIN.YHAMHPX001) chltype(RCVR) replace +
trptype(TCP) Both Channels display a status of running and the command
server on the Remote machine displays a status of Running. When I right
click on the Queue Managers and select the "Show a remote queue manager"
(Entering the value YHAM_HPX_001 in both fields) I get an error saying
the Queue Manager is not available for connection AMQ4043. Any suggestions
Cheers Damien.sophos.3.85.09.16.
*
Emails aren't always secure, and they may be intercepted or changed after they've been sent. Abbey doesn't accept liability if this happens. If you think someone may have interfered with this email, please get in touch with the sender another way.
This message doesn't create or change any contract. Abbey doesn't accept responsibility for damage caused by any viruses contained in this email or its attachments. Emails may be monitored.
If you've received this email by mistake, please let the sender know at once that it's gone to the wrong person and then destroy it without copying, using, or telling anyone about its contents.
Abbey National Treasury Services plc Reg. No. 2338548, Cater Allen International Ltd Reg. No. 2572704, and Inscape Investments Limited Reg. No. 3839455 are registered in England and have their Registered Offices at: Abbey National House, 2 Triton Square, Regent's Place, London, NW1 3AN.
Cater Allen International Ltd is a subsidiary of Abbey National Treasury Services plc. Abbey National Treasury Services plc and Cater Allen International Ltd are Members of The London Stock Exchange.
Abbey National Asset Managers Ltd. Reg. No. 106669. Registered Office: Abbey National House, 301 St Vincent Street, Glasgow, G2 5HN. Registered in Scotland.
Abbey National Asset Managers Ltd and Inscape Investments Limited are members of the Abbey Marketing Group and provide OEICS, PEPS, and ISAs.
Abbey National Treasury Services plc, Cater Allen International Ltd, Inscape Investments Limited, and Abbey National Asset Managers Ltd are authorised and regulated by the Financial Services Authority.
Abbey Financial Markets is the brand name for Abbey National Treasury Services plc.
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 queueManagerName 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('Remote IP 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('my machine 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
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 communications cannot be guaranteed to be
timely,secure, error or virus-free. The sender does not accept
liabilityfor any errors or
omissions.**
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 queueManagerName
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('Remote IP
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('my machine
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.
**
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:
gt; Hi !
gt;
gt; Thanks for the listserver, I have found out ways
to
gt; connect to a remote
gt; queue manager if you don't have MMC / MW
Explorer.
gt; But these don't seem to
gt; work.
gt;
gt; Ways are :
gt; 1. Websphere MQ support pac ...has a simple
gt; GUI...not tried yet
gt; 2. MQ Web administration : need a support pack /
gt; installation for this
gt;
gt; 3. MQJExplorer
gt; (http://www.kolban.com/mqjexplorer/download.htm)
gt; This needs the following to be done on
the
gt; remote queue manager
gt;
gt; (a) A channel definition for a SVRCONN
gt; channel called
gt; SYSTEM.ADMIN.SVRCONN
gt; eg define
gt; channel(SYSTEM.ADMIN.SVRCONN)
gt; chltype(SVRCONN) mcauser('mqm')
gt;
gt; (b) strmqcsv
lt;queueManagerNamegt;
gt;
gt; Not working. I suspect that the problem
is
gt; the mqm group. I think my user id should be a
gt; member of that group. But I don't
gt; rights to do that on my NT !
gt;
gt; 4. Page 87 admin guide : 'Administering Remote
gt; MQSeries Objects'
gt;
gt;I did all the steps mentioned here. I changed
the
gt; order or steps as per
gt; remote queue definition example on another pdf.
gt;
gt;Local QMGR : source.queue.manager
gt;Remote QMGR : target.queue.manager
gt;
gt;local machine
gt;
gt;(1) runmqslr -m source.queue.manager -t TCP -p
gt; 6002
gt;(2) define qlocal(target.queue.manager)
gt; usage(XMITQ)
gt;(3) define channel(source.to.target)
CHLTYPE(SDR)
gt; conname('lt;Remote IP
gt; here(6001)gt;')
gt;XMITQ(target.queue.manager) TRPTYPE(TCP)
gt;(4) define channel(target.to.source)
gt; CHLTYPE(RCVR) TRPTYPE(TCP)
gt;
gt;Now...on the remote machine, lemme...just run
a
gt; few cubicles away !
gt;
gt;(5) runmqlsr -m target.queue.manager -t TCP -p
gt; 6001
gt;(6) define qlocal(source.queue.manager)
gt; usage(XMITQ)
gt;(7) define channel(target.to.source)
CHLTYPE(SDR)
gt; CONNAME('lt;my machine
gt; ip(6002)gt;')
gt;XMITQ(source.queue.manager) TRPTYPE(TCP)
gt;(8) define channel(source.to.target)
gt; CHLTYPE(RCVR) TRPTYPE(TCP)
gt;(9) strmqcsv target.queue.manager
gt;
gt;local machine
gt;(10) runmqchl -c source.to.target -m
gt; source.queue.manager
gt;
gt;remote machine
gt;(11) runmqchl -c target.to.source -m
gt; target.queue.manager
gt;
gt;
gt;Now as per the pdf, I run the following
command
gt; on my machine :
gt;runmqsc -w 30 target.queue.manager and get
this
gt; message :
gt;
gt; 5724-B41 (C) Copyright IBM Corp. 1994,
2002.
gt; ALL RIGHTS RESERVED.
gt; Starting MQSC for queue manager
gt; target.queue.manager.
gt;
gt;
gt; AMQ8146: WebSphere MQ queue manager not
gt; available.
gt;
gt; No MQSC commands read.
gt; 0 command responses received.
gt;
gt; Someone please explain what I could be doing
wrong.
gt; Why does a simple task
gt; in MQ Series take a lot of time ?
gt;
gt; Muchos gracias !
gt;
gt; Dark Warrior
gt;
gt;
gt; HSBC Software Development (India) Pvt Ltd
gt; HSBC Center, Riverside, West Avenue,
gt; 25-B Raheja Woods, Kalyani Nagar, Pune 411006.
gt;
gt; Telephone: +91 20 26683000
gt; Fax: +91 20 26681030
gt;
gt;
gt;
gt;
**
gt; This E-mail is confidential. It may also be
legally
gt; privileged.
gt; If you are not the addressee you may not copy,
gt; forward, disclose
gt; or use any part of it. If you have received this
gt; message in error,
gt; please delete it and all copies from your system
and
gt; notify the
gt; sender immediately by return E-mail.
gt;
gt; Internet communications cannot be guaranteed to
be
gt; timely,
gt; secure, error or virus-free. The sender does not
gt; accept liability
gt; for any errors or omissions.
gt;
**
gt;
gt;
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 contact
@PERSOLS.COM
Sent by: MQSeries List MQSERIES
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 queueManagerName 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('Remote IP !
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('my machine 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.managerNow 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
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 wayfilters 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 assertsno 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: 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
WindowMQ). 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
30target.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
this3.
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
queueManagerName
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('Remote IP 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('my machine
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.managerNow 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 communications cannot be guaranteed to be
timely,secure, error or virus-free. T
Re: Remote Admin
We want to use MQExplorer on NT to administer queue managers on remote systems I believe I can do this for remote queue managers running on most platforms (UNIX etc) but not OS/390. Remote administration of MQ on OS/390 is pretty simple. Just send a command to its SYSTEM.COMMAND.INPUT queue (and get a reply from a queue you supply). See the attached REXX program. Basing on it, you can easily build your own, more sophisticated app. Best regards, Marcin Grabinski [EMAIL PROTECTED] mqremadm.rex Description: Binary data
Re: Remote Admin
A limitation on the OS390 platform is it does not accept PCF commands. Therefore there is a need to write MQSC commands directly to the SYSTEM.COMMAND.INPUT queue. NASTEL has written a PCF command server for the OS390. I do not know id the sell it seperatly. But with it I believe you can send PCF commands from any of the vendor apps that may be free to the OS390 and this server will process them and send back and answer. This is not a plug for the software just a statement that it exist. I used to work for them and I have a little knowledge of their product. bobbee From: Marcin Grabinski [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Remote Admin Date: Fri, 17 May 2002 09:12:41 +0200 We want to use MQExplorer on NT to administer queue managers on remote systems I believe I can do this for remote queue managers running on most platforms (UNIX etc) but not OS/390. Remote administration of MQ on OS/390 is pretty simple. Just send a command to its SYSTEM.COMMAND.INPUT queue (and get a reply from a queue you supply). See the attached REXX program. Basing on it, you can easily build your own, more sophisticated app. Best regards, Marcin Grabinski [EMAIL PROTECTED] mqremadm.rex _ Join the world s largest e-mail service with MSN Hotmail. http://www.hotmail.com 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
You could also use support pac MO71. -Original Message- From: Robert Broderick [mailto:[EMAIL PROTECTED]] Sent: Friday, May 17, 2002 5:29 AM To: [EMAIL PROTECTED] Subject: Re: Remote Admin A limitation on the OS390 platform is it does not accept PCF commands. Therefore there is a need to write MQSC commands directly to the SYSTEM.COMMAND.INPUT queue. NASTEL has written a PCF command server for the OS390. I do not know id the sell it seperatly. But with it I believe you can send PCF commands from any of the vendor apps that may be free to the OS390 and this server will process them and send back and answer. This is not a plug for the software just a statement that it exist. I used to work for them and I have a little knowledge of their product. bobbee From: Marcin Grabinski [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Remote Admin Date: Fri, 17 May 2002 09:12:41 +0200 We want to use MQExplorer on NT to administer queue managers on remote systems I believe I can do this for remote queue managers running on most platforms (UNIX etc) but not OS/390. Remote administration of MQ on OS/390 is pretty simple. Just send a command to its SYSTEM.COMMAND.INPUT queue (and get a reply from a queue you supply). See the attached REXX program. Basing on it, you can easily build your own, more sophisticated app. Best regards, Marcin Grabinski [EMAIL PROTECTED] mqremadm.rex _ Join the world s largest e-mail service with MSN Hotmail. http://www.hotmail.com 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 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
The Support Pac is MO71: http://www-3.ibm.com/software/ts/mqseries/txppacs/txpm2.html Mike Davidson TSYS MQSeries Tech Support [EMAIL PROTECTED] Pete Moir [EMAIL PROTECTED] Sent by: MQSeries List [EMAIL PROTECTED] 05/16/2002 08:49 AM Please respond to MQSeries List To:[EMAIL PROTECTED] cc: Subject:Remote Admin Hi, apologies if this is going over old ground, I am only an occasional subscriber (and only an occasional MQer), but I couldn't quite find what I wanted on the archive. We want to use MQExplorer on NT to administer queue managers on remote systems I believe I can do this for remote queue managers running on most platforms (UNIX etc) but not OS/390. However I seem to remember there was a product which allowed you to remotely administer OS/390 queue managers in this way. Does anyone know of it ? thanks, Pete. _ Notice to recipient: This e-mail is meant for only the intended recipient of the transmission, and may be a communication privileged by law. If you received this e-mail in error, any review, use, dissemination, distribution, or copying of this e-mail is strictly prohibited. When addressed to our clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by Bank of America. Both Bank of America, N.A and Banc of America Securities Limited are regulated by The Financial Services Authority. _ 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
