Manual - IBM · Web view2008/10/30 · Name Phone Number Email TECH-LINE (if known) Email Tape...

S Y S T E M P A C D E S I G N G U I D E

IBM Global Technology Services

Updated: 10/30/20085/21/2023

Customer Name Internal Use Only of 27

SystemPac Enrichment

Form for Sysplex Layout(Version 1.1)


INITIAL ENRICHMENT DATA.........................................................................................................................................4

Customer Contact Information..............................................................................................................................................4IBM Contact Information......................................................................................................................................................4Tape Media Selection............................................................................................................................................................5CPU Information...................................................................................................................................................................5System Name, Sysplex Name and Global CSI Selection......................................................................................................5Standalone Utility Tape.........................................................................................................................................................6JES Subsystem.......................................................................................................................................................................6Selective Follow-On Service.................................................................................................................................................6IBM Implementation Services for Parallel Sysplex (6948-74Z)...........................................................................................7Zone Nicknames/Zone Names:.............................................................................................................................................8Terminal and Printer Information..........................................................................................................................................9

Master Consoles.................................................................................................................................................................9TSO Terminals....................................................................................................................................................................9

I/O Configuration Information..............................................................................................................................................9Other Variables....................................................................................................................................................................10DASD..................................................................................................................................................................................11VOLUME LAYOUT...........................................................................................................................................................12Unix File System.................................................................................................................................................................13SMS Managed Data Sets.....................................................................................................................................................13Indirect Catalog Option.......................................................................................................................................................14SMPE Datasets....................................................................................................................................................................15

SMPE VSAM Datasets.....................................................................................................................................................15SMPE Global Non-VSAM Datasets.................................................................................................................................17SMPE TARGET & DLIB Non-VSAM Datasets................................................................................................................17

Master Catalog Options.......................................................................................................................................................20Dataset Names & User Catalog Options.............................................................................................................................21Catalogs Volume Assignement...........................................................................................................................................22Static System Symbols........................................................................................................................................................22

SYSPLEX NAMING STANDARDS.................................................................................................................................23

SYSPLEX Name.................................................................................................................................................................23System Name.......................................................................................................................................................................24SYSTEM Volume Names...................................................................................................................................................25UNIX System Services File System (Shared).....................................................................................................................27



Preface

This enrichment form is to collect customization data to tailor build your Sysplex enabled SystemPac. 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.

S U M M A R Y O F C H A N G E S :

Date Change

03/06/2007 Original copy04/05/2007 Updated Parallel Sysplex offerings06/11/2007 CICS SVC’s06/13/2007 Removed 3380 DASD device type10/01/2007 Sysplex Layout support12/11/2007 Added Internet option in media selection list and DASD layout modified19/03/2008 Added Catalogs Volume assignment26/09/2008 Added JES Subsystem selection

Contacts

Contact userid

IBM Manufacturing [email protected]



Initial Enrichment DataPlease 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 NameCustomer NumberCustomer ContactPhone NumberEmailCustomer Mailing Address for SystemPac

IBM Contact Information

Table 2 IBM Contact Information

NamePhone NumberEmailTECH-LINE (if known)Email



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

Table 3 Media Selection

SELECT MEDIA TYPE3480 348X (COMPACT) 3490E - High Density 36 Tracts 3590 - High Density 128 Tracks3592 – High Density 512 TracksInternet

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 InformationTable 4 CPU Information

Enter CPU INFO NotesCPU TYPECPU Model For orders with ISVs in it, please note

that some ISVs request the CPU serial and type/model and capacity for verifying licensing. For newer machines, you can obtain the model as well as a capacity setting via a D M=CPU command.

CPU SerialCPU Capacity Indicator

System Name, Sysplex Name and Global CSI SelectionTable 5 System Name and Global CSI Selection

Enter INFO NotesSYSNAME MZM1 Default is MZM1

System Name = LPAR Name = SMFID = JES Member IDNote: 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 TapeTable 6 Standalone Utility Tape

