ABCS file format

[Didik Rawandi]

dear all,

is jpos can handle ABCS message format? i know this was not iso 8583 but can jpos handle it?



--
Best Regards,

Didik Rawandi
354

[Mark Salter]

Didik Rawandi wrote:

> is jpos can handle ABCS message format?
>

Any chance you have mis-typed this acronym?

> i know this was not iso 8583 but can jpos handle it?
>

Can you narrow the field further and describe what format it is?

JPos does provide a means of handling Field Separator Delimited (FSD)
messages, check the documentation, source and search this list to see if
that looks anything close to the ABCS format you seek?



--
Mark

[Chung vu]

If i am not wrong , ABCS format is from Silver Lake system ?

--
You received this message because you are subscribed to the  "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to jpos-...@googlegroups.com
To unsubscribe, send email to jpos-users+...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/jpos-users

[Didik Rawandi]

yes this was from silver lake system, can jpos handle this format? it was actually in ebcdic format

[Chung vu]

No , jpos cannot process it.
It is internal message . If you want to use , you ask for specification and mapping in jpos
I also want to handele it but SVL doen't give us specification . Do you have it ? If you have , i can help

Regards,
VDC

[Mark Salter]

Didik Rawandi wrote:
> yes this was from silver lake system, can jpos handle this format? it was
> actually in ebcdic format

The character set matters much less than the actual structure.

Did you take a look at FSDMsg at all? Any good for your needs?

Unless someone here has experience of this interface (and is
willing/able to share), you are going to have to bring a little more to
this discussion, so that others might be able to help.

Can you describe the ABCS message structure at all - "not ISO8583" is
not any help.

--
Mark

[Mark Salter]

Chung vu wrote:
> No , jpos cannot process it.

Ok, so we have an answer.

> It is internal message . If you want to use , you ask for specification and
> mapping in jpos

"Silver Lake" provide a translation (to ISO8583) interface?

> I also want to handele it but SVL doen't give us specification . Do you have
> it ? If you have , i can help

Please take care...

If "Siver Lake" don't always share the specification, there is likely a
good reason and protection in place.

Didik, could probably not legally share the detail with anyone Vu.


--
Mark

[Chung vu]

Correct , Mark is right!
From my SilverLake side , you protect it . If your side is okie , you can do !

Mark

[Chung vu]

Correct , Mark is right!

From my SilverLake side , SVL protects it . If your side is okie , you can do !

[Didik Rawandi]

I have sample message & spesification also, i want to share it but as you said mark i can not share this to you because of legality. so i will do it my self thanks for your answer guys.

1 question again it was for confirmation, so i can not use FSDMsg to handle it?

[Mark Salter]

Didik Rawandi wrote:

> 1 question again it was for confirmation, so i can not use FSDMsg to handle
> it?

That was my suggestion, but with seeing or knowing the message structure
it is impossible to say.

Vu seems certain this is not a viable route, Vu, did you consider and
reject FSDMsg for this interface?

Perhaps if you have a sample message you could show from your setup or
testing? A quick glance should allow us to judge, if you have a 'dump'
format (I am assuming some binary content) then the hexadecimal detail
will also help. As ever, only post data you own or are allowed to share.

Thanks.

--
Mark