× 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.



Hi all,

From my point of view there most be something different wrong. The current source sequence numbers of a source member should not affect the line positioning when opening a source member from the iSphere Source File Search, as long as there is no way of changing the logic the Lpex editor positions to a line.

Service program FNDSTR does not return the actual line number to RDi but counts and returns the physical line number starting at 1. For example it always returns "11" when searching member DEMO1 for "demo".

I resequenced DEMO1 starting at 0000.02 with an increment of 0.3. When I search DEMO1 for "demo", iSphere returns "11" and the Lpex editor is positioned to line 0003.02.

The line numbers 1 to 11 are:

0000.02
0000.32
0000.62
0000.92
0001.22
0001.52
0001.82
0002.12
0002.42
0002.72
0003.02 //* Demo of iSphere Source File Search API

Thomas.

-----Ursprüngliche Nachricht-----
Von: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxxxxxxxx] Im Auftrag von Robert Rogerson
Gesendet: Mittwoch, 16. Januar 2019 19:44
An: wdsci-l@xxxxxxxxxxxxxxxxxx
Betreff: Re: [WDSCI-L] Wrong statement number in iSphere Source File Search...

@Kevin, thanks, I do see 711 in the upper left corner.

@Matt, in this scenario I'm not using iProjects.  But Kevin pointed out
my misunderstanding.

@Ken, as a standard in the shop we didn't resequence the members.  Since
almost everyone is using RDi I will bring it up as maybe the standard is
outdated and we could change it.

Thanks everyone.

Rob

On 1/16/2019 11:29 AM, Kevin Bucknum wrote:
Somewhere you should have some line numbers that aren't 1 away from the previous line number. So something like 50000 50100 50101 50102 50200
Look in the upper left hand side of your source and you see that you are on statement 711. Statement != line number.

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Robert Rogerson
Sent: Wednesday, January 16, 2019 10:26 AM
To: Websphere Development Studio Client for iSeries
Subject: [WDSCI-L] Wrong statement number in iSphere Source File Search...

Hi all,

First off, RDi 9.6.0.5 and iSphere 3.5.1.b001

I created a search for a variable name and multiple programs were returned in the iSphere Source File Search Tab.

When I click on the programs in the member column the statement and source text are displayed in the Statement column. When I right click and browse the editor opens to the correct line (as far as the text
goes) but the line in the editor doesn't match the line which was in the Statement column of the iSphere Source File Search
Tab.(https://imgur.com/a/ytJZvs6)

I've confirmed (as far as I can see) that the member that is opened is the member in the Member column of the iSphere Source File Search Tab. The line numbers do match for some programs in the tab but not for others.

Has anyone else seen this happen? Does anyone know what my problem may be?

Thanks,

Rob

--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/wdsci-l.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


[https://www.medtronsoftware.com/img/MedtronMinilogo.bmp] Kevin Bucknum
Senior Programmer Analyst
MEDDATA / MEDTRON
120 Innwood Drive
Covington LA 70433
Local: 985-893-2550
Toll Free: 877-893-2550
https://www.medtronsoftware.com



CONFIDENTIALITY NOTICE

This document and any accompanying this email transmission contain confidential information, belonging to the sender that is legally privileged. This information is intended only for the use of the individual or entity named above. The authorized recipient of this information is prohibited from disclosing this information to any other party and is required to destroy the information after its stated need has been fulfilled. If you are not the intended recipient, or the employee of agent responsible to deliver it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or action taken in reliance on the contents of these documents is STRICTLY PROHIBITED. If you have received this email in error, please notify the sender immediately to arrange for return or destruction of these documents.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.