SystemPac Enrichment Form for IBM Rapid Deployment of z/os and DB2 (Version 1.1)

Transcription

1 IBM Global Technology Services SystemPac Enrichment Form for IBM Rapid Deployment of z/os and DB2 (Version 1.1) Updated: 2/10/2010 Customer Name Internal Use Only Page 1 of 19

2 Table of Contents Preface 3 Contacts 3 Instructions 4 Instructions for SystemPac Manufacturing 4 Initial Enrichment Data 5 Customer Contact Information 5 IBM Contact Information 5 Tape Media Selection 5 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 9 Terminal and Printer Information 10 I/O Configuration Information 10 Volume Layout 11 Additional build Instructions 12 UNIX File System 12 Indirect Catalog Option 12 SMPE Data sets 13 Master Catalog Options 16 Data set Names & User Catalog Options 17 Catalogs Volume Assignement 18 Static System Symbols 19 Customer Name Internal Use Only Page 2 of 19

3 Preface This format of the enrichment form is unique to the IBM Rapid Deployment of z/os and DB2 offering, and is used to collect customization data to tailor build your SystemPac. Upon completion of this form, please it back to IBM Manufacturing at If there are questions with this form, please raise them to the IBM personnel who sent this form to you. SUMMARY OF CHANGES: Date Change 03/06/2007 Original copy 04/05/2007 Updated Parallel Sysplex offerings 06/18/2007 Modified enrichment form to meet IBM Rapid Deployment of z/os and DB2 requirements 19/03/2008 Added Catalogs Volume assignment 26/09/2008 Added JES Subsystem selection 09/02/2010 Removed ISV customization questions Contacts Contact IBM Manufacturing UserId Customer Name Internal Use Only Page 3 of 19

4 Instructions NOTE: Please read these instructions carefully before filling out your portion of this enrichment form. When filling out this enrichment form, only fields that are designated with a red asterisk and are highlighted in yellow require your input. All other fields are predefined default values for this offering and may not be changed. To clarify, you are only to provide input into the fields of tables listed in the following section marked User input required. User input required For your reference, the following are links to the tables and pages that require your input. To link to that section of the document, enter CTRL + click with first mouse button. Once you input the required data, use the Return to Instructions link in the document to return to these instructions. Customer Contact Information (see page 5) IBM Contact Information (see page 5) Tape Media Selection (see page 5) CPU Information (see page 6) JES Subsystem selection (see page 7) Selective Follow-On Service (see page 7) Instructions for SystemPac Manufacturing NOTE: Please read additional build instructions required. For your reference, the following are links to additional instructions or notes that are unique to this IBM Rapid Deployment of z/os and DB2 offering order. To link to that section of the document, enter CTRL + click with first mouse button. Changes for Zone Nicknames/Zone Names (see page 9) Terminal and Printer Information (see page 10) I/O configuration information (see page 10) Additions to DASD and volume layout (see page 11) Additional build Instructions (see page 12) Additions to SMP/E data sets (see page 13) Customer Name Internal Use Only Page 4 of 19

5 Data set Names & User Catalog Options (see page 17) NOTE: Please note the unique default values that have been added for the IBM Rapid Deployment of z/os and DB2 Offering. Throughout this document, the additional unique default values are designated with the following: Defaults Unique to This Offering. Initial Enrichment Data Please fill out the appropriate fields, throughout the following Enrichment Form, according to the instructions on page 4. Once the form has been received, IBM will input the information into our Production System. IBM will then begin the build of your SystemPac. Customer Contact Information Table 1 Customer Contact Information Customer Name * Customer Number * Customer Contact * Phone Number * * Customer Mailing * Address for SystemPac Return to Instructions IBM Contact Information Table 2 IBM Contact Information Name * Phone Number * * TECH-LINE (if known) Return to Instructions Tape Media Selection Table 3 Media Selection Please select a media type for your SystemPac order. Customer Name Internal Use Only Page 5 of 19

