ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Message Modeling - Doubt

Post new topic  Reply to topic Goto page 1, 2  Next
 Message Modeling - Doubt « View previous topic :: View next topic » 
Author Message
Gaya3
PostPosted: Sun Aug 23, 2009 11:10 pm    Post subject: Message Modeling - Doubt Reply with quote

Jedi

Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US

Hi All

Just need some differnt ideas and thought for doing the below message modeling

Message Structure
******************
Header [1-1]
Details [1-Many]
Trailer [1-1]

the data format
HeaderDetail[1]<CR><LF>
Detail[2]<CR><LF>
Detail[3]<CR><LF>
Trailer

Do i need to go ahead with Data Pattern or fixed length format.

if so how should i tackle this issue.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die


Last edited by Gaya3 on Mon Aug 24, 2009 1:56 am; edited 1 time in total
Back to top
View user's profile Send private message
elvis_gn
PostPosted: Mon Aug 24, 2009 12:40 am    Post subject: Reply with quote

Padawan

Joined: 08 Oct 2004
Posts: 1905
Location: Dubai

Hi Gaya3,

Are there any keys to identify the Header, Detail and Trailer ?

Avoid data pattern if you can do it with fixed length....data pattern is more memory consuming.

Regards.
Back to top
View user's profile Send private message Send e-mail
Gaya3
PostPosted: Mon Aug 24, 2009 1:25 am    Post subject: Reply with quote

Jedi

Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US

elvis_gn wrote:
Hi Gaya3,

Are there any keys to identify the Header, Detail and Trailer ?

Avoid data pattern if you can do it with fixed length....data pattern is more memory consuming.

Regards.


yes, here is the problem, there are no keys to identify the header, Detail and Trailer records.
Where Detail Records is the only one repeating.

I am wondering how to get it done this with out taking the data pattern in to consideration as you said it is more memory consuming.

Sample File
***********
AHD1234
123456AAAA<CR><LF>
123457BBBB<CR><LF>
ATH1234
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die
Back to top
View user's profile Send private message
nagarjun_vv
PostPosted: Mon Aug 24, 2009 1:48 am    Post subject: Reply with quote

Apprentice

Joined: 24 Jun 2008
Posts: 33

Are these values are fixed length?
or few values are fixed length(like only header and trailer).
Back to top
View user's profile Send private message Send e-mail
Gaya3
PostPosted: Mon Aug 24, 2009 1:51 am    Post subject: Reply with quote

Jedi

Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US

nagarjun_vv wrote:
Are these values are fixed length?
or few values are fixed length(like only header and trailer).


All values are Fixed Length, [No Variable Length]

Header - Fixed Length
Details - Fixed Length
Trailer - Fixed Length

the format would be like this
Header
Details1<CR><LF>
Details2<CR><LF>
Trailer
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die
Back to top
View user's profile Send private message
kimbert
PostPosted: Mon Aug 24, 2009 1:59 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

Quote:
there are no keys to identify the header, Detail and Trailer records.
Are you sure? What about the 'ATD' and 'ATH'. They look like tags to me.
Back to top
View user's profile Send private message
nagarjun_vv
PostPosted: Mon Aug 24, 2009 2:00 am    Post subject: Reply with quote

Apprentice

Joined: 24 Jun 2008
Posts: 33

Then you can go for variable length delimited.

For header and trailer give length(as observe length will checked by default first priority will be for length so what ever delimiter you give it wont consider that) and for details it will consider delimiter as you wont mention any length.

Hope this will solve ur problem.


Last edited by nagarjun_vv on Mon Aug 24, 2009 2:14 am; edited 2 times in total
Back to top
View user's profile Send private message Send e-mail
Gaya3
PostPosted: Mon Aug 24, 2009 2:06 am    Post subject: Reply with quote

Jedi

Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US

kimbert wrote:
Quote:
there are no keys to identify the header, Detail and Trailer records.
Are you sure? What about the 'ATD' and 'ATH'. They look like tags to me.


