Phase 8: ServerPac installation preparation
This chapter describes the preparation steps that are used to install the z/OS V2R2 ServerPac with the z/OS Customized Offering Driver (COD) system.
Before your ServerPac is installed, verify that prerequisites for the COD environment are in place. Then, the CustomPac Installation Dialog can be restored from the ServerPac installation media.
Finally, the Installation Dialog is used to create the jobs for receiving and installing the order that is described in Chapter 12, “Phase 9: ServerPac Build of z/OS V2R2” on page 183.
This chapter includes the following topics:
11.1 Goals
Phase 8 features the following goals:
•Order and receive the z/OS V2R2 ServerPac.
•Plan the ServerPac installation option and layout.
•Prepare the COD installation environment.
•Prepare the installation media and upload into the COD driver.
•Restore the CustomPac Installation Dialog for the next phase.
Phase 8 is required to achieve milestone 4: Use COD to install z/OS ServerPac. Where this phase is positioned in the overall process is shown in Figure 11-1.
Figure 11-1 Phase 8 Milestone 4
11.2 Requirements
The z/OS ServerPac is one software package that includes the installed z/OS products and operational data sets that make up a test target system that is ready to IPL when it is loaded to DASD volume.
You can load all SMP/E target and distribution library data sets directly from installation media and bypass the SMP/E receive, apply, and accept steps. ServerPac provides two kinds of installation options: Full System Replacement or Software Upgrade to the environment. In this chapter, we choose Full System Replacement to install one new z/OS V2R2 system as the target system by using the CusomPac Installation Dialog panels.
The hardware and software requirements are described next.
11.2.1 Driving system software requirements
The driving system includes the following requirements:
•Operating system is up
•TSO/E session is available
•User ID is authorized
•OMVS address space is active
•SMS is active, at least with one null configuration
•Proper level for service
•zFS configured properly (optional)
11.2.2 Driving system hardware requirements
The driving system includes the following hardware requirements:
•A TSO/E console
•Sufficient logical partition (LPAR) real storage
•A DVD reader for a 4.7 GB (single-sided, single-layered) DVD
•A workstation that is network-attached to your z/OS host system
•Enough workstation hard disk drive space to download the order if you use store-and-forward option
•IBM z Systems servers to support z/OS V1R13 and later release
•Minimum processor storage requirement of 256 MB for initial loading
•Identify I/O device and DASD space requirements
11.3 Related documents
The following IBM publications provide relevant information during this phase:
•ServerPac: Installing Your Order Order Number: OS2xxxx
•ServerPac: Using the Installation Dialog, SA23-2278
•z/OS Introduction and Release Guide, GA32-0997
•z/OS V2R2 Planning for Installation, GA32-0889
For more information, see this website:
The first document in this list is generated by IBM to match your order and is unique to your order.
11.4 Ordering and receiving the z/OS V2R2 ServerPac
ServerPac orders can be ordered and delivered electronically or physically on tape media or DVDs. Each ServerPac order includes publications, information about the ServerPac data sets that are shipped with your order, and service information.
Contact your IBM service representative to order your z/OS ServerPac.
11.5 Planning the ServerPac installation layout
To complete the installation, you must understand the layout and plan for the target system, including the following components:
•Volume labels and its usage purpose
•Data set names and volume locations
•Master and user catalogs that are used by target system
11.5.1 Volumes
The volume layout that is used is listed in Table 11-1.
Table 11-1 Volume layout for COD and ServerPac systems
|
Device Address
|
Volume Label
|
Access Systems
|
Usage
|
|
1200
|
D9ESY1
|
COD, ServerPac
|
COD Driver SYSRES1
|
|
1201
|
D9ESY2
|
COD, ServerPac
|
COD Driver SYSRES2
|
|
1202
|
D9ECAT
|
COD, ServerPac
|
COD Driver catalog
|
|
1203
|
D9ESY3
|
COD, ServerPac
|
COD Driver JES2 Spool
|
|
1204
|
D9EPAG
|
COD, ServerPac
|
COD Driver Paging
|
|
1280
|
M0SR21
|
COD, ServerPac
|
ServerPac SYSRES
|
|
1281
|
M0SD21
|
COD, ServerPac
|
ServerPac Distribution Library
|
|
1282
|
M0SCT1
|
COD, ServerPac
|
ServerPac catalog, Customized data sets
|
|
1283
|
LOGR01
|
COD, ServerPac
|
ServerPac Logsteam data sets, SMS-managed
|
|
1284
|
M0SUX1
|
COD, ServerPac
|
ServerPac OMVS data sets
|
|
2000
|
M0SIN1
|
COD, ServerPac
|
ServerPac installation HFS file system space
|
|
2001
|
M0SIN2
|
COD, ServerPac
|
ServerPac CustomPac Dialog, SMP/E CSI
|
|
2020
|
IODF00
|
ALL Systems
|
IODF Volume
|
11.5.2 Catalog
Catalog the following data sets in a user catalog. We suggest that CustomPac.Qualifier be CPAC.MASTER to distinguish the master dialogs from the order dialogs. The high-level qualifier (HLQ) is up to you. A good practice is to use a separate user catalog that is defined in your driving system to catalog the CPAC.MASTER into it for later use by the target system. When the target system is initially loaded, you must share and connect that user catalog and continue the postinstallation process:
• CustomPac.Qualifier.SCPPLOADL Load Modules
• CustomPac.Qualifier.SCPPCENU: Clist/Rexx execs
• CustomPac.Qualifier.SCPPEENUL CustomPac messages (VSAM)
• CustomPac.Qualifier.SCPPHENUL CustomPac dialog help (VSAM)
• CustomPac.Qualifier.SCPPMENU: Messages
• CustomPac.Qualifier.SCPPPENU: Panels
• CustomPac.Qualifier.SCPPSENU: Skeletons
• CustomPac.Qualifier.SCPPTENU: Tables
• CustomPac.Qualifier.SCPPVENUL Order inventory (VSAM)
11.6 Checking the z/OS COD driver system
The following checks must be completed:
•SMS subsystem
•zFS subsystem
These checks are described next.
11.6.1 SMS subsystem
Whether you plan to use SMS to manage the data sets in your order, you must start SMS on the driving system in at least a null configuration before you run the installation jobs that are described in this book.
To accommodate the UNIX file system data sets in your order, you also must have SMS active on the target system in at least a null configuration.
11.6.2 zFS subsystem
ServerPac now provides zFS as the default for all file system data sets. ServerPac jobs allocate and unload zFS file systems unless the customer switches it to hierarchical file system (HFS) via the Dialog. Large file systems (size greater than 3.6 GB) are shipped as an HFS.
Starting z/OS V2R2, COD file systems are shipped as zFS in place of HFS. When you IPL COD, zFS address space starts and COD file systems are mounted as zFS. You can allocate and mount file system data sets that are shipped with your order as zFS or HFS. If you intend to allocate data sets as zFS, see Chapter 1.11 Preparing the System for zFS File System of the Install Your Order document to determine whether you must take more actions to prepare your driving system.
In our example, we use HFS as the ServerPac file system.
11.7 Preparing the HFS for ServerPac storage
We complete the following steps to initialize the HFS:
1. We initialize the DASD with the specified volume labels that are described in 11.5.1, “Volumes” on page 174, as shown in Figure 11-2.
|
//INITVOL2 JOB (0000),INIT,CLASS=A,MSGCLASS=X,REGION=64M,NOTIFY=&SYSUID
//INITDISK EXEC PGM=ICKDSF,PARM=NOREPLYU
//SYSPRINT DD SYSOUT=*
INIT -
UNITADDRESS(2000) -
DEVICETYPE(3390) -
PURGE -
MAP -
VERIFY(*NONE*) -
NOVALIDATE -
VOLID(M0SIN1) -
VTOC(0,1,1349) -
INDEX(90,0,270)
INIT -
UNITADDRESS(2001) -
DEVICETYPE(3390) -
PURGE -
MAP -
VERIFY(*NONE*) -
NOVALIDATE -
VOLID(M0SIN2) -
VTOC(0,1,1349) -
INDEX(90,0,270)
|
Figure 11-2 Initializing volume by using ICKDSF
We must determine the appropriate VTOC and index according to the size of the DASD. For more information about calculating the correct size, see this website:
2. We go to OMVS and create one directory as the HFS mount point, as shown in Example 11-1.
Example 11-1 Creating directory for HFS mount point
TSO OMVS
cd /
mkdir serverpac
Then, a HFS data set can be defined and mounted to the mount point, as shown in Figure 11-3.
|
//HFSALLOC JOB CLASS=A,MSGCLASS=X,MSGLEVEL=(1,1),NOTIFY=&SYSUID,
// REGION=0M
//ALLOCHFS EXEC PGM=IEFBR14
//HFSDD DD DSN=OMVS.ZOSV22.CPAC.OS220149.HFS,
// UNIT=SYSALLDA,VOL=SER=M0SIN1,
// SPACE=(CYL,(20000,1000,5)),
// DSNTYPE=HFS,
// DISP=(NEW,CATLG)
//STEP002 EXEC PGM=IKJEFT1B
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
PROF MSGID WTPMSG
MOUNT FILESYSTEM('OMVS.ZOSV22.CPAC.OS220149.HFS') +
MOUNTPOINT('/serverpac/') +
TYPE(HFS) MODE(RDWR) NOSECURITY NOAUTOMOVE
|
Figure 11-3 Defining and mounting HFS
We must also ensure that there is enough space to accommodate the order package. IBM recommends that there is available space in the z/OS file system that is equal to two times the size of the order’s package. To convert to 3390 cylinders, multiply the number of MB by 1.4 and then multiply by 2. The size of our order is 8646 MB, one HFS is prepared for approximately 20000 cylinders in one 3390 Model 54 volume.
11.8 Transferring DVD content to z/OS host
The z/OS ServerPac order is provided in SMP/E GIMZIP format. The SMP/E utility GIMUNZIP must be used to process your order. You must perform the tasks that are described in this section to ensure that your host environment is set up to accommodate the package transfer.
Complete the steps that are described in the README.pdf, which is in the first DVD to transfer the contents to your z/OS host. Then, complete the following steps:
1. Copy the content from the three DVDs into one temporary directory of your workstation.
If there are multiple DVDs, copy all the <#order number>.content files into the <#order number>.content directory on your workstation, as shown in Example 11-2.
Example 11-2 Copying DVD content in your workstation
c:zOSV2R2<#order number>.content
c:zOSV2R2<#order number>.order
As shown in Example 11-2, <#order number> is the order name that you ordered through z/OS ordering process and was printed on the DVD.
2. Upload the z/OS ServerPac contents into z/OS driver system.
There are multiple options for making the package available to z/OS and the CustomPac Installation Dialog, an FTP client is the most common method that is used to transfer files.
In this example, we use the workstation as the FTP client and z/OS driver system as the FTP server.
Before transferring files to the z/OS host, ensure that the directories that are shown in Example 11-3 are on your z/OS host system.
Example 11-3 z/OS UNIX System Services directories in your HFS file system
/<mountpoint>/<mvs directory>
/<mountpoint>/<mvs directory>/<#order number>.order
/<mountpoint>/<mvs directory>/<#order number>.content
Where:
– <mountpoint > is the directory on the z/OS host system to which the HFS is mounted
– <mvs directory> is the directory on the z/OS host system into which the order is to be transferred
– <#order number> is the ServerPac order number
In this example, we create the directories that are shown in Example 11-4 in the HFS file system.
Example 11-4 Creating directories in COD z/OS host system
tso omvs
cd /serverpac/
mkdir zosv2r2/
mkdir zosv2r2/OS220149.order
mkdir zosv2r2/OS220149.content
3. Upload the ServerPac order and content into the COD driver system by using FTP, as shown in Example 11-5.
Example 11-5 FTP upload ServerPac contents to COD z/OS host system
C:> ftp <mvsaddress>
User (mvsaddress:(none)): <tsouid>
331 Send password please.
Password:
ftp> cd /mountpoint/<mvs directory>/<#order number>.order
ftp> bin
ftp> prompt off
ftp> mput <packagelocation><ordernumber>.order*.*
ftp> cd /mountpoint/<mvs directory>/<#order number>.content
ftp> mput <packagelocation><#order number>.content*.*
ftp> bye
Where:
– <mvsaddress> is the name or address of the z/OS host system.
– <tsouid> is the valid user ID that is used when logging on to the z/OS host system.
– <mountpoint> is the directory on the z/OS host system in which the HFS is mounted.
– <mvsdirectory> is the directory on the z/OS host system into which the order is transferred.
– <#order number> is the ServerPac order number.
– <packagelocation> is the directory path on the workstation hard disk drive to where the DVDs files were copied or the name of your DVD drive.
|
Note: You must validate that the number of files under each order directory is equal to the total number of files that are found under that directory across all the DVDs that comprise your order.
|
11.9 Running LOADRIM JCL to restore the CustomPac installation dialog
Upload the LOADRIM.jcl from your DVD into your COD driver system and customize the LOADRIM job to restore the CustomPac Installation Dialog to your named data sets.
Before the LOADRIM job is used to allocate and load the master dialog data sets, you must customize the job. Replace the JOB statement with a JOB statement that is valid for your installation and supply values for them.
|
Note: IBM suggests that you do not use an order number as part of CustomPac.Qualifier. Also, do not use a System Specific Alias (SSA) qualifier that you plan to use for any data sets that are included in the order.
Finally, you should not use SYS1 because you should catalog the data sets in a user catalog to assure portability between systems. For example, you can choose a CustomPac.Qualifier, such as CPAC.MASTER or IBM.INSTALL. However, you should avoid names, such as SYS1.CPAC and INSTALL.#order_number.
Each order includes order-related dialog data sets. You need another unique qualifier for each order’s data sets, which must be different from the qualifier that you choose for CustomPac.Qualifier.
|
We changed CustomPac.Qualifier to CPAC.MASTER and volser to M0SIN2, which was initialized in the last step.
As shown in the following SET statement, we specify the path for the directory in which the CustomPac dialog and order information are stored:
SET PATH='/serverpac/zosv2r2/'
Because we uploaded the ServerPac contents from the workstation to our z/OS COD driver system, there is no need to run GIMGTPKG to retrieve the contents from another FTP server (z/OS driver as FTP client in this scenario). Then, we remove the //UNPLOAD step from LOADRIM job, before submitting it.
This JCL is submitted for running.
11.10 Starting the CustomPac installation dialog
We modify the sample member CPPCSAMP in data set CPAC.MASTER.SCPPCENU, as shown in Figure 11-4.
|
/* ERROR MODE IS SET */
/* DIALOG TERMINATE ON ERROR */
ALTLIB ACTIVATE APPLICATION (CLIST) +
DATASET('CPAC.MASTER.SCPPCENU’) UNCOND
SET &ALTLIBRC = &LASTCC;
IF &ALTLIBRC NE 0 THEN +
WRITE &SYSICMD: ALTLIB(ACTIVATE) RC = &ALTLIBRC;
ELSE DO
ISPEXEC LIBDEF ISPMLIB DATASET ID('CPAC.MASTER.SCPPMENU’)
ISPEXEC LIBDEF ISPPLIB DATASET ID('CPAC.MASTER.SCPPPENU’)
ISPEXEC LIBDEF ISPSLIB DATASET ID('CPAC.MASTER.SCPPSENU’)
ISPEXEC LIBDEF ISPTLIB DATASET ID('CPAC.MASTER.SCPPTENU’)
ISPEXEC LIBDEF ISPLLIB DATASET ID('CPAC.MASTER.SCPPLOAD’)
/*--------------------------------------------------------*/
/* START CPAC DIALOG */
/*--------------------------------------------------------*/
ISPEXEC SELECT CMD(%CPPCISPF CPAC.MASTER)
NEWAPPL(CPP) PASSLIB
/*--------------------------------------------------------*/
/* CLEANUP */
/*--------------------------------------------------------*/
ISPEXEC LIBDEF ISPMLIB
ISPEXEC LIBDEF ISPPLIB
ISPEXEC LIBDEF ISPSLIB
ISPEXEC LIBDEF ISPTLIB
ISPEXEC LIBDEF ISPLLIB
ALTLIB DEACTIVATE APPLICATION(CLIST)
SET &ALTLIBRC = &LASTCC;
IF &ALTLIBRC NE 0 THEN +
WRITE &SYSICMD: ALTLIB(DEACTIVATE) RC = &ALTLIBRC;
END
EXIT CODE(0)
|
Figure 11-4 Updating CLIST to start the CustomPac Installation Dialog
Change CustomPac.Qualifier to CPAC.MASTER. Then, run the CLIST under TSO/E Option 6, as shown in the following example:
exec ’CPAC.MASTER.SCPPCENU(CPPCSAMP)’
After you see the information that is shown in the CustomPac Order Management Panel (as shown in Figure 11-5), you can receive and install your order.
|
CustomPac --------------------- IBM Corporation --------------------- 27.10.18
OPTION ==>
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.MASTER
This dialog supports secure Internet delivery.
********************************************************
* 5751-CS4, 5751-CS5, 5751-CS6, 5751-CS7 and 5751-CS9 *
* Copyright IBM Corp. 1988, 2015 *
********************************************************
|
Figure 11-5 CustomPac Order Management Menu
Phase 8 is now completed.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.