Enter INFO NotesStandalone Utility Tape Required

Yes Yes/NoEntering ‘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

JES SubsystemTable 7 JES Subsystem

Enter INFO NotesJES subsystem:

JES2 orJES3 orBoth

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

EnterSelection

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 ([email protected]) or an IBM representative.

Table 8 Parallel Sysplex Offering

EnterSelection

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).


mailto:[email protected]


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

ZoneDescription

TargetZoneName

DlibZoneName

ChangedTarget ZoneName

ChangedDlib ZoneName

z/OS Base MVST100 MVSD100JES2 MVST110 MVSD110JES3 MVST111 MVSD111SDSF (starting with z/OS R11)

MVST112 MVSD112

WEBSPHERE FOR Z/OS MVST113 MVST113ISV Products (per Vendor)

MVST130-MVST139 MVSD130-MVSD139

IMS IMST200 IMSD200DB2 DB2T300 DB2D300NCP NCPT400 NCPD400CICS 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

NameNew 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 zones are 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 NotesMaster 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 ConsoleJES3 Console if applicableSystem Printer if applicable

TSO Terminals

Table 12 Local TSO Terminals

Address Type Model NotesTSO TERM1 A minimum of 2 terminal addresses are required, however

up to six addresses may be included. TSO TERM2 TSO TERM3 TSO TERM4TSO TERM5TSO TERM6

I/O Configuration Information

Table 13 IODF

IODF InputConfiguration EDTConfiguration IDOther Variables

Provide answers to the following variables if the products were ordered.



Table 14 FDR

Do you want to restore with FDR (Yes/No)

Table 15 Syncsort

SVC Module Name for Syncsort 8 chars, in form IGC00xxxSVC Number 3 digits, between 200 and 255

Table 16 IMS

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

Table 17 CICS

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



DASDPlease 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 VolserName (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

ISV Products #1CATALOG VOLUME MZMCV1 xxxx 3390 9SMP/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 VolserName (6 char,

alphanum)

New Volser Name

Address (4 digits in hex)

Unit Type(3390)

Model

Sysplex SharedCDS = Couple Datasets P MZCDS1 Xxxx 3390 3CDS = Couple Datasets S MZCDS2 Xxxx 3390 3CDS = Couple Datasets B MZCDS3 Xxxx 3390 3CKP = Checkpoint MZCKP1 Xxxx 3390 3CKP = Checkpoint MZCKP2 Xxxx 3390 3SEC = Security primary MZSEC1 Xxxx 3390 3SMS = SMS MZSMS1 Xxxx 3390 3SPL = Spool MZSPL1 Xxxx 3390 3LOG = Logrec MZLOG1 Xxxx 3390 3

System SpecificPAG = Page Volume M1PAG1 Xxxx 3390 3SMF = SMF M1SMF1 Xxxx 3390 3Note: 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 MODELCICS TARGETCICS DLIBCICS SMPIMS TARGETIMS DLIBIMS SMPDB2 TARGETDB2 DLIBDB2 SMPNCP TARGETNCP DLIBNCP SMPISV TARGETISV DLIBISV SMP



Unix File System

Table 21 Unix 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 ? NoBuild PDSE data sets on SMS-Managed DASD? NoSMS Storage Class: (Default = SMSUCLAS) NoSMS 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:o Names must be less than or equal to 26 characterso 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.o Two different COBOL’s can't live in the same zone. o 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)o ISV's by default will be placed into a single zone, independent of vendors. An

option is available to place them in different zones.

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.10TARGET MVS MZ1AA1.SMP.CSI Default name for z/OS 1.10 and Sysplex

