Hi Craig We use U2AMI. It was a steep learning curve, but it all works well now...
I don't think I've ever seen a timeout error/issue when using amSendRequest. We do see it with amReceiveMsg though. However, this is not an issue for our application, when just try again...more specifically we simply check for "retCode # AMCC_OK" and for "reasonCode = AMRC_NO_MSG_AVAILABLE". I assume you're using the AMI Admin Tool? Can you be more specific? Where exactly are you setting your value you're expecting? I assume it's the "Receive" tab for the policy in question. Are you loading the correct policy file, before you invoke the U2AMI proxy client? Have you run any AMI debugging/trace logs? If you're going to be writing your own C, C++, COBOL or Java code -- and you want to use AMI, then this AMI guide is very handy... ftp://ftp.software.ibm.com/software/ts/mqseries/library/books/amtyak04.p df Regards David -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig Bennett Sent: Friday, August 03, 2007 3:39 PM To: [email protected] Subject: [U2] U2 AMI Interface Hi, is anyone actually using the U2AMI interface to talk to MQ Series? Have you experienced a problem where a timeout does not occur if your send a request with amSendRequest and no response is returned regardless of the timeout setting in the policy used? regards, Craig ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
