FIELD 55 data format in jPOS server

[Alavala Sanjeeva Reddy]

Hai all,

 

Can you please send me the data for field 55 in jpos server.

 

is there any utility available for filed 55 data for BCD format.

 

--
Thanks & regards,
Sanjeeva Reddy Alavala

[Mark Salter]

Alavala Sanjeeva Reddy wrote:
> Hai all,
>
> Can you please send me the data for field 55 in jpos server.
>
> is there any utility available for filed 55 data for BCD format.
>
>

Is there a structure defined for your field 55?
Knowing this may enable you to provide the detail for us to help you?

This is another in an increasing number of threads you start, but do not
continue with; please take a look at your other messages - and my
responses to them - to save me repeating myself?

--
Mark

[chhil]

My ISO8583 network spec tells me that field 55 is 100 oranges wide 

and each orange needs to be 4 cms in diameter.

In other words it means...

Every 8583 implementation has its own set of fields that contain specific data that it would require in its own format.

So yours may require apples in field 55 nd we don't want to compare apples with oranges...do we ;)

What does "your" spec tell about "your" field 55?

-chhil

[Andy Orrock]

Here are some related readings on the tasks:

 

http://www.andyorrock.com/2006/09/implementing_th.html

 

http://www.andyorrock.com/2007/01/onboarding_a_ne.html 

 

http://www.andyorrock.com/2007/08/on-boarding-a-2.html

[shaner]

Alavala,

Typically field 55 is used for Chip Card Data which Amex call
"INTEGRATED CIRCUIT CARD SYSTEM RELATED DATA" and Paymentech "Chip
Card Data (EMV Specification)". Which processor are you referring to
as both have very different formats?

Cheers, Shane Rowatt


On Mar 11, 1:38 am, Alavala Sanjeeva Reddy <asanjeevare...@gmail.com>
wrote:

[Alavala Sanjeeva Reddy]

Hai,

 

i am having string like this

String de55="820258008407A0000000041010950540000080009A030903109C01005F2A0203925F3401019F02060009090909009F090200029F1008010103A0280600009F1A0203569F1E0830333531313634359F260831221BC08E163B789F2701809F3303E0E0C89F34035E03009F3501229F360205509F3704291315229F530152";

ISOMsg iso=new ISOMsg();

iso.set(55,de55);

i am using like this , i am getting the response from the host as Format error("error code:96").

 

these string i want to set ISOMsg for field 55 and contacting host for response..

 

Please help me on this regard.......

 

 

Thanks & regards,

Sanjeeva Reddy

[Mark Salter]

Alavala Sanjeeva Reddy wrote:
> Hai,
>
> i am having string like this
> String
> de55="820258008407A0000000041010950540000080009A030903109C01005F2A0203925F3401019F02060009090909009F090200029F1008010103A0280600009F1A0203569F1E0830333531313634359F260831221BC08E163B789F2701809F3303E0E0C89F34035E03009F3501229F360205509F3704291315229F530152";
> ISOMsg iso=new ISOMsg();
> iso.set(55,de55);
> i am using like this , i am getting the response from the host as Format
> error("error code:96").

Sanjeeva, you are persistently missing the point - you need to provide
or information and tell us *exactly* what is needed by this host for us
to help you.

The data you want to send to this host is TLV data:-

82 (Application Interchange Profile).
0000 58 00 X.

84
0000 A0 00 00 00 04 10 10 .......

95 (Terminal Verification Results).
0000 40 00 00 80 00 @....

9A (Transaction Data).
0000 09 03 10 ...

9C (Transaction Type).
0000 00 .

5F2A (Transaction Currency Code).
0000 03 92 ..

5F34 (PAN Sequence Number).
0000 01 .

9F02 (Amount, Authorized).
0000 00 09 09 09 09 00 ......

9F09
0000 00 02 ..