prefix MZDLIB MVS DL1AA1.SMP.CSI Default name for z/OS 1.10TARGET DB2 SMPE.DB2.TARGET.CSIDLIB DB2 SMPE.DB2.DLIB.CSITARGET IMS SMPE.IMS.TARGET.CSIDLIB IMS SMPE.IMS.DLIB.CSITARGET NCP SMPE.NCP.TARGET.CSIDLIB NCP SMPE.NCP.DLIB.CSITARGET CICS SMPE.CICS.TARGET.CSIDLIB 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 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



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.10CICS SMPE.CICS.GLOBAL.CSI SMPE.CICS.TARGET.CSI SMPE.CICS.DLIB.CSIDB2 SMPE.DB2.GLOBAL.CSI SMPE.DB2.TARGET.CSI SMPE.DB2.DLIB.CSIIMS SMPE.IMS.GLOBAL.CSI SMPE.IMS.TARGET.CSI SMPE.IMS.DLIB.CSINCP SMPE.NCP.GLOBAL.CSI SMPE.NCP.TARGET.CSI SMPE.NCP.DLIB.CSI

Restrictions:o Must conform to normal DSN requirements (e.g. less than 44 chars)o DSN's must end with .CSIo A unique CSI must exist for each zone; multiple zones may not be combined into

one CSI.o 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

SMPEDDDEF 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= YDB2 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= YIMS 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= YNCP 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= YMVS 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

Table 28 SMPE Target & DLIB Non-VSAM

ZONE SREL

SMPEDDDEF DDNAME

Dataset Name Zone Type


CICD500 SMPDLOG SMPE.CICD500.SMPDLOG DLIB SMPDLOGA SMPE.CICD500.SMPDLOGA DLIBCICT500 SMPLTS SMPE.CICT500.SMPLTS TARGET SMPMTS SMPE.CICT500.SMPMTS TARGET SMPSCDS SMPE.CICT500.SMPSCDS TARGET SMPSTS SMPE.CICT500.SMPSTS TARGET SMPTLOG SMPE.CICT500.SMPTLOG TARGET SMPTLOGA SMPE.CICT500.SMPTLOGA TARGETDB2D300 SMPDLOG SMPE.DB2D300.SMPDLOG DLIB SMPDLOGA SMPE.DB2D300.SMPDLOGA DLIBDB2T300 SMPLTS SMPE.DB2T300.SMPLTS TARGET SMPMTS SMPE.DB2T300.SMPMTS TARGET SMPSCDS SMPE.DB2T300.SMPSCDS TARGET SMPSTS SMPE.DB2T300.SMPSTS TARGET SMPTLOG SMPE.DB2T300.SMPTLOG TARGET SMPTLOGA SMPE.DB2T300.SMPTLOGA TARGETIMSD200 SMPDLOG SMPE.IMSD200.SMPDLOG DLIB SMPDLOGA SMPE.IMSD200.SMPDLOGA DLIBIMST200 SMPLTS SMPE.IMST200.SMPLTS TARGET SMPMTS SMPE.IMST200.SMPMTS TARGET



ZONE SREL

SMPEDDDEF DDNAME



SMPSCDS SMPE.IMST200.SMPSCDS TARGET SMPSTS SMPE.IMST200.SMPSTS TARGET SMPTLOG SMPE.IMST200.SMPTLOG TARGET SMPTLOGA SMPE.IMST200.SMPTLOGA TARGETDL1AA1 SMPDLOG SMP1A.DL1AA1.SMPDLOG DLIB Default name for z/OS 1.10 SMPDLOGA SMP1A.DL1AA1.SMPDLOGA DLIB Default name for z/OS 1.10MVSD110 SMPDLOG SMPE.MVSD110.SMPDLOG DLIB JES2, if specified to be

merged, it will be merged with z/OS base zone

SMPDLOGA SMPE.MVSD110.SMPDLOGA DLIB JES2, if specified to be merged, it will be merged with z/OS base zone

MVSD111 SMPDLOG SMPE.MVSD111.SMPDLOG DLIB JES3, if specified to be merged, it will be merged

with z/OS base zone SMPDLOGA SMPE.MVSD111.SMPDLOGA DLIB JES3, if specified to be


