IBM Global Technology Services

SYSTEMPAC DESIGN guide

IBM Global Technology Services

Updated: 10/23/2018

Initial Enrichment Data

Customer Contact Information

IBM Contact Information

Tape Media Selection

CPU Information

System Name, Sysplex Name and Global CSI Selection

Standalone Utility Tape

JES Subsystem

Selective Follow-On Service

IBM Implementation Services for Parallel Sysplex (6948-74Z)

Zone Nicknames/Zone Names:

Terminal and Printer Information

Master Consoles

TSO Terminals

I/O Configuration Information

Other Variables

DASD

VOLUME LAYOUT

Unix File System

SMS Managed Data Sets

Indirect Catalog Option

SMPE Datasets

SMPE VSAM Datasets

SMPE Global Non-VSAM Datasets

SMPE TARGET & DLIB Non-VSAM Datasets

Master Catalog Options

Dataset Names & User Catalog Options

Catalogs Volume Assignement

Static System Symbols

SYSPLEX Naming Standards

SYSPLEX Name

System Name

SYSTEM Volume Names

UNIX System Services File System (Shared)

Preface

This enrichment form is to collect customization data to tailor build your Sysplex enabledSystemPac. For normal SystemPac (without sysplex enabled), please use the form “ SystemPac Enrichment Form Vx.x)Upon completion of the form, please send it back to IBM. If there are questions with the form, please raise them to the IBM personnel who send this form to you.

Summary of changes:

Date / Change
03/06/2007 / Original copy
04/05/2007 / Updated Parallel Sysplex offerings
11/06/2007 / CICS SVC’s
13/06/2007 / Removed 3380 DASD device type
10/01/2007 / Sysplex Layout support
12/11/2007 / Added Internet option in media selection list and DASD layout modified
19/03/2008 / Added Catalogs Volume assignment
26/09/2008 / Added JES Subsystem selection
09/02/2009 / Removed ISV customization questions

Contacts

Contact / userid
IBM Manufacturing /

Initial Enrichment Data

Please fill out the following fields in the attached Initial Enrichment Form accordingly.

Once the form has been received, IBM will input the information into our Production System.

IBM will begin the build of your SystemPac after the input from the Enrichment form is completed.

Note: The values highlighted in blue are default or recommended values that will be used to tailor and build your Sysplex enabled SYSTEMPAC. If you decide to change default values, refer to Sysplex Reference Architecture and Appendix of the form for recommended naming standard.

Customer Contact Information

Table 1 Customer Contact Information

Customer Name
Customer Number
Customer Contact
Phone Number
Email
Customer Mailing Address for SystemPac

IBM Contact Information

Table 2 IBM Contact Information

Name
Phone Number
Email
TECH-LINE (if known)
Email

Tape Media Selection

Media Selection was made at time of order, please indicate a change if necessary. Read note about Internet orders.

Table 3 Media Selection

SELECT MEDIA TYPE
3480
348X (COMPACT)
3490E - High Density 36 Tracts
3590 - High Density 128 Tracks
3592 – High Density 512 Tracks
Internet

Select “Internet” option only if your order is submitted in ShopzSeries as Internet delivery order.
Note that you cannot change an Internet delivery order to a physical media order and vice-versa.

CPU Information

Table 4 CPU Information

Enter CPU INFO / Notes
CPU TYPE
CPU Model
CPU Serial
CPU Capacity Indicator

System Name, Sysplex Name and Global CSI Selection

Table 5 System Name and Global CSI Selection

Enter INFO / Notes
SYSNAME / MZM1 / Default is MZM1
System Name = LPAR Name = SMFID = JES Member ID
Note: Read System Name section for system name naming convention
SYSPLEX NAME / MZPLEX / Default is MZPLEX.
Note: Read SYSPLEX Name section for sysplex name naming convention
Multiple GLOBAL CSI? (Yes/No) / No / Entering 'Yes' to 'Multiple GLOBAL CSI' will allow the Global CSI datasets to spread over each SREL (i.e. CICS,DB2,IMS or NCP) on an order, otherwise only ONE Global CSI dataset will be assigned.

Standalone Utility Tape

Table 6 Standalone Utility Tape

Enter INFO / Notes
Standalone Utility Tape Required / Yes / Yes/No
Entering ‘Yes’ to ‘Standalone Utility Tape Required’ will include 2 Standalone tapes on the same delivery media type:

