Phase 9: ServerPac Build of z/OS V2R2
This chapter describes the process that is used to install the z/OS V2R2 ServerPac order through CustomPac Installation Dialog by using the Customized Offering Driver (COD) system.
In the installation process, we receive and install the order by providing variables, defining volume layout, and modifying the data sets destination and attributes. Then, we create a serial of job stream for later submission.
This chapter includes the following topics:
12.1 Goals
Phase 9 features the following goals:
•Receive a new ServerPac order
•Create the work configuration
•Tailor the work configuration for the target system
•Generate the installation job stream
•Submit the installation job stream and check return code
•Save the work configuration after the order is installed
Phase 9 is required to achieve milestone 4: Installing the z/OS ServerPac. Where this milestone is positioned in the overall process is shown in Figure 12-1.
Figure 12-1 Phase 9 Milestone 4

As described in Chapter 11, “Phase 8: ServerPac installation preparation” on page 171, we ran the LOADRIM job to unload the CustomPac Installation Dialog in the driving system. The Dialog is used to tailor the ServerPac configuration to match your own system environment.
Then, the Dialog uses the tailored configuration to generate a customized installation job stream that creates the target system from the ServerPac order. The installation process allocates the data sets on the volumes from driving system and restores the ServerPac contents from the temporary UNIX file systems into those data sets, as shown in Figure 12-2 on page 185.
Figure 12-2 ServerPac installation
 
Note: You can use the CustomPac Installation Dialog as the main master dialog to install different ServerPac orders, such as z/OS, DB2, or IBM CICS® products. We suggest that you separate the master CustomPac Installation dialog data sets and the order-related data sets by using a different HLQ and middle qualifier.
The important terms that are used in this chapter are listed in Table 12-1.
Table 12-1 Important terms
Term
Meaning
Driver/Driving system
The system that you use to install the order; that is, the COD.
Target System
The system that you are creating.
Ready to run
The product requires no extra installation tasks.
12.2 Requirements
We completed the tasks that are described in Chapter 11, “Phase 8: ServerPac installation preparation” on page 171 to upload the ServerPac content and load the master CustomPac Installation Dialog. In this chapter, we continue the installation of the z/OS V2R2 ServerPac order.
12.2.1 COD System Readiness checklist
To continue the installation, our driving system must meet the following prerequisites:
•Customized Offering driving system is initially loaded and active.
•Personal Communication software is installed in the workstation.
•UNIX file system in the driving system is active. Check the status by issuing the D OMVS,F command.
•RACF profiles are defined for IBMUSER in driving system to access resources.
•SMS configuration is running with null configuration is acceptable. Check the SMS status by issuing the D SMS command.
•Volumes are reserved for target system and can be accessed from driving system. Check the state by issuing the D U,,,xxxx,nn command, where xxxx is the starting I/O device number for target system volume, and nn is the number of volumes that you want to check.
•CustomPac Installation Dialog is restored.
12.3 Related documents
For more information, see the following IBM publications:
•ServerPac: Installing Your Order Number: OS2xxxx
•ServerPac: Using the Installation Dialog, SA23-2278-02
•z/OS V2R2 Planning for Installation, GA32-08890-05
•CustomPac Installation Dialog Reference Manual
ServerPac: Installing Your Order Number: OS2xxxx is produced by IBM to match your order and is unique.
The ServerPac FAQ document contains frequently asked questions about ServerPac and is available at this website:
12.4 Planning the ServerPac installation configuration
By using the CustomPac installation dialog, the ServerPac order configuration can be tailored to the environment with the following inputs:
•Global Variables: HFS/zFS information, and so on
•Volumes: Names, device type, and number
•Data sets: Names, placement on volume, and space
•Catalogs: Names and System Specific Aliases (SSAs)
•Aliases: Associate to catalog
•Zones: SMP/E CSI and zone names
To keep the process simple, we adopt a policy of taking the default ServerPac variable settings where we can and make as few modifications as possible.
Next, we describe the variables and settings that you must set.
12.5 Receiving the z/OS V2R2 order
Start the CustomPac Installation Dialog, choose the R RECEIVE option to supply the information that is necessary to generate the RECEIVE job that obtains your order.
We select option F to use the file system to receive the order and OS220149 for our severpac order name, as shown in Figure 12-3.
CustomPac --------------------- Receive an Order -----------------------------
COMMAND ==>
Receive the order from ==> F F - File system
S - Server
T - Tape
Order Number ==> OS220149
 
