When creating an object (or a member) the system needs to know where you want to put it. *LIBL is too generic!
--Paul E Musselman
.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan
Sent: Thursday, August 17, 2017 11: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?
- Dan
midrange.com
