Pavel, One technique would be to write a wrapper for the command server. The wrapper uses and extends the PCF formats and monitors the command queue. Any commands that it knows about are handled by the wrapper. Any commands it does not know about are passed to the command server. The wrapper can provide extended services (display and manipulate OAM settings for example) and can also extend the security model. The only tricky part is to edit the amqpcsea binary to make it look at some queue *other than* the command queue.
-- T.Rob -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Pavel Tolkachev Sent: Wednesday, June 30, 2004 10:30 AM To: [EMAIL PROTECTED] Subject: Re: Command Server Working Mechanisms Hello Michael, Thanks for the answer. The answer to your questions is "both and more". More is that we have some controlling/monitoring process on Unix and Windows that uses server-side MQI and if we were able to do what command server does based on PCFs, we wouldn't require this yet another process (yes, having it has security implications and also potentially affects resources and complexity and increases the number of moving parts). I feel that using runmqsc is not better (rather, worse), than using command server for our purpose. So I just wanted to know whether or not there is an API that command server (and, for this purpose, runmqsc) use to do their job that our process could use or it is all platform-specific and undocumented. We really want bare bones or the lowest level available for the MQ administration software. Thank you, Pavel Michael Dag <[EMAIL PROTECTED] To: [EMAIL PROTECTED] ET.NL> cc: Sent by: MQSeries Subject: Re: Command Server Working Mechanisms List <[EMAIL PROTECTED] n.AC.AT> 06/29/2004 05:50 PM Please respond to Michael.Dag Pavel, the only 'process' that can create queues, etc... WITHOUT command server running is: runmqsc If you look at the runmqsc.exe for example on Windows, you'll notice it is a very small program... The API that runmqsc uses into QMgr is very obscure and IBM internal as I have understood. Now the important question... why do you not want to run the command server and find something to replace it. Is it educational or are you driven by potential security exposures? Michael -----Oorspronkelijk bericht----- Van: MQSeries List [mailto:[EMAIL PROTECTED] Pavel Tolkachev Verzonden: Tuesday, June 29, 2004 11:25 PM Aan: [EMAIL PROTECTED] Onderwerp: Re: Command Server Working Mechanisms Thanks Tim, We (Monique and myself are working together) are actually not after that book. The book says how to do things when the command server is running; our purpose is to understand if it is possible to write monitoring application that does not require command server to, for example, create a queue, but does it "instead of the command server". Is my suspicion correct that the command server works on a low level and there is no cross-platform API it uses to create a queue? Thank you in advance, Pavel Tim Armstrong <[EMAIL PROTECTED] To: [EMAIL PROTECTED] YER.COM.AU> cc: Sent by: MQSeries Subject: Re: Command Server Working Mechanisms List <[EMAIL PROTECTED] .AT> 06/29/2004 05:07 PM Please respond to MQSeries List The manual you are after is "Programmable Command Formats and Administration Interface" and its not easy. Any given single thing is relatively easy to do but there are an awful lot of things you can do. Regards Tim A -----Original Message----- From: Monique Diaz [mailto:[EMAIL PROTECTED] Sent: Wednesday, 30 June 2004 5:58 AM To: [EMAIL PROTECTED] Subject: Command Server Working Mechanisms Hi, I would like to know the API or mechanisms used by Command Server to perform administrative tasks(eg create a queue) on the Queue Manager. Is there any API that I could use to write my own command server for Unix and / or Windows? Monique 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. -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. 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 -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. 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