This i have to get it confirmed once again, from the Source team, the last conversation regarding this was, it could be anything over here..thats the reason i got confused.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die
Back to top
View user's profile Send private message
nagarjun_vv
PostPosted: Mon Aug 24, 2009 2:16 am    Post subject: Reply with quote

Apprentice

Joined: 24 Jun 2008
Posts: 33

Then you can go for variable length delimited.

For header and trailer give length(as observe length will checked by default first priority will be for length so what ever delimiter you give it wont consider that) and for details it will consider delimiter as you wont mention any length.

Hope this will solve ur problem.
Back to top
View user's profile Send private message Send e-mail
Gaya3
PostPosted: Mon Aug 24, 2009 2:21 am    Post subject: Reply with quote

Jedi

Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US

nagarjun_vv wrote:
Then you can go for variable length delimited.

For header and trailer give length(as observe length will checked by default first priority will be for length so what ever delimiter you give it wont consider that) and for details it will consider delimiter as you wont mention any length.

Hope this will solve ur problem.


i do agree that i can do variable length delimited for Header and Trailer but what delimiter should i give for the Details section.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die
Back to top
View user's profile Send private message
elvis_gn
PostPosted: Mon Aug 24, 2009 2:23 am    Post subject: Reply with quote

Padawan

Joined: 08 Oct 2004
Posts: 1905
Location: Dubai

Hi nagarjun_vv,
nagarjun_vv wrote:
Then you can go for variable length delimited.

For header and trailer give length(as observe length will checked by default first priority will be for length so what ever delimiter you give it wont consider that) and for details it will consider delimiter as you wont mention any length.

Hope this will solve ur problem.
How will this help her distinguish when the details section got over and the next record is not another detail but the trailer ?

I think you need to find out about the ATD and ATH as kimbert mentioned.

Regards.
Back to top
View user's profile Send private message Send e-mail
Gaya3
PostPosted: Mon Aug 24, 2009 2:41 am    Post subject: Reply with quote

Jedi

Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US

Gaya3 wrote:
kimbert wrote:
Quote:
there are no keys to identify the header, Detail and Trailer records.
Are you sure? What about the 'ATD' and 'ATH'. They look like tags to me.


This i have to get it confirmed once again, from the Source team, the last conversation regarding this was, it could be anything over here..thats the reason i got confused.


I confirmed this, the header would be AHD - by default and trailer - ATH - by default.

this values should not be excluded at all
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die
Back to top
View user's profile Send private message
kimbert
PostPosted: Mon Aug 24, 2009 3:00 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

So...this is what I think you are saying:
- the first record always starts with 'ATD'
- the final record always starts with 'ATH'
- other records are not identified in any way

Please confirm whether that is correct.
Back to top
View user's profile Send private message
nagarjun_vv
PostPosted: Mon Aug 24, 2009 3:01 am    Post subject: Reply with quote

Apprentice

Joined: 24 Jun 2008
Posts: 33

AHD1234
123456AAAA<CR><LF>
123457BBBB<CR><LF>
ATH1234

If you can consider the above message as like this

AHD1234
123456AAAA<CR><LF>
123457BBBB<CR><LF>
ATH

The above wil be a complex type where AHD is Group indicator and ATH is group terminator. first element with fixed length of 4 and other element with repeating delimited.

1234
this is another field in the message.

Confirmwhether this will solve the issue.

Regards,
VV
Back to top
View user's profile Send private message Send e-mail
Gaya3
PostPosted: Mon Aug 24, 2009 3:09 am    Post subject: Reply with quote

Jedi

Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US

kimbert wrote:
So...this is what I think you are saying:
- the first record always starts with 'ATD'
- the final record always starts with 'ATH'
- other records are not identified in any way

Please confirm whether that is correct.


Yes exactly Kimbert.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page 1, 2  Next Page 1 of 2

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Message Modeling - Doubt
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.