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 Set design - is there a way to ignore new fields?

Post new topic  Reply to topic Goto page Previous  1, 2
 Message Set design - is there a way to ignore new fields? « View previous topic :: View next topic » 
Author Message
mqjeff
PostPosted: Fri Aug 24, 2012 11:21 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

NealM wrote:
you know something has changed, create a warning message (email, trace, whatever) so that a developer is alerted that it's time to change AA again.


Well, yeah, but proper change management should have made sure that the developer was alerted that it was time to change AA again before the sending app's change went into UAT.
Back to top
View user's profile Send private message
kimbert
PostPosted: Fri Aug 24, 2012 12:30 pm    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

If proper change control cannot be implemented, then this is the most useful piece of advice that has been posted on this thread so far:
Quote:
There's no single method that can be chosen that can accommodate all of those potential changes.

There's no single method that can be chosen to resolve all possible forms of ONE of those potential changes.

If specific detail is given about the specific message being modified - INCLUDING detail about how parts are identified (fixed length, tagged/fixed length, delimited, etc. etc. etc.), and specific detail is given about which type of change is generally being made, then a meaningful suggestion can be made.
That last paragraph is very, very important. I am surprised that experienced people on this forum are making *any* recommendations yet - the some of the key requirements remain unknown to all but the OP.
Back to top
View user's profile Send private message
mqsiuser
PostPosted: Fri Aug 24, 2012 1:08 pm    Post subject: Reply with quote

Yatiri

Joined: 15 Apr 2008
Posts: 637
Location: Germany

Kimbert is right. Proposals can be more focused if detailed information is provided.

@OP: Pls post the (relevant) parts of your msg and current msg-set (and illustrate where the changes are to be expected).

I was just told once (by a trustworthy consultant) that "when it is not possible with TDS or CWF fixed length or delimited, then use reg exps"... which I did eversince (no problems with performance occuring from that (for me )).
Back to top
View user's profile Send private message
dyson
PostPosted: Fri Aug 24, 2012 2:13 pm    Post subject: Reply with quote

Apprentice

Joined: 04 Apr 2011
Posts: 45

Quote:
If so, you can alter the structure of the sequence containing the choice to include a variable length optional field at the end (call it FILLER or something). The unmodelled records will then be consumed by the FILLER.


That worked by the way ... Done!
Back to top
View user's profile Send private message
mqjeff
PostPosted: Fri Aug 24, 2012 3:22 pm    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

dyson wrote:
Quote:
If so, you can alter the structure of the sequence containing the choice to include a variable length optional field at the end (call it FILLER or something). The unmodelled records will then be consumed by the FILLER.


That worked by the way ... Done!


Since the comments that allowed this to be properly discussed are pushed back onto the previous page, I will elucidate a bit more here what had to be determined before any solution could be tested.

The model was specified as being tagged-delimited. The model was then specified as using the tags to resolve a choice (presumably the choice repeats). If the model was NOT using a choice, but instead using a sequence with fields in a fixed order, the solution given here would NOT work.

Because the choice resolves a single instance of an element, the choice allows each modeled field to be followed by some comparatively unmodeled 'stuff'. That 'stuff' consumes all of the records that were added since the last proper change of the model.

Again, we had to go into quite a bit of detail about the structure and methodology of the model before we could make a solution.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Message Set design - is there a way to ignore new fields?
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.