Browse Prior Art Database

Automatic Driver Integration Process

IP.com Disclosure Number: IPCOM000079087D
Original Publication Date: 1973-May-01
Included in the Prior Art Database: 2005-Feb-26
Document File: 2 page(s) / 13K

Publishing Venue

IBM

Related People

Wallach, JR: AUTHOR [+2]

Abstract

Systems integrations are performed more quickly and more accurately by automating the clerical aspects of the process, eliminating much need for specific, specialized knowledge, and providing a detailed history of the integration. Automatic Driver Integration Process (ADIP) does this.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 2

Automatic Driver Integration Process

Systems integrations are performed more quickly and more accurately by automating the clerical aspects of the process, eliminating much need for specific, specialized knowledge, and providing a detailed history of the integration. Automatic Driver Integration Process (ADIP) does this.

The preparation routines of ADIP are run to create two data sets; the Control Section (CSECT) Index contains a list of all the load modules in which each of many object modules are found, and the Link-Edit Image data set consists of 80- byte control statements needed to Link-Edit the load modules into their respective target libraries.

An ADIP Monitor is used as a root segment to link to the various programs that perform all of the ADIP functions.

The Automatic Link-Edit program (ALE) LINKs or COPYs object decks or modules into every load module in which they occur. ALE either reads the object module names from the object decks or, if the module is on a distribution library, prompts the operator for module name and input device. ALE uses the two previously-mentioned data sets and creates an Untested Function File.

The Test Bucket data set is a Partition Data Set (PDS) containing sets of test cases to be used for unit or regression testing. The test case sets, or "buckets", are executed by starting, from the console, an OS/VSI reader or the desired PDS member.

If, as a result of the testing, an error is noted in an object module, then the Automatic SuperZap program (ASZ) may be used to pl...