MVSD112 SMPDLOG SMPE.MVSD112.SMPDLOG DLIB SDSF, if specified to be merged, it will be merged

with z/OS base zone SMPDLOGA SMPE.MVSD112.SMPDLOGA DLIB SDSF, if specified to be


MVSD130 SMPDLOG SMPE.MVSD130.SMPDLOG DLIB SMPDLOGA SMPE.MVSD130.SMPDLOGA DLIBMZ1AA1 SMPLTS MZ1AA1.SMP.SMPLTS TARGET Default name for z/OS 1.10

and Sysplex prefix MZ SMPMTS MZ1AA1.SMP.SMPMTS TARGET Default name for z/OS 1.10

and Sysplex prefix MZ SMPSCDS MZ1AA1.SMP.SMPSDCS TARGET Default name for z/OS 1.10

and Sysplex prefix MZ SMPSTS MZ1AA1.SMP.SMPSTS TARGET Default name for z/OS 1.10

and Sysplex prefix MZ SMPTLOG MZ1AA1.SMP.SMPTLOG TARGET Default name for z/OS 1.10

and Sysplex prefix MZ SMPTLOGA MZ1AA1.SMP.SMPTLOGA TARGET Default name for z/OS 1.10

and Sysplex prefix MZMVST110 SMPLTS SMPE.MVST110.SMPLTS TARGET JES2, if specified to be


SMPMTS SMPE.MVST110.SMPMTS TARGET JES2, if specified to be merged, it will be merged with z/OS base zone

SMPSCDS SMPE.MVST110.SMPSCDS TARGET JES2, if specified to be merged, it will be merged with z/OS base zone

SMPSTS SMPE.MVST110.SMPSTS TARGET JES2, if specified to be merged, it will be merged with z/OS base zone

SMPTLOG SMPE.MVST110.SMPTLOG TARGET JES2, if specified to be merged, it will be merged with z/OS base zone

SMPTLOGA SMPE.MVST110.SMPTLOGA TARGET JES2, if specified to be merged, it will be merged with z/OS base zone

MVST111 SMPLTS SMPE.MVST111.SMPLTS TARGET JES3, if specified to be merged, it will be merged

with z/OS base zone SMPMTS SMPE.MVST111.SMPMTS TARGET JES3, if specified to be


SMPSCDS SMPE.MVST111.SMPSCDS TARGET JES3, if specified to be



ZONE SREL

SMPEDDDEF DDNAME




SMPSTS SMPE.MVST111.SMPSTS TARGET JES3, if specified to be merged, it will be merged

with z/OS base zone SMPTLOG SMPE.MVST111.SMPTLOG TARGET JES3, if specified to be


SMPTLOGA SMPE.MVST111.SMPLOGA TARGET JES3, if specified to be merged, it will be merged

with z/OS base zoneMVST112 SMPLTS SMPE.MVST112.SMPLTS TARGET SDSF, if specified to be


SMPMTS SMPE.MVST112.SMPMTS TARGET SDSF, if specified to be merged, it will be merged

with z/OS base zone SMPSCDS SMPE.MVST112.SMPSCDS TARGET SDSF, if specified to be


SMPSTS SMPE.MVST112.SMPSTS TARGET SDSF, if specified to be merged, it will be merged

with z/OS base zone SMPTLOG SMPE.MVST112.SMPTLOG TARGET SDSF, if specified to be


SMPTLOGA SMPE.MVST112.SMPTLOGA TARGET SDSF, if specified to be merged, it will be merged