------------- Order Dialog Data Set Allocation Information -----------------
Data Set Qualifiers ==> CPAC.ZOSV2R2 (Must be unique)
Volume Serial ==> M0SIN2 (Blank for SMS-managed data sets)
- or -
STORCLAS ==> (Blank for non-SMS-managed data sets)
Specify a data class for SMS or non-SMS managed data sets (optional).
DATACLAS ==>
Specify a management class for only SMS managed data sets (optional).
MGMTCLAS ==>
Dialog CLIST Record Format ==> FB (FB or VB)
Target Directory ==> /serverpac/zosv2r2/
 
Figure 12-3 Receiving an order
We also choose CPAC.ZOSV2R2 as our own data set qualifiers for this specific z/OS V2R2 order, which must be unique in the driving system and cataloged in one user catalog for easily connecting and disconnecting between the driving system and target system. The ServerPac order data sets are placed on volume M0SIN2 following our ServerPac Installation Layout that is described in Chapter 11, “Phase 8: ServerPac installation preparation” on page 171.
We provide the UNIX path location (/serverpac/zosv2r2/) as the Target Directory, which is where the z/OS ServerPac DVD content was uploaded, as described in Chapter 11, “Phase 8: ServerPac installation preparation” on page 171. You can also choose to receive order from FTP server or tape driver.
Press Enter and one job is generated. Submit the job to receive the order.
12.6 Installing the z/OS V2R2 order
After the order is successfully received, select the I INSTALL option from the main panel to proceed with creating the work configuration and generating the installation job stream that is used to create the target system, as shown in Figure 12-4.
CustomPac --------------------- IBM Corporation --------------------- 27.10.18
OPTION ==> I
CustomPac Order Management Menu
R RECEIVE - Receive an Order
I INSTALL - Install an Order
Order Number ==> OS220149 (Leave blank to list uninstalled orders)
D DISPLAY - Select Orders to Display
Master dialog data set qualifiers: CPAC.OS220149
This dialog supports secure Internet delivery.
********************************************************
* 5751-CS4, 5751-CS5, 5751-CS6, 5751-CS7 and 5751-CS9 *
* Copyright IBM Corp. 1988, 2015 *
********************************************************
Figure 12-4 Installing an order
12.6.1 Creating the work configuration
The first step to install one order is to create the work configuration and save the variables for next few steps. The order status can be: Shipped, Work, Saved, Started, by selecting the D Display option in the main panel of CustomPac Installation Dialog.
We choose the Full System Replacement method and install and merge JES2 into BCP in our configuration, as shown in Figure 12-5 on page 189.
 
CustomPac -------- Installation Options for Order ( OS220149 ) ----------------
OPTION ==> C
Complete these options to install the order:
C Create Create the Work Configuration
* Variables Specify Values for Variables
* Zones Specify SMPTLIB and SMP/E Zone Names Information
* Modify Modify the System Layout
* Alias Specify Catalogs for High-Level Qualifiers
* SSA Specify Temporary Aliases (SSAs) for Catalogs
* Installation Create and Submit Installation Jobs
You can use Save any time after creating the work configuration:
OPTION ==> F
Select the Install type :
F - Full System Replacement installs a complete new IPL-able
stand-alone system including all SMP/E-maintained libraries, SMP/E
environment, operational data sets, and CustomPac sample data sets.
The supplied operational data sets must be merged with or replaced
by production operational data sets before the new system is used
in production.
S - Software Upgrade installs only the SMP/E-maintained libraries,
SMP/E zones, and CustomPac sample data sets. Operational data sets,
including system control files (like LOGREC and VTAMLST), a security
system database, and a master catalog must exist. These
existing operational data sets must be updated as required for new
products and product changes before the first IPL.
Choose JES elements to be installed:
JES Elements to Install ==> JES2 (JES2, JES3, or BOTH)
Specify options for merging SMP/E target and DLIB zones:
Merge JES2 Zones into BCP Zone ==> Y (Y or N)
Figure 12-5 Installation options for the order
Then, enter CR create at the command line to create one work configuration (see Figure 12-6 on page 190). If a duplicate configuration is found, the dialog prompts you to confirm the deletion and recreation of the same name configuration. However, use care when performing this task because after your work configuration is overridden, the previous input is lost.
COMMAND ==> cr SCROLL ==> PAGE
Select Configuration
Primary Commands:(? SET Locate Find Next Previous SORT CReate)
Line Commands:(Select)
S CONFiguration Comment
- ----------------------------------- ----------------------------------------
* CPAC.ZOSV2R2 Always Selected for Order
- ----------------------------------- ----------------------------------------
** NO MERGABLE ORDER CONFIGURATIONS
 
