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



Gary,

Just a big WAG but, my SQL reference manual says the following about the
USING keyword in CONNECT:

If password is specified as a literal, it must be a character string. The
maximum length is 128 characters. It must be left justified. The literal
form of the password is not allowed in static SQL or REXX.

----------------------
If a *host-variable* is specified,
* It must be a character-string variable.
* It must not be followed by an indicator variable.
* The password must be left-justified within the host variable.
* If the length of the password is less than that of the host variable, it
must be padded on the right with blanks.
----------------------

So I wonder what would happen if you just enclose your password in quotes?
Something like:

wkUsing = '''' + %trim(wkUsing) + '''';

Not very sure about the quotes number.

HTH,



----

If password is specified as a literal, it must be a character string. The
maximum length is 128 characters. It must be left justified. The literal
form of the password is not allowed in static SQL or REXX. If a *host-variable
*is specified, v It must be a character-string variable. v It must not be
followed by an indicator variable. v The password must be left-justified
within the host variable. v If the length of

Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries
--



On Thu, Sep 29, 2011 at 1:20 PM, Gary Thompson <GThompson@xxxxxxxxxxx>wrote:

Thanks Alan and Dennis:

I changed D specs to:
D wkUser S 20A Varying(2) Inz('xxxxxxxx')
D wkUsing S 30A Varying(2) Inz('yyyyyy')

In debug, host variables look good, more or less matching STRSQL session
values, with the only
difference being the STRSQL password is enclosed in single quote
characters:
connect to JDBCTEST user xxxxxxxx using 'yyyyyy'

After re-compile and new debug session:

CONNECT TO still returns: SQLCODE -113 SQLSTATE 28000

--
This is the RPG programming on the IBM i / System i (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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.