6 High Density 138 Tracks 3592 High Density 512 Tracks Select Media Type Notes Return to Instructions CPU Information Table 4 CPU Information Enter CPU Info CPU TYPE * CPU Model * CPU Serial * CPU Indicator Return to Instructions System Name and Global CSI Selection Table 5 System Name and Global CSI Selection Enter Info Notes SYSNAME PRA1 Default is PRA1 Multiple GLOBAL CSI? (Yes or 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 Standalone Utility Tape Required Enter Info Yes Notes Yes is required because the 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 which will be used to initialize volumes and restore the tapes. Note: this option is only applicable to tape media delivery Customer Name Internal Use Only Page 6 of 19

7 JES Subsystem Table 7 JES Subsystem JES subsystem: JES2 or JES3 or Both Enter INFO Notes 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 SFSs 3 (0, 1, 2, or 3), default is 3. Frequency 30 Number of days between SFS Packages (Maximum 120 Days), default is 30. Electronic Delivery (via FTP) Yes (Yes or No) for Electronic Delivery * Required if Electronic Delivery is specified to Yes Customer Name Internal Use Only Page 7 of 19

8 Return to Instructions Customer Name Internal Use Only Page 8 of 19

9 Zone Nicknames/Zone Names Zone checking will be performed to ensure proper grouping/product compatibility and that products of different SRELs are not in the same zone. Default zone names have been provided; however, 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 8 and you want to assign specific zones to them, please add them to the table below or request a list of your ordered products. Table 9 SMPE ZONE Information Predefined values from Software Manufacturing Defaults Unique to This Offering Zone Description Target Zone Name DLIB Zone Name Change to Target Zone Name if Required Change to DLIB Zone Name if Required z/os Base MVST100 MVSD100 TZOS1AA DZOS1AA JES2 MVST110 MVSD110 TZOS1AA DZOS1AA JES3 MVST111 MVSD111 SDSF MVST112 MVSD112 DB2 DB2T300 DB2D300 TDB291A DDB291A 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 DBDDB2 Tools TDB2TUL DDB2TUL. 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. Customer Name Internal Use Only Page 9 of 19

10 Terminal and Printer Information Master Consoles Table 10 Master Consoles MVS Master Console Alternative Console Address Type Model Notes The address specified for the master console must be in the Nucleus Initialization Program (NIP) statement of your MVSCP or identified as a NIP console in the IODF. Valid values for MVS Master and JES3 Console are: 3270,3277, 3278 OR 3279 TSO Terminals Table 11 Local TSO Terminals Address Type Model Notes TSO TERM A minimum of 2 terminal addresses are required, however up to six addresses may be included. TSO TERM TSO TERM TSO TERM TSO TERM TSO TERM6 I/O Configuration Information Table 12 IODF IODF Input RDT.IODF00.CLUSTER Configuration EDT 00 Configuration ID PRDCNAO Customer Name Internal Use Only Page 10 of 19

11 DASD Please provide 3 SYSRES, 3 DLIB, 1 CATALOG and 1 SMP/E. If the order has many products, more volumes may be needed. Place third party (vendor) products on different packs, separate from IBM products, place subsystem on its own different pack(s). Enter Required Volume Information: Minimum DASD requirement 2 SYSRES volumes 2 DLIB volumes 1 Catalog volume 1 SMP/E volume Table 13 Volume Information Volume Type Volser Name (6 char, alphanum) Address (4 digits in hex) Unit Type (3390) Model SYSRES VOLUME #1 SYSRSA #2 SYSRSB #3 DLIB VOLUME #1 DLIB8A #2 DLIB8B #3 CATALOG VLUME DMCAT SMP/E VOLUME #1 SMPVOL #2 Volume Layout Table 14 Volume Layout for DB2 Products Type Volser Address Unit Model DB2 TARGET DSDBLA DB2 DLIB DSDBLA DB2 SMP SMPVOL DB2 Tools DSPROD NOTE: If an installation has limited volume space 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 (cphcpac@dk.ibm.com) about the situation. If during manufacturing, the specified number of volumes is 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. Customer Name Internal Use Only Page 11 of 19

12 Additional build Instructions NOTE: The following are additional build instructions for SystemPac Software Manufacturing. 1) Place the z/os target CSI and SMPLTS, SMPMTS, SMPSCDS, SMPSTS data sets on the SYSRES volume 2) Place the z/os DLIB CSI on the DLIB volume 3) On SMPVOL include the global CSI, SMPPTS and SMP related log data sets 4) The base DB2 SMP related data should go on DSDBLA volume 5) The DB2 tools SMP related data sets should go on DSPROD volume 6) Include the IODF on the catalog volume 7) Do NOT define OPERCNSL for standalone DFSMSdss utility UNIX File System Table 15 HFS or zfs SMS Options HFS or zfs Notes Build file system in zfs or HFS format? zfs Default is zfs Indirect Catalog Option NOTE: If indirect catalog referencing is not required (No is chosen) then No 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. Table 16 Indirect Catalog Option Catalog Options Does this order required Indirect Catalog Referencing? Yes or No Yes Customer Name Internal Use Only Page 12 of 19

