Browse Prior Art Database

Alternate Method to Initial Program Load an Operating System

IP.com Disclosure Number: IPCOM000081101D
Original Publication Date: 1974-Apr-01
Included in the Prior Art Database: 2005-Feb-27
Document File: 2 page(s) / 56K

Publishing Venue

IBM

Related People

De Jonge, RL: AUTHOR [+2]

Abstract

An alternate method to Initial Program Load (IPL) an operating system is referred to as "FASTNIP" The IPL must run disabled of Input/Output (I/O) interrupts, until the Nucleus Initialization Program (NIP) is capable of handling them. The depressing of the enter and/or request key on the master console must be capable of setting the attention bit in the channel status word (CSW).

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

Page 1 of 2

Alternate Method to Initial Program Load an Operating System

An alternate method to Initial Program Load (IPL) an operating system is referred to as "FASTNIP" The IPL must run disabled of Input/Output (I/O) interrupts, until the Nucleus Initialization Program (NIP) is capable of handling them. The depressing of the enter and/or request key on the master console must be capable of setting the attention bit in the channel status word (CSW).

Conventionally operating systems are designed in such a way to allow IPL flexibility to meet must user needs. Once the user has determined his IPL needs, the IPL procedure is set and is rarely deviated from. However, even with this set procedure, the operator has the redundant task to read and respond to specific IPL messages each time the system is IPLed.

To avoid this IPL redundancy, FASTNIP was implemented to provide an alternate method to IPL the operating system. The alternate method is faster and easier because the operating system recognizes the selected options, thus unnecessary operator responses are not required.

The operator may invoke the alternate method by simply pressing the request and/or the enter key on the master console after the IPL procedure has been started. I/O interrupts remain pending during IPL/NIP time until NIP's I/O interrupt handler is initialized, at which time the I/O interrupts are allowed to be processed. The CSW's are then checked for the attention; if on, the device address is saved for later...