with z/OS base zoneMVST130 SMPLTS SMPE.MVST130.SMPLTS TARGET I SMPMTS SMPE.MVST130.SMPMTS TARGET SMPSCDS SMPE.MVST130.SMPSCDS TARGET SMPSTS SMPE.MVST130.SMPSTS TARGET SMPTLOG SMPE.MVST130.SMPTLOG TARGET SMPTLOGA SMPE.MVST130.SMPTLOGA TARGETNCPD400 SMPDLOG SMPE.NCPD400.SMPDLOG DLIB SMPDLOGA SMPE.NCPD400.SMPDLOGA DLIBNCPT400 SMPLTS SMPE.NCPT400.SMPLTS TARGET SMPMTS SMPE.NCPT400.SMPMTS TARGET SMPSCDS SMPE.NCPT400.SMPSCDS TARGET SMPSTS SMPE.NCPT400.SMPSTS TARGET SMPTLOG SMPE.NCPT400.SMPTLOG TARGET SMPTLOGA SMPE.NCPT400.SMPTLOGA TARGET



Master Catalog Options

Table 29 Master Catalog Options

Master Catalog Options Default standard is: CATALOG.&VR.&SYSPLEX.MCAT &VR = z/OS Version and Release

&SYSPLEX = Sysplex NameMaster Catalog Name CATALOG.V1R10.MZPLEX.MCAT

Note: Listed master catalog name in back italic is preferred name for z/OS 1.10, when sysplex name is MZPLEX. Change it if you are using a different Sysplex name.



Dataset Names & User Catalog OptionsYou have the option to change the product high level qualifier and catalog them into the user catalog. Please specify below which alias you want to rename, and where the alias should be cataloged in.

*Please Note: The list below is a GENERIC list ONLY. All product DSNames are not included and it is not necessary to specify changes on all the Aliases listed. If you have other Aliases that are not listed below and you need them changed, please add them to this list.

Table 30 Dataset & User Catalogs

ALIAS(Default)

ALIAS(User Defined)

TARGET SYSTEM CATALOG (Default is Master Catalog or Specify User Catalog)

CBC CATALOG.V1R10.MZPLEX.MCATCDS CATALOG.V1R10.MZPLEX.MCATCEE CATALOG.V1R10.MZPLEX.MCATCFZ CATALOG.V1R10.MZPLEX.MCATCIM CATALOG.V1R10.MZPLEX.MCATCMX CATALOG.V1R10.MZPLEX.MCATCPAC CATALOG.V1R10.MZPLEX.MCATCSF CATALOG.V1R10.MZPLEX.MCATDFHSM CATALOG.V1R10.MZPLEX.MCATDFRMM CATALOG.V1R10.MZPLEX.MCATDFSMS CATALOG.V1R10.MZPLEX.MCATDL1AA1 CATALOG.V1R10.MZPLEX.MCATEOX CATALOG.V1R10.MZPLEX.MCATEOY CATALOG.V1R10.MZPLEX.MCATEPH CATALOG.V1R10.MZPLEX.MCATEUV CATALOG.V1R10.MZPLEX.MCATEUVF CATALOG.V1R10.MZPLEX.MCATFFST CATALOG.V1R10.MZPLEX.MCATGDDM CATALOG.V1R10.MZPLEX.MCATGIM CATALOG.V1R10.MZPLEX.MCATGLD CATALOG.V1R10.MZPLEX.MCATGSK CATALOG.V1R10.MZPLEX.MCATHCM CATALOG.V1R10.MZPLEX.MCATICQ CATALOG.V1R10.MZPLEX.MCATIMW CATALOG.V1R10.MZPLEX.MCATIOA CATALOG.V1R10.MZPLEX.MCATIOE CATALOG.V1R10.MZPLEX.MCATISF CATALOG.V1R10.MZPLEX.MCATISP CATALOG.V1R10.MZPLEX.MCATMZ1AA1 CATALOG.MZ1AA1.UCAT OMVS CATALOG.V1R10.MZPLEX.MCATSMPE CATALOG.DL1AA1.UCAT SMP1A CATALOG.DL1AA1.UCAT SYS1 CATALOG.V1R10.MZPLEX.MCATTCPIP CATALOG.V1R10.MZPLEX.MCAT

Note: Listed master catalog and user catalog names in black italic are preferred catalog names for z/OS 1.10, where assigned sysplex name is MZPLEX. Change it if you are using a different Sysplex name.



