OFS - Possible to reject a mesg thru IN.MSG.RTN?

Hi,

is it possible to reject an incoming mesg through the routine attached in IN.MSG.RTN? we need to carry out some validations in the incoming message coming frm an ext system thru TCServer. if it fails, is it possible to reject and respond directly through the routine attached in IN.MSG.RTN?

IN.MSG.RTN is used to convert or map the data received into the required OFS message format. If I am not mistaken you can't reject the message here.

Tnx. so when a mesg is received at TCServer end, it has to reach T24 to know the fate of it. is my understanding ryt?

Hi Saran,

If you want to do validations like checking the format of ID or number of characters in the message, i think you can do it by adding a routine in IN.MSG.RTN but not sure how to display the results... may be you can write the output of the validations in a flat file of a directory.

Yes. The message has to hit T24 to get a response. You can also try adding the validations you want to do in the version routines.

Please mention your expectation clearly, we can do it N number of ways,

1) by modifying the in message
2) addition rtn in version level
but the point is what kind of transaction u gonna perform and what kind of updation u r expecting ?

I would like to validate the incoming message thru IN.MSG.RTN (coming from an external interface through tcserver); if there is any issue in the incoming message, i would like to reject it directly thru the IN.MSG.RTN (Dont want the processing to go ahead where T24 processes it and then responds)

incoming messages can be for ENQUIRY or for FT

Hi Saran,

Is your problem solved or still looking for answer? Please do let me know which T24 release you are working on.

Everyone response above is right somehow but YES you can do it from IN.MSG.RTN but response will always go through OUT.MSG.RTN without hitting T24 as I just completed one interface in which I am checking message type and security to ensure that message is coming from trusted source (meaning only from external system for which I created interface) so if message type is wrong then I send Error message to external system as SECURITY VIOLATION ---- API ERROR this my generated error and my transaction do not hit T24. I generate this error in IN.MSG.RTN and send it through OUT.MSG.RTN.

No, i haven't got it solved. Could you share the info, if possible, on how you are rejecting the incoming messages w/o hitting T24...

Hi Saran,

Is your issue solved?

What I was saying that;

1. Create i_common that will be use in IN and OUT routine of OFS
2. then do validation of the msg in IN routine and if there is an error then null your incoming msg variable and save error in common variable that you defined in your own created I_common file.
3. check and extract value or error from common variable in OUT routine and assign that value of variable to your incoming variable of OUT routine and also assign null to common variable.

I did this in one of the interface and it is perfectly running on production system of my client.

Thanks for the clue; will try and update!

This is a sample routine, i would like to convert input currency from ZiG to ZWL. If any other currency comes it should be ignored. kindly guide me on the steps I need to take in OFS.SOURCE to achieve this I'm on TAFC R14.

SUBROUTINE SN.FORCE.ZiG.CONVERSION.VER(OUT.MSG)
 
 INSERT I_COMMON
 INSERT I_EQUATE
 
 IF DEBIT.CURRENCY = "ZiG" THEN 
 DEBIT.CURRENCY = 'ZWL'
 
RETURN
END

Hi
do I understand you correctly that you want the OFS message to be "canceled" if currency isn't "ZiG" ?

No, I want the message to be amended to "ZWL" instead of "ZiG"

so ordinarily it should be ECHANGE(CURRENCY, "ZiG" , "ZWL")

Hi
see my reply in your other (same) request. Let's continue there.