|
I fail to understand why all the WHERE conditions.
1=1??? Is this just a thing you always do to avoid warning errors that
you have no where clause?
And why
... and substr(table_Schema,1,1) not in ('Q', '#')
When you have
and table_schema = 'DPPDATA'
D already excludes Q and #.
Let me guess your evolution.
First, I was right on the evolution on the 1=1, right?
Second, you started by specifying Q and # to only get "user" libraries?
Third, then you added just the library you wanted?
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of a4g
atl
Sent: Monday, November 15, 2021 10:34 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: CPF2803, CPF428A
CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.
I am using SQL to list all columns in a table.
create table dfreinkel.tbl_fields as (
Select * from qsys2.syscolumns
where 1=1
and substr(table_Schema,1,1) not in ('Q', '#')
and table_schema = 'DPPDATA'
) with data ;
Select Table_Schema
, Table_Name
, Column_Name
, Column_Text
, Ordinal_Position
, Data_Type
, Length
, Numeric_Scale as Decimals
, precision
, Column_heading
from dfreinkel.tbl_fields
order by table_schema, table_Name, ordinal_Position
;
CL:CPYTOIMPF FROMFILE(DFREINKEL/TBL_FIELDS)
TOSTMF('/home/DFREINKEL/Table_Fields.csv') MBROPT(*REPLACE) RCDDLM(*CRLF)
RMVBLANK(*BOTH) ADDCOLNAM(*SQL)
;
The CL fails with the above error messages. It also fails when executed
from the command line.
This is a v7.3 system.
Any ideas on the problem and a work around?
TIA, DArryl Freinkel
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
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.