A z/OS Image IPL – Step by Step, by Step, by Step
Project and Program:
Enterprise-wide,
zNextGen Project
Tags:
Proceedings ,
SHARE Providence 2017 ,
2017
In this presentation each step of a typical z/OS Image IPL with be deconstructed and explained. Beginning at the ‘Back Door’ of a z System Mainframe, the presenter will explain the role of the components beginning with the tool set used in a Power-On-Reset (POR) - System Element (SE), Hardware Configuration Definition (HCD) and Hardware Configuration Manager (HCM). Next, the role played by the ‘Partition Builders’ – IODF/IOCP (Input/Output Configuration Program) and PR/SM (Processor Resource/System Manager) - in subdividing the z System Hardware into z/OS and z/VM Logical Partitions (LPARs).
With an LPAR built, the presenter will move on to explain the elements required – Unit Address, LOADPARM - to initiate a unique instance of a z/OS Image. Next the LOADPARM will be deconstructed into its elements – IODF Volume, LOAD Member Suffix, Message Suppression Indicator, and Nucleus Suffix. The presenter will then elaborate on the ‘Boot-Strap Process’ kicked-off by the value provided by the Unit Address – AKA the SysRes Volume.
With the IPL process now well underway, the presentation will focus on finding and interpreting the content of the LOADxx Member, for example – IODFDSN, SYSCAT, NUCLST – and the advantages of LOADxx filtering in the final determination of – PARMLIB, IEASYSxx, IEASYMxx – all leading to a discussion of IEASYS Directors and Parameters.
The balance of the presentation will focus on the resulting values of critical integrity definitions and components – APFList, LNKList, LPAList, SVC’s, EXIT’s and The Program Properties Table (PPT).-Glennon Bagsby-NewEra Software, Inc.
Back to Proceedings File Library