• Standalone Dump/Restore tape using DFSMSdss
• Standalone DASD Initialization tape using ICKDSF

Note: this option is only applicable to tape media delivery

JES Subsystem

Table 7 JES Subsystem

Enter INFO / Notes
JES subsystem:
JES2 or
JES3 or
Both / Select JES Subsystem that you would like to be delivered in SystemPac order.
Default is both JES2 and JES3.

Note: This option is valid with SystemPac z/OS V1R10 and up. The orders with SystemPac z/OS V1R9 do not support this option.

• If JES2 is specified, the JES3 Subsystem will not be delivered in the SystemPac
• If JES3 is specified, the JES2 Subsystem will not be delivered in the SystemPac
• If BOTH is specified, both JES2 and JES3 will be delivered in the SystemPac

Selective Follow-On Service

The Selective Follow-On Service (SFS) package includes HOLDDATA, HIPER PTFs, and PTFs correcting PTFs-in-error with all required “PRE” REQ service.

The package includes installation JCL and customized documentation for all subsystems in the original order. SFS tape media and shipping method will remain the same.

You can request up to 3 SFSs per SystemPac. We recommend that the SFS(s) are set to be shipped at 30 day intervals.

Table 8 Service

Enter
Selection / Notes
Number of SFS’s / (0,1,2,or 3)
Frequency / Number of days between SFS Packages (Maximum 120 Days)
Electronic Delivery (via FTP) / (Yes or No)
e-mail for electronic Delivery / Required if Electronic Delivery is specified to Yes

IBM Implementation Services for Parallel Sysplex (6948-74Z)

Indicating a "Y" to the questions below mean the sample datasets containing the SYSPLEX best practices samples will be shipped in the SystemPac. All the samples are shipped “AS IS”.

Please ensure that you have acquired the IBM Implementation Services for Parallel Sysplex (6948-74Z)and would like to obtain these samples before answering "Y" to the questions below. If you have not acquired the offering and will like more information about it, please contact Anna Lee () or an IBM representative.

Table 8 Parallel Sysplex Offering

Enter
Selection / Notes
Have you acquired the IBM Implementation Services for Parallel Sysplex Offering (6948-74Z)? / Yes / (Y–Yes, N-No)
If yes, do you want the best practices samples included in the SystemPac? / Yes / (Y–Yes, N-No) - only valid if customer acquired the Parallel Sysplex Offering
Provide value for MASID / MZM1 / MASID is the symbolic for the JES PLEX ID. It is possible to have multiple JES Plexes within the same parallel sysplex. Default is is ot be the same as System Name (MZM1).

Zone Nicknames/Zone Names:

Zone checking will be preformed to ensure proper grouping/product compatibility and that products of different SRELs are not in the same zone.

Default zone names have been provided. You have the option of selecting your own zone names.

Zone names MUST be less than or equal to 7 characters in length and each zone name MUST be unique.

 If you have other products which are not listed in Table 9 and you want to assign specific zones to them, please add to the table below or request for a list of your ordered products.

Table 10 SMPE ZONE Information

Zone
Description / Target
Zone
Name / Dlib
Zone
Name / Changed
Target Zone
Name / Changed
Dlib Zone
Name
z/OS Base / MVST100 / MVSD100
JES2 / MVST110 / MVSD110
JES3 / MVST111 / MVSD111
SDSF (starting with z/OS R11) / MVST112 / MVSD112
WEBSPHERE FOR Z/OS / MVST113 / MVST113
IMS / IMST200 / IMSD200
DB2 / DB2T300 / DB2D300
NCP / NCPT400 / NCPD400
CICS / CICT500 / CICD500
SystemPac Full Volume Dump format only
Add products below that you want to have assigned specific SMP/E zone.
(The products should not have dependencies on z/OS Base product)
Product Number and version / New Target Zone Name / New Dlib Zone Name

Note: In order to provide additional migration flexibility, three additional SMP/E zones are defined with z/OS R11, JES2 with SDSF support is placed in one zone, JES3 in another and SDSF in third zone, all are separated from the remainder of z/OS. With SystemPac Full Volume Dump format you have option to merge JES2, SDSF product or JES3 into z/OS base zone, specifying the z/OS base zone names (ex. MVST100/MVSD100). If you specified that you would like that JES3 or JES2 not to be delivered in SystemPac order then, product code and related SMP/E zones for JES2 or JES3 will not be assigned and delivered with your order.

