|
Initial Program Load. The initialization
procedure that causes an operating system to start operations
Types of IPL
Cold Start:
Any IPL that loads (or reloads) the
PLPA, but does not preserve VIO data set pages. The first IPL after system
installation is always a cold start because the PLPA is initially loaded.
Subsequent IPLs are cold starts when the PLPA is reloaded either to alter its
contents or to restore its contents if they were destroyed.
Quick Start:
Any IPL that does not reload the
PLPA and does not preserve VIO data set pages. (The system resets the page and
segment tables to match the last-created PLPA.)
Warm Start:
Any IPL that does not reload the
PLPA, but does preserve journaled VIO data set pages.
What happens at IPL time
LOAD SUCCESSFUL is a message from the IPL
hardware/microcode. IPL does:
1) hardware system reset
2) optional memory clear
3) issues a basic READ (CCW op code 02) to the IPL device.
It reads 24 bytes into absolute location 0. on disk, op code 02 is READ IPL,
which seeks to cyl 0, trk 0 and reads the data portion of record 1. This is the
IPL record on a disk initialized for IPL. On tape it just reads the first
physical record on the tape (assuming the tape is rewound).
4) it continues the I/O by expecting 1 or 2 additional READ
CCWs at absolute location 8 (part of the IPL record just read). On disk or tape
this reads record 2, which can be quite large. It is possible for this record
to contain more CCWs which are executed as part of the IPL, so it is possible
for the IPL hardware function to load complex code into various parts of
memory.
5) at this point, no instructions have been executed. If the
I/O was successful, it loads a PSW from absolute location 0 (start of the IPL
record) and starts execution.
If the I/O in steps 3/4 completes normally, you get LOAD
COMPLETE.
Wait states are detected after the program begins executing
(in the IPL program or NIP).
IPL PARMS
You can place the LOADxx member in one of the following
system data sets:
- SYSn.IPLPARM
- SYS1.PARMLIB Consider placing LOADxx in the SYSn.IPLPARM
data set.
During IPL, the system looks for LOADxx in the following
order:
- SYS0.IPLPARM through SYS9.IPLPARM on the IODF volume
- SYS1.PARMLIB on the IODF volume
- SYS1.PARMLIB on the sysres volume.
Do not create a SYSn.IPLPARM data set unless it contains the
LOADxx member that is used to configure your system. When the system finds
either SYSn.IPLPARM or SYS1.PARMLIB, it expects to find a LOADxx member in the
data set. If the LOADxx member specified on the LOAD parameter is not in the
data set, the system loads a wait state.
See the PARMLIB section
See the IPLPARM section.
The following is an example
of an IPL of a OS/390 2.6 system
All messages are not
display
|
IEE042I SYSTEM LOG DATA SET
INITIALIZED
(this is the first message displayed
on the console) |
|
IEA370I MASTER CATALOG SELECTED IS
CATALOG.MASTER.V26CAT |
| |
|
|
IEA101A SPECIFY SYSTEM
PARAMETERS |
Depress the
Enter Key to use the default |
|
IEE600I REPLY TO 00 IS;
|
|
| |
|
| Notice: the automatic start up commands issued from
SYS1.IBM.PARMLIB(IEACMD00) |
| START
LLA,SUB=MSTR |
|
| START
BLSJPRMI,SUB=MSTR |
|
| Notice: the automatic start up commands issued from
CPAC.PARMLIB(COMMND00) |
| S
TSS,SUB=MSTR |
Start Top
Serect |
| V
100-13F,OFFLINE |
Vary devices
100 to 13F offline |
| S
VLF,SUB=MSTR |
Start
VLF |
| S
LLA,SUB=MSTR |
Start
LLA |
| DD
ADD,VOL=V26CAT |
Add DASD
V26CAT |
| DD
ADD,VOL=COA200 |
Add DASD
COA200 |
| DD
NAME=SYS1.&SYSNAME..DMP&SEQ |
|
| DD
ALLOC=ACTIVE |
|
| S
EPWFFST.FFST,SUB=MSTR |
Start
FFST |
| S
RMF.RMF,,,MEMBER(00) |
Start
RMF |
| S CAS9
|
Start CAS9
(Computer Associates Products) |
| S NET
|
Start
VTAM |
| S
TSO |
Start
TSO |
| S EZAZSSI
|
Start
EZAZSSI |
| S IOAOSASF
|
StartIOAOSASF |
| S IXFP
|
Start Snap
Shot |
|
|
| *01 CAS2070I
Specify CAISEC Start options or reply U to continue |
Depress the
Enter Key to use the default |
| R 01
SUPPRESSED |
|
| |
|
| Next operator response will be |
|
| *02 $HASP426
SPECIFY OPTIONS - JES2 OS 2.5.0 |
|
| R 02,NOREQ |
*$HASP493 JES2
ALL-MEMBER WARM START IS IN PROGRESS |
| |
|
| Notice: the automatic start up commands issued from
CAI.PPOPTION(CAUTOCMD) |
| S CAENF
|
CA Event
Notification Facility |
| S OPERA
|
CA
Opera |
| S
ROSCOE |
CA
ROSCOE |
| S CASCHD
|
CA
Scheduler |
| S
CTS |
CA
CTS |
| |
|
| |
|
| *04 IST937A
GWNCP CORRELATOR MISMATCH ... REPLY 'RELOAD', 'INACT', OR 'IGNORE' |
|
| R 04,IGNORE |
IEE600I REPLY
TO 04 IS;IGNORE |
| |
|
| Automatic Startup Procedures from ROSCOE
|
| >STARTUP |
Automated
startup procedure activated |
| D
T |
Displays
local & GMT time and date |
| -START
DB2 |
Starts DB2
for xxx |
| =START
DB2 |
Starts DB2
for xxx |
| S
XTP1CICS |
Starts CICS
region XTP1 |
| S
XNSLCICS |
Starts CICS
region XNSL |
| S
XJISCICS |
Starts CICS
region XJIS |
| S
XDMNCICS |
Starts CICS
region XDMN |
| S
XSAFCICS |
Starts CICS
region XSAF |
| S
XARSCICS |
Starts CICS
region XARS |
| S
XICSCICS |
Starts CICS
region XICS |
| S
XARSD2 |
Starts CICS
region XARS2 |
| S
XJ05CICS |
Starts CICS
region XJ05 |
| S
XJ06CICS |
Starts CICS
region XJ06 |
| S
XJ07CICS |
Starts CICS
region XJ07 |
| F
WLM,MODE=COMPAT |
Modify Work
Load Manager to operate in compatability mode |
| SET
IPS=00 |
Use
CPAC.PARMLIB member IEAIPS00 |
| SET
ICS=00 |
Use
CPAC.PARMLIB member IEAICS00 |
| $PRT1 |
Starts JES
printer 1 |
| $PRT3 |
Starts JES
printer 3 |
| $PRT4 |
Starts JES
printer 4 |
| $PRT5 |
Starts JES
printer 5 |
| $SI2-4 |
Starts JES
initiators 2,3,4 |
| $SI7-10 |
Starts JES
initiators 7,8,9,10 |
| V
PATH(1000,88),ONLINE |
Vary path
1000 online |
| S
TCPIP |
Starts
TCP/IP |
| D A,L
|
Displays
Active tasks, All |
| |
|
| S DSNTDBM1
|
|
| S FTPD
|
|
| S DSNDIST
|
|
| D A,L
|
|
| |
|
| |
|
R 5,GO
IEE600I REPLY TO 05 IS; GO |
|
| |
|
R 6,GO
IEE600I REPLY TO 06 IS;GO |
|
| |
|
R 7,GO
IEE600I REPLY TO 07 IS;GO |
|
| |
|
| DD
DSN,CLEAR=ALL |
|
| |
|
| S
CJ05CICS,START=COLD |
|
...
...
... |
|
IPL Problems
These are problems that
some systems programmers have experienced. These problems are listed for
reference only. Review the proper IBM documentation for any problems that you
may encounter.
WAIT019
What happened for the wait019 was that SYS1.NUCLEUS was
destroyed, but not in extents. I should have looked inside the SYS1.NUCLEUS as
well outside. IEANUC01 should have been 608A10 in size, but was only about 7090
in size. Many other modules were hit also. Total size of SYS1.NUCLEUS was 13
cyls and should have been over 35 cyls. Just applied a lot of PTFs to the test
system, OS/390 2.4.
Wait064
During IPL, after messages IEA549I SYSTEM CONSOLE 0B80
DEFINED AS MASTER CONSOLE
IEA168I VATLST00: SYSTEM DEFAULT USE ATTRIBUTE OF
PRIVATE USED.
IEA304W SYSTEM WAIT STATE 800090064 DURING IEAVNPOE
INITIALIZATION
The system is now dead. The system codes indicates a program
check. wait064 09.
OW36941: A WAIT064 RC09
OCCURS DUE TO ABEND0C4 IN IEAVSWCS
ORIGINATING DETAILS: After removing a
system from the sysplex, a WAIT064 rc9 (rc09) occurred when trying to IPL that
system back into the sysplex. The WAIT064 occurred due to an ABEND0C4 in
IEAVSWCS because IEAVN614 found an entry in the array mapped by IEAVN100 that
had the CONRESET bit on, so IEAVN614 LINK'ed to IEECB825, who called IEAVSWCS,
but UCMEPSTC and UCMEPSFC were both zero, so we're trying to unswitch a console
that is not really switched. This entry in IEAVN100 is the 100th (or greater)
entry in the array, but IEAVN600 only gets enough storage for 99 entries inthe
array.
Wait088
How the system finds that Master Catalog
There are two sources:
member LOADxx's SYSCAT, or
SYS1.NUCLEUS(SYSCATLG)
SYSCATLG of SYS1.NUCLEUS will be used if the SYSCAT
parameter is not included in the LOADxx member of SYS1.IPLPARM (or whatever).
The system will ask for a suffix xx to be appended to SYSCAT
to form a member name in SYS1.NUCLEUS, if there's no SYSCAT statement in
LOADxx, or IMSI was specified A, C, D, or P (ignore LOADxx's SYSCAT). If
"Enter" is pressed, then the system will pick SYSCATLG. Or you can specify a
different suffix. Probably, something unpleasant will happen if you press
"Enter", but there's no SYSCATLG there.
IPLTEXT
I once had an IPL problem that turned out to be the wrong
level of IPLTEXT written to the IPL volume. Different (down level)
IPLTEXT...but as memory serves this just didn't load. |