Figure 12-6 Creating the work configuration
12.6.2 Specifying variable values
The variables that are used by the dialog obtain information about the driving and target systems, such as name and location of master catalog, RACF databases, naming conventions (for spool volume and work volume), file system directory for installing the target file system, jobcard information, and so on.
You can change the variables as you want or keep the default settings. The following variables are important:
•Installation directory
The /Service/ installation directory is the mount point on the driving system where the target system root file system is mounted. This directory is not your ServerPac temporary directory that we provided in the Receive Order option panel. Keep the default or create a directory in the driving system’s UNIX file system; then, specify it here.
•SMPWKDIR directory
The /tmp SMPWDIR directory is the temporary directory that is used by GIMUNZIP program to unpax the Pax ServerPac contents during restore job running. It requires a large amount of space; therefore, mount one larger file system to /tmp first if the driving system uses TFS file system for this mount point.
ServerPac includes the recommended primary and secondary values for SMPWKDIR file system allocation. These values include the variables PRIMARY CYLS and SECONDARY CYLS. If you set the value of the variable ALLOCATE SMPWKDIR to YES, ServerPac generates steps to allocate and mount the SMPWKDIR file system in the RESTORE job. If ALLOCATE SMPWKDIR value is set to NO, ServerPac generates a step to verify adequate space in the SMPWKDIR directory. If there is not enough space, the RESTORE job fails.
•SYSNAME: CPAC
If you change this value from the default (CPAC), you must also change the value of SYSNAME in the IEASYSxx member that is used to initially load the target system. For a full system replacement, changing the SYSNAME value requires that you update the system name list in the SMS Base Configuration (by using ISMF after you load the ServerPac system). Then, you must activate the changed SMS configuration before you can use SMS.
•EXISTING IODF
SYS1.IODF00 must include the operating system configuration that is used for the ServerPac load.
•VOLSER OLD CAT
This variable is the catalog volume of the driver.
•ORDER HLQ
This variable is the order’s HLQ, which must be different from your master dialog name HLQ.MLQ.
•OLD MASTERCAT
This variable is the driver’s master catalog. For this z/OS V1.13 COD driver, CATALOG.MVSICFM.VD9ECA is used.
For more information about other variables, see the ServerPac: Using the Installation Dialog manual.
12.6.3 Specifying SMP/E zone names
Change the Data Set prefix, volume label per ServerPac Installation Layout, and keep other variables as default, as shown in Figure 12-7.
CustomPac -------- Define SMPTLIB and Zone Names ( OS220149 ) Row 1 to 1 of 1
COMMAND ==> SAVE SCROLL ==> PAGE
Primary Commands:(? CANcel SAVE)
Line Commands:(elemenTs Fmids)
--------------------------- SMPTLIB Information ---------------------------
Data set Prefix ==> SMPE.ZOSV2R2
SMS Managed ==> No (Yes/No)
Device Type ==> 3390
Volume(s) ==> M0SIN2 ==> ==> ==> ==>
--------------------------- Zone Names Information ------------------------
S Nickname DLIB Zone Target Zone SST
- -------- --------- ----------- ----
100 MVSD100 MVST100 MVS
******************************* Bottom of data *******************************
Figure 12-7 Defining SMPTLIB and zone names
12.6.4 Modifying system layout
The Modify System Layout (MSL) option is where the most time is spent when the dialog is used. Here, we can assign data sets to volumes, change data set attributes, and so on. The ServerPac dialog option to create a recommended system layout (RSL) helps get to this recommended system layout.
Because you might use different device models or order products other than z/OS in your ServerPac, IBM does not include a pre-configured RSL. Instead, an RSL is created for you by using information that you provide in the dialog. Then, the dialog assigns data sets to physical volumes automatically. The intent is to have a quick and easy way to distribute data sets among physical volumes.
Logical volumes are assigned in the background. As data sets are assigned, the dialog fills each volume up to 85% full the first time that they are used and up to 90% full when they are used later. This configuration makes it less likely that volumes run out of space and more likely that similar data sets can be on the same volumes.
The View and Change facility makes it easier to change data sets and their attributes. We can create customized lists of data sets in the configuration; then, use these lists as targets for CHANGE and MERGE commands. There are many data set attributes that we can use to customize our own data set lists, such as element type, LNKLST eligible, LPA eligible, and required in master catalog.
First, in the Modify System Layout panel, we choose option A to allow the CustomPac installation dialog to create an RLS for us. Then, we must enter the volume type and volume label as described in Chapter 11, “Phase 8: ServerPac installation preparation” on page 171 (see Figure 12-8).
CustomPac -------- Automatic Data Set Assignment ( OS220149 ) Row 1 to 3 of 3
COMMAND ==> SCROLL ==> PAGE
Current Volume Configuration Scope ==> ALL
Primary Commands:(? Reset CReate)
Line Commands:(Select Insert List Move After Before eXclude)
Phys. Volume Sequence Device Used + Volume Existing Reserved
S Volume Type Number Type Reserved Threshold Data Space
- ------ ------ -------- -------- -------- --------- -------- --------
MVSRES TARGET T01 3390-9 173 % 85 % 0 % 0 %
MVSDLB DLIB D01 3390-9 156 % 85 % 0 % 0 %
MVSCAT BOTH B01 3390-9 37 % 85 % 0 % 0 %
*******************************Bottom of Data*********************************
 
