×
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.
rob@xxxxxxxxx wrote:
You could try weeding through the following to see if you might
have missed any. You may have to change length depending on
version of bpcs.
SELECT SYSTEM_COLUMN_NAME, SYSTEM_TABLE_NAME
, SYSTEM_TABLE_SCHEMA,
DATA_TYPE, LENGTH, NUMERIC_SCALE,
COLUMN_HEADING, LONG_COMMENT
FROM syscolumns
WHERE DATA_TYPE='CHAR' AND LENGTH=15
<<SNIP>>
Side comment about using the SQL catalog for possibly non-SQL
database files...
Always be sure to review or otherwise to understand the CREATE
statement of the VIEW being used, e.g. by DSPFD SYSCOLUMNS, before
depending on the output from a query of that VIEW. The WHERE clause
on the SYSCOLUMNS VIEWs eliminate some [types of] database files
which may be of interest to have included in, rather than excluded
from, the alluded interrogation. Also note neither the FROM clause
nor the DSPFD in this message give the qualified name, and would be
assumed to be QSYS2 to ensure system-wide [iASP anyhow] information.
If the SYSCOLUMNS file were to come from another library, the
WHERE clause of that VIEW in *LIBL [or with *SQL naming, from the
library name matching the authorization ID] could be even further
limited to a specific library.
Regards, Chuck
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.
midrange.com