13 SMPE Data sets SMPE VSAM Data sets 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 COBOLs can't live in the same zone. o Subsystems and their related products must live in the same zone (For example, GDDM for CICS has to be in the same zone as CICS itself) Table 17 Single SMPE Global For Single Global CSI Names Predefined values from Software Manufacturing Default Zone CSI Name Defaults Unique to This Offering Change To Zone CSI Name if Required MVS GLOBAL CSI: SMPE.GLOBAL.CSI SMPE.GLOBAL.CSI TARGET MVS SMPE.MVS.TARGET.CSI TZOS1AA.TARGET.CSI DLIB MVS SMPE.MVS.DLIB.CSI DZOS1AA.DLIB.CSI TARGET DB2 SMPE.DB2.TARGET.CSI TDB291A.TARGET.CSI DLIB DB2 SMPE.DB2.DLIB.CSI DDB291A.DLIB.CSI TARGET DB2 TDB2TUL.TARGET.CSI Tools DLIB DB2 Tools DDB2TUL.DLIB.CSI Customer Name Internal Use Only Page 13 of 19

14 SMPE TARGET & DLIB Non-VSAM Data sets NOTE: To software manufacturing, see changed zone names in table below. Table 18 SMPE Target & DLIB Non-VSAM Predefined Values from Software Manufacturing ZONE SREL/ Zone Name MVS Defaults Unique to This Offering Change to ZONE SREL/Zone Name MVS GLOBAL SMPE DDDEF DDNAME Predefined Values from Software Manufacturing Data Set Name Defaults Unique to This Offering Change to Data Set Name if Required Zone Type SMPGLOG SMPE.SMPGLOG SMPE.SMPGLOG GLOBAL SMPGLOGA SMPE.SMPGLOGA SMPE.SMPGLOGA GLOBAL SMPPTS SMPE.SMPPTS SMPE.SMPPTS GLOBAL DB2D300 DDB291A SMPDLOG SMPE.DB2D300.SMPDLOG SMPE.DB291A.SMPDLOG DLIB SMPDLOGA SMPE.DB2D300.SMPDLOGA SMPE.DB291A.SMPDLOGA DLIB DB2T300 TDB291A SMPLTS SMPE.DB2T300.SMPLTS SMPE.DB291A.SMPLTS TARGET SMPMTS SMPE.DB2T300.SMPMTS SMPE.DB291A.SMPMTS TARGET SMPSCDS SMPE.DB2T300.SMPSCDS SMPE.DB291A.SMPSCDS TARGET SMPSTS SMPE.DB2T300.SMPSTS SMPE.DB291A.SMPSTS TARGET SMPTLOG SMPE.DB2T300.SMPTLOG SMPE.DB291A.SMPTLOG TARGET SMPTLOGA SMPE.DB2T300.SMPTLOGA SMPE.DB291A.SMPTLOGA TARGET MVSD100 (MVS) MVSD110 (JES2) MVSD111 (JES3) DZOS1AA SMPDLOG SMPE.MVSD100.SMPDLOG SMPE.ZOS1AA.SMPDLOG DLIB SMPDLOGA SMPE.MVSD100.SMPDLOGA SMPE.ZOS1AA.SMPDLOGA DLIB DZOS1AA SMPDLOG SMPE.MVSD110.SMPDLOG SMPE.ZOS1AA.SMPDLOG DLIB SMPDLOGA SMPE.MVSD110.SMPDLOGA SMPE.ZOS1AA.SMPDLOGA DLIB SMPDLOG SMPE.MVSD111.SMPDLOG DLIB SMPDLOGA SMPE.MVSD111.SMPDLOGA DLIB Customer Name Internal Use Only Page 14 of 19