Figure 12-8 Default Automatic Data Set Assignment panel
Then, we choose to change the physical volume label, enter S in the S column before each Physical Volume line, as shown in Figure 12-9.
CustomPac -------- Automatic Data Set Assignment ( OS220149 ) Row 1 to 3 of 3
COMMAND ==> SCROLL ==> PAGE
Current Volume Configuration Scope ==> ALL
Primary Commands:(? Reset CReate)
Line Commands:(Select Insert List Move After Before eXclude)
Phys. Volume Sequence Device Used + Volume Existing Reserved
S Volume Type Number Type Reserved Threshold Data Space
- ------ ------ -------- -------- -------- --------- -------- --------
S MVSRES TARGET T01 3390-9 173 % 85 % 0 % 0 %
S MVSDLB DLIB D01 3390-9 156 % 85 % 0 % 0 %
S MVSCAT BOTH B01 3390-9 37 % 85 % 0 % 0 %
Figure 12-9 Changing the Physical Volume label
Then, we enter our planned volume information (label and model), as shown in Figure 12-10.
COMMAND ==>
Display and Change Volume Attributes
Volume Serial ==> M0SR21 (Always required)
Volume Type : TARGET (Target, DLIB or Both)
Device Type ==> 3390-27 (For example, 3390-9)
Reserved Space ==> 3000 (Cylinders)
Initialize Volume ==> Y (Y or N. Default is Y)
 
Display and Change Volume Attributes
Volume Serial ==> M0SD21 (Always required)
Volume Type ==> DLIB (Target, DLIB or Both - Always required)
Device Type ==> 3390-27 (For example, 3390-9)
Reserved Space ==> 3000 (Cylinders)
Initialize Volume ==> Y (Y or N. Default is Y)
 
Display and Change Volume Attributes
Volume Serial ==> M0SCT1 (Always required)
Volume Type ==> BOTH (Target, DLIB or Both - Always required)
Device Type ==> 3390-27 (For example, 3390-9)
Reserved Space ==> 3000 (Cylinders)
Initialize Volume ==> Y (Y or N. Default is Y)
Figure 12-10 Changing Physical Volume label and device type
The physical volume information is changed, as shown in Figure 12-11.
CustomPac -------- Automatic Data Set Assignment ( OS220149 ) Row 1 to 3 of 3
COMMAND ==> SCROLL ==> PAGE
Current Volume Configuration Scope ==> ALL
Primary Commands:(? Reset CReate)
Line Commands:(Select Insert List Move After Before eXclude)
Phys. Volume Sequence Device Used + Volume Existing Reserved
S Volume Type Number Type Reserved Threshold Data Space
- ------ ------ -------- -------- -------- --------- -------- --------
M0SR21 TARGET T01 3390-27 61 % 85 % 0 % 9 %
M0SD21 DLIB D01 3390-27 56 % 85 % 0 % 9 %
M0SCT1 BOTH B01 3390-27 20 % 85 % 0 % 9 %
*******************************Bottom of Data*********************************
Figure 12-11 Customized Automatic Data Set Assignment panel
If you want to add volumes to the data set assignment candidate list, enter the I INSERT line command, as shown in Figure 12-12.
CustomPac -------- Automatic Data Set Assignment ( OS220149 ) Row 1 to 5 of 5
COMMAND ==> SCROLL ==> PAGE
Current Volume Configuration Scope ==> ALL
Primary Commands:(? Reset CReate)
Line Commands:(Select Insert List Move After Before eXclude)
Phys. Volume Sequence Device Used + Volume Existing Reserved
S Volume Type Number Type Reserved Threshold Data Space
- ------ ------ -------- -------- -------- --------- -------- --------
M0SR21 TARGET T01 3390-27 61 % 85 % 0 % 9 %
M0SD21 DLIB D01 3390-27 56 % 85 % 0 % 9 %
M0SCT1 BOTH B01 3390-27 20 % 85 % 0 % 9 %
M0SIN1 BOTH B02 3390-001 8 % 85 % 0 % 8 %
I M0SIN2 BOTH B03 3390-001 8 % 85 % 0 % 8 %
 
