Content deleted Content added
ChaoticBrain (talk | contribs) No edit summary |
use new article name for Db2 |
||
Line 4:
*OAM datasets are not directly cataloged. Rather, they are stored into OAM collections, with only the OAM collection being cataloged. The reason for this is to prevent the catalog from being overloaded with large numbers of (e.g. image) files.<ref name="HardingClark1990">{{cite journal|last1=Harding|first1=W. B.|last2=Clark|first2=C. M.|last3=Gallo|first3=C. L.|last4=Tang|first4=H.|title=Object storage hierarchy management|journal=IBM Systems Journal|volume=29|issue=3|year=1990|pages=384–397|issn=0018-8670|doi=10.1147/sj.293.0384|quote=The ability to locate existing objects in storage is fundamental to any data processing system. The facility that carries out the locate function for data sets in an MVS system is the catalog. Typical MVS systems may have tens or even hundreds of thousands of data set entries recorded in a hierarchy of catalogs. In contrast, OAM must be able to manage hundreds of millions of objects, which if individually cataloged would require an excessively large catalog... The system catalog was extended through the concept of collections to handle the large numbers of objects expected for image applications. A catalog entry is defined for each collection, and provides the default storage class and management class assignments for objects stored in the collection, and the identifier of the storage group where the collection is physically stored.}}</ref>
OAM is used in conjunction with [[IBM
==History==
| |||