In SystemPac Copy By Data set format, the new zones can later be merged into the z/OS zone during installation or at a later time, depending on the customer migration preference.
If you ordered WebSphere for z/OS product, as default it would be delivered in a separate SMP/E zone.

Sample zone names z/OS 1.10 base zonesare provided in black italic. It should match your sysres volume name. It’s consisting of Sysplex prefix (MZ), z/OS version and release (1A) and the first sysres volume suffix (A1). If you would like to delete not required JES for example JES3 that can be done running provided post-IPL jobs after you receive the order.

If you ordered WebSphere for z/OS product, as default it would be delivered in a separate SMP/E zone.

Terminal and Printer Information

Master Consoles

Table 11 Consoles and Printers

Address / Type / Model / Notes
Master Console / The address specified for the master console must be in the NIP statement of your MVSCP or identified as a NIP console in the IODF.
Valid values for Master, Alternative and JES3 Console Type are the following: 3270,3277, 3278 OR 3279
Alternative Console
JES3 Console / if applicable
System Printer / if applicable

TSO Terminals

Table 12 Local TSO Terminals

Address / Type / Model / Notes
TSO TERM1 / A minimum of 2 terminal addresses are required, however up to six addresses may be included.
TSO TERM2
TSO TERM3
TSO TERM4
TSO TERM5
TSO TERM6

I/O Configuration Information

Table 13 IODF

IODF Input
Configuration EDT
Configuration ID

Other Variables

Provide answers to the following variables if the productswere ordered.

Table 14IMS

SVC Module Name for IMS / 8 chars, in form IGC00xxx
Type 2 SVC Number for IMS / 3 digits, between 200 and 255
Type 4 SVC Number for IMS / 3 digits, between 200 and 255

Table 15CICS

Type 3 SVC Number for CICS / 3 digits, between 200 and 255
Type 6 SVC Number for CICS / 3 digits, between 200 and 255

DASD

Please provide SYSRES, DLIB, CATALOG and SMP volumes using recommended System Layout. Place third parties' (vendors') products on different packs, separate from IBM products, place subsystem on its own different pack(s). Naming convention for volume names is available in this document in SYSTEM Volume Names section. Enter Required Volume Information:

Table 18 Volume Information

Volume Type / Volser
Name (6 char, alphanum) / Address (4 digits in hex) / Unit Type
(3390) / Model
SYSRES VOLUME #1 / MZ1AA1 / xxxx / 3390 / 9
#2 / MZ1AA2 / xxxx / 3390 / 9
#3
#4
DLIB VOLUME #1 / DL1AA1 / xxxx / 3390 / 9
#2
#3
CATALOG VOLUME / MZMCV1 / xxxx / 3390 / 9
SMP/E VOLUME #1 / MZSMP1 / xxxx / 3390 / 9

Note: Listed sample volume names in black italic are preferred DASD Type and Model, for a z/OS V1R10 system. If you are preferred Sysplex prefix is not MZ, you can change it to a different prefix.

Table 19 Volume Information - continuation

Volume Type / Default Volser
Name (6 char, alphanum) / New Volser
Name / Address (4 digits in hex) / Unit Type
(3390) / Model
Sysplex Shared
CDS = Couple Datasets P / MZCDS1 / Xxxx / 3390 / 3
CDS = Couple Datasets S / MZCDS2 / Xxxx / 3390 / 3
CDS = Couple Datasets B / MZCDS3 / Xxxx / 3390 / 3
CKP = Checkpoint / MZCKP1 / Xxxx / 3390 / 3
CKP = Checkpoint / MZCKP2 / Xxxx / 3390 / 3
SEC = Security primary / MZSEC1 / Xxxx / 3390 / 3
SMS = SMS / MZSMS1 / Xxxx / 3390 / 3
SPL = Spool / MZSPL1 / Xxxx / 3390 / 3
LOG = Logrec / MZLOG1 / Xxxx / 3390 / 3
System Specific
PAG = Page Volume / M1PAG1 / Xxxx / 3390 / 3
SMF = SMF / M1SMF1 / Xxxx / 3390 / 3

