Introduction
This chapter describes the high-level goals of this book. This book is based on scenarios that the team devised based on experience and best practices.
The scenarios implementation is described in this publication, along with the tools that help implement the configurations that are described.
This chapter includes the following topics:
1.1 High-level goal
The goal of this book is to help you plan for and complete the configuration tasks for a successful installation of an IBM z14 Model ZR1 server. The book covers the planning and preparation tasks that are needed from when a z14 ZR1 is delivered and physically installed up to the point when an LPAR is ready to be activated.
The book is based on two scenarios, and describes the planning considerations and configuration examples in detail from a Hardware Management Console (HMC) and Support Element (SE) and input/output definition file (IODF) perspective.
1.2 Scope
Before you perform the planning and preparation tasks that this book covers, the following tasks must be completed:
Customer’s Configuration Design
Together with your team, IBM provides design and configuration information for the installation of the z14 ZR1 system that you plan to purchase.
IBM Order to Manufacturing
Your IBM representative orders the agreed configuration. IBM makes available for download the machine configuration as a Configuration Report File (CFR). The CFR file can be obtained from the IBM Resource Link website (authentication is required, use your IBM ID) by using a Configuration Control Number (CCN) that is provided by your IBM representative.
Physical installation
With support from IBM, the new order or the upgrade to a z14 ZR1 server is physically installed. This process includes the preparations for and activation of the server in Dynamic Partition Mode (DPM).
HMC/TKE installation
With support from IBM, the HMCs and the (optional) Trusted Key Entry (TKE) workstations are installed and, if necessary, contents, such as user profiles and API settings, are migrated (in a replacement of HMCs and TKEs).
Based on the flowcharts that are shown in Figures 1-1, Figure 1-2 on page 4, and Figure 1-3 on page 5, this book describes the following scenarios when preparing for a z14 ZR1 server installation:
Upgrading an existing IBM Z server to a z14 ZR1
Installing a new z14 ZR1 server
Installing a new z14 ZR1 server to be managed by using Dynamic Partition Manager
Figure 1-1 Topics that are covered in this book
The flowchart that is shown in Figure 1-1 is divided in two main sets of task streams. The upper stream (marked in light yellow) is based on actions that should be performed before the hardware arrives and are not covered in this book. The lower stream (marked in light green) considers the use of a wizard, such as the configuration method that called Dynamic Partition Mode (DPM), which is described next.
1.3 Dynamic Partition Mode
Linux servers, IBM z/VM® and other specific applications ran on mainframe systems for years, but configuration and setup are fairly complicated and require the use of several specific tools. However, with DPM, system administrators now have a quicker and easier way to deploy Linux servers, z/VM LPARs that host Linux guests, or Secure Service Container (SSC) LEPERs that use only the Hardware Management Console (HMC).
DPM is a configuration manager that is designed for setting up and managing Linux servers that run on a mainframe system. On a DPM-enabled system, the runtime environment for your Linux server, your z/VM Hypervisor, or your SSC application is called a partition.
On other platforms, a partition is a portion of the system hard disk drive that you create to run different operating systems on the same disk, or to give the appearance of separate hard disk drives for multiple users or other purposes. On a mainframe system, a partition is a virtual representation of all of the physical hardware resources of that system, which include processors, memory, and input/output (I/O) adapters. On mainframe systems, as on other platforms, an adapter is a physical device that connects the system to other computers or devices.
 
Note: DPM mode cannot coexist with standard PR/SM mode. When DPM mode is used, only z/VM, Linux, and SSC partitions1 (LPARs) and connections to them can be defined.

1 For DPM, the term partition is equivalent to Logical Partition (LPAR).
The flowchart that is shown in Figure 1-2 is divided in two task streams. The stream on the left side of the flowchart is based on actions that must be performed by IBM on the SEs as preparation before the machine is handed to the customer.
The other stream (right side of the flowchart) is based on definitions that use the DPM wizard in basic mode. Based on the input that is provided to the DPM wizard, a configuration is activated that is used on the z14 ZR1 and the devices that are attached to the server. The actions that are defined in the two streams must be performed in sequence.
Figure 1-2 Installation flowchart DPM mode (applicable to both scenarios)
The flowchart that is shown in Figure 1-3 is divided in two task streams. One stream (left side of the flowchart) is based on actions that must be performed on the HMC or on the SEs. The other stream (right side of the flowchart) is based on definitions in the DPM wizard.
Based on the DPM wizard, the surrounding I/O configuration data is created that contains a description of all I/O functions and features that are used on the z14 ZR1 and the devices that are attached to the server. The actions that are defined in the two streams can have dependencies in between.
Figure 1-3 Installation flowchart non-DPM mode (applicable to both upgrade/MES and new system)
The IBM Z server is provided with a management appliance (HMC), which is a physical workstation that runs the HMC application. The HMC communicates with the SE appliance (physically installed in the frame of the z14 ZR1), which is used to communicate with the z14 ZR1 hardware. On the HMC/SE, you must set the number of parameters that allows you to activate a number of logical partitions (LPARs) that run an operating system.
To create an IODF (see Figure 1-2 on page 4), a set of tasks must be done in an application (such as hardware configuration definition [HCD]), which needs a running z/OS system. The IODF can be created on a different system than the target system.
Several HMC/SE and IODF tasks must be planned and prepared. For more information, see I/O Configuration Using z/OS HCD and HCM, SG24-7804.
This book describes what is needed from a HMC/SE, IODF, and DPM from the time when the z14 ZR1 is delivered and physically installed up to the point when an LPAR is ready to be activated. The flowcharts are intended to act as a checklist rather than a step-by-step procedure. Nevertheless, the steps in this book should provide enough information for you to replicate the approach in your environment.
For more information about how to deploy an operating system (z/OS in this case), see Mainframe from Scratch: Hardware Configuration and z/OS Build, SG24-8329.
1.4 Tools
Several tools are provided by IBM that help you to achieve a successful z14 ZR1 server installation. These tools are covered in 2.2, “Tools” on page 9.
Whenever possible, checklists are provided throughout the book that help you go through the steps that are required to complete a specified task.
In addition to the tools and checklists that are provided in this document, it is important that the planning and configuration steps are aligned with other technical departments within your organization, such as storage and network administration, and with the capacity (workload) planning and cryptographic and security teams.
 
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.19.75.133