OFS Message in Multi Threaded Routine.

Process

Multi Threaded

Procedure

Execute the service File read from BP folder for post transaction in LIMIT application

Version: LIMIT,ABC
Behavior = NO.AUTH EQ 0, GTS Control Nill, VERSION.CONTROL nill no routine.
Only update the ADVICED.AMOUNT field in limit application.

FIle structure


254553^0011100.01^194707470
219206^0000100.01^26609645
237620^0000100.01^7311385
184316^0000100.01^279102800
300816^0005106.04^18850000
313222^0010100.01^5294773

Routine read the 1. customer record and 2. limit ref record concatenate limit ref and customer for creation ID of limit application then post the 3. amount field in limit application.

OFS.SOURCE
Tested Globus and telnet both.

Result

Successful posted the OFS.MSG on jshell in debug mode
but when I see the records on T24 prompt application level system show old record.
as on OFS.MSG has updated the CURR.NO as per sequence wise there is no override there is no any error.
On T24 classic, globus and Browser all three modes showing old curr number results its unbelievable for me.

Test Cases.

Case 1
1. through tSS results working fine OFS record updated on application level.
2. Change OFS.SOURCE from globus to telnet define user name and password as per OFS.SOURCE requirement but results was same curr.number updated on jshell/debug mode only but no affect on application.
3. created single line routine to post the successful txn in customer application and in limit application
4. created multi threaded routine to post txn in account application on jshell txn posted successful but on application there was old CURR.NO.
5. change the environment and test all the above cases but system behavior was same.

================END==================


There is any test case which I missed please tell me why this problem occur there is any solution or I lock this issue on HD.

JPB,
OFS.SOURCE log not checked by me because ofs service is posting the message accurately only the writing on application level behavior is unknown for.
In routine using CALL OFS.GLOBUS.MANAGER(OFS.SOURCE.ID,OFS.MSG)

Regards
Jawaid

I have post the ofs in account table in same routine with same ofs.source its working fine but in limit the ofs posted but on application level no transaction reflected..


Regards
Jawaid