Note: Listed volumes are default assigned volumes that will be delivered with SystemPac Sysplex Offering. They can be changed if your preferred Sysplex and system prefix is not MZ and M1.

VOLUME LAYOUT

Table 20 Volume Layout

TYPE / VOLSER / ADDRESS / UNIT / MODEL
CICS TARGET
CICS DLIB
CICSSMP
IMS TARGET
IMS DLIB
IMS SMP
DB2 TARGET
DB2 DLIB
DB2 SMP
NCP TARGET
NCP DLIB
NCP SMP

Unix File System

Table 21Unix File System Options

Unix File System Options / HFS/zFS
Build file system in zFS or HFS format? / zFS / zFS is a mandatory option for Sysplex Offering
UNIX System Services File System (Shared) / Yes / Shared UNIX is option is mandatory for Sysplex offering
Merge z/OS products files systems into Version zFS?
(MZ1AA1.VERSION.ROOT) / Yes / If Yes, all z/OS components will be installed in a single version file system

SMS Managed Data Sets

Table 22 SMS Options

SMS Options / YES/NO
Build Unix HFS or zFS Data Sets on SMS-Managed DASD ? / No
Build PDSE data sets on SMS-Managed DASD? / No
SMS Storage Class: (Default = SMSUCLAS) / No
SMS Storage Group: (Default = STG4FVD) / No

PLEASE SUPPLY THE INFORMATION FOR 3 SMS VOLUMES - WE WILL USE ONLY AS NECESSARY.

Table 23 SMS Volumes

SMS Volume – VOLSER(6 DIGITS) / STARTING ADDRESS / UNIT / MODEL

NOTE: SMS Volume cannot be zFS01/HFS01 – zFS10/HFS10 or CPACx – CPACx or same prefix as any other VOLSER’s in this order.

Indirect Catalog Option

Table 24 Indirect Catalog Option

Catalog Options / YES/NO
Does this order required Indirect Catalog Referencing? / Yes

NOTE: If indirect catalog referencing is not required (N is chosen) then N must be also entered for static system symbols.

Indirect cataloging allows the system to dynamically resolve volume and device type information for non-VSAM data sets residing on the system residence volume (SYSRES) when accessed through the catalog. This allows you to change the volume serial number or device type of the system residence volume without also having to recatalog the non-VSAM data sets on that volume. Indirect cataloging can be used only for non-VSAM data sets which reside on the SYSRES.

With z/OS, in which many elements and optional features are provided, the space required by the data sets which logically belong on SYSRES may exceed the capacity of a single DASD volume. If some of these data sets are placed on overflow volumes rather than SYSRES, there is no way in the current indirect cataloging support to refer to them indirectly.

SMPE Datasets

SMPE VSAM Datasets

Define Zone CSI Names: Changes to CSI Names if required...

• Restrictions:
• Names must be less than or equal to 26 characters
• You have the option of grouping 2 entries in the same zone by specifying the same zone name, or else the names must be unique for different zones.
• Two different COBOL’s can't live in the same zone.
• Subsystems and their related products must live in the same zone

(E.g. GDDM for CICS has to be in the same zone as CICS itself)

Table 25 Single SMPE Global

FOR SINGLE GLOBAL CSI NAMES / DEFAULT ZONE CSI NAME / CHANGE TO CSI NAME IF REQUIRED
MVS GLOBAL CSI: / SMP1A.GLOBAL.CSI / Default name for z/OS 1.10
TARGET MVS / MZ1AA1.SMP.CSI / Default name for z/OS 1.10 and Sysplex prefix MZ
DLIB MVS / DL1AA1.SMP.CSI / Default name for z/OS 1.10
TARGET DB2 / SMPE.DB2.TARGET.CSI
DLIB DB2 / SMPE.DB2.DLIB.CSI
TARGET IMS / SMPE.IMS.TARGET.CSI
DLIB IMS / SMPE.IMS.DLIB.CSI
TARGET NCP / SMPE.NCP.TARGET.CSI
DLIB NCP / SMPE.NCP.DLIB.CSI
TARGET CICS / SMPE.CICS.TARGET.CSI
DLIB CICS / SMPE.CICS.DLIB.CSI

Default names for MVS CSIs and Global in sysplex environment for z/OS 1.10:

