Custom Packager problems

[z!†™]

i am trying to create a custom packager but i have the foLLowing
questions:

how do i deaL with variabLe Length fieLds?

and in the format given to me, there is this fieLd named Transaction
Code (e.g. request from cLient is 1100, 1200, etc. and response from
Host wouLd be 1110, 1210, etc.); this is the same as the MTI right?
but this one is at fieLd 7 and fieLd 0 for MTI isn't used..

thanks for your time.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To post to this group, send email to jpos-users@...
To unsubscribe from this group, send email to jpos-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jpos-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[z!†™]

oh, i aLmost forgot..

there is aLso this 3-byte message header with no fieLd number.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To post to this group, send email to jpos-users@...
To unsubscribe from this group, send email to jpos-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jpos-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[Mark Salter]

z!†™ wrote:
> i am trying to create a custom packager but i have the foLLowing
> questions:

As a java class or in a genericpackager xml structure?
>
> how do i deaL with variabLe Length fieLds?
By using the correct field type - one that handles the length structure.

>
> and in the format given to me, there is this fieLd named Transaction
> Code (e.g. request from cLient is 1100, 1200, etc. and response from
> Host wouLd be 1110, 1210, etc.); this is the same as the MTI right?
Sounds correct.

> but this one is at fieLd 7 and fieLd 0 for MTI isn't used..
Interesting, does this message have a bitmap  and anything before it,
but after the header that you mention in your other post?

--
Mark

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To post to this group, send email to jpos-users@...
To unsubscribe from this group, send email to jpos-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jpos-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[Mark Salter]

z!†™ wrote:
> oh, i aLmost forgot..
>
> there is aLso this 3-byte message header with no fieLd number.

Headers are added or extracted at the jpos Channel level.

Do you know which Channel you will be using yet?

--
Mark

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To post to this group, send email to jpos-users@...
To unsubscribe from this group, send email to jpos-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jpos-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[z!†™]

> As a java class or in a genericpackager xml structure?

as a genericpackager xml structure

> By using the correct field type - one that handles the length structure.

using the correct fieLd type?
it's onLy stated in the message format this way:
fieLd: 1
fieLd name: transaction LabeL
fieLd Length: var
fieLd type: aLpha numeric
no description or defauLt vaLue

> Interesting, does this message have a bitmap  and anything before it,
> but after the header that you mention in your other post?

i don't know actuaLLy..
after the header that i mentioned is fieLd 1 which is decribed above.

i aLso have an issue on their teminating fieLd:
fieLd 10 on the request message and fieLd 16 on the host response..
how wiLL i deaL with this?

the message header by the way is composed of 3 bytes as i mentioned.
The 1st byte is the null character, 2nd and 3rd are the message Length
excLuding the headers.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To post to this group, send email to jpos-users@...
To unsubscribe from this group, send email to jpos-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jpos-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[z!†™]

> Headers are added or extracted at the jpos Channel level.
> Do you know which Channel you will be using yet?

they have no specific instruction on which channeL to use.
any suggestions?

thank you so much for this.
i hope i couLd thank you enough.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To post to this group, send email to jpos-users@...
To unsubscribe from this group, send email to jpos-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jpos-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[z!†™]

On Jun 17, 1:48 pm, z!†™ <ganggingti...@...> wrote:
> > Headers are added or extracted at the jpos Channel level.
> > Do you know which Channel you will be using yet?

oh, and what do i need to consider in choosing a channeL?
by the way, fieLds are PIPe ( | ) dilimited...how do deaL with that?
and the header fieLd type is H...does that mean Hexa?

i'm reaLLy sorry for such no0bie questions..i'm reaLLy new to this
whoLe jpos thing
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To post to this group, send email to jpos-users@...
To unsubscribe from this group, send email to jpos-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jpos-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[z!†™-2]

pLus:

how do i determine that i shouLd use ASCII, BCD or EBCDIC?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To post to this group, send email to jpos-users@...
To unsubscribe from this group, send email to jpos-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jpos-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[chhil]

[z!†]oh, and what do i need to consider in choosing a channeL?
It is based on what additional decorations need to be added to your message before being sent e.g. headers like TPDU (See NACChannel) or length of message being sent prepended (see postchannel)to your message.

[z!†]by the way, fieLds are PIPe ( | ) dilimited...how do deaL with that?
Look at FSDMsg.java. It allows for messages delimited  with any type of field separators.
See Andys blog for examples.

[z!†]and the header fieLd type is H...does that mean Hexa?
It might be a hard coded H followed by some additional data like tpdu or lengh..its best you ask the entity that has provided you the spec.

-chhil

On Tue, Jun 17, 2008 at 12:37 PM, z!†™ <ganggingtimay@...> wrote:

On Jun 17, 1:48 pm, z!†™ <ganggingti...@...> wrote:
> > Headers are added or extracted at the jpos Channel level.
> > Do you know which Channel you will be using yet?

