Browse Prior Art Database

Processor to Processor Initial Program Load

IP.com Disclosure Number: IPCOM000107150D
Original Publication Date: 1992-Jan-01
Included in the Prior Art Database: 2005-Mar-21
Document File: 1 page(s) / 54K

Publishing Venue

IBM

Related People

Chavez, EA: AUTHOR [+4]

Abstract

This article describes a system for providing initial program load (IPL) capability for processor cards not having fixed disks, from other processor cards on the same bus which have locally attached fixed disks. By not requiring a fixed disk assembly for each processor, system complexity and system cost are reduced.

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

Processor to Processor Initial Program Load

       This article describes a system for providing initial
program load (IPL) capability for processor cards not having fixed
disks, from other processor cards on the same bus which have locally
attached fixed disks. By not requiring a fixed disk assembly for each
processor, system complexity and system cost are reduced.

      The system is configured with two or more CPU boards. Each CPU
board contains its own 80386 microprocessor and local bus.  One of
the CPU boards is dedicated to handling network communications.  The
other processor cards handle all local application processing.

      In an operational scenario, the processing element with a
locally attached fixed disk is IPLed just as it would be in a
personal computer.  The firmware finds the local fixed disk and
brings in the Operating System. After the Operating System is loaded,
the remote IPL (RIPL) server program is executed.  The RIPL Server
broadcasts a "Server Available" Message on the bus.  This indicates
to the processors requiring IPL, that the server is ready to handle
their requests.  The requesters or RIPL Clients then send an "IPL
request" to get their respective boot sectors.

      The RIPL client processors execute the same firmware during
boot- up as the servers.  The path of the client diverges from that
of the server when the client processor cannot find a locally
attached fixed disk device.  At this point the RIPL firmware...