Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Qualifiers in an output component

4 posts in General Discussion Last posting was on 2009-03-03 14:49:09.0Z
DOug Myers Posted on 2009-02-27 13:49:58.0Z
Sender: 1d55.49a4185f.1804289383@sybase.com
From: Doug Myers
Newsgroups: sybase.public.impact
Subject: Qualifiers in an output component
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <49a7ef86.442.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 27 Feb 2009 05:49:58 -0800
X-Trace: forums-1-dub 1235742598 10.22.241.41 (27 Feb 2009 05:49:58 -0800)
X-Original-Trace: 27 Feb 2009 05:49:58 -0800, 10.22.241.41
Lines: 12
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.impact:2161
Article PK: 230234

I am trying to use two qualifiers in the MSHMessageEventCode
output component to determine if the message event code
equals an A04 AND the patient class equals E (emergency).
If both are true I want to replace the A04 with an A05 in
the MSHMessageEventCode. I then set up another
MSHMessageEventCode output component with the same
qualifiers but as not equal to output the code as is. This
works fine if I only use the patient class qualifier or if I
only use the A04 qualifier but if I use both in the
component, nothing gets output. Is there a reason why the
component will not work with two or more qualifiers? They
used too. I am using V5.5.3 on an AIX server.


chris Posted on 2009-03-02 16:37:47.0Z
Sender: 203.49ac07f1.1804289383@sybase.com
From: Chris
Newsgroups: sybase.public.impact
Subject: Re: Qualifiers in an output component
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <49ac0b5b.253.1681692777@sybase.com>
References: <49a7ef86.442.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 2 Mar 2009 08:37:47 -0800
X-Trace: forums-1-dub 1236011867 10.22.241.41 (2 Mar 2009 08:37:47 -0800)
X-Original-Trace: 2 Mar 2009 08:37:47 -0800, 10.22.241.41
Lines: 51
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.impact:2162
Article PK: 230238

I'm not sure why the qualifier is failing ..
(they can be a bit touchy)
and you're negation may be off
sometimes the "and" needs to be an "or" when negating

Anyway,
I would recommend just using a filter..
it's a personal preference - but, I like it because usually
when you use qualifiers like this you need both a pro & a
con choice to make sure you have output ..
but, as you add more conditions
this changes from 2 to 4 to 8 lines each with pro/con
qualifiers

and this gets harder and harder to debug

--
if you use a filter, you would only need the output listed
once..
attach a datalink to the two elements you need to check

use ODL code in the custom filter..

if ( Event_dl = "A04" ) && ( Class_dl = "E" )
{
pb->set("A05");
}

return 1;

Note:
I've been using VB a lot lately so my syntax may be off a
bit

if/when the criteria changes - the filter just gets more
code

> I am trying to use two qualifiers in the
> MSHMessageEventCode output component to determine if the
> message event code equals an A04 AND the patient class
> equals E (emergency). If both are true I want to replace
> the A04 with an A05 in the MSHMessageEventCode. I then
> set up another MSHMessageEventCode output component with
> the same qualifiers but as not equal to output the code as
> is. This works fine if I only use the patient class
> qualifier or if I only use the A04 qualifier but if I use
> both in the component, nothing gets output. Is there a
> reason why the component will not work with two or more
> qualifiers? They used too. I am using V5.5.3 on an AIX
> server.


chris Posted on 2009-03-02 16:40:01.0Z
Sender: 203.49ac07f1.1804289383@sybase.com
From: Chris
Newsgroups: sybase.public.impact
Subject: Re: Qualifiers in an output component
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <49ac0be1.269.1681692777@sybase.com>
References: <49a7ef86.442.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 2 Mar 2009 08:40:01 -0800
X-Trace: forums-1-dub 1236012001 10.22.241.41 (2 Mar 2009 08:40:01 -0800)
X-Original-Trace: 2 Mar 2009 08:40:01 -0800, 10.22.241.41
Lines: 22
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.impact:2163
Article PK: 230239

Doug,
If you want to talk it through send me an email

celm
(at)
first choice professionals
(.com)

> I am trying to use two qualifiers in the
> MSHMessageEventCode output component to determine if the
> message event code equals an A04 AND the patient class
> equals E (emergency). If both are true I want to replace
> the A04 with an A05 in the MSHMessageEventCode. I then
> set up another MSHMessageEventCode output component with
> the same qualifiers but as not equal to output the code as
> is. This works fine if I only use the patient class
> qualifier or if I only use the A04 qualifier but if I use
> both in the component, nothing gets output. Is there a
> reason why the component will not work with two or more
> qualifiers? They used too. I am using V5.5.3 on an AIX
> server.


steve Posted on 2009-03-03 14:49:09.0Z
From: steve <sbenn@wakemed.org>
Newsgroups: sybase.public.impact
Subject: Re: Qualifiers in an output component
Date: Tue, 3 Mar 2009 06:49:09 -0800 (PST)
Organization: http://groups.google.com
Lines: 37
Message-ID: <197b9eb9-7ec3-4451-9a0a-d43622e371f2@e18g2000yqo.googlegroups.com>
References: <49a7ef86.442.1681692777@sybase.com>
NNTP-Posting-Host: 216.77.41.249
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1236091749 16920 127.0.0.1 (3 Mar 2009 14:49:09 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Tue, 3 Mar 2009 14:49:09 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: e18g2000yqo.googlegroups.com; posting-host=216.77.41.249; posting-account=GvyNvgkAAADKlzgEvPu6gxJG9z2jHW9V
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; InfoPath.2; MS-RTC LM 8),gzip(gfe),gzip(gfe)
Path: forums-1-dub!forums-master!newssvr.sybase.com!news-sj-1.sprintlink.net!news-peer1.sprintlink.net!nntp1.phx1.gblx.net!nntp.gblx.net!nntp.gblx.net!border2.nntp.dca.giganews.com!nntp.giganews.com!postnews.google.com!e18g2000yqo.googlegroups.com!not-for-mail
Xref: forums-1-dub sybase.public.impact:2164
Article PK: 230241


On Feb 27, 8:49 am, Doug Myers wrote:
> I am trying to use two qualifiers in the MSHMessageEventCode
> output component to determine if the message event code
> equals an A04 AND the patient class equals E (emergency).
> If both are true I want to replace the A04 with an A05 in
> the MSHMessageEventCode.  I then set up another
> MSHMessageEventCode output component with the same
> qualifiers but as not equal to output the code as is.  This
> works fine if I only use the patient class qualifier or if I
> only use the A04 qualifier but if I use both in the
> component, nothing gets output.  Is there a reason why the
> component will not work with two or more qualifiers?  They
> used too.  I am using V5.5.3 on an AIX server.

The first rule component might be the one that makes the A04 into
A05. It would not have the optional ck'ed on either qual.
The 2nd rule component would say
if event != A04 then run it <optional ck'ed>
OR
if pat class !=xyz then run it <optional ck'ed>
OR
if event = A04 and pat class ! = xyz run it <optional ck'ed


Other solutions:
You could have a rule that runs first and sets a dl which would then
be loaded into MSH_09_02 and EVN_01.
So before the MSH_OutRule you would create a Set_DLRule. You would
use a field side DL, DLf_MSH_09_02_Event to capture that value and
then have a filter that grabs the pat class. A custom func would have
the logic. I prefer custom funcs because I add a documentation header
at the top to explain why the function exists.

Or have two rule componants MSH_09_02a_A04toA05 and MSH_09_02b
each would have a qual that would eval the DLs (ODL function). One
rule componant would have the special logic to convert A04 to A05 and
the other would have the reverse of the first qual.