Re: Application Database Objects

["Mark S. Waterbury" <mark.s.waterbury@xxxxxxx>]

Think of it this way:

QSYS.LIB is the name of one of the file systems within the Integrated 
File System (IFS).  It is also sometimes called the Library file system.

QSYS is the name of the system library, which is also the "root" of the 
QSYS.LIB file system. All other *LIB (library) objects exist in QSYS.

All traditional OS/400 objects exist within an OS/400 library (and so, 
by definition, they must be within the QSYS.LIB file system). This 
includes *FILEs (physcail files and logical files in OS/400 terminology).

The QSYS.LIB file system is also known as the DB2 file system, because 
all DB2/400 tables and views etc. exist only within this file system in 
OS/400 or i5/OS.

Other file system in the IFS support mainly Unix-like "stream files" 
(aka. byte stream files).  This includes the "root" filesystem and the 
QOpenSys file system.  A User-Defined File System (UDFS) allows you to 
define a mountable file system (that also supports only stream files), 
and you can mount these UDFS "volumes" attaching it anywhere you want 
to, in the tree of directories under the "root" (/) file system. The 
QNTC file system allows accessing files on an NT server. 

See the InfoCenter for an overview of the IFS, and the various file systems.

   
http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/topic/ifs/rzaaxkickoff.htm
and
   
http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/topic/rzahs/rzahslotprod.htm

for starters...

Hope that helps.

> Laine, Rogers wrote:
> Based on the sample schema's I have created it will always put it in
> QSYS.
>
> Thanks for providing all the input on this question. It has help me
> understand the differences between the two operating systems.  
>
> Thanks,
> Rogers
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Campin
> Sent: Friday, August 21, 2009 2:59 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: Application Database Objects
>
> Also, the point should be made that you don't create it there. You
> simple create the library or collection and it puts it there. You have
> no control over where it puts the library. It is immaterial where they
> put in. You just refer to everything by the library or schema name
>
> On Fri, Aug 21, 2009 at 1:32 PM, Michael Ryan <michaelrtr@xxxxxxxxx>
> wrote:
>
>   
> > Your collection (library) will be in QSYS...all libraries 
> > (collections) exist in QSYS. Collection and schema and library are 
> > synonyms on the iSeries.
> >
> > On Fri, Aug 21, 2009 at 3:18 PM, Laine, Rogers <rlaine@xxxxxxxxxxxxxxx
> >     
> > > wrote:
> > >       
> > > My background is DB2 on the z-series, that is why I use the term 
> > > database.
> > >
> > > It sounds like on the I this is called SCHEMA.
> > >
> > > Again my concern is should my application schema's be located in the
> > >       
>
>   
> > > QSYS library or some where else?
> > >
> > > Rogers
> > >
> > > -----Original Message-----
> > > From: midrange-l-bounces@xxxxxxxxxxxx 
> > > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Elvis Budimlic
> > > Sent: Friday, August 21, 2009 1:46 PM
> > > To: 'Midrange Systems Technical Discussion'
> > > Subject: RE: Application Database Objects
> > >
> > > Still mixing terms I'm afraid.
> > >
> > > DATABASE=LPAR or iASP=collection of schemas and associated objects 
> > > SCHEMA=COLLECTION=LIBRARY TABLE=PHYSICAL FILE VIEW=NON-KEYED LOGICAL
> > >       
>
>   
> > > FILE INDEX=KEYED LOGICAL FILE ...
> > >
> > > Note that for several releases System i has supported installing 
> > > multiple databases on the same system/LPAR by leveraging the iASP 
> > > support. Run WRKRDBDIRE to see what he's talking about. If you have 
> > > iASPs installed, run WRKCFGSTS *DEV *ASP to see corresponding iASP 
> > > information.
> > >
> > > I don't know what the original poster's background is, but if he 
> > > came from another platform, he really means database when he says
> > >       
> database.
>   
> > > On a number of other platforms database is simply a stream file 
> > > (with complicated internal structure of course), install into a file
> > >       
>
>   
> > > system and a server can have many databases installed simultaneously
> > >       
> on it.
>   
> > > So, if OP is talking DB2 for i database, it's clear - either default
> > >       
>
>   
> > > LPAR or iASP library.
> > >
> > > If OP is talking a different database (i.e. mySQL), then IFS is a 
> > > valid option.
> > >
> > > Then again, the OP may indeed simply mean schemas, in which case 
> > > you're correct of course.
> > >
> > > Elvis
> > >
> > > Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS 
> > > and OS/400 www.centerfieldtechnology.com
> > >
> > >
> > > -----Original Message-----
> > > Subject: Re: Application Database Objects
> > >
> > > 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 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 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.
> >
> >
> >     
> --
> 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 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.
>
>