Thanks Tommy. I changed it to:
call GENERATE_SQL( 'CUSTMAST', '*LIBL', 'TABLE',
NAMING_OPTION => 'SYS' )
and got the same error.

To test NAMING_OPTION, I tried using the actual library name in place of
*LIBL, and it worked.

Looks like I'm going to have to use the QUSROBJD API to get the library
name.

- Dan

On Thu, Aug 17, 2017 at 11:40 AM, Tommy Holden <Tommy.Holden@xxxxxxxxx>
wrote:

You have to use *SYS naming to use *LIBL however you simply do *not*
qualify the stored procedure:
CALL GENERATE_SQL is all you would need


Thanks,
Tommy Holden

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan
Sent: Thursday, August 17, 2017 10:37 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: GENERATE_SQL doesn't like object_library = *LIBL

I am using the SQL procedure GENERATE_SQL in an RPG program to generate
the DDL source for existing DDS-defined tables. It works fine if I qualify
the object with a library name, but fails if I try to use *LIBL. So:

Works: call QSYS2.GENERATE_SQL( 'CUSTMAST', 'ARPROD', 'TABLE') Doesn't
work: call QSYS2.GENERATE_SQL( 'CUSTMAST', '*LIBL', 'TABLE') Doesn't work:
call QSYS2.GENERATE_SQL( 'CUSTMAST', *LIBL, 'TABLE')

Using '*LIBL' (with quotes) returns SQL0462 "NO OBJECTS FOUND". However,
"Select * from CUSTMAST" works fine in the same job.

We're on v7r1, recent PTFs and TRs. When I search for GENERATE_SQL in
KnowledgeCenter, there are results for this procedure in v7r2, but not
v7r1. The v7r2 GENERATE_SQL documentation shows that *LIBL is valid for
object_library.

https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_
72/rzajq/rzajqprocgensql.htm

Am I missing something for this parameter? Is it a bug in v7r1, or a new
feature added in v7r2?


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-2019 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].