TIBCO Rendezvous and MQ
Hi, I would like to ask the compatibility of TIBCO Rendezvous and MQ APIs. Thank you in advance. We have a C++ program running on HP-UX listening and sending TIBCO Rendezvous messages. Is it possible adding the MQ publishing and subscribing API there? Anybody has such experience? Our program is single-threaded, and changing to multi-thread is not probable. I am not sure whether there is conflict between the event handling of TIBCO and MQ. I would like to avoid explicitly polling for receival of the 2 messages. Thanks Yip __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.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: AW: Anyone have a CHAD exit Sample for MVS
Hi,
When MQXCC_SUPRESS_FUNCTION is returned channel goes to retrying state
and exit continues to print the same log every time it retries. Is there any
way to restrict it?.
I think we can change connection name to an Invalid value and Set Short
and Log retry count to 0, but we have to return MQXCC_OK for these changes
to take effect.
Regards
Mahesh
- Original Message -
From: Raabe, Stefan [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, June 12, 2003 1:30 PM
Subject: AW: Anyone have a CHAD exit Sample for MVS
i did some tests with a chad some time ago, its in c and it was on
unix, but maybe its of use too. i used it to output some fields
and to wipe out the security exit name in a cluster sender
channel.
i know its hard to find a sample (i did not found any at that time).
hope it helps.
regards, stefan.
#include stdio.h
#include stdlib.h
#include string.h
#include time.h
#include cmqc.h
#include cmqxc.h
MQCHANNELAUTODEFEXIT MY_MQ_CHANNEL_AUTO_DEF_EXIT;
FILE *log;
char buf[100] = ;
char myexit[128] = ;
void MQStart() {;} /* dummy entry point - for consistency only */
void MQENTRY MY_MQ_CHANNEL_AUTO_DEF_EXIT ( PMQVOID pChannelExitParms,
PMQVOID pChannelDefinition)
{
PMQCXP pCEP = pChannelExitParms;
PMQCD pCD = pChannelDefinition;
time_t t1;
log=fopen(/var/mqm/cadlog.txt,a);
// do a log entry
(void) time(t1);
strcpy(buf,cad exit started - version 1.0012);
fprintf(log,%s - %s \n, ctime(t1), buf);
// ... Insert code here
// assume we do not allow the channel autodefinition
pCEP-ExitResponse = MQXCC_SUPPRESS_FUNCTION;
strcpy(buf,ExitReason: );
if (pCEP-ExitReason==MQXR_INIT)
{
strcpy(buf, CAD-EXIT Init Call, Returning MQXCC_OK);
fprintf(log,%s \n, buf);
pCEP-ExitResponse = MQXCC_OK;
}
else
{
if (pCEP-ExitReason==MQXR_TERM)
{
strcpy(buf, CAD-EXIT Termination Call, Returning MQXCC_OK);
fprintf(log,%s \n, buf);
pCEP-ExitResponse = MQXCC_OK;
}
else
{
CXP_output(pChannelExitParms);
CD_output(pChannelDefinition);
if (pCEP-ExitReason==MQXR_AUTO_CLUSSDR)
{
if (strncmp(pCD-SecurityExit,MQMCHLX,7) == 0)
{
fprintf(log, !
erasing
channel security exit name %s \n, pCD-SecurityExit);
strncpy(pCD-SecurityExit, ,7) ;
}
}
pCEP-ExitResponse = MQXCC_OK;
}
}
// do a log entry
(void) time(t1);
strcpy(buf,cad exit ended);
fprintf(log,%s - %s \n, ctime(t1), buf);
fclose(log);
}
int CXP_output(PMQVOID pChannelExitParms)
{
PMQCXP pCEP = pChannelExitParms;
//
// now output cxp values
//
strcpy(buf, cxp structure output:);
fprintf(log,%s \n, buf);
strcpy(buf,strucid: );
strcat(buf, pCEP-StrucId);
fprintf(log,%s \n, buf);
fprintf(log,Version: %d \n, pCEP-Version);
// strcpy(buf,Version: );
//
// ch_ptr = (char *) pCEP-Version;
//
// switch (pCEP-Version)
// {
//case MQCXP_VERSION_1:
// strcat(buf,MQCXP_VERSION_1);
// break;
//case MQCXP_VERSION_2:
// strcat(buf,MQCXP_VERSION_2);
// break;
//case MQCXP_VERSION_3:
// strcat(buf,MQCXP_VERSION_3);
// break;
//case MQCXP_VERSION_4:
// strcat(buf,MQCXP_VERSION_4);
// break;
//default:
// strcat(buf,!!! unknown Version number );
// break;
// }
// fprintf(log,%s \n, buf);
strcpy(buf,ExitId: );
switch (pCEP-ExitId)
{
case MQXT_CHANNEL_SEC_EXIT:
strcat(buf,Channel Security Exit);
break;
case MQXT_CHANNEL_MSG_EXIT:
strcat(buf,Channel Message Exit);
break;
case MQXT_CHANNEL_SEND_EXIT:
strcat(buf,Channel Send Exit);
break;
case MQXT_CHANNEL_RCV_EXIT:
strcat(buf,Channel Receive Exit);
break;
case MQXT_CHANNEL_MSG_RETRY_EXIT:
strcat(buf,Channel Message Retry Exit);
break;
case MQXT_CHANNEL_AUTO_DEF_EXIT:
strcat(buf,Channel Auto Definition Exit);
break;
default:
strcat(buf,!!! unknown Channel Exit Point);
break;
}
fprintf(log,%s (%d) \n, buf, pCEP-ExitId);
strcpy(buf,ExitReason: );
switch (pCEP-ExitReason)
{
case MQXR_INIT:
strcat(buf,MQXR_INIT);
break;
case MQXR_TERM:
strcat(buf,MQXR_TERM);
break;
case MQXR_MSG:
strcat(buf,MQXR_MSG);
break;
case MQXR_XMIT:
strcat(buf,MQXR_XMIT);
break;
case MQXR_SEC_MSG:
strcat(buf,MQXR_SEC_MSG);
Re: Queue sharing Groups and RRS
Stewart, I think you don't have all the books needed for this. First of all, which version of MQ are you using if it is 5.2 upgrade to 5.3 first. If you are on 5.3, all you have to do is in the SCSQPROC and in the System Setup Guide. If this does'n 't help send me an email and tell me what you want to know exactly. Regards, Erik Dijkerman X Rabobank ICT/Serverbedrijf PIM/OS390 ZL-S206400 Mailbox 17100, 3500 HG Utrecht *(030) 215 4878 *(030) 215 3085 ? [EMAIL PROTECTED] The greatest mistake a man can make is to be afraid of making one. --Elbert Hubbard -Oorspronkelijk bericht- Van: Herd, Stewart [mailto:[EMAIL PROTECTED] Verzonden: vrijdag 4 juli 2003 10:32 Aan: [EMAIL PROTECTED] Onderwerp: Queue sharing Groups and RRS Dear All, Perhaps some of you could enlighten me on this subject, we are currently setting up a SYSPLEX where we will utilize Queue Sharing groups and whilst attempting to define these we ran into a problem because an OS/390 component RRS was not running as a started task, thus the QSG's could not be defined. After investigation we required both RRS and ARM to be running to facilitate moving forward with this but then we came across something called 'POLICIES' which seems to need some effort from both DB2 and MQ areas, I have found very little online explaining this concept so I would be very grateful if someone could either explain the relationship between MQ and these 'policies' or point me to an article or publication that explains the relationship. Thanks in advance for any help Stewart Stewart Herd Senior Software Engineer Systems Engineering Services ACS NSC Campus Loughmahon Technology Park Cork Ireland De informatie opgenomen in dit bericht kan vertrouwelijk zijn en is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onterecht ontvangt, wordt u verzocht de inhoud niet te gebruiken en de afzender direct te informeren door het bericht te retourneren. The information contained in this message may be confidential and is intended to be exclusively for the addressee. Should you receive this message unintentionally, please do not use the contents herein and notify the sender immediately by return e-mail. 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: TIBCO Rendezvous and MQ
Hi Yip, You can use MQ APIs in your C++ program along with the TIBCO Rendezvous APIs or TIBCO SDK APIs. You need to compile yourC++ programm along the required Libararies of MQSeries (eigther client orserver Lib). For info on which lib to use, you can refer 'Getting Started' pdfof MQSeries. I have used TIBCO SDK APIs along with MQ APIs in C++ and TIBCO Rendezvous APIs along with MQ APIs in JAVA. You can add MQ Publishing APIs ( PUT ) in your TIBCO Subscriber program. Simillarly,you can add TIBCO Publish API ( send ) in your MQ Get program. To get the message from MQ you have to poll the Queue. But it is possible to use Tibco's publish APIs in the same programe. You can n't avoid polling MQ Queue for getting the messages. Thanks,arul da doss Lai Chun Yip [EMAIL PROTECTED] wrote: Hi,I would like to ask the compatibility of TIBCO Rendezvous and MQ APIs.Thank you in advance.We have a C++ program running on HP-UX listening and sending TIBCORendezvous messages. Is it possible adding the MQ publishing andsubscribing API there? Anybody has such experience?Our program is single-threaded, and changing to multi-thread is notprobable. I am not sure whether there is conflict between the eventhandling of TIBCO and MQ. I would like to avoid explicitly polling forreceival of the 2 messages.ThanksYip__Do you Yahoo!?SBC Yahoo! DSL - Now only $29.95 per month!http://sbc.yahoo.comInstructions for managing your mailing list subscription are provided inthe Listserv General Users Guide available at http://www.lsoft.comArchive: http://vm.akh-wien.ac.at/MQSeries.archive Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month!
UNSUBSCRIBE
DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Thank you. 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: Weird triggering problem
... and I am no novice. well, you seem to be a novice with starting applications in the fore- or background. Just kidding ..., sorry. if you want to launch a GUI application, it must be run in the foreground. If you start it with a service, you'll have it running in the background. Of course you can't seethem on your screen,they are all in the background, "spawned"fromthe runmqtrm service. This is not just for NT, try typing this command in UNIX:"vi ", can you see the editor window? So if you want to start your GUI in the foreground, let it be triggered by a trigger monitor running in the foreground - command line. cheers, Benjamin Zhou State Street Corp. -Original Message-From: Roger Lacroix [mailto:[EMAIL PROTECTED]Sent: Friday, July 04, 2003 6:55 PMTo: [EMAIL PROTECTED]Subject: Weird triggering problemAll,I am having a problem with triggering from the "Trigger Monitor as a Service". I need to launch a GUI Windows program on a Windows 2000 box using WMQ v5.3 CSD3. No matter what I do, I cannot trigger my GUI Windows application (and I am no novice). So I thought I would do a basic test and launch notepad. In the process definition, I set the AppID to "start C:\WinNT\notepad.exe"I created the Trigger Monitor service and used a blank as the initiation queue name (this defaults to SYSTEM.DEFAULT.INITIATION.QUEUE).So put a message on the triggering queue nothing happens. I cleared the queue and tried it several times - nothing.So I stopped the Trigger Monitor service, open a Command Prompt and typed runmqtrm.exe (no parameters specified!!). I put a message on the triggering queue (same queue) and viola, notepad appeared. (I did not change any of the queue or process definitions). So, I stopped runmqtrm at the Command Prompt (closed notepad), started the Service Trigger Monitor and put a message on the triggering queue - nothing againAfter using IBM's name in vain, I checked the Windows Task Manager. Under the "Applications" tab, it was normal looking but under the "Processes" tab it showed that I had 5 notepad programs running. I also noticed several copies of my missing program that I did not think was started. So I looked at my Taskbar and also pressed Alt-Tab, there were no notepad programs (or my GUI appl.). If I try to kill them, I get "Access denied". The only way to get rid of them is by rebooting.I looked in the manuals but I don't see any restrictions about launching GUI applications from the Service Trigger Monitor. Obviously the simple solution is to run the trigger monitor from the Command Prompt but WHY. Why can't Trigger Monitor as a Service successfully start a Windows GUI application? (i.e. AppID set to "start C:\WinNT\notepad.exe")Anybody got any ideas?laterRoger...
Re: md.ReplyTo.. processing - why?
Thanks, Neil. that does make more sense. I only have a handful of queue managers, and can see how the administration problem might look different with many more spokes. Bill -Original Message- From: Neil Casey [mailto:[EMAIL PROTECTED] Sent: Thursday, July 03, 2003 6:00 PM To: [EMAIL PROTECTED] Subject: Re: md.ReplyTo.. processing - why? Hi Bill, the existing design works for both the common case, and for directing a response to some other queue manager. It is important to have the queue manager fill in its own ReplyToQMgr field. Imagine a network with 1000 windows queue managers connected to a hub. 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
UNSUBSCRIBE
Title: Message
UNSUBSCRIBE
Title: UNSUBSCRIBE
UNSUBSCRIBE
Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger
UNSUBSCRIBE
RBC Dain Rauscher does not accept buy, sell or cancel orders by e-mail, or any instructions by e-mail that would require your signature. Information contained in this communication is not considered an official record of your account and does not supersede normal trade confirmations or statements. Any information provided has been prepared from sources believed to be reliable but is not guaranteed, does not represent all available data necessary for making investment decisions and is for informational purposes only. This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you receive this e-mail in error, please advise me (by return e-mail or otherwise) immediately. Information received by or sent from this system is subject to review by supervisory personnel, is retained and may be produced to regulatory authorities or others with a legal right to the information. 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: Weird triggering problem
You can set a service to run in the foreground. Under services\Log On you need to set it up running under the local system account and select allow service to interact with the desktop. I havent personally tried with MQSeries, but it may be worth a try. It also may have unexpected and unwanted side-effects. Regards, ___ Chris Howarth CommerceQuest UK Ltd -Original Message- From: Benjamin Zhou [mailto:[EMAIL PROTECTED] Sent: 07 July 2003 13:41 To: [EMAIL PROTECTED] Subject: Re: Weird triggering problem ... and I am no novice. well, you seem to be a novice with starting applications in the fore- or background. Just kidding ..., sorry. if you want to launch a GUI application, it must be run in the foreground. If you start it with a service, you'll have it running in the background. Of course you can't seethem on your screen,they are all in the background, spawnedfromthe runmqtrm service. This is not just for NT, try typing this command in UNIX:vi , can you see the editor window? So if you want to start your GUI in the foreground, let it be triggered by a trigger monitor running in the foreground - command line. cheers, Benjamin Zhou State Street Corp. -Original Message- From: Roger Lacroix [mailto:[EMAIL PROTECTED] Sent: Friday, July 04, 2003 6:55 PM To: [EMAIL PROTECTED] Subject: Weird triggering problem All, I am having a problem with triggering from the Trigger Monitor as a Service. I need to launch a GUI Windows program on a Windows 2000 box using WMQ v5.3 CSD3. No matter what I do, I cannot trigger my GUI Windows application (and I am no novice). So I thought I would do a basic test and launch notepad. In the process definition, I set the AppID to start C:\WinNT\notepad.exe I created the Trigger Monitor service and used a blank as the initiation queue name (this defaults to SYSTEM.DEFAULT.INITIATION.QUEUE). So put a message on the triggering queue nothing happens. I cleared the queue and tried it several times - nothing. So I stopped the Trigger Monitor service, open a Command Prompt and typed runmqtrm.exe (no parameters specified!!). I put a message on the triggering queue (same queue) and viola, notepad appeared. (I did not change any of the queue or process definitions). So, I stopped runmqtrm at the Command Prompt (closed notepad), started the Service Trigger Monitor and put a message on the triggering queue - nothing again After using IBM's name in vain, I checked the Windows Task Manager. Under the Applications tab, it was normal looking but under the Processes tab it showed that I had 5 notepad programs running. I also noticed several copies of my missing program that I did not think was started. So I looked at my Taskbar and also pressed Alt-Tab, there were no notepad programs (or my GUI appl.). If I try to kill them, I get Access denied. The only way to get rid of them is by rebooting. I looked in the manuals but I don't see any restrictions about launching GUI applications from the Service Trigger Monitor. Obviously the simple solution is to run the trigger monitor from the Command Prompt but WHY. Why can't Trigger Monitor as a Service successfully start a Windows GUI application? (i.e. AppID set to start C:\WinNT\notepad.exe) Anybody got any ideas? later Roger...
Workflow File System Requirements
I am running out of space during an fdl deploy in Workflow. I would like to know if anyone has good information on what and how large the file systems should be. The error message is not very informative so I am not sure if I am running out of space in DB2 or Workflow. Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month!
Re: Multiple JMS Message Listeners
-Original Message- From: mikhail malamud [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 02, 2003 10:03 PM To: [EMAIL PROTECTED] Subject:Re: Multiple JMS Message Listeners Neil - It might be beneficial to have multiple listeners per session when each listener will be passed a distinct selector. - Original Message - From: Taylor, Neil [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, July 02, 2003 6:33 AM Subject: Re: Multiple JMS Message Listeners Sumeet JMS Sessions are, according to the JMS Specification, single threaded. Hence, all listeners created against a single session will be sequential - so no obvious benefit in having mutiple listeners that I can think of. However, if you create and use a seperate listener, PER SESSION, then you should get better performance. I say should, because I haven't tried it out yet. I do know, however, that it is not thread-safe to share the SAME listener instance accross mutiple sessions. To answer your question, I would have thought (but again, don't know for sure) that the mutiple sessions, each with its own listener, woud give the best throughoput, at a higher processing and memory cost. I guess that the optimum solution depends on your message volumes and time criticality. HTH Neil -Original Message- From: Sumeet Khosla [mailto:[EMAIL PROTECTED] Sent: 02 July 2003 06:39 To: [EMAIL PROTECTED] Subject: Multiple JMS Message Listeners Hi all, We are having a requirement where we need to process multiple messages (on a queue) simultaneously. One approach to that is to have multiple listeners associated with the same queue so that concurrent processing of messages can happen. I have tried two approaches for implementing multiple listeners which are as below: a) I create the QCF, Q, QConnection QSession and pass on the session to my listener class constructor and it creates receiver out of that session and sets the message listener class as message listener for the given Q. I am creating for listeners in this manner. b) I create the QCF, Q, QConnection and pass on the connection to my listener class constructor and it creates QSession and then receiver out of that session and sets the message listener class as message listener for the given Q. I am creating 4 listeners in this manner. I wanted to know which approach is better in terms of resource consumption, performance and on any other points. The time taken to process the messages was more in case of multiple listeners being created from a single session than multiple listeners being created from multiple sessions for 40 messages. Another observation was in case of multiple sessions, all the 4 listeners were used simultaneously, as in each group of 4 messages was processed by the four listeners simultaneously. In case of single session, the first 2 listeners were only used. If I add a sleep time of 2000 then four listeners are used but that too sequentially, first 10 msgs being taken by first listener, next 10 by second listener and so on... Thanks Regards, Sumeet Khosla 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 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- The information contained in this message is proprietary of Amdocs, protected from disclosure, and may be privileged. The information is intended to be conveyed only to the designated recipient(s) of the message. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, use, distribution or copying of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. -
Teh Gary/APRS/SCB is out of the office.
I will be out of the office starting 07/07/2003 and will not return until 07/23/2003. I will be away in ISCI. I will respond to your message when I have the chance to check my emails. -- THIS EMAIL, AND ANY ATTACHMENTS (THIS EMAIL), IS CONFIDENTIAL. IF YOU ARE NOT THE ADDRESSEE PLEASE TELL THE SENDER IMMEDIATELY, AND DESTROY THIS EMAIL WITHOUT USING, SENDING OR STORING IT. ANY OPINIONS, EXPRESS OR IMPLIED, IN THIS EMAIL, ARE THOSE OF THE SENDER, AND ARE NOT NECESSARILY APPROVED BY STANDARD CHARTERED GROUP (SCGROUP). EXCEPT AS EXPRESSLY STATED, THIS E-MAIL SHOULD NOT BE REGARDED AS AN OFFER, SOLICITATION, RECOMMENDATION OR AGREEMENT TO BUY OR SELL INVESTMENTS, SECURITIES, INSTRUMENTS OR BANKING PRODUCTS, OR TO ENTER INTO ANY CONTRACT. E-MAIL TRANSMISSIONS ARE NOT SECURE AND MAY SUFFER ERRORS, VIRUSES, DELAY, INTERCEPTION AND AMENDMENT. SCGROUP DOES NOT ACCEPT LIABILITY FOR DAMAGE CAUSED BY ANY OF THE FOREGOING.. SCGROUP MAY MONITOR OUTGOING AND INCOMING E-MAILS. -
UNSUBSCRIBE
UNSUBSCRIBE Kinlen, Dan [EMAIL PROTECTED] Sent by: MQSeries List [EMAIL PROTECTED] 07/07/2003 08:23 PM Please respond to MQSeries List To:[EMAIL PROTECTED] cc: Subject:UNSUBSCRIBE RBC Dain Rauscher does not accept buy, sell or cancel orders by e-mail, or any instructions by e-mail that would require your signature. Information contained in this communication is not considered an official record of your account and does not supersede normal trade confirmations or statements. Any information provided has been prepared from sources believed to be reliable but is not guaranteed, does not represent all available data necessary for making investment decisions and is for informational purposes only. This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you receive this e-mail in error, please advise me (by return e-mail or otherwise) immediately. Information received by or sent from this system is subject to review by supervisory personnel, is retained and may be produced to regulatory authorities or others with a legal right to the information. 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
