Introduction to z/OS Basics

Chapter 16B: The IPL process

© 2006 IBM Corporation

 Chapter 16B The IPL Process

Objectives

 In this chapter you will learn:

– About the IPL process
– Why a system would be closed down and reloaded
– About extended up time for z/OS systems

© 2006 IBM Corporation

2
 Chapter 16B The IPL Process

Overview

 IPL is “booting” the system

 The address of the IPL volume and the IODF
volume are required

© 2006 IBM Corporation

3
 Chapter 16B The IPL Process

IPLing the machine

IPL IPL ccuu

bootstrap
IPLtext

ISYSRES

LOADPARM
Alt
IODF ccuu LOADxx IMSI
Nuc
1-4 5-6 7 8

© 2006 IBM Corporation

4
 Chapter 16B The IPL Process

Initialization functions

 When the operator supplies the parameters and

tells the system to load the following happens:
– The bootstrap code on the IPL volume is loaded into
storage at address 0 and control passed to it
– The bootstrap the reads the IPLTEXT program IEAIPL00
which is given control and the complex task of loading the
system starts

© 2006 IBM Corporation

5
 Chapter 16B The IPL Process

IEAIPL00

 IEAIPL00 prepares the system by clearing central

storage to zeroes then defines storage areas for
the master scheduler
 SYS1.NUCLEUS is located and a series of
modules loaded which construct the normal
environment of control blocks and subsystems
 The first part of the Nucleus Initialization Program
is then loaded

© 2006 IBM Corporation

6
 Chapter 16B The IPL Process

Nucleus Initialization Program (NIP)

 NIP sets up
– SQA
– PLPA
– FLPA
– MLPA
– the common service area CSA
– And starts the master scheduler

© 2006 IBM Corporation

7
 Chapter 16B The IPL Process

Master scheduler

 The master address space starts all the other

required address space and initializes the
subsystems
 Once JES is ready jobs can be started and VTAM
and TSO will be started next.
 The system is now available to do work

© 2006 IBM Corporation

8
 Chapter 16B The IPL Process

Virtual Storage Layout for Multiple Address Spaces

Started Tasks

*
M P R T C C A V L S J V C T T I
A C A R A O L L L M E T I S S N
S
T
A
U
S
P
A
C ... T
A
N
S
L
O
F A S S A
M
C
S
O O I
T
E T E L O C U /
R H O L A S J
* G E S E O
R B

TSO Batch
LOGON Job
System and
Subsystem
Address Spaces

© 2006 IBM Corporation

9
 Chapter 16B The IPL Process

Address spaces

 Many address spaces are created before JES and

these each have special tasks
 Each address space by default is allowed 2GB of
virtual space
 The private region below the 16MB line is usually
around 10MB after the common area has been
allowed for, depending on system set up and the
size of installation modules in the LPA

© 2006 IBM Corporation

10
 Chapter 16B The IPL Process

The 31-bit address space

ELSQA/ESWA/229/230/249
Extended Extended User Region
Private

Extended CSA

Extended
Extended PLPA/FLPA/MLPA
Common
Extended SQA
Extended Nucleus
16 MB
Nucleus
SQA
Common PLPA/FLPA/MLPA
CSA 16M
LSQA/SWA/229/230/249

User Region

Private
20KB
System Region
4KB
Common PSA 0
© 2006 IBM Corporation
11
 Chapter 16B The IPL Process

Example 21-1 IPL checklist

To IPL the z/OS system, do the following:
1. Select the IPL option
2. IPL with the following parameters:
o If you receive the message IEA888A for the clock, enter:
=> r 00,u
o If you receive the message IXC4ZOD for XCF, enter:
=> r 00,i
o If you receive the message IXCZ48E for XCF data sets, enter:
=> r 00,u
3. When the $HASP426 SPECIFY OPTIONS message appears, enter the
following to cold start JES2:
=> xx COLD,NOREQ
where xx is the reply ID of the console prompt.
Note: If the $HASP454, $HASP420, $HASP441, or $HASP870 messages appear,
Enter a response of Y.

© 2006 IBM Corporation

12
 Chapter 16B The IPL Process

IPL Types

 Cold start: PLPA is reloaded and VIO is cleared. This must

happen when the contents of LPA have changed
 Quick Start: PLPA is not reloaded but VIO is cleared. No
changes were made to LPA but VIO needs to be refreshed
 Warm Start: PLPA and VIO are retained from before the IPL
allowing jobs to restart using journalled VIO data

© 2006 IBM Corporation

13
 Chapter 16B The IPL Process

Specifying information

 From the hardware console the operator specifies

the device address of the IODF file, selects the
LOADxx member name and controls how the
system will prompt during the IPL
 If the IEASYSxx is not specified in the LOADxx
member then the operator will be prompted to
SPECIFY SYSTEM PARAMETERS

© 2006 IBM Corporation

14
 Chapter 16B The IPL Process

IPL Errors

 If a required parmlib member has an error or is

missing then the operator will be prompted
 If the parameter cannot be corrected then the
default can be accepted
 If a default does not exist then the parameter may
be cancelled or the IPL abandoned

© 2006 IBM Corporation

15
 Chapter 16B The IPL Process

Parmlib data sets

 The parmlib concatenation is a set of up to 16

partitioned data sets defined in the LOADxx
member
 These contain the required members to supply the
parameters for the system.
 SYS1.PARMLIB is the 17th and default if no others
are specified
 IEASYSxx is mostly a director to other members

© 2006 IBM Corporation

16
 Chapter 16B The IPL Process

Shutting down the system

 z/OS systems are designed to run continuously

with potentially many months between reloads
 Important workloads may require 24x365
availability
 Systems are only shutdown when necessary
usually for a change

© 2006 IBM Corporation

17
 Chapter 16B The IPL Process

System profiles

 Test system
– Reloaded as required to satisfy the testing regime
 High availability banking system
– Loaded very infrequently
– May be only yearly for software refresh
 Outside influence may dictate reloads such as
machine room power maintenance

© 2006 IBM Corporation

18
 Chapter 16B The IPL Process

Dynamic change

 Over the last ten years much work has been done
on z/OS and its predecessors so that many
changes can be done dynamically

© 2006 IBM Corporation

19
 Chapter 16B The IPL Process

System shutdown

 Each task needs to be shut down in the correct

order
 Usually this is done by an automation package
 The final commands to remove automation and
remove connections to other systems are
performed by the operators

© 2006 IBM Corporation

20
 Chapter 16B The IPL Process

Summary

 IPL was defined

 The initialization process was explained
 Types of IPL were discussed
 VIO was explained
 Extended up time and reasons for IPL were
discussed

© 2006 IBM Corporation

21