no-match: no more phrases to try

[Gary Atkinson]

I know this topic has been posted before, but I am at a bit of a lost here.  Here is what we have in place for some inbound threads (for a clinical data hx load), which sends to flat file.

                     1. Using pdl with a timeout of “timeout:60000”

                     2.  Added a inbound tps proc to remove any “newlines” as we saw the outbound file terminating at a msg that had a newline inside one the OBX segements.

With both these implemented we still see the below following error in one of the inbound threads:

[pdl :PDL :ERR /0:CIS_Trans_Hist:05/12/2007 16:24:06] no-match: no more phrases to try

Besides the timeout and special character issue is there anything else that can cause the “no-match” error?

Topic

[Keith McLeod]

For TCPIP using mlp, the wrapper on the message should be

<0x0B> Message here <0x1C><0x0D>

The pdl is usually looking for a specific wrapper.  You would be able to see what you are getting with with the eo_alias turned up.  You acan look in the pdl file for what is expected.  It will be phrased something like:

/* This driver manages the transmission of messages using the HL7 defined

* MLP protocol.  Each message is bounded by a start character <0xb>

* and a stop string <0x1c><0xd>.

*

* The phrase basic-msg recognizes this message format.  Once recognized,

* the message data will be available from the ‘data’ field.

*/

define phrase basic-msg;

   ;

   field data = variable-array( not( ) );

   ; ;

end phrase;

[Michael Hertel]

Here’s a helpful post:

https://usspvlclovertch2.infor.com/viewtopic.php?t=245&highlight=pdl

[Gary Atkinson]

Thx for the link.  I actually found this pdl in our developer site (never knew it was there).  Question: the pdl we are already using for the inbound threads have a timeout of 6000.  If I add this line in do I have to recompile the pdl with hcidpc again?  Would the syntax be “hcidpc ?

[Michael Hertel]

Yes, you’ll have to recompile.

[Author]

Replies