z/OS MVS System Initialization Logic

Initial Program Load (IPL)
Silvio Sasso IBM Switzerland, Global Services ITS sisa@ch.ibm.com

Zürich | Mai 2006 Last revision September 2008

© 2006 IBM Corporation

The following are trademarks of the International Business Machines Corporation in the United States and/or other countries.

CICS* DB2* DB2 Universal Database DirMaint ESCON* FICON* GDPS* HiperSockets HyperSwap

IBM* IBM eServer IBM logo* IMS NetView* OMEGAMON* On Demand Business logo Parallel Sysplex*

RACF* S/390* System z9 System z10 Tivoli* TotalStorage* VSE/ESA VTAM* WebSphere* z/Architecture

z/Architecture z/OS* z/VM* z/VSE zSeries* zSeries Entry License Charge

* Registered trademarks of IBM Corporation The following are trademarks or registered trademarks of other companies. Java and all Java-related trademarks and logos are trademarks of Sun Microsystems, Inc., in the United States and other countries Linux is a trademark of Linus Torvalds in the United States and other countries.. UNIX is a registered trademark of The Open Group in the United States and other countries. Microsoft is a registered trademark of Microsoft Corporation in the United States and other countries. * All other products may be trademarks or registered trademarks of their respective companies. Notes: Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance ratios stated here. IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply. All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics will vary depending on individual customer configurations and conditions. This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without notice. Consult your local IBM business contact for information on the product or services available in your area. All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. Information about non-IBM products is obtained from the manufacturers of those products or their published announcements. IBM has not tested those products and cannot confirm the performance, compatibility, or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. Prices subject to change without notice. Contact your IBM representative or Business Partner for the most current pricing in your geography.

Zürich | 26. Oktober 2004

© 2004 IBM Corporation


This presentation will describe the general processing which is involved in initializing a z/OS system, from the IPL process until the system is ready to start either JES2 or JES3 The major steps described are: The hardware process of loading z/OS The loading and initialization of the nucleus The initialization of general system resources Master Scheduler Initialization IBM may change the implementation of internal processing at any time with no prior notice

Special Notice
This documentation contains some parts of the presentation “Pulling a System up by its Bootstraps” by Greg Dyck (IBM), SHARE session 2854, March 2000

Zürich | 26. Oktober 2004

© 2004 IBM Corporation


z/OS Initialization Overview
Processed in different phases Each phase builds on the next Within each phase, steps build on each other

Zürich | 26. Oktober 2004

© 2004 IBM Corporation


