RE: Accessing Remote Database using SQL - requesting an SQL Package?

The name "key" is simply a place holder word in this example. The actual column's name is not "key".

The definition of "key" is char(24).

Steve Needles


-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Mildenberger
Sent: Tuesday, July 29, 2014 3:36 PM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: RE: Accessing Remote Database using SQL - requesting an SQL Package?

key is also a reserved word, don't know if that could figure into it. If it mattered Chuck probably would have mentioned :) Maybe try with a different field name.

Scott


-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Tuesday, July 29, 2014 2:30 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Accessing Remote Database using SQL - requesting an SQL Package?

I would suggest trying to declare the variable KEY in different ways than shown, testing to see if\what variants might /circumvent/ the issue. I would try each of:

as DS component with explicit typing; not the LIKE()
standalone variable with the LIKE()
standalone variable with explicit typing, not the LIKE()
as DS component with LIKE() but no prefix in ext-DS and LIKE()

If /key/ is a DATE data type, then be sure to specify the SQL SET OPTION DATFMT=*ISO [or SQL compiler Date Format attribute] because IIRC, that mismatch between the RPG date format and the SQL date format is a common origin for -312; due to the default DATFMT(*JOB).
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.

________________________________
This communication, including attachments, is confidential, may be subject to legal privileges, and is intended for the sole use of the addressee. Any use, duplication, disclosure or dissemination of this communication, other than by the addressee, is prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy this communication and all copies.

TRVDiscDefault::1201