9F10 (Issuer Application Data).
0000 01 01 03 A0 28 06 00 00 ....(...

9F1A (Terminal Country Code).
0000 03 56 .V

9F1E (IFD Serial Number).
0000 30 33 35 31 31 36 34 35 03511645

9F26 (Application Cryptogram).
0000 31 22 1B C0 8E 16 3B 78 1"....;x

9F27
0000 80 .

9F33 (Terminal Capability Profile).
0000 E0 E0 C8 ...

9F34
0000 5E 03 00 ^..

9F35 (EMV Terminal Type).
0000 22 "

9F36 (Application Transaction Counter).
0000 05 50 .P

9F37 (Unpredictable Number).
0000 29 13 15 22 ).."

9F53
0000 52 R

But the *important* question is:-

How does the host you want to send it to expect it to look like? Does
it even expect it in field 55, what is the format of this field (for the
host) - binary, ascii character hex, ebcdic character hex. For all we
know it might be expecting the chip data in fields under the third bitmap!

If this data does travel in field 55 then the packager definition of
field 55 must match that which the host is expecting; *and* you need to
know what the host needs in the rest of the message.

Are you really just sending field 55 - I would suspect this host is
giving you an error (96 - system malfunction?) because you have not sent
enough data? As an example, how will the host know which card is in
use, or is the IFD serial enough?

--
Mark

[chhil]

We see a bunch of numbers/characters that you set in the field.

We do not know what your packager definition or field definition is so we don't know how your string is going to get packed. 

Have you asked the "other" entity responding to your message as to why they are responding with a 96.

-chhil

On Thu, Mar 12, 2009 at 10:42 AM, Alavala Sanjeeva Reddy <asanjee...@gmail.com> wrote:

820258008407A0000000041010950540000080009A030903109C01005F2A0203925F3401019F02060009090909009F090200029F1008010103A0280600009F1A0203569F1E0830333531313634359F260831221BC08E163B789F2701809F3303E0E0C89F34035E03009F3501229F360205509F3704291315229F530152"

[Alavala Sanjeeva Reddy]

Hai All,

 

continue last message,

 

my string is String d55="8202444";

 

host expecting format for filed 55 is BCD Format..

 

Ex..

 

original string is     

String de55="820258008407A0000000041010950540000080009A030903129C01005

F2A0203925F3401019F02060009090909009F090200029F1008010103A0280600009F1A0203569F1E08303335313

13634359F260831221BC08E163B789F2701809F3303E0E0C89F34035E03009F3501229F360205509F3704291315229F530152";

 

Host Expecting is " 82 02 25 80 ...."

 

my problem is : now host is taking istead of 82 it is taking 3832.. i want only to pass as 82 only...

 

 

Please Help me on this regard...

 

Thanks & regards,

Sanjeeva Reddy

[Mark Salter]

Alavala Sanjeeva Reddy wrote:
> Hai All,
>
> continue last message,
>
> my string is String d55="8202444";

This is not valid TLV, you are missing a nibble from the value
component! c'82024440' would be valid.

>
> host expecting format for filed 55 is BCD Format..
>
> Ex..
>
> original string is
> String de55="820258008407A0000000041010950540000080009A030903129C01005
> F2A0203925F3401019F02060009090909009F090200029F1008010103A0280600009F1A0203569F1E08303335313
> 13634359F260831221BC08E163B789F2701809F3303E0E0C89F34035E03009F3501229F360205509F3704291315229F530152";
>
> Host Expecting is " 82 02 25 80 ...."

So you have a *binary* field which is not truly bcd (binary coded
decimal). BCD only contains the 'digits' 0123456789, as soon as you
have values >9 (ABCDEF) you have a binary field.

You want to send x'82022580' and not c'82022580' == x'3832303232353830'.

>
> my problem is : now host is taking istead of 82 it is taking 3832.. i want
> only to pass as 82 only...

It is seeing ascii values because you are sending ascii characters,
which means your field 55 definition is ascii and not binary as you need.

You need to make sure the Packager you are using has a binary jpos field
for 55.

What packager are you using? Can you show us how it defines field 55
please? How about posting the entire packager (source or xml)?

