Hello !
Regarding your last message: collaborations (also subcollaboration) receive input events as a strings. This is true also about collaborations result - events are returned as a strings.
So, problem (AFAICS) is that MSG variable, probably, is event map and we can't assign string to this...
Hello !
All the things You are doing are right, except one small error.
Check in "Monk Developer’s Reference" difference between let and set! functions. In your code Your should use either set! function with prior variable definition, either You should include count un prior LET...
Hello !
You can`t change e*way settings directly from collaborations: they (collaborations) run in its own environment and e*way configuration variables just not visible from this point.
What You can do is to add into your .ssc one more node which will hold desired filename.
Then You have to...
Hello !
Yes. It is possible. And it works just fine.
I have two (development and testing) e*Gate instances on Solaris.
HOW-TO:
1. Create two+ user accounts on your unix box and
install two+ instances of e*Gate - each under created account.
2. Edit your rc files - you should give each registry...
Q: How to convert DATE in string from one format into another ?
Hello!
Sometimes there is need to reformat DATE which is represented as
string from one format into another (e.g. from "DD.MM.YYYY" to
"YY MON DD").
The very first solution of this problem you could think about is...
hi
it was much fun fo me when i try this first time :)
Check your schema (e*ways and collaborations), set Log to DEBUG level and check MNK, MSG, CFG, REG, IQ on e*Ways and IQmanager. Check your IQ - is it empty or filled with Your data ?
Regards
hello ncaffee!
I had similar problem and i've found a solution.
But why do You want to stop it ? And do you need to read all record from view each time ?
If not U could define global variable with timestamp of last reading from view and control it programmaticaly.
I mean: read records from view...
Hi!
IMHO, its quite easy. Just add additional node into ETD where
sending e*Way will put timestamp before publishing this into IQ.
And at the "end"-e*Way compare current time with the time
in your node. Of course, time should be synchronised on both (starting and ending) hosts.
AFAIK...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.