Browse Prior Art Database

Adaptive Data Recovery Process

IP.com Disclosure Number: IPCOM000117147D
Original Publication Date: 1995-Jun-01
Included in the Prior Art Database: 2005-Mar-31
Document File: 2 page(s) / 60K

Publishing Venue

IBM

Related People

Chiang, GM: AUTHOR [+6]

Abstract

This DASD subsystem Adaptive Data Recovery Process cuts down much on design, implementation and test cycle when data check recovery procedure require changes especially close to the end of the development cycle. At that time most of the programming will have been completed and changes can be very disruptive to the overall program. This table contains a certain number of entries. Each entry corresponds to a retry or read step. Each entry has four words (eight bytes), which are defined below.

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

Adaptive Data Recovery Process

      This DASD subsystem Adaptive Data Recovery Process cuts down
much on design, implementation and test cycle when data check
recovery procedure require changes especially close to the end of the
development cycle.  At that time most of the programming will have
been completed and changes can be very disruptive to the overall
program.  This table contains a certain number of entries.  Each
entry corresponds to a retry or read step.  Each entry has four words
(eight bytes), which are defined below.

      The Control Table approach is used.  Each entry of the Control
Table is just like a line of executable instruction of a software
program except that it is customized to execute specially defined
functions.  To change the DASD Data Recovery Procedure is just like
writing a patch to the "Control Table Program" or can even create a
new instruction for the "Control Table Language" which may cause the
execution of newly defined subroutine functions.

      The control table can have a varied number of entries.  Each
entry represents a step in the retry process.  The content of each
entry controls the functions to be performed in this retry step.
There are basically two categories of functions performed by each
retry step.  They are:
  o  Process function - action to be performed on the current retry
      step, and
  o  Conditional function - action to be taken depends on the outcome
      of some test conditio...