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.

Need help with Carriage retune pattern reorganization in Tran_IDE

2 posts in General Discussion Last posting was on 2007-07-30 17:59:59.0Z
Rama Parola Posted on 2007-07-16 02:25:46.0Z
Sender: 1c52.46839f88.1804289383@sybase.com
From: Rama Parola
Newsgroups: sybase.public.impact
Subject: Need help with Carriage retune pattern reorganization in Tran_IDE
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <469ad72a.7f61.1681692777@sybase.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 15 Jul 2007 19:25:46 -0700
X-Trace: forums-1-dub 1184552746 10.22.241.41 (15 Jul 2007 19:25:46 -0700)
X-Original-Trace: 15 Jul 2007 19:25:46 -0700, 10.22.241.41
Lines: 20
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.impact:2073
Article PK: 230159

We are running the impact version 5.4.6 and we are facing a
problem in Tran_IDE regarding pattern recognition involving
carriage return. Based on the information in a presentation
(Paul Hermens, Staff software engineer, Sybase) at this site
that showed how to recognize patterns with carriage returns,
we tried it out in our system. However it didn’t work as
expected. The pattern that we want recognized is the string
ORC following a carriage return.

In the Input Field Information window, when we select the
Follows-pattern, anchor field and input \015ORC in the
Pattern box, pattern is not being recognized. However, when
we define group and use Pattern Separator List and specify
the pattern there with \015 it works.

When we use only ORC it works. However, very rarely in some
segments there is data with the string ORC| in it and this
creates a problem in the input field.

Any help with this is greatly appreciated.


Christian Deschamps Posted on 2007-07-30 17:59:59.0Z
Sender: 72b0.4678177b.1804289383@sybase.com
From: Christian Deschamps
Newsgroups: sybase.public.impact
Subject: Re: Need help with Carriage retune pattern reorganization in Tran_IDE
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <46ae271f.3dcc.1681692777@sybase.com>
References: <469ad72a.7f61.1681692777@sybase.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 30 Jul 2007 10:59:59 -0700
X-Trace: forums-1-dub 1185818399 10.22.241.41 (30 Jul 2007 10:59:59 -0700)
X-Original-Trace: 30 Jul 2007 10:59:59 -0700, 10.22.241.41
Lines: 34
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.impact:2086
Article PK: 230168

Have you tried to select a previous field with the Anchor
and limit the scope with the Sep. patterns ?

The Anchor helps to set the parser pointer to the
appropriate location within the message. And the Scope
pattern specifies the pattern of the next segment, which
delimits the ORC boundary.

It might reduce the risk of finding a string pattern that is
not the header ORC that you are looking for.

hope it helps.

> We are running the impact version 5.4.6 and we are facing
> a problem in Tran_IDE regarding pattern recognition
> involving carriage return. Based on the information in a
> presentation (Paul Hermens, Staff software engineer,
> Sybase) at this site that showed how to recognize patterns
> with carriage returns, we tried it out in our system.
> However it didn’t work as expected. The pattern that we
> want recognized is the string ORC following a carriage
> return.
>
> In the Input Field Information window, when we select the
> Follows-pattern, anchor field and input \015ORC in the
> Pattern box, pattern is not being recognized. However,
> when we define group and use Pattern Separator List and
> specify the pattern there with \015 it works.
>
> When we use only ORC it works. However, very rarely in
> some segments there is data with the string ORC| in it and
> this creates a problem in the input field.
>
> Any help with this is greatly appreciated.