Wildcards on TRXID ADT_A(?!17)

This topic has 3 replies, 3 voices, and was last updated 19 years, 9 months ago by Dennis Pfeifer.

Creator

Topic
March 22, 2005 at 3:49 pm #47568
Dennis Pfeifer
Participant
Thought I’d toss this out for others ..

I was not able to get the following to work for a TRXID on a wildcard..

ADT_A(?!17)

basically, the messages were not sent to this route.

I was able to use explicit .. and get it to function..

ADT_A(01|02|03|04|05|06|07|08|11|12|13|28|31)

Coments?

Dennis
Creator

Topic

Viewing 2 reply threads

Author

Replies
- March 23, 2005 at 5:30 am #56147
  Charlie Bursell
  Participant
  Kind of wordy Dennis. Try this
  
  ADT_A(0[1-8])|(1[1-3])|28|31
- March 23, 2005 at 2:02 pm #56148
  Scott Lee
  Participant
  I’ve wondered about this.
- March 23, 2005 at 2:56 pm #56149
  Dennis Pfeifer
  Participant
  IMHO, I don’t think that the performance would be significantly different, and it would be difficult to measure.
  
  e.g. with Charlie’s regexp, an A28 may parse more quickly than the expanded form, but if you don’t receive many A28’s it’s not of much value.
  
  I prefer the expanded form, simply for readability. At a glance, I can see if an A17 is handled by this route…. With Charlie’s I must interpret the entire regexp to ensure that it’s not being used. (Not that it’s difficult to interpret, but .. my goal is usually to determine the Xlate that I need to review, not an exercise in regexp interpretation.)
  
  In the end .. either is fine and will get the job done … it’s a matter of personal preference.
  
  Ultimately, I prefer the first regexp which was intended to route everything but an A17 .. but that did not work in the engine’s regexp..
  
  Dennis
Author

Replies

Viewing 2 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.