Catalogs Volume Assignement Table 31 Catalogs Volume Assignement

Catalogs Volume Assignement Volume Primary Space

(Cylinders)

Secundary Space

(Cylinders)CATALOG.MVSICFM.Vxxxxx Default CATALOG Volume 5 5CATALOG.MVSICFU.Vxxxxx Default CATALOG Volume 5 5

Specify where master and user catalogs will be allocated for your new system, and the space required for each catalog. As the default all catalog will be allocated on Catalog volume.

Static System Symbols Table 32 System Symbolic

Define System Symbols Yes/NoVolume

Define in SYMDEF in IEASYMxx Yes&SYSR1 MZ1AA1&SYSR2 MZ1AA2

Using Static System Symbols allows one to indirect reference more than one volume. Now you can change the volume serial number or device type of the additional volume or volumes used for z/OS SYSRES without also having to recatalog the non-VSAM datasets.

Please provide Symbol Names: NOTE: If symbolic definition is required (Y is chosen) then Y must be also entered for indirect catalog referencing.

Note: Listed volume names are preferred names for z/OS 1.10, where assigned sysplex prefix is MZ. Change it if you are using a different Sysplex prefix



SYSPLEX Naming StandardsSYSPLEX Name

A Parallel Sysplex is named in order to uniquely identify and handle each Parallel Sysplex. The sysplex name as implemented in z/OS is limited in length to 8 characters. System Symbolic: &SYSPLEX.

SYSPLEX Name Requirements: 1. Support multiple Sysplex Environments (Test, Development, Production, Maintenance)2. Support 64 Sysplex3. Max 8 Characters4. One Character for the PLEX environment allows it to be used in the SYSTEM NAME.

Suggestion: 1. Start Sysplex identification with “Z” and increment in reverse order’

Table 33 Proposed Sysplex Name

Position Description Sample

Sample TZPLEX T Sysplex Test Environment Z Sysplex ID 1

PLEX

Sysplex Name

1 Sysplex Environment T TEST EnvironmentM Maintenance EnvironmentD Development EnvironmentQ Quality Assurance EnvironmentP Production Environment

2 Sysplex ID Z Z - 03 - 6 Sysplex Name XXXXX

XSysplex Name

Symbolic &SYSPLEX.



System Name

Some products and data sets are shared between multiple systems. For example, if you share your sysres, a number of systems will all access the same SYS1.LINKLIB library.

However, there are some resources such as page data sets and STGINDX which are system specific and cannot be shared. The data set names of these resources should indicate which system they are used by.

A system name is used to identify and handle each system individually. Due to the use of the system name as part of the naming of other entities, and the MVS imposed limit of 8 characters for SYSNAME in SYS1.PARMLIB, its length is limited. As both the SMF ID and the member name within a MAS are limited to 4 characters, there are some benefits to restricting your system names to just 4 characters if you can fit sufficient information within that limitation.

System Name Requirements: 1. Support multiple system environments (Test, Development, Production, Maintenance)2. Support 64 Systems3. System Name = LPAR Name = SMFID = JES Member ID4. Max 4 Characters (to be compatible with SMFID and JES2 member)5. Derive the Sysplex Environment and ID where the system runs from the system name

Suggestion: 1. Start System identification with “1” and increment forward

Table 34 System Name


Sample TZT1 T Sysplex EnvironmentZ Sysplex IDT LPAR Environment1 LPAR Number

1 Sysplex Environment T TEST EnvironmentM Maintenance EnvironmentD Development EnvironmentQ Quality Assurance / Test EnvironmentP Production Environment

2 Sysplex ID X Z – 0 3 LPAR / System Environment T TEST Environment

M Maintenance EnvironmentD Development EnvironmentQ Quality Assurance EnvironmentP Production Environment

4 LPAR / System ID L 0 - Z Symbolic &SYSNAME

&SYSCLONE



SYSTEM Volume Names z/OS Volume names are limited to 6 positions.