You are going to need to worry about the format of the length of the
data in field 55. How is the host expecting the length (of field 55) to
be presented to it? There are options here too.

--
Mark

[Alavala Sanjeeva Reddy]

Hai All,

 

i am using  jpos 1.4.1 server and using utility is ISOMsg to frame my iso messages...

Example ..

Object obj = ((ISOBasePackager) packager).getFieldPackager(55);

 

if i am using this then i am getting the object as :org.jpos.iso.IFB_LLLCHAR@4d76b4

 

 

.. what i understand from your mail 

'3832303232353830'.

instead of 8 i need to pass as 0x38 .. is this correct..

 

Thanks and regards,

Sanjeeva Reddy

[Mark Salter]

Alavala Sanjeeva Reddy wrote:

> i am using jpos 1.4.1 server and using utility is ISOMsg to frame my iso
> messages...
> Example ..
> Object obj = ((ISOBasePackager) packager).getFieldPackager(55);
>
> if i am using this then i am getting the object as
> :org.jpos.iso.IFB_LLLCHAR@4d76b4

Why not show us the packager code or xml itself?

>
>
> .. what i understand from your mail
> '3832303232353830'.
>
> instead of 8 i need to pass as 0x38 .. is this correct..

No, in setting the value of a field you can pass in a String; But the
field that receives this data and will pack it for transmission needs to be

org.jpos.iso.IFB_LLLBINARY

To send binary rather than character data.

You fail to answer my questions, so we will have to assume for now that
you have the correct length structure.

--
Mark

[Alavala Sanjeeva Reddy]

Hai  all,

 

i am having the string data, how to convert this to Binary format.

 

Can you please help me on this...

 

MY Code:

ISOPackager packager = new ISO93BPackager();
    packager.setLogger(log,"packager-logger");
    org.jpos.iso.header.NACHeader  head = new org.jpos.iso.header.NACHeader("6002220000");
    iso=new ISOMsg();
    iso.setPackager(packager);
    iso.setHeader(head);
    iso.setHeader(ISOUtil.hex2byte("6002220000"));
    byte [] hea = iso.getHeader();
    logger.fine("header " + hea);
    logger.fine("hexString " + ISOUtil.hexString(hea));
    iso.setMTI(WinPosConstants.SALE_REQUEST);//"0200";
  
Here i am passing my string..

iso.set(55,de55);

 

now my ISO is having  all the fields required..

Thanks & regards,

Sanjeeva Reddy

[Mark Salter]

Alavala Sanjeeva Reddy wrote:
> Hai all,
>
> i am having the string data, how to convert this to Binary format.

The ISOMsg.set(int,String) will convert it for you as field 55 is an
instance of a ISOBinaryFieldPackager.

>
> Can you please help me on this...
>
> MY Code:
> ISOPackager packager = new ISO93BPackager();
> packager.setLogger(log,"packager-logger");
> org.jpos.iso.header.NACHeader head = new
> org.jpos.iso.header.NACHeader("6002220000");
> iso=new ISOMsg();
> iso.setPackager(packager);
> iso.setHeader(head);
> iso.setHeader(ISOUtil.hex2byte("6002220000"));
> byte [] hea = iso.getHeader();
> logger.fine("header " + hea);
> logger.fine("hexString " + ISOUtil.hexString(hea));
> iso.setMTI(WinPosConstants.SALE_REQUEST);//"0200";
>
> Here i am passing my string..
> iso.set(55,de55);

You don't show how the field de55 is defined, but if it is a String then
with the ISO93BPackager (field 55 == IFB_LLLBINARY) it should just
'work'. Please note that we still don't know (you have not told us) how
the host is expecting to see this EMV data, so I am working on the
limited detail I have picked out of your postings.

If you did want to convert a String of hexadecimal character to a byte[]
of binary data to pass into the ISOMsg.set(int,byte[]), you can use
ISOUtil.hex2byte(String), just like you did in setHeader above :-

iso.setHeader(ISOUtil.hex2byte("6002220000"));

So, now to my questions, please attempt to answer or say that you cannot :-

