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



Just for an update - it was the rogue view in QSYS that was causing the problem. Our admin bod renamed it this morning and iSphere worked.

Thanks for all your help/
James Evans
Senior Analyst Programmer
ISG - IT Development
Newcastle Building Society
Tel: 0191 255 8442
Email: james.evans@xxxxxxxxxxxxxxx
Website: www.newcastle.co.uk
Principal Office, Portland House, New Bridge Street, Newcastle upon Tyne, NE1 8AL


-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: 22 October 2015 14:32
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] iSphere source file search issue

I won't reply from Chuck's reply - do read that and check out what he suggests - I looked at a 7.1 system and have SYSTABLES only in QSYS2 - it makes no sense that IBM would have 2 of the same name with such a subtle difference. And the system catalogs from their first appearance were presented as living in QSYS2.

HTH
Vern

On 10/22/2015 3:13 AM, James Evans wrote:
I've been doing some more investigating and there are 2 views of SYSTABLES - one in QSYS and the other in QSYS2 - both looking at the same files Qsys/QADBXREF and Qsys/QADBXMQT. However the view in QSYS shows nothing while QSYS2 shows the catalogue but unfortunately QSYS is above QSYS2 in the system library list.

When I dspfd the 2 logicals there is an SQL statement that builds them and they are just about identical apart from right at the end of the QSYS view it has added the statement AND DBXLIB = 'HSUDTF ' .

I have no idea yet if
1. There should be views in QSYS and QSYS2
2. The SQL Statements in both libraries should be different
3. This is all a red herring and there is something else that needs to be rebuilt.

I've got our infrastructure team speaking to IBM so I will let you know what I come across. Certainly the last change dates to Systables were the same date as when the PTFs were applied.

James Evans
Senior Analyst Programmer
ISG - IT Development
Newcastle Building Society
Tel: 0191 255 8442
Email: james.evans@xxxxxxxxxxxxxxx
Website: www.newcastle.co.uk
Principal Office, Portland House, New Bridge Street, Newcastle upon Tyne, NE1 8AL


-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Tools/400
Sent: 21 October 2015 16:22
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] iSphere source file search issue



Charles,

Of course there is nothing to add regarding to SQLCODE/SQLSTATE. I am as sure as I could be that also the OD (original developer) knows about that. He might not payed attention for it in FNDSTR, because he might rated SYSTABLES as "rock solid".

Regards,

Thomas.

Am 21.10.2015 um 01:26 schrieb CRPence:
On 20-Oct-2015 11:01 -0500, Tools/400 wrote:
On 20-Oct-2015 03:22 -0500, James Evans wrote:
When I run a search over a simple 4 letter string it falls over on
this line

LILINE = %SubSt(SRCDTA : LISTR : LILNG);

<<SNIP>>
It seems as if your SYSTABLES file in QSYS2 does not return a row for
your source file <<SNIP>>
FWiW, one might expect that a failure to find a "row for your source
file" would be exposed at that point in time; i.e. when\because the
SELECT ... INTO ... did not return a row, then an error would be
manifest in response to the sqlcode\sqlstate immediately after the
query, instead of allowing a number of lines of later code to operate
against the effective garbage-in established for the values of the
host-variables?
--
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@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.

This document may contain confidential information intended for the addressee only. Any views or opinions presented do not necessarily represent those of Newcastle Building Society or its subsidiary companies, hereinafter referred to as NBS Group.

If you are not the intended recipient, any disclosure, copying, or reliance upon this E-mail is prohibited. If you have received this document in error, please notify the sender so that NBS Group may arrange for its proper delivery. All e-mails are scanned for viruses and other unacceptable content, which may result in non-delivery of a small proportion of e-mails. Anyone sending urgent/important e-mails should therefore confirm delivery.

NBS Group does not enter into contracts by means of Internet or e-mail and staff are not authorised to enter into contracts in this way.

Newcastle Building Society is authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority and is entered in the Financial Services Register under Registration No. 156058 (www.fsa.gov.uk/register/).

Newcastle Building Society introduces to Newcastle Financial Services Limited (NFSL). NFSL is an appointed representative of Openwork Limited, which is authorised and regulated by the Financial Conduct Authority.

Web site: www.newcastle.co.uk


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.