SystemPac Enrichment Form · 2020. 5. 13. · SYSTEMPAC DESIGN GUIDE . Preface. This enrichment form is to collect customization data to tailor build your SystemPac. Upon completion

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

IBM Global Technology Services

SystemPac Enrichment

Form (Version 1.1)

Updated: 15/10/2012

Customer Name Internal Use Only Page 1 of 20


INITIAL ENRICHMENT DATA ....................................................................................................................................... 5

CUSTOMER CONTACT INFORMATION ................................................................................................................................... 5 IBM CONTACT INFORMATION.............................................................................................................................................. 5 PACKAGE MEDIA SELECTION............................................................................................................................................... 5 HARDCOPY MANUALS ......................................................................................................................................................... 6 CPU INFORMATION.............................................................................................................................................................. 6 SYSTEM NAME AND GLOBAL CSI SELECTION...................................................................................................................... 6 STANDALONE UTILITY TAPE................................................................................................................................................ 6 JES SUBSYSTEM................................................................................................................................................................... 7 SELECTIVE FOLLOW-ON SERVICE........................................................................................................................................ 7 ZONE NICKNAMES/ZONE NAMES:........................................................................................................................................ 1 SMPTLIB INFORMATION..................................................................................................................................................... 2 TERMINAL AND PRINTER INFORMATION .............................................................................................................................. 1

Master Consoles............................................................................................................................................................... 1 TSO Terminals ................................................................................................................................................................. 1

I/O CONFIGURATION INFORMATION..................................................................................................................................... 1 OTHER VARIABLES .............................................................................................................................................................. 1 DASD.................................................................................................................................................................................. 2 VOLUME LAYOUT........................................................................................................................................................... 3 UNIX FILE SYSTEM .............................................................................................................................................................. 3 SMS MANAGED DATA SETS ................................................................................................................................................ 4 INDIRECT CATALOG OPTION ................................................................................................................................................ 4 SMPE DATASETS................................................................................................................................................................. 5

SMPE VSAM Datasets ..................................................................................................................................................... 5 SMPE Global, TARGET & DLIB Non-VSAM Datasets Prefix ........................................................................................ 7

MASTER CATALOG OPTIONS................................................................................................................................................ 7 DATASET NAMES & USER CATALOG OPTIONS .................................................................................................................... 8 CATALOGS VOLUME ASSIGNEMENT .................................................................................................................................... 9 STATIC SYSTEM SYMBOLS ................................................................................................................................................. 10



Preface

This enrichment form is to collect customization data to tailor build your SystemPac. 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 copy 04/05/2007 Updated Parallel Sysplex offerings 11/06/2007 CICS SVC’s 13/06/2007 Removed 3380 DASD device type 12/11/2007 Added Internet option in media selection list 19/03/2008 Added Catalogs Volume assignment 26/09/2008 Added JES Subsystem selection 02/11/2009 Replaced SMP/E Non-VSAM data sets list with data sets prefix 09/02/2010 Removed ISV customization questions 23/06/2010 Removed SYNCSORT Alias and CPU Capacity 24/09/2010 Added new supported customization questions 16/09/2011 Updated z/OS 1.3 CustomPac process based supported customization questions 15/10/2012 Removed IBM Implementation Services for Parallel Sysplex questions

Contacts Contact

userid

IBM Manufacturing [email protected]





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.

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

Package Media Selection Media Selection was made at time of order, please indicate a change if necessary.

Table 3 Media Selection

SELECT MEDIA TYPE 3590 - High Density 128 Tracks 3592 – High Density 512 Tracks DVD - 4.7GB Internet using ShopzSeries

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.



Hardcopy Manuals Table 4 Hardcopy Manuals

Enter Selection Notes Installation Guide (Y–Yes, N-No) – default is No CustomPac Dialog Reference Manual (Y–Yes, N-No) – default is No CustomPac Message Manual (Y–Yes, N-No) – default is No

Select Manuals which hardcopy you would like to be printed and included in your SystemPac order package. If not specified, default is delivering Manuals only in softcopy.

CPU Information Table 5 CPU Information

Enter CPU INFO Notes CPU TYPE CPU Model CPU Serial

System Name and Global CSI Selection Table 6 System Name and Global CSI Selection

Enter INFO Notes SYSNAME Default is CPAC Multiple GLOBAL CSI? (Yes/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 7 Standalone Utility Tape

Enter INFO Notes Standalone Utility Tape Required 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 is option is only applicable to tape media delivery, not DVD media and Internet




JES Subsystem Table 8 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 9 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


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 11 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 11 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 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: 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). Starting with z/OS R12 SDSF zone you can merge it with JES2 or JES3 zone specifying there zone names (ex. MVST110/MVSD110 or MVST111/MVSD111). 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.

Note: WebSphere for z/OS zone will be assigned only if WebSphere Application Server is ordered. It is not applicable for other products from WebSphere product catalog, like WebSphere MQ.




SMPTLIB Information

Table 12 SMPTLIB Information

SMPTLIB Information

SMPTLIB data prefix (ex. SYS1.MVS) SMPTLIB SMS on Managed DASD? (Yes/No)

SPMTLIB SMS managed SMPTLIB Storage Class:

SPMTLIB not SMS managed SMPLIB Unit Type (ex SYSDA) SMPTLIB Volume 1 (max 6 characters) SMPTLIB Volume 2 (max 6 characters) SMPTLIB Volume 3 (max 6 characters) SMPTLIB Volume 4 (max 6 characters) SMPTLIB Volume 5 (max 6 characters)


Terminal and Printer Information

If you plan to provide IODF configuration file to be used during manufacturing your SystemPac order, review “Master Consoles and TSO Terminals questions and provide input information.