15 Predefined Values from Software Manufacturing ZONE SREL/ Zone Name MVSD112 (SDSF) Defaults Unique to This Offering Change to ZONE SREL/Zone Name SMPE DDDEF DDNAME Predefined Values from Software Manufacturing Data Set Name Defaults Unique to This Offering Change to Data Set Name if Required SMPDLOG SMPE.MVSD112.SMPDLOG DLIB SMPDLOGA SMPE.MVSD112.SMPDLOGA Zone Type DLIB MVST100 TZOS1AA SMPLTS SMPE.MVST100.SMPLTS SMPE.ZOS1AA.SMPLTS TARGET SMPMTS SMPE.MVST100.SMPMTS SMPE.ZOS1AA.SMPMTS TARGET SMPSCDS SMPE.MVST100.SMPSCDS SMPE.ZOS1AA.SMPSCDS TARGET SMPSTS SMPE.MVST100.SMPSTS SMPE.ZOS1AA.SMPSTS TARGET SMPTLOG SMPE.MVST100.SMPTLOG SMPE.ZOS1AA.SMPTLOG TARGET SMPTLOGA SMPE.MVST100.SMPTLOGA SMPE.ZOS1AA.SMPTLOGA TARGET MVST110 (JES2) TZOS1AA SMPLTS SMPE.MVST110.SMPLTS SMPE.ZOS1AA.SMPLTS TARGET SMPMTS SMPE.MVST110.SMPMTS SMPE.ZOS1AA.SMPMTS TARGET SMPSCDS SMPE.MVST110.SMPSCDS SMPE.ZOS1AA.SMPSCDS TARGET SMPSTS SMPE.MVST110.SMPSTS SMPE.ZOS1AA.SMPSTS TARGET SMPTLOG SMPE.MVST110.SMPTLOG SMPE.ZOS1AA.SMPTLOG TARGET SMPTLOGA SMPE.MVST110.SMPLOGA SMPE.ZOS1AA.SMPTLOGA TARGET MVST111 (JES3) SMPLTS SMPE.MVST111.SMPLTS TARGET SMPMTS SMPE.MVST111.SMPMTS TARGET SMPSCDS SMPE.MVST111.SMPSCDS TARGET SMPSTS SMPE.MVST111.SMPSTS TARGET SMPTLOG SMPE.MVST111.SMPTLOG TARGET SMPTLOGA SMPE.MVST111.SMPLOGA TARGET MVST112 (SDSF) TZOS1AA SMPLTS SMPE.MVST111.SMPLTS SMPE.ZOS1AA.SMPLTS TARGET Customer Name Internal Use Only Page 15 of 19

