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



Mostly we still use DDS, but for the cases where we do use DDL, we keep our SQL Create statements in *QMQRY objects. The source for these is stored in a QQMQRYSRC source physical file. The objects and source are under the control of our Change Management Software (MKS Implementer). It seems to keep SOX Auditors satisfied enough.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, March 15, 2011 3:36 PM
To: Midrange Systems Technical Discussion
Subject: Re: SQL Files - Source Based or Not?

I too agree that keeping the source is helpful. I tend to see stuff happen that many of you hopefully do not. Why, I really cannot go into.
But I have had file corruption of some files that weren't used often. And in a library that only gets saved once every other month when we do a full system save. By the time I noticed it was hosed it was when the SAVLIB *NONSYS aborted because it was so corrupted. At that time attempting to retrieve the source via iNav was unable to complete either. I had to recreate it from scratch.

Here's an interesting exercise:
CRTSRCPF FILE(ROB/QTBLSRC) RCDLEN(112)
STRSQL
SELECT SYSTEM_TABLE_SCHEMA, SYSTEM_TABLE_NAME, QCMDEXC('RTV...SRC TBL(' concat trim(SYSTEM_TABLE_SCHEMA) concat '/'
concat trim(SYSTEM_TABLE_NAME) concat ') SRCFILE(' concat
trim(SYSTEM_TABLE_SCHEMA) concat '/QTBLSRC)') FROM systables WHERE SYSTEM_TABLE_SCHEMA='ROB'
AND TABLE_TYPE='P' AND FILE_TYPE='D'
ORDER BY SYSTEM_TABLE_NAME

You just have to build the RTV command. :-) Unless you can find one on the internet to do what iNav does.

Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Luis Rodriguez <luisro58@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 03/15/2011 03:51 PM
Subject: Re: SQL Files - Source Based or Not?
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Gord,

Even as sometimes I create SQL views and/or tables directly from either
iNav's SQL Script editor or using iNav's wizards, I always save the SQL
source (sometimes using iNav). Besides being easier, as you wrote, to
recreate a file, it can also make it easier to create a new view or table,
as long as it is similar to one already defined.

Regards,

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



On Tue, Mar 15, 2011 at 2:20 PM, Gord Hutchinson
<gordm1@xxxxxxxxxxxxxxx>wrote:

We are (finally) going to begin creating some files with SQL instead of
DDS.

Are there any issues either way with using source-based SQL or not? I
would
think that source-based files would allow for more quickly recreating
files.

Any recommendations?


Thanks,


Gord

--
Gord Hutchinson

TST Overland Express
ghutchinson@xxxxxxxxxxxxxxx

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.