Master Consoles Table 13 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 14 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 15 IODF

IODF Input Configuration EDT Configuration ID



Other Variables

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

Table 16 IMS

DBRC Type 4 SVC 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 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



DASD Please provide 3 SYSRES, 3 DLIB, 1 CATALOG and 1 SMP. Place subsystem on its own different pack(s). 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 #2 #3

DLIB VOLUME #1 #2 #3

CATALOG VOLUME SMP/E VOLUME #1

#2 Minimum DASD requirement: 3 SYSRES volumes 3 DLIB volumes 1 Catalog volume 1 SMP volume NOTE: If 3390-27 is selected for any volume type, 3390-27 volumes can be populated only up to 8GB (10,000 cyls) due to current IBM CustomPac manufacturing limitation using GIMZIP when Internet or DVD is selected as the delivery option.



VOLUME LAYOUT

Table 19 Volume Layout

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

NOTE: If an installation is really tight on volumes and there are not a lot of products ordered, 2 SYSRES and 2 DLIBs may be enough to hold the content. Under such circumstances, contact CustomPac Support Group ([email protected]) about the situation. Should during manufacturing, the specified number of volumes are not enough to hold the content, I/T specialist will be informed to obtain more volumes from the customer. Only resolve to use this if number of volumes is a critical factor in an installation. Remember that in so doing, this may cause a delay in manufacturing. If using 3390 Mod 9's - then one RES and one DLIB is usually enough. Unix File System

Table 20 HFS or zFS

Unix File System Option

HFS/zFS

Build file system in zFS or HFS format? Default is zFS Volume Type Volser

Name (6 char, alphanum)

Address (4 digits in hex)

Unit Type (3390)

Model

File System Volume #1 #2

Note: If HFS/zFS volume(s) are not specified, as default, File System data sets will be allocated on SYSRES volume(s). In addition, this volume table information will only used when “No” is answered for question “Want to build Unix HFS and zFS data sets on SMS managed DASD?”. The default DASD is 3390-9.



SMS Managed Data Sets

Table 21 SMS Options

SMS Options

YES/NO

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

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

Table 22 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 23 Indirect Catalog Option

Catalog Options

YES/NO

Does this order required Indirect Catalog Referencing?

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 characters o 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)

Table 24 Single SMPE Global

FOR SINGLE GLOBAL CSI NAMES

DEFAULT ZONE CSI NAME CHANGE TO CSI NAME IF REQUIRED

MVS GLOBAL CSI: SMPE.GLOBAL.CSI TARGET MVS SMPE.MVS.TARGET.CSI DLIB MVS SMPE.MVS.DLIB.CSI 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



Table 25 Multi-SMPE Global

FOR MULTIPLE GLOBAL CSI NAMES

DEFAULT ZONE CSI NAME CHANGE TO CSI NAME IF REQUIRED

MVS SMPE.MVS.GLOBAL.CSI SMPE.MVS.TARGET.CSI

SMPE.MVS.DLIB.CSI

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: o Must conform to normal DSN requirements (e.g. less than 44 chars) o DSN's must end with .CSI o 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



SMPE Global, TARGET & DLIB Non-VSAM Datasets Prefix Table 26 SMPE Global, TARGET & DLIB Non-VSAM Datasets Prefix

ZONE SREL

SMPE data sets type

Default Dataset prefix

Zone Type

Changes to if required Comment

CICS SMPE Global SMPE.CICS GLOBAL SMPE Target SMPE TARGET

SMPE DLIB SMPE DLIB DB2 SMPE Global SMPE.DB2 GLOBAL

SMPE Target SMPE TARGET

SMPE DLIB SMPE DLIB IMS SMPE Global SMPE.IMS GLOBAL


SMPE DLIB SMPE DLIB NCP SMPE Global SMPE.NCP GLOBAL


SMPE DLIB SMPE DLIB MVS SMPE Global SMPE.MVS GLOBAL


SMPE DLIB SMPE DLIB

Master Catalog Options Table 27 Master Catalog Options

Master Catalog Options

Default is: CATALOG.MVSICFM.Vxxxxx = xxxxxx = VOLSER of Catalog

Master Catalog Name



Dataset Names & User Catalog Options You 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 28 Dataset & User Catalogs

ALIAS (Default)

ALIAS (User Defined)

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

ACFNCP AOP ASM BBO BDT1 BLM BPA CBC CDS CEE CFZ CICS CICSTS41 CIM CIZ CMX CPAC MUST BE IN MASTER CATALOG CSF CYE DSN910 DYZ EOX EOY EPH EUV EUVF FFST GDDM GIM GLD GSK HAP HCM ICQ IMS1010 IMW ING IOA




ALIAS (Default)

ALIAS (User Defined)

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

IOE IRLMV2 ISF ISP IWO OMVS REXX SMPE SYS1 MUST BE IN MASTER CATALOG TCPIP TCPIVP

Catalogs Volume Assignement Table 29 Catalogs Volume Assignement

Catalogs Volume Assignement

Volume Primary Space

(Cylinders)

Secundary Space

(Cylinders) CATALOG.MVSICFM.Vxxxxx Default CATALOG Volume 5 5 CATALOG.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

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.

Table 30 System Symbolic

System Symbol Names Default

System Symbol Names Change to

Yes/No Volume

Define in SYMDEF in IEASYMxx &SYSR1 &SYSR2 &SYSR3

SystemPac limits the Symbol Names to 6 characters including the “&”. NOTE: If symbolic definition(s) is required (Y is chosen) then Y must be also entered for indirect catalog referencing.

Documents

SystemPac Enrichment Form · 2020. 5. 13. · SYSTEMPAC DESIGN GUIDE . Preface. This enrichment form is to collect customization data to tailor build your SystemPac. Upon completion