MQSeries.net :: View topic - Admin Help

MBExpert · Posted: Fri Nov 27, 2009 5:54 am Post subject:

I am working for a finance domain based client, and the broker version they are using is 6.1 which is installed on z/OS.
Toolkit that we have been given for dev is 6.1.

I am facing a couple of issues in relation to admin and dev. Please let me know as much information as anyone of you have on these.

1) We do not have admin rights, so even though we have installed broker on our local machines, without admin rights we are not able for deploy and debug on broker if we are logged in using our domain username. Do we have some way to make it work. Please let me know if any more details are required to answer this questions.

2) We have access to client's dev environment but therein no debugger. Dev env is also in z/OS (Broker 6.0) and we access using remote connection to a windows vmware which has broker 6.0 installed. We have admin rights to this windows vmware and using this we have installed RAC to be able to debug on broker, but when I try to attach to remote/dev debugger I get the error:
Agent is inactive
Restart IBM Agent Controller if necessary and make sure that you have the correct level of IBM Agent controller installed with the broker

I need to know a few things regarding this issue:
a) Any simple way to take care of it?
b) debugger would work only if RAC is installed in both client toolkit and also in dev broker env? or I only need to install it on the windows machine which has toolkit and which I am using to debug on broker?
c) are there some ports that needs to be opened in the machine where broker is installed? (Z/OS)?

3) I am not able to run mqsichangetrace/mqsireadlog/mqsiformatlog commands. So without debugger and without these commands its very difficult for me to do the development. I need to know what rights do I need to have to be able to run these commands on broker dev machine? I do have putty access to that machine. but when I type those commands they dont work - Command not found. My best guess is that we dont require any specific rights, we just need to either add the mqsi installer bin path in our environment PATH or go to that path and run the commands. As of now I am not aware of the exact location of installation. But can someone confirm on this pls?

4) While trying to put message on any of the queues, there is no simple way for me as of now. (They have a client specific home built tool, which is very cumbersome and expires irrationally with many other issues). I tried using rfhutil, I got ih03 supportpac on my remote windows machine and used rfhutilc for the queue manager after making the .bat file (I used to do like this in my previous project too, so I am sure the .bat file is perfect and even the qmgr and port info is correct). But when I start the batch file, in the server name I am able to view queue manager channel but when I try to load queue or open any queue, it does NOT SHOW ANYTHINg. when i try to load it says error in getting queues. Any ideas about this pb?

5) As of now my only way of testing is using trace nodes. Any other way anyone is aware of?

6) and the last) Is it an environment that is common for ppl working on broker? This is my first exp to work in an environment like this

If I come to know of this answer, I can ask my upper management to take some other steps to ensure that these things are provided to our dev team.

Regards,
NK