This section lists some of some of the distinctions between banks. These distinctions do not involve the internal logic of the banks, but the nature of the range keys that they use.

Some space banks may provide pages that are safer than others. For instance some may provide storage that is twinned. Such pages are stored on two different devices in such a way that the data is still available if one device fails.

Some space banks may provide pages and nodes that are stored on inherently more reliable equipment.

Some space banks may provide pages with the attribute that "write verification" is performed when they are written.

Some space banks may provide space on 3850s {etc.}.

Two space banks may be alike except that one is allocating storage from one area and the other from another area. This is advantageous when one is trying to arrange for locality of reference on hardware such as the 3850.

CP/370 allocates disk storage inflexibly. The real storage allocated to a user is typically fixed for days at a time. Other operating systems allocate storage subject only to the restriction that the sum of the sizes of the files {measured in fixed-size blocks} of all of the users be less than the total system storage available. Still other systems mix these strategies by limiting a user so as not to let one user exhaust the system's entire storage.

These strategies and others can be administrated by space banks.

Space banks combined with accounts {(p2,account)} factor the problem of quality and quantity of storage.

The account mechanism can measure and perhaps limit storage used.

Some banks will provide pages and nodes guaranteed not to be deleted until previously agreed upon situation.