Display and Change Volume Attributes
Volume Serial ==> M0SUX1 (Always required)
Volume Type ==> BOTH (Target, DLIB or Both - Always required)
Device Type ==> 3390-27 (For example, 3390-9)
Reserved Space ==> 3000 (Cylinders)
Initialize Volume ==> Y (Y or N. Default is Y)
 
Current Volume Configuration Scope ==> ALL
Primary Commands:(? Reset CReate)
Line Commands:(Select Insert List Move After Before eXclude)
Phys. Volume Sequence Device Used + Volume Existing Reserved
S Volume Type Number Type Reserved Threshold Data Space
- ------ ------ -------- -------- -------- --------- -------- --------
M0SR21 TARGET T01 3390-27 61 % 85 % 0 % 9 %
M0SD21 DLIB D01 3390-27 56 % 85 % 0 % 9 %
M0SCT1 BOTH B01 3390-27 20 % 85 % 0 % 9 %
M0SIN1 BOTH B02 3390-001 8 % 85 % 0 % 8 %
M0SIN2 BOTH B03 3390-001 8 % 85 % 0 % 8 %
M0SUX1 BOTH B04 3390-27 9 % 85 % 0 % 9 %
*******************************Bottom of Data*********************************
Figure 12-12 Adding Physical Volume into the Data Sets Distribution list
Another scenario is that we want to move all ZFS and HFS data sets into one separate volume (M0SUX1) and move all VSAM data sets from SYSRES to another volume (M0SCT1). We complete the following steps to change the volumes for those specific ZFS/VSAM data sets from the default volumes to other volumes:
1. Select C (View and Change data sets by selected attributes).
2. Select Data Set Type.
3. Select ZFS.
4. In the command line, enter the commands that are shown in Example 12-1 to change their default physical volumes to the volume we want (see Figure 12-13).
Example 12-1 Changing physical volume commands
CH PVOL OP M0SUX1
CH PVOL TARGET M0SUX1
CH PVOL DLIB M0SUX1
 
CustomPac --------------- Data Set List ( OS220149 ) --------- Row 1 to 9 of 9
COMMAND ==> CH PVOL TARGET M0SUX1 SCROLL ==> PAGE
Data Set List for: Data Set Type
Primary Commands:(? SET Locate Find Next Previous SORT CHange OFile OList
FindComp)
Line Commands:(Merge eXpand Conflict Unmerge Select Insert Delete)
Physical
S Data Set Name Selected Value Volume
- ------------------------------------------- ----------------------- --------
FNT.OMVS.HFS ZFS M0SRS1
HKC.HKCCFGFZ ZFS M0SCT1
HKC.HKCDATFZ ZFS M0SCT1
HKC.HKCLOGFZ ZFS M0SCT1
OMVS.ETC ZFS M0SCT1
OMVS.ROOT ZFS M0SRS1
OMVS.SCFZHFS2 ZFS M0SCT1
OMVS.SIZUUSRD ZFS M0SRS1
OMVS.VAR ZFS M0SCT1
*******************************Bottom of Data*********************************
Figure 12-13 Changing the OMVS data sets volume destination
Another example is to increase the default secondary space. We complete the following steps:
1. Select C (View and Change data sets by selected attributes).
2. Select Secondary Space.
3. Select YES and generate a list of data sets that were shipped with secondary space allocations.
4. Enter CH SP 20 10 in the command line to increase the primary space by 20% and the secondary space by 10%.
By using the X line command, you can exclude data sets that you do not want affected by this change.
12.6.5 Specifying catalogs for Target Data Set HLQ
This option assigns these high-level qualifiers to a catalog. Use the panel that is shown in Figure 12-14 to define a catalog data set name for each of the aliases (high-level qualifiers) in this order. In the first phase, we must define only the master catalog and one user catalog name for our target systems’ data sets. You can define more user catalogs as needed.
CustomPac -------------- ALIAS to CATALOG ( OS220149 ) --------- Row 1 from 34
COMMAND ==> SCROLL ==> PAGE
Define CATALOG Dataset Names
Primary Commands:(? SET Locate Find Next Previous SORT CANcel SAVE)
Line Commands:(Delete Insert Repeat)
S Alias STA Target System Catalog Data Set Name Type
- -------- --- -------------------------------------------- ----
AOP ???????.CATALOG
ASM M ?MASTER.CATALOG MCAT
BDT1 ???????.CATALOG
CBC M ?MASTER.CATALOG MCAT
CDS ???????.CATALOG
CEE M ?MASTER.CATALOG MCAT
CFZ ???????.CATALOG
CPAC M ?MASTER.CATALOG MCAT
CSF M ?MASTER.CATALOG MCAT
FFST M ?MASTER.CATALOG MCAT
 
