Summary of changes
Summary of changes for the z/OS installation planner
Changes in z/OS V2R1 updates for September 2014
Changes in z/OS V2R1
Changes in z/OS V1R13 updates for September 2012
Changes in z/OS V1R13
Changes in z/OS V1R12
Learning about z/OS
Introduction to z/OS elements and features
List of base elements and optional features
Where are they now?
Two-year release cycle
Methods of installing z/OS
ServerPac (entitled with z/OS)
Product ServerPac
CBPDO (entitled with z/OS)
SystemPac (additional charge with z/OS)
Other fee-based methods (additional charge with z/OS)
Web deliverable method
Languages in which z/OS is available
Coexistence and fallback
Understanding coexistence
Rolling z/OS across a multisystem configuration
Understanding fallback
Which releases are supported for coexistence, fallback, and migration?
Platform (integration) testing by IBM
Service
Service policy
ServerPac and Product ServerPac service level
CBPDO service level
SystemPac service level
z/OS Web deliverables service level
PSP information
Consolidated service testing by IBM
Maintenance after installation
Service distribution
Shopz
SMP/E Internet Service Retrieval
SystemPac SFS
RefreshPac (fee offering)
Education and training
Choosing the software installation and delivery methods
Choosing an installation package for installing z/OS
Installing z/OS without using an installation package
Choosing the delivery medium: tape, DVD, or Internet
Choosing the Internet download method: direct or intermediate
Security of your Internet order
Network security
Preparing the driving system
What is the Customized Offerings Driver?
Identifying driving system software requirements for installing z/OS using ServerPac or dump-by-data-set SystemPac
Preparing for installation
Identifying driving system software requirements for installing z/OS using full volume dump SystemPac
Identifying driving system software requirements for installing z/OS using CBPDO
Driving system Wave 0 requirements
Driving system Wave 1 requirements
Driving system Wave 2 requirements
Identifying driving system software requirements for installing subsystems
Identifying driving system hardware requirements
Preparing the target system
Choosing software products to install and identifying requisites
Choosing the z/OS base and optional features
Alternate base
Identifying functional requisites for z/OS elements and features
Choosing IBM products that you want to run with z/OS
Choosing ISV products that you want to run with z/OS
Planning for the system identifier for z/OS
Ordering z/OS and related IBM products
The Internet delivery process
Identifying hardware requirements for the target system
Identifying server requirements
Processor storage
PSP hardware upgrade identifiers
Identifying DASD space requirements
Identifying I/O device requirements
Identifying service needed for the target system
If you are installing a z/OS ServerPac or Product ServerPac order . . .
If you are installing a z/OS CBPDO order...
If you are installing a z/OS SystemPac order...
If you are installing a System z server...
Using JES and SDSF with z/OS V2R1
ServerPac and SystemPac delivery of JES2, JES3, and SDSF
Using the z/OS Font Collection with V2R1
Preparing for customization and test
Customizing for CEA
Using dynamic enablement
Deciding whether to dynamically enable
Dynamic enablement Step 1: Notify IBM
Dynamic enablement Step 2: Update parmlib
z/OS priced features and TCP/IP
GDDM-PGF product
HLASM Toolkit feature
DCF product
Dynamic enablement Step 3: Establish the active parmlib member
Disabling what was enabled
Scheduling test activities
Preparing for future installations
System and installation requirements
Separating data from software
Placing data sets on specific volumes
Product sets
Introducing product sets
Characteristics of a product set
Which product sets are appropriate?
Product set for z/OS and closely-related products
Subsystem product sets
Licensed product sets
Vendor product sets
Recommended data set placement
SMP/E global data sets
Target libraries (TLIBs)
TLIB volume 1 (TVOL1)
TLIB volume 2 (TVOL2) through TLIB volume n (TVOLn)
HFS or zFS target volume
Licensed product target volume
Vendor product target volume
Subsystem target volume
Distribution libraries (DLIBs)
DLIB volumes for TVOL1, TVOL2 through TVOLn, HFS, and zFS
DLIB volume for licensed products
DLIB volume for vendor products
DLIB volumes for subsystems
Image-related data sets
Page data set volume 1
Page data set volumes 2-n
HFS or zFS customization volume
Cluster-related data sets
Master catalog volume
JES2 checkpoint volume
JES2 spool volume
Sysplex-related volume 1
Sysplex-related volume 2
Softcopy volume
Implementing the recommended data set placements
Decide whether to merge data sets
Determine which data sets to move and where to move them
Choose a volume serial naming convention if you plan to use indirect volume serial support
Decide whether to use your existing master catalog
Move data sets to appropriate volumes
Update SMP/E DDDEFs
Update catalog entries to point to appropriate volumes
Update IEASYMxx in your parmlib
If using ServerPac or SystemPac (dump-by-data-set format), save your configuration for the next release
Update any environmentals that are applicable
Choosing a naming convention for data sets
Using symbolic substitution
Using indirect catalog entries
Using parmlib concatenation (logical parmlib)
DASD space utilization and performance
Undefined record format data sets
Using recommended block sizes for z/OS data sets
Installation checklist
Step 1. Plan the details
Step 2. Order hardware and software
Step 3. If upgrading, prepare the current environment (old target system) for the new release
Step 4. Build the driving system
Step 5. Build and verify the target system
Step 6. Customize and test the target system
Step 7. Put the tested system into production (cut over to production)
Step 8. If upgrading, perform postmigration customization
Software requirements for running z/OS V2R1
Hardware requirements for running z/OS V2R1
Hardware Requirements for Communications Server
IP Hardware Requirements
Network Attachments
Miscellaneous IP hardware requirements
SNA Hardware Requirements
Making a copy of your system software (cloning)
Choosing names
Initializing the new volumes
Setting up SMS
Defining new catalogs and CSI data sets
Copying the software data sets
Copying the SMP/E zones
Making the copy usable
Testing
Migrating to another system
Accessibility