System Volume Name Requirements: 1. z/OS Version Release for SYSRES (makes SYSRES Clone easier to understand)2. Logical SYSRES SET Identification (makes SYSRES Clone easier to understand)3. Identify Volume Content from Volume name.4. Identify Associated SYSPLEX from Volume name.5. Identify Associated System from volume name (system specific volumes)

Table 35 Volume Names


Sample SYSRES

TZ18A1 Sample SYSREST Test Sysplex EnvironmentZ Sysplex ID Z1 z/OS Version 18 z/OS Release 8A SYSRES SET A1 SYSRES SET Volume 1

Sample System Specific

T1PAG1 Sample System SpecificT Test System Environment 1 System ID 1

PAG

System Function

1 Volume 1Sample Sysplex Shared

TZSPL1 Sample Sysplex SharedT Test Sysplex Environment Z Stsplex ID Z

SPL System Function1 Volume 1

1 - 2 Sysplex Environment or System Specific (EI) E Sysplex or System EnvironmentsT = TEST PLEX or TEST SystemP = PROD PLEX or PROD SystemD = Development PLEX or DEV SystemQ = Quality Assurance PLEX or QA systemM = Maintenance PLEX or Maint System

I Sysplex id or System id F = 0 - Z

3 - 5 Level (VRS) for SYSRES or DLIB VR Level for SYSRES Volumes V = z/OS VersionR = z/OS Release

S SYSRES SETA = SYSRES or DLIB SET AB = SYSRES or DLIB SET BC = SYSRES or DLIB SET C

3 - 5 System Function xxx xxx System SpecificPAG = Page VolumeSMF = SMF

xxx Sysplex SharedSPL = SpoolLOG = LogrecCKP = CheckpointSEC = SecurityCDS = Couple DatasetsMCV = Master CatalogUCV = User CatalogSMP = SMPERMM = RMMHSM = HSMSTG = Storage (non SMS)SAD = Stand Alone Dump




6 Volume Number (V) V Volume Number V = (0 – Z)

Notes: The assumption is that all systems in the parallel sysplex share a master catalog and IPL off the same SYSRES SET. The Exception is new level of z/OS or an maintenance upgrade.



UNIX System Services File System (Shared)USS File System Name Requirements (SYSPLEX SHARED):

1. ZFS compatible mode (single files system per ZFS) 2. HLQ of VERSION should be equal to the First volume (&SYSR1) of the associated SYSRES

SET.3. Cataloged to a USER CATALOG that resides on the associated SYSRES SET

(CATALOG.&SYSR1.UCAT)4. All z/OS Components should be installed in a single version files system, creating separate

Files systems for individual z/OS components cause the management of the SYSRES SET to be more complex.

5. Version ZFS should not be SMS Managed6. System Specific File Systems MLQ should be equal to &SYSNAME7. SYSPLEX Specific File Systems MLQ should be equal to &SYSPLEX

Table 36 USS Files System (SYSPLEX Shared)


SampleSYSPLEX VERSION

&SYSR1.VERSION.ROOT MZ1AA1.VERSION.ROOT

SampleSYSPLEXROOT

OMVS.&SYSPLEX.ROOT OMVS.MZPLEX.ROOT

SampleSystem Specific

OMVS.&SYSNAME.ZFSOMVS.&SYSNAME.ZFS.ETCOMVS.&SYSNAME.ZFS.DEVOMVS.&SYSNAME.ZFS.VAROMVS.&SYSNAME.ZFS.TMP

OMVS.MZM1.ZFSOMVS.MZM1.ZFS.ETCOMVS.MZM1.ZFS.VAROMVS.MZM1.ZFS.DEVOMVS.MZM1.ZFS.TMP


Manual - IBM · Web view2008/10/30 · Name Phone Number Email TECH-LINE (if known) Email Tape...

Documents

Transcript of Manual - IBM · Web view2008/10/30 · Name Phone Number Email TECH-LINE (if known) Email Tape...