US 5,014,192 AGrant
System for Locating a File in a Logical Ring by Sequentially Forwarding Access Request With File System Name and File Name
Issue Date:1991-05-07
•8 Claims
•6 Drawing Sheets
Abstract
A data management system used by a digital computer system comprises a plurality of individual file systems which are connected together in a logical ring configuration around which file requests travel. File requests may be transmitted by the user to the "next" file system in the ring relative to the user. File requests optionally may or may not specify a file system name. If a file system name is specified, then the request is forwarded unidirectionally around the logical ring until either that file system name is found or the request returns to its starting point. If no file system name is specified, then an attempt is made to satisfy the request on each file system in turn until either the request is satisfied or the request returns to its starting point.
Metadata
Assignee
- Motorola Computer X, Inc.
Inventors
- Bruce M. Mansfield
- Frank C. Kolnick
- Andrew I. Kun
Application Information
Application Number:US 3006875
Filing Date:1989-01-19
Priority Date:1985-05-06
Art Unit:232
Classifications
IPC:
G06I 1342
Field of Search:
364340370200 MS File;900 MS File825.05;825.5085.4;85.5;94.1
Patent Drawings (6 sheets)
Description
TECHNICAL FIELD
This invention relates generally to digital data processing, and, in particular, to a data management system comprising a plurality of file systems coupled in a logical ring.
BACKGROUND OF THE INVENTION
The present invention concerns a distributed data processing system--that is, two or more data processing systems which are capable of functioning independently but which are so coupled as to send and receive messages to and from one another.
A Local Area Network (LAN) is an example of a distributed data processing system. A typical LAN comprises a number of autonomous data processing "cells", each comprising at least a processor and memory. Each cell is capable of conducting data processing operations independently. In addition, each cell is coupled (by appropriate means such as a twisted wire pair, coaxial cable, fiber optic cable, etc.) to a network of other cells which may be, for example, a loop, star, tree, etc., depending upon the design considerations.
As mentioned above, the present invention finds utility in such a distributed data processing system, since there is a need in such a system for the processes which are executing or to be executed in the individual cells to share data and to communicate data among themselves.
Information may be thought of as being stored in the form of files in one or more "file systems". A file system is a way of logically organizing data, and it may comprise one or more physical data storage devices. Usually, a file system comprises an organized arrangement of data and a file index identifying the data, its location, and perhaps other characteristics.
In the present invention, any of the individual cells of a LAN may contain one or more file systems. Certain file systems may be unique, while other file systems may be copies in order to provide a degree of redundancy.
There is an urgent need in certain distributed data processing systems to provide "data access transparency". Data access transparency is defined herein to mean that any file can be accessed by any process located anywhere in the distributed data processing system.
There is also an urgent need regarding certain of such distributed data processing systems to provide "data residence transparency". Data residence transparency is defined herein to mean that any file can be accessed wherever it may reside, even if it has been physically moved within the system.
BRIEF SUMMARY OF INVENTION
Accordingly, it is an object of the present invention to provide an improved data management system within a distributed data processing system.
It is also an object of the present invention to provide a distributed data processing system having a data management system with data access transparency.
It is a further object of the present invention to provide a distributed data processing system having a data management system with data residence transparency.
These and other objects are achieved in accordance with a preferred embodiment of the invention by providing a data management system for use in a data processing system, the data management system comprising a plurality of individual file systems, means for coupling the file systems together, means for generating an access request to one of the file systems, and means for attempting to satisfy the access request by accessing successive file systems until either the access request is satisfied or until all of the file systems have been accessed.
BRIEF DESCRIPTION OF THE DRAWINGS
The invention is pointed out with particularity in the appended claims. However, other features of the invention will become more apparent and the invention will be best understood by referring to the following detailed description in conjunction with the accompanying drawings in which:
FIG. 1 shows a representational illustration of a single network, distributed data processing system incorporating the improved data management system of the present invention.
FIG. 2 shows a block diagram illustrating a multiple-network, distributed data processing system incorporating the improved data management system of the present invention.
FIG. 3 shows an architectural model of a data processing system incorporating the present invention.
FIG. 4 shows the relationship between software contexts and processes as they relate to the present invention.
FIG. 5 shows the relationship between external events and processes.
FIG. 6 shows how messages may be sent between processes within nested contexts.
FIG. 7 shows an architectural model of the improved data management system incorporating the present invention.
FIG. 8 shows an architectural software model of the improved data management system incorporating the present invention.
FIG. 9 shows the relationship between pictures, views, and windows in the human interface of a data processing system incorporating the present invention.
FIG. 10 shows a conceptual view of the different levels of human interface within a data processing system incorporating the present invention.
FIG. 11 shows a block diagram of a logical ring of file systems, illustrating how an access request to a file system is handled by the present invention.
FIG. 12 shows a flow diagram illustrating the operation of the improved data management system of the present invention.
OVERVIEW OF COMPUTER SYSTEM
With reference to FIG. 1, a distributed computer configuration is shown comprising multiple cells 2-7 (nodes) loosely coupled by a local area network (LAN) 1. The number of cells which may be connected to the network is arbitrary and depends upon the user application. Each cell comprises at least a processor and memory, as will be discussed in greater detail with reference to FIG. 2 below. In addition, each cell may also include other units, such as a printer 8, operator display module (ODM) 9, mass memory module 13, and other I/O device 10.
With reference now to FIG. 2, a multiple-network distributed computer configuration is shown. A first local area network LAN 1 comprises several cells 2, 4, and 7. LAN 1 is coupled to a second local area network LAN 2 by means of an Intelligent Communications Module (ICM) 50. The Intelligent Communications Module provides a link between the LAN and other networks and/or remote processors (such as programmable controllers).
LAN 2 may comprise several cells (not shown) and may operate under the same LAN protocol as that of the present invention, or it may operate under any of several commercially available protocols, such as Ethernet; MAP, the Manufacturing Automation Protocol of General Motors Corp.; Systems Network Architecture (SNA) of International Business Machines, Inc.; SECS-II; etc. Each ICM 50 is programmable for carrying out one of the above-mentioned specific protocols. In addition, the basic processing module of the cell itself can be used as an intelligent peripheral controller (IPC) for specialized devices.
LAN 1 is additionally coupled to a third local area network LAN 3 via ICM 52. A process controller 55 is also coupled to LAN 1 via ICM 54.
A representative cell N (7, FIG. 2) comprises a processor 24 which, in a preferred embodiment, is a Motorola 68010 processor. Each cell further includes a read only memory (ROM) 28 and a random access memory (RAM) 26. In addition, each cell includes a Network Interface Module (NIM) 21, which connects the cell to the LAN, and a Bus Interface 29, which couples the cell to additional devices within a cell. While a minimal cell is capable of supporting two peripheral devices, such as an Operator Display Module (ODM) 41 and an I/O Module 44, additional devices (including additional processors, such as processor 27) can be provided within a cell. Other additional devices may comprise, for example, a printer 42, and a mass-storage module 43 which supports a hard disk and a back-up device (floppy disk or streaming tape drive).
The Operator Display Module 41 provides a keyboard and screen to enable an operator to input information and receive visual information.
While a single cell may comprise all of the above units, in the typical user application individual cells will normally be dedicated to specialized functions. For example, one or more mass storage cells may be set up to function as data base servers. There may also be several operator consoles and at least one cell for generating hard-copy printed output. Either these same cells, or separate dedicated cells, may execute particular application programs.
The system is particularly designed to provide an integrated solution for factory automation, data acquisition, and other real-time applications. As such, it includes a full complement of services, such as a graphical output, windows, menus, icons, dynamic displays, electronic mail, event recording, and file management. Software development features include compilers, a window-oriented editor, a debugger, and performance-monitoring tools.
Local Area Network
The local area network, as depicted in either FIG. 1 or FIG. 2, ties the entire system together and makes possible the distributed virtual machine model described below. The LAN provides high throughput, guaranteed response, reliability, and low entry cost. The LAN is also autonomous, in the sense that all system and applications software is unaware of its existence. For example, any Network Interface Module (e.g. NIM 21, FIG. 2) could be replaced without rewriting any software other than that which directly drives it.
The LAN interconnection medium may be twisted-pair or coaxial cable. Two channels (logically, two distinct networks) may be provided for reliability and for increased throughput.
The LAN architecture is a logical ring, in which an electronic "token" is constantly passed from cell to cell at high speed. The current holder of the token may use it to send a "frame" of data or may pass it on to the next cell in the ring. The NIM only needs to know the logical address and status of its immediately succeeding neighbor. The NIM's responsibility is limited to detecting the failure of that neighbor or the inclusion of a new neighbor. In general, adjustment to failed or newly added cells is automatic.
The network interface maps directly into the processor's memory. Data exchange occurs through a dual-ported buffer pool which contains a linked list of pending "frames". Logical messages, which vary in length, are broken into fixed-size frames for transmission and are re-assembled by the receiving NIM. Frames are sequence-numbered for this purpose. If a frame is not acknowledged within a short period of time, it is retransmitted a number of times before being treated as a failure.
As described above with reference to FIG. 2, the LAN may be connected to other LAN's operating under the same LAN protocol via so-called "bridgeways", or it may be connected to other types of LAN's via "gateways".
Software Model
The computer operating system of the present invention operates upon processes, messages, and contexts, as such terms are defined hereinafter in the section entitled "Virtual Machine". This operating system offers the programmer a hardware abstraction, rather than a data or control abstraction.
Processes are referenced without regard to their physical location via a small set of message-passing primitives. Every process has both a unique system-generated identifier and a not necessarily unique name assigned by the programmer. The identifier provides quick direct access, while the name has a limited scope and provides symbolic, indirect access.
With reference to FIG. 3, an architectural model of the present invention is shown. The bottom, or hardware, layer 63 comprises a number of processors 71-76, as described above. The processors 71-76 may exist physically within one or more cells. The top, or software, layer 60 illustrates a number of processes P1-P10 which send messages m1-m6 to each other. The middle layer 61, labelled "virtual machine", isolates the hardware from the software, and it allows programs to be written as if they were going to be executed on a single processor. Conversely, programs can be distributed across multiple processors without having been explicitly designed for that purpose.
An important purpose of the virtual machine concept herein-disclosed is to provide the applications programmer with a simple, consistent model in which to design his system. This model, as mentioned above, is reduced to several elemental concepts: processes, messages, and contexts, each of which will be defined and discussed in detail below. As a consequence of this elemental model, hardware peculiarities are made transparent to the user, and changes in hardware configurations have no direct effect on the software.
The Virtual Machine
A "process" is a self-contained package of data and executable procedures which operate on that data. The data is totally private and cannot be accessed by other processes. There is no concept of shared memory within the present invention. Execution of a process is strictly sequential. Multiple processes execute concurrently and must be scheduled by the operating system. The processes can be re-entrant, in which case only one copy of the code is loaded even if multiple instances are active.
Every process has a unique "process identifier number" (PID) by which it can be referenced. The PID is assigned by the system when the process is created and remains in effect until the process terminates. The PID assignment contains a randomizing factor which guarantees that the PID will not be re-used in the near future. The contents of the PID are irrelevant to the programmer but are used by the virtual machine to physically locate the process. A PID may be thought of as a "pointer" to a process.
Every process also has a "name" which is a variable-length string of characters assigned by the programmer. A name need not be unique, and this ambiguity may be used to add new services transparently and to aid in fault-tolerance.
FIG. 4 illustrates that the system-wide name space is partitioned into distinct subsets by means of "contexts" identified by reference numerals 90-92. A context is simply a collection of related processes whose names are not known outside of the context. Context 90, for example, contains processes A, a, a, b, c, d, and e. Context 91 contains processes B, a, b, c, and f. And context 92 contains processes C, a, c, d, and x.
One particular process in each context, called the "context process", is known both within the context and within the immediately enclosing one (referred to as its "parent context"). In the example illustrated in FIG. 4, processes A-C are context processes for contexts 90-92, respectively. The parent context of context 91 is context 90, and the parent context of context 92 is context 91. Conceptually, the context process is located on the boundary of the context and acts as a gate into it.
Processes inside context 92 can reference any processes inside contexts 90 and 91 by name. However, processes in context 91 can only access processes in context 92 by going through the context process C. Processes in context 90 can only access processes in context 92 by going through context processes B and C.
The function of the context process is to filter incoming messages and either reject them or reroute them to other processes in its context. Contexts may be nested, allowing a hierarchy of abstractions to be constructed. A context must reside completely on one cell. The entire system is treated as an all-encompassing context which is always present and which is the highest level in the hierarchy. In enssence, contexts define localized protection domains and greatly reduce the chances of unintentional naming conflicts.
If appropriate, a process inside one context can be "connected" to one inside another context by exchanging PID's, once contact has been established through one or the other of the context processes. Most process servers within the present invention function that way. Initial access is by name. Once the desired function (such as a window or file) is "opened", the user process and the service communicate directly via PID's.
A "message" is a variable-length buffer (limited only by the processor's physical memory size) which carries information between processes. A header, inaccessible to the programmer, contains the destination name and the sender's PID. By convention, the first field in a message is a null-terminated string which defines the type of message (e.g., "read", "status", etc.) Messages are queued to the receiving process when they are sent. Queuing ensures serial access and is used in preference to semaphores, monitors, etc.
Messages provide the mechanism by which hardware transparency is achieved. A process located anywhere in the virtual machine can send a message to any other process if it knows its name. Transparency applies with some restrictions across bridgeways (i.e., the interfaces between LAN's operating under identical network protocols) and, in general, not at all across gateways (i.e., the interfaces between LAN's operating under different network protocols) due to performance degradation. However, they could so operate, depending upon the required level of performance.
With reference now to FIG. 5, the relationship of external events to processes will now be described. The virtual machine makes devices look like processes. For example, when an interrupt occurs in an external device 101, the virtual machine kernel 61 queues an interrupt message 103 to a specific process 104, known as an "external event service process" (EESP), functioning as the device manager. For efficiency, the message is pre-allocated once and circulates between the EESP and the kernel. The message contains just enough information to indicate the ocurrence of the event. The EESP performs all hardware-specific functions related to the event, such as setting control registers, moving data 105 to a user process 106, transmitting "Read" messages from the user process 106, etc., and then "releasing" the interrupt.
To become an EESP, a process issues a "connect" primitive specifying the appropriate device register(s). It must execute a "disconnect" before it exits. Device-independence is achieved by making the message protocol between EESP's and applications processes the same wherever possible.
Inter-Process Communication
All inter-process communication is via messages. Consequently, most of the virtual machine primitives are concerned with processing messages. The virtual machine kernel primitives are the following:
ALLOC--requests allocation of a (message) buffer of a given size.
FREE--requests deallocation of a given message buffer.
PUT--end a message to a given destination (by name or PID).
GET--wait for and dequeue the next incoming message, optionally from a specific process (by PID).
FORWARD--pass a received message through to another process.
CALL--send a message, then wait for and dequeue the reply.
REPLY--send a message to the originator of a given message.
ANY.sub.-- MSG--returns "true" if the receive queue is not empty, else returns "false"; optionally, checks if any messages from a specific PID are queued.
To further described the function of the kernel primitives, ALLOC handles all memory allocations. It returns a pointer to a buffer which can be used for local storage within the process or which can be sent to another process (via PUT, etc.). ALLOC never "fails", but rather waits until enough memory is freed to satisfy the request.
The PUT primitive queues a message to another process. The sending process resumes execution as soon as the message is queued.
FORWARD is used to quickly reroute a message but maintain information about the original sender (whereas PUT always makes the sending process the originator of the message).
REPLY sends a message to the originator of a previously received message, rather than by name or PID.
CALL essentially implements remote subroutine invocations, causing the caller to suspend until the receiver executes a REPLY. Subsequently, the replied message is dequeued out of sequence, immediately upon arrival, and the caller resumes execution.
The emphasis is on concurrency, so that as many processes as possible are executed in parallel. Hence neither PUT nor FORWARD waits for the message to be delivered. Conversely, GETS suspends a process until a message arrives and dequeues it in one operation. The ANY.sub.-- MSG primitive is provided so that a process may determine whether there is anything of interest in the queue before committing itself to a GET.
When a message is sent by name, the destination process must be found in the name space. The search path is determined by the nesting of the contexts in which the sending process resides. From a given process, a message can be sent to all processes in its own context or (optionally) to those in any higher context. Refer to FIG. 6. The contexts are searched from the current one upward until a match is found or until the system context is reached. All processes with the same name in that context are then queued a copy of the message.
For example, with reference to FIG. 6, assume that in context 141 process y sends a message to ALL processes by the name x. Process y first searches within its own context 141 but finds no process x. The process y searches within the next higher context 131 (its parent context) but again finds no process x. Then process y searches within the next higher context 110 and finds a process x, identified by reference numeral 112. Since it is the only process x in context 110, it is the only recipient of the message from process y.
If process a in context 131 sends a message to ALL processes by the name x, it first searches within its own context 131 and, finding no processes x there, it then searches within context 110 and finds process x.
Assume that process b in context 131 sends a message to ALL processes by the name A. It would find process A (111) in context 110, as well as process A (122) which is the context process for context 121.
A process may also send a message to itself or to its context process without knowing either name explicitly.
The concept of a "logical ring" (analogous to a LAN) allows a message to be sent to the NEXT process in the system with a given name. The message goes to exactly one process in the sender's context, if such a process exists. Otherwise the parent context is searched.
The virtual machine guarantees that each NEXT transmission will reach a different process and that eventually a transmission will be sent to the logically "first" process (the one that sent the original message) in the ring, completing the loop. In other words, all processes with the same name at the same level can communicate with each other without knowing how many there are or where they are located. The logical ring is essential for distributing services such as a data base. The ordering of processes in the ring is not predictable.
For example, if process a (125) in context 121 sends a message to process a using the NEXT primitive, the search finds a first process a (124) in the same context 121. Process a (124) is marked as having received the message, and then process a (124) sends the message on to the NEXT process a (123) in context 121. Process a (123) is marked as having received the message, and then it sends the message on to the NEXT process a, which is the original sender process a (125), which knows not to send it further on, since it's been marked as having already received the message.
Sending messages directly by PID obviates the need for a name search and ignores context boundaries. This is known as the DIRECT mode of transmission and is the most efficient. For example, process A (111) sends a message in the DIRECT mode to process y in context 141.
If a process sends a message in the LOCAL transmission mode, it sends it only to a process having the given name in the sender's own context.
In summary, including the DIRECT transmission mode, there are five transmission modes which can be used with the PUT, FORWARD, and CALL primitives:
ALL--to all processes with the given name in the first context which contains that name, starting with the sender's context and searching upwards through all parent contexts.
LOCAL--to all processes with the given name in the sender's context only.
NEXT--to the next process with the given name in the same context as the sender, if any; otherwise it searches upwards through all parent contexts until the name is found.
LEVEL--sends to "self" (the sending process) or to "context" (the context process corresponding to the sender's context); "self" cannot be used with CALL primitive.
DIRECT--sent by PID.
Messages are usually transmitted by queueing a pointer to the buffer containing the message. A message is only copied when there are multiple destinations or when the destination is on another cell.
Operating System
The operating system of the present invention consists of a kernel, which implements the primitives described above, plus a set of processes which provide process creation and termination, time management (set time, set alarm, etc.) and which perform cell start-up and configuration. Drivers for devices are also implemented as processes (EESP's), as described above. This allows both system services and device drivers to be added or replaced easily. The operating system also supports swapping and paging, although both are invisible to applications software.
Unlike known distributed computer systems, that of the present invention does not use a distinct "name server" process to resolve names. Name searching is confined to the kernel, which has the advantage of being much faster.
A minimal bootstrap program resides permanently (in ROM) on every cell, e.g. ROM 28 in cell N of FIG. 2. The bootstrap program executes automatically when a cell is powered up and begins by performing basic on-board diagnostics. It then attempts to find and start an initial system code module which comprises the entire kernel, and EESP's for the clock, disk (if required), and NIM (if required). The module is sought on the first disk drive on the cell, if any. If there isn't a disk, and the cell is on the LAN, a message will be sent out requesting the module. Failing that, the required software must be resident in ROM. System services for the clock and for process creation, an initialization program, and a minimal file system, are also built into the module. The initialization program sets up all of the kernel's internal tables and then calls predefined entry points in each of the preloaded services (file management, etc.). The net result is that EESP's for the attached devices are scheduled to run, and the cell is available.
In general, there exists a template file describing the initial software and hardware for each cell in the system. The template defines a set of initial processes (usually one per service) which are scheduled immediately after the cell start-up. These processes then start up their respective subsystems. A cell configuration service on each cell sends configuration messages to each subsystem when it is being initialized, informing it of the devices it owns. Thereafter, similar messages are sent whenever a new device is added to the cell or a device fails or is removed from the cell.
Thus there is no well-defined meaning for "system up" or "system down"--as long as any cell is active, the system as a whole may be considered to be "up". Cells can be shut down or started up dynamically without affecting other cells on the network. The same principle applies, in a limited sense, to peripherals. Devices which can identify themselves with regard to type, model number, etc. can be added or removed without operator intervention. The operating system cannot maintain a global status of the system, nor does it attempt to centralize control of the entire system.
Data Management
The present invention allows the user to store and retrieve data at several levels of abstraction. At various levels it provides device-independence, transparency, multiple views of the same data and support for transaction processing. Transparency means that a process need not know where a file is stored in order to access it. It also means that the file can be moved to another device without affecting the process. Only as many levels as are required for a particular application need be included in the system.
Referring now to FIG. 7, the lowest level of data management is the physical disk layer 153, which is completely hidden from all applications software 155. Immediately above this level are virtual disks 152 which define an interface in terms of linear arrays of 1K blocks, regardless of the actual medium. Although the usual medium is disk, RAM may also be used (for temporary files) to improve performance. Three types of messages are supported at this level: "initial", to format the virtual disk, and "read" and "write" to access specific blocks.
The third level, disk management 151, organizes data within a virtual disk by means of indices. A disk index is a file at this level and is viewed as an extensible linear array of bytes. Messages are accepted to initialize the disk, allocate and delete indices, and read and write indices. The later two functions operate starting at a given byte offset for a given byte length. An index is automatically extended when a request references a location outside the current limits. Physical storage is allocated only when data is actually written. Optional data caching is supported at the disk management level on a per cell basis.
File management 150 is layered on top of disk management 151 and introduces the concept of a "file system". A file system is a collection of named files (or named indices, in terms of the disk management layer 151). The name space constitutes a flat (single-level) directory which is allocated when the file system is initialized. A name may be up to 64 characters long and is hashed into the directory. Unnamed files are useful for building complex disk structures which are logically linked to each other, such as a hierarchical file directory or a database, or for temporary files which only the creator will use.
Transparency is supported only at the file management level 150 and above. It is used by simply omitting the file system name from the request (NEW, DELETE, RENAME, or OPEN). In this case, the request is forwarded through all file systems until the given file name is found.
The highest level 154 of data management deals in terms of "metaphors", which implement application-specific views of the data. A relational database is one example of a metaphor. Complex operations such as multi-user synchronization and record- or field-locking may be implemented at this level. The present invention supports two built-in views of the data: "plain" files, which are superficially equivalent to UNIX.TM. files, and a relational database.
FIG. 8 illustrates the design of the data management software up to the plain-file level. Each active (mounted) file system 165 is represented by a file management context 160. The set of all such contexts forms a logical ring for purposes of message transmission; in other words, they all have the same name ("file.sub.-- mgt"). The actual name of the file system (stored on the disk 166 at initialization) is known only to the context process.
In the plain-file metaphor, there is exactly one process for each open file, acting as a server for that file. That process (an instance of "fil.sub.-- access") can be located in the appropriate file management context, or any application can create its own private copy of the process. The process allows standard file management functions (NEW, DELETE, RENAME, OPEN, and CLOSE) plus SEEK, LOCK (lock the entire file against access by processes other than the owner) and UNLOCK. Note that a given file process is only opened once, by its owner. If not locked, any other processes which know its name or PID can read and write the file. Protection is provided through normal process name-scoping. Protection via passwords or a similar mechanism are in general unsupported unless supported by another metaphor.
Human Interface
The human interface (HI) of the present invention provides a set of tools with which an end user can construct a package specific to his applications requirements. Such a package is referred to as a "metaphor", since it reflects the user's particular view of the system. Multiple metaphors can be supported concurrently. One representative metaphor is, for example, a software development environment.
The purpose of the HI metaphor is to allow consistent, integrated access to the data and functions available in the system. Since user's perceptions of the system are based largely on the way they interact with it, it is important to provide an interface with which they feel comfortable. The HI allows a systems designer to create a model consisting of objects that are familiar to the end user and a set of actions that can be applied to them.
The fundamental concept of the HI is that of the "picture". All visually-oriented information, regardless of interpretation, is represented by pictures. A picture (such as a diagram, report, menu, icon, etc.) is defined in a device-independent format which is recognized and manipulated by all programs in the HI and all programs using the HI. It consists of "picture elements", such as "line", "arc", and "text", which can be stored compactly and transferred efficiently between processes. All elements have common attributes like color and fill pattern. Most also have type-specific attributes, such as typeface and style for text. Pictures are drawn in a large "world" co-ordinate system composed of "virtual pixels".
Because all data is in the form of pictures, segments of data can be freely copied between applications, e.g., from a live display to a word processor. No intermediate format or conversion is required. One consequence of this is that the end user or original equipment manufacturer (OEM) has complete flexibility in defining the formats of windows, menus, icons, error messages, help pages, etc. All such pictures are stored in a library rather than being built into the software and so are changeable at any time without reprogramming. A comprehensive editor is available to define and modify pictures on-line.
All interaction with the user's environment is through either "virtual input" or "virtual output" devices. A virtual input device accepts keyboards, mice, light pens, analog dials, pushbuttons, etc. and translates them into text, cursor-positioning, action, dial, switch, and number messages. All physical input devices must map into this set of standard messages. Only one process, an input manager for the specific device, is responsible for performing the translation. Other processes can then deal with the input without being dependent on its source.
Similarly, a virtual output manager translates standard output messages to the physical representation appropriate to a specific device (screen, printer, plotter, etc.) A picture drawn on any terminal or by a process can be displayed or printed on any device, subject to the physical limitations of that device.
With reference to FIG. 9, two "pictures" are illustrated--picture A (170) and picture B (174).
The concept of a "view" is used to map a particular rectangular area of a picture to a particular device. In FIG. 9, picture A is illustrated as containing at least one view 171, and picture B contains at least one view 175. Views can be used, for example, to partition a screen for multiple applications or to extract page-sized subsets of a picture for printing.
If the view appears on a screen it is contained in a "window". With reference again to FIG. 9, view 171 of picture A is mapped to screen 176 as window 177, and view 175 of picture B is mapped as window 178.
The HI allows the user to dynamically change the size of the window, move the window around on the screen, and move the picture under the window to view different parts of it (i.e., scroll in any direction). If a picture which is mapped to one or more windows changes, all affected views of that picture on all screens are automatically updated. There is no logical limit to the number or sizes of windows on a particular screen. Since the system is distributed, it's natural for pictures and windows to be on different cells. For example, several alarm displays can share a single, common picture.
The primary mechanism for interacting with the HI is to move the cursor to the desired object and "select" it by pressing a key or button. An action may be performed automatically upon selection or by further interaction, often using menus. For example, selecting an icon usually activates the corresponding application immediately. Selecting a piece of text is often followed by selection of a command such as "cut" or "underline". Actions can be dynamically mapped to function keys on a keyboard so that pressing a key is equivalent to selecting an icon or a menu item. A given set of cursors (the cursor changes as it moves from one application picture to another), windows, menus, icons, and function keys define a "metaphor".
The HI builds on the above concepts to provide a set of distributed services. These include electronic mail, which allows two or more users at different terminals to communicate with each other in real time or to queue files for later delivery, and a forms manager for data entry. A subclass of windows called "virtual terminals" provides emulation of standard commercially available terminals.
FIG. 10 shows the different levels of the HI and data flow through them. Arrows 201-209 indicate the most common paths, while arrows 210-213 indicate additional paths. The interface can be configured to leave out unneeded layers for customized applications. The philosophy behind the HI design dictates one process per object. That is, a process is created for each active window, picture, input or output device, etc. As a result, the processes are simplified and can be distributed across cells almost arbitrarily.
Error Management
An error management service is provided to catch errors and report them to the appropriate process(es). It serves as a foundation upon which more sophisticated diagnostics and/or recovery schemes may be constructed. The system can intercept processor internal exceptions (bus and address errors, "trap" instructions, etc.), external exceptions (such as a spurious interrupts), device faults, and software-defined errors. The latter category is open-ended and comprises unexpected termination of a process, the result of a diagnostic program, or in general any error detected by the kernel or by any process. Failure to find the destination of a transmitted message is one example. While internal exceptions can be associated with the particular process which caused the error, external exceptions are independent, although they may directly impact one or more processes.
In summary, the prime functions of the error management service are to: (1) classify and log errors, (2) generate notification messages, (3) accept requests to configure the service and specify options, (4) accept software error messages from other subsystems, and (5) terminate affected processes, if required. Item (3) above allows applications and services to indicate that they want to know about specific errors or classes of errors. Options include automatic logging, automatic display on the operator's terminal, automatic suspension (for debugging) or abortion of the offending process, and automatic dumping of the process image to a file. The default actions, if no options have been specified, are termination, logging and display. Any outstanding request can be cancelled at any time.
The HI logging service provides the facility to store error messages in a chronological file, maintain a hard-copy log, and create a dynamic display of errors, ordered by time, priority, class, etc. The debugger is often invoked upon occurrence of a process error to examine the process' state for clues.
DETAILED DESCRIPTION OF THE INVENTION
Referring now to FIG. 11, a block diagram is shown of a logical ring of file systems, illustrating how an access request to a file system is handled by the present invention. Each mounted disk volume in the distributed data processing system of the present invention constitutes a file system. Each file system is managed by a file management context whose architecture is represented by FIG. 8. On a relatively large system there may be any number of active file systems (i.e. active file management contexts), where each file management context has the name "file.sub.-- mgt". The set of these contexts is connected together in a logical ring, as shown in FIG. 11.
The name of file system is established when a disk volume is initialized. The file system name is written into the volume header on the disk. When a file management context starts up, it attempts to read the volume header of its associated disk. If successful, the volume name is read and becomes the name of the file system which that context manages. If unsuccessful, the volume is marked as uninitialized. Thereafter only an INITIAL command is accepted.
Within a file management context, requests which reference a file by name (NEW, DELETE, RENAME, OPEN, and CLOSE) are sent to the context process "file.sub.-- mgt". Requests which access data (READ and WRITE) are sent directly by their PID to the disk.sub.-- mgt process within the file management context. This PID, as well as the associated disk index, is returned in the reply to a successful NEW or OPEN command. This connects the user (e.g., a data management process) to a specific file allocation on a specific volume.
As shown in FIG. 11, all active file management contexts are viewed as forming a logical ring. Requests referencing a file by name are sent to the context process named "file.sub.-- mgt" using transmission mode NEXT. Each context process "file.sub.-- mgt" determines whether the request is for the file system which it manages, and, if it is not, it forwards the request to the next context "file.sub.-- mgt". If a request circulates the logical ring without success, then it is returned to the caller with an error indication.
In FIG. 11, assume that a user 300 (e.g. an application context) initiates a file access request to a certain "TEMP" file in file system "G" 306. The file access request is first received by the "file.sub.-- mgt" context process of file system "B" 302, which determines that the request is not for file system "B" and forwards it to file system "S" 304. Likewise, file system "S" 304 forwards the request on to file system "G" 306. The "file.sub.-- mgt" context process of file system "G" 306 recognizes that the request is intended for this file system and then responds to user 300 that it will attempt to satisfy the request.
Had the file access request circulated the entire loop without success, it would have returned to user 300 with an error message. To prevent the request from recirculating the loop, once a given file system (e.g. file system "B" 302) fails to satisfy the request, it records an indication that it has attempted to satisfy this particular request, so that it doesn't reattempt to satisfy the request on any wrap-around.
A file access request may either specify both a file system name and a file name, or it may simply specify a file name. Data residence transparency is achieved by not specifying the file system name. Suppose, for example, that user 300 doesn't know on which file system a desired file is located or doesn't care where a file is to be opened. In this case, an attempt is made by each successive "file.sub.-- mgt" context to satisfy the request of user 300. Thus the set of all disk volumes in the system may be considered one large disk space, and the user doesn't have to know on which file system any given file is logically or physically located.
For example, assume user 300 initiates a file access request to a file "ABC" without specifying the file system name. File system "B" 302 will first attempt to satisfy the request. However, if it's unable to, e.g. because of insufficient space, it forwards the request on to file system "S" 304. If file system "S" 304 is capable of satisfying the request, it so notifies user 300. Otherwise, the request continues on to each file system in turn until one is able to satisfy the request. If none is able to satisfy the request, an error message is returned to user 300. As mentioned above, once a file system fails to satisfy the request, it marks the attempt, so that it doesn't attempt to satisfy the request if the request circulates around the entire loop without being satisfied.
The flow diagram of FIG. 12 illustrates how a file access request is handled by the present invention. A file access request is received in block 320. Decision block 321 queries whether this is a wrap-around. If so, an error message is sent to the user, as indicated by block 322. If not, the procedure passes to decision block 323, which queries whether a file system has been specified. If not, this particular file system attempts to satisfy the request, as indicated by block 325. If so, decision block 324 queries whether this particular file system is the one specified. If so, this particular file system attempts to satisfy the request.
If this is not the file system specified, then the request is marked for wrap-around, as shown by block 328, and the request is forwarded to the next file system, as shown by block 329.
If the request can be satisfied (block 326), then the user is so informed (block 327). If not, decision block 330 queries whether a file system was specified. If so, an error message is sent to the user, as indicated by block 331. If not, the request is marked for wrap-around (block 328), and the request is forwarded to the next file system (block 329).
Appendix A contains a "C" language implementation of the flow diagram shown in FIG. 12.
Appendix B is a detailed description of the relevant portions of the source code listing of Appendix A.
It will be apparent to those skilled in the art that the herein disclosed invention may be modified in numerous ways and may assume many embodiments other than the preferred form specifically set out and described above. For example, a file system may obviously occupy some other physical device, or portion or grouping thereof, other than a disk volume, as disclosed above.
Accordingly, it is intended by the appended claims to cover all modifications of the invention which fall within the true spirit and scope of the invention. ##SPC1##
Claims
What is claimed is:
1. A method of providing file system access in a data management system used in a data processing system comprising at least one processor, at least one memory storage unit coupled to said at least one processor, and a plurality of individual file systems and a requesting process contained in said at least one memory storage unit, said method comprising the steps of: (a) generating an access request by said requesting process for a file having a given file name in one of said file systems having a given file system name, said access request specifying said file name and said file system name; (b) transmitting said access request to one of said file systems; (c) determining whether said file system has said specified file system name, and, if so, proceeding with step (e), but if not, automatically forwarding said access request to a different file system; (d) repeating step (c) until either said file system with said specified file system name is located, in which case proceeding with step (e), or until said access request has been received by all of said file systems without locating said file system with said specified file system name and in such case generating an indication of an unsuccessful access to said file to said requesting process; and (e) determining whether said access request can be satisfied by said file system with said specified file system name, and, if so, satisfying said access request and generating an indication thereof directly to said requesting process, but if not, generating an indication of an unsuccessful access to said file to said requesting process.
2. The method of providing file system access recited in claim 1, wherein in steps (b) and (c) said access request is always forwarded to said file systems in a predetermined order.
3. A method of providing file system access in a data management system used in a data processing system comprising a plurality of processors interconnected by a network, a plurality of memory storage units, each processor being coupled to at least one memory storage unit, and a plurality of individual file systems and a requesting process contained in at least one memory storage unit, said method comprising the steps of: (a) generating an access request by said requesting process for a file having a given file name in one of said file systems having a given file system name, said access request specifying said file name and said file system name; (b) transmitting said access request to one of said file systems; (c) determining whether said file system has said specified file system name, and, if so, proceeding with step (e), but if not, automatically forwarding said access request to a different file system; (d) repeating step (c) until either said file system with said specified file system name is located, in which case proceeding with step (e), or until said access request has been received by all of said file systems without locating said file system with said specified file system name and in such case generating an indication of an unsuccessful access to said file to said requesting process; and (e) determining whether said access request can be satisfied by said file system with said specified file system name, and, if so, satisfying said access request and generating an indication thereof directly to said requesting process, but if not, generating an indication of an unsuccessful access to said file to said requesting process.
4. The method of providing file system access recited in claim 3, wherein in steps (b) and (c) said access request is forward to said file systems in a predetermined order.
5. A data management system for use in a data processing system comprising: at least one processor for executing instructions; at least one memory storage unit coupled to said at least one processor, said memory storage unit storing instructions and data; a plurality of individual file systems contained in said at least one memory storage unit; means responsive to the execution of an instruction by said at least one processor for generating an access request for a file having a given file name in at least one of said file systems having a specified file system name, said access request specifying said file name and said file system name; means responsive to said access request generating means for transmitting said access request to one of said file systems; first means responsive to the receipt of said access request for determining whether said one file system has said specified file system name, and, if so, generating a first control signal, but if not, generating a second control signal; second means responsive to said first control signal for determining whether said access request can be satisfied by said file system having said specified file system name, and, if so, for satisfying said access request and generating a first indication of a successful access to said file directly to said at least one processor, and, if not, for generating a second indication of an unsuccessful access to said file; third means responsive to said access request generating means, to said second control signal, and to said second indication for automatically forwarding said access request to successive, different file systems whereby: (a) if said access request is forwarded to a file system having said specified file system name, said first control signal is generated by said first means, in which case said second means either generates said first indication or said second indication, depending upon whether said file is successfully or unsuccessfully accessed, respectively, and (b) if said access request is forwarded to a file system not having said specified file system name, said first means generates said second control signal, said third means ceasing to forward said access request after all of said file systems have been unsuccessful accessed and generating a third indication of an unsuccessfully access to said file directly to said at least one processor.
6. The data management system recited in claim 5, and further comprising means responsive to said access request generating means and to said access request forwarding means for forwarding said access request to said file systems in a predetermined pattern.
7. A data management system for use in a data processing system comprising: a plurality of processors for executing instructions, said processors being interconnected by a network; a plurality of memory storage units, each said processor being coupled to at least one of said memory storage units, said memory storage units storing instructions and data; a plurality of individual file systems contained in at least one of said memory storage units; means responsive to the execution of an instruction by one of said processors for generating an access request for a file having a given file name in at least one of said file systems having a specified file system name, said access request specifying said file name and said file system name; means responsive to said access request generating means for transmitting said access request to one of said file systems; first means responsive to the receipt of said access request for determining whether said one file system has said specified file system name, and, if so, generating a first control signal, but if not, generating a second control signal; second means responsive to said first control signal for determining whether said access request can be satisfied by said file system having said specified file system name, and, if so, for satisfying said access request and generating a first indication of a successful access to said file directly to said one of said processors, and, if not, for generating a second indication of an unsuccessful access to said file; third means responsive to said access request generating means, to said second control signal, and to said second indication for automatically forwarding said access request to successive, different file systems whereby: (a) if said access request is forwarded to a file system having said specified file system name, said first control signal is generated by said first means, in which case said second means either generates said first indication or said second indication, depending upon whether said file is successfully or unsucessfully accessed, respectively, and (b) if said access request is forwarded to a file system not having said specified file system name, said first means generates said second control signal, said third means ceasing to forward said access request after all of said file systems have been unsuccessful accessed and generating a third indication of an unsuccessfully access to said file directly to said one of said processors.
8. The data management system recited in claim 7, and further comprising means responsive to said access request generating means and to said access request forwarding means for forwarding said access request to said file systems in a predetermined pattern.
Patent Citations (11)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4366479 | 1982-12-01 | Mori et al. | |
| US4477881 | 1984-10-01 | Kobayashi et al. | |
| US4510492 | 1985-04-01 | Mori et al. | |
| US4543630 | 1985-09-01 | Neches | |
| US4590468 | 1986-05-01 | Stieglitz | |
| US4612541 | 1986-09-01 | Ohnishi | |
| US4644468 | 1987-02-01 | Doster et al. | |
| US4644470 | 1987-02-01 | Feigenbaum et al. | |
| US4649535 | 1987-03-01 | Ulug | |
| US4682326 | 1987-07-01 | Ulug | |
| US4698629 | 1987-10-01 | Mori et al. |
Non-Patent Literature (3)
- Ebrahimi et al. "File Name Mapping Method Permitting Network Location Transparency", IBM TDB vol. 26, No. 7B, Dec. 1983, pp. 3791-3794.
- IEE Proceedings, vol. 131, No. 2 Part E, Section A-I, Mar. 1984, pp. 38-44, Old Woking, Surrey, G.B., R. Hull et al., "Virtual Resource Ring".
- The 1st Int'l Conf. on Computer Communication, Washington, 24th-26th Oct. 1972, pp. 364-370, A.C.M., N.Y., D. J. Farber et al., "The Structure of a Distributed Computer System".