Browse Prior Art Database

Rename or Relocate of a Migrated File Without Recall

IP.com Disclosure Number: IPCOM000105597D
Original Publication Date: 1993-Aug-01
Included in the Prior Art Database: 2005-Mar-20
Document File: 2 page(s) / 50K

Publishing Venue

IBM

Related People

Anglin, MJ: AUTHOR [+3]

Abstract

A rename or a relocate of a migrated file requires a recall of that file in prior art. This recall is expensive (especially if the file is on tape). In addition, this recall is theoretically unnecessary since the file data is not being referenced. This has been a significant usability problem in all prior art, but none have been able to resolve it. Disclosed is a design which allows migrated files to be renamed or relocated without requiring a recall of the migrated data.

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

Rename or Relocate of a Migrated File Without Recall

      A rename or a relocate of a migrated file requires a recall of
that file in prior art.  This recall is expensive (especially if the
file is on tape).  In addition, this recall is theoretically
unnecessary since the file data is not being referenced.  This has
been a significant usability problem in all prior art, but none have
been able to resolve it.  Disclosed is a design which allows migrated
files to be renamed or relocated without requiring a recall of the
migrated data.

      Prior art keeps track of migrated files using the fully
qualified file names of the files in the primary file system.  When a
file name changes (for example during a file rename or file relocate
operation), this migrated file must be recalled.  This disclosure
takes a different view of the file name in the primary file system.
The fully qualified file name in the primary file system becomes just
an attribute of the data object (the file).  Such attributes should
be allowed to be changed without referencing the data object itself,
i.e., rename or relocate without a recall.

      An embodiment of this disclosure requires some unique
identifier in the primary file system which can be used to represent
the data object (or migrated file).  This unique identifier must be
such that it does not change when various attributes of the file
(such as file name) change.  If such identifier exists in the primary
file system, or ca...