Craig,
>>I didn't realise there were debug logs available, any suggestions on
where I should look?
Not sure what you need to check in the trace logs. I assume you
application is working okay or are debugging are existing issue?
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
this policy.
Regards
David
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
