Tertiary Bitmap Position

[Nap Ramirez]

Hi everyone,

I read in another thread that the default position for the Tertiary Bitmap is located right after the Secondary Bitmap.  I have confirmed by testing:

ISOMsg:

<isomsg>

    <field id="0" value="0800" />

    <field id="7" value="1111111111" />

    <field id="11" value="222222" />

    <field id="70" value="333" />

    <field id="166" value="5" />

    <field id="168" value="4444" />

</isomsg>

ASCII:

0800822000000000000084000000000000000000000005000000111111111122222233354444

I have this requirement of getting the Tertiary Bitmap back to DE065.  Using a custom GenericPackager xml config, I set the bitmap field DE001 to length 16 (for Primary and Secondary Bitmaps) and DE065 to length 8.

Now, I'm still having the Tertiary Bitmap located at DE001, right after the Secondary Bitmap.  Am I missing something? Where do I look at next?

Thanks in advance,

Nap

[Dave Bergert]

Are you sure you need the bitmap in DE 65 or just a bit that stats that the tertiary bitmap is present.

Many of the ISO8583 specs that I'm familiar with state something like:

"*Bit indicator of tertiary bitmap only*, tertiary bitmap data follows secondary in message stream"

David Bergert, CISSP, CISA, CPISM/A, CPP
Chief Technology Officer
On-Line Strategies, Inc.
"Always Available"
www.olsdallas.com
ber...@olsdallas.com
(972) 535-8833 (office)
(563) 424-0875 (cell)
www.paymentsystemsblog.com

This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage.
Please support jPOS, contact: sa...@jpos.org
 
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
 
 
 

[Nap Ramirez]

Hello David,

Yes, I'm afraid so.  DE 065 is described as "b 64", so the ISOMsg structure that I'm doing should follow:

| MTI | Primary Bitmap | Secondary Bitmap | DE 002-064 | Tertiary Bitmap DE 065 | DE 066-128 | DE 129-192 |

Cheers,

Nap

[Nap Ramirez]

Hi everyone,

I'm taking a stab at modifying ISOMsgFieldPackager.recalcBitMap().  If I'm successful, I may be able to submit it as a contribution.

I hope I'm going in the right direction.  Does anyone have other suggestions?

Thanks,

Nap

[Chhil]

Can you go through this thread and see if you get some pointers with an older version of jPOS that might be doing what you intended.

http://groups.google.com/group/jpos-users/browse_thread/thread/f076cbf4171e1bca?fwc=1

-chhil

[Gerritvw]

Hi

I have had a look at this and was wondering, is it possible to add the tertiary bitmap to a different field? (As opposed to after the secondary bitmap or field65, maybe just specify it in a .xml file and use the GenericPackager)

Gerrit

[Mark Salter]

On 21/02/2013 09:48, Gerritvw wrote:

> I have had a look at this and was wondering, is it possible to add the
> tertiary bitmap to a different field? (As opposed to after the secondary
> bitmap or field65, maybe just specify it in a .xml file and use the
> GenericPackager)

You can put it wherever you like - just amend the Packager source for
all pack and unpack processes (he said vaguely) :-) .

May I ask why you would want to do this though?

--
Mark

[Gerritvw]

Hi

I have made the changes to use a different field for the tertiary bitmap (Changes made to ISOBaserPackager), I just see field65 is still being marked as present in my bitmap and my field that contains the bitmap (127) in not marked as present in the bitmap. Any ideas of where to change this?

G

[Mark Salter]

On 27/02/2013 12:23, Gerritvw wrote:

> I have made the changes to use a different field for the tertiary bitmap
> (Changes made to ISOBaserPackager), I just see field65 is still being
> marked as present in my bitmap and my field that contains the bitmap
> (127) in not marked as present in the bitmap. Any ideas of where to
> change this?

You set any value in fields indicated by the tertiary bitmap?

How is you BitMap defined (source/xml)? Can you share the relevant details?

Perhaps a diff of your changes (or the source - perhaps on github? -
will also help see what might be wrong?

Can you also try to be a little clearer on what exactly is wrong, I
can't tell if F65 being marked is also a problem?

--
Mark

[Manu]

Hello,

I have the same requirement. The Tertiary Bitmap should be at DE65 and not directly after the the secondary bitmap.

| MTI | Primary Bitmap | Secondary Bitmap | DE 002-064 | Tertiary Bitmap DE 065 | DE 066-128 | DE 129-192 |

Is still necessary to extend / overwrite the generic packager source code?

Does anyone has an example how to do this?

Cheers

[Alejandro Revilla]

I think we had some of those and is supported by jPOS, but couldn't find a sample configuration in my records. 

It's a very rare and non standard setup. 

Can you tell me the endpoint name/software vendor so I can search if we have implemented this before?

--

@apr

--

--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: sa...@jpos.org
 

Join us in IRC at http://webchat.freenode.net/?channels=jpos

 
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
---

You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jpos-users+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/4cbf7303-525b-4579-bfdb-389e2968ba8d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Manu]

Its a LINK 2013 LIS5 Switch Interface. 

[Alejandro Revilla]

Doesn't ring a bell. Sorry.

--

@apr

To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/dfdde9b5-9a55-4ac3-9037-ca9c6e491387%40googlegroups.com.

[Mark Salter]

I think I have this interface supported via a GenericPackager and minor changes to the base components and a couple of additions.

I think I went for a 'portable' bit map approach, so that a BitMap could be placed in any field.

I will derive a pull request to the current code base to make sure it 'fits' and does not break anything - over the weekend if I can

--
Mark

[Manu]

Thanks a lot that sounds good.

[Mark Salter]

On 26/09/2014 09:30, Mark Salter wrote:
>
> I will derive a pull request to the current code base to make sure it
> 'fits' and does not break anything - over the weekend if I can

I have created :-

https://github.com/jpos/jPOS/pull/71

Which included the support of a BitMap is f65 for LIS and also a
SubFieldPackager+example generic packager xml.


--
Mark

[Manu]

Thanks you very very much! I will have a look!


Am Samstag, 27. September 2014 13:35:50 UTC+2 schrieb Mark Salter: