The current interface works but is frustrating as the environment setup is
difficult to track down.
The AMI (which are the libraries U2 use to access MQ) is now deprecated so
AMI configuration info is hard to find.
Also there is no support for MQ transactions in the BASIC API -- so once you
get a message, make sure you don't abort :).
IBM have been promising a better interface for ages using the MQI or
similar.
David Hona supplied me with the following information which was invaluable
in getting the thing to work:
Before we execute the BASIC application with the U2AMI calls, we defined
what AMI respository we want to use and then setup the optional AM_TRACE
variables (unset them to remove). The logs can be very details (esp.
level 9), so they need to be turned off. This on Sun Solaris
environment...UV 10.1.18:
SETMQENV
001 PA
002 ENV AMT_REPOSITORY=dmms_amt.xml
003 env AMT_HOST=amthost.xml
004 ENV AMT_TRACE_PATH=/DMMSDEV/DAVID/LIVE/&HOLD&
005 ENV AMT_TRACE_LEVEL=9
006 ENV AMT_TRACE=yes
007 ENV AMT_DATA_PATH=/DMMSDEV/DAVID/LIVE
In the above example, log files named AMTnnnnn.TRC are written out to
/DMMSDEV/DAVID/LIVE/&HOLD&. Unset AMT_TRACE to toggle tracing on/off.
More details on AMI tracing, etc are in this IBM document:
ftp://ftp.software.ibm.com/software/ts/mqseries/library/books/amtyak04.p
df
I am uncertain if this has anything to do with your issue...but I did
notice the following in the U2AMI.H include file in UNIVERSE.INCLUDE:
---snip---
**********************************************************************
** *
** Wait time constant for use with: *
** amPolGetWaitTime *
** amPolSetWaitTime *
** *
**********************************************************************
EQUATE AMWT_UNLIMITED TO -1
---snip---
According to the AMI documentation....
amPolGetWaitTime - Returns the wait time (in ms) set for this policy.
amPolSetWaitTime - Sets the wait time for any receive function using
HTH,
Craig
this policy.
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
