Re: Restore SQL collection to a different name? -- 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: Re: Restore SQL collection to a different name?
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Mon, 04 Apr 2005 12:25:28 -0500
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>

Mike Wills wrote:
> FWIW: I just created a new sql collection and did a CPYLIB on the
> original collection ... all the constraint information was actually
> copied over fine ... but the journal's were not attached to the files
> that were copied.

Thus the library name restriction appears to be related to the journals,
not the constraints.

As journals have existed in the OS since S/38 days, I'm floored that
this hasn't been an issue before.

david

-- 
David Gibbs
david@xxxxxxxxxxxx

Receipt of this message does not grant you permission to send me
Unsolicited Commercial Email

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Restore SQL collection to a different name? , Mike Wills
Re: Restore SQL collection to a different name? , Simon Coulter

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.