Hi,
I assume the naming was changed from *SYS to *SQL (even though I cannot
explain how it would have been happened).
When using System naming the library list will be searched, while with SQL
naming only files, views and indexes located in a single library/schema can
be used unqualified. Also the schema to be searches is the schema with the
name of the current use profile as long as it is not changed with the SQL
Statement SET CURRENT SCHEMA.
The path, set by SET PATH is only used to find Stored Procedures and User
defined Functions, but NOT to find files, views and indexes.
In either way I always add an SET OPTION statement into my sources with
NAMING = *SYS to make sure that always System Naming will be used, even if
the defaults of the compile command will change.
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im
Auftrag von daveML@xxxxxxxxxxxx
Gesendet: Monday, 26. July 2010 20:34
An: RPG programming on the IBM i / System i
Betreff: Re: SQL Errors after 7.1 upgrade?
Upgrade from 6.1 (with all latest cume/groups) to 7.1 (with all latest
cume/groups)...
Coincidently perhaps, things seem to be working. As a workaround I set the
native SQL PATH in the subprocedure that creates the JDBC connection. The
idea was to issue the SET PATH = "lib1","lib2" to force native SQL to have
the necessary libs. I think just by changing the module that creates the
JDBC connection to SQLRPGLE the SQL server mode is smart enough to grab the
calling job's libl now. Before it was blank, and now it has the full libl
-- not just the couple of libs I specified in the SET PATH.
Very odd, but hopefully this will continue to work.
----------------------------------------
From: "Luis Rodriguez" <luisro58@xxxxxxxxx>
Sent: Monday, July 26, 2010 11:24 AM
To: "RPG programming on the IBM i / System i" <rpg400-l@xxxxxxxxxxxx>
Subject: Re: SQL Errors after 7.1 upgrade?
Dave,
From which release are you upgrading?
Luis Rodriguez
IBM Certified Systems Expert - eServer i5 iSeries
--
midrange.com