I/O Device Info for both UCWs and UCB‘s. Devices) UCBs and EDTs (requires a Production IODF to activate) UCBs built during IPL/NIP IODF pointed to by the LOADPARMs and LOADxx HCD Production IODF contains the LPAR Names. CU. deleting or modifying the Hardware Definitions (CHPIDs. Channel Info Control Unit. EDT and NIP consoles IOCP Program Writes IOCDS HCD Work IODF used to define Configuration and to make Changes Zürich | 26.Introduction UCW and UCB Generation Activate using a Reset Profile (POR) Central Storage HSA UCWs (1 per Device) Main Storage UCBs (1 per Device) SE Selected IOCDS UCW Images (subchannels) Dynamic Changes HCD DYNAMIC Allows adding. Oktober 2004 © 2004 IBM Corporation 5 .

PARMLIB LOADxx SYSPARM xx IEASYM xx SYSPLEX Name SYSCAT IODF IODF Dataset UCB‘s and EDT‘s IMSI Field SYS1.NUCLEUS IEANUC0n SYSRES Volume R1 = IPL Record R2 = Bootstrap R4 = IPL text IODF Volume SYSn. Oktober 2004 © 2004 IBM Corporation 6 .Introduction Dataset Considerations – the big Picture Load Operation Load Address dddd Load Parameters dddd xx i n SYS1.IPLPARM or SYS1.PARMLIB Member IEASYS Modified by the Member IEASYSxx IEASYMxx contains Symbolics The Operator can override many Settings by using prompting in the LOAD Parameter IMSI Field Master Catalog Zürich | 26.

Introduction Load Parameters IODF dddd LOADxx xx IMSI i NUCx n DDDXXINN Load Parameter Values DDDD: XX: I: Device number of the volume containing the IODF dataset (Default is SYSRES) ID of the LOADxx member to be used (the default is LOAD00) Initial Message Suppression Indicator (IMSI) The default suppresses most informational messages and does not prompt for system parameters. will use the LOADxx values N: Nucleus ID to be used (default is 1: IEANUC01) Zürich | 26. Oktober 2004 © 2004 IBM Corporation 7 .

Oktober 2004 © 2004 IBM Corporation 8 .Introduction IMSI Character IMSI Character Period (.) or blank A C D M P S T Display informational Messages No Yes No Yes Yes No No Yes Prompt for Master Catalog Response No Yes Yes Yes No Yes No No Prompt for System Parameter Response No Yes No No No Yes Yes Yes Zürich | 26.

Introduction And all begins with a Mouse Click… Zürich | 26. Oktober 2004 © 2004 IBM Corporation 9 .

Hardware IPL Hardware IPL Overview Process is defined by the z/Architecture Controlled by hardware A single CPU is used for IPL . stopped) state A hardware system reset occurs before the process begins IPL records are written with ICKDSF Cyl 0.all other CPUs are placed into a manual (i. R1. R2.e. Trk 0. IEAIPL00 Zürich | 26. Oktober 2004 © 2004 IBM Corporation 10 .

equal TIC to Search ..Hardware IPL Hardware IPL Flow Load Operation 2) CSS stores IPL CCW into absolute Storage Location 0 and initiates SSCH with CCW Addr = 0 DASD will then seek to CYL 0. .id...data R2 TIC to R2 data SYSRES HSA Subchannels UCW‘s Central Storage 1) CSS UCW for Load Device Hardware turns on enable bit Record 2 IPL2 3) Record 1 will provide CCW‘s to read Record 2 4) Record 2 will provide CCW‘s to read Record 4 Seek Search.. Head 0 and read Record 1 Record 1 IPL1 0 Read. Read data IEAIPL00 CCHHR Record 3 Volume Label Volume Label User Label (optional) Record n (usually R4) IEAIPL00 Loc 0 00080000800005F4 5) IEAIPL00 Location 0 contains initial PSW After Record 4 has been read the Hardware Portion of IPL is complete Zürich | 26. Oktober 2004 © 2004 IBM Corporation 11 .

Hardware IPL Hardware IPL Summary Hardware generates an IPL CCW to read of 24 bytes IPL text into location 0 CCW = 02000000. record 1 Location 8 treated as a command chained CCW Read record 2 into storage.40000018 For DASD. Oktober 2004 © 2004 IBM Corporation 12 . this always reads cylinder 0. command chain to next CCW Transfer CCW execution to record 2 location Seek and search for IEAIPL00 record Read IEAIPL00 into location 0 CCW chain completion. PSW is loaded from absolute 0 and execution begun IEAIPL00 location 0 contains initial PSW Zürich | 26. track 0.

Oktober 2004 © 2004 IBM Corporation 13 .non relocatable Builds an initial virtual environment IPL workspace located at X'20000000' virtual Provides services to Back virtual storage with real frames Do I/O Controls the IPL initialization process Loads IPL Resource Initialization Modules (RIMs) into workspace Gives them control Zürich | 26.IPL Resource Initialization Overview Originally just loaded the Nucleus and set up the Master address space environment Processing has gotten more complex with the XA architecture and Dynamic I/O support Processing is single threaded The IPL vector table (IVT) contains global information during this phase IEAIPL00 A mini operating system .