Figure 12-14 Defining ALIAS to CATALOG
The catalog names initially are shown as “???????” because they are not yet defined. We then specify the catalog names with which an alias is to be associated by entering the question marks or copy and paste the master catalog and user catalog name after each Alias line in the panel that is shown in Figure 12-15 on page 199.
CustomPac -------------- ALIAS to CATALOG ( OS220149 ) --------- Row 1 from 34
COMMAND ==> SCROLL ==> PAGE
Define CATALOG Dataset Names
Primary Commands:(? SET Locate Find Next Previous SORT CANcel SAVE)
Line Commands:(Delete Insert Repeat)
S Alias STA Target System Catalog Data Set Name Type
- -------- --- -------------------------------------------- ----
AOP CATALOG.M0S0.USER
ASM M CATALOG.M0S0.MASTER MCAT
BDT1 CATALOG.M0S0.USER
CBC M CATALOG.M0S0.MASTER MCAT
CDS CATALOG.M0S0.USER
CEE M CATALOG.M0S0.MASTER MCAT
CFZ CATALOG.M0S0.USER
CPAC M CATALOG.M0S0.MASTER MCAT
CSF M CATALOG.M0S0.MASTER MCAT
EOX M CATALOG.M0S0.MASTER MCAT
EOY M CATALOG.M0S0.MASTER MCAT
EPH CATALOG.M0S0.USER
EUVF CATALOG.M0S0.USER
FFST M CATALOG.M0S0.MASTER MCAT
FNT CATALOG.M0S0.USER
GDDM M CATALOG.M0S0.MASTER MCAT
GIM M CATALOG.M0S0.MASTER MCAT
GLD CATALOG.M0S0.USER
GSK CATALOG.M0S0.USER
HAP CATALOG.M0S0.USER
HKC CATALOG.M0S0.USER
ICQ CATALOG.M0S0.USER
IOA CATALOG.M0S0.USER
IOE CATALOG.M0S0.USER
ISF M CATALOG.M0S0.MASTER MCAT
ISP M CATALOG.M0S0.MASTER MCAT
IZU CATALOG.M0S0.USER
OMVS CATALOG.M0S0.USER
PAGE M CATALOG.M0S0.MASTER MCAT
REXX M CATALOG.M0S0.MASTER MCAT
SMPE CATALOG.M0S0.USER
SYS1 M CATALOG.M0S0.MASTER MCAT
TCPIP M CATALOG.M0S0.MASTER MCAT
TCPIVP CATALOG.M0S0.USER
PAGE M CATALOG.M0S0.MASTER MCAT
REXX M CATALOG.M0S0.MASTER MCAT
SMPE CATALOG.M0S0.USER
SYS1 M CATALOG.M0S0.MASTER MCAT
TCPIP M CATALOG.M0S0.MASTER MCAT
TCPIVP CATALOG.M0S0.USER
 
Figure 12-15 Defining ALIAS to Target Master and User Catalog
12.6.6 Specifying temporary aliases for catalogs
As shown in Figure 12-16, the system-specific aliases (SSA) option is where we specify the SSA for the target system master catalog and user catalog. These SSAs create aliases in the driving system’s master catalog. SSAs are used by ServerPac so that the driving system data set names do not interfere with the target system data set names.
Figure 12-16 System-specific alias option
We create one alias for the target system’s master catalog and another one for the target system’s user catalog, as shown in Figure 12-17.
CustomPac --------------- SSA to CATALOG ( OS220149 ) -------- Row 1 to 2 of 2
COMMAND ==> SCROLL ==> PAGE
CATALOG Selection List
Primary Commands:(? CANcel SAVE)
Line Commands:(Select)
Allocate Define
| |
S Catalog Name SSA Name Type VOLume | | Unit
- -------------------------------------------- -------- ---- ------ - - ----
CATALOG.M0S0.USER ZOSV22U UCAT M0SCT1 Y Y 3390
CATALOG.M0S0.MASTER ZOSV22M MCAT M0SCT1 Y Y 3390
******************************* Bottom of data *******************************
Figure 12-17 Defining SSA to catalog
12.6.7 Saving work configuration
Choose S to save the current work configuration, as shown in Figure 12-18.
CustomPac -------- Installation Options for Order ( OS220149 ) ----------------
OPTION ==> s
Complete these options to install the order:
C Create Create the Work Configuration
V Variables Specify Values for Variables
Z Zones Specify SMPTLIB and SMP/E Zone Names Information
M Modify Modify the System Layout
A Alias Specify Catalogs for High-Level Qualifiers
SSA SSA Specify Temporary Aliases (SSAs) for Catalogs
I Installation Create and Submit Installation Jobs
You can use Save any time after creating the work configuration:
S Save Save the Current Work Configuration
 
