× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Update to RDp 7.5.0.5

Mike


Mike Hockings, P.Eng.
IBM Rational Developer for System z
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx
voice 1-905-413-3199 T/L 313-3199 ITN 23133199
http://www.ibm.com/software/rational/cafe/community/hats




From:
John_Maassel@xxxxxxxxxxxx
To:
wdsci-l@xxxxxxxxxxxx
Date:
05/11/2010 05:14 PM
Subject:
[WDSCI-L] Error message when compiling SQLRPGLE
Sent by:
wdsci-l-bounces@xxxxxxxxxxxx



The trial license on my RDi ran out, so we were told to grab the RDP demo
and use that until we order the permanent keys in the new fiscal year. I
removed RDi and installed RDP. Because I had a project with a lot of
custom member filters, I told RDP to use the workspace files created by
RDi. My filters and commands imported properly, but there is a little
annoyance.

Now, (most of the time) whenever I compile a SQLRPGLE program, I get a
popup window labeled "EVENTS FILE PROCESSINGE" with the following message:

"The ID field of the FILEEND event does not match the ID field of the last

SourceLineRange."

When I click Details, I see:
Mismatched IDs: FILEID: 004 FILEEND: FILEEND 0 001 000000

Our other RDP beta users do not see this message. I'm on version 7.5.0 of

RDP and i5/OS V5R4.

Any ideas on how to get rid of this message? Is it related to using the
existing RDi workspace?
Thanks,
--
John Maassel
IBM i Programmer/Analyst
Bob Evans Farms, Inc

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.