Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

On-Site ROS Patch Mechanism

IP.com Disclosure Number: IPCOM000040208D
Original Publication Date: 1987-Oct-01
Included in the Prior Art Database: 2005-Feb-02
Document File: 3 page(s) / 68K

Publishing Venue

IBM

Related People

Inomata, T: AUTHOR [+3]

Abstract

This article describes the patch mechanism on the microcode stores in ROS (read-only storage) of the machine to fix the microcode problem promptly, at the customer's location in the subsystem which has the down-load capability from the controller/file-server to the machine and the up-store capability from the machine to the controller/file-server. As shown in Fig. 1, the On-Site ROS Patch Utility is used in the machine to perform the On-Site ROS Patch Mechanism, and the CE (Customer Engineer) can fix the field problem on the microcode at the customer's location. The field incident is reported to the microcode maintenance department, the cause is analyzed, and then the resolution is tested.

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 55% of the total text.

Page 1 of 3

On-Site ROS Patch Mechanism

This article describes the patch mechanism on the microcode stores in ROS (read-only storage) of the machine to fix the microcode problem promptly, at the customer's location in the subsystem which has the down-load capability from the controller/file-server to the machine and the up-store capability from the machine to the controller/file-server. As shown in Fig. 1, the On-Site ROS Patch Utility is used in the machine to perform the On-Site ROS Patch Mechanism, and the CE (Customer Engineer) can fix the field problem on the microcode at the customer's location. The field incident is reported to the microcode maintenance department, the cause is analyzed, and then the resolution is tested. After the effect of the resolution is verified, the information is conveyed to the CE, and then the CE attempts to put the patch at the customer's location. The On-Site ROS Patch Mechanism requires the following resources/ tools.

(Image Omitted)

- On-Site ROS Patch Utility which enables the CE to enter the patch information into the machine - File structure which enables down-load and up-store - Transfer Vector Table which lists all entry addresses of microcode modules. Branch, call are done via this table. - RAM (random-access memory) space where the defective microcode module can be copied - Non-volatile storage (diskette) to save the patch information (file) in the controller/file-server with the down-load and

up-store capability After the CE puts the patch into the panel of the On-Site ROS Patch Utility, a file which contains the following information is created, and then the patch file is up-stored...