Browse Prior Art Database

Dynamic Reallocation of Disk Space for Reserved Objects

IP.com Disclosure Number: IPCOM000121450D
Original Publication Date: 1991-Sep-01
Included in the Prior Art Database: 2005-Apr-03
Document File: 1 page(s) / 54K

Publishing Venue

IBM

Related People

Corrigan, MC: AUTHOR [+3]

Abstract

This invention takes the space from reserved objects on the IPL disk device that are being truncated or destroyed and allocates it to the reserved objects that are being created, extended or moved to a different location on the IPL disk device. Nucleus code does the reallocation before any of the reserved areas can be accessed. The space is reallocated directly from one set of objects to the other without the space ever being generally available for the system.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 55% of the total text.

Dynamic Reallocation of Disk Space for Reserved Objects

      This invention takes the space from reserved objects on
the IPL disk device that are being truncated or destroyed and
allocates it to the reserved objects that are being created, extended
or moved to a different location on the IPL disk device.  Nucleus
code does the reallocation before any of the reserved areas can be
accessed.  The space is reallocated directly from one set of objects
to the other without the space ever being generally available for the
system.

      A table is used to list all of the reserved objects that exist
on the AS/400*.  This table is in the nucleus, and the new version is
loaded at the same time as the code that requires the reserved
objects on disk to change.  This table contains entries for all of
the reserved objects that have existed at any time on the system,
including old ones that should already have been destroyed.  It also
includes entries for all of the new reserved objects that need to be
created.  There are flags in each entry that indicate whether or not
the object should be destroyed, created, or changed in some way
(extended, truncated, or moved to a different location) at the
current level of code.  The entries in the table exist forever.  This
allows the most recent level of code to be put on over ANY older
version of code, and allows the system to skip from one release to
ANY later release.  The code verifies the current state of the
reserved objects...