Figure 12-18 Save Work Configuration option
The Save is confirmed, as shown in Figure 12-19.
CustomPac -------------- SAVE Configuration ( OS220149 ) ---------------------
Specify SAVE Library
Enter the High-Level Qualifier and the Volume Serial or Storage
Class of the Library to which the Order Configuration will be saved
Data Set HLQ ==> CPAC.OS220149.D151117.SAVE
Volume Serial ==> M0SIN2 (Blank for SMS-managed data sets)
- or -
STORCLAS ==> (Blank for non-SMS-managed data sets)
The default qualifier used is 'OrderHLQ'.
You may enter a Comment to identify the Configuration. This
is recommended if you use a qualifier other than the default.
==> DEMO SETUP
MASTER HLQ is : CPAC.MASTER
EsssssssssssssssssssssssssssssssssssssN
e CPP0604006I SAVE Request SUCCESSFUL e
DsssssssssssssssssssssssssssssssssssssM
COMMAND ==>
 
Figure 12-19 Save Work Configuration successful
12.7 Submitting installation jobs
After we tailor our ServerPac configuration to match the environment, the ServerPac installation dialog generates a customized job stream that is based on the information we provide. Enter the Installation option by entering I. We then review and submit the installation jobs.
If you find the installation jobs do not fit into your configuration, you can return to the previous options or you can use the VAR primary command to return to the variables options and adjust them before they are submitted. Then, reenter the installation option to issue GEN to regenerate all of the installation jobs.
The installation job stream is generated by the following phases:
•Phase 1: Installation jobs
These jobs are run on the driving system and install your order. When complete, your order is restored to DASD.
•Phase 2: Postinstallation from driving system
These jobs are postinstallation jobs (such as IBM RACF® setup) that must run on the driving system.
•Phase 3: Preinstallation jobs and actions
These jobs prepare the system for initial loading, such as setting up IODF, parmlib, and stand-alone memory dump.
•Phase 4: Initially load your new target system
The steps to initially load your new target system and messages that are displayed during system load.
•Phase 5: Postinstallation from target system
These jobs are postinstallation jobs that must run on the target system. They perform initial setup of many of the products that are contained in your order.
•Phase 6: Installation Verification
These jobs are product-supplied jobs that verify successful installation and must run on the target system.
•Phase 7: Completing the installation
These are jobs that perform installation cleanup, such as SSA removal, that are run after a successful installation of your new target system.
In this chapter, we describe phase 1 and 2. The rest of the phases are described in Chapter 13, “Phase 10: First initial program load of z/OS V2R2” on page 207.
12.7.1 Job stream summary
The types of installation job entries (grouped by category) are listed in Table 12-2.
Table 12-2 Job stream categories
Category
Explanation
SRC
Jobcard that can be edited. Use Select line command to generate SRC entry, which can be changed if necessary.
DOC
Documentation for the following set of jobs. Use Select line command to generate and view DOC entries.
JOB
Installation job that can be submitted. Use “S”elect line command to generate only the selected job that can be submitted. Use “B”ackup if you generated the job.
When we submit a job for running, the job number is written to a processing log. You can capture the job output by writing it to data set SCPPOENU. Doing so requires that you set the installation variable synonym OUTPUT LOGGING to YES.
 
Note: The job name must be the user ID and a character. The default job name is IBMUSER, assuming you log on the driving system as IBMUSER to receive and install the order.
You can add a character after IBMUSER, such as IBMUSERA, to differentiate each job in the JES2 output queue for job output viewing. If you change the job name other than IBMUSERx, you cannot view the job output and get the job return code in the CustomPac Installation dialog panel. You can view the job output through SDSF instead.
In the next sections, we review and submit each job individually.
12.7.2 Starting required VOLUMEs
The OFFLINIT job starts all volumes that you identify in the SUMP primary command in the Modify System Layout option of the CustomPac Installation Dialog. The VTOC and Index size are determined by the 3390 model that you provide in the Modify System Layout panel.
 
