Browse Prior Art Database

Patch Mechanism Using Non-Volatile Memory

IP.com Disclosure Number: IPCOM000034766D
Original Publication Date: 1989-Apr-01
Included in the Prior Art Database: 2005-Jan-27
Document File: 4 page(s) / 125K

Publishing Venue

IBM

Related People

Inomata, T: AUTHOR [+3]

Abstract

This article describes the patch mechanism using NVM (Non-Volatile Memory). There are some display terminals called DFTs (Distributed Function Terminals) whose objects are stored in the controller's diskette and are down loaded into the memory of the device when it is powered on. And, these devices can have the patch data in the controller's diskette. (Image Omitted) This article shows how to control the patch data for a DCA (Device Cluster Adapter) terminal which has NVM on it but cannot have its object in the controller's diskette. This patch mechanism uses the patch data transaction function between the device and the controller.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 54% of the total text.

Page 1 of 4

Patch Mechanism Using Non-Volatile Memory

This article describes the patch mechanism using NVM (Non-Volatile Memory). There are some display terminals called DFTs (Distributed Function Terminals) whose objects are stored in the controller's diskette and are down loaded into the memory of the device when it is powered on. And, these devices can have the patch data in the controller's diskette.

(Image Omitted)

This article shows how to control the patch data for a DCA (Device Cluster Adapter) terminal which has NVM on it but cannot have its object in the controller's diskette. This patch mechanism uses the patch data transaction function between the device and the controller. When this device is attached to the controller which does not have the capability to send the patch data to the device, the patch data is inputted from the keyboard and stored into NVM and its patch data is applied at the next POR (Power-On Reset) of the device, as shown in Fig. 1. On the other hand, when this device is attached to the controller which has the capability to send the patch data to the device, there are two ways to store a patch data in NVM. One is to input from the keyboard, and the other is to down load it from the controller's diskette. For the former case, when the new patch data is added or old patch data is deleted, the updated patch data is up-stored onto the controller's diskette, and the same patch data is distributed to all devices attached to that controller, as shown in Figs. 2 and 3. For the latter case, when the new controller's diskette with new patch data is released, its patch data is distribu...