oh, and what do i need to consider in choosing a channeL?

by the way, fieLds are PIPe ( | ) dilimited...how do deaL with that? 

and the header fieLd type is H...does that mean Hexa?

i'm reaLLy sorry for such no0bie questions..i'm reaLLy new to this
whoLe jpos thing

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To post to this group, send email to jpos-users@...
To unsubscribe from this group, send email to jpos-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jpos-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[Mark Salter]

z!†™ wrote:
>> As a java class or in a genericpackager xml structure?
>
> as a genericpackager xml structure
Ok, but...

>
>> By using the correct field type - one that handles the length structure.
>
> using the correct fieLd type?
> it's onLy stated in the message format this way:
> fieLd: 1
> fieLd name: transaction LabeL
> fieLd Length: var
> fieLd type: aLpha numeric
> no description or defauLt vaLue

 From one of your other posts, you have mentioned that you fields are
terminated (or separated) by pipe characters.  This is not therefore an
ISO8583 message structure and it changes things quite completely.

In ISO8583 a variable field will have a way of telling the reader how
long it is.  This may be in a binary length followed by data or a few
other ways.  Your field is variable and it's length is found by taking
the characters up to the pipe.  In another response Chhil indicates you
need to look at FSDMsg but you should also search this mailing list for
discussions on that and FSDISOMsg there are pointers to a web page.

> i aLso have an issue on their teminating fieLd:
> fieLd 10 on the request message and fieLd 16 on the host response..
> how wiLL i deaL with this?
What issue, deal with what?  It is not clear from the text given.

>
> the message header by the way is composed of 3 bytes as i mentioned.
> The 1st byte is the null character, 2nd and 3rd are the message Length
> excLuding the headers.
So you have a three byte binary message (or perhaps just two byte)
giving you the overall message length.

--
Mark

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To post to this group, send email to jpos-users@...
To unsubscribe from this group, send email to jpos-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jpos-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[Mark Salter]

z!†™ wrote:

> oh, and what do i need to consider in choosing a channeL?
The Channel deals with the message length and invokes the Packager to
split the fields out into an ISOMsg.

The Channel thus needs to handle the length of your message - which I
think you have indicated is 3 bytes binary.

> and the header fieLd type is H...does that mean Hexa?
The author of the specification you are reading can clarify that for
you, it could mean a few things, probably best not to guess.

--
Mark

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To post to this group, send email to jpos-users@...
To unsubscribe from this group, send email to jpos-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jpos-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[Mark Salter]

z!†™ wrote:
> pLus:
>
> how do i determine that i shouLd use ASCII, BCD or EBCDIC?
You need to carefully examine the specification.  Some systems support
all flavours via configuration, so check with the support team of the
system that you are trying to communicate with.

--
Mark

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To post to this group, send email to jpos-users@...
To unsubscribe from this group, send email to jpos-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jpos-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[z!†™-2]

>> i aLso have an issue on their teminating fieLd:
>> fieLd 10 on the request message and fieLd 16 on the host response..
>> how wiLL i deaL with this?

>What issue, deal with what?  It is not clear from the text given.

i meant that a fieLd is dedicated to indicate the end of message..
fieLd 10 on the request message and fieLd 16 on the host response.

i have started reading andy's post and i t0o think it's appropriate.
i'm not done reading though.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To post to this group, send email to jpos-users@...
To unsubscribe from this group, send email to jpos-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jpos-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[Mark Salter]

z!†™ wrote:
>>> i aLso have an issue on their teminating fieLd:
>>> fieLd 10 on the request message and fieLd 16 on the host response..
>>> how wiLL i deaL with this?
>
>> What issue, deal with what?  It is not clear from the text given.
>
> i meant that a fieLd is dedicated to indicate the end of message..
> fieLd 10 on the request message and fieLd 16 on the host response.
I would think that field 10 just happens to be the last field in a
request message and field 16 is just the last one currently used in a
response?

What data do fields 10 and 16 hold, does the specification describe
their content at all?

>
> i have started reading andy's post and i t0o think it's appropriate.
> i'm not done reading though.
You need to bear in mind that you are not dealing with ISO8583
structured messages, so I hope the page you are reading is relevant.


--
Mark

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To post to this group, send email to jpos-users@...
To unsubscribe from this group, send email to jpos-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jpos-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[z!†™-2]

> I would think that field 10 just happens to be the last field in a
> request message and field 16 is just the last one currently used in a
> response?

yes and yes.

> What data do fields 10 and 16 hold, does the specification describe
> their content at all?

a singLe character (~) tiLde

> You need to bear in mind that you are not dealing with ISO8583
> structured messages, so I hope the page you are reading is relevant.

i am reading the when your auth is non-iso8583 compLiant..
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To post to this group, send email to jpos-users@...
To unsubscribe from this group, send email to jpos-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jpos-users?hl=en
-~----------~----~----~----~------~----~------~--~---