custompac installation dialog dialog level: 27€¦ · custompac installation dialog reference...

CustomPac Installation DialogReference Manual

Dialog Level: 27

Document Number WWCP-28-0102-16

July 26, 2016

CustomPac Development, IBM TSS/EMEA

WWCP-28-0102-16

CustomPac Installation DialogReference ManualDialog Level: 27

Fourteenth Edition, Jul 2016

Printed: July 26, 2016

This edition applies to Dialog Level 27, and to CustomPac (program number 5751-CS4), and to any subsequentreleases until otherwise indicated in new editions or technical newsletters.

This publication was formatted using the Document Composition Facility (SCRIPT) and BookMaster programproducts and printed on IBM Advanced Function Printer.

© Copyright International Business Machines Corporation 1996-2016. All rights reserved.Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure issubject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.

Contents

Chapter 1. General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Preparing to install your CustomPac order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Orders from tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Orders from a server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Orders from DVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Driving System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3SMS Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Security Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Language Environment Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4CustomPac Offerings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 2. Understanding The Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Language Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7ISPF Edit CAPS Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Use of Colour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Sample Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Table Display MODES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Table Display Panel Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9OFILE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Dynamic HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 3. Installing and Starting the Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . 15Summary of tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Allocating and Cataloging the Dialog Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . 16Updating your dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Copying the UPDATE job from tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Copying the UPDATE job from DVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Downloading the EUPDATES or EUPDATEH job from a server . . . . . . . . . . . . . . . 19Installing the dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Starting the Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 4. Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Primary Option Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Chapter 5. Receiving a New Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Required Migration Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Beginning the receive process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Order Replace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Confirm Deletion of data sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Receiving an Order from Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Receiving an Order from the File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Receiving an Order from a Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Generating the RECEIVE Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Chapter 6. Installing the New Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Selecting an Order to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Installation Options Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Chapter 7. Creating a work Configuration for the Order . . . . . . . . . . . . . . . . . 56Choosing the Installation type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Selecting a JES for the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Contents iii

Creating the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Merging a configuration with a previous order . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Chapter 8. Defining Installation Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Variable Selection List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Selecting new values for the variables in your order . . . . . . . . . . . . . . . . . . . . . . . 79BROWSE Variable Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81DELETE a USER Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82EDIT Variable Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83INSERT a USER Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85RESTORE a Variable to the SHIPPED Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Chapter 9. Defining the SMP/E zone configuration . . . . . . . . . . . . . . . . . . . . . . 88How zone names are used in your order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Changing the SMPTLIB and zone names in your order . . . . . . . . . . . . . . . . . . . . . . 94Confirm Processing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Chapter 10. Update Configuration with Target Environment Data . . . . . . . . . . . 97Updating the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Chapter 11. Modify the System Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Important Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Modify System Layout Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Creating the Recommended System Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Viewing and Changing Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Displaying Device Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168Handling user data sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Displaying a Summary of Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Displaying a Summary of Physical Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Confirming Processing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Chapter 12. Defining Alias-to-Catalog Connections . . . . . . . . . . . . . . . . . . . . 187Define CATALOG data set Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187DELETE a USER Defined Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189INSERT a USER Defined Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190Confirm Processing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Chapter 13. Defining SSA-to-Catalog Connections . . . . . . . . . . . . . . . . . . . . . 192CATALOG Selection List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Define SSA and CATALOG Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Defining SSA data for software upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195Confirm Processing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Chapter 14. Submitting Installation Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198JOB Selection List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Generate Installation Jobs (GENSKEL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202Selecting Job Output Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203Processing LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204Delete a USER Defined JOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205INSERT a USER Defined JOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205EDIT Session - B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208EDIT Session - E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209EDIT Session - S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Chapter 15. Saving the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

iv CustomPac Installation Dialog Reference Manual

Chapter 16. Managing the Order Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . 214Selecting an Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Displaying an Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Deleting an Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217Editing an Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218Displaying Products/FMIDs for an Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220Displaying the FMIDs for a product or feature . . . . . . . . . . . . . . . . . . . . . . . . . . 221Report Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222Verifying the Status of an Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Appendixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Appendix A. Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226Using assistive technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226Keyboard navigation of the user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226z/OS information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Appendix B. Readers Comment Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Contents v

Figures

1. Sample TABLE Display (TErse MODE) . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2. Sample TABLE Display (VErbose MODE) . . . . . . . . . . . . . . . . . . . . . . . . . 8 3. Dialog Data Sets Must Remain in Their Original Formats . . . . . . . . . . . . . . . . 17 4. Panel: Copying the UPDATE job from the "system and . . . . . . . . . . . . . . . . . 17 5. Panel: Copying the LOADRIM job from the "system and . . . . . . . . . . . . . . . . 20 6. CPPPPOLI - Primary Option Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 7. CPPP610A - Receive an Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 8. CPPP6104 - Order Receive - Replace Order in Order Inventory . . . . . . . . . . . . 33 9. CPPP6102 - Order Receive - Confirm Deletion of data sets . . . . . . . . . . . . . . . 3510. CPPP6101 - Receive an Order From Tape . . . . . . . . . . . . . . . . . . . . . . . . . . 3611. CPPP610G - Receive an Order From the File System . . . . . . . . . . . . . . . . . . 3712. CPPP610B - Download Server Information . . . . . . . . . . . . . . . . . . . . . . . . . 3713. CPPP610C - Download File System Information . . . . . . . . . . . . . . . . . . . . . 3814. CPPP610F - Specify download method . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4015. CPPP610D - Download Client Information . . . . . . . . . . . . . . . . . . . . . . . . . 4016. CPPPEDIF Panel With Firewall Commands . . . . . . . . . . . . . . . . . . . . . . . . 4117. CPPP610D Download Client Information . . . . . . . . . . . . . . . . . . . . . . . . . . 4218. CPPPEDIF panel with HTTP or SOCKS proxy server statements . . . . . . . . . . 4319. CPPP610S Specify Secure FTP Options . . . . . . . . . . . . . . . . . . . . . . . . . . . 4320. CPPPEDIF panel with secure FTP commands . . . . . . . . . . . . . . . . . . . . . . . 4421. CPPP610S Specify Secure FTP Options . . . . . . . . . . . . . . . . . . . . . . . . . . . 4422. CPPP6103 - Edit JOB Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4523. CPPPEDIF Panel With JOB Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4524. CPPP610E - Edit RECEIVE Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4625. CPPPEDIF Panel With Receive Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4626. CPPP6071 - Install Orders - Order List . . . . . . . . . . . . . . . . . . . . . . . . . . . 4927. CPPP6072 - Install Orders - Order List . . . . . . . . . . . . . . . . . . . . . . . . . . . 4928. CPPPFLOW - Installation Options Menu for SystemPac/FunctionPac . . . . . . . . 5229. CPPPFLOW - Installation Options Menu for ProductPac . . . . . . . . . . . . . . . . 5230. CPPPFLOW - Installation Options Menu for RefreshPac . . . . . . . . . . . . . . . . 5331. CPPP6015 - Type of Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5632. Panel: JES Element Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5733. CPPP6011 - Select Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5934. CPPP6011 - Select configuration (configuration created) . . . . . . . . . . . . . . . . 6035. CPPP6013 - MERGE Configurations - Confirmation . . . . . . . . . . . . . . . . . . . 6136. CPPP6013 - MERGE Configurations - Confirmation . . . . . . . . . . . . . . . . . . . 6237. CPPP6012 - DELETE an EXISTING Configuration - Confirmation . . . . . . . . . 6238. Which Values are Used in a Merged Configuration . . . . . . . . . . . . . . . . . . . . 6539. CPPP6014 - Configuration Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6640. Data Set Merge Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7341. CPPP6111 - Variable Selection List - Variable Synonym . . . . . . . . . . . . . . . . 7642. CPPP6112 - Variable Selection List - Variable Name . . . . . . . . . . . . . . . . . . 7743. Installation variables that require some planning . . . . . . . . . . . . . . . . . . . . . . 8044. CPPP6113 - BROWSE Variable Definition - Value . . . . . . . . . . . . . . . . . . . . 8145. CPPP6114 - BROWSE Variable Definition - Usage . . . . . . . . . . . . . . . . . . . 8246. CPPP611D - DELETE a USER Variable - Confirmation . . . . . . . . . . . . . . . . 8347. CPPP6115 - UPDATE Variable Definition - Value . . . . . . . . . . . . . . . . . . . . 8448. CPPP6116 - UPDATE Variable Definition - Usage . . . . . . . . . . . . . . . . . . . . 8449. CPPP6117 - INSERT a USER Variable - Value . . . . . . . . . . . . . . . . . . . . . . 8550. CPPP6118 - INSERT a USER Variable - Usage . . . . . . . . . . . . . . . . . . . . . . 8651. CPPP611S - RESTORE a Variable - Confirmation . . . . . . . . . . . . . . . . . . . . 87

vi CustomPac Installation Dialog Reference Manual

52. CPPP6390 - Global CSI Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8853. CPPP6390 - Global CSI Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8954. CPPP639A - Modify Zones & Installation Manager Information . . . . . . . . . . . 8955. CPPP6398 - IM Installed Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9056. CPPP6399 - IM-installed products (verbose mode) . . . . . . . . . . . . . . . . . . . . 9057. CPPP639$ - Confirming processing requirements . . . . . . . . . . . . . . . . . . . . . 9158. CPPP6391 - Define SMPTLIB and Zone names with no selected for . . . . . . . . 9259. CPPP6391 - Define SMPTLIB and Zone names with yes . . . . . . . . . . . . . . . . 9260. CPPP6396 - Define SMPTLIB and Zone names . . . . . . . . . . . . . . . . . . . . . . 9361. CPPP6395 - Define SMPTLIB and Zone names . . . . . . . . . . . . . . . . . . . . . . 9362. CPPP6397 - Confirm Processing Requirements . . . . . . . . . . . . . . . . . . . . . . 9663. CPPP6393 - Confirm Processing Requirements . . . . . . . . . . . . . . . . . . . . . . 9664. CPPP6230 - Confirm continue processing . . . . . . . . . . . . . . . . . . . . . . . . . . 9765. CPPPMLOG - Update Configuration Message Panel . . . . . . . . . . . . . . . . . . . 9866. CPPP6233 - Indirect Reference Volume dialog box . . . . . . . . . . . . . . . . . . . . 9967. CPPP6233 - Indirect Reference Volume dialog box (Symbolic) . . . . . . . . . . . . 9968. CPPP6232 - Data Sets Names Conflict dialog . . . . . . . . . . . . . . . . . . . . . . 10069. CPPP6237 - GLOBAL Change - Candidate List . . . . . . . . . . . . . . . . . . . . . 10170. CPPP6238 - GLOBAL IGnoreNew - Candidate List . . . . . . . . . . . . . . . . . . 10371. CPPP6231 - Update Configuration Report . . . . . . . . . . . . . . . . . . . . . . . . . 10472. CPPP6231 - Execution Summary messages . . . . . . . . . . . . . . . . . . . . . . . . 10673. A Way of Organizing Your Volume Information... . . . . . . . . . . . . . . . . . . . 10874. CPPP605T - Modify System Layout Options . . . . . . . . . . . . . . . . . . . . . . . 10975. CPPP625B - Automatic Data Set Assignment . . . . . . . . . . . . . . . . . . . . . . 11376. CPPP625C - Current Volume Configuration . . . . . . . . . . . . . . . . . . . . . . . 11577. CPPP625D - Display and Change Volume Attributes . . . . . . . . . . . . . . . . . . 11878. CPPP625B - Automatic Data Set Assignment . . . . . . . . . . . . . . . . . . . . . . 11979. CPPP625C - Current Volume Configuration . . . . . . . . . . . . . . . . . . . . . . . 12080. CPPP625E - Automatic Assignment Confirmation . . . . . . . . . . . . . . . . . . . 12081. CPPPMLOG - Automatic Assignment Progress Panel . . . . . . . . . . . . . . . . . 12182. CPPP625C - Current Volume Configuration . . . . . . . . . . . . . . . . . . . . . . . 12183. CPPP625B - Automatic Data Set Assignment . . . . . . . . . . . . . . . . . . . . . . 12284. CPPP625C - Current Volume Configuration . . . . . . . . . . . . . . . . . . . . . . . 12385. CPPP625E - Automatic Assignment Confirmation . . . . . . . . . . . . . . . . . . . 12486. CPPP625C - Current Volume Configuration . . . . . . . . . . . . . . . . . . . . . . . 12587. CPPP625B - Automatic Data Set Assignment . . . . . . . . . . . . . . . . . . . . . . 12688. CPPP625C - Current Volume Configuration . . . . . . . . . . . . . . . . . . . . . . . 12789. CPPP625C - Current Volume Configuration . . . . . . . . . . . . . . . . . . . . . . . 12890. CPPP625B - Automatic Data Set Assignment . . . . . . . . . . . . . . . . . . . . . . 12991. CPPP625C - Current Volume Configuration . . . . . . . . . . . . . . . . . . . . . . . 13092. CPPP625C - Current Volume Configuration . . . . . . . . . . . . . . . . . . . . . . . 13193. CPPP605R - Select a Data Set View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13394. CPPP605S - Select Values to Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13495. CPPP605U - Data Set List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

| 96. CPPP605S - Panel: Select values to display . . . . . . . . . . . . . . . . . . . . . . . . 136| 97. CPPP60E4 - Panel: Data set list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136| 98. CPPP60E4 - Panel: Data set list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137| 99. CPPP605S - Panel: Select values to display . . . . . . . . . . . . . . . . . . . . . . . . 137

100. CPPP6050 - Global Change - Candidate List for Data Set Attributes . . . . . . . . 138101. CPPP6057 - Global Change - Candidate List for Data Set Space Values . . . . . 139102. CPPP605M - Data Set Merge Candidates . . . . . . . . . . . . . . . . . . . . . . . . . 151103. CPPP605V - Data Set Merge Candidates for UNIX File System Data Sets . . . . 153

| 104. CPPP60E1 - Merge error for OMVS.ROOT . . . . . . . . . . . . . . . . . . . . . . . . 154| 105. CPPP60E3 - Specify SMS classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155| 106. CPPP605U - Data Set List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Figures vii

| 107. CPPP605D - Data set attributes 1 of 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156| 108. CPPP605U - Data Set List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156| 109. CPPP60E5 - Modify system layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157| 110. CPPP60E6 - Merge error for OMVS.ROOT . . . . . . . . . . . . . . . . . . . . . . . . 157| 111. CPPP60E7 - Specify SMS classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

112. CPPP605X - Expansion of a Merged Data Set . . . . . . . . . . . . . . . . . . . . . . 161113. CPPP605W - Expansion of Merge Component Data Set for UNIX Filesystem

Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162114. CPPP605D - Data Set Attributes 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162115. CPPP605E - Data Set Attributes 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166116. CPPP605E - Data Set Attributes 2 for a shipped VSAM Data Set . . . . . . . . . . 166117. CPPP605F - Data Set Attributes 2 for a shipped VSAM Data Set . . . . . . . . . . 167

| 118. CPPP60E2 - Verify data set type change . . . . . . . . . . . . . . . . . . . . . . . . . . 167| 119. CPPP60E7 - Specify SMS Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

120. CPPP606# - Device Type Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168121. CPPP606I - Device Type Insertion/Edit . . . . . . . . . . . . . . . . . . . . . . . . . . 169122. CPPP606D - Device Type Deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170123. CPPP605U - Data Set List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171124. CPPP605I - Define a USER data set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172125. CPPP6053 - List of data set categories . . . . . . . . . . . . . . . . . . . . . . . . . . . 173126. CPPP6059 - List of zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174127. CPPP605U - Data Set List to display user-defined data sets . . . . . . . . . . . . . 175128. CPPP605D - Data Set Attributes 1 (User PDS/PDSE with Allocate Data set = Y) 176129. CPPP605D - Data Set Attributes 1 (User PDS/PDSE with Allocate Data set = N) 176130. CPPP605D - Data Set Attributes 1 (User HFS/zFS with Allocate Data set = Y) 177131. CPPP605D - Data Set Attributes 1 (User HFS/zFS with Allocate Data set = N) 177132. CPPP605D - Data Set Attributes 1 (SEQ user data set with Allocate Data set =

Y) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178133. CPPP605D - Data Set Attributes 1 (SEQ user data set with Allocate Data set =

N) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178134. CPPP605$ - Data Set Details to confirm the delete . . . . . . . . . . . . . . . . . . . 179135. CPPP6052 - Summary of Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180136. CPPP605K - SUMMARY Of Physical Volumes . . . . . . . . . . . . . . . . . . . . . 181137. CPPP605J - ASSIGN a Physical Volume . . . . . . . . . . . . . . . . . . . . . . . . . 184138. CPPP605Q - Assign a Storage Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185139. CPPP6058 - CONFIRM Processing Requirements . . . . . . . . . . . . . . . . . . . 186140. CPPP6021 - Define CATALOG data set Names . . . . . . . . . . . . . . . . . . . . . 187141. CPPP6024 - Confirm Delete Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189142. CPPP6023 - Specify Alias and Catalog Names. . . . . . . . . . . . . . . . . . . . . . 190143. CPPP6022 - Confirm Processing Requirements . . . . . . . . . . . . . . . . . . . . . 191144. CPPP6031 - CATALOG Selection List . . . . . . . . . . . . . . . . . . . . . . . . . . . 192145. CPPP6033 - Define SSA and CATALOG Data . . . . . . . . . . . . . . . . . . . . . . 194146. CPPP6035 - Define SSA and catalog data (software upgrade) master . . . . . . . 195147. CPPP6036 - Define SSA and catalog data (software upgrade) . . . . . . . . . . . . 196148. CPPP6032 - Confirm Processing Requirements . . . . . . . . . . . . . . . . . . . . . 197149. CPPP6121 - JOB Selection List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198150. CPPP6126 - Generate Installation Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . 203151. CPPP6125 - Processing LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204152. CPPP6124 - DELETE a USER Defined JOB - Confirmation . . . . . . . . . . . . . 205153. CPPP6122 - INSERT a USER Defined JOB . . . . . . . . . . . . . . . . . . . . . . . 206154. CPPP612I - BROWSE Existing USER JOB . . . . . . . . . . . . . . . . . . . . . . . . 207155. CPPP6123 - INSERT a USER Defined JOB - Confirmation . . . . . . . . . . . . . 207156. CPPP612B - EDIT BACKUP MEMBER . . . . . . . . . . . . . . . . . . . . . . . . . 208157. CPPP612E - EDIT SOURCE MEMBER . . . . . . . . . . . . . . . . . . . . . . . . . . 209158. CPPP612S - EDIT JOBSTREAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

viii CustomPac Installation Dialog Reference Manual

159. CPPP6041 - Save Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212160. CPPP6042 - DELETE an EXISTING Configuration - Confirmation . . . . . . . . 213161. CPPP607B - Order Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214162. CPPP6071 - Display Orders - Order List . . . . . . . . . . . . . . . . . . . . . . . . . 215163. CPPP6072 - Display Orders - Order List . . . . . . . . . . . . . . . . . . . . . . . . . 216164. CPPP6073 - Display Orders - DELETE an Order . . . . . . . . . . . . . . . . . . . . 217165. CPPP6074 - Display Orders - EDIT an Order . . . . . . . . . . . . . . . . . . . . . . . 218166. CPPP6076 - Display Orders - Display Products for an Order . . . . . . . . . . . . . 220167. CPPP6079 - Shipped FMIDs for a product/feature . . . . . . . . . . . . . . . . . . . 221168. CPPP607D - Shipped FMIDs for a product/feature . . . . . . . . . . . . . . . . . . . 221169. CPPP6077 - Display Orders - ENTER Report File Details . . . . . . . . . . . . . . 222170. CPPP607C - Display Orders - Status Verification . . . . . . . . . . . . . . . . . . . . 223

Figures ix

x CustomPac Installation Dialog Reference Manual

General Information

Chapter 1. General Information

The CustomPac installation dialog is an Interactive System Productivity Facility (ISPF)dialog that you use to install the order.

This chapter presents some important concepts that you should understand before using thedialog to install your order.

Preparing to install your CustomPac orderThe information that IBM provides to help you prepare for installation depends on what typeof package you are insatlling.

For SystemPac orders... Follow the instructions in z/OS Planning for Installation onpreparing your system for a ServerPac installation. For example, you must havea driving system that meets certain requirements to perform the installation.z/OS Planning for Installation lists the hardware and software requirements forthe driving system and also helps you determine how much DASD to use. Also,check the appropriate software preventive service planning (PSP) buckets fordriving system requirements.

For other orders... For the driving system requirements, see z/OS Planning for Installation.For instructions on preparing your system for a ServerPac installation, see thedocumentation that is provided with your order. Also, check the appropriatesoftware preventive service planning (PSP) buckets for coexistence and fallbackservice requirements.

See z/OS Planning for Installation for the PTFs that you might need to install on yourexisting system to allow it to coexist with the new release, and allow you to fall back to theexisting system if necessary.

Regardless of what type of order, use the installation dialog described in this book to installthe order.

Orders from tapeIf you received your order on tape, be sure to review the contents of the CustomPacshipment that you received from IBM before you install your order. Check the packing slipto ensure that you have a complete set of installation tapes and documentation. Also, takenote of your order number, which is printed on the cover of CustomPac: Installation Guide.You will later use this order number as input to the installation dialog.

You may need to install or update the installation dialog and its associated data sets on yourdriving system. Instructions for installing and updating the dialog are provided in Chapter 3,“Installing and Starting the Dialog” on page 15

Chapter 1. General Information 1

General Information

Orders from a serverIf you received your order from a server, be sure to review the contents of the CustomPacshipment that you received from IBM before you install your order. Also, take note of theorder number, server name, server directory, user ID, password, and hash value. This data islocated in the Dialog Data file on the Shopz Download page for your order. You will usethis information later as input to the installation dialog.

Additional information about Internet delivery of orders can be found in z/OS Planning forInstallation.

You might need to install or update the installation dialog and its associated data sets onyour driving system. Instructions for installing and updating the dialog are provided inChapter 3, “Installing and Starting the Dialog” on page 15

Orders from DVDIf you received your order on DVD, be sure to review the contents of the CustomPacshipment that you received from IBM before you install your order. Also, take note of yourorder number, which can be obtained from the file DIALOG.txt "CustomPac DialogInformation" on the first DVD. You will later use this order number as input to theinstallation dialog. See the README.pdf file on the first DVD for instructions of copyingthe order from workstation to your host system.

The following files and directories exist in the main order directory and are included on thefirst DVD:

• COPYRIGHT.txt file, IBM products copyright statements

• DIALOG.txt file, CustomPac Dialog Information

• IYO.pdf file, Order Installation Guide

• LOADRIM.jcl file, LOADRIM job to upload and restore CustomPac Dialog

• README.pdf file, Installation instructions

• UPDATE.jcl file, UPDATE job to update the CustomPac Dialog

• /<ordernum> main order directory

− /<ordernum>.order: subdirectory with archived Order RIM files

− /<ordernum>.content - subdirectory with archived Order content files

Note: <ordernum> is manufacturing order number

Copy all files from DVD root, order and content subdirectory to temporary work directoryusing the same directory structure as how files are stored on DVD.

The other DVDs have the following file structure:

• /<ordernum>.content: subdirectory with additional archived Order content files

Copy files from DVDs /<ordernum>.content subdirectory to temporary work directory/<ordernum>.content

You may need to install or update the installation dialog and its associated data sets on yourdriving system. Instructions for installing and updating the dialog are provided in Chapter 3,“Installing and Starting the Dialog” on page 15.

2 CustomPac Installation Dialog Reference Manual

General Information

Driving System RequirementsThe software requirements for running the dialog are as follows -

• Any IBM supported operating system. If V1R8, DFSMSdfp PTF UA34953 (for APAROA20599) is also required.

Please also refer to the CustomPac Installation Guide for further information onprerequisites needed to install the packages.

SMS ConsiderationsThe Storage Management Subsystem (SMS) must be active to allocate HFS and PDSE datasets, whether they are SMS-managed or non-SMS-managed. Also, the use of HFS data setsis supported only when SMS is active in at least a null configuration, even when the datasets are not SMS-managed. Do either of the following:

• To allocate non-SMS-managed HFS and PDSE data sets, you must activate SMS on thedriving system in at least a null configuration. You must also activate SMS on the targetsystem.

• To allocate SMS-managed HFS and PDSE data sets, you must activate SMS on thedriving system in at least a minimal configuration. Then you must define a storagegroup, create SMS-managed volumes, and write, translate, and activate a storage classACS routine that allows the allocation of PDSE and HFS data sets with the names in theALLOCDS job. You must also activate SMS on the target system.

Security ConsiderationsTo install the products delivered in ServerPac, you might need to create new definitions foryour security system.

Later, during the installation jobs phase of the installation process, you can submit jobsRACFDRV and (for z/OS orders only) RACFTGT. These jobs issue RACF„ commandsthat require your user ID to have the RACF SPECIAL attribute.

These jobs also require that your user ID have ALTER access for the data set high levelqualifiers (HLQs) in the order. You will need ALTER access for the following HLQs:

• CPAC

• SYS1 (for z/OS orders)

• Product-specific high-level qualifiers for the products in your order. For a listing ofthese qualifiers, use the A (ALIAS) option of the dialog after you finish modifying thesystem layout. For example, ServerPac uses the high-level qualifier "ISP" for the ISPFproduct data sets. If you change the ISP high-level qualifier to "XYZ" for those datasets, your userid must have ALTER authority for the "XYZ" high-level qualifier.

• System-specific aliases named in the SSA panel.

You will also need UPDATE access for the SSA qualifiers in the driving system's mastercatalog. For example, if you use an SSA of "ABC" for the ISPF data sets, and you use thedefault high-level qualifier, you will need ALTER access to "ABC" and UPDATE access to"ISP."

Review jobs RACFDRV and (for z/OS orders only) RACFTGT carefully before you submitthem. Modify these jobs as necessary to suit your particular installation.


General Information

Also, if you decide to use SMS to manage data sets in your order (as described in “Changingthe SMS Management Status” on page 143), the userid that you later use to submit theinstallation jobs requires at least READ access to the FACILITY class profile forSTGADMIN.IGG.DIRCAT, which allows you to direct a catalog request to a specificcatalog.

If you use a security product other than RACF you should perform the equivalent actions forthat product.

Language Environment ConsiderationsThe CustomPac Installation Dialog uses the Language Environment run-time library,SCEERUN. If SCEERUN is not in the link list on the driving system, you must edit theCustomPac installation jobs to add it to the JOBLIB or STEPLIB DD statements.

Do not specify the following Language Environment run-time options as nonoverrideable(NONOVR) in the CEEDOPT CSECT because CustomPac Dialog programs need tooverride these:

• ALL31• ANYHEAP• BELOWHEAP• DEPTHCONDLIMIT• ERRCOUNT• HEAP• HEAPCHK• HEAPPOOLS• INTERRUPT• LIBSTACK• PLITASKCOUNT• STACK• STORAGE• THREADHEAP• THREADSTACK

CustomPac Offerings

The increasing complexity of software has led to a strong demand for customised softwareservices.

CustomPac offers solutions to this problem, which will assist the customer in themanagement of his software environment in a less complex and time consuming way.

All CustomPacs are available in Copy format (which is also known by the term Dump bydata set).

In this format the deliverables are installed by a driving system on to a target system usingan Installation Dialog (shipped with the order).

Some CustomPacs are also available in Full Dump format.

In this format the deliverables do not need a driving system as they are "DASD images" of arunning system, which are restored by a special restore utility.


General Information

All deliverables are individually tailored, using customer supplied data, and delivered onthe IBM recommended service level, which is known to be error free at the time ofproduction.

ServerPacDelivers a complete operating system.

The ServerPac build process creates both TARGET and DISTRIBUTION libraries.

• Delivered with all products and service already installed.• Service is to the IBM recommended service level.• Each MVS ServerPac is individually IPL and IVP quality tested during production.• Available in COPY format, allows a high degree of system tailoring during installation.

SystemPacDelivers a complete operating system.

The SystemPac build process creates both TARGET and DISTRIBUTION libraries.

• Delivered with all products and service already installed.• Service is to the IBM recommended service level.• Each MVS SystemPac is individually IPL and IVP quality tested during production.• Available in FULL DUMP format, recommended for customers NEW to MVS.• Available in COPY format, allows a high degree of system tailoring during installation.

FunctionPacDelivers multiple product groups (grouped by associated products or by organisation), theproducts being defined by the customer.

The FunctionPac build process creates both TARGET and DISTRIBUTION libraries.

• Delivered with all products and service already installed.• Service is to the IBM recommended service level.• Service dependency report produced, to assist in Cross Zone checking during

installation.• Available in COPY format, allows a high degree of product tailoring during installation.

ProductPacDelivers NEW versions or releases of software to be installed in an EXISTING MVS systemor product group.

Customer supplies a copy of the SMPCSI, which is used as the basis of ProductPacproduction.

• A FULL Upgrade option is available, in addition to the service for the NEW products,service for ALL products in the related SMP-Zone will be included.

• All products and service are quality tested for installability.• Informational and action reports produced include -

− System Holds, plus resolved System Holds.− SMP/E regression, condensed version of the SMP APPLY run identifying problems

that could not be resolved at the production centre.− Installed service, Open PE's which couldn't be solved, Solved PE's, Hiper PTF's

and AHEAD service not included but shipped on the service tape.


General Information

ProductPac/EProductPac/E was withdrawn September 1997.

RefreshPacDelivers a service upgrade for all FMIDs in a related SMP-Zone.

Customer supplies a copy of the SMPCSI, which is used as the basis of RefreshPacproduction.

RefreshPac is NOT recommended if the current service level of the software is olderthan 2 years.

• All service is quality tested for installability.• Informational and action reports produced include -

− System Holds, plus resolved System Holds.− SMP/E regression, condensed version of the SMP APPLY run identifying problems

that could not be resolved at the production centre.− Installed service, open PE's which could not be solved, solved PE's, Hiper PTF's


Selected Follow on Service (SFS)Delivers a service upgrade for all FMIDs in a related SMP-Zone, for a previously shippedorder.

During the production of CustomPac a profile is produced which lists the FMIDs andservice from both the SMPCSI, used to build the Pac, and any sysmods shipped as part ofthe Pac. This profile is used as the basis for SFS production.


− System Holds, plus resolved System Holds.− Installed service, open PE's which could not be solved, solved PE's, Hiper PTF's


Refresh On Profile (ROP)Delivers a service upgrade for all FMIDs in a related SMP-Zone, for a previously shippedorder.

During the production of CustomPac a profile is produced which lists the FMIDs andservice from both the SMPCSI, used to build the Pac, and any sysmods shipped as part ofthe Pac. This profile is used as the basis for ROP production.


− System Holds, plus resolved System Holds.− Installed service, open PE's which could not be solved, solved PE's, Hiper PTF's



Understanding the Dialog

Chapter 2. Understanding The Dialog

Shipped with your order is a dialog that will assist you in installing your order.

This chapter describes the user interface features of the dialog, you need to be familiar withit before using it.

Language Support

The installation dialog is provided in U.S. English and Japanese. If the primary languagespecified in your TSO/E profile is neither of these languages, you must use the TSO/EPROFILE command to set the value of PLANGUAGE to either ENU for U.S. English, orJPN for Japanese.

To select U.S. English, enter the following command:PROFILE PLANGUAGE(ENU)

To select Japanese, enter the following command:PROFILE PLANGUAGE(JPN)

ISPF Edit CAPS Setting

The dialog uses the ISPF editor when you select a job through the S or B line commands.ISPF Edit is called with an initial macro that sets CAPS to OFF. This setting preserves yourtext input in the form in which you enter it (uppercase, lowercase, or mixed case).

If you enter mixed case input in a job, the dialog does not convert your input to uppercasecharacters. You must ensure that lines that should contain only uppercase characters (likemany JCL statements) do not contain lowercase characters. This is easily done with the ISPFEdit UC (Upper Case) line command.

For more information about ISPF Edit, initial macros, CAPS settings, and ISPF Edit linecommands, see z/OS ISPF Edit and Edit Macros.

Use of ColourThe dialog makes use of colour to identify key information on a panel, so the use of a colourterminal is considered essential (although the dialog will run without error on a monochrometerminal).

For the purpose of this document it is assumed that a SEVEN colour terminal is available.

Chapter 2. Understanding The Dialog 7


Sample DisplaysThroughout this chapter, use the sample displays in Figure 1, and Figure 2 to help youunderstand the main sections of the dialog panels.

� � CustomPac ----------- SAMPLE Table Display MODE(TE) ------- ROW 1 TO 16 OF 99 COMMAND ==> SCROLL ==> PAGE

PRIM Cmds:(? SET L F N P SORT VErbose) x1w LINE Cmds:(Browse Delete Insert Edit Select) x2w

S Order ID Pack SREL CUSTomer STatus - -------- ---- ---- -------------------------------------- x3w - --------

MD010001 EXP Z038 ASSENBACK CHEMICALS SHIPPED MD010022 CRS C150 BRECKS SHIPPED MD010023 EXP Z038 LONDON BUILDING SHIPPED MD010032 EXP Z038 BURGHERMAN CONTAINERS AND SHIPPING SHIPPED MD010037 EXP Z038 BRECKS SHIPPED MD010048 EXP Z038 BRECKS SHIPPED MD010057 EXP Z038 3C SALT SHIPPED MD010059 EXP Z038 ASSENBACK CHEMICALS SHIPPED MD010068 EXP Z038 ASSENBACK CHEMICALS SHIPPED MD010069 FPAC C150 3C SALT ACTIVE MD010070 CPP Z038 EBBER AND HALT SHIPPED MD010083 CPP Z038 GLANDALE LTD FINISHED MD010088 CPP Z038 ZYMKIOTHOS FG FINISHED MD010101 CPP Z038 HELLER DRUTH PARTNERSHIP SHIPPED MD010109 EXP P004 BRECKS LOADED MD010111 EXP Z038 ASSENBACK CHEMICALS SHIPPED

� �

Figure 1. Sample TABLE Display (TErse MODE)

� � CustomPac ----------- SAMPLE Table Display MODE(VE) -------- ROW 1 TO 3 OF 99 COMMAND ==> SCROLL ==> PAGE

PRIM Cmds:(? SET L F N P SORT TErse) x1w LINE Cmds:(Browse Delete Insert Edit Select) x2w

S Order ID Pack SREL CUSTomer STatusCTRY CONTACT

- -------- ---- ---- -------------------------------------- x3w - -------- MD010001 EXP Z038 ASSENBACK CHEMICALS SHIPPED C724 A. SCHMIDT Updated ON 1993/07/01 By STOBBS - -------- ---- ---- -------------------------------------------- --------

MD010022 CRS C150 BRECKS SHIPPED C616 H. QUARTERMAN Updated ON 1993/06/21 By STOBBS - -------- ---- ---- -------------------------------------------- --------

MD010023 EXP Z038 LONDON BUILDING SHIPPED C848 D.A EYRE Updated ON 1993/06/21 By STOBBS - -------- ---- ---- -------------------------------------------- --------

� �

Figure 2. Sample TABLE Display (VErbose MODE)



Table Display MODESThroughout much of the dialog, information that is displayed in a tabular format can bedisplayed in either of two styles (or modes), as follows -

• TErse mode, only one line of information is shown for each table item, as shown inFigure 1 on page 8. Most table displays use this mode.

• VErbose mode, multiple lines of information are displayed for each table item, asshown in Figure 2 on page 8.

If a table can be displayed in either mode, the panel displays the commands that allow youto switch between modes.

Table Display Panel AreasThe table display panel has three significant areas -

• x1w → The Primary Commands• x2w → The Line Commands• x3w → The FIELDS (Field Names, Synonyms, Separators and Columns)

Each of these areas is described in the sections that follow.

The Primary CommandsPrimary Commands are shown on the table display in area x1w

There are several CustomPac defined Primary Commands that you can use for tabledisplays; however, not all commands are available for every table. Primary Commands thatare valid for a particular table are shown after the Primary Commands: in the display.

? This command invokes any Dynamic HELP for the current display.

(See “Dynamic HELP” on page 14)

SET Synonym

This command specifies the field to be acted upon by the LOCATE, FIND,NEXT and PREVIOUS commands.

Where, for the examples shown SYNONYM may be -

*SORT The search field will track the SORT field(This is an "internal" synonym assigned to the current SORTfield)

OID Search the Order Number field

P Search the Package Type field

SR Search the SREL (System Release) field

CUST Search the Customer Name field

ST Search the Order Status field

L data [comparison]

This is the LOCATE command

Starting from the top of the table, search the SET field ahead for a "data"match that satisfies the comparison code.



only the first x characters of the fields will be searched for "data", where x isthe LENGTH in characters of "data".

i.e. "data" cannot be imbedded.

This command IS case sensitive.

"comparison" is optional (It defaults to EQ), If supplied it must be: EQ, NE,LE, LT, GE, GT.

Example

SET PL FPAC

SET SRL Z038 NE

If the data argument contains BLANKS, then it must be enclosed inQUOTATION marks.

SET CUSTL '3C Salt'

If a match is found the table row containing "data" will be positioned at thetop of the scrollable area.

This command replaces any active FIND command.

F data [EQ]

This is the FIND command

Starting from the top of the table, search the SET field ahead for a "data"match.

"data" may begin in ANY character position of the field i.e. it may beimbedded in the field.

This command IS NOT case sensitive, both "data" and the field contents willbe compared as if they were entered in upper case alpha.

All FIND comparisons are based on an EQ comparison code.

Example

SET CUSTF CHEMICAL

If the data argument contains BLANKS, then it must be enclosed inQUOTATION marks.

SET CUSTF 'AND SHIP'

If a match is found the table row containing "data" will be positioned at thetop of the scrollable area.

This command replaces any active LOCATE command.

N This is the NEXT command

This command repeats the last FIND or LOCATE command, searchingforward.



P This is the PREVIOUS command

This command repeats the last FIND or LOCATE command, searchingbackward. Starting from the first table row of the current panel display,search the SET field backwards for a "data" match that satisfies thecomparison code.

SORT Synonym

The table display will be presented in the specified sequence.

Where, for the examples shown SYNONYM may be -

OID Sort the Order Number field

P Sort the Package Type field

SR Sort the SREL (System Release) field

CUST Sort the Customer Name field

ST Sort the Order Status field

By appending a blank plus an A or D to the field name you may force the sortto be in Ascending or Descending sequence, otherwise the sequence will bethat pre-programmed for the field.

It is usual for date fields to be pre-programmed so that the latest date isshown first (i.e. Descending Sequence)

TErse This command may be abbreviated to TE

The table is displayed showing one display line of information for each tableitem.

This display mode will remain active until a VErbose command is issued.

(This command is only valid if the table display has both a TErse andVErbose mode).

VErbose This command may be abbreviated to VE

The table is displayed showing multiple display lines of information for eachtable item.

This display mode will remain active until a TErse command is issued.

(This command is only valid if the table display has both a TErse andVErbose mode).

The Line CommandsLine Commands are shown on the table display in area x2w

Line Commands are entered in the Selection FIELD, and are specific to the table beingdisplayed.

If the list of available Line Commands is enclosed within ( .. ), then multiple ROWS maybe selected.

If the list of available Line Commands is enclosed within < .. >, then only a SINGLEROW may be selected.

Most table display panels allow you to use the following commands -

B BROWSE



D DELETEE EDITI INSERTS SELECT

The effect of each command is generally consistent throughout the dialog. For example, "B"usually means "Browse". However the meaning of a command can vary for some displays,on some panels "B" can mean "Back-up". Throughout this book, all Line Commandsavailable for a panel are described fully in the section that describes the use of the panel.

OFILE CommandThis command, abbreviated as OF, writes this data set list to a user-defined file.

To dynamically allocate the user file and open it, enter the OFILE command as follows:

OF OPEN data set { OLD | SHR | NEW | MOD }

where:

• data set is a fully-qualified data set name (enclosed in single quotation marks). If youdo not enclose the data set name in quotes, your TSO/E PROFILE PREFIX is used asthe high level qualifier.

• OLD, for an existing data set is used. This is the default.• SHR, for an existing data set is used.• NEW, to allocate and catalog a new data set• MOD, to use the data set if it exists, or allocate and catalog a new data set, if needed.

The OFILE command requires an output data set to which a 120-byte fixed length recordcan be written. The output record has the following logical structure:

To send the list of data sets to the file, enter the OFILE command without any keyword dataset entry is written to a separate output record.

ColumnsFieldSize Description

1-44 44 Data set name

45 01 Data set merged flag

46 01 Data set changed flag

47-50 04 Record format (RECFM)

51-54 04 Data set organization (DSORG)

55-59 05 Logical record length (LRECL)

60-64 05 Reserved for IBM use

65-70 06 Logical volume

71-78 08 Physical volume or SMS storage class

79-82 04 Device number

83-90 08 Generic or esoteric unit name

91-98 08 Device type

99-102 04 Space required (in cylinders)

103-120 18 Reserved for IBM use



To close the file and free the dynamic allocation, enter the OFILE CLOSE command(abbreviated as OF C).

The FIELDS (Field NAME, Synonyms, Separators and Columns)Fields are shown on the table display in area x3w

Generally, each field on the table display is assigned a Field NAME. For the examplesshown the Field NAMEs (and their contents) are -

OrderID CustomPac Internal Order NumberPack Package TypeSREL System Release (Z038, C150, P004, P115 or MULT)CUSTomer Customer NameSTatus Order Status

Field NAMEs are shown above the Field COLUMNs (containing the data), displayed inWHITE.

A Field NAME may have a SYNONYM, which is used with some of the PrimaryCommands to take an action on a field.

SYNONYMs are identified by the CAPITAL LETTERS within the Field NAME, displayedin PINK.

NOTE

Some Field NAMES may have CAPITAL LETTERS, but NOT have any lettersdisplayed in PINK, in which case NO Synonym is present.

For the examples shown the Field NAMEs have the following Synonyms -

OrderID → OIDPack → PSREL → SR

NOTE

SREL is shown as the Field NAME in CAPITALS, but only the FIRST 2characters are displayed in PINK -

So the SYNONYM is SR

CUSTomer → CUSTSTatus → ST

Field SEPARATORs, are shown underneath the Field NAME and are made up of "-"characters, displayed in BLUE.

The Field SEPARATOR for the current SORT field is displayed in YELLOW.

(See “The Primary Commands” on page 9).

The Field SEPARATOR for the current SET field is displayed in TURQUOISE (only thefirst 2 characters)



(See “The Primary Commands” on page 9).

Field COLUMNs contain the table data to display, which are categorised as follows -

Selection FIELD

If present, this is the leftmost field on the display.

NOTE

This is omitted if the table display does not require a selection field, as in"output only" displays.

Primary FIELD

This field is almost always the leftmost field on the display (after theSelection Field).

If it is an OUTPUT field it displays in YELLOW, if it is an INPUT field itdisplays in RED.

Auxilliary FIELD(s)

Any auxilliary fields follow the PRIMARY field, there may be any numberof auxilliary fields (including None).

If it is an OUTPUT field it displays in TURQUOISE or GREEN, if it is anINPUT field it displays in RED.

Dynamic HELPMany CustomPac panel displays (for both tables and data entry) have a "Dynamic HELP"facility.

This facility is more flexible than the standard ISPF help panels, and allows much more helpto be displayed. When you invoke help, you be can "scroll" through information. You canset a PF key to 'HELP' or '?'. Or, you can simply enter HELP or ? at any time to invoke thehelp facility.


Installing and Starting the Dialog

Chapter 3. Installing and Starting the Dialog

If you are installing a CustomPac for the first time, you must install the installation dialog onyour system, see “Installing the dialogs” on page 19. For subsequent orders, you miay needto update the dialog prior to receiving your order, see “Updating your dialogs” on page 17.Restriction: If your Dialog is not at level 27.20.00 or higher, you will need to update thedialog before receiving your order. To determine whether you must update the dialog, startthe dialog and look at the first panel {CPPPPOLI}. If it does not contain a level number of27.20.00 or higher in the upper right corner, you need to update your dialogs. See “Updatingyour dialogs” on page 17.

Summary of tasksInstalling and starting the installation dialog involves the following activities:

1. Plan for where the dialog data sets are to be loaded and cataloged. See “Allocating andCataloging the Dialog Data Sets” on page 16.

2. If you are installing the dialogs for the first time:

a. For tape or DVD orders:

1) Copy or download the LOADRIM job to your driving system's DASD. See“Installing the dialogs” on page 19

2) Run the LOADRIM job to load the dialog data sets onto the driving system'sDASD.

Notes:

a) For tape orders only: After installing a new copy of the dialog, you mustuse the first "system and distribution tape" to run the first RECEIVE job.The first "system and distribution tape" is from the same order used to runthe LOADRIM job that installed the dialog. After the first RECEIVE jobis run, RECEIVE jobs can be run in any order.

b) For DVD orders only: See the README.PDF file for more informationabout downloading the LOADRIM job from DVD.

b. For orders from a server:

1) Copy or download the LOADRIMS or LOADRIMH job to your drivingsystem's DASD. See Installing the dialogs on page 15.

2) Run the LOADRIMS or LOADRIMH job to download and create the dialogdata sets on your driving system's DASD.

3. If you are updating your dialogs:

a. For tape orders:

1) Create a job to copy the UPDATE job from 'SYS1.orderid.DOCLIB'. See“Updating your dialogs” on page 17.

2) Run the UPDATE job to update the dialog data sets on your driving system'sDASD.

b. For DVD orders:

1) Copy the UPDATE job to your driving system's DASD. See “Updating yourdialogs” on page 17.

Chapter 3. Installing and Starting the Dialog 15


2) Run the UPDATE job to update the dialog data sets on your driving system'sDASD.

c. For orders from a server:

1) Download the EUPDATES or EUPDATEH job to your driving system'sDASD. See “Updating your dialogs” on page 17.

2) Run the EUPDATES or EUPDATEH job to download and update the dialogdata sets on your driving system's DASD.

4. Select a method of invoking the dialog. See “Starting the Dialog” on page 22.

Allocating and Cataloging the Dialog Data SetsYou use the dialog to create the jobs for installing your order. For a z/OS order, you runmany of these jobs on your driving system, and the rest on your new target system. For asubsystem order, all jobs are run on the driving system.

After IPLing the target system, you can use the dialog on that system to determine which jobto submit next, and to display the results of each job.

You will find it much easier to access the dialog from the target system if the data sets youcreate for the dialog (the master dialog data sets) are cataloged in a user catalog and resideon a volume that is accessible to both the driving system and the target system. Use a uniquehigh-level qualifier for the data sets, so that alias entries in the driving system and targetsystem master catalogs can refer to the user catalog.

Catalog the following data sets in a user catalog: We suggest that 'Qualifier' be MASTER todistinguish the master dialogs from the order dialogs:

• CustomPac.Qualifier.SCPPLOAD - Load Modules

• CustomPac.Qualifier.SCPPCENU - Clist/Rexx execs

• CustomPac.Qualifier.SCPPEENU - CustomPac messages - VSAM

• CustomPac.Qualifier.SCPPHENU - CustomPac dialog help - VSAM

• CustomPac.Qualifier.SCPPMENU - messages

• CustomPac.Qualifier.SCPPPENU - panels

• CustomPac.Qualifier.SCPPSENU - skeletons

• CustomPac.Qualifier.SCPPTENU - tables

• CustomPac.Qualifier.SCPPVENU - order inventory - VSAM

If the dialog s data sets are to be SMS-managed, assign them to a management class(MGMTCLAS) that does not allow the dialog data sets to be migrated unless the SMS andDFSMShsm environments will be shared between the driving system and target system.

When allocating the dialog data sets, do not convert them to PDSE format. In addition tothe SCPPnENU data sets, the following dialog data sets must remain in their originalformats (PDS or PS):



Figure 3. Dialog Data Sets Must Remain in Their Original Formats

Dialog Data Set Required Format

userid.CPPTEMPx.SCPPWORK PS (physical sequential)

hlq.orderid.LOG PS (physical sequential)

hlq.orderid.REPORT(MERGE) PDS (partitioned data set)

The final steps for porting the dialog to the target system are described in CustomPacInstallation Guide, in the chapter that describes how to IPL the target system.

Updating your dialogsThe CustomPac Installation Dialog must be at a level of 27.20.00 or higher. To determinewhether your dialog is at the correct level, look for the dialog level number in the upperright-hand corner of panel CPPPPOLI, the first panel displayed when the dialog starts.

For tape orders, see “Copying the UPDATE job from tape.”

For DVD orders, see “Copying the UPDATE job from DVD” on page 18.

For orders from a Server, see “Downloading the EUPDATES or EUPDATEH job from aserver” on page 19.

Copying the UPDATE job from tapeTo update the dialogs on your driving system, you must first copy the UPDATE job to yourdriving system.

1. Create a job to copy the UPDATE job from 'SYS1.orderid.DOCLIB', where orderid isthe IBM-supplied number for your order. The 'SYS1.orderid.DOCLIB' data set is thesixth file on the tape. Figure 4 shows a job that you can use:

distribution tape"

� �//EXTRACT JOB <JOB statement info goes here...>//*//STEP01 EXEC PGM=IEBCOPY//*//SYSPRINT DD SYSOUT=*//*//IDOC DD DISP=SHR,DSN=SYS1.OrderID.DOCLIB,LABEL=(06,SL),// VOL=SER=tapeser,UNIT=tapeunit//ODOC DD DSN=Work.Library.JCL,// DISP=(NEW,CATLG,DELETE),// VOL=SER=volser,UNIT=SYSDA,// SPACE=(9600,(240,30,20))//*//SYSIN DD *

COPY INDD=IDOC,OUTDD=ODOCS M=UPDATE

/*

� �

Figure 4. Panel: Copying the UPDATE job from the "system and



2. Modify the following values for your order:

OrderID Order number, which can be found on the cover of your packageInstallation Guide

Tapeser Volume serial for the first "system and distribution tape" shipped withyour order, which can be found on the external label and in Chapter 2 ofyour package Installation Guide.

Tapeunit Generic or esoteric name of the tape device that you will use to read the"system and distribution tape". For example, if you ordered yourCustomPac on a 3590 tape cartridge, this is the device you use to readthe 3590 tape.

Volser Volume serial number of the DASD volume on which the DOCLIB dataset is to be created. If UNIT specifies an esoteric name for a DASD poolto be used for permanent data sets, you can remove the VOL=SER=parameters of the DD statement instead of supplying this value.

SYSALLDA If your installation does not permit the use of SYSALLDA, change thisvalue to an appropriate esoteric or generic name.

ODOC Data set name for the UPDATE job.

3. Run the EXTRACT job.

4. Before using the UPDATE job to allocate and load the master dialog data sets, you mustcustomize the job. Make the following modifications:

CustomPac.QualifierHigh-level qualifier to be used for the master dialog data sets.

volser The volume serial number of the DASD volume to be used to allocatethe master dialog data sets.

Tapeser Volume serial for the first "system and distribution tape" shipped withyour order, which can be found on the external label and in Chapter 2 ofyour package Installation Guide.

Tapeunit Generic or esoteric name of the tape device that you will use to read the"system and distribution tape". For example, if you ordered yourCustomPac on a 3590 tape cartridge, this is the device you use to readthe 3590 tape.

5. Run the UPDATE job.

Copying the UPDATE job from DVDFor orders delivered on a DVD, IBM provides the UPDATE job as a file on the DVD.

1. Copy the UPDATE job to a workstation from the first DVD. Then, copy the UPDATEjob to your driving system.

2. Before using the UPDATE job to update your master dialog data sets, you must allocateand mount a UNIX file system to contain the destination directory and its files andcustomize the job. Replace the JOB statement with a JOB statement that is valid foryour installation and supply values for the following options:

SET PATH Specify the path for the directory in which the CustomPac dialog andorder information will be stored.



CustomPac QualifierThe high-level qualifier of your master dialog data sets.

Volser The volume serial number of the DASD volume to be used to allocatethe master dialog data sets.

3. Run the UPDATE job.

Downloading the EUPDATES or EUPDATEH job from a serverTo update the dialogs on your driving system, you must first copy the EUPDATES orEUPDATEH job from a server:

1. Click the link for the EUPDATES or EUPDATEH job on the Shopz download page andcopy the file to your workstation. Then copy the EUPDATES or EUPDATEH job toyour driving system.

2. Before using the EUPDATES or EUPDATEH job to update your master dialog datasets, you must allocate and mount a UNIX file system to contain the destinationdirectory and its files, and then customize the job. Replace the JOB statement with aJOB statement that is valid for your installation and supply values for the following:

PATH Specify the path for the directory in which the CustomPac dialog andorder information will be stored.

CustomPac.QualifierThe high-level qualifier of your master dialog data sets.


3. Run the EUPDATES or EUPDATEH job.

Installing the dialogsTo install the dialogs on your driving system for the first time, you must first copy theLOADRIM job to your driving system. Then, use LOADRIM to load the rest of the dialogdata sets onto your driving system's DASD.

Copying the LOADRIM job from tapeFor orders delivered on tape, IBM provides the LOADRIM job as member LOADRIM indata set SYS1.orderid.DOCLIB, where orderid is the IBM-supplied number for your order.The SYS1.orderid.DOCLIB data set is the sixth file on the tape, which has a standard label(SL).

Copy LOADRIM from SYS1.orderid.DOCLIB, as follows:

1. Create a job to copy the LOADRIM job to your driving system. Figure 5 on page 20shows a job you can use:



distribution tape"

� �//EXTRACT JOB ..........//*//STEP01 EXEC PGM=IEBCOPY//*//SYSPRINT DD SYSOUT=*//*//IDOC DD DISP=SHR,DSN=SYS1.OrderID.DOCLIB,LABEL=(06,SL),// VOL=SER=tapeser,UNIT=tapeunit//ODOC DD DSN=Work.Library.JCL,// DISP=(NEW,CATLG,DELETE),// VOL=SER=volser,UNIT=SYSDA,// SPACE=(9600,(240,30,20))//*//SYSIN DD *

COPY INDD=IDOC,OUTDD=ODOCS M=LOADRIM

/*

� �

Figure 5. Panel: Copying the LOADRIM job from the "system and

2. Modify the following values for your order:


Tapeser Volume serial for the order shipment tape, which can be found on theexternal label and in Chapter 2 of your package Installation Guide.

Tapeunit Generic or esoteric name of the tape device that you will use to read theorder shipment tape. For example, if you ordered your CustomPac on a3590 tape cartridge, this is the device you use to read the 3590 tape.

Volser Volume serial number of the DASD volume on which the DOCLIB dataset is to be created. If UNIT specifies an esoteric name for a DASD poolto be used for permanent data sets, you can remove the VOL=SER=parameters of the DD statement instead of supplying this value.

SYSALLDA If your installation does not permit the use of SYSALLDA, change thisvalue to an appropriate esoteric or generic name.

ODOC Data set name for the LOADRIM job.

3. Run the EXTRACT job.

4. Before using the LOADRIM job to allocate and load the master dialog data sets, youmust customize the job. Replace the JOB statement with a JOB statement that is validfor your installation and supply values for the following:

CustomPac.QualifierHigh-level qualifier to be used for the master dialog data sets. Choose aunique high-level qualifier. IBM recommends that you not use an ordernumber as part of CustomPac.Qualifier. Also, do not use any SSAqualifier that you plan to use for any data sets that are included in theorder. Finally, you should not use SYS1, because you should catalog thedata sets in a user catalog to assure portability between systems. Forexample, you could choose a CustomPac.Qualifier like CPAC.MASTERor IBM.INSTALL, but should avoid names like SYS1.CPAC andINSTALL.order_number.



Each order includes order-related dialog data sets. You will need anotherunique qualifier for each order's data sets, which must be different fromthe one you choose for CustomPac.Qualifier.

volser The volume serial number of the DASD volume to be used to allocatethe master dialog VSAM data sets.

Tapeser Volume serial for the order shipment tape, which can be found on theexternal label and in Chapter 2 of your package Installation Guide.

Tapeunit Generic or esoteric name of the tape device that you will use to read theorder shipment tape. For example, if you ordered your CustomPac on a3590 tape cartridge, this is the device you use to read the 3590 tape.


SYSDA If your installation does not permit the use of SYSDA, change this valueto an appropriate esoteric or generic name for permanent data sets.

5. Run the LOADRIM job.

For complete tape layout information, see Chapter 2 of your package Installation Guide.

Copying the LOADRIMS or EUPDATES job from a serverFor orders downloaded from a server, IBM provides the LOADRIMS or LOADRIMH job

as a file on the server.

1. Click the link for the LOADRIMS or LOADRIMH job on the Shopz download pageand copy the file to your workstation. Then copy the LOADRIMS or LOADRIMH jobto your driving system.

2. Before using the LOADRIMS or LOADRIMH job to allocate and load your masterdialog data sets you must allocate and mount a UNIX file system to contain thedestination directory and its files, and then customize the job. Replace the JOBstatement with a JOB statement that is valid for your installation and supply values forthe following options:

PATH Specify the path for the directory in which the CustomPac dialog andorder information will be stored.



3. Run the LOADRIMS or LOADRIMH job.

Downloading the LOADRIM job from a DVDFor orders delivered on a DVD, IBM provides the LOADRIM job as a file on the DVD.

1. Copy the LOADRIM job to a workstation from the first DVD. Copy the LOADRIM jobthen to your driving system.

2. Before using the LOADRIM job to allocate and load your master dialog data sets youmust allocate and mount a UNIX file system to contain the destination directory and itsfiles, and customize the job. Replace the JOB statement with a JOB statement that isvalid for your installation and supply values for the following:



SET PATH Specify the path for the directory in which the CustomPac dialog andorder information will be stored.



3. Run the LOADRIM job.

Starting the DialogAfter you have installed the dialog, you can start it in any of the following ways -

• “Use a CLIST with LIBDEF statements” on page 23• “Start the Dialog from the ISPF Primary Option Menu” on page 24

Using the dialog in split screen mode:

You can use ISPF's split screen mode to run other applications while using the dialog, butthe dialog does not support being used in more than one logical session at a time.

Also, the dialog temporarily sets your TSO/E profile to NOPREFIX.

Ensuring a sufficient region size: The dialog requires a minimum region size of 9megabytes (MB). When you log on to TSO/E to use the dialog, ensure that the TSO/E logonpanel specifies a value of 9000 or greater in the size field. If this much private area storageis not available below 16 MB, log on with a region size greater than 16 MB (for example,SIZE = 17000). Doing so causes the system to use private area storage above 16 MB.

Allowing for the allocation of additional data sets: When allocating additional data sets toa TSO/E session using CLISTs or LIBDEFs, ensure that you have a sufficiently high valuespecified for the DYNAMNBR parameter on the EXEC statement in your logon proc.DYNAMNBR defines the number of data sets that can be dynamically allocated at the sametime. If this value is too low, the data set allocations will fail. For more information aboutusing DYNAMNBR with logon procs, see the following:

• z/OS TSO/E Customization, SA22-7783• z/OS MVS JCL User's Guide, SA22-7598• * z/OS MVS JCL Reference, SA22-7597.

Ensure that your ISPPROF data set has sufficient available space: Because the dialogcopies some of the SCPPSENU data set members into your ISPPROF data set, ensure thatthe ISPPROF data set has at least approximately 30 tracks of available space.

Ensure that SCEERUN is in the program search order: When you allocate the dialog'sdata sets to use the dialog, ensure that the SCEERUN data set is placed in the programsearch order the system uses for you. If the SCEERUN data set is not in the link list, add itto the following:

• STEPLIB concatenation in your logon proc, ahead of any other libraries that containPL/I run-time modules (such as PLI.PLIBASE or PLI.PLITASK)

• The JOBLIB concatenation used in installation jobs that use a JOBLIB concatenationahead of any other libraries that contain PL/I run-time modules(such as PLI.PLIBASEor PLI.PLITASK)



• STEPLIB concatenations used in installation jobs that do not use a JOBLIBconcatenation ahead of any other libraries that contain PL/I run-time modules(such asPLI.PLIBASE or PLI.PLITASK).

Use a CLIST with LIBDEF statementsCopy and modify the sample member CPPCSAMP in data set SCPPCENU as shown asfollows:

CPPCSAMP PROC 0 DEBUG /********************************************************************/ /* 5751-CS4, 5751-CS5, 5751-CS6, 5751-CS7 and 5751-CS9 */ /* Copyright IBM Corp. 1988, 2007 */ /********************************************************************/ /* */ /* */ /* Module name: CPPCSAMP */ /* */ /* Purpose: */ /* Add Copyright Information */ /* */ /* Author: CS05542 Date:5 Feb 2007 Change#: DMJ00000 */ /* */ /* Change History: */ /* */ /* */ /********************************************************************/

/*-----------------------------------------------------------*//* SAMPLE CLIST TO SETUP ENVIRONMENT AND START CPAC DIALOG *//* *//* NOTE: CHANGE CustomPac.Qualifier to your environment *//*-----------------------------------------------------------*/

IF &DEBUG = DEBUG THEN CONTROL MSG LIST CONLIST SYMLIST FLUSHELSE CONTROL NOMSG

ATTN LOGOFF /* IF ATTENTION INTERRUPT OCCURS *//* THEN LOGOFF */

/*-----------------------------------------------------------*//* ALLOCATE (CPP) APPLICATION LIBRARIES *//*-----------------------------------------------------------*/

ISPEXEC CONTROL ERRORS CANCEL /* ERROR MODE IS SET *//* DIALOG TERMINATE ON ERROR */

ALTLIB ACTIVATE APPLICATION (CLIST) +DATASET('CustomPac.Qualifier.SCPPCENU') UNCOND

SET &ALTLIBRC = &LASTCC

IF &ALTLIBRC NE 0 THEN +WRITE &SYSICMD: ALTLIB(ACTIVATE) RC = &ALTLIBRC

ELSE DOISPEXEC LIBDEF ISPMLIB DATASET ID('CustomPac.Qualifier.SCPPMENU')ISPEXEC LIBDEF ISPPLIB DATASET ID('CustomPac.Qualifier.SCPPPENU')ISPEXEC LIBDEF ISPSLIB DATASET ID('CustomPac.Qualifier.SCPPSENU')ISPEXEC LIBDEF ISPTLIB DATASET ID('CustomPac.Qualifier.SCPPTENU')ISPEXEC LIBDEF ISPLLIB DATASET ID('CustomPac.Qualifier.SCPPLOAD')

/*--------------------------------------------------------*//* START CPAC DIALOG *//*--------------------------------------------------------*/

ISPEXEC SELECT CMD(%CPPCISPF CustomPac.Qualifier) +NEWAPPL(CPP) PASSLIB

/*--------------------------------------------------------*//* CLEANUP *//*--------------------------------------------------------*/

ISPEXEC LIBDEF ISPMLIBISPEXEC LIBDEF ISPPLIBISPEXEC LIBDEF ISPSLIBISPEXEC LIBDEF ISPTLIBISPEXEC LIBDEF ISPLLIB

ALTLIB DEACTIVATE APPLICATION(CLIST)SET &ALTLIBRC = &LASTCCIF &ALTLIBRC NE 0 THEN +

WRITE &SYSICMD: ALTLIB(DEACTIVATE) RC = &ALTLIBRCEND

EXIT CODE(0)

Run the CLIST under TSO/E Option 6, as in the following example:

exec 'OBRIEN.MD053718.SCPPCENU(CPPCSAMP)'



Start the Dialog from the ISPF Primary Option MenuTo start the dialog from the ISPF primary option menu, modify and copy the CPPCSAMPCLIST from the SCPPCENU data set into a data set that is available in your SYSPROCconcatenation. Follow the instructions in “Use a CLIST with LIBDEF statements” onpage 23 to modify CPPCSAMP. Then, modify an existing ISPF selection panel (forexample, ISR@PRIM) to include the following:

Modifications to Options Panel

)BODY

C CustomPac - Manage and Install CustomPac Orders

)PROC

&ZSEL = TRANS(&ZCMD,..........

C,'CMD(%CPPCSSMP)'.....)

After making this change, you can start the dialog by selecting option "C" from the selectionpanel you just modified.

If you use 44 character data set names, you must specify the ISPFX(Y) parameter (withoutthe curly braces).

Use a Clist with LIBDEF Statements

Copy and mofify the sample Clist CPPCSAMP, which is shipped in the SCPPCENU library.



Sample Clist: CPPCSAMPPROC 0 DEBUG

/*-----------------------------------------------------------*//* SAMPLE CLIST TO SETUP ENVIRONMENT AND START CPAC DIALOG *//* *//* NOTE: Change CustomPac.Qualifier to your environment *//*-----------------------------------------------------------*/

IF &DEBUG = DEBUG THEN CONTROL MSG LIST CONLIST SYMLIST FLUSHELSE CONTROL NOMSG

ATTN LOGOFF /* IF ATTENTION INTERRUPT OCCURS *//* THEN LOGOFF */

/*-----------------------------------------------------------*//* ALLOCATE (CPP) APPLICATION LIBRARIES *//*-----------------------------------------------------------*/

ISPEXEC CONTROL ERRORS CANCEL /* ERROR MODE IS SET *//* DIALOG TERMINATE ON ERROR */

ALTLIB ACTIVATE APPLICATION (CLIST) +DATASET('CustomPac.Qualifier.SCPPCENU') UNCOND

SET &ALTLIBRC = &LASTCC

IF &ALTLIBRC NE 0 THEN +WRITE &SYSICMD: ALTLIB(ACTIVATE) RC = &ALTLIBRC

ELSE DOISPEXEC LIBDEF ISPMLIB DATASET ID('CustomPac.Qualifier.SCPPMENU')ISPEXEC LIBDEF ISPPLIB DATASET ID('CustomPac.Qualifier.SCPPPENU')ISPEXEC LIBDEF ISPSLIB DATASET ID('CustomPac.Qualifier.SCPPSENU')ISPEXEC LIBDEF ISPTLIB DATASET ID('CustomPac.Qualifier.SCPPTENU')ISPEXEC LIBDEF ISPLLIB DATASET ID('CustomPac.Qualifier.SCPPLOAD')

/*--------------------------------------------------------*//* START CPAC DIALOG *//*--------------------------------------------------------*/

ISPEXEC SELECT CMD(%CPPCISPF CustomPac.Qualifier { ISPF4X(Y) } ) <<<<<<<<<<

/*--------------------------------------------------------*//* CLEANUP *//*--------------------------------------------------------*/

ISPEXEC LIBDEF ISPMLIBISPEXEC LIBDEF ISPPLIBISPEXEC LIBDEF ISPSLIBISPEXEC LIBDEF ISPTLIBISPEXEC LIBDEF ISPLLIB

ALTLIB DEACTIVATE APPLICATION(CLIST)SET &ALTLIBRC = &LASTCCIF &ALTLIBRC NE 0 THEN +

WRITE &SYSICMD: ALTLIB(DEACTIVATE) RC = &ALTLIBRCEND

EXIT CODE(0)

Use a Clist to Start the Dialog without First Starting ISPFAfter logging on to TSO, you can start the dialog by entering the CPPCINIT command fromthe TSO READY prompt(IE. After logging on you were taken directly to the READY prompt, or you have terminatedISPF using the "X" option from the ISPF Primary Option Menu).



� �READY

EX 'CustomPac.Qualifier.SCPPCENU(CPPCINIT)' 'CustomPac.Qualifier'

� �


Installation Overview

Chapter 4. Installation Overview

The installation of an order is performed in 2 separate stages:

• Receiving your Order

• Installing your Order

An additional function of the dialog -

• Managing the Order Inventory

assists in tracking the progress of order being installed, and provides an audit trail ofinstalled orders.

Receiving your Order

Use the dialog to receive your CustomPac order. The dialog generates a job to receive thenew order by loading information from a tape, a server, or a file system (local host orattached) to your DASD.

Receiving the order ensures that the following processes occur:

• The dialog is informed that the order is available for customization and installation.

• The IBM-supplied shipped configuration is copied to your DASD.

Installing your Order

When you install an order, you receive a shipped configuration, from which you create workand saved configurations.

These configurations are briefly described here, and, in detail, later in this book:

• Shipped:The IBM-supplied default configuration (tailored to your order).

• Work:A working copy of the order configuration that you tailor as you proceed withthe dialog. You use the installation dialog to create a copy of the shipped orderconfiguration and, optionally, merge it with a saved configuration.

• Saved:A work configuration that was tailored with installation information from apreviously installed order. You can have a different saved configuration for each order.For example, assume that you have installed three ServerPac orders and saved eachconfiguration. If you install a fourth ServerPac order, you have three savedconfigurations from which to select for merging with the work configuration. You are,however, limited to one saved configuration for merging.

Tip:You can also use a saved configuration to take a checkpoint while working with anorder. After you have selected all the prior options and have no configuration warnings,you can save the configuration with the Save option and use it to recreate the sameconfiguration, even for the same order. You do not need to submit any jobs to enablethe option and save the configuration. So, if there are changes you want to try, but arenot sure about, save the configuration and go ahead and try them. If the results areunsatisfactory, recreate the configuration using the saved one to get right back to whereyou were.

Installing a CustomPac order involves the following steps:

Chapter 4. Installation Overview 27


• Create a configuration to tailor. The shipped order configuration forms the basis of awork configuration that you will tailor. If you previously installed a ServerPac ordump-by-data-set SystemPac, and you saved the configuration, you can merge thesaved version with the shipped configuration. Whenever possible, the dialog will carryforward the changes that you made the last time, so you will not need to repeat them.The resulting work configuration requires less tailoring than was needed the first time.

• Tailor the work configuration. You use a series of dialog panels to:

− Select the installation type: full system replacement or software upgrade.− Define the variables to be used in the installation jobs.− Select appropriate names for the SMP/E zones.− Change the attributes and placement of data sets in the work configuration to suit

your needs.− Define your alias-to-catalog relationships.− Define your catalogs.

• Submit installation jobs. The installation dialog generates a series of jobs that you runon your system to create a new target system or subsystem. The jobs are generatedbased on the work configuration for your order, but you can edit them through thedialog if you want. Another book, SystemPac: Installation Guide guides you throughthis part of the process. That book describes the post-installation jobs that you mustrun, and guides you through your first IPL and verification of the target system.

− For physical orders, this book is shipped on tape in the SCPPLENU data set.− For DVD orders, this book is shipped on DVD in the SCPPLENU data set.− For electronic orders, the SCPPLENU data set is shipped in the ORDER package.

This data set is loaded to DASD when you receive your order.

In addition to the SCPPLENU data set, for tape orders, this book is also provided as aPDF file on the DVD shipped with the order. For DVD orders, this book is alsoprovided as a PDF file on the first DVD shipped for the order. For internet deliveryorders, this book is also provided as a PDF file on the Shopz download page.

• Save the work configuration and update the inventory. Save the workconfiguration, so that you can reuse the data for future orders. Then, use the dialog toupdate the order inventory.

OVERVIEW - Order Information

The Order Information Dialog provides information about an order which has been or isbeing installed.

(See Chapter 16, “Managing the Order Inventory” on page 214).

This dialog -

• Provides information about all previous and current orders.

• Allows tracking of all orders.

• Will write summary details of an order, its products and FMIDs to a customer specifieddata set.



Primary Option Menu

� � CustomPac ------------------- IBM Corporation -------------------------27.20.00 OPTION ==>

CustomPac Order Management Menu

R RECEIVE - Receive an Order

I INSTALL - Install an Order

Order Number ==> (Leave Blank to list uninstalled orders)

D DISPLAY - Select Orders to Display

Master dialog data set qualifiers: CPAC.MASTER

This dialog supports secure Internet delivery.

********************************************************* 5751-CS4, 5751-CS5, 5751-CS6, 5751-CS7 and 5751-CS9 ** Copyright IBM Corp. 1988, 2013 *********************************************************

� �

Figure 6. CPPPPOLI - Primary Option Menu

The CustomPac Primary Option Menu is the launch point for all functions needed tomaintain and install your CustomPac order.

R Receive an Order

This will unload the control tables and installation jobs from the shipmenttapes to your DASD.

You may be asked to enter some of the information from the documentationthat was shipped with the order, so have this available.

(See Chapter 5, “Receiving a New Order” on page 31).

I Install Orders

If you leave the order number field BLANK then a list of NEW orders will bedisplayed, and you can select the one you want to work on.

(See Chapter 6, “Installing the New Order” on page 48).

If you know the order number it may be more convenient to enter this into theorder number field.

Whatever method is used a further menu, the "Installation" menu will bedisplayed.

(See “Installation Options Menu” on page 52).

D Display Orders

If you want to know anything about any CustomPac order ....

This will display a summary of all CustomPac orders, the display may berestricted by specific order statuses.

Order details may be saved to a customer defined data set.

Chapter 4. Installation Overview 29


(See Chapter 16, “Managing the Order Inventory” on page 214).

Once you have selected an order for processing, an enque is issued against the order number.

This ensures that when you use the dialog only ONE person can be working on an individualorder at any one time (although several people can be working on several different orders).


Receiving a New Order

Chapter 5. Receiving a New Order

This section describes the required steps when receiving new orders.

Required Migration StepIf you are using a dialog whose package version is less than &diagver, you must migrate thedialog to level 27.20.00 or later. If the dialog level is less than &diagver, and you want togenerate the RECEIVE job to use the HTTP Secure (HTTP using Secure Sockets Layer orHTTPS) download method, then you must migrate the dialog to level 27.20.00 or later. Todetermine whether your dialog is at the correct level, look for the dialog level number in theupper right-hand area of panel CPPPPOLI, the first panel displayed when the dialog starts.

Beginning the receive process To begin receiving the order, select option R from the Main Installation panel (Figure 6 onpage 29) and press Enter.

The dialog displays the Receive an Order panel (Figure 7 ) for you to enter informationabout the order.

� � CPPP610A ---------------------Receive an Order -------------------------------- COMMAND ==>

Receive the order from ==> F - File systemS - ServerT - Tape

Order Number ==> MD053718

-------------- Order Dialog Data Set Allocation Information -------------

Data Set Qualifiers ==> STOB4.MD053718 (Must be unique)

Volume Serial ==> R12345 (Blank for SMS-managed data sets)- or -

STORCLAS ==> (Blank for non-SMS-managed data sets)Specify a data class for SMS or non-SMS managed data sets (optional).DATACLAS ==>Specify a management class for only SMS managed data sets (optional).MGMTCLAS ==>Dialog CLIST Record Format ==> FB (FB or VB)

Press Enter to continue or End to cancel

Note:The generated RECEIVE job will be saved in the Order's SCPPBENU data set.

� �

Figure 7. CPPP610A - Receive an Order

The fields, and their processing requirements are as follows -

Receive the order fromEnter either S for Server, F for File System, or T for Tape to specify wherethe CustomPac order resides. Server indicates that the CustomPac order isto be received from a server. Tape indicates that the CustomPac order is tobe received from tape. File System indicates that you used the Store andForward download method (download to workstation) and then uploaded the

Chapter 5. Receiving a New Order 31


order to the host Download Filesystem outside the Dialog. The RECEIVE jobgenerated by this option will retrieve the order directly from the Filesystemand not attempt a download. For DVD orders, you can choose either F or S.If you have set up a server such that the source directory points to theworkstation directory where the order is copied, choose S; otherwise, enter F.

There are three methods to upload the DVD files to the z/OS host system,including:

• Configure your workstation as a server. You can then use the CustomPacInstallation Dialog to receive the package from your workstation as anintermediate node. In this case you are first required to copy DVD ordercontent to your workstation.

• Transfer the files from the workstation to the z/OS host, using FTP fromyour workstation. In this case you are first required to copy DVD ordercontent to your workstation.

• Transfer the files from the DVD to the z/OS host, using FTP from yourworkstation. In this case you are not required to copy DVD order contentto your workstation.

Order NumberEnter your order number, as it was supplied by IBM (two alphabeticcharacters followed by six numerics). In Figure 7 on page 31, for example,the order number is MD053718.

To find your order number:

• For tape orders, check the title page of CustomPac Installation Guide.(IYO.pdf file on the DVD) or the printed label on the first "system anddistribution tape".

• For internet orders, check the title page of CustomPac Installation Guidefile ("Server: Installing Your Dialog" link) or Dialog Data file("Required information for ServerPac Dialog" link) provided on theShopz download pages.

• For DVD orders, check the title page of CustomPac Installation Guide(IYO.pdf file on the first DVD) or look at file Required information forCustomPac Dialog (DIALOG.txt file on the first DVD).

Data Set QualifiersEnter the high-level qualifier (without quotation marks) that you plan to useto allocate the order libraries.

IBM recommends that you include your order number as part of the qualifierto ensure that it is unique. For example, if your order is MD053718, you canspecify Data Set Qualifiers ==> STOB4.MD053718.

Do not use the CustomPac.Qualifier.

Consider placing all of the order s data sets on the same volume as the masterdialog data sets to make it easier to port the dialog to the target system. Formore information, see “Allocating and Cataloging the Dialog Data Sets” onpage 16.

Volume Serial or STORCLASEnter the serial number of the DASD volume that will receive the order datasets or a valid storage class (for SMS managed data sets) to be used toallocate the data sets.



DATACLAS Enter a valid data class (for SMS or non-SMS managed data sets) to be usedto allocate the data sets. This is an optional field.

MGMTCLASEnter a valid management class (for SMS managed data sets) to be used toallocate the data sets. This is an optional field.

Dialog CLIST Record FormattsEnter VB if you want to use the variable-block versions of the dialog s

CLISTs, which are supplied in the order in both FB and VB formats. FB isthe initial default, but any value specified here is saved in the user s profile(ISPPROF) data set when the Enter key is pressed and becomes the newdefault value.

When you press Enter, the next panel displayed will be either the:

Receive an Order From Tape panel (Figure 10 on page 36)if Tape is specified on the Order Type field, or

Download Server Information panel (Figure 12 on page 37)if Server is specified on the Order Type field

Order ReplaceThe Order Inventory is scanned for existing orders with the same order number as the oneyou are trying to receive.

If multiple occurances are found of the same order number, then a selection list is built anddisplayed.

� � CustomPac --------------------- Replace an Order ------------- Row 1 to 2 OF 2 COMMAND ==> SCROLL ==> PAGE

Line Commands:(Select)

You specified an order number that is already received. To proceed:

- Select a copy of the order and press Enter to replace it; or,- Press Enter to create another copy of the order; or,- Press End to cancel the operation and return to the prior panel.

--- Last Change -- S Order System Name SREL Package Build Date Status User Date

- -------- ----------- ---- -------- ---------- --------- ------- ---------- MD000277 MULT SERV 03/11/2003 Installed STOB5 15/11/2003 MD000277 MULT CRMO 30/11/2003 Installed STOBBS 30/11/2003 ******************************* BOTTOM OF DATA ********************************

� �

Figure 8. CPPP6104 - Order Receive - Replace Order in Order Inventory

If this panel IS displayed you have multiple occurances of the same order number.



HOW Can I Have Multiple Occurance ?

Assume your original order for a SystemPac was order number MD000277.

As time goes by you may receive selective follow on service (PTF's) which may beadded to the Order Inventory with order number MD000277, thereby identifying whichPTF's are applicable to which system shipment.

The order number would be the same, but the package type (PAC) would be different(EG. SERV for the ServerPac and maybe CRMO for the service).

You may REPLACE an existing order (by selecting it !) OR if you make NO selection andjust hit the END key it will be assumed that you wish to receive a NEW order.

Be AWARE however, that replacing an existing order involves deleting all SCPPxENUdata sets for that order. So if you replace an MVS CustomPac by an SFS of the same ordernumber you will no longer be able to view details of the original CustomPac. The followingPrimary Commands are valid for this panel -

?, SET, F, L, N, P, SORTThese are standard CustomPac table handling commands.(See Chapter 2, “Understanding The Dialog” on page 7)

CANCEL This may be abbreviated to CAN.

The receive of the order will be cancelled.

The standard ISPF END command CONTINUES processing.

If an order was Selected, it will be replaced.

The following Line Commands are valid for this panel -

Note: Multiple selection is NOT allowed.

D De-Select This De-Selects an order that was previously selected forreplacement.

S Select This selects an order for replacement.

The order will be flagged by an Q to the left of the Order Number field.

Confirm Deletion of data setsThe first step of the receive job is to delete any existing data sets for the order under thesupplied order high level qualifier.

This panel is displayed when data sets EXIST under the supplied high level qualifier.



� � CustomPac ----------------------- Order Receive ------------------------------- COMMAND ==>

CONFIRM DATASETS ARE TO BE DELETED

`````````````````````````````````````````````````````````````````````````````````` ``````````````````````````````````````` ORDER : MD000277 ``````````````````````````````````````` `````````````````````````````````````````````````````````````````````````````````````` `````````` Order HLQ : `````````` `````````` GLANDALE.MD000277 `````````` `````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````

`` You MUST Confirm DELETION By Typing DELETE and pressing ENTER

`` Press the END or RETURN key to CANCEL the DELETE request

� �

Figure 9. CPPP6102 - Order Receive - Confirm Deletion of data sets

data sets already exist under your specified order high level qualifier.

You must CONFIRM that the data sets cane be deleted.

Type DELETE in the COMMAND ==> field and press enter.

The END or RETURN keys will cancel the receive for the order.

Receiving an Order from TapeIf you select the Tape option on the Receive an Order panel, the dialog displays the Receivean Order From Tape panel (Figure 10 on page 36) for you to enter the information neededto load the order s data sets from tape.



� � CustomPac ------------------Receive an Order From Tape ------------------------ COMMAND ==>

RIM Tape Volume Serial ==> TAPE01

Tape Unit ==> 3590 (Generic or esoteric tape unit name)


� �

Figure 10. CPPP6101 - Receive an Order From Tape

In the Receive an Order From Tape panel, fill in the fields as follows:

RIM Tape Volume SerialEnter the volume serial number of the IBM-supplied tape that contains theorder-related installation material. This is the tape labeled with the ordernumber and volume serial in the format Rxxxxx, where "R" stands for "RIMtape" and "xxxxx" is the remainder of the volume serial. The exact label forthe RIM tape can be found in CustomPac Installation Guide.

Note: The first RECEIVE job after installing a new copy of the dialog mustuse the RIM tape from the same order used to run the LOADRIM job thatinstalled the dialog. After the first RECEIVE job is run, RECEIVE jobs canbe run in any order.

TAPE Unit Enter the type of the device on which the order tape is to be mounted, or asuitable, locally-defined esoteric unit name.

Press Enter. The panel in Figure 22 on page 45 is displayed. The next several panels are fordownloaded orders only, you can skip ahead to the panel shown in “Generating theRECEIVE Job” on page 44.

Receiving an Order from the File SystemIf you select the F (File System) option on the Receive an Order panel, the dialog displaysthe Receive an Order From the File System panel (Figure 11 on page 37) for you to enterthe information needed to load the order's data sets from the file system. This option is usedwhen you have used the Store and Forward download method (download to workstation)and then uploaded the order to the host Download File system outside the Dialog. TheRECEIVE job generated by this option retrieves the order directly from the file system anddoesn't attempt a download. When using the option to receive an order electronically from afile system you need to make the electronic images local to the host (driving system). TheCustomPac installation expects the new directory names be in the format (content and orderin lowercase):

/<ordernum>.order/<ordernum>.content



Where ordernum is the order number obtained from the CustomPac: Installation Guide file("Server: Installing Your Dialog" link) or Dialog Data file ("Required information forSystemPac Dialog" link) provided on the Shopz Download page.

� �CPPP610G------------ Receive an Order From the File system ---------------------COMMAND ==>

Target Directory ==>/service/very/big/omvs/filesystem/for/custompac/zosv1r6/v2

� �

Figure 11. CPPP610G - Receive an Order From the File System

In the Receive an Order from the File System panel, fill the field as follows:

Target directoryEnter the path name of the directory to which the order has been storedlocally on your host system.

Press Enter, the Edit JOB Statement panel (Figure 23 on page 45.) displays.

Receiving an Order from a ServerIf you select the Server option on the Receive an Order panel, the dialog displays theDownload Server Information panel (Figure 12) for you to enter the information needed toload the order s data sets from the server.

� �CPPP610B ------------------Download Server Information -------------------------COMMAND ==>

Enter either the Server's Name or Address below:

==>

Source Directory ==>/some/directory/on/some/server/somewhere/in/the/world

User ID ==>Somebody

Password ==>whoami

Hash Value ==>1234567890123456789012345678901234567890 (40 Characters)


� �

Figure 12. CPPP610B - Download Server Information



In the Download Server Information panel, fill in the fields as follows:

Server s Name or AddressEnter the name or address of the server from which the order is to bedownloaded. This value is required.

The server might be an IBM server or it might be an intermediate server towhich the order has been transferred from an IBM server.

| Note: Standard FTP (FTP) will no longer be available as a download| method option on the Specify Download Method panel if the name or address| entered is for an IBM server.

Source DirectoryEnter the name of the directory on the server that contains the order. Thisvalue is required.

User ID Enter a valid user ID to be used to log on to the server. This value is required.

Password Enter the password for the user ID. This value is required.

Hash Value Enter the hash value to be used for this download. This value is required.

If an intermediate server is used, the hash value must be the same as the oneused for transferring the order from the IBM server.

Note: When downloading from an IBM server, it is expected that most users will copy andpaste most or all of the data to be entered on this panel from the Dialog Data file providedon the Shopz download page. Data entered on this panel is case sensitive.

Press Enter. The Download File System Information panel (Figure 13) is displayed.

� �CPPP610C ---------------Download File System Information -----------------------COMMAND ==>

Target Directory ==>/service/very/big/omvs/filesystem/for/custompac/zosv1r6/v2

Allocate a new file system data set ==> YES (Yes or No)

--------------------------New File System Data Set Information -----------------

Data Set Name ==> OMVS.ZOSV1R6.FILE.SYSTEM Mount Point ==> /service/very/big/omvs/filesystem/for/eserverpac File System Type ==> ZFS (HFS or zFS) Primary Space ==> 17206 (Minimum 500 cylinders) Secondary Space ==> (Secondary space recommended) Volume Serial ==> (Leave blank for SMS)

- or - STORCLAS ==> USSCLASS (STORCLAS required for multivolume data set)

Specify a data class for SMS or non-SMS managed data set (optional). DATACLAS ==> Specify a management class for only SMS managed data set (optional). MGMTCLAS ==>


� �

Figure 13. CPPP610C - Download File System Information

In the Download File System Information panel, fill in the following fields:

Target DirectoryEnter the path name of the target directory into which the order is to bedownloaded. This value is required.



Allocate a new file system data setEnter Yes to allocate a new file system data set or No to use an existing filesystem data set. This value is required.

If Yes is specified for Allocate a new file system data set, then fill in the following fields:

Data Set NameSpecify a standard data set name for the file system data set.

Mount Point Specify the path name of the mount point for the file system data set.

File System TypeSpecify either HFS (for a hierarchical file system) or ZFS (for a zSeries filesystem). ZFS is the default.

Primary SpaceYou can find the order size in the Dialog Data file provided on the ShopzDownload Page. This can be used in the algorithm to determine the spacerequired in the filesystem. You can specify a primary space value of 500 to99999 cylinders. The default is the minimum value, which is 500 cylinders.

Guideline:On a 3390 DASD, 1.4 cylinders are required for eachMB(Megabytes). On a 3380 DASD, 1.7 cylinders are required per MB. Toassure adequate work space, 500 cylinders should be added to the amount ofthe space calculated.

Note: On a 3390 DASD, an order that required 5GB could be downloadedand processed using a file system that had: ((5000MB) * (1.4 cylinders/MB))+ 500 = 7500 cylinders.

Secondary SpaceSpecify a secondary space value of 1 to 99999 cylinders, or leave blank if nosecondary space is desired.

Guideline: Secondary space is recommended. Specifying space for this filesystem requires that you perform a calculation and estimate the size of thelargest file requiring a workspace within the file system as described above.There is opportunity for error in this calculation, and no way to "know"exactly how much workspace will be required. Your chances of success are"much" better if you specify secondary space.

Volume SerialFor a non-SMS-managed data set, specify the volume serial for an onlinevolume. For an SMS-managed data set, leave this field blank.

STORCLAS For a SMS managed data set, specify a valid storage class to be used toallocate the data set.

DATACLAS For SMS or non-SMS managed data set, specify a valid data class to be usedto allocate the data set. DATACLAS is an optional field.

MGMTCLASFor an SMS managed data set, specify a valid management class to be used toallocate the data set. MGMTCLAS is an optional field.

Note: If this panel has previously been used to supply information, the fields on the panelare primed with information previously supplied for this order num (if any), the last inputfrom this user ID (if any), or the most recent available.

| Press Enter. The Specify Download Method panel (Figure 14 on page 40 ) is displayed. If| an IBM download server name or address is specified on the Download Server Information



| panel, then the Specify Download Method panel is displayed and Standard FTP (FTP) is not| listed as a possible option.

� �CPPP610F ------------------- Specify Download Method -----------------------COMMAND ==>

Specify the Download Method you will be using: Standard FTP (FTP),Secure FTP (FTPS), or HTTP Secure (HTTPS)==> (FTP, FTPS, or HTTPS)


� �

Figure 14. CPPP610F - Specify download method

On the Specify Download Method panel, specify the download method that you will use.Answer FTP or FTPS or HTTPS to the question about the download method. If you specifyFTP or FTPS and press Enter, the Download Client Information panel (Figure 15) isdisplayed. If you specify HTTPS and press Enter, the Download Client Information panel(Figure 17 on page 42) is displayed.

� �CPPP610D -------------------- Firewall Commands --------------------------------COMMAND ==>

Do you need to enter commands to pass through a local FTP Firewall?(Yes or No)==> NO

Specify your Java home directory(for example: /usr/lpp/java/J1.4/ or leave blank if you are using ICSF)==> /usr/lpp/java/J1.6

For further information, review the discussion of the CLIENT (SMPCLNT DD)dataset in the SMP/E Commands manual.


� �

Figure 15. CPPP610D - Download Client Information

On the Download Client Information panel, you need to specify two pieces of information:

• Answer either YES or NO to the question about your need to enter commands to passthrough a local firewall.

If you specify NO (the default), you are indicating that no firewall commands arerequired by the server from which you plan to download your order.

• Indicate whether you are using ICSF or Java for encryption.

If you are using ICSF, delete the sample Java directory information and leave this fieldblank.

If you are using Java encryption, you need to specify your Java home directory on thisline in the format shown.


If you specify YES to the Firewall question and press Enter, an ISPF Edit panel is displayedwith a data set member containing skeleton firewall commands. Initially, this memberappears as shown in Figure 16 on page 41. If you specify NO to the Firewall question, andyou specified FTP as the download method on the Specify Download method panel(Figure 14), then when you press Enter, the Edit JOB Statement panel (Figure 22 onpage 45) is displayed. If you specified FTPS as the download method, then when you pressEnter, the Specify Secure FTP Options panel (Figure 19 on page 43) is displayed.

� �CPPPEDIF - MD053718 ----------------------------------------- COLUMNS 000 000COMMAND ==> SCROLL ==>HALF***********************************Top of Data ******************************000001 000002 000003 000004 000005 000006 000007 000007 000002 000003 000008 000009 000010 000011 000012 000013 000014 000015 000016 000017 000018 000019 000020 000021 000022 000023 000024 000025 000026 000027 000028 ****************************Bottom of Data ***********************************

� �

Figure 16. CPPPEDIF Panel With Firewall Commands

Edit this member to supply the needed firewall information and to remove the comment tags(<!- and ->) from around the SMP/E tags. When you save the member and end the editingoperation (with either the END Command or the END key), any changes you made aresaved for future use. After ending the Edit session, the Edit JOB Statement panel(Figure 22 on page 45 ) is displayed if you entered a download method of FTP on theprevious Specify Download Method panel or the Specify Secure FTP Options panel(Figure 19 on page 43) is displayed if you entered a download method of FTPS on theprevious Specify Download Method panel. Tip: If you get here by accident, you do notneed to back up. Press the END key to save the commented-out firewall commands andcontinue.


� �CPPP610D -------------------- Firewall Commands --------------------------------COMMAND ==>

Do you need to enter commands to pass through an HTTP or SOCKS Proxy?(Yes or No)==> NO

Specify your Java home directory (required)(for example: /usr/lpp/java/J7.0_64)==> /usr/lpp/java/J1.6

Specify the name of the security manager keyring or CERTAUTH virtualkeyring or the keyword javatruststore (required)'(for example: host_userid/ShareableKeyRing or *AUTH*/* or javatruststore)==>

For further information, review the discussion of the CLIENT (SMPCLNT DD)dataset in the SMP/E Commands manual.


� �

Figure 17. CPPP610D Download Client Information

• Answer either YES or NO to the question about your need to enter commands to passthrough an HTTP or SOCKS Proxy Server.

If you specify NO, you are indicating that no HTTP or SOCKS Proxy Server commandsare required.

• Specify your Java home directory in the format shown. This field is required.

• Specify the security manager key ring or CERTAUTH virtual key ring or keywordjavatruststore. It is a required field.

If you specify YES to the HTTP or SOCKS Proxy Server question and press Enter, anISPF Edit panel is displayed with a data set member that contains skeleton HTTP orSOCKS Proxy Server commands. Initially, this member appears as shown in Figure 18on page 43.

If you specify NO to the HTTP or SOCKS Proxy Server question and press Enter, theEdit JOB Statement panel (Figure 22 on page 45) is displayed.



� �CPPPEDIF - MD053718 ----------------------------------------- COLUMNS 000 000COMMAND ==> SCROLL ==>HALF***********************************Top of Data ******************************000001 <-- This section builds the SMPCLNT DD input. -->000002 <-- -->000003 <-- Most HTTPS operations to the remote IBM Server pass through an -->000004 <-- HTTP or SOCKS Proxy Server. If so, then you must identify HTTP or -->000005 <-- SOCKS Proxy Server information and commands below. When you have -->000006 <-- finished, press End to display and submit the RECEIVE job. -->000007 <-- -->000002 <-- Or,use the CANCEL command to return to the prior panel. -->000003 <-- -->000008 <-- Notes: -->000008 <-- 1. All tags below are commented out. Remove the XML comment start -->000009 <-- and end tags to specify HTTP or SOCKS Proxy Server information. -->000011 <-- 2. The tags here are defined by SMP/E.For -->000012 <-- information about them,see SMP/E Commands. -->000013 <-- 3. Do not include <CLIENT>tags in this data set. -->000014 <-- They are built automatically by the dialog. -->000015 <-- -->000016 <-- <HTTPPROXY -->000018 <-- host="host name|host ip address" -->000019 <-- user="userid" -->000020 <-- pw="password" -->000021 <-- port="port number"> -->000027 <-- </HTTPPROXY> -->000028 <-- -->****************************Bottom of Data ***********************************

� �

Figure 18. CPPPEDIF panel with HTTP or SOCKS proxy server statements

Edit this member to supply the needed HTTP or SOCKS Proxy Server information and toremove the comment tags (<-- and -->) from around the SMP/E tags. When you save themember and end the editing operation (with either the END Command or the END key), anychanges you made are saved for future use. After the Edit session is ended, the Edit JOBStatement panel (Figure 22 on page 45) is displayed.

� �CPPP610S ------------------ Verify Secure FTP Usage ------------------- --------COMMAND ==>

Will you be using an Existing FTP.DATA File? (Yes or No) ==>


� �

Figure 19. CPPP610S Specify Secure FTP Options

Answer either YES or NO to the question about using an Existing FTP.DATA File. If youspecify NO, when you press Enter, an ISPF Edit panel is displayed with a data set membercontaining skeleton secure FTP commands. Initially, this member appears as shown inFigure 20 on page 44).



� �CPPPEDIF - MD053718 ----------------------------------------- COLUMNS 000 000COMMAND ==> SCROLL ==>HALF***********************************Top of Data ******************************000001 ; These FTP.DATA statements provide the FTP client with information000002 ; to communicate with the FTP server securely using TLS.000003 ; Change values or add new lines based on your system set up.000004 SECURE_MECHANISM TLS000005 TLSRFCLEVEL CCCNONOTIFY000006 TLSMECHANISM FTP000007 SECURE_FTP REQUIRED000007 SECURE_CTRLCONN CLEAR ; Commands may be clear (unencrypted).000002 SECURE_DATACONN PRIVATE ; Payload must be encrypted.000003 KEYRING myid/keyring1000008 EPSV4 TRUE****************************Bottom of Data ***********************************

� �

Figure 20. CPPPEDIF panel with secure FTP commands

Edit this member to supply the needed secure FTP commands. When you save the memberand end the editing operation (with either the END command or the END key), any changesyou made are saved for use in the RECEIVE job and the Edit JOB Statement panelFigure 22 on page 45 is displayed. If you specify YES to the using Existing FTP.DATAFile question, when you press Enter, fields will be displayed as shown in Figure 21, tospecify the z/OS UNIX file name or a data set name for the FTP.DATA file that will be usedin the RECEIVE job.

� �CPPP610S ----------------- Specify Secure FTP Options --------------------------COMMAND ==>

Will you be using an Existing FTP.DATA File? (Yes or No) ==> YES

Specify the z/OS UNIX file name OR data set name for the FTP.DATA file(for example: /user/ftp/userid.ftp.data OR USERID.FTP.DATA).File Name ==>

- or -Data set name ==>


� �

Figure 21. CPPP610S Specify Secure FTP Options

You must enter a File Name or a Data set name but not both for the case when YES isspecified for the Existing FTP.DATA File question.

After specifying either a file name or a data set name for the Existing FTP.DATA File, whenyou press Enter, the Edit JOB Statement panel Figure 22 on page 45) is displayed.

Note: If you choose to use Secure FTP to download your order, the RECEIVE job isgenerated with only -f parameter. You can edit the generated JCL to add any other FTPparameters as required by your system settings.

Generating the RECEIVE Job



� �CPPP6103 --------------------Edit JOB Statement --------------------------------COMMAND ==>>

Press Enter to edit the JOB statement.The information you enter herecreates the JOB statement that is used to generate the RECEIVE job,and used later for the installation jobs.(If you want to change theJOB statement before generating the installation jobs,you will beable to change it later by selecting "DEFAULT JOBCARD.")

Press Enter to continue or End to cancelFILES', <

� �

Figure 22. CPPP6103 - Edit JOB Statement

Press Enter. An ISPF Edit panel is displayed with a data set member containing a skeletonJOB statement. Initially, this member appears as shown in Figure 23.

� �CPPPEDIF - MD053718 ----------------------------------------- COLUMNS 000 000COMMAND ==> SCROLL ==>HALF*********************************** TOP OF DATA ******************************000001 //JOBNAME JOB ,ACCOUNTING INFO , PROGRAMMER NAME ,000002 // CLASS=A,000003 // MSGCLASS=H,000004 // MSGLEVEL=(1,1),000005 // NOTIFY=&SYSUID.,000006 // USER=&SYSUID.,000007 // TIME=NOLIMIT,000008 // REGION=0M000009 //*000010 //JOBLIB DD DISP=SHR,DSN=DAVID.DO000277.SCPPLOAD000011 //*000012 //* ***********************************************************000013 //* *THIS JCL WAS GENERATED BY SKELETON CPPS6101000014 //* ***********************************************************000015 //*000016 //STEP00 EXEC PGM=IDCAMS000017 //*000018 //* ***********************************************************000019 //* *DELETE EXISTING ORDER LIBRARIES000020 //* ***********************************************************000021 //*000022 //SYSPRINT DD SYSOUT=*000023 //*000024 //SYSIN DD *

� �

Figure 23. CPPPEDIF Panel With JOB Statement

Modify the JOB statement as required and press Enter. The Edit RECEIVE Job panel(Figure 24 on page 46) is displayed.



� �CPPP610E --------------------- Edit RECEIVE Job --------------------------------COMMAND ==>

Press Enter to edit and submit the RECEIVE job.After making any needed changes,submit the job.

(Note:A copy of the job will be saved in theSCPPBENU data set.)


� �

Figure 24. CPPP610E - Edit RECEIVE Job

Press Enter. An ISPF Edit panel is displayed with a data set member containing thegenerated RECEIVE job. Initially, this member appears as shown in Figure 25

� �CPPPEDIF - MD053718 ----------------------------------------- COLUMNS 000 000COMMAND ==> SCROLL ==>HALF*********************************** TOP OF DATA ******************************000001 //JOBNAME JOB ,ACCOUNTING INFO , PROGRAMMER NAME ,000002 // CLASS=A,000003 // MSGCLASS=H,000004 // MSGLEVEL=(1,1),000005 // NOTIFY=&SYSUID.,000006 // USER=&SYSUID.,000007 // TIME=NOLIMIT,000008 // REGION=0M000009 //*000010 //* MODIFY THE JOB STATEMENT ABOVE AS REQUIRED FOR YOUR INSTALLATION'S000011 //* REQUIREMENTS.PRESS END TO CONTINUE OR ENTER CANCEL TO CANCEL.000012 //*000012 //*000014 //*000015 //* ------------------DO NOT REMOVE JOBLIB STATEMENT BELOW!-----------000016 //*000017 //JOBLIB DD DISP=SHR,DSN=DAVID.DO000277.SCPPLOAD000018 //*****************************BOTTOM OF DATA *************************************

� �

Figure 25. CPPPEDIF Panel With Receive Job

Edit the job, if necessary, and save it. To submit the job, enter SUBMIT and then exit thedialog. The job loads your order from tape, a server, or file system to your DASD.

Notes:

1. The RECEIVE job must be submitted with REGION = 0M parameter on the jobcard.

2. You must exit the dialog for the RECEIVE job to run. It is not necessary log off fromTSO.

3. If the RECEIVE job fails, you must go into the CustomPac Installation Dialog panels toregenerate and re-run the RECEIVE job.



If you are downloading your order from a server, the entire download might takeconsiderable time. However, the download is done in two phases, and the first phase willusually not take very long. Once it has finished, you can begin to use the dialog to configureyour new order. The RECEIVE job will send you a message to tell you when the dialog isready to be used if you are logged on and have INTERCOM set in your TSO/E Profile. Tosee whether you have INTERCOM set, issue the PROFILE command from the TSO/EReady prompt or ISPF Option 6. To set INTERCOM, issue PROFILE INTERCOM.

Note: It is acceptable for some steps to "flush" if one of the following conditions applies:

• CHKVERSN receives an RC4 indicating that your master dialogs are currently at thesame level or higher than the order you are currently receiving.

• CHKINV receives an RC4 indicating that a new master dialog isare loaded with theLOADRIM job and there are no current orders stored in the dialog inventory.

If you want to save a copy of the job, you can use the ISPF Edit CREATE primarycommand to save the job in a data set (or data set member) of your choice.


Installing the New Order

Chapter 6. Installing the New Order

Before you install the order...

To avoid enqueue contention for dialog data sets, allow only one userid work with anorder at a time.

To begin installing the order, select option I on the Order Processing panel (Figure 6 onpage 29).

To go directly to a specific order, enter the order number in the blank field under"INSTALL" and press Enter. Processing proceeds directly to the Installation Menu for theorder (see “Installation Options Menu” on page 52).

If you leave the order number field blank and press Enter, the dialog displays a list of ordersfrom which to choose (see “Selecting an Order to Install”). Select an order to install andpress Enter.

Note: Although z/OS V1R10 or higher supports Extended Address Volumes (EAV), theServerPac Dialog does not support EAV in the configuration during installation.

Note:

Selecting an Order to InstallTo list all of the uninstalled orders, select the I option, but leave the order number fieldblank. The dialog displays a list of orders for your selection, as shown in Figure 26 onpage 49.

The order list will be shown in the same mode as when it was last displayed (TErse orVErbose).



� � CustomPac ------------------------ ORDER LIST ------------- ROW 1 TO 13 OF 13 COMMAND ==> SCROLL ==> PAGE

Primary Commands:(? SET Locate Find Next Previous OFile SORT VErbose VERsion)Line Commands:(Select Edit Delete Products Report Output)

--- Last Change -- S Order System Name SREL Package Build Date Status User Date - -------- ----------- ---- -------- ---------- --------- ------- ----------

MD000165 Z038 EXP 1997/05/26 Installed STOB6 1997/05/27MD000166 Z038 EXP 1997/06/30 Installed STOB6 1997/07/07MD000179 P004 HCHK 1997/09/22 Installed STOB6 1997/09/23

MD000181 SYS01 Z038 EXPDD 1997/10/01 Started STOB6 1997/10/14 MD000199 Z038 OMIS 1997/11/12 Installed STOB6 1997/11/17

MD000277 SIM4 MULT SERV 1997/11/13 Received STOB5 1997/11/15 ******************************* BOTTOM OF DATA *******************************

� �

TErse Mode

Figure 26. CPPP6071 - Install Orders - Order List

� � CustomPac ------------------------ ORDER LIST -------------- ROW 1 TO 5 OF 13 COMMAND ==> SCROLL ==> PAGE

Primary Commands:(? SET Locate Find Next Previous OFile SORT TErse VERsion)Line Commands:(Select Edit Delete Products Report Output)


Cust Num Cust Name Order Comment - -------- ----------- ---- -------- ---------- --------- ------- ----------

MD000165 Z038 EXP 1997/05/26 Installed STOB6 1997/05/2711997111 GLANDALE Install HBP for VS4 upgrade

- -------- ----------- ---- -------- ---------- --------- ------- ----------MD000166 Z038 EXP 1997/06/30 Installed STOB6 1997/07/0711997111 GLANDALE GRAFF 27

- -------- ----------- ---- -------- ---------- --------- ------- ----------MD000179 P004 HCHK 1997/09/22 Installed STOB6 1997/09/2311997111 GLANDALE Check RACF fixes

- -------- ----------- ---- -------- ---------- --------- ------- ----------MD000181 SYS01 Z038 EXPDD 1997/10/01 Started STOB6 1997/10/1411997111 GLANDALE Install VS5 CLONE

- -------- ----------- ---- -------- ---------- --------- ------- ----------MD000199 Z038 OMIS 1997/11/12 Installed STOB6 1997/11/1711997111 GLANDALE PDF 3.3 FIX FOR 0C4'S

- -------- ----------- ---- -------- ---------- --------- ------- ----------

� �

VErbose Mode

Figure 27. CPPP6072 - Install Orders - Order List

The Order Installation panel indicates installable orders with either of the following statuscodes (in the Status column):

Received This status is set when the order can be selected on the order list panel. Fororders delivered on tape, this is after the RECEIVE jobs has run. For ordersthat are downloaded, this is after the first phase of the download has beencompleted.

Chapter 6. Installing the New Order 49


Started This status is set when the work configuration has been created.

After you have installed an order and reset its status to Installed, you can no longer displaythe order with the I option (Install Orders) on the Order Processing panel. You can,however, still view the order s work configuration and installation jobs through the dialog byusing the O option (Display Orders) on the Order Processing panel (Figure 6 on page 29)and then selecting the desired order from the list. Or, if you use the GENSKEL commanddescribed in “Generate Installation Jobs (GENSKEL)” on page 202, you can view theorder's installation jobs in the data set for the order.

Select an order by entering an S line command before the desired order. In Figure 26 onpage 49, order number MD053718 has been selected. The following Primary Commandsare valid for this panel -

? SET Locate Find Next Previous SORT VErboseThese are standard CustomPac table handling commands.(See “The Primary Commands” on page 9)

OFILE This command may be abbreviated to OF

This command sends the list of orders to an external customer defined file.(ALL the orders in the list are sent, not just those displayed on the currentscreen).

(See “OFILE Command” on page 12).

VERSION This command may be abbreviated to VER.

The current version date of the Installation Dialog will be displayed.



S Select

This will start the installation procedure for the selected order.

E Edit

This will allow the status of an order to changed, other "documentary" typefields may also be changed.

(See “Editing an Order” on page 218).

D Delete

This will delete an order from the Order Inventory.

You will be prompted to confirm the delete request.

(See “Deleting an Order” on page 217).

P Products

This will display all the data for one order along with its products andFMIDs.

(See “Displaying Products/FMIDs for an Order” on page 220).

R Report

This will write all information associated with an order and its products to theISPF list data set or to a customer defined data set.



(See “Report Processing” on page 222).

O Output

This command is NOT valid for an order in receive status.

A list of the installation jobs, and job output for the order is displayed.

(See “Processing LOG” on page 204).

NOTE

In order for installation job output to be captured and to be available forthe Output command, the SYSOUT class used for the installation jobsmust be a HELD output class.

Furthermore, NO output will be available until the Installation DialogSelect and Submit Installation Jobs function has been started.



Installation Options Menu

When you select an order to install, the Installation Menu is displayed (Figure 28). Thispanel is the starting point for all of the functions that are needed to install your order.

� �CustomPac --------------- (C) IBM Corporation 1990-2000 -----------------------OPTION ==>

Complete these options to install the order:

C Create Create the Work Configuration V Variables Specify Values for Variables Z Zones Specify SMPTLIB and SMP/E Zone Names Information M Modify Modify the System Layout A Alias Specify Catalogs for High-Level Qualifiers

SSA SSA Specify Temporary Aliases (SSAs)for Catalogs I Installation Create and Submit Installation Jobs

(Option not available until download complete )

You can use Save any time after creating the work configuration:

S Save Save the Current Work Configuration

� �

Figure 28. CPPPFLOW - Installation Options Menu for SystemPac/FunctionPac

� � CustomPac --------------- (C) IBM Corporation 1990-2000 ----------------------- OPTION ==>


C Create Create the Work Configuration V Variables Specify Values for Variables

UC Update Update Configuration with Target Environment Data M Modify Modify the System Layout A Alias Specify Catalogs for High-Level Qualifiers

SSA SSA Specify Temporary Aliases (SSAs)for Catalogs I Installation Create and Submit Installation Jobs

(Option not available until download complete )



� �

Figure 29. CPPPFLOW - Installation Options Menu for ProductPac



� � CustomPac --------------- (C) IBM Corporation 1990-2000 ----------------------- OPTION ==>


C Create Create the Work Configuration V Variables Specify Values for Variables

UC Update Update Configuration with Target Environment DataSSA SSA Specify Temporary Aliases (SSAs)for Catalogs

I Installation Create and Submit Installation Jobs(Option not available until download complete )



� �

Figure 30. CPPPFLOW - Installation Options Menu for RefreshPac

NOT all installation options are applicable to all Pac types. Figure 28 on page 52 illustratesthe installation of a SystemPac or FunctionPac and Figure 29 on page 52 shows the menufor a ProductPac or RefreshPac.

A customised version of this panel is included with each order, showing only the optionsrequired to install your order.

C Create

Create the Work Configuration

Use this option to create a work configuration for the order you are installing.You can choose to merge the order's shipped configuration with aconfiguration that you saved from a previous order. The new order, togetherwith the saved configuration, if any, forms the work configuration that youmanipulate in subsequent functions of the dialog.

For operating system orders, you are prompted to choose an installationmethod (full system replacement or a software upgrade) and select a job entrysubsystem (JES) for the installation.

(For more information, see Chapter 7, “Creating a work Configuration forthe Order” on page 56).

V Variables

Specify Values for Variables

Installation of your order involves the generation and submission of batchjobs from the Installation Jobs dialog.

The JCL for the batch jobs is generated using shipped ISPF skeletons, whichrequire 'dialog variables' specific to the current order.

This dialog allows you to -

• Alter data values for NON customised variables.• Define your own USER variables.

(See Chapter 8, “Defining Installation Variables” on page 76).



Z Zones (For SystemPac and FunctionPac only)

Specify SMPTLIB and SMP/E Zone Names Information

This is only required for SystemPac (DD), ServerPac and FunctionPac.

Products and features delivered with your order are shipped using defaulttarget and DLIB zone names. The dialog allows you to define the target andDLIB zone names when installing your order. IBM recommends that you usedifferent zone names for each order. For more information, see Chapter 9,“Defining the SMP/E zone configuration” on page 88.

This dialog also provides the SMS and non-SMS managed volumes supportfor the SMPTLIB DDDEF definition.

IBM also recommends that you use different CSI data set names for eachorder. To change the names of the CSI data sets, use the Modify SystemLayout function (see Chapter 11, “Modify the System Layout” onpage 107).

UC UCpdate (For ProductPac and RefreshPac only)

Update Configuration with Target Environment Data

This is only required for ProductPac and RefreshPac.

Your order is built base on the CSI shipped. This option updates the targetenvironment information to prepare for the Modify System Layout option.

This dialog scans the target system catalog, as supplied from the variableoption, and updates the tables that is required by the next option.

Panels will be prompted for information not matching the shipped CSI and areport will be generated for actions required in order to continue with the nextoption.

(See Chapter 10, “Update Configuration with Target Environment Data” onpage 97).

M Modify

Modify the System Layout

This is only required for SystemPac (DD), ServerPac, FunctionPac andProductPac.

Shipped with your order is a CustomPac generated ISPF table, known as theLVT (Logical Volume Table).

This table contains a list of all the data sets needed for your ordered system.

Each data set entry in the table is known as a data set PROFILE. Thisdescribes the data set name, what kind of data set it is, where it resides andwhat space it needs.

This dialog assists in modifying the data set profiles so that they match yourcomputer centre's DASD plan.

data set profiles may be customised as a group (using GLOBAL CHANGEcommands) or individually.

(See Chapter 11, “Modify the System Layout” on page 107).

A Alias

Specify Catalogs for High-Level Qualifiers



This is only required for SystemPac (DD), ServerPac, FunctionPac andProductPac.

data sets shipped with your order are referenced by normal catalog searchprocedures. This means that there must be an alias in the master catalogpointing to the user catalog in which the data set will be cataloged.

This dialog defines the catalog data set names and the aliases associated withthem.

(See Chapter 12, “Defining Alias-to-Catalog Connections” on page 187).

SSA System Specific Alias

Specify Temporary Aliases(SSAs) for Catalogs

Many of the data sets in your new order also exist on the driving system. Tosimplify recovery during the installation, it is recommended that you enablethe installation jobs to allocate and access the target system's data sets withalternative high-level qualifiers (HLQs) temporarily. Use this function of thedialog to define these temporary HLQs for the target system data sets. Duringthe installation, your order's data sets are cataloged with the temporaryHLQs. To direct the catalog entries to the proper catalog, the temporaryHLQs are defined as aliases to the driving system's master catalog. Hence,these alternate HLQs are called "System-Specific Aliases" or SSAs. At theend of the installation, the installation jobs remove the SSAs, and rename thetarget system's data sets to their true names. For more information, (SeeChapter 13, “Defining SSA-to-Catalog Connections” on page 192).

I Install

Create and Submit Installation Jobs

The installation job stream shipped with your order consists of controlinformation stored in tables and customisable ISPF skeletons.

This dialog generates and manages execution of the job stream.

(See Chapter 14, “Submitting Installation Jobs” on page 198).

S Save

Save the Current Work Configuration

During the installation of your order you may have customised the shippedorder configuration -

• Merged it with a master and/or saved work configuration.• Changed data values for variables.• Added your own user variables.• Added your own installation jobs.

This dialog allows you to save the work configuration so that it may bemerged with future orders.

You may save the configuration as a saved work configuration, AFTERwhich it may also be saved as a master configuration.

(See Chapter 15, “Saving the Configuration” on page 211).


Creating a work Configuration for the Order

Chapter 7. Creating a work Configuration for the Order

Choosing the Installation type

For an operating system order, option Create displays the Type of Installation panel shownin Figure 31. For other orders, skip ahead to “Creating the Configuration” on page 59.

� � CustomPac ------------- CREATE Configuration ( MD000277 ) --------------------- OPTION ==>

Select the Install type

F - Full System Replacement installs a complete new IPL-ablestandalone system including all SMP/E maintained libraries, SMP/Eenvironment, Operational data sets and CustomPac sample data sets.The supplied operational data sets must be merged with or replacedby production operational data sets before the new system is usedin production.

S - Software Upgrade installs Only the SMP/E maintained libraries,SMP/E zones and CustomPac sample data sets. Operational data sets,including system control files (like LOGREC and VTAMLST), a securitysystem database, and a master catalog must already exist. Theseexisting operational data sets must be updated as required for newproducts and product changes before the first IPL.

For more information about Software Upgrade, enter ? in the option field

� �

Figure 31. CPPP6015 - Type of Installation

Use this panel to select the type of installation that you prefer, Full System Replace orSoftware Upgrade. Select the installation type by entering Full system replacement orSoftware upgrade in the OPTION ==> field and pressing enter.

A Full System Replace installs a complete z/OS system. It installs all data sets needed toIPL, log on to the target system, and run a z/OS image for completing other installation andcustomization tasks. These data sets fall into two major categories:

1. System software and related data sets (such as distribution and target libraries, SMP/ECSI data sets, and sample libraries)

2. Operational data sets (such as page data sets, system control files, and a master catalog).

Because IBM creates a working set of operational data sets for you, a full systemreplacement helps assure a successful first IPL.

Unless you are installing a new image, you must merge your existing operational data setswith the data sets created by ServerPac; this can be done before or after the first IPL.

A software upgrade installs only system software and related data sets (category 1 above).You must provide the operational data sets (category 2 above) and make them accessible tothe new level of software installed. When new operational data sets are required, you must



allocate and initialize them before you IPL. For example, you might need to add parametersrequired by the new software level, or change data sets so that they work with both the oldand new levels.

A software upgrade uses your existing catalog structure. This includes your existing mastercatalog and user catalogs (with direct or indirect cataloging references). Also, softwareupgrade allows you to create new user catalogs as part of the installation process.

If you select software upgrade or full system replacement and later wish to change theinstallation type, you must recreate the configuration by selecting Option C, specifying thedesired installation type, specifying the JES elements to be installed, selecting a savedconfiguration for merge (if applicable), and issuing the Create command. If you wish topreserve your modifications, save the configuration. Doing so can reduce the amount ofdata that you would need to re-enter, depending on how far along you are in the installationprocess.

Software Upgrade is available for z/OS orders. It is not available for the related subsystemproducts (DB2, CICS, IMS and NCP) or WebSphere Application Server.

Selecting a JES for the ConfigurationAfter you select a configuration for your z/OS order, the dialog displays the panel shown inFigure 32 to prompt you to select a JES element.

� �CPPP6016 ------------- JES Element Selection ( MD053718 ) --------------------

COMMAND ==>

Choose JES elements to be installed:

JES Elements to Install ==> (JES2, JES3, or BOTH)

Note: For more information, enter ? in the command field.

� �

Figure 32. Panel: JES Element Selection

Select at least one JES element for installation: JES2 (and SDSF) or JES3 (and SDSF). Ifyour installation requires both JES elements, select BOTH. After your selection, the panel isdisplayed with appropriate merge options.

The default of each merge option is "N." In the available merge options, you can onlyspecify one "Y." In other words, the merge options are mutually exclusive. If you specifymore than one "Y" you will receive message CPPO601008E. If you plan to migrate tosubsequent releases of JES2 or JES3 when you migrate to the next level of z/OS, it isrecommended that you merge the JES zones with the BCP zone.

If you select JES2, the following panel is displayed:

Chapter 7. Creating a work Configuration for the Order 57


� �CPPP6016 ------------- JES Element Selection ( MD053718 ) -------------COMMAND ==>


JES Elements to Install ==> JES2 (JES2, JES3, or BOTH)

Specify options for merging SMP/E target and DLIB zones:

Merge SDSF Zone into JES2 Zone ==> N (Y or N)

Merge SDSF/JES2 Zones into BCP Zone ==> N (Y or N)


� �

If you select JES3, the following panel is displayed:



JES Elements to Install ==> JES3 (JES2, JES3, or BOTH)




Note: For more information, enter ? in the command field.� �

If you select BOTH, the following panel is displayed:





JES Elements to Install ==> BOTH (JES2, JES3, or BOTH)






Merge SDSF/JES2/JES3 Zones into BCP Zone ==> N (Y or N)


� �

If you wish to change any of these decisions later, you must config again by selectingOption Create, specifying the desired changes, selecting a saved configuration for merge (ifapplicable), and issuing the CReate command.

Creating the ConfigurationAfter you select the JES Element (for a z/OS order) or select option C (for a subsystemorder), the Create Configuration panel is displayed, as shown in Figure 33.

� � CustomPac ------------ CREATE Configuration ( MD053718 ) ---- ROW 1 TO 3 OF 3 COMMAND ==> CR SCROLL ==> PAGE

Select Configuration

Primary Commands:(? SET Locate Find Next Previous SORT CReate)Line Commands:(Select)

S CONFiguration Comment - ----------------------------------- ---------------------------------------- * CPP.MD053718 Always Selected for Order - ----------------------------------- ---------------------------------------- S CPP.MD058475 First saved config

CPP.MD058476 Second saved config ******************************* BOTTOM OF DATA ********************************

� �

Figure 33. CPPP6011 - Select Configuration



The shipped configuration is always automatically selected. Any configurations you havesaved are also displayed. Selecting a saved configuration (if you have one) will reduce thetime needed to install the order.

If you are using the dialog for the first time, simply enter the CReate primary command.Later in the installation, you will be able to save this configuration for use with subsequentCustomPac orders, or to preserve your work if you decide to recreate the configuration tochange installation types or JES selections.

If you are merging this order with a saved configuration, see “Merging a configuration witha previous order” for further considerations.

When you create the work configuration, the message Work Configuration Created appears, as shown in Figure 34.

� � CustomPac ------------ CREATE Configuration ( MD053718 ) ---- ROW 1 TO 3 OF 3 COMMAND ==> CR SCROLL ==> PAGE

CPP0601004I WORK Configuration Created

Select Configuration

Primary Commands:(? SET Locate Find Next Previous SORT CReate)Line Commands:(Select)

S CONFiguration Comment - ----------------------------------- ---------------------------------------- * CPP.MD053718 Always Selected for Order - ----------------------------------- ---------------------------------------- S CPP.MD058475 First saved config

CPP.MD058476 Second saved config ******************************* BOTTOM OF DATA ********************************

� �

Figure 34. CPPP6011 - Select configuration (configuration created)

Press the END key to return to the dialog's Main Menu.

Merging a configuration with a previous orderAt this stage of installing your order, you can reuse any configuration information you mighthave customized and saved from previous orders. To do so, you merge the new order withthe saved information. Wherever possible, saved data set attributes replace shippedattributes. New jobs are generated based on the resulting attributes and on furthercustomization that you will do in the dialog. Data set types (PDS, PDSE, HFS or zFS) arederived from the saved order when those data sets are present in both the savedconfiguration and the new configuration and they are flagged as switchable in the new order.

You can merge a saved configuration with the order's shipped configuration. Selection of thesaved configuration selection is restricted to configurations created in your current dialogrelease or up to three prior releases. For example if your shipped configuration was created



in Dialog Level 18, you can not merge this with a saved configuration from Dialog Level14.

You select configurations to be merged with the new order configuration on the CreateConfiguration panel. Enter line command S for each configuration that you want to mergewith the current order, and enter CR on the command line to create the new configuration.Figure 35 shows the panel that is displayed.

� � CustomPac ------------- CREATE Configuration ( MD000277 ) --------------------- COMMAND ==>

``````````````````````````````````````````````````````````````````` `````` ORDER : ZF85900.MD000277 `````` `````` The following configurations will be MERGED with the `````` Shipped Order Configuration `````` `````` CONFIG : ZF85900.MD000166.CONFIG `````` `````` REPORT : ZF85900.MD000277.REPORT `````` (data set merge report) `````` ```````````````````````````````````````````````````````````````````

`` You MUST Confirm the MERGE By Typing MERGE and pressing ENTER

`` Press the END or RETURN key to CANCEL the MERGE request

� �

Figure 35. CPPP6013 - MERGE Configurations - Confirmation

If you are installing a z/OS V2R1 or later order and the selected saved configuration doesnot contain the RACFTGT job, then the CREATE Configuration (CPPP6013) panel displaysan additional text as shown in Figure 36 on page 62. Job RACFDLTA uses savedconfiguration data sets to generate the job. The job will not be generated if the configurationof the order being installed is not merged with a saved configuration or is merged with asaved configuration which does not contain the RACFTGT job. It is recommended that youselect a saved configuration of the same SREL as the order being installed for the merge.SREL details can be found on the ORDER LIST panel.




``````````````````````````````````````````````````````````````````` `````` ORDER : ZF85900.MD000277 `````` `````` The following configurations will be MERGED with the `````` Shipped Order Configuration `````` `````` CONFIG : ZF85900.MD000166.CONFIG `````` `````` REPORT : ZF85900.MD000277.REPORT `````` (data set merge report) `````` `````` THE SELECTED SAVED CONFIGURATION DOES NOT CONTAIN `````` JOB RACFTGT. THEREFORE JOB RACFDLTA WILL NOT BE `````` GENERATED FOR THIS ORDER. `````` ```````````````````````````````````````````````````````````````````

`` You MUST Confirm the MERGE By Typing MERGE and pressing ENTER

`` Press the END or RETURN key to CANCEL the MERGE request

� �

Figure 36. CPPP6013 - MERGE Configurations - Confirmation

To confirm the merge, enter MERGE in the COMMAND ==> field and press Enter.

If the dialog detects an existing work configuration for the current order, the panel shown inFigure 35 on page 61 will not appear until you delete the existing work configuration.Instead, the panel shown in Figure 37 is displayed to request that you delete the existingconfiguration.


DELETE an EXISTING Configuration

````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````` `````````` A configuration for this order already exists `````````` `````

````` If you continue this will be DELETED ````` ````` `````

````` You will lose ALL modifications you have made `````````` `````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````



� �

Figure 37. CPPP6012 - DELETE an EXISTING Configuration - Confirmation



To confirm the deletion, enter DELETE in the COMMAND ==> field and press Enter. Afteryou have deleted the existing configuration, the panel shown in Figure 35 on page 61 willbe displayed as previously described.

Modify the configuration as required, and save it. For subsequent installations, you canmerge a new shipped configuration with the one you save after making changes to thisconfiguration or with a configuration you saved from another installation.

User-defined jobs will retain the sequence if the working configuration is merged with R13or post-R13 saved configurations.

Information Used by CustomPac When Merging ConfigurationsWhen you create a configuration for your new order, the dialog allows you to reuseinformation that you saved from a previously installed order. Here, the dialog merges theinformation from the saved configuration with the information in the new order.

If a previously-installed product is in the new order at a new level and it now includes a newdata set, then there is nothing to bring forward and the new data set gets the shipped defaultsin the work configuration. Likewise, if a data set is not present in the product's new release,it is not carried forward from the saved configuration to the work configuration.

If your new order adds a product that was not in the previously installed order, the dialogadds the information about the product and its data sets from the new order to theconfiguration being created. If your new order omits a product that was included in apreviously saved order, the dialog does not carry forward information or data sets for theomitted product in the new configuration.

Thus, if WebSphere for z/OS (for example) was included in the previously installed order,but is not included in the new order, the dialog does not include WebSphere data in theconfiguration being created. As a result, your changes for WebSphere (such as data setnames or space) are not applied to the configuration for the new order, nor is the data forWebSphere saved when you save the configuration.

Another consideration for merging data exists when attributes of a data set are changedbetween levels of a product. Saved changes to allocation amounts (primary, secondary, anddirectory) are carried forward using the same increase amounts as were applied to the datasets in the saved configuration, except when secondary allocation amounts were allowed fora data set in the saved configuration, but are not allowed for that data set in the shippedconfiguration. For example, assume that data set A in the previously saved configuration had15 secondary blocks and you increased that amount to 20. Data set A in the new release ofthe product shipped with the new order has secondary blocks of 30. The secondary blocksvalue for data set A in the configuration being created is set to 35 (an increase of 5, just asbefore). On the other hand, if data set A in the new order had secondary blocks of 0; thesecondary blocks value for data set A in the configuration being created would be set to 0and any previous increase amount would be ignored.

When you merge the data sets into the new order, the dialog checks the previously savedconfiguration for user-defined data sets. The dialog adds these data sets to the configurationbeing created if their names do not conflict with any data set names in the new shippedorder. Otherwise, the dialog indicates the existence of data set name conflicts in the MergeReport (see “Merge Report” on page 67).

During merge configuration processing, the dialog first determines whether a data set will beincluded in the work configuration. If so, the dialog determines what information about the



data set will be included in the work configuration from the previously saved configuration,as follows :

• If, in the previously saved configuration, you did not change the particular data value(Eg. space value, logical volume) from the value that was originally shipped, then thedialog uses the new shipped value in the work configuration being created.

• If you have changed the data value in the previously saved configuration from the valuethat was originally shipped, the dialog uses the rules in Figure 38 to determine whichvalue is to be used in the work configuration being created.



Figure 38. Which Values are Used in a Merged Configuration

Data Set Value Dialog Action

Data Set Name If the data set exists in both the previously saved configuration and the new shipped order, the dialog uses the data setname from the previously saved configuration, unless the data set is marked unrenameable in the shipped configuration.

A merged data set (described in “Merging and Unmerging Data Sets” on page 150) retains its name. However, if acomponent data set in the merged data set does not appear in the new shipped order, the dialog automatically removes thecomponent data set from the merged data set and updates the attributes and space of the merged data set based on theremoval of the component data set.

Renameable This sttribute is not saved or merged. If you changed the status of some data sets from not renameable to overridden inthe saved configuration, and want to rename them again, you must change their status using the CHANGE RENAMEcommand (“Making Unrenameable Data Sets Renameable” on page 141) and then rename them in each order. If thedata set exists in both the previously saved configuration and the new shipped order, the dialog uses the data set namefrom the previously saved configuration.

DSORG If the data set's organization (DSORG) in the previously saved configuration is different from its DSORG in the newshipped configuration, the dialog uses the DSORG from the new shipped configuration for the data set.

For a merged data set, if the DSORG of a component data set changes from DSORG=PO, the dialog removes thecomponent data set from the merged data set. The dialog automatically updates the attributes and space of merged dataset based on the removal of the component data set.

RECFM If the record format (RECFM) of the data set in the previously saved configuration is different from the RECFM in thenew shipped configuration, the dialog uses the RECFM from the new shipped configuration.

For a merged data set, if the RECFM of a component data set no longer matches that of the merged data set, the dialogremoves the component data set from the merged data set. The dialog automatically updates the attributes and space ofmerged data set based on the removal of the component data set. In this case, the component dat set's RECFM andallocation amounts are set from the new shipped configuration.

LRECL If the logical record length (LRECL) in the previously saved configuration is different from its LRECL in the newshipped configuration, the dialog uses the LRECL from the new shipped order configuration.

For a merged data set, if the LRECL of a component data set no longer matches that of the merged data set, the dialogremoves the component data set from the merged data set. The dialog automatically updates the attributes and space forthe merged data set based on the removal of the component data set. In this case, the component dat set's allocationamounts are set from the new shipped configuration.

Primary Space The dialog uses one of the following values:

• The primary allocation amount from the new shipped configuration plus the amount of space that was added to theold shipped configuration in the saved configuration.

• If no saved configuration is being merged, the primary allocation amount from the new shipped configuration.

Secondary Space If the value in either the previously saved configuration or the new shipped order value is 0 (zero), the dialog uses a valueof 0 for the configuration being created. A value of 0 means that no secondary space allocation is allowed. When a dataset shipped with no secondary allocation has been overridden using the CHANGE SECOND command, the value storedin the saved configuration will reflect the shipped value (0) not the overridden value.

Otherwise, the dialog uses one of the following values:

• The secondary allocation amount from the new shipped configuration plus the amount of space that was added to theold shipped configuration in the saved configuration.

• If no saved configuration is being merged, the secondary allocation amount from the new shipped configuration.

Directory Blocks The dialog uses one of the following values:

• The number of directory blocks from the new shipped configuration plus the number of directory blocks that wasadded to the old shipped configuration in the saved configuration.

• If no saved configuration is being merged, the number of directory blocks in the new shipped configuration.

Logical Volume The dialog uses the logical volume name from the previously saved configuration for the data set, unless the logicalvolume name in the new shipped default configuration is IPLVOL.

If the dialog uses the Logical Volume name from the previously saved configuration, the dialog also updates thefollowing fields:

• Physical Volume value• Physical Volume Control Unit Address value. This is the device number for the volume, as assigned through the

hardware configuration definition (HCD).• Physical Volume Device Type

For a merged data set, if the logical volume of a component data set in the new release becomes IPLVOL, the dialogautomatically reassigns the logical volume of the merged data set to IPLVOL accordingly.

SMS-Managed The dialog uses the SMS-managed status from the saved configuration, unless doing so would conflict with the data set'sSMS-eligible or SMS-required attributes.



Using Merge Configuration ReportsTo aid you in identifying what information has been merged, the dialog generates threedifferent types of reports when you create the merged configuration:

• “Summary Report”• “Merge Report” on page 67• “Data Set Merge Report” on page 73

Summary ReportOne report, which is called the Summary Report, summarises the data in the tables thatwere merged from a previously saved configuration and the new shipped orderconfiguration. The dialog displays the Summary Report on your screen at the end of mergeprocessing.

� � CustomPac ------------- CREATE Configuration ( MD000277 ) ROW 237 TO 265 OF 250 COMMAND ==> SCROLL ==> HALF

Configuration Profile

Primary Commands:(? Find Next Previous SAVE)

------------------------------------------------------------------------------ ****************************************************************************** * MERGE DEVICE TYPE TABLE * * * * SOURCE (CPPTENUM) * ******************************************************************************

DEVICE NAME(STGTEK ) TYPE(3390 ) ADDED

****************************************************************************** * MERGE INSTALLATION JOBS * * * * SOURCE (CPPTENUC) * ******************************************************************************

COPY JOB($DEREK ) OK

****************************************************************************** * SAVE CONFIGURATION * ******************************************************************************

TABLE(NEWA2CD) SAVED - ALIAS TO CATALOG RELATIONSHIPS TABLE(NEWCD2S) SAVED - CATALOG TO SMS RELATIONSHIPS TABLE(NEWDEVT) SAVED - DEVICE TYPES TABLE(NEWFTBL) SAVED - INSTALLATION FLOW TABLE(NEWITBL) SAVED - INSTALLATION JOBS TABLE(NEWLTBL) SAVED - LOGICAL VOLUME DATA TABLE(NEWPTBL) SAVED - PHYSICAL VOLUMES TABLE(NEWVTBL) SAVED - INSTALLATION VARIABLES TABLE(NEWXTBL) SAVED - EXTRA DDDEFS TABLE TABLE(NEWZTBL) SAVED - ZONE CONFIGURATION TABLE

******************************* BOTTOM OF DATA ********************************

� �

Figure 39. CPPP6014 - Configuration Profile

The following Primary Commands are valid for this panel -

?, F, N, P These are standard CustomPac table handling commands.(See Chapter 2, “Understanding The Dialog” on page 7)

SAVE Saves the displayed Summary Report to a data set.



You can save the Summary Report to a data set by entering the SAVE primary command onthe Summary Report panel command line. The SAVE command saves the report in a dataset with the following naming convention -

OrderHLQ.LOG

EG. GLANDALE.MD000277.LOG

Merge ReportThe dialog also generates a second type of report, which is called the Merged Report,which identifies in tabular format the changes that were made to the Logical Volume Tableas a consequence of the merge. The report is saved in a data set with the following namingconvention -

OrderHLQ.REPORT(MERGE)

EG. GLANDALE.MD000277.REPORT(MERGE)

Use this report to discover potential problems with the merge. These are identified in theSTATUS column of the report. You are strongly recommended to investigate each row inthe report that contains a non-blank status.

Each column in the report is separated by one blank, the report displays information in thefollowing order -

1. Shipped SST, in alphabetical order.

2. Low-Level qualifier (LLQ) of the saved data set, in alphabetical order.

3. High-Level qualifier (HLQ) and any middle level qualifier(s) of the saved data set, inalphabetical order.

The fields in the report are described as follows -

SST Subsystem name. This field is blank for operational and CustomPac data sets. Forproduct-supplied data sets, it indicates the major system or subsystem with which thedata set is associated.(DB2, CICS, IMS, MVS or NCP)

STATUSThis is the status field, and has a maximum length of 11 characters.

NEWThe data set is a new data set. This means the data set did not exist in thepreviously saved configuration, but exists in the shipped order configuration.When a data set with a status of NEW is reported, only the the Saved LVolfield is not supplied, the rest of the fields are populated with data values for thedata set from the shipped order configuration.

As the report is sorted using the Saved Data Set Name, the Saved Data SetName value is set to the Shipped Data Set Name value, preventing it frombeing shown as a blank.

DSORGThere is a DSORG conflict between the new shipped order configuration andthe same data set in the previously saved configuration.

As the report is sorted using the Saved Data Set Name, the Saved Data SetName value is set to the Shipped Data Set Name value, preventing it frombeing shown as a blank.



LRECLThere is an LRECL conflict between the new shipped order configuration andthe same data set in the previously saved configuration. The data set spaceallocations are not merged, but any data set name, logical volume name andphysical attributes (volser, address and device type) are merge candidates.

RECFMThere is a RECFM conflict between the new shipped order configuration andthe same data set in the previously saved configuration. The data set spaceallocations are not merged, but any data set name, logical volume name andphysical attributes (volser, address and device type) are merge candidates.

D The data set mode has been changed, the new shipped order configurationorder mode is used. The data set mode indicates the installation type for whichthe data set is to be used (Full System Upgrade, Software Upgrade, or both).

There are 3 possible causes for this status -

• The data set in the previously saved configuration is required for SoftwareUpgrade only, and the data set in the new shipped order configuration isrequired only for Full System Replacement, or it is required for bothSoftware Upgrade and Full System Replacement.

• The data set in the previously saved configuration is required for Fullsystem Upgrade only, and the data set in the new shipped orderconfiguration is required only for Software Upgrade, or it is required forboth Software Upgrade and Full System Replacement.

• The data set in the previously saved configuration is required for bothSoftware Upgrade and Full System Replacement, and the data set in thenew shipped order configuration is required for Software Upgrade only, orfor Full System Replacement only.

DSNAMEThere is a data set name conflict between the new shipped order configurationand the same data set in the previously saved configuration.


• When a user added data set in the previously saved configuration has thesame name as an IBM data set in the new shipped order configuration.

• When a data set in the previously saved configuration has been renamed,and a data set in the new shipped order configuration is now shipped withthat name.

In either case, no data set information is merged. The Saved Data Set Namevalue contains the name of the data set with the conflict. The Shipped DataSet Name value will be one of the following -

• 'USER DATA SET' for user added data set name conflicts.• 'IBM DATA SET' for renamed data set name conflicts.

Also, for each DSNAME conflict for data sets flagged as 'IBM DATA SET',there is also an entry in the report with a status of NEW.

I There is an IPLVOL conflict between the new shipped order configuration andthe same data set in the previously saved configuration.




• The data set in the previously saved configuration was required to be onIPLVOL, but the same data set in the new shipped order configuration isnot required to be on IPLVOL.

• The data set in the previously saved configuration was not required to beon IPLVOL, but the same data set in the new shipped order configurationis required to be on IPLVOL.

M There is change to the data set requirement of being in the master catalog.


• The data set in the previously saved configuration was required to be inthe master catalog and the same data set in the new shipped orderconfiguration is not required to be in the master catalog.

• The data set in the previously saved configuration was not required to bein the master catalog, but the same dataset in the new shipped orderconfiguration is required to be in the master catalog.

R There is a reblock flag conflict between the new shipped order and the samedata set in the saved order configuration. There are two possible ways thisstatus can be set:

• The data set in the saved configuration was allowed to be reblocked (theREBLOCK ALLOWED flag is set to Y), but the same data set in the newshipped order cannot be reblocked (the REBLOCK ALLOWED flag isset to N).

• The data set in the saved configuration was not allowed to be reblocked(the REBLOCK ALLOWED flag is set to N), but the same data set in thenew shipped order can be reblocked (the REBLOCK ALLOWED flag isset to Y).

S There is a secondary blocks conflict between the new shipped orderconfiguration and the same data set in the previously saved configuration.


• The data set in the previously saved configuration was allowed to havesecondary blocks, but the same data set in the new shipped orderconfiguration cannot have secondary blocks.

• The data set in the previously saved configuration was not allowed tohave secondary blocks, but the same data set in the new shipped orderconfiguration can have secondary blocks.

T There was a type conflict between a data set in the new shipped order and thesame data set in the saved order configuration. Either of following occurred:

• The data set in the saved order configuration is a PDS, but the same dataset in the new shipped order is a PDSE.

• The data set in the saved order configuration is a PDSE, but the same dataset in the new shipped order is a PDS.

In these cases, the dialog uses the format of the data set from the savedconfiguration, unless the data set in the new shipped order is not eligible tohave its format converted.

SMSThere was a conflict in the SMS status of the data set between the savedconfiguration and the shipped configuration. The data set is either of thefollowing:



Managed by SMS in the saved configuration, but is not eligible for SMS management in the shipped configuration.

Unmanaged by SMS in the saved configuration, but is required to be SMS-managed in the shipped configuration.

The data set's SMS status in the shipped configuration is unchange.

The dialog attempts to merge the remaining attributes of the data set.

X The data set was moved across SSTs between the previously saved orderconfiguration and the new shipped order configuration. This status can be setwhen a data set in the previously saved configuration was associated with oneSST and the same data set in the new shipped order configuration is associatedwith a different SST.

Notes on the Status field

1. Any combination of single character status values may appear at one time in thestatus field for the same entry. If more than one status value is shown it isseparated from the previous status value by a single comma.

2. The DSNAME and DSORG status values indicate that no merge of any values isdone.

3. The LRECL and RECFM values allow the merge of only the data set name,logical volume and physical attributes (volser, address and device type), where amerge value applies.

4. Any non-blank value in the table indicates the user should look closely at thedata set to ensure that any merged values are still valid. Also the followingshould be reviewed -

• Data set name• Reblocking of the data set• Logical volume to physical volume mapping• Data set blocksize• Data set space attributes, primary, secondary, directory blocks

5. A blank value indicates that no potential conflicts were identified during mergeof the values for the data set.

SAVED DATA SET NAMESpecifies the data set name that now exists in the new work configuration createdwhen the previously saved configuration was merged with the new shipped orderconfiguration.

This field is always non-blank because it is used as one of the primary sort fields forthe report. There are cases where the Saved Data Set Name value and the ShippedData Set Name value will be the same -

• The status is set to NEW or DSORG

• The previously saved configuration data set name and the new shipped orderconfiguration data set name are the same.

Note: For a status of DSNAME, the Saved Data Set Name is the name of the dataset and the Shipped Data Set Name is 'USER DATA SET'.



SHIPPED DATA SET NAMESpecifies one of the following -

• The name of the data set in the new shipped order configuration.

• 'USER DATA SET', a user added data set was copied from the previously savedconfiguration and added to the new work configuration. This value is alsoshown when a user added data set cannot be merged because of a data set nameconflict (status is DSNAME).

• 'IBM DATA SET', a data set was renamed in the previously savedconfiguration, and a data set of the same name is now part of the new shippedorder configuration.

SVLVOLSpecified the Logical Volume from the previously saved configuration.

If this value is non-blank it is the value that is used for the new work configuration.If the value is blank, one or both of the following is true -

• The Saved LVol is the same as the Shipped LVol• The status is set to NEW, DSNAME or DSORG

SHLVOLSpecifies the Logical Volume from the new shipped order configuration.

This value is blank when the logical volume in the previously saved configurationhas the same value as the logical volume in the new shipped order configuration.

SHPVOLSpecifies the physical volume that exists in the merged configuration (the new workconfiguration) for this data set.

SHPVOL is blank when the value of the physical volume in the previously savedorder configuration is the same as the value of the physical volume in the newshipped order configuration. If the status is set to NEW, then this is a new data setand the value will be populated from the new shipped order configuration.

DEVNSpecifies the device number of the physical volume taht is displayed in the PhysicalVolume column, or 'SMS' for an SMS-managed data set. This value is 1-4characters. If the Physical Volume colume is blank, this field is also blank.

ED Specifies whether data already exists on the physical volume shown in the SHPVOLfield. If the SHPVOL field is blank, then this field is also blank, else this field willhave a value of "Y" or "N".

DEVICESpecifies the device characteristics of the physical volume shown in the SHPVOLfield. If the SHPVOL field is blank, then this field is also blank.

PRIMSP(delta)Specifies the primary allocation value of the dat set in the merged configuration ifthere was a difference between the value in the saved order configuration and thenew shipped configuration for this data set. delta is the difference between theseprimary allocations, if any. delta is 1-12 characters.

The value is blank if you did not change the value of the primary allocation in thesaved order configuration, regardless of the value in the new shipped order.However, if you increased the the value of the primary allocation in the saved order,one of the following occurs:



• If the value in the new shipped order is less than the value in the saved orderconfiguration, the saved order configuration value is used and this is the valuedisplayed in the Saved Primary field.

• If the value in the new shipped order is greater than the value in the saved orderconfiguration, the amount of increase that the user specified in the saved orderconfiguration is added to the new shipped order value. This new value is thevalue displayed in the Saved Primary field.

There are two ways in which you could have changed the primary allocation:

• You entered the CHANGE command to change the primary allocation of one ormore data sets in the saved order configuration.

• You changed a specific data set's primary allocation.

SECSP(delta)Specifies the secondary allocation value of the data set in the merged configuration ifthere was a difference between the value in the saved order configuration and thenew shipped configuration for this data set. delta is the difference between the savedorder configuration secondary allocation and the new shipped order. delta is 1-12characters.

If you did not change the value of the secondary allocation in the saved orderconfiguration, delta is blank, regardless of the value in the new shipped order. Ifyou changed the the value of the secondary allocation in the saved order, one of thefollowing occurs:

• If the value in the new shipped order is less than the value in the saved orderconfiguration, the dialog uses the saved order configuration value and displaysthis value shown in the Saved Secondary field.

• If the value in the new shipped order is greater than the value in the saved orderconfiguration, the dialog adds the amount of increase that you specified in thesaved order configuration to the new shipped order value. The dialog displaysthe new value in the Saved Secondary field.

• If the value if either the new shipped order or the saved order configuration iszero, the dialog displays a zero(0) in the Saved Secondary field, and an "S" inthe status field.

There are two ways in which you could have changed the secondary allocation:

• You entered the CHANGE command to change the secondary allocation of oneor more data sets in the saved order configuration.

• You changed a specific data set's secondary allocation.

DIRB(delta)If there was a difference in the directory blocks between the previously savedconfiguration and the new shipped order configuration, then this field shows thedifference between the directory blocks values.

If this field is blank then you did not change the value of the directory blocks in thepreviously saved configuration, regardless of the directory blocks in the new shippedorder configuration. However if you increased the the value of the directory blocksin the previously saved configuration, one of the following occurs -

• If the value in the new shipped order configuration is less than the value in thepreviously saved configuration, the previously saved configuration value isused, and this is the value shown in the Saved Dirblks field.



• If the value in the new shipped order configuration is greater than the value inthe previously saved configuration, the amount of increase that the userspecified is added to the new shipped order configuration value. This new valueis is shown in the Saved Dirblks field.

There are 2 ways you could have changed the directory blocks value -

• You used the global change command on the previously saved configuration tochange the directory blocks value for a group of data sets.

• You changed the directory blocks value for a specific data set.

Data Set Merge ReportThe dialog generates the Data Set Merge report to show possible conflicts involving mergeddata sets as a result of merging of the saved configuration with the new configuration. Usethis report to discover potential problems, which are identified in the STATUS column ofthe report. It is strongly recommended that you investigate any data sets that have anon-blank status in the reports.

The dialog saves this report in a member name DSMERGE in a data set with the followingconvention:

OrderHLQ.REPORT(DSMERGE)

EG. GLANDALE.MD000277.REPORT(MERGE)

The following is an example of the report:

� �STATUS Merged DSname Component DSname RECFM LRECL DSTYPE AVBLOCK PRI SEC DIR C IU SYS1.PANELS FB 80 PDS 8800 75 7 50 Y NA,I SYS1.PANELS N N

GIM.SGIMPENU N NISP.SISPPENU N N

D ABC.SABCPENU Y NDEF.SDEFPENU Y N

P SYS1.CLIST FB 80 PDSE 8800 60 10 40 Y N SYS1.CLIST Y N GIM.SGIMCLS0 Y N ABC.SABCCENU Y N A SYS1.MSGS FB 80 PDS 17200 60 10 40 Y N SYS1.MSGS Y N GIM.SGIMMENU Y N ABC.SABCMENU Y N U SYS1.SKELS FB 80 PDS 17200 60 10 40 Y N C SYS1.SKELS Y N GIM.SGIMSENU Y N ISP.SISPSENU Y N

� �

Figure 40. Data Set Merge Report

The fields in the report are described as follows:

Status Identifies potential problems, such as data set name conflicts. Valid valuesfor this fields are as follows:

U Data set was unmerged as a result of the configuration merge.

A One or more of the data sets flags (shown in the right-most columns inthis report) have changed as a result of the merge. Each flag is markedwith a value of Y or N ('yes' or 'no') to indicate the post-mergeconditions for the data set, as follows:



C Must the data set be cataloged in the Master Catalog?

I Must the data set reside on the IPL volume?

N Can the data set be renamed?

M Can the data set be merged with another data set?

D Can the data set's type (HFS, PDS, PDSE, zFS) be changed?

S Must the data set be managed by SMS?

E Can the data set be managed by SMS?

The operating system requires some data sets to have particular names,or reside on the IPL volume, or be cataloged in the master catalog.ServerPac sometimes requires that additional data sets follow theserestrictions. During the installation, you can choose to make these datasets renameable through the CHANGE RENAME command. Or, youcan rename, move, or recatalog these data sets after completing theCustomPac installation.

C Data set was automatically unmerged of all of its component data setsbecause the dialog detected a member name conflict between it andanother data set (which is also indicated with a C status elsewhere in thisreport).

D Data set was not in the shipped configuration. The data set is deleted. Ifit was part a merged data set, then it was either a merge component dataset (that is, it was merged into another data set) or a merge target dataset (that is, other data sets were merged into it). If it was a mergecomponent, it is no longer part of the merged data set. However, if itwas a merge target, then the dialog unmerges the data sets. If you wantthe data sets merged agin, you will have to choose a different mergetarget data set.

I Data set is ineligible for merging. This status is accompanied with astatus of A to indicate that the merge attribute of the data set haschanged to N.

P The merged data set is a PDSE, but it contains at least one componentdata set that is a non-switchable PDS.

Merged DSnameNamd of the merged data set.

Component DSnameName of a component data set in the merged data set. The first value in thislist is the name of the component targe merge data set.

LRECL Logical record size of the merged data set. This value is the same for allcomponent data sets within the merged data set.

DSTYPE Data set organization of the merged data set. Possible values are PDS andPDSE. This value is the same for all component data sets in the merged dataset.

AVBLOCK Space units of the merged data set. This value is the same for all componentdata sets in the merged data set.

PRI Primary space allocation for the merged data set, including the space requiredfor its component data sets.



SEC Secondary space allocation for the merged data set, including the spacerequired for its component data sets.

DIR Number of directory blocks required for the merged data set, including thespace required for its component data sets.

Note: For z/OS orders, the MERGE report shows both JES2 and JES3 data sets whether ornot they are present in the configuration. If they appear incorrectly in the MERGE report,ignore them.


Defining Installation Variables

Chapter 8. Defining Installation Variables

Installation of your order involves the generation and submission of batch jobs from theInstallation Jobs Dialog.

The JCL for the batch jobs is generated using shipped ISPF skeletons, which require 'dialogvariables' specific to the current order.

The Installation Variables Dialog allows you to -

• Alter data values for NON Customised variables

• Define your own USER variables

Variable Selection List

This panel shows the variables for your order.

� � CustomPac ------------ Installation Variables ( MD000277 ) - ROW 1 TO 14 OF 75 COMMAND ==> SCROLL ==> PAGE

Variable Selection List SHOW( * )

Primary Commands:(? SET Locate Find Next Previous CANcel SAVE SHow VARname)Line Commands:(Browse Delete Edit Insert Repeat Ship)

S Synonym STA Contents- --- ----------------- --- ----+----0----+----0----+----0----+----0----==> INSTALL OPTIONS

DYNAMIC DASD INFO P YES

==> GEN SYSTEMPACWORK UNIT D SYSDATGT UNIT TYPE DTARGET VOLSER DASSEMBLER NAME D ASMA90

==> HFS/zFS InfoINSTALL DIRECTORY D /Service

==> MVS NEW ADRSADMP CONSOLE D 0F2

==> MVS NEW MISCTIMEZONE OFFSET P W.05.00.00SMF IDENTIFIER D MVS1SYSNAME D CPACSYSPLEX D LOCALSYSTEM LOGGER HLQ D IXGLOGR

� �

Figure 41. CPPP6111 - Variable Selection List - Variable Synonym



� � CustomPac ------------ Installation Variables ( MD000277 ) - ROW 1 TO 14 OF 75 COMMAND ==> SCROLL ==> PAGE

Variable Selection List SHOW( * )

Primary Commands:(? SET Locate Find Next Previous CANcel SAVE SHow VARname)Line Commands:(Browse Delete Edit Insert Repeat Ship)

S Synonym STA Contents- --- ----------------- --- ----+----0----+----0----+----0----+----0----==> INSTALL OPTIONS

FADAXX01 P YES

==> GEN SYSTEMPACFA0GUX00 D SYSDAFA0GUN00 DFA0GVN00 DFA0NDD15 D ASMA90

==> HFS/zFS InfoFA00PQ04 D /Service

==> MVS NEW ADRF00NAI06 D 0F2

==> MVS NEW MISCF00NXX04 P W.05.00.00F00NXX05 D MVS1F00NXX06 D CPACF00NXX17 D LOCALF00NXX18 D IXGLOGR

� �

Figure 42. CPPP6112 - Variable Selection List - Variable Name

The display will be shown in the last selected format (VARname or SYNonym as the majorfield)

If the variable is NOT customised then you may overtype the Contents field, this willchange the current data value for the variable.

If you choose to change the data value using this method then, do NOT at the same timeissue a line command against the table row.


?, SET, F, L, N, PThese are standard CustomPac table handling commands.(See Chapter 2, “Understanding The Dialog” on page 7)

CANCEL This command may be abbreviated to CAN.

This command forgets any changes made since the last checkpoint and exitsthe Installation Variables dialog.

(A checkpoint is taken on entry and exit to the dialog and after any SAVEcommand).

SAVE This command saves any changes that you have made and establishes a newcheckpoint.

(A checkpoint is taken on entry and exit to the dialog and after any SAVEcommand).

Chapter 8. Defining Installation Variables 77


SHOW This command may be abbreviated to SH.

A list of variable status codes may be supplied to limit the display to onlyvariables that satisfy those codes.

Valid codes are -

Q ALL VariablesC CustomisedD DefaultE ErasedI InsertedP Pre-DefinedU User Defined

The list of status codes may be prefixed by a ¬ (logical NOT operator) tolimit the display to only variables with status codes that are NOT one of thosein the list.

Examples

COMMAND ==> SH CP

• Display only variables with a status code of

C (Customised) ORP (Pre-Defined)

COMMAND ==> SH ¬CP

• Display only variables with a status code that is NOT

C (Customised) ANDP (Pre-Defined)

SYNONYM This command may be abbreviated to SYN

The display is re-built showing the variable SYNONYM as the major field.

(See Figure 41 on page 76).

VARNAME This command may be abbreviated to VAR

The display is re-built showing the variable NAME as the major field.

(See Figure 41 on page 76).


B Browse

Displays all information for the selected variable, including -

• Variable Name• Full Status• Default Data Value• Current Data Value• Variable Description

(See “BROWSE Variable Definition” on page 81)

D Delete

DELETEs a USER variable.



You will be required to confirm your DELETE request.

(See “DELETE a USER Variable” on page 82)

NOTE

You will NOT be allowed to delete CustomPac shipped variables

E Edit

Allows the following fields to be updated -

• Current Data Value• Variable Description

(See “EDIT Variable Definition” on page 83)

NOTE

Variables with a status of C (Customised) may NOT be updated.

I Insert

Allows INSERTION of a USER variable

(See “INSERT a USER Variable” on page 85)

R Repeat

Allows INSERTION of a USER variable, using values copied from theselected variable (only the Variable Name is NOT copied).

(See “INSERT a USER Variable” on page 85)

S Ship

Restores the variable to the shipped CustomPac values.

You will be required to confirm your SHIP request.

(See “RESTORE a Variable to the SHIPPED Value” on page 87)

WARNING

The S line command is generally used as Select in the other dialogpanels.

(See “The Line Commands” on page 11)

Selecting new values for the variables in your order

Reviewing the variables in your order and identifying values for them in advance willsimplify your work for this task. Figure 43 shows some variables that will likely requiresome research on your part, and, perhaps, a discussion with your installation's storageadministrator and security administrator.



Notes:

1. As shipped in your order, the system name (SYSNAME) for the target system is CPAC.If you change the SYSNAME value for your order, later in the installation you must

Figure 43. Installation variables that require some planning

Variable synonym Default value Description

DYNAMIC DASDINFO

Default: Yes Specifies whether the dialog should useinformation from online volumes toautomatically determine devicecharacteristics, including device geometry,volume size and device number. If thesystem on which the dialog runs is not thesame system on which the installation jobswill run, two different volumes with thesame volume serial could be online (one ineach system) and the dialog could retrieveinformation about the wrong device. In thissituation, you should specify "No" for thisvariable and define the volumes manually.

INSTALLDIRECTORY

Default: /Service Directory on the driving system in whichyour order's file system elements are to berestored and its file systems mounted. Thisvalue cannot be blank. By default, theInstall Directory is /Service. If you specifya directory other than /Service, do notexceed 20 characters. Mixed casecharacters are allowed. If your drivingsystem file system is mounted read-only,the specified directory must already existon the driving system. In a multileveldirectory path, the lowest directory fromthe root is automatically created. Higherdirectories are not created.

SPOOL VOLPREFIX

Default: MVSC1 First 5 characters for names of spoolvolumes. This value must match the valuespecified in the allocation values for theHASPACE data set.

SYSNAME Default: CPAC System name, as it is specified on theSYSNAME= parameter of the IEASYSxxparmlib member. Standard data set namingconventions apply. If you change this valuefrom the default (CPAC), you must alsochange the value of SYSNAME in theIEASYSxx member used to IPL the targetsystem. For a full system replacement,changing the SYSNAME value requiresthat you update the system name list in theSMS Base Configuration (using ISMF afteryou IPL). Then, you must activate thechanged SMS configuration before you canuse SMS.

SYSTEM LOGGERHLQ

Default: IXGLOGR This variable sets the high-level qualifierthat System Logger will use to createstaging data sets and log data sets for logstreams.



ensure that the new system name is defined in the appropriate places, as described in thechapter on IPLing the target system in SystemPac: Installation Guide.

2. The RACF OLD PDSN and RACF OLD BDSN variables allow you to specify only oneprimary RACF database name and one backup RACF database name. If you use morethan one primary or backup RACF database, or do not use a backup RACF database,you must change some of the installation jobs accordingly.

BROWSE Variable Definition

The variable details are displayed using a two panel sequence.

� � CustomPac ------------ Installation Variables ( MD000277 ) -------------------- COMMAND ==>

BROWSE Variable Definition - Value

Variable : F90GDQ01

Synonym : PREFIX DIALOG DSN

Status : PREDEFINED

Default Value

: CUSTNAME.MD000277

Current Value

: GLANDALE.MD000277

( Press ENTER for Description Fields )

� �

Figure 44. CPPP6113 - BROWSE Variable Definition - Value




BROWSE Variable Definition - Usage

Variable Description

: You MUST change this entry to the same prefix: (Custname.Ordernumber) as you used for the: output datasets of the job described in the: Installation Guide under 'DOWNLOAD RIM TAPE'.:: EG. If the dialog datasets are named:: GLANDALE.VS4.SCPPxENU:: Then, this variable should be set to:: GLANDALE.VS4:::

� �

Figure 45. CPPP6114 - BROWSE Variable Definition - Usage

NOTE

Variable section HEADERs ( ==>) may also be browsed.

The format of the first panel display will be changed to show only the synonym andstatus.

The description panel gives a general overview of the variables in the current section.

The ENTER/END/RETURN keys have the following actions -

ENTER On the Value panel, displays the Usage panel.

On the Usage panel, terminates the Browse function.

END/RETURNOn the Value panel, terminates the Browse function.

On the Usage panel, displays the Value panel.

DELETE a USER Variable

This panel is displayed when you have requested the delete of a user defined variable.




DELETE a USER Variable

```````````````````````````````````````````````````````````````````````````````````` ````````````````````````````````````````` Variable : $VS4ISPF ````````````````````````````````````````` `````````````````````````````````````````````````````````````````````````````````````````` `````````` Status : USER Synonym : VS4 ISPF HLQ `````````` `````````` Default : VS4.ISPF `````````` `````````` Current : GLANDALE.ISPF `````````` `````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````



� �

Figure 46. CPPP611D - DELETE a USER Variable - Confirmation

You have requested that a USER defined variable be deleted.

You are required to CONFIRM your request by typing DELETE in the COMMAND==> field and pressing enter.

WARNING

If the variable is used by user defined installation jobs (or modified CustomPac shippedjobs) then errors may occur when the JCL is generated by the Installation Jobs dialog.

EDIT Variable Definition

The variable details are updated using a two panel sequence.




UPDATE Variable Definition - Value

Variable : F00ODD01

Synonym : DSN CONSOL00

Status : MERGED/DEFAULT

Default Value

: SYS1.PARMLIB(CONSOL00)

Current Value

==> VS4.PARMLIB(CONSOL00)


� �

Figure 47. CPPP6115 - UPDATE Variable Definition - Value


UPDATE Variable Definition - Usage


==> Location of the driving systems' CONSOL00==> member==>==>==>==>==>==>==>==>==>==>==>==>==>

� �

Figure 48. CPPP6116 - UPDATE Variable Definition - Usage

only variables that do NOT have a status of C (Customised) may be updated.

You may change the following fields -

Current ValueThe data value of the variable which will be used when installation jobs aregenerated.



Variable DescriptionThe description of the variable.

There are 15 fields that may be used for this purpose.

NOTE

Variable section HEADERs ( ==>) may also be Updated.

only the description may be changed.



On the Usage panel, terminates the Edit function and updates the variableusing the values entered.

END/RETURNOn the Value panel, terminates the Edit function.


INSERT a USER Variable

The USER variable is inserted using a two panel sequence.


INSERT a USER Variable - Value

Variable Name ==> $ VS4ISPF:

User Variables are ALWAYS a $ plus 1 to 7 characters

Synonym ==> VS4 ISPF HLQ

Status : USER

Default Value ==> VS4.ISPF

Current Value ==> GLANDALE.ISPF


� �

Figure 49. CPPP6117 - INSERT a USER Variable - Value




INSERT a USER Variable - Usage


==> Enter the High Level Qualifiers of==> the ISPF system libraries for the==> VS4 complex.==>==> ** NOTE **==>==> The PRODUCTION version of ISPF is==>==> VS4.V4R2M0==>==> The TESTING version of ISPF is==>==> VS4.V4R3M0==>==>

� �

Figure 50. CPPP6118 - INSERT a USER Variable - Usage

You must define the following fields -

Variable NameThis is the name of the variable, it must follow the naming conventions for astandard ISPF variable.

It must be unique and NOT already used, if it is used you will receive a"duplicate" message.

RESTRICTION

Shipped CustomPac variables all begin with the letter "F"

You are FORCED to use the $ character as the first character of the uservariable name.

This restriction is needed to ensure that there is no possibility ofcorrupting any variables used internally by the CustomPac InstallationDialog.

Synonym This is a short description used to identify your variable.

Default ValueThe data value of the variable used as a reference value (if the Current Valueis not the same as this value, then the Current Value may have been changedby the installer).

Current ValueThe data value of the variable which will be used when installation jobs aregenerated.

Variable DescriptionThe description of the variable.

There are 15 fields that may be used for this purpose.





On the Usage panel, terminates the Insert function and inserts the variableusing the values entered.

END/RETURNOn the Value panel, terminates the Insert function.


RESTORE a Variable to the SHIPPED Value

This panel is displayed when you have requested that a variable is restored to the shippedCustomPac value.


RESTORE a Variable to the SHIPPED Value

```````````````````````````````````````````````````````````````````````````````````` ```````````````````````````````````````` Variable : F90GDQ01 ```````````````````````````````````````` ````````````````````````````````````````````````````````````````````````````````````````` `````````` Status : PREDEFINED Synonym : PREFIX DIALOG DSN `````````` `````````` Default : CUSTNAME.MD000277 `````````` `````````` Current : GLANDALE.MD000277 `````````` `````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````

`` You MUST Confirm RESTORE By Typing RESTORE and pressing ENTER

`` Press the END or RETURN key to CANCEL the RESTORE request

� �

Figure 51. CPPP611S - RESTORE a Variable - Confirmation

You have requested that a variable be restored to the shipped CustomPac value.

• The Default Data Value is restored

• The Current Data Value is restored

• The Variable Description is restored.

You are required to CONFIRM your request by typing RESTORE in the COMMAND==> field and pressing enter.

NOTE

If a USER variable is restored, then the Current data value will be made the same as theDefault data value.


Defining the SMP/E zone configuration

Chapter 9. Defining the SMP/E zone configuration

NOTE

This is only required for SystemPac (DD), ServerPac FunctionPac. and ProductPac.

From the Installation Menu, enter Z to begin the next dialog function, Define ZoneConfiguration. If you are installing a FunctionPac order, then the dialog displays the GlobalCSI Selection (CPPP6390) panel as shown in Figure 52. The CPPP6390 panel is notdisplayed if the order is not a FunctionPac order. If your order is not a FunctionPac orderand it contains products installed by Installation Manager (IM), the dialog displays theModify Zones & Installation Manager Information (CPPP639A) panel as shown inFigure 54 on page 89. The CPPP639A panel is not displayed if the order does not containIM-installed products. If your order is not a FunctionPac order and it does not containIM-installed products, then the Define SMPTLIB and Zone Names (CPPP6391) panel isdisplayed.

� �CPPP6390 --------------- Global CSI Selection (QD002626) --------------- COMMAND ==>

Do you want to use your existing Global CSI? (Yes or No)

===> NO

WARNING: If you select YESs your existing Global CSI will be updated with the shipped information of the order. You should make a backup of your existing Global CSI beforehand.

� �

Figure 52. CPPP6390 - Global CSI Selection

On the Global CSI Selection panel, specify whether you want to use your existing GlobalCSI data set for installing the FunctionPac order. Answer either YES or NO to the questionabout using existing Global CSI. If you specify NO, you are indicating that you do not wantuse your existing Global CSI. When you press Enter, either the Modify Zones & InstallationManager Information panel (see Figure 54 on page 89) or the Define SMPTLIB and ZoneNames panel (see Figure 58 on page 92) is displayed. If you specify YES to the existingGlobal CSI question and press Enter, you are asked to enter the existing Global CSI name,as shown in Figure 53 on page 89.



� �CPPP6390 --------------- Global CSI Selection (QD002626) --------------- COMMAND ==>

Do you want to use your existing Global CSI? (Yes or No)

===> YES

WARNING: If you select YESs your existing Global CSI will be updated with the shipped information of the order. You should make a backup of your existing Global CSI beforehand.

Enter the Global CSI Name:

===>� �

Figure 53. CPPP6390 - Global CSI Selection

You must enter a valid Global CSI name when YES is specified for the existing Global CSIquestion.

After specifying the data set name for the Existing Global CSI and when you press Enter,either the Modify Zones & Installation Manager Information panel (see Figure 54) or theDefine SMPTLIB and Zone Names panel (see Figure 58 on page 92) is displayed.

� �CPPP639A Modify Zones & Installation Manager Information ( ND001575 )OPTION ==>

Z Specify SMPTLIB and Zone Names Information

P Specify Installation Manager Installed Products Information (Required)

� �

Figure 54. CPPP639A - Modify Zones & Installation Manager Information

On the CPPP639A panel, selecting the Z option will display the CPPP6391 panel, which isthe same panel as the one in Figure 58 on page 92. This option is explained in detail laterin this chapter. You can also select the P option to display the CPPP6398 panel (Figure 55on page 90), which shows the list of components that can be installed using InstallationManager. For mandatory components, the Install field is filled with Y. For optionalcomponents, the Install field is displayed with default value ?, which must be changed to Yor N.

Chapter 9. Defining the SMP/E zone configuration 89


� �CPPP6398 ------------- IM Installed Products( ND001575 ) ----- Row 1 to 5 of 5COMMAND ==> SCROLL ==> CSR

Primary Commands:(? CANcel SAVE VErbose)Line Commands:(NONE)

Component Names identified below will be installed via Installation Managerif you enter a Y for Install field.

FMID Component Name InstallName (Y or N)------- -------------------------------------------------------------- --------HEJC800 WAS XD Compute Grid for WASV8 ?HEJC800 WAS XD Compute Grid for WASV7 ?HBBO800 WAS V8 Webserver Plug-ins ?HBBO800 WAS V8 IBM HTTP Server ?HBBO800 WebSphere Application Server V8 base YHBBO800 WAS V8 DMZ Secure Proxy Server ?HCYE720 WAS V8 ITCAM ?******************************* Bottom of data ********************************

� �

Figure 55. CPPP6398 - IM Installed Products

On the CPPP6398 panel, enter Y or N next to the optional components to include or excludethem for installation by the Installation Manager. You can also enter the primary commandVE to display the VErbose mode of the panel as shown in Figure 56.

� �CPPP6399 ------------- IM Installed Products( ND001575 ) ----- Row 1 to 5 of 5COMMAND ==> SCROLL ==> CSR

Primary Commands:(? CANcel SAVE TErse)Line Commands:(NONE)

Component Names identified below will be installed via Installation Managerif you enter a Y for Install field.

FMID Component Name InstallName (Y or N) PGM Number File System Path Name------- -------------------------------------------------------------- --------HEJC800 WAS XD Compute Grid for WASV8 Y 5655V62 /usr/lpp/zWebSphere/V8R0HEJC800 WAS XD Compute Grid for WASV7 Y 5655V62 /usr/lpp/zWebSphereCG/V8R0HBBO800 WAS V8 Webserver Plug-ins Y 5655W65 /usr/lpp/zWebSphere_Plugins/V8R0HBBO800 WAS V8 IBM HTTP Server Y 5655W65 /usr/lpp/IHSA/V8R0HBBO800 WebSphere Application Server V8 base Y 5655W65 /usr/lpp/zWebSphere/V8R0HBBO800 WAS V8 DMZ Secure Proxy Server Y 5655W65 /usr/lpp/zWebSphere_SPS/V8R0HCYE720 WAS V8 ITCAM Y 5655W65 /usr/lpp/zWebSphere/V8R0******************************* Bottom of data ********************************

� �

Figure 56. CPPP6399 - IM-installed products (verbose mode)

The CPPP639$ panel is displayed when you attempt to exit CPPP639A panel without goinginto the P option.



� � CustomPac --------------------------------------------------------------------- COMMAND ==>

Confirm Processing Requirements

This order contains IM installed products.

You have not selected which products

components you want to install.

Invoke option P on panel CPPP639A to

select the components to be installed.

Press the ENTER key to continue editing the table.

Press the END or RETURN key to save the current values andEXIT. Processing will resume at this function.

� �

Figure 57. CPPP639$ - Confirming processing requirements

Note: Panels CPPP639A, CPPP6398, CPPP6399 and CPPP639$ are not displayed if orderdoes not contain products installed by the Installation Manager.

'Define Zone Configuration' function allows you to change the SMP/E zone names that IBMsupplied for your order.

Choose SMP/E zone names that are unique for your installation. Doing so will allow you touse SMP/E's cross-zone processing, such as SMP/E's reporting and management functions.

If you want to rename the CSI data set, you can do so later in the Modify System Layoutfunction, described in Chapter 11, “Modify the System Layout” on page 107.

This panel allows you to change the names of zones in your order, but not the contents ofzones.

On entering the Z option, the dialog displays the current DLIB and target zone names foryour order (as shown in Figure 59 on page 92. When an SMP/E operational data setincludes the zone name you specified, your future changes to the zone names are propagatedto the SMP/E operational data set. If the zone name does not appear on the data set name,then an informational message is shown to indicate that the subsequent zone name changeswill not be propagated.

All SMP/E operational data sets are checked as to whether their rename causes the data setsname to exceed the 42 character limit (due to the minimum length of SSA). When the limitis exceeded, the data set that exceeded the limit is not renamed. The CPP0639009E errormessage is issued with the number of data sets, and the name of the data set that exceededthe limit.

If you select "NO" for SMS Managed, the following window appears.



� � CustomPac ---------- Define SMPTLIB and ZONE names ( MD053718 ) --- Row 1 of 5 COMMAND ==> SCROLL ==> CSR

Primary Commands:(? CANcel SAVE)Line Commands:(elemenTs Fmids)

--------------------------- SMPTLIB Information --------------------

Data set Prefix ==> SYS1.NCPSMS Managed ==> No (Yes/No)

Device Type ==> 3390Volume(s) ==> USER01 ==> USER02 ==> USER03 ==> USER04 ==>

--------------------------- Zone Names Information -----------------

S Nickname DLIB Zone Target Zone SST- -------- --------- ----------- ----

100 KMSD100 KMST100 MVS110 HHSD110 HHST110 MVS111 KMSD111 KMST111 MVS112 HHSD112 HHST112 MVS113 KMSD113 KMST113 MVS

******************************* Bottom of data ********************************

� �

the SMS Managed field

Figure 58. CPPP6391 - Define SMPTLIB and Zone names with no selected for

If you select YES in the SMS Managed field, the following window appears:

� � CustomPac ---------- Define SMPTLIB and ZONE names ( MD053718 ) --- Row 1 of 5 COMMAND ==> SCROLL ==> CSR

Primary Commands:(? CANcel SAVE)Line Commands:(elemenTs Fmids)

--------------------------- SMPTLIB Information -----------

Data set Prefix ==> SYS1.NCPSMS Managed ==> Yes (Yes/No)

Storage Class ==>

--------------------------- Zone Names Information --------

S Nickname DLIB Zone Target Zone SST- -------- --------- ----------- ----

100 KMSD100 KMST100 MVS110 HHSD110 HHST110 MVS111 KMSD111 KMST111 MVS112 HHSD112 HHST112 MVS113 KMSD113 KMST113 MVS

******************************* Bottom of data ********************************

� �

Figure 59. CPPP6391 - Define SMPTLIB and Zone names with yes



If you run an elementTs line command against a zone from the CPPP6391 panel, theCPPP6396 panel is displayed.

� � CPPP6396 -------- Define SMPTLIB and Zone Names ( MD053718 ) ---- Row 1 OF 82 COMMAND ==> SCROLL ==> PAGE

SUMMARY Of Features/Elements for MVSD100/MVST100

Primary Commands:(? SET Find Locate Next Previous)Line Commands:(Fmids)

S Feature/Element FMID#- --------------------------------------- -----

dsf ICKDS ENU 2msys for Setup 2z/OS UNIX System Services - Intgd Call 1z/OS UNIX System Services Application Se1zSecure Base 1zSecure Bookshelf 1Appl Wkload Mod Z/OS 1ASF V3R4 MUL 1BookManager Build ENU 2BookManager Read ENU 2BCP - Capacity Provisioning 1BCP Base 3BDT 1BDT FILE-TO-FILE 1BDT SNA NJE 1C/C++ Host Perf Analyzer 1Common Information Model 1

� �

Figure 60. CPPP6396 - Define SMPTLIB and Zone names

If you run an Fmids line command against a zone from the CPPP6391 panel, the CPPP6395panel is displayed with a summary of the FMIDs for that zone. You can also invoke thisdialog by running an FMID line command in panel CPPP6396.

� � CPPP6395 -------- Define SMPTLIB and Zone Names ( MD053718 ) ---- Row 1 OF 82 COMMAND ==> SCROLL ==> PAGE

FMID Summary for MVSD100/MVST100

PRIM Cmds:(? SET Find Locate Next Previous) LINE Cmds:(NONE)

FMID Description------ ----------------------------------------------------------------EDU1H01 ICKDSF - Device Support Facilities, BaseEER3500 Environmental Record Editing and PrintingEMI2220 MICR/OCRental Record Editing and PrintingETI1106 TIOC/OCRFDU1H07 ICKDSF - Device Support Facilities, ISMF/MODSFDU1H08 ICKDSF - Device Support Facilities, ISMF/ENUSHBB7750 BCP Base Device Support Facilities, ISMF/ENUHBCNC00 SMP/E Planning and Migration Assistant Software Info BaseHBCND0B SMP/E Planning and Migration Assistant Software Info BaseHBD6602 BULK DATA TRANSFER BASEation AssistantHBKM300 BOOKMANAGER READ/MVS BASEHBKP300 BOOKMANAGER BUILD/MVS BASEHBKQ330 Library ServerILD/MVS BASEHCKR1AB IBM Tivoli zSecure BookshelfHCKR1A0 IBM Tivoli zSecure BaseHCMG110 OS/390 UNIX SYSTEM SERVICES COHCM1A10 Hardware Configuration Manager

� �

Figure 61. CPPP6395 - Define SMPTLIB and Zone names



How zone names are used in your order

All DLIB zones for each SREL are physically defined in the same DLIB CSI data set. Alltarget zones for each SREL are physically defined in the same target CSI data set.

More than one zone pair (a DLIB and target) might be supplied with your order. Each zonepair has a 3-digit number as a nickname. The nickname is used to associate DLIB andtarget zones together.

For example, suppose you selected JES2 when creating the work configuration, but chosenot to merge its zones with the z/OS BCP zones. The following zone nicknames might beused:

Example

Nickname 100 . . . z/OS BCPNickname 110 . . . JES2

The zone nicknames are also used to generate the default DLIB and target zone names,based on the following naming convention:

• First 3 characters of the order name: CIC, DB2, IMS or NCP.

• 1 character zone type identifier

D Distribution Zone (Dlib)T Target Zone (Tlib)

• 3 character zone pair nickname.

For example, assume that a zone nickname of 500 was generated for a CICS order. The zonenames would be:

Example

CICD500 . . . for the Distribution ZoneCICT500 . . . for the Target Zone

For descriptions of the zones that came with your order, see the topic, Zones Shipped withYour Order, in SystemPac Installation Guide (Note that JES zones for an unselected JESelement and JES zones that are to be merged with the BCP zones will not appear in thedialog, even though they are listed in SystemPac Installation Guide.)

Changing the SMPTLIB and zone names in your order

For the SMPTLIB information, the Data set Prefix and SMS Managed (Yes/No) fields aremandatory. If SMS Managed is set to "No" (default), the Device Type field and at least oneVolume is also mandatory. If SMS Managed is set to "Yes", the Storage Class is alsomandatory. The dialog checks for all required SMPTLIB information to be specified, and ifanything is missing or incorrect, a message is shown.

In the panel (shown in Figure 59 on page 92), type over the DLIB and target zone nameswith the names that you want for your installation and press Enter. The dialog checks for



duplicate zone names and, if one is found, displays a message (CPP0639006E DUPLICATEZone Name) on the panel.

Ensure that the zone names you specify are unique for all environments in your installation.The new zone names should not appear in ZONEINDEX subentries in the global zoneZONE entries for any of your existing systems.

The following primary commands are valid for this panel:

CANCEL This command,abbreviated to CAN, discards any changes that you havemade since the last checkpoint, and exits the Zone Configuration panel. (Acheckpoint is taken on entry and exit to the dialog, and after any SAVEcommand).

SAVE This command saves any changes that you might have made and establishes anew checkpoint. (A checkpoint is taken on entry and exit to the dialog, andafter any SAVE command).

The following line command is valid for this panel:

ELEMENTSDisplays the features/elements that are installed in the selected zone. Specifya T for a zone pair and press Enter to display the features installed in thezone. This line command displays feature names only; it does not showFMIDs, nor does it display any other type of SYSMODs, such as PTFs, forexample.

FMIDS FMIDS Displays the FMIDs that are installed in the selected zone. Specify aF for a zone pair and press Enter to display the FMIDS with the descriptioninstalled in the zone.


The CPPP6397 panel is displayed when you attempt to end the Define SMPTLIB and ZoneNames function when the required SMPTLIB information is not specified or is in error, andyou ignored the ISPF messages "Enter required field" or "Invalid value". Some of therequired SMPTLIB information have never been specified or were invalid.





````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````` `````````` Some of the required SMPTLIB information have `````````` `````````` not been specified OR were invalid. `````````` `````````` `````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````

`` Press the ENTER key to continue editing the table

`` Press the END or RETURN key to save the current values and EXIT. Processing will resume at this function. If you enter CAN cel command on the previous panel, no new checkpoint will be established.

� �

Figure 62. CPPP6397 - Confirm Processing Requirements

Figure 63 shows the panel that is displayed when you attempt to end the ZoneConfiguration function when the DLIB and target zone names you have specified are inerror and you chose to ignore error message CPP0639006E or CPP0639013E. Either youhave used the same zone name more than once or (in the case of a FunctionPac order), if youhave selected to use the existing Global CSI, then the zone names are already present in theexisting Global CSI entered.



````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````` `````````` The Zone Configuration table contains at `````````` `````````` least one duplicate zone name `````````` `````````` `````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````


`` Press the END or RETURN key to save the current values andEXIT, Processing will resume at this function

� �


If you press Enter, the cursor is positioned on the first duplicate zone name. If you pressEnd, you exit the panel now, but you will have to return to it before you can continue withthe installation.



Chapter 10. Update Configuration with TargetEnvironment Data

NOTE

This is only required for ProductPac (FU) and RefreshPac.

Even if your ProductPac or RefreshPac is built with the SMPE CSI that you have shippedto the IBM production site, the configuration that shipped with the order does not have allthe information about the system that the order is going to be installed.

With the target system master Catalog and the driving system master catalog that aresupplied through the Variable option, the Update Configuration function scans the catalogsto ensure that the target system

• does not have the new product data sets that are going to be installed for ProductPac,and

• does contain the existing data sets which are required to install your zone serviceupgrade for ProductPac (with FULL UPGRADE) or RefreshPac.

Your order's configuration will then be updated to reflect the environment of the Targetsystem that will be used for the Modify System Layout and Installing your order options.

Updating the Configuration

� � CustomPac ------------------- Update Configuration ---------------------------- Command ==>

The Update Configuration function updates created configuration withtarget system information for all data sets affected by zone serviceupgrade and SMP/E related data sets. The list of affected data setswas detected during the order production time based on SMP/E APPLYand ACCEPT output.

This function will perform the following tasks :o Verify if Driving system and Target System master catalogs exist.o Search catalog for each of datasets that will be affected during

order installation. Save collected information for latter steps.o Produce Execution Report at the end of processing.o New Product datasets that are found in the catalog will be displayed

and users are asked to provide new names for the listed data sets.o Service affected data sets, identified in CSI, that are not found in

the catalog will be displayed and users will be asked to change andcorrect dataset names.

o Press END to search catalog again, or Type CANCEL to abort.Note that the user is required to fix all errors on the report beforecontinue with next function. This function cannot be bypassed.

ENTER - Run FunctionEND - Return without running function

� �

Figure 64. CPPP6230 - Confirm continue processing

After the function is selected, a panel will be displayed to explain the actions this function isgoing to take and prompt for continue processing.

Chapter 10. Update Configuration with Target Environment Data 97


Press:

• <ENTER> to confirm if you wish to start the scan and update immediately.

• <END> to return to the Installation Options Menu.

� � CustomPac --------------- (C) IBM Corporation 1990-1998 ----------------------

All Rights Reserved

```````````````````````````````````````` ```````` P L E A S E W A I T ```````` ```````` READING ```````` TARGET MASTER CATALOG ```````` DDDEF : AISTCLI0 ```````` SYS1.AISTCLI0 ```````` ````````````````````````````````````````

� �

Figure 65. CPPPMLOG - Update Configuration Message Panel

The function is executed online and it may take a while to search through all the data setswithin the configuration.

A message panel is displayed to notify you the current data set the function is processing. Bepatient while the updating is in progress.

Prompt for Indirect Reference VolumeIf your Target System Master Catalog contains indirectly catalog referencing or usingsymbolic variables, and the supplied CSI does not contain the volume information, a dialogbox will be displayed to ask you to supply the correct volume information.



� � CustomPac --------------- (C) IBM Corporation 1990-1998 -----------------------

All Rights Reserved

+---------------------------------------------------+| CustomPac ---- Indirect Reference Volume ------- || || Provide physical volume name to resolve || Following Indirect Reference Volume || || Indirect Reference Volume ****** || Physical Volume ______ || || || COMMAND ==> |+---------------------------------------------------+

� �

Figure 66. CPPP6233 - Indirect Reference Volume dialog box

� � CustomPac --------------- (C) IBM Corporation 1990-1998 -----------------------

All Rights Reserved

+---------------------------------------------------+| CustomPac ---- Indirect Reference Volume ------- || || Provide physical volume name to resolve || Following Indirect Reference Volume || || Indirect Reference Volume &RESV1 || Physical Volume ______ || || || COMMAND ==> |+---------------------------------------------------+

� �

Figure 67. CPPP6233 - Indirect Reference Volume dialog box (Symbolic)

Correct Data Set Names



� � CustomPac ----------- Dataset Names Conflict ( PI243259 ) -- Row 1 to 14 of 14 COMMAND ==> SCROLL ==> PAGE

Review and change listed data set name to correct reported errors:

PRIM Cmds:(? F N P CHD CANcel)

DDDEF Name Dataset Name to Correct Reason ---------- -------------------------------------------- ----------------------

SMPGCSI MVSSMPE.GLOBAL.CSI DATA SET NOT FOUNDTKANCMD TIVOLI.TKANCMD NEW DATA SET EXISTS

TKANMODL TIVOLI.TKANMODL NEW DATA SET EXISTSTKANMOD TIVOLI.TKANMOD NEW DATA SET EXISTSTKANMAC TIVOLI.TKANMAC NEW DATA SET EXISTS

TKANHENU TIVOLI.TKANHENU NEW DATA SET EXISTS TKANDATV TIVOLI.TKANDATV NEW DATA SET EXISTS

TKANSAM TIVOLI.TKANSAM NEW DATA SET EXISTS TKANPKGI TIVOLI.TKANPKGI NEW DATA SET EXISTS

TKANPAR TIVOLI.TKANPAR NEW DATA SET EXISTS TKANMODS TIVOLI.TKANMODS NEW DATA SET EXISTS TKANPENU TIVOLI.TKANPENU NEW DATA SET EXISTS

MVSDCSI CPPPI.PI243259.DLIB.CSI DATA SET NOT FOUNDMVSTCSI CPPPI.PI243259.CSI DATA SET NOT FOUND

******************************* Bottom of data ********************************

� �

Figure 68. CPPP6232 - Data Sets Names Conflict dialog

If the data sets exist in your order's configuration but cannot be located through the targetsystem master catalog, a panel will be displayed to show the missing data sets. Supply thecorrect name of the missing data set according to the DDDEF names.

For ProductPac orders, if the new product's data set names can be located through the targetsystem master catalog, a panel will be displayed. You can supply another data set names forthe new products to ensure that the existing data sets will not be overwritten when the newproduct is installed. If you want to use the existing data sets for installation of the newproducts, you can use the 'IGnoreNew' command to remove them for the data set list. The'IGnoreNew' Command also allows you to defer the rename of the new product data setsaction until the 'Modify System Layout' option where you will have the list of all data sets tobe allocated.

Press <END> and the function will scan again the catalog to build the correct information.

Change Data Set Names

The global change command may be used to change any string of characters in the data setname to any other string of characters.

The resulting data set name is checked to see that it is a valid MVS data set name AND thatit conforms to CustomPac standards.

Command Syntax

CHD source target

source This is the character string to be searched for

target This is the character string to be substituted for the source.



Example

For all data sets in the current Display LIST you want to change character stringISP.V3R5M0 to GLANDALE.ISP

CHD ISP.V3R5M0 GLANDALE.ISP

So ISP.V3R5M0.ISPPLIB would be changed to GLANDALE.ISP.ISPPLIB

LOW Level Qualifier

Generally you are NOT ALLOWED to change the LOW LEVEL QUALIFIER of the dataset profile name.

For SMP/E managed data sets CustomPac forces the SMP/E DDDEF name to be the sameas the low level qualifier.

Hint

When using CHANGE command for HLQs and to prevent accidental change of acharacter string which may imbedded in the low level qualifier, it is suggested you usethe command with a trailing period (".").

For example, To change the HLQ from "CEE." to "SYS1.CEE.":

CH "CEE." "SYS1.CEE."

ALL data set profiles in the current Display LIST are processed against the specified globalchange parameters, any that would be changed are added to a table of "Hits".

The "Hits" table is displayed so that you can decide whether to commit the changes, cancelthe global change request or eXclude specific data sets from the change request.

� � CustomPac ------------- Modify System Layout ( MD000277 ) -- ROW 1 TO 4 OF 22 COMMAND ==> SCROLL ==> PAGE

GLOBAL Change - Candidate List

PRIM Cmds:(? SET L F N P CANcel) LINE Cmds:(eXclude)

S DSName (Old New) - --------------------------------------------

ISP.V3R5M0.AISPALIBGLANDALE.V3R5M0.AISPALIB--------------------------------------------ISP.V3R5M0.AISPEXECGLANDALE.V3R5M0.AISPEXEC--------------------------------------------ISP.V3R5M0.AISPGENUGLANDALE.V3R5M0.AISPGENU--------------------------------------------ISP.V3R5M0.AISPMACSGLANDALE.V3R5M0.AISPMACS--------------------------------------------

� �

Figure 69. CPPP6237 - GLOBAL Change - Candidate List



At this point in time global changes have only been simulated, NO data sets have actuallybeen changed.

If you press the END or RETURN key then ALL global changes shown in the list will beapplied to the data set profiles.

(See CANCEL PRIMary command and eXclude Line Commands).


?, SET, F, L, N, PThese are standard CustomPac table handling commands.(See Chapter 2, “Understanding The Dialog” on page 7)

CANCEL This may be abbreviated to CAN

The command forgets any global changes that would have been made to thedata set profiles, NOTHING is changed.


X eXclude

The global change shown for the selected data set profile will be removedfrom the list of Global Changes.

The data set profile will NOT be changed.

Bypassing New Product Data Sets WarningNew Product data sets that are found in the catalog will be displayed and users are asked toprovide new names for the listed data sets. The The global IGnoreNew command may beused to remove the New Product data sets from the list, if users want to

• use those existing data sets for installing the product, or• defer providing new names for the listed data sets until 'Modify System Layout' option.

Command Syntax

IGN hlq

hlq This is the data set prefix to be searched for

Example

For all data sets in the current Display LIST you want to take out those data sets withprefix ISP.V3R5M0

IGN ISP.V3R5M0

So all data sets with prefix ISP.V3R5M0.ISPPLIB would be listed

Based on the parameter you specify on your IGnoreNew command, the dialog extracts thedata sets in the current display list with the qualifier specified and returns a candidate list ofdata sets. For example, Figure 70 on page 103 show a candidate list that simulates theIGnoreNew command action.



� � CustomPac -----------New Dataset Names found ( MX000277 ) -- ROW 1 TO 4 OF 22 COMMAND ==> SCROLL ==> PAGE

GLOBAL Ignore - Candidate List

PRIM Cmds:(? SET L F N P CANcel) LINE Cmds:(eXclude)

S DSName - --------------------------------------------

ISP.V3R5M0.AISPALIB--------------------------------------------ISP.V3R5M0.AISPEXEC--------------------------------------------ISP.V3R5M0.AISPGENU--------------------------------------------ISP.V3R5M0.AISPMACS--------------------------------------------

� �

Figure 70. CPPP6238 - GLOBAL IGnoreNew - Candidate List

You now must determine whether to commit the change as shown in the display, cancelyour change request, or exclude particular data sets from the candidate list beforecommitting the change.

To commit the change, press PF3. To cancel the change, enter the CANCEL command andpress Enter.


?, SET, F, L, N, PThese are standard commands for panels that display lists. See Chapter 2,“Understanding The Dialog” on page 7

CANCEL This command, abbreviated to CAN, discards any changes that you havemade since the data set list.


X Excludes the selected data set from the list of data sets to be removed. Thedata set is not removed if the change is committed.

Using the Update Configuration ReportAfter all data set names have been corrected, that is, all existing data set names are found,and all new product data set names are confirmed not present in the target system, theUpdate Configuration Report will be displayed.



� � CustomPac ------------ Update Configuration ( AF000105 ) -------- Row 1 of 994


PRIM Cmds:(? F N P SAVE)

------------------------------------------------------------------------------ ****************************************************************************** * EXECUTION SUMMARY * * * ******************************************************************************

NO ERRORS FOUND. YOU MAY CONTINUE WITH NEXT FUNCTION

****************************************************************************** * CATALOG INFORMATION * * * ******************************************************************************

DRIVING SYSTEM MASTER CATALOG: CATALOG.MCATVFF TARGET SYSTEM MASTER CATALOG: CATALOG.MVSICFM.VIT2C1A

****************************************************************************** * TARGET CATALOG * * CATALOG.MVSICFM.VIT2C1A * * * ******************************************************************************

TARGET SYSTEM MASTER CATALOG :CATALOG.MVSICFM.VIT2C1A CONNECTED

DRIVING SYSTEM MASTER CATALOG :CATALOG.MCATVFF CONNECTED

DSN: GIM.SGIMPENUCAT: CATALOG.MVSICFM.VIT2C1A VOL: RS1VFF

DSN: GIM.SGIMLMD0CAT: CATALOG.MVSICFM.VIT2C1A VOL: RS1VFF

DSN: GDDM.SADMSYMCAT: CATALOG.MVSICFM.VIT2C1A VOL: RS3VFF

DSN: GDDM.SADMSAMCAT: CATALOG.MVSICFM.VIT2C1A VOL: RS3VFF

...

...

...

� �

Figure 71. CPPP6231 - Update Configuration Report



SAVE Saves the displayed Summary Report to a data set.

You can save the update report to a data set by entering the SAVE primary command. It issaved with the following convention :-

OrderHLQ.LOG2

indicated by the message:



CPP0623001I Report output has been saved in data set''CPP.RAYMOND.AF000105.LOG2''

The meaning of the report headings are as follows:-

EXECUTION SUMMARY This part indicates whether the update configurationoption is successfully completed. Only when there isNO ERROR FOUND then the dialog is allowed tocontinue to the next function.

If the configuration update is not successful, thissection will summarize all the encountered problems inthe form of messages. Details of the message can befound in the later section that describes the data set.

The description of the error messages and theresolution will be described in “Update ConfigurationError Messages.”

CATALOG INFORMATION This section shows the target system master catalogand driving system master catalog information. Toindicate if the catalogs are accessible by the drivingsystem.

TARGET CATALOG This portion of the report shows all data sets in theconfiguration that are successfully located through thecatalogs and indicates the volume the data set isplaced.

If a data set is not successfully found, it will be shownhere also with the corresponding error message asindicated in the EXECUTION SUMMARY section.

Update Configuration Error MessagesIf you want to abort the Catalog checking step and continue, type CAN on panel CPPP6232(see Figure 68 on page 100), and the Update Configuration Report will be displayed.



� � CustomPac ------------ Update Configuration ( AF000105 ) -------- Row 1 of 994


PRIM Cmds:(? F N P SAVE)

------------------------------------------------------------------------------ ****************************************************************************** * EXECUTION SUMMARY * * * ******************************************************************************

THE FOLLOWING TYPES OF ERRORS FOUND, PLEASE CORRECT

MSG01E - MASTER CATALOG(S) NOT CONNECTED.

MSG02E - DATA SET(S) FOUND IN CATALOG; BUT NOTFOUND IN VOLUME OBTAINED FROM CATALOG.

MSG03W - MISSING DDF NAMES. REQUIRED DDF COULD NOT BEFOUND DURING ORDER BUILD

MSG04W - DATA SET VOLUME OBTAINED FROM CATALOG DIFFER TODDDEF VOLUME.

MSG05E - LISTDSI UNEXPECTED ERROR. SEE MESSAGE FOR MOREDETAILS.

MSG06E - SERVICE AFFECTED DATA SETS NOT FOUND IN CATALOG.

MSG07E - CATALOG(S) NOT FOUND. SEE MESSAGE FOR MORE DETAILS

MSG08W - DATA SET(S) MIGRATED AND 'NO WAIT FOR HSM RECALL'WAS REQUESTED. YOU MUST RECALL THOSE DATA SETS AND RE-RUN.

MSG09E - INSUFFICIENT AUTHORITY PROBLEM. OBTAIN APPROPRIATEAUTHORITY THEN INVOKE FUNCTION AGAIN.

� �

Figure 72. CPPP6231 - Execution Summary messages



Chapter 11. Modify the System Layout

NOTE

This is only required for SystemPac (DD), ServerPac and FunctionPac andProductPac.

Shipped with your order is a CustomPac generated ISPF table known as the LVT (LogicalVolume Table). This table contains a list of all the data sets needed for your orderedsystem.

Each data set entry in the table is known as a data set profile, each data set profile describesa unique DDDEF. If the shipped data set profiles do not fit your installations' DASD plan,then this dialog will assist you in customising them so that they do. Data set profiles may becustomised as a group (using GLOBAL CHANGE commands) or individually. Certainrestrictions are placed on the customisation (Eg. data sets required for an IPL must reside ona specific Logical Volume), but generally you are allowed a lot of freedom in defining the"layout" of your system.

Important Concepts

Data Set ProfilesA data set profile is the collection of information that defines a unique DDDEF within theCustomPac process.

This information includes -

• The data set name

• Space information

• Physical attributes

EG. DCB information and DASD residency

• Flags which describe the relationship of the data set to other data sets and to theinstalled system as a whole.

EG. "data set must be in the master catalog"

Logical VolumesData set profiles are assigned to LOGICAL VOLUMES. The Logical Volume is thenassigned to a Physical Volume.

A Logical Volume name (just like a Physical Volume name) is 6 characters long, they aresimply a means of grouping together data set profiles that are connected by DASDresidency.

Generally, CustomPac groups data set profiles using the following Logical Volume names -

Chapter 11. Modify the System Layout 107


CATxxx Logical Volumes that begin with the characters CAT identify data setprofiles that reside on a CATALOG volume.

RESxxx Logical Volumes that begin with the characters RES identify data set profilesthat reside on a system RESidence volume.

DLBxxx Logical Volumes that begin with the characters DLB identify data set profilesthat reside on a Dlib (Distribution LIBrary) volume.

You are free to define your own logical volume names or transfer data set profiles betweenlogical volumes.

There are TWO special Logical Volumes used by CustomPac that you may NOT customisein any way, shape or form -

CSIVOL This Logical Volume is reserved for the CSI data sets used to hold the Dliband Tlib zones for the ordered products.

IPLVOL This Logical Volume is reserved for data set profiles that are required forsystem IPL.

Data set profiles may not be transferred to, or transferred out of either of these logicalvolumes.

SMxxxx SMS-managed data sets, as follows:

SMDxxx SMS-managed data sets on a DLIB volume.SMHxxx SMS-managed hierarchical file system (HFS) files.SMRxxx SMS-managed data sets on a target volume.SMZxxx SMS-managed CSI data sets.

You are free to define your own logical volume names or transfer data sets between logicalvolumes. Before you begin, however, it is recommended that you gather the information youwill need for each feature or element. Figure 73 shows one approach you could use forgathering this information.

Figure 73. A Way of Organizing Your Volume Information...

Feature orElement

Logicalvolume

Physicalvolume

SMS StorageClass VOLSER Device type

DeviceAddress

Existing Device SupportThis means that the data set profiles can be allocated to a physically existing DASD deviceat your installation.

This allows you to better manage your system layout and to make better use of DASD. Youno longer need several completely empty DASD devices to install your order, thus easingthe installation process.

This added flexibility brings with it extra responsibilities for the installer !

When you specify the data set space requirements in Modify System Layout, a check ismade "at that point in time" to see if they are valid.



However because DASD space can be extremely dynamic then problems may occur whenthe allocaton job is run in the Installation Jobs function. This is because the amount of freespace on the DASD may have been reduced in the period between defining the data setprofile and running the job to allocate it.

The installer must be aware of this possibility.

If this happens, then you may have to re-evaluate your system layout in Modify SystemLayout, or perform some housekeeping on the physical DASD device causing the problem.

The installer must also be aware that any data sets that Modify System Layout intends toallocate on the physical DASD must not already exist, else expect a JCL error at the veryleast.

If you specify an existing volume and receive the message "Volume information is notavailable", ensure that the volume is online. If not, make the volume available. Otherwise,the message relates to the level of DFSMS or DFPthat is running on the driving system, asfollows:

• If your driving system is running DFP Release 3.3 or earlier, you cannot use an existingvolume. Specify a new volume.

• If your driving system is running DFSMS Release 1.1 or later, rebuild the index of theaffected volume and respecify it.

If you selected a Software Upgrade (and are therefore using your existing catalog structure)and you are not using existing volumes, ensure that any data sets to be scratched for the newsystem retain their existing catalog entries. This action is necessary for all data sets that arenot processed through the Modify System Layout function of the dialog.

Modify System Layout Options

The Modify System Layout Options panel is displayed if you enter M from the InstallationMenu.

� � CustomPac ------------- Modify System Layout ( MD053718 ) --------------------- OPTION ==>

A Create a Recommended System Layout (Automatically assign target andDLIB data sets to physical volumes by data set type)

C View and change data sets by selected attributesT View and change device type table (DEVT)

D Data Set Summary (SUMD)V Physical Volume Summary (SUMP)L Logical Volume Summary (SUML)

P Product, Feature and Element Summary

------------------- Session Control Options -----------------------K Keep Changes made in this dialog session so far (SAVE)B Back Out changes from this dialog session (CANcel)

� �

Figure 74. CPPP605T - Modify System Layout Options



During this part of the dialog, you create the data set layout for your new system. After youhave modified this configuration, you can save it for merging with future CustomPacinstallations.

IBM recommends that you modify your configuration in the following order:

1. Data set merges, if any

2. Data set space changes, if any

3. Specifying Reserved Space, if it will be used

4. Specifying which volumes are not to be initialized

5. Everything else.

This method can help you avoid situations in which volumes become overallocated.

You can create the new data set layout in one of three ways:

• Use Option A, Recommended System Layout, to assign your order's target and DLIBdata sets to volumes automatically.

• Use Option C, View and Change, to assign your order's data sets to volumes bydisplaying groups of data sets and use the CHANGE PVOL command to specify theirplacement on physical volumes.

• Use the other options (D, V, L, and P) to assign your order's data sets to logical volumesand then assign those logical volumes to physical volumes (DASD).

To save the most time in the dialog, use Option A to create the recommended system layout.The dialog will automatically assign your order's target and DLIB data sets to your DASDvolumes, attempting to match, as closely as possible, the IBM recommended system layoutthat is described in the topic, “Recommended Data Set Placement,” in z/OS Planning forInstallation. Then use the View and Change for any subsequent changes you make to theconfiguration data sets.

This chapter describes the recommended approach in three sections, as follows:

• Option A in “Creating the Recommended System Layout” on page 111• Option C in “Viewing and Changing Data Sets” on page 131• Option T in “Displaying Device Types” on page 168.

To control data set placement, use either Options A and C, or use the Summary Displaycommands for data sets (the SUMD commands), but not both. If you create a new layoutthrough Option A or change data set assignments in Option C and later attempt to managedata set placement using the dialog's Summary Display commands, you will have difficultybecause the dialog's automatic logical volume assignments will be dramatically differentfrom those you have saved in previous releases. (Note that the summary of physicalvolumes displayed by Option V or the SUMP command is still used to manage volumes, nomatter how you choose to control data set placement.)

To aid your work in this phase of the dialog, the Modify System Layout Options panelincludes session control options to allow you to set the dispositon of your changes, asfollows:

Option DescriptionK Keep any changes that you have made since the last SAVE.B Back out (discard) any changes that you have made since the last SAVE,

and exit the Modify System Layout function.



Creating the Recommended System LayoutIBM's recommended system layout provides a foundation for the ongoing growth andmaintenance of your system. When you group your system's data sets by their content andimportance to your installation, you help to minimize the complexity of future installations.For a further dicussion of the benefits of using the recommended system layout, see thetopic, “Recommended Data Set Placement,” in z/OS Planning for Installation.

When you select the Recommended System Layout option of the dialog, you are choosing toallow the dialog to automatically assign some or all of the target and DLIB data sets inyour order to DASD volumes. The dialog assigns data sets based on the followingconsiderations:

• Whether the data set is a target data set or a DLIB data set• Whether the data set must reside on the IPL volume• The type of data in the data set (panels, messages, load modules, and so on)• If the data set should reside on a particular volume in the configuration (for example,

the first volume or one of the last volumes).

The dialog does not automatically assign an order's operational data sets or any of thesample CustomPac data sets. Nor does the dialog automatically assign any SMS-manageddata sets in the configuration. You must continue to place these data sets yourself. When youdo so, it is recommended that you place operational data sets on volumes separate fromthose containing your target and DLIB data sets. Also, it is required that your SMS-manageddata sets reside on volumes other than those used for automatic assignment.

If you include a saved configuration from a previous order in the current work configuration,the dialog preserves any data set changes you might have made in the saved configuration,but does not preserve the assignment of data sets to logical or physical volumes.

The Role of Volumes in Automatic AssignmentTo begin the automatic assignment of data sets to volumes, you can make some of yourexisting volumes available to the dialog for creating the new system, or you can have thedialog create a configuration based entirely on new volumes. During automatic assignment,the dialog assigns data sets to these volumes. If the dialog requires additional volumes tocontain the new configuration, the dialog creates more volumes automatically.

If you are installing a z/OS order, you will restore the root file system into a single data set.For the root file system to be allocated as a single data set, you can place your z/OS root filesystem on a large DASD volume (generally larger than 3390-3), or use multiple volumes forthe z/OS root file system data set (if you only have 3390-3 volumes available). Subsystemorders typically do not contain large file system data sets, so the amount of space to usemight be smaller than z/OS. Note that the default volume value is 3390-9 in the dialog. Ifyou are using smaller values for new volumes, you need to change the default volume tomatch.

How Volume Types Are UsedThe type of data sets to be stored on a volume determines its volume type, as follows:

Target Volume Target library data sets

DLIB Volume DLIB data sets

BOTH Volume Target library data sets or DLIB data sets (or both).BOTH volumes are intended for use with subsystemorders, which are often small enough to fit entirely on



one volume. Also, BOTH volumes provide a finalalternative in the event there are not enough target orDLIB volumes available for a data s assignment.

Usually, the dialog creates only target and DLIB volumes, not BOTH volumes. The dialogcreates BOTH volumes only in the case in which there are no target (or DLIB) volumesavailable in the configuration, you have explicitly created at least one BOTH volume for theconfiguration, and there are additional target or DLIB data sets to be assigned.

How Volume Sequence Numbers Are UsedFor each volume in the new configuration, the dialog assigns a unique sequence number toindicate the order in which the volume will be selected for data set assignments. The volumesequence number follows a naming convention: Tnn for target volumes, Dnn for DLIBvolumes, and Bnn for BOTH volumes, where nn is 01 - 99, for a maximum of 99 volumesper type.

Assigning Data Sets to VolumesIf the work configuration contains data sets that must reside on the IPL volume, the dialogassigns these data sets to the first target volume (T01). Then, the dialog assigns data sets tovolumes in groups, based on their element type. The dialog assigns element types in thefollowing order (from first to last):

• LMOD• PARM• PROC• CLIST• EXEC• PNLxxx• SKLxxx• TBLxxx• MSGxxx• HELPxxx• Data sets that should reside on the first target volume• All other element types and data sets having no element type• Data sets that should reside on the last target volume.

For example, the dialog assigns your configuration's panel data sets (element type PNLxxx)to volumes before it assigns your skeleton libraries (element type SKLxxx).

Some products include one or more data sets that should reside on the first or last targetvolume in a configuration. For example, a product might include several data sets of elementtype DATA that should reside on the IPL volume, which is always the first target volume.During automatic assignment, the dialog recognizes such data sets and attempts to placethem according to this requirement, rather than with other data sets of the same elementtype.

Setting the Scope of Automatic AssignmentsWhen you select "Create a Recommended System Layout" (Option A) from Modify SystemLayout Options panel, the following panel is displayed.



� �CustomPac -------- Automatic Data Set Assignment ( MD053718 ) -----------------OPTION ==>

A - ALL Assign all target and DLIB data sets in the configurationto physical volumes automatically. This option creates arecommended system layout.

N - NEW Add new data sets to an existing configuration. Thisoption automatically assigns all new data sets, butpreserves the placement of previously-assigned datasets in your saved configuration.

P - PARTIAL Assign new data sets and reassign some existing data setsto physical volumes. This option automatically assignsall new data sets to physical volumes, as well as datasets from selected volumes in the saved configuration.

Enter EITHER a default device type OR a model volume below:Default Device Type ==> 3390-9 (For example, 3390-9) Model after Volume ==> (For example, ZOSRES)

� �

Figure 75. CPPP625B - Automatic Data Set Assignment

The Modify System Layout Options panel allows you to control the scope of the dialog'sautomatic assignments through the following settings:

ALL This setting causes all target and DLIB data sets in the configuration thatare not SMS-managed to be automatically assigned to physical volumes.

NEW This setting causes data sets that are new to the configuration to beautomatically assigned to physical volumes, but preserves the assignmentof data sets that already exist on volumes in the saved configuration.

PARTIAL This setting causes all new data sets in the configuration to beautomatically assigned to physical volumes, and also allows you toexclude particular volumes from the saved configuration, freeing their datasets for reassignment.

To see which new data sets will be assigned automatically, you can use the dialog's Viewand Change Facility to create a list of data sets that have the attribute "New Data Set." Formore information, see “Viewing and Changing Data Sets” on page 131.

In some cases, not every setting on this panel is selectable. For example, if you are notincluding a saved configuration in the new configuration, the only selectable scope on thispanel is ALL.

Choosing Between the PARTIAL and NEW: The PARTIAL and NEW settingsallow you to preserve some or all of your existing data set assignments. Choosing betweenthese two settings requires careful consideration of your existing volumes. Usually, the bestchoice is the one that creates the least work for you.

Both PARTIAL and NEW cause the dialog to automatically assign all new data sets andpreserve your current assignments. NEW preserves all of your existing assignments;PARTIAL preserves your existing assignments, except for those volumes that you choose tomake available for reassignment (through the eXclude line command).

The advantage of PARTIAL over NEW is increased flexibility. NEW does not allow you tomove volumes or rename them before you enter the CREATE command (as you can withALL or PARTIAL).



If you have used the Recommended System Layout option before, the dialog displaysvolumes in sequence number order. Otherwise, the NEW setting simply displays the IPLvolume first, if there is one in the configuration, and places remaining volumes inalphanumeric order. The dialog always attempts to assign data sets to volumes in the orderin which they are displayed. Once they are used for automatic assignment, each volume willhave a sequence number. If you need to move or rename volumes, it is recommended thatyou use ALL or PARTIAL. (If you choose NEW and then need to rename volumes so thatthey show up in the order you want, you must follow the procedures described at the end ofthis section.)

In choosing between NEW or PARTIAL, consider whether you have used theRecommended System Layout option before. If so, use NEW when both of the followingconditions are true:

• You used ALL in the past and you want to continue placing new data sets according tothe Recommended System Layout.

• Your volumes have enough space to ensure that new data sets will be logically groupedwith existing data sets of the same element type.

You should also use NEW if you do not want existing data sets to be moved and you do notwant to place the new ones yourself.

In all other cases, choose ALL or PARTIAL instead of NEW.

If you are reusing a saved configuration and you have not used Recommended SystemLayout option before, the NEW setting offers the most benefit when your existingconfiguration follows the IBM recommended system layout that is described in the topic,“Recommended Data Set Placement,” in z/OS Planning for Installation and your volumeshave adequate free space. If you have already gone through the effort of manually creating aRecommended System Layout configuration and have sufficient free space on the volumes,you should use the NEW path.

The first time you use automatic assignment, the dialog will assume that volumes are namedusing an ascending alphanumeric naming pattern (like OSRES1, OSRES2... or OSRESA,OSRESB...) when assigning sequence numbers for automatic assignment. Therefore, if youhave not used automactic assignment before and your target volume names do not follow anascending alphanumeric naming pattern, you should rename the volumes before using theNEW path, and then rename the volumes to their original names afterward, as follows::

• Before using Recommended System Layout, enter the SUMP command to display thework configuration's physical volumes. In the display, rename the target volumes tonames that would ensure that the volumes would appear in the proper sequence whensorted alphanumerically.

• In Recommended System Layout, chose the NEW setting and create the newconfiguration. The volumes will be assigned sequence numbers.

• Display the volumes in the new configuration. Change the target volume names back towhat you want them to be. The dialog will preserve this volume sequence forsubsequent installations regardless of the volume names, until you choose to no longerpreserve the volumes (for example, by excluding them during a subsequent PARTIALautomatic assignment).

Setting the Default Device Type or Model-After Volume:: On the Automatic DataSet Assignment panel, you must enter either a device type or a model volume to specify thetype of device to be used if the dialog creates more volumes for data set assignments. If youchoose to specify a model volume, either the volume must already be in the configuration or



you must have set the DYNAMIC DASD INFO variable to Y and the volume must beonline.

If you choose to specify a device type, ensure that device type has been defined to thedialog. To see a list of other available devices, enter a question mark (?) in the DefaultDevice Type field and press Enter. You can then select the device type you want from thepop-up display.

To add user-defined device types to this list, return to the Modify System Layout Optionspanel and enter Option T.

If you are installing a z/OS order, you must use 3390-9 volumes (or larger) to accommodatesome large data sets in the order. You can use smaller volumes for a subsystem orderbecause these orders usually do not contain large data sets; however, you need to change thedefault volume value from 3390-9 to a smaller one in the dialogs.

Displaying the Current Volume ConfigurationAfter you select a setting for automatic assignment, the dialog displays the current volumeconfiguration, as shown in Figure 76.

� �CustomPac -------- Automatic Data Set Assignment ( MD053718 ) -----------------COMMAND ==> SCROLL ==> CSR

Current Volume Configuration Scope ==>

Primary Commands:(? Reset CReate)Line Commands:(Select Insert List Move After Before eXclude)

Phys. Volume Sequence Device Used + Volume Existing Reserved S Volume Type Number Type Reserved Threshold Data Space - ------ ------ -------- ------ -------- --------- -------- -------- MVSRES TARGET T01 3390-3 315 % 85% 0 % 0 % MVSDLB DLIB D01 3390-3 224 % 85% 0 % 0 %******************************* Bottom of Data *********************************

� �

Figure 76. CPPP625C - Current Volume Configuration

As shipped by IBM, a new configuration consists of a target volume (MVSRES), a DLIBvolume (MVSDLB), and a catalog volume (MVSCAT). Because MVSCAT contains onlyoperational data sets, this volume is excluded from automatic assignments, and therefore isnot shown in the panel display.

Volumes are shown in volume sequence order if they have been used for automaticassignment before. Otherwise, all volumes except the IPL volume are shown inalpanumerical order. The IPL volume, if it is present in the order, is always shown first withsequence number T01.

If you use existing volumes for data set assignments, the dialog checks the storage capacityof these volumes. If the dialog creates a volume ( and the DYNAMIC DASD INFOinstallation variable is set to YES), the dialog determines whether the volume is online. Ifso, the dialog retreive the volume's attributes and availbale space, just as if the volume hadbeen inserted on the Current Volume Configuration Panel. For the ALL or PARTIALsettings, the dialog limits its use of volumes (new and existing) to 85% of capacity. Thedialog preserves the remaining 15% of each volume's capacity for the future growth of



configuration data sets over time and subsequent data set assignments for futureinstallations. For the NEW setting, the dialog limits its use of new volumes to 85% ofcapacity, but allows its use of existing volumes to increase to 90% before restricting thesevolumes from further data set assignments.

When the total of used space and reserved space is 10 times the size of the volume or more(that is, more than 999%), the "Used + Reserved" column will contain "999 % *". with theasterisk(*) highlighted as an eyecatcher.

In the Current Volume Configuration panel, use line command S to select volumes forchanges. Use line command L to list the data sets currently assigned to a volume. Use linecommand I to insert more volumes into the work configuration. Use line command X tomake exceptions to automatic assignment (as described in “Excluding Volumes fromAutomatic Assignments”).

When you select the ALL or PARTIAL settings, the following line commands are alsoavailable on this panel:

M, A, B Move a volume to a different position in the list. To move a volume after another,enter M for the volume to be moved, and A for the volume that is to precede it. Tomove a volume before another, enter M and B.

You can move a volume only among other volumes of the same type. For example,you can move a target volume before or after other target volumes but not into agroup of DLIB volumes or BOTH volumes.

To move a volume into a group of volumes of a different type, you must firstchange the volume's type to the other type (target, DLIB, or BOTH) through linecommand S. You can then move the volume within the group of volumes with thattype.

Moving a volume will cause the dialog to adjust the volume sequence numbersaccordingly.

If your installation uses volume names that do not ascend in the same order in which youwant to have the dialog use the volumes, you can use the M, A, and B line commands in theCurrent Volume Configuration panel to reposition the volumes in the order in which youwant them to be used. The dialog will retain the volume sequence numbers and use them inthe appropriate order thereafter.

If you select the NEW setting for your first use of automatic assignment you shouldtemporarily rename the volumes in the dialog, use the Recommended System Layout option,and then rename the volumes back to their original names.

When you have finished making changes to volumes, enter the primary command CR on theCurrent Volume Configuration display to create a new configuration.

Excluding Volumes from Automatic Assignments: The Current VolumeConfiguration panel provides line command X (eXclude) to allow you to make exceptions toautomatic assignment. Line command X has different uses, based on the scope of automaticassignment, as follows:

• For the ALL setting, you use line command X to select volumes for removal from thework configuration (the volumes are not actually removed from the work configurationuntil the CREATE command to create the configuration). The dialog does not useexcluded volumes for data set assignments. When you create the new configuration(through the CREATE command) and display it again, excluded volumes do not appearin the panel.



• For the NEW setting, you use line command X to make a volume ineligible for theassignment of new data sets; the volume remains in the work configuration and itsexisting data set assignments are left unchanged. However, as in the ALL setting, thevolume is removed from the Current Volume Configuration panel because no new datasets will be assigned to it. When you create the new configuration and display it again,excluded volumes do not appear in the panel. (However, if you exit the RecommendedSystem Layout function and re-enter it, the volume is again included in the CurrentVolume Configuration panel.)

• For the PARTIAL setting, you use line command X to make a volume's data setseligible for reassignment. When you create the new configuration, the excluded volumeis removed from the work configuration. When you enter a CREATE command, anexcluded volume will also be removed from the Current Volume Configuration panelbecause the volume's data sets will be reassigned to other volumes. When you redisplaythe Current Volume Configuration panel, the excluded volume does not appear in theCurrent Volume Configuration panel.

If you exclude a volume from the work configuration and then later change your mind, youcan restore the volume to the Current Volume Configuration panel. If you have not yetcreated the new configuration (through the CREATE command), you can restore the volumeto the panel by exiting the Recommended System Layout option and re-entering it. Theconfiguration will be displayed as it was when you previously entered the RecommendedSystem Layout option.

If you have already created the configuration, choose one of following approaches:

• In the ALL and PARTIAL settings, the volume is gone. Do one of the following:

− Add the volume to the configuration and assign data sets to it− Rename one of the new volumes to the volser you want− Recreate the configuration (re-enter the CREATE command) and try again. This

action resets all changes back to the values stored in the saved configuration if onewas used. Otherwise, this action restores the configuration to the order's shippedvalues.

• In the NEW setting, the volume will re-appear when you exit the Recommended SystemLayout option after creating the new configuration.

Selecting Volumes for ChangesIf you select a volume for changes, the dialog displays the panel shown in Figure 77 onpage 118, allowing you to change the volume and save your changes.



� �CustomPac ------ Automatic Assignment - Attributes ( MD053718 ) ---------------COMMAND ==>

Display and Change Volume Attributes

Volume Serial ==> MVSRS1 (Always required)

Volume Type ==> TARGET (Target, DLIB or Both - Always required)Device Type ==> 3390-9 (For example, 3390-9)

Reserved Space ==> 0 (Cylinders)

Initialize Volume ==> N (Y or N)

Note: Only the volume serial and volume type are required for online volumeswhen the DYNAMIC DASD INFO variable is set to Yes.

� �

Figure 77. CPPP625D - Display and Change Volume Attributes

Use caution in resetting volumes from Existing Data YES to Existing Data NO. Doing socauses the volume to be initialized by the installation jobs, and any existing data on thevolume is lost.

Volumes for which initialize Volume is set to NO must be online, even if DYNAMICDASD INFO is set to NO.

To save your changes to the volume, press Enter. You return to the Current VolumeConfiguration display.

Examples of Using Automatic AssignmentHow you achieve the recommended system layout depends on whether you are starting withan entirely new system or bringing forward a saved configuration to be merged with the neworder. And, in the later case, whether you are using the Recommended System Layoutoption for the first time, or have already used it on the saved configuration.

This section presents the panel sequence for each of these situations. To determine a courseof action, review each example and choose the one that best matches your objectives, asfollows:

• “Example 1: Using ALL without a Saved Configuration”• “ Example 2: Using ALL with a Saved Configuration” on page 122• “ Example 3: Using NEW with a Saved Configuration” on page 125• “Example 4: Using PARTIAL with a Saved Configuration” on page 128.

Example 1: Using ALL without a Saved ConfigurationFollow this path if you are installing a CustomPac order for the first time, or if you are notusing a saved configuration as the basis of your new system. This approach creates a newconfiguration based only on the new order to be installed.

Select "Automatic Data Set Assignment" (Option A) from the Modify System LayoutOptions panel. The following panel is displayed.








� �


Because you are not including a saved configuration in the new configuration, the onlyselectable setting on this panel is ALL. This setting causes the dialog to automatically assignall target and DLIB data sets in your order to physical volumes.

On the Automatic Data Set Assignment panel, you must enter either a device type or modelvolume to specify the type of device to be used when the dialog creates more volumes fordata set assignments. Check this value to ensure that the device type is available for thisinstallation. To see a list of other available devices, enter a question mark (?) in the DefaultDevice Type field and press Enter. You can then select the device type you want from thepop-up display. A configuration can include more than one device type.

If the DYNAMIC DASD INFO variable is set to Y, the model volume must be online. IfDYNAMIC DASD INFO is set to N, the model volume must already exist in theconfiguration.

Enter A to select the ALL setting and Press Enter. The current volume configuration isshown.






Phys. Volume Sequence Device Used + Volume Existing Reserved S Volume Type Number Type Reserved Threshold Data Space - ------ ------ -------- ------ -------- --------- -------- -------- MVSRES TARGET T01 3390-3 315 % 85% 0 % 0 % MVSDLB DLIB D01 3390-3 224 % 85% 0 % 0 %******************************* Bottom of Data *********************************

� �


Here, the configuration consists of a target volume (MVSRES), a DLIB volume(MVSDLB), and a catalog volume (MVSCAT). Because MVSCAT contains onlyoperational data sets, this volume is excluded from automatic assignments, and therefore isnot shown in the panel display. Observe that MVSRES and MVSDLB are overallocated.

If you plan to rename these volumes, select the volumes now through line command S andrename them as needed. Later, when the new configuration is created, it is more difficult torename these volumes.

If you choose to change the device type, do so now through line command S, rather thanafter you create the new configuration (by entering the CReate command on the CurrentVolume Configuration panel). Otherwise, the volume might become overallocated (forexample, if the default is 3390-9 and you change it to 3390-3).

To have the dialog create the new configuration, enter the primary command CR and pressENTER. The following panel is displayed, allowing you to confirm this action beforecontinuing.

� �CustomPac ------ Automatic Assignment Confirmation ( MD053718 ) ---------------COMMAND ==>

Scope: ALL

You have chosen to have data sets automatically assigned to physical volumes. IF YOU CONTINUE, THE ASSIGNMENTS CANNOT BE EASILY REVERSED WITHIN

MODIFY SYSTEM LAYOUT. However, you will be able to modify the configurationafter the assignments have been done. If you decide not to use theautomatic assignments after they have been done, return to CreateConfiguration, create the configuration again, and use other options inModify System Layout to tailor your configuration. You can also use theSHIP command to recreate the shipped, unmerged configuration.

Enter Y to continue, or N to return to the previous panel:

Continue ==> Y ( Y or N )

� �

Figure 80. CPPP625E - Automatic Assignment Confirmation



To continue, press Enter. The CustomPac progress panel is displayed (as shown inFigure 81 on page 121) as volumes are assigned.

� � CustomPac --------------- (C) IBM Corporation 1990-2000 ----------------------

All Rights Reserved

```````````````````````````````````````` ```````` P L E A S E W A I T ```````` ```````` AUTOMATIC ```````` DATA SET ASSIGNMENT ```````` IN PROGRESS ```````` VERIFYING SEQ. NUMBERS ```````` ````````````````````````````````````````

� �

Figure 81. CPPPMLOG - Automatic Assignment Progress Panel

If you want to change the device type from this panel, you should do so before you createthe new configuration (by entering the CR command on the Current Volume Configurationpanel). If done afterwards, the volume could be overallocated (for example, if the default is3390-3 and you change it to 3390-2).

After Recommended System Layout completes, the Current Volume Configuration panel(Figure 82) is displayed again to show you the new configuration.




Phys. Volume Sequence Device Used + Volume Existing Reserved S Volume Type Number Type Reserved Threshold Data Space - ------ ------ -------- ------ -------- --------- -------- -------- MVSRES TARGET T01 3390-3 84% 85% 0 % 0 % TARG02 TARGET T02 3390-3 83% 85% 0 % 0 % TARG03 TARGET T03 3390-3 85% 85% 0 % 0 % TARG04 TARGET T04 3390-3 62% 85% 0 % 0 % MVSDLB DLIB D01 3390-3 83% 85% 0 % 0 % DLIB02 DLIB D02 3390-3 83% 85% 0 % 0 % DLIB03 DLIB D03 3390-3 55% 85% 0 % 0 %******************************* Bottom of Data *********************************

� �


The new configuration is shown. Observe the following results:

• Four target volumes and three DLIB volumes were used for the new configuration:MVSRES, TARG02, TARG03, TARG04, MVSDLB, DLIB02, and DLIB03. You canrename these volumes by selecting them through line command S.



• The volumes were assigned sequence numbers T01 through T04, and D01 through D03,respectively, and are of the device type 3390-3.

• All but the last volumes of each type were filled close to the threshold (85%). The finalvolumes, TARG04 and DLIB03, contain the remainder of the target and DLIB data setsfrom your order.

• No volumes are over-allocated.

In some cases, you might find that the dialog creates more volumes than you think you need.If the last target or DLIB volume has very little used space and you want to eliminate it byplacing its data sets on other volumes, you can reassign the volume's data sets using thedialog's View and Change Facility (Option C on the Modify System Layout Options panel).Select "Current PVOL," select each volume in turn, and then use the CH PVOL command tomove the data sets to other volumes. For more information, see “Viewing and ChangingData Sets” on page 131.

If you decide to change the volumes after the new configuration has been created, useOption V from the Modify System Layout Options panel (shown in Figure 74 on page 109)to display the Summary of Physical Volumes and modify the volume names accordingly (asdescribed in “Displaying a Summary of Physical Volumes” on page 180.

Example 2: Using ALL with a Saved ConfigurationThis approach creates a new configuration based on your order and a saved configuration.Follow this path if you want the dialog to restructure your saved configuration in accordancewith IBM's recommended system layout.







� �


To reassign all target and DLIB data sets (saved and new), choose the ALL setting to causethe dialog to automatically assign these data sets to your DASD volumes, based on data settype. The ALL setting allows the dialog to create a new configuration that will follow therecommended system layout as much as possible.



On the Automatic Data Set Assignment panel, you must enter either a device type or modelvolume to specify the type of device to be used if the dialog creates more volumes for dataset assignments. If you choose to specify a model volume, either the volume must alreadybe in the configuration or you must have set the DYNAMIC DASD INFO variable to Y andthe volume must be online.

If you choose to specify a device type, ensure that device type has been defined to thedialog. To see a list of other available devices, enter a question mark (?) in the DefaultDevice Type field and press Enter. You can then select the device type you want from thepop-up display.

Press Enter. The panel shown in Figure 84 is displayed, showing the current configurationthat you would see if the model volume "MODVOL" specified on the previous panelhappened to be a 3390-3.




Phys. Volume Sequence Device Used + Volume Existing Reserved S Volume Type Number Type Reserved Threshold Data Space - ------ ------ -------- ------ -------- --------- -------- -------- MARNA1 TARGET T01 3390-3 92% 85% 0 % 0 % MARNA2 TARGET T02 3390-3 85% 85% 0 % 0 % MARNA3 TARGET T03 3390-3 86% 85% 0 % 0 % MARNA4 TARGET T04 3390-3 27% 85% 0 % 0 % OSDLB1 DLIB D01 3390-3 88% 85% 0 % 0 % OSDLB2 DLIB D02 3390-3 86% 85% 0 % 0 % OSDLB3 DLIB D03 3390-3 38% 85% 0 % 0 %******************************* Bottom of Data *********************************

� �


When you re-use a saved configuration, you already have target and DLIB volumes. Notethat the contents of several volumes (MARNA1, OSDLIB1, OSDLIB2) exceed 85% ofcapacity.

In this panel, you can use line command X (eXclude) to select volumes for removal from thework configuration (the volumes are not actually removed from the work configuration untilafter you enter the CREATE command to create the configuration). The dialog does not useexcluded volumes for data set assignments.

To have the dialog create the new configuration, enter the primary command CR and pressENTER. The panel shown in Figure 85 on page 124 is displayed, allowing you to confirmthis action before continuing.



� �CustomPac ------ Automatic Assignment Confirmation ( MD053718 ) ---------------COMMAND ==>

Scope: ALL

You have chosen to have data sets automatically assigned to physical volumes. IF YOU CONTINUE, THE ASSIGNMENTS CANNOT BE EASILY REVERSED WITHIN

MODIFY SYSTEM LAYOUT. However, you will be able to modify the configurationafter the assignments have been done. If you decide not to use theautomatic assignments after they have been done, return to CreateConfiguration, create the configuration again, and use other options inModify System Layout to tailor your configuration. You can also use theSHIP command to recreate the shipped, unmerged configuration.

Enter Y to continue, or N to return to the previous panel:

Continue ==> Y ( Y or N )

� �

Figure 85. CPPP625E - Automatic Assignment Confirmation

Be aware that the dialog organizes logical volumes very differently from the manner inwhich you assigned them in previous releases. If you attempt to use the older dialogfunctions (the Summary Display Commands) to manage the configuration after usingRecommended System Layout, you will the find the old groupings to be replaced.Therefore, use either Recommended System Layout to derive logical volumes automatically,or the Summary Display Commands to derive logical volumes manually, but not acombination of both.

To continue, press Enter. The CustomPac progress panel is displayed as volumes areassigned.

After Recommended System Layout completes, the Current Volume Configuration panel(Figure 84 on page 123) is displayed again, to show you the new configuration.

Press Enter. The following panel is displayed, showing the current configuration.






Phys. Volume Sequence Device Used + Volume Existing Reserved S Volume Type Number Type Reserved Threshold Data Space - ------ ------ -------- ------ -------- --------- -------- -------- MARNA1 TARGET T01 3390-3 85% 85% 0 % 0 % MARNA2 TARGET T02 3390-3 83% 85% 0 % 0 % MARNA3 TARGET T03 3390-3 84% 85% 0 % 0 % MARNA4 TARGET T04 3390-3 83% 85% 0 % 0 % TARG05 TARGET T05 3390-3 26% 85% 0 % 0 % OSDLB1 DLIB D01 3390-3 84% 85% 0 % 0 % OSDLB2 DLIB D02 3390-3 85% 85% 0 % 0 % OSDLB3 DLIB D03 3390-3 83% 85% 0 % 0 % DLIB04 DLIB D04 3390-3 12% 85% 0 % 0 %******************************* Bottom of Data *********************************

� �



• The new configuration required five target volumes and four DLIB volumes. Thesevolumes were assigned sequence numbers T01 through T05, and D01 through D04,respectively.

• Because the saved configuration contained several volumes that exceeded 85% ofcapacity, the dialog created two new volumes (TARG05 and DLIB04) of the defaultdevice type to reduce the use of volumes to no more than 85%. In the resultingconfiguration, all but the last volumes of each type were filled close to the threshold(85%).

Example 3: Using NEW with a Saved ConfigurationThis approach creates a new configuration by automatically assigning data sets in your orderthat are not present in your saved configuration. Follow this path if you want the dialog topreserve your saved configuration, but assign new data sets automatically. In this example,NEW is used with a configuration for which automatic assignment was not done previously.









� �


Select the NEW setting to cause the dialog to automatically assign data sets that are new tothe configuration to physical volumes. The dialog preserves the assignment of data sets thatalready exist on volumes in the saved configuration.

On the Automatic Data Set Assignment panel, you must enter either a device type or modelvolume to specify the type of device to be used if the dialog creates more volumes for dataset assignments. Check this value to ensure that the device type is available for thisinstallation. To see a list of other available devices, enter a question mark (?) in the DefaultDevice Type field and press Enter. (The list of available devices iwll contain only thedevices that have already been defined or whose characteristics have already beendiscovered.) You can then select the device type you want from the pop-up display. Aconfiguration can include more than one device type.


Press Enter. The panel shown in Figure 88 on page 127 is displayed, showing the currentconfiguration.







� �


The dialog treats data sets in the saved configuration as existing data sets, and data sets thatappear only in the new order as new data sets. Because automatic assignment has never beendone for this configuration, your existing target and DLIB volumes lack volume sequencenumbers. In this case, the dialog shows the sequence numbers for these volumes as theywould appear after an automatic assignment.

If you want the volumes to be used in a different order, use this panel to reposition thevolumes. The dialog will adjust the volume sequence numbers accordingly.

Because you limited automatic assignments to only new data sets, the dialog will use 100%of volume's capacity for existing data sets and will assign new data sets to a volume that hasreached up to 90% of its capacity. This additional space allows for the possible expansion ofexisting data sets and increases the likelihood that data sets of a given type will be placedtogether.

On this panel, you can use line command X to make a volume ineligible for the assignmentof new data sets; the volume remains in the work configuration and its existing data setassignments are left unchanged.

Enter the primary command CR on the Current Volume Configuration display to create anew configuration. The Automatic Assignment Confirmation panel is displayed, allowingyou to confirm this action before continuing.

Recommended System Layout organizes logical volumes very differently from how theywere organized in previous releases. If you attempt to use the older dialog functions (theSummary Display Commands) to manage the configuration after using RecommendedSystem Layout, you will the find the old groupings to be replaced. Therefore, use eitherRecommended System Layout to derive logical volumes automatically, or the SummaryDisplay Commands to derive logical volumes manually, but not a combination of both.

To continue, press Enter. The CustomPac progress panel is displayed as volumes areassigned. After Recommended System Layout completes, the Current VolumeConfiguration panel (Figure 88) is displayed again.







� �



• The dialog preserved the data set assignments of the saved configuration.

• The dialog automatically assigned all new target and DLIB data sets to volumes.

• The dialog created two new volumes (TARG05 and DLIB04) because the new orderwould exceed the capacity threshold of the existing volumes. The dialog restricts theother volumes from any additional data set assignments.

Example 4: Using PARTIAL with a Saved ConfigurationFollow this path if you are re-using a saved configuration and want to preserve some of yourexisting data set assignments, while allowing the dialog to reassign other existing data sets.The PARTIAL setting allows you to redistribute data sets if, after several installations withthe NEW setting, configuration volumes become overallocated (due to the normal growth ofsome configuration data sets over time).









� �


To reassign some data sets but not all, choose the PARTIAL setting. During automatic dataset assignment, the dialog reassigns all data sets on volumes that you explicitly excludethrough line command X on the next panel.

On the Automatic Data Set Assignment panel, you must enter either a device type or modelvolume to specify the type of device to be used if the dialog creates more volumes for dataset assignments. Check this value to ensure that the device type is available for thisinstallation. To see a list of other available devices, enter a question mark (?) in the DefaultDevice Type field and press Enter. (The list of available devices iwll contain only thedevices that have already been defined or whose characteristics have already beendiscovered.) You can then select the device type you want from the pop-up display. Aconfiguration can include more than one device type.


Press Enter. The panel shown in Figure 91 on page 130 is displayed, showing the currentconfiguration.







� �


To make the data sets on an existing volume (MARNA2) available for automaticassignment, enter the X line command to the left of the volume. The dialog will reassign thedata sets on this volume.

Enter the primary command CR on the Current Volume Configuration display (Figure 91)to create a new configuration. The Automatic Assignment Confirmation panel is displayed,allowing you to confirm this action before continuing.

To continue, press Enter. The CustomPac progress panel is displayed as volumes areassigned.

After Recommended System Layout completes, the Current Volume Configuration panel(Figure 92 on page 131) is displayed again.







� �



• All data set assignments except those on MARNA2 (which was excluded), werepreserved. MARNA2's data sets were reasssigned.

• Data sets on the volumes with sequence numbers T01, T03, T04, and D01-D03 werenot reassigned, but stayed where they were.

• The final volumes of each type, TARG05 and DLIB04, have increased to 76% and 55%of capacity, respectively.

If unnecessary additional volumes are created, you can reassign their data sets using thedialog's View and Change Facility (Option C on the Modify System Layout Options panel).Select "Current PVOL," select each volume in turn, and then use the CH PVOL command tomove the data sets to other volumes. For more information, see “Viewing and ChangingData Sets.”

Viewing and Changing Data SetsThe dialog provides you with a general-purpose view and change facility for working withthe data sets in your configuration. With this facility, you can view subsets of data sets inyour configuration by various attributes. Then, you can enter change or merge commandsfor these data sets, or save the lists.

For example, you can use the View and Change Facility to do the following:

• Identify your ISPF panel libraries, so that you can consolidate them through theMERGE command

• Identify your link list libraries, so that you add or remove secondary allocation amountsfor these data sets

• Identify all unrenameable data sets, or those required in the master catalog, and changetheir status



• Identify all new data sets. This list is useful, for example, when adding security systemdefinitions, updating production PROCs, and in determining what new entries areneeded in production master catalogs during migration.

To access the View and Change Facility, select Option C from the Modify System LayoutOptions panel. A panel with a list of possible attributes from which to select is displayed, asshown in Figure 93 on page 133.

Generally, the process of viewing and changing data sets in the work configuration followsthis flow:

1. Choose the attribute to display. For example, assume that you want to view only thedata sets in your configuration that can be placed in the link pack area (LPA). Here, youbegin by choosing the "LPA Eligible" attribute.

2. Narrow the scope of the display to only those data sets having one or more possiblevalues for the attribute. In this example, only two values are possible — YES and NO.To list only the LPA-eligible data sets, choose the value YES for the attribute "LPAEligible."

3. The resulting panel displays the list of data sets that match your criteria. From thisdisplay, you can enter CHANGE or MERGE commands for some or all of the data setsin this list, or you can save the list to a separate file for later examination. If you changeor merge data sets, your actions become effective when you save the changes and exitthe Modify System Layout function of the dialog.

You can change data sets in various ways, including the following examples:

• Data set names and high level qualifiers• DASD volumes to which data sets are assigned• Making unrenameable data sets renameable.

For information about the CHANGE command, see “Making Changes to Data Sets” onpage 137.

Figure 93 on page 133 shows the panel that is displayed when you access the dialog's Viewand Change Facility (Option C on the Modify System Layout Options panel).



� �CustomPac ------------- Select Data Set View ( MD053718 ) ---------------------COMMAND ==> SCROLL ==> PAGE

Select a Data Set List View:

Primary Commands: (?)Line Commands: (Select)

S Display Data Set List Description - --------------- ---------------------------------------------------------

APF Required APF Authorization Required (Yes or No)Category DLIB, Target, OperationalCurrent LVOL Assigned Logical VolumeCurrent PVOL Assigned Physical VolumeCylinders Current Data Set Size in CylindersData Set Origin Origin of data sets (IBM or User-Defined)Data Set Type HFS, PDSE, PDS, SEQ, VSAM or ZFSDevice Type Assigned device typeDDDEF Name Owning Product DDDEF NameElement type Data Set Element Type (LMOD, PNLENU, EXEC, etc.)HLQ Data Set High Level QualifiersLNKLST Eligible Eligible for Placement in the Link List (Yes or No)LPA Eligible Eligible for Placement in LPA (Yes or No) No)LPA Required Required in LPA List (Yes or No)LRECL Logical Record LengthMaster Catlg Must be in Master Catalog (Yes, No or Overridden)Merge Status Merged and unmerged data setsMount Point Unix File System Mount Point )New Data Set Whether data set is new in this order (Yes or No)Product Name Name of the product, feature or element n)Renameable Whether rename is allowed (Yes, No or Overridden)RECFM Record Format (FB, VB, U, etc.) s or No)Secondary Space Whether secondary space is allowed (Yes or No)Switchable Can be changed between PDS/PDSE or HFS/zFS (Yes orNo) Required Whether data set must be SMS-managed (Yes or No)

s SMP/E SYSLIB Data set in SMP/E SYSLIB concatenation (Yes or No)SMS-Eligible Whether data set may be SMS-managed (Yes or No) or No)SMS-Managed Whether data set is SMS-managed (Yes or No)SMS-Required Whether data set must be SMS-managed (Yes or No)SST Subsystem Type (MVS, CICS, DB2, IMS, NCP)Tracks Current Data Set Size in TracksTVOL Special target volume placement (FIRST or LAST)Unit Assigned UnitVolume Number Volume Sequence Number (Tnn, Dnn, and Bnn)************************** Bottom of Data **************************

� �

Figure 93. CPPP605R - Select a Data Set View

The list of attributes is scrollable. You can view data sets by any single attribute; you cannotselect more than one attribute at a time. In Figure 93, the attribute "Data Set Origin" isselected; this is the first step in displaying a list of the data sets that are IBM-shipped orUser-Defined.

Use the Select line command to select an attribute to display and press Enter. The dialogdisplays a second panel with the values found for the selected attribute. In Figure 94 onpage 134, for example, the value IBM is selected for the attribute Data Set Origin.



� �CustomPac ----------- Select Values to Display ( MD053718 ) ---- Row 1 to 2 of 2COMMAND ==> L SCROLL ==> CSR

Select list for: Data Set Origin

Select values for which data sets are to be listed and press Enter

Primary Commands:(?)Line Commands:(Select SS)

S Values -- ----------------------------------------

IBMUser-Defined

*******************************Bottom of Data*********************************

� �

Figure 94. CPPP605S - Select Values to Display

The dialog displays only values that are applicable to the order. For example, if you attemptto display the Data Set Origin data sets in an order that does not contain User-Defined datasets, the only displayed value is IBM.

For the Values section, IBM indicates IBM-defined data sets while User-Defined indicatesuser-defined data sets.

Select the values for the attribute to display and press Enter. The dialog displays a list of thedata sets that satisfy your search criteria. The values you selected are shown, along with thephysical volumes for the data sets. For example, in Figure 95, the dialog displays the datasets that are shipped with your order by IBM.

� �CustomPac --------------- Data Set List ( MD053718 ) -------- Row 1 to 3 of 3COMMAND ==> SCROLL ==> CSR

Data Set List for: SMP/E SYSLIB

Primary Commands:(? SET Locate Find Next Previous SORT CHange OFile OListFindComp)

Line Commands:(Merge eXpand Conflict Unmerge Select Insert Delete)

PhysicalS Data Set Name Selected Value Volume- -------------------------------------------- ----------------------- --------

ACFNCP.ANCPMAC1 IBM MVSRESACFNCP.SNCPMAC1 IBM MVSRESACFNCP.SSPCLS1 IBM MVSRES****************************** Bottom of Data *****************************

� �

Figure 95. CPPP605U - Data Set List

From this panel, you can make a number of changes to the data sets shown. For example,you could change all the displayed IBM-defined data sets to set their secondary spaceallocation to zero (see “Making Changes to Data Sets” on page 137). Your changes affectonly the data sets that you select from the list.


?, SET, L, F, N, P, SORTThese are standard commands for panels that display lists. See “The PrimaryCommands” on page 9.



CHANGEThis command, abbreviated as CH, is used to make changes to data sets in display lists.Use CHANGE to modify the various attributes and space requirements of multiple datasets. For information about the CHANGE command, see “Making Changes to DataSets” on page 137.

OFILEThis command writes this data set list to a user-defined file. For information about theOFILE command, see “OFILE Command” on page 12.

OLISTThis command, abbreviated as OL, writes the list of data sets to the ISPF LIST data set.

FCThis command helps you find a particular component data set among your merged datasets — which can be useful, if you forget where you put the data set. Use this commandto search on the shipped name of the data set or its modified name, using a full or partialdata set name as input (as described in “Finding "Lost" Component Data Sets” onpage 160).

The following line commands are valid for this panel:

Merge-related commands, as follows:

M Starts the data set merge process by presenting a list of the currentlydisplayed data sets that you can choose to merge into the selected dataset. For more information, see “Merging and Unmerging Data Sets”on page 150.

X Expands the display of a merged data set to show its component datasets. The components of a merged data set are displayed in ascrollable pop-up window that allows you to review the attributes andspace of the individual component data sets. This display also allowsyou to unmerge specific component data sets. For more information,see “Merging and Unmerging Data Sets” on page 150.

C Displays any data sets (in a scrollable pop-up) that contain at least onemember with the same name as the selected data set. The dialogautomatically excludes these data sets from the Merge Candidatespanel for the selected data set.

U Unmerges the entire merged data set into its original, component datasets. For more information, see “Merging and Unmerging Data Sets”on page 150.

S Displays a panel on which you can change a particular data set attributes. See“Modifying a Data Set's Attributes” on page 162.

I Displays a panel on which you can add user-defined data sets. See “Defining newuser data sets” on page 171.

D Displays a panel on which you can confirm the request to delete the user-defineddata set. You cannot delete IBM supplied data sets. See “Deleting user-defineddata sets” on page 178.

| If you select SMS Classes in Figure 93 on page 133 Figure 96 on page 136 will be| displayed with three values : Data Class, Management Class and Storage Class.



| �| �| CPPP605S ----------- Select Values to Display ( MD053718 ) ---- Row 1 to 2 of 2| COMMAND ==> SCROLL ==> CSR

| Select list for: SMS Classes

| Select values for which data sets are to be listed and press Enter

| Primary Commands:(?)| Line Commands:(Select SS)

| S Values| -- ----------------------------------------| Data Class| Management Class| Storage Class| *******************************Bottom of Data*********************************

| �| �

| Figure 96. CPPP605S - Panel: Select values to display

| If you select the Storage class, Data Class and Management Class options, then Figure 97| will be displayed with with Dataset name, Selected value and Class name. If the data sets| are SMS Managed but ACS controlled, *ACS* will be displayed under column Class Name.

| �| �| CPPP60E4 ----------- Select Values to Display ( MD053718 ) ---- Row 1 to 2 of 2| COMMAND ==> SCROLL ==> CSR

| Data Set List for: Data Class

| Primary Commands:(? SET Locate Find Next Previous SORT CHange OFile OList| FindComp)| Line Commands:(Merge eXpand Conflict Unmerge Select Insert Delete)

| Class| S Data Set Name Selected Value Name| -- ---------------------------------------- -------------------- ---------| AOK.AAOKHFS Data Class DATA| OMVS.JAVA31M1 Data Class DCVSAMEX| *******************************Bottom of Data*********************************

| �| �

| Figure 97. CPPP60E4 - Panel: Data set list

| If you select both Storage Class and Data Class from Figure 96, then Figure 98 on| page 137 will be displayed with a list of data sets that have assigned selected Class. In this| scenario, if you issue the Global Change command, it will not be executed and the following| message will be displayed:

| CPP0605241E Global change command for SMS classes can only be used when| selecting a single class from the Class Selection view.

| It will be supported only if 'Storage Class' , Data Class or Management Class is Selected.



| �| �| CPPP60E4 CMD -------- Select Values to Display ( MD053718 ) ---- Row 1 to 2 of 2| COMMAND ==> SCROLL ==> CSR

| Data Set List for: Data Class and Storage Class


| Class| S Data Set Name Selected Value Name| -- ---------------------------------------- -------------------- ---------| AOK.AAOKHFS Storage Class SMSDCLAS| AOK.AAOKHFS Data Class DATA| OMVS.JAVA31M1 Data Class DCVSAMEX| OMVS.JAVA31M1 Storage Class TEST02| *******************************Bottom of Data*********************************

| �| �

| Figure 98. CPPP60E4 - Panel: Data set list

| If you select option SMS ACS in Figure 96 on page 136, Figure 99 will be displayed with| values Yes and No. If you select Yes, then Figure 95 on page 134 will be displayed with| with Data Set Name, Selected Value and Physical Volume. 'ACS' will be displayed in| physical volume column If you select No, the same CPPP605U panel will be displayed, but| the physical volume column displays *SMS*/Physical Volume.

| �| �| CPPP605S CMD -------- Select Values to Display ( MD053718 ) ---- Row 1 to 2 of 2| COMMAND ==> SCROLL ==> CSR

| Select list for: SMS ACS

| Select values for which data sets are to be listed and press Enter

| Primary Commands:(?)| Line Commands:(Select SS)

| S Values| -- ----------------------------------------| No| Yes| *******************************Bottom of Data*********************************

| �| �

| Figure 99. CPPP605S - Panel: Select values to display

| The following line commands are valid for this panel:

| S Selects the value for which configuration data sets are to be displayed.

| SS Selects a range of values for which configuration data sets are to be displayed.

| If you use line command SS and S more than once, then the global Change command will be| disabled from the resulting Data Set List panel (CPPP605U).

Making Changes to Data SetsYou can use the CHANGE command to change the data sets displayed in a list, such as inthe dialog's View and Change facility. Use this command to do the following:

• “Changing Data Set Names” on page 139• “Making Unrenameable Data Sets Renameable” on page 141• “Changing Data Set Types” on page 141• “Changing the SMS Management Status” on page 143



• “Overridding the Master Catalog Requirement for Data Sets” on page 144• “Changing Physical Volumes” on page 145• “Changing Logical Volumes” on page 146• “Allocate secondary space for data sets shipped with no” on page 146• “Changing Data Set Space Values” on page 147.

Based on the parameters you specify on your change command, the dialog checks the datasets in the current display list and returns a candidate list of data sets that would be changedby the command. At this point, changes are only simulated; no data sets have actually beenchanged.

For example, Figure 100 shows a candidate list that simulates a change to data set types (forthe CHANGE TYPE command).

� �CustomPac ------------- Modify System Layout ( MD053718 ) ----- ROW 1 TO 4 OF 22COMMAND ==> SCROLL ==> CSR

GLOBAL Change - Candidate List Change: Type

Primary Commands:(? SET Locate Find Next Previous SORT CANcel)Line Commands:(eXclude)

DS P.Volume/ Seq LogicalS Data Set Name (Old New) Type SMS STORCLAS No. Volume- -------------------------------------------- ----- --- --------- --- -------

AOP.AAOPEXEC PDS N DLIB02 D02 DLB308AOP.AAOPEXEC PDSE N DLIB02 D02 DLB308-------------------------------------------- ----- --- --------- --- -------AOP.AAOPHFS PDS N MVSDLB D01 DLB318AOP.AAOPHFS PDSE N MVSDLB D01 DLB318-------------------------------------------- ----- --- --------- --- -------AOP.AAOPMENU PDS N DLIB02 D02 DLB308AOP.AAOPMENU PDSE N DLIB02 D02 DLB308-------------------------------------------- ----- --- --------- --- -------AOP.AAOPPENU PDS N DLIB02 D02 DLB307AOP.AAOPPENU PDSE N DLIB02 D02 DLB307-------------------------------------------- ----- --- --------- --- -------

� �

Figure 100. CPPP6050 - Global Change - Candidate List for Data Set Attributes

You now must determine whether to commit the changes as shown in the display, cancelyour change request, or exclude particular data sets from the candidate list beforecommitting the changes. For example, the data sets shown in Figure 100 are currently inPDS format. Committing this change, however, the data sets to be converted to PDSEformat (PO-E).

To commit the changes, press Enter or End. To cancel the changes, enter the CANCELcommand and press Enter.

Figure 101 on page 139 shows an example of a candidate list that is displayed for changesto data set space values (for the CHANGE SPACE command).



� � CustomPac ------------- Modify System Layout ( MD053718 ) -- ROW 1 TO 4 OF 22 COMMAND ==> SCROLL ==> PAGE

GLOBAL Change - Candidate List Change: Space

Primary Commands:(? SET Locate Find Next Previous SORT CANcel)Line Commands:(eXclude)

Primary Secondary Directory S DSName (Old New) Tracks Tracks Blocks - -------------------------------------------- ---------- ---------- ---------

AOP.AAOPHFS 144 21 10AOP.AAOPHFS 216 21 10-------------------------------------------- ---------- ---------- ---------ASMT.V1R2M0.AASMBOK2 1714 184 100ASMT.V1R2M0.AASMBOK2 2571 184 100-------------------------------------------- ---------- ---------- ---------ASMT.V1R2M0.AASMSHF2 728 121 160ASMT.V1R2M0.AASMSHF2 1092 121 160-------------------------------------------- ---------- ---------- ---------ASMT.V1R2M0.SASMBOK2 838 98 80ASMT.V1R2M0.SASMBOK2 1257 98 80-------------------------------------------- ---------- ---------- ---------

� �

Figure 101. CPPP6057 - Global Change - Candidate List for Data Set Space Values

Any changes that you make to merged data sets through the CHANGE command areapplicable to their component data sets. These changes are retained even if you laterunmerge the data set.


?, SET, F, L, N, P, SORTThese are standard commands for panels that display lists. See “The PrimaryCommands” on page 9.

CANCELThis command, abbreviated as CAN, discards any changes that you have made to thedata sets.


X Excludes the selected data set from the list of data sets to be changed. The data setis not changed if the change is committed.

Changing Data Set NamesYou can use the CHANGE DSNAME command to modify a string of characters in a dataset name. The dialog checks the new data set name to ensure that it is a valid MVS data setname and conforms to CustomPac standards. Be aware that if you change the high levelqualifier of a data set, you might need to re-establish its catalog and SMS relationships.

Only data sets that are allowed to be renamed are displayed in the candidate list that resultsfrom a CHANGE DSNAME command. For information about unrenameable data sets, see“Making Unrenameable Data Sets Renameable” on page 141.



Command Syntax

CHANGE DSNAME source target

DSNAME This may be abbreviated to DSN or D

source This is the character string to be searched for

target This is the character string to be substituted for the source.

Example

For all data set profiles in the current Display LIST you want to change character stringISP.V3R5M0 to GLANDALE.ISP

CH D ISP.V3R5M0 GLANDALE.ISP

So ISP.V3R5M0.ISPPLIB would be changed to GLANDALE.ISP.ISPPLIB

LOW Level Qualifier

Generally you are NOT ALLOWED to change the LOW LEVEL QUALIFIER of the dataset profile name.

For SMP/E managed data sets CustomPac forces the SMP/E DDDEF name to be the sameas the low level qualifier.

There are a few data sets that are NOT SMP/E managed (Eg. IPO data sets) to which thisrule does not apply.

The Low level qualifier may be changed.

HIGH Level Qualifier

Use care in entering the CHANGE DSNAME command because it replaces all occurrencesof the source string in the names of your data sets. For example, assume that you want torename data set CBC.SCBCMOD1 to XXX.SCBCMOD1. If you enter the CHANGEDSNAME command as follows:

CH DSN CBC XXX

the resulting data set name is XXX.SXXXMOD1, which is probably not what you wanted.Here, to make the correct change, you must include the period (.) with the source string, asfollows:

CH DSN CBC. XXX.

The resulting data set name is XXX.SCBCMOD1.

When renaming a data set, limit the names of non-VSAM data sets to 35 characters, andlimit the names of VSAM data sets to 29 characters. These limits allow data set names to beexpanded during some phases of the installation:

• For non-VSAM data sets, names of no more than 35 characters allow the dialog to addan eight-character SSA, plus the period between qualifiers, without exceeding the dataset name limit of 44 characters.

• For VSAM data sets, names of more than 29 characters allow the dialog to add aneight-character SSA plus a period, and allow the system to add ".INDEX" and ".DATA"



to the data set component names without exceeding the VSAM data set componentname limit of 44 characters.

Your changes cannot exceed the 44-character limit for data set names. If they do, an errormessage is issued.

Making Unrenameable Data Sets RenameableOnly data sets that are allowed to be renamed are displayed in the candidate list for aCHANGE DSNAME command. Data sets that normally cannot be renamed include thefollowing:

• CSSLIB• LINKLIB• PROCLIB• MIGLIB• LPALIB• SVCLIB• NUCLEUS

For a complete list of unrenameable data sets in the configuration, enter the dialog's Viewand Change Facility and display data sets with a renameable attribute of NO.

You can use the CHANGE RENAME command to make data sets renameable. From anydata set list, enter the CHANGE RENAME command, as follows:

CH RENAME Y

Then, exclude any data sets that you do not want to rename and press Enter.

The data set display is updated to show the renameable attribute of these data sets as"Overridden."

To reverse the preceding action, display only the data sets having a renameable value of"overridden." Then, enter the CHANGE RENAME command as follows:

CH RENAME N

Unlike other changes you make to data sets, the dialog does not preserved the "overridden"value when you later save the configuration for use with future orders.

Changing Data Set TypesYou can use the CHANGE DSNTYPE command to convert your shipped order's data sets toa different format:

• PDS data sets to PDSE data sets• PDSE data sets to PDS data sets (This can be donw only for data sets that were

originally PDS data sets)• HFS data sets to zFS data sets• zFS data sets to HFS data sets

You can abbreviate the CHANGE DSNTYPE command as CH TYPE or CH T.

The main advantage of using a PDSE over a partitioned data set is that a PDSE uses DASDspace more efficiently. The size of a PDS directory is fixed, regardless of the number ofmembers in it, while the size of a PDSE directory is flexible and expands or contracts to fitthe stored members. Also, PDSEs do not need to be compressed.



PDSEs offer other functional benefits, too, such as the ability to store program objects ordata. For a complete description of PDSEs and their restrictions, see z/OS DFSMS: UsingData Sets, SC26-7410.

A zFS data set is a VSAM Linear Data Set (LDS), which offers some performance and filesharing features not available in HFS.

The dialog displays only those data sets that are allowed to be changed. The dialog doesnot, for example, allow you to convert your order's PDSE data sets to PDS data sets becausethey contain members that cannot be loaded into a PDS. You can convert a PDSE data setto a PDS only when the PDSE was originally shipped as a PDS data set.

The dialog displays only those data sets that are allowed to be changed. The dialog does notallow you to change a data set's type if any of the following are true:

• The data set was originally shipped as a PDSE• Record format (RECFM) is U• Logical volume is IPLVOL.

You can use the dialog's View and Change Facility to display a list of data sets that can bechanged. In View and Change, select "Switchable" and then select "Yes" to get the list.

The dialog does not enforce all product requirements. You must determine whether data setsare allowed to be PDSEs before changing them.

Some system data sets are shipped in PDS format and must remain as such. The followingsystem data sets, for example, cannot be converted to PDSE format:

• SYS1.NUCLEUS• SYS1.SVCLIB• Data sets listed in the LPALSTxx member of parmlib• Master JCL data sets, such as:

− PARMLIB data sets− Procedure libraries concatenated to IEFPDSI or IEFJOBS− BRODCAST− SYS1.UADS

• DB2 DBRM data sets.

Examples of Using the CHANGE DSNTYPE Command: To change PDS data setsto PDSE data sets, enter the CHANGE DSNTYPE command as follows:

CH TYPE PDS PDSE

To change HFS data sets to zFS data sets, enter the CHANGE DSNTYPE command asfollows:

CH TYPE HFS ZFS

| Multiple data sets can be changed from type HFS to ZFS. The panel CPPP6050 will be| displayed with a warning message indicating the zFS data set size is greater than 4 GB (if| there is any such data set in the system) and must use an SMS Data Class that supports| extended addressability, so that you can exclude some of the candidate data sets in the list. If| you want to continue with the zFS file system data type, then panel CPPP60E3 will be| displayed to collect SMS information. If there are no data sets with size greater than 4 GB,| then the warning message will not be displayed.

| But for a z/OS V2R1 Driving System, if a data set is not SMS managed, it will not be| changed to SMS managed. Panel CPPP60E7 will be displayed to collect the Data Class. If a



| data set is SMS managed, panel CPPP60E3 will be displayed to update SMS information| and to collect SMS Data Class.

Overriding Secondary Allocation FlagCustomPac ships the link list data sets with no secondary space allocations. The CHangeSECOND command allows you to override this and allocate secondary space for these datasets. Only the data sets in the list that were originally shipped with no secondary are eligibleto have secondary space allocation changed. This command has no effect on data sets withshipped secondaries. For instance, if you use the CHange SECOND Y command to allocatesecondary spaces for data set that were shipped with no secondary space, you cansubsequently use the CHange SECOND N command to restore the no secondary attribute.You cannot, however, use this CHange SECOND N command to restore the no secondaryattribute for data sets that were shipped with secondary space allocated.

You can eXclude data sets from this list.

Examples: To override the no secondary attribute for a data set, enter the CHangeSECOND command, as follows:

CH SECOND Y

Then, exclude any data sets for which you do not want to change the secondary spaceattribute and press Enter.

To reverse the preceding action, display only the data sets having a secondary space attributevalue of "overridden." Then, enter the CHANGE SECOND command as follows:

CH SECOND N

Changing the SMS Management StatusYou can use the CHANGE SMS command to change the SMS management status of datasets in your work configuration. You can abbreviate CHANGE SMS as CH SMS.

The dialog displays only those data sets that are allowed to be changed.

Use valid SMS storage classes for any data sets that you assign to SMS management, andensure that these classes are defined before running installation jobs that allocateSMS-managed data sets. For information on assigning SMS storage classes, see “Changingan SMS storage class” on page 185.

Also, when you later examine the installation jobs, ensure that the SMS attributes assignedby the installation jobs are acceptable and will allow the system to be used if you plan to IPLit.

If you use SMS to manage the data sets in your order configuration, the userid that you lateruse to submit the installation jobs requires at lease READ access to the FACILITY classprofile for STGADMIN.IGG.DIRCAT.

To see which data sets in your configuration are eligible for SMS-management, use thedialog's View and Change Facility. Be aware that you cannot assign data sets that mustreside on the IPLVOL logical volume to SMS-managed logical volumes.

You cannot use the dialog to assign catalog data sets to SMS management. To use SMS tomanage your catalogs, you must do one of the following:

• Modify the CustomPac installation jobs to allocate the catalogs properly• Use pre-allocated SMS-managed catalogs



• Have your ACS routines redirect the allocation of the catalogs to SMS-managedvolumes.

Be aware that the dialog allows you to change the SMS status for all eligible data sets,regardless of whether such changes make the best sense for your particular installation.Therefore, it is important that you carefully consider the consequences of using SMS tomanage your target data sets and operational data sets, such as the following:

• For a full system replacement, SMS-managed data sets on your driving system are noteasily accessible from the target system before you run the CATCVTM and CATCONVinstallation jobs.

• SMS-managed data sets on your target system are not easily accessible from the drivingsystem after you run clean-up jobs, DELDSN and DELSSA.

• When you re-assign a data set to SMS management, the dialog does not automaticallyremove the VOLUME parameter from JCL in jobs that allocate or locate the data set.Depending on your SMS configuration, you might have to remove the VOLUMEparameter from jobs that allocate or locate SMS-manage data sets.

The installation jobs and post-installation jobs for your CustomPac order are described inSystemPac: Installation Guide.

To add unmanaged data sets to SMS management, enter the CHANGE SMS command, asfollows:

CH SMS Y

This command activates SMS management for any data sets in the "hit list" that are notalready managed by SMS. Y or YES is accepted in any combination of uppercase andlowercase letters.

To remove data sets from SMS management, enter the CHANGE SMS command, asfollows:

CH SMS N

This command removes from SMS management any data sets in the "hit list" that arecurrently managed by SMS. N or NO is accepted in any combination of uppercase andlowercase letters.

Overridding the Master Catalog Requirement for Data SetsSome data sets in your order are required to be defined in your system's master catalog. Ifnecessary, you can usually override this requirement through the dialog's CHANGE MCATcommand.

To override the master catalog requirement for data sets in your configuration, do thefollowing:

• Use the dialog's View and Change Facility to display data sets with a Master Catalogattribute of 'Yes'. You cannot change data sets having a Master Catalog attribute of 'No'.

• From the list of master catalog data sets, enter the CHANGE MCAT command asfollows:

CH MCAT N

• Exclude any data sets that you do not want to change (through line command X) andpress Enter.



• Press Enter or End to refresh the display. The overridden data sets are removed from thelist.

To view the overridden data sets in your configuration, return to the selection list for mastercatalog data sets and display data sets having a Master Catalog attribute of 'Overridden'.

To reverse the preceding action, display the data sets having a Master Catalog value of'Overridden.' Then, enter the CHANGE MCAT command as follows:

CH MCAT Y

After excluding any data sets that you do not want to change, and press Enter. Then, pressExit to refresh the display. The changed data sets are removed from the list.

Changing Physical VolumesYou can use the CHANGE PVOL command to reassign data sets to a different DASDvolume. If the volume serial you enter is known to the dialog, the data sets are assigned to it.If there is enough space remaining on the volume for the data sets, no other actions areneeded.

If the volume serial that you enter is not known to the dialog, then:

• If DYNAMIC DASD INFO is set to Yes (the default), the dialog tries to dynamicallyretrieve the physical attributes of the device. If this is successful, the Global ChangeCandidate List panel (CPPP6050) is displayed.

− If the dialog cannot dynamically retrieve the device information, but the dialogexpects the device to be offline, the dialog accepts the input on the command anddisplays the Global Change Candidate List panel. The dialog will not require thevolume to be online, but will recheck volume availability during some operationsand, if the volume has become available, it will verify the volume's attributes andcorrect them, if necessary.

− If the dialog does not expect the device to be offline, then you must either press theEnter key to tell the dialog that the device is expected to be offline and to accept theinput and display the Global Change Candidate List panel, or press the End key todiscard the input and cancel the command.

• If DYNAMIC DASD INFO is set to No, the device type is set to 3390-9 and the devicenumber is set to CCUU.

Enter the CHANGE PVOL command as follows:

CH PVOL TARGET|DLIB|OPERATIONAL value

where:

TARGET|DLIB|OPERATIONALSpecifies the type of data sets are to be reassigned. You can use thefollowing abbreviations: T or TARG, D or DLIB, and O or OP.

value Specifies the physical volume to which the data sets are to be reassigned.

You cannot use this command to reassign SMS-managed data sets or data sets that mustreside on the IPL volume.



Changing Logical VolumesYou can use the CHANGE LVOL command to reassign data sets to a different logicalvolume. You can abbreviate the CHANGE LVOL as CH LV or CH L.

The dialog displays only those data sets that are allowed to be reassigned.

Command Syntax

CHANGE LVOL source target

LVOL This may be abbreviated to LV or L

source This is the name of the Logical Volume to which data set profiles arealready assigned.

target This is the name of the Logical Volume to replace the sourceLogical Volume.

If the target Logical Volume is an EXISTING Logical Volume, thenthe device attributes will be inherited from the target.

If the target Logical Volume is NOT YET DEFINED, then thedevice attributes will be inherited from the source.

Example

For all data set profiles in the current Display LIST you want to change Logical VolumeRES001 to RES999

CH L RES001 RES999

Restrictions on the CHANGE LVOL Command: You cannot assignnon-SMS-eligible data sets to SMS-managed logical volumes. Nor can you assignSMS-required data sets to logical volumes that are assigned to physical volumes.

Also, observe that the following logical volume names are reserved for the system's use:

CSIVOL Reserved for the CSI data sets that are used to hold the DLIB and targetzones for the ordered features and elements.

IPLVOL Reserved for data sets that must reside on the IPL volume.

You cannot specify either of these names in the source or target positions of a CHANGEcommand. If you do so, your request is rejected with an error message.

Allocate secondary space for data sets shipped with nosecondary space

CustomPac ships the link list data sets with no secondary space allocations. The CHangeSECOND command allows you to override this and allocate secondary space for these datasets. Only the data sets in the list that were originally shipped with no secondary are eligibleto have secondary space allocation changed. This command has no effect on data sets withshipped secondaries. For instance, if you use the CHange SECOND Y command to allocatesecondary spaces for data set that were shipped with no secondary space, you cansubsequently use the CHange SECOND N command to restore the no secondary attribute.You cannot, however, use this CHange SECOND N command to restore the no secondaryattribute for data sets that were shipped with secondary space allocated.



You can eXclude data sets from this list.

Command Syntax

CHANGE SECOND Y|N

Y Override the no secondary attribute for selected data sets. When youissue the CH SECOND Y command, secondary space is set to avalue that is 10% of the primary for the selected data sets shippedwith no secondary space.

N Restore the no secondary attribute for selected overridden data sets.

Example

To override the no secondary attribute for a data set, enter the CHange SECONDcommand, as follows:

CH SECOND Y

Then, exclude any data sets for which you do not want to change the secondary spaceattribute and press Enter.

To reverse the preceding action, display only the data sets having a secondary spaceattribute value of "overridden." Then, enter the CHANGE SECOND command asfollows:

CH SECOND N

Restrictions on the CHANGE SECOND Command: You can only use thesecommands with data set that were shipped with no secondary space allocated.

Changing Data Set Space ValuesThe global change command may be used to -

• Increment or decrement the primary space needed for a data set profile.

• Increment or decrement the secondary space needed for a data set profile.

• Make the secondary space needed for a data set profile a fixed percentage of theprimary space.

• Increment or decrement the number of directory blocks needed for a PARTITIONEDdata set profile.

The dialog displays only those data sets that are allowed to be changed.



Command Syntax

CHANGE SPACE privalue secvalue dirbs

SPACE This can be abbreviated to SP or S

privalue This specifies the PERCENTAGE by which to increase or decreasethe current primary space value.

To INCREASE the space specify a percentage, which must be aninteger in the range +1 through +100.

• The prefixed PLUS sign is OPTIONAL.

To DECREASE the space specify a percentage, which must be aninteger in the range -1 through -50.

• The prefixed MINUS sign is MANDATORY.

An asterisk Q may be specified, which indicates that the primaryspace is NOT to be changed, but other parameters may have beenspecified.

secvalue This specifies the PERCENTAGE by which to increase or decreasethe current secondary space value, or specifies the fixedPERCENTAGE of the primary space to make the secondary space.





To make the secondary space a fixed percentage of the primary spacespecify the percentage, which must be an integer in the range P1through P100.

• The prefixed P is MANDATORY.

To set secondary space to zero, specify P0.

An asterisk Q may be specified, which indicates that the secondaryspace is NOT to be changed, but other parameters may have beenspecified.



Command Syntax ... continued

CHANGE SPACE privalue secvalue dirbs

dirbs This specifies the PERCENTAGE by which to increase or decreasethe current number of directory blocks.





An asterisk Q may be specified, which indicates that the directoryblocks are NOT to be changed, but other parameters may have beenspecified.

Restrictions on the CHANGE SPACE Command

• You cannot decrease the primary space for a data set profile to a value LESS than theshipped value. So, if the resulting primary space value is LESS than the shipped value,the shipped value is used.

• For user-defined data sets, you cannot decrease the primary space allocation to less thanit was when you first defined it. You can increase the amount, but you cannot reduce itunless you delete the data set and redefine it with a smaller space allocation.

• If the current secondary space allocation for a data set profile is ZERO, then it willremain at ZERO.

• You cannot decrease the number of directory blocks for a data set profile to a valueLESS than the shipped value. So, if the resulting directory blocks are LESS than theshipped value, the shipped value is used.



Example(s)

For all data set profiles in the current Display LIST you want to increase the primaryspace by 20% and the secondary space by 50%

CH S 20 50 (or CH S +20 +50)

For all data set profiles in the current Display LIST you want to decrease the primaryspace by 10% and increase the secondary space by 25%

CH S -10 25 (or CH S -10 +25)

For all data set profiles in the current Display LIST you want to decrease the primaryspace by 15% and make the secondary space 40% of the primary space.

CH S -15 P40

For all data set profiles in the current Display LIST you want to make the secondaryspace 30% of the primary space.

CH S Q P30

For all data sets in the current display list, you want to remove the secondary spacealtogether (for example, for LNKLST eligible data sets).

CH S Q P0

For all data set profiles in the current Display LIST that have a data set organisation ofPARTITIONED you want to increase the number of directory blocks by 40%.

CH S Q Q 40

Merging and Unmerging Data SetsThe dialog allows you to simplify your new configuration by merging some of the PDS andPDSE or HFS and zFS data sets in your order (see “Merging Unix File System Data Sets”on page 152). You can merge target data sets to reduce the number of libraries with similarattributes and uses. For example, you can merge ISPF panel libraries to consolidate them.Later, when you save your configuration through the Save Configuration command (seeChapter 15, “Saving the Configuration” on page 211), the dialog also saves the data foreach merged data set and its component data sets. The merged data sets are then availablefor merging with future CustomPac orders.

Unmerging a data set causes its attributes and space allocations to revert to their pre-mergevalues, with the exception of changes made to merged data sets through the CHANGEcommand (these are retained). Therefore, to avoid possible extra work, you shouldcomplete all merges and unmerges before going on to modify the attributes and spaceallocations of your merged data sets (as described in “Modifying a Data Set's Attributes” onpage 162).

While you can merge data sets from any data set list panel, you can use this function mosteffectively from the dialog's View and Change Facility (described in “Viewing andChanging Data Sets” on page 131). Use the View and Change Facility to create lists oftarget data sets for merging, so that you spend less time excluding individual data sets frommerges.

The merge and unmerge functionality is available for user-defined data sets as target-datasets.



When you select a data set profile from the Summary of Data Sets panel for merging(through the M line command), the Data Set Merge Candidates panel shown in Figure 102on page 151 is displayed.

� � CustomPac ------------- Modify System Layout ( MD053718 ) --- ROW 1 TO 9 OF 9

Data Set Merge Candidates for BFS.SBFSPLIB

Primary Commands:(? SET Locate Find Next Previous SORT Merge)Line Commands:(Information Select Conflict)

Element DS MCAT IPL S Data Set Name Type Type Reqd Vol APF - -------------------------------------------- ----- ----- ----- --- ----

EOY.SEOYPENU PNLENU PDS N N NGIM.SGIMPENU PNLENU PDS N N NICQ.ICQPLIB PNLENU PDS N N NIOE.SIOEPNLE PNLENU PDS N N NSYS1.DGTPLIB PNLENU PDS N N NSYS1.SBPXPENU PNLENU PDS N N NSYS1.SCBDPENU PNLENU PDS N N NSYS1.SICEPENU PNLENU PDS N N N**************************** BOTTOM OF DATA ********************************

� �

Figure 102. CPPP605M - Data Set Merge Candidates

This panel shows the data sets that are eligible for merging with the selected data set (thetarget data set). Enter Information to the left of a candidate data set and press Enter to getinformation about data set attributes. Enter Select to the left of candidate data sets to selectthem for merging with the target data set.

In the Merge Candidates panel, observe the following:

• The Element Type column displays the SMP/E element type of the data set, or one ofthese values:

− LMOD, for load libraries and PDSEs containing program objects− DLIB, for distribution libraries.

For information about SMP/E element types, see SMP/E Reference, SA22-7772.

• The DS Type column displays the data set type.

• The MCAT Reqd column displays a Y if the data set must be cataloged in the mastercatalog.

• The IPL Vol column displays a Y if the data set resides on the IPLVOL logical volume.

• The APF column displays a Y if the data set requires APF authorization.

Not all data sets can be merged, The dialog restricts you from some, but not all, mergeoperations that would result in configurations that would be unworkable, lack importantfunctions, or perhaps even be impossible to IPL. Specifically, the dialog prevent you frommaking the following type of merges:

• Merging libraries that are required in the LPA with libraries that cannot reside in theLPA.

• Merging libraries that are eligible to reside in the LPA with that libraries that cannotreside in the LPA.

• Merging libraries that are eligible to reside in the link list concatenation with librariesthat cannot reside in the link list.

• Merging data sets shipped with no secondary space with data sets with secondary space.



Also, the dialog prevents you from merging the following types of data sets:

• HFS data sets• NUCLEUS data sets• Operational data sets, such as PARMLIB and VTAMLST• SMP/E data sets• SVSLIB data sets• User data sets• VSAM data sets• zFS data sets.

The dialog allows you to merge data sets only when they share all of the following attributeswith the target data set:

• Record format (RECFM)• Logical record size (LRECL)• Data set type(DSNTYPE)• Eligibility to be managed by SMS• Compatible link list or LPA attributes• Origin library (DLIB or target library).

The candidate list automatically excludes any data sets that do not match these attributes ofthe target data set.

The candidate list excludes data sets with RECFM as U or V or VB, which have block sizevalue higher than that of the target data set.

Also, the candidate list excludes data sets that do not match the SMS eligibility of the targetdata set. For a target data set that is managed by SMS, for example, the candidate listexcludes data sets that are not eligible to be managed by SMS. Likewise, for a target set thatis non-managed, the candidate list excludes data sets for which SMS management isrequired.

The candidate list can extend for several screens. Use your keyboard's PFkeys to scrollthrough the list and select data sets, is needed, for merging with the target data set.

When you are done selecting data sets, enter M (merge) primary command on the commandline of this panel and press ENTER to merge the data sets. The dialog checks each selectedcomponent data set for member name conflicts with data sets that were previously mergedinto the target data set. If the dialog detects a conflict, a pop-up panel appears at the bottomof your screen. Press ENTER to clear the pop-up and continue with the next selected data setin the candidate list. When the merge operation completes, the Data Set Merge candidatespanel displays a message indicating that the merge is successful.

Redisplaying the Summary of Data Sets panel now shows an asterisk in the X column forthe target data set. Also, the component data sets that were merged into the target data set nolonger appear in the summary.

Merging Unix File System Data SetsThe dialog allows you to merge some of the eligible HFS and zFS data sets in your order.When you select a UNIX file system data set as a merge target (through line command M),the Data Set Merge Candidates panel shown in Figure 103 on page 153 is displayed. Thepanel shows the file system data sets that are eligible for merging with the selected data set(target data set). Later, when you save your configuration through the Save Configurationcommand (see Chapter 15, “Saving the Configuration” on page 211), the dialog also saves



the data for each merged file system data set and its component data sets. The merged filesystem data sets are now available for merging with future CustomPac orders.

� � CustomPac ------------- Modify System Layout ( MD053718 ) --- ROW 1 TO 4 OF 4 COMMAND ==> SCROLL ==> HALF Data Set Merge Candidates for OMVS.ROOT Primary Commands:(? SET Locate Find Next Previous Line Commands:(Information Select)

DS S Data Set Name Type Mount Point - -------------------------------------------- ----- -----------------------

OMVS.AS390 zFS /usr/lpp/wasOMVS.XML zFS /usr/lpp/xml**************************** BOTTOM OF DATA ********************************

� �

Figure 103. CPPP605V - Data Set Merge Candidates for UNIX File System Data Sets

The functions of the primary and line commands on this panel are the same as those forFigure 102 on page 151. The Conflict line command, however, is not applicable to theUNIX file system data sets and is not available on this panel.

Not all file system data sets can be merged. The dialog prevents you from these restrictions.Specifically, the dialog prevents you from merging the following file system data sets inz/OS orders:

• OMVS.ETC• OMVS.VAR

Also, the dialogs prevents you from merging when the following conditions are not met:

• The data set must be either:

− The same type (HFS or zFS), or− The file system data set must be marked as Switchable. Use the dialog's View and

Change Facility (Option C on the Modify System Layout Options panel) and selectthe display "Switchable."

• The merge target file system data set has a lower-level mount point.

In order to merge eligible HFS and zFS data sets together they must both be included in thegenerated list from which you issue the Merge line command. For example, if you generateyour list of file system data sets using the Data Set Type display from the dialogs View andchange data sets by selected attributes facility, you must select both HFS and zFS data settypes.

Once you have selected the file system data sets to be merged you can enter the primarycommand MERGE. For UNIX file system data sets, merge will proceed for a selectedcomponent when there are no other file system data sets having a mount point that ishierarchically between the target data set's mount point and the candidate component dataset's mount point. The space allocated for a merged file system data set will be equal to thesum of the space of both the merge target data set plus the space of all the merge componentdata sets.



| Merging UNIX file system data sets greater than 4 GB| This section contains the following topics:

| • For driving system z/OS V1R13 or for a z/OS V2R1 driving system where target data| set is already SMS managed

| • For driving system z/OS V2R1 and where target data set is non SMS managed

| For driving system z/OS V1R13 or for a z/OS V2R1 driving system where target data| set is already SMS managed: When you select a zFS data set as a merge target (through| line command M) and that target dataset exceeds 4 GB. Figure 104 will be displayed with| the total calculated size of the merge target data set along with the merge candidate data set| in GB information where the requirement and options for you will be explained. You will| have the following options:

| 1. Review and change SMS Classes

| 2. Change data set types to HFS

| 3. Unmerge one or more file systems and reduce total size of file systems to less than 4| GB.

| Specify the desired option in the command line.

| If the target data set is non SMS Managed, the first option will be 'Change file systems to be| SMS Managed with a Data Class for z/OS V1R13 driving system.

| �| �| CPPP60E1 CMD ---------- Merge Error for OMVS.ROOT --------------------| COMMAND ==>

| Error: Estimated target zFS file system size is 4.58 GB

| A zFS that is > 4GB must be SMS managed and use a SMS Data| Class that supports extended addressability.

| To continue with the merge, select one of the following:

| 1 Review and change SMS Classes| 2 Change data set type(s) to HFS| 3 Unmerge one or more file systems and reduce total size of file| systems to less than 4 GB.

| �| �

| Figure 104. CPPP60E1 - Merge error for OMVS.ROOT

| If you select option '1', Figure 105 on page 155 is displayed to collect SMS information,| such as Storage Class, Data Class and Management Class. If SMS Storage Class was| assigned prior to this request, it will be set to that value. If Data Class was assigned prior to| this request, it will be set to that value. If no classes are assigned, defaults will be used for| Storage Class and Data Class. The default values are as follows:

| • Storage Class

| • SMSTCLAS

| • Data Class

| • DCVSAMEX



| �| �| CPPP60E3 CMD --------- Specify SMS Classes ( RF001230 ) ----------------------| COMMAND ==>

| Data Set Name: OMVS.ROOT

| Data Class ==> DCVSAMEX

| Management Class ==>

| Storage Class ==> SMSTCLAS

| Specify a Data Class that supports extended addressability.| The SMS Classes specified must be defined to SMS.| Leave blank to indicate the data set is managed by ACS routines.

| Press Enter to continue or End to cancel

| �| �

| Figure 105. CPPP60E3 - Specify SMS classes

| Once you enter SMS Class information and hit ENTER, then the existing Figure 106 will be| displayed with information message that merge is completed.

| �| �| CPPP605U --------------- Data Set List ( RF001230 ) --------- Row 5 to 6 of 6| COMMAND ==>

| Data Set List for: Data Set Type


| Physical| S Data Set Name Selected Value Volume| - -------------------------------------------- ----------------------- --------| OMVS.SCFZHFS2 ZFS TEST03| OMVS.VAR ZFS TEST03| *******************************Bottom of Data**********************************

| �| �

| Figure 106. CPPP605U - Data Set List

| If you select option '2', the target data set will be changed to HFS and Figure 107 on| page 156 will be displayed with the message

| CPP0605237I Data set type changed to HFS and the merge request was| successful.

| The Data class value will be blank and SMS Managed will be YES or NO (depends on| target data set SMS Managed input before merging) in the Data Set Attributes panel. See| Figure 106



| �| �| CPPP605D --------- Data Set Attributes 1 of 2 ( LX000349 ) -------------------| COMMAND ==>

| Data set Name ==> OMVS.ROOT| Shipped Name : OMVS.ROOT| Data Set Type ==> ZFS (HFS or ZFS) Shipped : ZFS| Data Set Element Type : FS| Category : Target

| Logical Volume ==> SMR042 Shipped : RES042| SMS Managed ==> Yes (Yes or No)

| Storage Class : SMSRCLAS (Blank if managed by ACS routines)| Data Class :| Management Class :

| Primary Tracks ==> 78000 Shipped : 45092| Secondary Tracks ==> 4510 Shipped : 4510

| Product, Element, or Feature : USER DEFINED DATASETS

| �| �

| Figure 107. CPPP605D - Data set attributes 1 of 2

| �| �| CPPP605U --------------- Data Set List ( RF001230 ) --------- Row 5 to 5 of 5| COMMAND ==>

| Data Set List for: Data Set Type


| Physical| S Data Set Name Selected Value Volume| - -------------------------------------------- ----------------------- --------| OMVS.VAR ZFS TEST03| *******************************Bottom of Data**********************************

| �| �

| Figure 108. CPPP605U - Data Set List

| If you select option '3', then the candidate list should be re-displayed in a new dialog panel| Figure 109 on page 157 A new error message will be displayed asking you to deselect one| or more file systems from the candidate list.



| �| �| CPPP60E5 CMD ----------- Modify System Layout ( RF001230 ) -- Row 1 to 6 of 6| COMMAND ==> SCROLL ==> CSR

| CPP0605231E Deselect one or more data sets from merge candidate list.| Merge Component Data Sets for: OMVS.ROOT| Press F3 to continue.

| Line Commands:(Information Unmerge)

| S Data Set Name DS Type Size in GB/MB| - -------------------------------------------- ------- --------------------| * OMVS.ROOT ZFS 4.91 GB| OMVS.SIGYROOT ZFS 0.81 MB| OMVS.JAVA64V7 ZFS 417.96 MB| OMVS.SIBMROOT ZFS 1.62 MB| OMVS.SAOPROOT ZFS 318.33 MB| OMVS.TIVOLI ZFS 79.38 MB

| �| �

| Figure 109. CPPP60E5 - Modify system layout

| After you unmerge one or more zFS file systems (in the preceding figure), if the target data| set still exceeds 4 GB, the panel CPPP60E1 will be displayed again with reduced size| information.

| For driving system z/OS V2R1 and where target data set is non SMS managed: When| you select a zFS data set as a merge target (through line command M) and that target data| set exceeds 4 GB, Figure 110 will be displayed with the total calculated size of the merge| target data set along with the merge candidate data set in GB information and options for the| user. You will have the following options:

| 1. Allocate Data set using Data Class with Extended Addressability.

| 2. Unmerge one or more file systems and reduce total size of file systems to less than 4| GB.

| Specify the desired option in the command line.

| �| �| CPPP60E6 ------------- Merge Error for OMVS.ROOT --------------| COMMAND ==>

| Error: Estimated target zFS file system size is 5.55 GB

| A zFS that is > 4GB must use a Data Class that supports| extended addressability with no extended Format and DSORG = LS

| To continue with the merge, select one of the following:

| 1 Allocate Data set using Data Class with Extended Addressability

| 2 Unmerge one or more file systems and reduce total size of files| systems to less than 4 GB

| �| �

| Figure 110. CPPP60E6 - Merge error for OMVS.ROOT

| If you select option '1', Figure 111 on page 158 will be displayed to collect Data Class with| Extended Addressability. If you have already provided Data Class for the data set, this panel| will be displayed with pre-populated Data Class.



| �| �| CPPP60E7 ------------ Specify SMS Classes ( RF001424 ) -------------| COMMAND ==>

| Data Set Name: OMVS.ROOT

| Data Class ==>

| Specify a Data Class that supports extended addressability with| No Extended Format and Recorg = LS


| �| �

| Figure 111. CPPP60E7 - Specify SMS classes

| If you select option '2', it will be processed the same way as option 3 of Figure 104 on| page 154

Considerations for Merging Data SetsWhen you enter the MERGE command from a data set list panel, the dialog checks the dataset list panel for data sets with matching attributes, and presents these data sets as candidatesfor merging. The dialog does not enforce the operating system's rules for data set placement,or rules that individual products might impose. Therefore, use caution in deciding whichdata sets to merge.

For example, you should not merge libraries that are required in the LPA list with librarieshaving modules that cannot reside in LPA, because the resulting configuration will beunworkable, lack important functions, or even be impossible to IPL. Similarly, mergingmacro libraries with panel libraries can cause assemblies to fail. A less obvious examplewould be merging required LPA libraries with LPA-eligible libraries. Doing so might resultin configurations that are usable on some systems in your enterprise, but unusable on others.

To avoid creating configurations that are unworkable or difficult to manage, you shouldgenerally consider merging only those libraries that serve similar purposes. Use the dialog'sView and Change Facility, described in “Viewing and Changing Data Sets” on page 131, toidentify distinct groups of target data sets so that you can consolidate them through theMERGE command (the dialog does not display DLIB data sets by individual type). Youmight, for example, merge any target libraries that are required in the LPA list, or mergeyour ISPF panel libraries. Also consider merging your procedure libraries into a smallernumber of procedure libraries. These actions result in configurations that are reasonablyeasy to manage.

IBM recommends that you merge only target data sets having the same element type, ratherthan DLIB data sets.

Data Sets Restricted from MergingThe dialog automatically prevents you from merging the following types of data sets:

• Operational data sets, such as PARMLIB and VTAMLST• SMP/E data sets• VSAM data sets• HFS data sets• User data sets.



Also, you cannot merge data sets that are already components of merged data sets. In thiscase, you must first unmerge the component data set from the merged data set before youcan merge it with another data set.

Merging PDSE Data SetsWhen merging PDSE data sets, observe the following:

1. You can merge PDSE data sets when they have matching RECFM, LRECL, and originlibrary (target or DLIB).

2. With some exceptions, you can merge PDS data sets with a PDSE target data set. ThePDSE target data set must have matching characteristics (RECFM, LRECL, originlibrary). The exceptions are PDS data sets that must reside on the IPL volume or have arecord format (RECFM) of U. The dialog automatically excludes these PDS data setsfrom the candidates list for a PDSE target data set.

3. You cannot merge a PDSE data set with a PDS target data set, unless you first convertthe PDSE data set to a PDS data set. This conversion is possible only if the PDSE wasoriginally shipped as a PDS data set.

Merging IBM data sets into a merge target user-defined data setUser-defined data set can be used as target data set to merge eligible IBM data sets asmerged components. However, user-defined data sets are not eligible for merge componentdata sets. User-defined data sets cannot be used to merge into the target data set.

In order to merge eligible IBM data sets into eligible user-defined target data set, they mustboth be included in the generated list from which you issue the Merge line command. Forexample, if you generate your list of data sets using the Data Set Origin display from thedialogs View and change data sets by selected attributes facility, you must select both IBMand User-Defined. After you select the IBM data sets to be merged into user-defined dataset, you can enter the primary command Merge. The selected IBM data sets will then bemerged into the target user-defined data set.

Effects of Merging Data SetsWhen merged, component data sets assume the following attributes of the target data set:

• Data set name.

• Data set type (PDS or PDSE, HFS or zFS).

• Logical Volume

• Catalog, unless one or more of the component data sets is cataloged in the mastercatalog. If so, the merged data set becomes cataloged in the master catalog.

A merged data set has the combined space of the merge target data set and its mergecomponent data sets.

If you merge data sets of different element types, the dialog displays only one of thoseelement types for the merged data set in subsequent dialog data set lists. In selecting anelement type to represent the merged data set, the dialog selects the "highest" element typefrom among the data sets being merged. To select an element type, the dialog uses the samepriority order it uses for creating a recommended system layout (from highest to lowest; see “Creating the Recommended System Layout” on page 111). For example, merging apanel data set (element type PNLxxx) with a skeleton library (element type SKLxxx) resultsin a merged data set with an element type of PNLxxx.

If you intend to change the merge target data set from SMS-eligible to SMS-managed, youshould make the change prior to the merger.



The dialog updates the installation jobs in your order to use the name of the merged data set.The dialog does not, however, update any product-supplied code on your system (such asEXECs or CLISTs) that might refer explicitly to data sets by name. As with renaming datasets, be aware that merging data sets can cause conflicts in any products that reference datasets explicitly by name.

When a merge action completed, the dialog reserves the names of component data sets sothat you can, if desired, unmerge the data sets durng the Modify System Layout phase ofinstallation. Use care, however, in merging data sets. After you begin to run the installationjobs, unmerging a data set requires you to reinstall the order, starting from the ModifySystem Layout phase of the installation.

Finding "Lost" Component Data SetsIf you forget where a particular data set is after you merge it, you can use the FC primarycommand on the Select Values to Display panel to find it among your merged data sets. TheFC command allows you to search for a data set by its shipped name, or its new name if yourenamed the data set during a subsequent phase of installation.

To search on a fully qualified data set name, enter the FC command followed by the name ofthe data set. The dialog displays the name of the merged data set that contains the specifieddata set.

To search on a partially qualified data set name, enter the FC command followed by the firstfew characters of the data set name and a wildcard (*). The dialog displays a pop-up list ofdata sets — the "Data Set Selection List" — that match the specified argument. Forexample, entering FC SYS1.M* results in a list of all component data sets beginning with'SYS1.M,' allowing you to select the desired data set with line command S to obtain thename of the merged data set.

If you specify a data set that is not a component of a merged data set, the dialog displays themessage "component not found."

Unmerging Data SetsWhen unmerged, a data set returns to its pre-merge values for data set name, data set type,attributes, and space allocations, with the exception of any changes you made through theCHANGE command (these are retained). The dialog also adjusts these data set values in themerged data set, if applicable. For example, assume that one component data set in a mergeddata resides on the IPLVOL volume, thus requiring the entire merged data set to reside onthe IPLVOL volume. If you unmerge the IPLVOL-resident data set from the merged dataset, the merged data set reverts to the logical volume of the target data set.

You can unmerge a merged data set of all of its components at once, or you can removeparticular component data sets from a merged data set. To unmerge a merged data set of allits component data sets at once, enter the U (unmerge) line command to the left of themerged data set. When you press ENTER, a message is displayed to indicate whether theunmerge action was successful.

To remove only particular component data sets from a merged data set, you must firstexpand the diaplay of the merged data set to see its individual componenet data sets. To doso, enter the X (expand) line command to the left of the merged data set on the Summary ofData Sets panel. The pop-up window shown in Figure 112 on page 161 is displayed.



� �CustomPac ------------ Data Set List ( MD053718 ) ---- ROW 1 TO 10 OF 10COMMAND ==> SCROLL ==>

Data Set List for: Element type

Primary Commands:(? SET Locate Find Next Previous SORT CHange OFileOList FindComp)

Line Commands:(Merge eXpand Conflict Unmerge Attribs Space Resolve)------------------------------------------------------

DSName |CPPP605X :(Information Unmerge) Row 1 to 3 of 3 | R C I- ----------| | - - -

ANF.AANFE | | Y N NANF.AANFL | Merge Component Data Sets for: | Y N NANF.AANFM | ANF.AANFEXEC | Y N NANF.AANFM | S DSName | Y N N

X ANF.AANFP | - ------------------------------------ | Y N NANF.AANFS | * ANF.AANFPROC | Y N NANF.SANFE | ASU.AASUEXEC | Y N NANF.SANFL | ASU.AASUPROC | Y N NANF.SANFM | | Y N NANF.SANFM | | Y N NANF.SANFP ----------------------------------------------------- Y N NANF.SANFSAMP SAMP FB PO Y N N

**************************** BOTTOM OF DATA ***************************

� �

Figure 112. CPPP605X - Expansion of a Merged Data Set

Select individual component data sets for unmerging by entering a U to the left of thecomponent data set and press ENTER. A message is displayed to indicate whether theunmer action was successful.

Enter 'I' to the left of a component data set and press Enter to get information about thecomponent data set.

As shown in Figure 112, the pop-up list indicates the target data set with an asterisk. This isthe name of the target data set before it was merged. Only line commands I, or U are validfor the target data set.

It is also possible to completely unmerge the data set of all its component data sets from theEXPAND pop-up. Simple enter a U for every component data set in the pop-up and pressENTER.

Note: This is not true for UNIX file system data sets. The dialog prevents you fromunmerging all the components at once. They must be unmerged one at a time. See"“Unmerging Unix File System Data Sets” for more information.

Unmerging Unix File System Data SetsUnmerging UNIX file system data sets is different then unmerging other data set types.

The dialog will prevent you from unmerging a file system data set from a target file systemdata set if there is a third file system component data set with a mount point that ishierarchically below the mount point of the target file system and the selected componentfile system data sets. In this situation, you have the following options:

• Deselect the file system data set you selected for unmerging and the unmerge should becancelled, or

• Unmerge the third file system data set and then you can unmerge the other componentfile system data set.



For example, a data set with a mount point of /a/b cannot be unmerged from a data sethaving mount point of /a if another component of the merge has a data set with a mountpoint of a/b/c.

When you enter the line command eXpand to the left of a merged UNIX file system data seton panel CPPP605U, the Figure 113 panel appears.

� � CPPP605W --- Show Merged Data Set Components ( MD053718 ) --- ROW 1 TO 4 OF 4 COMMAND ==> SCROLL ==> HALF

Line Commands:(Information Unmerge)

S Data Set Name Mount Point - -------------------------------------------- ----------------------- * OMVS.ROOT /

OMVS.AS390 /usr/lpp/wasOMVS.XML /usr/lpp/xml**************************** BOTTOM OF DATA ********************************

� �

Figure 113. CPPP605W - Expansion of Merge Component Data Set for UNIX Filesystem Data Sets

Saving Merged Data SetsTo preserve your merged data sets for merging with future CustomPac orders, you must saveyour configuration through the Save Configuration command (see Chapter 15, “Saving theConfiguration” on page 211). The dialog saves the data for each merged data set and itscomponent data sets.

Modifying a Data Set's Attributes

The Data Set Attributes panel, shown in Figure 114, appears when you enter a Select linecommand from a data set list panel or when you enter an Information line command from adata set merge candidate panel. This panel shows the attributes of a specific data set. Whenyou navigate to this panel from any of the data set merge candidate panels (CPPP605M orCPPP605V), or CPPP605X, all fields are display only.

� � CPPP605D --------- Data Set Attributes 1 of 2 ( MD053718 ) ------------------- COMMAND ==>

Data set Name ==> SMPE.CICT500.SMPSTS Shipped Name : SMPE.CICT500.SMPSTS

Data Set Type ==> PDS (PDS or PDSE) Shipped : PDS

Data Set Element Type : SRC Category : Target d)

Logical Volume ==> SMR002 Shipped : RES008SMS Managed ==> No (Yes or No) )

Storage Class : SMSRCLAS

Primary Tracks ==> 154 Shipped : 154Secondary Tracks ==> 16 Shipped : 16Directory Blocks ==> 100 Shipped : 100

Product, Element, or Feature : CUSTOMPAC SMP/E DATA SETS

� �

Figure 114. CPPP605D - Data Set Attributes 1



Depending on the data set's type (VSAM, sequential, or partitioned), you can change thefollowing fields on this panel:

• Data set name• Data set type (for HFS, PDS, PDSE, and zFS data sets only)• Logical volume.• SMS Managed status• Tracks

The fields in the Data Set Attributes 1 panel are described as follows.

Data Set NameSpecifies the name of the data set. If the Data Set Name field is preceded by ==>, youcan rename the data set. Unrenameable data sets cannot be renamed unless you firstoverride this attribute through a CHANGE RENAME command. For information aboutunrenameable data sets, see “Making Unrenameable Data Sets Renameable” onpage 141.

If you change the high level qualifier of a data set, you might need to re-establish itscatalog and SMS relationships.

Rule: The data set must be renamed to a valid data set name. The dialog does notenforce special cases; for example, the restriction limiting SYS1.DAE data set name to20 characters or less is not enforced. For information about valid data set names, referto the appropriate z/OS documentation.

For other considerations about changing the names of data sets in your configuration,see “Changing Data Set Names” on page 139.

Shipped NameSpecifies the shipped name of the data set.

Data Set TypeSpecifies the data set type. For data sets that are eligible (see“Changing Data SetTypes” on page 141 ), zFS is the default data set type. The Data Set Modification -Attributes panel (Figure 114 on page 162) allows you to change

• PDS data sets to PDSE data sets• PDSE data sets to PDS data sets• HFS data sets to zFS data sets• zFS data sets to HFS data sets

Type over the Data set type field with the new value, as follows:

HFS To change a zFS data set to an HFS data setPDS To change a PDSE data set to a PDS data set (if the PDSE was

originally shipped as a PDS data set).PDSE To change a PDS data set to a PDSE data setZFS To change an HFS data set to a zFS data set

For data sets that are not eligible to be changed, the Data Set Type field is read-only.The dialog does not, for example, allow you to change your order's PDSE data sets toPDS data sets because they contain members that cannot be loaded into a PDS.

The dialog does not enforce all product requirements. You must determine whether datasets are allowed to be changed before changing them.

For considerations about changing the data set type of data sets in your configuration,see “Changing Data Set Types” on page 141.



Data Set Element TypeSpecifies the element type of the data set. For example, MAC stands for macro libraryand LMOD is a load module. For user-defined data sets, the element type is *USER*.

CategoryThe Category field contains a 1-character value that indicates where the data set resides,as follows:

DLIBDLIB volume

TargetTarget library volume

OperationalCatalog volume. This value is set for operational data sets, such as page and dumpdata sets.

UserUser-defined data set; not shipped as part of the order.

Logical VolumeSpecifies the logical volume to which the data set is assigned. This is a data entry field,preceded by ==>, if the logical volume is one you can change; otherwise, this will be adisplay-only field, preceded by a colon (:).

Observe the following considerations:

• You cannot re-assign a data set to a logical volume that contains data sets of adifferent type (target, DLIB, or operational).

• If space re-calculation is required (because the new Logical Volume is assigned toa Physical Volume that has different device capacity to the Physical Volume of theold Logical Volume), then this will be carried out automatically.

• Two logical volumes, CSIVOL and IPLVOL, are reserved for the system's use.You may not assign any data sets to or from either of these logical volumes, if youattempt this then your request will be rejected.

For other considerations about changing the logical volumes of data sets in yourconfiguration, see “Changing Logical Volumes” on page 146.

SMS-ManagedSpecifies the SMS status of a data set, that is, specify whether SMS is to manage thedata set. If the data entry area for the SMS-Managed field is active, you can change thesetting for this data set. Data sets for which the SMS-Eligible field is set to YES can beSMS-managed or not, as you choose. Data sets for which the SMS-Required field isYES must remain SMS-managed data sets. For more information, see “Changing theSMS Management Status” on page 143.

To see which data sets in your configuration are eligible for SMS-management, use thedialog's View and Change Facility (describe in “Viewing and Changing Data Sets” onpage 131). Be aware that you cannot assign data sets that reside on the IPLVOL logicalvolume to SMS-managed logical volumes.

For considerations about changing the SMS management status of data sets in yourorder, see “Changing the SMS Management Status” on page 143.

Physical Volume or Storage ClassIf the value for SMS Managed is No, the displayed name for this field is PhysicalVolume and the value is the name of the physical volume to which the logical volumehas been assigned.



If the value for SMS Managed is Yes, the displayed name for this field is Storage Classand the values is the storage class to which the data set has been assigned.

TracksDepending on a data set's record format (RECFM) and type (VSAM, sequential orpartitioned), you can change the following fields on the Data Set Attributes 1 panelFigure 114 on page 162

• Primary Tracks• Secondary Tracks• Directory Blocks

You cannot decrease the size of a shipped data set to less than its original, shippedamount.

The fields in the Data Set Modification - Space panel are described follows.

Primary TracksSpecifies the primary space allocation (in tracks) for the data set. You can specifyany value from 1 to 999999 tracks. However, you cannot specify less than the"Shipped" amount shown on the right side of the panel.

Note: If you want to change the primary space allocations for a large number ofdata sets, it might be faster to use the View and Change option and the CHANGESPACE command in “Changing Data Set Space Values” on page 147.

Secondary TracksSpecifies the secondary space allocation (in tracks) for the data set. You canspecify any value from 0 to 999999 tracks.

To specify no secondary space allocation for the data set, set this value to 0 (zero).You can, if necessary, reset this value at a later time.

Notes:

1. If you want to change the secondary space allocations for a large number ofdata sets, it might be faster to use the View and Change option and theCHANGE SPACE command (described in “Changing Data Set Space Values”on page 147).

2. Some data sets are not allowed to have secondary space because of operatingsystem restrictions. These data sets are shipped with their Secondary Spacefields set to zero.

Directory BlocksSpecifies the number of directory blocks for a partitioned data set (PDS). You canset this field to any value between 1 and 99999, but you cannot decrease it belowthe shipped number of directory blocks.

For information about directory blocks, see z/OS DFSMS Using Data Sets.

Product, Element, or FeatureSpecifies the product, element, or feature associated with the data set.

If you press End on this panel, the previous panel appear.

If you make modifications on the Data Set Attributes 1 panel (Figure 114 on page 162) and press Enter, the panel remains on display with the updated fields. If you thenpress Enter again, the Data Set Attributes 2 panel (Figure 115 on page 166) appearsfor non-UNIX file system data sets. If you make no modifications on the Data SetAttributes 1 panel (Figure 114 on page 162) and press Enter, the Data Set Attributes 2panel (Figure 115 on page 166) appears for non-UNIX file system data sets.



� � CPPP605E --------- Data Set Attributes 2 of 2 ( JF002610 ) -------------------

Data set Name : SMPE.CICT500.SMPSTS

RECFM : FB LRECL : 80 APF Authorized : No LPA Eligible : No LPA Required : No

Link List Eligible : NoSMP/E SYSLIB Data Set : No

Required on IPL Volume : No SMS-Eligible : Yes SMS-Required : No Renameable : Yes

Required in Master Catalog : No

� �Figure 115. CPPP605E - Data Set Attributes 2

This is an information only display panel. It presents the current values for the data set.Changes to eligible fields can only be made with the CHange command. The displayedvalues are for presentation only and may not reflect the actual internal value. Forexample, the internal value of Y is presented as the logical value Yes. Also, any valuethat has been overridden is displayed as its logical value (Yes or No) followed by theword Overridden.

This panel displays different fields depending on the data set type. For example,Figure 116 shows a panel for a shipped VSAM data set.

� � CPPP605E --------- Data Set Attributes 2 of 2 ( JF002610 ) -------------------

Data set Name : SMPE.GLOBAL.CSI

Required on IPL Volume : No SMS-Eligible : Yes SMS-Required : No Renameable : Yes

Required in Master Catalog : No

� �Figure 116. CPPP605E - Data Set Attributes 2 for a shipped VSAM Data Set

For UNIX file system data sets, when you press Enter on the Data Set Attributes 1 panel(Figure 114 on page 162), the Data Set Attributes 2 panel for a UNIX file system dataset (Figure 117 on page 167) appears. The entire mount point can be displayed on thispanel along with the data set attributes. Pressing end on this panel returns you to theData Set Attributes 1 panel.



� � CPPP605F --------- Data Set Attributes 2 of 2 ( JF002610 ) ------------------- COMMAND ==>

Data set Name : OMVS.ROOT Mountpoint : /

Required on IPL Volume : No SMS-Eligible : Yes Renameable : Yes SMS-Required : No Required in Master Catalog : No

� �Figure 117. CPPP605F - Data Set Attributes 2 for a shipped VSAM Data Set

| For driving system z/OS V1R13 or z/OS V2R1 and SMS managed data set:For UNIX| file system data sets larger than 4 GB, if you change HFS to ZFS, Figure 118 will be| displayed. This panel is also displayed when the global Change command is used. The| information that zFS file system is larger than 4 GB, and that it must be SMS managed with| a Data Class that includes extended format and addressability is displayed. The User will| have the option to confirm the request or to cancel it.

| �| �| CPPP60E2 CMD ------ Verify Data Set Type Change ( JF002610 ) ------| COMMAND ==>

| OMVS.ROOT| The zFS or VSAM file system is larger than 4GB, and it must be| SMS managed with a Data Class (defined with Extended Format and| Extended Addressability) and a Storage Class.

| Do you want to change the Data Set Type (Yes or No)| ==>


| �| �

| Figure 118. CPPP60E2 - Verify data set type change

| The user will need to provide Data Class with extended addressability. If the user has| already provided Data Class for the data set, Figure 120 on page 168 will be displayed with| pre-populated Data Class.

| For driving system z/OS V2R1 and non-SMS managed data set: If you change the large| file system data set type from HFS to ZFS, either using the change command or using the| Data Set Attributes panel (CPPP605D), the following panel on Figure 119 on page 168 will| be displayed.



| �| �| CPPP60E7 ------------ Specify SMS Classes ( JF002610 ) -------------| COMMAND ==>

| Data Set Name: OMVS.SBBOIMRM

| Data Class ==>

| Specify a Data Class that supports extended addressability with| No Extended Format and Recorg = LS


| �| �

| Figure 119. CPPP60E7 - Specify SMS Classes

| The user will need to provide Data Class with extended addressability. If the user has| already provided Data Class for the data set, this panel will be displayed with a| pre-populated Data Class.

Displaying Device TypesFigure 120 shows the panel that is displayed when you enter Option T on the ModifySystem Layout options panel (or enter the DEVT command from another panel).

� � CustomPac --------------------- Device Type Table --------- ROW 1 TO 11 OF 11 COMMAND ==> SCROLL ==> PAGE

Primary Commands:(?)Line Commands:(Select Delete Insert)

Device Unit Bytes/ Tracks/ Cylinders/ VTOC Index HowS Type Type Track Cylinder Volume TRKS TRKS Defined- -------- -------- ------- -------- ---------- ---- ----- -------

D001-001 D001 65536 19 17206 399 80 DYNAMIC3380-1 3380 47476 15 885 30 6 IBM3380-2 3380 47476 15 1770 45 9 IBM3380-3 3380 47476 15 2655 60 12 IBM3390-1 3390 56664 15 1113 30 6 IBM3390-2 3390 56664 15 2226 60 12 IBM3390-3 3390 56664 15 3339 75 15 IBM3390-6 3390 56664 15 6678 150 30 USER3390-9 3390 56664 15 10017 225 45 IBM9345-1 9345 46456 15 1440 45 9 IBM9345-2 9345 46456 15 2156 60 12 IBM

******************************* BOTTOM OF DATA ********************************

� �

Figure 120. CPPP606# - Device Type Table

This panel shows the direct-access storage devices (DASD) defined to CustomPac. Youcannot delete or edit IBM-defined devices. However, you can add entries for real oremulated devices, and edit and delete those entries.


? These are standard CustomPac table handling commands.(See “The Primary Commands” on page 9)




S Select a user-defined device for editing. You can do this only if the device isnot currently referenced by any data sets (see “Inserting or Editing DeviceTypes”). You cannot edit IBM-supplied DASDs or dynamically-createdentries.

D Delete a user-defined device. You must confirm the delete request. (see“Deleting Device Types” on page 170). You cannot delete IBM-suppliedDASDs or dynamically-created entries.

I Insert a user-defined device. For more information, see “Inserting or EditingDevice Types.”

Inserting or Editing Device Types

Figure 121 shows the panel that is displayed when you enter I (INSERT) or S (SELECT)for a device type on the Device Type Table panel. (This panel is not displayed forIBM-defined devices, because you cannot modify those devices.)

� � CustomPac --------------------- Device Type Table ----------------------------- COMMAND ==>

Device Type ==> (Must be unique)Unit Type ==> (UNIT to be used for allocation)

Cylinders/Device ==> (50 to 32767 Cylinders)Tracks/Cylinder ==> (10 to 999 Tracks)Bytes/Track ==> (32767 to 65535 Bytes)

How Defined : USER

� �

Figure 121. CPPP606I - Device Type Insertion/Edit

The following fields must be supplied

Device TypeSpecifies the device type and model by which the DASD is to be known.

Unit TypeSpecifies the generic name to be used to allocate data sets on the device. For example,UNIT might be specified as 3390 or 3380.

Cylinders/DeviceSpecifies the number of cylinders for each DASD. Obtain this value from your DASDsupplier, it need not match the number of cylinders available on any IBM device.

Tracks/CylinderSpecifies the number of tracks for each cylinder on the DASD. Obtain this value fromyour DASD supplier.



Bytes/TrackSpecifies the number of bytes for each track on the DASD. Obtain this value from yourDASD supplier.

How DefinedSpecifies whether the device was user defined (USER) or dynamically defined(DYNAMIC).

For a user defined device, you can modify any of the values in this panel. For adynamiclly-defined device, you can modify only the Device Type value.

Deleting Device Types

This panel is displayed when option D is used to select a Device Type from the Device TypeTable panel.

� � CustomPac ---------- Device Type Deletion, Confirmation Request --------------- COMMAND ==>

DELETE REQUESTED

```````````````````````````````````````````````````````````````````````````````````` ````````````````````````````````````````` DEVICE ATTRIBUTES ````````````````````````````````````````` `````````````````````````````````````````````````````````````````````````````````````````` `````````` Device NAME: STAGEDEV Bytes/Track : 56664 `````````` Device TYPE: 3390 Tracks/Cyl : 15 `````````` Cyls/Device : 200 `````````` `````````````````````````````````````````````````````````````````````



� �

Figure 122. CPPP606D - Device Type Deletion

You can delete only non-IBM DASD device types.

You must confirm deletion by typing DELETE in the COMMAND ==> field andpressing ENTER.

If the Device Name is still used by any data set profile then your DELETE request will berejected.

Handling user data setsThis section lists the tasks connected with handling user data sets.



Defining new user data setsUser data sets can be defined as HFS or zFS data sets.

To define a new user data set, you must first go to the Data Set List (CPPP605U) panel.

You can go to Data Set List panel by using option C (View and change data sets by selectedattributes) on Modify System Layout as shown in Figure 74 on page 109 and thenselecting any of the attributes on Select Data Set View panel as shown in Figure 93 onpage 133. When you use the Select line command to select an attribute to display and pressEnter, the dialog displays a second panel with the values found for the selected attribute.Select the values for the attribute to be displayed and press Enter. The dialog displays theData Set List panel which has line command Insert.

Enter the Insert command on the Data Set list panel as shown in Figure 123 to display theDefine a USER Data Set panel (Figure 124 on page 172).


Data Set List for: Data Set Origin



PhysicalS Data Set Name Selected Value Volume- -------------------------------------------- ----------------------- --------I ACFNCP.ANCPMAC1 IBM MVSRES

ACFNCP.SNCPMAC1 IBM MVSRESACFNCP.SSPCLS1 IBM MVSRES****************************** Bottom of Data *****************************

� �

Figure 123. CPPP605U - Data Set List



� � CPPP605I ------------ Define a USER Data Set ( MD000277 ) -------------------- COMMAND ==>

Data Set Name ==> USERDEFINEDLogical Volume ==> LVUSERData set DDNAME ==>Define DDDEF ==> N (Y or N)Data Set Category ==> (? For List of Available Types)Allocate Data set ==> Y (Y or N)

Data Set Type ==> (PDS, PDSE, SEQ, HFS, ZFS) IZE)RECFM ==> (U, F-B-S-AM, V-B-S-AM)LRECL ==> (0 - 32760)Block Size ==> (1-32760 or blank for optimizedBLKSIZE) Tracks ==>Primary Tracks ==>Secondary Tracks ==>Directory Blocks ==> (Zero for sequential data set)

If defining the DDDEF, the following information is required:Zone Nickname ==> (? For List of Available Zones)If defining the DDDEF for HFS or zFS, the following information isrequired:DDDEF Path ==>If Data set Type is HFS or zFS, the following information is required:Mount Point ==>

� �

Figure 124. CPPP605I - Define a USER data set

On the Define a USER Data Set panel (Figure 124), fill out the required fields and pressEnter to add the user data set.

The fields in the Define a USER Data Set panel are described as follows:

Data Set NameSpecifies the name of the data set. This name must be unique within your order's workconfiguration

Logical VolumeSpecifies the logical volume to which the data set is to be assigned. This is a requiredfield. You can specify any logical volume, except for two volumes, CSIVOL andIPLVOL, which are reserved for the system's use. If you specify a logical volume namethat is not already known to the dialog, you can use the SUML primary command (fromthe Summary of Features/Elements panel) to assign the logical volume to a physicalvolume. (To assign a data set to a physical volume, use the dialog's CHANGE PVOLcommand.)

Data set DDNAMESpecifies the name of the data set DDNAME. This field is mandatory because it is usedas the DD name for merge processing. The name must be unique within your order swork configuration. The value of this field is defined as DDDEF in CSI zones if theDefine DDDEF field is set to Y.

Define DDDEFIndicates whether or not the SMP/E DDDEF should be defined in CSI zones. Set thisfield to Y if you want the dialog to define the DDDEF in CSI zones. Otherwise, set thefield to N.

Data Set CategorySpecifies the data set category. If you are unsure of the available categories enter a ?and a list will be displayed as shown in Figure 125 on page 173.



Available Categories

S CATEGORY DESCRIPTION- -------- -----------

D DLIBO OPERATIONALT TARGET

- -------- -----------

Figure 125. CPPP6053 - List of data set categories

Allocate Data SetIndicates whether the data set should be physically allocated by dialog install job. If theuser data set already exists, then this field must be set to N. If data set is to be allocatedby the dialog install job, then this field must be set to Y.

In the Full System Replacement (FSR) install for z/OS, make sure that the user-defineddata sets that already exist (for example, Allocate Data Set is set to N), are not catalogedin the driving system's master catalog. The existing user data sets must be defined in theuser catalog during z/OS FSR install. This restriction is not there for z/OS softwareupgrade installations and subsystem installations.

Data Set TypeSpecifies the data set type: PDS, PDSE, SEQ, HFS or zFS.

RECFMSpecifies the record format. You can specify any of the following formats:

U Undefined

Fixed You can specify any of the following formats:

• B (blocked)

• S (standard block size)

• A (ANSI control characters)

• M (machine control characters)

Variable You can specify any of the following formats:

• B (blocked)

• S (standard block size)

• A (ANSI control characters)

• M (machine control characters)

LRECLSpecifies the logical record length (LRECL). This field can contain any value from 0 to32760. While defining HFS or zFS user data set, you can keep this field blank.

Block SizeSpecifies the block size. This field can contain any value from 1 to 32760 or you cankeep this field blank.

Primary TracksSpecifies the primary space allocation (in tracks) for the data set. You can specify anyvalue from 1 to 65535 tracks.



Secondary TracksSpecifies the secondary space allocation (in tracks) for the data set. You can specifyany value from 0 to 65536 tracks. To specify no secondary space allocation for the dataset, set this value to 0 (zero). You can, if necessary, reset this value later.

Directory BlocksFor a PDS or HFS data set, this value specifies the number of directory blocks. You canset this field to any value between 1 and 99999.

Zone NicknameSpecifies the nickname of the zone in which you want to define the SMP/E DDDEF. IfDefine DDDEF is set to Y then this field is required. If you are unsure of the availablezones enter a ? and a list of available zones in your order will be displayed as shown inFigure 126. Select one of the displayed zone nicknames from that list. For the DLIBcategory data sets, DDDEF is defined in both DLIB and Target zones corresponding tothe specified zone nickname. For Target and Operational category data sets, DDDEF isdefined in Target zone corresponding to the specified zone nickname.

Available Zones

S Nickname DLIB Zone Target Zone SST- -------- --------- ----------- ---

100 MVSD100 MVST100 MVS101 MVSD110 MVST110 MVS102 MVSD111 MVST111 MVS

- -------- --------- ----------- ---

Figure 126. CPPP6059 - List of zones

DDDEF PathSpecifies the DDDEF path name for the HFS or zFS file system data set. If DefineDDDEF is set to Y for HFS or zFS data set, then DDDEF is defined pointing to thispath in CSI zones.

Mount PointSpecifies the path name of the mount point for the HFS or zFS file system data set.

Viewing user-defined data setsTo view a list of all user-defined data sets, select the Data Set Origin attribute on the SelectData Set View panel as shown in Figure 93 on page 133 and press Enter. The dialogdisplays a second panel with the values IBM and User-Defined as shown in Figure 94 onpage 134. Select User-Defined and press Enter. The dialog displays a list of all theuser-defined data sets on the Data Set List panel as shown in Figure 127 on page 175.




Data Set List for: Data Set Origin



PhysicalS Data Set Name Selected Value Volume- -------------------------------------------- ----------------------- --------

CPPDEV.TEST.ONE User-Defined MVSRESCPPDEV.USER.PDSY User-Defined MVSRESCPPDEV.YOGESHD.JCL User-Defined MVSRES****************************** Bottom of Data *****************************

� �

Figure 127. CPPP605U - Data Set List to display user-defined data sets

On the Data Set List panel, you can Select the data set to view the attributes.

Depending on the data set type (HFS/zFS or PDS/PDSE or SEQ) and the value of theAllocate Data set field (Y or N) of the user defined data set, there will be a different viewsof Data Set Attributes 1 of 2 panel for user data sets.

The following fields on the Data Set Attributes 1 of 2 panel are displayed only foruser-defined data sets. They are for display only.

• Allocate Data Set

• Define DDDEF

• Data set DDNAME

• Zone Nickname

• DDDEF Path (This field is displayed only for HFS or zFS user-defined data sets.)

The following fields on the Data Set Attributes 1 of 2 panel are not displayed foruser-defined data set that have the Allocate Data Set field set to N.

• Primary Tracks

• Secondary Tracks

• Directory Blocks

The PDS/PDSE user data set with Allocate Data set=Y will have the following Data SetAttributes 1 of 2 panel display as shown in Figure 128 on page 176.



� � CPPP605D --------- Data Set Attributes 1 of 2 ( OD000349 ) ------------------- COMMAND ==>

Data set Name ==> CPPDEV.USER.PDSY Shipped Name : CPPDEV.USER.PDSY

Data Set Type ==> PDS (PDS or PDSE) Shipped : PDS Data Set Element Type : *USER*

Category : DLIB

Logical Volume ==> CAT001 Shipped : CAT001SMS Managed ==> No (Yes or No)

Physical Volume : USER01

Primary Tracks ==> 50 Shipped : 50Secondary Tracks ==> 30 Shipped : 30Directory Blocks ==> 10 Shipped : 10Allocate Data set : YDefine DDDEF : YData set DDNAME : USRPDSYZone Nickname : 100

Product, Element, or Feature : USER DEFINED DATASETS

� �

Figure 128. CPPP605D - Data Set Attributes 1 (User PDS/PDSE with Allocate Data set = Y)

The PDS/PDSE user data set with Allocate Data set=N will have the following Data SetAttributes 1 of 2 panel display as shown in Figure 129

� � CPPP605D --------- Data Set Attributes 1 of 2 ( OD000349 ) ------------------- COMMAND ==>

Data set Name ==> CPPDEV.USER.PDSN Shipped Name : CPPDEV.USER.PDSN

Data Set Type ==> PDS (PDS or PDSE) Shipped : PDS Data Set Element Type : *USER*

Category : DLIB



Allocate Data set : NDefine DDDEF : YData set DDNAME : USRPDSNZone Nickname : 100


� �

Figure 129. CPPP605D - Data Set Attributes 1 (User PDS/PDSE with Allocate Data set = N)

The following fields are not displayed for user-defined data sets with Allocate Data Set=N.

• Primary Tracks

• Secondary Tracks

• Directory Blocks

The HFS/zFS user data set with Allocate Data set=Y will have the following Data SetAttributes 1 of 2 panel display as shown in Figure 130 on page 177



� � CPPP605D --------- Data Set Attributes 1 of 2 ( LX000349 ) ------------------- COMMAND ==>

Data set Name ==> CPPDEV.USER.HFSY Shipped Name : CPPDEV.USER.HFSY

Data Set Type ==> HFS (HFS or ZFS) Shipped : HFS Data Set Element Type : *USER*

Category : DLIB



Primary Tracks ==> 50 Shipped : 50Secondary Tracks ==> 30 Shipped : 30

Allocate Data set : YDefine DDDEF : YData set DDNAME : USRHFSYZone Nickname : 100DDDEF Path : /user/hfs1


� �

Figure 130. CPPP605D - Data Set Attributes 1 (User HFS/zFS with Allocate Data set = Y)

The following fields is displayed only for HFS/zFS user-defined data sets and isdisplay-only.

• DDDEF Path

The HFS/zFS user data set with Allocate Data set=N will have the following Data SetAttributes 1 of 2 panel display as shown in Figure 131


Data set Name ==> CPPDEV.USER.ZFSN Shipped Name : CPPDEV.USER.ZFSN

Data Set Type ==> ZFS (HFS or ZFS) Shipped : ZFS Data Set Element Type : *USER*

Category : DLIB



Allocate Data set : NDefine DDDEF : YData set DDNAME : USRZFSNZone Nickname : 100DDDEF Path : /user/zfs1


� �

Figure 131. CPPP605D - Data Set Attributes 1 (User HFS/zFS with Allocate Data set = N)

The SEQ user data set with Allocate Data set=Y will have the following Data Set Attributes1 of 2 panel display as shown in Figure 132 on page 178




Data set Name ==> CPPDEV.USER.SEQY Shipped Name : CPPDEV.USER.SEQY

Data Set Type : SEQ Shipped : SEQ Data Set Element Type : *USER*

Category : DLIB



Primary Tracks ==> 20 Shipped : 20Secondary Tracks ==> 10 Shipped : 10

Allocate Data set : YDefine DDDEF : YData set DDNAME : USRSEQYZone Nickname : 100


� �

Figure 132. CPPP605D - Data Set Attributes 1 (SEQ user data set with Allocate Data set = Y)

The SEQ user data set with Allocate Data set=N will have the following Data Set Attributes1 of 2 panel display as shown in Figure 133


Data set Name ==> CPPDEV.USER.SEQN Shipped Name : CPPDEV.USER.SEQN

Data Set Type : SEQ Shipped : SEQ Data Set Element Type : *USER*

Category : DLIB



Allocate Data set : NDefine DDDEF : NData set DDNAME : USRSEQNZone Nickname :


� �

Figure 133. CPPP605D - Data Set Attributes 1 (SEQ user data set with Allocate Data set = N)

Deleting user-defined data setsFigure 134 on page 179 shows the panel that is displayed when you enter line command Dto delete a user-defined data set from the Data Set List panel (Figure 127 on page 175).



� �CPPP605$ --------------------- Data Set Details -------------------------------COMMAND ==>

DELETE a User-Defined Data Set

````````````````````````````````````````````````````````````````````````````````` `````````````````````````````````````` DATA SET DETAILS `````````````````````````````````````` `````````````````````````````````````````````````````````````````````````````````````` `` Data Set Name: CPPDEV.USER.SEQN `` `````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````


`` Press the END or RETURN key to CANCEL the DELETE request� �

Figure 134. CPPP605$ - Data Set Details to confirm the delete

Confirm the deletion by entering DELETE in the COMMAND ==> field and pressing Enter.

Restrictions: The following data sets cannot be deleted:

• IBM-shipped data sets

• Data sets that contain merge data sets.

Displaying a Summary of Data SetsFrom the Modify System Layout Options panel (see Figure 74 on page 109), enter OptionD to display the Summary of Data Sets panel. You can also display this panel by enteringthe SUMD command from the Summary of Features/Elements panel.

The Figure 135 on page 180 is displayed.



� � CustomPac ------------- Modify System Layout ( MD057318 ) ---- Row 693 of 1696 COMMAND ==> SCROLL ==> HALF

Summary of Data Sets


Line Commands:(Merge eXpand Conflict Unmerge Select)

--- Data Set --- Primary S Data Set Name X F Type RECFM LRECL Tracks WARN - ------------------------------------------ - - ---- ----- ----- ------- ----

ISP.AISPALIB * PDS FB 80 59ISP.AISPEXEC * PDS FB 80 18ISP.AISPGENU * PDSE FB 80 789ISP.AISPMACS PDS FB 80 987ISP.AISPMENU PDS FB 80 876ISP.AISPMOD1 PDS U 0 2718ISP.AISPPENU PDS FB 80 543ISP.AISPPUBS PDS FB 80 321ISP.AISPLPA PDS U 0 3141OMVS.ETC ZFS 7206 WARNOMVS.ROOT HFS 491400 WARNSOME.VSAM.DATA.SET VSAM 210

� �

Figure 135. CPPP6052 - Summary of Data Sets

For descriptions of various Primary Commands and Line Commands in this panel, pressHELP (?).

In the panel, the WARN column indicates data set conditions you have to resolve beforecontinuing with the installation. The possible warnings are as follows:

WARN The data set already exists in the driving system master catalog. For moreinformation, see the description of message CPP0605229E.

Displaying a Summary of Physical VolumesTo see the physical volumes that are used by a particuler feature or element, use theSummary of Features/Elements panel. From the Modify System Layout Options panel(Figure 74 on page 109), enter Option V to display the Summary of Physical Volumespanel. You can also display this panel by entering the SUMP command from the Summaryof Features/Elements panel.

The panel shown in Figure 136 on page 181 is displayed.



� � CustomPac ------------- Modify System Layout ( MD053718 ) --- ROW 1 TO 3 OF 3 COMMAND ==> SCROLL ==> HALF

SUMMARY Of Physical Volumes

Primary Commands:(? DEVT)Line Commands:(Select Dslist)

PVolume/ Seq Device Device Warn- Init ------------ Cylinders ----------- S STORCLAS No. Number Type ings Volume Existing RSVD Assignd Used Free - -------- --- ------ -------- ------ ------ -------- ----- ------- ----- ----- MVSCAT 04C7 3390-3 OVR<<S Y 0 0 2706 0 633 MVSDL1 D01 CCUU 3390-3 OVR<<S N 0 0 2939 0 400 MVSDL2 D02 CCUU 3390-3 OVR<<S N 0 0 1323 0 2016 MVSRS1 T01 CCUU 3390-3 N 0 0 2871 0 468 MVSRS2 T02 CCUU 3390-3 N 0 0 2065 0 1274 MVSRS3 T03 CCUU 3390-3 N 0 0 2724 0 615 SMSDCLAS 1115 SMSRCLAS 2157 ******************************** BOTTOM OF DATA *****************************

--------------------------------------------------| CPP0605059S Volume (MVSCAT) is overallocated. |--------------------------------------------------

� �

Figure 136. CPPP605K - SUMMARY Of Physical Volumes

For descriptions of the fields in this panel, press HELP (?).

Use this panel to verify and change (if necessary) the attributes of the physical volumes.Before you proceed, however:

• If there are warnings on this panel, you should not try to resolve them unitl you havecompleted any data set merges, space allocation changes, or volume assignmentchanges that you intend to make.

• If you have DYNAMIC DASD INFO set to No, you must use the Select line commandto display the Display and Change Volume Attributes panel, on which you must specifythe required information about each volume and may choose to reserve space on thevolume or tell the dialog not to initialize it.

• If you have DYNAMIC DASD INFO set to Yes, you must use the Select line commandto reserve space on the volume or tell the dialog not to initialize it.

• These changes should be among the last things you do before exiting Modify SystemLayout (because other changes you make could force you to do rework), but they mustbe completed before you attempt to run any jobs that install the data sets on your DASDvolumes.

To accomodate libraries that expand during the installation of service, and to make it lesslikely that libraries will have to be moved when you install a subsequent release, allow atleast 15% free space for each physical volume allocation. You can create more space bymoving some data sets to another volume. For more information, see “ResolvingOver-Allocated Volume Conditions” on page 183.

In the panel, the Warnings column indicates volume conditions you might have to resolvebefore continuing with the installation. The possible warnings are as follows:

DEV<<S Incorrect device type specified for the volume. For more information, see thedescription of message CPP0605055S in CustomPac Installation DialogMessage Book.



OFF<<S Volume cannot be accessed because it is offline. For more information, seethe description of message CPP0605056S in CustomPac Installation DialogMessage Book.

EXT<<W The combined size of the data sets to be allocated on this volume exceeds thesize of the largest free extent on the volume. For more information, see thedescription of message CPP0605057W in CustomPac Installation DialogMessage Book.

VOL<<S Information about the volume could not be retrieved. For more information,see the description of message CPP0605058S in CustomPac InstallationDialog Message Book.

OVR<<S The number of cylinders to be allocated on the volume exceeds the totalnumber of cylinders for the volume. For more information, see thedescription of message CPP0605059S in CustomPac Installation DialogMessage Book.


? These are standard CustomPac table handling commands.(See “The Primary Commands” on page 9)

DEVT Displays the currently-defined device types and their storage capacities (incylinders).


S Select

Use the S line command to select physical volumes and SMS storage classesfor reassignment, as follows:

• For a physical volume, the S line command displays a panel that allowsyou to specify a different physical volume and to change the attributes ofthe current physical volume, as described in “Changing the attributes of aphysical volume” on page 183.

• For a storage class, the S line command displays a panel that allows youspecify a new storage class, as described in “Changing an SMS storageclass” on page 185.

Note: To assing a STORCLAS in place of a physical volume, you mustassing the logicla volume to the STORCLAS.

D Dslist

Use the D line command to display the data sets for the selected physicalvolume or storage class. The Summary of Data Sets panel is displayed,allowing you to do any of the following:

• Merge or unmerge CustomPac-shipped data sets (you cannot merge ofunmerge user-defined data sets)

• Make global changes to multiple data sets (using one of the CHANGEcommands described in “Making Changes to Data Sets” on page 137).

• Modify the attribtes of particular data sets or modify their spaceinformation (using one of the CHANGE commands described in“Making Changes to Data Sets” on page 137).

• Write a list of the data sets in the ISPF LIST data set or to a user-definedfile (using the OLIST or OFILE command described in “The PrimaryCommands” on page 9).



Resolving Over-Allocated Volume ConditionsWhile processing the configuration you specify in Modify System Layout, the dialog mightshow that some volumes are over-allocated (as in Figure 136 on page 181). The dialogdisplays a message on the panel, with “OVR<<S” indicated for the over-allocatedvolume. Until you resolve this condition, the dialog prevents you from continuing to thenext function.

There are several ways to resolve this condition:

• Add another volume and move data sets from the over-allocated volume to the newvolume.

• Change the device type to one that has larger capacity.

• Move data sets to another physical volume. See the topic, “Recommended Data SetPlacement” in z/OS Planning for Installation for assistance in determining which datasets to move.

For help in changing the device type or moving a data set to another physical volume, seethe descriptions that accompany Figure 137 on page 184.

To add another volume, follow this process:

1. Enter the END command (or press PF3 using the default PFK definitions) to return tothe Summary of Features/Elements panel.

2. On the Summary of Features/Elements panel, select entries to be moved to a newvolume and press Enter. The Logical Volume by Feature/Element panel is displayed.

3. The Logical Volume by Feature/Element panel lists the logical volumes that have beendefined for the feature or element. Write down the names of the logical volumes to bemoved. Enter the END command to return to the Summary of Features/Elements panel.

4. Enter the SUML primary command to display the Summary of Logical Volumes panel.

5. On the Summary of Logical Volumes panel, select the logical volumes to be moved.Specify line command A for the volumes. Assign a physical VOLSER to the logicalvolume. Enter the END command.

6. On the Summary of Features/Elements panel, enter the SUMP command to display theSummary of Physical Volumes panel. The new volume is shown.

Changing the attributes of a physical volume

When you select a physical volume from the Summary of Physical Volumes panel (throughline command S), the panel shown in Figure 137 on page 184 is displayed.



� � CustomPac ------------- Modify System Layout ( MD000277 ) --------------------- COMMAND ==>

Display and Change Volume Attributes

Volume Serial ==> MVSCAT (Always required)

Device Number ==> 00C0Device Type ==> 3390-3 (Enter ? For List of Available Devices)

(See Device Type Table for UNIT Type)

Reserved Space ==> 0 (Cylinders)

Initialize Volume ==> Y (Y or N. Default is Y)

Press Enter to continue or End to Cancel

Note: Only the volume serial is required for online volumes when theDYNAMIC DASD INFO variable is set to Yes.

� �

Figure 137. CPPP605J - ASSIGN a Physical Volume

You can change these attributes for a physical volume:

Volume SerialA unique name for the physical volume, you cannot use a name that is already definedto the dialog.

Device NumberA unique device number for the volume, in hexadeciaml. Each physical volume thatyou define in the dialog must have a unique device number. This field is filled in onlyif the DEFAULT DASD INFO variable is set to NO.

Device TypeA device type that is defined to the dialog.

For a list of available device names, enter a question mark (?) in the Device Type field.A pop-up window - Defined Device Types - displays the currently-defined device typesand their storage capacities (in cylinders).

By default, the device name is 3390-9.

If space re-calculation is required because the new physical volume has a differentdevice capacity, the dialog recalculates the space automatically.

This field is filled in only if the DEFAULT DASD INFO variable is set to NO.

Reserved SpaceAmount of space, in cylinders, that you require to be reserved on the volume. Specify avalue from 0 to 999. The maximum allowed value is the maximum allocatable space onthe volume, minus one cylinder. The default is 0 (no space is reserved).

To accommodate libraries that can use secondary extents, allow at least 15 percent freespace for each physical volume allocation.

Initialize VolumeUse this field to specify whether the dialog is to initialize the volume. Valid values areY or N (yes or no). The default is Y. If the volume already contains data that you wishto preserve, specify N.



IBM recommends that you defragment any existing volumes that you plan to use fordata sets supplied with your order. Also, to avoid a warning message, ensure that theVTOCs of existing volumes are placed at the beginning or end of each volumes

Also, check the names of data sets on the existing volumes; these names must beunique. They must not duplicate names of data sets shipped with your CustomPac order,or with product-specific VSAM data sets or HFS data sets that you create when yousubmit your installation jobs.

In checking for duplicate names, note that a name that includes an SSA prefix isconsidered to be the same as the name without the prefix. For example, within anexisting volume, data sets named ‘XYZ’ and ‘ssa.XYZ’ are considered to be duplicates.

Changing an SMS storage class

When you select a storage class from the Summary of Physical Volumes panel (through linecommand A), the following panel is displayed.

� �CustomPac ------------ Modify System Layout ( MD053718 ) -----------COMMAND ==>

ASSIGN a Storage Class

STORAGE CLASS : SMSDCLAS

NEW STORAGE CLASS ==> SMSDCLS2

The STORCLAS you specify must be defined to SMS

� �

Figure 138. CPPP605Q - Assign a Storage Class

To change the storage class, enter the 1-8 character name of the new storage class. Thestorage class you choose must be defined in the active SMS configuration before you run thefirst installation job that allocates a data set on an SMS-managed volume in this storageclass.

You can also use ACS routines to override the storage classes that are assigned in the jobsgenerated by the dialog. In this case, the acceptable values for the storage class you enter aredetermined by the ACS routines.

Confirming Processing Requirements

The panel in Figure 139 on page 186 is an example of what is displayed when you haveattempted to exit the Modify System Layout when problem exist. This panel is tailored toshow only the problems that actually exist, so any actual panel displayed would likely showfewer problems. The panel shown in Figure 139 on page 186 would be displayed only ifyou attempted to exit the Modify System Layout when one or more of the followingsituations exist:

• At least one physical volume has an invalid device number. The logical volume table isshipped with the device numbers set to CCUU. You must change CCUU to a validhexadecimal device numbers.

• Problems were encountered with physical volumes.



• SMS is not active on the driving system.


``````````````````````````````````````````````````````````````````````````````````` Warning! `````````` Configuration Problem Found `````````` `````````` Press ENTER to return to Modify System Layout. `````````` Press END or RETURN to save the current values and exit. `````````` ```````````````````````````````````````````````````````````````````````````````````

Problem Type What to do: ---------------------------- ------------------------------------------------- Physical Volume See Physical Volume Summary Display for more info

SMS Subsystem NOT active Activate SMS subsystem

� �

Figure 139. CPPP6058 - CONFIRM Processing Requirements

To continue working with the configuration, press the ENTER key and correct the problemsidentified on the panel.

To exit the panel, press the END key. Your subsequent work with the dialog resumes at theModify System Layout function.


Defining Alias-to-Catalog Connections

Chapter 12. Defining Alias-to-Catalog Connections

NOTE

This is only required for SystemPac (COPY format), ServerPac and FunctionPac.

The dialog and the installation process for CustomPac use the standard order of catalogsearch when defining and locating data sets. Therefore, there must be an alias in the targetsystem master catalog for each high-level qualifier used for data sets that will be catalogedin a user catalog.

This dialog allows you to define a catalog data set name for each alias in your order.

Define CATALOG data set Names

� � CustomPac -------------- ALIAS to CATALOG ( MD000277 ) ------ ROW 1 TO 9 OF 9 COMMAND ==> SCROLL ==> PAGE

Define CATALOG Data set Names

Primary Commands:(? SET Locate Find Next Previous SORT CANcel SAVE)Line Commands:(Delete Insert Repeat Mcat NoMcat)

S Alias STA TARGET System Catalog DSName Type- -------- --- -------------------------------------------- ----

COB2 ???????.CATALOGGIM ???????.CATALOGICQ ???????.CATALOGIPO1 M ?MASTER.CATALOG MCATISP ???????.CATALOGISR ???????.CATALOGNETVIEW ???????.CATALOGSMPE ???????.CATALOGSYS1 M ?MASTER.CATALOG MCAT

******************************* BOTTOM OF DATA ********************************

� �

Figure 140. CPPP6021 - Define CATALOG data set Names

The catalog names are initially shown as "???????" because they are not yet defined. Youcan specify the catalog name with which an alias is to be associated by typing over thequestion marks in the Target System Catalog Data Set Name field. Blank out the rest of theline after the catalog name.

To associate the master catalog with an alias, type over ?MASTER.CATALOG with theactual master catalog name. Then, to use the master catalog for another alias, enter thefollowing:

HP2.?MCAT

Chapter 12. Defining Alias-to-Catalog Connections 187


To use a catalog name that is already defined for another alias, enter a question mark (?),followed by the alias name, for example:

HP2.?SYS1

If a data set must be in the master catalog, then all data sets with the same high levelqualifier must be in the master catalog. If you do not want all data sets with that high levelqualifier to be in the master catalog, you can either:

• Rename the data set that must be in the master catalog to use a high level qualifier thatis cataloged in the master catalog (SYS1, for example), or

• Rename the data sets that should not be in the master catalog to use a high levelqualifier that will cause them to be cataloged in a user catalog.

STA field indicates, for each currently-existing high level qualifier, which ones must beassociated with catalogs because data sets starting with them existed at the conclusion ofModify System Layout, and which of them must be associated with the master catalog. Thisfield can show any of the following values:

blank This high-level qualifier can be associated with any catalog. You mustassociate this high-level qualifier with the master catalog or a user catalog.

M This high-level qualifier must be associated with the master catalog.

U This high-level qualifier is not associated with any of the data sets in thework configuration. You created it with the R or I line command on thispanel. You must associate it with the desired catalog.



CANCEL This command, abbreviated to CAN, discards any changes that you havemade since the last checkpoint and exits the Specify Catalogs for HLQfunction. (A checkpoint is taken when you enter and exit the function, andafter any SAVE command).

SAVE This command saves any changes that you have made and establishes a newcheckpoint. (A checkpoint is taken when you enter and exit the function, andafter any SAVE command).


D Delete a user-defined alias (only aliases with a status (STA) of "U" can bedeleted). You must confirm your delete request on the panel that results.Confirm deletion by entering DELETE in the COMMAND ==> field andpressing Enter.

I Insert a user-defined alias. You must specify the alias and catalog name onthe panel described in “INSERT a USER Defined Alias” on page 190.

R Repeat the insertion of a user-defined alias. You must specify the alias name,but the catalog name is copied from the alias on which you entered thiscommand. See “INSERT a USER Defined Alias” on page 190.

When an order does not contain any aliases that must be cataloged in the mastercatalog (often, a subsystem order), this panel shows the following line commands only:



M Associate the high-level qualifier's alias with the master catalog (the Typefield is set to MCAT).

N Delete an existing master catalog association (the Type field is reset toblanks). You can use this command to reverse the effect of entering linecommand M earlier, if you change your mind.

When you exit the Define Alias to Catalog Relationships function, your changes areautomatically saved. The dialog checks to ensure that all aliases are associated with validcatalog data set names. If not, the panel described in “Confirm Processing Requirements” onpage 190 is displayed to prompt you for a correct name.

DELETE a USER Defined Alias

This panel is displayed when you have requested that a USER defined alias be deleted.

� � CustomPac -------------- ALIAS to CATALOG ( MD000277 ) ------------------------ COMMAND ==>

DELETE an Alias to Catalog Connection

```````````````````````````````````````````````````````````````````````````````````` ```````````````````````````````````````` GLANDALE ```````````````````````````````````````` ````````````````````````````````````````````````````````````````````````````````````````` `````````` CATALOG.ICK.GLASS9 `````````` `````````` `````````` `````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````



� �

Figure 141. CPPP6024 - Confirm Delete Request

You must confirm deletion by typing DELETE in the COMMAND ==> field andpressing ENTER.

NOTE

This processing only removes the alias to catalog definition from CustomPacprocessing, if a physical connection already exists (maybe because you are re-installingthe package), then the physical connection will not be deleted .. this must be donemanually.



INSERT a USER Defined Alias

This panel is displayed when you have requested that a USER defined alias be inserted.

� � CustomPac -------------- ALIAS to CATALOG ( MD000277 ) ------------------------ COMMAND ==>

INSERT (REPEAT) Alias Details

ALIAS Name ==> GLANDALE

Catalog DSNAME ==> CATALOG.ICK.GLASS9

� �

Figure 142. CPPP6023 - Specify Alias and Catalog Names.

The following fields are required -

ALIAS This is the USER defined alias, to be defined as part of the CustomPacinstallation process.

The alias may be associated with a master catalog or a USER catalog.

CATALOG This is the catalog data set name, which may be a master catalog or a USERcatalog.

SHORTCUT

If you wish the catalog name to be the same as that already defined for another alias,then -

Enter a question mark "?" immediately followed by the model alias name .. EG. ?SYS1

If you wish the master catalog name to be used, then -

Enter the shortcut ?MCAT


This panel is displayed when you have requested that the Define Alias to CatalogRelationships dialog be terminated, but not all relationships have been supplied, or were inerror.



� � CustomPac --------------- ALIAS to CATALOG ( MD000277 ) ----------------------- COMMAND ==> SCROLL ==> HALF


````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````` `````````` Some Alias to Catalog Relationships have not `````````` been defined OR were Invalid `````````` `````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````



� �


One (or both) of the following situations exist -

• At least one alias has not been defined.

(The Catalog DSNname is BLANK).

• At least one alias has an invalid Catalog DSName.

If you press ENTER then you may continue editing the Alias Data.

If you press the END/RETURN key then you will exit the dialog, but future processing willresume at the Define Alias to Catalog Relationships dialog.


Defining SSA-to-Catalog Connections

Chapter 13. Defining SSA-to-Catalog Connections

NOTE

This is NOT applicable to Selective Follow On Services. For ProductPac orRefreshPac with Indirect Reference volumes, this option will be SKIPPED and amessage will be displayed to inform user of this condition.

data sets shipped with your order need to be installed by a DRIVING system.

It is VERY likely that data sets meant for the TARGET system will also exist in their ownright on the DRIVING system.

This dialog defines SSA's (System Specific Aliases), allowing the DRIVING system toaccess the TARGET system catalog(s) without danger of destroying data sets on theDRIVING system.

CATALOG Selection List

� � CustomPac ---------------- SSA to CATALOG ( MD000277 ) ------ ROW 1 TO 4 OF 4 COMMAND ==> SCROLL ==> PAGE

CATALOG Selection List

Primary Commands:(? CANcel SAVE)Line Commands:(Select)

Allocate Define| |

S Catalog Name SSA Name Type VOLume | | Unit - -------------------------------------------- -------- ---- ------ - - ----

NET.CATALOG ? UCAT Y YSMOMP.CATALOG ? UCAT Y YTSO.CATALOG ? UCAT Y YVS4.MASTCAT ?MCAT MCAT Y Y

******************************* BOTTOM OF DATA ********************************

� �

Figure 144. CPPP6031 - CATALOG Selection List

For a software upgrade installation, the target system's master catalog must already exist (theAllocate field is set to N and cannot be changed). User catalogs can be new or existingcatalogs.



When you first display the Catalog Selection List panel, you might see a message warningyou that you have not defined at least one SSA. If you try to exit this panel beforecompleting the SSA definitions, the message reappears. Whether you receive this messageor not, you should ensure that the needed SSA definitions exist and that any SSA definitionsinherited from a saved configuration are still valid.


? This is a standard CustomPac table handling commands.(See “The Primary Commands” on page 9)

CANCEL This command, abbreviated as CAN, discards any changes that you havemade since the last checkpoint and exits the Define SSA to CatalogRelationships function. (A checkpoint is taken when you enter and exit thedialog and after any SAVE command).

SAVE This command saves any changes you made, and establishes a newcheckpoint. (A checkpoint is taken when you enter and exit the dialog, andafter any SAVE command).


S Selects a catalog, allowing you to specify:

• SSA• When an SSA is to be used for this catalog, the SSA name• Whether the catalog is to be allocated• When the catalog is to be allocated, the unit and volume• When the catalog is to be allocated, its size

Enter line command S for a data set name on this panel and press Enter todisplay the next panel, which is described in “Define SSA and CATALOGData”). After you define the SSAs, the dialog displays the Catalog SelectionList panel again with the updated SSA information. When you are satisfiedwith the results, return to the Installation Menu panel. (Figure 28 onpage 52).

Define SSA and CATALOG Data

This panel is displayed when you want to define the physical attributes of a catalog.

Chapter 13. Defining SSA-to-Catalog Connections 193


� � CustomPac --------------- SSA to CATALOG ( MD000277 ) ------------------------- COMMAND ==>


Catalog : SMOMP.CATALOGType : UCAT

Alloc Catalog ==> Y ( Y or N )Define SSA ==> Y ( Y or N )

SSA Name ==> USMOMP

----------- If Alloc Catalog = Y --------------------------

DASD Volser ==> MVSDLB (? For List of Available Vols)

Pri.Space ==> 6 (1-999 Cylinders)Sec.Space ==> 2 (1-999 Cylinders)

� �

Figure 145. CPPP6033 - Define SSA and CATALOG Data

In the panel, the fields are as follows:

Catalog Name of the catalog for which an SSA is to be defined

Type Type of catalog. MCAT indicates a master catalog; UCAT indicates a usercatalog.


SSA Name This is the System Specific Alias used by the DRIVING system to locate adata set on the TARGET system.

Alloc CatalogThis must be set to Y if the catalog does not already exist on the TARGETsystem, and is to be physically allocated.

This must be set to N if the catalog already exists on the TARGET system, itmust NOT be allocated again.

Define SSA This must be set to Y if the SSA is not yet connected to master catalog of theDRIVING system, and is to be defined.

This must be set to N if the SSA is already defined in the master catalog ofthe DRIVING system, it must NOT be defined again.

NOTE

If the Alloc Catalog field was set to Y then this field must also be set toY.

DASD VolserThis is the volume serial of the DASD on which the catalog is to reside.

The volser may only be one of those defined in the Modify System Layoutdialog (SUMP command).

Specify a volser of ? for a list of available volsers

(you may select a volser by entering S, it will be inserted in the volser field).



If you wish to use a volser that is not in the list, then you must re-select theModify System Layout dialog and define it.

(See Chapter 11, “Modify the System Layout” on page 107).

Space This is the PRIMary and SECondary space to be allocated to the catalog.

Defining SSA data for software upgrade

For a software upgrade installation, two panels are used to define SSAs: one for have takenthe Software Upgrade install path. the master catalog and one for user catalogs.

Note: For software upgrades, if the driving system master catalog is the same as the targetsystem master catalog, do not expect an alias connection to be defined in the driving systemmaster catalog. The connection is not necessary because the driving system master catalogand the target system master catalog are the same catalog.

For the master catalog, define your SSAs with the panel shown in Figure 146.


Define SSAs

Catalog : VS4.MASTCATType : MCAT

SSA Name ==> CVS4 (Required)

� �

catalog

Figure 146. CPPP6035 - Define SSA and catalog data (software upgrade) master

In the panel, the fields are described as follows:

Catalog Name of the catalog for which an SSA is to be defined.

Type Type of catalog. Always MCAT, indicating the master catalog.

Define the following field:

SSA Name Specifies the system-specific alias to be used to locate target system data sets.The name you choose must not have an existing alias entry in the drivingsystem's master catalog, and cannot be the same as the high-level qualifier ofany data set cataloged in the driving system's master catalog. For a software



upgrade installation, these same restrictions apply to existing entries in thetarget system's master catalog.

For user catalogs, define your SSAs with the panel shown in Figure 147.



Catalog : SMOMP.CATALOGType : UCAT

SSA Name ==> USMOMP (Required)

Allocate Catalog ==> Y ( Y or N )

If allocating the catalog, the following information is required:

Volume ==> MVSDLB (? For List of Available Vols)Primary Space ==> 6 (1-999 Cylinders)Secondary Space ==> 2 (1-999 Cylinders)

� �

Figure 147. CPPP6036 - Define SSA and catalog data (software upgrade)

In the panel, the fields are described as follows:

Catalog Name of the catalog for which an SSA is to be defined.

Type Type of catalog. Always UCAT, indicating a user catalog.

Define the following field:

SSA Name Specifies the system-specific alias to be used to locate target system data setsthat will be cataloged in the specified catalog. The name you choose must nothave an existing alias entry in the driving system's master catalog, and cannotbe the same as the high-level qualifier of any data set cataloged in the drivingsystem's master catalog. For a software upgrade installation, these samerestrictions apply to existing entries in the target system's master catalog.

Allocate CatalogSpecifies whether to allocate the catalog. Set this value to Y (yes) if thecatalog does not yet exist on the target system, and is to be allocated. Set thisvalue to N (no) if the catalog already exists on the target system; it cannot beallocated again.

Catalog VolumeIf you specify that the catalog is to be allocated (that is, you set the AllocateCatalog field to Y), use the Catalog Volume field to specify the volume serialof the DASD on which the catalog is to reside. For a pop-up list of volumesthat exist in the work configuration, enter a question mark (?). Select avolume by entering S before the desired volume serial. You are not requiredto choose a volume from the list. Any volume serial may be specified; if itdoes not exist, it is added to the configuration.



If the volume you specified already exists in the work configuration, the unityou specify here must match the unit value you specified previously.Otherwise, a message is displayed to prompt you to resolve the mismatch.

If you did not specify that the catalog is to be allocated (you set the AllocateCatalog field to N), do not enter a value for this field.

Space Specifies the primary and secondary space to be allocated to the catalog, ifthe catalog does not yet exist on the target system and must be allocated. Seethe section "Determining Catalog Size" in z/OS DFSMS Managing Catalogs,SC26-7409 for information on how much space to allocate for catalogs.


If, when you try to exit the Specify Temporary Aliases (SSAs) for Catalogs function, thedialog detects an invalid catalog alias definition or (for a software upgrade installation) thatthere is not at least one catalog alias defined, the panel shown in Figure 148 is displayed.

� � CustomPac ---------------- SSA to CATALOG ( MD000277 ) ------------------------ COMMAND ==>


````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````` `````````` `````````` Some Catalog to SSA Relationships have not `````````` been defined OR were Invalid `````````` `````````` `````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````



� �


To continue working with the configuration, press Enter.

To exit the function, press End. Subsequent processing of the dialog resumes at the SpecifyTemporary Aliases (SSAs) for Catalogs function.


Submitting Installation Jobs

Chapter 14. Submitting Installation Jobs

JOB Selection List

From the Installation Menu, enter I to begin the next dialog function, Select and SubmitInstallation Jobs. The Job Selection List is displayed (Figure 149), showing the installationjobs, plus any additional jobs you might have defined.

IBM recommends that you use the GENSKEL command to tailor all of the installation jobsat one time. When GENSKEL completes, the dialog saves the jobs in a backup data set.You can select the jobs from the backup data set through line command B (rather than linecommand S). GENSKEL saves you time during installation, and free your TSO/E sessionfor other tasks while the jobs are being tailored. For more information, see “GenerateInstallation Jobs (GENSKEL)” on page 202.

� � CustomPac -------------- Installation JOBs ( MD000277 ) ---------------------- COMMAND ==> SCROLL ==> HALF

JOB Selection List SS$( EXCLUDE )

Primary Commands:(? SET Locate Find Next Previous GENskel OFile OList SUMmarySS$ VARedit)

Line Commands:(Backup Delete Edit Insert Log Output Select SS-block Vars)

S Description STEP MC STAtus RC -- --- ---------------------------------------- -------- -- ---------- ----

SRC DEFAULT JOBCARDJOB COPY TEST LOGS FOR PREVIOUS INSTALL $IDCAMS 12 JOB04090 0012DOC COBOL LB CMP DBG ENU 1.04 0

==> PACKAGE SPECIFIC INSTALLDOC PACKAGE INSTALLATION STEPSJOB OFFLINE INIT OF DASDS OFFLINIT 00 JOB04092 0000JOB DEFINE VVDS DATASETS DEFVVDS 00 JOB04093 0000JOB COPY SISBCIE TO AUTHORIZED LIBRARY COPYSIS 04 JOB04096 0000JOB DEFINE CATALOGS DEFCAT 00 JOB04097 0000JOB DEFINE SYSTEM SPECIFIC ALIASES DEFSSA 00JOB ALLOCATE AND CATALOG DS ALLOCDS 00JOB RENAME DS TO FINAL NAME ALTCAT 00JOB COPY DATASETS TO SYSTEMPAC VOLS RESTORE 04

� �

Figure 149. CPPP6121 - JOB Selection List

At this stage of the installation process, your primary source of information is CustomPac:Installation Guide. This chapter supplement the information in that book. When you havefinished running the installation jobs and verification programs (IVPs) described inCustomPac: Installation Guide, you continue with Chapter 15, “Saving the Configuration”on page 211.

The panel displays only the jobs and documentation that are required to install your order,based on the installation type that you chose earlier in the installation (full systemreplacement or software upgrade).

The "Table of Jobs" in CustomPac: Installation Guide lists all of the jobs and indicates theinstallation type to which they apply (full system replacement or software upgrade).



The job selection list includes the maximum return code ("MC") of the "STEP", the status ofthe "STEP" and the actual return code of the "STEP". For a system abend, the RC fieldshows "SYST".

As Figure 149 on page 198 shows, the installation jobstream has three types of"components," as follows:

SRC Identifies the default job statement (or "source data"). The source data alwaysappears first in the jobstream. You can browse it by selecting it, or edit itthrough ISPF EDIT.

DOC Identifies a part of the tailored documentation for your order. You can browsethe documentation by selecting it.

JOB Identifies an installation job for your order. If you enter S for the job, thedialog displays the job, tailored according to your work configuration. Youcan submit the job for execution.

If you include the job within a set of block Select (SS) line commands, thedialog tailors all the included "STEPs" into a single job and displays it.

If you enter B for the job (and have run GENSKEL), the dialog displays thepreviously-tailored job.

You can always edit a job and submit it, no matter how you select it. Note,however, that your changes will be saved only if you:

• Use the ISPF EDIT CREATE command to save the altered job, or• Use the ISPF EDIT REPLACE command to create a BACKUP member,

or• Edit an IBM-supplied job in the backup library (SCPPBENU), or• Edit a user-supplied job in the skeleton library (SCPPSENU).


? SET Locate Find Next PreviousThese are standard CustomPac table handling commands.(See Chapter 2, “Understanding The Dialog” on page 7)

GENSKEL This may be abbreviated to GEN

This command will submit a BATCH job to generate the installation jobs forALL jobs.

Each file tailored job will be stored in the SCPPBENU data set.

(See “Generate Installation Jobs (GENSKEL)” on page 202).

SUMMARY This may be abbreviated to SUM

This command displays the processing LOG, which contains a list of all jobssubmitted from the job stream and their return codes.

If output logging is active then the job output may be browsed.


SS$ This command controls whether USER defined JOBs should be included infile tailored JCL when selected by the SS line command.

The SS$( ??CLUDE ) field shows the current status.

Issuing the command reverses the current status -

Eg. EXCLUDE -> INCLUDE -> EXCLUDE

Chapter 14. Submitting Installation Jobs 199


VAREDIT This may be abbreviated to VAR

This command is a "fastpath" into the Installation variables dialog.


ALL variables are re-loaded on exit from the dialog, changes to data valueswill be available for immediate use.


B Backup

This command is only valid for a JOB component.

The JCL for the JOB is retrieved from the backup library (SCPPBENU) andplaced into ISPF EDIT status.

The job may be submitted to the internal reader for execution.

(See “EDIT Session - B” on page 208).

D Delete

This command is only valid for a USER defined JOB component.

The JOB will be deleted (any Processing LOG entries will remain).

You will be required to confirm your DELETE request.

(See “Delete a USER Defined JOB” on page 205).

E Edit

This command is only valid for a SRC or USER defined JOB component.

The source data or JCL for the JOB is retrieved from the skeleton library(SCPPSENU) and placed into ISPF EDIT status.

• Source data may be edited.

• USER defined JOBs may be submitted to the internal reader forexecution.

(See “EDIT Session - B” on page 208).

I Insert

A USER defined JOB will be INSERTED into the job stream.

(See “INSERT a USER Defined JOB” on page 205).

L Log

This command displays the processing LOG for the selected job, whichcontains a list of all executions of the job and their return codes.

(The job may have been run more than once due to previous processingfailures .... etc).

If output logging is active then the job output may be browsed.

This command uses the same processing as for the SUMMARY PRIMarycommand.




O Output

If output logging is active then the job output will be placed into ISPFBROWSE status, the maximum return code issued for the job will be placedin the RC field.

If output logging is NOT active only the processing status of the job will bereported.

Eg. 'ON OUTPUT QUEUE'

S Select

If the selected component is a JOB -

• The JCL for the JOB is retrieved from the skeleton library (SCPPSENU),file tailored and placed into ISPF EDIT status.

The default JOBcard is automatically inserted before the STEP JCL.(Unless it is a USER defined JOB and the MAX return code field isBLANK).


(See “EDIT Session - S” on page 210).

Hint

You are recommended to use the GENSKEL primary command tofile tailor all jobs in a batch job. Using Select command inforeground mode may cause timeout.

If the selected component is a DOC or SRC -

• The DOC/SRC data is retrieved from the skeleton library (SCPPSENU),file tailored and placed into ISPF BROWSE status.

SS Block Select

This is a block command, mark the start and end of a block of jobs with theSS command pair.

The marked block may contain any kind of component, but only JOBcomponents are selected.

If USER defined JOBS are contained in the block, then they will only beselected if the current setting of the SS$ command indicates INCLUDE.

The JCL for the JOBs are retrieved from the skeleton library (SCPPSENU),file tailored and placed into ISPF EDIT status.

The default JOBcard is automatically inserted before the first STEP JCL.


(See “EDIT Session - S” on page 210).

NOTES: Block Selection Mode, JOBCARD Handling

When you select several job steps to be executed within the same job, thesteps will be generated so as to execute in the correct sequence. There willbe only one JOB statement, generated before the first step in the sequence.

Sometimes the installation process includes steps which are NOT based onCustomPac skeletons, but from product specific generation jobs.



One example is the step CALLLINK, which is generated by the new SMP/EREPORT CALLLIBS command. This member has its' own jobcard beforethe step, there is NO way to generate the job without the jobcard.

If this step were selected using the block SS command the generated jobwould include a second jobcard from the CALLLINK step.

Steps that have their own jobcard can be identified by a blank MC field.

The following example illustrates this -

S Description STEP MC STAtus-- --- ---------------------------------------- -------- -- ----------

DOC BUILD POST APPLY LINKSJOB BUILD POST APPLY LINKS CALLJOB 00 JOB05195JOB EXECUTE POST APPLY LINK CALLLINK

==> PRODUCT SPECIFIC INSTALL

Step CALLLINK will not include the standard JOBCARD but will have its'own generated job statement.

Important

You are recommended NOT TO USE the block selection method forsteps with a blank MC field.

V Vars

This command is only valid for a JOB component.

The Installation Variables Dialog is invoked, showing only CustomPacvariables (those prefixed with F) and User Defined variables (those prefixedwith $) for the selected job.

If any of the variables are NOT defined, then a variable status panel will bedisplayed BEFORE entry to the Installation Variables dialog.

Any variables flagged as ** ERROR ** Undefined must be defined toensure successful generation of the job.


ALL variables are re-loaded on exit from the dialog, changes to data valueswill be available for immediate use.

Note: For execution of the jobs in the Job Selection List, refer to Section 8 in theInstallation Guide.

Generate Installation Jobs (GENSKEL)

This panel is displayed when the GENSKEL primary command is entered from theInstallation Jobs display.



� � CustomPac -------------- Installation JOBS ( MD000277 ) ----------------------- COMMAND ==>

GENERATE File Tailored Installation Jobs

This function generates a BATCH job which will file tailorALL Installation Jobs in one pass, and save the jobs to theBACKUP dataset.

If a job already exists in the backup dataset

REPLACE Job ==> Y (Y or N)

Note: After submitting the GENSKEL job, you must exitthe dialog to release GENSKEL processing. Also,to avoid dataset contention, you may not invokethe dialogs until the GENSKEL job has completed.

� �

Figure 150. CPPP6126 - Generate Installation Jobs

You must tailor each of the installation jobs before you submit them. You can use theGENSKEL command to tailor installation jobs in the background. GENSKEL generates theinstallation jobs for your order, and stores them in the backup data set (SCPPBENU).Having the installation jobs stored in SCPPBENU allows you to review them, if desired,after the order is installed.

File-tailored jobs might already exist in the SCPPBENU data set. Specify whetherGENSKEL is to replace these jobs or preserve them. Set the Replace Job field to Y toreplace jobs; set the field to N to preserve them.

Press Enter to generate the GENSKEL job. Then, submit the job with the SUBMITcommand. Exit the dialogs until the GENSKEL job completes.

For your convenience, the Job Selection List panel displays only the installation jobs thatapply to your order's installation type (full system replacement or software upgrade). Toview the entire set of jobs generated by GENSKEL, including jobs that are not needed foryour installation type, check the SCPPBENU data set. (The GENSKEL output lists allgenerated jobs in the SYSPRINT output data set. ) To access these jobs, enter line commandB on the Installation Jobs display.

Selecting Job Output LoggingWhen you submit a job for execution, the job number is written to a processing log.

You can capture the job output by having it written to data set SCPPOENU. Doing sorequires that you set the installation variable synonym OUTPUT LOGGING to YES. Thejobname also needs to be the users id plus a character.

The process for setting installation variables is described in Chapter 8, “DefiningInstallation Variables” on page 76.



If data set SCPPOENU runs out of space, rename it, and allocate a new one with morespace. Copy the renamed data set into the new SCPPOENU data set and then delete theoriginal.

Processing LOG

The display shows all jobs submitted from the job stream and their return code.

� � CustomPac -------------- Installation JOBs ( MD000277 ) ----- ROW 1 TO 5 OF 5 COMMAND ==> SCROLL ==> HALF

Processing LOG

PRIM Cmds:(? SET L F N P SORT) LINE Cmds:(Output)

S STEPname JOB name job ID RC UserID DATE stamp - -------- -------- -------- ---- -------- ----------------- $IDCAMS STOB4DCT JOB04090 0012 STOB6 94/09/01 09:06:23 OFFLINIT STOB4A00 JOB04092 0000 STOB6 94/09/01 10:08:46 DEFVVDS STOB4B00 JOB04093 0000 STOB6 94/09/01 10:44:33 COPYSIS STOB4C00 JOB04096 0000 STOB6 94/09/01 11:10:28 DEFCAT STOB4D00 JOB04097 0000 STOB6 94/09/01 13:21:12 ******************************* BOTTOM OF DATA ********************************

� �

Figure 151. CPPP6125 - Processing LOG




O Output

If output logging is active then the job output will be placed into ISPFBROWSE status, the maximum return code issued for the job will be placedin the RC field.

If output logging is NOT active only the processing status of the job will bereported.

Eg. 'ON OUTPUT QUEUE'



Delete a USER Defined JOB

This panel is displayed when you have requested the delete of a user defined job.

� � CustomPac -------------- Installation JOBs ( MD000277 ) ----------------------- COMMAND ==>

DELETE a USER Defined JOB

```````````````````````````````````````````````````````````````````````````````````` ````````````````````````````````````````` $IDCAMS ````````````````````````````````````````` `````````````````````````````````````````````````````````````````````````````````````````` `````````` JOB : COPY TEST LOGS FOR PREVIOUS INSTALL `````````` `````````` Delete Member from the Skeleton Library ==> N `````````` `````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````



� �

Figure 152. CPPP6124 - DELETE a USER Defined JOB - Confirmation

You have requested that a USER defined JOB be deleted.

You are required to CONFIRM your request by typing DELETE in the COMMAND==> field and pressing enter.

The default is NOT to delete the physical skeleton from the skeleton library (SCPPSENU),only the entry for the job in the control table will be deleted.

(This will allow the job to be re-inserted at a later stage).

If you wish the physical skeleton to be deleted, specify Y in the Delete Skeleton field.

INSERT a USER Defined JOB

This panel is displayed when you have requested that a USER defined JOB be inserted inthe jobstream.



� � CustomPac -------------- Installation JOBs ( MD000277 ) --------------- COMMAND ==>


User STEP Name ==> $ IDCAMS:

User Names are ALWAYS a $ plus 1 to 7 characters

Max Return Code ==> 12

Data Description ==> COPY TEST LOGS FOR PREVIOUS INSTALL

� �

Figure 153. CPPP6122 - INSERT a USER Defined JOB


STEP Name This is the name by which you want the JOB to be known.(It is NOT the JOBname !)

It must be unique and NOT already used, if it is used you will receive a"duplicate" message.

NOTE

You are forced to use a $ character as the first character of the STEPname.

The remaining 7 characters may be anything, provided the resulting nameis a valid member name.

MAX Return CodeThis is the maximum expected return code for the step.

If the value is in the range 00-99, then the default JOBcard will beautomatically inserted before the step when file tailoring is performed(Option S from the JOB Selection List).

If the value is BLANKed out, then it is assumed that the USER defined JOBwill already include a valid JOBcard. (NO JOBcard will be automaticallyinserted).

Description This should be a meaningful description of the STEP.

A scan of the skeleton library (SCPPSENU) is made.

If the STEP name you wish to use does not exist as a current member of the library thenEDIT processing is invoked to allow creation of source JCL for the STEP.

(See “EDIT Session - E” on page 209).



If a member currently exists which has the same name as the STEP name you wish to usethen it is possible that -

• It is an OLD version put there by person or persons unknown !

• It is a previously deleted USER defined JOB, but physical delete of the skeletonmember was specified as NO.

It is up to YOU to decide ......

To assist in the decision ...... the member is displayed

� � BROWSE -- GLANDALE.MD000277.SCPPSENU($IDCAMS) ------ LINE 00000000 COL 001 080 COMMAND ===> SCROLL ===> PAGE********************************* TOP OF DATA **********************************//STEP001 EXEC PGM=IDCAMS 00000100//* 00000200//* ********************************************************** 00000300//* * THIS JOB REPROS THE TEST LOGS FOR THE PREVIOUS SYSTEM * 00000400//* * TO DEREKS' USERID DATASETS, THEN DELETES THEM * 00000500//* * * 00000600//* * THE TEST LOGS CONTAIN INSTALLATION VERIFICATION DATA * 00000700//* ********************************************************** 00000800//* 00000900//SYSPRINT DD SYSOUT=* 00001000//* 00001100//SYSIN DD * 00001200

REPRO INDATASET(SYSDEREK.TESTLOG.AYNUK) + 00001300OUTDATASET(GLANDALE.TESTLOG.AYNUK) 00001400

00001500REPRO INDATASET(SYSDEREK.TESTLOG.ALIUK) + 00001600

�� 001700� CPP0612001W User JOB $IDCAMS EXISTS as a member of the File Tailoring � 001800� Library, REVIEW The Contents of the Member � 001900�� 002000******************************** BOTTOM OF DATA ********************************

� �

Figure 154. CPPP612I - BROWSE Existing USER JOB

� � CustomPac -------------- Installation JOBs ( MD000277 ) --------------- COMMAND ==>


`````````````````````````````````````````````````````````````````````````````````````` `````````````````````````````````````````````` W A R N I N G `````````````````````````````````````````````` ``````````````````````````````````````````````````````````````````````````````````````````` `````````` The JOB you have tried to insert EXISTS as a `````````` member in the SOURCE Library `````````` You must verify this member can be used `````````` ```````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````

`` Confirm the Member can be USED, Type USE and pre

`` Press the END or RETURN key to CANCEL the INSERT

� �

Figure 155. CPPP6123 - INSERT a USER Defined JOB - Confirmation



You are required to CONFIRM that the member that exists in the skeleton library can beused as source for the STEP USER defined JOB.

You are required to CONFIRM this by typing USE in the COMMAND ==> field andpressing enter.

If confirmed then EDIT processing is invoked to allow changes to the source JCL for theSTEP.

(See “EDIT Session - E” on page 209).

EDIT Session - B

This panel is displayed when you have issued the Backup line command from the JOBSelection List.

� � CustomPac - BACKUP MEMBER(OFFLINIT) -------------------------- COLUMNS 001 072 COMMAND ==> SCROLL ==> HALF ****** ***************************** TOP OF DATA ****************************** 000100 //STOB4A00 JOB (7928),'DEREK STOBBS ROOM532', 000200 // CLASS=S,MSGCLASS=K,MSGLEVEL=(0,0) 000300 //* 000600 //*------------------------------------------------------------------- 000700 //* GDE: SystemPac INSTALLATION 000800 //* DOC: INITIALIZE ALL NEEDED DASDS. 000900 //* 001000 //* BEFORE RUNNING THIS STEP, BE SURE THAT THE FOLLOWING 001100 //* DEVICES HAVE BEEN PUT OFFLINE : 001200 //* A00 001300 //* B00 001400 //* C00 001500 //* AFTER HAVING COMPLETED THIS STEP, BE SURE THAT ABOVE 001600 //* DEVICES ARE PUT ONLINE. 001700 //* 001800 //* NOTE: THIS JOBS REQUIRES AN OPERATOR RESPONSE FOR EACH DASD TO BE 001900 //* INITIALIZED . 002000 //* 002100 //* MRC: THE MAXIMUM EXPECTED RETURN CODE IS: 0 002200 //*------------------------------------------------------------------- 002300 //OFFLINIT EXEC PGM=ICKDSF,COND=(4000,LT)

� �

Figure 156. CPPP612B - EDIT BACKUP MEMBER

This EDIT session is acting directly on the named member in the backup library(SCPPBENU).

If you delete all records from the member you will NOT be allowed to exit the panel unlessyou issue the CANCEL primary command, a null member is NOT allowed in the backuplibrary.

Standard EDIT commands have the following use when processing a BACKUP job.

CANCEL The EDIT session is terminated, nothing is saved.

END/RETURNIf the backup member has NO records the command is ignored, you areforced to use the CANCEL command.

SAVE If the backup member has NO records the command is ignored.



SUBMIT The job is submitted to the internal reader for execution, the job number iscaptured and stored in the Processing LOG.

EDIT Session - E

This panel is displayed when you have issued the Edit line command from the JOBSelection List.

� � CustomPac - SOURCE MEMBER($IDCAMS) --------------------------- COLUMNS 001 072 COMMAND ==> SCROLL ==> HALF ****** ***************************** TOP OF DATA ****************************** 000100 //STEP001 EXEC PGM=IDCAMS 000200 //* 000300 //* ********************************************************** 000400 //* * THIS JOB REPROS THE TEST LOGS FOR THE PREVIOUS SYSTEM * 000500 //* * TO DEREKS' USERID DATASETS, THEN DELETES THEM * 000600 //* * * 000700 //* * THE TEST LOGS CONTAIN INSTALLATION VERIFICATION DATA * 000800 //* ********************************************************** 000900 //* 001000 //SYSPRINT DD SYSOUT=* 001100 //* 001200 //SYSIN DD * 001300 REPRO INDATASET(SYSDEREK.TESTLOG.AYNUK) + 001400 OUTDATASET(GLANDALE.TESTLOG.AYNUK) 001500 001600 REPRO INDATASET(SYSDEREK.TESTLOG.ALIUK) + 001700 OUTDATASET(GLANDALE.TESTLOG.ALIUK) 001800001900 DELETE SYSDEREK.TESTLOG.AYNUK002000 DELETE SYSDEREK.TESTLOG.ALIUK

****** **************************** BOTTOM OF DATA ****************************

� �

Figure 157. CPPP612E - EDIT SOURCE MEMBER

This EDIT session is acting directly on the named member in the skeleton library(SCPPSENU).

If you delete all records from the member you will NOT be allowed to exit the panel unlessyou issue the CANCEL primary command, a null member is NOT allowed in the skeletonlibrary.

Standard EDIT commands have the following use when processing SOURCE DATA -

CANCEL The EDIT session is terminated, nothing is saved.

END/RETURNIf the source member has NO records the command is ignored, you are forcedto use the CANCEL command.

SAVE If the source member has NO records the command is ignored.

SUBMIT This command is DISABLED .. you cannot submit source data for execution!



EDIT Session - S

This panel is displayed when you have issued the Select line command from the JOBSelection List.

� � CustomPac - JOBSTREAM(DEFVVDS) ------------------------------- COLUMNS 001 072 COMMAND ==> SCROLL ==> HALF ****** ***************************** TOP OF DATA ****************************** 000100 //STOB4B00 JOB (7928),'DEREK STOBBS ROOM532', 000200 // CLASS=S,MSGCLASS=K,MSGLEVEL=(0,0) 000300 //* 000400 //*-------------------------------------------------------------------- 000500 //* DOC: DEFINE THE VVDS DATASETS FOR ALL INITIALIZED DASDS. 000600 //* 000700 //* MRC: THE MAXIMUM EXPECTED RETURN CODE IS: 0 000800 //*-------------------------------------------------------------------- 000900 //DEFVVDS EXEC PGM=IDCAMS 001000 //SYSPRINT DD SYSOUT=* 001100 //SYSIN DD * 001200 DEFINE CLUSTER( - 001300 NAME(SYS1.VVDS.VMVSCAT) - 001400 VOLUMES(MVSCAT) - 001500 NONINDEXED - 001600 CYLINDERS(2 2)) 001700 DEFINE CLUSTER( - 001800 NAME(SYS1.VVDS.VMVSDLB) - 001900 VOLUMES(MVSDLB) - 002000 NONINDEXED - 002100 CYLINDERS(2 2))

� �

Figure 158. CPPP612S - EDIT JOBSTREAM

This ISPF Edit session allows you to edit the job before submitting it. If you make changes,you can save the job in the backup data set by using the BACKUP or REPLACE commandas described below. (To re-select a job you have edited, use the "B" line command to selectit on the previous panel, rather than the "S" line command.)

In this session, ISPF edit commands work as expected, with the exceptions of End, Replace,Save and Submit. The effects of these commands are described, as follows:

END Ends the edit session, but does not save your changes.

REPLACE Replaces an existing backup member (created by the BACKUP command;see below).

SAVE Command is DISABLED.

SUBMIT The job is submitted to the internal reader for execution, the job number iscaptured and stored in the Processing LOG.

Besides the ISPF Edit commands, you can use the dialog's BACKUP command to save thecontents of this edit session in a new member of the backup library, SCPPBENU. When youend the session, the new member is shown in the STEP column in the dialog.

If the member already exists, the BACKUP command is rejected with the message"BACKUP MEMBER EXISTS." (To replace an existing backup member, use theREPLACE command.)

The BACKUP command creates members in the SCPPBENU library only. You cannot useBACKUP to create members in other libraries. You can, however, use the ISPF EditCREATE command to do so.


Saving the Configuration

Chapter 15. Saving the Configuration

After you install a CustomPac order, use the Save the Current Work Configuration functionof the dialog to save your work configuration. Doing so can help you save time in installingsubsequent CustomPac orders. Rather than manually re-entering all of the data required foreach new order, you can merge the saved configuration with the new order and avoid muchof the data entry.

For example, while installing your order, you might have chosen to customize the shippedconfiguration. You might have:

• Merged it with a saved work configuration

• Changed the values of variables

• Added your own user variables and installation jobs

• Changed data set names

• Changed the space allocated for data sets

• Assigned data sets to physical volumes

• Merged data sets

• Changed the catalog configuration.

To keep these settings available for a future order, save the configuration.

Another, equally important reason to save a configuration is to take a checkpoint to whichone can return. You can use the Save command at any time after the work configuration iscreated. If you wish to preserve the work configuration in a particular state (for example, tobe able to return to that state if a subsequent step goes awry), you can save it. You can saveit more than once; each time you save it, the previously saved copy is overlaid. To return tothe saved state, recreate the configuration and select the saved configuration for merging.The work configuration will then reflect the saved configuration. However, you mustre-select each previously-completed option on CPPPFLOW, in turn, before being able toreturn to the option in use when the configuration was last saved.

Figure 159 on page 212 shows the panel that you use to save the work configuration. Todisplay this panel, select option S (Save the Current Work Configuration) from theInstallation Menu.

Chapter 15. Saving the Configuration 211


� � CustomPac -------------- SAVE Configuration ( MD000277 ) ---------------------- COMMAND ==>

Specify SAVE Library

Enter the High Level Qualifier and the Volume Serial or StorageClass of the Library to which the Order Configuration will be saved

Data Set HLQ ==> CPP.MD053718.CONFIG

Volume Serial ==> (Blank for SMS-managed data sets)- or -

STORCLAS ==> (Blank for non-SMS-managed data sets)

The default qualifier used is 'OrderHLQ'.You may enter a Comment to identify the Configuration. Thisis recommended if you use a qualifier other than the default.

==> DEBBIE S Z/OS REL.5 SET-UP WITH RECOMMENDED LAYOUT

MASTER HLQ is : CPPMASTR

� �

Figure 159. CPPP6041 - Save Configuration

Enter the high-level qualifiers for the saved work configuration (up to 35 characters,including the periods). To identify the saved configuration, use your order qualifier as one ofthe specified qualifiers, along with something meaningful (such as CONFIG or SAVECFG).

To your specified qualifiers, the dialog appends one of the following low-level qualifiers tothe data sets in the saved configuration:

SCPPSENU For skeleton libraries

SCPPTENU For table libraries

For example, if the order qualifiers are CPP.MD053718, a good high-level qualifier to usefor the saved configuration would be:

• CPP.MD053718.CONFIG

and the two libraries used to save the configuration are:

• CPP.MD053718.CONFIG.SCPPSENU

• CPP.MD053718.CONFIG.SCPPTENU

For the Volume Serial or STORCLAS fields, enter the serial number of the DASD volumeor a valid storage class (for SMS-managed data sets ) to be used to allocate the configurationdata sets.

If you use ACS routines, ensure that these routines permit the allocation of the dialog datasets, SCPPSENU and SCPPTENU on the specified Volume Serial or STORCLAS. Or,preallocate these data sets before saving the configuration. Otherwise, your SAVEcommand might fail with a dynamic allocation error. For information about writing ACSroutines, see z/OS DFSMSdfp Storage Administration.

Enter a meaningful description in the comment field. Include the release level of the productthat you installed. For example:

DEBBIE S Z/OS REL.5 SET-UP WITH RECOMMENDED LAYOUT



During your next installation of a ServerPac order, you will find the description of the savedconfiguration displayed on the Select Configuration panel as shown in “Creating theConfiguration” on page 59.

If the saved configuration data sets do not exist, the dialog prompts you to confirm that thedata sets can be automatically allocated.

You can save only one configuration for an order. If a saved work configuration exists, thedialog prompts you to confirm that the configuration can be deleted (see Figure 160).Processing cannot continue until you allow the existing configuration to be deleted.

� � CustomPac -------------- SAVE Configuration ( MD000277 ) ---------------------- COMMAND ==>

DELETE an EXISTING Configuration

````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````` `````````` A Saved Configuration already exists in Library `````````` `````````` GLANDALE.MD000277.CONFIG `````````` `````````` This must be DELETED before SAVE can continue `````````` `````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````



� �

Figure 160. CPPP6042 - DELETE an EXISTING Configuration - Confirmation

To CONFIRM that the configuration can be deleted, enter DELETE in the COMMAND==> field and pressing Enter.

Chapter 15. Saving the Configuration 213

Managing the Order Inventory

Chapter 16. Managing the Order Inventory

The Display Orders option allows orders received or installed at a customer site to betracked.

Information available for each order includes -

• The current processing status.• Where the order was loaded.• Product information

Selecting an Order

� � CustomPac ---------------- Select Orders to Display --------------------------- COMMAND ==>

Display Orders by Status:

Received ==> Y (Y or N)Started ==> Y (Y or N)

Installed ==> N (Y or N)**Error** ==> N (Y or N)

� �

Figure 161. CPPP607B - Order Selection

To display only those orders having a specific status, specify a Y for each status type to beincluded in the order display list and an N for each status type to be excluded from the orderdisplay list.

Any field left blank defaults to Y. If all status fields are specified as Y (the default), allorders are shown. The available status selections are -

ReceivedThis status is set when the order can be selected on the order list panel. For ordersdelivered on tape and DVD, this is after the RECEIVE job has run. For orders thatare downloaded, this is after the first phase of the download has been completed.

StartedThis status is set when the work configuration has been created. You can still makechanges to an order that is in the started status.

InstalledThis status is set once the installation jobs for the order have been run. You cannotmake changes to an order that is in the installed status.



**Error**This status is set when the RECEIVE job fails and the failure is detected by the job.(It cannot be set if the job is canceled, abends, or ends due to a system failure.) Whenan order's status is **Error**, examine the output of the RECEIVE job, correct theproblem, and resubmit the job.

If no orders are found that match your selection criteria, a message is issued and the panelre-displayed to allow a different selection criteria to be entered.

Press the END or RETURN key to terminate the Display Orders dialog.

Displaying an OrderWhen you complete the Select Orders to Display panel, a list of orders that matches yourselection criteria is displayed in the Order List panel (Figure 162). (This panel is alsodisplayed if you enter Option I on panel CPPPPOLI.)

� � CustomPac ------------------------ ORDER LIST ------------- ROW 1 TO 13 OF 13 COMMAND ==> SCROLL ==> PAGE

Primary Commands:(? SET Locate Find Next Previous OFile SORT VErbose VERsion)Line Commands:(Select Edit Delete Products Report Output)

--- Last Change -- S Order System Name SREL Package Build Date Status User Date - -------- ----------- ---- -------- ---------- --------- ------- ----------

MD000165 Z038 EXP 1997/05/26 Installed STOB6 1997/05/27MD000166 Z038 EXP 1997/06/30 Installed STOB6 1997/07/07MD000179 P004 HCHK 1997/09/22 Installed STOB6 1997/09/23

MD000181 SYS01 Z038 EXPDD 1997/10/01 Started STOB6 1997/10/14 MD000199 Z038 OMIS 1997/11/12 Installed STOB6 1997/11/17

MD000277 SIM4 MULT SERV 1997/11/13 Received STOB5 1997/11/15 ******************************* BOTTOM OF DATA *******************************

� �

TErse Mode

Figure 162. CPPP6071 - Display Orders - Order List

Chapter 16. Managing the Order Inventory 215


� � CustomPac ------------------------ ORDER LIST -------------- ROW 1 TO 5 OF 13 COMMAND ==> SCROLL ==> PAGE

Primary Commands:(? SET Locate Find Next Previous OFile SORT TErse VERsion)Line Commands:(Select Edit Delete Products Report Output)


Cust Num Cust Name Order Comment - -------- ----------- ---- -------- ---------- --------- ------- ----------

MD000165 Z038 EXP 1997/05/26 Installed STOB6 1997/05/2711997111 GLANDALE Install HBP for VS4 upgrade

- -------- ----------- ---- -------- ---------- --------- ------- ----------MD000166 Z038 EXP 1997/06/30 Installed STOB6 1997/07/0711997111 GLANDALE GRAFF 27

- -------- ----------- ---- -------- ---------- --------- ------- ----------MD000179 P004 HCHK 1997/09/22 Installed STOB6 1997/09/2311997111 GLANDALE Check RACF fixes

- -------- ----------- ---- -------- ---------- --------- ------- ----------MD000181 SYS01 Z038 EXPDD 1997/10/01 Started STOB6 1997/10/1411997111 GLANDALE Install VS5 CLONE

- -------- ----------- ---- -------- ---------- --------- ------- ----------MD000199 Z038 OMIS 1997/11/12 Installed STOB6 1997/11/1711997111 GLANDALE PDF 3.3 FIX FOR 0C4'S

- -------- ----------- ---- -------- ---------- --------- ------- ----------

� �

VErbose Mode

Figure 163. CPPP6072 - Display Orders - Order List


? SET Locate Find Next Previous OFile SORT VErbose VERsionThese are standard CustomPac table handling commands.(See Chapter 2, “Understanding The Dialog” on page 7)


This command sends the list of orders to an external customer defined file.(ALL the orders in the list are sent, not just those displayed on the currentscreen).


VERSION This command may be abbreviated to VER.

The current version date of the Installation Dialog is displayed.



D Delete

This will delete an order from the Order Inventory.

You will be prompted to confirm the delete request.

(See “Deleting an Order” on page 217).

E Edit

This will allow the status of an order to changed, other "documentary" typefields may also be changed.

(See “Editing an Order” on page 218).



P Products

This will display all the data for one order along with its products andFMIDs.

(See “Displaying Products/FMIDs for an Order” on page 220).

R Report

This will write all information associated with an order (including productand FMID information), to the ISPF list data set or to a customer defined dataset.

(See “Report Processing” on page 222).

O Output

This command is NOT valid for an order in receive status.

A list of the installation jobs, and job output for the order is displayed.


NOTE

In order for installation job output to be captured and to be available forthe Output command, the SYSOUT class used for the installation jobsmust be a HELD output class.

Furthermore, NO output will be available until the Installation DialogSelect and Submit Installation Jobs function has been started.

Deleting an OrderThis panel will be displayed when an order has been selected for deletion.

� � CustomPac --------------------- ORDER DETAILS --------------------------------- COMMAND ==>

DELETE an Order

```````````````````````````````````````````````````````````````````````````````````` ````````````````````````````````````````` ORDER DETAILS ````````````````````````````````````````` `````````````````````````````````````````````````````````````````````````````````````````` `````````` Order Number: MD000179 Customer No: 11997111 `````````` Profile : PAC Type : HCHK `````````` SREL : P004 System Name: `````````` `````````````````````````````````````````````````````````````````````

WHEN YOU DELETE THE ORDER ITS RELATEDDATA SETS WILL ALSO BE DELETED



� �

Figure 164. CPPP6073 - Display Orders - DELETE an Order



You are required to CONFIRM the DELETE request.

Type DELETE in the COMMAND ==> field and press enter.

The END or RETURN keys will cancel the delete request.

| NOTE

| This panel will notify you that when the order is deleted, the data sets associated with| the order will also be deleted. You must confirm it by typing DELETE on the command| line and pressing ENTER. You can cancel delete request by pressing the END or| RETURN key.

Editing an OrderThis panel will be displayed when an order is selected for editing through line command Eon the Order Display panel.

� � CustomPac ---------------------- Order Details -------------------------------- COMMAND ==>

Order Number : JE000001Package Type : SERV

Production Date : 2004/08/31SREL : ZO38 ( MVS )

Customer Name : IBM Corp.Customer Number : 1234567

Last Changed On : 2004/09/01Last Changed By : DAVID

Status ==> S (Started, Received, Installed, *System Name ==> SYSA

Comments ==> z/OS R6 5

Last Saved Configuration:

Description ==> z/OS R4 ORDER #1 5Qualifiers ==> DAVID.DO000277.CONFIG4 5

� �

Figure 165. CPPP6074 - Display Orders - EDIT an Order

Update the order information in the panel and press Enter to save the changes. You canchange only the Status, System Name, and Comment fields, and (if they appear), theDescription and Qualifiers fields under Last Saved Configuration. You cannot change theother fields.

The "Last Saved Configuration:" text, the two data entry fields that follow it, the content ofthose fields, and their descriptions are displayed only when there is a saved configuration forthe order. When there is a saved configuration, they appear regardless of the order's status.The following fields are displayed for an order, not all fields are editable.

Order NumberThis value is supplied by IBM.

Package TypePackage Type of the order. Valid values are -



CPP - ProductPacCRMO - Selected Follow on ServiceCRS - RefreshPacEXP - SystemPacEXPDD - SystemPac Dump By data setFPAC - FunctionPacHCHK - Health CheckOMIS - OMISSERV - ServerPac

Production DateProduction date. The date is in the format:

DD/MM/YYYY

SREL System release of the order. These are the SRELs defined by IBM:

C150 - CICSMULT - The order contains MULTiple SRELsP004 - NCPP115 - IMS/DB2Z038 - MVS

Customer NameYour company name.

Customer NumberYour customer number.

Last Changed OnYou cannot change this field. This is the date the status field was lastchanged. It is updated automatically whenever the status field is changed.

Last Changed byYou cannot change this field. This is the userid of the person or program thatlast changed the status field. It is updated automatically whenever the statusfield is changed.

Status The current install status of the order. Possible values are:

R Received

S Started

I Installed

E **Error**

Notes:

1. No data entry value is allowed for a status of **Error**, which can bedisplayed, but not set.

2. Orders having a status of "Finalized", which could be set using priorlevels of the dialog, are displayed as "Installed."

3. For the meaning of each status code, see “Selecting an Order” onpage 214.

4. You must confirm the change in status (see “Verifying the Status of anOrder” on page 223). The normal status sequence is:

• Received >> Started• Started >> Installed



System NameThis optional field is reserved for your use; it is not set by IBM. You can putwhatever you want here or leave it blank.

Comment This is an optional, user-defined field. You can change it at any time.

Description This is an optional, user-defined field. You can change it at any time.

Qualifiers This is an optional, user-defined field. You can change it at any time.

Displaying Products/FMIDs for an OrderThis panel will be displayed when you select an order for display of product and FMIDinformation.

� � CustomPac ---------------- ORDER DETAILS ( MD000277 ) ------------ Row 1 of 12 COMMAND ==> SCROLL ==> HALF

Shipped PRODUCTS/FEATURES

PRIM Cmds:(? SET L F N P SORT OFile) LINE Cmds:<Fmids>

S Product Name PGM# VERsion FMID# - ---------------------------------------- -------- ------- ----- ACF/NCP 7.04.0 5648-063 070400 1 ACF/SSP 4.04.0 5655-041 040400 1

F C/C++ NO DEBUG 5647-A01 020500 8CICS TS ENU 5655-147 010100 16COBL LB CMP DBG ENU 1.04.0 5668-958 010400 8DFSMS-FULL FUNC 5694-A01 010100 2DFSORT RESIDENT 5694-A01 010100 7GDDM-PGF 5694-A01 010100 1Z/OS BASE 5694-A01 010100 113RMF 5694-A01 010100 3SDSF 5694-A01 010100 4SECURITY SERVER 5694-A01 010100 1

******************************* Bottom of data ********************************

� �

Figure 166. CPPP6076 - Display Orders - Display Products for an Order




This command sends the list of products (and related FMIDs) to an externalcustomer defined file.(ALL the products in the list are sent, not just those displayed on the currentscreen).



F FMIDs

This will display panel a panel showing all the FMIDs for a product.

(See “Displaying the FMIDs for a product or feature” on page 221).



Displaying the FMIDs for a product or featureFrom the panel shown in Figure 166 on page 220, you can view the FMIDs for a particularproduct or feature by entering line command F. If the PROCLVL is less than 23.00.00 , theCPPP6079 panel is displayed as shown in Figure 167; if the PROCLVL is equal to or morethan 23.00.00, the CPPP607D panel is displayed as shown in Figure 168.


Shipped FMIDs for PRODUCT/FEATURE C/C++ NO DEBUG

Primary Commands: (? Find Next Previous)Line Commands: (NONE)

FMID------- ------- ------- ------- ------- ------- ------- -------HCKVB00 HLB4701 HLC4731 HTV4721 H24P111 JCKVB03 JLB4702 JTV4722

***************************** Bottom of data *******************************

� �

Figure 167. CPPP6079 - Shipped FMIDs for a product/feature


Shipped FMIDs for PRODUCT/FEATURE Z/OS V1 BASE

PRIM Cmds:(? Find Next Previous) LINE Cmds:(NONE)

FMID DescriptionEDU1H01 ICKDSF - Device Support Facilities - BaseEER3500 EREPEMI2220 MICR/OCRETI1106 TIOCFDU1H07 ICKDSF - Device Support Facilities - ISMF/MODSFDU1H08 ICKDSF - Device Support Facilities - ISMF/ENUHBB7720 BCP BASEHBCNC00 SMP/E Planning and Migration Assistant Software Info BaseHBCNC0B SMP/E Planning and Migration AssistantHBD6602 Bulk Data Transfer BaseHBKM300 BookManager Read/MVS BaseHBKP300 BookManager Build/MVS BaseHBKQ310 Library ServerHCMG110 OS/390 UNIX System Services Connection Manager BaseHCM1710 Hardware Configuration Manager

� �

Figure 168. CPPP607D - Shipped FMIDs for a product/feature

The following Primary Commands are valid for this panel:


NO Line Commands are valid for this panel.



Report ProcessingThis panel will be displayed when you have selected an order whose order data, product dataand FMIDs are to be written to the ISPF LIST data set, or to a customer defined data set.

� � CustomPac ---------------- ORDER DETAILS ( MD000277 ) ------------------------- COMMAND ==>

REPORT File Details

Send REPORT to ISPF LIST Dataset ==> N (Y or N)

OR

Enter Details of the Dataset to which the Report will be Written.

Dataset Name ==> MD001047.REPORT

DISPosition ==> OLD (NEW, MOD, OLD or SHR)

When Allocated NEW (DSORG=PS,RECFM=FB,LRECL=80)

Volume Serial ==> (Default SYSDA )

� �

Figure 169. CPPP6077 - Display Orders - ENTER Report File Details

A report is produced that lists the basic order details along with all products for the order,and all FMIDs for each product.

You may direct the report output to the ISPF LIST data set, or to a customer defined dataset.

You are required to enter values for -

Send REPORT to ISPF LIST data setIf the report is to be directed to the ISPF LIST data set then specify Y, elsespecify N.

The ISPF LIST data set may be made available immediatly after the reporthas been created by use of the TSO LIST command, else it may be printedwhen the current logged on TSO session is terminated.

If the report is directed to a data set, then enter values for -

data set NameThis field is MANDATORY

This is the data set name of the the file to which the output report will bewritten, it may be -

• FULLY qualified, enclosed in single quotation marks.

• Unqualified, where the TSO prefix will be used as the high levelqualifier.

The DCB of the file must be compatible with RECFM=FB, LRECL=80

If the data set exists, and is a PDS, then a member name must be specified.



Examples of acceptable data sets would be -

DSN=USER.REPORT.FB DCB=(RECFM=FB,LRECL=80,BLKSIZE=4000)DSN=USER.REPORT.VB DCB=(RECFM=VB,LRECL=90,BLKSIZE=9004)DSN=USER.REPORT.FB(MEMBER) DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)DSN=USER.REPORT.VB(MEMBER) DCB=(RECFM=VB,LRECL=120,BLKSIZE=124)

DISPosition This is the allocation disposition of the data set, it must be -

OLD An EXISTING data set will be used.SHR An EXISTING data set will be used.NEW A NEW SEQUENTIAL data set will be allocated and cataloged.MOD An EXISTING SEQUENTIAL data set will be used.

Volume SerialThis field is optional.

If the data set is to be created NEW, then it may be allocated on a specificvolume by supplying the VOLUME SERIAL information (which defaults toSYSDA).

Verifying the Status of an OrderThis panel will be displayed when you attempt to change to the status of an order. This canoccur, for example, if you edit the status field (see “Editing an Order” on page 218).

� � CustomPac ---------------- ORDER DETAILS ( MD000277 ) ------------------------- COMMAND ==>

STATUS Change Requested

````````````````````````````````````````````````````````````````````````````````````` ``````````````````````````````````````````` STATUS ATTRIBUTES ``````````````````````````````````````````` ```````````````````````````````````````````````````````````````````````````````````````` ```` Old Status : STARTED ```` ```` New Status : RECEIVED ```` ``````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````

`` You MUST Confirm UPDATE By Typing STATUS and pressing ENTER

`` Press the END or RETURN key to CANCEL the UPDATE request

� �

Figure 170. CPPP607C - Display Orders - Status Verification

The normal status sequence is -

• Received >> Started >> Installed

You requested a status change that does not follow the normal status sequence. This isallowable, but you must confirm it by typing STATUS on the command line and pressingEnter. You can cancel the status change request by pressing End.


Appendixes

Appendixes 225

Appendix A. Accessibility

Accessibility features help a user who has a physical disability, such as restricted mobility orlimited vision, to use software products successfully. The major accessibility features inz/OS(TM) enable users to:

• Use assistive technologies such as screen readers and screen magnifier software• Operate specific or equivalent features using only the keyboard• Customize display attributes such as color, contrast, and font size

Using assistive technologiesAssistive technology products, such as screen readers, function with the user interfacesfound in z/OS(TM). Consult the assistive technology documentation for specific informationwhen using such products to access z/OS interfaces.

Keyboard navigation of the user interfaceUsers can access z/OS(TM) user interfaces using TSO/E or ISPF. Refer to z/OS TSO/EPrimer, z/OS TSO/E User's Guide, and z/OS ISPF User's Guide Vol I for information aboutaccessing TSO/E and ISPF interfaces. These guides describe how to use TSO/E and ISPF,including the use of keyboard shortcuts or function keys (PF keys). Each guide includes thedefault settings for the PF keys and explains how to modify their functions.

z/OS informationz/OS information is accessible using screen readers with the BookServer/Library Serverversions of z/OS books in the Internet library athttp://www.ibm.com/servers/eserver/zseries/zos/bkserv/


Appendix B. Readers Comment Form

Readers Comment Form for CustomPac Installation Dialog Reference Manual.

You may use this form to communicate your comments about the installation dialogs, their organization, subjectmatter or publication, with the understanding that IBM may use or distribute whatever information you supply inany way it believes appropriate without incurring any obligation to you. Your comments will be sent to the author'sdepartment for whatever review and action, if any, are deemed appropriate.

Time (hrs)

DATE CUSTOMER IBM

Order

Receive

Installation

Pre-Installation

Installation

Post-Installation

CUSTOMER SATISFACTION:

very good:_____ good:_____ fair:_____ poor:_____

Problems:

1.During installation (JCL samples, etc.):

Appendix B. Readers Comment Form 227

2.Documentation (Installation Guide, etc.)


Readers Comment Form

Problems:

3. Suggestions (improvements, enhancements, other )

Name:

Telephone:

Please return to :IBM CANADACustomPac Development3600 Steeles Avenue EastMarkham, OntarioCANADAL3R 9Z7

Appendix B. Readers Comment Form 229

Printed in U.S.A.

custompac installation dialog dialog level: 27€¦ · custompac installation dialog reference...

Documents