- Have you changed the packager you are using to ISO93BPackager; what
was it before?

- Why don't you need to pass in a card number, perhaps in field 2?

--
Mark

[Alavala Sanjeeva Reddy]

Hai All,

 

previously i have ISOPackager packager = new ISO87BPackager(); and iso=new ISOMsg();
    iso.setPackager(packager);

 

for this package we have field 55 that is having IFB_LLLCHAR so host is taking each each character 2 bytes.

 

now i made the change to ISOPackager packager = new ISO93BPackager();
     iso=new ISOMsg();
     iso.setPackager(packager);

in this package is having field 55 IFB_LLLBINARY 

 

 finally the host is expecting BCD Format.

 

if i pass the value like iso.set(55,ISOUtil.hex2byte(String),  then i am getting the

 

Exception:

java.lang.ClassCastException: java.lang.String cannot be cast to [B
        at org.jpos.iso.IFB_LLLBINARY.pack(IFB_LLLBINARY.java:76)
        at org.jpos.iso.ISOBasePackager.pack(ISOBasePackager.java:134)
        at org.jpos.iso.ISOMsg.pack(ISOMsg.java:292)
        at com.enstage.winposplus.WinPosUtility.isoMsgToHexString(WinPosUtility.java:74)
        at com.enstage.winposplus.HostInterface.doSale(HostInterface.java:538)
        at com.enstage.winposplus.CommandHandler.doSale(CommandHandler.java:2105)
        at com.enstage.winposplus.CommandHandler.handleCommand(CommandHandler.java:376)
        at org.quickserver.net.server.impl.BlockingClientHandler.processRead(BlockingClientHandler.java:323)
        at org.quickserver.net.server.impl.BlockingClientHandler.run(BlockingClientHandler.java:190)
        at org.quickserver.util.pool.thread.ClientThread.executeClient(ClientThread.java:104)
        at org.quickserver.util.pool.thread.ClientThread.run(ClientThread.java:133)
06:19:42,442 [WARNING] com.enstage.winposplus.HostInterface.doSale - ISOException :java.lang.ClassCastException: java.la
ng.String cannot be cast to [B
java.lang.NullPointerException
        at com.enstage.winposplus.DbUtil.updateResponse(DbUtil.java:2031)
        at com.enstage.winposplus.CommandHandler.doSale(CommandHandler.java:2139)
        at com.enstage.winposplus.CommandHandler.handleCommand(CommandHandler.java:376)
        at org.quickserver.net.server.impl.BlockingClientHandler.processRead(BlockingClientHandler.java:323)
        at org.quickserver.net.server.impl.BlockingClientHandler.run(BlockingClientHandler.java:190)
        at org.quickserver.util.pool.thread.ClientThread.executeClient(ClientThread.java:104)
        at org.quickserver.util.pool.thread.ClientThread.run(ClientThread.java:133)

My JPOs Version is jpos 1.4.1

 

Please help me on this regard...

 

 

Thanks & regards,

Sanjeeev Reddy

[Mark Salter]

Alavala Sanjeeva Reddy wrote:

> previously i have ISOPackager packager = new ISO87BPackager(); and iso=new
> ISOMsg();
> iso.setPackager(packager);
>

Ok at least that explains the difference and improvement.

>
> now i made the change to ISOPackager packager = new ISO93BPackager();
> iso=new ISOMsg();
> iso.setPackager(packager);
>
> in this package is having field 55 IFB_LLLBINARY
>
> finally the host is expecting BCD Format.

I have already mentioned that this statement is not terribly accurate,
but never mind.

>
> if i pass the value like iso.set(55,ISOUtil.hex2byte(String), then i am
> getting the
>

> *Exception:*
> *java.lang.ClassCastException: java.lang.String cannot be cast to [B

> at org.jpos.iso.IFB_LLLBINARY.pack(IFB_LLLBINARY.java:76)
> at org.jpos.iso.ISOBasePackager.pack(ISOBasePackager.java:134)
> at org.jpos.iso.ISOMsg.pack(ISOMsg.java:292)
> at

Can you carefully recheck this please?

If you ran the code :-

iso.set(55,ISOUtil.hex2byte("82024440"));

Then are passing in a byte[] and I don't see how the class cast
exception could occur?

If however you ran the code:-

iso.set(55,"82024440");

then this exception might occur, depending on if the hex2byte helper
code was present in 1.4.1 (see below).

Please ensure you are compiling your code before each run attempt.

> *My JPOs Version is jpos 1.4.1*

Any reason why you cannot use the latest version at all?

In your copy of ISOMsg, does it's ISOMsg.set(int, String) method , look
anything like:-

/**
* Creates an ISOField associated with fldno within this ISOMsg
* @param fldno field number
* @param value field value
*/
public void set(int fldno, String value) throws ISOException {
if (value != null) {
if (!(packager instanceof ISOBasePackager)) {
// No packager is available, we can't tell what the field
// might be, so treat as a String!
set(new ISOField(fldno, value));
}
else {
// This ISOMsg has a packager, so use it
Object obj = ((ISOBasePackager)
packager).getFieldPackager(fldno);
if (obj instanceof ISOBinaryFieldPackager) {
set(new ISOBinaryField(fldno, ISOUtil.hex2byte(value)));
} else {
set(new ISOField(fldno, value));
}
}
}
else
unset(fldno);
}

I don't have 1.4.1 to hand, so can you check for me please?

--
Mark

[Alavala Sanjeeva Reddy]

Hai All,

 

After adding this ISOMsg.java,

 

I got this Exception...

 

Packing Dude at Fri Mar 13 15:51:32 GMT+05:30 2009
Finsihed Packing Fri Mar 13 15:51:32 GMT+05:30 2009
<log realm="nac_relm" at="Fri Mar 13 15:51:32 GMT+05:30 2009.973">
  <send>
    <isomsg direction="outgoing">
      <field id="0" value="0200"/>
      <field id="2" value="4761739001010010"/>
      <field id="3" value="000000"/>
      <field id="4" value="000000020000"/>
      <field id="11" value="000001"/>
      <field id="12" value="155033"/>
      <field id="13" value="0313"/>
      <field id="14" value="1012"/>
      <field id="22" value="051"/>
      <field id="24" value="230"/>
      <field id="25" value="00"/>
      <field id="35" value="4761739001010010=10122011143878089?"/>
      <field id="41" value="22410390"/>
      <field id="42" value="000022411010041"/>
      <field id="55" value="820258008407A0000000041010950540000080009A030903139C01005F2A0203925F3401019F0206000909090900
9F090200029F1008010103A0280600009F1A0203569F1E0830333531313634359F260831221BC08E163B789F2701809F3303E0E0C89F34035E03009F
3501229F360205509F3704291315229F530152" type="binary"/>
      <field id="62" value="000001"/>
    </isomsg>
    <exception name="[B cannot be cast to java.lang.String">
    java.lang.ClassCastException: [B cannot be cast to java.lang.String
        at org.jpos.iso.IFB_LLLCHAR.pack(IFB_LLLCHAR.java:77)
        at org.jpos.iso.ISOBasePackager.pack(ISOBasePackager.java:134)
        at org.jpos.iso.ISOMsg.pack(ISOMsg.java:331)
        at org.jpos.iso.BaseChannel.send(BaseChannel.java:438)
        at org.jpos.iso.ISOMUX.doTransmit(ISOMUX.java:362)
        at org.jpos.iso.ISOMUX.run(ISOMUX.java:379)
        at java.lang.Thread.run(Unknown Source)
    </exception>
  </send>
</log>
<log realm="nac_relm" at="Fri Mar 13 15:51:33 GMT+05:30 2009.4">
  <mux>
    <iso-exception>
      unexpected exception
      <nested-exception>
      java.lang.ClassCastException: [B cannot be cast to java.lang.String
        at org.jpos.iso.IFB_LLLCHAR.pack(IFB_LLLCHAR.java:77)
        at org.jpos.iso.ISOBasePackager.pack(ISOBasePackager.java:134)
        at org.jpos.iso.ISOMsg.pack(ISOMsg.java:331)
        at org.jpos.iso.BaseChannel.send(BaseChannel.java:438)
        at org.jpos.iso.ISOMUX.doTransmit(ISOMUX.java:362)
        at org.jpos.iso.ISOMUX.run(ISOMUX.java:379)
        at java.lang.Thread.run(Unknown Source)
      </nested-exception>
      org.jpos.iso.ISOException: unexpected exception (java.lang.ClassCastException: [B cannot be cast to java.lang.Stri
ng)
        at org.jpos.iso.BaseChannel.send(BaseChannel.java:460)
        at org.jpos.iso.ISOMUX.doTransmit(ISOMUX.java:362)
        at org.jpos.iso.ISOMUX.run(ISOMUX.java:379)
        at java.lang.Thread.run(Unknown Source)
    </iso-exception>
  </mux>
</log>

 

 

Please help me on this regard,

 

Thanks & regards,

Sanjeeva Reddy

[Mark Salter]

Alavala Sanjeeva Reddy wrote:

> After adding this ISOMsg.java,
Adding what please? I asked you to check what your
ISOMsg.set(int,String) looked like, not to change it?

>
> I got this Exception...

So what does the setting of field 55 currently look like for the run
below? Surprisingly this would be nice to know. I know you can see it,
but we can't?

Hold on one second....
.. you are mixing things up left right and centre. This is not the
Exception you said you had just now at all.

>
> Packing Dude at Fri Mar 13 15:51:32 GMT+05:30 2009
> Finsihed Packing Fri Mar 13 15:51:32 GMT+05:30 2009
> <log realm="nac_relm" at="Fri Mar 13 15:51:32 GMT+05:30 2009.973">

[snip log]

> <exception name="[B cannot be cast to java.lang.String">
> java.lang.ClassCastException: [B cannot be cast to java.lang.String
> at org.jpos.iso.IFB_LLLCHAR.pack(IFB_LLLCHAR.java:77)

Why are you back using *IFB_LLLCHAR* again? *This* Exception is because
you are passing a byte[] into a field that is expecting a *String*;
meaning you are trying to use IFB_LLLBINARY but are not!

How are you specifying the packager - on the ISOMsg and on the Channel?

Show your code here, or send it all to me off-list if you would prefer
everyone not to see it.

This random confusion has to stop! If you want help here (from me
anyway), you *must* present all the facts of what you are doing, not a
tiny part and not your interpretation.

Here I go again...

Please read, absorb and even ask questions about :-

www.catb.org/~esr/faqs/smart-questions.html

In my opinion, you really need to do this *before* continuing any further?

Other group members, please pull me up if I am being too harsh - I hope
you would!

--
Mark

[chhil]

Mark hats off to you...you have been very very patient... this thread has become cyclic in nature and your request for information has fallen on deaf ears....

-chhil

[Andres Alcarraz]

Mark I think you have been too much soft, people must learn that if they want help they have to put some effort of they part, all I see from Alavala are attempts that you resolve his problems for him.
I would have stopped to respond after the first response to your poniter to the smart questions, I honestly think he never tried to read it because is too long to loose his time on it, but he does not think o the time you spent on him.

thanks giving  is not just saying thanks, one have to demonstrate it with fact like making an effort to simplify things to the one you are thanking.

I apologize for my english.

Best regards

chhil escribió:

[Mark Salter]

Andres Alcarraz wrote:
> Mark I think you have been too much soft, people must learn that if
> they want help they have to put some effort of they part, all I see
> from Alavala are attempts that you resolve his problems for him. I
> would have stopped to respond after the first response to your
> poniter to the smart questions, I honestly think he never tried to
> read it because is too long to loose his time on it,

I do agree with you. It is sometimes hard to tell when someone is just
not bothering to help themselves rather than struggling with a foreign
language.

Sometimes too I think we have people that are not familiar with any of
the basic problem investigation techniques; assuming that their problem
is someone else's fault. Trust in others code also is a factor; I know
that if something I do with our code does not work first time it is
usually an error I have made.

> but he does not think of the time you spent on him.
Well, I agree this is very likely.

>
> thanks giving is not just saying thanks, one have to demonstrate it
> with fact like making an effort to simplify things to the one you are
> thanking.

I agree again.

>
> I apologize for my english.

No need for apologies, your English puts my Spanish to shame 8).

--
Mark

[Alavala Sanjeeva Reddy]

Dear Mark,

 

i am really thankful to you to help me on this issue, i have resolved my issue.

you are always there for me to resolve..

 

Thanks & regards,

Sanjeeva Reddy

 

[chhil]

Glad things worked out for you.

It would be great to know how it was resolved.

-chhil

[Alavala Sanjeeva Reddy]

Hai,

 

i used different packager for field 55 data, i.e org.jpos.iso.packager.ISO93BPackager
 there it is passing binary data to the host.

 

/*055*/ new IFB_LLLBINARY(255,"IC card system related data"),

 

so my problem resolved....

 

once again , thank you very much for your quick response always....

 

 

Thanks & regards,

Sanjeeva Reddy

[chhil]

If I look through the email chain....there was a posting by you earlier...

[snippet from earlier email]

"now i made the change to ISOPackager packager = new ISO93BPackager();

     iso=new ISOMsg();
     iso.setPackager(packager);

in this package is having field 55 IFB_LLLBINARY 

 

 finally the host is expecting BCD Format.

 

if i pass the value like iso.set(55,ISOUtil.hex2byte(String),  then i am getting the.....

java.lang.ClassCastException: java.lang.String cannot be cast to [B

        at org.jpos.iso.IFB_LLLBINARY.pack(IFB_LLLBINARY.java:76)....

"

So why were you getting an exception then, could you explain? 

-chhil

[Andres Alcarraz]

Glad to know too, sorry if I sounded too rude in my previous post, I believe that my critic was not very constructive, may be I should have provided directions to follow, and some one had to be the bad guy since Matías didn't play its role so far :).
Well the point I want to state here is, I understand that this ISO8583 world may be somewhat overwhelming to the newcomers, and that some enterprises expect that developers understand and can start being productive since the very first touch or with very little time and training, but I don't thing that others have to spent their time (and hence money) to help developers that work for other enterprises winning a lot from their work without any retribution, some times I have the feeling that people like mark spent more time investigating that the people asking.
I had the bless of being tutored by Alejandro itself in the use of jpos, but the company I worked for in that moment payed for Alejandro's hours.
So if you want help you first have to help yourself, how? Well just investigating, lots of the questions posted in this forum are not even regarding jpos, if you have a ClassCastException you have jpos code to read and see what YOU'RE code is doing bad. And you should try to investigate that before asking other that have no idea of what YOU'RE code do.
I'm not trying to grumble anybody just, maybe educating a little, thing that I should not be doing if people read the smart questions link that Mark constantly provides.
One of the things that article states is that when you find the solution you should share it with the community so you can some how re tribute the community for the help they gave to you. Else you are being somewhat selfish and not truly thanking.

I guess this time the critic is a bit  more constructive.

good luck


Andrés






chhil escribió:

[Alavala Sanjeeva Reddy]

Hai,

 

Previously i am using  ISO87BPackager for my iso messages and NAC Channel is having ISO93Packager, so , there is Mismatch is came.

 

 

Now i am using same packages in both NAC as well as ISOMsg, my problem resolved.

 

 

Thanks & regards,

Sanjeeva Reddy

 

[Andres Alcarraz]

Hai,

Hello

 

Previously i am using  ISO87BPackager for my iso messages and NAC Channel is having ISO93Packager, so , there is Mismatch is came.

 

 

Now i am using same packages in both NAC as well as ISOMsg, my problem resolved.

 

What do you mean by using  ISO87BPackager for your iso messages?
Do you need to pack/unpack messages other where but in the channel?

Andrés