A library (*LIB) on the AS/400 is an AS/400 object that is used as a system directory to keeps track of other AS/400 object. (It is also keeps track of Program Temporary Fix in AS/400 system libraries.) (The other directories that can be used are the AS/400 Integrated File System and AS/400 Document Library Services AS/400 object.) AS/400 object are not actually stored in libraries. They're really nothing more than namespaces, but it's easier to refer to an AS/400 object as being "in" or "stored in" a library. An AS/400 object can only be stored in one library at a time and there are AS/400 Command Language to help move objects around. Libraries cannot be stored within other libraries as they're designated as "system" AS/400 object. They're made to appear as if they're stored in the QSYS library. Other "system" AS/400 object include user profiles (*USRPRF), configuration AS/400 object (*LIND, *CTLD, & DEVD), etc. ==Qualified Objects== On a AS/400 Command Language, to reference an AS/400 object in a specific library one would specify the library name first, followed by a forward slash, and then the AS/400 object name (ie. MYLIB/MYOBJ). This is called "qualifying an AS/400 object." In almost every AS/400 shop it's the rule that programs must't qualify AS/400 object unless it can't be helped. Programs should always depend on the job's AS/400 Library List to find AS/400 object unless circumstance dictate otherwise, such as in emergencies or if the program is temporary, like a fix program or a kluge. ==Shop Standards== On systems with hierarchical filing systems the norm is to have many directories, most of which are contained one within the other, and with a moderate numbers of files in each directory. Since libraries cannot be stored within other libraries on the AS/400 and because historically the AS/400 Library List was always so small, the opposite became the norm; small numbers of libraries each of which contain large numbers of AS/400 object. Most homegrown applications have between one and three libraries. Some have program, source, and file AS/400 object together in one library. With shops that have a huge amount of data and a small backup window they usually split the database files into a separate data library and keep the source and programs in another library. In companies with a separate development systems they tend to split it further by placing the source into its own library. ==AS/400 and SQL== Most DBMS systems use SQL based terminilogy to describe objects. The AS/400's terminilogy is unique to the AS/400 and may have generated some confusion. HLL languages have often been preferred over SQL with AS/400 programming, do to actual or perceived performance reasons. As SQL programming has become more common on the AS/400, both methods traditional and SQL based have become availble to create and use objects, depending on preference or need. For the most part traditional library based objects are the same as SQL objects, with at least equivalent capabilities. For example a Library is a Schema, a Physical File is a Table, Logical File is a View and a Access Path is a Index. AS/400
See other meanings of words starting from letter:
Words begining with AS/400_library:
AS/400_library
AS/400_Library_List
AS/400 library
A library (*LIB) on the AS/400 is an AS/400 object that is used as a system directory to keeps track of other AS/400 object. (It is also keeps track of Program Temporary Fix in AS/400 system libraries.) (The other directories that can be used are the AS/400 Integrated File System and AS/400 Document Library Services AS/400 object.) AS/400 object are not actually stored in libraries. They're really nothing more than namespaces, but it's easier to refer to an AS/400 object as being "in" or "stored in" a library. An AS/400 object can only be stored in one library at a time and there are AS/400 Command Language to help move objects around. Libraries cannot be stored within other libraries as they're designated as "system" AS/400 object. They're made to appear as if they're stored in the QSYS library. Other "system" AS/400 object include user profiles (*USRPRF), configuration AS/400 object (*LIND, *CTLD, & DEVD), etc. ==Qualified Objects== On a AS/400 Command Language, to reference an AS/400 object in a specific library one would specify the library name first, followed by a forward slash, and then the AS/400 object name (ie. MYLIB/MYOBJ). This is called "qualifying an AS/400 object." In almost every AS/400 shop it's the rule that programs must't qualify AS/400 object unless it can't be helped. Programs should always depend on the job's AS/400 Library List to find AS/400 object unless circumstance dictate otherwise, such as in emergencies or if the program is temporary, like a fix program or a kluge. ==Shop Standards== On systems with hierarchical filing systems the norm is to have many directories, most of which are contained one within the other, and with a moderate numbers of files in each directory. Since libraries cannot be stored within other libraries on the AS/400 and because historically the AS/400 Library List was always so small, the opposite became the norm; small numbers of libraries each of which contain large numbers of AS/400 object. Most homegrown applications have between one and three libraries. Some have program, source, and file AS/400 object together in one library. With shops that have a huge amount of data and a small backup window they usually split the database files into a separate data library and keep the source and programs in another library. In companies with a separate development systems they tend to split it further by placing the source into its own library. ==AS/400 and SQL== Most DBMS systems use SQL based terminilogy to describe objects. The AS/400's terminilogy is unique to the AS/400 and may have generated some confusion. HLL languages have often been preferred over SQL with AS/400 programming, do to actual or perceived performance reasons. As SQL programming has become more common on the AS/400, both methods traditional and SQL based have become availble to create and use objects, depending on preference or need. For the most part traditional library based objects are the same as SQL objects, with at least equivalent capabilities. For example a Library is a Schema, a Physical File is a Table, Logical File is a View and a Access Path is a Index. AS/400
See other meanings of words starting from letter:
A
AB | AC | AD | AE | AF | AG | AH | AI | AJ | AK | AL | AM | AN | AO | AP | AR | AS | AT | AU | AW | AX | AY | AZ |Words begining with AS/400_library:
AS/400_library
AS/400_Library_List
Sponsored links: praca.
These materials are based on Wikipedia and licensed under the GNU FDL
YouTube.com videos better site than Turbo Tax 2007