• Global CSI name: SMP&vr.GLOBAL.CSI, for V1R10 will be set to SMP1A.GLOBAL.CSI
• Target CSI: &sysres.SMP.CSI, for V1R10it will be automatically renamed to MZ1AA1.SMP.CSI
• DLIB CSI: &dlib.SMP.CSI, for it will be automatically renamed to DL1AA1.SMP.CSI

Table 26 Multi-SMPE Global

FOR MULTIPLE GLOBAL CSI NAMES / DEFAULT ZONE CSI NAME / CHANGE TO CSI NAME IF REQUIRED
MVS / SMP1A.GLOBAL.CSI / Default name for z/OS 1.10
MZ1AA1.SMP.CSI / Default name for z/OS 1.10 and Sysplex prefix MZ
DL1AA1.SMP.CSI / Default name for z/OS 1.10
CICS / SMPE.CICS.GLOBAL.CSI
SMPE.CICS.TARGET.CSI
SMPE.CICS.DLIB.CSI
DB2 / SMPE.DB2.GLOBAL.CSI
SMPE.DB2.TARGET.CSI
SMPE.DB2.DLIB.CSI
IMS / SMPE.IMS.GLOBAL.CSI
SMPE.IMS.TARGET.CSI
SMPE.IMS.DLIB.CSI
NCP / SMPE.NCP.GLOBAL.CSI
SMPE.NCP.TARGET.CSI
SMPE.NCP.DLIB.CSI

• Restrictions:
• Must conform to normal DSN requirements (e.g. less than 44 chars)
• DSN's must end with .CSI
• A unique CSI must exist for each zone; multiple zones may not be combined into one CSI.
• GLOBAL,TARGET/DLIB CSIs cannot have SRELs mixed i.e. IMS and CICS cannot be placed in the same target/dlib CSIs or global

Default names for MVS CSIs and Global in sysplex environment for z/OS 1.10:

• Global CSI name: SMP&vr.GLOBAL.CSI, for V1R10 will be set to SMP1A.GLOBAL.CSI
• Target CSI: &sysres.SMP.CSI, for V1R10 it will be automatically renamed to MZ1AA1.SMP.CSI
• DLIB CSI: &dlib.SMP.CSI, for it will be automatically renamed to DL1AA1.SMP.CSI

SMPE Global Non-VSAM Datasets

Table 27 SMPE Global Non-VSAM

ZONE SREL / SMPE
DDDEF DDNAME / Dataset NAME Name / Zone Type / Changes to if required / Comment
CICS / SMPGLOG / SMPE.CICS.SMPGLOG / GLOBAL / Only when multiglobal= Y
SMPGLOGA / SMPE.CICS.SMPGLOGA / GLOBAL / Only when multiglobal= Y
SMPPTS / SMPE.CICS.SMPPTS / GLOBAL / Only when multiglobal= Y
DB2 / SMPGLOG / SMPE.DB2.SMPGLOG / GLOBAL / Only when multiglobal= Y
SMPGLOGA / SMPE.DB2.SMPGLOGA / GLOBAL / Only when multiglobal= Y
SMPPTS / SMPE.DB2.SMPPTS / GLOBAL / Only when multiglobal= Y
IMS / SMPGLOG / SMPE.IMS.SMPGLOG / GLOBAL / Only when multiglobal= Y
SMPGLOGA / SMPE.IMS.SMPGLOGA / GLOBAL / Only when multiglobal= Y
SMPPTS / SMPE.IMS.SMPPTS / GLOBAL / Only when multiglobal= Y
NCP / SMPGLOG / SMPE.NCP.SMPGLOG / GLOBAL / Only when multiglobal= Y
SMPGLOGA / SMPE.NCP.SMPGLOGA / GLOBAL / Only when multiglobal= Y
SMPPTS / SMPE.NCP.SMPPTS / GLOBAL / Only when multiglobal= Y
MVS / SMPGLOG / SMP1A.GLOBAL.SMPGLOG / GLOBAL / Default name for z/OS 1.10
SMPPTS / SMP1A.GLOBAL.SMPPTS / GLOBAL / Default name for z/OS 1.10
SMPGLOGA / SMP1A.GLOBAL.SMPGLOGA / GLOBAL / Default name for z/OS 1.10

SMPE TARGET & DLIB Non-VSAM Datasets