Planning
This chapter provides you with an outline of the milestones to perform the initial build and the associated activities to achieve them. The tasks are divided into phases. A cross-reference table is provided at the end of the chapter to clarify the process.
3.1 Process overview
The hardware is now officially handed over to us. We stand in front of the hardware, holding a few sheets of paper, DVDs, and manuals.
What is next?
We must define milestones so we can see the journey that leads to us loading the system.
3.1.1 Milestones
An overview of the process we undertook is shown in Figure 3-1. Building more operational environments is described in Mainframe from Scratch Volume 2 Operational Deployments, SG24-8337.
Figure 3-1 Initial build milestones
Milestone 1: Creating a configuration for the COD system
The Customized Offering Driver (COD) system is shipped with a pre-generated configuration. To use the COD, we must configure a few hardware devices to match the COD’s pre-generated configuration. We create an input/output configuration data set (IOCDS) and make that data set available for the COD system to use. This task requires us to use the stand-alone IOCP via the Hardware Management Console (HMC).
After the I/O Exerciser Tool is configured, you can use the tool to verify that the physical connections are working. Although the configuration might be correct, the I/Os can fail if a cable was damaged during installation.
|
Note: Stand-alone activities are not part of every day activities. The more prepared you are, the more likely you are to succeed. We suggest that you read Stand-Alone Input/Output Program User’s Guide, SB10-7166-00, and have a copy of this publication readily available for reference purposes.
|
Milestone 2: Stand-alone restore of the COD
The COD system’s documentation guides you through the stand-alone restore of the DVDs to three disk drives that you configured for the previous milestone. We also define a console and a terminal on the Open Systems Adapter (OSA) card to initially program load (IPL) and log on to the COD system.
After the COD system is restored and initially loaded, the z/OS operating system provides more tools to make further modifications to the configuration.
Milestone 3: Expanding the hardware configuration
We use the hardware configuration definition (HCD) on the COD’s z/OS system to define more devices to the configuration in preparation for the ServerPacs. Initially, we defined sufficient devices to load the COD. We must expand the number of devices to be used for the following components:
•New z/OS we are about to build by using the z/OS ServerPac
•Operational environment
•Extra applications
•New LPARs
Milestone 4: Installing the z/OS ServerPac
We use the COD system to install the z/OS ServerPac. This task requires selecting options from the ServerPac’s customization panels. The procedures generate batch jobs to align with the choices. The jobs run on the COD system to build the files that are required to create a full z/OS V2R2 operating system.
Milestone 5: Loading the new z/OS system and running the IVPs
We load the z/OS V2R2 system and run the supplied Installation Verification Programs (IVP). We now have a running z/OS V2R2 system with which to work.
Milestone 6: Installing the DB2 ServerPac
We install the DB2 ServerPac system, but we use the new z/OS system that we just built to run the jobs.
Milestone 7: Loading the new DB2 system and running the IVPs
We load the DB2 subsystem and run the supplied IVPs. We now have a running z/OS V2R2 system with a DB2 subsystem active.
3.1.2 Phases
The tasks to achieve the milestones are divide into 12 phases, which are described next.
Phase 1: Preparing IBM z13
This phase might not be required because it depends on how the z13 is handed over to you. Establish the status of the machine. Ask the z13 installer if the following tasks were successfully completed:
•The z13 had a successful Power-on Reset (POR) by using the IOCDS D0.
•The Support Element (SE) and the HMC are physically connected.
•The SE is defined to the HMC.
Phase 1 is required only if any of these tasks are still outstanding. We show you how to perform the tasks that are necessary to achieve this status.
Phase 2: Configuring stand-alone hardware
There is no operating system available at this point; therefore, we use the stand-alone capabilities of the IOCP to build the initial configuration via the HMC. The following tasks are required:
•Define a minimum z13 input/output configuration to meet the COD requirements.
•Build an IOCDS on SE slot A0 and perform a POR from it.
•Define and activate COD z/OS driving system LPAR.
Phase 3: Setting up DS8000 logical configuration
In our controlled laboratory, we used a DS8000 for the disk configuration. You might have a different disk subsystem; therefore, you must follow the instructions from your supplier. The approach is similar.
The following tasks must be completed:
•Set up a configuration worksheet to plan your disk configuration. Check the supplied COD configuration to ensure address compatibility.
•Configure the disks and control units as per the configuration worksheet.
Phase 4: Configuring OSA-ICC and TN3270
This phase concentrates on communications. The Open Systems Adapter is setup as an Integrated Console Controller (OSA-ICC) in the z13. This configuration provides 3270 emulation to the operating system and TN3270 server functionality to the network. The following tasks must be completed:
•Define and configure the OSA-ICC channel.
•Configure the TN3270 session by using the HMC 3270 emulation function or IBM Personal Communication (PCOMM).
The addresses that are generated must match the addresses within the range of the COD’s pre-generated system.
A console for operating system communication is necessary. Also, a terminal must be defined to use for logging on to Time Sharing Option (TSO).
Phase 5: Restoring stand-alone COD
The COD is shipped on three DVDs and each DVD is restored to a disk. Each disk address must be known to the COD’s pre-generated configuration.
Restore COD DVDs onto three DASD volumes by using DFSMSdss Stand-Alone Services.
Each COD DVD is shipped in a DFSMSdss physical memory dump format and has a copy of the DFSMSdss stand-alone program, so you can load the stand-alone restore service from the DVD.
Phase 6: IPLing the COD system
We are now in a position to IPL the COD system. The process includes the following key steps:
1. Activate the COD LPAR.
2. IPL the COD.
3. Ensure that the console is working correctly.
4. Establish a TSO session.
Phase 7: Expanding the configuration
The COD system is a z/OS system, but it is to be used as a driver system only. Therefore, it is a small, pre-generated configuration. We are preparing the configuration to receive the ServerPac and build a new z/OS V2R2 system that can be customized to accommodate more software products and a basic operational set-up. The following tasks are required:
•Create more disk volumes that are available on DS8000 DASD subsystem.
•Create and load new IOCDS to match the expanded configuration.
•Make more local 3270 devices available on z13 and z/OS.
•Make TCP/IP connectivity available via TN3270 and TCP/IP
•Add extra SPOOL and Paging space.
You might want to add more devices than we do in our example. How many you add depends on your circumstances and requirements.
Phase 8: Preparing ServerPac installation
Although we include ordering and receiving the z/OS V2R2 ServerPac here, we suggest that you complete these tasks in advance. The ServerPac can be shipped to you on DVD or you can chose to download your order. If your data center is new one, you might not have the network connectivity to download the order. We are using the DVDs in our controlled laboratory environment.
The following steps must be completed:
1. Order and receive the z/OS V2R2 ServerPac.
2. Plan the ServerPac installation option and layout.
3. Prepare the COD installation environment.
4. Prepare the installation media and upload into the COD driver.
5. Connect to the CustomPac Installation Dialog for the next phase.
Phase 9: Building z/OS V2R2 ServerPac
We are processing the ServerPac to build the new z/OS V2R2 system. Each ServerPac is well-documented and is specific to each ServerPac order and shipment. We took a basic software configuration. Although your jobs can differ from ours, they can be similar.
The following steps must be completed:
1. Receive a new ServerPac order.
2. Create the work configuration.
3. Tailor the work configuration for the target system.
4. Generate the installation job stream.
5. Submit the installation job stream and check return code.
6. Save the work configuration after the order is installed.
Phase 10: First IPL and IVPs
The first IPL of the newly built z/OS system is the primary goal. After the IPL is complete, we run the IVPs to provide initial testing and base verification that the ServerPac process worked successfully.
The following tasks must be completed:
•Pre-IPL jobs and tasks: Jobs that prepare the system for IPL such as setting up IODF, parmlib, and stand-alone memory dump.
•IPL your new target system.
•Postinstallation from target system: These postinstallation jobs must run on the target system. They perform initial setup of many of the products that are contained in your order.
•Installation verification: These product-supplied jobs verify a successful installation and must run on the target system.
•Completing the installation: These jobs perform installation cleanup, such as System Specific Alias (SSA) removal, that is run after a successful installation of your new target system.
Phase 11: DB2 ServerPac build
We process the DB2 ServerPac to build an initial DB2 subsystem. We run the installation jobstream on the newly generated z/OS system that does not use the COD system.
The following high level tasks are required:
•Plan the DB2 V11 ServerPac installation layout
•Plan the DB2 V11 ServerPac configuration
•Receive the DB2 V11 ServerPac order
•Submit the installation jobs
Phase 12: Start DB2 subsystem
The focus in this phase is to start the DB2 subsystem. After the subsystem starts, we can verify the environment and complete the DB2 V11 ServerPac process.
The following tasks are required:
•Run the installation start up preparation jobs
•Start DB2
•Run the installation verification programs
•Complete the installation
3.1.3 Summary
The phases and milestones that the phases achieve and in which chapter the phase is described are listed in Table 3-1.
Table 3-1 Phases, milestones, and chapters
|
Phase
|
Milestone
|
Chapter
|
|
1 IBM z13 Preparation
|
1 Creating a configuration for the COD system
|
|
|
2 Stand-alone hardware configuration
|
||
|
3 DS8000 logical configuration
|
||
|
4 OSA-ICC and TN3270 configuration
|
||
|
5 COD Restore
|
2 Stand-alone COD restore and IPL
|
|
|
6 IPL the COD system
|
||
|
7 Expand the configuration
|
3 Expand the configuration
|
|
|
8 ServerPac installation preparation
|
4 Installing the z/OS ServerPac
|
|
|
9 z/OS V2R2 ServerPac build
|
||
|
10 First IPL and IVPs
|
5 Loading the new z/OS system and running the IVPs
|
|
|
11 DB2 ServerPac build
|
6 Install the DB2 ServerPac
|
|
|
12 Start DB2 subsystem
|
7 Loading the new DB2 subsystem and running the IVPs
|
The tasks are described in more detail in each chapter. We suggest that you read this IBM Redbooks publication, review the content, and create a plan that is based on your requirements and your planning standards.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.