5.IPLPARM ON DEVICE 5411 SELECTED FOR IPL PARAMETERS IEA246I LOAD ID 00 SELECTED first Message displayed on NIP Console 6. Locate usable real storage at top of memory Get IPL load parameters. Oktober 2004 © 2004 IBM Corporation 14 . and set any defaults Search LOADxx. Search IODF. process the information in LOADxx IEA371I SYS0. IODF DEVICE NUMBER = 5411 Build a table of NIP consoles max. Test Block Instruction (clear Storage) Read SCPINFO Get loadparm Set autostore status on 3.IODF24 IEA520I CONFIGURATION ID = SM15DPRI.IPL Resource Initialization IPL RIM Processing 1. 4. process the information in the IODF IEA246I NUCLST ID 00 SELECTED IEA519I IODF DSN = SYSIOD. number of NIP consoles supported by IPL RIM is 64 (HCD supports 128) o see APAR OA12877 for additional information Zürich | 26. 2.

) Invoke the device UIMs to Identify device specific nucleus and LPA modules Calculate required SQA and ESQA Build device control blocks in the workspace Build the Allocation EDT in the workspace 7. Oktober 2004 © 2004 IBM Corporation 15 .IPL Resource Initialization IPL RIM Processing… 6. Load modules. RMODE and read-only 8. and UIMs CSECTs are grouped/positioned by attributes. process the information in the IODF (cont. Create a map of the DAT-on nucleus CSECTs IEA091I NUCLEUS 1 SELECTED IEA093I MODULE IEANUC01 CONTAINS UNRESOLVED WEAK EXTERNAL REFERENCE IFFIOM IEA093I MODULE IEANUC01 CONTAINS UNRESOLVED WEAK EXTERNAL REFERENCE IEDQATTN IEA093I MODULE IEANUC01 CONTAINS UNRESOLVED WEAK EXTERNAL REFERENCE IECTATEN Includes modules identified by NMLs. dynamically resolving external references Zürich | 26. NUCLSTxx.

Load Prefix Register 15. build available frame queue IPL workspace is destroyed 14. LOADxx INITSQA. Create Master's VSM control blocks and LSQA 11.IPL Resource Initialization IPL RIM Processing… 9. UIM determined value 10. Create Master's permanent page and segment tables 12. Create the initial SQA/ESQA areas Sum of IBM supplied value. Switch to nucleus version of the PSA Zürich | 26. Move from the workspace into SQA/ESQA Device control blocks Allocation EDT IPL Messages LPA device support module list 13. Oktober 2004 © 2004 IBM Corporation 16 . Validate real storage.

Oktober 2004 17 .IPL Resource Initialization Virtual Storage Layout 16Eb Private Shared Area Low User Private Extended Private High User Region Default shared Memory Addressing Low User Region Reserved Extended LSQA/SWA/229/230 Extended User Region Extended CSA Extended Common Extended FLPA/MLPA/PLPA Extended SQA Extended Nucleus Nucleus Common SQA FLPA/MLPA/PLPA CSA LSQA/SWA/229/230 Private Common User Region System Region PSA 24K 8K 0 © 2004 IBM Corporation 512Tb 2Tb 4Gb 2Gb 16Mb Zürich | 26.

Re-IPL required No Is SYS1. enter non-restartable disabled Wait State WSC=0B1 RC=01. Re-IPL required LOADxx found.IPLPARM? No LOADxx not found. enter non-restartable disabled Wait State WSC=088 RC=00. Re-IPL required LOADxx not found. Oktober 2004 © 2004 IBM Corporation . enter non-restartable disabled Wait State WSC=088 RC=00. continue IPL/NIP processing 18 Zürich | 26.PARMLIB No LOADxx not found.PARMLIB on the IODF volume? Yes No Is SYS1.IPLPARM on the IODF volume? (n=0-9) Yes Is LOADxx in SYSn. digits 5 and 6 (example Load Parm = 012355M) Is SYSn.IPL Resource Initialization LOADxx Search Sequence Search for the LOADxx member specified in the LOADPARM field.PARMLIB on the SYSRES volume? Yes No Yes Yes Is LOADxx in SYS1.

POST.) are initially available Additional services enabled as NIP RIMs run The NIP vector table (NVT) contains global information during this phase Control routine Sets traps for unexpected errors (no RTM support is available yet) Verifies the hardware environment Creates IPL processor control blocks Creates global VSM control blocks Creates I/O control block pools Creates the initial system trace table Opens SYS1. EXCP.NIP Resource Initialization Overview Initializes basic system resources Processing is multithreaded . WAIT. etc.NUCLEUS as the LNKLST Loads and invokes NIP RIM routines Zürich | 26. Oktober 2004 © 2004 IBM Corporation 19 .normal dispatching of work is done Basic system service (SRBs. ATTACH.

bit 2) • at the completion of this mapping process all devices defined to both the channel subsystem (UCWs) and MVS (UCBs) will be enabled and connected • any UCWs without corresponding UCBs will be left disabled • any UCBs without corresponding UCWs will be left not connected Devices in either one of these states cannot be used by the system Zürich | 26. the I/O configuration (UCWs) loaded into the HSA with a POR (or updated via dynamic I/O) is matched with the operating system configuration (UCBs) defined in the IODF The UCWs are placed in the disabled state after POR or system reset Initial UCB state: • the UCBs are built with the “not connected“ state bit = 1 (UCB byte 7. Oktober 2004 © 2004 IBM Corporation 20 .NIP Resource Initialization UCW to UCB Mapping In order for MVS to use a device: HSA UCS Device # 2400 Enable Bit Interrupt Subclass (ISC) Interruption Parameter Central Storage UCB Device # 2400 Channel Paths SSID Connected • a UCW for the device must exist • a UCB for the device must exist During device mapping: • each matching UCW is enabled • each matching UCB is connected During the mapping process.

NIP Resource Initialization Non-DASD Pathing The process of determining path availability is referred to as Pathing • during this process MVS will check all paths for devices genned to come up online by attempting to complete an I/O operation down each path defined to a device • if at least one path is operational the device will be online Printers • Tapes are an exception: pathing is performed to offline tape devises MVS does not report any paths or devices that are found to be not operational during pathing Tapes Zürich | 26. Oktober 2004 © 2004 IBM Corporation 21 .

Oktober 2004 © 2004 IBM Corporation 22 . IEA214A SYSRES) • at end of pathing wait 15 seconds for any outstanding I/O to complete mark any UCB with outstanding I/O to test later again purge all outstanding requests Zürich | 26. represents CHPID‘s defined in IOCDS create LPM (Logical Path Mask). timeout (no IOS120A message during path testing) create PIM (Path Installed Mask). used by UCB to control paths to be used for an I/O operation • Get device characteristics – one path • Self description – each path (msg IOS291I) • VOLSER checking – one path for SDP products (all paths for other DASD) DASD Devices Dynamic Paths Matrix duplicate VOLSER message (IEA213A – not SYSRES.NIP Resource Initialization DASD Pathing A NIP console is required before DASD pathing takes place to allow the operator to respond to out-of-line conditions encountered during the DASD pathing • Issue SSCH to multiple devices (test multiple devices in parallel) • After each successful I/O another device is tested • Redrive another device if an I/O is complete for a device If an I/O fails to complete within 15 seconds.5 sec. the I/O operation is purged • Perform path testing on each path no 1.

IEA213A or IEA214A (any A or action messages requires operator response) CCW = Channel Command Word RCD = Read Configuration Data RDC = Read Device Characteristics SDP = Self-describing Product SSID = Subsystem ID (DASD CUs) Zürich | 26. Oktober 2004 © 2004 IBM Corporation 23 . IGGN505A. FA RCD Message: IEC334I (duplicate SSID) 3 (S) SDP Each Path CCWs: E4 Sense Id (one Path) FA RCD (each Path) Message: IOS291I (Configuration Mismatch) Messages: IEA213A. IGGN505A. IEC334I. Required Dataset missing. self-describing product (S) and VOLSER processing (V) Any error consitions detected during the DASD pathing steps are reported to the NIP console via messages IGGN504A. 54 Subsystem. IOS120A moved to MSI 2 (D) UCB Device Characteristics Initialization One Path CCWs: E4 Sense Id.NIP Resource Initialization DASD Pathing… 1 (P) Path Testing Each Path CCW: 94 Release Messages: IGGN504A. read device characteristics (D). 64 RDC. IOS291I. IEA214A (Duplicate VOLSER) 4 (V) VOLSER One Path SDP Device Each Paths non-SDP device DASD pathing consists of 4 different phases: path testing on each path (P).

NIP Resource Initialization DASD Pathing… Dynamic Pathing Error Messages IOS291 CONFIGURATION DATA COULD NOT BE READ ON PATH (24C0.CCA X‘00‘. DEVIVE 24C0 NOT BROUGHT ONLINE • In addition the the IOS291I messages. Oktober 2004 © 2004 IBM Corporation 24 .49) RC=21 • IOS291I messages with a RC of 21. 27 or 29 indicate a possible configuration error and should be investigated IEC334I DUPLICATE SUBSYSTEM X‘0001‘. either message IEA213A or IEA214A will be issued Zürich | 26. a misconfiguration problem to a DASD CU may also show up as a duplicate SSID condition IEA213A DUPLICATE VOLUME ‘SPOOL1‘ FOUND ON DEVICES 2465 AND 28A0 IEA213A REPLY DEVICE NUMBER WHICH IS TO REMAIN OFFLINE IEA214A IEA214A IEA214A IEA214A DUPLICATE SYSRES ‘S15R21‘ FOUND ON DEVICE 22C4 VERIFY THAT THE CORRECT DEVICE WAS USED FOR IPL DUPLICATE DEVICE WILL REMAIN OFFLINE REPLY ‘CONT‘ TO CONTINUE IPL • The last step of dynamic pathing is Direct Access Volume Verification (DAVV) • DAVV processing reads the volume label of each online DASD device and updates the UCB with the VOLSER • If a duplicate VOLSER exists.

REPLY ‘CONT‘ OR ‘WAIT‘ IOS600I REPLY TO 00 IS ‘WAIT‘ *IOS124A STILL WAITING FOR RESPONSE FROM DEVICE 1A60.LINKLIB ON DCSYS2 OR CANCEL • IGGN504A or IGGN505A message issued if required dataset is on a volume that was busy during DASD pathing and the dataset is required for the IPL to complete • Issue D U.LINKLIB ON DCSYS2 OR CANCEL R 00. Oktober 2004 © 2004 IBM Corporation 25 . REPLY ‘CONT‘ OR ‘WAIT‘ *IOS120A DEVICE 1A60 SHARED.1A60 • If the busy condition still exists IOS120A will be issued *IOS120A DEVICE 1A60 SHARED.NIP Resource Initialization DASD Pathing… Dynamic Pathing Error Messages… IGGN505A SPECIFY UNIT FOR SYS1.UNIT UNACCEPTABLE. REPLY ‘CONT‘ OR ‘WAIT‘ IOS600I REPLY TO 00 IS ‘WAIT‘ IGGN306I 1A60.PRODXY. 00000004 IGGN505A SPECIFY UNIT FOR SYS1.VOL=vvvvvv on an active system that shares the DASD device to obtain the device number associated with the VOLSER Zürich | 26.1A60 IEE600I REPLY TO 00 IS.PRODXY. TOTAL WAIT TIME IS 46 SECONDS.

2. 9. 4.NIP Resource Initialization NIP RIM Processing 1. 5. Create RTM recovery and control blocks Create WTO control blocks and pools WTOs issued now will be logged in SYSLOG Initialize Machine Check handling (MCH) Device mapping (UCWs to UCBs). test availability. prompt for system parameters (message IEA101A) 11. and LOGREC 10. 8. and initialize non-DASD devices Select and initialize NIP WTOs will now be displayed on the NIP console Test availability. If required. 6. Oktober 2004 © 2004 IBM Corporation 26 . and initialize DASD devices (DASD Pathing) Operator can be prompted during validation Open the master catalog Create the system symbolics from IEASYMxx Open SVCLIB. PARMLIB. 3. Merge and analyze the system parameters Zürich | 26. 7.

Initialize ASM. expand initial SQA/ESQA 14. Initialize Cross-memory services. Create the PLPA if CLPA specified LPALSTxx datasets UIM specified device support from SYS1.NIP Resource Initialization NIP RIM Processing… 12. Create FLPA and MLPA. Oktober 2004 © 2004 IBM Corporation . PLPA boundaries control SQA/ESQA boundaries On a coldstart. Enable RTM for task termination / SRB purge Limited Function Address spaces can now be created by master scheduler 21. Complete type 3 and 4 SVC table entries 18. Process CSA= parameter 19. Create user SVC table entries from IEASVCxx 15.NUCLEUS 16. fix FLPA area and protect both areas as requested 17. Initialize system resource manager (SRM) 20. creates PCAUTH address space 27 Zürich | 26. opening page and swap datasets 13. Process SQA= parameter On a quickstart (CLPA not specified).

Initialize XCF/XES services. creates CONSOLE address space Full function console is still unavailable 31.drops SYS1. Initialize SVC dump services. creates SMXC and SYSBMAS address spaces 29. sets TOD if needed 25. Initialize data management 33. Initialize Timing services. Initialize RSM Dataspace services. Initialize System Trace services. creates XCFAS address space 27. Open LNKLST -. creates OMVS address space Zürich | 26.NUCLEUS 30. Initialize Console services. creates GRS address space 28.NIP Resource Initialization NIP RIM Processing… 22. Initialize SMS and PDSE services. creates DUMPSRV address space 26. creates TRACE 24. Initialize WLM services. Initialize Concurrent-copy. creates ANTMAIN and ANTAS000 address spaces 34. Oktober 2004 © 2004 IBM Corporation 28 . Initialize GRS services. Initialize UNIX System Services. creates RASP 23. creates WLM address space 32.

Oktober 2004 © 2004 IBM Corporation 29 . Close master catalog 36. creates CATALOG address space Limited function. enables full RTM recovery/retry LINK to Master Scheduler processing Zürich | 26.NIP Resource Initialization NIP RIM Processing… 35. for use until MSI completes 37. Initialize Catalog services. Exit NIP processing Create the IPL parameter area (IPA) Free control blocks no longer needed by NIP Reset traps for unexpected errors.

creates IEFSCHAS address space Initialize MSTR subsystem Initialize Common JES services. creates JESXCF address space Initialize Allocation services. creates ALLOCAS address space Attach Initiator to start Master JCL Zürich | 26.Master Scheduler Initialization Master Scheduler Initialization (MSI) Overview Completes initialization of system functions Coordinates final completion with primary subsystem (JES2/JES3) Basic Processing Initialize Master Trace processing Enable full function Console processing All MCS consoles are now available Initialize Sysplex-wide ENF services. Oktober 2004 © 2004 IBM Corporation 30 .

DEL=RD etc. Oktober 2004 © 2004 IBM Corporation 31 . 7. 8. 6.Master Scheduler Initialization MSI Processing Details 1. create IOSAS Initialize Master's security environment Initialize Console attributes. 10. Initialize APPC services Initialize TSO services Initialize LOGREC Logstream recording Enable ENF services Initialize System Logger services. 3. 11. Initialize MIH services Complete ASM initialization Initialize IOS dynamic pathing. Initialize SMF services. creates IXGLOG address space Vary all available CPs online we are now multiprocessing 12. 5. creates SMF address space Zürich | 26. 2. 9. 4.

Indicate MSI is complete 19. Initialize System security processing 16. Initialize RTM services LOGREC recording Address space termination SVC dump processing 15. Build defined subsystems Invoke initialization routine Issue START for primary JES subsystem. Issue commands in IEACMD00 and COMMNDxx parmlib members only commands processed by CONSOLE will execute now 14.Master Scheduler Initialization MSI Processing Details… 13. Initialize Master command processing Any pending commands that execute in Master will now be executed Start commands are executed by Master Zürich | 26. Hold primary JES STC and TSO processing 18. Oktober 2004 © 2004 IBM Corporation 32 . if requested 17.

Issue command processing available message 21.Master Scheduler Initialization MSI Processing Details… Full function address spaces can be created . Oktober 2004 © 2004 IBM Corporation 33 .JES and other tasks started under MSTR will now start 20. Wait for JES to indicate primary services are available Release primary JES STC and TSO processing Start the System Log Syslog/OPERLOG All IPL processing is now complete The next and final step is to bring up and initialize the job entry subsystem (JES2 or JES3) Zürich | 26. Allow pending address space creates (not done by Master) to complete Create full function CATALOG Original CATALOG terminates Address spaces may switchover from limited to full function 22.

662 00:00:00. etc.093 00:00:00.010 00:00:00. use IPCS VERBX BLSAIPST to display IPL statistics information Total IPL Time: 00:00:12.001 00:00:00.019 00:00:00.006 00:00:01.052 00:00:00.PFT.257 00:00:00. etc.317 ISNIRIM . master RAB. Copy and relocate EDT to ESQA Page frame table and cleanup To determine the time required for an IPL in your installation.000 00:00:01. ULUT.Read SCPINFO Test Block storage to 2G Fast FIND service LOAD service IPLWTO service Read SCHIBs into IPL workspace Process Load and Default parameters IPL parmlib .000 00:00:00. Oktober 2004 © 2004 IBM Corporation 34 .000 00:00:00.595 00:00:06.107 00:00:00. master SGT IAXMI .009 00:00:00.Master Scheduler Initialization IPCS Display IPL Statistic VERBX BLSAIPST *** IPL Statistics *** IEAIPL10 IEAIPL20 IEAIPL11 IEAIPL31 IEAIPL30 IEAIPL46 IEAIPL49 IEAIPL50 IEAIPL51 IEAIPL43 IEAIPL60 IEAIPL70 IEAIPL71 IEAIPL08 IEAIPL40 IEAIPL42 IEAIPL41 IEAIPL05 IEAIPL02 IEAIPL04 IEAIPL14 IEAIPL06 IEAIPL09 IEAIPL07 IEAIPL03 IEAIPL18 IEAIPL99 00:00:00.007 00:00:00.199 00:00:00. Update AMODE for nucleus resident SVCs Build UCBs.029 00:00:00.RSM blocks.158 00:00:00.000 00:00:01.load CBD and IOS services Build DFT for each device Read EDT information from IODF Read MLTs from nucleus Read NMLs from nucleus (IEANynnn modules) Read PDS directory entries and CESD records Build and sort NUCMAP Load nucleus modules Allocate PFT and SQA/ESQA Build LSQA/ELSQA for Master IARMI .012 00:00:00.914 Zürich | 26.000 00:00:00.166 00:00:00.014 00:00:00.357 00:00:00.784 00:00:00.process LOADxx and NUCLSTxx System architecture Find and Open IODF data set Read NCRs from IODF UIM environment .047 00:00:00.

009 00:00:04.Process REAL= Build GRS blocks in SQA ASM .102 00:00:00.DASD UCBs Locate and Open master calalog Open SYS1.569 00:00:00.Master Scheduler Initialization IPCS Display IPL Statistic… *** NIP Statistics *** IEAVNIP0 IEAVNIPM IEAVNPE6 IEAVNPFF IEAVNPA6 IEAVNPC6 IEAVNPC3 IEAVNP24 IEAVNP06 IEAVNP27 IEAVNPA2 IEAVNPCA IEAVNPB2 IEAVNP11 IEAVNPC7 IEAVNPOP IEAVNPIL IEAVNPC4 IEAVNP03 IEAVNPCF IEAVNP76 IEAVNPE8 IEAVNP23 IEAVNP04 IEAVNPA8 IEAVNPC2 IEAVNP14 IEAVNPGD IEAVNP25 IEAVNP05 IEAVNP44 IEAVNPB1 00:00:00.002 NIP Base Invoke NIP RIMs Service Processor Interface Loadwait/Restart RTM .Non-DASD UCBs NIP Console IOS .057 00:00:02. Oktober 2004 © 2004 IBM Corporation 35 .029 00:01:25.RTCT and recording buffer WTO Issue messages from IPL message queue SMS Open/Mount Machine Check Reconfiguration IOS .056 00:00:00.008 00:00:00. APF ASA Reuse stuff Process CSCBLOC= Zürich | 26.493 00:00:00.276 00:00:00.114 00:00:00.003 00:00:00.032 00:00:00.033 00:00:16.034 00:00:00.Expand SQA IOS .032 00:00:00.025 00:00:00.054 00:00:00.179 00:00:00.012 00:00:00.428 00:00:00.039 00:00:00.004 00:00:00.012 00:00:08.Build SQA control blocks Move console data to ESQA Process SVC= LPA.SVCLIB Open PARMLIB Process IEALSTxx Prompt for System Parameters Merge and analyze system parameters Process system name and system variables Open LOGREC RSM .Open page and swap data sets VSM .072 00:00:00.037 00:00:00.099 00:00:00.015 00:00:00.Move CDT to SQA ASM part 2 .018 00:00:00.071 00:00:00.022 00:00:00.189 00:00:00.

017 00:00:00. etc.OPT=. IPS=.026 00:00:17.033 00:00:01.Master Scheduler Initialization IPCS Display IPL Statistic… IEAVNPE2 IEAVNPB8 IEAVNP47 IEAVNPD6 IEAVNP09 IEAVNPD8 IEAVNP10 IEAVNPD1 IEAVNPD2 IEAVNPCX IEAVNPX1 IEAVNPF5 IEAVNPF8 IEAVNP1F IEAVNP51 IEAVNP20 IEAVNP21 IEAVNP57 IEAVNPF9 IEAVNP33 IEAVNPLM IEAVNPED IEAVNP26 IEAVNPE5 IEAVNPD5 IEAVNP88 IEAVNPA1 IEAVNPDC IEAVNP16 IEAVNP13 IEAVNP17 IEAVNPG8 IEAVNP18 IEAVNPF2 00:00:00.033 00:00:00.I/O measurement blocks TRACE Process CLOCK= TOD clock SDUMP XCF GRS License manager PROD SMS LNKLST Load pageable device support modules Allocation move EDT II CONSOLE WLM EXCP appendages Prepare NIP/MSI interface GTF Monitor Call interface VSM defined monitor call enablement PARMLIB Scan Routine interface Process IOS= Zürich | 26.023 00:00:00.681 00:00:31.048 00:00:00.262 00:00:00.269 00:00:29.002 00:00:00.003 00:00:00.003 00:00:04.614 00:00:00. ESTAE Build ASVT RSM . Oktober 2004 © 2004 IBM Corporation 36 . ABDUMP.126 00:00:00.894 00:00:00.891 00:00:00.005 00:00:00.156 00:00:00.167 00:00:00.030 00:00:00.015 00:00:00.513 00:00:01.221 00:00:01.127 00:00:00.086 00:00:00.232 00:00:00.358 00:00:00.003 00:00:00. VRREGN= and RSU= SRM .683 00:00:05.327 RACF SAF Create CSA ENF RTM .021 00:00:00.718 00:00:00. registration services NIP cleanup PCAUTH RASP SRM .029 00:00:13. ABDUMP SDUMP Context services.019 00:00:00.Frame queues.SDUMP.

001 Process VATLST RRS USS Unicode Close catalog Nip final cleanup Total NIP Time: 00:03:53.112 00:00:02.732 Zürich | 26. Oktober 2004 © 2004 IBM Corporation 37 .381 00:00:00.512 00:00:00.020 00:00:01.Master Scheduler Initialization IPCS Display IPL Statistic… IEAVNP15 IEAVNPRR IEAVNPOE IEAVNPLE IEAVNPUN IEAVNPXE IEAVNP1B IEAVNIPX 00:00:01.401 00:00:00.481 00:00:00.029 00:00:00.

264 00:00:00.013 00:00:01.Master Scheduler Initialization IPCS Display IPL Statistic… *** IEEVIPL Statistics *** IEETRACE ISNMSI UCMPECBM ENFPC005 IEFSCHIN IEFJSINT IEFSJLOD IAZINIT IAZFSII IEFQBINT IEFAB4I0 IEEVIPL 00:00:00.708 Zürich | 26.872 00:00:00.062 00:00:00.612 00:05:46.000 Tip: in the IPCS dialog.003 00:00:00. Select IPCS option 6 (commands) Issue DROPD MAIN (delete data from a previous IPCS session using in-storage as source) Issue VERBX BLSAIPST MAIN *** IEEMB860 Statistics *** ILRTMRLG IECVIOSI ATBINSYS IKJEFXSR IXGBLF00 ILMINITM COMMNDXX SMFWAIT SECPROD IEFJSIN2 IEFHB4I2 CSRINIT FINSHMSI IEEMB860 00:00:00.734 00:00:00.010 00:00:00.UCB scan Windowing services Wait for attached CMDs Uncaptured time: 00:00:00.029 00:00:00.526 00:00:02. 2.250 00:00:00.098 00:00:19.194 00:00:00. Oktober 2004 ASM IOS dynamic pathing APPC TSO Logger License manager COMMANDxx processing SMF Security server SSN= subsystem ALLOCAS .019 00:00:00.012 00:00:00.098 Total Time: © 2004 IBM Corporation 38 .721 00:00:00.134 00:00:00.375 00:00:10. to display the last IPL statistic using in-storage source rather than an SVC dump.687 00:00:38.000 00:00:00.104 00:00:00.673 00:00:06.448 Master trace SPI CONSOLE address space CONSOLE ready ENF IEFSCHAS address space Subsystem interface JESCT JESXCF address space FSI trace SWA manager ALLOCAS address space Uncaptured time: 00:00:00.000 00:01:33. 4.036 00:00:24. 3.134 00:00:00. proceed as follows: 1.

Oktober 2004 © 2004 IBM Corporation 39 .Glossary Terms and Abbreviations ASM • ENF • IOCP • IOS • IRIM • MCH • MIH • NIP • RIM • RTM • SRM • SYSRES • UCB • UIM • Auixiliary Storage Manager Event Notification Facility I/O Configuration Program Input/Output Supervisor IPL Resource Initialization Module Machine Check Handler Missing Interrupt Handler Nucleus Initialization Phase Resource Initialization Module Recovery Termination Manager System Resource Manager System residence Volume Unit Control Block Unit Information Module DAT IOCDS IODF IPL JES MCS MSI POR RSM SMS SVC TOD UCW VSM Dynamic Address Translation I/O Configuration Data Set I/O Definition File Initial Program Load Job Entry Subsystem Multiple Console Support Master Scheduler Initialization Power-on-Reset Real Storage Manager System managed Storage Supervisor Call Time of Day Clock Unit Control Word Virtual Storage Management Zürich | 26.

.The End. Oktober 2004 © 2004 IBM Corporation © 2004 IBM Corporation 40 .. Oktober 2004 Zürich | 26.any Questions? Zürich | 26.

Sign up to vote on this title
UsefulNot useful