SQL object naming convention -- MIDRANGE-L

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

Subject: SQL object naming convention
From: "Dan Bale" <dbale@xxxxxxxxxxxxx>
Date: Mon, 19 Jul 2004 10:34:05 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Frustration's setting in.  Trying to burn off the weekend brain fade.

Wanting to use iSeries Navigator's "Run SQL scripts" function, but am dying
on the SQL object naming convention.  It is set to use *SQL convention.  How
do I change it to *SYS convention permanently?  Tried the RTFM, no help.

Is there an option on the system to set the default to *SYS for every SQL
task permanently?

tia,
db

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: SQL object naming convention , Vern Hamberg

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.