16 Predefined Values from Software Manufacturing ZONE SREL/ Zone Name Defaults Unique to This Offering Change to ZONE SREL/Zone Name SMPE DDDEF DDNAME Predefined Values from Software Manufacturing Data Set Name Defaults Unique to This Offering Change to Data Set Name if Required Zone Type SMPMTS SMPE.MVST112.SMPMTS SMPE.ZOS1AA.SMPMTS TARGET SMPSCDS SMPE.MVST112.SMPSCDS SMPE.ZOS1AA.SMPSCDS TARGET SMPSTS SMPE.MVST112.SMPSTS SMPE.ZOS1AA.SMPSTS TARGET SMPTLOG SMPE.MVST112.SMPTLOG SMPE.ZOS1AA.SMPTLOG TARGET SMPTLOGA SMPE.MVST112.SMPLOGA SMPE.ZOS1AA.SMPTLOGA TARGET DDB2TUL SMPDLOG SMPE.DB2TUL.SMPDLOG DLIB SMPDLOGA SMPE.DB2TUL.SMPDLOGA DLIB TDB2TUL SMPLTS SMPE.DB2TUL.SMPLTS TARGET SMPMTS SMPE.DB2TUL.SMPMTS TARGET SMPSCDS SMPE.DB2TUL.SMPSCDS TARGET SMPSTS SMPE.DB2TUL.SMPSTS TARGET SMPTLOG SMPE.DB2TUL.SMPTLOG TARGET SMPTLOGA SMPE.DB2TUL.SMPTLOGA TARGET Master Catalog Options Table 19 Master Catalog Options Master Catalog Master Catalog Name Defaults Unique to This Offering MASTER.DRIVING.CATALOG Customer Name Internal Use Only Page 16 of 19

17 Data set 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. Important Notice: 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 20 Data set & User Catalogs Predefined Values from Software Manufacturing ALIAS Defaults Unique to This Offering ALIAS (User defined) Target System Catalog (Default is Master Catalog or Specify User Catalog) ANF AOP ASM CBC CDS CEE CMX CPAC MUST BE IN MASTER CATALOG DMCAT CSF DSN910 DB2910.SETA USERCAT.DSDBLA.DB2910 DSDBLA ADB USERCAT.DSPROD.DB2TOOLS DSPROD ANL USERCAT.DSPROD.DB2TOOLS DSPROD ARY USERCAT.DSPROD.DB2TOOLS DSPROD CKZ USERCAT.DSPROD.DB2TOOLS DSPROD DAH USERCAT.DSPROD.DB2TOOLS DSPROD DDA USERCAT.DSPROD.DB2TOOLS DSPROD EGF USERCAT.DSPROD.DB2TOOLS DSPROD FEC USERCAT.DSPROD.DB2TOOLS DSPROD GOC USERCAT.DSPROD.DB2TOOLS DSPROD HAA USERCAT.DSPROD.DB2TOOLS DSPROD TZOS1AA USERCAT.SYSRSA SYSRSA DZOS1AA USERCAT.DLIB8A DLIB8A TDB291A USERCAT.DSDBLA.DB2910 DSDBLA DDB291A USERCAT.DSDBLA.DB2910 DSDBLA TDB2TOOL USERCAT.DSPROD.DB2TOOLS DSPROD DDB2TOOL USERCAT.DSPROD.DB2TOOLS DSPROD EOY EPH EUV FFST Catalog Volume (Additions to This Offering) Customer Name Internal Use Only Page 17 of 19

18 Predefined Values from Software Manufacturing Defaults Unique to This Offering Target System Catalog Catalog Volume ALIAS (Default is Master Catalog or (Additions to ALIAS (User defined) Specify User Catalog) This Offering) GDDM GIM GLD GSK HCM ICA ICF ICQ IMW IOA IOE ISF ISP NETVIEW OMVS OMVSD USERCAT.DMCAT DMCAT REXX SCRIPT SMPE SYS1 MUST BE IN MASTER CATALOG TCPIP TIVOLI Catalogs Volume Assignement Table 21 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. Customer Name Internal Use Only Page 18 of 19

19 Static System Symbols Using Static System Symbols allows you 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 (Yes is chosen) then Yes must be also entered for indirect catalog referencing. Table 22 System Symbolic Define System Symbols Volume (Yes or No) Notes Define in SYMDEF in Yes Default is Yes IEASYMxx &SYSR1 Yes Default is Yes &SYSR2 Yes Default is Yes Customer Name Internal Use Only Page 19 of 19