ROLLBACK on RUN()

[soltyskamil]

I have two Cards.
In First one call I with RUN() a map that check duplicity of message and saves Audit Info if no duplicate message found.
The Second Card is proofing the return code. If no duplicity found and Audit Infos saved, it writes the message on the Output Queue.

Problem: If message could not be written onto Out-Queue map makes Rollback - but not on the map called in run function (Audit Infos ar not rollbacked!)
How can I do this?
Any Tips? (Sorry my Englisch)

 

[BocaBurger]

What does the RUN map write to? If all maps and cards are set to a scope or map, everything should be rolled back.

Also, what version and platform are you running on. In older versions there was a problem in this area.



BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!

 

[soltyskamil]

Platform: Mercator 6.7.1 on AIX 5.1
All cards are running in Scope Map.
The map writes a notification about the message to DB (ORA 9.2).
Today have I probably found a Problem: the Mercator crashes completely (SIGSEGV) on the next card. The Card writes the message on to not existing OraAQ. This can be a problem why can be not the transaction rolled back. I have tryed use the VALID(PUT("AQ",...)) function, with same result. Why crashes AQ Adapter all the maps?
Any Idea?
Thanks.

 

[BocaBurger]

Well, if the crash was while the map was running, it should be "rolled back", actually, since it is to a DB, we would not have sent the commit, thus, if the data is still there, check with your DBA.

The PUT function has almost not error handling, use the RUN function. Make sure your environment points to the oracle /libs32 and not to /libs.





BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!