Note: OFFLINIT deletes any data on the volumes.
Before running this job, ensure that the devices were varied offline. Use one of the following commands, where nnnn is the device number of the appropriate volume:
•From an z/OS console: V nnnn,OFFLINE
•From SDSF: /V nnnn,OFFLINE
When the job completes successfully, vary the devices back online by using one of the following commands:
•From an z/OS console: V nnnn,ONLINE
•From SDSF: /V nnnn,ONLINE
Job INITSMS
The INITSMS job starts an SMS-managed volume that is named LOGR01. This volume is defined to the LOGGER storage group in the sample DFSMS configuration in your order. The job is an optional job. The Storage Group (LOGGER) is used in JOB DEFNLOGS to define SMF LOGSTREAMS for target system. This process is done after the Target initial load.
12.7.3 Creating RACF profiles on driving system
The RACFDRV job creates the RACF profiles that are needed on the driving system to run the other driving system installation jobs. RACFDRV also creates profiles for the high-level qualifiers in the order. Run this job on the driving system. The user ID that runs the RACFDRV job must have the RACF SPECIAL attribute. In our Lab, we use IBMUSER on the driver.
When this job completes, examine the job output to verify that your installation’s security setup objectives are met.
 
Note: Review the contents of this job before submitting it. RACFDRV contains sample definitions; running it unchanged on a system might result in an outage or significant rework for you later, depending on your installation’s current security definitions.
12.7.4 Defining catalogs
The DEFCAT job allocates and defines the target system master catalog and user catalog and connect them as user catalogs to the driving system master catalog. DEFCAT also imports the user catalogs to the target system master catalog. If there is no master catalog to be allocated, DEFCAT does not define one.
For more information, review the ServerPac DOC: RACFDRV, DEF CAT, SSA, and RESTORE.
12.7.5 Defining SSA
The DEFSSA job defines the SSAs for the catalogs on the driving system and target system that are needed to install your order.
For more information about SSAs and how they are used during installation, see ServerPac: Using the Installation Dialog, SA23-2278-02, and 12.6.6, “Specifying temporary aliases for catalogs” on page 200
For more information, see the ServerPac DOC: RACFDRV, DEF CAT, SSA, and RESTORE.
12.7.6 Allocating and cataloging data sets
The ALLOCDS job allocates and catalogs your new target system data sets. Many of these data sets have unique considerations for serialization, availability, security, backup, and recovery. For these considerations, see the planning and implementation documentation for the products that you are installing.
If ALLOCDS fails, you can restart the job by using the RESTART parameter of the job card in the appropriate step. Do not resubmit this job because some data sets might be allocated and you might encounter the JCL error if duplicate data set is found.
For more information, see the ServerPac DOC: RACFDRV, DEF CAT, SSA, and RESTORE.
12.7.7 Restoring data sets
Restoring the ServerPac content files is directed to the Install Directory on the driving system. By default, the Install Directory is /Service. This value cannot be blank (the job fails). Ensure that the SMPWKDIR directory /tmp is mounted with one temporary HFS or zFS that is larger enough to hold the temporary files during job running.
In our example, the /tmp directory is mounted with one HFS approximately 9 GB. If SMPWKDIR is mounted without a block parameter and a file in your order is greater than 2 GB, the RESTORE job fails during GIMUNZIP processing with the message GIM43501S and RETURN CODE '00000077'X.
The RESTORE job might run for some time (minutes to hours), depending on your LPAR’s resources configuration (Logical CP, LPAR Weight, Storage).
For more information, see ServerPacDOC: RACFDRV, DEF CAT, SSA, and RESTORE.
12.7.8 Updating default data sets names
The CPPUPDT job changes the ServerPac default data set names to the names that you specified in the Modify System Layout function of the installation dialog.
Job CPPUPDT also adds members to the CPAC.PARMLIB data set for products in your order, as listed in Table 12-3.
Table 12-3 CPPUPDT added members
PARMLIB Members
Usage
PROG00
For data sets that are in the link list or require APF authorization.
LPALST00
For data sets that are in LPA storage.
If CPPUPDT fails, do not restart the job. Rerunning certain update steps can result in data set names that are incorrect for your installation.
12.7.9 Defining SMP/E environment
The UPDDDD job updates your target system’s new CSIs (global, target, and DLIB) with the DDDEFs for the newly allocated SMP/E data sets.
All order installation jobs that are running on the driving system are done and it is ready to prepare the pre-loading jobs and actions for the first initial load of z/OS V2R2.
We now move on to Phase 10
..................Content has been hidden....................

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