Re: Configuring Multiple Channel Exits
Thanks David. That was a very useful piece of information. Another question at this point. If I need to set 2 MsgExits on my Auto-Defined CLUSSDR channel, then I should set this in MsgExitPtr and set the MsgExitsDefined to 2. If, on the CLUSRCVR channel no MsgExits were set, then the MsgExitPtr will initially point to NULL. Does this mean thatmy Auto-Definition Exit should allocate the required memory to hold the Exit List ( from your previous information this will be "2*ExitNameLength" bytes. This memory cannot be freed by my exit. Who will free it then? Also, if the CLURCVR has 1 MsgExit configured, then when I override this with my 2 MsgExits, again I have to allocate memory to hold my 2 exit names and point MsgExitPtr to this allocted memory. Is my above understanding of the problem correct on the first hand? Is the approach of allocating the memory in my exit and pointing the ExitPtr to this memory the correct way of solving this? Thanks in advance. Shailesh Kumar - Original Message - From: David C. Partridge To: [EMAIL PROTECTED] Sent: Tuesday, September 02, 2003 2:08 PM Subject: Re: Configuring Multiple Channel Exits 1) Each field is the length of ExitNameLength, which isn't necessarily the same as MQ_EXIT_NAME_LENGTH. The total length (pointed to e.g. by MsgExitPtr) will be ExitNameLength times ExitNameLength. 2) IIRC, If the QM supports chained exits, then it will always use MsgExitsDefined, and MsgExitPtr rather than MsgExit. Be warned, on 390, the MQCD version may be incorrectly set in a clustered environment (too high a level) and so an 0C4 may not be far away if you totally trust it. There was an APAR raised for this in MQ 2.1 (can't remember if it was PQ39541, or PQ41371), and it may have also applied to 5.2. Dave
Configuring Multiple Channel Exits
Hi,
I am trying to set the channel exit attributes in my
Auto-Definition Exit.
From MQ Documentation I found that, to do this, I need
to setthese values using the MQCD-MsgExitPtr, MQCD-SendExitPtr
etc... I should also set the MQCD- MsgExitsDefined,
MQCD-SendExitsDefined etc. to the number of exits I need to set.
Using MQSC commands, I set multiple exits as follows.
ALTER CHANNEL(TEST.CH) CHLTYPE(CLUSSDR) .
MSGEXIT('exit1(MsgExit),exit2(MsgExit)').
In AutoDefinition exit, Document says, to configure multiple exits, I need
to use multiple fields each of length MQ_EXIT_NAME_LENGTH(128 bytes)(with
blank padded on the right).
Questions:
1. Is the total string length pointed by MQCD-MsgExitPtr
is 128 or each field is 128.
2. Can I use MQCD-MsgExit instead of MQCD-MsgExitPtr?
Regards Shailesh Kumar
Platform information in MQ Exits
Hi all, I am Required to write an Exit which involves logic, whichrequires to know the "Partner Queue Manager's Platform". i.e. If QM1 and QM2 are queue managers running on Solaris and Windows-NT respectively, and a channel QM1.TO.QM2 is configured between them, can an Exit configured on this channel on QM1 find out that it is connecting to a queue manager running on Windows-NT. Is there anyway I can get this in my Exit? If not, is there any indirect way todo this? Any help or reference is appreciated. Thanks in advance Shailesh Kumar
Re: Some cluster problems/questions
1)) To remove it completely from the cluster issue the following command on the repository queue manager and from wherever else you want to remove. RESET CLUSTER(MYCLUSTER) QMID(string) ACTION( FORCEREMOVE ) You can Get the QMID using the command DISPLAY CLUSQMGR(MYCLUSTER) ALL This will display the QManager ID with which it is recognized in the cluster internally. 2)) I don't know this but let me know when you get the answer. 3)) MQExplorer is just a window to your MQ Setup. So whatever is the results from the RUNMQSC command, same should be the behavior with the MQExplorer. - Original Message - From: Ruzi R [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, August 20, 2003 1:33 AM Subject: Some cluster problems/questions I would very much appreciate your responses to the following questions. I am gathering this info to help me with the major clustering work that I would be doing soon. 1- QM1 was a member of the cluster, and as it was not needed any longer, it was deleted by someone (not me, not me : )!) a long time ago before it was removed from the cluster following the steps indicated in the Queue Manager Clusters manual. The server housing the queue manager has long been removed from the network. But it is still displayed on MQ Explorer as, I think, the cluster still thinks that it is part of the cluster. It cannot even be made hidden on the Explorer as there is not connection to the qmgr. I cannot remove it from the cluster as it does not exist any more. I have just issued on the full repository: RESET CLUSTER(MYCLUSTER) QMNAME(QM1) ACTION(FORCEREMOVE) Is there anything else I can/should do to get rid of all references to QM1? Is QM1 going to keep showing on the MQ Explorer forever? 2- When I look at the clusters on the MQ Explorer on the machine housing the full repository, I see the same cluster displayed twice. Why? I can hide one of them from the display but I am wondering why it shows twice in the first place. 3-If I remove a member from a cluster gracefully (meaning, following the steps mentioned in the Cluster manual and not delete the queue manager afterwards, it won t try to rejoin the cluster after 90 days as it was not removed forcibly. Correct? Will it stay in the MQ Explorer display for 90 days, and then go away completely (from the display)? Thank you, Ruzi 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
