Re: Application Database Objects

Amplifying what Laine said. Libraries are traditional and SQL libraries. The
SQL term is Schema or Collection. If you want to create your tables as SQL
tables, create your libraries as SQL libraries.

SQL libraries look like regular libraries but have a journal automatically
created and standard views over the system tables. Anytime a table is
creating(DDL or DDS) in an SQL library, it is automatically journalled.

You create SQL libraries by using Ops Nav or by doing STRSQL and using
CREATE COLLECTION.


On Fri, Aug 21, 2009 at 10:21 AM, Michael Ryan <michaelrtr@xxxxxxxxx> wrote:

Mixing terms here. Are you talking about tables or collections? Collections
(databases) are libraries, and they're always in QSYS. Tables can be in any
library. The IFS wouldn't have anything to do with this. The IFS is for
non-traditional objects, specifically non-library based objects like stream
files and such. The traditional file system is very flat - all objects
exist
in a library, all libraries exist in QSYS.



On Fri, Aug 21, 2009 at 12:11 PM, Laine, Rogers <rlaine@xxxxxxxxxxxxxxx

wrote:

We would like to start creating application databases on our Power6.

When i create a sample database it gets placed in the QSYS.LIB.

Is this the recommended library to create these databases. I think of
QSYS as a System Type library.

I would think it would be better to create these databases under a new
IFS library called QAPPL.

So what is the command to create QAPPL under IFS, if this is the
approved method?

Rogers
************************************************
This E-Mail transmission (and/or the documents accompanying it)
may contain information belonging to the sender which is confidential,
privileged and/or exempt from disclosure under applicable law. The
information is intended only for the use of the individual(s) or entity
named above. If you are not the intended recipient, you are hereby
notified that any disclosure, copying, distribution or the taking of any
action in reliance on the contents of this information is strictly
prohibited. If you have received this E-Mail transmission in error,
please immediately notify us by return E-Mail or telephone to arrange
for return of its contents including any documents.
--
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.

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